Database Info

How to stop an OTA update?

Okay first off, i know this is the wrong section. I can not post in development because I am new here, but I am in need of help desperately. Okay so I am rooted on 1.85 and the bootloader is NOT unlocked. Well i decided today to take the update to 4.0.4 before I did research. (Stupid me eh?) Well I start the OTA and then do some research. I learn that the update to 4.0.4 might be harmful to rooted users. So I disconnect from WiFi knowing it will pause the download. Well now I have a download that is just paused in the notification bar, and any time i connect to wifi it will continue the download. While the download is paused, can i unroot and take the update safely? I have seriously been searching for hours on end to find someone with a situation that I am in and i can not.

If you do a factory reset the update will go away. But that would also make you loose root. You should unlock the bootloader, then flash the rooted 2.20 update from the dev section.
Sent from my HTC One XL using xda app-developers app

Yep, get that bootloader unlocked immediately and flash a rooted stock ROM or a custom ROM. Make sure you backup all your stuff with Titanium because the bootloader unlock will wipe your phone.
Also, just so you know, this thread most definitely did NOT belong in development, which is reserved for ROMs and kernels and root guides and the like ONLY. Threads like this belong in Q+A but nobody is gonna kill you for posting it in General.

After the download, you should get a prompt to either Install, Postpone, or you can press the "back" capacitive button to cancel. Cancel should stop the update notifications. At least this is how its worked on past HTC OTAs. I personally can't verify, as I haven't gotten the notification yet. But others seem to verify this: http://forum.xda-developers.com/showthread.php?t=1817429
But if you want to be safe, you should SuperCID and unlock bootloader first, as others have suggested. Pressing the wrong button for the method I suggested above will be catastrophic otherwise (lose the ability to root and unlock BL).

Thanks for your help guys!
I just did a factory data reset on my phone. Honestly, I've gotten myself into trouble with rooting. I really need to read up before i continue with things of this sort. So since i did a factory data reset, am i 100% unrooted? Will i be safe to take the OTA now? Thanks for your help guys!

If you were stock 1.85, and rooted using the one-click or "manual" method (which you must be, if you you are still BL locked), then you are now unrooted. You are either rooted or not, there is no "percentage" of rooted.
What kind of trouble have you gotten into rooting, and what do you typically use root for?

I've been debating on whether or not to just go ahead and install the OTA to 2.2. The only thing I've used for root was for WiFi-Tether and I don't even use that anymore so I think I don't even necessarily NEED root anymore. I'm just tired of the updater telling me there's a new update to install - frankly very annoying. I've been just using the back capacitive button to cancel it. BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?

extol1337 said:
BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
Click to expand...
Click to collapse
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.

redpoint73 said:
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
Click to expand...
Click to collapse
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...

extol1337 said:
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
Click to expand...
Click to collapse
Is the update actually downloaded to your phone? You may need to locate and delete it.
It may be trying to install the OTA from recovery, which makes sense. Don't actually know what happens when an OTA installs.
I've never installed an OTA! I'm always rooted, always will be!!!!

Just to be sure.
I did a factory data reset the night of the problem, been good ever since! I have not done anything to the phone except install a few apps. Should i be okay to take the OTA now? Sorry i just really want to be sure. This is my 3rd phone is 3 months so... no second chances.

SOLVED
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:

Did everyone got an update ?
I still do not see update notification
From beast called HTC One X

It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.

wantabe said:
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
Click to expand...
Click to collapse
Excellent info!

ssteven232 said:
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Click to expand...
Click to collapse
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app

borets.boris said:
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced). One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone! My quadrant went up 800 points and battery life is still ridiculously good! I also have to agree with "I can't own an android without root access" especially on AT&T. Personally I'm good to go until the Jelly Bean update! Decisions, decisions! :laugh:

wantabe said:
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced).
Click to expand...
Click to collapse
I've never installed an OTA, so I wouldn't know either. Honestly, I don't know why one would do that, when the awesome devs here post ROMs with the latest OTAs and root prebaked into them. There are "modded" ROMs and "stock" (or close to stock) ROMs available to everyone's taste.
wantabe said:
One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone!
Click to expand...
Click to collapse
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
wantabe said:
My quadrant went up 800 points and battery life is still ridiculously good!
Click to expand...
Click to collapse
Where was your improvement? Did the increase happen in the aspect/area that directly affects your daily use, or in some esoteric algorithm that the phone all of a sudden processes faster? I used to go crazy on quadrant scores, but now I don't really understand their value/accuracy. As long as the phone feels buttery smooth while lasting 5+ hours of screen time, I'm happy!
Since you're interested in the scores, I installed quadrant and ran it, so you can compare.
Sent from my HTC One X using xda app-developers app

in admiration, totally confused!
borets.boris said:
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
Click to expand...
Click to collapse
Hi, do you think you could point me in the right direction for this? I found the general thread on radios, but am at a total loss about what it means or what to do with it!

You knew this was the wrong section but posted here anyway? Not a good way to start your membership on XDA. First rule of thumb is to search before creating a thread. Google is a great source for information. For future reference, all questions belong in the Q&A section, where coincidentally, this is being moved to.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.

update to 4.3 unsuccessful ?

i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
(wasnt really expecting to get the update at all with a rooted phone)

also i cannot get into supersu cause my phone is still recongnized as 4.3 instead of 4.1.2
...not really sure what to do

Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3

SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update

KabuTheFox said:
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
Click to expand...
Click to collapse
Nah, you'll have a hardbricked phone with seemingly no way to fix it if you attempt to downgrade. If/when VRUCML1 stock tar file is posted then you could flash that in Odin. What you'll need is something specifically for TW 4.3 whether that's root, root/unlock, or Odin. Nothing older is compatible.

KabuTheFox said:
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
Click to expand...
Click to collapse
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.

Thanks Slim !!
:good::good:
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
SafeRoot was a success and I now have a rooted device. I just purchased this used and it did an automatic update when i turned it on. Pretty bummed about now being able to switch out the ROM, but at least I've got root now! saferoot is awesome!

aarontsuru said:
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Click to expand...
Click to collapse
the update database doesnt recongize my phone tho, and thats why it couldnt complete the update.
but according to my phone im still on 4.3 technically
it has been some time, there might already be something out for all i know by now

De-bricking time!

Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!

killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7

There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app

phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too

codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.

codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.

killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part

XT926 Razr Maxx HD rooted but locked HELP

Hey everyone so i have a XT926
System version 9.18.79.XT926.Verizon.en.US
Android version 4.1.2
Build 9.8.1Q-79
Boot Mode 10.9B
AP Fastboot flash (device is locked status code 0
So about 6 months ago i tried to root and unlock phone, i rooted fine but messed up on the unlock. And the phone was stuck in boot loop. anyways i was able with help from here on XDA get it out of boot loop and working. My issue is a couple things.
1. Can it be unlocked (i have read and read and dont believe its possible)
2. It wont do a factory hard reset it errors out and just reboots.
3. I try to do the OTA and it just get the android guy with the red triangle and then reboots.
4. when i hold volume up and power and get the factory reset, normal boot etc options, any i select just reboot phone.
I would like to do 1 of the following things. and would prefer 1.:
1. if possible unlock and install custom rom.
2. Do the OTA update and have a fresh install
3. Do a factory wipe and sell phone.
Please any help would be great, as the phone has gotten super slow and i usualy like to do a factory reset every 4-5 months to wipe it.
thanks

#1= not possible on your build. you can only install safestrap roms which are limited and most commonly found over on razr forum.
to clean it up and go back to stock you could either, use rsd to reflash stock, or grab the one click utility from the dev forum to do the same. the one click utility is the easiest of the 2, just be sure to get the build that matches your system version or newer. you can flash the same version or newer only, trying to flash an older version will just result in a boot loop.

bweN diorD said:
#1= not possible on your build. you can only install safestrap roms which are limited and most commonly found over on razr forum.
to clean it up and go back to stock you could either, use rsd to reflash stock, or grab the one click utility from the dev forum to do the same. the one click utility is the easiest of the 2, just be sure to get the build that matches your system version or newer. you can flash the same version or newer only, trying to flash an older version will just result in a boot loop.
Click to expand...
Click to collapse
Are you talking about DROID RAZR HD Utility 1.21 - Windows/Mac/Linux

soloblazer said:
Are you talking about DROID RAZR HD Utility 1.21 - Windows/Mac/Linux
Click to expand...
Click to collapse
for your build you would need version 1.33 found here http://forum.xda-developers.com/showpost.php?p=46269380&postcount=1
1.21 would bootloop because of the locked bootloader.

bweN diorD said:
for your build you would need version 1.33 found here http://forum.xda-developers.com/showpost.php?p=46269380&postcount=1
1.21 would bootloop because of the locked bootloader.
Click to expand...
Click to collapse
Ok, i will give it a shot in the morning after full battery charge, i will let you know,,
thanks for your help.

bweN diorD said:
for your build you would need version 1.33 found here http://forum.xda-developers.com/showpost.php?p=46269380&postcount=1
1.21 would bootloop because of the locked bootloader.
Click to expand...
Click to collapse
Everything went smooth with the #1 option and doing a factory reset etc.
thanks for your help.

soloblazer said:
Everything went smooth with the #1 option and doing a factory reset etc.
thanks for your help.
Click to expand...
Click to collapse
happy to help, glad you got it fixed.

Hi, I have a question.
I had a hard time getting any of the utilities to work initially. Booting up was just scrambled and broken. Anyway, I used v1.34 and it's made progress. It worked it's way through writing system and such. Now the phone is stuck on a bootloop. The phone cannot make it passed the red M before rebooting.
When the phone is plugged in and on an inescapable bootloop, is it charging? My battery was hovering above empty before the v1.34 utility brought me here.

soloblazer said:
Everything went smooth with the #1 option and doing a factory reset etc.
thanks for your help.
Click to expand...
Click to collapse
So now that the OTA for kitkat is out, i tried to do it and it fails now. what do you suggest to get the newest OTA with kitkat?
thanks

soloblazer said:
So now that the OTA for kitkat is out, i tried to do it and it fails now. what do you suggest to get the newest OTA with kitkat?
thanks
Click to expand...
Click to collapse
Are you rooted? If so, that is why.
Did you freeze or remove any apps? If so, that's another reason why.
In either case, you will have to FXZ back to stock, unrooted to take the OTA. However, you WILL lose root and there is no root exploit for Kit Kat unless you have an unlocked bootloader, which you already found out you can't have based on the version your phone was at (9.18.X). And, there is NO way to carry root over the OTA. Voodoo doesn't work with Kit Kat at all, and there is just no other way to keep root on locked bootloaders, period.
So, either hold off on the Kit Kat update and pray someone finds a way to root it for locked bootloaders, or else if you can't wait, then realize you may never see root on this phone again.

iBolski said:
Are you rooted? If so, that is why.
Did you freeze or remove any apps? If so, that's another reason why.
In either case, you will have to FXZ back to stock, unrooted to take the OTA. However, you WILL lose root and there is no root exploit for Kit Kat unless you have an unlocked bootloader, which you already found out you can't have based on the version your phone was at (9.18.X). And, there is NO way to carry root over the OTA. Voodoo doesn't work with Kit Kat at all, and there is just no other way to keep root on locked bootloaders, period.
So, either hold off on the Kit Kat update and pray someone finds a way to root it for locked bootloaders, or else if you can't wait, then realize you may never see root on this phone again.
Click to expand...
Click to collapse
I am the one that started this thread, and i used DROID RAZR HD Utility to get my phone updated via the last update. i have not frooze or removed any of the stock apps. and i dont think i am still rooted. I dont care about having root anymore, so just would like to flash the newest OTA>

iBolski said:
Are you rooted? If so, that is why.
Did you freeze or remove any apps? If so, that's another reason why.
In either case, you will have to FXZ back to stock, unrooted to take the OTA. However, you WILL lose root and there is no root exploit for Kit Kat unless you have an unlocked bootloader, which you already found out you can't have based on the version your phone was at (9.18.X). And, there is NO way to carry root over the OTA. Voodoo doesn't work with Kit Kat at all, and there is just no other way to keep root on locked bootloaders, period.
So, either hold off on the Kit Kat update and pray someone finds a way to root it for locked bootloaders, or else if you can't wait, then realize you may never see root on this phone again.
Click to expand...
Click to collapse
I am the one that started this thread, and i used DROID RAZR HD Utility to get my phone updated via the last update. i have not frooze or removed any of the stock apps. and i dont think i am still rooted. I dont care about having root anymore, so just would like to flash the newest OTA>

soloblazer said:
I am the one that started this thread, and i used DROID RAZR HD Utility to get my phone updated via the last update. i have not frooze or removed any of the stock apps. and i dont think i am still rooted. I dont care about having root anymore, so just would like to flash the newest OTA>
Click to expand...
Click to collapse
My bad for not realizing that.
Are you still getting the dead Andy screen after applying the OTA? If so, then you need to go back into the recovery as you did before and then apply the OTA again. This is a two-step process, especially if you applied the OTA manually rather than taking it automatically.
It's still waiting to continue the update for the OTA. So, go back into recovery and navigate to where you stored the OTA zip file on your external SD card and then apply it again and you should be good to go.

iBolski said:
My bad for not realizing that.
Are you still getting the dead Andy screen after applying the OTA? If so, then you need to go back into the recovery as you did before and then apply the OTA again. This is a two-step process, especially if you applied the OTA manually rather than taking it automatically.
It's still waiting to continue the update for the OTA. So, go back into recovery and navigate to where you stored the OTA zip file on your external SD card and then apply it again and you should be good to go.
Click to expand...
Click to collapse
So just to be clear.
I go to settings/aboutphone/system update. It says checking for update. Update Available/ then i hit download, it downloads it. I click install now. Phone reboots and i see the android man, status bar starts going and gets about 1/3 the way and then get the red triangle in the stomach of the android man. and then phone reboots.

soloblazer said:
So just to be clear.
I go to settings/aboutphone/system update. It says checking for update. Update Available/ then i hit download, it downloads it. I click install now. Phone reboots and i see the android man, status bar starts going and gets about 1/3 the way and then get the red triangle in the stomach of the android man. and then phone reboots.
Click to expand...
Click to collapse
At that point when it reboots, it should continue on and you should see the android picture again as it continues on installing. This is the second stage of the install and can take up to 15 minutes to complete.
Are you saying it just keeps rebooting at that point and never completes? If so, then you need to go here and follow SamuriHL's directions to the letter to get you up and running -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/

iBolski said:
At that point when it reboots, it should continue on and you should see the android picture again as it continues on installing. This is the second stage of the install and can take up to 15 minutes to complete.
Are you saying it just keeps rebooting at that point and never completes? If so, then you need to go here and follow SamuriHL's directions to the letter to get you up and running -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Click to expand...
Click to collapse
No after the android guy with the red triangle, it just does a complete reboot back into android. and then says update failed.

soloblazer said:
No after the android guy with the red triangle, it just does a complete reboot back into android. and then says update failed.
Click to expand...
Click to collapse
Were you rooted at any point in time? If so, did you flash back to stock? Just uninstalling root will not work.
Your phone must be completely stock with no evidence of it being modified in order for the OTA to work. Rooting is one thing that will modify it to where an OTA will not take.
I had explained earlier that if you rooted and/or froze/removed any system/stock apps, you must use an FXZ image to put your phone back to stock. The link I supplied you with in that previous post will give you a stock Kit Kat image to flash to your phone. That is what you must do.

soloblazer said:
So now that the OTA for kitkat is out, i tried to do it and it fails now. what do you suggest to get the newest OTA with kitkat?
thanks
Click to expand...
Click to collapse
the razr utility has been updated since you started this thread, to KK.
just go back to the utility post from before, and you will see the new KK version at the bottom.
use it the same way you used the old one and you will be on stock KK. its the same as taking the ota update.

Hi there:
I've been following this thread, as I'm in a similar situation. I'm pretty sure I'm stuck with either rooted JB or unrooted KK, but just wanted to confirm.
Here's what I have:
-Phone: Razr HD
-System version: 9.18.94.XT926 (VZW US)
-Android: 4.1.2
-Rooted
-Locked bootloader
I'd love some clarifications/confirmations on the following, if anyone has them:
-There is no way to downgrade the system version to an unlockable version (like 9.16). Not even with flashing back to stock everything with the Droid Razr HD Utility.
-There is currently no way to root KK without an unlocked bootloader.
-If I unroot (flash back to stock) and upgrade, I will lose root and likely not get it back.
-The only way for me to currently keep root is to stay on JB.
I'm not interested in custom ROMs, just root.
Thanks in advance.

phraxen said:
Hi there:
I've been following this thread, as I'm in a similar situation. I'm pretty sure I'm stuck with either rooted JB or unrooted KK, but just wanted to confirm.
Here's what I have:
-Phone: Razr HD
-System version: 9.18.94.XT926 (VZW US)
-Android: 4.1.2
-Rooted
-Locked bootloader
I'd love some clarifications/confirmations on the following, if anyone has them:
-There is no way to downgrade the system version to an unlockable version (like 9.16). Not even with flashing back to stock everything with the Droid Razr HD Utility.
-There is currently no way to root KK without an unlocked bootloader.
-If I unroot (flash back to stock) and upgrade, I will lose root and likely not get it back.
-The only way for me to currently keep root is to stay on JB.
I'm not interested in custom ROMs, just root.
Thanks in advance.
Click to expand...
Click to collapse
-no, cant be done
-correct
-correct
-correct

will their ever be a stock 4.4 using odin

wanted to know if their will ever be a stock kitkat rom for the ones that have an unlocked boot loader that can be flashed in odin or something
need kitkat but don't want to lose my unlocked boot loader

Dude, the ROM released yesterday but apparently only in a limited fashion because only some people have been able to pull it. When the files we available and people have had some time to work on them we will likely see a release. That is unless Verizon has done something particularly nasty.
So have patience. We all want kit Kat but we all have to wait until someone figures it out.
Sent from my SCH-I535 using Tapatalk

morbidking said:
wanted to know if their will ever be a stock kitkat rom for the ones that have an unlocked boot loader that can be flashed in odin or something
need kitkat but don't want to lose my unlocked boot loader
Click to expand...
Click to collapse
It's very likely and would be flashed in TWRP or CWM.

SlimSnoopOS said:
It's very likely and would be flashed in TWRP or CWM.
Click to expand...
Click to collapse
thanks for the quick reply just didnt want to take the update and lose unlocked boot now that i know it can be done with out loosing unlocked boot i will wait
need my google wallet working again

morbidking said:
thanks for the quick reply just didnt want to take the update and lose unlocked boot now that i know it can be done with out loosing unlocked boot i will wait
need my google wallet working again
Click to expand...
Click to collapse
Everyone just has to be patient as new OTAs always introduce their own set of problems that the devs must deal with. It may be a few weeks before anything is released or it may be a few days.