I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?
Yes, but i flashed backed to stock kernal.
win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?
Nope
Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope
win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.
I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?
Related
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
Get s-off and restore any RUU.. After restore, better get s-off before you update, you won't be able to get it after the update.
Sent from my iPod touch using Tapatalk
TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
you need to flash the stock recovery and lock your bootloader to be able to do the update.
[email protected] said:
you need to flash the stock recovery and lock your bootloader to be able to do the update.
Click to expand...
Click to collapse
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
nkk71 said:
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
Click to expand...
Click to collapse
i stand corrected.
a stock recovery will do
[email protected] said:
i stand corrected.
a stock recovery will do
Click to expand...
Click to collapse
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
nkk71 said:
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
Click to expand...
Click to collapse
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
TaintedCross said:
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
Click to expand...
Click to collapse
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
nkk71 said:
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
Click to expand...
Click to collapse
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
TaintedCross said:
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
Click to expand...
Click to collapse
Does fastboot work?
Sent from my HTC One using Tapatalk
nkk71 said:
Does fastboot work?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I can boot into fastboot on my phone but I've no idea what to do from there.
Edit: HELLS YEAH! I got it! lol had to relock bootloader using fastboot and then go back into fastboot on my phone and run the RUU.exe and it worked this time! SOOO freaking stoked and happy! I've been up for 7 hours straight trying to fix this!
Nice. Please update the thread and put SOLVED
Sent from my HTC One using xda app-developers app
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.
PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?
gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?
nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Sorry, meant 4.4.2.
gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.
I derped hard by working on my phone late at night. I accidentally wiped internal storage in TWRP and couldn't get ADB sideload to work. I've tried pushing files in NRT, flashing stock + unroot... nothing seems to work.
I then tried flashing the stock image using the instructions on Google's image download page. The command prompt said for security reasons I should re-lock the bootloader, and I did in my sleepy ways. DOH!
Now I can get into the bootloader and TWRP, but sideload isn't working. When I type fastboot devices in the bootloader, my device shows up. Same with TWRP, until I go into Advanced > ADB sideload, then my device suddenly isn't listed. I am using TWRP 2.8.5.0. Is this a bug? I updated ADB binary to the latest version.
Am I totally screwed or is there something I can try before begging google to fix this?
You tried using Nexus Toolkit and select soft-brick to restore phone? Ive ran it a few times and always works for me, will pull latest SW and get it all set up again. After flash just unlock BL and root.
Unless I'm not understanding you correctly:
Since you've locked your bootloader i do believe the acronym SOL applies...
Didgeridoohan said:
Unless I'm not understanding you correctly:
Since you've locked your bootloader i do believe the acronym SOL applies...
Click to expand...
Click to collapse
I believe he is too but I swear I saw a thread somewhere here Motorola had a method for getting out of this. I would search XDA harder
Sent from my Google N6 on VZ
SurlyGnex said:
I derped hard by working on my phone late at night. I accidentally wiped internal storage in TWRP and couldn't get ADB sideload to work. I've tried pushing files in NRT, flashing stock + unroot... nothing seems to work.
I then tried flashing the stock image using the instructions on Google's image download page. The command prompt said for security reasons I should re-lock the bootloader, and I did in my sleepy ways. DOH!
Now I can get into the bootloader and TWRP, but sideload isn't working. When I type fastboot devices in the bootloader, my device shows up. Same with TWRP, until I go into Advanced > ADB sideload, then my device suddenly isn't listed. I am using TWRP 2.8.5.0. Is this a bug? I updated ADB binary to the latest version.
Am I totally screwed or is there something I can try before begging google to fix this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059518
Try this.
Sent from my Nexus 6
Casper34 said:
http://forum.xda-developers.com/showthread.php?t=3059518
Try this.
Sent from my Nexus 6
Click to expand...
Click to collapse
To be more specific, this isn't actually a fox for this issue but the guy in the last post as of now, reckons he managed to somehow get KT working. Though I'm skeptical
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
I downloaded the factory image and fastboot flashed the files.
Sent from my Nexus 6 using Tapatalk
Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
What error? Also, have you unencrypted?
Evolution_Tech said:
What error? Also, have you unencrypted?
Click to expand...
Click to collapse
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Shift2win said:
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Click to expand...
Click to collapse
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
Mine is doing the exact same, I'm also stock and on T-Mobile.
^same here...rooted and T-Mobile.
skipm said:
Mine is doing the exact same, I'm also stock and on T-Mobile.
Click to expand...
Click to collapse
n7plus1 said:
^same here...rooted and T-Mobile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61119896
Evolution_Tech said:
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Click to expand...
Click to collapse
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
neudof said:
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
Click to expand...
Click to collapse
Fastboot. You need an unlocked bootloader.
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
robert_shipley said:
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
Click to expand...
Click to collapse
That's exactly my problem, I'm completely stock and have to remain that way since I use my phone at work and they require the AirWatch MDM agent to be installed. I even tried deactivating AirWatch and uninstalling it and I still couldn't get the update to install. I hope there is some way they can either erase and download the update again or just overwrite the current one because this one definitely has problems.
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
bchildress said:
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
Click to expand...
Click to collapse
Just flash the system image. No need to flash everything. If you've unencrypted, then flash boot image too.
I have the same problem totaly stock, not rooted, untouched! I have the same error. I have 64 gb nexus 6 build number LMY47D.
Ok Guys,
Here is the solution,
1. Download stock image from google developer page, https://developers.google.com/android/nexus/images
2. Flash with long way;' DONT USE FLASH-ALL SCRIPT' (I tried, update fails again)
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-shamu-XXXXXX/cache.img
(FOR FURTHER INFO PLS SEE THE PAGE; http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
3. Just turn on your N6 and it will find update and will be succesfull this time
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Evolution_Tech said:
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Click to expand...
Click to collapse
Hey,
I am Rooted with TWRP Recovery and Elemental X custom kernel, still encrypted with unlocked bootloader. I got the OTA (LMY47Z) notification and I have got the Factory Image as well as the OTA Zip. Can you guide me as to how can I update my Nexus (currently LMY47I) to 5.1.1 without losing any data?
Thanks.
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
peerpower said:
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
Click to expand...
Click to collapse
Download the OTA Zip, Extract it and check the "\META-INF\com\android\otacert" file to find the version number for your phone.
bootloop. & bootloader is locked. And I do not have usb debugging enabled. Any way to get around this?
Depends... You're quite sparse with information about what you've done to get to where you are and about your setup.
A few options come to mind. If you have TWRP you can try flashing a custom rom zip and that could fix it. You could also try the special N preview OTA that google provided to fix phones that got screwed up by an N OTA. http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Yeah sorry about that. While updating to 6.0 the phone died. And is now stuck in a bootloop (stuck at the google logo screen). I was trying to use nexus root toolkit to flash stuck android back onto it, however my bootloader is locked. And I did not have usb debugging enabled either. So I am trying to find a way to unlock my bootloader. If that makes any sense
Use the second method I suggested. Should work.
Can you get in bootloader or recovery mode?
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Try to sideload shamu-ota-npc91k-201dd8d1.zip. (This upgrades to Android N Preview.)
Since the OTA is a complete image, it should restore the device to working condition. Then you should be able to enable USB debugging and OEM unlock so the bootloader can be unlocked through fastboot.
Sorry for the late replies. I am attempting the second method & I am able to boot into recovery mode. However I keep getting "adb server is out of date" so I am trying to work it out at the moment
This worked for me! Locked bootloader, no usb debugging, no custom recovery, stuck in bootloop due to software issues.
Bootloader showing engineering
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Warhammer143 said:
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Click to expand...
Click to collapse
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
simms22 said:
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
Click to expand...
Click to collapse
tried many things but not sure..
Is there any thread where I can find the instructions???
Warhammer143 said:
tried many things but not sure..
Is there any thread where I can find the instructions???
Click to expand...
Click to collapse
well, instructions, probably not. if its a flashable zip, that means that you can use twrp recovery to flash it. fastboot flashing has to be done while youre in the bootloader, using fastboot. the command is.. fastboot flash bootloader zipname.img
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Warhammer143 said:
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Click to expand...
Click to collapse
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
simms22 said:
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
Click to expand...
Click to collapse
Well, I will be searching on google, but thanks a lot!