• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root I messed up my GF's Desire and now she has banned sex.. HELP!

krisdf

Lurker
Yep as the topic states, im in trouble, and i think i may need your help! Ive been lurking arround here for the past year, reading guides and looking at UI's for inspiration, but now i need some assistance getting a desire working again.

Thing is, Back in march i rooted the phone, installing revolutionary and tried off different roms. The lady however did not fancy any of them and wanted to go back to stock. So i flashed the phone with the GB RUU. this went great, and she used the phone for about a month, then got a One S.
Now she wants to sell the Desire, but it needs to go in for repair as the power button is buggy. But in my haste running the RUU i did not lock the fastboot thingie / had it restored to stock. so now when i enter the fastboot menu there is a pink text saying "revolutionary" at the very top. So how do i remove this, so it can be repaired?

The phone is
PVT4 SHIP- S-OFF
Hboot- 6.93.1002
Microp-051d
Touchpanel-synt0101
Radio-5.17.05.23


I can enter the Revolutionary recovery, but what do i need to flash to get it to stock bootloader with S-on?
 
Hi Krisdf, and welcome to AF :)

Well I think that's the first time I've seen the problem expressed that way in this forum ;) Luckily there is a straightforward solution.

You need to go to alpharev.nl and download the "downgrader" hboot from there. Install that as they describe on that site (our own adb and fastboot faq will tell you how to set up fastboot on your computer - see the All Things Root Guide sticky for a link to this). The downgrader hboot can be overwritten by a RUU (that's its sole purpose), so once you have installed this, run the RUU again and the phone will be competely stock.

As you know, the RUU will wipe the phone, so backup essential stuff first. Most people would prefer to wipe the phone before sending it in for repair, so I assume this isn't a problem (they usually come back from repairs wiped anyway).
 
Hi Krisdf, and welcome to AF :)

Well I think that's the first time I've seen the problem expressed that way in this forum ;) Luckily there is a straightforward solution.

You need to go to alpharev.nl and download the "downgrader" hboot from there. Install that as they describe on that site (our own adb and fastboot faq will tell you how to set up fastboot on your computer - see the All Things Root Guide sticky for a link to this). The downgrader hboot can be overwritten by a RUU (that's its sole purpose), so once you have installed this, run the RUU again and the phone will be competely stock.

As you know, the RUU will wipe the phone, so backup essential stuff first. Most people would prefer to wipe the phone before sending it in for repair, so I assume this isn't a problem (they usually come back from repairs wiped anyway).

Great I think I got it now! The main issue was that i did not know how to make the bootloader "writable" I then flashed the GB RUU as it was on that revision earlier. I treid flashing Froyo but then i was prompted with the "Error 140: to new FW bla bla bla. from the RUU flasher. But I think I got it working now... the values in fastboot is:

PVT4 SHIP- S-ON
Hboot- 1.02.0001
Microp-051d
Touchpanel-synt0101
Radio-5.17.05.23

The time and date however is messed up, but im not sure where fastboot gets it's values for time and date, so i guess that could be when the RUU was signed?

BTW: Do any of you know if warenty still active when flashing GB RUU? or should i go for Freyo?

And if so i recon i should: reroot -> dump a custom rom (equal or lower than Freyo) -> and then do the steps I just did again?
 
Looks right to me.

The warranty should still be fine with the official HTC 2.3 update.

Great well i decided to do the method with the custom rom and then running Freyo RUU, so now the fastboot is locked again and it's back as out of box!

its on 0.93.0001 but i asume thats right for Freyo?
 
Just a quick update.

The phone is fixed now and i'm a lucky guy again ;)

thanks to everyone who helped me fix it:)

Thread closed!
 
Back
Top Bottom