I have followed the guides to the best of my ablity
This is the procedure I followed: From this thread
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
FAILED (remote: oem unlock is not allowed)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.100s]
finished. total time: 0.100s
I then tried to downgrade to s19, but does not seem to work.
Anyway, if anyone has any ideas it would be welcomed, thank you
Is there an option you can turn on in dev options called "allow bootloader unlocks"? Because my mom's Le 2 has it and I assume it allows the unlock to go through. Are you on a vendor ROM? Flash the original stock Chinese 18s for your device.
Closest setting like that I have is the "OEM unlock" and I have it enabled
Well, did you have it enabled back when you were trying to unlock it? Because not having it enabled is usually what causes the unlock to fail.
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
I will try this asap, thanks
Woot! that worked
Hey can i lock the bootloaded after I am done? I want to use like android pay and stuff
Well I figured out I can relock it, bit now my issue is when I am in fastboot mode adb does not see the device...
I installed the drivers, did not work....
Even went to my wife's laptop that I have never once plugged my phone in to... Installed adb, and plugged in the phone in fastboot... Still not being seen when I do an "adb devices"
I really want to use android pay
Don't understand
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
bobster82 said:
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure ur files are in the right directory or cd to where they are.
bobster82 said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
You may need to do the XBL as well:
Then
Run
and then
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
You need adb installed on your computer.
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
bobster82 said:
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
Click to expand...
Click to collapse
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
mchlbenner said:
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
bobster82 said:
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
Click to expand...
Click to collapse
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
mchlbenner said:
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
see this the only thing I don't understand. I booted into fastboot and attempted to flash the files eemc and the xl files to unlock bootloader. The first try gave me an error and then the screen went black and has not come back on yet. No vibrations,no lights, no nothing.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
sk8223 said:
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
Click to expand...
Click to collapse
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
bobster82 said:
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
Click to expand...
Click to collapse
Well, I simply rephrased slgooding's post in this thread. See the first page. And by brick, I assume you only have fastboot working.
Try the other commands: https://forum.xda-developers.com/showpost.php?p=74123111&postcount=5
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
bobster82 said:
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
Click to expand...
Click to collapse
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
mchlbenner said:
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hi I made sure I downloaded the correct twrp recovery and when I command in prompt its telling me now that it cannot load the image error. the build is Le_zl1 -eng 6.0.1 WAXCNFN5841510281D eng.letv.
I'm almost fixing to give up cause no matter what I do I cannot get into twrp recovery
Hey community!
first of all: my android knowledge is very limited, but I try my best to formulate my problem!
So, my Huawei p8 lite freezes on the Huawei logo and doesn't let me enter safe mode or anything else than fastboot/recovery mode (if trying volume down and power it just starts on huawei logo and freezes again). I know, that there are some posts on the internet for that topic, however, they all require OEM unlocked. I am pretty sure, that I didn't unlock my OEM in the developer settings and my thesis, that its locked, is confirmed by the 'remote: Command not allowed!' message when I type nearly any fastboot oem command (e.g. fastboot oem getvar all) on my computer. So, my question: Is there any possibility to unlock OEM with my phone just being able to enter fastboot mode?
With OEM unlocked I then hope to be able to unlock my bootloader and recover my phone ... (but thats another topic )
possibly useful information:
- HiSuite is installed on my PC (win10)
- fastboot&adb is 'installed' on my PC
- I can see my phone in 'fastboot devices', but I can't see it in 'adb devices' (it also doesn't appear in device manager if that should be the case ...)
- my bootloader is locked (I can howsoever see that with fastboot oem get-bootinfo)
Looking forward to your answers and thanks a lot in advance!
i am on pie 073 firmware... i want to unlock my bootloader ... all the drivers are installed even my phone is detected both in adb and fastboot mode... but when i run the unlock both normally or running uts as administrator it doesnt work... nor the application of unlockimg boot loader works on my phone
Did you try manually typing the unlock command?
Code:
fastboot oem unlock
I've tried this , but it says
Comman failed
No error...
I also has the same problem
KVCmoto said:
Did you try manually typing the unlock command?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
You need to download the Asus Unlock Tool.
If you still have issues, go to their forum ZenTalk and they can help you. They are very fast.
hi .
i cannot Root Coolpad Cool 1
when enter this command to adb : fastboot oem unlock-go
H:\New folder (3)\A\platform-tools_r30.0.3-windows\platform-tools>adb reboot boo
tloader
error: no devices/emulators found
H:\New folder (3)\A\platform-tools_r30.0.3-windows\platform-tools>
All drives & ADB are installed
No phone detection when fast boot
sorry; cannot speak english ...
This phone doesn't respond to fastboot unlock command.
First you need to enable usb debugging and allow OEM unlock in developer options.
Then you just flash TWRP recovery , by using Qualcomm QPST flash tool.
Once you have TWRP installed , flash Magisk to root the phone.
Search the threads here , there are a few Twrp/rooting guides that you can follow.
Sent from my C103 using XDA Labs
Hello to all gurus here
my Redmi Note 7 had a screen broken...I can only hardy recognize when it's in fastboot or recovery.... Touch not working.
The bootloader is locked, I am not sure if USB Debugging was enabled, but I suppose it was not because I get the following:
C:\MyDocs\TEMP\Varie\platform-tools>fastboot oem unlock
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
In this terrific scenario, is there any way on earth to recover my data?
I can only see my device in fastboot mode for what I can say...
On the other hand I could probably install a TWRP (which should already have debugging enabled) using fastboot but it seems to me it should clear all my user data.
Any way out?
Thanks in advance
unlocking bootloader requires bonded mi account in developer options and can only unlocked from miunlock tool. btw that will erase userdata during unlock for security reasons