Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks
download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.
Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app
dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.
YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app
Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
jaed.43725 said:
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
Click to expand...
Click to collapse
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
luiseteyo said:
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
Click to expand...
Click to collapse
Ok. So what I did was kinda following your setup here. I had to get the Android SDK first. Then extract that into C:/. Then I got the 4.3 like you said and extracted that C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools. Then because of the new SDK I put the phone into the first 3-button mode. I then ran flash-all. And after a minute I had stock 4.3.
Well i'm trying to update my Nexus 7 2012 to Android 5.0.2, after receiving the OTA update but keep getting an error.
I rooted my Nexus 7, and been thinking that's the problem, since it restarts to install the OTA update but goes to Recovery mode, and when i try to manually install the file get the following error :
https://www.dropbox.com/s/dqjc2ztzfbkvnuy/IMAG0897.jpg?dl=0
Any tips or solution for the problem?
Thanks in advance
Go here and flash the full image: https://developers.google.com/android/nexus/images
Skeetch79 said:
Go here and flash the full image: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Didn't want to do that, because means i'm going to loose everything
lmcmil said:
Didn't want to do that, because means i'm going to loose everything
Click to expand...
Click to collapse
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Thanks for the tip and explanation Skeetch79, will try to do like you wrote.
lmcmil said:
Thanks for the tip and explanation Skeetch79, will try to do like you wrote.
Click to expand...
Click to collapse
Np. Keep me posted
Sent from my XT1096 using Tapatalk
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
This method works great! I was in the same boat. I analyzed the updater script and then analyzed the ro.build.fingerprint from my system, and it doesn't contain the weird one that it errors out on. I debated just removing the build prop check and repackaging it as an update, but decided against it.
@lmcmil - per chance, did you flash a different kernel and/or switch to F2FS before this happened? If so, that might correlate to mine, since I did do that....
Either way, I'm gonna run stock again for a while and see how it feels.
EDIT:
I think these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
getprop("ro.build.fingerprint") == "google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/nakasi/grouper:5.0.2/LRX22G/1649326:user/release-keys" ||
abort("Package expects build fingerprint of google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys or google/nakasi/grouper:5.0.2/LRX22G/1649326:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
are what causes it to explode. First, it tries to mount ext4 instead of F2FS, which makes sense, but would cause the system partition to be unreadable if you converted it to F2FS. That COULD explain the odd "deestroy" build prop it thinks it got when it pulled ro.build.fingerprint, since when my system was fully booted mine matched the stock LRX21P using getprop from adb.
toastido i tryied to load the OTA using the Nexus Root Toolkit and the error i got was regarding missing calculator, wich i removed after installing "Calculator ++" app
Still haven't had time to try this method, i'm working this weekend so only next week i can give it a try and post the result.
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Good Man !!!
Thanks Very Much for that one,
I got stuck on the boot after performing the advised but a quick Cache Wipe sorted that out.
Once again Much Obliged !!!
Yeah forgot to mention the above. if you are stuck in a boot loop: shut down. reboot to recovery. wipe cache and dalvic. Reboot. Profit.
Sent from my XT1096 using Tapatalk
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Does this also work if I want to go back to Kitkat? I am asking, because I've tried the following:
Code:
@echo off
echo. listing devices:
fastboot devices
echo. To continue press Enter
pause
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
REM adopt the following line according to the bootloader image filename
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And no matter, if I do a wipe cache afterwards or not, I end up in a boot-loop.
Do you know a way to keep apps and settings while going back to Kitkat?
nieroster
lmcmil said:
toastido i tryied to load the OTA using the Nexus Root Toolkit and the error i got was regarding missing calculator, wich i removed after installing "Calculator ++" app
Still haven't had time to try this method, i'm working this weekend so only next week i can give it a try and post the result.
Click to expand...
Click to collapse
lmcmil said:
Well i'm trying to update my Nexus 7 2012 to Android 5.0.2, after receiving the OTA update but keep getting an error.
I rooted my Nexus 7, and been thinking that's the problem, since it restarts to install the OTA update but goes to Recovery mode, and when i try to manually install the file get the following error :
https://www.dropbox.com/s/dqjc2ztzfbkvnuy/IMAG0897.jpg?dl=0
Any tips or solution for the problem?
Thanks in advance
Click to expand...
Click to collapse
TWRP is incompatible with 5.x OTA: it uses its own moronic default.prop instead of importing the device build.prop (or something like that) . It needs to be fixed.
You have to bother flashing the full image (minus the wiping eventually) and reinstall root & TWRP with every update, just like the rest of us
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
lmcmil said:
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
Click to expand...
Click to collapse
Well decided to use the Nexus Root Kit and flash the full image LRX22G, doing it now.
Will post how it went.
lmcmil said:
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
Click to expand...
Click to collapse
I had the 2012 Nexus 7 WiFi before I picked up the 2013 model. I had the same issue with that bootloader. Seems to be a common issue. Here are articles discussing the issue and fixes.
http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
https://code.google.com/p/android/issues/detail?id=62198&
http://forum.xda-developers.com/showthread.php?t=2573015
I remember flashing a modified bootloader to resolve the issue, since as you can see the bootloader packaged with the images is borked.
EDIT: try flashing the appropriate bootloader from this thread: http://forum.xda-developers.com/showthread.php?t=2417097
lmcmil said:
Well decided to use the Nexus Root Kit and flash the full image LRX22G, doing it now.
Will post how it went.
Click to expand...
Click to collapse
So my Nexus 7 is now running with 5.0.2, and did not loose any apps since i chose the "No wipe mode"
Going to root it again, and install latest TWRP Recovery
lmcmil said:
So my Nexus 7 is now running with 5.0.2, and did not loose any apps since i chose the "No wipe mode"
Going to root it again, and install latest TWRP Recovery
Click to expand...
Click to collapse
So i have now a Nexus 7 running 5.0.2, already rooted again and with TWRP 2.8.4.1.
Thanks a lot!
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- ...
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Thanks for the great tutorial! Used it yesterday on my rooted Nexus 7 to upgrade to 5.0.2, worked like a breeze! :good:
Afterwards I used WugFresh's Nexus Root Toolkit to regain root.
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
I followed this tutorial yesterday and everything went great I now have 5.0.2 working on my Nexus 7 2013, with no problems I can detect at the moment. Thank you, because I was just frustrated I saw the OTA notification without being able to do anything.
Cheers.
I try it too 5.0.2 ota update and nothing still on 4.4.4 I guess on Lollypops for me
My phone is now turning off at 30% so I'm sending it in under warranty to Huawei. Has anyone else done this? Did you put your phone back to stock?
Yes I did in November. Wouldn't boot the nougat rom and just hung on the Google screen. Tried absolutely everything via ADB twrp and sdk windows and Mac. No joy. So I relocked the bootloader then flashed the stock MM rom. Still no joy and basically screwed as stuck in the Google screen. I rang Huawei UK and they authorised a RTM repair. They changed the motherboard and the same phone came back with a new imei letter and sticker. It's been fine since and happily running Pure Nexus 7.1.2 with Franco and magisk. :laugh:
I sent mine for repair and I'm in the UK. Although I did it through my carrier (EE) not Huawei. You really want to put everything back to stock, you don't want any reason for them to deny you warranty or anything. Flash the latest images from the Google nexus page then relock the bootloader. That should be all you need to do, I've sent mine back twice and did that. They knew anything.
Followed Step 10 in Heisenbergs post
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
But its been on the spinning Google logo for about 20 minutes now...
Exact steps I carried out:
1. Go to Settings/Backup & Reset and perform a factory data reset.
2. Download the appropriate factory images (7.1.2 (N2G47O, May 2017))
3. Unzip the angler-xxxxxx-factory-xxxxxxxx C:\angler\)
4. Move the following files to a new directory named C:\angler\images\
-bootloader-angler-angler-03.68.img
-radio-angler-angler-03.81.img
5. Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
-boot.img
-bootloader-angler-angler-03.68.img
-radio-angler-angler-03.81.img
-recovery.img
-system.img
-userdata.img
-vendor.img
6.Boot into the bootloader and connect your phone to your PC via usb cable,enter these commands to flash:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.68.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.81.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
7. Then I rebooted.
Could it be because I 'fastboot erase cache'?
vinokirk said:
Exact steps I carried out:
1. Go to Settings/Backup & Reset and perform a factory data reset.
2. Download the appropriate factory images (7.1.2 (N2G47O, May 2017))
3. Unzip the angler-xxxxxx-factory-xxxxxxxx C:\angler\)
4. Move the following files to a new directory named C:\angler\images\
-bootloader-angler-angler-03.68.img
-radio-angler-angler-03.81.img
5. Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
-boot.img
-bootloader-angler-angler-03.68.img
-radio-angler-angler-03.81.img
-recovery.img
-system.img
-userdata.img
-vendor.img
6.Boot into the bootloader and connect your phone to your PC via usb cable,enter these commands to flash:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.68.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.81.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
7. Then I rebooted.
Could it be because I 'fastboot erase cache'?
Click to expand...
Click to collapse
I doubt that would be the issue. Give it a bit more time, these things often take a while to boot first time. You dont't have to extract everything and do the individual commands though. After the first unzip there is a flash-all.bat (assuming you're on windows), just run that with adb/fastboot files added to that directory
I wanted to make this post about my adventure with my old Pixel 2. I was getting non-stop red lines out of the log in TWRP. Many times I would have problems mounting system and vendor partitions as well as vendor partitions needing "to be cleaned".
This led me to believe that I may have a corrupted partition, so I did some research into how the partitions are organized, and what happens when you flash a lot of ROMs. Perhaps you want to go back to the stock firmware? Perhaps - like in my case - you want to install a ROM such as GrapheneOS that's meant to lock the bootloader afterwards, and act more like the stock ROM.
What I didn't understand up until recently is how exactly the A and B slots of phones like the Pixel 2 work. They work because the firmware allows updating OTA to the opposite slot of what's active. That way - in the worst case scenario - you can actually boot into the opposite slot and regain access to your phone. I'm not an expert on this, but that's my basic understanding.
So now that that's covered, another important aspect is flashing ROMs. If you are like me and like testing many different ROMs, you may end up running into issues such as the one I stated above with TWRP.
The only way I was able to avoid these types of issues is to run some commands through fastboot.
One such command is
Code:
fastboot format system
This command will format the system partition and make it easier to install ROMs without running into issues.
Another command is
Code:
fastboot format vendor
This command was very important in my case, because the vendor partition was actually unusable for my slot A. Doing this command finally fixed that issue.
Another thing to note is ROMs can be installed in both slots. A lot of people don't do this, because they leave their bootloader unlocked and probably just run the ROM for half a day, and flash another. In my case, I needed to flash both slots in order to lock the bootloader in GrapheneOS, and allow the OS to update OTA. If you don't flash both slots, that won't work.
Just to clarify further, these are the commands (at the bootloader) I ran (from a command prompt in Windows) in order from start to finish when I was flashing a ROM I wanted to keep:
Code:
fastboot --set-active=a
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot --set-active=b
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
// Let the phone reboot into the new ROM, let it sit for a minute,
// then reboot into bootloader manually and then continue with fastboot:
fastboot --set-active=a
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
Once I've done this, and can confirm it successfully loads into the ROM I've installed, I can now say that I have a clean, fresh install in BOTH slots A and B.
I'll update this thread if I can think of anything else that can help newbies like me.
Cheers!
HCFL said:
I wanted to make this post about my adventure with my old Pixel 2. I was getting non-stop red lines out of the log in TWRP. Many times I would have problems mounting system and vendor partitions as well as vendor partitions needing "to be cleaned".
This led me to believe that I may have a corrupted partition, so I did some research into how the partitions are organized, and what happens when you flash a lot of ROMs. Perhaps you want to go back to the stock firmware? Perhaps - like in my case - you want to install a ROM such as GrapheneOS that's meant to lock the bootloader afterwards, and act more like the stock ROM.
What I didn't understand up until recently is how exactly the A and B slots of phones like the Pixel 2 work. They work because the firmware allows updating OTA to the opposite slot of what's active. That way - in the worst case scenario - you can actually boot into the opposite slot and regain access to your phone. I'm not an expert on this, but that's my basic understanding.
So now that that's covered, another important aspect is flashing ROMs. If you are like me and like testing many different ROMs, you may end up running into issues such as the one I stated above with TWRP.
The only way I was able to avoid these types of issues is to run some commands through fastboot.
One such command is
Code:
fastboot format system
This command will format the system partition and make it easier to install ROMs without running into issues.
Another command is
Code:
fastboot format vendor
This command was very important in my case, because the vendor partition was actually unusable for my slot A. Doing this command finally fixed that issue.
Another thing to note is ROMs can be installed in both slots. A lot of people don't do this, because they leave their bootloader unlocked and probably just run the ROM for half a day, and flash another. In my case, I needed to flash both slots in order to lock the bootloader in GrapheneOS, and allow the OS to update OTA. If you don't flash both slots, that won't work.
Just to clarify further, these are the commands (at the bootloader) I ran (from a command prompt in Windows) in order from start to finish when I was flashing a ROM I wanted to keep:
Code:
fastboot --set-active=a
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot --set-active=b
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
// Let the phone reboot into the new ROM, let it sit for a minute,
// then reboot into bootloader manually and then continue with fastboot:
fastboot --set-active=a
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
Once I've done this, and can confirm it successfully loads into the ROM I've installed, I can now say that I have a clean, fresh install in BOTH slots A and B.
I'll update this thread if I can think of anything else that can help newbies like me.
Cheers!
Click to expand...
Click to collapse
Would this help in bootloop as well? I have a pixel 1st gen that does. I have flashed and or tried to anyways factory images...OTA and even was able to boot twrp and get lineage to flash, only to get a random reboot and bootloop. I would need to flash the factory image in order to get this phone operable. Should I flash a factory image and then do your steps or should I do the steps first and then flash the factory image?
Nope. Did not work. Seems as if the stock recovery is fubar