All,
Attempting to unlock and root for the first time .
Bootloader unlocked - Done
Issue is with rooting and twrp installation :
RootChecker app says phone is not rooted properly.
Now as i am new to this there is something definitely wrong - i followed this thread and this is the closest i have come to rooting :
Currently the phone in the fastboot and so called rooting in progress :
screen reads :
cmd : OEM unlock
cmd : OEM unlock
cmd : OEM unlock-go
cmd : OEM unlock-go
cmd : Finishing unlock (does not look like it is finishing it)
Any help on this is greatly appreciate - i am practicing this on Moto G as if i am successfull i will move to OP2 and use it with latest android ROM
Related
while unlocking bootloader on the command prompt window i gave first command ''fastboot'" devices and it succeded but when i entered the second command correctly along with the key it showed failed to command ,,plssss help i want to unlock the bootloader
Which method you used for unlocking bootloader and which phone you are using
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
Hello,
Did anyone managed to unlock bootloader on Realme 5i ?
I flashed the latest Android 10 firmware from RealMe website, everything went ok, but now I want to unlock bootlader to root the device, and it seems that nothing helps.
Please help, thanks
how to unlock the bootloader in Realme 5i RMX2030
Here is a good guide that worked for me to unlock the bootloader:
www ytechb com/how-to-root-realme-5i-and-unlock-bootloader/
The root part didn't work, Magisk complains about unknow boot image format
G0bl1n said:
Here is a good guide that worked for me to unlock the bootloader:
www ytechb com/how-to-root-realme-5i-and-unlock-bootloader/
The root part didn't work, Magisk complains about unknow boot image format
Click to expand...
Click to collapse
I've done the in-depth test and it's on the Fastboot screen but when I type fastboot flashing unlock in a command window it just shows me the help text for fastboot, which doesn't show any command or option for either flashing or unlock, so how can I get it to work if those aren't valid commands?
fastboot devices shows my phone, so the device is recognised.
EDIT: I'm still on Android 9 A.15. I understand that there's no unlocked for Android 10 yet.
EDIT: Nevermind. I was using adb/fastboot from the link in this guide, which is v1.3 https://www.ytechb.com/how-to-root-realme-5i-and-unlock-bootloader/
After I updated to minimal v1.43 from here it worked https://androidmtk.com/download-minimal-adb-and-fastboot-tool
My problem was same. But i successfully downgrade to color os 6. I guess you can try it too.
Enable USB Debugging and Allow unlock boot loader option in USB debugging.
Connect your mobile with PC and use following Command.
adb reboot bootloader
fastbook flashing unlock
Check mobile for unlock option.
How did you downgraded to colour os 6?
I'm trying to root my realme 5i that i upgraded to 10.
Can you help me?
M. Farhad said:
My problem was same. But i successfully downgrade to color os 6. I guess you can try it too.
Enable USB Debugging and Allow unlock boot loader option in USB debugging.
Connect your mobile with PC and use following Command.
adb reboot bootloader
fastbook flashing unlock
Check mobile for unlock option.
Click to expand...
Click to collapse
what's the next step
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.