I have a new Moto G100. I would like to root the phone using Magisk. In order to be able to do that I used the procedure to get an unlock key from Motorola. When boot into the bootloader and try to send the key to the phone using
fastboot oem unlock <key>
I get the following response:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.060s
Developer settings are enabled. When I go to Android Settings > Developer and check 'OEM unlocking', the setting is grayed out. It looks like the setting is set to On.
The phone is eligible for unlocking according to the information from Motorola (cid variable is 0032).
Why is the unlock command failing? What can I do to fix it?
gewe said:
I have a new Moto G100. I would like to root the phone using Magisk. In order to be able to do that I used the procedure to get an unlock key from Motorola. When boot into the bootloader and try to send the key to the phone using
fastboot oem unlock <key>
I get the following response:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.060s
Developer settings are enabled. When I go to Android Settings > Developer and check 'OEM unlocking', the setting is grayed out. It looks like the setting is set to On.
The phone is eligible for unlocking according to the information from Motorola (cid variable is 0032).
Why is the unlock command failing? What can I do to fix it?
Click to expand...
Click to collapse
You need to connect to the internet, and wait 3 days or so, till oem unlocking is not grey
Edit does it look like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sd_shadow said:
You need to connect to the internet, and wait 3 days or so, till oem unlocking is not grey
Edit does it look like this?
Click to expand...
Click to collapse
Do this and update to latest OTA
After about 72 hours the option was magically enabled.
Related
My Nexus S is stuck on the google screen.
I have downloaded the drivers for Android ADB and have gotten fastboot talking to the device but for some reason ADB doesn't talk to the device (though it does with my HTC HD2).
The phone is still locked and has no custom bootloader on it.
I can list devices attached with Fastboot and it shows the Nexus's serial number but when I try to do "Fastboot oem unlock" it comes on the phones screen to unlock the bootloader and when I select yes it hangs there and cmd says:
Code:
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I am running windows 7 64bit.
The only difference I notice from the tutorials and mine is that the driver says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instead of Samsung Android Device.
I had to install the drivers manually as PDAnet couldn't pick up the device and I found the drivers on one of the many topics on this.
Any idea's would be much appreciated, I have been trying to fix this for over a week
inode86 said:
My Nexus S is stuck on the google screen.
I have downloaded the drivers for Android ADB and have gotten fastboot talking to the device but for some reason ADB doesn't talk to the device (though it does with my HTC HD2).
The phone is still locked and has no custom bootloader on it.
I can list devices attached with Fastboot and it shows the Nexus's serial number but when I try to do "Fastboot oem unlock" it comes on the phones screen to unlock the bootloader and when I select yes it hangs there and cmd says:
Code:
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I am running windows 7 64bit.
The only difference I notice from the tutorials and mine is that the driver says
Instead of Samsung Android Device.
I had to install the drivers manually as PDAnet couldn't pick up the device and I found the drivers on one of the many topics on this.
Any idea's would be much appreciated, I have been trying to fix this for over a week
Click to expand...
Click to collapse
If fastboot recognises your phone, have you tried flashing latest cwm.img recovery through it? (fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img) from your sdk tools folder? It could be that you never had USB debugging ticked in settings!
I have tried flashing the latest recovery .img to it but it comes up with the exact same error.
I don't think USB debugging was enabled before it bricked. I have no idea where to do from here as the phone was bought second hand so no warranty.
bump........
Ok, so when I turn on the phone, it gets stuck on the HTC screen logo forever. With the volume down and power button, I'm able to get into hboot/hboot usb plug when connected to the computer. The recovery, factory reset, image crc options don't work. In my linux computer, when I type fastboot devices, I'm able to get serial number of the phone. The picture links below summarize my current state
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The commands that I've tried are below.
(command): /fastboot devices [output] SH******** fastboot -- (note: here I did get my serial number but I know better than to post it here.
(command): ./fastboot oem rebootRUU [output]... FAILED (status malformed (1 bytes))
(command): ./fastboot flash zip PD15IMG.zip [output]: sending 'zip' (322693 KB)... FAILED (status malformed (1 bytes))
Tools in hand: android-sdk-linux, linux mint, PD15IMG.zip and phone
note: I also tried all of the above commands on windows 7 home premium 64 bit with adb installed and got the same error messages from fastboot. I tried the official htc bootloader unlocker but kept getting that error: 120 battery less than 30%.. although my battery is fully charged and that stopped the tool from unlocking the boot loader.
I read somewhere If i find the orginal stock recovery image, I might get out of this but I cannot find it anywhere yet.
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
RUU?
gesange said:
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
Click to expand...
Click to collapse
Yeah I tried RUU and it gets stuck all the time at Rebooting bootloader or waiting for bootloader
I'm trying to root my device after fetching unlock code from Huawei website
However, when I use adb command
HTML:
adb reboot bootloader
I get message on screen which says Phone is locked. FRP lock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BackToAndroid said:
I'm trying to root my device after fetching unlock code from Huawei website
However, when I use adb command
HTML:
adb reboot bootloader
I get message on screen which says Phone is locked. FRP lock.
Click to expand...
Click to collapse
you can unlock bootloader using command-
Code:
fastboot oem unlock [unlock key here]
and Don't use Development thread for question and help,
XN Logos said:
you can unlock bootloader using command-
Code:
fastboot oem unlock [unlock key here]
and Don't use Development thread for question and help,
Click to expand...
Click to collapse
When I use
Code:
adb reboot bootloader
command then immediately I get Phone Lock. FRP lock. message on mobile still if I got ahead and use
Code:
fastboot oem unlock [unlock key here]
I get failed message.
I thought rooting and similar questions go here, my bad. Can I move it or delete & repost it?
Android device manager
Did u deactivate Android device manager before restart into fastboot?
[email protected] said:
Did u deactivate Android device manager before restart into fastboot?
Click to expand...
Click to collapse
I don't think so, can you guide me how to
BackToAndroid said:
I don't think so, can you guide me how to
Click to expand...
Click to collapse
Go to settings> Security> Device administrators
BackToAndroid said:
I don't think so, can you guide me how to
Click to expand...
Click to collapse
Did you tick the OEM unlock option in Developer options? If not, go to Settings, About Phone, tap Build Number 7 times. Developer options will appear in Settings. Tick OEM unlock.
Hi friends, i am a new member here
First let me explain my problem
It has been couple weeks since i accessed the *#*#4636#*#* menu on my device and my curiousity kicked in and led my device to a total disaster. I have stupidly accessed the radioband option and stupidly tap the USA Band. Now my device can't make nor receive a call, message, and even access the MMI Code provided by my network provider. It works only on 4G/LTE network, and the network just disappears everytime i switch it to 3G network. Now my XPeria is just like a brick with "accessing 4G internet" ability
Yesterday i found a solution in a forum that requires me to debug my device from pc. I think this method is the solution because lot of user reply and say that this worked on their device so i decided to follow it too. I have followed the instructions, install the ADB in my PC and the fastboot and ****s. It alsosaid that i have to type these following commands in the command prompt i've opened in the adb folder
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
I have done this but i stuck in step 2 and 3 (the erase modemst). Everytime i type the command, it appears like (picture included)
fastboot erase modemst1
erasing 'modemst'.....
FAILED <remote: command not allowed>
finished. total time: 0.007s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can somebody please help me with this? How to make the command success. Or do you have another method to fix my radioband problem?
Thanks a lot beforehand
fadelsabdurrahmans said:
Hi friends, i am a new member here. First let me explain my problem. It has been couple weeks since i accessed the *#*#4636#*#* menu on my device and my curiousity kicked in and led my device to a total disaster...
Click to expand...
Click to collapse
I don't have this device but, the following threads may be helpful for what you need. Don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3130092
https://forum.xda-developers.com/showthread.php?t=3053512
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Warning] im not responsible for any brick
Requires
1 PC
2 ADB driver link https://mega.nz/#!Q7YnCQTb!W0baXOu5VxYLTfPBClumkSR_pCAK-Mntiz7HnKCx7yw
3 usb cable
step 1 install adb driver on pc
step 2 backup anything you want to keep [Example] photos and videos
step 3 in LAVA A3 you go to settings > about phone > more > click 7 time Build number now back to settings go to more Now you will see developer options there ON that
step 4 Enable OEM unlocking
Enable USB debugging
like screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
step 5 USB cable connected through PC
then open cmd command
Type the first comment then you will see a popup ON mobile screen Allow USB debugging like this screenshot
HERE THE commands
1) adb devices
2) adb reboot bootloader
3) fastboot devices
4) fastboot oem unlock
5) fastboot reboot
All done
4) (select volume up for confirming unlock bootloader and select volume down for not unlock bootloader) like this screenshot
After you unlock bootloader you will see this message like this screenshot
If you try these comments than you Device storang data and all others data will be erage so you need to make a backup first
Donation linkhttps://www.paypal.me/AnvarMc
HOW TO FLASH RECOVERY LINK https://forum.xda-developers.com/general/help/lava-3-lava-z25-twrp-philz-touch-t3807436
while doing that my phone suck on fastboot mode, any help ??
You need to contact their customer service department and they will help you.
problem solved.
while i was stuck on fastboot. just press volume up+volume down+power button at the same time 30+ sec. and it's normaly on. and again follow the steps. now i'm sucess. thanks
OEM unlocking
How? How are you expecting me to turn on OEM unlocking when there is no option for doing that in devloper option. I tried rsetting my device as it was new. without any update nothing but still i couldn't found OEM unlocking option in devloper option. then i used there OTA Update and even then i wasn't unable to locate OEM unlocking. without that this post doesn't work. I use lava a3 (not mini) still didn't work . Tired googling , Some forams but didn't worked . Help :crying::crying::crying::crying:
abirbd said:
How? How are you expecting me to turn on OEM unlocking when there is no option for doing that in devloper option. I tried rsetting my device as it was new. without any update nothing but still i couldn't found OEM unlocking option in devloper option. then i used there OTA Update and even then i wasn't unable to locate OEM unlocking. without that this post doesn't work. I use lava a3 (not mini) still didn't work . Tired googling , Some forams but didn't worked . Help :crying::crying::crying::crying:
Click to expand...
Click to collapse
Basic knowledge must have this process
Otherwise you will break your phone
mranwarmc said:
Basic knowledge must have this process
Otherwise you will break your phone
Click to expand...
Click to collapse
I explained my problem bro! i don't might have that knowledge! help me out bro