Related
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.
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 have been doing some searching and seen that several people have had trouble with knock on. I ran into the same problem but have yet to fix it. Got me wondering what causes the problem in the first place. Any thoughts? Additional pointers to fixing it would also be appreciated.
Sent from my VS980 4G using XDA Free mobile app
NOTE: Just noticed that when I dialed *611 to get Verizon, com.lge.doubletap fc'd.
More info is needed like what rom or kernel your on to know or have an idea why it's not working for you. Then you might get some answers that help you out
It's not all that critical to me just more of a brain exercise to me trying to figure it out. Interestingly, I found that immediately after I went back stock, rerooted, etc and turned on the option to use the power key to lock knock on quit working and wouldn't come back on.
I have stock ROM and rooted but after I installed twrp recovery the knock on stopped working. Now when I double tap the phone restarts. I liked using that feature.
Found a solution that worked for me, sensor calibration in settings , gestures.
Unfortunately it worked for a little while, now its not working. Seems like the phone goes into deep sleep and when I double knock the phone restarts.
This morning I did factory reset, its still rooted but I will try it without a custom recovery. Knock on is working for now. I thought factory
reset would get rid of TWRP, its still there and so is the knock problem.
Knock on help
Hello everyone,
This is my first post ever on XDA. I will try to be as brief and detailed as possible.
I have been rooted with custom recoveries using vs98024A through vs98026. After going back to stock(24A) using LG Flash tool 2014 and the kdz method, then factory upgrading to 27A(latest software upgrade from VZW) and re-rooting(stump root) and finally getting twrp re-installed(Auto Rec), I also lost my knock on feature and have a dead strip close to the top of my screen.
I've done the hidden menu touch firmware upgrade and that doesn't work for me. It says it upgraded but it didn't fix the issue. I tried flashing the cloudyfa g3 port last night. The installation was a success. It didn't fix the dead spot but knock code halfway worked. I know knock code is different than knock on. I am looking for a fix to knock on. I've been reading forums for about a week now I've found that the hiddenmenu fix has only helped a handful of people with the vs980. I haven't tried any kernel flashing yet.
I'm running stock rooted 4.4.2 VS98027A build number KOT491.VS98027A Kernel Version 3.4.0-perf [email protected] Baseband version VS98027A-MPSS.DI.2.0.c2-00079-M8974AAAAANAZM-1
I also have TWRP recovery working
Let me know if I left out any pertinent information and I will be more than happy to produce that information.
This dead spot on the screen and no knock on is killing me. Any suggestions would be greatly appreciated.
Thanks in advance =)
dakattak said:
Hello everyone,
This is my first post ever on XDA. I will try to be as brief and detailed as possible.
I have been rooted with custom recoveries using vs98024A through vs98026. After going back to stock(24A) using LG Flash tool 2014 and the kdz method, then factory upgrading to 27A(latest software upgrade from VZW) and re-rooting(stump root) and finally getting twrp re-installed(Auto Rec), I also lost my knock on feature and have a dead strip close to the top of my screen.
I've done the hidden menu touch firmware upgrade and that doesn't work for me. It says it upgraded but it didn't fix the issue. I tried flashing the cloudyfa g3 port last night. The installation was a success. It didn't fix the dead spot but knock code halfway worked. I know knock code is different than knock on. I am looking for a fix to knock on. I've been reading forums for about a week now I've found that the hiddenmenu fix has only helped a handful of people with the vs980. I haven't tried any kernel flashing yet.
I'm running stock rooted 4.4.2 VS98027A build number KOT491.VS98027A Kernel Version 3.4.0-perf [email protected] Baseband version VS98027A-MPSS.DI.2.0.c2-00079-M8974AAAAANAZM-1
I also have TWRP recovery working
Let me know if I left out any pertinent information and I will be more than happy to produce that information.
This dead spot on the screen and no knock on is killing me. Any suggestions would be greatly appreciated.
Thanks in advance =)
Click to expand...
Click to collapse
I don't know about fixing the dead spot/black band on your screen (you probably need a new screen now), but I suggest you .kdz your way back to stock 27A, use stump root again, but, this time, do not use AutoRec. Using AutoRec on 27A causes all kinds of issues.
You have to flash a bumped recovery using adb commands...I think I read somewhere that there is a tool, or something that automates the adb commands for you, and flashes a bumped recovery for you, but I can't remember where I read it...use blastagator's bumped recovery to flash to your phone; just take out the recovery image from his zip, and flash it using adb commands.
Blastagator recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Thanks for your response. I guess using auto rec on 27a was the culprit like you say. I seem to remember it happening shortly after the update.
As for the dead spot. It doesn't affect my screen other than not responding to touch in the affected region. The entire screen display works visually.
I'll give this a shot tonight and see how it goes.
Again, thank you for your response!
Cheers
Sent from my VS980 4G using XDA Free mobile app
I had a similar issue and it was the dead spot in the screen causing problems. It sounds like it died in the same location too. I restored to stock without it fixing the problem and ended up getting a replacement from Verizon. Hopefully you're still under warranty, I had a month left in mine.
ATgiant said:
I had a similar issue and it was the dead spot in the screen causing problems. It sounds like it died in the same location too. I restored to stock without it fixing the problem and ended up getting a replacement from Verizon. Hopefully you're still under warranty, I had a month left in mine.
Click to expand...
Click to collapse
After a lengthy power outage in my building, I was finally give blastagator's bumped recovery a try. I flashed back to stock 27A and rooted with stump like you suggested. Couldn't get it to flash manually with adb or terminal. I ended up using flashify to flash blastagator's bumped recovery image. It installed fine and I was able to boot into the custom recovery, unfortunately the dead spot is still there.
So annoying. It looks like I'll be contacting Verizon about a replacement.
Thanks again for your help
This is NOT a how-to or anything. Don't try to follow in my footsteps of stupidity and brick your phone.
That being said...
XT 1060 (Verizon)
I have been running 4.4.4 for quite a while now. Right after JCase released sunshine for our phones. (I have an unlocked bootloader.)
I had it rooted, and tried out the 5.0 ROMs a while ago. Flashed back to stock to wait for the update when we heard it was coming "very soon". But tonight I got impatient and decided I was going to re-root and switch back to CM12. So, I opened Moto X Toolkit (love that tool) and installed TWRP. When I manually rebooted I forgot to boot into recovery. Don't know if that had anything to do with the ensuing problems or not, but after that, I couldn't get it to boot into recovery.
So, I flashed back to stock 4.4.4 again. Tried rebooting into stock recovery... no joy.
So off I go again... one more attempt to flash stock 4.4.4. This time, when it asked me if I wanted to reboot into bootloader or android, I tried to boot into android. Sadly I missed the "a" and typed "ndroid". The toolkit began doing something... looks like it was running the flash all over again. I let it do its thing, then very carefully typed "android" so I wouldnt screw it up again.
It rebooted perfectly, but once it was up and running, I noticed all of my icons were blue. I quickly jumped into the "about phone section and noticed it said "4.2.2".
This is not supposed to be possible, so at this point I was half panicking and half curious... so I decided to do an even more stupid thing and accept the updates.
I am now updated completely to 4.4.4. Zero issues... recovery works fine, radio is fine, wifi and BT are fine.
This leads me to two questions (Directed to developers)...
1) Is there a possibility this is repeatable?
2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?
You are lucky you didn't bricked it by installing ota
updates. Whatever you do please don't install any ota updates. Simple wait for the sbf and manually flash it with rsd. Don't even even attempt to downgraded
I know I got lucky, but that didn't answer either of my questions.
I wouldn't try to repeated it if I were you. Go to moto x bricked phones thread and read the comments. That will satisfy and answer your questions http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Fadelight said:
This leads me to two questions (Directed to developers)...
1) Is there a possibility this is repeatable?
2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?
Click to expand...
Click to collapse
1) I would NOT try to repeat it. You are lucky.
What likely happened is the toolkit flashed 4.2.2 via mFastboot, errored on GPT.BIN and Motoboot.img, and continued flashing the rest. Taking an OTA in this state USUALLY bricks the phone, however we have seen a few, like yourself, who reported it didn't brick.
Due to the sheer number of people and threads from those who have bricked doing this, the warnings have been... do NOT try it unless you don't mind if you turn your phone into a paper weight!
To be safe at this point, I would consider downloading the Verizon 4.4.4 SBF, and re-flashing it using Option 5 (and its pre-reqs) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html to make sure everything is back to stock/consistent. Its your choice if you don't want to.
2) Worst case is you turn your phone into a paperweight.
Some have screwed it up very badly but have been able to recover following these instructions -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 It is the last resort. You'll also see many in that thread who followed those instructions and were unsuccessful, leaving their phone unusable.
We've also seen a few who were able to reflash the latest rom (currently 4.4.4) via mFastboot, with a few "extra" commands and have been able to recover, but that is a very small number compared to those who have bricked.
That's the odd thing... it DIDN'T error on anything. I would've thought the same thing... error on motoboot and gpt.
I don't mind screwing up a phone and taking a day or two to get it back to operable. As long as there is a way to fix it, I'm good. I just don't want to completely brick the phone. That's why I asked if people meant truly bricked or the new standardized "bricked" which usually means nothing more than having to RSD.
Fadelight said:
That's the odd thing... it DIDN'T error on anything. I would've thought the same thing... error on motoboot and gpt.
I don't mind screwing up a phone and taking a day or two to get it back to operable. As long as there is a way to fix it, I'm good. I just don't want to completely brick the phone. That's why I asked if people meant truly bricked or the new standardized "bricked" which usually means nothing more than having to RSD.
Click to expand...
Click to collapse
I haven't used that tool kit. I do everything manually. So I don't know exactly what processes it runs, or what steps it takes when flashing. IF while flashing it does try to flash all parts, it should have given an error on GPT.BIN if it tried to downgrade, but at the same respect, if its a batch file that just runs the fastboot commands one after the other, if fastboot errors, it will just go to the next line in the bat file, so unless you are paying attention and watching it from start to finish, you could have missed the error.
Another possibility would be if you, or someone who had your phone, upgraded to 4.4.4 by flashing only system.img, and the older bootloader and partition table remained on your phone, then attempting to "downgrade" would not have failed (depending on the bootloader/gpt.bin on your phone).
As said... there are enough that have NOT been able to recover their phones, even after following the instructions in -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 which are usually the last resort.
Yeah, the second it started running again after I typed "ndroid" by accident, I was in full-on panic mode, so my eyes were glued to the phone and the computer. I saw them flash.
As far as upgrading, I was on 4.4.0 until Sunshine was released... at which point I unlocked my BL and took all of the OTA updates. So it was on full 4.4.4.
This is the oddest thing I have seen in a long time. I was tempted to send a DM to JCase and ask him, but I figured that would probably go over like a fart in church.
I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
waylo said:
I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
Click to expand...
Click to collapse
Did u pull battery?
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Did u pull battery?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
waylo said:
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
Click to expand...
Click to collapse
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
waylo said:
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
Click to expand...
Click to collapse
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yeah, next time I will go the KDZ route to return to stock. Bummer!
Look up G2 unbrick.
Sent from my LG-H811 using Tapatalk
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
MrSteelX said:
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
Click to expand...
Click to collapse
Thank you all for the education.
10N hadn't been out for a day, so I was concerned this would raise some red flags at the store. Otherwise would have kept it on--a vast improvement over 10H.
I haven't been on LG at all previously, so all this info would have been nice to know beforehand. =/
Oh well, live and learn.
Of course it's similar with most phones (i.e. Samsung won't let you downgrade bootloaders/modem), but typically it will just not take, rather than brick. As I recall, what happened to me is an inherent danger with TWRP zip flashing.
Yeah, the KDZ failed 10h flash would have been a nicer way to let me know I am trying to do something very very bad.
I looked at some LG2 unbrick notes. Most of them talk about the connected computer showing several hard drives when connected. At this point, I can't even get the computer to show the qhsusb_bulk driver install attempt again. Any tips on how to get the phone to power on the right way to allow for this?
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Biker1 said:
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Click to expand...
Click to collapse
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
waylo said:
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
Click to expand...
Click to collapse
I hear ya.
I needed to make an updated 10h Nandroid anyway.
Don't hold me to it but from what i can tell we aren't being locked out of downgrading in future updates, just in 10n as it's main purpose was to patch stage fright which was a massive security flaw and they felt it unsafe to allow downgrade to an insecure state
so uh huge question here...i got my phone from tmobile aand it was 10h....so i flashed twrp and it worked...but now no matter what rom i run i get a hang until i reboot..then when i reboot the phone spazzes the **** out...help anyone thanks
Your problem is unrelated to this thread. Your phone is buggy but not bricked.
Last night I tried to root my phone. I pushed a rooted image. It completed and rebooted. Then I got a security error 11. I then pushed a factory image using the KDZ method. Now it's completely dead. Pulled battery a few times. Nothing. Held down power and volume down a few times. Nothing. Plugged it in to charge. No LED light, no battery charging animation, no security error. No nothing. I also connected it to my PC with a usb cable while holding in volume up. Nothing. A whole lot of nothing. I contacted LG and they sent me a fedex label. It's now in the mail.
Question: I have the naughty image on there, but as far as I know it never actually took so I never had root. Also, presumably the factory image is what is currently loaded. So will they be able to detect that the phone is rooted? If they find the naughty file will they consider that in the same way as if I had succeeded in rooting it?
I knew at the time that I was doing something that would void the warranty so I can't complain too much. So then in the process of finding that I was naughty will they unbrick it at least to the point where I can pray for a future fix? I can say "gosh darn just send it back as is" and hope that they helped me out while detecting my naughtiness. Or if I say, "ok you got me, what's it gonna cost for you to unbrick my phone?" will they fix it at a reasonable price? If not, can I run it over with my car and pay the $150 deductible on my insurance? Basically, where am I at?
this is lg we are talking about. They will do 1 of 2 things to fix it, 1. reflash the whole emmc chip call it done. 2. swap out the mother board and call it done.
So sorry, it was not a bad flash I did this exact thing tried to revert. You are hard bricked I just turned my phone in though because I did it on day 2 I had it and got a new one. Just warning people you upgrade and try to go back you will get a hard brick.
I did the same thing as smkyle, but I haven't turned mine in yet. Is there any hope for fixing it.
Edit: In device manager it showed "QHSUSB_BULK" and then stopped. I have a spare battery and charger so after swapping out the battery the computer read the phone again, but this time installed drives and now shows "Qualcomm HS-USB QDLoader 9008 (COM7)".