Related
My Play edition phone has been giving me endless headaches ever since the KitKat update dropped - I can't seem to get it to load.
For the status of my phone before all of this, I unlocked the bootloader, installed ClockworkMod, and used it to install a root Zip. I never wanted or tried to get S-OFF. So the bootloader shows Tampered and Unlocked, but S-ON, version 1.54. Everything worked fine, and I was happy with the phone.
Now, before I get started, my desired end-state for this phone is a bone-stock KitKat installation. I'm okay with not having root, having stock recovery and bootloader, just as long as the stock OTAs arrive and install with zero mucking around with recoveries, ROMs, backups, etc. I bought this phone because I want stock Android and the latest updates ASAP, and I'm not very happy that I've had to spend all of this time messing with it and still don't have the update.
This take starts when the little update icon for KitKat showed up, and in my innocence, I pressed it.
The phone reboots, CWM flashes the update, and reboots into it. Instead of the normal boot, I am greeted with a blue-green screen covered with little green lines, unresponsive to any input. In retrospect, I think this is because I don't have S-OFF, and the KitKat update requires a radio update which the updater includes, but can't be flashed from a modified recovery without S-OFF.
So I boot back into CWM and flash a backup to get my phone working again. I still want KitKat, of course, so it's time to search for other things to try.
First off, I try flashing a stock aftermarket ROM, the one by bigxie. Now the phone boots, but it bootloops, rebooting about 5 seconds after the lock screen comes up. With a little reading and a few questions, I get that this is also because I don't have S-OFF. Mmm, okay. Recover from backup again.
I downloaded the stock GPE RUU, pulled the stock recovery from it, flashed that, and tried to use it to install the OTA update, figuring that it would be signed properly or whatever to flash the radio. Same result as CWM. Install CWM again, restore from backup again.
My options are starting to seem a little limited. It looks like I can either get S-OFF and try the OTA again, or flash the stock GPE RUU and go back to 100% stock. Except that the instructions I found for flashing a stock RUU say that I need S-OFF for that too, though I'm a little skeptical of this - wouldn't that be only for rewriting the Model ID and Cell ID to the GPE?
First, I decide to try getting S-OFF. I get rumrunner S-OFF set up and running (moonshine doesn't have a version for me, and revolutionary doesn't support bootloader 1.54), and it does it's thing for a while, only to tell me at the end:
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Click to expand...
Click to collapse
Hmm... so I try flashing a kernel. I grabbed flar2's kernel and tried to flash it, and the Aroma installer never goes past 0%. Still reboots into exactly like it was before. Not real inclined to spend a lot of time messing with flashing kernels, since I want to end up at stock.
So next, I try flashing the stock GPE RUU, according to the above instructions. The flash fails with the message:
FAILED (remote: 99 unknown fail)
Yes, I ran the flash command twice, same result both times.
I'm downloading that again, but I'm not really sure what to do here. I'm okay at this point with flashing the stock RUU and wiping everything, if it gets me back to hassle-free stock. Should I keep trying to get that working? Or is S-OFF really necessary for that, and I need to get that figured out first? Or maybe I should just throw the phone out a window at this point.
ufmace said:
So next, I try flashing the stock GPE RUU, according to the above instructions. The flash fails with the message:
FAILED (remote: 99 unknown fail)
Yes, I ran the flash command twice, same result both times.
I'm downloading that again, but I'm not really sure what to do here. I'm okay at this point with flashing the stock RUU and wiping everything, if it gets me back to hassle-free stock. Should I keep trying to get that working? Or is S-OFF really necessary for that, and I need to get that figured out first? Or maybe I should just throw the phone out a window at this point.
Click to expand...
Click to collapse
I'm in much the same situation as you, S-ON with H-Boot 1.54, and Rumrunner/Moonshine keep on giving me the same errors you got. The only thing I have to contribute so far is, you cannot flash RUUs until you have S-OFF.
I've been searching for a proper insecure kernel for rumrunner to do it's magic with, but haven't found anything yet.
Fireye00 said:
I'm in much the same situation as you, S-ON with H-Boot 1.54, and Rumrunner/Moonshine keep on giving me the same errors you got. The only thing I have to contribute so far is, you cannot flash RUUs until you have S-OFF.
I've been searching for a proper insecure kernel for rumrunner to do it's magic with, but haven't found anything yet.
Click to expand...
Click to collapse
Thanks, I was afraid of that. Do you (or anyone else) know much about this insecure kernel thing? I assumed that all of the kernels for download here are insecure, but none of them say anything about it.
36664523 18206
ufmace said:
Thanks, I was afraid of that. Do you (or anyone else) know much about this insecure kernel thing? I assumed that all of the kernels for download here are insecure, but none of them say anything about it.
Click to expand...
Click to collapse
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Fireye00 said:
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Click to expand...
Click to collapse
Thanks. I found a reference to a carbonite ROM that supposedly worked here. I'll try and flash that or that Renovate one when I have time.
Fireye00 said:
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Click to expand...
Click to collapse
Thing's I've tried tonight:
* Tried moving from a USB Hub (Multi-TT) to a port on my mobo, No change.
* Flashed Renovate 7.0. Selected the APEX launcher, but when I got in, apex kept on crashing.
* Flashed Renovate 7.0 again, and this time selected GEL (Google Experience Launcher), which worked this time. Proceeded to run rumrunner, got to Pouring (2), but it errored out saying WTF are you doing (system reset itself in the middle of pouring)
* Moved to a new USB port, tried running rumrunner again, SUCCESS!
Resulting rumrunner output from working run:
Code:
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)............................
pouring (2).........
Waiting for ADB (27/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
Do note that during pouring 1 and 2, it rebooted twice, apparently that is normal.
ufmace said:
Thanks. I found a reference to a carbonite ROM that supposedly worked here. I'll try and flash that or that Renovate one when I have time.
Click to expand...
Click to collapse
I finally got S-OFF working with the linked ROM. It was a faster download than the Renovate one, so I thought I'd give it a try, and it's good. Just flashed and wiped data, didn't bother to set anything up or install anything. At least I'm finally making some progress here!
First, I'm going to restore my CWM backup and see if the factory update flashes properly now. If that doesn't work, I'll probably try the RUU. I'll post an update with the result.
ufmace said:
I finally got S-OFF working with the linked ROM. It was a faster download than the Renovate one, so I thought I'd give it a try, and it's good. Just flashed and wiped data, didn't bother to set anything up or install anything. At least I'm finally making some progress here!
First, I'm going to restore my CWM backup and see if the factory update flashes properly now. If that doesn't work, I'll probably try the RUU. I'll post an update with the result.
Click to expand...
Click to collapse
I was able to flash the 4.4 RUU without any trouble. My phone now works perfectly, whereas before I would sometimes get app crashes and junk. Now to take a fresh 4.4 backup, and revel in the awesomeness.
Grats on getting S-OFF finally!
Fireye00 said:
I was able to flash the 4.4 RUU without any trouble. My phone now works perfectly, whereas before I would sometimes get app crashes and junk. Now to take a fresh 4.4 backup, and revel in the awesomeness.
Grats on getting S-OFF finally!
Click to expand...
Click to collapse
Finally done! The update on my backup didn't work, same blue screen. So I just flashed the RUU that I had, let it pull all of the updates, and ran them. And this time, the KitKat update finally worked! So now I have a new, blank phone with KitKat to restore back to how I had everything set up.
I'm planning on leaving all of the system stuff bone stock. No root, recovery, nothing. All because, when the next update drops, I want it to just install without spending the better part of my free time for a week or two hacking around with it.
Incidentally, did you find an actual 4.4 RUU? The one I used was the launch RUU with 4.3, so it needed 2 OTA updates to get to 4.4.
ufmace said:
Finally done! The update on my backup didn't work, same blue screen. So I just flashed the RUU that I had, let it pull all of the updates, and ran them. And this time, the KitKat update finally worked! So now I have a new, blank phone with KitKat to restore back to how I had everything set up.
I'm planning on leaving all of the system stuff bone stock. No root, recovery, nothing. All because, when the next update drops, I want it to just install without spending the better part of my free time for a week or two hacking around with it.
Incidentally, did you find an actual 4.4 RUU? The one I used was the launch RUU with 4.3, so it needed 2 OTA updates to get to 4.4.
Click to expand...
Click to collapse
I had downloaded a 4.4 RUU back when it first hit for the HTC One, filename of "RUU-HTC_One_GE-4.4-3.58.1700.5.zip". I'm pretty sure it's the one on this thread, named "RUU Zip M7 Google Edition 4.4 3.58.1700.5 ".
Bit of a post-script, the 4.2.2 OTA update for my phone just dropped yesterday night. I let it install normally, and everything just worked. Now that's what I'm talking about!
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
Hasn't this already been discussed in the update thread? Flash the stock ATT JB, then accept the update.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
devilsking said:
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
Click to expand...
Click to collapse
Same here!
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
magocop said:
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
Click to expand...
Click to collapse
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
audit13 said:
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
Click to expand...
Click to collapse
Did you have to call Bell to get that customer recovery? And where can I get one at?
skeevydude said:
Did you have to call Bell to get that customer recovery? And where can I get one at?
Click to expand...
Click to collapse
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
audit13 said:
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
Click to expand...
Click to collapse
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
skeevydude said:
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
Click to expand...
Click to collapse
No worries. Good thing you brought the error to my attention; otherwise, Bell would start receiving requests for the "customer" recovery files:laugh:
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
I probably did when i first figured out how to use custom roms i was trying a whole bunch of them but that was awhile ago and now i dont remember how to flash a stock recovery or where to get it and i did awhile ago use RSD Lite to flash a stock rom onto my phone but that is the last thing I did and know its been sooo long i dont remember how any help from anyone would be greatly appreciated and sorry i have not got back to this post in a few days been busy doing other things but once again if anyone could help me it would be appreciated
Thanks
- Bart
Try using Myth Tools to flash back to stock, take the update, install a custom recovery, and flash a KK ROM.
http://forum.xda-developers.com/showthread.php?t=2262726
So, I imported and gifted this device to my GF and will describe what happened as she did. She was downloading a torrent and suddenly the screen just went black. After holding the power button for awhile, the phone came back on but, would get stuck on the boot logo(welcome message) screen and in a boot loop. I know that it is a SIM unlocked Moto X(XT 1053?)
So far, I've tried getting into the bootloader and am able to. The only problem is when I get to the recovery, I don't see the little dead Android dude. The phone ends up dying. Now I have it charging and I'm on the bootloader screen, but I still can't get into recovery. I just get a blank screen when I try.
It will be hard, time consuming and maybe a little expensive RMAing the device, as I'd probably have to send it back to the US for the warranty.
I'm thinking maybe I just try and unlock the bootloader and see if the subsequent factory reset helps. But I don't know if this will work.
I have tried fastboot erase cache but it didn't help.
I think somehow my recovery is gone. I've tried flashing a recovery.img but it errors out. (failed to hab check for recovery)
Any ideas?
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
KidJoe said:
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
Click to expand...
Click to collapse
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
deejaylobo said:
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
Click to expand...
Click to collapse
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
KidJoe said:
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
Click to expand...
Click to collapse
I only found one person with a similar issue, and you're right, he did end up getting a replacement. That's just not an option for me. It's too much of a pain sending it back to the US.
Yeah, I think I will reflash a ROM. Can you point me towards figuring out which is the correct ROM? My System Version is 212.44.21.ghost_row.Retail.en.US. So, I just grab the corresponding SBF, yeah? I flashed the logo with mfastboot, so I'm okay with that. EDIT: No worries. Foudn the right file. Sorted. Everything seems to be working fine. Thanks!
The face thing, is just to prank her. I previously had a custom message set up for her through the Moto Maker. I think she'll be rebooting her phone more often now.
https://twitter.com/theHTCscene/status/632273058322096128
My phone automatically downloaded it and is asking me every 20 seconds to install. Does anyone know if this is an acceptable update if rooted on stock ROM?
If not, how to stop the notification from appearing?
SeriesOfTubes said:
My phone automatically downloaded it and is asking me every 20 seconds to install. Does anyone know if this is an acceptable update if rooted on stock ROM?
If not, how to stop the notification from appearing?
Click to expand...
Click to collapse
I tried on my stock rooted ROM (went back to stock recovery first) and my phone wouldn't reboot afterward. It went into recovery, finished the update, but then stayed on the HTC One boot screen for half an hour. May have been an issue with root, xposed, or something else. I had to go back to one of my nandroid backups. So, I'd stay away for now if I were you.
coal686 said:
I tried on my stock rooted ROM (went back to stock recovery first) and my phone wouldn't reboot afterward. It went into recovery, finished the update, but then stayed on the HTC One boot screen for half an hour. May have been an issue with root, xposed, or something else. I had to go back to one of my nandroid backups. So, I'd stay away for now if I were you.
Click to expand...
Click to collapse
What I did was disabled *updater* and *configupdater* in the Apps settings.
Hope that works for you.
Even after a year on Android, I'm quite the novice, so please bear with me. So, I rooted my Moto X '14 using CF Autoroot because it was so easy. But, I had no idea how to unroot. So I googled some stuff and I attempted to flash back to total stock rooted rom and recovery. Foolishly, I picked the option to not wipe. So, when it rebooted, it went to the boot screen and crashed.
After trying everything, I realized I had no choice and did an external reset. So, hello 2014 because I'm back on KitKat but still was rooted. After looking around, I realized I can 'unroot' by pressing the option on SuperSU. But, I think all I did was revoke root access because on the bootloader, it still says modified.
I tried to go back to lolipop, but every time I take the OTA, the install crashes, but my phone works fine. So, what I wanna know is how I can go back to stock. Is it easy as flashing as flashing a 5.0 factory image? Or is there more I have to do?
bump
Ownage516 said:
Even after a year on Android, I'm quite the novice, so please bear with me. So, I rooted my Moto X '14 using CF Autoroot because it was so easy. But, I had no idea how to unroot. So I googled some stuff and I attempted to flash back to total stock rooted rom and recovery. Foolishly, I picked the option to not wipe. So, when it rebooted, it went to the boot screen and crashed.
After trying everything, I realized I had no choice and did an external reset. So, hello 2014 because I'm back on KitKat but still was rooted. After looking around, I realized I can 'unroot' by pressing the option on SuperSU. But, I think all I did was revoke root access because on the bootloader, it still says modified.
I tried to go back to lolipop, but every time I take the OTA, the install crashes, but my phone works fine. So, what I wanna know is how I can go back to stock. Is it easy as flashing as flashing a 5.0 factory image? Or is there more I have to do?
Click to expand...
Click to collapse
Just flash system and the root will be gone. Also, if you have other mods like TWRP or different modem the OTA won't install, so in order to get the latest update just flash all the files
Good luck
juliospinoza said:
Just flash system and the root will be gone. Also, if you have other mods like TWRP or different modem the OTA won't install, so in order to get the latest update just flash all the files
Good luck
Click to expand...
Click to collapse
Man, this would've been so helpful a month ago, lol.
Ownage516 said:
Man, this would've been so helpful a month ago, lol.
Click to expand...
Click to collapse
Sorry. Usually I just browse the last 10 questions. And in this post I saw "bump" bit I didn't check that wasn't you who did it LOL.
juliospinoza said:
Sorry. Usually I just browse the last 10 questions. And in this post I saw "bump" bit I didn't check that wasn't you who did it LOL.
Click to expand...
Click to collapse
Haha, it's all good. I just didn't know how that other dude dug this up.