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
Related
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.
I realize that there may be no easy solution (or none at all) for this predicament at this time. However, I thought it might be helpful to start a thread that is solely devoted to trying to get root access back on devices that unfortunately have already applied the mandatory Rogers update.
I have absolutely no answers, but I am more than willing to donate to someone who puts time into solving this issue. The other thread(s) are filled with pages upon pages of people just whining and complaining about Rogers and their ill-fated attempts to work with tech support. This is not my intention for this thread. There are a few posts within the sea of complaints that are directed towards a solution, but they are not the easiest to pick out.
Anyone with any ideas, PLEASE post here!
Hack the nbh?
Hi,
As I said in an earlier post, we all now know that the flashrec method is broken, and the goldcard method seems to be broken.
Trying to downgrade the rom fails with an error that basically says you can't install an older firmware over a newer version.
Question: How does the firmware perform this validation? Is it via the build number or timestamps on the files?
Question: Are we able to make our own NBH files? Is the structure known?
If someone can figure out the first question, then we will be half-way there, assuming someone can package nbh files.
gNoob
I'm in school right now (taking college courses now )
But, when I get home, i'll play around with it.
Question: How does the firmware perform this validation? Is it via the build number or timestamps on the files?
Click to expand...
Click to collapse
There is a "version" on the NBH that is checked. (when i get home today, i'll show you guys the down-and-dirty of each NBH [the latest and the old one])
Question: Are we able to make our own NBH files? Is the structure known?
Click to expand...
Click to collapse
Yes, and no. The structure is known. We *CAN* create NBH files, but they won't be signed. The stock SPL runs a check on the NBH files for a signature. If the signature is off, it won't flash. Therefore, no we can't.
Has anyone tried this method?
Could this method work. Treating the phone as a brick and bringing it to a pristine state?
Sorry, I'm a "new" user so I can't post urls correctly until the admins let me
code dot google dot com/p/android-roms/wiki/Unbrick
JakeArmitage79 said:
Could this method work. Treating the phone as a brick and bringing it to a pristine state?
Sorry, I'm a "new" user so I can't post urls correctly until the admins let me
code dot google dot com/p/android-roms/wiki/Unbrick
Click to expand...
Click to collapse
http://code.google.com/p/android-roms/wiki/Unbrick
Yeah they did that cause new users would spam Ads or other things.
Nope, this unbricking procedure doesn't work. It returns the following message:
Model ID incorrect!
Update Fail
Not too surprising, actually. If only we could get someone who works for HTC to sneak their signing key to Haykuro. Then an .nbh file with a version number greater than the version inside the SPL could be created and maybe the SPL would allow itself to be replaced.
Interesting challenge, this.
Okay, so I decided to try and see what was inside this RUU from Rogers. When it is initially run, it extracts its contents into my temp directory, and there you can find the rom.nbh file. I thought, maybe, it might allow me to switch out the rom.nbh with Haykuro's older image. So I started the installer, while it was sitting on the start page of the wizard, I replaced rom.nbh with Haykuro's, and it allowed me to get to the part of the updater where it uploads the image to the phone and tries to verify the update.
Unfortunately this fails because it reports the BootLoader version is 'incorrect'. I wonder if this means the wizard can be 'patched' to allow the downgrade?
I also noticed that there's a version fastboot.exe and adb.exe inside the installer's temporary files. I wonder if there's anything different about these versions of the files that might allow them to sidestep the new bootloader checks? Though I suspect without a correct signature this would also fail.
Just fiddling with this, trying to understand the details.
Old Rom:
Version: 1.85.631.5
Model ID: DREA21000
Target CID: ROGER001
New Rom:
Version: 1.89.631.1
Model ID: DREA21000
Target CID: ROGER001
I'll have more time to play with this later, i had some other stuff come up right now. Hopefully in a few days i'll have a bit more to put up.
Thanks Haykuro,
Just a little more information about my fiddling today. I verified that the fastboot.exe is pretty much stock. Trying to 'flash' the firmware with this returns a 'Remote not allowed' error. I also tried taking a look at ARUWizard.exe and ARUGlobal.dll. I thought these might be .NET code, but as far as I can tell, they are not, so maybe a standard decompiler would give some idea of what it's doing inside there? I might try to understand this a little more later.
120 volts to the battery terminals...
That should wipe the Rogers crap off the eff'ing memory and clean things up real good
With that wipe thought in mind is there a way to wipe the device and basically take it back to how it would have been before any rom image was installed at the factory? jtag'ing perhaps...
The problem I think is that the bootloader won't allow a version below version 1.89.631.1..
Man they locked this thing up tight...
Since my dream is pretty much now a useless crashing and freezing POS I was tinkering with the erase/flash <partition> commands of fastboot from the command line and all I get is the FAILED <remote: not allow> Same message when trying to flash a recovery image.
Tried to write an spl too and nadda...signature errors
Wonder if jtagging it would do the trick...hehehe
Too bad we can't JTAG. If we could then there wouldn't be all these DeathSPL bricks laying around :\
Yea eh...seems nobody has found a solution that would allow us to do that. I was reading the HTC service manual last night and it's not mentioned in it so I think if a brick needs fix they install a new motherboard.
t3mp3st said:
I realize that there may be no easy solution (or none at all) for this predicament at this time. However, I thought it might be helpful to start a thread that is solely devoted to trying to get root access back on devices that unfortunately have already applied the mandatory Rogers update.
I have absolutely no answers, but I am more than willing to donate to someone who puts time into solving this issue. The other thread(s) are filled with pages upon pages of people just whining and complaining about Rogers and their ill-fated attempts to work with tech support. This is not my intention for this thread. There are a few posts within the sea of complaints that are directed towards a solution, but they are not the easiest to pick out.
Anyone with any ideas, PLEASE post here!
Click to expand...
Click to collapse
Thank you for starting this, I agree with it all. Most willing to donate to whoever figures it out.
I also stupidly updated and am kicking myself for it. So hopefully we can get something done soon.
I'm definitely up for sending a donation to the winner too. Jeez am I looking forward to that day!
Hopefully Haykuro will soon have some time to share his expertise with us!
Anyone have any thoughts on what you see in the first pic attach to my post in this thread ??
Never mind...figured out where I got the file and like the others mine fails to complete because of a version error.
Ok I fixed the version error fail part...
With a hex editor I changed the version info in the ROGERSDREAM.nbh file haykuro posted here from 1.85.631.5 to 1.89.631.1 but now I get a "Signature incorrect" error. I need the 1.89.631.1 nbh so I can compare but trouble is HTC Sync since the update no longer see my device so the RUU won't run which screws me from digging the nbh out of a temp folder.
I just finished working with Matt Mastracci getting our bootloader unlocked successfully (s-off). This is the same as the EVO & Incredible's "Unrevoked Forever" just for the Hero now as well.
This allows you to flash an ***.img file to a specific partition on your phone without making a zip. You can also make a HERCIMG.zip (a zip with multiple images in it ie, system.img, data.img, boot.img, recovery.img) and flash that straight from hboot.
What s-off does is unlock hboot to be able to flash any HERCIMG.zip you provide it. It bypasses the need for HTC's private keys to have signed the zip, so you can make your own HERCIMG.zip with whatever image you wish to flash inside it (say the old grey on black HTC splash screen, or an engineering SPL) and it will flash with no problem.
This is completely permanent. It is below the radio level, so even if you RUU, it will still be s-off. Basically you will never have to "root" your phone again. You just flash something from the bootloader and it will work (for example, you RUU, then go into the bootloader and flash a recovery right away)
To verify successful after flashing, reboot to the bootloader. You should see "S-OFF" on the top.
For more information please go to http://unrevoked.com/forever
For the S-ON Method go HERE
Before you flash this, you NEED to upgrade to the newest hboot, version 1.47.0000 (due to finding variances in testing). You can do this by nandroiding, then running the Official 2.1 RUU in my rooting thread (post #2) and then rooting again and flashing this, then restoring your nandroid backup. You can check your bootloader version by typing (in command prompt)
Code:
adb shell
Code:
[B]
getprop ro.bootloader
[/B]
if that doesn't work (or returns nothing)
instead, type
Code:
adb shell
cat /proc/cmdline
and look for android.bootloader, and the value after that is your version
No one is responsible other than yourself if anything goes wrong after flashing this. We have had extensive testing with no errors.
Flash this as a normal zip in recovery.
Download
MD5: dd680a16c48b74d6d04e81e947825c56
I have the following radios (if you see one that is missing that is still in use by you guys, please post what you are using!)
Sprint
1.04.01.09.21
2.32.40.11.09 (eris)
2.41.04.02.02
2.42.00.03.10
2.42.01.04.27
2.41.05.02.03
Cell South
2.42.01.04.23
Alltel
2.42.01.04.23
MetroPCS
2.42.01.04.27
ACS wireless
2.42.01.04.23
Sprint 2.42.01.04.27 will also gladly do testing
Sent from my HERO200 using XDA App
Cell South
2.42.01.04.23
Sent from my HERO200 using XDA App
I would love to help! Thank you regaw_leinad!!!
MetroPCS
2.42.01.04.27
CyborgNM156 said:
I would love to help but I do not know how to find what radio I am using..LOL Sorry...My carrier is MetroPCS. If someone could explain how I go about finding which radio I am using...
Click to expand...
Click to collapse
go to settings, about phone then look at baseband version
I will gladly test for you, sprint, baseband already listed.
Thanks for your effort reg and matt, I think this is a great step forward for the HeroC!
2.42.00.03.10
I'm sorry, I still don't quite understand what this does. How does this benefit me as a basic non-cook user?
LiquidSolstice said:
I'm sorry, I still don't quite understand what this does. How does this benefit me as a basic non-cook user?
Click to expand...
Click to collapse
check out www.unrevoked.com/forever for more info
ACS wireless:
2.42.01.04.23
I know its the same as Alltell and CS, ALL ACG carriers will be using this radio unless the user flashed the sprint radio later as this is the one included in the ACG 2.1 update, just thought I'd mention...
This is really cool! good work.
Carrier:Cellular South
Radio:2.42.01.04.23
Hey there, I do realize what this is for, and it's awesome to see, however I was wondering if you could provide the md5 hash for this as it's such a sensitive-accurate file to be flashed. Anything I do that is with a low level flash I make sure the md5 meets up.
Here is some info on it.
BTW This MD5 is from my rom (South Paw) not from your mod, just using it as an example.
***CHECK THE FILE AFTER DOWNLOAD!!!***
MD5 Sum: f61654f61d7e75757d3307764061d20a
This sum is a mathematical 'hash' that can tell you if a file downloaded properly or not. There has been a lot of issues with people downloading a bad zip file from media fire, and now you can make SURE that it's downloaded properly before flashing.
Heres the info on it.:
Windows (and mac) users:
1. download Hashtag, a free md5 file hash check utility from here: http://beeblebrox.org/hashtab/
2. After downloading and installing, just right click on any file. On Windows, select properties and you will see a new "File Hashes" tab. On Mac select "File Hashes" (on 10.5 the "File Hashes" menu item will be found under the "More" submenu). This is will start HashTab providing more or less the same view that you see on Windows. This File Hashes window displays all the hashes for the file.
3. Check the hash to make sure it's the same big jumble of numbers and letters as the hash above. If it is not the same, the download is bad and you should redownload the file.
Linux users:
1. go into your linux terminal or shell (not the adb shell)
2. navigate to the folder that contains the rom (mine is in downloads, so you would type 'cd Downloads')
3. for my rom, type 'md5sum SouthPawV1.5Final.zip
4. the output should look as shown:
Code:
OUTPUT_ZIP$ md5sum SouthPawV1.5Final.zip
f61654f61d7e75757d3307764061d20a SouthPawV1.5Final.zip
[email protected]:~/Desktop/kitchen/OUTPUT_ZIP$
hexskrew said:
Hey there, I do realize what this is for, and it's awesome to see, however I was wondering if you could provide the md5 hash for this as it's such a sensitive-accurate file to be flashed. Anything I do that is with a low level flash I make sure the md5 meets up.
Click to expand...
Click to collapse
Is this a guide for me to learn what an md5 is? lol just kidding
I am definitely going to do that, as I did with a few other of my releases on here. I haven't posted anything yet though, and I won't be for another day or so, so don't get worried yet.
Is it safe?
This may be a noob question and if so I apologize but can someone tell me if I have a non-Sprint Hero that currently has radio 2.42.01.04.23 is it safe for me to update to 2.42.01.04.27 or is it only for Sprint users?
Oh no man, I wasn't trying to school you on it or anything, but a lot of people don't know about md5 checking, so I figured just in case you didn't I would post it for convenience (just a copy/paste from my own thread).
You are the man regaw, I am definitely not denying that. You been on this scene before I was gnawing at the teeth for my Hero And you have definitely made your uber share for the community.
hexskrew said:
Oh no man, I wasn't trying to school you on it or anything, but a lot of people don't know about md5 checking, so I figured just in case you didn't I would post it for convenience.
You are the man regaw, I am definitely not denying that. You been on this scene before I was gnawing at the teeth for my Hero And you have definitely made your uber share for the community.
Click to expand...
Click to collapse
Haha nah it's cool I was kidding (hope you saw the just kidding changed a different color lol)
It's definitely a good post, personally I just use the console md5sum for windows and put it in C:\Windows\system32
http://etree.org/md5com.html
directions on the site above
I have just one question. If we use this, do we lose the ability to update radio until a new release from you guys, or does flashing a new radio just turn off the s-off (does that make it s-on I assume?) In the unrevoked faq there, it says it can't be undone, but from what I can tell it does flashing a new radio would undo it unless this breaks the ability to do so somehow...
jamesjharris01 said:
This may be a noob question and if so I apologize but can someone tell me if I have a non-Sprint Hero that currently has radio 2.42.01.04.23 is it safe for me to update to 2.42.01.04.27 or is it only for Sprint users?
Click to expand...
Click to collapse
It should work, you may need to re-program your PRL afterwards, and I dunno if you can downgrade a radio, if not you may loose the ability to unroot by running the RUU.
ipfreelytech said:
It should work, you may need to re-program your PRL afterwards, and I dunno if you can downgrade a radio, if not you may loose the ability to unroot by running the RUU.
Click to expand...
Click to collapse
well i know for sure you can downgrade your radio, but I have no idea what to say about flashing a Sprint radio from another carrier
regaw_leinad said:
well i know for sure you can downgrade your radio, but I have no idea what to say about flashing a Sprint radio from another carrier
Click to expand...
Click to collapse
It's fine, as part of the rooting process on my phone I had to flash the sprint leaked 2.1 RUU so i was on a sprint radio up until the ACG ruu came out.
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
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
reptarsaurusflex said:
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
Click to expand...
Click to collapse
Generally I think you are out of luck until they launch the Windows 10TP for HTC M8's. When that happens, you should be able to use the Windows Phone Recovery Tool to re-flash your phone. It looks like it's basically a re-skinned version of the Lumia Software Recovery tool, and it only makes sense for them to release this as well if they are going to be providing a way to recover and flash non-Lumia branded phones in the future.
There is a way to re-flash the HTC One M8 for Windows if you have the ROM, but so far only the Verizon version has leaked. I hope this is not your only phone, because if you wait a month or so you should be able to re-flash using the Microsoft tool
You have absolutely no right to be mad at Microsoft, HTC and/or T-Mobile for the problems. They are completely justified making you pay the deductible to get this fixed, why should they eat the cost of fixing it?
Don't get me wrong, I don't blame anyone but myself for this. I'm simply surprised that there isn't a recovery option out there in general. Someone could have a problem that isn't their fault at all that could benefit from having this. That being said, I have an open ticket with the HTC dev team. All I really want is access to a ROM that must clearly already exist. The software got on the phone in the first place, right? Of course I am not a dev and probably have no idea what I'm talking about. I apologize if I'm coming off as an ass looking for a hand out. It just seems to me that this is a simple issue with a simple fix. I know from when I had a Lumia device that I could open up the navifirm+ software and download any ROM for any windows phone from any region of the world.
reptarsaurusflex said:
Don't get me wrong, I don't blame anyone but myself for this. I'm simply surprised that there isn't a recovery option out there in general. Someone could have a problem that isn't their fault at all that could benefit from having this. That being said, I have an open ticket with the HTC dev team. All I really want is access to a ROM that must clearly already exist. The software got on the phone in the first place, right? Of course I am not a dev and probably have no idea what I'm talking about. I apologize if I'm coming off as an ass looking for a hand out. It just seems to me that this is a simple issue with a simple fix. I know from when I had a Lumia device that I could open up the navifirm+ software and download any ROM for any windows phone from any region of the world.
Click to expand...
Click to collapse
Fair enough. Its a bit weird that only Nokia put out any kind of program to re-flash phones, but I have a feeling that the app Microsoft has put out will, going forward, be used to reflash any Windows Phone that is having problems. They kind of need to provide that functionality if they are going to take control of the update process from the carriers (which i know they want to do, whether they actually pull it off remains to be seen).
I'd say just hang in there, you will likely be able to re-flash in a month or so. I hope you can somehow get access to the rom, but there isn't program released to flash it on the phone (though there are ways, look at the Verizon RUU thread. There is also a Youtube video out there showing how to do it)
i was the first with htc w8 (tmous) to hack the w10 beta on it if you check my twitter.
the only reason why i even considered to do this is because i have a way out.
that can't be said for public. so why the hell you didn't check if you have
a way to go back to stock before even considering such a highly
experimental thing to your precious device?
sure you can't expect any support from ms or tmous for that scenario.
i flashed back to w81 the next day already because of htc related bugs.
i will restore it for you if you send it to me and pay 2-way shipping.
this is a one time personal offer from me that i will do for you.
contact me via pm if you didn't send it in yet.
let this be a lesson to you guys...
reptarsaurusflex said:
I did something really dumb even though I was advised not to. I managed to get the Windows Phone 10 Technical Preview on my HTC One M8 for Windows. The OS version that got pushed to it simply is not compatible with this hardware and so many things don't work. I want to go back but the Microsoft-provided recovery tool doesn't detect the phone because it was never intended to work with this model. In short, my question is does anyone have a way to just flash an HTC One M8 for Windows back to the factory T-Mobile ROM that it came with out of the box? If so, where do I get it and how can I flash to it? HTC has no recovery tool to speak of for this phone, Microsoft was just as much help, and TMo wants me to pay an insurance deductible before they will replace the thing. I will be ever so grateful if someone can help out.
Thanks!
Click to expand...
Click to collapse
You might be out of luck for now at the moment. I'm sure the TMo ROMS aren't available, otherwise you would be able to. Remember that the trick to update to Windows 10 Preview was AT YOUR OWN RISK due the fact that the phone isn't OFFICIALLY SUPPORTED
HD2Owner said:
i was the first with htc w8 (tmous) to hack the w10 beta on it if you check my .
the only reason why i even considered to do this is because i have a way out.
that can't be said for public. so why the hell you didn't check if you have
a way to go back to stock before even considering such a highly
experimental thing to your precious device?
sure you can't expect any support from ms or tmous for that scenario.
i flashed back to w81 the next day already because of htc related bugs.
i will restore it for you if you send it to me and pay 2-way shipping.
this is a one time personal offer from me that i will do for you.
contact me via pm if you didn't send it in yet.
let this be a lesson to you guys...
Click to expand...
Click to collapse
I'd like to know how you did this instead of sending you my phone.
flashed the stock rom.
HD2Owner said:
flashed the stock rom.
Click to expand...
Click to collapse
Is it possible to flash the stock rom on a verizon phone?
sure. by stock rom i mean the original rom meant for the device/carrier.
on verizon w8 -> verizon rom
on at&t w8 -> at&t rom
on tmous w8 -> tmous rom
don't try to flash different carrier rom. it won't work.
all 3 carrier variants have different modelID which is checked before allowing flash.
HTC One M8 for Windows
HD2Owner said:
sure. by stock rom i mean the original rom meant for the device/carrier.
on verizon w8 -> verizon rom
on at&t w8 -> at&t rom
on tmous w8 -> tmous rom
don't try to flash different carrier rom. it won't work.
all 3 carrier variants have different modelID which is checked before allowing flash.
Click to expand...
Click to collapse
I have been looking everywhere for the Verizon rom and software so I can reflash my phone. Do you happened to know where I can get these?
dans95tbird said:
I have been looking everywhere for the Verizon rom and software so I can reflash my phone. Do you happened to know where I can get these?
Click to expand...
Click to collapse
there: http://forum.xda-developers.com/showpost.php?p=55201370&postcount=2
download the htc RUU that i attached to this post and extract with winrar.
place the htc w8 verizon nbh in the extracted RUU folder with filename "RUU_Signed.nbh".
then go into bootloader (power off, then hold vol-&vol+ while pressing power until it vibrates).
it will show white bootloader screen with hardware info.
when the pc installed the drivers for bootloader mode it switches from "serial" to "usb" on the bottom.
then doubleclick the ROMUpdateUtility.exe and it will flash the phone.
everything will be wiped of course.
HD2Owner said:
there: http://forum.xda-developers.com/showpost.php?p=55201370&postcount=2
download the htc RUU that i attached to this post and extract with winrar.
place the htc w8 verizon nbh in the extracted RUU folder with filename "RUU_Signed.nbh".
then go into bootloader (power off, then hold vol-&vol+ while pressing power until it vibrates).
it will show white bootloader screen with hardware info.
when the pc installed the drivers for bootloader mode it switches from "serial" to "usb" on the bottom.
then doubleclick the ROMUpdateUtility.exe and it will flash the phone.
everything will be wiped of course.
Click to expand...
Click to collapse
since ppl dnt seem to give u a thanks ill spam the thread any say thank and the "thanks" button....ppl appreciate his help!!!
The latest build of Win10 works way better on a One M8 btw. I have installed it using the registry method and running it without many problems. So if you have a t-mobile/at&t version of this phone (where there is no RUU availible) with windows 10 installed i advice upgrading to the latest build.
really? i noticed bugs with background picture not showing and many htc apps/settings not working..
they work now on latest build?
in the new version of windows phone recovery tool, ms added support for htc devices.
http://go.microsoft.com/fwlink/?LinkID=525569
Any luck with Verizon HTC One?
HD2Owner said:
in the new version of windows phone recovery tool, ms added support for htc devices.
Click to expand...
Click to collapse
I downloaded the newest version, 2.0.3, of the recovery tool. Even though it says it supports HTC devices it still fails to rollback my Verizon HTC M8. I receive the error: "Software Package is not found on server"
This is after the tool recognizes my device and asks me to restart in boot-loader mode.
Anyone else have success with using ver. 2.0.3 with a HTC M8?
Shockakohn said:
I downloaded the newest version, 2.0.3, of the recovery tool. Even though it says it supports HTC devices it still fails to rollback my Verizon HTC M8. I receive the error: "Software Package is not found on server"
This is after the tool recognizes my device and asks me to restart in boot-loader mode.
Anyone else have success with using ver. 2.0.3 with a HTC M8?
Click to expand...
Click to collapse
Recognized my T-Mobile M8 and flashed WP8.1 successfully.
Not able to update to latest Windows 10 mobile TP build
My HTC One is currently on 10.0.12562.84 (Build 10080). For some reason I am not able to see the latest build 10.0.12648.133 (Build 10149). Any one able to update to the latest build. Any idea why I'm not seeing it still?
Tried using the phone recovery tool to flash back to 8.1 but it says no builds available.
germanh said:
Tried using the phone recovery tool to flash back to 8.1 but it says no builds available.
Click to expand...
Click to collapse
which variant? verizon, at&t or tmous?