[GUIDE]Unlock Bootloader - Moto X (2014) [PURE VERSION ONLY] - X 2014 General

UNLOCK YOUR BOOTLOADER​
THIS IS FOR PURE VERSION ONLY
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto X(2014).
To relock the bootloader:
Go to Fastboot and give the command fastboot oem lock
You can always appreciate my work by pressing the Thanks Button.:good:
Good Day

[SIZE=+1]Q1:How to remove the unlocked bootloader message? [/SIZE]
Download the zip.
Extract all the files
Reboot to fastboot mode (power + vol down)
Now open cmd and use cd command to go to the directory where you placed the file.
Now Type the command: fastboot flash logo logo.bin
Reboot from the recovery (use vol up to select and vol down to navigate)
Now your bootlogo should be restored back to the normal version
Thanks Helvio88 for the zip

I assume this is for Pure version only.

mtoomey79 said:
I assume this is for Pure version only.
Click to expand...
Click to collapse
Yes for now.

Falcon G said:
Yes for now.
Click to expand...
Click to collapse
Is there any feeling if the bootloader on the VZW model will be able to be unlocked?

mtoomey79 said:
Is there any feeling if the bootloader on the VZW model will be able to be unlocked?
Click to expand...
Click to collapse
If a good developer finds a way to unofficially unlock it or motorola gives us an official way to unlock maybe after a year. But I can't say for sure

HTH
FACTORY IMAGES FOR DEVELOPER EDITION DEVICES

Hello, the last Bootloader Unlock i did was with Moto X 2013, in order to root it. Then i switch to Galaxy S5 and Sony Z2, both didnt need the Bootloader unlocking, so i kinda forgot what the unlocking is for. Is it to install CWM or TWRP and install custom roms ? I just need rooting ,so i think there isn't one right?
Thanks.

Galinha1 said:
Hello, the last Bootloader Unlock i did was with Moto X 2013, in order to root it. Then i switch to Galaxy S5 and Sony Z2, both didnt need the Bootloader unlocking, so i kinda forgot what the unlocking is for. Is it to install CWM or TWRP and install custom roms ? I just need rooting ,so i think there isn't one right?
Thanks.
Click to expand...
Click to collapse
Yes you need unlocked bootlader in order to install custom Roms recovery

A few questions:
1) I thought Pure had an unlocked bootloader, or is it "unlockable"?
2) Any reason not to do this on day 1 since it wipes the device? Moto has indicated unlocking the bootloader does not void your warranty on Pure.

km8j said:
A few questions:
1) I thought Pure had an unlocked bootloader, or is it "unlockable"?
2) Any reason not to do this on day 1 since it wipes the device? Moto has indicated unlocking the bootloader does not void your warranty on Pure.
Click to expand...
Click to collapse
It's unlockable. It doesn't come unlocked. The phone comes carrier unlocked.

@Falcon G i thought it was confirmed that unlocking the bootloader on the Moto X (2nd Generation) doesn't void the warranty

:laugh:cool

mrvirginia said:
@Falcon G i thought it was confirmed that unlocking the bootloader on the Moto X (2nd Generation) doesn't void the warranty
Click to expand...
Click to collapse
That would entirely depend on if they consider the Pure Edition a Developer Edition.
The Legal Agreement and Warning on the unlock page still states as follows:
(5) 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 THAT MAY HAVE BEEN PROVIDED BY MOTOROLA, BOTH EXPRESS AND IMPLIED, INCLUDING ANY WRITTEN WARRANTY THAT ACCOMPANIED THE DEVICE AT THE TIME OF PURCHASE OR DELIVERY, AND AGREES THAT ANY RIGHTS OR REMEDIES PROVIDED BY SUCH A WARRANTY ARE NULL AND VOID. MOTOROLA MAKES NO WARRANTIES OF ANY KIND AND DISCLAIMS ALL WARRANTIES OF EVERY KIND, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE IN CONNECTION WITH AN UNLOCKED DEVICE. USER ACKNOWLEDGES AND AGREES THAT ALL SUCH WARRANTIES ARE HEREBY EXCLUDED AND THAT ALL UNLOCKED DEVICES ARE PROVIDED "AS IS," WITH NO WARRANTY OF ANY KIND;
Click to expand...
Click to collapse
So even if they did SAY that, with the wording of the agreement, technically they wouldn't have to honor it until they add Pure Edition into that agreement.
I believe I heard the same somewhere as well about it not voiding the warranty, but I haven't been able to locate it.

km8j said:
A few questions:
1) I thought Pure had an unlocked bootloader, or is it "unlockable"?
2) Any reason not to do this on day 1 since it wipes the device? Moto has indicated unlocking the bootloader does not void your warranty on Pure.
Click to expand...
Click to collapse
I've done this (or some variation) for every phone that needed it the second they came out of the box. It's easier if you do it before you mess with the phone at all since you'll have to start over anyhow.

So I just chatted with a support person, and after asking the question 4 different ways, I got her to say
Me: So I will maintain my warranty then if I unlock it?
Agent: Yes. The pure edition is unlock. Let's say it's like a developer edition.
Click to expand...
Click to collapse
Now all we need is a root method

fortinj1354 said:
So I just chatted with a support person, and after asking the question 4 different ways, I got her to say
Now all we need is a root method
Click to expand...
Click to collapse
There already is one. I am rooted right now
sent from my Moto X (2014)

link please?
0.0 said:
There already is one. I am rooted right now
sent from my Moto X (2014)
Click to expand...
Click to collapse
Link please or it didn't happen

Is unlocking the bootloader or at least rooting possible on Verizon?

flyinggerbil said:
Link please or it didn't happen
Click to expand...
Click to collapse
If you have the Pure Edition, you can. Just search the forums. But here is a link http://forum.xda-developers.com/showthread.php?t=2887452
sent from my Moto X (2014)

Related

[WARNING] Do NOT lock your bootloader when on Android 5.1

The new Device Protection features of Android 5.1 on the Nexus 9 and Nexus 6 can, in certain cases, cause you to have a bootloader which can not be unlocked.
Please have a read of the following links:
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
What a pita
Sent from my Nexus 5 using XDA Free mobile app
i would never relock my bootloader
people unlock there bootloader for a reason
but to relock it after thats just wrong...
thats one of the things i hate about CM
they recommend you to relock your bootloader...
Agreed, why would you lock your bootloader unless sending in for repairs maybe?
But Google is really messing up the flow. The nexus 6 5.1 OTA is a mess right now but I will leave that for another thread.
Android 5.1 for Nexus 9? You must be joking.
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
No no you can still unlock it
But if you relock it that's the problem
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
efrant said:
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
Considering this is a tablet, hopefully I won't lose or misplace it
Thanks, guys! Glad I stumbled across this thread before the thing arrived.
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
doitright said:
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
Click to expand...
Click to collapse
Example: I have a device running a stock ROM with no encryption, the stock recovery and a lock screen password. I happen to lose my phone. What happens to the photos of me dancing to Old Time Rock & Roll in my underwear that are stored on the device? If the bootloader is unlocked, someone just plugs it into a PC, boots TWRP and pulls them off. If the bootloader is locked, there is no easy way to see or get the photos off the device.
That is all I was saying about security. Nothing to do with you leaving your device somewhere or losing it, and then finding it again. Strictly about the personal content on the device.
efrant said:
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
bailyc said:
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
Click to expand...
Click to collapse
If you have never booted into Android, then you don't need to check that setting. As I said, that's the way I did it on my N6: take out of box -> charge -> boot directly into bootloader -> "fastboot oem unlock". No other steps required if you don't boot into Android first.
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
lilliput222 said:
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Yes, that should work for the N9 as well.
The bootloader on my Nexus 9 Android 5.1.1 is locked forever due to my mistake
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to check "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
quekl84 said:
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
Not possible. You will have to return it to HTC for repair or replacement.
quekl84 said:
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to uncheck "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
cobyman7035 said:
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
Click to expand...
Click to collapse
Yes, I forgot to check the box to allow oem UNLOCK. And now my device is locked forever.
A quick question: A lot of N9 ROMs require flashing an updated bootloader from the factory image. Aren't these bootloaders locked by default? Can we flash a factory bootloader over a custom ROM?
It seems that we might bork our Nexus 9s if we flash a locked bootloader in.

How to unlock bootloader (tutorial)

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?

Re-Lock the bootloader

Is there any possible way to re-lock my bootloader and get back the warranty of my device?
Some buddy posted in my Kernel's thread that you should be able to do:
fastboot reboot oem-lock
But idk if this has some kind of sense and after unlocking BL your device is marked as non-appliable for warranty in Moto's database.
https://firmware.center/firmware/Motorola/Moto G4 Play/
Go to here and find right for your moto g4 play edition. And flash.
Sent from my XT1068 using Tapatalk
abhimanyuk said:
Is there any possible way to re-lock my bootloader and get back the warranty of my device?
Click to expand...
Click to collapse
Don't, after unlock you lose the warranty, if you re-lock after, the bootloader status don't go back to when you buyed the device (In the same way it says unlocked in the bootloader, it also says that it has been relocked), so it's useless.
And like facuarmo said:
facuarmo said:
Your device is marked as non-appliable for warranty in Moto's database.
Click to expand...
Click to collapse
Yeah, you can't get your warranty back once you've unlocked the boot loader. The fastboot command mentioned above can be used to re-lock your boot loader but that won't bring back warranty of your device.

[Root && Unlock] Droid Turbo 6.0.1 mcg24.251-5-5

@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
fastboot oem config fsg-id " "
Click to expand...
Click to collapse
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
ChazzMatt said:
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
Click to expand...
Click to collapse
mcg24.251-5-5
Fantastic. Yeah, I figured that had to be typo.
Will make a lot of people happy.
I will try now
KARIM9377 said:
I will try now
Click to expand...
Click to collapse
Yes, great news, right?
jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
TheSt33v said:
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
Click to expand...
Click to collapse
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Oh My Lord. @jcase and @autoprime do it again! Even though mine is unlocked my replacement 32gb isnt and this may make me buy a new screen for it to use! Looks like i know what im doing on my day off tomorrow. Transplanting this screen back onto its orginal donor and unlocking that sucker
autoprime said:
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Click to expand...
Click to collapse
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
no, pressing volume down or vol dwn + pwr should not interfere with sunshine.
whichever method people find easier.. i'd assume not everyone will be able to catch it on the initial reboot after sunshine completes.
i'd just avoid pressing buttons while sunshine is still running.. but once the screen shuts off have at it.
also, not sure how it is with the turbo but on my g4 play i do not have to force a 'power down' while phone is in bootloop. i just wait for bootloop cycle to turn screen off and then quickly press the button combo to go into fastboot (volume down + power for g4 play).
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
killer520 said:
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
Click to expand...
Click to collapse
ChazzMatt said:
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
Click to expand...
Click to collapse
Those instructions were in autoprime's OP, so they did make it into my guide.
need more help
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
KARIM9377 said:
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
Click to expand...
Click to collapse
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
TheSt33v said:
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
Click to expand...
Click to collapse
thanks for your help
can you please update the TWRP
KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
What @TheSt33v said.
This link is to the most recent TWRP with @bhb27 mods for our Quark phones. @bhb27 is our official TWRP maintainer. He's why our TWRP has official status. But he also builds personalized versions which include some features/mods for our phones that other TWRP versions do not have, mods specifically for our Quarks. His modded versions are always better than the versions on the TWRP website (which again are only there due to his efforts).
On that page below you want the modded TWRP with the most recent date -- will always be the one listed at the bottom.
https://www.androidfilehost.com/?w=files&flid=39562
need help
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
i need stack firmware to flash it with my locked droid turbo xt1254 MCG24.251-5-5 with tool to falsh it

Have an unlocked bootloader - how to re-lock? Google Pay fails because of it?

I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
back to official rom, before that
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
r_w said:
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
Click to expand...
Click to collapse
Look at the other threads about rooting.
You can do a couple of things to solve the issue:
Install ElementalX kernel
Install Magisk
VoidWalkerAlpha said:
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
Click to expand...
Click to collapse
Perfect! Flashed the latest original from Essential per HapRow's comment, pulling from Essentials current build website.
Had to wait a long time to restore everything. Then the "fastboot flashing lock" erases everything, so I had to restore again.
Took a while, but was thankfully uneventful.
And now Google Pay works!
Thank!

Categories

Resources