Related
Hello everyone,
i do not understand despite having read the dedicated thread, because you have to downgrade from version .29 or .26 to .17 for the root my asus was to version .29, I unlocked the boot with the asus app, I flashed the recovery and installed it. zip to the root that benefits from the downgrade? thanks to who answer me and sorry for my English
savioonline said:
Hello everyone,
i do not understand despite having read the dedicated thread, because you have to downgrade from version .29 or .26 to .17 for the root my asus was to version .29, I unlocked the boot with the asus app, I flashed the recovery and installed it. zip to the root that benefits from the downgrade? thanks to who answer me and sorry for my English
Click to expand...
Click to collapse
Some people would prefer not to unlock their bootloader. If you aren't installing a custom rom, but you would like to root, it makes more sense to obtain it without voiding your warranty.
So if I understand correctly, is a way to have the root without unlocking the bootloader, right?
Yes and no,
If you happen to have an US version, then ...yes
If you happen to have an WW version, then ... no (that is the conclusion at this moment anyway, untill someone finds a WW .17 blob file)
And as far as I could understand, it's the same thing with the DE version.. not possible
For WW en DE owners root only seems to be possible through unlocking the bootloader and using the ClockWorkMod (or something similar).
And unlocking = void warranty
ok thanks ... now my warranty is gone
I hope to start making games gameloft currently incompatible: (
If anyone has any creative ideas on how to extract the 17 WW blob from a device, there is a whole thread of people on 17 WW here (although not much longer) who are waiting for OTAs:
http://forum.xda-developers.com/showthread.php?t=1647649&page=3
TXKSSnapper said:
Some people would prefer not to unlock their bootloader. If you aren't installing a custom rom, but you would like to root, it makes more sense to obtain it without voiding your warranty.
Click to expand...
Click to collapse
so that means you don't lose your warranty if you root it?
i didn't know this
nooktablet said:
so that means you don't lose your warranty if you root it?
i didn't know this
Click to expand...
Click to collapse
I think you can lose your warranty if they can tell you rooted your device, for example you send your tablet for a RMA because is doing weird stuff and you forget to remove root (this is pure speculation). In any case root is easily removable.
I have an AT&T HOX. Came stock with 1.85.
I rooted it using the "redbend" method described here (http://forum.xda-developers.com/showthread.php?t=1709296)
(More or less, the pulling SIM card business wasn't part of the steps when I used it, but the root was successful).
I am using SuperSU to manage root access by apps.
I have not done anything beyond that.
Now, I understand, at some point, AT&T is going to force a 2.20 update on me.
My primary concern is to avoid losing root.
(I have enabled the "preserve root across OTA" in SuperSU, but not sure if its effective or not)
I've looked at the howto's for SuperCID, unlocking the bootloader, etc, and I'm not sure which I NEED, and which are optional, and/or what the pros/cons are of each...
I'd like to stay as close to "stock" as possible, but I want to ensure that I can keep root.
I'm still within my AT&T contract, and would really prefer to avoid bricking the phone.
I'm wondering what the recommendations are as to the minimum steps I should take to keep root in the event the OTA is forced on me?
Can I pre-empty the OTA by installing this? ( http://forum.xda-developers.com/showthread.php?t=1812459 )
If so, what is the safest method for installing it?
FWIW, I am a linux user, and I am comfortable with adb as well as the command line on the phone itself.
I have no windows systems, so any special tools I'd need other than adb I'd have to find a linux version.
I don't need "one click" methods, in fact I'd prefer to see/perform the individual steps and understand what they are doing.
unlock your bootloader using this method http://forum.xda-developers.com/showthread.php?t=1672284 if you don't you wont get root again afterwards.
Dont have to unlock to flash roms?
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
My ATT HOX is currently rooted, and I now have SuperCID. I assumed I would need to unlock my bootloader, but I havent done that yet.
Can I install this:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Megadave123 said:
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
Click to expand...
Click to collapse
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Megadave123 said:
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
Click to expand...
Click to collapse
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Megadave123 said:
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Click to expand...
Click to collapse
SuperCID survives OTA. But the 2.20 OTA has a new hboot, which fixes the hole by which kernels and radios can be flashed from recovery, so my recommendation would be not to install the OTA.
redpoint73 said:
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Click to expand...
Click to collapse
FWIW, I didnt google that site. It was linked to from an XDA post. I't didnt seem right to me, which is why I asked here
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Click to expand...
Click to collapse
Ok, that is VERY good to hear.
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Megadave123 said:
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Click to expand...
Click to collapse
I think bypassing the user acceptance dialogues for the OTA install would be a violation of how Android fundamentally works. It would be a serious security issue, as it might allow rogue software to be installed on your device without your interaction. I seriously doubt AT&T would institute such a thing.
The user confirmation of the OTA might be a liability thing, too. If the performance of the device is adversely affected by the OTA (happens to some people) and the OTA was forced by AT&T without the owner having a choice, it would seem to me that AT&T has to accept the responsibility. People can claim its AT&T's fault, and demand a replacement device (since AT&T technically installed the software remotely). By making you confirm the OTA installation (and giving you the chance to opt out), you pretty much are volunteering to install the software and accept the consequences.
In theory, unlocking the bootloader voids you warranty. But more than a few folks on here have gotten warranty replacements from AT&T (after unlocking the bootloader), without issue. Sometimes in-store (within the first 30 days) without them even checking for the bootloader unlock. No guarantee that this will always be the case. But just throwing it out there. Its still up to you whether unlocking the BL is worth the risk in your own case.
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
18th.abn said:
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
Click to expand...
Click to collapse
The hoxl is officially supported by twrp and can be downloaded from goomanager. I do not know if you can install a custom recovery without an unlocked bootloader. I would be interested to know if this can be done as well.
Sent from my Nocturnalized One XL using Forum Runner
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Is there any harm in trying it?
If I install "goo manager", and let it do its thing, and the locked bootloader prevents it from doing so, there wont be any other side effects, will there?
If I come off as a complete noob at this - its because I am..
This is my first Android phone, and I *really* want to avoid bricking it, so I want to make sure I understand as much as possible before I go
trying to do anything to it.
Also I'm still wary of unlocking, mainly because of the whole "will erase your phone" bit.
I'm not yet fully comfortable that I know how/what to fully backup all of "my" data on the phone so as to facilitate easily putting it all back.
I'll answer some q's here.
1.) you cannot flash a custom recovery from hboot with a locked bootloader
2.) you CAN dd a custom recovery with a locked bootloader. However your device will be soft-bricked.
3.) you CAN install custom ROM's via dd right from android. This is how we did it back "in the day".
4.) you "might" be able to get away with dd'ing a custom kernel with locked BL, not not sure. In fact, I'd bet it will softbrick now that I think about it.
Anyways, the SAFEST way to do it is via unlocking the bootloader and installing your roms from custom recovery.
gunnyman said:
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Click to expand...
Click to collapse
Beaups pretty much already answered it. But this guy tried installing TWRP thru goomanager with a locked bootloader, and confirmed it doesn't work: http://forum.xda-developers.com/showthread.php?p=31220704#post31220704
Hey I've had my tablet since release and have been updating it incrementally as the updates came out while progressively watching the Android Dev. section for progress on the custom recoveries and custom ROMs.
My question today is, how do I, if it's possible with any current rooting method(s), root my TF700T? Do I still need to use the ASUS bootloader unlocking tool or is there an alternative that doesn't use their unlocking tool?
Thanks
incarceration said:
My question today is, how do I, if it's possible with any current rooting method(s), root my TF700T? Do I still need to use the ASUS bootloader unlocking tool or is there an alternative that doesn't use their unlocking tool?
Click to expand...
Click to collapse
You can downgrade to ICS, then root, use OTA RootKeeper, and apply incremental updates via the dlpkgfile method (manually applying OTA updates). There is a thread somewhere on this forum that explains how to do it, just use the search function.
Yeah I've seen that; I was just curious if there was anything else that I may've missed.
Thanks for your response
From what I have read, the answer is no but I have some more questions so I guess Id ask anyway.
Transformer was very expensive and I have more than a year of warranty left. On the other hand I would very much like some of the features that require root. What action is possible to roll back? Unlocking, rooting or flashing a custom rom? I need to unlock the device before I can root it right?
I would use a number of features that rooting allows, but my main desire is to be able to use keyboard dock and mouse or even a gamepad as game controllers. Only program that can do that (joy2touch) requires root. But if I had root I guess I would try Cyanogenmod too because I can only see people praising it for how greatly it improves experience.
Also, there is lots of information around here but its still not dumb enough for someone who just wants to root a device but has no idea where to start (its pretty confusing). So sorry in advance for possibly asking obvious questions.
3DeX said:
From what I have read, the answer is no but I have some more questions so I guess Id ask anyway.
Transformer was very expensive and I have more than a year of warranty left. On the other hand I would very much like some of the features that require root. What action is possible to roll back? Unlocking, rooting or flashing a custom rom? I need to unlock the device before I can root it right?
I would use a number of features that rooting allows, but my main desire is to be able to use keyboard dock and mouse or even a gamepad as game controllers. Only program that can do that (joy2touch) requires root. But if I had root I guess I would try Cyanogenmod too because I can only see people praising it for how greatly it improves experience.
Also, there is lots of information around here but its still not dumb enough for someone who just wants to root a device but has no idea where to start (its pretty confusing). So sorry in advance for possibly asking obvious questions.
Click to expand...
Click to collapse
If you just want root to use joy2touch, then your warranty is still good. If you unlock your device, then your warranty is voided... you can find more information about unlock and root here.
http://forum.xda-developers.com/showthread.php?t=1833212
Good luck..:fingers-crossed:
Yes but, there is rooting for either unlocked devices or devices running ICS or lower. And whatever rooting for JB I found (im running newest OTA) is only for unlocked devices as well. As I understand it, rooting does not void the warranty but unlocking does? Does that mean im screwed? I dont even know the difference between unlocking and rooting...
3DeX said:
Yes but, there is rooting for either unlocked devices or devices running ICS or lower. And whatever rooting for JB I found (im running newest OTA) is only for unlocked devices as well. As I understand it, rooting does not void the warranty but unlocking does? Does that mean im screwed? I dont even know the difference between unlocking and rooting...
Click to expand...
Click to collapse
A rooting is allowed you to access your system files so you can modify them as will. A unlocking is allowed you to install custom rom and recovery. Someone else may have a better explaination for you.
No, you still can root your device if you have a bootloader .8 or earlier. If you have the latest bootloader, you can downgrade and root it..
LetMeKnow said:
No, you still can root your device if you have a bootloader .8 or earlier. If you have the latest bootloader, you can downgrade and root it..
Click to expand...
Click to collapse
Rooting exploits a bug in the kernel, not in the bootloader, so it's the ROM/kernel build 10.6.1.14.8, not the bootloader build. But it's always the same on locked devices anyway.
Uhm... you are confusing me even more. So is there a rooting guide that doesnt involve unlocking, can be reverted or doesnt void warranty, and works with newest stock OTA?
To my knowledge I dont have any kind of bootloader.
_that said:
Rooting exploits a bug in the kernel, not in the bootloader, so it's the ROM/kernel build 10.6.1.14.8, not the bootloader build. But it's always the same on locked devices anyway.
Click to expand...
Click to collapse
Thanks _that. What I meant is the latest firmware from Asus.
@3DeX
1. Download the Asus firmware 10.6.1.14.8
2. Backup your personal data and everything that you like to keep to your computer or your external SD.
3. Make sure that your battery is full so it is not shutdown during the installing process..
4. Unzip it once because there is another zip file insde it.
5. Copy the second zip file to the root directory of your internal SD.
6. Reboot your tablet.
7. After reboot, you will see the downgrade notification in the lower right corner.
8. Click on the downgrade notification and follow the instructions.
9. During the installing process, Do not try to turn it off. It will reboot by itself when the installation is completed. It may take 2 to 3 minutes..
10. Use motochopper to root your device.
Good luck..
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.