I tried all day to update my One X to 4.0.4.The phone was rooted but stock.Tried putting the stock recovery, but a red triangle appears in recovery, after that i tried locking the bootloader , but with no succes. I don't know what i'm doing wrong.Please help..
deusexisagod said:
I tried all day to update my One X to 4.0.4.The phone was rooted but stock.Tried putting the stock recovery, but a red triangle appears in recovery, after that i tried locking the bootloader , but with no succes. I don't know what i'm doing wrong.Please help..
Click to expand...
Click to collapse
Sounds a bit of a mess. If I were you I would run the RUU to get back to stock, update OTA and then re-root again.
dr9722 said:
Sounds a bit of a mess. If I were you I would run the RUU to get back to stock, update OTA and then re-root again.
Click to expand...
Click to collapse
I am having the same problem. Tried all day yesterday. Also tried installing the RUU and that failing install as well for me. I have another thread with some details of the error I get in recovery. Basically Here is the info
Get the details of install
Gets downto verifying current system...
Assert failed: apply patch check /system /app/7digital3.apk
E:error in //internal_sdcard/download/ota (file)
Status 7
Installation aborted
So was there a problem with htc servers corrupting the downloads yesterday. Just a question when I see two now with the same issue in updating.
Have the same problem with OTA update from 1.29.401.12 to 2.17.401.12 fail.
Have tryed to remove CID check as have worked with earlier OTA, that dosnt work on this.
RUU also fail with aborted installation as mention over here, but I have had error with all RUU since I got One X 6 monts ago.
Same here, i tried to change name update.zip,asserts but it doesnt work.It says "assert failed: check_cid(get prop("ro.cid"),......."
I think its because u guys remove the bloatware from the system. Ota update need the bloatware even if u r rooted
Sent from my HTC One X using xda app-developers app
Just run your stock rom, flash your stock recovery. You can enter recovery when you see the phone & red triangle just push vol up + power button. You see some errors also. No problem. It's because stock recovery can not mount your sd !
Just boot into your stock rom with stock recovery, bootloader can stay UNLOCKED.
update your phone with the software update program and it should update fine, did this myself last night. After that you can flash the custom recovery and run a custom rom again if you want.
Verstuurd van mijn HTC One X
Can't get OTA to (re)install itself on HTC One X
MarcelHofs said:
Just run your stock rom, flash your stock recovery. You can enter recovery when you see the phone & red triangle just push vol up + power button. You see some errors also. No problem. It's because stock recovery can not mount your sd !
Just boot into your stock rom with stock recovery, bootloader can stay UNLOCKED.
update your phone with the software update program and it should update fine, did this myself last night. After that you can flash the custom recovery and run a custom rom again if you want.
Verstuurd van mijn HTC One X
Click to expand...
Click to collapse
Hi, there I have an HTC One X, relocked, with RUU put back on, but it is the last OTA: OTA_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10-1.26.707.4_release_2571341oc2x91f61pch2z9
That caused the problems as FOTA. My touchscreen now randomly does not accept any inputs.
All because the FOTA was applied while loading the battery, stupid of me of course but s..t happens,right.
So all I want to do now is applying last OTA again. Read all forum updates, but no real solution.
Tried the above, put the ota on de sdcard, even renamed it to update.zip and also on card, but when in stock recovery none of the options seem to pick it up or work.
The RUU succesfully applied was:
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
And yes it was bought in Singapore:angel:
I could unlock it again and I tried running Maximus V2.2 but the same annoying touchscreen problem.
And yes i tried the option not to go to sleep when loading on charger but didn't help either.
Who can help, or do I wait for the FOTA of Jelly Bean coming this month from HTC (or so it is stated on many websites)?
Thanks for any help in advantage!:good:
TRobdeV said:
Hi, there I have an HTC One X, relocked, with RUU put back on, but it is the last OTA: OTA_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10-1.26.707.4_release_2571341oc2x91f61pch2z9
That caused the problems as FOTA. My touchscreen now randomly does not accept any inputs.
All because the FOTA was applied while loading the battery, stupid of me of course but s..t happens,right.
So all I want to do now is applying last OTA again. Read all forum updates, but no real solution.
Tried the above, put the ota on de sdcard, even renamed it to update.zip and also on card, but when in stock recovery none of the options seem to pick it up or work.
The RUU succesfully applied was:
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
And yes it was bought in Singapore:angel:
I could unlock it again and I tried running Maximus V2.2 but the same annoying touchscreen problem.
And yes i tried the option not to go to sleep when loading on charger but didn't help either.
Who can help, or do I wait for the FOTA of Jelly Bean coming this month from HTC (or so it is stated on many websites)?
Thanks for any help in advantage!:good:
Click to expand...
Click to collapse
hi i have a similar issue how did u manage to sought the problem of screen
Hi, I'm from Italy and my uncle send me an SGH-i747.. I've unlocked it for use my Italy Sim.
The phone is currently 4.1.1 and it doesn't check update. Kies says me that the 4.1.1 is the latest update.. I've download OTA Updater but it says that the rom haven't got otaupdater.otaid or it is empty.
I hope you can help me. :3 Sorry for my bad english.
Spyro1997 said:
Hi, I'm from Italy and my uncle send me an SGH-i747.. I've unlocked it for use my Italy Sim.
The phone is currently 4.1.1 and it doesn't check update. Kies says me that the 4.1.1 is the latest update.. I've download OTA Updater but it says that the rom haven't got otaupdater.otaid or it is empty.
I hope you can help me. :3 Sorry for my bad english.
Click to expand...
Click to collapse
You won't be able to get an OTA update in Italy because the update is delivered via AT&T which you probably don't have access to. You would need to have a valid AT&T SIM card in the phone with Wi-Fi access. You may be able to update manually in 2 steps first to 4.1.1 and then to 4.3 which is the latest OS version by following the process in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2387423
Download the 2 stock files for 4.1.2 and 4.3 respectively. Copy both zips to a good quality micro SDHC card
Power off the phone. Place the SD card into your phone. Boot into recovery mode by simultaneously holding down the volume up, power and home buttons. Wait until you see a blue message flash across the screen then release the power button but continue to hold the volume up and menu button until the Android image appears. Install the 4.1.2. Wait for the process to finish and your phone to reboot. Power off again and repeat for 4.3. Hope this helps you.
Now I try, Thanks .. But I've need to Root my phone?
I've tried to update to 4.1.2 but at the restart of the phone, after "rethink is possible" it remain on the Samsung screen... help D:
Spyro1997 said:
I've tried to update to 4.1.2 but at the restart of the phone, after "rethink is possible" it remain on the Samsung screen... help D:
Click to expand...
Click to collapse
If you got to that stage, then it worked. Sometimes it takes several minutes for the rest of the set-up menu to come up after reboot. Wait for a while and if nothing comes up, pull out and replace the battery, then reboot into recovery mode. Do a hard wipe/factory reset in recovery mode and reboot.
You do not need to root your phone for this process. In fact, it may not work with a rooted phone. You can, however, still root your phone after the update and there are several ways of doing this. However, first get through the updating process and let's know how that goes.
Really thanks, I've done an Hard Reset and it works.. now i've 4.3 thanks a lot. You can close the thread.
My phone is rooted on stock 4.1.2 with a locked bootloader. I have deleted some system apps and I do have lots of xposed modules running. I downloaded the kit kat update but it doesn't install. When I turn off my phone and boot it back up it only works for about 30 seconds then shuts down and goes back to this screen.
killedbymonday said:
My phone is rooted on stock 4.1.2 with a locked bootloader. I have deleted some system apps and I do have lots of xposed modules running. I downloaded the kit kat update but it doesn't install. When I turn off my phone and boot it back up it only works for about 30 seconds then shuts down and goes back to this screen.
Click to expand...
Click to collapse
Try flashing the latest SBF thru rsd, that should fix it, you always have to put your phone the most stock possible so you can be allowed to install the OTA.
I downloaded the latest 4.1.2 firmware, but when I opened it in rsd the process failed and I could not continue.
Sent from my Nexus 7 using XDA Free mobile app
killedbymonday said:
My phone is rooted on stock 4.1.2 with a locked bootloader. I have deleted some system apps and I do have lots of xposed modules running. I downloaded the kit kat update but it doesn't install. When I turn off my phone and boot it back up it only works for about 30 seconds then shuts down and goes back to this screen.
Click to expand...
Click to collapse
I had this same problem. I think what is happening is that every time you reboot your phone it powers off in an attempt to install KitKat, but because something went wrong in the initial update, it boots up in fastboot mode.
RSD did not work for me either.
I fixed mine by using House Of Moto. It got me back to stock 4.1.2 (no root). I have not yet tried to update to KitKat again. I will probably try later tonight.
Here's the link http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/
You will have to register with the site to download everything. My activation link went to my spam folder fyi.
Make sure you follow the directions very carefully. (Especially the parts about the script generator and the snapdragon fxz support).
Once I was finished with the entire process, my phone still booted up in fastboot, however when I chose "normal boot" from the fastboot menu it booted up to stock 4.1.2.
I had to follow these directions to get it to boot up normally. http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
(use the third post in that thread)
You can understand why am hesitant to try the KitKat update again.
UPDATE:
I updated via the OTA and everything went smoothly. Running 4.4.2 without root
My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.