[Q] bricked htc-corrupted partitions

Search This thread

rmann

Member
Jan 23, 2013
13
15
yeah you are right
some partitions are broken probably from TWRP because a lot of users faced issues similar with yours

someone posted a solution few days ago how to boot a rom from sdcard
he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
he created two partitions
one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
but i can't find that post
if i find it i will come with edit

Yes, I managed to boot my sensation from SD card by moving both /system and /data partition using a patched boot.img and modified rom install script...

Here is the link to the thread:http://xdaforums.com/htc-sensation/help/recovering-data-mount-issues-t2859588

Posted in Q&A as I didn't had privileges.

PS: I have to add some e2fsck commands as well as after some time the log starts showing warnings on mounts in the log but phone working ok.
 
  • Like
Reactions: MatesCZ and rzr86

MatesCZ

Member
May 19, 2008
9
0
Yes, I managed to boot my sensation from SD card by moving both /system and /data partition using a patched boot.img and modified rom install script...

Here is the link to the thread:http://xdaforums.com/htc-sensation/help/recovering-data-mount-issues-t2859588

Posted in Q&A as I didn't had privileges.

PS: I have to add some e2fsck commands as well as after some time the log starts showing warnings on mounts in the log but phone working ok.

Thanks, I tried your method precisely, yet the installation failed again. Moreover, the log doesn't even show anything useful this time (I think).

Log from 4EXT:
Code:
Starting AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers

aroma/s: Open Archive
aroma/s: Initializing Resource

DEVICE NAME: proximity - /sys/board_properties/virtualkeys.proximity
EV ST: minX: 0  maxX: 0  minY: 0  maxY: 0
EV MT: minX: 0  maxX: 0  minY: 0  maxY: 0

...
(bunch of lines similar to those last three)
...

aroma/s: Opening Freetype
aroma/s: Mute Parent
aroma/s: Starting Interface
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
E:Error in /sdcard/Revelation_1.0.3.zip
(Status 0)
Installation aborted.

The zip is the one with the replaced boot.img and updater-script. The installation failed roughly around 51% of the process.
 

rmann

Member
Jan 23, 2013
13
15
Seems like I have attached the wrong updater-script with the thread. Try the one that is attached to this. Please note the ext is .txt as edited in notepad(in office at the moment).

Use the attached boot.img as well... Once you confirm success, i will update my original post with the new files.
 

Attachments

  • updater-script.txt
    23.4 KB · Views: 358
  • new_boot.img
    5.1 MB · Views: 274
Last edited:
  • Like
Reactions: MatesCZ

MatesCZ

Member
May 19, 2008
9
0
Seems like I have attached the wrong updater-script with the thread. Try the one that is attached to this. Please note the ext is .txt as edited in notepad(in office at the moment).

Use the attached boot.img as well... Once you confirm success, i will update my original post with the new files.

Awesome, just tried it and it works now :D The only problem I have now is the wifi refuses to turn on for some reason...but hey, I basically have a working Sensation again, so thanks a lot! Shame there isn't something universal that could make it work for (almost) any ROM.
 

rmann

Member
Jan 23, 2013
13
15
Glad that it worked. For me the WiFi works as well.

Can you share the boot log, which will have info on why WiFi is failing.


Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Free mobile app
 

MatesCZ

Member
May 19, 2008
9
0
Glad that it worked. For me the WiFi works as well.

Can you share the boot log, which will have info on why WiFi is failing.


Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Free mobile app

I'm not exactly sure what is considered boot log, but here is my kmsg if that's it.
 

Attachments

  • kmsg.txt
    127.3 KB · Views: 35

rmann

Member
Jan 23, 2013
13
15
I'm not exactly sure what is considered boot log, but here is my kmsg if that's it.

I have compared it to mine and can't find any suttle differences. You might want to try re-installing...

BTW, I am now trying to install Slimkat.. will share the scripts if mine boots ok.
 
Last edited:

MatesCZ

Member
May 19, 2008
9
0
I have compared it to mine and can't find any suttle differences. You might want to try re-installing...

BTW, I am now trying to install Slimkat.. will share the scripts if mine boots ok.

Already tried reformating and reinstalling twice, still the same. That would be nice, different ROM might help :)
 

wilsonkok19996

Senior Member
May 24, 2012
96
1
Kuala Lumpur
HELP MY PHONE IS DEAD. BELOW IS THE FASTBOOT GETVAR ALL
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.106
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3976mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
 
Last edited:

razor26

Senior Member
I also have this problem regarding internal sdcard partition getting corrupted. Somehow I am able to resolve the unable to mount /data issue and all partitions are readable perfectly in the 4ext recovery. I can flash custom roms and install them fine in the recovery but the result is always bootloop. Any ideas on how to fix this? Thanks.
 

rzr86

Senior Member
May 21, 2012
8,107
2,456
38
Nafpaktos
I also have this problem regarding internal sdcard partition getting corrupted. Somehow I am able to resolve the unable to mount /data issue and all partitions are readable perfectly in the 4ext recovery. I can flash custom roms and install them fine in the recovery but the result is always bootloop. Any ideas on how to fix this? Thanks.

if you are on S-ON just flash the boot.img of the rom via fastboot
otherwise if you have 4ext recovery enable smartflash exactly before flashing the rom
 

razor26

Senior Member
My Sensation is on S-off. I cannot try the smartflash because I already resort to use my external sdcard as /data and successfully boot CM12, I'm in fear of messing my phone again. However, I wish there will be a fix soon.
 

Mitster2015

Member
Nov 24, 2015
12
0
I'm in the same boat. I have oveelapping partitions so I'm pretty much stuck. Surely there must be a way to reflash all partitions to stock? Ive tried everything from 4ext to ruu restore and nothing. I would rather not rely on an external sd card seeing as I have an internal one :)

I have managed to pull this out. I cannot see any overlapping partitions, but I keep getting it when trying to use parted to format. Anyone able to assist? I think that once I have the overlapping partitions issue resolved, I should hopefully be able to progress...fingers crossed.

C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6nfdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60

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

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 256 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 257 768 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 769 65502 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 65503 4718590 2326544 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 65504 65535 16 5a Unknown
/dev/block/mmcblk0p6 65537 66048 256 73 Unknown
/dev/block/mmcblk0p7 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p8 106936 107447 256 0 Empty
/dev/block/mmcblk0p9 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p10 109498 110009 256 47 Unknown
/dev/block/mmcblk0p11 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p12 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p13 116157 116220 32 0 Empty
/dev/block/mmcblk0p14 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p15 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p16 130560 131071 256 76 Unknown
/dev/block/mmcblk0p17 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p18 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p19 229376 262143 16384 0 Empty
/dev/block/mmcblk0p20 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p21 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p22 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p23 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p24 4412899 4658576 122839 83 Linux
/dev/block/mmcblk0p25 4658578 4658641 32 90 Unknown
/dev/block/mmcblk0p26 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p27 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p28 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p29 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p30 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p31 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p32 4716545 4718589 1022+ 76 Unknown
/dev/block/mmcblk0p33 65504 65535 16 5a Unknown
/dev/block/mmcblk0p34 65537 66048 256 73 Unknown
/dev/block/mmcblk0p35 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p36 106936 107447 256 0 Empty
/dev/block/mmcblk0p37 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p38 109498 110009 256 47 Unknown
/dev/block/mmcblk0p39 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p40 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p41 116157 116220 32 0 Empty
/dev/block/mmcblk0p42 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p43 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p44 130560 131071 256 76 Unknown
/dev/block/mmcblk0p45 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p46 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p47 229376 262143 16384 0 Empty
/dev/block/mmcblk0p48 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p49 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p50 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p51 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p52 4412899 4658576 122839 83 Linux
/dev/block/mmcblk0p53 4658578 4658641 32 90 Unknown
/dev/block/mmcblk0p54 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p55 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p56 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p57 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p58 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p59 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p60 4716545 4718589 1022+ 76 Unknown

Partition table entries are not in disk order
~ # ←[6nfdisk
BusyBox v1.22.1 bionic (2015-03-25 05:34 +0000) multi-call binary.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    yeah you are right
    some partitions are broken probably from TWRP because a lot of users faced issues similar with yours

    someone posted a solution few days ago how to boot a rom from sdcard
    he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
    he created two partitions
    one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
    but i can't find that post
    if i find it i will come with edit

    Yes, I managed to boot my sensation from SD card by moving both /system and /data partition using a patched boot.img and modified rom install script...

    Here is the link to the thread:http://xdaforums.com/htc-sensation/help/recovering-data-mount-issues-t2859588

    Posted in Q&A as I didn't had privileges.

    PS: I have to add some e2fsck commands as well as after some time the log starts showing warnings on mounts in the log but phone working ok.
    1
    here is the latest version of 4ext
    http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
    extract the recovery.img and flash it via fastboot command

    but probably your emmc is corrupted unfortunately:(

    by the way did you try a ruu.exe?
    tried ruu exe but nth happened,cant find the device,and cant fastboot
    1
    Seems like I have attached the wrong updater-script with the thread. Try the one that is attached to this. Please note the ext is .txt as edited in notepad(in office at the moment).

    Use the attached boot.img as well... Once you confirm success, i will update my original post with the new files.