Database Users

[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.

[Q] Nexus 7(2012) Recovery Mode no command?

Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?

JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.

JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
GedBlake said:
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi guys, I actually encountered this problem a minute ago when I attempt to flash a new version of TWRP recovery on my grouper. Whenever I go to the recovery, it just shows 'No command' with a red alert of Android on it (I started to panic when I found that there's an unusual error that prevents me from entering the recovery and this is the first time that I saw this error on my flashaholic experience *btw my previous recovery was CWM) I'm currently on stock 4.4.2 with an unlocked bootloader. I have no idea what problem is causing to display that issue when attempting to enter recovery but then I left it for like 5-10mins while it's displaying that error and after that the device reboots then it just quickly enter TWRP recovery normally as is :silly: sick of that haha, silly ol grouper jesus -_-
EDIT
After entering recovery, I got stuck forever on bootloader and recovery! whenever I reboot, I always get directly enter to the recovery and it forces me to not to enter the ROM oh my god at least I can still configure the recovery so I can backup and flash another ROM :|

[Q] Nexus 10 bootloop and no Recovery menu

Hi, I've been trying to downgrade my Nexus 10 from Lollipop to KitKat but without success. I got as far as unlocking the bootloader. But when I download the .tar factory image and extract it, I don't get any .img files nor the flash-all.bat files. (I managed to downgrade my Nexus 5 mobile, however, with the right .img files and flash-all.bat files).
Something must have gone wrong with my Nexus 10. It's locked in a bootloop indefinitely. To make it worse, when I enter Recovery mode, I don't get the image of the lying robot, and can't access the factory reset menu. The bootloader is presently unlocked.
Please help...I'm really lost.

jbm59er said:
Hi, I've been trying to downgrade my Nexus 10 from Lollipop to KitKat but without success. I got as far as unlocking the bootloader. But when I download the .tar factory image and extract it, I don't get any .img files nor the flash-all.bat files. (I managed to downgrade my Nexus 5 mobile, however, with the right .img files and flash-all.bat files).
Something must have gone wrong with my Nexus 10. It's locked in a bootloop indefinitely. To make it worse, when I enter Recovery mode, I don't get the image of the lying robot, and can't access the factory reset menu. The bootloader is presently unlocked.
Please help...I'm really lost.
Click to expand...
Click to collapse
What do you get when trying to go into the bootloader?

jsgraphicart said:
What do you get when trying to go into the bootloader?
Click to expand...
Click to collapse
It's OK now. I managed to install Clockworkmod recovery, and flashed a CM11 image. Thanks just the same.

Help really need here, big issues

Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126

the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049

Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck

gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way

Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.

adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS

It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.

fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess

Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?

Upgrading from Build N4F26J (7.1.1) to OPR6.170623.017 (8.0.0). Bricked?

Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!

Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
You don't flash a factory image in TWRP. Unzip the file and flash the individual images: boot, system, and vendor. Try that method or use ADB sideload to install the full OTA image. Full OTA images can be downloaded from the same site.
Sent from my Nexus 5X using Tapatalk

I'm assuming you have ADB / fastboot in place (if not, google it): unzip your factory image to a given folder. Navigate to this folder using prompt / terminal. Turn on your phone with vol down pressed and leave it at that screen. Plug it onto your computer and type fastboot devices - you should see a line with a bunch of numbers. If Windows, run flash-all.bat. If Mac / Linux, run flash-all.sh. Your phone should get back to life in a few, sit back and relax.

Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.

wizardwiz said:
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
Click to expand...
Click to collapse
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.

ultyrunner said:
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
Click to expand...
Click to collapse
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked.
I wasn't talking about using a manual fastboot option to flash an indevidual image.

wizardwiz said:
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked. I wasn't talking about using a manual fastboot option to flash an indevidual image.
Click to expand...
Click to collapse
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.

ultyrunner said:
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
Click to expand...
Click to collapse
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.

wizardwiz said:
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
Click to expand...
Click to collapse
No we're not in competition. My point was you gave him one option with the least control and not remotely the best option to get his device up and running, particularly making an assumption he has a locked bootloader, when you never asked. If he is able to use a command line to run a flash command, then pointing him to the guide is the best bet. If something goes wrong with flash-all scripts then he's probably going to be really lost.