Database Info

[RUU] RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/

Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work

thanks for sharing!

appreciate this very much!

thanks flipzmode....always a chance this could come in handy at some point

THANKS! was worried about having a with Google phone until now

thanks flipz

Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)

Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.

This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!

Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.

johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.

posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.

someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)

fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today

Thanks!
this saved my phone. I was about to throw it away.

USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.

nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")

Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie

Rogers! Downgrade your device if you're stuck!

WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.

Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.

wow dat was quick, so downgrade and follow the rooting process again is it ?

Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?

What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?

Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome

dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???

dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?

ok update failed

dammm... was hoping for a fix!

Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....

I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e

weird, I have lost all the signal ever since trying to flash the nbh file

copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers

alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.

copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?

Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.

I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.

Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.

Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.

Bricked cdma htc hero after ruu 1.56 Semi Solution

Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL

can you launch the RUU again and (hopfully) have it restore your phone correctly?

You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet

rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions

This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.

wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?

have you tried both of the RUU's? the original and 1.56?

My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution

did you try the 1.29 RUU?

yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this

BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R

rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.

IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.

Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?

SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?

mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen

tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.

Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.

well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny

I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.

[ruu] [stock] att 2.20 ota

Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Issues:*
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.*
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.*
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.
HTC One X for AT&T ROM Update | 8.02.2012
Starting August 2nd 2012, HTC will be rolling out a system update for the HTC One X.
This update will only be available for AT&T HTC One X customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > All Apps > Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
New features:
NFC Capabilities
Additional content added to HTC Hub
Third party music applications accessible from the Car application.
Fixes/Updates:
Wi-Fi connectivity fixes
Improved Bluetooth automobile compatibility
3G/4G connectivity improvements
HTC Sense fixes
Contacts synchronization fix
Network time fix (clock displays 30 minutes off)
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the battery as this will stop the update and your device may be rendered inoperable!
Getting Started
Before you proceed with the update, make sure you have done the following:
Set aside approximately 20 minutes to allow the device to update, possibly longer based on Wi-Fi network speed
Connect the device to a charger
Ensure the battery is charged to at least 30%
Connect to a stable Wi-Fi network to download the software file.
Installation instructions
To manually perform the update, follow these steps below:
From the Home screen, tap All apps and then tap Settings.
Tap AT&T Software Update.
Tap Check for updates.
Tap OK to download the update.
After you select your method of download, you will be prompted with a Wi-Fi or Data fee warning message. If this is acceptable, tap OK to start the upgrade process.
Status of the download can be viewed in the Notifications pull down.
Once the download is complete, the user will be prompted to install from the Notifications pull down. Tap the System update to begin the upgrade process.
Tap OK to begin the update process to software version 2.20.502.7.
Device will reboot and begin installation. Users will not be able to use their device during the installation process (approximately 10 minutes).
System update complete. Tap OK to continue
Manual system update instructions:
If you are outside of AT&T/Wi-Fi coverage, or the update is not found, you may perform a manual system update.
Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
Download and save the HTC One X™ for AT&T ROM update to your PC.
Connect your device to your PC via the supplied USB cable. NOTE: You must have HTC Sync Manager installed on your PC in order to run the update.
NOTE: If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/us/support/.
Ensure the device is properly recognized on the PC, then locate the HTC One X™ for AT&T ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
Follow all of the system update wizard instructions shown on your PC.
Once the update is complete, click Finish in the Wizard and the device will reboot.
Once the device reboots, the initial setup wizard will appear.
Once the initial setup process is complete, the device is ready for use.
Download
portions of this post copyright HTC 2012. All rights reserved to them.

kewl

http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe

.
Third party music applications accessible from the Car application.
Click to expand...
Click to collapse
WOOT.

Thank you for not using File Factory haha

"NFC capabilities"????
Sent from my HTC One X

OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms

XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.

slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yeah if you know what you're doing, but damn I'm going to miss the one stop flashing we used to have.

eraste said:
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Click to expand...
Click to collapse
I thought that was good?
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
This was to be helpful for us that already did OTA. I agree tho if one isint literate in the world of android wait to use this until all the things above are worked out.
scribed on my 2.20 HOX

slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yea thats fine if you know how, but why make everyones life harder when this upgrade is older then the asia 2.23.
its just going to make a lot of un needed posts to developers asking why the rom dont boot and so on. Run this ruu and it will cause more problems then anyone needs. As well as set you back from any S-Off development.
But that is my warning. Just saying, i cant see it from my house, my phone flashes
kernels just fine and always will. One Stop flashing.

I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.

gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I know i am, Ive been down this road several times in the past and i know what to flash and not to flash. That being said, I,m just trying to warn anyone that thinks the ruu is better then the rom alone...

gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX

To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2

Nrod0784 said:
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Anytime
scribed on my 2.20 HOX

eraste said:
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
Click to expand...
Click to collapse
Well I'm in america too! but i thought a warning would be nice, But what do i know

i think his warning was sufficient enough. he stated no benefits of flashing. unless you already did it prior. plus there are other threads who state warnings as well. people dont care or dont read and will flash anyway :laugh:
not taking sides i see what people do here that go against there better judgments or even when told not too :laugh:

Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.

eraste said:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
Click to expand...
Click to collapse
whoa and i just downloaded too lol. just in time add to the RUU collection lol

Building and installing ROMs for HTC

Hi, please let me know if this should me moved to another section.
I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.
So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.
Thanks!

miked63017 said:
Hi, please let me know if this should me moved to another section.
I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.
So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
I don't know much about the differences between dev'ing for HTC/Samsung, but an R.U.U is a Rom Update Utility, it includes 100% stock Rom, firmware, radios, etc. Flashing it will wipe ALL data on device (internal/SD card ) as well, so back Up any saved pics/data
Sent from my HTC One A9 using XDA Labs

So I got a flashable CM image, but it boot loops and I think I need to work on the kernel since I was using the one from hiaeul and I need hiaewhl. I pulled the sources from HTC and will start on that, but I have a question. Does anybody know what causes the "This build is for development purposes only" message?
I don't have the message on the stock rooted rom, but the message popped up after flashing CM, and coincidentally is where it bootloops at. I thought this pops up once you unlock the bootloader, but I haven't seen it until now.

miked63017 said:
So I got a flashable CM image, but it boot loops and I think I need to work on the kernel since I was using the one from hiaeul and I need hiaewhl. I pulled the sources from HTC and will start on that, but I have a question. Does anybody know what causes the "This build is for development purposes only" message?
I don't have the message on the stock rooted rom, but the message popped up after flashing CM, and coincidentally is where it bootloops at. I thought this pops up once you unlock the bootloader, but I haven't seen it until now.
Click to expand...
Click to collapse
It's built into the hboot/boot loader. Only way to change it is to hex edit the boot, which is risky. All HTC phones get that red msg after flashing (I forget exactly what causes it, I think custom boot.img, kernel, or something like that)
Sent from my HTC One A9 using XDA Labs

I could be wrong...but i remember only getting that red message about build being dev purposes only...when i was flashing or attempting to flash a different firmware meant originally for international handset versions after changing my CID/MID. It has been awhile since those days when i first got the A9 and nearly bricked it but i think that was the cause. If so, perhaps its the boot or kernel that is the issue? I also came from Samsung to HTC and it was quite the learning curve. ONly differences ive seen is...well...everything lol. Using RUUs, flashing via fastboot/adb sans odin, encryption of the internal memory, S-on/S-off and unlocking the bootloader. I am sure you know all these as well lol but just mean in general its a real b*tch working with this handset and it is picky on little things like specific order of events like flashing order......if you have several things to flash ive seen it mess up from just one part out of sequence when flashing. Anyhoo, still pretty new on a lot myself so I could be off but its what ive experienced so far. Good luck though and Ill be looking out your results for sure.
P.S - I also have sprint so I posted these elsewhere since no one else really looks out for our version much haha and you may need these for some reason later.
Sprint 1.60.651.4
http://www.mediafire.com/download/ki...1.60.651.4.exe
also
http://www.mediafire.com/download/d5...1/firmware.zip - for the Firmware zip to be flashed via RUU mode
System/recovery/boot images for stock are below:
http://www.mediafire.com/download/xe...zfh3x/boot.img
http://www.mediafire.com/download/oa...p/recovery.img
http://www.mediafire.com/download/48...g7j/system.img

mcbright80 said:
P.S - I also have sprint so I posted these elsewhere since no one else really looks out for our version much haha and you may need these for some reason later.
Sprint 1.60.651.4
http://www.mediafire.com/download/ki...1.60.651.4.exe
also
http://www.mediafire.com/download/d5...1/firmware.zip - for the Firmware zip to be flashed via RUU mode
System/recovery/boot images for stock are below:
http://www.mediafire.com/download/xe...zfh3x/boot.img
http://www.mediafire.com/download/oa...p/recovery.img
http://www.mediafire.com/download/48...g7j/system.img
Click to expand...
Click to collapse
Psst, none of your links are working. Looks like Mediafire deleted them.

help htc one a9
I recently updated my HTC One A9 to the new Marshmallow 6.01 version and now the wifi does not work at all (missing wifi module (8)) and the battery is at 4000%. My software number is 1.56.709.70, i believe this is the taiwan variant but it is unlocked. How do I fix this? Please help, do I flash an ruu or something? How do I know which ruu works for this phone?

JohnRogers23 said:
Psst, none of your links are working. Looks like Mediafire deleted them.
Click to expand...
Click to collapse
Ah damn! Ok ill upload them elsewhere...

JohnRogers23 said:
Psst, none of your links are working. Looks like Mediafire deleted them.
Click to expand...
Click to collapse
NEW LINK to Sprint 1.60.651.4
https://1drv.ms/f/s!AtVcVcbLOGTdgP9-e2NAN2fNHHIKVQ