I must have missed a step when I unlocked my XT1053 last year. I never did anything with it and assumed that because it gives the the caution screen when I turn it off and back on, that the bootloader is unlocked. However, now that I decided to get down and do stuff, it's telling me via third party apps that my phone isn't actually unlocked. There's no super user app or anything. Do I need to go through the unlocking process again? I'm on 4.4.4.
Me again. I'm following the directions for rooting it and have flashed TWRP 2.8.6.0 but when I select Recovery, there's a dead android and it says "No Command."
You have an unlocked boot loader but you don't have root privelages.Also try holding down volume down+power on no command
It takes some reading comprehension but the tutorials here really are excellent. I guess I have a philosophical question: why would you unlock the bootloader without the intention of rooting the phone? I had (obviously) confused the terms.
s3ars said:
I must have missed a step when I unlocked my XT1053 last year. I never did anything with it and assumed that because it gives the the caution screen when I turn it off and back on, that the bootloader is unlocked. However, now that I decided to get down and do stuff, it's telling me via third party apps that my phone isn't actually unlocked. There's no super user app or anything. Do I need to go through the unlocking process again? I'm on 4.4.4.
Click to expand...
Click to collapse
Can you boot the phone into Fastboot/Bootloader mode? What does it say for the status?
If its LOCKED Status 0, then your bootloader is locked. If its LOCKED Status 2 (or 1), then you are "Relocked" (i.e. the bootloader was unlocked, then someone used the Fastboot OEM LOCK process to relock the bootloader). The phone will always show the UNLOCKED Warning message screen if your status is no longer 0. (As users, we can toggle between Unlocked and Relocked, but can't get it back to Locked Status 0).
Since the XT1053 can unlock its bootloader via the code from Moto's web site, you can always just follow the bootloader unlock process again, using the same unique code for your phone.
After your phone's bootloader is showing UNLOCKED Status 3, you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 (Step 8 IS necessary) Please be sure to use the latest TWRP fastboot IMG file and Installable ZIP of SuperSU
---------- Post added at 08:31 AM ---------- Previous post was at 08:26 AM ----------
s3ars said:
It takes some reading comprehension but the tutorials here really are excellent. I guess I have a philosophical question: why would you unlock the bootloader without the intention of rooting the phone? I had (obviously) confused the terms.
Click to expand...
Click to collapse
Since doing the bootloader unlock process is "desctructive" (i.e. wipes use data/apps from the phone), some will unlock the bootloader when they first get the phone, run with it, and maybe root later... that way when they do decide to root, they wont need to also wipe the phone and have to set it back up from scratch.
But that is the only reason I can think of why one would unlock the bootloader, and not root. At the same respect, if you don't have a phone which is branded Developer Edition, you've already voided the phones warranty by requesting the code from Moto, so, why not root immediately?
Related
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
STEyeAndroid said:
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
Click to expand...
Click to collapse
I would start here: http://forum.xda-developers.com/showthread.php?t=2536200
I don't know why the unlocked bootloader warning screen would stay set if you relocked it, but you can change that screen to display whatever you want. See here for details:
http://forum.xda-developers.com/showthread.php?t=2417961
Since you have the dev edition, you should be able to unlock, install TWRP, and root without slapmymoto or pwnmymoto. I did it all AFTER installing the latest OTA, and I had no trouble.
I have not used RSDLite, but that is the way I understand it.
STEyeAndroid said:
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
Click to expand...
Click to collapse
Sell or trade your dev edition. Installing SafeStrap on that phone is such a waste of time and energy.
Or read more. There are ways to remove the boot logo screen.
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
STEyeAndroid said:
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
Click to expand...
Click to collapse
It appears to. And the statement about still receiving the unlocked bootloader warning after re-locking the bootloader is correct.
However, since the warranty of the Dev Edition is not voided, just unlock the bootloader, root, and then get rid of the message by replacing the logo.bin
STEyeAndroid said:
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
Click to expand...
Click to collapse
You bought a dev edition, it doesn't matter if the flag is set or not.
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
Hi all,
I've purchased a used P20 Pro from a friend which has an unlocked bootloader and has been previously rooted. I normally keep my phones stock so I want to lock relock the bootloader (I have the code) but despite trying to follow various guides I have been unsuccessful.
Would anyone be able to guide me through the process of relocking the bootloader please?
The main reason I like to keep stock is manufacture updates etc and I don't have the knowledge to maintain a rooted phone.
R89B said:
Hi all,
I've purchased a used P20 Pro from a friend which has an unlocked bootloader and has been previously rooted. I normally keep my phones stock so I want to lock relock the bootloader (I have the code) but despite trying to follow various guides I have been unsuccessful.
Would anyone be able to guide me through the process of relocking the bootloader please?
The main reason I like to keep stock is manufacture updates etc and I don't have the knowledge to maintain a rooted phone.
Click to expand...
Click to collapse
I don't believe that an unlocked bootloader will prevent you from getting updates. As far as I know the only difference is the warning you get when you boot that "you can't trust the phone."
IF YOU BRICK YOUR PHONE IT'S YOUR RESPONSIBILITY
Don't know if there is another way but of you have fastboot and adb you can do it:
1. Make sure developer options are enabled
2. Connect your phone to the computer using USB cable.
3. Open a command window and type 'adb boot bootloader'
4. Once the device has booted into the bootloader mode type 'fastboot oem lock'
This WILL ERASE all your user data and you will have to configure everything from scratch. You will need the unlock code if you ever want to unlock it again so make sure you don't loose it.
Yesterday, I was going to lock my bootloader to cell my Nokia 8 cuz' I needed money. Being the noobie that I'm I didn't have my unlock key saved anywhere. and couldn't get a new one because the stupid Bootloader unlock app doesn't work on Pie. I did know that locking the bootloader doesn't require a key. So I just went with it without remembering that I still had TWRP instead of stock boot img installed. So when I locked the bootloader the phone booted into a screen similar to the unlocked Bootloader warning screen. But it said "Your Device is corrupt. It can't be Trusted and will not boot." Instead. So now I have locked bootloader with TWRP that I can't boot into. I still can boot into fastboot mode but I can't do much Because LoCkEd BooTlOaDeR. The only sulotion is to unlock the bootloader with an unlock key Which I don't have and flash stock boot. So please help. You'll be literally saving my life. This is my first thread ever on the internet so forgive me If I made any mistakes:laugh:
EDIT: I took my phone to the service centre near me and they were able to fix it
CommieTurtle said:
Yesterday, I was going to lock my bootloader to cell my Nokia 8 cuz' I needed money. Being the noobie that I'm I didn't have my unlock key saved anywhere. and couldn't get a new one because the stupid Bootloader unlock app doesn't work on Pie. I did know that locking the bootloader doesn't require a key. So I just went with it without remembering that I still had TWRP instead of stock boot img installed. So when I locked the bootloader the phone booted into a screen similar to the unlocked Bootloader warning screen. But it said "Your Device is corrupt. It can't be Trusted and will not boot." Instead. So now I have locked bootloader with TWRP that I can't boot into. I still can boot into fastboot mode but I can't do much Because LoCkEd BooTlOaDeR. The only sulotion is to unlock the bootloader with an unlock key Which I don't have and flash stock boot. So please help. You'll be literally saving my life. This is my first thread ever on the internet so forgive me If I made any mistakes:laugh:
EDIT: I took my phone to the service centre near me and they were able to fix it
Click to expand...
Click to collapse
Hello! I have the same problem! (((You were not interested in what exactly or how you should do to correct the error? And how much money did you get for repair?
Well you can use original OST not NOST and flash signed images (.NB1) without unlocking bootloader.
KonikoO said:
Well you can use original OST not NOST and flash signed images (.NB1) without unlocking bootloader.
Click to expand...
Click to collapse
Only with service point authorization as far as I know. OST (and NOST by extension) usually show you a login prompt when you launch them. Service Points login to a server that generates a temporary unlock key, which allows OST to reflash the partitions. With the proper authorization, even NOST could flash .qlz files (as long as the images inside are official and signed) with a locked bootloader.
Since we don't have service point permission we have to patch the tool to ignore it (both NOST and the hacked OST). It will still try to request the temporary key, fail, and pass an empty value to the bootloader. To get the bootloader to accept the following flashing commands, you have to unlock it.
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening