Related
Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..
YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.
zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.
Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:
lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s
That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Im have the same issue but I have no recovery installed..Anyway to do this
i have same issue plz give me any solution if you found any???plz let me know plzzzzz
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
I can`t unlock bootloader, I get the following error:
FAILED (remote: Command not allowed)
finished. total time: 0.018s
Phone relocked. FRP Lock. Can't boot normally. Stuck in eRecovery or in bootloader mode.
dj_adri said:
I can`t unlock bootloader, I get the following error:
FAILED (remote: Command not allowed)
finished. total time: 0.018s
Phone relocked. FRP Lock. Can't boot normally. Stuck in eRecovery or in bootloader mode.
Click to expand...
Click to collapse
Unfortunately, because of the FRP lock, is what is causing the commands to fail.
Were you doing anything prior to trying to unlock the bootloader?
What model do you have?
dj_adri said:
I can`t unlock bootloader, I get the following error:
FAILED (remote: Command not allowed)
finished. total time: 0.018s
Phone relocked. FRP Lock. Can't boot normally. Stuck in eRecovery or in bootloader mode.
Click to expand...
Click to collapse
you must logout huawei id before unlock bootloader
ccchill said:
you must logout huawei id before unlock bootloader
Click to expand...
Click to collapse
How do I do it? The phone is in bootloop
Wirmpolter said:
Unfortunately, because of the FRP lock, is what is causing the commands to fail.
Were you doing anything prior to trying to unlock the bootloader?
What model do you have?
Click to expand...
Click to collapse
MHA-L09C02 but is rebranded to mha-l29c432b363. I close the bootloader because i flash xposed and the phone entered to bootloop, I could have closed it but now I can not open it.
Have you solve it? Unfortunatelly i have the same issue:crying:
dj_adri said:
MHA-L09C02 but is rebranded to mha-l29c432b363. I close the bootloader because i flash xposed and the phone entered to bootloop, I could have closed it but now I can not open it.
Click to expand...
Click to collapse
Yeah, seems xposed causes this type of issue for everyone I've heard who tries to install it.
Can you still get into erecovery?
Icaxus said:
Have you solve it? Unfortunatelly i have the same issue:crying:
Click to expand...
Click to collapse
Yes, this is the only solution without pay:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
I got LineageOS installed, restarted to bootloader and locked bootloader.
I can now:
Get into LineageOS Recovery
Boot to LineageOS ROM
I cannot:
Unlock bootloader
Unlock flashing
Unlock OEM from developer options (Option is greyed out)
What I tried, rooting and trying the following adb commands.
HTML:
adb root
adb shell setprop ro.oem_unlock_supported 1
Got the error:
HTML:
setprop: failed to set property 'ro.oem_unlock_supported' to '1'
I can only run LineageOS and go into LineageOS recovery and Adb sideload from recovery and install rooting apps.
Help! Want to 'fastboot flashing unlock'
Video:
https://vimeo.com/304615053
UPDATE:
UPDATE: Solution given by the dev razorloves(https://forum.xda-developers.com/member.php?u=614507) the dev who mantains the LineageOS ROM for Pixel details here:
https://forum.xda-developers.com/showpost.php?p=78361157&postcount=32
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Archangel said:
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Click to expand...
Click to collapse
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
tomatosmoothie said:
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
Click to expand...
Click to collapse
Archangel said:
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
Click to expand...
Click to collapse
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
I hearya nothings worse than having a problem and your the only one. Did that on a few phones. I have the Pixel 3 too now and I stay stock with some small edits and my Substratum themes running. I love the custom roms but sometimes they can be a real pain. Yeah I would give LOS 16 a try I guess what do you have to lose.
tomatosmoothie said:
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
tomatosmoothie said:
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
bafforosso said:
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
Click to expand...
Click to collapse
Thanks, I was thinking the same thing, also, the idea was to flash a ROM that would be able to allow OEM unlocking in dev options, but I feel maybe LOS Recovery is not allowing me to unlock.
Also thinking of flashing stock factory image via LOS Recovery.
I will tread carefully though, thanks.
No way your bl is locked.
Sent from my Pixel XL using Tapatalk
lafester said:
No way your bl is locked.
Click to expand...
Click to collapse
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
bafforosso said:
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
Click to expand...
Click to collapse
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
tomatosmoothie said:
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
Click to expand...
Click to collapse
Sorry I mixed things up : use the flash-all.sh (or flash-all.bat if using Windows) script with your device in fastboot mode as described on the stock firmwares download page.
[Correct but not for flashing stock firmware]
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
bafforosso said:
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
Click to expand...
Click to collapse
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
tomatosmoothie said:
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
Click to expand...
Click to collapse
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
bafforosso said:
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
Click to expand...
Click to collapse
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.025s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.034s
[email protected]:~$ fastboot oem unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.027s
[email protected]:~$
tomatosmoothie said:
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
Click to expand...
Click to collapse
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideload file.zip"
tomatosmoothie said:
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
Click to expand...
Click to collapse
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
bafforosso said:
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
Click to expand...
Click to collapse
Got a Permission denied.
HTML:
[email protected]:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$ ./flash-all.sh
bash: ./flash-all.sh: Permission denied
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying: