Flashing 5.0.1 - Nexus 6 Q&A, Help & Troubleshooting

I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6

SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.

Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...

So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error

mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6

SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.

SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!

Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360

I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.

dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?

mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.

Awesome man, worked perfect, you sir rock!

Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.

Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse

Related

[Q] Attempted to Downgrade and now bricked [solved]

First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
**EDIT**
If you have done the same bone-head move I made, then follow these simple steps.
1. Use RSD lite to update to 4.4.4
2. Follow this guide to then root your device once you have updated to 4.4.4
This works because your bootloader is unlocked, thanks to sunshine.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
RSD 422 means a downgrade. What did it "say"?
Downgrading is the no no.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
http://forum.xda-developers.com/showpost.php?p=55491148&postcount=10
samwathegreat said:
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
Click to expand...
Click to collapse
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
But I followed the rest of the directions and it still will only boot into fastboot.
wisenick said:
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
Click to expand...
Click to collapse
Did you really put spaces in between boot and loader? And Moto and boot?
samwathegreat said:
Did you really put spaces in between boot and loader? And Moto and boot?
Click to expand...
Click to collapse
No sorry, auto correct on the wife's phone.
wisenick said:
No sorry, auto correct on the wife's phone.
Click to expand...
Click to collapse
A "Permission denied" error sounds strange to me....don't recall having seen that one before.
Though I'm rather certain that your downgrade attempt (big no-no) is the culprit, I'm curious if @jcase might have any suggestions...
1) I don't think you are bricked, this should be fixable. This is due to you flashing older firmware to a device that has been updated, nothing to do with sunshine.
2) your title makes it sound like sunshine to blame, this is really bad for me. SunShine CANT brick motorola (nor htc) phones. We simply have too many safety checks, and verification. If you were able to flash and boot TWRP (which you were because you took a backup) then it can't be sunshine. It would be great if you changed the title to be more accurate.
Having said that, I have no problem helping you recover your phone, it certainly isn't bricked
I'm out from 10amPST to 2pmPST tomorrow, but please email me jcase AT cunninglogic DOT com, and I will have you up on your feet in minutes. Probably setup teamviewer and I will just remote in and do my best.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
samwathegreat said:
Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
jcase said:
...nothing to do with sunshine.
2) your title makes it sound like sunshine to blame...
Click to expand...
Click to collapse
That is what I first thought when I read the subject...
 @wisenick, you even mention in your OP you don't blame Sunshine, so why mention it in the subject?
Can you change the subject of this thread to "Attempted to Downgrade and now bricked" or "Attempted to downgrade and now phone wont boot"? That would be more accurate.
piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Just checked the XML and it is gpt then bootloader. I'll see if that fixes things.
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Verttex said:
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Click to expand...
Click to collapse
Thank you but I've tried that. It says that it flashed but when I try to boot into recovery it simply boots into fastboot
piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Double checked the order and according to the xml , its gpt first. However I still get an error when I try to flash motoboot
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
If Sunshine unlocked your bootloader, you should be able to do whatever.
wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
Yes you lost root! but
If you used sunshine, you turned your consumer phone into a developer phone, meaning you will always be able to root it trivially and properly.
True. if your back in android w/o root
Download Supersu in a zip file
boot to bootloader
fastboot flash new recovery
reboot into the new recovery
flash supersu zip
you have root! Easy w/ an unlocked bootloader!

5.0.1 without wiping?

So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
scothern99 said:
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
Click to expand...
Click to collapse
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
livinginkaos said:
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
Click to expand...
Click to collapse
Ok, so not to be a noob, where do I get the image files to flash?
Nexus images are all posted here - https://developers.google.com/android/nexus/images
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
scothern99 said:
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
Click to expand...
Click to collapse
Does anyone know if this is correct?
What I did to upgrade without wiping, i was on stock with elementalx kernel, root and twrp.
Only flashed radio and system img.
1. Downloaded images, extracted zip of the images.
2. Reboot to bootloader
3. Fastboot commands
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
4. Reboot to bootloader again
Run chainfire autoroot script.
5. Done
Remember to read read read if you don't know what are you doing, nobody here is responsible if things go wrong.
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
lion1750 said:
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
Click to expand...
Click to collapse
I'm wondering the same. Usually it was out right away and I would do the same as you. Seems crazy to me that we would have to unroot update and reroot agaain.
Usually I would flash a stock rom with the update that the dev would also throw root into.
livinginkaos said:
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
Click to expand...
Click to collapse
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
GMoGoody said:
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
Click to expand...
Click to collapse
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
livinginkaos said:
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
That su 2.4zip is for all devices? Not just for the n7 fhd? Thx
Via my NeXus™ 7FHD on XDA Premium app

Flash LMY47E and Preserve Data

I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.
Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery
From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up
y2whisper said:
From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up
Click to expand...
Click to collapse
Only if you boot android before rooting. Install-recovery.sh is suppled with the ROM that upon boot will install stock recovery. However flashing SuperSU hijacks this script for its own purposes, removing its ability to flash recovery. So trick is flash the ROM, boot straight to recovery and flash SuperSU
Ah. Good to know
rootSU said:
Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery
Click to expand...
Click to collapse
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
EDIT: See your post above (I took too long typing). Thanks for clarifying.
ManHands said:
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
Click to expand...
Click to collapse
Have a look above.
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed
moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
rootSU said:
Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed
Click to expand...
Click to collapse
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.
ManHands said:
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.
Click to expand...
Click to collapse
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.
Look at the op on Franco's thread and you'll have your answer
holeindalip said:
Look at the op on Franco's thread and you'll have your answer
Click to expand...
Click to collapse
If he looks in the Franco thread, it will answer his question about having to flash a stock boot.img?
moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?
rootSU said:
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.
Click to expand...
Click to collapse
Brain fart, for future reference Franco r1-r19 is 5.0,5.0.1,5.0.2 and r20+ is for 5.1
Thanks for the input everyone. To follow-up, I took the steps just as I planned in OP. No need to flash boot.img as frano-r20 is what I'm running and is compatible with 5.1 (despite the build # difference). I also didn't want to encrypt as the factory boot.img will force encrypt.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
And just as @rootSU pointed out, prior to booting system, go into TWRP from bootloader to install su.zip first (otherwise factory recovery will overwrite TWRP). Then boot system, and you're back in business. Just had to re-do a couple build.prop edits, but everything else was as it was before.
If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?
lamenting said:
If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?
Click to expand...
Click to collapse
That, or you can wait for 47E factory boot.img that's non-enforcable. But, from the sounds of it people are still able to use the 47D boot.img linked in the post you provided. I'd imagine there's not much difference between the two.
Forerunner326 said:
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?
Click to expand...
Click to collapse
I have no idea honestly, I saw someone else post it that way. It is probably not necessary.
ManHands said:
I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.
Click to expand...
Click to collapse
After flashing the files in fastboot you said to use the hardware buttons to boot into TWRP. How exactly did you go from fastboot to TWRP? Did you just power off while in fastboot or something else?

[Q] Unable to upgrade rooted Nexus 6 to 5.1.1

I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.
2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.
danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.

While upgrading from 6.01-7.0 crashed at 83% Now Stuck at Google logo image w/Unlock

Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?
touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!

Categories

Resources