Related
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
wimobile246 said:
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
Click to expand...
Click to collapse
Not really sure what it is, but have you tried to launch SDK Manager and update platform-tools and google driver?
wimobile246 said:
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
Click to expand...
Click to collapse
Its likely cause your tablet is booting into the OS and not fastboot...
Use this AIO_scripts_R.A.H._TWRPv2.6.3.zip - 12.00 MB
Ive created that for installing twrp recovery but also included tools to unlock your boot loader.
under the windows folder and click the runme.bat and simply folliw the prompts for what you want to do...cant get any easier.
Sent from my SCH-I605 using Tapatalk 2
Thanks guys for the reply.
@mikecore - SDK manager, platform-tools and drivers were up to date. @runandhide05 - I made sure I was in the fastboot mode. And thank you so much for the link but it wasn't that I was doing wrong, the problem was the bootloaders were very old from the very first built or probably even before the xoom was released to public (when it was in manufacture trial or something). So whenever I tried to check the software update it said it was uptodate but it was running froyo (2.5 or something). What I did was I got the imgs of the latest built available from motorola and pushed that in fastboot mode. After that I got like 5 software updates OTA and it updated the bootloader to the latest version and now I am running android 4.1. Also I was able to unlock the bootloader now.
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
No exist a official tool for unlock the bootloader and by adb commands not is posible because the OEM unlock option not found on developper options menu. The trick of the delaying the date does not work as asus support suggest.
Someone know how unlock the bootloader for this model?
My guess is that if OEM unlock option isn't offered in Android Settings->Developer option then unlocking the bootloader is denied by OEM/Carrier.
BTW: ADB isn't used to deal with device's bootloader, but Fastboot is.
jwoegerbauer said:
My guess is that if OEM unlock option isn't offered in Android Settings->Developer option then unlocking the bootloader is denied by OEM/Carrier.
BTW: ADB isn't used to deal with device's bootloader, but Fastboot is.
Click to expand...
Click to collapse
Thanks a lot for your reply. I tried a lot things, between fastboot, you have reason. I have contacted to asus support and their reply is nothing. I will try with miracle box. do you know about this box?
Thanks a lot for your reply. I tried a lot things, between fastboot, you have reason. I have contacted to asus support and their reply is nothing. I will try with miracle box. do you know about this box?
Hello,
PROBLEM:
I have a phone, and it has an option in Settings -> System -> Developer options, called "OEM unlocking", and I have activated it.
But there is NO way in reality, to do that (all the adb or fastboot commands say that the device is closed, including the one that unlocks the bootloader), so... with no firmware available, and no TWRP, it is impossible to unlock the bootloader, root and of course, install any custom roms.
ASSUMPTION:
IF the manufacturer sells a phone with that option available, should we, the users, be always allowed to do that ? Is the seller violating any customer laws or terms of service by not doing that ?
SELLER ANSWER:
I've received from the seller this justification:
"
Please be advised that open Bootloader as well as other technical specifications of the OS were being designed by Google, the developer of the AndroidTM project. For more details, please consult Google Support for Android: https://support.google.com/android/topic/7651524?hl=en&ref_topic=7311597
In order to perform a fresh install of the proprietary software, you can use our direct service process by our authorized service partner, blablablah"
NOTES:
That phone I'm talking about is an Alcatel 3 2019, so nothing really remarkable, I know... but I'm asking a generic question for all the devices.
Thanks in advance !
I wouldn't blame the seller. I don't know anything about Alcatel devices, but if OEM Unlocking is toggleable in Developer Options, you should be able to unlock the bootloader via fastboot. Exactly how to do that may depend on the device.
This article details how it works. You essentially have 3 components at play here:
ro.oem.unlock.supported, which is baked into the ROM, determines whether OEM Unlocking is available in Developer Options.
get_unlock_ability is the state of OEM Unlocking. Off is 0, on is 1.
If get_unlock_ability=1, the bootloader can be unlocked via fastboot, usually by using fastboot flashing unlock, but in Alcatel's case, may be fastboot oem unlock
Hope this helps.
V0latyle said:
I wouldn't blame the seller. I don't know anything about Alcatel devices, but if OEM Unlocking is toggleable in Developer Options, you should be able to unlock the bootloader via fastboot. Exactly how to do that may depend on the device.
This article details how it works. You essentially have 3 components at play here:
ro.oem.unlock.supported, which is baked into the ROM, determines whether OEM Unlocking is available in Developer Options.
get_unlock_ability is the state of OEM Unlocking. Off is 0, on is 1.
If get_unlock_ability=1, the bootloader can be unlocked via fastboot, usually by using fastboot flashing unlock, but in Alcatel's case, may be fastboot oem unlock
Hope this helps.
Click to expand...
Click to collapse
Thanks ! but...
fastboot flashing get_unlock_ability -> FAILED (remote: 'unknown command')
fastboot flashing unlock -> same
fastboot oem unlock -> same
observingman said:
Hello,
PROBLEM:
I have a phone, and it has an option in Settings -> System -> Developer options, called "OEM unlocking", and I have activated it.
But there is NO way in reality, to do that (all the adb or fastboot commands say that the device is closed, including the one that unlocks the bootloader), so... with no firmware available, and no TWRP, it is impossible to unlock the bootloader, root and of course, install any custom roms.
ASSUMPTION:
IF the manufacturer sells a phone with that option available, should we, the users, be always allowed to do that ? Is the seller violating any customer laws or terms of service by not doing that ?
SELLER ANSWER:
I've received from the seller this justification:
"
Please be advised that open Bootloader as well as other technical specifications of the OS were being designed by Google, the developer of the AndroidTM project. For more details, please consult Google Support for Android: https://support.google.com/android/topic/7651524?hl=en&ref_topic=7311597
In order to perform a fresh install of the proprietary software, you can use our direct service process by our authorized service partner, blablablah"
NOTES:
That phone I'm talking about is an Alcatel 3 2019, so nothing really remarkable, I know... but I'm asking a generic question for all the devices.
Thanks in advance !
Click to expand...
Click to collapse
What soc in that device?
observingman said:
Thanks ! but...
fastboot flashing get_unlock_ability -> FAILED (remote: 'unknown command')
fastboot flashing unlock -> same
fastboot oem unlock -> same
Click to expand...
Click to collapse
It looks like the OEM uses different commands for its bootloader. What exact model of device do you have?
Try fastboot -i 0x1bbb oem unlock
V0latyle said:
It looks like the OEM uses different commands for its bootloader. What exact model of device do you have?
Try fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
Thanks again... it didn't work:
C:\WINDOWS\system32>fastboot -i 0x1bbb oem unlock
fastboot: unknown option -- i
The model is the alcatel 3 2019 5053Y
PizzaG said:
What soc in that device?
Click to expand...
Click to collapse
For the device (alcatel 3 2019 5053Y), the soc is the Qualcomm SDM439 Snapdragon 439 (12 nm):
alcatel 3 (2019) - Full phone specifications
www.gsmarena.com
Google didn't help much, so you might be SOL with this device.
V0latyle said:
Google didn't help much, so you might be SOL with this device.
Click to expand...
Click to collapse
Ouch ! Yep, it's sad... Anyway, thanks
By the way, I can access the shell (no root of course) by using 'adb shell' ... Is there any way then, to dump the boot partition without root and locked bootloader?) I assume you must be LOL right now
observingman said:
By the way, I can access the shell (no root of course) by using 'adb shell' ... Is there any way then, to dump the boot partition without root and locked bootloader?) I assume you must be LOL right now
Click to expand...
Click to collapse
Unfortunately no, without root access it is not possible to dump partition contents, with the exception of /data.
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking
Thats great thanks
I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too
Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?
Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.
Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch
Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!
underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock