Related
Hi, I've got the 6045Y model which I've been trying to install twrp on, but I can't unlock the bootloader; it says oem unlock is not allowed.
I've tried on os x and linux with sudo but it's the same on both sides. As my phone isn't carrier locked, I don't understand why it's not allowing me to unlock the bootloader. There's also no oem unlock option in the developer options.
Any help?
You must do something wrong?
Can you trY with Windows
You need Alcatel Drivers+Minimal Adb and Fastboot
connect device you must enable debugging and then
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
Alek Dev said:
You must do something wrong?
Can you trY with Windows
You need Alcatel Drivers+Minimal Adb and Fastboot
connect device you must enable debugging and then
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
Click to expand...
Click to collapse
I tried on windows just now and the same thing happened: "FAILED (remote: oem unlock is not allowed)". I should mention though, I flashed twrp before unlocking the bootloader. I wonder if this is what's causing the problem.
I dont remember if this option was there, but you can try. Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
DallasCZ said:
I dont remember if this option was there, but you can try. Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
aradalien said:
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
Click to expand...
Click to collapse
same here in the uk have same version and cannot unlock bootloader anyone been sucssesful
aradalien said:
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
Click to expand...
Click to collapse
Same problem with same UK model and installed that patch too. I managed to flash TWRP and install PAC ROM still bootloader claims to be locked.
fastboot -i 0x1bbb oem unlock
FAILED (remote: oem unlock is not allowed)
fastboot -i 0x1bbb oem device-info
(bootloader) Device tempered:false
(bootloader) Device Unlock:false
easiest way is to download stock firmware with flsh tool for panasonic eluga switch (rebranded idol3),. Flash it with using the included flash tool. then unlock bootloader. Then use mobile upgrade Q 5.0.6 to go back to stock. And you are on stock uk firmware with unlocked bootloader.
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Reippi said:
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Click to expand...
Click to collapse
the Panasonic firmware flash also the aboot partition which has bootloader unlock enabled. without unlocked bootloader you could end with bricked device and the only solution is mobile upgrade q.
I did as you said and finally got bootloader unlocked, yey! Hopefully I don't have to go thought that process anytime soon. Thanks and thumps up!
Reippi said:
I did as you said and finally got bootloader unlocked, yey! Hopefully I don't have to go thought that process anytime soon. Thanks and thumps up!
Click to expand...
Click to collapse
no, its permanent.
I try to unlock my bootloader but two problems : oem unlock is not allowed and eluga sotware stuck at 2 %!!! I want install MM and I have stock rom can install the same the MM upgrade without unlock the bootloader? Regards
camelotto said:
I try to unlock my bootloader but two problems : oem unlock is not allowed and eluga sotware stuck at 2 %!!! I want install MM and I have stock rom can install the same the MM upgrade without unlock the bootloader? Regards
Click to expand...
Click to collapse
1-You didnt wrote phch model do you have.
2-newer heard of this issue . Install the drivers from the eluga firmware app, reboot, turn off your device, connect device to computer, run the download form the eluga firmware app.
jlocohustler said:
I tried on windows just now and the same thing happened: "FAILED (remote: oem unlock is not allowed)". I should mention though, I flashed twrp before unlocking the bootloader. I wonder if this is what's causing the problem.
Click to expand...
Click to collapse
And do you have sucess in flash? It worked? Do you have TWRP????
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Reippi said:
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Click to expand...
Click to collapse
That is the point from my previouse question! If you flash TWRP, your bootloader is unlocked by default!
persona78 said:
And do you have sucess in flash? It worked? Do you have TWRP????
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
That is the point from my previouse question! If you flash TWRP, your bootloader is unlocked by default!
Click to expand...
Click to collapse
After flashing panasonic rom, you have unlockable bootloader.
Look here
http://forum.xda-developers.com/idol-3/general/guide-repair-idol-3-t3372076
I have 6045Y and panasonic rom work!
fastboot is detecting device but oem unlock/flashing unlock command not working.
I think that command has been changed since this june month security patch.
yash_rathore25 said:
fastboot is detecting device but oem unlock/flashing unlock command not working.
I think that command has been changed since this june month security patch.
Click to expand...
Click to collapse
It looks like MM update dont include aboot with commands for unlocking bootloader. You have to use mobile upgrade Q PC aPP, or Panasonic eluga firmware flash tool (for 6045Y) to go back to 5.0.2. Then unlock bootloader, and flash update to MM (or when on panasonic firmware youhave to use mobile upgrade Q to go back to stock). When on stock, wat for OTA MM or flash MM from XDA thread.
DallasCZ said:
It looks like MM update dont include aboot with commands for unlocking bootloader. You have to use mobile upgrade Q PC aPP, or Panasonic eluga firmware flash tool (for 6045Y) to go back to 5.0.2. Then unlock bootloader, and flash update to MM (or when on panasonic firmware youhave to use mobile upgrade Q to go back to stock). When on stock, wat for OTA MM or flash MM from XDA thread.
Click to expand...
Click to collapse
but fastboot flash command is working and also sending data to phone but unable to write on phone as bootloader is locked
yash_rathore25 said:
but fastboot flash command is working and also sending data to phone but unable to write on phone as bootloader is locked
Click to expand...
Click to collapse
because they have erased this command/s from aboot partition (bootloader)
I used the mtk-su and instantly achieved a root with permissive selinux in an adb shell. The development on this subject has basically successfully achieved fully working temp root.
I know the Official Application doesn't support our phones and just crash, but is their any "modifications" I can do with root privileges to cause it to work?
THANKS!
Hello, i'm sorry but i'm afraid to tell you i've got the solution !
Tested on nokia 3.1 TA-1063 00WW-00.3.180-SP04
1. grab your serial number
2. generate a md5 hash with your serial number as input text, That is your bootloader unlocking key !
3. reboot into fastboot mode via adb (adb reboot bootloader)
4. make sure your device is detected (fastboot devices)
5. unlock your bootloader (fastboot oem key your-md5-hash) ex: fastboot oem key 5fd3280b7b61e5e31519a3a1788f13f6
6. enjoy !
pitachu sensei said:
Hello, i'm sorry but i'm afraid to tell you i've got the solution !
Tested on nokia 3.1 TA-1063 00WW-00.3.180-SP04
1. grab your serial number
2. generate a md5 hash with your serial number as input text, That is your bootloader unlocking key !
3. reboot into fastboot mode via adb (adb reboot bootloader)
4. make sure your device is detected (fastboot devices)
5. unlock your bootloader (fastboot oem key your-md5-hash) ex: fastboot oem key 5fd3280b7b61e5e31519a3a1788f13f6
6. enjoy !
Click to expand...
Click to collapse
Did you really test it? Because it's not working. Fastboot will respond to "fastboot oem key" with "OKAY", but it responds like this to any key entered. Bootloader remains locked.
I tried using nokia official bootloader unlock method but the unlock app crashes.
sixline said:
I tried using nokia official bootloader unlock method but the unlock app crashes.
Click to expand...
Click to collapse
Because it only works with Nokia 8, confirmed by official support
MilesSeventh said:
Because it only works with Nokia 8, confirmed by official support
Click to expand...
Click to collapse
Thats really bad.
Hello to everyone that read and thanks you for the time passing to read my problem.
First of all : this is not my native language so excuse me for my english ... :/
After that, this is my first thread ... :/
And then , i'm tryin to learn but i'm pretty newbie on computing ... :/
(i'm trying to root my phone like every newbie does first by following slowly and accurately this tutorial: https://www.getdroidtips.com/root-wiko-view-3-lite/
i'm gonna details all i did step by step but at the end cause i don't think that the problem come from here)
so after etablishing the connection between my device and the PC using a wiko usb driver
i tried to flash my Wiko View 3 Lite ROM to boot the patched "boot.img" via Minimal ADB and Fastboot V1.4.3 (latest version)
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
( that's what i did:
1/ i've downloaded magisk.apk's last vertion on my phone
2/ found a Wiko View 3 Lite full ROM online for the rom.pac file
3/ converted it w the SPD flash tool (i didn't really understood this step :/) : https://www.getdroidtips.com/patch-boot-img-root-spreadtrum-device/
4/ sent it to my phone
5/converted it agan via magisk.apk on my phone
6/ took it back from my computer to the same folder that i launch the ADB and fastboot comand prompt
7/last step normally :/ i should write the command: fastboot flash boot xxxxxxxxx.img and i gotstuck here ....
)
thanks again for all your help guys ))
Hakodu13 said:
...
so once i enter the command : fastboot flash boot "MyPatchedBootFile".img
i got a :
Failed.(flashing lock flag is locked. Please unlock it first!)
so i should able the flashing option somehow somewere ?
i tried several fastboot command but nothing... (btw i is there a way to kow all the comandes i can do on my PC cause i see the command changing depending phones or fastboot )
that's what i have :
FAILED (remote :Not implemet.)
i'm not sure to understand what "no implemet" mean ??
I can't find any useful info exept this one unfortunately that could be the same for my phone's model :
Rooting a wiko jerry is impossible due to all fastboot commands lock the phone
On Linux: All fastboot commands lock. Particularly fastboot oem unlock or fastboot flashing unlock. After removing and re-attaching the phone to the usb port (without turning it off), the phone bec...
android.stackexchange.com
i'm continuing to look for anwsers, can someone have an idea ??
...
Click to expand...
Click to collapse
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
jwoegerbauer said:
Before trying to deal with phone's bootloader, will say running any Fastboot commands, you have to enable "OEM unlock" option in phone's Android Settings->Developer option. If done so, reboot phone. Afterwards run Fastboot commands
Code:
fastboot devices
fastboot oem unlock <- or: fastboot flashing unlock
Click to expand...
Click to collapse
Hey
Thanks for your awnser,
i did it already, i've activated EOM unlock , USB debug and also desactivated the standby when the phone is plugged
also i think all fastboot command work cause i can reboot my phone using "fastboot reboot"command
fastboot devices reconize my phone
fastboot flashing unlock dosn't work
it is writed: FAILED (remote: Not implemet.)
fastboot oem unlock dosn't work,
it is writed: FAILED (remote: unknown cmd.)
something interesting is when i write fastboot "AnithingElse" unlock
it says: fastboot: usage: unknown command "AnithingElse"
and no: FAILED (remote: unknown cmd.)
like if adbandfastboot know the commannd " fastboot oem unlock " somehow but not my phone.
thanksthanksthanks again for your awnser!!!
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
jwoegerbauer said:
My guess is that running Fastboot commands is denied by OEM/Carrier. And that's not wondering me because phone is based on UniSoc chipset.
AFAIK to get Fastboot working on such phones you have to request from OEM/Carrier the unlock-code as 1st thing of all things and when received have to flash it to phone.
Click to expand...
Click to collapse
Ye i guessed the commands is denied on purpose
but why ? just for me not to have root acces ?
and what if i want to flash or reflash my ROM just to have back a new fresh boot ?
do a lot of phone constructor use that radical trick ?
and what is OEM/Carrier ? where can i find this ? i can't find anything online ...
merci ))
OEM is an acronym and stands for Original Equipment Manufacturer ( e.g Samsung )
Carrier is the is cell phone company that provide cellular service to cell phone users ( e.g. AT&T, Verizon )
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
theandies said:
I posted this in the appropriate forum but this phone is so old I've not received any response.
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help. Even installed everything in the root directory on my hard drive - no help
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone before. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Things I have not tried yet:
Another computer
Tested fastboot command on one of my other phones
Any help is appreciated.
Click to expand...
Click to collapse
The process to unlock a moto phone is a bit different. OEM commands are as it says, defined by the OEM. They need to be precise and functional. The command:
Code:
fastboot oem unlock
alone will not work.
Step1:
Instead, You should enter:
Code:
fastboot oem get_unlock_data
You will get an unique 131 ID string that looks for example like this:
Code:
(bootloader) 0000000000000000000000000000001
(bootloader) 0000000000000000000000000000002
(bootloader) 0000000000000000000000000000003
(bootloader) 0000000000000000000000000000004
(bootloader) 0000005
Copy the output to a text editor and delete the (bootloader) and the spaces in between, so it's one whole string.
Step2:
Visit the official Moto unlock website. Sign-in with your account, you will be using the E-mail used to create said account to receive the unlock key. Paste the edited 131 ID string and click Can my device be unlocked? button. If it is unlockable, then a conformation page will appear asking for consent and warranty bla bla bla.... Just read it and accept.
Step3:
When you click unlock, you will receive a KEY through your E-mail attached to the moto account used. Save that E-mail somewhere offline, as it can be used to re-unlock the bootloader in the future if you relock it. Connect your device in fastboot again and type:
Code:
fastboot oem unlock KEY
Where KEY is the one you got in the E-mail.
Done!!! Enjoy your freedom , also check the mark near my answer if it solved your question so others don't have to search for long.
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
theandies said:
Thanks for your reply. Yes I wrote the fastboot command wrong in my post.
The problem I'm having is even when using the fastboot command you posted I still get "access denied" when using fastboot commands. ADB works fine allowing me to reboot into the bootloader through the command prompt/USB as in ADB devices.
Click to expand...
Click to collapse
As long as in Android -> Settings -> Developer options the option "OEM unlock" isn't got enabled - and phone got rebooted afterwards - you receive the reported error.
OEM unlocking is turned on in developer settings
I'll post up some screenshots soon. Right now I'm on day three of work on the 12 hour night shift.
Hi, i am loading booting to bootloader from adb with commnad (adb reboot bootloader) this isnt working, only restart its instantly switch to normal os, any ideas ?
Run
Code:
adb reboot
or
Code:
fastboot reboot
oh sorry man, i am idiot, and i am say it wrong.. I trying boot to fastboot but not working instantly switch to os, any ideas please ?
Unlock bootloader if not done yet.
where i unlock bootloader ? In developer settings ? (i have unlocked)
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
xXx yYy said:
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
Click to expand...
Click to collapse
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Matyas66055 said:
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Click to expand...
Click to collapse
I have new thread, where i am writing all info :/ https://forum.xda-developers.com/t/zte-blade-a7-2019-fastboot-mode-missing.4462035/
I don't know if you are still interested in accessing Fastboot but you can access it using a specific firmware version.
Still, let me tell you that unlocking the bootloader is virtually impossible. Since the well-known generic method doesn't work for the SoC SC9863A, you need to have a special Fastboot's program version and a dedicated private key that only they provide.... and I emphasize the word "dedicated" since apparently ZTE did not use a generic key to sign their ROMS. At least on this device.
Unless they decide to release the key or give support to unlocking the bootloader, all we can do is wait for them to change their minds. Because they don't want to provide it. I know because I tried to order it several times.