Related
I am using Nexus Root kit to unroot my device. However I totaly forgot that I rooted it and tried to update to 4.4 kitkat. I got the error and when I try to boot up, it says no command. THere is no way past that screen. So in the toolkit i flash stocked and unrooted the device, but then i have to relock it. But to do so I need usb debugging enabled which is impossible to do without being able to boot up device. Now when I boot it up it has the android figure laying down with red triangle saying nothing. What do I do?
vito2772 said:
I am using Nexus Root kit to unroot my device. However I totaly forgot that I rooted it and tried to update to 4.4 kitkat. I got the error and when I try to boot up, it says no command. THere is no way past that screen. So in the toolkit i flash stocked and unrooted the device, but then i have to relock it. But to do so I need usb debugging enabled which is impossible to do without being able to boot up device. Now when I boot it up it has the android figure laying down with red triangle saying nothing. What do I do?
Click to expand...
Click to collapse
That Android guy lying down is fastboot. In fastboot mode you give this command: fastboot oem lock. This will re lock your bootloader. I think you will lose all your data. But I cant remember if it was with unlocking or locking the bootloader.
But why do you want to lock the bootloader?
Sent from my Galaxy Nexus using XDA Premium HD app
WOW, I fixed this problem 1 2 3. My nexus has been broken like this for weeks and I went to this link, went to the first step and downloaded from that link. I clicked on the file in there, it was a .exe and it ran something in command promt and the nothing happened. I thought nothing of it. Then after a few minutes I unplugged and gave up. Two seconds later I felt a vibration and the Nexus 10 set up came up and I was sooooo happy. Here is the link, I have no idea what it did, but it fixed it and my boot-loader is still unlocked!!!!! I broke up the URL so I could input the link.
redmondpie.com
/how-to-set-up-android-adb
-and-fastboot-on-windows-tutorial/
Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this
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.
The current state of my tablet is quite curious: Its stuck on Google logo and it will be this way until the battery completely drains.
What I've tried:
- Holding the Power button shuts it down for 1 second...then it boots right back up by itself.
- Recovery (POWER+VOL DOWN) doesnt work, it goes straight to Google screen.
- Connecting via USB to the computer, Windows doesnt recognize the device.
In fact, the only way I found to Turn the Tablet off is popping the back cover and unplugging the battery cable. I've left it unplugged at night, hoping it would clear some sort of Cache, didnt work. Also I've tried unplugging the battery cable, plugging it back and Turning it on with POWER+VOL DOWN in hopes of acessing recovery but it goes straight to Google screen.
Additional Info:
- This happened while I was trying to downgrade from 5.1 to 4.4.4.
- My device is the LTE version of N7 2012
- My device is currently rooted.
@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.
AndDiSa said:
@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough.
Click to expand...
Click to collapse
1 second is the ammount of time the tablet remains off, not the ammount of time i've pressed it. Yes, I've held it 20 seconds obviously.
AndDiSa said:
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.
Click to expand...
Click to collapse
Followed this guide right here: https://drive.google.com/file/d/0Bz6x7k-VkpUJU09paVM5cmh2Xzg/view
All the steps worked until the fastboot flash boot .\boot.img command. Sometimes it would get stuck on the command prompt and the tablet was frozen in Recovery Mode. I had to close the command Prompt, reboot the tablet into recovery again and Flashing another thing first, like recovery and system and THEN i would flash the boot.img.
So theres no hope?
First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs
AndDiSa said:
First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
The one indicated on the guide, named razorg-mob30x-factory-10b7ca08.zip, the link is in the guide link also.
I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs
AndDiSa said:
I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Oh Crap, really? Is there a fix?
Yup, same deal here, not done by me. Now I am stuck in APX mode and I need to somehow flash bootloader back into the tablet. Please, don't tell me there isn't any way to do this...
RavenEffect said:
Oh Crap, really? Is there a fix?
Click to expand...
Click to collapse
Have you tried flashing the images google gives on their website? (they also give a helpful guide)
Charles IV said:
Have you tried flashing the images google gives on their website? (they also give a helpful guide)
Click to expand...
Click to collapse
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
I know for mediatek, there is smartphoneflashtool, which flashes to the device when it's turned off. I don't know if there is an equivalent that you can use.
I don't think NRT does it, so you might be screwed.
There is nvflash ... but only if you have backed up *your* individual device images before you need them. So if your device is already bricked there is no chance ...
Sent from my Nexus 7 using XDA Labs
krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
Problem is that, when you plug the Tablet to the PC via USB, it doesnt recognize the device, like I've stated on the original post, so I cant even get to a step where I can flash any sort of file.
Well, if I think about it, only the bootloader got destroyed. The image is free on google sites. I just have to put the bootloader image into the tablet so I can get to the bootloader and flash everything else with fastboot. There has to be way to do that. I mean if the "BIOS" (screen with google logo) got destroyed, that is bad, but it is just matter of damage on free to share universal loader. There has to be way...
Hopefully someone can help me out here. I have been trying to root my phone, and everything goes fine but for some odd reason as soon as I relock the bootloader the phone wont boot anymore, I just get stuck at the boot screen indefinitely and have to revert to stock. I went through this process several times with the same issue, and unfortunately I got frustrated and started messing around. Not thinking I went into developer options and uncheck "allow OEM unlock," and forgot about it and rebooted. Now I can't get the phone to boot, but I can't flash unlock either. It will not boot into TWRP for some unknown reason as well, so at this point I don't see how I am going to fix this.
Even better, I just got the phone today...
Help!
sublimejhn said:
Hopefully someone can help me out here. I have been trying to root my phone, and everything goes fine but for some odd reason as soon as I relock the bootloader the phone wont boot anymore, I just get stuck at the boot screen indefinitely and have to revert to stock. I went through this process several times with the same issue, and unfortunately I got frustrated and started messing around. Not thinking I went into developer options and uncheck "allow OEM unlock," and forgot about it and rebooted. Now I can't get the phone to boot, but I can't flash unlock either. It will not boot into TWRP for some unknown reason as well, so at this point I don't see how I am going to fix this.
Even better, I just got the phone today...
Help!
Click to expand...
Click to collapse
Do not try to lock the BL if you are not completely stock.
If you have TWRP or anything like Magisk installed do not lock the BL.
If something goes wrong, you have a brick.
only lock the BL if you are completely stock.
sublimejhn said:
Hopefully someone can help me out here. I have been trying to root my phone, and everything goes fine but for some odd reason as soon as I relock the bootloader the phone wont boot anymore, I just get stuck at the boot screen indefinitely and have to revert to stock. I went through this process several times with the same issue, and unfortunately I got frustrated and started messing around. Not thinking I went into developer options and uncheck "allow OEM unlock," and forgot about it and rebooted. Now I can't get the phone to boot, but I can't flash unlock either. It will not boot into TWRP for some unknown reason as well, so at this point I don't see how I am going to fix this.
Even better, I just got the phone today...
Help!
Click to expand...
Click to collapse
Why would you relock bootloader? Not a good idea especially after modifying software
Sent from my PH-1 using Tapatalk
tech_head said:
Do not try to lock the BL if you are not completely stock.
If you have TWRP or anything like Magisk installed do not lock the BL.
If something goes wrong, you have a brick.
only lock the BL if you are completely stock.
Click to expand...
Click to collapse
Man, I could have sworn it was not recommended to leave the bootloader unlocked. Not exactly the answer I wanted to hear unfortunately. Any idea why it won't boot just because I relocked the bootloader? It just seems like an odd thing to cause a boot loop, and it did it 3 separate times
Can you go to bootloader?
Sent from my PH-1 using Tapatalk
TJSteveMX said:
Can you go to bootloader?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I can get into fastboot
sublimejhn said:
I can get into fastboot
Click to expand...
Click to collapse
If your PC can recognize adb fastboot then just get the stock zip file from "back to stock" section here
https://forum.xda-developers.com/showthread.php?t=3701681
I messed up too and back to stock was my only way.
Make sure under bootloader, if you type fastboot devices and is waiting for device, use
fastboot devices -i 0x2e17
If the PC recognize your device then, you can save from your bootloop
Sent from my PH-1 using Tapatalk
TJSteveMX said:
If your PC can recognize adb fastboot then just get the stock zip file from "back to stock" section here
https://forum.xda-developers.com/showthread.php?t=3701681
I messed up too and back to stock was my only way.
Make sure under bootloader, if you type fastboot devices and is waiting for device, use
fastboot devices -i 0x2e17
If the PC recognize your device then, you can save from your bootloop
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I would do this, but I had unchecked "allow OEM unlock" when I booted up earlier. I cannot unlock the bootloader now from fastboot, and I can't flash back to stock because my bootloader is locked. I am pretty sure I am screwed at this point
sublimejhn said:
I would do this, but I had unchecked "allow OEM unlock" when I booted up earlier. I cannot unlock the bootloader now from fastboot, and I can't flash back to stock because my bootloader is locked. I am pretty sure I am screwed at this point
Click to expand...
Click to collapse
Try holding volume up and down right after essential logo and see if you can get into safe mode. Worth a shot.
Skickat från min PH-1 via Tapatalk
do you see your device in fastboot at all? try switching the slot.. fastboot --set-active=x where x is either _a or _b.
superior8888 said:
Try holding volume up and down right after essential logo and see if you can get into safe mode. Worth a shot.
Skickat från min PH-1 via Tapatalk
Click to expand...
Click to collapse
Not sure if I'm doing something wrong, but holding both volume buttons does nothing for me.
And I can get into fastboot and it registers the phone, but when I try to change slots it tells me it failed and I cannot change slots while locked
sublimejhn said:
Not sure if I'm doing something wrong, but holding both volume buttons does nothing for me.
And I can get into fastboot and it registers the phone, but when I try to change slots it tells me it failed and I cannot change slots while locked
Click to expand...
Click to collapse
It just stays on lineage boot screen?
Skickat från min PH-1 via Tapatalk
try reinstalling TWRP and flash LOS again, I think once you flash a different software the OEM UNLOCKING switch are not highlighted anymore(what I mean is you can't turn it off), if you can do fastboot, try doing fastboot -w and wait till it reboots.
imna357 said:
try reinstalling TWRP and flash LOS again, I think once you flash a different software the OEM UNLOCKING switch are not highlighted anymore(what I mean is you can't turn it off), if you can do fastboot, try doing fastboot -w and wait till it reboots.
Click to expand...
Click to collapse
It's OEM locked. Not true, you can lock it, and so he did.
Skickat från min PH-1 via Tapatalk
See this thread on Reddit:
https://www.reddit.com/r/essential/comments/7hocrl/psa_if_youre_running_a_custom_rom_recovery_on/
sublimejhn said:
Man, I could have sworn it was not recommended to leave the bootloader unlocked. Not exactly the answer I wanted to hear unfortunately. Any idea why it won't boot just because I relocked the bootloader? It just seems like an odd thing to cause a boot loop, and it did it 3 separate times
Click to expand...
Click to collapse
Check any forum of a phone with an unlockable bootloader. You never ever relock the bootloader unless you are 100% completely stock. Once relocked with modified software there is nothing you can do to get it to boot.
Your only hope might be a deep flash cable and qpst if you can figure out how to use it.
superior8888 said:
It just stays on lineage boot screen?
Skickat från min PH-1 via Tapatalk
Click to expand...
Click to collapse
Yeah it just continues to boot as normal, and then of course goes into the boot loop.
I cannot reflash twrp or any other room. Attempting to flash anything fails with the error cannot flash while locked. Same with using -w
Did you try the fastboot unlock command?
varxx said:
See this thread on Reddit:
https://www.reddit.com/r/essential/comments/7hocrl/psa_if_youre_running_a_custom_rom_recovery_on/
Click to expand...
Click to collapse
Just saw your post. Wonderful. Might be a good sticky on xda, I didn't see this on Reddit. Anyone want to buy a really expensive shiny brick?!