Revert Back to Telus 1.84 ROM - Desire HD General

Hello
I'm trying to revert my phone back to the stock ROM from telus. I've downgraded to 1.32 and gave up when i found out that sound on the desire HD doesnt work on CM7.
How do I revert back?
ive searched the forum and tht's all ive found
" just flash a stock RUU? That uses your PC to flash your phone, not bootloader."
any help would be appreciated. Where do i get the RUU file and how do i go about doing this.
A $10 paypal donation will given to anyone who helps. i really need to get the phone back, its my girlfriend's. (
btw i have turned S-air off and done a perm-root with visionary already.. how do i get the cherry back in place?lol

You can flash either Raidroid in clockworkmod, or use Telus RUU. Android Revolution HD is also a good (the best) option if you want performance and good battery life.
Raidroid is a stock ROM that will keep your root and S-OFF, so it is easy to flash a custom ROM in the future. RUU will revert your phone to stock, Radio S-OFF will remain if you used it. Android Revolution HD is the best custom ROM out there. Every option gives you working sound.

jkoljo said:
You can flash either Raidroid in clockworkmod, or use Telus RUU. Android Revolution HD is also a good (the best) option if you want performance and good battery life.
Raidroid is a stock ROM that will keep your root and S-OFF, so it is easy to flash a custom ROM in the future. RUU will revert your phone to stock, Radio S-OFF will remain if you used it. Android Revolution HD is the best custom ROM out there. Every option gives you working sound.
Click to expand...
Click to collapse
are there any issues with android revolution?like sound problems with the CM7?

Nope, Telus users are reporting that it works great. Some users have had small microphone echo while using it, but that can be fixed by flashing a simple zip in clockworkmod just like you would flash a ROM.
http://www.wbakkercomputers.nl/mic_fix.zip

jkoljo said:
Nope, Telus users are reporting that it works great. Some users have had small microphone echo while using it, but that can be fixed by flashing a simple zip in clockworkmod just like you would flash a ROM.
ok, i'll try android revolution hd. Earlier today when i checked the terminal was showing the # instead of $. now when i checked, its back to $. I went on visionary app again, did a temp root and perm root, and checked the terminal again but its still showing the $ sign.
i don't know what the build number is for, but its now on 1.32. I wanna go back to the 1.84. I've noticed that the revolution HD has the 'official HTC RUU 1.84.61.2', so in the process of flashing the ROM, 1.84 should be back, right??
I'm a little bit confused about baseband versions and md5 checksums. mine is 12.28b.60.140eU_26.03.02.26_M. which radio version should i flash with?
I'm totally new to this and I hope to get working by tomorrow night. I really appreciate your help, donation will definitely be made once i get this thing working. i couldnt pick up any calls today..lol
Thanks a lot
Click to expand...
Click to collapse

ziyaad89 said:
Hello
I'm trying to revert my phone back to the stock ROM from telus. I've downgraded to 1.32 and gave up when i found out that sound on the desire HD doesnt work on CM7.
How do I revert back?
ive searched the forum and tht's all ive found
" just flash a stock RUU? That uses your PC to flash your phone, not bootloader."
any help would be appreciated. Where do i get the RUU file and how do i go about doing this.
A $10 paypal donation will given to anyone who helps. i really need to get the phone back, its my girlfriend's. (
b
btw i have turned S-air off and done a perm-root with visionary already.. how do i get the cherry back in place?lol
Click to expand...
Click to collapse
Android Revolution works perfect, and has lots of customization options.
In case you still want Cyanogen, CM7 nightly build 12 worked just fine on my Telus... It has the sound fix built in to it.

ziyaad89 said:
jkoljo said:
ok, i'll try android revolution hd. Earlier today when i checked the terminal was showing the # instead of $. now when i checked, its back to $. I went on visionary app again, did a temp root and perm root, and checked the terminal again but its still showing the $ sign.
i don't know what the build number is for, but its now on 1.32. I wanna go back to the 1.84. I've noticed that the revolution HD has the 'official HTC RUU 1.84.61.2', so in the process of flashing the ROM, 1.84 should be back, right??
I'm a little bit confused about baseband versions and md5 checksums. mine is 12.28b.60.140eU_26.03.02.26_M. which radio version should i flash with?
I'm totally new to this and I hope to get working by tomorrow night. I really appreciate your help, donation will definitely be made once i get this thing working. i couldnt pick up any calls today..lol
Thanks a lot
Click to expand...
Click to collapse
After you flash a ROM with 1.84, you'll be back on 1.84
I wouldn't mess around with radio just yet, it works fine using stock Telus radio. If you notice battery drain or reception issue then flash the recommended radio.
Click to expand...
Click to collapse

cue_32 said:
ziyaad89 said:
After you flash a ROM with 1.84, you'll be back on 1.84
I wouldn't mess around with radio just yet, it works fine using stock Telus radio. If you notice battery drain or reception issue then flash the recommended radio.
Click to expand...
Click to collapse
ok so i'm running revolution HD right now, and the in-call sound quality is really bothering. I've installed that zip file mentioned above that is "supposed" to fix it but still the same
Are you running CM7 on yours?hows the incall sound quality? i might revert back to the stock ROM. Its weird how a slightly modified stock ROM is giving such an issue.
Click to expand...
Click to collapse

Related

Nandroid Backup > Run Release RUU 2.27.651.5 > Nandroid Restore = Safe?

----------------------------------------------------
Original Text:
----------------------------------------------------
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU, RUU_Hero_C_Sprint_2.20.651.1_signed_test, and re-push flash_image or does it even really matter which hboot I'm running on (figure hboot is the only thing permanently stuck on phone from RUU)?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Any thoughts welcome
-----------------------------------------
This is sorta deprecated now that we have Root on the Release RUU, so repurposing the thread.
My new question: Now that i've rooted the Official Release version, can I restore my old nandroid backup without breaking my phone?
I did a nandroid backup of my fully-set-up Fresh 2.1.2 Install before I ran the Official RUU to 2.27.651.5 and now I'm wondering if it will break anything to "restore" that backup.
Again, any thoughts are welcome.
diaknia said:
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU and re-push flash_image or does it even really matter which hboot I'm running on?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Click to expand...
Click to collapse
to my knowledge if your hboot changes from 1.56 to the one from the official you will lose root as of now, the test RUU still has root but its super buggy, why would you want to flash the official or the test anyways, theres roms here that blow the stock ones out the water, but once again to my knowledge you WILL lose root. And the test ruu with root has mad issues you should do a search bro as far as upgrading to the newer hboot well im not sure if it has features but the devs are still trying to break root in the new hboot.
check this out bro just in case you already flashed it http://forum.xda-developers.com/showthread.php?t=693449&highlight=hboot
I have not yet flashed the Test RUU.
From what I understand the Test RUU still has su built in, so all I need to do is re-push flash_image to get a custom recovery back on it and I'm golden from there.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
diaknia said:
I have not yet flashed the Test RUU.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
Click to expand...
Click to collapse
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
good to know
dirkydirk23 said:
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
Click to expand...
Click to collapse
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
diaknia said:
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
Click to expand...
Click to collapse
There is nothing wrong w/ the hboot. and the hboot isn't even the thing blocking root. The audio issue seems to differ from phone to phone, I have never had audio issues on my phone.
Thanks for the responses, regaw and dirky.
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
On a side note.... i'm an eager follower of the official RUU ROOT thread on the dev sub-forum, Regaw, keep up the good work. Still feel bad for you that you've been stuck without root so long...
When you crack the thing, and I maintain hope you will, that's when I'll probly go and upgrade to the Release RUU.
diaknia said:
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
Click to expand...
Click to collapse
Basically this.
abcdfv said:
Basically this.
Click to expand...
Click to collapse
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
dirkydirk23 said:
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
Click to expand...
Click to collapse
If you had run the test ruu and already pushed flash_image and custom recovery back to the phone then you can restore the original hboot in about 10 seconds if you want.
From recovery flash the .zip attached here and the hboot will revert to 1.41 instead of 1.47.
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
diaknia said:
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
Click to expand...
Click to collapse
I am curious about this also. Currently running fresh 2.1.1 previously from a 1.5 root and was thinking about updating to the .5 ruu and doing the root and than restoring a nandroid

[Q] Is there a Stand-alone Radio Image Update to 2.22.27.08?

I'd like to use the new radio with my oem Donut. Is it as simple as taking the file from one of the update guides and flashing it in the traditional manner? I'm kind of noobish so I'm reluctant to try to take one piece of a Froyo update guide and flash the radio. I'm not really in the market for a sleek black paperweight.
I wouln't do it!
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
QUESTION: What does DONUT have that you like so much?
Edubyah said:
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
Click to expand...
Click to collapse
lol, I agree, that's why I posted first.
QUESTION: What does DONUT have that you like so much?
Click to expand...
Click to collapse
SPEED. I tried the TMUS rom posted up here a few days ago and it was ok, much better than other Froyo ROMs I've tried, but still laggy compared to my oem androoted Donut.
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
I'm scared to try this. Is this the radio that came with the T-MOUS Fro-Yo OTA? I wonder why there isn't a thread for it yet.
Moving to General
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
The hboot? Which hboot are you talking about? The first half of the ota update succeeded but the second half failed so I have the new SPL but not the new radio or OS.
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
d3vilskid said:
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
Click to expand...
Click to collapse
Cool, did you or she notice any improvements?
Yea i got to messed with it a little bit more, signal is pretty strong and stays constant, but that might vary from phone to phone, not much to say about the market since it was down a couple days back. Overall she is satisfied with it. Cant wait till it is ported to the 32b phones so we can take advantaged of the extra 10-15mb it frees up.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
So I just flash this through recovery as I would any other zip file? Any idea if this is compatible with older roms? If I nandroid back to my oem 1.6 without rolling back to 23.02 will my phone explode? How about Eclair?
If I flash this is it just as easy to flash back to 23.02 if I need to for some reason?
Sorry for all the obsessive questions; I've never flashed a radio before so I don't know what it is that I don't know.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Foo_Blyat said:
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Click to expand...
Click to collapse
It worked for me, except it caused a bootloop because it's not compatible with the CM6 kernel, or at least ezterry's CM6 kernel. I had to flash back to 2.22.23.02.
If you're not using the oem t-mobile/android kernel, don't flash this radio.
I really want to know if this radio is compatible with oem Donut.

My New Desire HD

Finally I purchased a Desire HD on Tmobile without any contract ( I Paid just for the phone) Waoow things did change a lot since all the roms I tried on my beloved HTC Blueangel.
It is locked on T Mobile
SW 1.39.110.1 Is this the latest rom? Although so far It didnt bother me all the bloatware from T Mobile, Is it worth leaving them alone ? I know it is possible to debrand desire and unlock etc. Is it also possible to Debrand Desire HD and unlock and flash with HTC Stock rom? Or shall I just not bother?
And also realised some of the HTC things dont work well HTC HUB unable to download catalog etc. Any reason?
Hi,
I got mine on monday afternoon, coming from a Desire.
By Tuesday morning it was Rooted running Leedroid's Rom, wow what a difference.
Only thing I dont like so far, (yes the screen is not as sharp/colourfull, but you do get used to it, it's just when they are side by side you really notice it), is that the ringtone etc is a little on the quiet side.
Apart from that, what a piece of hardware.
Good luck whatever you do, just enjoy it.
Cheers
Been reading on leedroids thread, Although it is easy to follow the instructions, I just would like to know what is permaroot s-off etc mean?
koalauk said:
And also realised some of the HTC things dont work well HTC HUB unable to download catalog etc. Any reason?
Click to expand...
Click to collapse
I've noticed the same thing, I've heard that HTC are working on the Hub. Congratulations on a great purchase and welcome to the DHD community.
Sent from my Desire HD using Tapatalk
Woohoo
Since I got my new phone I can not stop reading
I completed visionary temp perm root
And S off unlock etc etc. checked at the boot S -off is there so now my existing orange sim works on this tmobile branded DHD all good.
I have done all this in order to actually put a stock rom on to my new phone without any tmobile bloatware on it.
Now the my phone is ready for a ROM
Can I just put HTC stock rom ? If I do will I be able to install a custom rom later on ? Would I loose root or any other features so far?
Many regards
If you're going to all that trouble, why bother with the stock ROM when LeeDRoid has created (and supports) a truely great custom ROM 1.51? Highly recommend it, as he has made it with a custom kernal allowing easy OC or UC with SetCPU & Smartass governor.
You made need to ENG S-off before flashing the recommended radio though. But make sure you do a full backup with ROM Manger and also copy full sdcard to PC first.
Thanks for your answer, I dunno why I kinda want to keep it stock for a little while before I start flashing with Developers excellent roms
UpInTheAir said:
If you're going to all that trouble, why bother with the stock ROM when LeeDRoid has created (and supports) a truely great custom ROM 1.51? Highly recommend it, as he has made it with a custom kernal allowing easy OC or UC with SetCPU & Smartass governor.
You made need to ENG S-off before flashing the recommended radio though. But make sure you do a full backup with ROM Manger and also copy full sdcard to PC first.
Click to expand...
Click to collapse
koalauk said:
Thanks for your answer, I dunno why I kinda want to keep it stock for a little while before I start flashing with Developers excellent roms
Click to expand...
Click to collapse
Good idea. Then you will actually appreciate the advantages of leedroid when you get around to flashing it. Flash it straight away and you won't really know what the difference is.
-----
Someone Swyped my idea.
If I was to flash with stock rom later on can I flash it to Leedroids rom later? As I read stock 1.72 2.2.1 somehow deroots and makes changes so can not flash it to custom roms ? Is that right ?If so what do you think my next step ?
dr.m0x said:
Good idea. Then you will actually appreciate the advantages of leedroid when you get around to flashing it. Flash it straight away and you won't really know what the difference is.
-----
Someone Swyped my idea.
Click to expand...
Click to collapse
koalauk said:
If I was to flash with stock rom later on can I flash it to Leedroids rom later? As I read stock 1.72 2.2.1 somehow deroots and makes changes so can not flash it to custom roms ? Is that right ?If so what do you think my next step ?
Click to expand...
Click to collapse
As far as I know, you have to downgrade to 1.32 first.
http://forum.xda-developers.com/showthread.php?t=905003
Then root again s-off with visionary, you can then upgrade to a custom rom & kernal (over/underclock CPU).
Some ROM are optimized to work with certain raidios (battery / reception performance, so to flash the suggested one, you'll need to Eng s-off as well.
http://forum.xda-developers.com/showthread.php?t=841076
All worked for me
on the first link about downgrade it says!
System requirements:
HTC Sync (or ADB drivers)
Desire HD with build number 1.72 or higher
Not sure how this is related to me as mine is currently on 1.39
UpInTheAir said:
As far as I know, you have to downgrade to 1.32 first.
http://forum.xda-developers.com/showthread.php?t=905003
Then root again s-off with visionary, you can then upgrade to a custom rom & kernal (over/underclock CPU).
Some ROM are optimized to work with certain raidios (battery / reception performance, so to flash the suggested one, you'll need to Eng s-off as well.
http://forum.xda-developers.com/showthread.php?t=841076
All worked for me
Click to expand...
Click to collapse
OK, I got you, the post wasn't that clear. Your now stock 1.39 considering upgrade to 1.72 or other OTA update / ROM?
If you upgrade OTA, it will "unroot" your phone, and then you'll have to follow the steps (or some of) I outlined in my previous post. That is if you wish to have root again.
If you wish to upgrade and have root, best bet would be to just install a custom 1.78 ROM and kernal to match.
Yes, for now I just want to upgrade to stock HTC 1.72 and perhaps later flash a custom Rom as I am not very clues up on Android devices ( coming from wm environment) as my previous post what should be my next step ( clean HTC stock Rom ) ?
Sent from my Desire HD using XDA App
How do I check my CID ? I cant seem to see it in the bootloader screen ? and anyone know what simlock image crc etc do?
I'd recommend getting permanent root (visionary), eng s-off AND radio s-off, install rom manager from market and flash clockwork mod recovery from it, and then there is a guide on here to upgrade to 1.72 without losing root, by flashing it through clockwork mod.
Still, the easier option is to install a custom rom since those will obviously not try to unroot your phone.
Sent from my leedroid Desire HD
koalauk said:
How do I check my CID ? I cant seem to see it in the bootloader screen ? and anyone know what simlock image crc etc do?
Click to expand...
Click to collapse
From Fastboot menu -> Bootloader -> System Info
If Super CID, should have CID-11111111, meaning carrier ID unlocked, enabling flashing of ROM other than carrier specific (I think).
Image CRC - not too sure, possibly checksum of certain working harware, radio etc?????????? Anyone?
For the dutch who want to root there 1.72 DHD....
hypervortex . com/?p=50
For non-dutch...google translate
It's a really great written artikle on how to downgrade and root your DHD
Thanks,
Now rooted, s-off and eng s-off and debranded
UpInTheAir said:
From Fastboot menu -> Bootloader -> System Info
If Super CID, should have CID-11111111, meaning carrier ID unlocked, enabling flashing of ROM other than carrier specific (I think).
Image CRC - not too sure, possibly checksum of certain working harware, radio etc?????????? Anyone?
Click to expand...
Click to collapse

[Q] unrEVOked 3 root

Does anyone know when unrEVOked will be able to find a root for the Wildfire on 2.2.1? I hope they find it soon. From how much they've been delaying it seems like they just don't want to even try. Should I disable the Search online for updates feature so my phone stops updating?
* They will release it when they want to. We have no option or control over them. If they want to try, it is their wish, if they don't want to try, again it is their wish. Live with it.
* If you are already on 2.2.1, there's no point disabling search for updates because it is extremely unlikely there will be any.
*Sigh*, why cant you read already existing threads before creating another one? Is it too hard?
omfg! seems like you have disabled search function for this forum, this topic gets posted at least once a day
jayvaidya96 said:
Does anyone know when unrEVOked will be able to find a root for the Wildfire on 2.2.1? I hope they find it soon. From how much they've been delaying it seems like they just don't want to even try. Should I disable the Search online for updates feature so my phone stops updating?
Click to expand...
Click to collapse
just re rooted my wildfire on froyo
chubby65 said:
just re rooted my wildfire on froyo
Click to expand...
Click to collapse
How did you do this ?
I was told that if we make a new thread everyday about it they will update it!!
bigbossa said:
How did you do this ?
Click to expand...
Click to collapse
when i got the phone it was on 2.1 but did'nt want to wait for froyo so rooted using unrevoked and installed the wildpuzzle rom 2.2.1 then tried the stock rom thought i screwed up when i read the forums and discovered root was not availiable for froyo first i checked hboot version on my phone discovered that it was 0.80.0003 then i installed the wildpuzzle rom back onto the sd card rebooted phone in recovery mode and installed rom from sd card rebooted and waited for it to restart now have root back on wildfire not sure if it will work on the new hboot tho
chubby65 said:
when i got the phone it was on 2.1 but did'nt want to wait for froyo so rooted using unrevoked and installed the wildpuzzle rom 2.2.1 then tried the stock rom thought i screwed up when i read the forums and discovered root was not availiable for froyo first i checked hboot version on my phone discovered that it was 0.80.0003 then i installed the wildpuzzle rom back onto the sd card rebooted phone in recovery mode and installed rom from sd card rebooted and waited for it to restart now have root back on wildfire not sure if it will work on the new hboot tho
Click to expand...
Click to collapse
WildPuzzle 2.2.1 (Or rather, ANY custom ROM), removes the updated HBOOT. So, obviously, 2.2.1 will be rootable in such cases.
3xeno said:
WildPuzzle 2.2.1 (Or rather, ANY custom ROM), removes the updated HBOOT. So, obviously, 2.2.1 will be rootable in such cases.
Click to expand...
Click to collapse
so using a custom rom over the top of a stock 2.2.1 as i did makes the wildfire rootable again?
chubby65 said:
so using a custom rom over the top of a stock 2.2.1 as i did makes the wildfire rootable again?
Click to expand...
Click to collapse
No. You will not be able to use a Custom ROM over Stock 2.2.1 because installing a Custom ROM requires root.
3xeno said:
No. You will not be able to use a Custom ROM over Stock 2.2.1 because installing a Custom ROM requires root.
Click to expand...
Click to collapse
dont know how i managed it but thats what i've done
If I understood what you said, then I dont think you have installed the official 2.2.1 update. I cant see that anywhere in your post. (Saying you applied the official 2.2.1 update).
When you went back to the Stock ROM, it was still at 2.1, which is why the HBOOT was still at 0.80. To install the official update, from the Stock ROM, you would have to accept the OTA Update, and then install it, which I don't think you did.
3xeno said:
If I understood what you said, then I dont think you have installed the official 2.2.1 update. I cant see that anywhere in your post. (Saying you applied the official 2.2.1 update).
When you went back to the Stock ROM, it was still at 2.1, which is why the HBOOT was still at 0.80. To install the official update, from the Stock ROM, you would have to accept the OTA Update, and then install it, which I don't think you did.
Click to expand...
Click to collapse
when i went back to the stock rom it was deffo 2.2.1 i put the wildpuzzle rom straight over the top of it
Not possible. There is some error in communication somewhere, but, if it were possible to directly put Custom ROMs over the official 2.2.1, we wouldnt have had threads like this everyday.
unless after you rooted and flashed, you then installed a ruu then updated you did not have 2.2. when you went back did you restore a nandroid backup?
you are able to install ota update on rooted phone
ephbee said:
unless after you rooted and flashed, you then installed a ruu then updated you did not have 2.2. when you went back did you restore a nandroid backup?
you are able to install ota update on rooted phone
Click to expand...
Click to collapse
no back up all i know is that after i updated i had no root on the wildfire and on 2.2 now after putting wildpuzzle rom over the top of it i now haved a rooted wildfire again
chubby65 said:
no back up all i know is that after i updated i had no root on the wildfire and on 2.2 now after putting wildpuzzle rom over the top of it i now haved a rooted wildfire again
Click to expand...
Click to collapse
Share the rom, maybe it is signed xD
Bewz said:
Share the rom, maybe it is signed xD
Click to expand...
Click to collapse
tell me how to share and i will
Bewz said:
Share the rom, maybe it is signed xD
Click to expand...
Click to collapse
this is the rom i used to get the 2.2 upgrade http://www.megaupload.com/?d=LF2TWEHJ
But isn't it possible to modify oryginal rom from HTC to downgrade HBOOT , and then make Wildfire rootable? Or make some crash in HBOOT witch will allow to root? That's a lot of ways, is it possible that HTC make Wildfire really unrootable on 2,2,1? That they make unlockable bootloader? Like a motorola?

[Q] Can't unroot, "Main version is older"

I'm trying to unroot my phone so I can send it back in for a replacement but whenever I try to flash the PD15IMG in the bootloader it says the "Main version is older" and the update fails. I used the PD15IMG from the unlockr, but I guess I guess I need an updated one? Anyone know how I can fix this?
EDIT:
I ended up figuring everything out. Here's the thread I made that explains everything.
http://forum.xda-developers.com/showthread.php?t=1356607
Tmobile doesnt look to see If your phone is rooted or Not. There only interested in the physical aspect of the device.
Sent from my Senseless Doubleshot using xda premium
jberg22 said:
I'm trying to unroot my phone so I can send it back in for a replacement but whenever I try to flash the PD15IMG in the bootloader it says the "Main version is older" and the update fails. I used the PD15IMG from the unlockr, but I guess I guess I need an updated one? Anyone know how I can fix this?
Click to expand...
Click to collapse
you should have reverted back to the stock radio before flashing the stock PD15IMG...you could try flashing the newest updated RUU and then downgrade back to 2.2
aznprodgy said:
you should have reverted back to the stock radio before flashing the stock PD15IMG...you could try flashing the newest updated RUU and then downgrade back to 2.2
Click to expand...
Click to collapse
alright so i tried flashing the stock radio, but now the bootloader says i have s-on? does this mean i'm not rooted anymore, even though i'm running a custom rom?
jberg22 said:
alright so i tried flashing the stock radio, but now the bootloader says i have s-on? does this mean i'm not rooted anymore, even though i'm running a custom rom?
Click to expand...
Click to collapse
I ran into the same problem as youre having when I tried to revert back to stock. flashed the stock PD15IMG in hboot, but was on an updated radio. you still have root access even tho it says s=on, but you can ONLY use the rom you were currently using when trying to go back to stock. (ex- if you were on Virtuous Unity v2.39 then you could only flash and use that rom) theres a thread that goes more into detail, heres the link http://forum.xda-developers.com/showthread.php?t=1092170 make sure you read the entire thread carefully
from what I understand, youll have to flash an updated RUU to fix the issue
aznprodgy said:
I ran into the same problem as youre having when I tried to revert back to stock. flashed the stock PD15IMG in hboot, but was on an updated radio. you still have root access even tho it says s=on, but you can ONLY use the rom you were currently using when trying to go back to stock. (ex- if you were on Virtuous Unity v2.39 then you could only flash and use that rom) theres a thread that goes more into detail, heres the link http://forum.xda-developers.com/showthread.php?t=1092170 make sure you read the entire thread carefully
from what I understand, youll have to flash an updated RUU to fix the issue
Click to expand...
Click to collapse
Thanks for the link man, I should've searched before I posted. I read through the whole thing, and I'm still not sure what to do.. just a thought, but would this basically be like trying to root from the official 2.3.4 OTA?
And if there's an RUU for the GB OTA would that work in HBOOT, since it has the updated radio?
same thing happened to me, i have a glacier. (mytouch 4g) would appreciate any help. I was actually trying to restore to stock, unroot, and now i am s-on rooted
I got my problem resolved. If anyone has the same problem I made a thread about how to fix it.
http://forum.xda-developers.com/showthread.php?t=1356607
Sent from my HTC Glacier using XDA App
jberg22 said:
I got my problem resolved. If anyone has the same problem and wants to know how I fixed it feel free to PM me and I'll help out.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
heh sorry bro, been busy the past couple days. glad you got your phone fixed tho
aznprodgy said:
heh sorry bro, been busy the past couple days. glad you got your phone fixed tho
Click to expand...
Click to collapse
Its all good haha I appreciate the help though. I had to figure out how to use adb to fix it, so at least I learned something new in the process.
Sent from my HTC Glacier using XDA App

Categories

Resources