Database Info

[Q] Razr Maxx HD w/ unlocked Bootloader

Just purchased an HD MAXX from Ebay and the seller said it has a permanently unlocked bootloader and a custom ROM flashed. I'm upgrading from a Bionic that I rooted, installed SafeStrap and tried a few custom ROMs in the slots. I'm going to have the phone flashed over to Page Plus and the person doing the flashing told me it has to be on stock. The seller told me that the bootloader is permanently unlocked. The seller also told me how the bootloader was unlocked and I read something similar here that if it were unlocked at a certain point, or before a certain update was pushed out, it would be permanently unlocked,
I just don't want to screw anything up trying to flash it back to stock. It's running the TWRP custom recovery. I've flashed ROM's before, I've rooted phones before but from what I understand having a Razr with an unlocked bootloader is something special and I wouldn't want to screw that up. Thanks

SkyRocker_58 said:
Just purchased an HD MAXX from Ebay and the seller said it has a permanently unlocked bootloader and a custom ROM flashed. I'm upgrading from a Bionic that I rooted, installed SafeStrap and tried a few custom ROMs in the slots. I'm going to have the phone flashed over to Page Plus and the person doing the flashing told me it has to be on stock. The seller told me that the bootloader is permanently unlocked. The seller also told me how the bootloader was unlocked and I read something similar here that if it were unlocked at a certain point, or before a certain update was pushed out, it would be permanently unlocked,
I just don't want to screw anything up trying to flash it back to stock. It's running the TWRP custom recovery. I've flashed ROM's before, I've rooted phones before but from what I understand having a Razr with an unlocked bootloader is something special and I wouldn't want to screw that up. Thanks
Click to expand...
Click to collapse
The seller is correct. May 25 is dday for the ...79 build that locks the boot.
You do not state your build.
Get the latest twrp 2632 for a pocket proof noob recovery but for a successful cm 11 flash you need philz newest & philz 6079 for some flashes that err 7 on the 619 ver.
926 philz only comes in .img. Get recovery tools to load the img from homescreen. Philz is in the orig dev section.
When in doubt backup.
See my 907 stuff for lots similar things/guides that apply to the 926 as well.

SkyRocker_58 said:
Just purchased an HD MAXX from Ebay and the seller said it has a permanently unlocked bootloader and a custom ROM flashed. I'm upgrading from a Bionic that I rooted, installed SafeStrap and tried a few custom ROMs in the slots. I'm going to have the phone flashed over to Page Plus and the person doing the flashing told me it has to be on stock. The seller told me that the bootloader is permanently unlocked. The seller also told me how the bootloader was unlocked and I read something similar here that if it were unlocked at a certain point, or before a certain update was pushed out, it would be permanently unlocked,
I just don't want to screw anything up trying to flash it back to stock. It's running the TWRP custom recovery. I've flashed ROM's before, I've rooted phones before but from what I understand having a Razr with an unlocked bootloader is something special and I wouldn't want to screw that up. Thanks
Click to expand...
Click to collapse
as long as you have the drivers installed on your pc all you have to do is grab one of the utilities from the dev forum and flash it back to stock. there is also an option in there to put the stock recovery back on. its all plug and click.

Thanks guys!
Appreciate the replies and info. My main concern was doing something to possibly "re-lock" the bootloader. From what you're saying I shouldn't have any problems, flash it back to stock, flash it to page plus, flash custom recovery, start trying out ROM's lol
Thanks again!

Once the fuse is blown it cannot be "rearmed". But I've heard that there are couple of those in our RAZR. But I don't think vz or moto are interested in making our phones inoperable.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app

I can attest to the fact that once you unlock the bootloader, it won't get relocked since it's a physical change (blown e-fuse as others have mentioned).
I have flashed back to a previous stock, took the OTA and the bootloader was still unlocked.
However, never say never and when KitKat comes out for this phone, I will not be quick to install it. I will wait and see what everyone says before I accept it. No way I take an OTA that somehow finds a different way to lock the bootloader.

[Q] Unlock bootloader on XT926 rooted after JB OTA update 9.30.1

I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.

The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app

Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?

impinball said:
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?
Click to expand...
Click to collapse
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.

RikRong said:
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.
Click to expand...
Click to collapse
I have done absolutely nothing beyond rooting it, installing Superuser & SuperSU (both through a script I can attach, but I'm on the wrong computer), and backed up a slew of apps.
This first begun when I modified the script to fix a bug in it (ash in JB 4.2 doesn't have a -f switch in rm, and the script had a 'rm -f'). If that bug didn't exist, then it would've still happened the first of several times (I attempted it about 4-5 times, but only the last caused this). The rm -f was actually doing effectively (with successful root privileges) 'rm -f /system/install-script-2.sh', but the script actually had another script to be put into it at the location /system/install-script.sh.

???
Start by detailing steps in your 2nd paragraph.
Your boot is locked if it was never unlocked before you upgraded to ...79 or later

what a coincidence i just got a xt926 and im at the same spot.. 9.30.1 rooted but locked ... iguess we're screwed huh

impinball said:
I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.
Click to expand...
Click to collapse
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".

skeevydude said:
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).

impinball said:
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).
Click to expand...
Click to collapse
First, there is no Dev Edition Fastboot....the closest would be Bell ICS since Bell shipped unlocked/unlockable Atrix HD's.
You don't flash zip files with fastboot flash.....Why is this becoming an issue these days?* The kernel is "fastboot flash boot boot.img"
*just thinking out loud
EDIT: Just realized that this was the RAZR HD forums.....just replying to quoted posts this morning....Not sure about RAZR HD Dev Edition fastboots....

Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The shame is, I never cared about unlocking the bootloader, as I prefer to stick to OTA's, but I do require root. So that's all I've ever done. I'm successfully rooted with the locked bootloader on 9.30.1, but it seems (at least as far as I've read on here) that I'm stuck there as I can't go anywhere else and maintain root. Would love kitkat, but root is essential.

Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.

killrhythm09 said:
Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.
Click to expand...
Click to collapse
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.

crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk

iBolski said:
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
This. It's no coincidence that the xt925 can be unlocked through Motorola. Carriers are always the problem here in the US.

crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Well, in actual reality, the XT926 was never meant to be unlocked. It was only unlockable via an exploit, just like obtaining root for locked devices is an exploit in the security of the OS/device.
So, there never really was a "sunset" for unlocking this device as it wasn't meant to be. Only after the exploit was found did a patch come out to stop that exploit from being utilized on any remaining unlocked phones, current or future.
So, when there is an exploit to unlock a device, your best bet is to take advantage of it immediately.
When I got my RAZR HD, it was as a warranty replacement for my OG RAZR MAXX. When I fired it up, it stated there was an OTA available. I immediately told it no and then went straight to the forums here and on another site to investigate what my options were. When I found out that there was the possibility of my unlocking the bootloader, I immediately went to where the tool was and downloaded it. I then proceeded to read and then ask questions on if my phone couldn't unlock, would it hurt it. SamuriHL helped me out a great deal and that is how I found all his tools and how much help he provides. If it weren't for him, I wouldn't have discovered that I could unlock my bootloader.
Usually, I investigate the phone I'm interested in to see if:
1. Can the bootloader be unlocked (or is it already unlocked)?
2. Is there a known root exploit IF the bootloader cannot be unlocked?
3. What are the ROM options (safestrap, cwm, twrp recovery)?
It's definitely something I normally would look into, but I didn't know that I was going to receive the RAZR HD. Once I discovered the possibility of unlocking the bootloader, I was hoping beyond all hope that it could happen and it did. How I received a replacement phone that wasn't patched to the latest OTA was beyond me, but that is the reason I refused the OTA when I first fired up the phone. I had already read about other "horrors" of people taking an OTA and then finding they couldn't root or do other things with their phones.
Lesson learned is, NEVER take an OTA until you've fully researched what it does and what it might prevent.

Relocking Verizon Google Pixel (2016 Model)

Okay so I have spent over 2 hours looking to see if anyone has asked this, but cannot find an answer.
I have a Verizon Google Pixel it was on 7.1 when I unlocked the bootloader with DePixel8.
I have to return it and was wondering how do I relock the bootloader? Also do I need to be back on Android 7.1?
I have since unlocked the updated to android 8.0 (or w.e. the current version of Android is out.) while bootloader is unlocked.
(I AM NOT ROOTED NOR HAVE I INSTALLED ANY TYPE OF CUSTOM RECOVERY ONLY APPS FROM PLAY STORE)
Now one last thing. If I relock will I need to use the DePixel8 method again and give the command fastboot oem lock?
Any help is appreciated. And sorry for being such a darn noob. Kinda new to this.
P.S. forgive me if this was asked somewhere and I couldn't find it,

You should be able to run the command in bootloader mode "fastboot flashing lock" and then toggle oem unlocking in settings off if it isnt already.

i have bought several Pixels and Pixel 2s and they all have locked bootloader.

i have bought several Pixels and Pixel 2s and they all have a locked bootloader. as in, once developer mode is enabled, the OEM unlock option is greyed out. the tricks to unlocking verizon and ee pixels is no good any longer. i have tried ebay and amazon and returned phones because generally no one knows what the OEM unlock even is unless they are here on XDA reading about ROMs. what is the source for buying phones from knowledagle people? is there a sale forum i dont know about? a model number for a pixel or pixel 2 that comes OEM unlocked? its tedious to talk ebay sellers through enabling developer options and checking that toggle switch in the settings.
i am getting frustrated. my nexus 5x will only keep up so much longer.
thanks
d.

dcarrco said:
i have bought several Pixels and Pixel 2s and they all have a locked bootloader. as in, once developer mode is enabled, the OEM unlock option is greyed out. the tricks to unlocking verizon and ee pixels is no good any longer. i have tried ebay and amazon and returned phones because generally no one knows what the OEM unlock even is unless they are here on XDA reading about ROMs. what is the source for buying phones from knowledagle people? is there a sale forum i dont know about? a model number for a pixel or pixel 2 that comes OEM unlocked? its tedious to talk ebay sellers through enabling developer options and checking that toggle switch in the settings.
i am getting frustrated. my nexus 5x will only keep up so much longer.
thanks
d.
Click to expand...
Click to collapse
As long as you get a Google pixel rather than a Verizon model you should be able to unlock the bootloader.

You might have to connect it to the internet before you're able to toggle the OEM unlocking option. I've had to do this with two different Google model Pixels that I've used.

ok. ill just try to find one locally so i can see that it can be OEM unlocked. all the resellers on ebay and amazon refuse to enable developer mode and check that option.
thanks!

dcarrco said:
ok. ill just try to find one locally so i can see that it can be OEM unlocked. all the resellers on ebay and amazon refuse to enable developer mode and check that option.
thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Use the above link. I have a Verizon pixel and used this guide to unlock my phone on 9.0. Installed twrp and magisk with no issues.

excellent!
I have a pixel coming Friday because you have given me hope. I'll let you know. thank you.

GREAT! now...
@tecsironman
that's awesome. that method DOES work and I have managed to unlock the bootloader with that method. I have a couple more questions though. I ran TWRP through fast boot, loaded Lineage, then ran the Pixel TWRP installer. all good. but then a Lineage update came out and I installed it through TWRP and when I rebooted I had the Lineage recovery. do I have to reinstall the Pixel TWRP each time I update Lineage? this whole A/B partition thing is a mite bit confusing. I haven't figured out how to install the ElementalX kernel either (I like the power saving it gives me) because every time I install it I get a bootloop....
anyway any advice appreciated,
thanks again
d.

dcarrco said:
@tecsironman
that's awesome. that method DOES work and I have managed to unlock the bootloader with that method. I have a couple more questions though. I ran TWRP through fast boot, loaded Lineage, then ran the Pixel TWRP installer. all good. but then a Lineage update came out and I installed it through TWRP and when I rebooted I had the Lineage recovery. do I have to reinstall the Pixel TWRP each time I update Lineage? this whole A/B partition thing is a mite bit confusing. I haven't figured out how to install the ElementalX kernel either (I like the power saving it gives me) because every time I install it I get a bootloop....
anyway any advice appreciated,
thanks again
d.
Click to expand...
Click to collapse
That I would not know. I'm not running any ROMs other than stock with twrp and magisk.
I would go into the appropriate ROMs thread for your question.

dcarrco said:
@tecsironman
that's awesome. that method DOES work and I have managed to unlock the bootloader with that method. I have a couple more questions though. I ran TWRP through fast boot, loaded Lineage, then ran the Pixel TWRP installer. all good. but then a Lineage update came out and I installed it through TWRP and when I rebooted I had the Lineage recovery. do I have to reinstall the Pixel TWRP each time I update Lineage? this whole A/B partition thing is a mite bit confusing. I haven't figured out how to install the ElementalX kernel either (I like the power saving it gives me) because every time I install it I get a bootloop....
anyway any advice appreciated,
thanks again
d.
Click to expand...
Click to collapse
Yes, you will have to reinstall TWRP each time you update the OS on devices with A/B partitions. The reason is because these devices do not have a recovery partition. What we think of as recovery is actually part of the boot.img file. When you update the OS, you update the boot.img. The TWRP installer .zip finds and unpacks the boot.img, then modifies it to make the device load TWRP instead of stock recovery. By default, the TWRP installer installs to both A & B partitions. If you screw something up (like flashing the wrong version of TWRP, for example) and put yourself into a bootloop, you can often recover by simply flashing the original boot.img file with fastboot flash boot boot.img .

Isn't locked, unlocked?
I thought that if the OEM unlock option was grayed out and switched on that the bootloader was already unlocked and the only option to turn OEM unlock off is to relock the bootloader.

8T TMobile Unlock Oddities

Hi guys! Having some weird issues getting custom roms to flash on my 8T. I purchased the TMobile variant as it was the only one in stock, and I planned to use it with a TMobile mnvo. It's the KB2007 model. I purchased it outright, and went to unlock the bootloader - this was not possible as the device was locked. I reached out to TMobile on Twitter, gave them my phone number, IMEI and told them my story. They said it would take 2-5 business days for the unlock team to look at the request as I wasnt a direct TMobile customer. A few days later, I went into the android settings app, and attempted to permanently unlock the device and it unlocked. I rebooted and was able to toggle the developer setting to allow OEM unlocking, yay! Since that point, I've ran the kebabt -> kebab EU firmware MSM tool to convert the device to the EU firmware (as I've heard it's more stable, I'm US based though)
However, after that I've gone to replace oxygen os with Lineage, and I'm getting errors from fastboot about the device still being locked. Any ideas where to go from here?

You probably need to unlock your bootloader?
fastboot flashing unlock

AlmightyGrapefruit said:
Hi guys! Having some weird issues getting custom roms to flash on my 8T. I purchased the TMobile variant as it was the only one in stock, and I planned to use it with a TMobile mnvo. It's the KB2007 model. I purchased it outright, and went to unlock the bootloader - this was not possible as the device was locked. I reached out to TMobile on Twitter, gave them my phone number, IMEI and told them my story. They said it would take 2-5 business days for the unlock team to look at the request as I wasnt a direct TMobile customer. A few days later, I went into the android settings app, and attempted to permanently unlock the device and it unlocked. I rebooted and was able to toggle the developer setting to allow OEM unlocking, yay! Since that point, I've ran the kebabt -> kebab EU firmware MSM tool to convert the device to the EU firmware (as I've heard it's more stable, I'm US based though)
However, after that I've gone to replace oxygen os with Lineage, and I'm getting errors from fastboot about the device still being locked. Any ideas where to go from here?
Click to expand...
Click to collapse
You will get fastboot errors about unlocking critical partitions if you try to flash partitions other than boot, recovery and a few others while you're in bootloader mode.
For the rest you must be in fastbootd mode.

Chances are you need the unlock token from OnePlus themselves it takes a week