Related
Ok, this worked for me as of 10/20/10, i had my phone rooted by unrevoked, I am like many of the people here who kept having issues with all the PC36IMG.zip not working. I have extracted a new PC36IMG.zip from the ruu's and have not had any issues. I also had the dreaded "main version is older" issue. This seemed to take care of the issue! Im now back to stock!
Step 1 you will need to go here:
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
If you used Unrevoked Forever at any time, flash unrevoked-forever-son.zip from recovery until hboot shows S-ON(Credit to djR3Z tut)
Step 2
http://www.megaupload.com/?d=108Z9R8Y
This is the PC36IMG.zip file that you will need
- Put this on the root of your sdcard
- Boot into hboot and let it load up the PC36IMG.zip
- It will run like a normal update
- Reboot when finished
- It will do a few other things (Load radio and update)
- After it fully loads you should be back to complete stock!!!!
Lemme know if this doesn't work for you
LIKE I SAID THIS WORKED AS OF 10/20/2010!!!
I am not responsible for damages to your phone! You chose to go the route you did, so face the consequences, I'm just posting what has worked for me, so use at your own risk! Love the android, love my evo!
Has been tested and works if you have a rooted via unrevoked method.
So can I update my evo ota to 3.29.651.5 and then follow these steps? Right now I have the stock 3.26.651.6 rooted with unrevoked3. TIA
m4f1050 said:
So can I update my evo ota to 3.29.651.5 and then follow these steps? Right now I have the stock 3.26.651.6 rooted with unrevoked3. TIA
Click to expand...
Click to collapse
Im not understanding? If you apply just the PC36IMG you should at least lose root and be updated to latest update. You have to run the first tool to relock the bootloader. You will see in hboot if it is locked or unlocked. Locked is s- on unlocked is s- off
My bad, I was wanting to root or better yet, update to 29 and then root.
Sent from my PC36100 using XDA App
yes you can achieve root on the new update through unrevoked. I'm not a fan of rooting this way, as people have had lots of trouble unrooting (had this problem myself). Thats why I came up with this tut so you can unroot if you have to send back to sprint. my method was the only one that worked for me to get unrooted.
people...just use unrevoked 3...i mean its a one click process...u dont have to do anything after that in about 2 minutes your rooted and nand unlocked =P
m4f1050 said:
So can I update my evo ota to 3.29.651.5 and then follow these steps? Right now I have the stock 3.26.651.6 rooted with unrevoked3. TIA
Click to expand...
Click to collapse
Just flash a ROM that's based on the 3.29 update.
Well hopefully this works. I'm not going to root with unrevoked again I don't think. It was much easier for me to unroot my last phone w/o using unrevoked.
Nope, as of 1/19/11 this does not work.
Will this work if I didn't use unrevoked? I am currently having an issue where my usb/charging port is not working properly and can not connect to the computer. I am rooted but need to unroot so I can send my phone back.
Diplomat2387 said:
Will this work if I didn't use unrevoked? I am currently having an issue where my usb/charging port is not working properly and can not connect to the computer. I am rooted but need to unroot so I can send my phone back.
Click to expand...
Click to collapse
This is incredibly outdated, so no, it will not currently work with your phone.
dkelle4 said:
This is incredibly outdated, so no, it will not currently work with your phone.
Click to expand...
Click to collapse
Even if I downgraded my ROM?..I am currently on a 2.1 ROM..
Only one way to find out. It SHOULD. I ended up downloading one of the early official 2.2 releases and flashed that on my phone. Of course now it won't do another OTA because the "signatures are invalid".
dkelle4 said:
This is incredibly outdated, so no, it will not currently work with your phone.
Click to expand...
Click to collapse
I haven't seen any "unroot" threads that have worked for me. Is there one I'm missing?
jpitt916 said:
Only one way to find out. It SHOULD. I ended up downloading one of the early official 2.2 releases and flashed that on my phone. Of course now it won't do another OTA because the "signatures are invalid".
Click to expand...
Click to collapse
I tried just putting the pcimg on my sd card and power up into bootloader and it gives me an error saying that the image is older or something...Agh.
I installed the new jelly Bean ROM for the tf300, forced it really with a forum in the general section, everything was working fine except i had lost my recovery.
I tried installing the recovery back on but i couldent, then i tried wipe user data waited a long time for that but nothing happened so i rebooted and now it is stuck at the Asus logo and i cant access the boot loader!! please im desperate! hope its not totally messed up.
I did EXACTLY the same. You are ****ed no way to fix it. I will be sending my tf300 for RMA later this day.
sparky28000 said:
I did EXACTLY the same. You are ****ed no way to fix it. I will be sending my tf300 for RMA later this day.
Click to expand...
Click to collapse
Let us know how that goes - rumor has it that Asus doesn't service tablets with unlocked motherboards. So they'll throw your board in the trash, place in a new one, then charge you for it.
krhainos said:
Let us know how that goes - rumor has it that Asus doesn't service tablets with unlocked motherboards. So they'll throw your board in the trash, place in a new one, then charge you for it.
Click to expand...
Click to collapse
what about locked tablets but w/ rooted w/ SU installed? any rumors that they wouldn't service it? I think I should be fine. My JB update is causing tons of Gapps force closings, must have been a corrupt update. Sending it in since I want to keep the BL/warranty intact
paedz718 said:
what about locked tablets but w/ rooted w/ SU installed? any rumors that they wouldn't service it? I think I should be fine. My JB update is causing tons of Gapps force closings, must have been a corrupt update. Sending it in since I want to keep the BL/warranty intact
Click to expand...
Click to collapse
If your bootloader is intact, your warranty is completely intact. I think there are ways to force the unit to flash stock firmwares.
If you have your root, check this out: http://forum.xda-developers.com/showthread.php?t=1622628
Method 2 worked for me going back to 9.4.3.30/ICS, then I was able to go to JB afterwards. Bootloader unlock NOT required.
krhainos said:
If your bootloader is intact, your warranty is completely intact. I think there are ways to force the unit to flash stock firmwares.
If you have your root, check this out: http://forum.xda-developers.com/showthread.php?t=1622628
Method 2 worked for me going back to 9.4.3.30/ICS, then I was able to go to JB afterwards. Bootloader unlock NOT required.
Click to expand...
Click to collapse
oh nice! I may need to try this. I assume you were unrooted when you tried Method 2. curious, why did you have to go back to .30/ICS before going to JB? and did the JB OTA update come down again for you or you had to try that workaround method?
paedz718 said:
oh nice! I may need to try this. I assume you were unrooted when you tried Method 2. curious, why did you have to go back to .30/ICS before going to JB? and did the JB OTA update come down again for you or you had to try that workaround method?
Click to expand...
Click to collapse
The JB update script will fail when it tries to patch APK's that you removed. I removed a bunch to de-bloat, so you need a 100% complete stock 9.4.3.30 ICS before the JB update from Asus will work.
I was rooted and unlocked, so I couldn't use the traditional method -- I used a modified zip file that I flashed through TWRP.
krhainos said:
The JB update script will fail when it tries to patch APK's that you removed. I removed a bunch to de-bloat, so you need a 100% complete stock 9.4.3.30 ICS before the JB update from Asus will work.
I was rooted and unlocked, so I couldn't use the traditional method -- I used a modified zip file that I flashed through TWRP.
Click to expand...
Click to collapse
thanks for the info
paedz718 said:
thanks for the info
Click to expand...
Click to collapse
Couple other things -- you will lose TWRP or CWMR upon flashing, attempting to flash one* will brick your unit.
Make sure you back up your root with Voodoo OTA Rootkeeper and SuperSU (not Superuser) -- there's a couple threads about this floating around. I was following this one:
http://forum.xda-developers.com/showthread.php?t=1840504
* - they are currently working on making a new JB-compatible recovery after a bunch of us bricked our tablets
krhainos said:
Couple other things -- you will lose TWRP or CWMR upon flashing, attempting to flash one* will brick your unit.
Make sure you back up your root with Voodoo OTA Rootkeeper and SuperSU (not Superuser) -- there's a couple threads about this floating around. I was following this one:
http://forum.xda-developers.com/showthread.php?t=1840504
* - they are currently working on making a new JB-compatible recovery after a bunch of us bricked our tablets
Click to expand...
Click to collapse
I read that about the custom recoveries since they need to be JB compatible. looks like TWRP is on the case. My instance, I kept my bootloader intact and wanted to keep it still like that just in case I screwed it up like cracking the screen. I've only had it for a few months. That's why I may have to try the Wolf method for rooted users w/ locked bootloaders. I just need to verify thru ADB that I still have root after I upgraded or try the unrooted method to go back to ICS.
Just read that link closely and I def did not have SuperSU installed only Voodoo OTA RK, guess I'm no longer rooted after the update then. I should have waited a few days before I updated and scoured the forums. oh well, I'm just hoping to get a working tablet back. I can only get to the "Welcome" setup screen on JB and immediately get gapps force closes, popping up one after the other. Def a corrupt flash.
How is the rma thing have u gotten word back? I bricked mine upgrading to jb. The fast boot USB method errors and locks up the unit.
So I opened an RMA ticket and am sending my tablet in a day... my boot loader is unlocked as well.
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
Hey guys, got a question here. I just got my infinity, so i haven't gone into rooting it yet, and have received the option to upgrade firmware. I'm. A bit scared cause ive read people got theirs bricked following an upgrade. Is this possible?? Or was it happening to rooted users only?? How safe is it to upgrade to JB with a full stock infinity??
Example of what I mean: http://www.transformerforums.com/fo...pdate-brick-anyone-elses-infinity-tablet.html
Seen it somewhere on xda too
Thanks for the help!
Pd: don't have time right now to get into rooting it ( i will later on), so I'd appreciate if we could skip the " just root" suggestion, thanks!
not sure why you think we care if you root or not.
just run the update and be happy.
coldsun15 said:
Hey guys, got a question here. I just got my infinity, so i haven't gone into rooting it yet, and have received the option to upgrade firmware. I'm. A bit scared cause ive read people got theirs bricked following an upgrade. Is this possible?? Or was it happening to rooted users only?? How safe is it to upgrade to JB with a full stock infinity??
Example of what I mean: http://www.transformerforums.com/fo...pdate-brick-anyone-elses-infinity-tablet.html
Seen it somewhere on xda too
Thanks for the help!
Pd: don't have time right now to get into rooting it ( i will later on), so I'd appreciate if we could skip the " just root" suggestion, thanks!
Click to expand...
Click to collapse
First, check to see what's the current build version on your tab, if it's .26, then you need to do nvflash backup your bootloader (very important), will get back to this later. If you have version .30 you just go ahead and update to Jelly Bean. Just for your information, once you're on Jelly bean and if you want to root, you need to downgrade back to .30, root it then upgrade back to Jelly bean. OR you could UNLOCK your device (this will void your warantty) while on Jelly Bean, then root it. Read this carefully and make your decision.
lafester said:
not sure why you think we care if you root or not.
just run the update and be happy.
Click to expand...
Click to collapse
Exactly.
No problems updating from a rooted device here.
I lost root, but I didn't care.
No reason to fool with all the rooting stuff if you just want to use the tablet.
An easier root solution will come along eventually.
Update and...be happy!
Thats OK said:
Exactly.
No problems updating from a rooted device here.
I lost root, but I didn't care.
No reason to fool with all the rooting stuff if you just want to use the tablet.
An easier root solution will come along eventually.
Update and...be happy!
Click to expand...
Click to collapse
Ok, that i didnt know... previous to this tablet, all i've had is my htc phone, which is a pain in the arse to root, unlock, and well, basically, cant update if u have root, since it would brick, so i thought same applied here.
I will root at some point, cause i really like the freedom it gives you (root + unlock bootloader actully)
buhohitr said:
First, check to see what's the current build version on your tab, if it's .26, then you need to do nvflash backup your bootloader (very important), will get back to this later. If you have version .30 you just go ahead and update to Jelly Bean. Just for your information, once you're on Jelly bean and if you want to root, you need to downgrade back to .30, root it then upgrade back to Jelly bean. OR you could UNLOCK your device (this will void your warantty) while on Jelly Bean, then root it. Read this carefully and make your decision.
Click to expand...
Click to collapse
i knew that if i updated, id later have to downgrade it back in order to root, but just feel like trying official jb before getting into trying roms.
and btw, even though im .30, whats the problem with updating if in .26??
lafester said:
not sure why you think we care if you root or not.
just run the update and be happy.
Click to expand...
Click to collapse
Well, my experience in other forums (desire z), most of the times people suggested to root, so i just wanted to make it clear. Not that i think anyone cares or should care.
coldsun15 said:
Ok, that i didnt know... previous to this tablet, all i've had is my htc phone, which is a pain in the arse to root, unlock, and well, basically, cant update if u have root, since it would brick, so i thought same applied here.
I will root at some point, cause i really like the freedom it gives you (root + unlock bootloader actully)
i knew that if i updated, id later have to downgrade it back in order to root, but just feel like trying official jb before getting into trying roms.
and btw, even though im .30, whats the problem with updating if in .26??
I thought if you do have .26 then you are a very lucky man. You could able to backup your bootloader and make your device brick safe.
http://forum.xda-developers.com/showthread.php?t=1901479
Click to expand...
Click to collapse
buhohitr said:
coldsun15 said:
I thought if you do have .26 then you are a very lucky man. You could able to backup your bootloader and make your device brick safe.
http://forum.xda-developers.com/showthread.php?t=1901479
Click to expand...
Click to collapse
well, thats a bummer, lol.
So, in any case, with the .30 version, is it safe to upgrade, or do i have the risk of getting into the same problem i stated in the link at post 1?
Click to expand...
Click to collapse
coldsun15 said:
buhohitr said:
well, thats a bummer, lol.
So, in any case, with the .30 version, is it safe to upgrade, or do i have the risk of getting into the same problem i stated in the link at post 1?
Click to expand...
Click to collapse
It's very safe, piece of cake!! go for it!
Click to expand...
Click to collapse
buhohitr said:
coldsun15 said:
It's very safe, piece of cake!! go for it!
Click to expand...
Click to collapse
So, just for my own information (and anyone else who might find it interesting), why have this persons ran into bricks when updating to jb?
Click to expand...
Click to collapse
I just got my TF700 today. I am prepping for REALLY long airline flights and bought this setup for the battery life so I purchased the keyboard attachment for the added battery life. It came stock with JB (can't remember the firmware #) but I was able to downgrade to firmware .30 via: http://forum.xda-developers.com/showthread.php?t=1925230 then rooted via http://forum.xda-developers.com/showthread.php?t=1706588. Playing with it tonight has angered me enough to know that I want to unlock and install a new ROM. I am aware that I cannot use NVFlash because of the .30+ firmware which angers me even more...almost to the point of returning the tablet.
On to the point:
All of the unlocking guides for the TF700 say the process is for ICS which I am running with the .30 (right?) Will the fact that I reverted from JB to ICS adversely affect the unlocking process using the methods available?
Should just return the tablet (and keyboard) and get another setup?
lowriderdog37 said:
I just got my TF700 today. I am prepping for REALLY long airline flights and bought this setup for the battery life so I purchased the keyboard attachment for the added battery life. It came stock with JB (can't remember the firmware #) but I was able to downgrade to firmware .30 via: http://forum.xda-developers.com/showthread.php?t=1925230 then rooted via http://forum.xda-developers.com/showthread.php?t=1706588. Playing with it tonight has angered me enough to know that I want to unlock and install a new ROM. I am aware that I cannot use NVFlash because of the .30+ firmware which angers me even more...almost to the point of returning the tablet.
On to the point:
All of the unlocking guides for the TF700 say the process is for ICS which I am running with the .30 (right?) Will the fact that I reverted from JB to ICS adversely affect the unlocking process using the methods available?
Should just return the tablet (and keyboard) and get another setup?
Click to expand...
Click to collapse
Unlocking works in either ICS or JB so no problem there.
If it's possible to return the tab for an ICS .21 or .26 version that would good as far as NVFlash is concerned.
Otherwise just unlock and do the custom ROM flash of your choice.
Hope all goes well either way...and welcome to the board!
Go ahead and unlock. You will be fine. As long as you are carefull and follow instructions you shouldn't run into a problem that would require nvflash to restore
Sent from my LG-P999 using Tapatalk 2
laod said:
Go ahead and unlock. You will be fine. As long as you are carefull and follow instructions you shouldn't run into a problem that would require nvflash to restore
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Just want to remind you of one thing, I also unlocked mine works fine, and yes it was smoother, but a few weeks ago, my tf700 was suddenly broken, did no reboot anymore.
So there goes my 700 euro tablet because with the unlock I don't have any warrenty.
Zuran said:
Just want to remind you of one thing, I also unlocked mine works fine, and yes it was smoother, but a few weeks ago, my tf700 was suddenly broken, did no reboot anymore.
So there goes my 700 euro tablet because with the unlock I don't have any warrenty.
Click to expand...
Click to collapse
No way to tell if your problem was related to the unlock procedure -- so I cannot refute that point of view, either -- but the changes are slim at best. Lots of follks -- myself included -- have unlocked succesfully and have enjyed a custom ROM since then.
Thats OK said:
Unlocking works in either ICS or JB so no problem there.
If it's possible to return the tab for an ICS .21 or .26 version that would good as far as NVFlash is concerned.
Otherwise just unlock and do the custom ROM flash of your choice.
Hope all goes well either way...and welcome to the board!
Click to expand...
Click to collapse
All of the research I have been doing has said that .30 changed the bootloader and you cannot go back from that.
lowriderdog37 said:
All of the research I have been doing has said that .30 changed the bootloader and you cannot go back from that.
Click to expand...
Click to collapse
Ah,
I meant could you return the tablet to where you had bought it in hopes of obtaining a .26 versioned tablet.
True NVFlash is a no go with ICS version .30 and higher.
Apologies for the confusion.
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