Jump to content


Photo

Flashing after KK OTA update, unlocked, rooted


  • Please log in to reply
19 replies to this topic

#1 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 23 May 2014 - 05:18 PM

I did all the fancy stuff no problem... went from CM11 to the official KK. Successfully installed the patched CWM from dhacker29 and installed root. I also was able to make a good backup in CWM. 

 

Now - Moto's KitKat basically sucks and i want to go back. I'll be calling CyanogenMod tomorrow to apologize for cheating on them and beg forgiveness.

 

I've tried to flash the latest nightly CM11 and another unofficial build of CM11 and get stuck at the red M bootlogo. I can get back into CWM and restore the stock system just fine.

 

The question: are we not able to flash roms yet?



#2 RikRong

RikRong

    Cap'n Slow

  • Superuser
  • 2,117 posts
  • LocationNoDak
  • Current Device(s):Pixel 7

Posted 23 May 2014 - 09:11 PM

The ROMs out there right now won't work with the new CWM.  I thought I read somewhere that the bootloader was changed, causing CWM to have to be updated, and the ROMs also need to be updated to work with the newer recovery.  


R. Long: Pixel 5

 


#3 livinginkaos

livinginkaos

    I don't know what I'm doing anymore.....

  • Administrator
  • 15,282 posts
  • Google+:Hangouts - livinginkaos@gmail.com
  • LocationOregon
  • Current Device(s):Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7

Posted 24 May 2014 - 04:24 AM

Give it a bit longer and you should see twrp updated. Dhacker put out the cwm for kk just to get everyone by for now. He is waiting for the source code before he can touch it and that will be at least another week or two.

Sent from my Unlocked Moto G


b2wvCBn.png

Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7


#4 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 24 May 2014 - 04:35 AM

Sadly, that's what i figured. Maybe i was just hoping for a ray of light. Thanks to both for the response!

 

 

As a note to you others who think the stock KitKat might me nice... Don't. just. don't.

 

 

/H

~XT926, unlocked



#5 Choiceadvocate

Choiceadvocate

    n00b

  • Members
  • Pip
  • 1 posts

Posted 06 June 2014 - 02:39 PM

As a note to you others who think the stock KitKat might me nice... Don't. just. don't.

Wish I had read this before...

Noob question: Will we eventually be able to flash away KK and go back to something tastier?



#6 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 07 June 2014 - 05:20 AM

Yes. In fact it seems dhacker29 cracked it and *may* be building today... With any luck, he'll release a quick unofficial.

Oh! Did I mention it's 4.4.3?

#7 ibolski

ibolski

    Droid Master

  • Dedicated Supporter
  • PipPipPip
  • 535 posts
  • Twitter:iBolski
  • Google+:Ivan Samuelson
  • LocationColumbus, Ohio
  • Current Device(s):Samsung Galaxy S7

Posted 09 June 2014 - 04:46 AM

Sadly, that's what i figured. Maybe i was just hoping for a ray of light. Thanks to both for the response!

 

 

As a note to you others who think the stock KitKat might me nice... Don't. just. don't.

 

 

/H

~XT926, unlocked

I actually have no issue with it. It performs as well, if not better, than a lot of the other JB custom ROMs out there.

 

I've never ran any of the CM ROMs for the HD, but the performance of my phone has gotten much better under KK.

 

Most people's issues are either taking the OTA, leaving installed apps as is rather than doing a complete FDR and going from there.

 

But, each to his own, I guess. It's too bad it didn't work for you.

 

I would say this to people with unlocked phones, you have a way to go back to whatever your were running before, so it won't hurt anything to try it.

 

Those with locked bootloaders, it all depends. If you're running stock, then it might be worth a try. Otherwise, you might want to hold off since there is no way to revert back to JB and there is no root for locked bootloaders.


VZW Samsung Galaxy S7 Stock and unrooted running Marshmallow 46A, 32gb Nexus 7 unlocked
2cqd4t2.png


#8 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 09 June 2014 - 05:02 PM

Saying that it 'works' is subject to interpretation. Is it better than any version of JB.... Yup.

NO YOU CANNOT RETURN TO WHATEVER IF U TAKE THIS UPDATE. **Capital letters for those who for want to read this whole thread.**

ATM, you have one option -- see below.

However, coming from CM11, I find that stock is terribly unstable. Every app I use that is memory intensive FC's. Several apps aren't listed as running but instead 'restarting'. Responsiveness is barely existent. Maybe I was just spoiled.

My hope with returning to stock was the updated kernel and an assumption that moto had a team of people on it. Looks like they should have taken notes from CM.

dhacker29 got the new kernel running. Once the GPS is operational, I'll flash it (Gps and speaker phone are only things reported inop)

If u have the opportunity, flash CM11 to whatever u drive. I'm sure u won't be disappointed.

Cheers
/h

#9 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,441 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 09 June 2014 - 06:46 PM

Stupid question. Did you fdr when returning to stock or did you try to keep the data partition?

Sent from my SM-P600 using Tapatalk


Non potest esse nisi unus


#10 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 09 June 2014 - 06:57 PM

Not stupid, but yes, FDR. I basically zero'd this thing.

Please don't mistake my pseudo rant. Stock KK is light years better than any JB build to date.

But comparing CM11 (with jb bootloader and kernel) to moto KK, the change was a mistake. Hats off to the devs at cm. I wish i'd have stayed.

Simply fair warning to anyone who was under the same presumption that I was. *** it turns out, I've read numerous posts across the forums of testers experiencing the same issues.

#11 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,441 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 09 June 2014 - 07:07 PM

I had to ask as I've seen people try that before and then complain that the rom or stock or whatever they flashed sucks and crashes and is totally unusable etc. Keeping data in those cases is dangerous. But if you wiped and still had issues, well, yea... That's not great.

Sent from my SM-P600 using Tapatalk


Non potest esse nisi unus


#12 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 09 June 2014 - 07:13 PM

Heh... Understandable, I've seen the same one the last couple years.

There seems to be some serious memory hangups and (of course) a $#!+ ton of bloat ware ruining what Google intended.

Thanks to all for responding

/h

#13 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,441 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 09 June 2014 - 07:16 PM

Makes me appreciate my gpe that much more.

Sent from my SM-P600 using Tapatalk


Non potest esse nisi unus


#14 ibolski

ibolski

    Droid Master

  • Dedicated Supporter
  • PipPipPip
  • 535 posts
  • Twitter:iBolski
  • Google+:Ivan Samuelson
  • LocationColumbus, Ohio
  • Current Device(s):Samsung Galaxy S7

Posted 10 June 2014 - 04:09 AM

NO YOU CANNOT RETURN TO WHATEVER IF U TAKE THIS UPDATE. **Capital letters for those who for want to read this whole thread.**

Cheers
/h

Sorry if you took offense to what I said. I was just trying to be helpful.

 

Also, if you have an unlocked bootloader, you CAN go back to JB. I've done it numerous times. It's only people with locked bootloaders that can't. I thought I had made that clear in my original statement, but maybe I didn't? If not, my bad.

 

Also, to just blindly tell people to stay away from it because you had a bad experience is not good either. As I replied, if you have an unlocked bootloader, go ahead and try it. It can't hurt. Worse comes to worse, FXD back to JB and you can go back to what you had before (you'll have to flash an older TWRP or CWM).

 

I also stated that those with locked bootloaders should decide whether the risk is worth the rewards as they won't be able to go back.


VZW Samsung Galaxy S7 Stock and unrooted running Marshmallow 46A, 32gb Nexus 7 unlocked
2cqd4t2.png


#15 hellagil

hellagil

    n00b

  • Members
  • Pip
  • 8 posts

Posted 10 June 2014 - 05:09 PM

I'm not sure why you're arguing with an opinion that was followed by reasoning... But to each his own. After my post, I found many others across the boards experiencing the same problems.

The op and topic both state unlocked.

As for fxz back to jb... I'll give it a try, but I'm given to understand it won't work, which was the reasoning behind the caps. Not an insult, just fair warning to others.

#16 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 43,441 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 June 2014 - 05:10 PM

I'm not sure why you're arguing with an opinion that was followed by reasoning... But to each his own. After my post, I found many others across the boards experiencing the same problems.

The op and topic both state unlocked.

As for fxz back to jb... I'll give it a try, but I'm given to understand it won't work, which was the reasoning behind the caps. Not an insult, just fair warning to others.

 

That last part is wrong if unlocked.  You just have to know what you're doing.  ;)  Use my RSD Script Generator to generate scripts for your FXZ, then flash the UNIVERSAL script.  Done.


Non potest esse nisi unus


#17 ibolski

ibolski

    Droid Master

  • Dedicated Supporter
  • PipPipPip
  • 535 posts
  • Twitter:iBolski
  • Google+:Ivan Samuelson
  • LocationColumbus, Ohio
  • Current Device(s):Samsung Galaxy S7

Posted 11 June 2014 - 03:38 AM

I'm not sure why you're arguing with an opinion that was followed by reasoning... But to each his own. After my post, I found many others across the boards experiencing the same problems.

The op and topic both state unlocked.

As for fxz back to jb... I'll give it a try, but I'm given to understand it won't work, which was the reasoning behind the caps. Not an insult, just fair warning to others.

 

As Samuri has stated, and as I was trying to explain to you not argue, is that with an unlocked bootloader, you CAN go back to JB. Use Sam's tools to do that. It's really not that difficult and that's the beauty of an unlocked bootloader.

 

That's all I was trying to say. In fact, I even apologized if I offended you, so we'll leave it as a misunderstanding since it's difficult to understand someone's intentions sometimes on a forum.

 

If you have an unlocked bootloader, you can go back to JB.


VZW Samsung Galaxy S7 Stock and unrooted running Marshmallow 46A, 32gb Nexus 7 unlocked
2cqd4t2.png


#18 Guest_kinnelonfire75_*

Guest_kinnelonfire75_*
  • Guests

Posted 17 June 2014 - 04:46 AM

I did all the fancy stuff no problem... went from CM11 to the official KK. Successfully installed the patched CWM from dhacker29 and installed root. I also was able to make a good backup in CWM. 

 

Now - Moto's KitKat basically sucks and i want to go back. I'll be calling CyanogenMod tomorrow to apologize for cheating on them and beg forgiveness.

 

I've tried to flash the latest nightly CM11 and another unofficial build of CM11 and get stuck at the red M bootlogo. I can get back into CWM and restore the stock system just fine.

 

The question: are we not able to flash roms yet?

 

 

I too am getting stuck on the bootlogo and had to use my backup to go to stock KK. Has there been any progress with this? I tried using both manual TWRP and Rom Manager to flash CM11 M6 as well as M7 but I end up in the same place... Red Bootlogo



#19 RikRong

RikRong

    Cap'n Slow

  • Superuser
  • 2,117 posts
  • LocationNoDak
  • Current Device(s):Pixel 7

Posted 17 June 2014 - 04:59 AM

I too am getting stuck on the bootlogo and had to use my backup to go to stock KK. Has there been any progress with this? I tried using both manual TWRP and Rom Manager to flash CM11 M6 as well as M7 but I end up in the same place... Red Bootlogo

You need to read this thread again. None of the ROMs out there right now will work with the new bootloader, they are all based off of the old kernel. DHacker has a test build of CM out right now and that's the only that's been booting.

R. Long: Pixel 5

 


#20 XE_Nerd

XE_Nerd

    Member

  • Members
  • PipPip
  • 193 posts
  • Current Device(s):DROID RAZR HD, HTC Rezound

Posted 17 June 2014 - 02:10 PM

You need to read this thread again. None of the ROMs out there right now will work with the new bootloader, they are all based off of the old kernel. DHacker has a test build of CM out right now and that's the only that's been booting.

I'm using his work in progress right now. So far it's pretty good. The only snag I ran into was once I touched the screen brightness it always went to the lowest brightness possible after going to a lock screen and would not adjust after. Had to restore to stock KK and reinstall. I now have a backup of cm11 as well so I don't have to reinstall if I get stuck with a dim screen again.


  • RikRong likes this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users