Develop Bugs

Downgrading from 2.3 Gingerbread to 1.32 to S-OFF, root, update to 2.3 RUU question

Hi can someone explain to me in nice and easy terms how to downgrade from this user guide please as I have seen a few people asking so it would help them too.
http://forum.xda-developers.com/showthread.php?t=905003
Section 2b [For Gingerbread ROMs, 2.x]
Connect Desire HD to a computer. Charge only, USB Debugging enabled!
Open up a cmd and go to Downgrade folder, execute commands:
Right this is where I get stuck what exactly do you put in the command line in cmd? is the Downgrade folder the PD98IMG.zip file you put on your SD card or what do you actually type?
The PD98IMG.zip file is on my K: drive on the SD card if that's relevant in anyway.
and then after obviously I could then follow on with the next steps of the rest being the following
execute commands:
Code:
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
Section 3
If you got "#" in the result, you have temporary root! Proceed with commands:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.6
Close the CMD. Reboot while holding volume down, it will go to the bootloader
Follow the instructions (start the update)

Hi,
Where did you put the downgrade folder? The attachment from the first post?
If you placed it directly on your C: Drive, the example would be, from within a cmd window -
Code:
cd C:\Downgrade
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak

Hi Andy,
From Section 1 I put the PD98IMG on my desktop and then copied it onto my SD card which is on my K: drive where my DHD is attached via USB cable.
Do I need to put the PD98IMG on my desktop in a folder called 'Downgrade' or something?

No, look at the first post again. Download the Downgrade_v2.zip file right at the bottom of the post. Extract the contents to your C:\
For the sake of ease make sure its
C:\Downgrade\<files should be in here>

andyharney said:
Hi,
Where did you put the downgrade folder? The attachment from the first post?
If you placed it directly on your C: Drive, the example would be, from within a cmd window -
Code:
cd C:\Downgrade
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
Click to expand...
Click to collapse
one thing @andy.... maybe i´m talking about the same thing like you.... sometimes the languaje bothers me
maybe he can´t execute adb commands from c:/ if he don´t fixed it for the adb parameters works from all directories(supposing he use Windows)...
maybe he should to write it from this directory:
Code:
c:/cd sdk
c:/sdk/cd platform-tools
c:/sdk/platform-tools
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
[
maybe i´m mistaken... i don´t have any idea about windoze lol

I'm assuming ToneyEricsson hasn't added adb to his Windows environment. I think it would be simplest to put the directory on his C:\
I know what you mean, I float between XP, archlinux, and Ubuntu. Remembering what in where can get confusing.
EDIT: /Off Topic does clicking this link make you feel better?

@toney... you have installed into your computer htc sync (for obtain drivers for "android usb debug "adb) and installed the "SDK of ANDROID into your sistem?
if not take it:
http://developer.android.com/sdk/index.html

andyharney said:
I'm assuming ToneyEricsson hasn't added adb to his Windows environment. I think it would be simplest to put the directory on his C:\
I know what you mean, I float between XP, archlinux, and Ubuntu. Remembering what in where can get confusing.
Click to expand...
Click to collapse
aaaaahhh ok ok i supossed it and
in adition...ouch! i wrote my post of avobe before read your last post, sorry..
i said the same think like you... sorry @andy

I'm using Windows 7 64bit Ultimate - I have only HTC Sync installed.
I have put the Downgrade onto C: drive and get this when running the Section 2b [For Gingerbread ROMs, 2.x] command
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
1546 KB/s (15837 bytes in 0.010s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
2054 KB/s (16830 bytes in 0.008s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./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 system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0[*] vold: 5483 GOT start: 0x00014360 GOT end: 0x000143a0[*] vold: 5483 idx: -3072 fault addr: 0x000132b4
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?

Backup files from your SDcard to your computer and format your SDcard. Its failing to see it. Or put it in, if you removed it.

andyharney said:
Backup files from your SDcard to your computer and format your SDcard. Its failing to see it. Or put it in, if you removed it.
Click to expand...
Click to collapse
The 32GB SD card is in my DHD. I have a few SD cards here I'll format a smaller one put the PD98IMG on it and try again.
So you have seen this before?

Ok, any SDcard will do. Yes I've seen this before.

Toney, when you have your HD connected to the PC at that stage, also make sure it is in Charge mode only, not disk mode.

Done formatting an 8GB SD card and put PD98IMG on the SD card and now back in Charge only mode with USB debugging enabled.
I have now both HTC Sync and Android SDK on my pc I will try the commands again as before.

nednapalm said:
Toney, when you have your HD connected to the PC at that stage, also make sure it is in Charge mode only, not disk mode.
Click to expand...
Click to collapse
Completely forgot about that. That could be the cause.

andyharney said:
Completely forgot about that. That could be the cause.
Click to expand...
Click to collapse
caught me out once too!

Well I got HTC Sync and Android SDK installed, Charge only, USB debugging enabled and just ran the same command line as earlier and get the exact same
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1718 KB/s (15837 bytes in 0.009s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
1494 KB/s (16830 bytes in 0.011s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./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 system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1226 GOT start: 0x00014360 GOT end: 0x000143a0
[*] vold: 1226 idx: -3072 fault addr: 0x000132b4
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?

ToneyEricsson said:
Well I got HTC Sync and Android SDK installed, Charge only, USB debugging enabled and just ran the same command line as earlier and get the exact same
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1718 KB/s (15837 bytes in 0.009s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
1494 KB/s (16830 bytes in 0.011s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./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 system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1226 GOT start: 0x00014360 GOT end: 0x000143a0
[*] vold: 1226 idx: -3072 fault addr: 0x000132b4
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
Click to expand...
Click to collapse
you need to enter the commands like the post 5 of this thread....
ensure you that you are leaved in platform-tools folder of the sdk the downgradev2 folder

Toney, I would also try downloading the RUU for 2.36 from XDA and flashing that to get a clean start (don't set up any accounts just skip the setup till you get to the launcher and start the process again).

nednapalm said:
Toney, I would also try downloading the RUU for 2.36 from XDA and flashing that to get a clean start (don't set up any accounts just skip the setup till you get to the launcher and start the process again).
Click to expand...
Click to collapse
I have the 2.3 RUU already downloaded but I need to downgrade to 1.32, get rooted with Visionary and and S-OFF with the tool and then after that update with 2.3 RUU.
Edit: All done, S-OFF and rooted in 2.3 with Gingerbreak.
P.S Sergie is the man! a big thanks!

[Q] Downgrade DHD

Hi guys Sorry to touble you with this n00b post, but i've searched everywhere and cannot find an answer.
I have a DHD with android 2.3.3 and sense 2.1. In order to install a custom rom I have to downgrade the phone.
I follow this guide: http://forum.xda-developers.com/showthread.php?t=905003
Of course, i use the Section 2b. As you can tell by the screenshot i've downloaded the misc_version and gingerbreak to my platform tools folder.
why cant i push? I've searched in astro. When i go into data, I cant find a folder named "local". Dont know if it should be there or if it is created when you type in cmd.
USB debugging is on, charge only. I've installed SDK according to this guide on cynogen wiki: http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK
I followed the install guide exactly, but could not finish step 24. I dont have and exclamation mark over an unknown adb device. All i can relate to this in device manager is "my htc". I've installed HTCsync/usb drivers.
Can someone please help me?
/matekr

Not too sure, but a common problem is not having the HTC drivers? Have you installed HTC sync before to get all the correct drivers?

Tamen said:
Not too sure, but a common problem is not having the HTC drivers? Have you installed HTC sync before to get all the correct drivers?
Click to expand...
Click to collapse
Yes I have As you can see in the screenshot ADB finds my phone, but cant push files.

matekr said:
Yes I have As you can see in the screenshot ADB finds my phone, but cant push files.
Click to expand...
Click to collapse
If your version is 2.37 there is no way you can downgrade your DHD. We can just hope for the devs to find a way to downgrade that version.

you have to be in the correct directory to be able to push the file. The command would go as follows:
cd c:\android-sdk-windows\platform-tools
then run the adb push command.
This is assuming that your sdk folder is in the root of C: If not just amend the command accordingly.
I would personally rename the sdk folder to just 'android' then move it to C: in which case the command would then be:
cd c:\android\platform-tools
Hope this helps you bud.

Agreed that was my mistake i wasn't in the correct folder and it drove me crazy for ages till i realised my stupid mistake!

jonpenn101 said:
Agreed that was my mistake i wasn't in the correct folder and it drove me crazy for ages till i realised my stupid mistake!
Click to expand...
Click to collapse
What a stupid mistake! Thanks for the help!

Sorry dude didn't check the screenshot -yeah I had that problem too, put the files in the folder you start adb in

I am trying to root my DHD (it's currently on the latest Gingerbread OTA update)
Can you confirm that you have rooted your DHD using this method? And what version was your DHD at when you attempted this?
Currently this is where I'm stuck at
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Duy>cd Desktop
C:\Users\Duy\Desktop>cd Downgrade 2
C:\Users\Duy\Desktop\Downgrade 2>adb push misc_version /data/local/tmp
1405 KB/s (15837 bytes in 0.011s)
C:\Users\Duy\Desktop\Downgrade 2>adb push GingerBreak /data/local/tmp
1643 KB/s (16830 bytes in 0.010s)
C:\Users\Duy\Desktop\Downgrade 2>adb shell chmod 777 /data/local/tmp/misc_versio
n
C:\Users\Duy\Desktop\Downgrade 2>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Users\Duy\Desktop\Downgrade 2>adb shell
$ ./data/local/tmp/GingerBreak
./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 system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1226 GOT start: 0x00014360 GOT end: 0x000143a0
I assume that rooting was unsuccessful then? Can anyone give me some tips? (I am quite new at this if you can't already tell, just got this phone not too long ago)
Thanks

duynguyenle said:
I am trying to root my DHD (it's currently on the latest Gingerbread OTA update)
Click to expand...
Click to collapse
Check your software number.
If it's on 2.37 or 2.42, the latest Gingerbread OTA update, it is NOT downgradeable as of this moment.

Zulmacher said:
Check your software number.
If it's on 2.37 or 2.42, the latest Gingerbread OTA update, it is NOT downgradeable as of this moment.
Click to expand...
Click to collapse
That's what I thought, oh well guess I'll wait till someone root it then. Thanks

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

SOLUTION: S-ON HTC Wildfire S Downgrade Error "Main Version is Older. Update fail."
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!
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.
Connect your phone via USB and select the HTC sync option when prompted. Also ensure that USB debugging is enabled (this is the default).
Extract the zip and open a windows command prompt and browse to the directory where you extracted the files.
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
Now enter the interactive shell mode with the following command:
Code:
adb shell
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 #).
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
Now exit from root permissions. The shell prompt should change back to a $.
Code:
exit
Clean up a few files and exit from adb.
Code:
rm /data/local/tmp/sh
rm /data/local/tmp/boomsh
exit
Copy the image file from your SD card using the command:
Code:
adb pull /sdcard/misc.img misc.img
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.
Copy misc2.img to your SD card using the following command:
Code:
adb push misc2.img /sdcard/misc2.img
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.)
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
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

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 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

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.

m3ritum said:
should I change 9.0.0.0 to 1.30.401.0 ?? My current rom is TMobile PL 1.30.401.2.
Click to expand...
Click to collapse
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.

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.

sammyke007 said:
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.
Click to expand...
Click to collapse
Maybe the GingerBreak exploit is patched on your ROM...

Beer for U mphi it works great !!!

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!

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.

m3ritum said:
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.
Click to expand...
Click to collapse
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*

snowie72 said:
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*
Click to expand...
Click to collapse
Ahh, the GingerBread exploit must have been patched in that ROM then. It's a double-edged sword really; if you were running a ROM that is unpatched a malicious app could take full control of your phone...
Having said that, it still might be possible to enter recovery mode and reflash without S-OFF, but I really haven't done much research and wouldn't know where to start

Its just a shame there is not much going on in this section compared to other phones, lol.
I'm just going to take it into to town and get it unlocked for cash on the weekend, then save for a Galaxy S2.

Does not work for me with Wildfire S HBoot 0.90 and European T-Com ROM 1.34.11.5

Hi!
I had the same 11th line as on picture - 9.0.0.0.
I put the tutorial values and a solutions works 4 me as well.
I don't remember ROM version but was branded for tmobile polska, and I'm sure that was never than 1.30.401.2. - something like 1.33.xxxx or even 1.35.xxxx
After all I tried a goldcard method - now works fine.
Many thanks for a solution!!

Chinese to european ROM
Hi
I'm trying to install the euro ROM (1.33...) using the goldcard metod in my Wildfire S but I get the downgrade error (now I'm running a 1.38... version and 0.90.0000 HBOOT).
Now I'm in China and I don't know why can't visit mediafire for download the zip with the files that I need for follow this tuto. Is there some alternative web for get this files?
Another question is if in the future will be a euro version newer than the chinese one that allow me to change the ROM without do the practice of this tuto.
I have not a lot of experience doing this, so it will be grat and easier for me
Thanks in advance!!

There's no way to tell if there will be a newer official HTC ROM > 1.38..., but if there is, you should be able to download without this tutorial.
I've re-uploaded the files to a few more filehosts, hopefully you can access at least one of them:
http://www.megaupload.com/?d=OKI8MVO1
http://depositfiles.com/en/files/fodci19ux
http://www.zshare.net/download/926497736bd36c1c/
http://uploading.com/files/9fa81218/tools.zip/
http://www.filesonic.com/file/1452304874/tools.zip
http://hotfile.com/dl/124169210/fc79b70/tools.zip.html

Thanks mphi!!
Yesterday was my first post. Im very lucky to enjoy this comunity

hi i get an error after part 11 i get access denied

Can't get root permissions
sammyke007 said:
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...
Click to expand...
Click to collapse
Same problem
I'm running HBOOT 0.90.0000 an my rom is 1.38.1400.5, official HTC chinese ROM

Need assistance downgrading 2.36

Hello,
My DHD is running 2.3.3 Gingerbread with 2.36.771.14 Build Number.
It's a branded phone so I followed THIS guide on creating a Goldcard which I have now done.
My next step was to follow THIS precisely however I end up with a few errors in the CMD. I've moved the PD98IMG.zip file into the root of the SD Card unextracted, I've extracted the Download_v2.zip into the C:\ Drive on my computer.
This is what I input into the CMD:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\NAME>CD/
C:\>CD Downgrade
C:\Downgrade>adb push misc_version /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1718 KB/s (15837 bytes in 0.009s)
C:\Downgrade>adb push GingerBreak /data/local/tmp
1369 KB/s (16830 bytes in 0.012s)
C:\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
C:\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./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
I've searched for a few days on how to resolve this issue, the only solutions that I've seen is to retry making a Goldcard and perform a factory reset and follow the steps again. I've done both and yet I still receive this error, can anybody point me in the right direction?

Is this before or after you managed to downgrade using the goldcard?
If its after the downgrade to 2.36.405 or lower, use this...
http://driphter.com/index.php?topic=3867.0
You may not have to downgrade as Gingerbreak should work with your v2.36 as well (as its just the carrier modded 2.36. The .771 signifies the vendor's id#)
eg: Telus = 661, hence all telus builds are .661.x

Hi there thank you for your quick response,
I have not yet managed to downgrade at all, that is where my problem lies.
- I will try that guide out and let you know the result.

I followed that guide, however the RUU gives me an error:
"ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again."

TheRealKeyboardWarrior said:
I followed that guide, however the RUU gives me an error:
"ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again."
Click to expand...
Click to collapse
You're going to need to use the goldcard to downgrade first then, then you'll be able to root only after downgrading.
(Try this method: http://forum.xda-developers.com/showthread.php?t=1152233&page=7 to DOWNGRADE ONLY!)

That guide is for 2.37, I'm on 2.36.771.114 Build.

TheRealKeyboardWarrior said:
That guide is for 2.37, I'm on 2.36.771.114 Build.
Click to expand...
Click to collapse
it should still work. Either the bootloader will bypass the update to 2.37, or it will take. If it takes, then you can downgrade to 1.32 and root your device. If it doesnt, then it doesnt and you're still on 2.36.771.
So its either a win situation, or a loss of 10 minutes. lol

JSLEnterprises said:
it should still work. Either the bootloader will bypass the update to 2.37, or it will take. If it takes, then you can downgrade to 1.32 and root your device. If it doesnt, then it doesnt and you're still on 2.36.771.
Click to expand...
Click to collapse
Great, I'm halfway through the process as we speak. Thank you for your consistent help so far.

JSLEnterprises said:
it should still work. Either the bootloader will bypass the update to 2.37, or it will take. If it takes, then you can downgrade to 1.32 and root your device. If it doesnt, then it doesnt and you're still on 2.36.771.
So its either a win situation, or a loss of 10 minutes. lol
Click to expand...
Click to collapse
I am now rooted and have Radio-off. I will be flashing LeeRoid later today, thank you very much for all your help

N.P.
Recommendation: use the 2.36.405.8 ruu to update to that version and root it (unless you want to update your raidio using fastboot and shell commands)

[TUTORIAL] Error 190 Fix (Works with 2.13.401.3)

Hi, here's an tutorial how to Fix the "ERROR[190]: ROM IS NOT UPDATED"
mphi said:
Warning: You could probably brick your phone if you flash an invalid misc partition. So follow these steps carefully (or not at all)!
Click to expand...
Click to collapse
Android Tool's what you will need : Click
Confirmed: http://forum.xda-developers.com/showthread.php?t=1444512&page=2
1. Be sure u got all drivers.
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. Unzip my pack somewhere. I suggest like (x:\folder)
4. Start cmd. Be sure u are in the ADB folder with CMD.
5. Write those commands carefully, be sure you wrote them correctly.
adb push flash_image /sdcard/flash_image
adb push zergRush /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/zergRush
Click to expand...
Click to collapse
Enter Shell by using
adb shell
*You should notice $*
Click to expand...
Click to collapse
Execute zergRush
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
adb shell
*You should notice that $ changed to #*
Click to expand...
Click to collapse
Get the misc.img
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
Click to expand...
Click to collapse
Copy misc.img from sdcard to current directory
adb pull /sdcard/misc.img misc.img
Click to expand...
Click to collapse
6.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. I set my version number to 2.13.401.2 since this was the version number. The changes made will be highlighted in red. File -> Save As and name it misc2.img.
Pictures!
1. Find your version my was 10.13.401.2
http://i.imgur.com/xfltH.png
2.Write currect Version (Dont worry if something will left, we will get off this soon)
http://i.imgur.com/yHp9W.png
3.Change the Selected number what left, for me it was 2. Then in this BIG table of weird things, there will be selected an value for me it's 32, just change it to 00, and save file. Should look like this:
http://i.imgur.com/3omav.png
Click to expand...
Click to collapse
If your version of misc.img match the required version of the RUU you can complete the tutorial (this is not a problem to which this guide will help you). If the versions are different, set the version that is required, and continue the tutorial from step 7.
7. Back to adb window. Copy the misc2.img to sdcard. (no # or $)
adb push misc2.img /sdcard/misc2.img
Click to expand...
Click to collapse
Flashing time
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 777 /data/flash_image
*Flash Command, it depends your life, be sure you wrote this correctly*
/data/flash_image misc /sdcard/misc2.img
Click to expand...
Click to collapse
ALL CREDITS TO mphi, i just edit it to zergrush...
Click to expand...
Click to collapse
After those steps you should be able to install RUU from htcdev to unlock bootloader.
Reply if something went wrong.
If it helps just click THANKS
If you use zergRush again, clean dump's from zergRush via
Code:
adb shell
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh

My version was 10.13.401.2 I've changed it to 2.13.401.2 so now I should go on from step 7?

Yes, go to step 7 edit it to good one and flash it.
I edited the red text so it will be easier to undestand good luck

Hi Unkheq,
Came back to hit thanks!
It totally worked for me, it was showing version 10.13.401.2 and i edited to 2.13.401.2, followed all your steps exactly and all went fine.
RUU ran succesfully.
Thanks for the tut!

adb shell
*You should notice $*
Click to expand...
Click to collapse
done ok I get $
Execute zergRush
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
adb shell
*You should notice that $ changed to #*
Click to expand...
Click to collapse
Fail.. I get premission denied.
What should I do now?

hi gusta1,
Did you give zergrush full permissions with this command: adb shell chmod 777 /data/local/tmp/zergRush ? it's under step 5.

yes I did and all went well till executing zergrush... here I get a premission denied

are you sure u copied zergrush in good directory, or try giving chmod again

Unkheq said:
are you sure u copied zergrush in good directory, or try giving chmod again
Click to expand...
Click to collapse
I write code a several times and allways stuck at that point... i don't know what to do anymore.. what could be wrong? My WFS is S-ON and it is not rooted yet

gusta1, be sure you are in the directory where you put the files. For example, if you extracted them in D:\WFS\APPS then in CMD you need to type command: chdir D:\WFS\APPS and after that start with step 5 from tutorial.

I have the same problem as gusta1 even I'm in proper folder I've got following message:
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: Permission denied
$
Click to expand...
Click to collapse
I run cmd as admin (Vista), repeated prcedure and restarted phone several times, but with the same result.
But my history is different. I have S-off my Wildfire S successfuly at the begining when I was on 2.3.3. However I put phone to my wife and once phone asked for update to 2.3.5 she allowed it and S-off was gone. Since that I can not move, everywhere is some error.

Anorien said:
gusta1, be sure you are in the directory where you put the files. For example, if you extracted them in D:\WFS\APPS then in CMD you need to type command: chdir D:\WFS\APPS and after that start with step 5 from tutorial.
Click to expand...
Click to collapse
I tried again and I got same result... I am in good directory,Any idea?

Hi,
Try this:
After entering "adb shell":
run these commands in adb shell:
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
Then continue with the step to execute zerg rush.

Anorien said:
Hi,
Try this:
After entering "adb shell":
run these commands in adb shell:
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
Then continue with the step to execute zerg rush.
Click to expand...
Click to collapse
Thanks!! You are the best!! I made it with your advice!

Oh i forgot about cleaning commands if x times zergRush, will add ^^

gusta1 said:
Thanks!! You are the best!! I made it with your advice!
Click to expand...
Click to collapse
You welcome, glad I could help!

Worked with orange romania wildfire S phone.
Thanks

Thank you very much it worked fine for me>>> all the thanx

Hi
I've got an UK T-mobile S_ON WFS with
HBoot 0.90.000
Android 2.3.3
Rom 1.34.11.03
HTC unlock bootloader fails with error 190 and tip http://forum.xda-developers.com/showthread.php?p=21120374 fails with Hboot bypassed.
Am I likely to have any major problems? Don't want to brick my phone.
Thanks

Help
* bump *