Database Info

Rom Flashing Newbie

Hi,
I have been playing with WM devices for a few years but I have never flashed a ROM before and I am hoping to unlock and then flash a new rom tonight. (Yes this is my idea of good time on a friday night!)
I just want to make sure that I have everything right before I get going as I really don't want to brick my phone....
First off, I have a telus TP2 running WM 6.1. I don't know the radio version.
Here are the steps:
1. Unlock with hardspl found it here.
2. Hard reset the phone after unlock.
3. Install the new ROM. (I like the BigCoOkieColor ROM.) I downloaded the latest telus version. I think this is just run off a .exe install from the PC.
4. Hard reset again.
So a few questions...
1. Do I have to install radio software? Will the new ROM wipe this out?
2. What set up to I have to do to get my voice and data up and running again? (Like when my carrier initally set up the phone.)
Sorry for the newbie questions, but I really don't want to srew this up....
Thanks in advance.

First off, you are right to be slightly cautious, you want to make sure you have done it properly, and so far you have taken the necessary steps to prepare yourself for a successful flashing experience.
1) All custom ROMs will not come with a radio, this means that whichever radio you have installed will stay. You can find which radio you are using by going to Start > Settings > System > Device Info. If you want to flash the stock telus radio you can go here:
http://forum.ppcgeeks.com/showthread.php?t=90342
If you want to flash a custom Radio, you need to be security unlocked. Follow the instructions in this thread:
http://forum.ppcgeeks.com/showthread.php?t=106571
2) Dial you carriers programming number. For verizon I dial *228 and hit option 1. Voice, data, sms are all restored and I can use my phone like normal. I'm not sure how telus does it, but it is exactly like when you first get your phone.
Hope that answers your questions, let us know if you have any other questions that arise.

Thanks for the help Burtonsnow8.
I am of the school of thought that if it's not broken don't fix. I'm not sure if the radio is included in the rom I've chosen. If I flash and find it doesn't include the radio, do I have to flash back to the stock rom?
I have a buddy who is the manager at the local telus store. I'm pretty sure that he'll give me the programming codes. (I did a quick search and couldn't find them online.)
Thanks again for the help,

If you flash a ROM that does not include a radio it doesn't mean that you will have no radio, it just means that you will not be changing your current radio. Honestly I wouldn't worry too much about the radio unless you are having serious reception/GPS issues. Anyways, without paying for the security unlock you cannot flash a new radio regardless, so as of now I'd say you are in the clear.
*22803
That should be the telus programming code.

How To UN ROOT. TUTORIAL. Your Problems are solved!

UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....

Thanks op.

Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.

arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.

Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?

sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!

Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...

sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!

Well, worry even less! Special thanks to Calkulin!

thankssssss

Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop

I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...

I'm getting error 155 running Ava Froyo and trying to go back.

blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.

How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?

joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.

tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.

Yes. I have .79, thanks!
Sent from my PC36100 using XDA App

[ROM] DHD Vodafone Australia Stock Branded Rom 1.32.178.5

I finally got around to rooting and S-OFFing my phone today, while I was at it I used clockwork recovery to make a backup of the Stock VHA Branded ROM.
I saw a few people were looking for this so here it is. Feel free to mirror it or whatever, this is my first ROM-dump so if anything is amiss or I did something wrong please let me know. I still have the device available to make further dumps.
This is for the Desire HD (Obviously) Branded by Vodafone Australia.
hxxp://depositfiles.com/files/3x1c6v6hj
Sorry for posting a link as a new member, I thought this would be worth it.
EDIT: Obviously the dump is all at factory defaults, on first boot it should be like buying a new phone, from a bloatware company.

Except it will be a rooted bloatware rom?

That's the point People have been asking for it as a backup rom, as flashing a non Vodafone rom may void certain warranties, which flashing this back could increase your chance of keeping. I personally upgraded my own DHD to a much better ROM as soon as I could.

Awesome, ive been waiting for the stock ROM. Good Work

Sting17 said:
Awesome, ive been waiting for the stock ROM. Good Work
Click to expand...
Click to collapse
No worries man. Let me know how it turns out if you use it. Everything should be at factory defaults as I wiped the device with Clockwork before making the backup. If you find anything wrong just let me know in this thread.

Thanks Should be handy for warranty issues!

Thanks champion!

Thanks mate. I've downloaded and it all looks good so far (haven't flashed though to check).
Is it rooted with VISIONary r12?

Sweet, been waiting for this. Thanks mate!
Sent from my Desire HD

Yeah the process I followed was Perma root with VISIONary v12, install hboot, install clockwork test, use clockwork to wipe to factory and then backup to SDcard. I'm unsure as to the exact details of how VISIONary works at this time so it may not still be rooted, I don't know if root persists after factory reset.

Thanks! this is getting downloaded for safety/warranty reasons.

Thanks a lot for extracting and hosting the original (Vodafone AUS) ROM!
Am i right, that this is the only thing you need to set your mobile into delivery condition? If there are some other traces of flashing they might decline warranty, too!
Perhaps, if you have the time and pleasure, you could write a detailed how-to for newbies (with links to software you need, e.g.!) how to extract the original firmware.
I think this would be necessary if the DHD will be available in other countries on other network providers (with their own ROM).

Excellent! I'm just 2 days into my new DHD from Vodafone Oz and just about to do the same... Rooting!
I'll probably make a back for myself but I'm downloading this one too... Just to be safe.
Thanks heaps Kazuroka!
BTW - Don't listen to those lame ppl who don't have anything positive to add.

Just a note: I believe that this ROM, although the stock Vodafone image, is a rooted one. So if Vodafone have a moderately smart technical department they will still be able to tell that it is not running their complete stock image.

@ivolol: That's exactly what i'm thinking about! For e. g., changing ROM on my Windows Mobile phone requires a modification of the bootloader. If you flash back your old (original) ROM you have to remember to change the bootloader to original too. Otherweise you have the original ROM on your phone but another bootloader and this could be be detected very easily. I know that the procedure changing ROM on DHD is another than on Windows Mobile, but perhaps you have to think about more things than only flashing the original ROM?!

ivolol said:
Just a note: I believe that this ROM, although the stock Vodafone image, is a rooted one. So if Vodafone have a moderately smart technical department they will still be able to tell that it is not running their complete stock image.
Click to expand...
Click to collapse
After flashing back the backup ROM I did not have root. I installed Terminal Emulator and tried to su, and even downloaded VISIONary+ and re-Rooted the device. However I did still have the Eng hboot, as that was not included in this backup. I have a copy of the original hboot from when S-OFFed the phone, I will see what I can do about getting the original hboot and stock ROM into one package for everyone, and then perhaps write a tutorial for flashing them back individually. I MAY NOT, however, write the tutorial as I am still rather new and would not like to lead people into doing something the wrong way. I will also include the stock hboot in a seperate archive for those who have already downloaded this release.

Original HBOOT: http://www.megaupload.com/?d=X1QFR2D2

could be better i gues...thanks OP

ROM Version: 1.32.178.5
Download link: http://www.multiupload.com/3UFP92FNMJ
Size: 558 MB
md5sum: 834dc33ab316a702c93b61533681356b
This is the original system.img that comes on a brand new Vodafone Desire HD.
This image was dumped manually without Visionary messing with stuff, and Obviously the image is NOT rooted. It's completely stock.
This would probably be the best image to use if you're worried about returning the phone
Note: I have had to return a Desire HD to Vodafone who did not check that it was rooted and S-OFF'ed - So, don't worry too much.

OzJD
Why is your file so much bigger than Kazuroka's original upload and also just wondering your method of extracting the img?
Thanks

Canadian i9020a stock

Hi, does anyone have a backup image or a flashable zip of 19020a UCKB2 , 2.3.3 software. I accidently, deleted my backup. I mainly need the UCKB2 radio modem software in case of future warranty. I have the stock 2.3.3 software but missing radio, i am currently running xxkb3 radio, thanks.

pterry30 said:
Hi, does anyone have a backup image or a flashable zip of 19020a UCKB2 , 2.3.3 software. I accidently, deleted my backup. I mainly need the UCKB2 radio modem software in case of future warranty. I have the stock 2.3.3 software but missing radio, i am currently running xxkb3 radio, thanks.
Click to expand...
Click to collapse
That is one thing we are lacking right now...

Other than cwm and rooting. I am stock. Give me some instructions on how to download the modem and I'll get it posted.
I am also 90% sure that I did a nandroid backup before rooting. Otherwise it's stock with root on the backup.
Sent from my Nexus S

Ill be picking one up brand new in a few hours. I can pull the radio if i am shown how.

someone just posted the radio.img file on the NS general discussion board, u may want to try it out even though its not been tested.

Ya, notexactly sure how to pull radio software
Some body will post a flashable radio on future. Ph
One has only been out a week or sp
Sent from my Nexus S using XDA Premium App

You can get the radio from this post
http://forum.xda-developers.com/showthread.php?p=13103802#post13103802

Thanks, flashed KB2 radio with sucess, looks stock now, i have done a backup of stockrom and radio again, much appreciated.

Could someone please post there boot.img I lost my backup and can't boot

How would I back up my stock ROM with nandroid?

Hi,
I have a new AT&T htc one x. Before I get into any custom roms, rooting, or flashing anything, I want to back up my entire phone, like a snapshot image.
I know that Nandroid is what I want, but don't I need to root, and flash clockwork recovery first? If I do that, will my backup image truly be stock at&T?
I've had a bear of a time reverting to stock before, and this time I figure that I will just back up as step #1 before I try ANYTHING.
Thank you

lamenramen said:
Hi,
I have a new AT&T htc one x. Before I get into any custom roms, rooting, or flashing anything, I want to back up my entire phone, like a snapshot image.
I know that Nandroid is what I want, but don't I need to root, and flash clockwork recovery first? If I do that, will my backup image truly be stock at&T?
I've had a bear of a time reverting to stock before, and this time I figure that I will just back up as step #1 before I try ANYTHING.
Thank you
Click to expand...
Click to collapse
If you data isn't too Important and you have saved else where then you can always ruu back which will make it 100% stock ans youl lose root and cwm so it will be like you nought the phone
Sent from my HTC One X using xda app-developers app

You need root and unlocked bootloader in order to install recovery and make a nandroid. So its not possible to make one before rooting.
As mentioned, running the RUU will return you to stock, if you ever need it. With the exception that the bootloader can never be truly returned to LOCKED, it will say RELOCKED.
If you are talking about backing up your user data before rooting, I don't think there is an easy answer. For things like Gmail and Contacts, just keep them on the cloud. SMS messages can be backed up by using various apps. For other data (like game save data, etc) there are also apps that may help. Otherwise, its really not that hard to restore settings, etc. manually.

Thanks, I got into a situation where I could not run the RUU, even though I know it was the correct one. (People on the board told me that the RUU I was running did match my CID).
I think the issue was that I had an unlocked bootloader and was rooted.
Even though I relocked the bootloader, the RUU still refused to run. Prior to that experience, I had always thought that if you just relock your bootloader and run the correct RUU, going back to stock is as easy as that.

It should be as easy as that yes (relock bootloader and run RUU for your CID). Seeing as you are AT&T, you must have SuperCID in order to unlock the BL (unless you changed it back to the AT&T CID). Technically, SuperCID should let you run any RUU, even one older than what is installed. But I know a few folks have had trouble trying to "roll back" from 1.85 to 1.73. Are you trying to run the 1.85 RUU?
Also, I would check the simple stuff. Does HBoot report "relocked" status? For at least one person that I know of, simply reinstalling the drivers on your computer (by reinstalling HTC Sync) fixed his issue of not being able to run the RUU. You could also try re-downloading the RUU, to make sure it wasn't downloaded improperly (corrupted, etc.).

This is the worst part about getting into altering your device, the comfort and safety of unlocked bootloader, custom recovery, etc only come AFTER you finished breaking into the darn thing. I recommend finding a good guide on android authority, or a one click designed by someone here, and just spending 10 times as long as you should making sure you get it right, you'll be fine welcome

Piggybacking
So, I wasn't 100% clear on this, and I've been searching the Goog and the forums and wasn't able to find the clear definition. I have my AT&T HOX rooted (1.85), bootloader unlocked and loaded TWPR for recovery. Immediately I made a full Nandroid backup of my stock (rooted) ROM. If I do a wipe/factory reset, install CM10 and then want to go BACK to the Nandroid backup... do I only need to wipe/factory reset and restore? I'd rather not soft brick or hard brick my phone only having it 2 days =). Thanks!

chris.sterbank said:
So, I wasn't 100% clear on this, and I've been searching the Goog and the forums and wasn't able to find the clear definition. I have my AT&T HOX rooted (1.85), bootloader unlocked and loaded TWPR for recovery. Immediately I made a full Nandroid backup of my stock (rooted) ROM. If I do a wipe/factory reset, install CM10 and then want to go BACK to the Nandroid backup... do I only need to wipe/factory reset and restore? I'd rather not soft brick or hard brick my phone only having it 2 days =). Thanks!
Click to expand...
Click to collapse
Restoring wipes the system and data partitions for you, but yeah that's it.