Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
Hi, so I made the dumb mistake of deleting the OS from my HTC One (Sprint). I got the One deodexed stock Jelly Bean rom from Android Revelution HD. Sideloaded it onto the phone and went into TWRP recovery to install the zip. It says the install was successful, however, when I hit reboot, it doesn't start into the rom. It just stays on the bootloader screen and sometimes I have to fastboot flash a recovery in order to get back into TWRP. I have tried fastboot erase cache and have also tried factory resetting it and wiping cache/dalvik cache before I install. Nothing seems to work. Any ideas???
tale419 said:
Hi, so I made the dumb mistake of deleting the OS from my HTC One (Sprint). I got the One deodexed stock Jelly Bean rom from Android Revelution HD. Sideloaded it onto the phone and went into TWRP recovery to install the zip. It says the install was successful, however, when I hit reboot, it doesn't start into the rom. It just stays on the bootloader screen and sometimes I have to fastboot flash a recovery in order to get back into TWRP. I have tried fastboot erase cache and have also tried factory resetting it and wiping cache/dalvik cache before I install. Nothing seems to work. Any ideas???
Click to expand...
Click to collapse
If it was me, I would just RUU and start over. Once that is done, boot it up transfer your rom over to the internal storage via usb while booted up. Then go back into fastboot, flash newest TWRP recovery and flash your rom. Also I don't think that rom supports the Sprint Variant at least that what is says under the details section. That could be part of your issues as well. I usually stay away from roms that weren't specifically made for my version but that's just me.
uckaus was
Sim-X said:
If it was me, I would just RUU and start over. Once that is done, boot it up transfer your rom over to the internal storage via usb while booted up. Then go back into fastboot, flash newest TWRP recovery and flash your rom. Also I don't think that rom supports the Sprint Variant at least that what is says under the details section. That could be part of your issues as well. I usually stay away from roms that weren't specifically made for my version but that's just me.
Click to expand...
Click to collapse
You're right. I checked and it's not compatible with Sprint. I downloaded the 31.6, but now I can't install it? Something about error with partitions. I've thought about doing the RUU but thought it might be more difficult.
tale419 said:
You're right. I checked and it's not compatible with Sprint. I downloaded the 31.6, but now I can't install it? Something about error with partitions. I've thought about doing the RUU but thought it might be more difficult.
Click to expand...
Click to collapse
RUU is easy. Just boot into fastboot, connect usb and launch the RUU. Once it's done then flash recovery and a different rom. It won't affect your s-off either if you are. I am currently using stock with goodies. It's a little older but it's rock solid, bloat is all gone, no blink feed and awesome battery. Will be switching once kit kat officially drops.
Sent from my HTCONE using XDA Premium 4 mobile app
Sim-X said:
RUU is easy. Just boot into fastboot, connect usb and launch the RUU. Once it's done then flash recovery and a different rom. It won't affect your s-off either if you are. I am currently using stock with goodies. It's a little older but it's rock solid, bloat is all gone, no blink feed and awesome battery. Will be switching once kit kat officially drops.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
RUU was SO much easier! Only problem is I can't get service now? It says I have Sprint service and there are some signal bars, but it doesn't say 3G or anything. Anyone have this problem after RUU?
tale419 said:
RUU was SO much easier! Only problem is I can't get service now? It says I have Sprint service and there are some signal bars, but it doesn't say 3G or anything. Anyone have this problem after RUU?
Click to expand...
Click to collapse
Try resetting the radio. ##786 then reset. You will need your MSL there are a few ways to get it. When I first activate a new phone, I always get in the habit of getting the MSL so I just have it. If you don't have it just call Sprint and ask. If you get some moron CSR just hang up and call back don't argue. I also don't like to use the word MSL when asking, I always say reset code so you can reset your phone most the time they will give it to you.
Sim-X said:
Try resetting the radio. ##786 then reset. You will need your MSL there are a few ways to get it. When I first activate a new phone, I always get in the habit of getting the MSL so I just have it. If you don't have it just call Sprint and ask. If you get some moron CSR just hang up and call back don't argue. I also don't like to use the word MSL when asking, I always say reset code so you can reset your phone most the time they will give it to you.
Click to expand...
Click to collapse
I did an easy fix and just re-inserted the sim card in hahaha. Hopefully it stays, but if I have any problems I'll definitely call them. Thanks for your help guys!
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.
I've browsed the threads and searched and can't find a for sure answer. Is it possible to flash a Rom like XDABBEB's by downgrading or any other relatively safe process if I'm on 3aa? I'm trying not to even soft brick because my home internet is very slow and it would possibly take me hours to download necessary files to recover from a soft brick. If it,is possible can you point me to where the directions are or help me out?
Always best to have a way back should anything go wrong.
Return to stock
http://forum.xda-developers.com/showthread.php?t=2448960
Don't think you need to downgrade, just root, autorec twrp, and you're all set.
Oh, and read, a lot.
Sent from my Nexus 6 using XDA-Developers mobile app
Dork6243 said:
Always best to have a way back should anything go wrong.
Return to stock
http://forum.xda-developers.com/showthread.php?t=2448960
Don't think you need to downgrade, just root, autorec twrp, and you're all set.
Oh, and read, a lot.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the reply. I must be doing something wrong if I don;'t need to downgrade to flash his rom from 3aa. I did exactly that above, rooted, autorec'd twrp and then tried flashing his rom with the 39a bootstack flashed first. Got a secure boot error, so tried it without the 39a bootstack after restoring my twrp backup and received the same secure boot error
Problem solved by flashing 12b bootloader. Saw it mentioned this: 12B Bootloader - needed for older kernel/boot images (and firmware that contains a kernel) that ONLY support loki.
SO decided to give it a try (ive bricked a phone or two flashing bootloaders so wasn't too comfortable trying this) AND it worked....
But im running into all kinds of crazy issues. Phone signal drops and reconnects between 3g, 4g lte, and no signal every 10 seconds or so. WHen i try to go to the settings to switch it off global mode, that screen flickers like crazy and cant click anything.... but it booted, so tahts a start