Database Info

Stuck on Unlocking Bootloader screen - Alcatel Pixi 4

Hey all,
So Ive tried to unlock my bootloader but its not working, ive followed the steps from this site to unlock it but its stuck on the unlock bootloader screen. I have two options to choose from yes or no I click yes but it doesnt work, yet I click no and it takes me back to choose from fastboot, recovery and normal. My phone is a Alcatel Pixi 4.
I have enabled developer mode enabled usb debugging. I also have confirmed the RSA fingerprint for the computer. Also I have enabled OEM unlock in dev settings. This is what my cmd prompt window loooks like. I will also take a photo of my alcatel frozen on bootloader screen.
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
5HQGTCEQCAVS7TTS device
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootloader
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
...
This is what my phone looks like that im stuck on.
https://s11.postimg.org/8e2cjxooj/IMG_20161129_172555.jpg
does anyone know why this is happening or know how to fix?

Also when I reboot my phone it takes me through the setup like I've reset my phone back to factory settings.

I've researched and found out the reason its stuck is because the bootloader is locked.

TA-1020 Bootloader Won't Unlock.

I have used all of my knowledge with past android phones yet to no avail. Every time I issue the command "Fastboot oem unlock", the bootloader returns an error on the phone claiming "Unlock failed... rebooting to fastboot in 3s" and my command prompt returns "FAILED: Error 0x7000". I do not understand as OEM Unlock is enabled, and so is USB debugging. Help would go a long way.
EDIT: Silly me, I forgot that I got this on EE contact. It's sim locked ?

Maybe cause of encryption on 7.0?
Sent from my TA-1032 using Tapatalk

Nikola Jovanovic said:
Maybe cause of encryption on 7.0?
Sent from my TA-1032 using Tapatalk
Click to expand...
Click to collapse
encryption shouldn't be an issue. I've dealt with multiple android N devices and the bootloader unlocks were simple and sweet.
Your reply to my question doesn't answer, except widen the issue.
If it's a matter of encryption, then how do I remove such?

Same issue here!! Any idea?

Still waiting for someone to reply or give a useful answer....

I was under the impression the bootloader was locked by Nokia.

Did you fail to read the post? It's locked.

retr0gr4d3 said:
I have used all of my knowledge with past android phones yet to no avail. Every time I issue the command "Fastboot oem unlock", the bootloader returns an error on the phone claiming "Unlock failed... rebooting to fastboot in 3s" and my command prompt returns "FAILED: Error 0x7000". I do not understand as OEM Unlock is enabled, and so is USB debugging. Help would go a long way.
EDIT: Silly me, I forgot that I got this on EE contact. It's sim locked ?
Click to expand...
Click to collapse
Same happened to me, maybe try to factory reset the phone and then try again.
And my sim is unlocked but still doesn't work.

SkaboXD said:
Same happened to me, maybe try to factory reset the phone and then try again.
And my sim is unlocked but still doesn't work.
Click to expand...
Click to collapse
Fastboot Oem Unlock seems to require an unlock key following this code. Perhaps, maybe a mix or sum.

Hi Guys,
To unlock the access to bootloader on my Nokia 3 I had to plug the charger or have above 70/80% BAT. Activate developer options, go in there and tick the "OEM Unlocking", shutdown the phone. Press Vol Down and Power Button until you see a post message counting some seconds, keep the buttons down ALL THE TIME until you see the bootloader.
Hope it goes well for you too
Glad to help

Johker said:
Hi Guys,
To unlock the access to bootloader on my Nokia 3 I had to plug the charger or have above 70/80% BAT. Activate developer options, go in there and tick the "OEM Unlocking", shutdown the phone. Press Vol Down and Power Button until you see a post message counting some seconds, keep the buttons down ALL THE TIME until you see the bootloader.
Hope it goes well for you too
Glad to help
Click to expand...
Click to collapse
This is false, as the phone just continues to boot after the countdown. Don't try it people, it's a waste of time

retr0gr4d3 said:
This is false, as the phone just continues to boot after the countdown. Don't try it people, it's a waste of time
Click to expand...
Click to collapse
maybe try with miracle box, there is a option to unlock bootloader

SkaboXD said:
maybe try with miracle box, there is a option to unlock bootloader
Click to expand...
Click to collapse
I hadn't even thought of this, I will give it a try asap. Thanks for the suggestion

retr0gr4d3 said:
I hadn't even thought of this, I will give it a try asap. Thanks for the suggestion
Click to expand...
Click to collapse
Download miracle with loader https://forum.hovatek.com/thread-15700.html

SkaboXD said:
Download miracle with loader https://forum.hovatek.com/thread-15700.html
Click to expand...
Click to collapse
Already downloaded and on it ? giving it a try when it's set up

SkaboXD said:
Download miracle with loader https://forum.hovatek.com/thread-15700.html
Click to expand...
Click to collapse
Didn't work ?

retr0gr4d3 said:
Didn't work ?
Click to expand...
Click to collapse
sorry about that, ask @the_laser for help, he unlocked bootloader, just send him imei and serial number and he will give you a key. I tried and it worked.

SkaboXD said:
sorry about that, ask @the_laser for help, he unlocked bootloader, just send him imei and serial number and he will give you a key. I tried and it worked.
Click to expand...
Click to collapse
Ahhhh, I've got a code from him but every time I enter it my adb hangs at <Waiting for Device>

retr0gr4d3 said:
Ahhhh, I've got a code from him but every time I enter it my adb hangs at <Waiting for Device>
Click to expand...
Click to collapse
did you enabled usb debugging and allowed it on your computer?

SkaboXD said:
did you enabled usb debugging and allowed it on your computer?
Click to expand...
Click to collapse
Yeah that all works and the recovery works and all the adb commands work, but issuing OEM key (***) just makes it permanently wait. I've tried on Mac and 2 Windows, it doesn't change. Any chance you can inform me on your setup of adb (drivers used, etc)

Question OEM Unlock greyed out and device not found in fastboot

I'm trying to unlock bootloader, but OEM Unlock option is greyed out.
Device can enter fastboot but doesn't respond to any commands. For example "fastboot devices" do nothing. Using same computer, fastboot commands work fine with another device.
Any solutions? thanks

Windoors said:
I'm trying to unlock bootloader, but OEM Unlock option is greyed out.
Device can enter fastboot but doesn't respond to any commands. For example "fastboot devices" do nothing. Using same computer, fastboot commands work fine with another device.
Any solutions? thanks
Click to expand...
Click to collapse
Try removing the sim card, or putting another carriers card in there. I seem to remember this popping up before

Beetle84 said:
Try removing the sim card, or putting another carriers card in there. I seem to remember this popping up before
Click to expand...
Click to collapse
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?

Windoors said:
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?
Click to expand...
Click to collapse
Help with unlock OEM no work
Is off and dont put on, say Conect to Internet or call you carrier. Any help please... thanx
forum.xda-developers.com
Have a read of this thread

Windoors said:
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?
Click to expand...
Click to collapse
Also try installing tinyfastboot from the lineage or evo rom threads. Select the recommended moto drivers, fastboot should be fine afterwards.

Fastboot working after installing drivers from: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/

Bootloader Unlock Help

Have tmobile oneplus 8 and when trying to unlock with the cust-unlock command it gives me an error as shown in the image attached. made sure that the oem unlocking switch is enabled in the settings

This only happens when you didn't enable OEM unlocking, I know you said you did, but I'd double check. Boot the phone up, go to Settings -> About phone and tap "build number" a bunch of times til the message pops up.
Than go to Settings -> System -> Developer options and enable OEM Unlocking.
Then repeat the same steps in fastboot to unlock.

Restarted my phone turned it off. Then restarted again and turned it on. And still no luck

FoxyDrew said:
This only happens when you didn't enable OEM unlocking, I know you said you did, but I'd double check. Boot the phone up, go to Settings -> About phone and tap "build number" a bunch of times til the message pops up.
Than go to Settings -> System -> Developer options and enable OEM Unlocking.
Then repeat the same steps in fastboot to unlock.
Click to expand...
Click to collapse
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck

Snekxs said:
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
Click to expand...
Click to collapse
Are you on stock T-Mo firmware, and have taken all OTA updates? I saw you said in another thread that after using MSM tool "the software update button is greyed out in the settings". If that's still the case...well it shouldn't be lol. I would MSM again back to OOS10, than immedietly try booting the phone up enabling OEM unlocking and try to unlock the bootloader again.

FoxyDrew said:
Are you on stock T-Mo firmware, and have taken all OTA updates? I saw you said in another thread that after using MSM tool "the software update button is greyed out in the settings". If that's still the case...well it shouldn't be lol. I would MSM again back to OOS10, than immedietly try booting the phone up enabling OEM unlocking and try to unlock the bootloader again.
Click to expand...
Click to collapse
Yeah. The button was greyed out but my phone still installed an update. Gonna try to use msm again and see

Curious if you found a solution to this one? Been fighting a similar situation, not the MSM tool just but the unwillingness to let me run the unlock bin token.

Problem with installing a custom recovery (custom binary blocked by OEM lock)

I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​

You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.

Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine

I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse

It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...

Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com

wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.

so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion

DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked

Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.

Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!

geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!