Hi people, I have screwed up majorly.
I own a rooted froyo stock HTC Desire and got tired of seeing the update notice on the small OTA updates HTC have made. Since my phone was rooted, I was unable to actually install it normally because it would give me some error and exit as you all know.
When I finally had enough, I downloaded the update and renamed it to update.zip, placed it in the root directory of my SD card and proceeded to install it through Clockworkrecovery. In the beginning it proceeded as normally by installing, but somewhere it screwed up and I was stuck in the infinite reboot thing. The HTC logo would appear and seconds later it would turn off and start over again.
I then tried to boot into clockwork recovery to run the update again, but alas I couldnt. It now says "E:Cant open /cache/recovery/command" now I am stuck in the normal recovery system.
Is there any way out of here? I have tried to download Cyanogenmod and rename to update.zip and install, but file verification fails. I know it was a longshot.
I dont think it's bricked....
"All" you have to do is get an official RUU - put it in fastboot mode and run the RUU
That way u get a unrooted stock rom.
After that u can root again using Unrevoked and get the rooted 2.29.405.5 rom
the one i use is : RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
http://www.multiupload.com/UOWLL86GVB
Smirge said:
I dont think it's bricked....
"All" you have to do is get an official RUU - put it in fastboot mode and run the RUU
That way u get a unrooted stock rom.
After that u can root again using Unrevoked and get the rooted 2.29.405.5 rom
the one i use is : RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
http://www.multiupload.com/UOWLL86GVB
Click to expand...
Click to collapse
Mange tak!
I am downloading the official RUU now, but just to be sure:
I enter fastboot mode by powering the phone on, holding volume down. Then I connect the phone to my computer and run the .exe?
yup - that should be it...
og velbekomme
Just make sure your desire isnt branded, else running the WWE RUU wont work.
RaymondErasmus said:
Just make sure your desire isnt branded, else running the WWE RUU wont work.
Click to expand...
Click to collapse
Well its not branded, but got another issue.
I only have access to a computer with Windows 7 and got error 170. I have been searching and all the guides to bypass it requires the phone to be turned on and connected to HTC Sync, for above reasons I am not able to do so.
Any ideas?
Edit: Seems like I got it working, used this guide to correct my USB drivers.
http://forum.xda-developers.com/showthread.php?t=776056
So it's working now ? u got your phone back ?
Hi all,
I got a notification this morning about an OTA on my Vodafone UK One X, I have unlocked it already though, so the OTA refuses to install as per previous OTAs.
Like the previous OTA, I opened the zip (OTA_ENDEAVOR_U_ICS_40_S_Vodafone_UK_2.17.161.4-1.29.161.13_release_280431g20qld0c8sg0f1qb.zip) and modified the META-INF\com\google\android\updater-script to remove the cid check, copied the zip to the device, rebooted into CWM v5.8.4.0, disabled signature verification, flashed the zip.
All went well, progressed as normal patching the system, no errors displayed.
The device now boots all the way to my Android home screen with screen saver etc, but then immediately reboots as if it thinks part of the update is still pending. Any ideas what I can do to get out of the boot loops? I remember something like this from the last flash.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1832900
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom
May help ?
Aidey68 said:
http://forum.xda-developers.com/showthread.php?t=1832900
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom
May help ?
Click to expand...
Click to collapse
Thanks, useful to know I have a few things to try before putting a stock recovery back and factory ruu.
I'll give them a try tonight, cheers!
Hi all,
This is my M8 - Stock, Rooted & S-OFF. It's an unlocked O2 one which I use on EE in the UK
M8_UL PVT SHIP S-OFF
CID-02___001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.206.1 <--- after the OTA, this now reads OS-4.20.206.2
eMMC-boot 2048MB
The Stagefright OTA for my M8 just downloaded, so I re-flashed recovery with one that I extracted from the last 5.0.1 OTA (it usually has the latest TWRP) & let it install the OTA. Everything went fine, it rebooted afterwards to recovery, then automatically rebooted again... & then it sticks at the boot screen after showing the O2 logo & chiming.
From the stuck boot screen, I can reboot it into the boot loader or recovery fine, but now when I boot it into recovery I get this:
Android system recovery <3e>
LRX22C release-keys
Volume up/down to move highlight;
enter button to select.
reboot system now
apply from sd card
wipe data/factory reset
wipe cache partition
reboot into bootloader
power down
view recovery logs
apply from phone storage
_____________________
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
Write host_mode success
handle_cota_install: No CW files. Skip cw installation.
What do you advise?
I haven't tried to factor reset it yet, but there is nothing on the phone that isn't backed up, so I can reset, re-flash or do anything required to get it back. As it's S-OFF, at a pinch I could change the SID & flash an entirely different ROM, although I have tended to stay Stock up until now...
If everything else fails, is it worth downloading the 5.0.1 RUU from http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 resetting my CID to HTC__001 & then letting it re-download & re-install the OTA before I re-root it & install TWRP again?
Nope... that didn't work! I just get
(bootloader) shift_signature size for header checking...
FAILED (remote: 32 header error)
regardless of whether I have a CID of HTC__001 or 11111111
& a factory reset doesn't seem to have made any difference either, as it is still stuck on the boot screen.
Any ideas of what to try next please?
Hey i Have the same Problem, but i doesnt have S-off (Still on S-ON) so i cant get RUU, or ?
Problemts solving hints ?!?!
I got the same problem, stuck on the boot screen.
S off, supercid, rooted, stock recovery and rom.
Hope we ll havé a solution quickly...
Hi,
maybe install TWRP recovery, restore everything to the state before applying the OTA and then trying once more?
But the newer TWRP versions might not even work any more, at least I have this problem, see http://forum.xda-developers.com/htc-one-m8/help/help-longer-enter-twrp-recovery-one-m8-t3186208.
HTC really seems to have done something nasty with this update. And it actually does not even fix all StageFright vulnerabilitis, the latest one stays open.
Cheers,
Tim
OK, I managed to get my phone back... I left the CID as HTC__001 but the trick was to rename the RUU to 0P6BIMG.zip & copy it to the root of the SD card using an adapter plugged into my PC. Then, I just rebooted it with Power & Vol Down, whereupon it automatically found it & started the update. I did note the prominent warning of "Do not power off your phone", so I left it to do its thing which took quite a while). Now, it's busy "optimizing apps", so I know that we are back up & running. OK, now, it's found the OTA & is busy downloading it again as well, so it appears that I now have a nice, stock, unrooted WWE install instead of my old O2 one. I must do a nandroid backup as soon as I replace the recovery with whatever version of TWRP works, but happy happy, I have my phone back again. I do hope the OTA doesn't kill it again when I run it, but as it is now 100% stock, I am full of hope.
Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
JustinSB said:
OK, I managed to get my phone back...
Click to expand...
Click to collapse
Glad you got it running again. It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
tim_h said:
It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
Click to expand...
Click to collapse
I live right out in the sticks here in England, so my Internet connection is filthy - I'll have to leave it overnight to download all the apps that it needs to reinstall before I'll even try the OTA again. Then I'll see if the latest TWRP works, or it we have to go way back to get a version that plays nice. I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
It looks like tomorrow will be just as much of a learning curve as today
JustinSB said:
I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
JustinSB said:
Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
Click to expand...
Click to collapse
Hmm
Found out, that i doesnt have stock OS. I Have CID VODAP102.
And Now ? Nandroid Backups which i Found for that need again S-OFF
peter13337 said:
Hmm
Found out, that i doesnt have stock OS. I Have CID VODAP102.
And Now ? Nandroid Backups which i Found for that need again S-OFF
Click to expand...
Click to collapse
crap
I've got exactly the same problem after running OTA I'm on s-on
I would be greatful for the solution
Edit: TWRP restore saved my phone
BTW it would be good to know how to apply this bloody update. I've stock rom so no sure why it bricked my phone
I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe
I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.
Note: It will wipe the device.
o2 RUU can be found here:
https://www.androidfilehost.com/?fid=95916177934555499
Peter13337 - There's a Stock Nandroid backup for your CID here, which would give you (hopefully) a way out: http://forum.xda-developers.com/showthread.php?t=2701376
It may also give you the chance to run the update, then factory reset it to Google will restore everything for you from its automatic backups. Good luck
ritdaw said:
I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe
I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.
Note: It will wipe the device.
o2 RUU can be found here:
https://www.androidfilehost.com/?fid=95916177934555499
Click to expand...
Click to collapse
:sly: You are a legend :thumbup:
Sent from my Nexus 6 using XDA Free mobile app
After restoring TWRP I tried running OTA again
it screwed the device up again
I've got a feeling there will be wave of similar posts soon
thanks HTC for faulty OTA
Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.
I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
Sent from my HTC One_M8 using Tapatalk
tony_5309 said:
Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.
I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
tim_h said:
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
Click to expand...
Click to collapse
tim_h, I flashed TWRP 2.8.7.0 without any problems, rebooted it & used it to flash super-su 2.46 fine. It doesn't give me any problems at all & everything works & boots exactly as it should.
m112 said:
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
Click to expand...
Click to collapse
Oh ok. Good.
Sent from my HTC One_M8 using Tapatalk
JustinSB said:
I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
OK, after flashing the RUU yesterday, as I mentioned above, I left it downloading all my apps overnight, along with the Stagefright OTA (on my reeeaaaly sloooooow Internet connection), rebooted it to load various HTC updates, then installed the OTA. WARNING! The OTA reboots it twice, & the second time it just sits there on the Boot Screen for well over a minute before it boots & goes into the whole "optimizing apps" routine. I was getting really worried that it had all gone wrong again, but thankfully I stepped away from the phone & let it be, & it came good just before I gave up hope. But compare this with what originally happened yesterday (on a rooted, slightly elderly stock ROM), when I also left it alone & it just sat there for an hour, doing nothing... I don't know the answer, but this OTA seems to be really very picky!
One it had installed & rebooted & I was 100% certain that I was in the clear on the OTA, I flashed in the latest TWRP, which worked fine & gave me no problems at all (Note, there have been reports of people having problems with recent versions of TWRP after this OTA, but I didn't replicate those problems). I used TWRP to install UPDATE-SuperSU-v2.46.zip so I am now back up & running rooted again. But because of this I now have a brand new, shiny WWE Stock ROM (as opposed to my elderly, & heavily patched O2 Stock) with the latest firmware, TWRP & SuperSU. I'm happy that it all works, but I have the greatest of sympathy for everyone out there who didn't have S-OFF, as without it I'd have had very serious problems.
Good luck everyone
So a couple days ago i got a new system update 4.20.531.5 (54.21MB) for my phone ( T-mobile) OTA update
I tried to update it but with no success, the phone enters recovery mode with a message "install aborted" and reboots with the same system update notification.
Is there any way to install the update? or maybe to remove the notification.. yes my phone is rooted.. i though to use xposed maybe ...but i tried to install it and failed so i removed it (it bricked my phone,prob installed it the wrong way).
To receive official updates your device needs to be unrooted. Xposed won't help. The 2 options are
1. Use Xposed to disable notification for system update or use application manager and uncheck receive notification.
2. Go back to stock to receive update.
Sent from my HTC One_M8 using Tapatalk
You can also delete in system/priv-app/updater.apk and updater.odex
This will get rid of ota all together
Sent from my HTC One_M8 using Tapatalk
I'm having the same problem except that I rooted the phone and applied the update after replacing the original recovery, but still, each time I apply the update I get htc one Logo (white) and nothing happens. even though I tried to restart my phone using volume up and power button, restart takes me to the same htc one screen then the screen fades.. I think the phone was bricked so I tried to replace the recovery into twrp and wiped the phone (keeping internal storage ofcourse), but also the same thing happens
* Note: I tried to give the phone 1 hour and the phone stayed in the same htc logo!
Thank god for having a Nandroid backup that saved me, but now the phone keeps saying that it wants to update! what should I do?
humam2104 said:
Thank god for having a Nandroid backup that saved me, but now the phone keeps saying that it wants to update! what should I do?
Click to expand...
Click to collapse
If the nandroid was fully stock, corresponds to your firmware, and you have stock recovery, it should be okay to update.
Worst that happens, you can revert to TWRP and restore the nandroid, like you just did.
Or disable the updates, and just carry on with stock nandroids or custom ROMs, if you don't want to risk being stuck in the same spot again.
Hi, I went completely back to stock with my relocked bootloader, super Cid and s-off HTC 10 two days ago. Everything went well, after flashing RUU I once tried if stock recovery was working- it was- and went, as last step, s-on again. After that I installed several OTA updates without any problems and am now on the latest version. So far so good, only strange thing (for me at least) is no access to stock recovery anymore. I wanted do perform a factory reset so I tried to boot into recovery via bootloader mode. But than I got a screen image with a tiny HTC 10 image and a red triangel with an exclamation point... I remember something like this from way back with my Galaxy S2 between flashing ROMs and firmware updates when there was no recovery at all...
But as I said- after flashing RUU stock recovery was fine and if there was something wrong with it wouldn't it be impossible to install OTA updates?
Does this has something to do with s-on?
By the way, I found the option to do a factory reset in the nougat settings, so this is solved, but this red triangel irritates me very much!
Any help would be great!
Thanks.
Sent from my SHIELD Tablet K1 using XDA-Developers Legacy app
ronnbon said:
Hi, I went completely back to stock with my relocked bootloader, super Cid and s-off HTC 10 two days ago. Everything went well, after flashing RUU I once tried if stock recovery was working- it was- and went, as last step, s-on again. After that I installed several OTA updates without any problems and am now on the latest version. So far so good, only strange thing (for me at least) is no access to stock recovery anymore. I wanted do perform a factory reset so I tried to boot into recovery via bootloader mode. But than I got a screen image with a tiny HTC 10 image and a red triangel with an exclamation point... I remember something like this from way back with my Galaxy S2 between flashing ROMs and firmware updates when there was no recovery at all...
But as I said- after flashing RUU stock recovery was fine and if there was something wrong with it wouldn't it be impossible to install OTA updates?
Does this has something to do with s-on?
By the way, I found the option to do a factory reset in the nougat settings, so this is solved, but this red triangel irritates me very much!
Any help would be great!
Thanks.
Click to expand...
Click to collapse
Please see steps in attachment
Thank you, did not exactly work like this- in download mode was no fastboot mode but via bootloader to recovery and than step 4+5 did the trick! Sorry, really did not expect this to be such a mundane answer....
Sent from my SHIELD Tablet K1 using XDA-Developers Legacy app