I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
<Moderator Edit>: Post edited. I will PM you as to why shortly.
I have rog phone 5s pro tencent edition china rom... and I success to convert to global ww rom
krampyl said:
I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
Click to expand...
Click to collapse
You can't root this device that way. You need the ASUS unlock tool and I believe ASUS have pulled their unlock service for the time being. I think you will find tens if not hundreds of posts related to this topic on the forum. Patching via EDL is an option but not done so far as everyone have used the ASUS Unlock tool?
krampyl said:
I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
Click to expand...
Click to collapse
Also, do not pay anyone on Facebook or other places for this type of work. Just a friendly advise to save you some $.
Related
i tried to unlock my vivo y21l using adb command "fastboot oem unlock" but i get an error saying "device lock" message but my phone get identified by adb command so it's not a driver problem.is there any other way to unlock the bootolader? i just want to root my phone but not any one click methods are working so i guess it's because of locked bootloader maybe.thanks for anyone who can help.
Imalka Muthukumara said:
i tried to unlock my vivo y21l using adb command "fastboot oem unlock" but i get an error saying "device lock" message but my phone get identified by adb command so it's not a driver problem.is there any other way to unlock the bootolader? i just want to root my phone but not any one click methods are working so i guess it's because of locked bootloader maybe.thanks for anyone who can help.
Click to expand...
Click to collapse
Hi I can see you have already asked this before here
https://forum.xda-developers.com/showthread.php?t=3584719
You can bump your original post once every 24 hours but please don't create duplicate threads
Kind Regards
Sawdoctor
I've tried online guides to unlock bootloader, but messed up in some point and now I'm stuck.
1st. Download indepth test and reboot to bootloader within the app.
2nd. Tried adb devices successfully
3rd. Fastboot oem unlock nor Fastboot flashing unlock run (output: fastboot oem unlock failed "remote unknown command")
4th. Decided to make a factory reset (just becase I had to make an stupid desition)
Now I can reboot into fastboot again, because in depth test app won't install anymore. Installer says "Installation failed -An app with the same signature has already been installed"
I've unsuccessfully tried to flash stock rom from recovery but thein depth test seems to be "installed" without front user interface, also fasboot reboot bootloader get stuck in waiting for any device.
Can someone have a solution I already tried anything that comes to my mind.
Thanks.
I was able to solve the problem installing extractly the same apk.
The "fastboot oem unlock" dont work for me
What work on me 5pro is "fastboot flashing unlock"
Then flash twrp and vbmeta
To relock bootloader "fastboot flashing lock"
Source https://forum.xda-developers.com/realme-5-pro/how-to/bootloader-unlock-tutorial-t3985003
Other, might helpful source:
https://forum.xda-developers.com/realme-5-pro/development/rom-pixel-experience-t4053357
Hello!
I am trying to root my Nokia 3, which I don't use daily, but I'm having difficulty finding a recent thread, and I'm not really sure of what I'm doing.
I am comfortable with this type of things and "messing around" with devices, but I haven't rooted a phone since I got my first Android phone (Samsung Galaxy Gio) and it was really simple and different back then. (Pretty sure I just had to get the right .zip file and enter recovery mode to "load" it).
I want to know what are the pre-requisites to root my Nokia 3 and, if possible, have a guide with the steps on how to do it, because I don't want to brick the phone or something similar.
Thank you for your attention!
Okay, I've started trying to actually root it, starting by unlocking the bootloader.
I'm following this guide: https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
But these commands are confusing me:
fastboot oem dm-verity <your_unlock_key>
fastboot flash lk NE1-0-215H.lk.bin
fastboot reboot-bootloader
Click to expand...
Click to collapse
I don't understand what is my unlock key, I've entered my serial number here: https://passwordsgenerator.net/md5-hash-generator as the guide suggested, but it returns "FAILED (remote: unknown command)" when I run fastboot oem dm-verity.
I also tried "fastboot flashing unlock" and "fastboot oem unlock" because those commands were listed on "fastboot help", but that just returns "FAILED (remote:Unlock operation is not allowed)".
I'm very lost at this point and have no idea of what I can do to solve this. Any help would be greatly appreciated.
Thank you.
Hi,
I have a new X95 with Android 10 go edition. aperently I get an error message when I use some apps.
do not disturb access this feature is not available on this device
Is there anything I can do, to solve this problem?
I would like to flash another img file to the device but got all the time <wating for device> any solution for that?
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
tennoguchi said:
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
Click to expand...
Click to collapse
Use only this command:
Fastboot flashing unlock
I too want to unlock, root and customize the X95... And failed at the very first steps.
I hope some of the forum gurus watches this phone/thread
Here's the steps I took and the errors I got, any help would be appreciated!
1. enable "OEM unlocking" in development options
2. adb reboot fastboot
3. a) fastboot flashing unlock FAILED (remote: 'Unrecognized command flashing unlock')
3. b) fastboot oem unlock FAILED (remote: 'Command not supported in default implementation')
Also, this phone seems not to be recognized in bootloader mode (displays only "=> fastboot", but fastboot doesn't recognize any device).
When booting to recovery, entering fastboot from there (same as after "adb reboot fastboot"), I can get to the point of failure above.
I'm really uncomfortable with the current setup, any help would be appreciated!
Someone got root
Someone got root.
Thank you.
gatolocox said:
Someone got root.
Thank you.
Click to expand...
Click to collapse
This answer/question (?) is not really helpful, can you please elaborate?
Any news on how to root the x95?
Olize said:
Any news on how to root the x95?
Click to expand...
Click to collapse
I haven't tried since the failure reported above, meanwhile I got a redmi note 9s for 119€, so I'm using this one on a custom setup now.
Still using the x95 as an AP, I'm interested on any progress made on the topic..
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.