Database Users

[HELP] Error change SPL

hey
I have an HTC Magic was trying to change and upgrade the terminal to 2.2.3, Ruu was run when it has not completed and now the mobile phone does not start and only have access to fastboot, adb does not detect the terminal.
Now it happens that I only have access to so fastboot and when I use the recovery, is in (boting. ..) and do not pass some time there.
32A SHIP S-ON H
HBOOT-1.76.0008 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009 15:56:29
Help please.
Sorry for my bad English.
Thks

Issue these commands from fastboot
Code:
fastboot getvar version-main
fastboot getvar cid
Depending on you answers, we can work our way through this.

mumilover said:
Issue these commands from fastboot
Code:
fastboot getvar version-main
fastboot getvar cid
Depending on you answers, we can work our way through this.
Click to expand...
Click to collapse
after executing the commands indicated, these were the results.
Code:
C:\androidsdk\tools>fastboot getvar version-main
version-main: 3.54.527.6
C:\androidsdk\tools>fastboot getvar cid
cid: HTC__506ñ»☻└

0verd0se said:
after executing the commands indicated, these were the results.
Code:
C:\androidsdk\tools>fastboot getvar version-main
version-main: 3.54.527.6
C:\androidsdk\tools>fastboot getvar cid
cid: HTC__506ñ»☻└
Click to expand...
Click to collapse
HTC__506 is for the users from Portugal.
3.54.527.6 is the Brazilian update for the 32A devices.
You should be able to flash it one more time using a goldcard.
Download the SAPPIMG.zip from this link:
http://www.htc.com/br/SupportDownload.aspx?p_id=272&cat=2&dl_id=1065
Put it on a sdcard.
Start in hboot mode (volume -(decrease) together with power) and the device should automatically flash the image.
Post here the results.
PS: if you are from Portugal, you should understand the instructions on the link :0)

H:\>fastboot getvar version-main
version-main: 3.54.631.3
finished. total time: 0.002s
H:\>fastboot getvar cid
cid: HTC__038☺
finished. total time: 0.001s
I have the same problem... can you help me

:S
MR mumilover
I did what I said and did not resolve.
After creating the goldencard and have copied the file to the root of SAPPIMG SD I turn off the terminal and he always stays with this RUU with the image of the beginning.
Thanks.

kkannan1982 said:
H:\>fastboot getvar version-main
version-main: 3.54.631.3
finished. total time: 0.002s
H:\>fastboot getvar cid
cid: HTC__038☺
finished. total time: 0.001s
I have the same problem... can you help me
Click to expand...
Click to collapse
Well almost the same..
HTC__038 is Indian users.
3.54.631.3 is Rogers 2,1 update.
Download this file and flash using a goldcard. Just as above..
https://rapidshare.com/files/2551144515/3.54.631.3Rogers.zip
Remember to rename to SAPPIMG.zip
Remember to hit that Thank-you button or donate :0)

0verd0se said:
MR mumilover
I did what I said and did not resolve.
After creating the goldencard and have copied the file to the root of SAPPIMG SD I turn off the terminal and he always stays with this RUU with the image of the beginning.
Click to expand...
Click to collapse
OK.. then we have a problem.
Run this command
Code:
fastboot oem h

mumilover said:
OK.. then we have a problem.
Run this command
Code:
fastboot oem h
Click to expand...
Click to collapse
C:\androidsdk\tools>fastboot oem h
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOtask
INFOenableqxdm
INFOrtask
OKAY

0verd0se said:
C:\androidsdk\tools>fastboot oem h
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOtask
INFOenableqxdm
INFOrtask
OKAY
Click to expand...
Click to collapse
This needs a chat session. Cannot be done over forum...
Check your pm.

Hi! I have the same problem on a HTC Magic 32A! Any solution?

Soft bricked MyTouch 1.2 any help appreciated

Hello all. I’m wondering if I could get any help with a semi-bricked Mytouch 3g 1.2.
I’ve seen this problem posted, but I haven’t been able to find any thread that had a clearcut solution so I thought I’d try to post asking for help. Like other’s on the board, I followed the rooting instructions on the Unlockr.com not knowing the link to the sappimg.zip was incorrect.
I am now stuck with the information below. I am able to get into fastboot, and the phone is recognized. I have tried to flash the “correct” sappimg file, but the phone will freeze when it is trying to unzip the system file. ADB devices command does not list the phone at all for some reason any longer.
I do have a working gold card. Any help at this point to try to get this phone working would be greatly appreciated.
Sapphire Unknown 32A Ship S-on H
HBoot: 1.33.0009 (Sapp31000)
CPLD: 13
Radio: 3.22.20.17
May 8, 2009, 21:02:32
Fasbtoot Devices: SH04KPB00691

Run these commands:
Code:
fastboot getvar version-main

mumilover said:
Run these commands:
Code:
fastboot getvar version main
Click to expand...
Click to collapse
Mumilover,
Thanks for the reply. I've entered the command string but all it's giving me is a list of fastboot commands.
if I enter "fastboot getvar version" it gives me version 0.5

Code:
fastboot getvar version-main
Forgot the "-" character... my bad :0)

mumilover said:
Code:
fastboot getvar version-main
Forgot the "-" character... my bad :0)
Click to expand...
Click to collapse
nah...np. you're the one that's helping me.
I feel like a moron, though. I should have been able to figure that out.
Version-main: 2.16.707.3
God knows what I've done trying to get this thing back up including trying to flash another sappimg & it freezing when it tries to unzip the system file.

Use this guide:
http://forum.xda-developers.com/showthread.php?t=734617

I've actually tried that. when I try to use a new sapping the phone freezes when unzipping. if I try to push the radio, I get a signature validation error.

Hmm... that's kinda bad... because you need that flash..
The reason why this is failing is because you have radio/spl from a 32A rom - 2.16.707.3 Singapore, Philippines
Try this command:
fastboot oem h

mumilover said:
Hmm... that's kinda bad... because you need that flash..
The reason why this is failing is because you have radio/spl from a 32A rom - 2.16.707.3 Singapore, Philippines
Try this command:
fastboot oem h
Click to expand...
Click to collapse
I'm getting the following following string
...
comandlist
keytest
heap
boot
reset
powerdown
rebootruu
task
rtask

Try to force a boot and see if you get adb access:
fastboot oem boot

i get a text string that looks like this then everything freezes:
C:\androidsdk\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA1200100 cmdline add=0x980728E0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x22800
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting.cid::T-MOB010
(bootloader) serial number: SH04KPB00691
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =337
(bootloader) active commandline: board_sapphire.disable_uart3=0 board_sap
(bootloader) phire.usb_h2w_sw=0 board_sapphire.disable_sdcard=0 smisize=3
(bootloader) 2 androidboot.baseband=3.22.20.17 androidboot.cid=T-MOB010
(bootloader) androidboot.carrier=TMUS androidboot.keycaps=qwerty androidb
(bootloader) oot.mode=normal androidboot.serialno=SH04KPB00691 androidboo
(bootloader) t.bootloader=1.33.0009 no_console_suspend=1 console=null
(bootloader) PARTITIOM_NUM_MAX =6 Valid partition num=6

i am able to adb device list
C:\androidsdk\tools>fastboot devices
SH04KPB00691 fastboot
C:\androidsdk\tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
033c208242410197 device
C:\androidsdk\tools>

Very good....
Don't touch it... i'll update here when i have time (very soon, preparing for defending my bachelor thesis, so kinda busy)

I'm ready.
When ever you have time try to catch me on gtalk or skype.
I'll pm you my info...

time difference is about 12 hours, i believe

I'm on now... just catch me...
it's 8 pm now in Denmark

pm'd info, also think I tried to add you via gtalk just now.

[SOLVED]SPL/Radio mismatch HTC Magic 32a

Hi!
I think my phone is bricked... or semi-bricked.
I was using eyegor's radio switcher to switch SPL/Radio/Recovery every time I was changed the rom. I used:
hboot-1.33.2010OldSPL.img
Radio_HTC_PVT_32A_3.22.20.17OldRadio.img
recovery-RA-magic+-v2.2.1-bladyle
everything was nice, but my battery started to die... every day I had to charge it. So I bought a new battery and I thought, it would be nice to be formatted with a stock rom. So I started to install RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe (what I installed the same way like before with success). When it got to update RADIO_V2 my screen goes black and the update failed.
Now when I try to turn the phone on (showing me the same with POWER; BACK+POWER; HOME+POWER; VOL_DOWN+POWER), says:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
I can access fastboot from computer, but adb not. I searched all over the internet to find solution to this.
Code:
fastboot oem boot
gives me in output:
Code:
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8F083CA4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x21401
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is VODAPC23
(bootloader) setting.cid::VODAPC23
(bootloader) serial number: HT95XKF02109
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =365
(bootloader) active commandline: board_sapphire.disable_uart3=0 board_sap
(bootloader) phire.usb_h2w_sw=0 board_sapphire.disable_sdcard=0 smisize=3
(bootloader) 2 androidboot.baseband=3.22.20.17 androidboot.cid=VODAPC23
(bootloader) androidboot.carrier=COMMON androidboot.mid=SAPP10000 android
(bootloader) boot.keycaps=qwerty androidboot.mode=normal androidboot.seri
(bootloader) alno=HT95XKF02109 androidboot.bootloader=1.76.0008 no_consol
(bootloader) e_suspend=1 console=null
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) 69466957
(bootloader) 69784520
(bootloader) 7473
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
FAILED (status read failed (Too many links))
finished. total time: 8.454s
after 2-3 minutes brings up the old rom, but at the beginning force closes and restarts
I tried to install other ruu-s but with no success. I created a goldcard, tried to flash sappimg.zip from RUU_Sapphire_HTC_Europe_2.16.401.6_Vodafone_CZ_release_signed_NoDriver.exe but it fails at the very beginning with "43 main version check fail".
mumilover's fastboot commander's output:
Code:
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.76.0008
finished. total time: 0.002s
********************************
###Calling fastboot with: getvar version-baseband###
version-baseband: 3.22.20.17
finished. total time: 0.004s
********************************
###Calling fastboot with: getvar version-main###
version-main: 3.05.401.1
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar cid###
cid: VODAPC23âSÐ
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar version-cpld###
version-cpld: 12
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP10000
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar security###
security: on
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: SHIP
finished. total time: 0.001s
********************************
I saw mumilover helped to someone with almost the same problem, maybe he or someone can help me.

So it can't be solved...
If someone in Serbia can JTAG, I would be send to him/her and pay for it...

Don't know why I was thinking like a noob... a had already extracted the RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe and I always tried to flash only the rom.zip which failed at radio update. So now I tried to flash the other zip... rom1.zip
Now I have working hboot, fastboot and a system which I cant access

It looks like no one can help me...
I tried to make a goldcard, with two cards. The first was 4gb Kingston sdcard and the second one is a noname 512mb sdcard. Without my goldcards I get Model ID error. With the goldcard inserted (never mind which one) I pass this check, but fails at main version check. I read on many forums and tutorials how to make a goldcard... On these sites I found many answers. Someone says the goldcard is good when passes the Model ID check. But there are a few responds where they say they can pass the main version check... Somewhere on this forum with almost the same problem (SPL/Radio mismatch) someone wrote that he had to make three goldcards to pass the main version check, but with first two he passed only the Model ID check...
Now I'm a little bit confused... I would appreciate if someone can confirm that the goldcard is then a good goldcard when it can pass the main version check (in RUU - ERROR 140 - BOOTLOADER VERSION ERROR).
If someone confirms this I will buy more sdcard (because I bought my phone without a sdcard (for those sdcards which comes with the phone everyone says these are good for creating a goldcard (said on the forums)) before two years)...

... and sorry for my really bad english

more than 140 views and no one replied...
wondering...
if XTC Clip can help me?

I wrote you a pm.
"Main version is older" is not something which a goldcard can fix...
But we can fix that :0)
We just need to get into the system, flash a different misc partition and you should be able to flash a different ruu file.
Once we have a matching spl/radio combo, we can flash a different combo matching your device (32A).

I have to say... many thanks to mumilover, because he wanted to help me. I told him in Monday that I ordered a XTC Clip by Raskal and I want to try it first... Today I got the Clip and successfully unlocked it... it said S-OFF and showed in fastboot:
before:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.0008 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
after:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.0008 (SAPP*****)
CPLD-12
RADIO-3.22.20.17
downloaded the original ROM, which was for me RUU_Sapphire_HTC_Europe_2.16.401.6_Vodafone_CZ_release_signed_NoDriver because of my phone was VODAPC23... now in fastboot with command:
fastboot oem boot
it gives me "CID is super CID" and "setting.cid::11111111"
when the unlock succeeded I type in cmd:
fastboot oem rebootRUU
unpacked, the downloaded RUU and installed the "update"(downgrade):
fastboot flash zip rom.zip
everything went well! So now my phone works like new, but it is unlocked If someone will have same problem I suggest to buy a XTC Clip from Raskal...

Anyway, how can I make it solved?

How did you do it?
I have the same issue. My phone is stuck in ruu mode. I have an xtc clip but when I try it, it does nothing. I assume its because the phone is still stuck in ruu mode but how do I get it out of ruu mode?
Can you help me?
SPL and Radio are exactly as above.
Thanks.

Here is my exact device info.
...........................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.76.0008.
Radio version: 3.22.20.17.
Main software version: 3.05.401.1.
cid: roger001.
cpld: 12.
product: sapphire.
mid: sapp50000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.

To get into fastboot/hboot and get rid of ruu screen:
1.a. Download RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe and extract it.
Find rom.zip and rom1.zip files
1.b. Or download rom.zip and rom1.zip
2. Put these zip files in the same folder where is fastboot.exe
3. Connect your phone to PC in RUU mode
4. Run the commands from the same directory:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip
This will fail. Disconnect the phone, get the battery out for 10secs, put back and connect to PC.
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom1.zip
This will be successfully installed. And now you have fastboot/hboot. In XTC Clip make the goldcard. Put the card in the phone and power on with VOLUME_DOWN+POWER.

jeBACH said:
To get into fastboot/hboot and get rid of ruu screen:
1.a. Download RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe and extract it.
Find rom.zip and rom1.zip files
1.b. Or download rom.zip and rom1.zip
2. Put these zip files in the same folder where is fastboot.exe
3. Connect your phone to PC in RUU mode
4. Run the commands from the same directory:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip
This will fail. Disconnect the phone, get the battery out for 10secs, put back and connect to PC.
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom1.zip
This will be successfully installed. And now you have fastboot/hboot. In XTC Clip make the goldcard. Put the card in the phone and power on with VOLUME_DOWN+POWER.
Click to expand...
Click to collapse
Thanks.
I figured this out last night but thanks anyway.
Just to add, to get back to a bootable system, I had to flash another rom after completing the above steps.

Is there a way to get the Tom and rom1 rehosted? If not where can i get it from?

tlipur said:
Is there a way to get the Tom and rom1 rehosted? If not where can i get it from?
Click to expand...
Click to collapse
You can get the ROM from HTC Dev. You need to sign up for an HTC Dev account and then go to the HTC bootunlocker page (you have to google as I'm not allowed to post the link). You can download the RUU there and then once downloaded open the file and when its open go to %temp% (or your temp file directory) and find the most recent modified folder. Inside of there you will find another folder which will contain, amongst other things rom[1].zip file(s).

rom.zip
rom1.zip

Awesome thanks
Sent from my GT-P7510 using Tapatalk 2

fastboot remote: not allow and stuck on RUU mode screen

ok i dont know but my phone has no recovery and does not boot
and i tried the sappimg.zip it hangs on radio when i tried
mytouch 3g 3.5mm fender
THIS IS WHAT IT SAY IN HBOOT:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-6.35.16.19
mismatch spl/radio i know
when i try to this command: fastboot flash (e.g hboot,recovery,and radio) file.
i get the same message
FAILED (remote: not allow)

Download an apropriate RUU and flash it through fastboot.
Fastboot command: fastboot oem rebootRUU
Then run the RUU from PC.
Hope this solves your problem.

alex6vasy said:
Download an apropriate RUU and flash it through fastboot.
Fastboot command: fastboot oem rebootRUU
Then run the RUU from PC.
Hope this solves your problem.
Click to expand...
Click to collapse
okay i tried all 3 ruu from this ruu thread http://forum.xda-developers.com/showthread.php?t=659403 for T-Mobile myTouch 3G 1.2
i tried fastboot oem rebootruu and it goes in ruu usb
they all said error usb connection error
but its plug and this is for
2.10.531.3 T-Mobile USA DRD35
2.10.531.4 T-Mobile USA DRD35
but 1.94.531.1 T-Mobile USA DMD64 loads but at the end it says
find the correct phone version idk help pls

This issue has been answered before by me... it's kinda complicated and requires some thinking... do a search with my name and you shall find the answer and all the necessary files/instructions.
Good luck hunting.

i looked thru all your post but still nothing if u could link me or point me somewhere lol

Download my fastboot commander and provide here ALL device info.

ok i tried fast oem boot and got this
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x98070CA0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x22800
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) radio_flash_id=0x5510BCAD
(bootloader) die_size=0x1
(bootloader) radio_flash_id=0x5510BCAD
(bootloader) die_size=0x1
(bootloader) TAG:die_size = 0x1
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting.cid::T-MOB010
(bootloader) serial number: HT043PB03144
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =337
(bootloader) active commandline: board_sapphire.disable_uart3=0 board_sap
(bootloader) phire.usb_h2w_sw=0 board_sapphire.disable_sdcard=0 smisize=3
(bootloader) 2 androidboot.baseband=6.35.16.19 androidboot.cid=T-MOB010
(bootloader) androidboot.carrier=TMUS androidboot.keycaps=qwerty androidb
(bootloader) oot.mode=normal androidboot.serialno=HT043PB03144 androidboo
(bootloader) t.bootloader=1.33.0013 no_console_suspend=1 console=null
(bootloader) PARTITIOM_NUM_MAX =6 Valid partition num=6
i download your FBCOMMANDO and it wont detect my phone on fast boot this is what i got when i check connection and print device info
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
No fastboot device connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
i think it wont detect because i dont have a eng spl or s-off
So now i have a new problem omg lol
it wont boot to hboot anymore
it goes to ruu screen with the mirco-chip crossed out
on every boot or everytime i turn it on

now its stuck on RUU mode
so i cant use adb
no hboot so i cant use a gold card
so i have to flash from the computer (fastboot flash zip sappimg.zip)
only ruu that work is RUU_Sapphire_T-Mobile_US_2.10.531.4
but hangs on radio

-----------------------------------.
HT043PB03144 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.0013.
Radio version: 6.35.16.19.
Main software version: 2.10.531.4.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.

I have same problem too
LBOG_Kush said:
-----------------------------------.
HT043PB03144 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.0013.
Radio version: 6.35.16.19.
Main software version: 2.10.531.4.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Click to expand...
Click to collapse
I have the same problem too and i try the same way to get out of Stuck RUU USB Screen and still no luck
here my celphone info too:
-----------------------------------.
HT02BPB02502 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.76.0007.
Radio version: 6.35.07.29.
Main software version: 3.57.0.0.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
I think i need JTAG to fix that problem.

i have the same problem
here is my device information:
***UNLOCKED***
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0013(SAPP 10000)
CPLD-12
RADIO-3.22.20.17
my phone is stuck on vodafone logo and keep restart the
any help to fix it ???

over 1000 posts by you xD
mumilover said:
This issue has been answered before by me... it's kinda complicated and requires some thinking... do a search with my name and you shall find the answer and all the necessary files/instructions.
Good luck hunting.
Click to expand...
Click to collapse
I've looked through a good 90% of your over 1000 posts, can you please pm me the link for the solution? I also seem to have this problem (and I tried fastboot oem rebootRUU and all the ruu updaers, I get an error and it drops the program xD
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
fastboot commander says this (as does the phone when I hold vol down and power)
pressing the home key and power key (and holding) does nothing but freezes at a green mytouch 3g splash logo...
holding vol down and power gives me access to hboot ,
hboot says press back to go to fastboot
fastboot is useless as s-on
I don't have a recovery at all, I guess I don't have a rom at all either, I would think it was a brick, if I couldn't get to hboot and fastboot... wait, IS this a brick?
SPL/hboot version: 1.33.0013.
Radio version: 6.35.16.19.
Main software version: 3.57.0.0.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.

as a curiosity, what type of devices do you have?? 32A or 32B?

george.wgx said:
as a curiosity, what type of devices do you have?? 32A or 32B?
Click to expand...
Click to collapse
Looks like the T-MOB010 cid was used for 32B's and Fender/1.2's. In any case, unless I'm very mistaken, this is a radio mismatch.
Thomas1031, does your phone have a headphone jack?

[Q] HELP: adb,ruu,bootloader,fastboot freeze stuck

Hi guys,
I've searched all over the internet and offcourse XDA but I don't know what to do anymore.
Somehow my HTC Desire Z frooze a few weeks back, and after pulling the battery the phone was stuck at the HTC screen. I tried factory reset,recovery etc but that all didn't work. The phone just freezes.
The phone is NOT rooted, unlocked etc. No apps where installed before the phone froze.
Some information:
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
"fastboot getvar all" output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.4
(bootloader) serialno: SH0B9RT0****
(bootloader) imei: ****************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
1. Downloaded this RUU which i'm sure it's correct.
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
2. Drivers are installed and recognized (fastboot and bootloader) on Windows 7 x64 and Windows XP Home Edition. (have 2 PC's just in case)
3. I have installed the latest Android SDK.
4. I have installed HTC Sync. (messed around with drivers from Google and HTC)(believe me I know what i'm doing so it can't be because of the drivers)
5. I don't have or need a goldcard.
6. ADB is recognized by Windows but shows
Code:
error: device not found
7. Fastboot lists my device as "fastboot devices"
Code:
SH0B9RT0**** fastboot
8. When in HBOOT I can manually switch back and forth between fastboot and bootloader, but when selecting "reboot bootloader" from the fastboot menu the phone immediatly freezes again.
9. When the RUU reboots the bootloader the phone freezes.
10. When the RUU says "waiting for bootloader", and I manually power on the phone to HBOOT (seen as "Android Bootloader Interface" by Windows) the phone still isn't recognized.
11. Also tried updating the device list for ADB from the command line "androind update adb" - no result
12. Manually add the device ID "0BB4" to "adb_usb.ini" - still not seen by ADB.
I really believe I tried everything google threw at me. Can my bootloader be corrupted somehow? Any suggestions?
--------------------
UPDATE:
I extracted the ROM.zip from the RUU, renamed it to PC10IMG.zip and placed it in the root of my SD card. Booted up the phone in HBOOT and it automaticly started the update process. At this point it is once again stuck at the bootloader.
At this point I think the eMMC chip is dead.
Code:
[COLOR="Blue"]HBOOT[/COLOR]
[COLOR="Green"]Parsing PC10IMG.zip [SD ZIP]
[1] BOOTLOADER [COLOR="Magenta"]- Updating[/COLOR]
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] RADIO_V2
[11] RADIO_CUST[/COLOR]
[COLOR="Blue"]Do you want to start update?[/COLOR]
[COLOR="Red"]<VOL UP> Yes
<VOL DOWN> No[/COLOR]
[COLOR="Blue"]Update is in progress...[/COLOR]
[COLOR="Red"]Do not power off the device![/COLOR]

I have the same issue with a TMOUS G2
tried all the steps like you
also tried flashing just the hboot first and also the whole rom through ADB in fastboot but i get a weird error that the command was incorrect by 1byte or something like that
did you ever get anywhere with your phone?

You've probably got a fried emmc, which is a hardware issue.
if it is that, there is nothing you can do about it, except get a warranty replacement (if its still under warranty)
Being unrooted and S-ON limits anything you can do even if the emmc isn't fried.
-Nipqer

Nipqer said:
You've probably got a fried emmc, which is a hardware issue.
if it is that, there is nothing you can do about it, except get a warranty replacement (if its still under warranty)
Being unrooted and S-ON limits anything you can do even if the emmc isn't fried.
-Nipqer
Click to expand...
Click to collapse
yup :/
it was even a pain in the ass to try to do the PC10 method because all zips I found from the gude to restore to stock were too old.. fortunately I was able to extract the rom from the update from a few weeks ago and that would have worked, but as you say, I think my emmc is hosed
wish there was a tool like on the evo where you purposely 'hardbrick' the phone but can flash/repartition the bootloader in ubuntu