• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Cant unlock bootloader using ADB

D

dan198969

Newbie
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/IM...129_172555.jpg

does anyone know why this is happening or know how to fix?
 
Welcome to our AndroidForums, Dan :).

Which site's instructions are you referring to? (I don't see a link listed...)

When you say "click yes", do you mean that you were pressing the Volume UP rocker to unlock the device?

Also, is it possible that your device supports the new "fastboot flashing unlock" instead of "fastboot oem unlock"?

By the way, we've seen issues like this for some random Nexus 7 tablets--never really did figure-out what was going on there, I'm afraid.

I'm not at all familiar with Alcatel devices, so the above is just based on experience with other devices...
 
scary alien said:
Welcome to our AndroidForums, Dan :).

Which site's instructions are you referring to? (I don't see a link listed...)

When you say "click yes", do you mean that you were pressing the Volume UP rocker to unlock the device?

Also, is it possible that your device supports the new "fastboot flashing unlock" instead of "fastboot oem unlock"?

By the way, we've seen issues like this for some random Nexus 7 tablets--never really did figure-out what was going on there, I'm afraid.

I'm not at all familiar with Alcatel devices, so the above is just based on experience with other devices...
Click to expand...

Hey Thanks and thanks for your reply sorry forgot to add the link to the instructions that I followed http://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597/page19

and yes I select volume up and nothing happens, yet when I press volume down it works perfectly fine, also the volume up key as been tested and it works perfectly fine so I really dont know why its not allowing me to unlock the bootloader.

I also thought this was the case but when I do that it says the command doesnt exist and gives me a bunch of commands that can be used. I tried fastboot flashing unlock and says the cmd isnt valid. the only command it will see is the fastboot oem unlock.

When you said you heard of issues on the nexus 7 tablets is it the same story or different issue?
 
Yeah, your issue does some similar to several Nexus 7 threads (and maybe one Nexus 5 threads) we've seen over the years: inexplicable inability to get the bootloader to unlock despite following the proper, proscribed instructions.

I can't view the XDA thread at the moment--the page doesn't resolve well here at work--but I'll view it when I get home this evening.

Not sure what else to tell you other than hopefully someone else might chime-in.
 
I wonder if you need to press the power button after using the volume up (to highlight yes) as a sort of verification that you truly want to proceed. If you're already doing that or have tried that then disregard.
 
yeh im lost hints why ive resorted to online help, unfortunately iowabowtech it doesnt highlight any option its just a simple if you want to unlock the bootloader press volume up if not press volume down when I press volume down im taken to a different screen straight away, yet when I press volume up its like the phone is ignoring the command for some reason weird.

is there some sort of special forum I can post on that specialises with this tool? Ive tried posting in XDA but its a dead forum sadly.
 
dan198969 said:
yeh im lost hints why ive resorted to online help, unfortunately iowabowtech it doesnt highlight any option its just a simple if you want to unlock the bootloader press volume up if not press volume down when I press volume down im taken to a different screen straight away, yet when I press volume up its like the phone is ignoring the command for some reason weird.

is there some sort of special forum I can post on that specialises with this tool? Ive tried posting in XDA but its a dead forum sadly.
Click to expand...

kirito9 is one of the kindest, most helpful Developers I have ever worked with at XDA. Go ahead and ask your question in his thread. Tag his name and tell him I sent you.

Edit: You mentioned that the thread was dead but there was activity from the OP yesterday. He always tries to help.
 
Last edited:
Good advice there, @Bg260....I've not really seen or been exposed to too many Alcatel device rooting (or otherwise) threads over the years here, so hopefully you can re-kindle the fires with that dev over at XDA.

Best of luck!
 
These are Media-Tek devices. So things are a little different. I chatted with kirito9, we are both a little befuddled. ONLY DO THIS IF YOU CAN AFFORD TO BREAK THIS DEVICE His suggestion, if you are willing would be to use Flashify. Be sure to back up the stock recovery first. I think this can be done with the app. If not than you will need to find out which block the recovery partition is mounted on. You can invoke the "dd" command and create a recovery.img. It is important to do this. Then use the app to flash TWRP. When done open a terminal and reboot recovery. If it worked you will be in TWRP. If it didn't work the device will most likely just boot back into Android. If this happens use Flashify to flash the stock recovery.img that you made.. I have done it myself on an Alcatel with a broken charging port.
He noted that there is a debrick available if something goes wrong.
 
Last edited:
Hey, I spoke to Kirito9 from xda he said hes gonna look into it for me.

Its just extremely weird how the fastboot command works yet it wont unlock the bootloader really bizzare.

I will definately look into flashify tomorrow at some stage thanks for suggestion greatly appreciate it.
 
dan198969 said:
Hey, I spoke to Kirito9 from xda he said hes gonna look into it for me.

Its just extremely weird how the fastboot command works yet it wont unlock the bootloader really bizzare.

I will definately look into flashify tomorrow at some stage thanks for suggestion greatly appreciate it.
Click to expand...

Good deal. The Alcatel community over there is outstanding. I had an Elevate which is a piece of crap, but the helpful folks made it seem not so.......crappy. Im looking to buy another Alcatel if the price is right. Just for the learning experience.
kirito9 and a few others have drastically changed my opinions of XDA. There is still plenty of help to be found there. You just have to know where to look.
Good luck.
 
dan198969 said:
Hey, I spoke to Kirito9 from xda he said hes gonna look into it for me.

Its just extremely weird how the fastboot command works yet it wont unlock the bootloader really bizzare.

I will definately look into flashify tomorrow at some stage thanks for suggestion greatly appreciate it.
Click to expand...

Hey, I'm here as well :p. Did you try the MUS tool I told you about...did you forget to reply? :). I was also thinking it may be a bug in the device....hardware/software?

While in fastboot mode, run this command "fastboot getvar all" and tell me what you get. You should see something like this. Look specifically at these two "(bootloader) unlocked: yes | (bootloader) secure: no"
Code: 
kirito9@kirito9:~$ fastboot getvar all
(bootloader)     max-download-size: 0x8000000
(bootloader)     partition-size:userdata: 32000000
(bootloader)     partition-type:userdata: ext4
(bootloader)     partition-size:cache: 10000000
(bootloader)     partition-type:cache: ext4
(bootloader)     partition-size:system: 65000000
(bootloader)     partition-type:system: ext4
(bootloader)     partition-size:metadata: 2000000
(bootloader)     partition-type:metadata: raw data
(bootloader)     partition-size:nvdata: 2000000
(bootloader)     partition-type:nvdata: ext4
(bootloader)     partition-size:frp: 800000
(bootloader)     partition-type:frp: raw data
(bootloader)     partition-size:expdb: 1000000
(bootloader)     partition-type:expdb: raw data
(bootloader)     partition-size:logo: 800000
(bootloader)     partition-type:logo: raw data
(bootloader)     partition-size:para: 80000
(bootloader)     partition-type:para: raw data
(bootloader)     partition-size:keystore: 800000
(bootloader)     partition-type:keystore: raw data
(bootloader)     partition-size:secro: 800000
(bootloader)     partition-type:secro: raw data
(bootloader)     partition-size:oemkeystore: 800000
(bootloader)     partition-type:oemkeystore: raw data
(bootloader)     partition-size:recovery: 1000000
(bootloader)     partition-type:recovery: raw data
(bootloader)     partition-size:boot: 1000000
(bootloader)     partition-type:boot: raw data
(bootloader)     partition-size:lk: 800000
(bootloader)     partition-type:lk: raw data
(bootloader)     partition-size:seccfg: 800000
(bootloader)     partition-type:seccfg: raw data
(bootloader)     partition-size:protect2: a00000
(bootloader)     partition-type:protect2: ext4
(bootloader)     partition-size:protect1: a00000
(bootloader)     partition-type:protect1: ext4
(bootloader)     partition-size:nvram: 500000
(bootloader)     partition-type:nvram: raw data
(bootloader)     partition-size:proinfo: 680000
(bootloader)     partition-type:proinfo: raw data
(bootloader)     partition-size:preloader: 40000
(bootloader)     partition-type:preloader: raw data
(bootloader)     off-mode-charge: 1
(bootloader)     warranty: no
(bootloader)     unlocked: yes
(bootloader)     secure: no
(bootloader)     kernel: lk
(bootloader)     product: PIXI4_4_8G1G
(bootloader)     version-preloader: 0.1.00
(bootloader)     version: 0.5
all: Done!!
finished. total time: 0.009s
 
@kirito9 Hey, welcome. I thought you might show up. We have a lot of fun here.
We have Sub-Forum for 19 Alcatel devices all of which are badly neglected.

http://androidforums.com/categories/android-phones.3/

I know you're busy but feel free to add what you can. I'd be glad to help in anyway possible. I can look into getting you developer status quickly if you want.
Hopefully the OP will be back to see all this support.
I used to have a saying, "Folks go to XDA and break their phones and then come here to get them fixed"! I think I just spent too much time in a bad and heartless community over there. Anyway. Good to see you.
 
Bg260 said:
@kirito9 Hey, welcome. I thought you might show up. We have a lot of fun here.
We have Sub-Forum for 19 Alcatel devices all of which are badly neglected.

http://androidforums.com/categories/android-phones.3/

I know you're busy but feel free to add what you can. I'd be glad to help in anyway possible. I can look into getting you developer status quickly if you want.
Hopefully the OP will be back to see all this support.
I used to have a saying, "Folks go to XDA and break their phones and then come here to get them fixed"! I think I just spent too much time in a bad and heartless community over there. Anyway. Good to see you.
Click to expand...

Hehe thanks :). I was actually looking to see if I can find more Alcatel devices to help out :). What are the perks of having developer status? :P I wouldn't mind it, thanks. I replied to his PM and solved the problem, his device doesn't need the bootloader unlocked. It's one of those devices with an older MTK chip (mt6572). Yeah maybe you did but I'm glad I found this one :D.
 
Hey guys. thank you all for your on going support and helpful advice I ran that command and it says the bootloader is unlocked, thats soo weird as I cant install supersu on my device or root my device. heres the code listed below.

(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:fat: 2b00000
(bootloader) partition-type:fat: fat
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 8000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 54000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:custom: 800000
(bootloader) partition-type:custom: ext4
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 800000
(bootloader) partition-type:sec_ro: raw data
(bootloader) partition-size:recovery: 600000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 600000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: 1000000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: PIXI4_35
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.184s

Also not sure if I mentioned it but in dev settings theres an option to allow OEM to be unlocked, which ive turned on as previously when trying to unlock the bootloader it said operation not allowed. After researching this I found out that turning on that setting allow oem to be unlocked. it gets me one step closer towards solving the puzzle.

I remember a while ago I got into the phone rooting modding situation never had any issues towards the bootloader at all I was running a Samsung Galaxy S4 rooted and running CM11 with no issues.

I do have another device Ive borrowed from a mate called ZTE blade I will see how I go with unlocking that bootloader just curious as to what the outcome will be.
 
Last edited:
dan198969 said:
Hey guys. thank you all for your on going support and helpful advice I ran that command and it says the bootloader is unlocked, thats soo weird as I cant install supersu on my device or root my device. heres the code listed below.

(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:: 1500000
(bootloader) partition-type:: <null>
(bootloader) partition-size:fat: 2b00000
(bootloader) partition-type:fat: fat
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 8000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 54000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:custom: 800000
(bootloader) partition-type:custom: ext4
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 800000
(bootloader) partition-type:sec_ro: raw data
(bootloader) partition-size:recovery: 600000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 600000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect_s: a00000
(bootloader) partition-type:protect_s: ext4
(bootloader) partition-size:protect_f: a00000
(bootloader) partition-type:protect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:pro_info: 300000
(bootloader) partition-type:pro_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-size:preloader: 1000000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: PIXI4_35
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.184s

Also not sure if I mentioned it but in dev settings theres an option to allow OEM to be unlocked, which ive turned on as previously when trying to unlock the bootloader it said operation not allowed. After researching this I found out that turning on that setting allow oem to be unlocked. it gets me one step closer towards solving the puzzle.

I remember a while ago I got into the phone rooting modding situation never had any issues towards the bootloader at all I was running a Samsung Galaxy S4 rooted and running CM11 with no issues.

I do have another device Ive borrowed from a mate called ZTE blade I will see how I go with unlocking that bootloader just curious as to what the outcome will be.
Click to expand...

How are you trying to root?


@kirito9
Im not sure the perks of Developers status. You get a fancy banner under your avatar and the admiration of the masses. . . .
I'm looking into it.
 
Hey sorry guys for some reason couldnt post on the forums anyway, Ive tried rooting with the one click apps like Kingroot iroot Kramaroot it gets to about 30% and fails.
 
Yep sure have same deal no luck :(

btw this is a little off topic but testing out the zte blade and im stuck on waiting for any device. Ive googled it and people suggest drivers but ive installed drivers and still error. Ive done a backup of my phone and tried to install supersu but got installation aborted, not sure on how to fix this.

This is the original reason why I thought my bootloader was locked on my alcatel device. both devices wont allow me to install supersu in stock recovery both have the same error code.

also curious is a nandroid backup just a general user back up?
 
dan198969 said:
Yep sure have same deal no luck :(

btw this is a little off topic but testing out the zte blade and im stuck on waiting for any device. Ive googled it and people suggest drivers but ive installed drivers and still error. Ive done a backup of my phone and tried to install supersu but got installation aborted, not sure on how to fix this.

This is the original reason why I thought my bootloader was locked on my alcatel device. both devices wont allow me to install supersu in stock recovery both have the same error code.

also curious is a nandroid backup just a general user back up?
Click to expand...

Kingroot should've worked as it worked for another user but I guess all this is possible with different models.

You're trying to install SuperSU on the stock recovery, that's why you're getting this error. Stock recovery only allows signed packages to be installed like say an OTA upgrade that you downloaded. In the past I think there were a few users who have found a way to sign their own zips so that it can be used with stock recovery but for SuperSU, it doesn't work.

Also, you cannot make a nandroid backup with the stock recovery. It only backs up userdata and I'm not even sure if that works, I've never used it. Custom recovery is the way to go (Y).

I'll post the correct method to flash a custom recovery and install SuperSU soon. Have to go to work now :D.
 
Last edited:
Ah that makes sense why everything was failing when installing in stock recovery. As with the rooting situation nothing wants to work, it reboots my device so I go in and unlock it and go back into the app and yeh says it failed ill post some screen grabs.

Thanks for the guide Kirito9 greatly appreciate it ill give it a shot and report back :)

any advice with the blade issue? I downloaded the drivers from this site. http://gsmusbdriver.com/zte-blade downloaded both drivers unfortunately with the adb driver I keep getting code 10 after installing the driver. refer to picture below for details.

https://data2.m4v.me/files/upload/3428021477069600.png
 
Hey all,

Just a quick update the primary issue has been resolved, as Kirito09 has informed us that the bootloader is unlocked by default as this was the primary issue for this thread im happy to close this thread. Im still having issues rooting with Kingroot when I get around to it il make a new thread with the error codes stay tuned.

Thanks again for everyone who replied to my thread greatly appreciated.

Kind Regards,
Dan
 
You must log in or register to reply here.
Back
Top Bottom