Hello all! First post here so if I out this in the wrong section, or do the pst wrong, then feel free to correct me.
I am trying to root my old phone, which is a Moto e4. I tried rooting with mutiple sources (Using a computer) but all of them failed. I concluded through google searches that one reason this may be happening is because the bootloader is still locked, so I started on that.
I got to the command promt, and can locate and identify the device, but when I run the command to unlock the bootloader and get the code for the motorola website, (fastboot oem unlock, and some variations of this command, all the same result.) When I do this, I get the results that I should get, but where the code should be, it says not found. I have my OEM unclokcing checked in Deve settings, and USB debugging is on as well. I am at school right now, so unfornatly I cannot give information on the model number, or anything like that, but I can respond to questions when I can. If I don't even need to unlock the bootloader on the moto e4 to root, then all the better, but I am fine with going through the trouble of unlokcing the bootloader!
Thanks,
Eriith
Eriith said:
Hello all! First post here so if I out this in the wrong section, or do the pst wrong, then feel free to correct me.
I am trying to root my old phone, which is a Moto e4. I tried rooting with mutiple sources (Using a computer) but all of them failed. I concluded through google searches that one reason this may be happening is because the bootloader is still locked, so I started on that.
I got to the command promt, and can locate and identify the device, but when I run the command to unlock the bootloader and get the code for the motorola website, (fastboot oem unlock, and some variations of this command, all the same result.) When I do this, I get the results that I should get, but where the code should be, it says not found. I have my OEM unclokcing checked in Deve settings, and USB debugging is on as well. I am at school right now, so unfornatly I cannot give information on the model number, or anything like that, but I can respond to questions when I can. If I don't even need to unlock the bootloader on the moto e4 to root, then all the better, but I am fine with going through the trouble of unlokcing the bootloader!
Thanks,
Eriith
Click to expand...
Click to collapse
yes bootloader needs to be unlocked.
It could be a usb driver issue
See moto driver link in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
yes bootloader needs to be unlocked.
It could be a usb driver issue
See moto driver link in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
In between the time you responded and now, I have ublcoked the bootloader, and got TWRP to work, not I just need to install Magisk and start the root! Thank you for responding though.
Related
When I try to acces recoveryPLAY or try to unlock the bootloader I get the "failed, phone must bee rooted" I just flashed everything to 2.3.3 before I was rooted and haad a unlocked bootloader, but relocked it to update OTA, now none of the fastboot stuff is working. Anyone have any ideas? I would really really appreciate any help.
You have to unlock the bootloader again. I had the same problem.
Sent from my R800x using XDA App
IfI could unlock the bootloader I would. The unlock code is not working. Its the same code I used over a month ago to unlock my bootloader before I relocked it to update.
Whether I am trying to unlock the bootloader or fastboot recoveryPLAY both come back with "failed, phone must be rooted".
Probably a silly question, but, do you have the unlock command line correct, and have you verified if fastboot is working properly? Try 'fastboot -i 0x0fce getvar version'. It should return a version number if fastboot is working properly.
Sent from my R800x using XDA App
Yes, I have checked everything 4 times and the fastboot getvar is showing the phone is connected. Even using flashtool to flash back to 2.3.2 then trying to use the fastboot commands gives the same results.
Is there a 2.3.2 .FTF files that has root embedded that I can try and flash and see if that works?
What does it say when you try to unlock the bootloader?
Sent from my R800x using XDA App
I have already listed what it says. "Failed, phone must be rooted".
This repsonse is for both commands to either unlock the bootloader or boot into recoveryPLAY.img
And yes my bootloader unlock code is correct when i type it in, and when I used it before the OTA to unlock my bootloader. So the code is the correct code.
That's very strange. If all your command lines are correct, and you are inputting the correct code, it should be working. I only got that message when trying to boot a recovery image without unlocking. Sorry, I don't know what to tell you now.
Sent from my R800x using XDA App
thats okay. I just really hate having no root access and a locked bootloader. I would at least like to have root so I can use TB. I appreciate your attempts to assist me. Thank you
Anyone have any ideas for a solution to this or why this is happening? Everyone else seems to be able to reroot and unlock the way they have always done, except for me nothing is working.....
Bootloader unlock request spits out this:
<bootloader> Unlock phone requested
FAILED <remote: oem unlock failed!>
finished. total tim: 0.003s
Is there a FTF file that has root embedded into it I can use with flashtool? Fastboot is not accepting my code lines for either recoveryPLAY or my attempts to unlock the bootloader.
bump.......
Just realized about 10 minutes ago the unlock code IWas using was for my old xperia play. I found the code that pertained to my current phone and it still gives me the same results.....damn
Can you try wontanserver to go back to 2.3.2?
never heard of it, is it free? Looks like its a website or something
wow.... I am so unintelligent sometimes. I have been fighting with getting this phones bootlaoder to unlock and then it came to me, I am not typing it in caps. So I did and BAM!!!!!! bootloader unlocked. Guess since the 2 months I last unlocked it my brain got soggy like a bowl of runny oatmeal
Ya its free and imho the easiest way to flash any stock firmware from every region. The wontanserver program has it all.
K, I will save that for later. Thank you.
IS your phone R8OOX? ask alejandrox -whatever his name is for you to unlock it
edit: glad you fixxed it
I finally got my bootloader unlocked last night. I was misinterpreting a "0" (zero) as a "O" as in Oh. Got my phone updated i 2.3.3 with root and bootloader unlocked. I would like to thank everyone for their help. Guess I should get me eyes checked.
Here is a tutorial to unlock the bootloader on our Moto X Play: http://www.gammerson.com/2015/08/steps-how-to-unlock-bootloader-of-moto-x-play.html
The warranty is not there after this, is there any way to lock it again without Motorola being able to see that it was unlocked?
Gesendet von meinem XT1562 mit Tapatalk
I guess every moto phones have the same process
http://forum.xda-developers.com/showthread.php?t=2753110
Sent from my Moto E using XDA Free mobile app
The unlocked bootloader warning message can easily be removed too: http://www.droidviews.com/remove-bootloader-unlocked-warning-on-moto-x-and-moto-x-2014/ I tested it and it work on our Moto X Play.
Oops.....completely forgot that this will wipe the phone (as all devices do when unlocking the bootloader).
Nico3d3 said:
We may not have CWM recovery and root yet, but here is a tutorial to unlock the bootloader on our Moto X Play: http://www.gammerson.com/2015/08/steps-how-to-unlock-bootloader-of-moto-x-play.html
Click to expand...
Click to collapse
We have TWRP recovery now, lets root it .
[Steps] How to Root Moto X Play by Flashing TWRP Recovery
Nico3d3 said:
The unlocked bootloader warning message can easily be removed too: http://www.droidviews.com/remove-bootloader-unlocked-warning-on-moto-x-and-moto-x-2014/ I tested it and it work on our Moto X Play.
Click to expand...
Click to collapse
This will work even if it's a Moto X 2014 logo? I'm a little uneasy in doing this.
karendar said:
This will work even if it's a Moto X 2014 logo? I'm a little uneasy in doing this.
Click to expand...
Click to collapse
So far, hasn't caused any issues for me.
Worked for me too
If I just remove the message, won't the technical assistance be aware that I unlocked the bootloader?
LuizHenrique91 said:
If I just remove the message, won't the technical assistance be aware that I unlocked the bootloader?
Click to expand...
Click to collapse
They already know since you requested the bootloader unlock code. From the terms and conditions:
THE FOLLOWING APPLIES TO ALL UNLOCKED DEVICES EXCEPT FOR DEVELOPER EDITION DEVICES. BY OBTAINING THE UNLOCK CODE FOR THIS DEVICE, IRRESPECTIVE OF WHETHER THE DEVICE'S BOOTLOADER IS SUBSEQUENTLY UNLOCKED OR ITS SOFTWARE OR OPERATING SYSTEM IS MODIFIED, USER AGREES TO WAIVE AND VOID ALL WARRANTIES
Click to expand...
Click to collapse
Removing the message is more for us, so we don't need to keep seeing it.
... disregard.... This is not the post you're looking for, move along.
Is unlocking for your device not dangerouse?
blackmaffia said:
Is unlocking for your device not dangerouse?
Click to expand...
Click to collapse
nope not dangerous, rather you can have more control over your device than Motorola gives you.
blackmaffia said:
Is unlocking for your device not dangerouse?
Click to expand...
Click to collapse
You just loose your warranty.
Sent from my XT1562 using Tapatalk
Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
Anyone please help me.
I tried to install the official OTA and something went wrong. The device got stuck into bootloops. I entered into bootloader and decided to unlock it. As adviced by the xda thread i followed the instructions, but after getting the Unique key via Email, when i enter "fastboot unlock OEM UNLOCKKEY", it gives an error saying Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
I cannot boot my phone.
Please help me.
Hamzasr said:
Anyone please help me.
I tried to install the official OTA and something went wrong. The device got stuck into bootloops. I entered into bootloader and decided to unlock it. As adviced by the xda thread i followed the instructions, but after getting the Unique key via Email, when i enter "fastboot unlock OEM UNLOCKKEY", it gives an error saying Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
I cannot boot my phone.
Please help me.
Click to expand...
Click to collapse
i recall this problem happening to someone earlier, he solved it by clearing cache and factory wipe from recovery
bootloader>>recovery>>factory reset and clear cache
http://forum.xda-developers.com/mot...-how-to-downgrade-6-0-to-5-1-1-t3267253/page5
Hamzasr said:
Anyone please help me.
I tried to install the official OTA and something went wrong. The device got stuck into bootloops. I entered into bootloader and decided to unlock it. As adviced by the xda thread i followed the instructions, but after getting the Unique key via Email, when i enter "fastboot unlock OEM UNLOCKKEY", it gives an error saying Failed to unlock Bootloader. Check "Allow OEM unlock" in Developer Options.
I cannot boot my phone.
Please help me.
Click to expand...
Click to collapse
There is a thread I created for the first timers.
You have to check the option "allow oem unlock" in developer options.
Please check the whole forum for details before doing anything like this.
Sent from my XT1562 using Tapatalk
blackmaffia said:
Is unlocking for your device not dangerouse?
Click to expand...
Click to collapse
If you leave it unlocked after rooting then it can make your phone more susceptible to localised threats like someone stealing your phone and re-purposing it or stealing your data from it directly.
But for many the reward outweighs the risks and there are ways to mitigate.
Trying to unlock Moto X Play on Linux by using "fastboot oem get_unlock_data", but it just says waiting for device. I ran "adb devices" and also enable "Allow unlocking device" in the Developer menu. Am I missing something?
Trying to root my phone but the OEM Unlock option does not show up in the developer options..I've searched around and couldn't find anything.
johnronin said:
Trying to root my phone but the OEM Unlock option does not show up in the developer options..I've searched around and couldn't find anything.
Click to expand...
Click to collapse
Who's your carrier?
T-Mobile has it
Verizon
johnronin said:
Trying to root my phone but the OEM Unlock option does not show up in the developer options..I've searched around and couldn't find anything.
Click to expand...
Click to collapse
I know it was there on 12A. Also if you are on VS995 Verizon, why do you need OEM Unlock. I don't remember seeing anywhere in the dirtysanta instructions that you need to do OEM unlock.
I have checked on both firmware available for the vs995..neither has it as an option.
The instructions don't say to check oem unlock ..but they also don't say to make sure the phone is in debug mode either. ...and every dirtysanta tutorial I looked up had oem unlock and debug as prerequisites except for the xda tut...
...I tried rooting and got all the way to step 3 but twrp would not let me format the data ...I'll try one more time before heading to sleep.
We don't have OEM UNLOCK on Verizon V20. Did you finish the dirtysanta successfully?
Sent from my VS995 using XDA-Developers Legacy app
johnronin said:
I have checked on both firmware available for the vs995..neither has it as an option.
The instructions don't say to check oem unlock ..but they also don't say to make sure the phone is in debug mode either. ...and every dirtysanta tutorial I looked up had oem unlock and debug as prerequisites except for the xda tut...
...I tried rooting and got all the way to step 3 but twrp would not let me format the data ...I'll try one more time before heading to sleep.
Click to expand...
Click to collapse
my suggestion would be to ask for help in the dirtysanta thread, you will get more help there
That's a good suggestion but it wouldn't let me post in that forum... I should have enough posts now though...
I was able to go through all of the steps and get twrp and booted up but root checker says no root access
Verizon removed that option from the menu. No Verizon V20 has it. That being said--it isn't needed if you follow the dirty santa instructions.
Hi,
So I recently got my hands on this new phone, and the blimming phone won't unlock. I'm using the XT1700!!! Not E3 Power!. It's on TESCO UK, and the System Version is "23.0.XT1700_S303_160829_UK". Yes, in developer options, OEM Unlocking is ticked! Tried two PCs, different drivers, different cables... idk.
I get the output on my phone to unlock with both "flashing unlock_critical" and "oem unlock"; both say "Unlock failed, returning to fastboot in 3s..."
This is the output in CMD:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 7.803s
Any suggestions? I'm really not sure.
jcolongo said:
Hi,
So I recently got my hands on this new phone, and the blimming phone won't unlock. I'm using the XT1700!!! Not E3 Power!. It's on TESCO UK, and the System Version is "23.0.XT1700_S303_160829_UK". Yes, in developer options, OEM Unlocking is ticked! Tried two PCs, different drivers, different cables... idk.
I get the output on my phone to unlock with both "flashing unlock_critical" and "oem unlock"; both say "Unlock failed, returning to fastboot in 3s..."
This is the output in CMD:
Any suggestions? I'm really not sure.
Click to expand...
Click to collapse
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure if you read elsewhere in the unlock bootloader thread, the S303 firmware DOES NOT allow the bootloader to be unlocked.
My E3 is S124 firmware, although I have been running Lineage OS 14.1 (android 7.1.2) on it for some time.
Sorry but there's no way you can unlock this model
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure if you read elsewhere in the unlock bootloader thread, the S303 firmware DOES NOT allow the bootloader to be unlocked.
My E3 is S124 firmware, although I have been running Lineage OS 14.1 (android 7.1.2) on it for some time.
Sorry but there's no way you can unlock this model
Click to expand...
Click to collapse
Is there not anyway I can flash S124? Its MTK so I could surely use a flashtool?
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure you need to unlock the bootloader to do that.
Its really not worth the hastle.
S124 isn't available anywhere to download unless you pay for it, but you got to unlock the bootloader before you can flash it, as its only available as a TWRP back up.
I lost my IMEI number doing that and had to flash an S131 E3 power firmware and reflash my IMEI which wasn't easy at all.
I've just checked and S303 and S512 are indeed bootloader locked.
Click to expand...
Click to collapse
bubba1601 said:
bubba1601 said:
Yeah.
My E3 XT1700 was purchased from Tesco but its sim free, not locked to tesco.
I'm pretty sure you need to unlock the bootloader to do that.
Its really not worth the hastle.
S124 isn't available anywhere to download unless you pay for it, but you got to unlock the bootloader before you can flash it, as its only available as a TWRP back up.
I lost my IMEI number doing that and had to flash an S131 E3 power firmware and reflash my IMEI which wasn't easy at all.
I've just checked and S303 and S512 are indeed bootloader locked.
Click to expand...
Click to collapse
Damn man. Is there anyway I can root at least?
Click to expand...
Click to collapse
jcolongo said:
bubba1601 said:
Damn man. Is there anyway I can root at least?
Click to expand...
Click to collapse
Not unless you find one if these "one click root" apps via PC that supposedly magically root.
Its a shame these bootloaders cannot be advertised as not unlocking compatible, it would have saved you a lot of trouble.
Do try everything although to be fair, I've not seen anyone post about unlocking those two firmwares.
I'm only sorry I can't help more
Click to expand...
Click to collapse
bubba1601 said:
jcolongo said:
Not unless you find one if these "one click root" apps via PC that supposedly magically root.
Its a shame these bootloaders cannot be advertised as not unlocking compatible, it would have saved you a lot of trouble.
Do try everything although to be fair, I've not seen anyone post about unlocking those two firmwares.
I'm only sorry I can't help more
Click to expand...
Click to collapse
It's all good. I'm making progress however; managed to find a S124 SP flash firmware, but I'm scared to flash it, as I'll be out of a phone for 3 months which is a problem, as I need it for collage. I'll continue to look around.
Click to expand...
Click to collapse
I am trying to unlock my bootloader and root my phone but I am unable to turn on the OEM unlocking feature in developers options. Several months ago I returned/restored the phone's stock image. I previously rooted my phone but decided to unroot it. Now I am attempting to root it again but I cannot unlock the bootloader by switching on OEM unlocking.
The OEM Unlocking option is greyed out and appears to be locked or inaccessible. I have attached a screen shot.
Can someone tell me what I must do to fix this.
LeoG360 said:
I am trying to unlock my bootloader and root my phone but I am unable to turn on the OEM unlocking feature in developers options. Several months ago I returned/restored the phone's stock image. I previously rooted my phone but decided to unroot it. Now I am attempting to root it again but I cannot unlock the bootloader by switching on OEM unlocking.
The OEM Unlocking option is greyed out and appears to be locked or inaccessible. I have attached a screen shot.
Can someone tell me what I must do to fix this.
Click to expand...
Click to collapse
Are you sure the BL is locked now? If not boot into BL and check it. In any case Google is your friend:
https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
That's why I don't see any sense in relocking, I can't find any advantage in it.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
That's why I don't see any sense in relocking, I can't find any advantage in it.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I hear you Wolfcity. And it is something that seems to come up on every device I have owned starting with the Moto G2 (G3, G4, G5+, & G5s+). I have had users flat out tell me I am wrong and that you need to relock the device in order to go back to stock or remove root. :silly: