Hello,
I tried to unlock my bootloader following the guide stickied in general. I got the message from minimal adb and fastboot the unlock was succesful, now when I try to root it fails on install, so I went to check the status through the # code thingy. Before it said yes, now it says no.. What happened?
Related
I am trying to unlock the bootloader of my oneplus one, when using the oneplus one toolbox ive put phone into fastboot and clicked unlock bootloader but it just reboots my phone and does not change anything, ive tried doing fastboot oem unlock through cmd it says its successful but still does not change anything???
i realized that why nothing was changing was because it was already unlocked, now i have flashed supersu but i dont have root access when i open titanium it says that i can't get root access???
Did you install TWRP? You need that as well to get root.
Stop using the toolbox and do things manually, that's probably what's causing your problems. There's a guide in my signature.
Transmitted via Bacon
Hi all, i search all from the OPO thread still unable to find solution for my problem, now i have a third party recovery,i use many toolkit to perform unlock bootloader and i also use cmd command to unlock bootloader, but all action failed, it unable to unlock bootloader and straight bring me into recovery mode, so now when i trying to use cmd command to flash image fail was fail because it state the bootloader is lock, so now im stuck, i also cant restore cm recovery as the bootloader is lock, some one please guide me, thanks!!
keanyiap said:
Hi all, i search all from the OPO thread still unable to find solution for my problem, now i have a third party recovery,i use many toolkit to perform unlock bootloader and i also use cmd command to unlock bootloader, but all action failed, it unable to unlock bootloader and straight bring me into recovery mode, so now when i trying to use cmd command to flash image fail was fail because it state the bootloader is lock, so now im stuck, i also cant restore cm recovery as the bootloader is lock, some one please guide me, thanks!!
Click to expand...
Click to collapse
You might want to take a look at this:http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
elrey311 said:
You might want to take a look at this:http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
Thank you so much for help,i manage to found this thread yesterday
hello everyone my xperia e3 is rooted and i want to unlock the bootloader using the cmd commands shown in youtube.but when i try those commands at last the status says the the "device is already rooted"
should i remove the root to try unlocking the bootloader or how to continue futhur process for unlocking bootloader?
Hi everyone,
Today I decided to root my Mate 9.
I started out with turning 'OEM unlock' on and usb debugging. With ADB installed and the huawei drivers, I began to unlock my bootloader. On the 'EMUI Huawei' homepage I filled out my device details and obtained an unlock code. I opened ADB and checked with 'adb devices' if my device was there. It was. So I continued with typing 'adb reboot bootlader'. After that I typed 'fastboot devices'. My device was still showing up. I typed 'fastboot oem unlock CODE (with the code). On my screen I pressed 'Yes'. Bootloader unlocked.
After this step I tried to flash twrp with the command 'fastboot flash recovery xxxx.img'. I couldn't continue because every adb/fastboot command keeps failing (remote: command not allowed). Now when I boot up my phone it shows 'your device has been unlocked and can't be trusted'. Phone=unlocked, FRP=locked. I can't do anything.
Device: Mate 9 L29C432B198
What did I do wrong or what did I missed? :crying:
I had this issue at first to had to redownload the original rom via the phone recovery this will fix the frp lock then u have to unlock and flash twrp 3.1.01 that is linked in the threads on here
Did it format after it unlocked?
You can try fastboot oem relock UNLOCKCODE
Then go to Settings -> Dev options -> enable OEM Unlocking
Then unlock again.
It probably will fail though if FRP is locked, but worth a shot.
Edit: It's supposed to say
PHONE Unlocked FRP Unlock
So I got my new U12+, bought the unlocked version, I'm pretty sure when it updated it became locked??
Anyway, went to HTCdev to unlock and I get this message when I try
Security checking failed DENY
Shows it as locked S-ON
Should I reset it then get S-Off?
Sounds like you might be confusing a few things.
The Unlocked version is the sim-unlocked. The boot loader will be Locked S-ON. Two different things.
Now to unlock your boot loader to run custom software make sure you follow the steps exactly on HTCdev website.
Get your token key while in Download Mode, copy and paste the correct parts. Then unlock once you have the correct unlock token bin from HTC.
Unlocking your boot loader is all down while in Download Mode. Make sure your have OEM boot loader unlock enabled in Developer Settings.
What a dummy....
OK, de-bugging on and OEM unlocking is enabled.
Tried the steps at HTC and got no response from the phone after typing the get identifier command
I'll try again
BTW, is it just me or is it a pain to get the button sequence just right?
geoffwoerner said:
What a dummy....
OK, de-bugging on and OEM unlocking is enabled.
Tried the steps at HTC and got no response from the phone after typing the get identifier command
I'll try again
BTW, is it just me or is it a pain to get the button sequence just right?
Click to expand...
Click to collapse
It's annoying. But if you have adb on your computer with Debugging enabled within Developer Settings.
adb reboot bootloader
Thatll save you a few a minute or two
OK, so now I'm stumped again,
adb reboot bootloader
phone reboots as it should
fastboot oem get_identifier_token and nothing
<waiting for any device>
Never Mind, took a few tries and new drivers, we're good to go!
How were you able to resolve it? what drivers should i download? I tried twice and i am getting the same message:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
HTC u 12 Plus . android 9. adb and fastboot installed on a mac os mojave