Yes, I think that is hboot what was used in that version. Or close enough...
Yes it is.It's the "hboot_8x60_1.18.0000_20110802_signedbyaa.nb0" right? (Just making sure )
if you arent perfectly sure about it, download the latest ruu for your cid and extract itIt's the "hboot_8x60_1.18.0000_20110802_signedbyaa.nb0" right? (Just making sure )
root@ubuntu:/home/arne/Downloads# ./emmc_recover --flash hboot.img --device /dev/sdg12
emmc_recovery 0.1
Messing up with device /dev/sdg12, ARE YOU SURE? (CTRL+C if not)
Flashing image file is hboot.img
Device is /dev/sdg12!!
PRESS CTRL+C if everything is not correct!
Connect device into emmc partition mode NOW
Waiting device /dev/sdg12.......
Foundit!
511+1 records in
511+1 records out
1047808 bytes (1.0 MB) copied, 0.575342 s, 1.8 MB/s
Return code is 0
Everybody disconnect from irc. I have to fix something
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
when i try to flash the new hboot it says:
"dd: writing '/dev/sdb12': no space left on device"
could be that my hboot is not on sdb12?
or am i trying to flash another thing i extracted the file boot_signed.img and renamed to hboot.img
am i on the right way?
am supposed to push the hboot_8x60_1.18.0000_20110802_signedbyaa.nb0 file?
Yes. That's it. You almost pushed a kernel
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
you are not supposed to, but it would be better if you didbut why in terminal you guys are writing hboot.img? i should rename it?
---------- Post added at 06:19 PM ---------- Previous post was at 06:11 PM ----------
GREAAT it workkeed !!!
now am supposed to reflash the RUU?
We will get the hboots... eventuallyI would recommend everyone with dead Sensation to use GNU/Linux for the unbrick process (Ubuntu preferre). Because it needs just about 5 seconds to finish the hboot injection process.
@Dexter, maybe You should decide the Fuses' method as the prime tutorial; unless everyone has a stable eMMC mode like Me so they could use WinHex instead.
I have tried to brick and unbricked my phone for 21 times with luck, so I'm sure we could release the tutorial as soon as possible. Even if some people might just get stucked at the bootloader, they could fix it as we did on my device by running the proper RUU which depends on the mainver (mine was 1.50.707.1).
PS: 21 times of successful brick and unbrick is enough for Me
We should collect every hboot from RUU built into tutorials, so noon won't do anythings' dangerous.
./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.......