Can't update rooted nexus 6 - Nexus 6 Q&A, Help & Troubleshooting

Hey got my nexus 6 yesterday. Unlocked and rooted it. Now i cant install the OTA update. TWRP asks for a password. What is that about. Do i need to relock and reinstall the stock bootloader?

To apply OTA, you need to be completely stock. Not even rooted.
Either go back to stock, or just flash the new system images without wiping user data

Can i flash this system images from the downloads through the OTA?

driskl said:
Can i flash this system images from the downloads through the OTA?
Click to expand...
Click to collapse
Not sure what you meant. You can't flash a system image as an OTA. You can however download the system images and flash them in fastboot (you'll need to unzip it and flash the images one by one - see Method 2 at this Nexus 5 thread about how to flash - the steps are essentially the same. Just remember to enable OEM unlock in developer options before anything)
Note; unless you skip userdata image, your data will get wiped.

jj14 said:
Not sure what you meant. You can't flash a system image as an OTA. You can however download the system images and flash them in fastboot (you'll need to unzip it and flash the images one by one - see Method 2 at this Nexus 5 thread about how to flash - the steps are essentially the same. Just remember to enable OEM unlock in developer options before anything)
Note; unless you skip userdata image, your data will get wiped.
Click to expand...
Click to collapse
Ok thanks, that seems simple enough. Ill search for the files when i get home i guess.

driskl said:
Ok thanks, that seems simple enough. Ill search for the files when i get home i guess.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images

jj14 said:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Haha, Thanks that helps. Its my first nexus device, its never been that easy.
Now is wish my work computer didnt struggle with MTP and ADB.

Related

Unable to install OTA LRX21O

Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse

[Q] Error while installing 5.0.1 update

Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )
Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.
cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?
Anyone? I would appreciate the feedback, thanks!
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app
saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Keeping root when updating?

Maybe I'm just super bad at finding things in this forum but I can't find any discussion on how to guard root when going up to 5.1. It looks like the only app for that (OTA Rootkeeper) is no longer working. Do I have to unroot my n6 before I upgrade to 5.1?
Simple answer, yes.
Longer answer, you'll need to be 100% stock for an OTA to work.
Bootloader unlocked is okay...but everything else... System, kernel and recovery must be 100% stock firmware or else OTA will fail.
carlz28 said:
Simple answer, yes.
Longer answer, you'll need to be 100% stock for an OTA to work.
Bootloader unlocked is okay...but everything else... System, kernel and recovery must be 100% stock firmware or else OTA will fail.
Click to expand...
Click to collapse
Ok, so I have unlocked bootloader and I'm rooted. The OTA update just became available to me today. What are my next steps?
Sauveur said:
Maybe I'm just super bad at finding things in this forum but I can't find any discussion on how to guard root when going up to 5.1. It looks like the only app for that (OTA Rootkeeper) is no longer working. Do I have to unroot my n6 before I upgrade to 5.1?
Click to expand...
Click to collapse
Dude I had these same questions you can use the WugFresh Tool-Kit it works like a charm you do have to un-root but you can do so by keeping your data without a wipe just go to his website.
defyiant said:
Dude I had these same questions you can use the WugFresh Tool-Kit it works like a charm you do have to un-root but you can do so by keeping your data without a wipe just go to his website.
Click to expand...
Click to collapse
carlz28 said:
Simple answer, yes.
Longer answer, you'll need to be 100% stock for an OTA to work.
Bootloader unlocked is okay...but everything else... System, kernel and recovery must be 100% stock firmware or else OTA will fail.
Click to expand...
Click to collapse
Thank you both! I just need to find the Mac version of Wug's toolkit....
Sauveur said:
Maybe I'm just super bad at finding things in this forum but I can't find any discussion on how to guard root when going up to 5.1. It looks like the only app for that (OTA Rootkeeper) is no longer working. Do I have to unroot my n6 before I upgrade to 5.1?
Click to expand...
Click to collapse
Just use fastboot flash.
Go to Google and download the factory image for the one you want to flash. Unzip Factory image until you see system.img, recovery.img, boot.img, radio.img, and bootloader.img and copy them into your adb folder. On mine it is C/Androidsdk/sdk/platform-tools. Delete anything else unless you just want to keep it. DO NOT FLASH userdata.img as it will wipe data.
If any of the above have names that are different, change them to what is above.
Connect the phone to your computer and open a command prompt and get to your adb folder.
adb reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You are now updated with unlocked bootloader. You will have to re root the device. I suggest just putting TWRP on it and when you open twrp and select reboot it will ask if you want to root the device.
I found this info in another comment section on another site and can't remember the name to give credit. He's a boss though.

[Q] Can't unlock bootloader as there is no OS installed

Hi everyone,
I was in the process of installing the stock Android factory 5.1 image from Chroma -- During this process I wiped everything (System data, user data, cache, etc) in TWRP and then went to fastboot to start the factory image flashing process. However, I accidently relocked my bootloader by executing my commands in the wrong order. I am now in the position where I can't unlock my phone's bootloader, as I need to enable "Allow OEM Unlock" in the developer settings, however, I can't do that as my phone currently has no OS installed.
I am at a gridlock currently, not sure how to proceed. Any ideas as to how I can fix this?
Any help would be much appreciated, as at this point, I am totally locked out of my device
Format cache and userdata via fastboot.
Edit: TWRP for the win
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ
DebianDog said:
See @rootSU a tool might have saved him
Click to expand...
Click to collapse
@DebianDog, I never need saving
DebianDog said:
Format cache and userdata via fastboot. If that doesn't work, nothing you can do.
Edit: no OS? Yeah....
Sorry bro RMA
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3
Ooohhh Nice! Nothing like having a backup Good job!
Sent from my Benzo'd Google N6 on VZ
curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?
BladeRunner said:
curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?
Click to expand...
Click to collapse
Cutting and pasting while not paying attention is what I figured.
Not something I've done on my phone but at work once or twice....
Sent from my Benzo'd Google N6 on VZ
Glad it's all sorted.
Just noticed the avatar, very appropriate
rootSU said:
Glad it's all sorted.
Just noticed the avatar, very appropriate
Click to expand...
Click to collapse
I was thinking the same thing actually haha
No TWRP backup...
p011uX said:
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3
Click to expand...
Click to collapse
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?
NDAMT said:
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?
Click to expand...
Click to collapse
Do you have TWRP recovery installed?
rootSU said:
Do you have TWRP recovery installed?
Click to expand...
Click to collapse
Yes. Luckily. :good:
NDAMT said:
Yes. Luckily. :good:
Click to expand...
Click to collapse
Just download a stock rom.zip and put it on your sdcard.
rootSU said:
Just download a stock rom.zip and put it on your sdcard.
Click to expand...
Click to collapse
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
Where did you get that? Got a link?
NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk
rootSU said:
Where did you get that? Got a link?
Click to expand...
Click to collapse
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
zephiK said:
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
No you need a flashable rom.zip from XDA.
NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Sent from my Nexus 6 using Tapatalk
rootSU said:
No you need a flashable rom.zip from XDA.
Click to expand...
Click to collapse
zephiK said:
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Click to expand...
Click to collapse
OK, at this point treat me like a noob. What rom.zip would you recommend for someone who is trying to get their phone back to factory?

Categories

Resources