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?
Related
I have the US version the 690Y and get the remote failed unknown command error when I do the command fastboot oem unlock.I even tried the newer fastboot oem flashing unlock.Do you have any idea how to work this out?My device is recognized in fastboot,all drivers correct but I keep getting errors.Any ideas?I haven't seen anyone post they've successfully unlocked the bootloader yet so I assume it's not possible as of yet?I appreciate any suggestions.
bob24260 said:
I have the US version the 690Y and get the remote failed unknown command error when I do the command fastboot oem unlock.I even tried the newer fastboot oem flashing unlock.Do you have any idea how to work this out?My device is recognized in fastboot,all drivers correct but I keep getting errors.Any ideas?I haven't seen anyone post they've successfully unlocked the bootloader yet so I assume it's not possible as of yet?I appreciate any suggestions.
Click to expand...
Click to collapse
So far it doesn't seem possible on the 690Y but works on the 690M. The lack of development for this phone is sad. I would gladly pay for a root option.
There must be some way to easily unlock the bootloader since the option "OEM unlocking - Allow the bootloader to be unlockled" exists in the developer settings. What are we missing?
I have the 690M and same, I check allow OEM unlock in developer settings but then the command is not recognized.
Ideas?
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
Hey all,
A quick question here. I realize that this phone just got released and the tools from our diligent devs are being either worked on or already released.
Will the oneplus 8 bootloader be easier to unlock without hassling with an unlock token (i.e. oneplus 7t). I've used the msm tool with my oneplus 6t (t-mobile version)
Please advise.
NOTE: I can already see some of you out there trying to be a smart ass or be an asshole about this. Like most of us, we are trying to accomplish something, not entertain your ego or justify your miserable existence. We've all seen it.
Mods: delete this.
I just hit allow OEM unlocking in developer options and typed "fastboot oem unlock" in fastboot. It wiped the phone and the bootloader was unlocked. Easy peasy. ?️
BeardKing said:
I just hit allow OEM unlocking in developer options and typed "fastboot oem unlock" in fastboot. It wiped the phone and the bootloader was unlocked. Easy peasy. ️
Click to expand...
Click to collapse
It's all done now. I had to wait for the unlock code from oneplus.com
BeardKing said:
I just hit allow OEM unlocking in developer options and typed "fastboot oem unlock" in fastboot. It wiped the phone and the bootloader was unlocked. Easy peasy. ️
Click to expand...
Click to collapse
Which version of your device was 'easy peasy'?
I have a pixel 3a with a locked bootloader and a very barebones android os on it. It has basically no apps, the only ones shown are clock and settings, the settings app is very stripped down from a regular settings app too. For example, and maybe most importantly, there is no build number so I can't unlock the bootloader. I've tried pressing everything that sounds somewhat related, nothing enabled developer options. The recovery is very barebones as well, it only has reboot or power off options. So this phone is basically bricked.
Is there any hope? Any tools that can force unlock the bootloader? I did find some that claim they can but they seem very sketchy so idk if I want to try those.
Any other solutions are welcome as well of course
Android Flash Tool
flash.android.com
Here's the easiest option - back to stock. This site from google does all the work. As long as you can get to bootloader - you are good.
mmead1143 said:
Android Flash Tool
flash.android.com
Here's the easiest option - back to stock. This site from google does all the work. As long as you can get to bootloader - you are good.
Click to expand...
Click to collapse
That was the first thing I tried, but like I said, there's no way to unlock the bootloader (as far as I can tell) so it doesn't work
If you can get to the bootloader screen you can unlock it there via ADB and Fastboot:
Here's an article: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3a-0198625/
Try this command: fastboot flashing unlock
mmead1143 said:
If you can get to the bootloader screen you can unlock it there via ADB and Fastboot:
Here's an article: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3a-0198625/
Try this command: fastboot flashing unlock
Click to expand...
Click to collapse
That command only works if you allow the bootloader to be unlocked from the developer options, and like I said, I can't enable developer options on this phone
I'm having the same problem.
Did you somehow resolve it yet?
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.