SOLUTION: S-ON HTC Wildfire S Downgrade Error "Main Version is Older. Update fail."

62 posts
Thanks Meter: 22
 
By mphi, Member on 10th July 2011, 11:13 PM
Post Reply Email Thread
Like a few people I have been trying to debrand my S-ON Wildfire S by flashing an official HTC ROM. Since my phone shipped with a later version number (1.34.110.3), the bootloader would refuse to flash the latest Official HTC ROM (1.33.401.2) even with a gold card!

Luckily I've now managed to bypass this error by hex editing and reflashing the misc partition. The following method should allow you to downgrade to any signed HTC ROM no matter what version you currently have installed, even if your phone is S-ON.

Warning: You could probably brick your phone if you flash an invalid misc partition. So follow these steps carefully (or not at all)! Also, if you flash a very recent ROM, you may not be able to use these steps to downgrade again!
  1. Ensure you have the HTC Sync USB drivers installed then download the zip at mediafire.com/?wxf6y4yq6d6nc8d containing the tools you need, and an official HTC ROM executable. I used the ROM at filefactory.com/file/cbd7165.
  2. Connect your phone via USB and select the HTC sync option when prompted. Also ensure that USB debugging is enabled (this is the default).
  3. Extract the zip and open a windows command prompt and browse to the directory where you extracted the files.
  4. Execute the following commands in the command prompt:
    Code:
    adb push flash_image /sdcard/flash_image
    adb push GingerBreak /data/local/tmp/GingerBreak
    adb shell chmod 777 /data/local/tmp/GingerBreak
  5. Now enter the interactive shell mode with the following command:
    Code:
    adb shell
  6. Gain temporary root access by executing the following command within the interactive shell:
    Code:
    ./data/local/tmp/GingerBreak
    Ensure that it has worked successfully (the shell prompt should change from $ to #).
  7. As root now execute the following commands:
    Code:
    cat /dev/mtd/mtd0 > /sdcard/misc.img
    cat /sdcard/flash_image > /data/flash_image
    chmod 777 /data/flash_image
  8. Now exit from root permissions. The shell prompt should change back to a $.
    Code:
    exit
  9. Clean up a few files and exit from adb.
    Code:
    rm /data/local/tmp/sh
    rm /data/local/tmp/boomsh
    exit
  10. Copy the image file from your SD card using the command:
    Code:
    adb pull /sdcard/misc.img misc.img
  11. Run HxD.exe, select "OK" at the prompt then File -> Open and locate misc.img (which is in the current directory). On the 11th line you should see the version number of your current ROM, change this to a lower number. I set my version number to 1.30.401.0 since this was the version number of the previous official HTC ROM. The changes made will be highlighted in red. File -> Save As and name it misc2.img.
  12. Copy misc2.img to your SD card using the following command:
    Code:
    adb push misc2.img /sdcard/misc2.img
  13. Reboot your phone so that you can use GingerBreak again to attain temporary root privileges. (This may not be strictly necessary, but I think it's worthwhile just in case.)
  14. Once it's back and you've connected via USB using the HTC Sync option again, issue the following commands in your command prompt:
    Code:
    adb shell
    ./data/local/tmp/GingerBreak
    /data/flash_image misc /sdcard/misc2.img
  15. Now run the official ROM installer executable as normal. Note that the installer may state your current version number but this is ignored and you should be able to downgrade successfully!

Let me know if you have any problems.

Confirmed Working on:
  • TMobile UK 1.34.110.3 + HBOOT 0.90.0.0
  • TMobile Polska 1.30.401.2 + HBOOT 0.90.0.0
The Following 13 Users Say Thank You to mphi For This Useful Post: [ View ] Gift mphi Ad-Free
11th July 2011, 12:51 AM |#2  
Senior Member
Flag Beveren-Waas
Thanks Meter: 94
 
Donate to Me
More
You also have/had the 1.03.0000 hboot?

I get:

./data/local/tmp/GingerBreak

[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi

[**] donate to [email protected] if you like
[**] Exploit may take a while!

[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0

And it stays there...
The Following User Says Thank You to sammyke007 For This Useful Post: [ View ] Gift sammyke007 Ad-Free
11th July 2011, 01:46 AM |#3  
OP Member
Thanks Meter: 22
 
More
The hboot version I have is 0.90.0000, but I don't see why this wouldn't work for any version.

How long are you waiting for it to complete? Like it says, it can sometimes take a while for the exploit to take effect. Sometimes it took up to a minute for me.

Every time you use GingerBreak you should make sure that you remove sh, boomsh and crashlog if they exist, reboot your phone then push and chmod GingerBreak again.

Code:
adb shell
rm /data/local/tmp/sh
rm /data/local/tmp/boomsh
rm /data/local/tmp/crashlog
exit

** restart phone **

adb push GingerBreak /data/local/tmp/GingerBreak
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
11th July 2011, 09:00 PM |#4  
Junior Member
Thanks Meter: 3
 
More
11 row
In my misc.img 11th row look like this:




should I change 9.0.0.0 to 1.30.401.0 ?? My current rom is TMobile PL 1.30.401.2.
11th July 2011, 09:23 PM |#5  
OP Member
Thanks Meter: 22
 
More
Quote:
Originally Posted by m3ritum

should I change 9.0.0.0 to 1.30.401.0 ?? My current rom is TMobile PL 1.30.401.2.

It seems unusual that your ROM has a 9.0.0.0 version number

But, yes, as long as 1.30.401.0 is lower than the version number of the RUU you are intending to flash, it should be fine. If it doesn't work you can use flash_image to reflash misc.img to get back the old version number.
11th July 2011, 11:54 PM |#6  
Senior Member
Flag Beveren-Waas
Thanks Meter: 94
 
Donate to Me
More
I tried it again after remove commands and rebooting but no luck... Waited +5mins and nothing happened.

I guess the new HBOOT is the problem.
12th July 2011, 12:13 AM |#7  
OP Member
Thanks Meter: 22
 
More
Quote:
Originally Posted by sammyke007

I tried it again after remove commands and rebooting but no luck... Waited +5mins and nothing happened.

I guess the new HBOOT is the problem.

Maybe the GingerBreak exploit is patched on your ROM...
12th July 2011, 09:55 AM |#8  
Junior Member
Thanks Meter: 3
 
More
Beer for U mphi it works great !!!
12th July 2011, 10:46 PM |#9  
OP Member
Thanks Meter: 22
 
More
If this has worked for you, please can you post your previous ROM version number and your HBOOT version? I'll keep a list of working version numbers updated in the first post. Thanks!
13th July 2011, 06:34 AM |#10  
Junior Member
Thanks Meter: 3
 
More
Sure, ROM was branded TMobile Polska 1.30.401.2 and Hboot is 0.90.0.0.
Now I have unbranded 1.30.401.2.
13th July 2011, 07:32 PM |#11  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by m3ritum

Sure, ROM was branded TMobile Polska 1.30.401.2 and Hboot is 0.90.0.0.
Now I have unbranded 1.30.401.2.

Hey there, I flashed my phone with

RUU_Marvel_Sasktel_Canada_WWE_1.58.669.2_Radio_47. 10c.35.3030_7.47.36.19M_release_199460_signed

hoping it would be unlocked, but now it means I cannot use your method which I previously used. I think I'm stuck on this until a new ROM comes out.. D:

Just giving people a heads up so they don't hit a wall like I did, and hope you can create a work around THANKS!!


//Edit

The only way to fix this is to get S-OFF right? *Looks like I'm forking out the cash lol*
Post Reply Subscribe to Thread

Tags
debranding, error 140

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes