Database Users

Need help recovering my nexus 6p!

Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.

When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?

matteosaeed said:
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
Click to expand...
Click to collapse
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.

Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Also check this out, it might help

matteosaeed said:
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Also check this out, it might help
Click to expand...
Click to collapse
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!

Why don't you just go to Heisenberg's guide in the general section and flash the latest stock images from Google via Fastboot and start from there? This way you'll at least have a working phone to boot into. From there you can reflash custom recovery and even systemless root. This is what I have always done when the phone wouldn't boot, or I had a backup handy and flashed that. When in trouble just flash latest images.

Asmodic said:
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
Click to expand...
Click to collapse
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Sounds like you need to update you drivers if your computer is not recognizing it

Asmodic said:
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Click to expand...
Click to collapse
Any Luck?

it's because you don't have the NEWEST version of TWRP.
Even the simplest of searches would've come up with this answer.

If your phone stuck at bootloop just go to recovery and wipe cache it will work.

pankajste said:
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
Click to expand...
Click to collapse
No it won't, not in this situation.

Heisenberg said:
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!

Asmodic said:
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Click to expand...
Click to collapse
So this should be marked "Solved?"

It should be marked as "when in trouble revert to Heisenberg's guide."

OPT is stuck and I cannot fix it

I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.

Flash fastboot images search and follow naman's unbrick guide, skip the data partition to keep your files
Sent from my ONE A2005 using Tapatalk

1439soccerdude said:
I was trying to install The paranoid custom rom 6.0.1 to my OPT when I started to running into an issue with boot looping. The phone would run through the bootup animation and then say it way starting up the apps. Once it was done with all the apps it would just start rebooting again. I tried to get into recovery to flash an old rom but I couldnt get in to recovery (holding the volume down and power button just turns the screen on and then back off.) I then tried this firstaid script I found on here that would supposedly install an older twrp and allow me to get into recovery mode, but that has not worked. And now I cannot even get the phone to go to a boot animation, it just sits on the oneplus logo. Adb is not detecting my device on windows or mac, but fastboot is working. At this point I have no idea of what to do, becuase even if I get into recovery I dont have a backup rom stored on my phone. If anyone has any ideas, I please share, I am in desperate need of help here.
Click to expand...
Click to collapse
This thread will help you, https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/

if you use twrp recovery and is not working on the Vol+ "-", try this way : RENAME your recovery file into twrp.img and flash it again.
If is not working,
following this thread first:
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
Then repeat my rename recovery method.

SOFT brick
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%

Seimus said:
You are a happy owner of a SOFTbricked OP2, happends mostly when you corrupt the partions. It easy to recover by Oneplus guide. You can use the link provided above by colleague on oneplus forum or this one XDA http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543. GO step by step works 100%
Click to expand...
Click to collapse
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours

Spannaa said:
Or you could use the updated version by @fareed_xtreme that @qingmui linked to in the post just above yours
Click to expand...
Click to collapse
Indeed but i prefer to go back to the previous build as per I know its stable. I like to do rollback and then the update. So I can better isolate any new caused issue

OEM unlock

I have the Chinese version of axon 7 and under development options I can click on OEM unlock then it asks for a pin number. How do I get that pin number?

Have you contacted zte customer service?

Please let me know how this turns out
I've been around these forums multiple times now and the ways that should work don't seem to work for me :/ Can't find a confirmed unlock of the Chinese version and am stuck on B13 while I wany Cyanogen.

If you go and sign up for ztes website and then go to the developers lounge there is a lot of talk about bootloader unlock. The way I read it you could have signed up to receive a pin number to unlock bootloader but zte has put that on hold? But are suppose to start it back up?

you can flash unlock bootloader in port 9008, I unlocked successfully by this way

@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.

enkrs said:
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
Click to expand...
Click to collapse
Did you flash twrp ? Official recovery does not support adb.
If you have already flashed twrp, then open computer manager- device manager, you will see your phone doesn‘t work correctly (triangle) , right click on the triangle, and click update driver, then computer will fix this proble automatically.

Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.

Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .

enkrs said:
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Click to expand...
Click to collapse
waiting for device...you should kill adb process first, and then reconnect your pc
---------- Post added at 11:33 ---------- Previous post was at 11:32 ----------
enkrs said:
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
Click to expand...
Click to collapse
if you want to downgrade the b13 to the b10，maybe you should use official recovery

If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.

enkrs said:
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
Click to expand...
Click to collapse
Hello Mate,
I am in the same situation as you. I have been looking all over the internet and came across a Chinese forum. Apparently, it is possible to unlock and root B13. However, I have used Google translater to translate the page. It's hard to understand the steps. I have not tested it. But maybe someone out there will have a better understanding and could give it a go. Here is the link
http://www.myzte.cn/forum.php?mod=viewthread&tid=320458&mobile=2
Hope that helps

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.

[SOLUTION] How to get out of the soft bricks and bootloops

If your device has unlocked boot loader and for some reason you just tried to flash something and it went wrong then there is no problem guys. The simplest solution if you are stuck on boot is that press vol down and power key for 3 minutes. It will work and will reboot. No before rebooting into the phone just go to the recovery by pressing the vol up key on boot process. This will load you in eRecovery of huawei. From there you can power off the phone. Now take out the sd card and put the desired rom in it. If you want stock android then you need to put UPDATE.APP in the dload folder in sd card and then go to eRecovery again. If you have a twrp recovery then you can go to stock as well and switch to a custom rom as well. Just place custom rom zip file and gapps zip file and flash it through twrp recovery.
For custom roms and recover visit :
Meticulus.co.vu

Thank you if I ever need it. Maybe someone that has needed to use this fix will confirm that it works.

gerrykiddy said:
Thank you if I ever need it. Maybe someone that has needed to use this fix will confirm that it works.
Click to expand...
Click to collapse
Well, it doesn't work for me... I held those buttons for 5 minutes, and all my phone did was to reboot about every15 seconds to the "Your device is booting now..."
I also tried with other button combos without any luck.

SnowmanDK said:
Well, it doesn't work for me... I held those buttons for 5 minutes, and all my phone did was to reboot about every15 seconds to the "Your device is booting now..."
I also tried with other button combos without any luck.
Click to expand...
Click to collapse
What happened to your device. Please tell me in detail ?

Arsaam said:
What happened to your device. Please tell me in detail ?
Click to expand...
Click to collapse
I made a post just before you did over here: https://forum.xda-developers.com/hu...i-p9-lite-stuck-bootloop-enter-t3600868/pages
After that post I managed to get into fastboot mode, when connected to my computer using usb, however my frp is locked and fastboot unlocked, so I am stuck there at the moment.

SnowmanDK said:
I made a post just before you did over here: https://forum.xda-developers.com/hu...i-p9-lite-stuck-bootloop-enter-t3600868/pages
After that post I managed to get into fastboot mode, when connected to my computer using usb, however my frp is locked and fastboot unlocked, so I am stuck there at the moment.
Click to expand...
Click to collapse
Download the SRK Tool for huawei p9 lite and unlock bootloader ( if required ). Then flash twrp recovery and then root the device. You might have made a mistake between any one of the processes. Also check if the OEM is unlocked in device developer options

Arsaam said:
Download the SRK Tool for huawei p9 lite and unlock bootloader ( if required ). Then flash twrp recovery and then root the device. You might have made a mistake between any one of the processes. Also check if the OEM is unlocked in device developer options
Click to expand...
Click to collapse
As written in the other thread, the phone boot loops, and I only have access to fastboot. It refuses to go into recovery and can not boot normally.
I can't flash TWRP as frp is locked.
I tried messing around with Miracle Loader 2.27A, but it can't find my phone (maybe I am doing something wrong).