[UnORom][RECOVERY]Latest TWRP v2.7.0.0 [07 May]

[lovendsuicide]

o.k. where i can download last release of twrp for senny?

Sent from my HTC Sensation using Tapatalk

Dude, are you serious?

 

[derproblembaer]

I had no problems with the last version. I used it successfully on three different Sennys.

TWRP is imho the best recovery out there. I hope theres a way to fix it. It's Open Source and the function to queue multiple zips is awesome.

It's possible to save the last version from a Senny which already has it using the dd command. I've done that yesterday without issues. But I would not recommend doing that.

 

[Sajito]

I had no problems with the last version. I used it successfully on three different Sennys.

TWRP is imho the best recovery out there. I hope theres a way to fix it. It's Open Source and the function to queue multiple zips is awesome.

The problem is not twrp in general, it's this one from shantur, which sometimes while wiping freezes. That leads to corrupted partitions.
With the one from dexter I never had problems, except that battery does not charge while phone is off.

 

[sly68]

thanks, i have installed 4ext.

Sent from my HTC Sensation using Tapatalk

 

[shantur]

I see that many people seem to have broken the device using this recovery. My apologies to all of you.
I have taken down the recovery. If any of you guys with broken phone can send me the phone to me in London, UK i can try and help reviving it.
I cannot try the same on my device as i will need one working device to find the solution.

If anyone wishes to send me the phone PM me and I will give you my details.

No one?

 

[corumuk]

seems there's a new official version of twrp available for pyramid, v2.7.1.0 in case anyone is interested. i've tried it out by carrying out a factory reset, then an advanced wipe including data etc, then restored a backup. all seems to work ok now.

 

[derproblembaer]

seems there's a new official version of twrp available for pyramid, v2.7.1.0 in case anyone is interested. i've tried it out by carrying out a factory reset, then an advanced wipe including data etc, then restored a backup. all seems to work ok now.

Nice, I will try it out as soon as I'm at home.

Download Link:
http://techerrata.com/browse/twrp2/pyramid

 

[Sajito]

No one?

I would send you mine, but it's totally dead. I'm going to send it to htc and hope that they'll repair it under warranty, though I don't have much hope.

 

[shantur]

So it wasn't me

http://forum.xda-developers.com/showpost.php?p=53322518&postcount=1304

 

[corumuk]

Wow, glad I didn't brick mine yesterday then. Tested v2.7.1.0 and data partition formatted fine. Twice.

At the end of the day we all know the risks I guess and certainly nobody is pointing any fingers but its still an unwelcome kick in the cojones when something like this happens.

Kudos to shantur for offering to attempt repairs though.

Sent from my Nexus 7 using XDA Free mobile app

 

[01 Vlatce]

Guys, the new official TWRP 2.7.1.0 for Pyramid you are talking about is taken down or something? Because there's no new 2.7.1.0 img file on TWRPs page for Pyramid, only for Sensation XL*Runnymede.

 

[Sajito]

Guys, the new official TWRP 2.7.1.0 for Pyramid you are talking about is taken down or something? Because there's no new 2.7.1.0 img file on TWRPs page for Pyramid, only for Sensation XL*Runnymede.

I think it has been taken down, because someone reported that the official bricked his device too. There seems to be something wrong with twrp itself.

 

[shider]

I can confirm that twrp 2.7.1.0 realy bricks Sensation. Mine was damaged during wipe of data partition. Currently i can't install or recover any rom. I tried other recoveries with same result. Problem is realy strange. After wipe or format data partition other partitions become unmountable. After restart it becomes mountable again. I tried recovring using RUU but it hangs on 39% and the phone stucks with damaged hboot. I recovered it from this state flashing it again with update zip whithout system and data partitions.

It is also strange but after one of install of cm-11-20140511-Sultan-pyramid smatphone get up normally. Unfortunetlu i cant reproduce this again

@shantur can you explain what twrcp is doing exacly during wipe and format of data partition? I can't send You my device (because of shipping costs) but I can provide You any informations using any tools.

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

~ # 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?

Flashing RUU via fastboot hangs on:

...
(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.

 

[frert]

@shantur do you still want a sensation to work on? I can send you mine so you can investigate the problem.

Sent from my GT-I9300 using Tapatalk

 

[shantur]

I can confirm that twrp 2.7.1.0 realy bricks Sensation. Mine was damaged during wipe of data partition. Currently i can't install or recover any rom. I tried other recoveries with same result. Problem is realy strange. After wipe or format data partition other partitions become unmountable. After restart it becomes mountable again. I tried recovring using RUU but it hangs on 39% and the phone stucks with damaged hboot. I recovered it from this state flashing it again with update zip whithout system and data partitions.

It is also strange but after one of install of cm-11-20140511-Sultan-pyramid smatphone get up normally. Unfortunetlu i cant reproduce this again

@shantur can you explain what twrcp is doing exacly during wipe and format of data partition? I can't send You my device (because of shipping costs) but I can provide You any informations using any tools.

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

~ # 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?

Flashing RUU via fastboot hangs on:

...
(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.

I dont know what TWRP does to screw the phone. I think best is to ask TWRP devs such as @Dees_Troy

@shantur do you still want a sensation to work on? I can send you mine so you can investigate the problem.

Sent from my GT-I9300 using Tapatalk

I can work on it but I am busy with other things for some time as well so might not be able to do something too quick.
If you expect for something to happen real soon dont send otherwise i will definitely look into it as i get time.

If you are happy PM me I will give you my details.

 

[Jack E]

@shantur, would it be possible for you to provide us with an image of a working, freshly formatted data partition by running this in recovery?

adb shell
mount sdcard
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23.img

Any help is much appreciated, from you, or anybody for that matter!

Edit: Likewise could someone with a working phone provide us with the output from this command?

fdisk -l /dev/block/mmcblk0

 

[shantur]

@shantur, would it be possible for you to provide us with an image of a working, freshly formatted data partition by running this in recovery?

Any help is much appreciated, from you, or anybody for that matter!

Edit: Likewise could someone with a working phone provide us with the output from this command?

Image is located at : http://xda.shantur.com/get.php?p=test/mmcblk0p23.img.zip

Partition details :

~ # 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
~ #

 

[Jack E]

Thanks Shantur, it does indeed seem to be caused my an eMMC controller bug as suggested by dexter93 in his unbrick project thread. There appear to be bad blocks caused by the format midway through the data partition :/

 

[shider]

Thanks Shantur, it does indeed seem to be caused my an eMMC controller bug as suggested by dexter93 in his unbrick project thread. There appear to be bad blocks caused by the format midway through the data partition :/

On my Sensation it looks similar. But bad blocks should be in constant place, here isn't. I tried to dump data partition using dd and every time it produce different count of bytes. After that other partitions became unavailable.

 

[hinxnz]

<snip> I tried recovring using RUU but it hangs on 39% and the phone stucks with damaged hboot. </snip>

Just a random suggestion, if your phone is S-off you could try a GB RUU