Database Users

Bootloop on brand new 4.2.2

I've encountered an unpleasantly unique problem (as far as the internet is concerned) with my Nexus 7.
It started when I wanted to upgrade my Nexus from 4.2.1 to 4.2.2. For whatever reason, the upgrade wouldn't install, gave me an error a quarter of the way through and booted me back into 4.2.1 with no repercussions.
Using WugFresh's Nexus Root Toolkit, I managed to get 4.2.2 onto there by flashing it over everything. It seemed fine, but went into a bootloop on the Google splash screen before it could start up and go through the first time setup.
I have tried everything. I tried flashing again with NRT, and got the image attatched, a hither-to unseen error that could not be fixed with a pc reboot or reinstall of NRT. I tried using the old Nexus Toolkit to boot into CWM recovery, but since USB debugging isn't (and can't be) turned on, that could do nothing. I've tried using the SDK command line to unlock it and flash it, but the device can't be found because it hasn't been booted up for that first time startup configuration. I've tried uninstalling all the drivers and trying all of that again, with nothing.
What's left is a nexus 7 with a brand new 4.2.2 that can't boot, no USB debugging, that is locked and unrooted. I can get into the bootloader, but there's no recovery installed.
I'm sorry if this has happened before. I'm sorry if this isn't new. But good christ almighty I just want my tablet to work.
tl:dr help me gods of the Android

If you can boot into the bootloader, can you use the SDK's fastboot tool to flash the stock recovery?

jfmcbrayer said:
If you can boot into the bootloader, can you use the SDK's fastboot tool to flash the stock recovery?
Click to expand...
Click to collapse
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.

fudgyhoops said:
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
Click to expand...
Click to collapse
I suppose "fastboot oem unlock" doesn't work, either?

fudgyhoops said:
Nope. It just says "<waiting for device>" and stalls indefinitely when trying to flash anything onto the device.
Click to expand...
Click to collapse
As long as you can get into fastboot, you should be able to use fastboot commands, sounds like you have a driver problem. Did you uninstall all the drivers and install the pdanet drivers? If the pdanet drivers don't work try naked drivers. It doesn't matter if debugging is enabled or not or if your device is unlocked and unrooted, you should still be able to do everything via fastboot commands. I recommend wiping everything via fastboot commands and than flashing the stock image. I recommend avoiding rootkits they are more trouble than they're worth, fast boot is a lot easier, faster and safer. You might want to try a different computer if nothing else works. You might have a defective bootloader though. Make sure you check the device manager on your computer to see if there are any errors with the drivers, it should show a yellow triangle if the driver is not working, if that's the case click on update driver and navigate to the SDK drivers.
http://www.androidegis.com/how-to/how-to-unbrick-the-nexus-7/
---------- Post added at 09:01 AM ---------- Previous post was at 08:54 AM ----------
Once you get the stock image flashed, unlocked and rooted, you can use goo manager to install the twrp recovery.

jfmcbrayer said:
I suppose "fastboot oem unlock" doesn't work, either?
Click to expand...
Click to collapse
I was surprised when it did. I had done a full driver reinstall to prestige777's advice, and fastboot started working again. Ran into an error when trying to flash 4.2.2 and bootloader version 4.18 with mismatched signatures, but tried it on another computer (thank you prestige777 again) and it's booting!
Thank you both so much!

fudgyhoops said:
I was surprised when it did. I had done a full driver reinstall to prestige777's advice, and fastboot started working again. Ran into an error when trying to flash 4.2.2 and bootloader version 4.18 with mismatched signatures, but tried it on another computer (thank you prestige777 again) and it's booting!
Thank you both so much!
Click to expand...
Click to collapse
No problem, I'm glad it worked for you.

[Q] Help please--Nexus stuck on bootloader

I am a noob at android--just putting that out there. But trying...
I just received my new nexus 7 2013. I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it, and then the plan was to root it. Something happened in the process--can't say for certain what, but at some point the tool brought up TWRP on the nexus and a file that the tool said was supposed to be there, wasn't. The end result now is that my nexus is stuck on the bootloader. None of the buttons seem to work, other than restart bootloader. Turn off DOES turn off the nexus, but then when pressed again, goes right back to the bootloader. The recovery one flashes the screen quickly, then goes back to the bootloader. The Start option makes it so the screen shows the "Google" icon indefinitely with the unlocked lock icon. I need to note that the option to get into the bootloader (power + vol up and vol down) did not work for me—the only way I was able to go into the bootloader was the power and vol down. Currently though, pressing the power button makes the nexus go directly into the bootloader.
When plugged into computer via the usb cord, windows xp currently doesn't recognize anything is plugged in, although I do have the latest USB drivers installed.
I downloaded and ran SDK and went through the various fastboot commands from within a cmd window. The fastboot devices command does bring up a device number, so it is recognized by fastboot.
Here's where others will start to shake their heads in bewilderment...in my haste to try and get this up and working and out of the endless bootloader menu, I *could* have flashed it with the nexus 7 2012 recovery image, because when using fastboot to do so, at end says something about grouper and my device says flo (although nothing changed with the nexus—as in there are no obvious changes as still in bootloader). I am aware that the official flo factory image is not yet available, although at this point, I don’t have much confidence in that doing anything.
If I open up Wugfresh’s Toolkit, I can’t do anything with it, as it says that ADB doesn’t work or something and to enable USB debugging, which I can’t do because I’m stuck on the bootloader.
I don't know where to go from here--I don't know if the device is salvageable or if it is completely toast and I should just return it and get another one...I see that in the day since I downloaded Wugfresh’s Toolkit, he has released two more versions—not sure if the new version can do anything—haven’t tried yet. Can anyone with more knowledge than myself give me a hand or some advice? Thanks in advance.

You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.

Username invalid said:
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Click to expand...
Click to collapse
it is unlocked. I am able to use the fastboot commands to unlock and lock. it currently is unlocked.

Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w

"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.

Username invalid said:
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Click to expand...
Click to collapse
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.

busdonic said:
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
Click to expand...
Click to collapse
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.

Username invalid said:
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Click to expand...
Click to collapse
Yeah, I see that....not sure why I did it myself actually, cuz now that you mentioned it, does seem pretty stupid--I guess that explains why I'm here asking for advice
I'm assuming that the one click restore will work. If it doesn't, I think I found a non-official flo factory image. I think (?) if I flash that to the tablet in fastboot, that will restore it, or at least get it past either the bootloader menu or past the Google icon shown at startup.

Geodude074 said:
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
Click to expand...
Click to collapse
this worked--thanks much. Am much relieved to be up and running again....

Nexus 10 Boot Loop after OTA 4.4.3 Update

I have a Nexus 10, rooted but still running stock. I clicked the 4.4.3 OTA update, it updated, and restarted in a boot loop. No idea what went wrong with the update.
I went to Recovery Mode and did a factory/data reset, but after that completed, it was still in a boot loop. I noticed the system recovery says "K0T49H", which is 4.4.3 that didn't install correctly, so I'm thinking maybe factory reset is out as an option.
I also tried entering Recovery Mode and applying the update via adb, but it says "Fastboot device was not found".
Any ideas on how to get it running again?

Giraffeteria said:
I have a Nexus 10, rooted but still running stock. I clicked the 4.4.3 OTA update, it updated, and restarted in a boot loop. No idea what went wrong with the update.
I went to Recovery Mode and did a factory/data reset, but after that completed, it was still in a boot loop. I noticed the system recovery says "K0T49H", which is 4.4.3 that didn't install correctly, so I'm thinking maybe factory reset is out as an option.
I also tried entering Recovery Mode and applying the update via adb, but it says "Fastboot device was not found".
Any ideas on how to get it running again?
Click to expand...
Click to collapse
It says "fastboot device was not found" because Fastboot is only for when you are in the Bootloader. ADB is for when you are in Recovery, or booted into the Android OS. Since you already did a factory data reset, I would assume you don't mind losing data. If that's the case, just boot into the bootloader and flash the entire factory image for 4.4.3.

charesa39 said:
It says "fastboot device was not found" because Fastboot is only for when you are in the Bootloader. ADB is for when you are in Recovery, or booted into the Android OS. Since you already did a factory data reset, I would assume you don't mind losing data. If that's the case, just boot into the bootloader and flash the entire factory image for 4.4.3.
Click to expand...
Click to collapse
When I go to bootloader, NRT doesn't find the device any more. Is there something else I need to do?

Giraffeteria said:
When I go to bootloader, NRT doesn't find the device any more. Is there something else I need to do?
Click to expand...
Click to collapse
Oh. You're using a toolkit... Sorry, can't help you much then. I'm not a big fan of toolkits for this very reason. It's much easier to figure out what went wrong, and where, when you flash everything manually. However, it sounds like there's a driver issue. Make sure you still have the correct drivers installed. That's all I can think of.

Giraffeteria said:
When I go to bootloader, NRT doesn't find the device any more. Is there something else I need to do?
Click to expand...
Click to collapse
I followed this guide: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and flashed through the bootloader. Wouldn't have gotten there without your help, though! Thanks!

Giraffeteria said:
I followed this guide: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and flashed through the bootloader. Wouldn't have gotten there without your help, though! Thanks!
Click to expand...
Click to collapse
NICE! Glad I could help. These Nexus devices are so easy to flash manually, so I don't really see the need for toolkits for this device. I can understand other locked down devices though. After I picked up my Gnex, doing everything manually was how I learned the basics of ADB and Fastboot.

Hi,
Glad to see that you solved your issue, could you please add a [SOLVED] tag to the title now?
~Lord

Soft Bricked Nexus 6P With Locked Bootloader (Need Help)

My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?

AlfexOmega said:
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
Click to expand...
Click to collapse
I'm in the exact same boat...hopefully something can be done, but I'm afraid we're idiots for not having checked OEM Unlocking. I've tried adb sideloading the OTA image, but as you said, with a locked bootloader, we've got nothing. Anybody have any ideas?

You might be able to use ADB to modify the OEM Unlock setting while booting.
Also, if you ever plan to mess with your OS, especially alpha/beta versions, always have your bootloader unlocked to prevent issues like this.

Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.

imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Live booting TWRP works on the 6P even with the bootloader is locked?
Sent from my Nexus 5X using Tapatalk

imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Can't boot twrp.img because the device is locked. Anything else I can do?

I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try

spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
No luck for me, unfortunately. Keep in mind that I tried to sideload the OTA.zip with a locked bootloader before doing this, so that may have made this process not work. For those who haven't tried to "fix" their failed installation like I did, give the cache clear a try first.

Apparently some people can use the fastboot format command while their bootloader is locked. You can try booting into the bootloader and issuing these commands. (THIS WILL WIPE YOUR ENTIRE DEVICE INCLUDING SDCARD/INTERNAL STORAGE. Of course, your device is now bricked, so I'm sure this is fine for you.)
Code:
fastboot format cache
fastboot format userdata

My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip

AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled

lightmastertech said:
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
Click to expand...
Click to collapse
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip

Ame123 said:
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Click to expand...
Click to collapse
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing

silviuardelean said:
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
Click to expand...
Click to collapse
Seems like it could be a driver issue. If you run adb devices does your device show up?

freezerbite said:
Seems like it could be a driver issue. If you run adb devices does your device show up?
Click to expand...
Click to collapse
Yes, the device was showing up in cmd but couldn't get over <waiting for devices>... I've tried to install TWRP and failed again. After trying to sideload the image a dozen times and clearing cache, formatting data, etc several times, it somehow worked in the end. Thank you very much!

It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging

GeorgeOSbeta said:
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
Click to expand...
Click to collapse
I was able to get mine to work without having it enabled you could try using Nexus Root Toolkit it guides you through how to do everything
https://www.youtube.com/watch?v=LfDSZsr6230

Locked bootloader 7.1.1 ota preview help!
I have the latest preview build directly installed ota from Google. The phone just started bootlooping the other day for no apparent reason. I didn't have the developer options on or oem unlock enabled.
I can get to bootloader mode and recovery mode. I have wiped and reset from recovery with no help. I can access adb and fastboot on the pc but it won't let me write any files because of the locked bootloader. Anything I try to sideload so far gives an error. Any further suggestions?

AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?

solefero69 said:
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
Click to expand...
Click to collapse
You use recovery to sideload it via adb. If you are unsure how to do so you can download and use Nexus Root Toolkit it does everything for you, it's really useful This video will help
https://www.youtube.com/watch?v=LfDSZsr6230

How to fix boot loop without OEM unlocking allowed or allow it using fastboot?

I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!

anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.

RoyJ said:
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
Click to expand...
Click to collapse
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?

anokmik said:
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
Click to expand...
Click to collapse
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.

anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.

RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
fapste said:
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
Click to expand...
Click to collapse
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.

anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.

jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.

Alsen Lea said:
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Click to expand...
Click to collapse
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
Click to expand...
Click to collapse
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.

RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Steps that I have done from stock recovery:
1. Wipe cache
2. Wipe data/ factory reset
3. Sideload 7.0 (angler-ota-nbd91k-32c2eac8) and the result is successful "script succeded: result was [1.000000]"
4. Wipe cache
5. Wipe data/ factory reset
6. Power off
7. Power on
Unfortunately boot loop persists and if I go back to recovery there is the same build version MTC20F (6.0.1).
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
Click to expand...
Click to collapse
For "fastboot oem unlock" command prompt returns "failed: remote: unknown command". I think this is because Google has changed such command to "fastboot flashing unlock", which gives me "failed: remote: oem unlock is not allowed". This because OEM unlocking hasn't been allowed from Developer Options by previous owner and now I cannot get there because of boot loop. Also have tried "flash-all.bat" from 7.0 latest factory image and on each step it returns error "failed: remote: device is locked. cannot flash images" and this is because of locked bootloader.
Possible solution?
In Stock recovery I have "Mount /system" option. Maybe someone can clarify what does it mean and could it potentially fix boot loop in some way? I have tried google for it, but unfortunately have no luck in finding information about this option.
Thanks in advance for any information!

anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796

You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
---------- Post added at 11:39 AM ---------- Previous post was at 11:29 AM ----------
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/

fapste said:
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
Click to expand...
Click to collapse
Issue has star from me now. Thanks for the link!
jhs39 said:
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.

anokmik said:
Issue has star from me now. Thanks for the link!
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
Click to expand...
Click to collapse
Are you running the latest versions of ADB and Fastboot?

This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?

jhs39 said:
Are you running the latest versions of ADB and Fastboot?
Click to expand...
Click to collapse
These are the outputs from command prompt:
adb:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
fastboot:
fastboot version 0e9850346394-android
I think that they are the latest, because I'm an Android dev and I'm updating SDK with tools as soon as new version come in.
jhs39 said:
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
Click to expand...
Click to collapse
Yep, I have known that device has boot loop issue and it was selling as-is for repair. Also I have known that this issue could be fixed, so it was hit or miss. Now I think that this was a miss.

It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.

jhs39 said:
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
Click to expand...
Click to collapse
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?

anokmik said:
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
Click to expand...
Click to collapse
I don't think the warranty is transferable but it won't cost you anything to contact Huawei and see if they will help you out.
http://consumer.huawei.com/in/support/warranty-query/index.htm
You can go to this site to check if the device is still under warranty. I have read about them allowing RMA on 6Ps that were out of warranty so it's worth a try at least.

http://consumer.huawei.com/us/support/warranty-query/index.htm
Sorry this is the site to check if phone is in warranty within the US. Other site was for India.