[UNBRICK] HTC Unbricking Project

Did this work?

  • Total voters
    537
Search This thread
By:
Advanced…
S

Sajito

Senior Member
Sep 1, 2013
1,119
834
dexter93 said:
Format? How did you even damage the partitioning?
Click to expand...
Click to collapse

I'm not the only one. I used shanturs twrp and while wiping it froze and I couldn't do anything. After about 30 minutes I pulled battery out, to try again. That seems to have damaged the emmc.
But now it seems my phone is hard bricked. Nothing works, it's recognized as qhsusb_dload only.
 
L

lotan_rm

Senior Member
Apr 2, 2012
64
20
Xiaomi Poco F4 (Munch) / Redmi K40s
dexter93 said:
So it seems to be TWRP's fault. But how come it's only happening on certain devices? When does the problem occur? With wiping?
Click to expand...
Click to collapse

GizmoTheGreen was the first to report it in this thread:
http://xdaforums.com/showthread.php?t=2542506&page=12, comment #112 onward

To me it happened during standard "Wipe". It got stuck, I pulled the battery, put it back in, restarted recovery tried to format and got errors during the mkfs_ext4 call for cache. I tried a 4ext recovery without luck. RUU was my last resort and it got stuck at around 41%. I tried several times, every time stuck at 41% which makes me think, the "partitioning" is messed up.

As Sajito mentioned, trying your procedure in the OP, our devices don't even show up in dmesg.
 
S

Sajito

Senior Member
Sep 1, 2013
1,119
834
dexter93 said:
So it seems to be TWRP's fault. But how come it's only happening on certain devices? When does the problem occur? With wiping?
Click to expand...
Click to collapse

Seems so, but for some reason with your build everything was fine...
I wiped my phone with your build very often and nothing happened. I wiped twice with the one from shantur and both times it got stuck while wiping. First time I could save it since it was only the cache partition, seconds time it was the data partition, so I wasn't able to do anything...

It happens while wiping. For some reason the wipe process freezes or can't complete, but it doesn't abbandon, so you have to pull out the battery. That leads to this problem.
 
dexter93

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,607
2,341
Sajito said:
Seems so, but for some reason with your build everything was fine...
I wiped my phone with your build very often and nothing happened. I wiped twice with the one from shantur and both times it got stuck while wiping. First time I could save it since it was only the cache partition, seconds time it was the data partition, so I wasn't able to do anything...

It happens while wiping. For some reason the wipe process freezes or can't complete, but it doesn't abbandon, so you have to pull out the battery. That leads to this problem.
Click to expand...
Click to collapse

The kernel is the same in both cases, so it shouldn't be our issue. Only updates recovery wise were in init.. But it shouldn't be related. Smells like TWRP
 
S

Sajito

Senior Member
Sep 1, 2013
1,119
834
dexter93 said:
The kernel is the same in both cases, so it shouldn't be our issue. Only updates recovery wise were in init.. But it shouldn't be related. Smells like TWRP
Click to expand...
Click to collapse

But how come that I never had issues with your build? Don't get me wrong, I'm not giving anyone the fault, I just don't get why with your build everything is fine and this problem occured only with shanturs build.
 
S

shantur

Senior Member
Dec 6, 2010
1,095
3,076
Sajito said:
But how come that I never had issues with your build? Don't get me wrong, I'm not giving anyone the fault, I just don't get why with your build everything is fine and this problem occured only with shanturs build.
Click to expand...
Click to collapse

We built at different times, that means different twrp codes. His build might be unaffected from the bug introduced in TWRP.
 
dexter93

dexter93

Inactive Recognized Developer
Jul 1, 2010
11,607
2,341
  • Like
Reactions: Winins
Jack E

Jack E

Senior Member
Nov 30, 2009
247
3
Warwick
I am still able to access recovery and have flashed the latest version of CWM on my TWRP damaged sensation - I don't suppose it would be possible to dd an uncorrupted blank userdata partition over my TWRP formatted one?

I get this output when running e2fsck on the partition:

~ # /sbin/e2fsck -n -f /dev/block/mmcblk0p23
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Error reading block 163923 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? no

Error while scanning inodes (38240): Can't read next inode
e2fsck: aborted
Click to expand...
Click to collapse
 
Last edited:
Jack E

Jack E

Senior Member
Nov 30, 2009
247
3
Warwick
On further investigation the size of the cache partition seems to be incorrect, at least when compared to that stated in this thread, as can be seen from cat /proc/emmc output:

mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p24: 077f5c00 00000200 "cache"
Click to expand...
Click to collapse

It gives a partition size of 077f5c00 rather than the expected 077fde00.
 
Last edited:
S

shider

Member
Aug 5, 2009
8
1
Hi. I also damaged sensation using twrp 2.7.1.0. Recover is accesible but something goes wrong every time after wipe or format data partition. Other recoveries doesn't help too.

@Jack E Here's my fdisk -l /dev/block/mmcblk0:

Code: 
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60

Disk /dev/block/mmcblk0: 2415 MB, 2415919104 bytes
1 heads, 16 sectors/track, 294912 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1   *           1          17         128  4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2              17          49         256  51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3              49        4094       32367  5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4            4094      294912     2326544   5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5            4095        4096          16  5a Unknown
/dev/block/mmcblk0p6            4097        4129         256  73 Unknown
/dev/block/mmcblk0p7            4129        6684       20442+  0 Empty
/dev/block/mmcblk0p8            6684        6716         256   0 Empty
/dev/block/mmcblk0p9            6716        6844        1024  45 Unknown
/dev/block/mmcblk0p10           6844        6876         256  47 Unknown
/dev/block/mmcblk0p11           6876        7132        2048  46 Unknown
/dev/block/mmcblk0p12           7132        7260        1024  4c Unknown
/dev/block/mmcblk0p13           7260        7264          32   0 Empty
/dev/block/mmcblk0p14           7264        8032        6144  34 Unknown
/dev/block/mmcblk0p15           8032        8160        1024  36 Unknown
/dev/block/mmcblk0p16           8161        8192         256  76 Unknown
/dev/block/mmcblk0p17           8193       13313       40960  77 Unknown
/dev/block/mmcblk0p18          13313       14336        8190+ 74 Unknown
/dev/block/mmcblk0p19          14337       16384       16384   0 Empty
/dev/block/mmcblk0p20          16385       18433       16384  48 Unknown
/dev/block/mmcblk0p21          18433       20480       16383  71 Unknown
/dev/block/mmcblk0p22          20481      122880      819199  83 Linux
/dev/block/mmcblk0p23         122881      275807     1223409  83 Linux
/dev/block/mmcblk0p24         275807      291162      122839  83 Linux
/dev/block/mmcblk0p25         291162      291166          32  90 Unknown
/dev/block/mmcblk0p26         291166      291678        4096  4a Unknown
/dev/block/mmcblk0p27         291678      292190        4096  4b Unknown
/dev/block/mmcblk0p28         292190      294750       20480  19 Unknown
/dev/block/mmcblk0p29         294750      294750           4   0 Empty
/dev/block/mmcblk0p30         294750      294782         256  23 Unknown
/dev/block/mmcblk0p31         294783      294784          16   0 Empty
/dev/block/mmcblk0p32         294785      294912        1022+ 76 Unknown
/dev/block/mmcblk0p33           4095        4096          16  5a Unknown
/dev/block/mmcblk0p34           4097        4129         256  73 Unknown
/dev/block/mmcblk0p35           4129        6684       20442+  0 Empty
/dev/block/mmcblk0p36           6684        6716         256   0 Empty
/dev/block/mmcblk0p37           6716        6844        1024  45 Unknown
/dev/block/mmcblk0p38           6844        6876         256  47 Unknown
/dev/block/mmcblk0p39           6876        7132        2048  46 Unknown
/dev/block/mmcblk0p40           7132        7260        1024  4c Unknown
/dev/block/mmcblk0p41           7260        7264          32   0 Empty
/dev/block/mmcblk0p42           7264        8032        6144  34 Unknown
/dev/block/mmcblk0p43           8032        8160        1024  36 Unknown
/dev/block/mmcblk0p44           8161        8192         256  76 Unknown
/dev/block/mmcblk0p45           8193       13313       40960  77 Unknown
/dev/block/mmcblk0p46          13313       14336        8190+ 74 Unknown
/dev/block/mmcblk0p47          14337       16384       16384   0 Empty
/dev/block/mmcblk0p48          16385       18433       16384  48 Unknown
/dev/block/mmcblk0p49          18433       20480       16383  71 Unknown
/dev/block/mmcblk0p50          20481      122880      819199  83 Linux
/dev/block/mmcblk0p51         122881      275807     1223409  83 Linux
/dev/block/mmcblk0p52         275807      291162      122839  83 Linux
/dev/block/mmcblk0p53         291162      291166          32  90 Unknown
/dev/block/mmcblk0p54         291166      291678        4096  4a Unknown
/dev/block/mmcblk0p55         291678      292190        4096  4b Unknown
/dev/block/mmcblk0p56         292190      294750       20480  19 Unknown
/dev/block/mmcblk0p57         294750      294750           4   0 Empty
/dev/block/mmcblk0p58         294750      294782         256  23 Unknown
/dev/block/mmcblk0p59         294783      294784          16   0 Empty
/dev/block/mmcblk0p60         294785      294912        1022+ 76 Unknown

Partition table entries are not in disk order

Is this partition table correct?

I tried flashing RUU via fastboot but it hangs on:

Code: 
...
(bootloader) start image[dzdata] unzipping & flushing...
(bootloader) [RUU]UZ,dzdata,0
(bootloader) [RUU]UZ,dzdata,100
(bootloader) [RUU]WP,dzdata,0

After deleting dzdata_4g.* from PG58IMG.zip other partitions are flashed whithout any problems. Unfortunately smartphone goes into bootloop.
 
Last edited:
M

mx568549060@gmail.com

Member
May 15, 2014
15
1
shider said:
Hi. I also damaged sensation using twrp 2.7.1.0. Recover is accesible but something goes wrong every time after wipe or format data partition. Other recoveries doesn't help too.

@Jack E Here's my fdisk -l /dev/block/mmcblk0:

Code: 
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60

Disk /dev/block/mmcblk0: 2415 MB, 2415919104 bytes
1 heads, 16 sectors/track, 294912 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1   *           1          17         128  4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2              17          49         256  51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3              49        4094       32367  5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4            4094      294912     2326544   5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5            4095        4096          16  5a Unknown
/dev/block/mmcblk0p6            4097        4129         256  73 Unknown
/dev/block/mmcblk0p7            4129        6684       20442+  0 Empty
/dev/block/mmcblk0p8            6684        6716         256   0 Empty
/dev/block/mmcblk0p9            6716        6844        1024  45 Unknown
/dev/block/mmcblk0p10           6844        6876         256  47 Unknown
/dev/block/mmcblk0p11           6876        7132        2048  46 Unknown
/dev/block/mmcblk0p12           7132        7260        1024  4c Unknown
/dev/block/mmcblk0p13           7260        7264          32   0 Empty
/dev/block/mmcblk0p14           7264        8032        6144  34 Unknown
/dev/block/mmcblk0p15           8032        8160        1024  36 Unknown
/dev/block/mmcblk0p16           8161        8192         256  76 Unknown
/dev/block/mmcblk0p17           8193       13313       40960  77 Unknown
/dev/block/mmcblk0p18          13313       14336        8190+ 74 Unknown
/dev/block/mmcblk0p19          14337       16384       16384   0 Empty
/dev/block/mmcblk0p20          16385       18433       16384  48 Unknown
/dev/block/mmcblk0p21          18433       20480       16383  71 Unknown
/dev/block/mmcblk0p22          20481      122880      819199  83 Linux
/dev/block/mmcblk0p23         122881      275807     1223409  83 Linux
/dev/block/mmcblk0p24         275807      291162      122839  83 Linux
/dev/block/mmcblk0p25         291162      291166          32  90 Unknown
/dev/block/mmcblk0p26         291166      291678        4096  4a Unknown
/dev/block/mmcblk0p27         291678      292190        4096  4b Unknown
/dev/block/mmcblk0p28         292190      294750       20480  19 Unknown
/dev/block/mmcblk0p29         294750      294750           4   0 Empty
/dev/block/mmcblk0p30         294750      294782         256  23 Unknown
/dev/block/mmcblk0p31         294783      294784          16   0 Empty
/dev/block/mmcblk0p32         294785      294912        1022+ 76 Unknown
/dev/block/mmcblk0p33           4095        4096          16  5a Unknown
/dev/block/mmcblk0p34           4097        4129         256  73 Unknown
/dev/block/mmcblk0p35           4129        6684       20442+  0 Empty
/dev/block/mmcblk0p36           6684        6716         256   0 Empty
/dev/block/mmcblk0p37           6716        6844        1024  45 Unknown
/dev/block/mmcblk0p38           6844        6876         256  47 Unknown
/dev/block/mmcblk0p39           6876        7132        2048  46 Unknown
/dev/block/mmcblk0p40           7132        7260        1024  4c Unknown
/dev/block/mmcblk0p41           7260        7264          32   0 Empty
/dev/block/mmcblk0p42           7264        8032        6144  34 Unknown
/dev/block/mmcblk0p43           8032        8160        1024  36 Unknown
/dev/block/mmcblk0p44           8161        8192         256  76 Unknown
/dev/block/mmcblk0p45           8193       13313       40960  77 Unknown
/dev/block/mmcblk0p46          13313       14336        8190+ 74 Unknown
/dev/block/mmcblk0p47          14337       16384       16384   0 Empty
/dev/block/mmcblk0p48          16385       18433       16384  48 Unknown
/dev/block/mmcblk0p49          18433       20480       16383  71 Unknown
/dev/block/mmcblk0p50          20481      122880      819199  83 Linux
/dev/block/mmcblk0p51         122881      275807     1223409  83 Linux
/dev/block/mmcblk0p52         275807      291162      122839  83 Linux
/dev/block/mmcblk0p53         291162      291166          32  90 Unknown
/dev/block/mmcblk0p54         291166      291678        4096  4a Unknown
/dev/block/mmcblk0p55         291678      292190        4096  4b Unknown
/dev/block/mmcblk0p56         292190      294750       20480  19 Unknown
/dev/block/mmcblk0p57         294750      294750           4   0 Empty
/dev/block/mmcblk0p58         294750      294782         256  23 Unknown
/dev/block/mmcblk0p59         294783      294784          16   0 Empty
/dev/block/mmcblk0p60         294785      294912        1022+ 76 Unknown

Partition table entries are not in disk order

Is this partition table correct?

I tried flashing RUU via fastboot but it hangs on:

Code: 
...
(bootloader) start image[dzdata] unzipping & flushing...
(bootloader) [RUU]UZ,dzdata,0
(bootloader) [RUU]UZ,dzdata,100
(bootloader) [RUU]WP,dzdata,0

After deleting dzdata_4g.* from PG58IMG.zip other partitions are flashed whithout any problems. Unfortunately smartphone goes into bootloop.
Click to expand...
Click to collapse

I have the same problem,,do you have fixed？
 
You must log in or register to reply here.

Similar threads

mike1986.
[ROM] Android Revolution HD 7.3 | ICS | High Quality & Performance | Legendary
Replies
81K
Views
16M
Ulumia
Ulumia
m0narx
[ROM][Sense 4.1][05.06] Team Venom presents: ViperS 2.0.3 - welcome to the future
Replies
26K
Views
5M
O
OBLIVION007
bruce2728
[ROM][CM10][Kang][Pyramid][4.1.2][04 Oct]
Replies
22K
Views
5M
P
Proxymist
V6-Maniac
[ROM] [29 Sept] ELEGANCIA™ | Sense 3.6 | 4.0 |► ◄| Sense 4.1 | 8.0.0 |EQS,APM,HUB|
Replies
28K
Views
4M
M
materijalmen
shnizlon
[ROM][Sense 4.0][FINISHED] OrDroid 9.0.0 | EQS | APM | Tweaks | Fast & Stable
Replies
17K
Views
3M
dodge67
dodge67

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 167
    dexter93
    dexter93
    We are proud to announce that the Sensation is now UNbrickable. Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional.

    Unbrick-proj-Sensation.jpg

    ​

    Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it

    The "core" of the unbricking project dev team:
    MOVZX
    RussianBear
    Fuses
    Dexter93
    Testing stuff and irc support:
    globatron
    Deceptivechaos
    dburgd84
    Snake_skw
    Other stuff:
    dmcb123
    xIndirect
    Hawke84    ​

    Thanks to trevE, xHausx and the rest of the evo3d team that gave us the basic info to work on and made us curious to see if we could get something out of it. Also thanks to ief and his team @revolutionary for helping us understand the bootloaders better. We should also not forget to thank cxb01 of malshenzu.com and xda members arthurire and untrueparadox who helped in translation.
    View
    82
    dexter93
    dexter93
    Prerequisites
    • a linux box/live cd with automount disabled and without unity
    • the appropriate package for the device
    • the latest RUU for your device
    • a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
    • a usb cable
    • some basic linux experience
    • patience

    DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.

    Instructions​
    Detailed video on the process. Thanks kgs1992


    1. Boot the linux box and download the appropriate package for the device.
      WARNING: IT IS DEVICE SPECIFIC. DO NOT USE THE XE VERSION ON A 4G/ORIGINAL SENSATION AND VICE VERSA
    2. Extract the package in the home directory
    3. Open up a terminal
    4. Remove SIM, microSD card and battery and connect the device using the USB cable. This procedure must be done without battery
    5. Detect the device using the script provided. Type this in the terminal
      Code: 
      ./brickdetect.sh
      You should get something like sdX. We are interested on that "X"
    6. Unplug the usb cable from the device
    7. Backup the hboot currently in the phone by using this command. Plug the device in ONLY when asked to
      Code: 
      sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
      Replace the "X" with the letter the script gave you
    8. Follow the on-screen instructions from emmc_recover
    9. Hexdump the b_hboot to check the hboot version
      Code: 
      hexdump -C b_hboot.img |less
      The output should be like this:
      Code: 
      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|
      This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.17
    10. If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again
    11. Unplug the device
    12. Check again it is the right version, because if you do a mistake here, you won't be able to go back
      You can only flash the same version as the one in the device.


      !!!!!DO NOT ATTEMPT TO FLASH ANOTHER VERSION OR DOWNGRADE!!!IT HAS BEEN PROVEN FATAL!!!!
    13. Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.17, 1.18, 1.19, 1.20, 1.23, 1.27) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to
      Code: 
      sudo ./emmc_recover --flash pyrV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0
    14. Follow the on-screen instructions from emmc_recover. A successful flash should have this output:
      Code: 
      511+1 records in
511+1 records out
1047808 bytes(1.0 MB) copied
    15. Unplug the device, put SIM, microSD card and battery in and power on
    16. Congratulations, the device is unbricked.
    17. FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.

    Notes on the procedure:​

    • If the device doesn't power on, get a copy of the hboot_f.nb0 and b_hboot.img (should be located in the home directory) and contact us
    • The connection between the device and the pc will be unstable, and will time out. You have to be quick when doing the above, specially while flashing. If the connection times out don't panic, just unplug and replug the device
    • Unity and automount are known to cause issues in ubuntu 11.04 and 11.10. We recommend getting rid of both, or use a 12.04, or 10.04/.10 liveCD
    • USB3 ports do not work properly. Please plug the device in a USB2 port
    • The liveCD provided has autoount enabled. please disable it
    • How to disable automount on ubuntu
      Code: 
      gsettings set org.gnome.desktop.media-handling automount false


    Downloads

    For Sensation and Sensation 4G:
    32bit version MD5: 859cf1c8f4cc96a9c911ecf696579e6f
    64bit version MD5: d160e90234999a0f8e5ed632d3a2bb4e

    For Sensation XE:
    32bit version MD5: dec2309cc06dbc01398a4a49f8ae13cf
    64bit version MD5: de677136626fe2e096f0a7f48e438978


    Don't have a linux distro installed on your pc? We highly recommend this livecd
    ​
    View
    18
    F
    Fuses
    It is unbelievable how many writesecureflag bricked devices there are in this world!!

    I write this little tool to help people to unbrick those phones. It also helps unbrick those phones that can be in emmc_mode only few seconds. It uses dd to flash images into device.

    In this guide I will assume that hboot is causing that brick and hboot is at /dev/sdb12 when emmc_mode enabled phone is connected.

    What you need:
    1) Bricked sensation :D
    2) Linux, If you want to use windows you have to wait that somebody makes emmc_mode stable. If you don't have Linux installed, some Live-cd should be fine.
    3) signed hboot from original rom you are using
    4) This little tool called emmc_recover
    5) Figure out what will be correct device node when phone is in emmc_mode
    It is usually /dev/sda /dev/sdb /dev/sdc etc.

    With this tool you can reflash any partition you want. SO BE CAREFUL.

    There are few options in this tool:
    Code: 
    emmc_recovery 0.1 usage:
emmc_recovery [OPTIONS]
	-h | --help: display this help
	-b | --backup
	-f | --flash
	-d | --device

    How to use it (You have to root):
    1) First BACKUP partition
    Code: 
    ./emmc_recover --backup backupfile.img --device /dev/sdb12
    This will backup current sensation hboot into file backupfile.img.

    2) Check that this really is correct partition
    Code: 
    hexdump -C backupfile.img |less
    It should be something like this for hboot
    Code: 
    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|
    3) If backup was successfull, flash new hboot
    Code: 
    ./emmc_recover --flash hboot_xxxx.xxx.xx.xx.xx.nb0 --device /dev/sdb12
    4) Done.

    Below are usual output from tool:
    Code: 
    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

    Connect device into computer when you see line.
    Code: 
    Waiting device /dev/sdb12.......

    Not before!!

    NOTE: There may be bugs present....
    View
    11
    R
    RussianBear
    awesome!

    any people that know chinese, we need your help:

    a chinese forum where a member posted a guide on how to de-brick a phone (zte u960) from qhsusb_mode:

    http://bbs.malshenzu.com/read-htm-tid-38591-page-1.html

    http://bbs.malshenzu.com/read-htm-tid-41957-page-1.html ( Sales MultiDL tool guide)

    they use an additional tool (Sales MultiDL) that backs up alot of .mbn and .img files that we don't have (yet), so i'm not sure if we can pull those files out of the phone manually, or what?

    80_4747_74ac8bc91c00562.jpg


    translation per untrueparadox:

    1. choose program mode
    2. select the .hex and .mbn files from the included package
    3. load the .xml included in the package
    ____ the path to xml file will show here
    4. after selecting everything, click download to revive the brick

    the files they used to flash:

    80_4747_6a6329c38cb962f.jpg




    anyone knows Chinese (google chrome translator is ok for basic understanding, but nothing more than that)? :)
    i did pm the op of those threads to see what he thinks.
    View
    11
    MOVZX
    MOVZX
    Oh my God...

    Dude... Looks like I have my God besides Me... And my heart is now crying (really)...

    MY PHONE IS NOW ON!! IT COULD BE TURNED ON AGAIN!!


    Thanks God! I really need a beer, I'm going to go now for a celebration...

    PS: I will write tutorials to resurrect the bootloader as soon as possible...


    Thanks XDA Dev... And now I'm sure we'll be able too so ressurrect any phone with MSM8260/MSM8660 including EVO 3D...
    View

New posts