I have installed CM 10.2 (Android 4.3) and have tried running an RUU (both through fastboot and the executable) to which they both end up failing. The fastboot states too many threads when writing the bootloader and the Windows executable gives an error 155.
[SOLVED] Look below!
Anyone able to help I am just starring at my boot loader screen all day. TWRP will not even allow me to sideload says cannot mount anything.
So after two days of not having a phone, I solved the issue.
It seems the RUU would not run with the newer version of HBOOT found in the GE version of the rom. So I reflashed HBOOT 1.44 (see attached) and BOOM RUU worked and back to stock!
Hope this helps someone
https://mega.co.nz/#!XhRlXBhB!V8In4VJhp5MXwj9r9gyleTCFiUIbKWxDFmcmn8v3zIU
is that the latest version? I am kind of new to rooting and stuff, I guess when you flash TWRP it replaces HBOOT so that is why you had to reflash HBOOT? I am going to install Android Revolution HD and would like to get all the info beforehand.
schn1tt3r said:
is that the latest version? I am kind of new to rooting and stuff, I guess when you flash TWRP it replaces HBOOT so that is why you had to reflash HBOOT? I am going to install Android Revolution HD and would like to get all the info beforehand.
Click to expand...
Click to collapse
Custom recovery does not replace hboot. You shouldn't have to replace hboot to flash ARHD. You don't even have to unlock the bootloader. Just S-off, flash custom recovery, nandroid backup, and flash ARHD. After Rom is flashed, flash new firmware to update your 1.29 firmware to 2.24
Sent from my HTC One using xda premium
Trying to go back to stock. I too tried the 4.3 firmware and hboot, radio. So right now I am on hboot 1.54 and firmware 3.06.1700.10
I want to go back to stock...any help?
Related
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
badtlc said:
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
Click to expand...
Click to collapse
Yes there are a lot of files that cant be updated with roms. The only way to get all of the new firmware is to run the ruu. Turge has figured out how to flash radios now without flashing the ruu so thats good. But thats not everything. I'd wait to run the ruu until the devs change their rom base to the new update. Otherwise no custom rom yet. You can root the stock update after installing, just not many goodies atm.
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Yep I ran ruu and got it running stock but my 2nd x+ still running old one wit elegancia till roms get updated I don't mind unrooting updating and rooting takes 30 min tops just patiently waiting for a update hell if viper gets updated first ill rock that
Sent from my HTC One X+ using XDA Premium HD app
badtlc said:
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
nugzo said:
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
Click to expand...
Click to collapse
Correct, but I wasn't sure if you could update directly to that RUU from a custom ROM and get all the updates like hboot, firmware and radio. I was wondering if I needed to go from a custom ROM back to stock 1.15 and THEN do this 1.19 update to get everything updated properly.
If you update your phone to the latest RUU, you won't be able to installed a custom ROM until the devs update their ROM. You update, you stay stock for a moment. You still can ROOT the stock ROM.
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
[QUOTE"badtlc"]If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?[/QUOTE]
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.[/QUOTE]
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
Click to expand...
Click to collapse
You can do one of two things to get the full update. One is to go back to a 1.15 stock ROM, flash the stock recovery and run the OTA. The other is to run the latest RUU from HTC (the one from the link posted above) after you've flashed the stock recovery and re-locked the bootloader (otherwise the RUU might not proceed). Bare in mind that running the RUU will wipe your phone to factory settings.
I started a thread here http://forum.xda-developers.com/showthread.php?t=2245955 about people's experiences updating and post-update. Once you decide to update feel free to share your experience there!
I have already updated. I went from elegancia. I locked the bootloader, rebooted to fastboot, and then ran the 1.15 stock RUU. After that, I ran the 1.19 update I downloaded from HTC. I was just trying to figure out if I would have went straight from elegancia to 1.19 if everything including radio, kernel, etc. would have updated properly since elegancia was on the phone and not stock version 1.15. I don't know what these RUUs look at before applying their updates.
so.
i'm posting this on my fiancee's behalf.
anyways.
we got her phone unlocked via htcdev, rooted, 4ext installed, couldn't install any 4.2.2 rom's, realised it was due to the 1.58 hboot.
installed Negalite-BluRom, which worked, had instructions for downgrade to 1.4 hboot. hboot didn't downgrade.
fiancee was after dirty unicorn.
was advised that manually flashing the boot.img from the rom zip via fastboot should circumvent the hboot issue.
did not circumvent.
also tried pacman, didn't work either.
reflashed stock recovery via fastboot.
relocked (fastboot oem lock)
tried to restore stock via exe RUU (2.89) ( have also tried 1.13)
RUU fails with an hboot version error.
currently stuck on bootloop (but can access recovery)
are we trying the wrong RUU? ( sprint(cdma) version evo, using sprint RUU's )
if so, what one should we be using?
(update : no longer able to access recovery, no longer see bootscreen, phone goes straight to bootloader.)
if not.... HAAAALLLLP?
Realtbhuion said:
so.
i'm posting this on my fiancee's behalf.
anyways.
we got her phone unlocked via htcdev, rooted, 4ext installed, couldn't install any 4.2.2 rom's, realised it was due to the 1.58 hboot.
installed Negalite-BluRom, which worked, had instructions for downgrade to 1.4 hboot. hboot didn't downgrade.
fiancee was after dirty unicorn.
was advised that manually flashing the boot.img from the rom zip via fastboot should circumvent the hboot issue.
did not circumvent.
also tried pacman, didn't work either.
reflashed stock recovery via fastboot.
relocked (fastboot oem lock)
tried to restore stock via exe RUU (2.89) ( have also tried 1.13)
RUU fails with an hboot version error.
currently stuck on bootloop (but can access recovery)
are we trying the wrong RUU? ( sprint(cdma) version evo, using sprint RUU's )
if so, what one should we be using?
if not.... HAAAALLLLP?
Click to expand...
Click to collapse
You can not use anything but ics sense roms on your hboot version. You need s-off to be able to downgrade. I suggest flashing back to negalite rom then manually flashing the kernel. After that your phone will be fine. If you want jelly bean (dirty unicorn) you need to read up on getting s-off.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
You can not use anything but ics sense roms on your hboot version. You need s-off to be able to downgrade. I suggest flashing back to negalite rom then manually flashing the kernel. After that your phone will be fine. If you want jelly bean (dirty unicorn) you need to read up on getting s-off.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
yeah..... i completely forgot about reflashing the kernel from negalite.
thanks, 'tis working again now.
Managed to get my phone back working, also now running Dirty Unicorns. Downgraded my Hboot to 1.4. Wire trick.
Thanks for the help though.
Got an old phone from a friend which I'm using since wife broke her phone and I'm trying to decide what to replace it with.
Anyhow, I have an Aria with hboot 1.03, I have unlocked it via the HTC site and managed to get Cyano 10 on it. It is still s-on and I've tried multiple times to redownload Cyano 11 and always get an error of "Error in <name>.zip (Status 0) Installation Aborted". I'm making an assumption based on research that it is due to a combination of s-on and hboot 1.03 so I need to kick it down to 1.02 and s-off it. However, I have been unable to find a valid link for the Official HTC Froyo link to downgrade so I can run Revolutionary to s-off and move ahead.
Thanks in advance.
Hmm, can't find a link either... I can reupload it for you
But before you do that, try updating your recovery to this: http://forum.xda-developers.com/showthread.php?t=2474662
HTCdev unlock shouldn't have any problems with CM11, so it's probably your recovery...
Anyway, here's the RUU
http://goo.gl/OBVJL7
md5sum: 66d703b8a92fc382c38ceec4992a379c
And the rom.zip extracted from it if you just want to run it directly from the phone:
http://goo.gl/WF3RhW
md5sum: 49e737569d1d99e11e652ddcfc15bf84
Edit: Here's a list of them instead of just the AT&T one: http://www.androidruu.com/?developer=Liberty
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
CollinsJ said:
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
Click to expand...
Click to collapse
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
dansou901 said:
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
Click to expand...
Click to collapse
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
WinSuk said:
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
Click to expand...
Click to collapse
Possible. I own one of them (points at signature) and it's been that way for me then. When I rooted my Gratia way back, I also directly did the S-OFF so I never checked the procedure with S-ON. Have been a newbie at that time.
So I'm in a similar boat. I have an old aria, and seeing a cm11, id like to try it (though a nexus is my dd). Anyway, i had cm7 on it, went through some old nandroids, and finally got back to 2.1 just after i used unrevoked on it. I've tried to flash the posted rom.zip (2.2.2, so i can then s-off and /or upgrade hboot [which i also tried to do via htcdev with no success]), it fails a sig check on my cwm 2.5.0.1, telling me bad, even though i verified the md5. Figured it could be the recovery, but i cannot flash the newer version on here via ./fastboot flash recovery recovery.img. i also tried ./fastboot boot recovery.img to no avail. I also couldnt flash the recovery through the old cwm. Im baffled a bit here... Any suggestions are welcomed.
Im thinking of trying to put my sim in it and see if the old att update would go through, any thoughts on that?
So I see a number of people reporting using Baseband: 1.13.11.1105, including Captain_Throwback. I'm on Baseband: 1.13.11.0830 and am having some trouble with the phone connection - dropped calls, static on the line, etc. but data is fine (in fact I can make voip calls through hangouts no problem, but incoming calls are normal phone).
I looked at C_T's firmware collection on themikmik but that only contains up to Baseband: 1.13.11.0830 with the 3.17 software version.
I'm S-OFF via rumrunner after having flashed the 2.10 hboot and 4.13 651.4 Sense 5 Android 4.3 - Deodex to update the partitions to the new format. I've since flashed CM11 snapshot M12. Same phone issues on the rooted Sense and CM11.
Thanks to Captain_Throwback for all the excellent guides and collections here. Any suggestions from you or anyone here on where to find the latest baseband, and if you think this or maybe a custom PRL may help. (Is it possible to flash a custom PRL in CM11 or do I have to flip back to my Sense nandroid first?)
Thanks!
The baseband you're looking for can be found with the 4.3 RUU. You can find said RUU in the first post of my Hboot thread (top link in my sig). Not sure how you updated your Hboot but not your firmware, but I suggest running the RUU. You'll remain S-off afterwards.
To answer your other question you have to be running a Sense ROM to install a custom PRL.
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
cmags said:
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
Click to expand...
Click to collapse
I would run the RUU. Once done, you'll need to unlock and install TWRP again. Then you can restore your backup. As far as recovery goes I'm not sure which is most recent.
Well, that was only partially successful, and I could use some suggestions.
I did a nandroid of my CM11 M12 snapshot image, and ran the RUU in your post (RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_R…igned_one_step.exe).
Afterwards Hboot is 2.10, and Radio is 1.13.11.1105. Great. Bootloader remains S-OFF (expected), and unlocked (unexpected, but cool).
I run fastboot flash recovery TWRP-Recovery-2.8.0.3-jewel-CPTB.img. Boot into recovery, restore my CM11 image, and reboot. Phone just spins on the boot animation.
Rebooted into recovery, wiped cache/dalvik/system/data, install flash CM fresh, wipe again, then restore (without boot) - same issue. About to wipe again and try restoring Sense nandroid, or flashing roms (CM and Sense) anew to see if i get different results.
Any other thoughts? Any way to verify the partition layout? Any way to get a log of what its hung up on while spinning the boot animation?
Thanks!
The issue you're describing reminds me of the issue that comes about from being S-on and having to flash the kernel separately from the ROM. You say you're S-off so that's not the issue, obviously. If you ran the RUU then you are on the new partition layout. Not getting any errors in recovery when you flash the ROM, are you? You might want to 're-download the ROM, check the MD5, and flash again.
Got it sorted out. Something must have gotten corrupted in the nandroid. A stock nandroid worked fine. So i restored cm11 then flashed the rom over the top to fix the boot partition. Im all set now, though the updated baseband didnt fix the static and dropped calls. Must be a hardware issue.
I'm on hboot version 3.16 but I need to go up to 3.19 or the latest one. I don't know how to do this so I'm hoping XDA will help. I currently have an unlocked boot loader and a rooted SkyDragon GPE ROM on 4.4.4. I tried the update to 5.0.1 with the SkyDragon ROM but the WiFi doesn't work. The FAQ for the ROM said this:
"Q: Why isn't wifi working?
A: Need to flash either latest GPE L firmware in this post, or Latest Sense firmware 4.16.xxxx.x. If you are S-ON however you will have to wait until you get latest Official OTA for your device as you cannot flash a different firmware unless you are S-OFF. If you still don't have wifi after firmware flash you need to clean your system/data(Not sdcard)/cache and reflash the rom."
http://forum.xda-developers.com/showthread.php?t=2706391
I am currently downloading a stock HTC Sense ROM and am going to go back to stock and try and do an official OTA update and hopefully it will update hboot or I need a way to get S-OFF.
Here is the link with the stock ROM and recovery http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
I know how to flash the stock ROM but I do not know how to flash the stock recovery.img. Please give me directions on how to flash the recovery after I flash the stock ROM. I also will need to know how to get back to where I am now. Will going back to stock lose the unlocked boot loader? Will I lose root?
Although if there is a way to avoid that by getting S-OFF I will need to know how to do that.
My experience on this is small. I am familiar with adb and flashing ROMs but that's where it ends.
Any help is greatly appreciated. Thanks in advance
Even if you flash the latest 4.4.4 ATT update you still may have issues,You cant flash non att device firmware unless s-off,and as there is no official lollipop version for ATT.youd need to be s-off to get it all updated,changing cid and mid for gpe device requires this to be fully converted.
Bootloader question,I think if s-on you have to relock bootloader to take the ota(could be wrong,search this answer)
Root question yes youll loose root by going back to stock
Flashing:
Flash the backup of stock ROM via twrp.
Copy stock recovery to adb/fastboot location,connect phone via fastbootusb,open command prompt run fastboot flash recovery (nameofrecovery).img
There are more in depth tutorials here on the forum that answer all your question,suggest reading before jumping in with both feet
Edit: Dottat has uploaded the signed firmware for 3.42.502.1 in General Section so go there, grab it, and flash away (don't forget to give that man a thumb up for his REAL effort)
Yes, you CAN absolutely flash firmware with S-On. If your main-version through getvar is 1.58.502.1 or below, you can run the RUU for 4.4.3, http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Then run the latest RUU for 4.4.4 to get newer hboot.
Disregard ALL the claims about unable to flash firmware with S-On, those who insist so are simply too lazy to explain that their uploaded firmware packages are modified ones from the originals. If the firmware comes signed by HTC, you can flash it as long as you meet all the pre-requisites (version-main, MODELID, CID) :fingers-crossed:
iTzz_KAMIKAZE said:
I'm on hboot version 3.16 but I need to go up to 3.19 or the latest one. I don't know how to do this so I'm hoping XDA will help. I currently have an unlocked boot loader and a rooted SkyDragon GPE ROM on 4.4.4. I tried the update to 5.0.1 with the SkyDragon ROM but the WiFi doesn't work. The FAQ for the ROM said this:
"Q: Why isn't wifi working?
A: Need to flash either latest GPE L firmware in this post, or Latest Sense firmware 4.16.xxxx.x. If you are S-ON however you will have to wait until you get latest Official OTA for your device as you cannot flash a different firmware unless you are S-OFF. If you still don't have wifi after firmware flash you need to clean your system/data(Not sdcard)/cache and reflash the rom."
http://forum.xda-developers.com/showthread.php?t=2706391
I am currently downloading a stock HTC Sense ROM and am going to go back to stock and try and do an official OTA update and hopefully it will update hboot or I need a way to get S-OFF.
Here is the link with the stock ROM and recovery http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
I know how to flash the stock ROM but I do not know how to flash the stock recovery.img. Please give me directions on how to flash the recovery after I flash the stock ROM. I also will need to know how to get back to where I am now. Will going back to stock lose the unlocked boot loader? Will I lose root?
Although if there is a way to avoid that by getting S-OFF I will need to know how to do that.
My experience on this is small. I am familiar with adb and flashing ROMs but that's where it ends.
Any help is greatly appreciated. Thanks in advance
Click to expand...
Click to collapse