I have an unlocked and rooted stock Nexus 7 with the stock rom. I Just performed an OTA update to Android 4.2 and now the Nexus is stuck on the Google splash screen with the unlocked padlock symbol. I have tried booting to recovery with the Wugs Rootkit and it shows a an android with a red warning triangle above it. Please can anyone help me to fix this.
I have a PC with Wugs Toolkit 1.5.5 and I have the Google Nexus 7 Root Toolkit 3.2.0.
Please anyone know how to the fix this as I have no idea.
Exact same problem
randomvector said:
I have an unlocked and rooted stock Nexus 7 with the stock rom. I Just performed an OTA update to Android 4.2 and now the Nexus is stuck on the Google splash screen with the unlocked padlock symbol. I have tried booting to recovery with the Wugs Rootkit and it shows a an android with a red warning triangle above it. Please can anyone help me to fix this.
I have a PC with Wugs Toolkit 1.5.5 and I have the Google Nexus 7 Root Toolkit 3.2.0.
Please anyone know how to the fix this as I have no idea.
Click to expand...
Click to collapse
I have the exact same problem. For the record I had the very latest version of SuperSU Pro that got updated today (0.98, I think) with survival mode activated. Don't know if that's the cause of the problem or just the fact that it's rooted.
Dang. Same thing here. And I also just installed the new SuperSU before applying the OTA.
Try the two posts right above this one.
I know the thread Stuck on Google Screen has some solutions that may help.
Sent from my Nexus 7
Clean ROM 2.0 - leankernel .5
ezas said:
Try the two posts right above this one.
I know the thread Stuck on Google Screen has some solutions that may help.
Click to expand...
Click to collapse
Well, since you replied, this thread is now at the top of the stack, so there's nothing above it. I'm getting old and blind, but I don't see a thread and can't find one with search called anything like "Stuck on Google Screen". Except this one, of course.
Edit...Eh, nevermind. I just flashed the full 4.2 from Google instead of mess with this any more. Restoring apps now.
CSX321 said:
Dang. Same thing here. And I also just installed the new SuperSU before applying the OTA.
Click to expand...
Click to collapse
I did exacty the same thing the app had already updated before I could do the Android 4.2 update. I fix the isue. I had to do restore to stock Rom 4.1.1 then update to 4.1.2 and then to 4.2 then recovered some of the stuff I lost with an old Titanium Backup I did a few weeks ago.
Recovered mine
Hi all,
(I'm the second poster)
I managed to get my Nexus 7 back, although losing all the data, which I think cannot be avoided.
Here is what I did, for dummies:
- Reboot into fastbood mode. For this, hold the power, volume up and volume down button.
- Use the Nexus 7 Toolkit (I donated to get the latest version) or the Nexus Root Toolkit (which I guess works as well) and flash the google factory stock rom.
- If using the Nexus 7 toolkit, at the beginning I selected that I had Android 4.2 installed.
- After flashing, my tablet was as if just taken out from the box (but still unlocked). All my old apps got downloaded automatically, although the settings / game progress were not saved. Fortunately I have some Titanium Backup backups from a little while ago.
- After all apps got downloaded, I put the tablet in fastboot mode again, and I rooted it with the Nexus 7 toolkit via option 4 and then sub-option 2.
Sorry if I said some obvious stuff, but I am not an expert, and wanted to help other non-experts
Good luck to everyone.
aran80 said:
Hi all,
(I'm the second poster)
I managed to get my Nexus 7 back, although losing all the data, which I think cannot be avoided.
Here is what I did, for dummies:
- Reboot into fastbood mode. For this, hold the power, volume up and volume down button.
- Use the Nexus 7 Toolkit (I donated to get the latest version) or the Nexus Root Toolkit (which I guess works as well) and flash the google factory stock rom.
- If using the Nexus 7 toolkit, at the beginning I selected that I had Android 4.2 installed.
- After flashing, my tablet was as if just taken out from the box (but still unlocked). All my old apps got downloaded automatically, although the settings / game progress were not saved. Fortunately I have some Titanium Backup backups from a little while ago.
- After all apps got downloaded, I put the tablet in fastboot mode again, and I rooted it with the Nexus 7 toolkit via option 4 and then sub-option 2.
Sorry if I said some obvious stuff, but I am not an expert, and wanted to help other non-experts
Good luck to everyone.
Click to expand...
Click to collapse
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
---------- Post added at 09:49 AM ---------- Previous post was at 09:44 AM ----------
aran80 said:
I have the exact same problem. For the record I had the very latest version of SuperSU Pro that got updated today (0.98, I think) with survival mode activated. Don't know if that's the cause of the problem or just the fact that it's rooted.
Click to expand...
Click to collapse
I installed the latest SuperSU version but have not updated yet, what do you recommend I do, remove the SuperSU software or not uprgade at all at this time?
Thanks,
JBIRD
jbird92113 said:
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
Click to expand...
Click to collapse
Before doing all that, plug your Nexus in and make sure USB Debugging is enabled, and also its set to camera mode, not MTP.
Goto command prompt, and use:
adb reboot recovery
You will then see the Android with a red triangle, at the same time quickly tap power and volume up, you'll then be taken to a blue screen.
Choose wipe cache.
Also you could factory reset?
Then reboot
Hope this helps.
Nexus 7 toolkit
jbird92113 said:
Can you advise which toolkit you used, was it Wug's Toolkit? Can you possibly provide the link?
Thanks,
JBIRD
Click to expand...
Click to collapse
Sure First I thought about using Wug's Toolkit, but I saw it was not updated yet to handle Android 4.2 stuff, whereas the Nexus 7 Toolkit was.
You can download it from http://forum.xda-developers.com/showthread.php?t=1809195, but only version 3.2.0 which does not have Android 4.2 stuff. To get the latest version (3.8.2, updated yesterday 14 november), you have to donate and wait until the developer sends you a key. I donated 5 pounds but the developer says any amount is OK. I got my key 1-2h after donating.
aran80 said:
Sure First I thought about using Wug's Toolkit, but I saw it was not updated yet to handle Android 4.2 stuff, whereas the Nexus 7 Toolkit was.
You can download it from http://forum.xda-developers.com/showthread.php?t=1809195, but only version 3.2.0 which does not have Android 4.2 stuff. To get the latest version (3.8.2, updated yesterday 14 november), you have to donate and wait until the developer sends you a key. I donated 5 pounds but the developer says any amount is OK. I got my key 1-2h after donating.
Click to expand...
Click to collapse
Thanks. Do you recommend that I remove SuperSU prior to running the OTA or even for that matter just hold off on upgrading for now?
jbird92113 said:
Thanks. Do you recommend that I remove SuperSU prior to running the OTA or even for that matter just hold off on upgrading for now?
Click to expand...
Click to collapse
Well, I can only tell you the situation that I had before installing the 4.2 OTA:
- Unlocked
- Stock Android 4.1.2
- Rooted with SuperSu 0.98 and survival mode activated
Maybe the problem was to be rooted; or to have SuperSU; or to have specifically SuperSU 0.98; or to have survival mode active... I don't know.
If you want to be fairly sure to not have any problems, I would uninstall SuperSU. There is an option to do a full unroot inside SuperSU itself. Maybe before that to be even safer, you could even uninstall all the root-requiring applications?
Then, reboot, apply the OTA, and cross your fingers
Then you can root again with Nexus 7 toolkit, it was done very fast, and you will have supersu again.
Rooting or unrooting should not wipe your data.
From now on I think I will not have the survival mode activated before an OTA, just in case, as I now know how to unroot / root quite fast.
Good luck
randomvector said:
I had to do restore to stock Rom 4.1.1 then update to 4.1.2 and then to 4.2
Click to expand...
Click to collapse
I didn't bother with reverting to stock. I just booted into fastboot mode, which I was still able to do, and installed the factory 4.2 image from https://developers.google.com/android/nexus/images. I develop apps, so I already had a full development environment and the needed tools installed.
aran80 said:
Well, I can only tell you the situation that I had before installing the 4.2 OTA:
- Unlocked
- Stock Android 4.1.2
- Rooted with SuperSu 0.98 and survival mode activated
Maybe the problem was to be rooted; or to have SuperSU; or to have specifically SuperSU 0.98; or to have survival mode active... I don't know.
If you want to be fairly sure to not have any problems, I would uninstall SuperSU. There is an option to do a full unroot inside SuperSU itself. Maybe before that to be even safer, you could even uninstall all the root-requiring applications?
Then, reboot, apply the OTA, and cross your fingers
Then you can root again with Nexus 7 toolkit, it was done very fast, and you will have supersu again.
Rooting or unrooting should not wipe your data.
From now on I think I will not have the survival mode activated before an OTA, just in case, as I now know how to unroot / root quite fast.
Good luck
Click to expand...
Click to collapse
Thanks. I didn't purchase the pro version so I don't have the survival mode feature . I may just wait and see if there are any other folks running into the same issue. Thanks again
Has anyone figured this out yet? I'm also stuck on the Google boot screen after installing the 4.2 OTA on my stock, rooted Nexus 7, and I've tried the following:
- Wiped cache.
- Re-flashed the 4.2 OTA (build JOP40C) from stock recovery via adb.
- Flashed TWRP (via Wug's Root Toolkit) and renamed Superuser.apk, assuming that was the issue.
- Re-flashed the 4.2 OTA (build JOP40C) from custom recovery via WugFresh's Nexus Root Toolkit v1.5.5.
Nothing worked -- it's still locked up on the Google screen at boot. How do I fix this (ideally without wiping my user data)?
rcs408 said:
Has anyone figured this out yet? I'm also stuck on the Google boot screen after installing the 4.2 OTA on my stock, rooted Nexus 7, and I've tried the following:
- Wiped cache.
- Re-flashed the 4.2 OTA (build JOP40C) from stock recovery via adb.
- Flashed TWRP (via Wug's Root Toolkit) and renamed Superuser.apk, assuming that was the issue.
- Re-flashed the 4.2 OTA (build JOP40C) from custom recovery via WugFresh's Nexus Root Toolkit v1.5.5.
Nothing worked -- it's still locked up on the Google screen at boot. How do I fix this (ideally without wiping my user data)?
Click to expand...
Click to collapse
Same here, didn't try all you did.
I'll try to descibe what I did to see similarities,
I had my N7, Rooted 4.1.2, unlocking via face-lock, , I has just installed last update from super su, had root protection enabled,
I'm willing to pay 2.7 Bitcoins, (~31$) to someone helping me fix it without reinstalling everything.
Just an update on my situation: Since adb still worked from the Google boot screen, I managed to batch pull my TitaniumBackup folder down onto my PC. I went ahead and flashed back to stock (good guide here, for anyone who needs it: http://forum.xda-developers.com/showthread.php?t=1781250), updated, re-flashed SuperSU and Busybox, and restored all my backups without any issues.
First time I've actually had to do that, but I'm happy to see that my daily TiBu backup schedule paid off, and I'll probably feel much more confident repeating the process in the future.
Anyway, I'm assuming the issue had something to do with the SuperSU apk, as others here have guessed. I, too, had SuperSU's survival mode enabled (which I've disabled) -- and I also had OTA RootKeeper installed (which I've now ditched), In the future, I'll probably just err on the side of caution and fully unroot before applying an OTA; it's easy enough to just re-root, rather than rolling the dice with any sort of survival mode.
And if SuperSU ISN'T the issue, I'd sure like to know what is!
Hi guys, my girlfriend updated to 4.2 yesterday, and it was fine up until her battery died. so she charged it and then tried to turn it on, and it was in an endless boot loop first starting with the google logo coming up, then itll go kinda staticy and go to the X (and sorry for my future description) but then the screen will look like its in the matrix? If that makes sense. I can provide a picture if needed, but then itll just reboot and do the same thing over and over again. We went to Virgin and called samsung and they both said the same thing that the system would have to be recovered. Virgin, however directed me over to use Odin. I've never really used Odin before and am not sure what to do, so would someone mind helping me out with this issue? i've tried going into recovery menu as well, but it doesn't work. I really appreciate the answer in advance!!!!! Her phone is the galaxy nexus.
AdmiralAqbar said:
Hi guys, my girlfriend updated to 4.2 yesterday, and it was fine up until her battery died. so she charged it and then tried to turn it on, and it was in an endless boot loop first starting with the google logo coming up, then itll go kinda staticy and go to the X (and sorry for my future description) but then the screen will look like its in the matrix? If that makes sense. I can provide a picture if needed, but then itll just reboot and do the same thing over and over again. We went to Virgin and called samsung and they both said the same thing that the system would have to be recovered. Virgin, however directed me over to use Odin. I've never really used Odin before and am not sure what to do, so would someone mind helping me out with this issue? i've tried going into recovery menu as well, but it doesn't work. I really appreciate the answer in advance!!!!!
Click to expand...
Click to collapse
AdmiralAqbar, if you need to return your Nexus 7 to stock, follow this guide: http://forum.xda-developers.com/showthread.php?t=1781250
You could also boot into recovery (hold Volume Up and Down keys while you power on, then select Recovery from the list), and then try to return to stock from there (in Recovery, press Power and Volume Up at the same time, and there should be an option in the resulting list).
rcs408 said:
AdmiralAqbar, if you need to return your Nexus 7 to stock, follow this guide: http://forum.xda-developers.com/showthread.php?t=1781250
You could also boot into recovery (hold Volume Up and Down keys while you power on, then select Recovery from the list), and then try to return to stock from there (in Recovery, press Power and Volume Up at the same time, and there should be an option in the resulting list).
Click to expand...
Click to collapse
I didn't even realize this was a nexus 7 thread i'm sorry! I just noticed the same problem so i clicked into this thread haha, she has the Galaxy Nexus i9250. And i tried that, and then it'd just reboot. I'm assuming the recovery menu is corrupt maybe? Would i be able to follow the same steps in that guide for her phone?
Hello everyone,
I tried to root my 32g Nexus 7 with WugFresh's toolkit 1.6.1 (I'm fairly new to the rooting thing so I tried to use a toolkit). It did not go well. During the process I received messages from the toolkit saying it could not read Fastboot - but they seemed to go away after I switched USB ports. After the bootloader unlocked, I went back into the device and saw that it didn't fully wipe (I thought it was supposed to wipe out *everything*). When the rooting portion was finished, there were no new apps in my app page (super user and whatnot).
So I decided to nix the whole thing and just put it back into stock and try again tomorrow. I followed the instructions to get the drivers to where they needed to be, and then set it to flash back to stock and unroot the device.
First time around, it stalled during the flash. Rebooted, tried again, flash went fine. Toolkit said it would appear to be stuck in a bootloop for about 5-10 minutes. Well, after 20 minutes, it was still on that colorful "x". So, I reset it once again, and now it's stuck on the pretty colored "x". I do think the unlock is still there because the open padlock still shows up when I reboot. It just gets stuck on the "x".
Can anyone help me? I'd really rather not remove the battery if I have to (though it doesn't look that hard).
I feel terrible about this. This was my Christmas gift, and I feel like I've completely ruined the thing over what was supposed to be an easy root procedure.
EDIT: I was able to get to the Android with the red triangle on it and did a factory reset, but it seems that it still can't get past the "x".
Horadrius said:
Hello everyone,
I tried to root my 32g Nexus 7 with WugFresh's toolkit 1.6.1 (I'm fairly new to the rooting thing so I tried to use a toolkit). It did not go well. During the process I received messages from the toolkit saying it could not read Fastboot - but they seemed to go away after I switched USB ports. After the bootloader unlocked, I went back into the device and saw that it didn't fully wipe (I thought it was supposed to wipe out *everything*). When the rooting portion was finished, there were no new apps in my app page (super user and whatnot).
So I decided to nix the whole thing and just put it back into stock and try again tomorrow. I followed the instructions to get the drivers to where they needed to be, and then set it to flash back to stock and unroot the device.
First time around, it stalled during the flash. Rebooted, tried again, flash went fine. Toolkit said it would appear to be stuck in a bootloop for about 5-10 minutes. Well, after 20 minutes, it was still on that colorful "x". So, I reset it once again, and now it's stuck on the pretty colored "x". I do think the unlock is still there because the open padlock still shows up when I reboot. It just gets stuck on the "x".
Can anyone help me? I'd really rather not remove the battery if I have to (though it doesn't look that hard).
I feel terrible about this. This was my Christmas gift, and I feel like I've completely ruined the thing over what was supposed to be an easy root procedure.
EDIT: I was able to get to the Android with the red triangle on it and did a factory reset, but it seems that it still can't get past the "x".
Click to expand...
Click to collapse
The best thing to do is reflash using fastboot. Google "flash n7 with fastboot". It is really the best way to work on an n7, or any nexus device.
Sent from my Nexus 7 using xda premium
rebel1699 said:
The best thing to do is reflash using fastboot. Google "flash n7 with fastboot". It is really the best way to work on an n7, or any nexus device.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh wow, it worked!!! I used the .tgz file with the Toolkit and it came back!!! Thank you so much!!
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
CausableMidget said:
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
Click to expand...
Click to collapse
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
CausableMidget said:
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
Click to expand...
Click to collapse
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
CausableMidget said:
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
Click to expand...
Click to collapse
Have you tried calling an Exorcist?
I've run out of ideas!
Sent from my Nexus 7 (2013)
Okay, I gave this a shot.
I used the Nexus Root Toolkit and rooting the thing went pretty well. I downloaded a Cyanogenmod rom, actually 2, and that was the start of my issues I think. I accidentally loaded the nightly instead of the stable.
I also didn't realize that adb would not boot anymore with 4.2.2 so I was stuck. I checked in the settings of the Nexus and it loaded up various roms you could use. I would select them and it would start to load, but then show the error message with the little android on his back.
I followed the tutorial "Root and Install CWM On Nexus 7 Running JB 4.2.2" in an attempt to get some control back and it went well until I was supposed to find the zip on the device. I had copied it over, separate from any folder, but I could not find it while in bootloader.
I ended up manually putting it in bootloader and using the Nexus Root Toolkit to restore the stock rom.
I liked certain things about the custom rom, but it was a pain not having the Google Apps, and I could not get the Gapps to install either.
Obviously I knew just enough to get halfway there. I am not sure when I will try this again, although I would like to learn more. I guess I better read some more tutorials on here.
Why didn't you just flash gapps in recovery?
Sent from my Nexus 7 using Tapatalk
Well first off there isn't Android 4.2.2 for the new Nexus 7, you must have followed a tutorial for the old one.
I used the nexus 7 toolkit.... There lies your problem
You used a toolkit not knowing what you're actually doing. Or what any of the terms mean / how and what they're used for etc.
Adb doesn't boot... Um what. Fastboot couldn't flash cm11...um what 4.2.2 um what