Database Users

Nexus 7 wont boot pass google logo after root/unroot

I got a nexus7 a week ago but decided to root the device today just to try apps which require root, i rooted it fine but i decided to unroot and thats where the problem started i cant boot pass the google image, i can get into where you hold down volume and power for so many seconds and team win recovery which says i have no OS in the reboot section, i've tryed nexus 7 toolkit v3.2.0 and nexus root toolkit to restore back to factory system but no luck, so is it me doing something wrong or is my nexus 7 just a paper weight now.

Doubt it,
Being you still have a custom recovery you didn't follow the right steps to unroot, might need to unlock the bootloader again, but follow one of the many guides, and try to stay away from a tool kit
Sent from my HTC Vision using xda premium

Unlock bootloader
Flash boot, recovery, system, userdata.
Files are zipped in the factory images directly from google.
Wipe cache.
Relock bootloader.
Reboot into recovery.
Factory reset. (Nexus 7 will only see 8GB if you don't do this step)
That is the gist of how it's done.

I followed a step by step guide on laptop man website but when i come to flash the android image it says file too large, i used 4.2.1 from googles site, if i'm correct when you type fastboot -w update image-nakasi-jro03d.zip (in the walkthrough) i can replace it with a later newer android in this case 4.2.1 jop40d

You could do it that way. Some people have. Although I received an error every time I did.
I didn't receive an error when I flashed the files in the zip.
First make sure you have the correct factory image for your device downloaded.
Then make sure you extract the boot.img, recovery.img, system.img, and userdata.img files to your fastboot folder and perform the following actions...
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
Lastly, boot your system up into recovery and perform a factory reset from there. If you don't do the last step they you will be stuck with ouly 8GB, vice 16 or 32.
It's that easy.

When i try to boot into recovery mode i get the android mascot with a red triangle, does that mean i have no recovery file.
OOOPS the system booted up into android as the recovery mode didnt work (as above) is there anyway i can reset to factory settings to get the 32GB back as it shows 6GB.
Update: I think i sorted it out now somehow as it shows up as 27.oddGB now (about same as i got it) instead of 6GB, anyway thanks for your help, it seemed complex well it is but once you know whats what it's not so, the hardest part is getting the files and putting them in the right places

When I try to reboot to recovery via the bootloader it just hangs... Can boot to recovery inside android (usually using Rom Manager or another reboot application)... any idea why?

I have read reports that it will hang when booting into recovery if not connected to a PC.
And as for that triangle you see.... That's normal.
That means that your in recovery mode. Your menu is just hidden.
Press power and volume up to view it.

[Q] Nexus 7 gets stuck booting. Tried reflashing stock OS multiple times.

I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...

evenstevens said:
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
Click to expand...
Click to collapse
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !

Red Devil said:
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Click to expand...
Click to collapse
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock

evenstevens said:
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
Click to expand...
Click to collapse
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !

Red Devil said:
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Click to expand...
Click to collapse
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks

evenstevens said:
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
Click to expand...
Click to collapse
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best

Red Devil said:
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Click to expand...
Click to collapse
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...

evenstevens said:
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
Click to expand...
Click to collapse
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah

evenstevens said:
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
Click to expand...
Click to collapse
Okay my solution to this:
Just keep flashing it with the flash-all.bat command until it just... worked.
Must've done it about 15 times.
Well that's that ordeal over.

updated to 4.4.1 stuck in boot animation!

Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?

RedBullet said:
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
Click to expand...
Click to collapse
I would recommend flashing the 4.4 stock factory image from here in fastboot mode. Then once your device is booting up properly again I would recommend taking a look at this guide to properly install the 4.4.1 update.

You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.

planet_x69 said:
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
Click to expand...
Click to collapse
Thanks, I eventually got it. I was really puzzled that I couldn't select recovery from the bootloader. All set now though, thanks!

I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?

jalize said:
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
Click to expand...
Click to collapse
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...

RedBullet said:
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
Click to expand...
Click to collapse
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!

jalize said:
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
Click to expand...
Click to collapse
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery

RedBullet said:
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
Click to expand...
Click to collapse
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.

jalize said:
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
Click to expand...
Click to collapse
Hi,
Try flashing it fresh stock again, factory reset your device from recovery, download the stock image file from here, untar it, then unzip the zip inside the tar and you'll get some files (.img). Copy those files to your fastboot folder and then open a cmd there. (Guessing that you're using Windows)
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
If you're using Linux, do the same, but instead of only fastboot use:
Code:
sudo ./fastboot
Then boot it. I had the same problem when I updated mine to 4.4.1, but I did one thing a little different... Instead of fully "stocking" it again, I flashed back 4.3, flashed 4.4 OTA and then let it boot, without wiping my data, after all it was running like this before. Worked. But as I'm unsure of your situation I think it's more secure and easier to fully stock it again.
Hope this helps,
~Lord
PS.: Remember to put your device in fastboot mode!

[Q] not turn on after installing ClockworkMod Recovery

I have tried root my nextus 4 for install blinkfeed (http://forum.xda-developers.com/showthread.php?t=2696399)
enter into Fastboot mode.
and unlock the bootloader:
fastboot oem unlock
Then, without rebooting the phone, I installed ClockworkMod
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-mako.img
So I went to turn on the phone and I found it with the surprise that no turn on
the phone not pass the splash screen, with the drawing of circles moving.
But the phone enters fastboot mode if I press volume down and Power buttons.
appreciate any help.
excuse my English.
UPDATE
I have tried:
wipe data/factory reset
wipe cache partition
wipe dalvik-cache.
from fastboot, adb devices does not list anything. But "fastboot oem unlock" and fastboot "flash recovery recovery-clockwork-6.0.4.3-touch-mako.img" work.
really appreciate any help

Flash the factory image, then re-flash install cwm. Not rebooting after unlocking the bootloader is what is causing your problem
Sent from my Nexus 5

these
jd1639 said:
Flash the factory image, then re-flash install cwm. Not rebooting after unlocking the bootloader is what is causing your problem
Sent from my Nexus 5
Click to expand...
Click to collapse
excuse my ignorance.
I downloaded the factory image from developers.google.com/android/nexus/images
It contains a .bat called flash-all.bat.
Do I run the. bat? Or just need only re-flash the bootloader?

rockdrigo16 said:
excuse my ignorance.
I downloaded the factory image from developers.google.com/android/nexus/images
It contains a .bat called flash-all.bat.
Do I run the. bat? Or just need only re-flash the bootloader?
Click to expand...
Click to collapse
I'd use the flash-all.bat. you'll have to put the custom recovery back on and root
Sent from my Nexus 5

jd1639 said:
I'd use the flash-all.bat. you'll have to put the custom recovery back on and root
Sent from my Nexus 5
Click to expand...
Click to collapse
it worked! I love you.
Thank you very much.

Can't boot into recovery no matter how many times it is installed

Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?

carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app

Same thing, successful install and it won't open. Just shows the dead android when going to recovery.

carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app

Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought

tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app

tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.

If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.

Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!