Related
Ok so sorry if this has already been posted but I can't find anything. This is my first attempt at rooting. I am trying to root my 2014 Moto x. I am on US cellular so I believe the model is XT1093. Not sure though as this seems to be missing from settings in lollipop. I tried a root tutorial for xt1097 but did not work. There is no OEM unlock setting in my Developer options. I think I have to unlock my bootloader through Motorola but havn't been successful.. any help would be greatly appreciated.
Andrew
I've got the same problem here I think it's a US Cellular problem with what they eliminated from lollipop but I can't be sure looking everywhere but can't find any answers. I wish we could get some help with this though would love to unlock and root this thing.
Yea, I think your right about it being a US Cellular thing. No one else seems to have the problem and US Cellular is a unique model number (XT1093 vs 1095 or 1097). Iv tried to unlock the bootlader through motos web cite which should work but I'm having some difficulties. I entered the info from my device, it said it was able to be unlocked and gave me the unlock key. but when I entered the key I got an error. Not sure if I'm doing something wrong or they are.. Still working on it..
[email protected] said:
Yea, I think your right about it being a US Cellular thing. No one else seems to have the problem and US Cellular is a unique model number (XT1093 vs 1095 or 1097). Iv tried to unlock the bootlader through motos web cite which should work but I'm having some difficulties. I entered the info from my device, it said it was able to be unlocked and gave me the unlock key. but when I entered the key I got an error. Not sure if I'm doing something wrong or they are.. Still working on it..
Click to expand...
Click to collapse
What command are you using to unlock your bootloader with the key? And what error are you getting?
I've tried the unlock method from Motorola. It all works until it prompts you to check the box in developing. options that says unlock oem functions. On the 1093 in lollipop the dev. option is not there. Also tried the tool kit in this forum that is made for non pure phones... It works great... even tells you your phone is unlocked but it doesn't finish. What I mean is it doesn't reboot your phone and the phone is still locked. Really frustrating ? Any help or ideas are very welcome. PLEASE HELP!
Is there a way to root the phone without unlocking? Cause if we could... We could try a different rom and see if from there we could find the unlock box in the developer options.
Golfmech said:
Is there a way to root the phone without unlocking? Cause if we could... We could try a different rom and see if from there we could find the unlock box in the developer options.
Click to expand...
Click to collapse
There's no such thing as "Unlock/ Unlock OEM functions" in developer options, in any ROM, ever.
Just found this.. Apparently Nexus 6 & 9 have this additional step to unlock the bootloader. I didn't have to do this while unlocking my device whilst on lollipop. So I'm gonna assume it's possible to unlock the bootloader on your device if this option is missing from the Developer Options..
Follow the procedure on motorola's website to unlock the bootloader and report back with the error you see on the online tool, or the actual device.
P.S - voids your warranty, unless you have a dev device
It doesn't give an error per say... It tells you to go to dev options and check the box or click on the option to unlock oem. Of course it's not there so the program will not execute the unlock. It says waiting for device....
Golfmech said:
It doesn't give an error per say... It tells you to go to dev options and check the box or click on the option to unlock oem. Of course it's not there so the program will not execute the unlock. It says waiting for device....
Click to expand...
Click to collapse
Has there been any more insight on this?
After updating to 5.1, OEM unlock is in developer options now
Hi there,
I bought me a new Huawei P9 a few month ago and installed the android 7 update first. I also unlocked bootloader (fastboot oem unlock <key>) and in the fastboot menu phone and FRP is unlocked. Every attemp to install a recovery like twrp e.g. failed. I get the black/orange boot-message that I cant trust my device because its unlocked. Navigating to Developer options and took a look onto the OEM Unlock entry: Its disabled and grayed out. Any ideas what to do? My main target is just to root that device...
Please help me
Best Regards,
LongBeardHagrid
Hello I have a new Moto G6. I have enabled developer options and I've enabled OEM unlocking. But it doesn't seem to stay enabled between reboots? I just bought this yesterday. I'm trying to unlock the bootloader, but I can't unless OEM unlocking stays enabled. Am I missing something? I know there's currently no root for the G6, but still I think I should be able to unlock it, or am I mistaken?
jloh1963 said:
Hello I have a new Moto G6. I have enabled developer options and I've enabled OEM unlocking. But it doesn't seem to stay enabled between reboots? I just bought this yesterday. I'm trying to unlock the bootloader, but I can't unless OEM unlocking stays enabled. Am I missing something? I know there's currently no root for the G6, but still I think I should be able to unlock it, or am I mistaken?
Click to expand...
Click to collapse
That just allows the bootloader to be unlocked. You still would need to actually unlock it following the unlocking guide thread in the guides section
dejello said:
That just allows the bootloader to be unlocked. You still would need to actually unlock it following the unlocking guide thread in the guides section
Click to expand...
Click to collapse
Yes I know this is not root, this is just unlocking the bootloader, yes I do have a key from motorola. But I can't do anything if OEM unlocking will not persist between reboots. I'm just trying to unlock the bootloader. And yes it is unlocked for sims.
jloh1963 said:
Yes I know this is not root, this is just unlocking the bootloader, yes I do have a key from motorola. But I can't do anything if OEM unlocking will not persist between reboots. I'm just trying to unlock the bootloader. And yes it is unlocked for sims.
Click to expand...
Click to collapse
I said nothing of root. Unless I am missing something from your original post, "Allow OEM unlocking" just allows the bootloader to be unlockable. After you tick it, reboot directly into fastboot mode (not back into android, that'll untick it again).
[GUIDE] Unlock Bootloader - This states after enabling OEM Unlock in settings (from within Android) to reboot into the bootloader (This guide says power off and then power back on while holding volume down, if you have debugging on you can just "adb reboot bootloader"). Rebooting back into Android with the bootloader still locked I believe does untick the OEM Unlock option.
ok thanks, I'll try again.
I have the XT 1925-6 US unlocked version. One of the first things I do with a new phone is to enable Developer Options and toggle OEM Unlock even though I may not Unlock the Bootloader right away.
The OEM Unlock toggle has stayed persistently on through numerous reboots with the Bootloader still locked.
Hmm.. Well I could have sworn I had seen what was described before, however it has been a while. I unlocked mine all in one go so I can't say. If it's supposed to stay on then I'd really be curious why it isn't for jloh
dejello said:
Hmm.. Well I could have sworn I had seen what was described before, however it has been a while. I unlocked mine all in one go so I can't say. If it's supposed to stay on then I'd really be curious why it isn't for jloh
Click to expand...
Click to collapse
I tried it again and it worked, thanks. I guess I rebooted android at first. Thank you.
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.