Nexus 6P - the locked bootloader and bootloop paradox - Nexus 6P Q&A, Help & Troubleshooting

Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.

Hey!
Thanks for your fast reply and your helpful tone.
However, when I choose Recovery mode it once again stucks in bootloop resulting in me never accessing recovery mode

npjohnson said:
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Click to expand...
Click to collapse
I am not sure my first reply was sent (having an unstable connection) so trying again:
When in bootloader and pressing recovery mode it goes straight back to bootloop. Hence, I cannot access recovery mode. Feels like a catch-22.

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
maybe if you posted it in the correct forum, you would get an answer...

Moved to the correct board...

If you can't boot the phone and you can't boot to recovery and Android debugging and oem unlocking are not enabled, there isn't much (read anything) you can do. Maybe take it to a local repair shop and see if they can replace the motherboard for you.

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Heating the phone temporarily boots the phone. (You can also check videos for saving data in bootlooped LG phones)

Related

[SOLVED] Bootloop. No recovery. Bootloader locked.

================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008

Bootloop and cannot boot into recovery

Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.
I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app
Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.
Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.
Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.
Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.

Bootloop / No Recovery / History Unknown

Good evening XDA,
I've got a Nexus 6p (obviously), and can't get it to boot. Unfortunately, I don't know the exact history as to how it's in this state.
I've tried everything I can think of and read every guide/steps/forums I can find that relates to my situation.
I can get to the bootloader and issue Fastboot commands. I've got adb/fastoot/drivers installed via the sdk/platform tools, and drivers are up to date as far as I can tell.
-I'm using the OEM cable attached to my computer (Surface Pro3, Windows 10)
-I can unlock/re-lock the bootloader as I wish.
-I've tried WugFresh toolkit, flash factory + unroot. All completes, but phones continues to loop even after leaving it for an hour+.
-I've tried Heisenbergs guide for manually flashing stock google images via fastboot to no avail. Tried several different google images. Everything completes, but it still just loops.
-I can get all fastboot commands to complete with no errors, but the phone just simply bootloops at the google logo, or if I leave bootloader unlocked it loops with the orange triangle & google logo. I have left it looping for at least an hour+, but it doesn't finish:crying:
-Stock recovery or a fastboot flashed trwp recovery simply won't boot, it just goes to the google logo and loops, I don't get the dead android w/triangle. "Recovery" in the bootloader selections is RED, if that means anything. Tried fastboot commands to boot recovery, but just sends it to the google logo and loops.
-Adb commands don't work, only fastboot commands.
-During flashing a google stock image with fastboot, the only thing that stands out is "max download of ####### reached", or something similar, but it still completes.....?
Seems to me that I've got a true brick (first ), and just need to send it in for repair.
Any help would be greatly appreciated. TIA.
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
TnT_ said:
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
Click to expand...
Click to collapse
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Dhickory said:
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Click to expand...
Click to collapse
Does all the data in the bootloader look fine? The storage size etc?
TnT_ said:
Does all the data in the bootloader look fine? The storage size etc?
Click to expand...
Click to collapse
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Dhickory said:
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Click to expand...
Click to collapse
Usually with board failure - that I saw in other threads - there are missing fields. My phone had a little glitchyness after I accidentally flashed the userdata.img - which caused my 128gb to become 32gb, which I found amusing - Other than that, I don't know. I'm sure others would reply.
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Dhickory said:
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Click to expand...
Click to collapse
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Jammol said:
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, and I've been reading the "Let's figure out this brick together" thread. The link you posted requires ADB commands to work to fix the EFS partition, but I can only run fastboot commands. ADB nor Recovery work on my device. Still reading...
Woohoo! Huawei replaced the phone, no questions asked. I think the saving grace was being able to flash stock images, and relock the bootloader. May be helpful to anyone else in this situation that can only run fastboot commands, and no recovery.

Stuck on Encryption Unsuccessful

I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
epr2175 said:
I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
Click to expand...
Click to collapse
There is another thread around here that answers your problem. I had the same issue. Something along the lines of plug in phone and open command prompt with command : and reboot bootloader and reboot phone. When you see twrp booting and installing files hit enter and you should boot into twrp again.
I tried it about 35-40 times and failed. It finally worked after many tries. Look for the thread around here somewhere though.
---------- Post added at 04:42 AM ---------- Previous post was at 04:38 AM ----------
Found it, its under questions and answers. The title is "hi guys my tmobile is stuck in bootloop"
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Also stuck at the same page with the reset button please help
Locking/Unlocking Bootloader Works!!
Thank You!!! You finally got my phone to work after trying for a few days! :laugh:
jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you for this tips, i Lock the bootloader and then Unlock it again as your command, and viola my phone back to life haha
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
still have issue, i can't install ane apps now.. how to solve it please ?
jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
You saved the day my friend! Locking and unlocking via fastboot did the trick. Phone booted right up.
runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
Okay - I have this too now. I have a h910 that I just followed runningnak3d's dirty santa guide on. Been flashing all around the last 2 weeks - learning a lot along the way. But today I flashed back to stock 10r. I fomatted data in TWRP - typed yes etc and it just reboots to that. I went to TWRP and installed Alpha Omega Oreo - same error. Restored one of my backups of Lineage I get the same error. So what is the right way out of this problem?
KDZ back and follow your dirty santa guide to re/unlock the bootloader? (I sure hope Brian is still around reading these) Not to screw up the terminology - but if TWRP still boots as my recovery - doesn't that mean my bootloader is unlocked.?
Well - not sure what I was doing yesterday... But wiped all, format data and factory reset in TWRP this morning and flashed h910 10r and then Magisk v20.4 and it worked. Could it be as simple as forgetting to flash Magisk? Maybe that is all that was wrong?
Thanks for reading.
Well if you find yourself in this same sticky spot - check out this here
I flashed 2018-04-15 level and my restore worked without issue.
YMMV
Good Luck
I formatted data in twrp. No change
The correct answer is to downgrade twrp, at least only that fixed it for me.

Cant leave fastboot after unlocking bootloader....

So just got the axon 7 mini yesterday and was so excited I decided to try to root it with my laptop while my girl was driving us home from Las Vegas..... Ell I got as far as unlocking the boot loader.... now i get this odd screen after i try to exit fastboot. (pic-1) and no matter what option I pick the only thing that will come up is this screen. The only time its different is if I try to chose start from this screen then I get (pic-2) The best thing about this is that I can still go back to fastboot anytime. And it shows up in fastboot devices. Do I need to reflash stock thru fastboot? If so How and Where can i find it. Can I just flash nougat? I'm new to ADB/Fastboot.... Thank you for your time and consideration ahead of time for any help.
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
William Guo said:
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Click to expand...
Click to collapse
I tried the thing were saying over and over
MrWhite0429 said:
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
Click to expand...
Click to collapse
so I was stuck all day yesterday trying anything and everything. BY THE WAY...Im very knowledgable but im pretty much a newb in rooting dept. especially fastboot. Well it seems I erased everything including the bootloader then battery died and no I have NOTHING on screen, no vibrations. Pretty much looks bricked. But when I try to put it in my computer to charge it it still shows up in my devices. BUT its not being found in adb/fastboot. I've tried every key combo/and length of holding them which doesnt do nothing
Can you place the device in edl? It will not display any lights or images when it is in edl.

Categories

Resources