Unrooting Htc Hero

[THunDA]

I couldnt get the ruu to work either, a few weeks ago I tried it because I was bored and wanted to try a clean start but couldnt get it to work. So I gave up because my phone is running so FRESH why bother..

[datboy1212]

Yea I agree too, there is no need to have the stock rom when you're running fresh, but I could not restore my nandroid backup that I had saved before, so I wanted to root again and have a backup that works just in case.

[THunDA]

I even tried restoring a nandroid backup that I made when I was stock and rooted only before trying to flash the ruu because Ive read that might make it work... but it still didnt work.

[HeroFF1]

Originally Posted by flipzmode

Nandroid stores the backups on the sd card on your phone. There's no need to be connected to your computer.

See thats what I thought but I cant find it...**** it, I'm waaaaaaay too dumb for all this. Peace out homies

[flipzmode]

So I've been working with datboy all night. I took him as far as manually performing the RUU one line at a time. Between him and other people having this issue I've tried countless things.

His initial error from the RUU is:

Error[140]: Bootloader Version Error

When running RUU manually via fastboot/hboot a more detailed error is shown:

sending 'zip' (104671 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)

We then tried it manually from straight fastboot but we were getting

remote: not allowed

When I created a custom.zip and tried to bypass verification I got

RUU_Hero_C_Sprint_1.29.651.1_signed_release\rom\us erdata.zip
--------------------------------------------
Bootloader Version...: 1.41.0000
Baseband Version.....: 1.04.01.09.21
Serial Number........: x
--------------------------------------------
sending 'boot' (1772 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)

The strange thing is that fastboot is supposed to completely bypass signature checking. That's kind of the whole point of it. So I did some more digging. I couldn't find any help at all on what the actual error code numbers mean. However I did find a lengthy discussion in a Sapphire forum (I think) that was talking about flashing a NEW spl and an OLD hboot to bypass signature verification. So as it turns out the (current) fastboot from HTC on our phones doesn't allow signature bypassing. And because our phone is the one and only, we don't really have anything else to work off of.

I mimicked an RUU but made it in to an update.zip.

What this will do:
- Reset all of /data and restore to factory .img
- Reset all of /system and restore to factory .img
- Reset boot.img and restore to factory .img
- aka: this is just like the RUU. You will be back to factory settings including unrooted

What this might do:
- Whatever is preventing the real RUU from working might be fixed by this. I need someone who is suffering from the RUU problems described above to try flashing this rom, and then flash the RUU and let me know your results. But in either case... this zip will do what you are looking for.

Download: Download link pulled because my update-script doesn't write the proper permissions to /data, leaving you locked out of it. I have to fix it. This is a temporary link. Once I see if it's working for people or not I'll put it up on geekfor.me and such. Please report back on
A. If it accomplished what you wanted
B. Can you now run RUU without errors? (more important to me)
C. Do you have a "with google" phone?

[datboy1212]

I did the restore with the .zip file to stock and it appears to be a success. However the RUU still gives me the error when running it.

[flipzmode]

Originally Posted by datboy1212

I did the restore with the .zip file to stock and it appears to be a success. However the RUU still gives me the error when running it.

Blah. So we have restored your recovery.img, boot.img, userdata.img, and your system.img to stock.

Any chance that you have another computer you could try running the RUU on? Don't forget you'll need to reinstall all the drivers. Or maybe try deleting your phone from device manager and letting it reinstall itself? I'm out of ideas on what it could be on the phone. You are totally stock at this point.

[thacounty]

Originally Posted by flipzmode

Blah. So we have restored your recovery.img, boot.img, userdata.img, and your system.img to stock.

Any chance that you have another computer you could try running the RUU on? Don't forget you'll need to reinstall all the drivers. Or maybe try deleting your phone from device manager and letting it reinstall itself? I'm out of ideas on what it could be on the phone. You are totally stock at this point.

Going to thank again, this is exactly what I was looking for! Who needs an RUU when you can do it from SD?!

[Tuffgong4]

I'm a little on the concerned side and I'm guessing you guys can ease my mind. I've installed flashrec and successfully installed the 1.5.2 recovery img...will this cause me any problems flashing to any updates that sprint releases of if I have an issue with my phone will they call me out on it like unlocking my touch pro...(having to relock it if I send it in)

[thacounty]

Originally Posted by Tuffgong4

I'm a little on the concerned side and I'm guessing you guys can ease my mind. I've installed flashrec and successfully installed the 1.5.2 recovery img...will this cause me any problems flashing to any updates that sprint releases of if I have an issue with my phone will they call me out on it like unlocking my touch pro...(having to relock it if I send it in)

Take that update that is stock.zip from 3 posts above and flash that when you have to send in. It will be stock again.

Oh, and if sprint releases an update you will have to wait for a rom to incorporate it because it won't update unless its stock.