HTC jetstream QHSUSB_Dload

[mazmaz1]

Hello
I have a HTC Jetstream with qhsusb_dload state
I jtag it with Riff box and resurrect it,without any change after successful resurrection whit generic resurrection and repairing kernel and htc section repairing too.
Is full dump writing solve this prob?
Any one have any address for full dump file for this model?
this is log of resurrection

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [HTC JetStream (PG0941000) V1.0.4816.55337]

Connecting to the dead body...OK
Detected dead body ID: 0x106A10E1 - CORRECT!
Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0045/0x0100 (SEM32G, 0x00076E000000 Bytes = 29.72 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0045/0x0100 (SEM32G, 0x000000100000 Bytes = 1.00 MB)

Flashing the dead body...OK
Resurrection complete!

[mazmaz1]

Any one dosn't have answer?!

[mazmaz1]

Dear supporter
please share your direction
Is this file available on your server?

[saleem5001]

u r ressurection complete now whats condition and check try to send it into fast boot mode

means check its bootloader mode

and post now its present condition

[mazmaz1]

it doesnt go to fast boot mode with vol- and power key
only qhsusb_dload mode in usb connection

[BABAK NURI]

Hi
Do you know about phone history...? because if phone damaged suddenly,this is HW problem for sure
but if your phone damaged by wrong FW,Maybe dump file can help...

I don't have personaly dump file for this model,but please contact me via ICQ,,,May i can help you for extract stock ruu then inject to phone by eMMC Plugin

Thanks

[mazmaz1]

Hello Dear Mr babak
Thanks for your reply
No,I don't know about crashing history,but customer say's that it happened suddenly without any reason!
Are we able to write any other dump for set with near structure and platform to this set then after that alive and go to undead state recover it to original shape? or may this way destroy some section of emmc chip?
thanks Mr nuri

[BABAK NURI]

Hi
if you have suddenly dead,for 99% is eMMC or other HW part issue ....

You can extract RUU and inject Only Bootloader part via eMMC plugin,BUT PLEASE TAKE BACKUP Because may need some important data for IMSI(PGFS)

[sadullo]

Originally Posted by mazmaz1

Hello
I have a HTC Jetstream with qhsusb_dload state
I jtag it with Riff box and resurrect it,without any change after successful resurrection whit generic resurrection and repairing kernel and htc section repairing too.
Is full dump writing solve this prob?
Any one have any address for full dump file for this model?
this is log of resurrection

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [HTC JetStream (PG0941000) V1.0.4816.55337]

Connecting to the dead body...OK
Detected dead body ID: 0x106A10E1 - CORRECT!
Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0045/0x0100 (SEM32G, 0x00076E000000 Bytes = 29.72 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0045/0x0100 (SEM32G, 0x000000100000 Bytes = 1.00 MB)

Flashing the dead body...OK
Resurrection complete!

Hi. I have htc jetstream, what have solved a problem? needs help

[mazmaz1]

I did returned it back to customer