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.
Related
I am a noob at android--just putting that out there. But trying...
I just received my new nexus 7 2013. I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it, and then the plan was to root it. Something happened in the process--can't say for certain what, but at some point the tool brought up TWRP on the nexus and a file that the tool said was supposed to be there, wasn't. The end result now is that my nexus is stuck on the bootloader. None of the buttons seem to work, other than restart bootloader. Turn off DOES turn off the nexus, but then when pressed again, goes right back to the bootloader. The recovery one flashes the screen quickly, then goes back to the bootloader. The Start option makes it so the screen shows the "Google" icon indefinitely with the unlocked lock icon. I need to note that the option to get into the bootloader (power + vol up and vol down) did not work for me—the only way I was able to go into the bootloader was the power and vol down. Currently though, pressing the power button makes the nexus go directly into the bootloader.
When plugged into computer via the usb cord, windows xp currently doesn't recognize anything is plugged in, although I do have the latest USB drivers installed.
I downloaded and ran SDK and went through the various fastboot commands from within a cmd window. The fastboot devices command does bring up a device number, so it is recognized by fastboot.
Here's where others will start to shake their heads in bewilderment...in my haste to try and get this up and working and out of the endless bootloader menu, I *could* have flashed it with the nexus 7 2012 recovery image, because when using fastboot to do so, at end says something about grouper and my device says flo (although nothing changed with the nexus—as in there are no obvious changes as still in bootloader). I am aware that the official flo factory image is not yet available, although at this point, I don’t have much confidence in that doing anything.
If I open up Wugfresh’s Toolkit, I can’t do anything with it, as it says that ADB doesn’t work or something and to enable USB debugging, which I can’t do because I’m stuck on the bootloader.
I don't know where to go from here--I don't know if the device is salvageable or if it is completely toast and I should just return it and get another one...I see that in the day since I downloaded Wugfresh’s Toolkit, he has released two more versions—not sure if the new version can do anything—haven’t tried yet. Can anyone with more knowledge than myself give me a hand or some advice? Thanks in advance.
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Username invalid said:
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Click to expand...
Click to collapse
it is unlocked. I am able to use the fastboot commands to unlock and lock. it currently is unlocked.
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Username invalid said:
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Click to expand...
Click to collapse
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
busdonic said:
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
Click to expand...
Click to collapse
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Username invalid said:
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Click to expand...
Click to collapse
Yeah, I see that....not sure why I did it myself actually, cuz now that you mentioned it, does seem pretty stupid--I guess that explains why I'm here asking for advice
I'm assuming that the one click restore will work. If it doesn't, I think I found a non-official flo factory image. I think (?) if I flash that to the tablet in fastboot, that will restore it, or at least get it past either the bootloader menu or past the Google icon shown at startup.
Geodude074 said:
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
Click to expand...
Click to collapse
this worked--thanks much. Am much relieved to be up and running again....
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 :|
So I was running cynogenmod on my nexus 7 2012, and now that lollipop is out, I wanted to do a complete restore of my device and install stock. I first tried a few one click methods, but none of those worked, so I tried using the android sdk to install it through the command prompt. After a long struggle, I gave up and tried to turn my device back on, but it says "booting failed" in the upper right corner, and it doesnt get past the google screen. I can get to fastboot no problem, but I cant get into my recovery(which I am guessing got wiped). When I tried to reinstall stock again, every method i tried got stuck on trying to flash the bootloader. Is my device permanently bricked? If its not how can I fix it? thanks
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
bftb0 said:
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
Click to expand...
Click to collapse
Yea in fastboot it says that the bootloader version is 4.23. Ill try flashing it without the bootloader and see if that works
ok so I tried running the flash-all.bat, and it says archive does not contain boot.sig, and archive.sig. Then, it continues flashing, but after it gets to sending boot, I get an error that says FAILED(data transfer failure (unknown error)). then When I try to do something on the nexus it is frozen, and I have to hold power and volume down to get back into fastboot. Am I missing the boot and archive files?
ok so I reinstalled the android sdk and then flashed the image and it worked. There must have been some files missing or something. Thanks for your help!
Hello XDA forums members. I need some help on recovering my Softbricked Nexus 10.
Here the situation. I unlocked the bootloader using Wug nexus toolkit. (Latest version as of typing is v2.1.9)
The procedure runs smoothly until the time to temporary boot to stock bootloader (Which does nothing btw)
I was thinking, what the heck, the unlock is already done, why not try booting to the stock recovery by Holding down Power+Volume Up
This was the time I realize my mistake, oh god. No Stock Recovery. Tried rebooting back to Fastboot. No Fastboot (When starting fastboot mode the tablet just restart itself.)
The only thing that I can access with the tablet is Download mode.
P.S: I did realize that in the C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Stock, There in no recovery stock.img in the folder which I suppose that's why my tablet won't boot to stock recovery.
Welp, solved by trying to flash twrp using odin and try to boot to bootloader from there, it seems like my fastboot mode was restored when i do that, and I restored to stock when fastboot is available. admin can you please delete this thread.
Thanks.
P.S: Gosh I'm stupid :'(
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.