Database Users

Probs with getting into recovery menu

Hey XDA
Im having a little problem with my Magic.
I would like to flash a new ROM, but i cant get into the recovery menu.
Here is what i do:
I have installed the latest version of SDK on my computer.
I then connect my Magic with the cable, and when Vista comes up with the note saying that want to install the software i tell it to use the drivers that are in the SDK/usb_driver/x86 folder.
I then turn off the phone, and press and hold back button + power button until the phone shows the "3 androids on skateboard" menu.
Then on my computer in the cmd prompt i write: fastboot boot recovery.img, and the the cmd prompt says: <waiting for device> and the nothing else happens, the recovery image dosn't show up on the phone either.
I have checked with adb devices that my phone is connected.
Are there anyone that can help me with this problem because its beginning to annoy me alot, i would like to root my phone and flash another ROM.
So any help would be much appreciated.
Per

Just to check, you made sure you have a spl that's rootable?
http://forum.xda-developers.com/showthread.php?t=529019
And fallowed this before fastboot.
First, setting up your PC (I'm going to assume you're using windows for this) to work with Android in a debugging enviroment.
1. Get the latest Android SDK from here (http://developer.android.com/sdk/1.5_r2/index.html) and unzip it into a convienent directory (most people use C:\Android\, so I suggest you do the same). The result should be something along the lines of C:\Android\android-sdk-windows-1.5_r2\.
2. Set up your phone to work with debugging drivers. The method of doing so can be found here (http://developer.android.com/guide/...ing/device.html) in the "Setting up a Device for Development" section, steps 2 and 3. To test that it works properly, open up a command prompt and navigate to the tools directory (C:\Android\android-sdk-windows-1.5_r2\tools). Type into the prompt:
Code:
adb devices
If it returns your device and serial number, then you're all set.
3. Lastly, grab fastboot.exe from here (http://www.htc.com/www/support/android/adp.html) and place it in the tools directory of the sdk.
Next up, rooting.
Clinton

Thx for the answer, but there is a problem with one of the links you posted, the last one of them (http://developer.android.com/guide/...ing/device.html). it dosn't work.
But you also write something about the SPL, i dont know if i have the right SPL, how can I see if its the right one i have? I've tried reading the link about the SPL, but my problem is that i cant even get into the recovery menu, so i cant flash a new SPL either, or am i wrong?
Please help me
Per

To check your SPL just boot up fastboot (back + power) then just look at the top and see what it says. Then check on the first link I posted and see if your SPL is rootable or not.
Don't know why the last link didn't post proper Here it is.
Clinton

perevers said:
Hey XDA
Im having a little problem with my Magic.
I would like to flash a new ROM, but i cant get into the recovery menu.
Here is what i do:
I have installed the latest version of SDK on my computer.
I then connect my Magic with the cable, and when Vista comes up with the note saying that want to install the software i tell it to use the drivers that are in the SDK/usb_driver/x86 folder.
I then turn off the phone, and press and hold back button + power button until the phone shows the "3 androids on skateboard" menu.
Then on my computer in the cmd prompt i write: fastboot boot recovery.img, and the the cmd prompt says: <waiting for device> and the nothing else happens, the recovery image dosn't show up on the phone either.
I have checked with adb devices that my phone is connected.
Are there anyone that can help me with this problem because its beginning to annoy me alot, i would like to root my phone and flash another ROM.
So any help would be much appreciated.
Per
Click to expand...
Click to collapse
Sound like you're not using the right Recovery .img
Check here to start with: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03

ClintonH said:
To check your SPL just boot up fastboot (back + power) then just look at the top and see what it says. Then check on the first link I posted and see if your SPL is rootable or not.
Don't know why the last link didn't post proper Here it is.
Clinton
Click to expand...
Click to collapse
I have the: SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
If what im reading at the first link is correct, my SPL cant be root'et, or im not reading the first link correctly?
And if i need a new SPL, how do i flash that one? and what SPL should i choose? and last, how can i then get my SPL back to how it is now if i need to get the phone to repair?
Per
antonram said:
Sound like you're not using the right Recovery .img
Check here to start with: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
Click to expand...
Click to collapse
I am using the right recovery image, i also tried the one you linked, that didn't work either
Per

perevers said:
I have the: SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
If what im reading at the first link is correct, my SPL cant be root'et, or im not reading the first link correctly?
Per
Click to expand...
Click to collapse
Afraid your not going to be able to root right now. It's in the works though so it might be soon.
Clinton

ClintonH said:
Afraid your not going to be able to root right now. It's in the works though so it might be soon.
Clinton
Click to expand...
Click to collapse
Damn, thats a load of ..... (sorry).
I have just got my phone back from the repair shop because the camera restarted the phone everytime i tried to use it. Before i sent it to repair i had no problem rooting it or getting in the recovery menu.
But can you tell what the problem is? is it because the recovery image dosn't work with my SPl and the recovery image guys need to "crack" my SPL first or what?
Per

perevers said:
Damn, thats a load of ..... (sorry).
I have just got my phone back from the repair shop because the camera restarted the phone everytime i tried to use it. Before i sent it to repair i had no problem rooting it or getting in the recovery menu.
But can you tell what the problem is? is it because the recovery image dosn't work with my SPl and the recovery image guys need to "crack" my SPL first or what?
Per
Click to expand...
Click to collapse
Here you go read This on the SPL. By the way which phone do you have? Is it a Rogers Magic? Just good to know what's not rootable, you should post your phone details in that thread if it's something not listed on the first page.
Clinton

ClintonH said:
Here you go read This on the SPL. By the way which phone do you have? Is it a Rogers Magic? Just good to know what's not rootable, you should post your phone details in that thread if it's something not listed on the first page.
Clinton
Click to expand...
Click to collapse
Its a HTC branded magic, dont know if its a rogers. But im from Denmark, and bought it in Denmark. dont know if that helps.
Thx for the help, will read the thread.
Btw. can you tell where i can see how far they are in "cracking" this SPL?
Per

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] Help with recovering from brick

I guess I'm pretty much SOL, but want some suggestions. Here's my situation:
G2 with
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010,17:59:38
-Won't boot past the white and green HTC screen both on normal boot and boot into Recovery.
- Can't get adb to see the device.
- Fastboot works.
Tried:
- A few PC10IMG.zip, G2 sees it, checks it out, but won't flash it. If there is a PC10IMG.zip that you feel will help, please let me know.
- fastboot flash recovery doesn't work with error saying: FAILED (remote: signature verify fail).
- fastboot boot <recovery>.image fails with error: FAILED (remote: not allowed).
- fastboot update doesn't work either.
Any ideas?

asunp said:
I guess I'm pretty much SOL, but want some suggestions. Here's my situation:
G2 with
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010,17:59:38
-Won't boot past the white and green HTC screen both on normal boot and boot into Recovery.
- Can't get adb to see the device.
- Fastboot works.
Tried:
- A few PC10IMG.zip, G2 sees it, checks it out, but won't flash it. If there is a PC10IMG.zip that you feel will help, please let me know.
- fastboot flash recovery doesn't work with error saying: FAILED (remote: signature verify fail).
- fastboot boot <recovery>.image fails with error: FAILED (remote: not allowed).
- fastboot update doesn't work either.
Any ideas?
Click to expand...
Click to collapse
Try this one. Rename it to pc10img.zip and place it on your sd card.
http://www.mediafire.com/?53371ev99qfk855

Thanks, I'll try that one. Is that the latest stock ROM? Is it rooted?

asunp said:
Thanks, I'll try that one. Is that the latest stock ROM? Is it rooted?
Click to expand...
Click to collapse
No, its not rooted. You can read more about it here:
http://forum.xda-developers.com/showthread.php?t=1074391
edit: I don't think it can be rooted at this time either, but I may be wrong.

I haven't read the whole thread, but will it be tough to root from this stock ROM? Ehm, probably I should not get my hopes up too soon.
Edit:
Too bad, the G2 complains about "Lack of heap" for this PC10IMG.zip. Thanks for the suggestion though.

asunp said:
I haven't read the whole thread, but will it be tough to root from this stock ROM? Ehm, probably I should not get my hopes up too soon.
Edit:
Too bad, the G2 complains about "Lack of heap" for this PC10IMG.zip. Thanks for the suggestion though.
Click to expand...
Click to collapse
Give this one a try:
http://www.mediafire.com/?kcugvobjewkj63a
you can read more about it here:
http://forum.xda-developers.com/showthread.php?t=912399

Thanks, but still no luck. It checks out the PC10IMG.zip with progress bar, then "Checking.." and goes back to HBOOT page without flashing anything.

So this is probably the closest I got to unbricking, but still no dice. I use this PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip as PC10IMG.zip and the phone actually says "Main version is older" and refuses to flash.
Will it be possible to use a hex editor and edit the version number to trick the G2 to flash that ROM?

asunp said:
Thanks, but still no luck. It checks out the PC10IMG.zip with progress bar, then "Checking.." and goes back to HBOOT page without flashing anything.
Click to expand...
Click to collapse
After it checks the pc10img.zip you don't get any prompt at all to update, such as volume bar up to update and volume bar down to cancel?

EdKeys said:
After it checks the pc10img.zip you don't get any prompt at all to update, such as volume bar up to update and volume bar down to cancel?
Click to expand...
Click to collapse
Nope, it just went back to the HBOOT page. However, with the other PC10IMG.zip file I mentioned, it actually says that the "main version is older" and hence not flashing. I'm thinking if I can just edit the version in android-version.txt, then maybe that will trick the G2 to flash? Is there any other place/file where version check is done?

After you put the pc10img.zip on the sd card and you reboot into bootloader, press the power bar one time and there should be a progress bar on the right side that does a check. After that, don't do anything, just report here what is says on the phone display.

Here's the result so far:
1. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=1074391
PC10IMG_Vision_Gingerbread_S_TMOUS_2.13.531.8_Radio_12.52.60.25_26.08.04.30_M3_release_188635_signed.zip
No blue bar, error saying "Lack of heap" during Loading...[PC10IMG.zip]
2. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=912399
There is a blue bar progress. After the bar is all blue, phone proceeds to "Checking...[PC10IMG.zip]" and then it simply jumped back to HBOOT/bootloader page with Fastboot, Recovery, etc options. No error message or any option whatsoever.
3. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=835971
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
Blue bar progress. After bar is all blue, phone proceeds to "Checking..[PC10IMG.zip]". Then error message saying:
Main Version is older!
Update Fail!
Press <POWER> to reboot.
That's why I thought maybe by hacking the version in the 3rd PC10IMG.zip might trick the phone to flash the PC10IMG.zip.

asunp said:
Here's the result so far:
1. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=1074391
No blue bar, error saying "Lack of heap" during Loading...[PC10IMG.zip]
2. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=912399
There is a blue bar progress. After the bar is all blue, phone proceeds to "Checking...[PC10IMG.zip]" and then it simply jumped back to HBOOT/bootloader page with Fastboot, Recovery, etc options. No error message or any option whatsoever.
3. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=835971
Blue bar progress. After bar is all blue, phone proceeds to "Checking..[PC10IMG.zip]". Then error message saying:
Main Version is older!
Update Fail!
Press <POWER> to reboot.
That's why I thought maybe by hacking the version in the 3rd PC10IMG.zip might trick the phone to flash the PC10IMG.zip.
Click to expand...
Click to collapse
Well, that might be your only option left... good luck with it. I can't think of anything more except to wait it out for others to jump in here with possible solutions.

asunp said:
Here's the result so far:
1. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=1074391
PC10IMG_Vision_Gingerbread_S_TMOUS_2.13.531.8_Radio_12.52.60.25_26.08.04.30_M3_release_188635_signed.zip
No blue bar, error saying "Lack of heap" during Loading...[PC10IMG.zip]
2. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=912399
There is a blue bar progress. After the bar is all blue, phone proceeds to "Checking...[PC10IMG.zip]" and then it simply jumped back to HBOOT/bootloader page with Fastboot, Recovery, etc options. No error message or any option whatsoever.
3. PC10IMG.zip from this thread http://forum.xda-developers.com/showthread.php?t=835971
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
Blue bar progress. After bar is all blue, phone proceeds to "Checking..[PC10IMG.zip]". Then error message saying:
Main Version is older!
Update Fail!
Press <POWER> to reboot.
That's why I thought maybe by hacking the version in the 3rd PC10IMG.zip might trick the phone to flash the PC10IMG.zip.
Click to expand...
Click to collapse
You could mod the stock images, but you would have to sign it with HTC's signature. Maybe a goldcard will fix this?
If I follow this correctly, the main version is older error is because you are trying to flash an older ROM on top of an new one. You are also using the stock, S-ON, non-engineering bootloader so you get stuck at the signature checks.
Maybe you might get lucky...
http://forum.xda-developers.com/showthread.php?t=842495

If you can boot into the system, or a custom recovery, it is possible to change the version values, using the misc_version tool from the wiki.
Otherwise, you could try flash the 2nd PC10IMG via fastboot.
-Nipqer

Unfortunately, I can't boot into the system. I can only get the bootloader and fastboot. Both recovery and normal boot give me the HTC splash screen and stuck there. Thus I cannot use adb at all
I guess I'll look more into the gold card method. I've never tried a gold card before. Is there a good tutorial on this? Thanks for all the suggestions.

Don't rule out adb until you try it. Even if it's stuck on the splash screen, you might be able to use adb shell.
I'm not 100% sure the gold card will work, but it's worth a shot. You can search for it on xda- other phones relied on it more for rooting than the g2.

Well, after checking the PC10IMG.zip that I've used, I still have some questions.
From my understanding, the second PC10IMG.zip won't work because it's not signed. It is a homebrew with clockwork recovery, original 1.12 ROM and .76 HBOOT. That's probably why the phone just returns back to G2 HBOOT screen after checking the PC10IMG.zip
The problem with third PC10IMG.zip is simply that it's too old and G2 refuses to flash it.
My question is why the first PC10IMG.zip not flashing? It is the latest OTA from T-MO, signed and sealed All I get is "Lack of heap" error when the HBOOT found the PC10IMG.zip

You might be onto something...
The unofficial leaked version is 2.13.531.8, but the official GB update is higher - 2.15.531.3.
It's out here somwhere- let me fire up the ol' search engine.
---------- Post added at 11:02 PM ---------- Previous post was at 10:48 PM ----------
Try the ROM in this thread.
http://forum.xda-developers.com/showthread.php?t=1210835
It's version is 2.15.531.8, so it should be higher than any T-MO ROM out there.
If you still get the lack of heap error, than try a gold card.
Good luck!
Edit: to be clear, the first ROM you flashed is the leaked version - 2.13.531.3.

Goldcard will not help, a goldcard only lets you bypass CID errors.
I've only seen lack of heap when someone tried to flash a DZ PC10IMG to a G2, so make sure you have a proper one.
You can try flash it from fastboot.
1. get to fastboot (hold down trackpad when powering up, or select fastboot from hboot menu)
2. in cmd 'fastboot devices' to make sure it works (from tools or platform-tools if you havn't set Path variable)
3. fastboot oem rebootRUU (this will get you to a black screen with silver HTC logo)
4. fastboot flash zip PC10IMG.zip
If it stops and says "FAILED: Repeat Immediatly" just redo the fastboot flash zip command.
-Nipqer

I need some serious help. This man's phone might be bricked.

I know. What you want to tell me is to search the forum. What you want to tell me is to go on somewhere and stop being a noob. I know, because I have felt the same before. But please, stop for a second and read this.
I have a T-Mobile G2 aka Desire Z. I have no idea what has been done to it because a friend gave it to me for the sole purpose of attempting to fix it. I accepted the phone as a challenge.
When turned on, all I get is the white screen with a green HTC logo. It boots into HBOOT when I hold the volume down key, and from HBOOT I am able to go to recovery. Here is exactly what it says when I boot to HBOOT:
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE SRC
When I try doing a factory reset from this screen, it'll go to the loading screen that has a green exclamation mark with arrows around it for a few seconds, then reboot; again going to the HTC logo.
When I go to recovery from the HBOOT screen, it goes straight to the screen with a red exclamation point. When it is at the red exclamation point screen, I can connect it to my computer and use adb, but it says that it is offline, even though it shows the phones serial number.
I tried flashing the stock ROM via fastboot, but it did not work. I will greatly appreciate any help i could get.
If you know of any threads on the same issue that I may have overlooked, please let me know.
Thanks :good:

i am very sleepy right now so i cant fully help, BUT, to shine some light for you, the phone is not bricked. its only bricked when you cannot even turn on the phone, or usb cant even connect to it.

when the phone's hboot is "SHIP" instead of "ENG" then you can't do fastboot and the only way you'll be able to apply anything would be via the PC10IMG.zip method from the SD card.
Adb doesn't work in fastboot/hboot mode, and if you have no rom with adbd launched on it it won't connect there either.
With the phone in S-ON method you won't be able to downgrade to a older firmware than the one currently installed (and may need a gold card to bypass the CID check).
Also a Bricked phone is one that:
1) Doesn't turn on
2) Can't get into bootloader
3) Can't get into recovery
If you can get into the bootloader you have a chance, an RUU update might be the way to go, but I am not 100% sure on exactly which image should be obtained (maybe wait a day and see if you get more helpful response).

Sweet! Just the fact that I now know it isn't bricked gives me a new hope! Lol.
One thing I forgot to mention is that I downloaded a supposed "stock" PC10IMG.zip and put it on the sd card via an adapter, but when I boot to HBOOT, when it checks the sd, it claims that there is no PC10IMG.zip on there..confuses me...
Also, when i go into Android system recovery, i get the following error:
E:Can't open /cache/recovery/command
Again. Any help will be appreciated.

although it may not be "bricked" you are showing signs of a failled emmc. if you can get adb access you can check which chip you have. just search the thread for "fried emmc" and you'll find multiple threads on this as well as a a way to check what chip you have in the phone (as one chip is proned to curroption)
Sent from my HTC Vision using xda premium

demkantor said:
although it may not be "bricked" you are showing signs of a failled emmc. if you can get adb access you can check which chip you have. just search the thread for "fried emmc" and you'll find multiple threads on this as well as a a way to check what chip you have in the phone (as one chip is proned to curroption)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Or click the emmc link in my sig, there's been some postings in that poll thread on various ways to check.

demkantor said:
although it may not be "bricked" you are showing signs of a failled emmc. if you can get adb access you can check which chip you have. just search the thread for "fried emmc" and you'll find multiple threads on this as well as a a way to check what chip you have in the phone (as one chip is proned to curroption)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
kbeezie said:
Or click the emmc link in my sig, there's been some postings in that poll thread on various ways to check.
Click to expand...
Click to collapse
I thought that might have been a possibility. I had read a lot about failed chips, and had hoped it wasn't the problem.
All the methods of finding the chip serial number require ADB. This doesn't help me much because when I try doing anything via ADB, it gives me the following error:
error: device offline
Another thing worth mentioning is that it either isn't finding the SD card or it isn't reading it correctly.
when I first boot to HBOOT, it scans the SD card and says this:
SD Checking...
Loading...[PC10DIAG.zip]
No image!
Loading...[PC10GIAG.nbh]
No image!
Loading...[PC10IMG.zip]
No image!
Loading...[PC10IMG.nbh]
No image or wrong image!
This is weird, because I downloaded a stock PC10IMG.zip, and put it on the SD card.
Crap...I think I may have already mentioned that ^ lol.

well did you name in pc10img.zip or pc10.img.zip.zip (windows may put file extentions in there for you)
also is it on the root of your sd card (not in any folders)
and sd is properly formatted? (fat32)
it is very possible that the sd card slot is damaged, problem is without a working phone it is hard to check it
Sent from my HTC Vision using xda premium

Did you also make sure to put the PC10IMG.zip file at the root of your sdcard?

Run the ruu
Sent from my Energized Amaze 4G
Yes girls know about XDA
you can thank a girl on here

You might want to try to see if you have a faulty SD card first.
The same thing happened to my G2 while I was at the middle of rooting/flashing it and I thought I've done something wrong and bricked the phone.
At the end, it turned out to be a corrupted microSD card that was causing all the problem.
Try rescue it with another SD card first.