if you have unlocked your bootloader status and you want your original 'Locked' status instead of 'ReLocked' status, follow the procedure.
1. fastboot reboot bootloader
2. fastboot oem relock UnlockCode this will ReLock your bootloader
3. switch on your phone, go to developer menu and Uncheck the OEM unlocking
4. Reboot your phone, done , your Phone status is now "Locked" , FRP is also Locked , you can check it in fastboot mode
5. if you want to unloack FRP, then just go to developer menu and Allow oem unloack, this will turn off FRP but bootloader status remains "LOCKED" , it doesn't change to ReLocked.
Enjoy
Dr.Anshuman said:
if you have unlocked your bootloader status and you want your original 'Locked' status instead of 'ReLocked' status, follow the procedure.
1. fastboot reboot bootloader
2. fastboot oem relock UnlockCode this will ReLock your bootloader
3. switch on your phone, go to developer menu and Uncheck the OEM unlocking
4. Reboot your phone, done , your Phone status is now "Locked" , FRP is also Locked , you can check it in fastboot mode
5. if you want to unloack FRP, then just go to developer menu and Allow oem unloack, this will turn off FRP but bootloader status remains "LOCKED" , it doesn't change to ReLocked.
Enjoy
Click to expand...
Click to collapse
Great..
When I complete step 2, I get the message:
<bootloader> The device will reboot and do factory reset...
FAILED (status read failed (Invalid argument))
finished. total time: 5.036s
I am immediately prompted on the phone to either proceed and factory reset or cancel.
Of course, I proceed. Factory reset lowlevel completes and reboots me to eRecovery.
I am given the option to "Download latest version and recovery" from wi-fi (which doesn't exist for the BND-L24), "Reboot", or "Shutdown".
Rebooting brings me right back, so my only option is to shutdown and use hardware keys to boot into recovery or fastboot. Recovery allows me to factory reset, wipe cache, or reboot, so, really, the only option is to go back into fastboot.
From there, I can see PHONE Relocked and FRP Unlock. I choose, therefore, to run fastboot oem unlock {myUnlockCode} and factory reset again.
I get the FAILED (status read failed (Invalid argument)) again, but it works to end the bootloop and take me to the setup wizard.
Has anyone else with an unlocked bootloader on the BND-L24 re-locked it successfully? How?
What am I doing wrong?
This removes the initial notice that the phone has been unlocked right?
johncro13 said:
When I complete step 2, I get the message:
<bootloader> The device will reboot and do factory reset...
FAILED (status read failed (Invalid argument))
finished. total time: 5.036s
I am immediately prompted on the phone to either proceed and factory reset or cancel.
Of course, I proceed. Factory reset lowlevel completes and reboots me to eRecovery.
I am given the option to "Download latest version and recovery" from wi-fi (which doesn't exist for the BND-L24), "Reboot", or "Shutdown".
Rebooting brings me right back, so my only option is to shutdown and use hardware keys to boot into recovery or fastboot. Recovery allows me to factory reset, wipe cache, or reboot, so, really, the only option is to go back into fastboot.
From there, I can see PHONE Relocked and FRP Unlock. I choose, therefore, to run fastboot oem unlock {myUnlockCode} and factory reset again.
I get the FAILED (status read failed (Invalid argument)) again, but it works to end the bootloop and take me to the setup wizard.
Has anyone else with an unlocked bootloader on the BND-L24 re-locked it successfully? How?
What am I doing wrong?
Click to expand...
Click to collapse
I did just like the op has listed, it re-locks. But I cannot get it to be "locked" it remains "relocked"
Before you do this you must be all stock. No TWRP .
---------- Post added at 09:49 PM ---------- Previous post was at 09:49 PM ----------
lowspeed said:
This removes the initial notice that the phone has been unlocked right?
Click to expand...
Click to collapse
Yes it does
I should have mentioned that I'm using stock recovery. I had TWRP but used logcat to get the URL for the 130 OTA download to my PC, extracted the recovery images from it, and flashed recovery 1 to 1 and 2 to 2.
can I do this while on a treble rom?
So I can get netflix to work?
Bootloader Relocked
Status of my Bootloader is relocked and FRP is locked, in reboot show me this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pligamia said:
Status of my Bootloader is relocked and FRP is locked, in reboot show me this screen
Click to expand...
Click to collapse
Is that the result of relocking, or some time later.
Do you have stock recovery and stock rom installed. Or did you make changes while you had unlocked.
luckily I had a warning message when I tried to re-lock . It said "root status fail", then failed to re-lock.
after flashed stock recovery it succeeded. I ended up unlocking again because updates still failed to install.
Any way back to your problem.
There is a tool called DC -unlock-er.
https://www.dc-unlocker.com/
It is not free, but claims to provide a needed code to unlock your FRP. then with that unlocked, you are supposed to be able to unlock bootloader again.
I did the unlocking, I tried to update via FF but a system file error occurred, I put TWRP, I took TWRP and I blocked the bootloader again then it started to appear that message, and even with the reloaded Bootloader I can not update via FF OTA.
Pligamia said:
I did the unlocking, I tried to update via FF but a system file error occurred, I put TWRP, I took TWRP and I blocked the bootloader again then it started to appear that message, and even with the reloaded Bootloader I can not update via FF OTA.
Click to expand...
Click to collapse
oh, but still boots. you just have the warning screen?
Anybody finding problem in opening page to get unlock code from Huawai unlock page https://emui.huawei.com/en/plugin/unlock/index
I have already registered, but unlock option is not shown or from other links page shows opening error. Pl help
Related
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Unlock your bootloader and retry.
Already retried to unlock the bootloader.. But no luck.. Thanks for the tips btw
I have found the solution.. I will post it in the weekend
luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
when u post please tell my in the praivte
[email protected]
Kingroot worked for me bit only after the second try
Tengo10 said:
Kingroot worked for me bit only after the second try
Click to expand...
Click to collapse
can u explain me please how u do it with king root??
eyalyagel said:
can u explain me please how u do it with king root??
Click to expand...
Click to collapse
I coud've offered more direct support if you messaged me or replied to my thread.
Have you found any solution?
Breadcrust said:
I coud've offered more direct support if you messaged me or replied to my thread.
Click to expand...
Click to collapse
can u give me please the link or explain may the way????
thank u very much
eyalyagel said:
can u give me please the link or explain may the way????
thank u very much
Click to expand...
Click to collapse
Did you do fastboot -i ox2b4c oem unlock?
Breadcrust said:
Did you do fastboot -i ox2b4c oem unlock?
Click to expand...
Click to collapse
yes,
FAILED (remote: Oem unlock is not support)
finished. total time: 0.008s
and i allow the oem in the developer option....
also i have the same phone in my home but the difrrent bitween them:
1. have only home press in the bottom
the ather phone have home, back,manu, bottom this phone can be unlocked and i sucsses to instal twrp
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
xnoobx said:
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
Click to expand...
Click to collapse
I'm also facing the same problem with my ZUK Z1
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
Dear
I was using CM12 new version till last week and i have lots of problems, specially with mobile signal during the calls voice is dropping signal is too week as well. So i have decided to move to ZUI version and it's perfect so far i'm not facing any problem. Only the vulnerable is there some kind of malware and GPS having some bugs i have checked with bbs.zuk forms and they are suppose to fix it with next update. so i was trying to install the stagefright fix via recovery.remaining everything is smooth and faster than CM12.
hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
I also tried to boot. But it also denies this action :/.
So with the latest version my boot loader is locked. Sounds wonderful.
luqmanhans said:
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Click to expand...
Click to collapse
In this case, you need flash fw Z1_CN_OPEN_USER_Q4275715.1_L_ZUI_1.0.050_ST_150910 via sd card ( root internal memory/creat sdfuse folder), after turn off fone and boot phone via factory mode recovery ( voulme down + power ). If phone flash ok, version is 1.0.050. So, phone can flash twrp recovery and rom CyanogenMod 12.1 .
Goodluck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
hristos13gr said:
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
Click to expand...
Click to collapse
First you must downgrade the ZUI from 1.2.040, just search this topic in this forum: how-to-flash-zuk-z1-zui-version-t3265741
After that you can boot with TWRP recovery. But if you failed to flash Cyanogen, use Modaco steps: 375804-convert-z1-from-zukui-to-cyanogen-os/
When your ZUK Z1 already use Cyanogen, you can flash to other recovery or ROMs easier .
Hello folks,
as for me such guides were really helpful in the past, and there are alway poeple who are new to a device and modding it, I decided to do one on my own, to show you how to perform a reset of your HTC U11 to Full Stock ROM/Firmware.
In many points I tried carrying together all that has been written down prior to this guide in many others, by many others. Thus I - in some kind - just consolidate the fact, using my own words and a little bit different structure than others. Anyway I'll show you my steps again in this tutorial as I think it is of importance to many that they can read the hole to do in one thread. But I advise everyone.
Please note that I will not accept any responsibility for possible occurring bricks. I can only confirm that this tutorial has been used by me, for my specific unit and all went successful.
Look here for [Collection] HTCU U11 – RUU/Firmware/Recovery/OTA/Backups
Regards
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Restore using a Nandroid Backup
Restore using a RUU
Knowledge of adb/fastboot
htc_fastboot and adb installed
HTC U11
07 RU_CID_FAIL: CID in android-info.txt does not match your phone’s CID
10 RU_MODELID_FAIL: MID in android-info.txt does not match your phone’s MID
12 SIGNATURE FAIL: phone expects an HTC signature and can't find one; or found a wrong one
22 RU_HEADER_ERROR: something wrong with your zip; check md5 of download
23 PARSING IMAGE FAIL: something wrong with the image within the zip
24 ANDROID-INFO FAIL: something wrong with android-info.txt within the zip
32 HEADER ERROR: the zip couldn't be read and unzipped properly; seems same as 22.
33 NOT KNOWN YET: might indicate hardware failure.
35 FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT <PartitionName>): means you can’t flash an image in download mode, as it has to be done in bootloader mode.
41 WRONG MODEL ID: means the RUU is menat for a different device
42 WRONG CUSTOMER ID: means you got to swap CID first
90 PRE-UPDATE FAIL: means it only flashed aboot and you have to run the process again immediately to flash all other partitions. The htc_fastboot.exe now auto-reboots on Error 90!
99 UNKNOWN: usually indicates you are S-ON, but sometimes also recognizes other Security related issues.
130 WRONG MODEL ID: see 41
155 INDICATES DIFFERENT THINGS:
the need to relock bootloader; if S-ON
the RUU cannot be executed, because the software versions of ROM, Firmware and RUU aren't matching
170 CHECK USB: RUU won’t run because ADB isn't working properly
171 USB ERROR: happens all the time when the RUU reboots the phone to download mode. For some reason the device is losing its connection and making a RUU flash virtually impossible . There is an incompatibility between USB 3/3.1 and Fastboot/ADB, as well as an issue with Windows Device Detection on the newer Windows 10 builds.
171 USB ERROR FIX by @Sneakyghost:
How to fix RUU error 171 on Windows 10x64 easily
System: Win 10 Redstone (1607) x64 with Intel based USB3.0 and USB2.0 ports:
Sync Manager from HTC Website
Imported Reg-File from Post #1
Reboot
Click to expand...
Click to collapse
Restore using a Nandroid
flash TWRP custom recovery
download custom recovery at https://twrp.me
reboot to download mode
Code:
adb reboot download
flash recovery image
Code:
htc_fastboot flash recovery nameoftwrp.zip
Restore your Nandroid. If you got none yourself, it might be possible that you’ll find one here.
unzip the according Nandroid
copy Nandroid to TWRP/Backup/SerialNo/Nameofbackup on your extSD
restore Nandroid by using TWRP > RESTORE and choosing above copied Nandroid
Flash incremental OTA firmware
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download all incremental OTA firmwares to your PC, starting with the one above your current firmware version, up to the software version number of your above choosen Nandroid Backup (ATTENTION: If you are S-OFF it will suffice to download the latest Incremental OTA as well as the latest Combined Full Wipe firmware according to the above choosen Nandroid Backup)
flash all incremental OTA firmwares – one after another – following the below named steps (ATTENTION: If you are S-OFF you start with the Combined FullWipe, and proceed with the Incremental OTA one, to ensure that you’ll be able to receive upcoming OTA updates)
Code:
htc_fastboot flash zip nameoffirmeware.zip
(ATTENTION: this has to be done twice to comlete, and it will flash full firmware, thus TWRP will be replaced by stock recovery)
As soon as you restored the Nandroid and flashed all incremental firmware file up to the current build number of your Nandroid, that's it. Your are now Full Stock again!
Restore using a RUU
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download the latest Stock RUU for your device over here.
flash your RUU to revert to stock
rename RUU to 2PZCIMG.zip
copy 2PZCIMG.zip to root directory of SD card
reboot to download mode
press Volume Up button to confirm flash of RUU
As soon as your RUU has been flashed sucessfully, that's it. Your are now Full Stock again!
Reserved just in case
Thanks you for this Always needed thread
Is it possible to install a non-branded RUU on a branded device, but otherwise keep things completely stock?
Zico 10 said:
Is it possible to install a non-branded RUU on a branded device, but otherwise keep things completely stock?
Click to expand...
Click to collapse
Not possible for as long as S-OFF isn't available. Will do a de-branding thread as soon as it becomes available.
Sent from my htc_ocnuhl using XDA Labs
deleted
Will this wipe my data?
5m4r7ph0n36uru said:
Not possible for as long as S-OFF isn't available. Will do a de-branding thread as soon as it becomes available.
Click to expand...
Click to collapse
Dying to unbranded my HTC U11 as well...
Will the bootloader say "Relocked" or "Locked" if i use this method and restore it to stock?
Sorry for the basic question.. Its been a long time used a HTC phone.
rkrishnamurthy said:
Will the bootloader say "Relocked" or "Locked" if i use this method and restore it to stock?
Sorry for the basic question.. Its been a long time used a HTC phone.
Click to expand...
Click to collapse
It will say relocked. A real locked state might be possible if S-OFF hits, but no way to do it until then.
Sent from my htc_pmeuhl using XDA Labs
Nice info when in the future want to go back to stock.
Sent from my HTC U11 using XDA Developers 2016 Premium
Hi,
I'm new to android. I was advised to root my HTC U 11 but after doing so and exploring options I decided I'd rather just remove root and return to stock. However, I'm a noob and didn't do a backup before flashing the recovery and rooting. I found this thread and it seems to have what I need but I'm hesitant to take the next step as I don't want to brick my new phone. Can someone explain what I need to do to return to stock in as simple/dumbed down way as possible?
It's a single sim variant, carrier is Optus (Australia) and the original software version was 1.03.710.7
There's only this step by step guide. Couldn't be more precise at what to do. If you don't understand such a detailed guide I'm a little bit irritated at why you rooted in the first part, if you don't know what happens by doing so and how to revert back properly
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
There's only this step by step guide. Couldn't be more precise at what to do. If you don't understand such a detailed guide I'm a little bit irritated at why you rooted in the first part, if you don't know what happens by doing so and how to revert back properly
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
i've did all the steps and still my bootloader will not relock with the RUU method.
Stock RUU flash not working, her is fail message. Any ideas?
Error code 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
mr573162 said:
i've did all the steps and still my bootloader will not relock with the RUU method.
Click to expand...
Click to collapse
RUU any method does not relock bootloader, you have to manually do it in fastboot. Download mode, CMD type fastboot oem lock
---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------
andybg40 said:
Stock RUU flash not working, her is fail message. Any ideas?
Error code 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
Click to expand...
Click to collapse
Are you flashing the correct RUU?
schmeggy929 said:
RUU any method does not relock bootloader, you have to manually do it in fastboot. Download mode, CMD type fastboot oem lock
---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------
Are you flashing the correct RUU?
Click to expand...
Click to collapse
Yes I have tried the command of fastboot oem lock and it tells me failed unknown command.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
mr573162 said:
Yes I have tried the command of fastboot oem lock and it tells me failed unknown command.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
Click to expand...
Click to collapse
You really doing it in download mode, or are you in bootloader?!
Sent from my htc_pmeuhl using XDA Labs
Hi folks,
I just received my Essential Phone, purchased through amazon. As you recall, the Essential Phone was rumored to have an unlocked bootloader. This was confirmed by @essential confirming that it will, in a tweet.
However, this is not what I'm experiencing with the phone.
After powering it up and playing around a bit, I enabled USB debugging and linked it to my computer, where I have the latest (as of today) android platform tools installed. I rebooted to fastboot and tried to issue "fastboot oem unlock", as I did with my previous phone, a nexus 6p. However, it seems "oem" is no longer a valid subcommand of fastboot; it has been renamed to "flashing unlock", along with some other new-to-me commands:
Code:
$ fastboot --help
usage: fastboot [ <option> ] <command>
commands:
.....
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
The "flashing unlock" command looks interesting. Let's try that:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
Hmmm... I don't like the look of that. Well, let's see what "get_unlock_ability" says:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Ok, that looks bad too. Let's try those other new commands and see if we can get anywhere...
Code:
$ fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s
Nope.
Code:
$ fastboot flashing get_unlock_bootloader_nonce
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Double nope.
Well that's not encouraging. I don't claim to be any sort of expert in regards to unlocking phones, but I can't find any other methods using these tools, and Essential's docs aren't any help. I've contact their phone support but haven't heard back after about an hour. (They use some ridiculous system where you schedule a callback... Not happy.)
So, I'm feeling pretty upset. Let's be clear here:
Essential said this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But shipped a product with this:
Code:
$ fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
finished. total time: 0.000s
Did you turn on the allow unlocking toggle in developer options?
tw1tch175 said:
Did you turn on the allow unlocking toggle in developer options?
Click to expand...
Click to collapse
Thanks, that did the trick
xMopx said:
Thanks, that did the trick
Click to expand...
Click to collapse
So ...wich are the right steps and command d to unlock the bootloader?
thx
mastercut said:
So ...wich are the right steps and command d to unlock the bootloader?
thx
Click to expand...
Click to collapse
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
frhoward said:
1) Check the box next to OEM Unlockable.
2) Then reboot your phone to fastboot
3) In a command prompt within the adb folder: type -> fastboot flashing unlock
4) Use the volume button to click yes when prompted.
Cheers
Click to expand...
Click to collapse
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
DenverDroid said:
I've tried all of these steps and once I get to the fastboot flashing unlock step my cmd prompt just hangs at waiting for device and I never get the option for "Yes." Instead I have Start, Recovery, Power off, etc.
What am I doing wrong?
Click to expand...
Click to collapse
First in fastboot type "fastboot devices" if a string of numbers answers it is ok otherwise you need fastboot driver ....have you cheked?
Hi guys, I have an issue with unlocking the bootloader. fastboot devices returns the device ID, but flashing unlock gives me failed, unknown command error. I cannot get it working. Any ideas?
/edit: changing PC's helped
Essential Phone stuck in Start up screen with Locked Bootloader
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
[email protected] said:
My Essential Phone is frozen at boot up screen while trying to Update the latest Android P Beta 3 ... I restarted the phone on promoting to do so after downloading the update and now I'm here stuck with boot up screen.
Boot loader: Locked
Please let me know if there is a way around this to get it back up !!
Pleaseeeee....
Thanks in advance!!
Click to expand...
Click to collapse
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
wrecklesswun said:
If you've already waited for some time to pass, i would let it go dead, then plugin and allow it to power up on its own. I've only had limited success with this though. Other options are goto into recovery mode and factory reset.
Click to expand...
Click to collapse
Yeah, I had such instances too in the past. But no luck this time...
My OEM locking is not switched on and I'm unable to sideload the OTA or Rest the phone to factory.
Hi i've done something stupid, i've blocked bootloader idk why, anyway im in LineageOs 16, but now i can't back to stock or flash something else ¿i cant re-unlock bootloader?
What is the error that you're getting?
Fastboot flash bootloader permission denied
elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
weazie said:
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
Click to expand...
Click to collapse
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
Did you find any solution?
Same problem!
Works for me!
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
First, install gnirehtet for reverse tethering internet with usb and pc
https://github.com/Genymobile/gnirehtet
Then you will see that you can enable OEM
I'm still not able to unlock oem in settings. I have WIFI on and did all the updates to the latest
elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Same error here. Did anyone find a solution?
Constantinologia said:
Same error here. Did anyone find a solution?
Click to expand...
Click to collapse
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
mrsiri said:
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
Click to expand...
Click to collapse
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Constantinologia said:
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
View attachment 5251849 View attachment 5251851
Click to expand...
Click to collapse
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
mrsiri said:
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
Click to expand...
Click to collapse
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Constantinologia said:
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Click to expand...
Click to collapse
I don't remember the steps to reproduce, but I remember being possible to take the very own boot.img currently flash on your phone. I think it was through adb commands, what if you try booting that one instead? That's what I did on mine, but it didn't help with toggling oem unlock, only entering the system
I accidentally locked mine and im in the same situation as everyone here, but i think the only solution is BlankFlashing or sideloading a signed OTA on it... Im trying everyday new possible methods of fixing it and if i get into some ill share here
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good Luck
thehulk1969 said:
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good LuckView attachment 5274327
Click to expand...
Click to collapse
It would be the solution if the stock was corrupted, but i have locked mine on StyxOS, and there isn't any boot.img for it so stock boot.img gives a system corrupted error. But nice idea.
Edit: Does it need to match the ro.fingerprint on getvar all? only tested with latest pie, so
Good afternoon guys, sorry my english
My Mi A1 appeared this photo error below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
it is blocked and does not have root.
I used Miflash with the last room but it did not work.
I tried to make a wipe but without success.
I tried unlocking the bootloader, it also was not, I need the oem function unlocked in android.
I used the EDL mode with the latest rom version, it does all the worry, but it does not replace anything.
any help is valid.
Thank you.
Can you boot to the recovery?
Yes I can enter, but this error appears above, I can not do wipe.
Did you find any solution... I am also facing the same issue...
Flash stock recovery from fastboot on both slots. See what happen.
bandity said:
Good afternoon guys, sorry my english
My Mi A1 appeared this photo error below.
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
it is blocked and does not have root.
I used Miflash with the last room but it did not work.
I tried to make a wipe but without success.
I tried unlocking the bootloader, it also was not, I need the oem function unlocked in android.
I used the EDL mode with the latest rom version, it does all the worry, but it does not replace anything.
any help is valid.
Thank you.
Click to expand...
Click to collapse
Hi i also have this problem.. my phone have this bootloop. I tried to fix by repairing ES in miracle tool but nothing happen. I tried fastboot via cmd by unlocking the bootloader but still the same. it just restarted the phone and still in MI Logo stuck.
i try to reset it, but it says
API 3:
E: Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
i try miracle tool to unlock oem it says
Code:
oem unlock
Reading info..
Auto detection Enabled..
Found: MSM8953
serial: 0xd33a613d
hw id: 0x000460e1
but still nothing happen.
it just rebooted the phone at the same state. i also tried using fastboot unlock bootloader in cmd. just the same.
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.064s]
finished. total time: 0.064s
i tried using mi flash the it saying " the device is locked"
i tried mi unlock it says " cant get info to the phone"
Last chance i tried flashing EDL Mode using 2 pins to detect Qualcomm USB
But still nothing happens. please help.
my phone still in bootloop and i can only access recovery mode and fastboot.
Please help anyone??please..
Same thing happened to me yesterday, the device just freezed and now it doesn't boot.
I tried to do a factory reset via stock recovery but it stuck at formating /data.
I think the memory is dead
same with my phone iots freezed and then cat load, I am in stuck at formating/data