Yeah sorry I hadn't posted earlier, I follow them on twitter and saw them tweet that on the 21 of Feb, but I hadn't seen this post before lol
who is "them"? any guys from "them" on here?
Yeah sorry I hadn't posted earlier, I follow them on twitter and saw them tweet that on the 21 of Feb, but I hadn't seen this post before lol
This picture shows that phone has exposed emmc chip as external usb disk. This means that they are in totally different "download mode" that we can have access to... Extremely interesting... Now somebody have to do same thing with sensation.
I can't understant a single word of chinese. What ZTE device was used?
Fantastic thread, i've been following this closely since it poped up. I think this is what we need a way of recovering bricked devices, ive bricked mine once so know the pain!
I dont know a lot about this but would be willing to help with whatever i can..
I've seen that some people have managed to dump the whole phone contents in DL mode so i guess thats a good start..
FYI there's a jtag for Sensation available.
http://mobiletechvideos.mybigcommerce.com/htc-sensation-4g-jtag-brick-repair/
that guy is really good, he fixed my gf's sgs4g after i bricked it lol
As for the wenku link,it's about how to flash a ROM.But it doesn't have any information about which device it is.The only information is this cellphone is using screens made by SHARP.
The picture is just the same with the last picture we have talked.
Under the pictures is another method to flash(terminal in Linux System)
Then the passage discussed how to mod the ROM if the cellphone is using AUO(WTF it is?) screen.
After that,flash commands.
This thread and the picture is just talking about why the ROM is 300M,for example but it requires 900MB freespace.
The picture and the thread says that the official flash tool will divide the ROM into small blocks(64MB each) Even the MISC partition is only 256k but it still needs 64MB free space.
do you have the phone? if so, follow all the steps in the first post to hook it up with qpst in download mode, then see if you can get winhex and/or parition manager to recognize the phone as a drive. then see if you can clone anything
just a small bump. im not able to work on that until the weekend.. also if some volunteers with bricked devices are here, please contact
So it seems like the riff box got updated to support the sensation. Interesting...
EDIT: Seems like the riff box doesnt support the sensation yet http://www.jtagbox.com/category/riff-jtag-features/
also the riff box guy is still searching for dead devices http://forum.gsmhosting.com/vbb/f634/htc-sensation-does-anyone-have-hw-dead-board-1437249/
are you sure it was riff box?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
I remember there is a way to forcefully boot up your phone.
Try supercharge, I can't find the post for supercharging, but it is like opening up your phone charger's wire, tweak and make its voltage or what so higher, forcing you to temporarily open up your phone, boot into recovery and reflash.
Erm, trying searching through the forum, I remembered I saw it under Sensation or Desire HD's thread.
Your warranty is void when you S-Off your phone, I do not really think the store will replace a new phone for you, but... you can try corrupt the whole phone and say it is not your fault, HTC has nice reputations for replacing their phones because of the manufacturing flaws. (HTC is infamous for its of manufacturing problems...)
As long as you do not flash hboot or radio, your phone has a high chance of reviving, good luck
My friend's phone also become brick, cannot charge, cannot boot, cannot do anything.
I also have HTC SENSATION and try to enter diag mode then I take QCN file already.
- First I install GSscript and run script to enable diag mode
- Then connect the phone and turn on QPST
- Many times get the no phone connect but 1 time I get my lucky. It can connect and can copy NV (qcn file), backup QCN file.
- After backup QCN file, I try to take Multi-image but it tell me that the current phone is not in Download mode then
it reboot and try to go to dowload mode (the process is fail)
- I try with brick phone in restore tab but it warn that the phone is not in diag mode.
Now I plus my phone back and get no-phone connect isssue.
I stuck here, will update if have any information
(sorry about my English)
This is interesting...
http://xdaforums.com/showpost.php?p=17537143&postcount=26
I think I will brick my phone again to test the 'supercharge' method to force boot of bricked HTC Sensation. No worry about it because I have another HTC Sensation too
a BIG thanks to wildstang83 for this!
If you are getting vibrates when trying to boot your phone. do the following:
Download
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
google, you will find it.
backup your SD card, format it fat 32 and place this file on the root of your card. Be sure to rename it PB31IMG.zip
Once it is on your sd card, verify the MD5 to ensure the file was not corrupted during the download or during the transfer.
Hold Vol down + power. you will feel 5 vibrations
wait for a god 2 to 3 min. if everything is going correctly, your phone is verifying the IMG file and this takes a bit.
after 2 to 3 min. wait one more min
now, press vol up. this tells the phone to update.
wait 2 to 3 min for the update to happen then wait one more.
press vol up again. you should feel the phone single vibrate and then presto.. working phone again
next time be more careful
Please let me know if this did not work for you.
THANKS WILDSTANG!! You're what these forums are all about
the "bad" (bricked) phone is in the download mode, which is different from the diagnostic mode the script enables. besides, those qcn files are not what's needed to restore the phone.
see this post and try it: http://xdaforums.com/showpost.php?p=23106274&postcount=29
I'm not sure what flasher-box is He actually using. But He just told Me that the box He used to repair my HTC Sensation is RIFF-BOX and some pin-out (He just said pin-out or pinout, I'm not really understand) combination. But I can see now my device looks like has been dissected/disassembled (maybe for the repair purpose).
I got the guy from this forum: http://www.bandung-flasher.com (In my country, Bandung-Flasher community is the biggest Flasher Guy support center. They even could repair broken devices way faster and cheaper than the official service center, it's why people in my country never repaired the dead phones to official service center. And they have a huge collection of flasher-box equipment. And Bandung -city- well known also with the biggest Independent/Unofficial Flasher Service).
-------edit------------------
I got the image from the guy:
Bro! The problem here is: I cannot change mode of the good phone to download mode (If I can, I will take a full backup which produce several mbn file), also cannot change mode of the bad phone to diag mode.
why can't you change the good phone into the dl mode? grab a wire and do the pin trick like posted.
forget about the bricked phone for now.
./brickdetect.sh
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
hexdump -C b_hboot.img |less
00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 10 40 |...............@|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 1f 40 00 01 00 00 |...........@....|
00000020 d8 fc 1f 40 00 00 00 00 12 00 00 ea 31 2e 31 37 |...@........[B]1.17[/B]|
00000030 2e 31 31 31 31 00 00 00 38 32 36 30 20 53 50 4c |.1111...8260 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 32 |.. ... .HBOOT-82|
00000060 36 30 00 00 00 f0 20 e3 39 32 65 35 33 37 31 30 |60.... .92e53710|
sudo ./emmc_recover --flash pyrV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0
511+1 records in
511+1 records out
1047808 bytes(1.0 MB) copied
gsettings set org.gnome.desktop.media-handling automount false
emmc_recovery 0.1 usage:
emmc_recovery [OPTIONS]
-h | --help: display this help
-b | --backup
-f | --flash
-d | --device
./emmc_recover --backup backupfile.img --device /dev/sdb12
hexdump -C backupfile.img |less
00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 10 40 |...............@|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 1f 40 00 01 00 00 |...........@....|
00000020 d8 fc 1f 40 00 00 00 00 12 00 00 ea 31 2e 31 38 |...@........1.18|
00000030 2e 30 30 30 30 00 00 00 38 32 36 30 20 53 50 4c |.0000...8260 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 32 |.. ... .HBOOT-82|
00000060 36 30 00 00 00 f0 20 e3 39 64 32 34 31 32 33 66 |60.... .9d24123f|
./emmc_recover --flash hboot_xxxx.xxx.xx.xx.xx.nb0 --device /dev/sdb12
emmc_recovery 0.1
Messing up with device /dev/sdb12, ARE YOU SURE? (CTRL+C if not)
Flashing image file is hboot_xxxx.xxx.xx.xx.xx.nb0
Device is /dev/sdb12
Press ENTER if everything is correct, CTRL+C if not
Connect device into emmc partition mode NOW
Waiting device /dev/sdb12.......
Foundit!
512+0 records in
512+0 records out
1048576 bytes (1.0 MB) copied, 0.740003 s, 1.4 MB/s
Return code is 0
Waiting device /dev/sdb12.......