Database Develop

[Q] Bootloop...Help?

So I rooted and unlocked yesterday, flashed cwm, and then flashed cm10 posted in the dev forum.
After having wifi issues, I decided to go to the Goldenrom.
Now I'm stuck in a boot loop. I can get back to recovery (and no, I forgot to make a backup), and tried wiping and flashing again. no luck.
I thought about trying to RSD but I can't. I can get to fastboot but RSD doesn't recognize it as being anything.
Please help.

Did you try holding the vol down and power until it shuts off. Then hold both vol down and up with power at the same time. It will give you options to choose. Then vol down to fastboot and press up to select it.

JayWheelz said:
Did you try holding the vol down and power until it shuts off. Then hold both vol down and up with power at the same time. It will give you options to choose. Then vol down to fastboot and press up to select it.
Click to expand...
Click to collapse
Yeah I've tried all that.
It can be mounted in fastboot, and RSD sees a device, but it doesn't have any information. Doesn't see it as an atrix, a razr, anything.
I also can't mount the sd card in cwm for file transfer. I was gonna try and flash one of the stock rooted roms I saw around here, but can't get the zip on storage.
Any thoughts?

rcloke91 said:
So I rooted and unlocked yesterday, flashed cwm, and then flashed cm10 posted in the dev forum.
After having wifi issues, I decided to go to the Goldenrom.
Now I'm stuck in a boot loop. I can get back to recovery (and no, I forgot to make a backup), and tried wiping and flashing again. no luck.
I thought about trying to RSD but I can't. I can get to fastboot but RSD doesn't recognize it as being anything.
Please help.
Click to expand...
Click to collapse
//////////////////////////////////////////////////////////////////////////////////////
you get in fastboot you in good shape....
rsd does not recognize your device.....uninstall mot helper drivers and install it back.....
you ll see now rsd recognize your device...

health unityni
htchd2fix said:
//////////////////////////////////////////////////////////////////////////////////////
you get in fastboot you in good shape....
rsd does not recognize your device.....uninstall mot helper drivers and install it back.....
you ll see now rsd recognize your device...
Click to expand...
Click to collapse
tried and rsd recognizes it, but doesn't say what it is.
uninstalled and reinstalled motohelper. didn't help anything, unfortunately. any other ideas, guys?

Don't worry
If you can get to fastboot don't worry your fine. Follow the steps below. You can just flash the stock files via fastboot tools.You can thank skeevy420 also. Got this from his post here.
http://forum.xda-developers.com/showthread.php?t=2226527
These are the steps:
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot

thanks
jkm43 said:
If you can get to fastboot don't worry your fine. Follow the steps below. You can just flash the stock files via fastboot tools.You can thank skeevy420 also. Got this from his post here.
http://forum.xda-developers.com/showthread.php?t=2226527
These are the steps:
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Click to expand...
Click to collapse
that did the trick. well done. im still curious as to what the problem was, but at least now i know it can be fixed.

So I did this and it worked, decided to re-root and reflash CM10.
I'm selling my Atrix now, so I've decided to reflash the stock rom. This time, though, the above steps didn't work. I'm stuck at the motorola logo. I can still get to fastboot. I've tried reflashing stock, but it hasn't worked, as I'm still stuck at the M logo.
I'd try the RSD Lite method, but even after reinstalling drivers, RSD doesn't recognize the device.
Any NEW thoughts?
I feel like a noob...
EDIT:
Nvm, figured it out. I forgot about the snapdragon fastboots...

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

Flashing 5.0.1

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

[Q] Mismatched partition size (recovery) when flashing stock 5.0.1 recovery

I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.

Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.

Evo_Shift said:
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Click to expand...
Click to collapse
I used fastboot -w to format the userdata/cache. And I also tried the three fastboot commands you listed. They all seem to work, but the reflashing of the recovery still throws the same error.
MD5 checksum of the whole zip is the same. I re-extracted the recovery.img file just to be sure and it still throws the same error.

Kramit said:
when I try to get back into recovery, the phone sits at the android with the red triangle and !.
Click to expand...
Click to collapse
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen

rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.

rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
yes, thats norml

cmh714 said:
yes, thats norml
Click to expand...
Click to collapse
Hmm. And if it doesn't work?

Kramit said:
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Click to expand...
Click to collapse
I have the same problem here but maybe i have found a solution for it:
what i did was i left the 5.1 bootloader.img and took all the other stuff from a 5.0 factory image such as: radio.img, system.img..... fastbooted everything and i was with a 5.0 LP stock out of the box, then i have rooted it, installed twrp with f2fs support and voila i'm now good to go
hope this will help you out

Kramit said:
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
Click to expand...
Click to collapse
When you see the android with the red triangle and !, you need to hold the power button, and while you are holding it down, press volume up. Pushing them both together, or one after the other, or holding them down together or whatever else won't work.
Sent from my Nexus 6 using Tapatalk

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!