View Single Post
  #15 (permalink)  
Old 12-17-2009, 03:26 AM
flipzmode's Avatar
flipzmode
VIP Member
Offline
 
Join Date: Jan 2009
Posts: 390
Reputation: 2820
flipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIPflipzmode is a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Unrooting Htc Hero

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:
Quote:
Error[140]: Bootloader Version Error
When running RUU manually via fastboot/hboot a more detailed error is shown:
Quote:
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
Quote:
remote: not allowed
When I created a custom.zip and tried to bypass verification I got
Quote:
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?
__________________
Fresh Evo: 4.2 (Android 2.3.3) || 3.5.0.1 (Android 2.2)
Fresh Hero: 2.4.0 (Android 2.1) || Fresh Kitchen
CDMA Hero Development & Fresh ROM home: http://GeekFor.Me || Twitter

Last edited by flipzmode; 12-20-2009 at 01:11 PM.
Reply With Quote
This post has been thanked 1 times.