Database Users

How to root (& unroot) a South African HTC Dream (MTN). [Now with froyo!]

(this comes from my post in the 'Rogers, heres your real root' thread, using a combination of Haykuro's and Lunatik78's methods)
EDIT! now with Froyo (Android 2.2), I've tried Chromatic 4.2, 4.3 & 4.4 (based on Cyanogen 6 RC3), BiffMod, AOSP 2.2 OTA, Yoshi 1.8 pancake and they all work - 12 Jan 2011
EDIT: newer radio works great too - now using 2.22.28.25 and H-Boot 1.33.0013d - follow ezterry's thread after rooting and getting your new ROM running - http://forum.xda-developers.com/showthread.php?t=831139
*Please reply to this thread with feedback if you've used this method! (And please let me know if a link is broken!)
I've just re-rooted my South Africa HTC Dream and thought I'd share my successful method, it's actually pretty easy. Please note however, that the steps in this method must be followed EXACTLY otherwise will not be successful.
BTW the HTC Dream's were only released by MTN but as the phone is not carrier specific Vodacom, Cell-C & Virgin-Mobile will work fine too.
To unroot your phone and go back to stock, PM me for the link for the RUU
This will very likely work on the Rogers Dream as that is what the original how-to was based on, if someone tries it, please let me know so I can confirm it here!
Info from phone: (yours needs to be the same otherwise you might have problems, the important stuff is in bold - if you don't know how to find this info then STOP here, you need to search & read up some more to familiarize yourself before rooting the phone)
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA20000)
CPLD-4
RADIO-3.22.20.17 (or 3.22.xx.xx)
Jun 2 2009,21:33:16
Firmware: 1.5
Baseband: 62.525.20.18U_3.22.20.17
Kernel: 2.6.27-9af60ed4 [email protected]
Build: 1.87.421.1 146733 CL#47295 release-keys
Start:
Make sure your battery is fully charged!
This requires that you use SPL 1.33.2005. (this is safe on all rogers (or MTN) dream devices)
You need the Android SDK - get it here: http://developer.android.com/sdk/index.html
install SPL 1.33.2005 using this method: One Click Root for Rogers, come back here at Step 11 (see link below this how to install flashrec on a stock phone)
(See: Method to install flashrec (any .apk) on your Dream: steps-to-install-and-uninstall-apk-file-on-android-g1-device)
Check if you have SPL 1.33.2005 (to check, boot into FASTBOOT by holding Send or Answer and then powering the phone on, it should say HBOOT-1.33.2005 near the top)
IF you have it then proceed:
download givemeroot.zip
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
Extract the contents of 'givemeroot.zip' to the "android-sdk-windows\tools" folder
IMPORTANT: You have to put the rom you'd like to install (I've used Cyanogen's and SuperD's) in the root of your phone's sd card (a freshly formatted FAT32 SD Card) as well as the rom image "signed-dream_devphone_userdebug-ota-14721.zip" (MD5 checksum b3e12b004c155761a10b1a848288e0c3 - 3rd option - from here: http://developer.htc.com/adp.html#s3)
(YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE ROM IN ZIP FORMAT TO GET ONE)
For Dream/G1 users: power off, then hold "send or answer" button & press power button until you're into "FASTBOOT" mode, make sure the words HBOOT-1.33.2005... appear near the top of the phone's screen!
NOW:
Connect the phone via USB to the computer if it's not connected already, 'FASTBOOT' should change to 'FASTBOOT USB'
Open a command prompt (Start>Run: cmd), navigate to your "android-sdk-windows\tools" folder and type in the following (hit enter after each line and wait for the 'finished.total time: x.xxxs' before continuing!):
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
POWER OFF your phone (not reboot, power it off). (You can do this using the corresponding button [it says it on the screen] or just pull the battery [make sure everything is done flashing of course!])
(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)
Unplug your phone from the USB connection
Power up your phone in recovery mode (hold "home" + press Power). You should see that you are now in v1.4 + JF, that means you got the right recovery.
Select the option "Apply any zip from SD". Select "signed-dream_devphone_userdebug-ota-14721.zip", and then press the Home button to confirm. Do not reboot your phone yet!
Once that installation is complete, select the option "Apply any zip from SD" again. This time, select "update-cm-4.3.2.1-signed.zip" (or Cyanogen's current version, or your preferred ROM, I've used 1.6, 2.0, 2.1 & 2.2 ROMS, and then press the Home button to confirm.
When this is complete you'll see this:
Build: CyanogenMod v1.4 + JF
Formatting CACHE....
you may see "writing radio..." and boot back into the recovery but just reboot your phone by pressing Home & Back (or the trackball when "reboot" is highlighted). When you see "Formatting CACHE....", it's done, reboot now again (Home + Back).
The first proper boot of the OS may take a while (5+ minutes) then enjoy!
The newer radio image 2.22.23.02 works great on the SA HTC dream - I definately get better reception/more bars, I flashed it like this (In THIS order):
1) fastboot erase recovery
2) fastboot flash radio radio.img (get the img from here: http://forum.xda-developers.com/showthread.php?t=640535)
3) fastboot flash recovery recovery.img (used Recovery-RA-1.7.0 from here: http://forum.xda-developers.com/showthread.php?t=566669) (no need for the "Recovery-RA-1.7.0R" recovery image!)

Thank you, your guide work perfectly on my phone

No luck here, unfortunately. I'm stuck at the Recovery Flasher. I get Flash FAILED: Could not run command. Could be that your kernel was not patched yet as the newer Rogers one is running HBOOT-1.33.0010 (DREA21000). Oh well, I hope someone finds a way soon!

If your phone info is the same as listed in the first post then this will work (if followed correctly). Anything different may require a different method, I suggest searching for a solution.

problem with entering recovery mode using power+home button
ok, so now i am desperate....
i have read and read and followed instructions in all the forums that google can generate using different keywords and everything about the issue. so i have totally exhausted the options i got.
My phone is the SouthAfrican mtn HTC dream with the so called perfect spl 1.33.0010 SPL.
firmware version 1.5
baseband version
62.52s.20.18u_3.22.20.17
kernel version
2.6.27-9af60ed4
[email protected]
build number
1.86.421.1 146733 cl#47295 release-keys
hboot info is as follows:
Dream PVT 32B SHIP S-ON d
HBOOT- 1.33.0010 DREA20000
cpld-4
radio - 3.22.20.17
jun 2 2009
ok now when i install flashrec, on the top corner it claims that my device is a
i hve tried the fastboot method of rooting, but my attempts end when cmd give a remote- not allow error
so i have tried using the method above. i have successfully installed flashrec, backed up my existing image, no problem. so at this point i am supposed to shut down the phone and reboot into recovery, by holding the home button when powering up.
i tried using the reboot into recovery using the button provided in the new flash rec but nothing happens.
when i restart the phone while holding the home button, the HTC DREAM logo comes up and just freezes there. i have held the button for up to 5 minutes, nothing, i have also left the logo on for almost half an hour and nothng seems to happen.
Please help me out anyone? this phone is pretty lame as stock especially for the amount you pay for it..

sounds like you're not doing it to the letter, after installing flashrec it says "For Dream/G1 users: power off, then hold "send or answer" button & press power button until you're into "FASTBOOT" mode, make sure the words HBOOT-1.33.2005... appear near the top of the phone's screen!" NOT 'i am supposed to shut down the phone and reboot into recovery, by holding the home button when powering up."
if you don't do it right it won't work right

pardus said:
sounds like you're not doing it to the letter, after installing flashrec it says "For Dream/G1 users: power off, then hold "send or answer" button & press power button until you're into "FASTBOOT" mode, make sure the words HBOOT-1.33.2005... appear near the top of the phone's screen!" NOT 'i am supposed to shut down the phone and reboot into recovery, by holding the home button when powering up."
if you don't do it right it won't work right
Click to expand...
Click to collapse
true that.. i found out that i was downloading the wrong recovery image... for you MTN guys, be sure to use
recovery-RA-dream-v1.7.0R.img
and not the previous version as it did not work for me!!!
thanx so much!! cant wait to try our eclair!!!!!!!!!!!

Hi,
Thanks for great post on rooting your SA dream. I've been trying to root my phone for ages and have bricked it once.(But thank goodness leaf didnt released it and fixed it at no charge) So this time when I do it, I wanna be very sure.
When you say:
"You have to put the rom you'd like to install (I've used Cyanogen's and SuperD's) in the root of your phone's sd card "
Where do i get the cyanogen or SuperD's rom?

Scratch what i said before... i used Chromatic 4.5 rom and my build number is 1.86.421.1 146733 cl#47295 release-keys.
And it works perfect.
Thanks so much. Looks amazing

If you haven't figured it out already then you can get a ROM from one of the ROM threads in the G1 Android Developement section.
But perhaps it might be a good idea to do a little more reading as to why you would like to root and what ROM you would actually like on your phone, remember you can't just put any ROM on and may brick the phone again if you make a mistake.

You effin ROCK!!!!!
Worked like a charm!

Thanks Pardus! My HTC Dream is now like a new phone! I'm loving it!
Only problem I had was the rom image "signed-dream_devphone_userdebug-ota-14721.zip" from developer.htc.com/adp.html#s3 was either corrupt or just not dowloading properly. I got nervous at first when it didn't work but then googled the file name and downloaded another copy. I then mounted the SD card and placed the new file in the SD card root. It was all good from there.
Awesome!!

Excellent, doesn't it just give new life to our Dreams !
So far the 'Official AOSP 2.2 OTA test-3' ROM is working well for me as is the new radio and spl (2.22.28.25 and 1.33.0013d).

okay im new tothis and im a noob lol, well im having problems with the cmd section, cant get my pc to do anything with cmd, any idea's on how i can get past this? Since I havent actually ever used cmd before so I don't actually know what i need to type when I get to that step, please help

Ashman46 said:
okay im new tothis and im a noob lol, well im having problems with the cmd section, cant get my pc to do anything with cmd, any idea's on how i can get past this? Since I havent actually ever used cmd before so I don't actually know what i need to type when I get to that step, please help
Click to expand...
Click to collapse
OK, you'll need to learn quick, read read read here on the forums. Mistakes can brick your phone.
To get a Command prompt in Windows (XP) click: Start, then Run, then type "cmd" (without quotes) then click OK
If you have the SDK installed properly then you can try typing "fastboot getvar battery-voltage" (without quotes) and see what result you get.

Okay I figured out how to use cmd, I'm running windows 7, now I have one huge problem, I type in the full name and everything with the "fastboot flash radio radio.img" then it tells me error: cannot load 'radio.img' what do I do now? Since I know I can't skip this step

pardus said:
If you have the SDK installed properly then you can try typing "fastboot getvar battery-voltage" (without quotes) and see what result you get.
Click to expand...
Click to collapse
okay so I tried the "fastboot getvar battery-voltage" but all it says is "<waiting for device>" and nothing happens after that, so now what do I do?

Are the contents of "givemeroot.zip in your "android-sdk-windows\tools" folder?

Ashman46 said:
okay so I tried the "fastboot getvar battery-voltage" but all it says is "<waiting for device>" and nothing happens after that, so now what do I do?
Click to expand...
Click to collapse
Your phone has to be in fastboot mode: "For Dream/G1 users: power off, then hold "send or answer" button & press power button until you're into "FASTBOOT" mode, make sure the words HBOOT-1.33.2005... appear near the top of the phone's screen!" then connect it to USB...

yeah all of it is there. i dont know maybe im missing something?

HTC Magic (PVT 32A) bricked or can it be saved?

Hi all,
spent entire last night trying to figure out how to flash a custom ROM into my phone - problem initially was that I'd updated it with the ROM from the HTC site, so it was in perfectSPL.
Anyway, after a lot of searching and attempting I managed to get in an engineer SPL and then attempted to flash with the Cyanogen Mod 5.0.7. It kept on giving me an error which I figured was due to my Radio being the newer one, so I went through these instructions to flash an older one, using the following code:
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
Click to expand...
Click to collapse
But in my case I used Radio_HTC_PVT_32A_3.22.20.17.img so as to get the Cyanogen Mod to (hopefully) work, and I used the recovery-RA-hero-v1.6.2.img as that was the one I'd used to get the engineer SPL installed as well. I did use the suggested hboot-1.76.2007.img, but probably made a mistake in doing so? Reading further down the page for changing RADIO it describes how to downgrade to radio 3.22 and it says I should use hboot-1.33.2010.img instead....
After the last command, however, it went into reboot but since then I'm stuck with this screen regardless of how I boot (recovery/fastboot/regular) - see attached image.
(I did enter the command literally as above, no space between reboot and -bootloader - that of any concern?)
My problem seems to differ from the others I've read about when searching for "bricked" - I'm perfectly willing to accept my fate if it really is bricked, but as of yet I'm not quite convinced. For one, if I run the HTC official updater it starts and actions are displayed in the HTC screen, but unfortunately it always stops at 36% when sending Radio... so fairly sure it's something wrong with it.
Question is: is there any way to re-flash another (proper) Radio and see if I can get anywhere from there?
Would appreciate any suggestions
Cheers
//Joris

maybe if you read the proper directions - even my thread has links to them then u would be fine
you need the 2010 spl for that radio and u have a 1.76.2007 spl u used ...
I suggest u look up cursordroids directions

As a follow-up, please see attached image - this is what I get when I try to use the fastboot commands to either flash radio or hboot

JorisS said:
As a follow-up, please see attached image - this is what I get when I try to use the fastboot commands to either flash radio or hboot
Click to expand...
Click to collapse
do u have v 2007? or a perfect spl installed - I think its perfect...

i do not know if this helps. but if you managed to flash the older radio, then try to flash an original rom for your board which includes old radio and post any results.

alan090 said:
maybe if you read the proper directions - even my thread has links to them then u would be fine
you need the 2010 spl for that radio and u have a 1.76.2007 spl u used ...
I suggest u look up cursordroids directions
Click to expand...
Click to collapse
Thanks for the quick reply - I realize I messed up, was getting later and later so lost focus I'm afraid. Plus been reading so many different instructions and suggestions that I simply lost track and - in this case - failed to read further down the page. (I am indeed on his page, the one you link to on yours)
However, question right now is whether or not the phone can be saved? See my above post - it won't flash in another radio or SPL at the moment, at least not using fastboot command from the cmd prompt. Any alternative suggestions or other commands I can/should run first?
Cheers
//Joris

mariosraptor said:
i do not know if this helps. but if you managed to flash the older radio, then try to flash an original rom for your board which includes old radio and post any results.
Click to expand...
Click to collapse
I tried using the official HTC ROM (that comes as an .exe package) - tested with the last official one I get when I download it from their site, as well as the one before which I got from this sites ROM collection - both get stuck at 36% when "sending Radio" I believe it says at that point. I did try this one as well: 2.17.401.2 HTC Nordic - from what I could see this is the oldest Nordic HTC ROM - that one however gave me another error message, something about wrong Board or so I believe.
Which one would you suggest I try? At this point these .exe packages seem to "work", at least they start and identify the phone and all.
alan090 said:
do u have v 2007? or a perfect spl installed - I think its perfect...
Click to expand...
Click to collapse
I'm afraid that at this point I really do not know anymore
I followed these steps to get past the 1.76.0009:
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
Click to expand...
Click to collapse
After this I proceeded with the following:
fastboot flash radio Radio_HTC_PVT_32A_3.22.20.17.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.6.2.img
fastboot erase system -w
fastboot reboot-bootloader
Click to expand...
Click to collapse
(I have now edited in the exact files I used)
After this I ended up in the position I'm in now - it did a reboot but nowo I'm only getting into the screen as shown in the first attachment.
On a sidenote, how can I get my account verified so I do not have to wait 5 mins between posts?

I just tried the following ROM update:
RUU_Sapphire_HTC_Europe_2.17.401.2_HTC_Nordic_release_signed_NoDriver.exe
Result is as per attached image.
Seems I've managed to mix up everything and managed to have incompatible radio/hboot and probably also SPL....
Is there any way to fix this

what version of spl does your fastboot report?
if you have 2007 u should be able to fastboot images
if you have perfect spl u may have to root again using gold card...

alan090 said:
what version of spl does your fastboot report?
if you have 2007 u should be able to fastboot images
if you have perfect spl u may have to root again using gold card...
Click to expand...
Click to collapse
How do I check this? Was testing around some more whilst hoping for a reply here and found that I cannot find the device using the adb devices command, but the phone appears to be in fastboot mode as I can detect it with "fastboot devices". That said and as the attached image in post #3 shows, I can't seem to flash images - giving me an error message.
So basically on the phone it displays what's shown in the attached picture (if I plug in the USB cable then "USB" shows up behind the orange RUU text). Regardless of whether I try to start it with home + power, back + power or just power. It comes to the same screen.
Will start reading into gold card and what that is/how to make one - saw the term passing by here and there already.
Thanks so far, much appreciated!

It seems I've ended up in one of these loops one cannot get out of - checked out how to make a goldcard (theunlockr.com/2010/03/10/how-to-create-a-goldcard/ and some other sites) and basically I need to be able to use ADB in order to get the CID of the card. Problem is that I can only access fastboot, not ADB.
Guess it's game over then?
Would it be possible in any other way to root/flash the phone using fastboot only?

Just attempted to use the fastboot to flash sappimg.zip, giving me the following:
fastboot -s HT95NKF09666 flash zip sappimg.zip
sending 'zip' (63878 KB)... OKAY [ 12.561s]
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)
finished. total time: 41.653s
Click to expand...
Click to collapse
Does this give away any useful information towards a possible rescue?

try goldcard

jejer said:
try goldcard
Click to expand...
Click to collapse
I did - followed a guide and used an ubuntu bootcd to get the CID off the SD card and successfully made the goldcard. But don't know what to do with it really, since the phone goes straight to the same RUU screen even if I try the 'vol down' + 'power' button boot.
That's why I tried using fastboot to flash the sappimg.zip, goldcard was inserted into the phone at this point. Result is as shown above I think I need a newer version of the sappimg.zip file - any such thing available?
//J

If you can get to fastboot than an RUU install + goldcard can work. From there you can re-root and start fresh. Just pick an RUU suitable for you phone and is rootable afterward.

I think the problem is with my radio version - either it being from an older ROM or somehow it was corrupted.
But just to be sure - how should I do the RUU install + goldcard? Simply insert the goldcard (completely empty otherwise?) and run the latest RUU I have downloaded from HTC using my serial number?
How does the goldcard differ from a regular memory card when performing an RUU install? Isn't the part that messed up in the phones memory?
Thanks
//Joris

yes, just do the RUU exe install. The goldcard is just an SD with a modified header that allows the RUU to ignore any issues with reporting a model id error. You may not even need a goldcard depending on the RUU and what the phone reports. Nothing else special about the goldcard, you can fill it like any other or format later. I left mine alone and used it like normal.

I've tested this with the following RUU versions (and the goldcard inserted):
* RUU_Sapphire_HTC_Europe_2.17.401.2_HTC_Nordic_release_signed_NoDriver.exe
* RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_Nordic_release_signed_NoDriver.exe
Both these give a bootloader version error. Tried these two:
* RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe
* RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe
With those the installation freezes at 36%. I've attached the RUU report file, in case that is of any help?
I could in principle carry on and try every single RUU that's available, but getting increasingly doubtfull that any will work. It simply seems as though either it's a wrong version or something goes wrong when it tries to update the radio, but I don't know why (I mean - it's overwriting whatever's on the phone, isn't it? Why would it freeze? I successfully used the same RUU before I started messing about with rooting and all that to update the phone to latest firmware).
Gah!
*edit*
forgot the file
Also, when it comes to 36%, the screen on the Magic goes black and the LED at the top turns blue...

Maybe try downloading the latest offical RUU from the HTC website, and then try to root it after?

Thanks but I've tried that.... stuck on 36%, "Updating Radio".
I managed to create a complete mismatch it would seem, i.e. the hboot and the radio and the actual main version (it is, according to the RUU updater, on 3.05.401.3 version), so whenever something works, something else doesn't - etc etc. Crap!

Bricked MT3G 1.2? Cant recover

So I tried unlockr's tutorial to rooting and along the way something went wrong and I was getting htc magic splash. Now everytime I try to run sappimg it hangs at unzipping and when I try to run recover.img or any other img, in cmd prompt I get a signature verify fail. Haven't had the phone for 48 hours yet and managed to **** it up. Help. Anyone.

wrong sappimg
Donarudo said:
So I tried unlockr's tutorial to rooting and along the way something went wrong and I was getting htc magic splash. Now everytime I try to run sappimg it hangs at unzipping and when I try to run recover.img or any other img, in cmd prompt I get a signature verify fail. Haven't had the phone for 48 hours yet and managed to **** it up. Help. Anyone.
Click to expand...
Click to collapse
Ok first stop and open the sappimg dont un zip just click on it. them click on the android-info.txt if it reads this your good
ModelID: SAPP10000
CIDNUM: HTC__037
CIDNUM: 11111111
MainVer: 2.53.707.2
If it reads any thing else its a simi brick I hope you got insurance if ya do pm me ill walk ya in so you can get a new one!
Ok just do the fastboot radio,hboot.nb0,recovery,reboot and your good
i had the same ish with the unlocker steps. I simi bricked it with the wrong sappimg if the cidnum say some thing like vada-xxx (x=numbers) or some thing do not update with it.

How is this ROM Development?
Moved to General.

Yes, the txt checks out. Every time I try those commands I receive the signature verify fail error. I've tried to reflash the sappimg to the phone again and again and I get 'unzipping' then nothing. My phone also reads:
SAPPHITE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
If this helps.

Can ANYONE please help me. I regret trying this and just want my phone back to normal... So many smart ppl on here but nobody is giving me their .02 cents. Sheesh

Donarudo said:
Can ANYONE please help me. I regret trying this and just want my phone back to normal... So many smart ppl on here but nobody is giving me their .02 cents. Sheesh
Click to expand...
Click to collapse
yea bro i can help but i need more info\\where are you files placed and what are your file names

Can you hold the power and home button to get into your recovery screen?

thricemin said:
Can you hold the power and home button to get into your recovery screen?
Click to expand...
Click to collapse
No it wont. for some funky reason the radio and spl are linked to the board tmobile attempt to lock root out thats why the 1.2 kernel dose not support wifi teather apps, but i never tried any of of the hero teather apk or hacks.
But If you did every thing on the unlocker site for the fender/1.2 it should work>>>>
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
8. Once the phone starts to turn back on begin holding home and power (do not let go until you see the recovery mode) to boot into recovery mode.
9. You should end up in Amon Ra’s recovery mode. Now click on USB MS Toggle to turn on USB mounting. Plug in your USB cable and you should be able to access your memory card on your computer now.
10. Load the custom Fender ROM with Root added below onto your SD card (NOT in any folder, just on the SD card itself, do NOT extract it, leave it as a .zip)
Custom Fender w/ Root Access (THIS WORKS FOR THE MYTOUCH 1.2 OR FENDER).
Then click the button on your phone to disable USB MS Toggle and then click Apply .zip and select the Fender ROM .zip file we just put on the sd card.
Once it loads click reboot and you are all set!

[Q] Main version older! Update fail!

Disclaimer: I have searched and searched, but found nothing that works.
Mytouch 3g, google branded.
Rooted about a year ago. Installed CM5(I think it was 5). Got greedy and messed it up. Tried to go back to stock. Failed. Bought a Vibrant. Put the mytouch in a drawer. Trying to get it to work again. Here is the problem(s):
The recovery installed was a vodafone. It booted up fine, but when on the welcome screen where it says "touch the android to begin" the phone would not recognize the fact that I was actually touching the screen. Track ball worked fine, but since it actually wanted me to touch the screen it was a no go.
Today while trying to fix the phone and trying to flash all kinds of recovery images I would get the "Main version is older! Update fail!" message. I finally found one (the 2.53.707.2_-_sappimg.zip) that would actually get past the update fail.
The phone now boots up to the main home screen. But it still does not recognize the fact that I am actually touching the screen. The only way I can navigate anything is by using the track ball.
When I click on the "dialer", "contacts", or "call log" icons I get the message:
"Sorry. The process android.process.acore has stopped...blah blah blah"
Does anyone have any ideas?
I have a gold card.

Download my fastboot commander from my signature and provide here all device info.
Just don't flash anything until i say so... you have been warned.

I have a similar problem.
Device info:
SAPPHIRE PVY 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:28:28
Initially the device wouldn't boot up at all. I managed to flash an RRU and get Android to boot the phone but now the problem is the SDCARD isn't recognized, every time the device boots up it says SD CARD is ready to be removed. I found a command to fix the sdcard bit from the cyanogen mod forums even though I am not running it (I know) remote boot is not allowed on my phone so I can't even use that. Tried to flash the Engineering SPL 2.53.707.2_-_sappimg using a gold card but it pops up stating:
Main Version is older!
Update Fail!
Please help!
[EDIT]
Also, fastboot getvar version-main gives out the following:
version-main: 2.56.494.7
I understand that my version is higher. Is there a way I could modify it? or the sappimg to think otherwise?
[EDIT]
Cheers!
[UPDATE]
I have managed to root using one click method and now have busybox and su.
I have also managed to flash amon_ra recovery without sd card (well obviously since SD card isn't working for me). Recovery doesn't see the sd card either sadly.
[/UPDATE]

[Q] Mytouch 4g can't load

Hey guys,
I know this has been asked and discussed many times here, but I'm really frustrated and can't get my problem solved!
I have tried to "factory reset" my phone regularly from the settings, but since then it restarted and never booted again. I have tried many steps out there to go around or solve this problem but no hope! it just goes to white "HTC" screen and that is it!
when I hold vol down and power, it goes to H-boot, with the following screen. I tried everything from the screen, here are the results: (of course connected with USB)
it quickly checks for pd15img.zip and says "wrong image" or "wrong file"
1- Fastboot: new menu:
-Bootloader: goes back the first menu.
-Reboot: restarts and stays on the "HTC" white screen for ever.
-Reboot Bootlaoder: FREEZES!
-PowerDown: shuts down.
2-Recovery: restarts then screen shows a cellphone with green "sync" arrows on top. then screen turns off and phone vibrates short and quick 8 vibrations.
3-FactoryReset: FREEZES!
4-Simlock: FREEZES!
5- Image CRC: FREEZES!
what do I do? if you know other thread talks about this problem please direct me to it. I'm suppose to be a Communications Engineer in my fourth year... but after seeing this problem and how clueless I am.. i feel like ****!
thanks in advance
Code:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.09-04-26_,
eMMC-boot
APR 14 2011,13:18:22
HBOOT
[COLOR=ORANGE]<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FAST BOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

Tell me something, please. What is the name of the FIRST THREAD at the top of this sub-forum?

Jack_R1 said:
Tell me something, please. What is the name of the FIRST THREAD at the top of this sub-forum?
Click to expand...
Click to collapse
Thank you for your reply, But yes I have read that thread and tried their steps. However, my phone checks the PD15IMG.zip file and shows the following:
Code:
CID incorrect!
Update Fail!
press <power> to reboot.
and when I pressed the power button it reboots and stays on the "HTC" white screen. could it be there is something wrong with the file? or do I need PD15IAG.zip file?

Now tell me something else. What does Google show when you search for 'PD15IMG.ZIP CID incorrect update failed'?
And what can you learn about your phone, if it shows this message?
Isn't this the very very basics of searching for solution?

Jack_R1 said:
Now tell me something else. What does Google show when you search for 'PD15IMG.ZIP CID incorrect update failed'?
And what can you learn about your phone, if it shows this message?
Isn't this the very very basics of searching for solution?
Click to expand...
Click to collapse
Ok Mr obvious! you seem to be too cool to talk or give a solution, just looking for the "thank you" hits.
what a waste. Still couldn't find what you were referring to as " the very very basics". Plus your forum that you were too cool to mention its name didn't say anything regarding "CID not found update fail"
but thanks again, no bad feelings :angel:

Try formatting your sd card to fat32. I did that to mine,made sure hidden extentions were off and put it on my sd and it worked like a charm.
Sent from my HTC Glacier using xda premium

gamingwiz said:
Try formatting your sd card to fat32. I did that to mine,made sure hidden extentions were off and put it on my sd and it worked like a charm.
Click to expand...
Click to collapse
This is good only if PD15IMG wouldn't be read at all. Judging by OP's message, his phone actually loads PD15IMG and fails the CID check. It would be also very, very strange if his PD15IMG would be corrupted in such way as to remain a proper ZIP, but corrupt the signature file with CID. Also, I believe that he at least did the download right. Maybe I'm giving him too much credit.
Dear Mr. OP,
I don't give solutions to people that are too lazy/ignorant/blind to make the minimal required basic effort to get to the solution themselves. If you'd bother searching, you'd see that the FIRST Google hit is a specific page on a specific thread in this forum, and if you had something that remotely resembles brain, you'd learn that most likely:
1) You don't have MyTouch 4G, but another phone (though also an HTC Glacier).
2) There's a way to circumvent CID check on this phone to flash MT4G's PD15IMG.
Since you're trying to annoy the very people you're asking for help, I'll leave you with that. Good luck.

Well i tried : p
Sent from my HTC Glacier using xda premium
---------- Post added at 08:20 AM ---------- Previous post was at 08:11 AM ----------
Ohh wait dosnt CID have to do with gold card?
Sent from my HTC Glacier using xda premium

gamingwiz said:
Ohh wait dosnt CID have to do with gold card?
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Ding ding ding. We have a winner…

what carrier did you get your phone from and which country? is this actually where did you download the PD15IMG.zip from exactly? (and i'm assuming that you do indeed have the PD15IMG.zip on the root of your sdcard when youre starting the bootloader) is this the stock rom version for your phone? are you able to get a fastboot connection via usb, and if so, have you tried to flash the rom via by renaming PD15IMG.zip to StockRom.zip and running these commands from the terminal.
./fastboot oem rebootRUU
./fastboot flash zip StockRom.zip
./fastboot reboot
are you even able to get an ./adb connection from the bootloader? if you can get either a fastboot or adb connection this can be fixed.

haxin said:
what carrier did you get your phone from and which country? is this actually where did you download the PD15IMG.zip from exactly? (and i'm assuming that you do indeed have the PD15IMG.zip on the root of your sdcard when youre starting the bootloader) is this the stock rom version for your phone? are you able to get a fastboot connection via usb, and if so, have you tried to flash the rom via by renaming PD15IMG.zip to StockRom.zip and running these commands from the terminal.
./fastboot oem rebootRUU
./fastboot flash zip StockRom.zip
./fastboot reboot
are you even able to get an ./adb connection from the bootloader? if you can get either a fastboot or adb connection this can be fixed.
Click to expand...
Click to collapse
Can't use fastboot unless he has the engineering bootloader.

estallings15 said:
Can't use fastboot unless he has the engineering bootloader.
Click to expand...
Click to collapse
im not sure where you got that idea but he most certainly can use fastboot. the OP even shows that he is able to set fastboot on the phone, im now wondering if he's able to get ./fastboot devices to see it on the computer.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
yorodan said:
Ok Mr obvious! you seem to be too cool to talk or give a solution, just looking for the "thank you" hits.
what a waste. Still couldn't find what you were referring to as " the very very basics". Plus your forum that you were too cool to mention its name didn't say anything regarding "CID not found update fail"
but thanks again, no bad feelings :angel:
Click to expand...
Click to collapse
you can check inside of the PD15IMG.zip archive and open a file named android-info.txt
it will have listed modelid:
cidnum:
mainver:
hbootpreupdate:
that will tell you the device that, that particular rom is intended for
cidnum will be T-MOB010 if its a tmobile

There is no adb from bootloader. Ever. In any phone.
Flashing PD15IMG through fastboot doesn't make any difference besides making him unable to exit fastboot RUU mode - because the same CID check will be applied.
Mytouch 4G is T-Mobile phone ONLY, and there is no other PD15IMG "in the wild" for any other CID.
There is another Glacier, and it doesn't have PD15IMG, it has RUU EXE (and PD15IMG for this phone can be extracted from this RUU - but it's a wasted step anyway).
---------- Post added at 02:27 PM ---------- Previous post was at 02:21 PM ----------
estallings15 said:
Can't use fastboot unless he has the engineering bootloader.
Click to expand...
Click to collapse
He can, but he won't be able to flash custom stuff with it (it'll fail signature check) - this is the difference between ENG and regular bootloader, ENG doesn't check signatures and allows flashing to various locked-by-default partitions like splash1.