Okay so i have been looking all over the forums for help with my issue for the last like 6 hours and i have found stuff that is relevant but i have a weird twist.
I was installing google voice on the latest miui build for the t-mobile G2 and the device froze soo I restarted it causing this nightmare to begin.
I can not get back into android the phone freezes on the HTC screen, however i can get into fastboot which I can then use to get into clockworkmod recovery. At that point however I run into a problem, clockworkmod recovery can't mount anything including my SD card. I tried reformatting the card in clockworkmod and outside of it and no go. My device is S-OFF and when its in fastboot i can connect it to my computer and execute fastboot commands but i don't have a nandroid backup to recover the img files from for a manual reinstall from fastboot.
Any information i can give you to help i will try to get and if i am confused about something please correct me I am kinda new to all of this so I could very easily be confused about something.
[Solution]
Yay I fixed it! Well kinda... I figured out a work around for the emmc problem using an SD card to take its place.
Okay so the break down of the problem was that my phone would not boot into android but i still had clockworkmod and fast boot. When I went into clockworkmod I got the cache errors and it couldnt mount anything including my SD card. If i adb into the device from clockworkmod and typed:
cd ls /dev/block/
i got this if i didnt have an sdcard
loop0 loop2 loop4 loop6 platform
loop1 loop3 loop5 loop7
and when i did have one in i got this
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p1
~ # cat /proc/kmsg | grep mmc0
came up with this
<3>[ 4.155456] mmc0: No card detect facilities available
<6>[ 4.156005] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 4.156280] mmc0: Platform slot type: MMC
<6>[ 4.156402] mmc0: 4 bit data mode disabled
<6>[ 4.156646] mmc0: 8 bit data mode enabled
<6>[ 4.156799] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.157043] mmc0: Slot eject status = 0
<6>[ 4.157165] mmc0: Power save feature enable = 1
<6>[ 4.157318] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2ae95000
<6>[ 4.157562] mmc0: DM cmd busaddr 0x2ae95000, cmdptr busaddr 0x2ae95300
<3>[ 4.279235] mmc0: error -110 whilst initialising MMC card
and i was basically told that the eMMC went was busted and i was screwed but then i found this: http://tjworld.net/wiki/Android/HTC/Vision/LinuxAnalysis
Its basically a break down of the partition tables of the eMMC and when i saw that the block name for the eMMC was the same as what my SD card was showing up as in the /dev/block directory i decided to attempt to recreate the partition table for the eMMC on my SD card and see if i could use it as a eMMC replacement
So i went back into the device with adb typed 'fdisk /dev/block/mmcblk0' deleted the current partition and started to recreate the partition tables on my sd card exactly like they were on the eMMC. My SDCard partition table looks like this:
Disk /dev/block/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 16 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 16 18 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 18 159 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 159 242560 7756840+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 159 1097 30000 49 Unknown
/dev/block/mmcblk0p6 1097 1487 12500 50 Unknown
/dev/block/mmcblk0p7 1488 1552 2048 51 Unknown
/dev/block/mmcblk0p8 1552 1648 3072 52 Unknown
/dev/block/mmcblk0p9 1648 1712 2048 53 Unknown
/dev/block/mmcblk0p10 1712 1744 1024 54 Unknown
/dev/block/mmcblk0p11 1744 1776 1024 56 Unknown
/dev/block/mmcblk0p12 1776 2050 8751+ 55 Unknown
/dev/block/mmcblk0p13 2050 2146 3072 4a Unknown
/dev/block/mmcblk0p14 2146 2242 3072 4b Unknown
/dev/block/mmcblk0p15 2242 2274 1024 74 Unknown
/dev/block/mmcblk0p16 2274 2554 8957+ 75 Unknown
/dev/block/mmcblk0p17 2554 2562 256 76 Unknown
/dev/block/mmcblk0p18 2563 2595 1024 47 Unknown
/dev/block/mmcblk0p19 2595 2627 1024 34 Unknown
/dev/block/mmcblk0p20 2627 2667 1280 36 Unknown
/dev/block/mmcblk0p21 2667 2939 8701 71 Unknown
/dev/block/mmcblk0p22 2939 3067 4096 48 Unknown
/dev/block/mmcblk0p23 3067 3075 256 73 Unknown
/dev/block/mmcblk0p24 3076 3084 256 31 Unknown
/dev/block/mmcblk0p25 3084 16388 425726+ 83 Linux
/dev/block/mmcblk0p26 16388 58948 1361920+ 83 Linux
/dev/block/mmcblk0p27 58948 65502 209715+ 83 Linux
/dev/block/mmcblk0p28 65502 66142 20480 19 Unknown
Then I ran the following commands:
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
at this point i was able to mount the system, cache, and data directories from clockworkmod which was all good but i didnt have any android rom installed on any of these directories and at this point my sd card was being used as the main drive for the phone so clockworkmod couldnt mount it and i had no way to load a rom from it...
Soo... back into adb and i ran 'fdisk /dev/block/mmcblk0' and added another partion to the table that was 1gb in size and marked as fat32. Then on my computer made an image an sd card pushed it to the device and ran 'dd if=/data/sdcard.img of=/dev/block/mmcblk0p29' then 'mount /dev/block/mmcblk0p29 /sdcard' and wala clockworkmod detects the SD Card partition. I pushed down the cyanogenmod rom to the now mounted SD Card partition go to clockworkmod and install the zip file from there and reboot the device.
The end result is that my phone doesnt recognize that there is an SD Card pluged in because its using it as if it was the eMMC but it works! im back up and running again!
I know this is all jumbled when i get more time i will go through and try to clean it up and make the instructions a little more straight forward but i hope this helps some of you out there with bricked G2s... apparently it is possible to use your sdcard as a eMMC replacement
CollegeBound1987 said:
Okay so i have been looking all over the forums for help with my issue for the last like 6 hours and i have found stuff that is relevant but i have a weird twist.
I was installing google voice on the latest miui build for the t-mobile G2 and the device froze soo I restarted it causing this nightmare to begin.
I can not get back into android the phone freezes on the HTC screen, however i can get into fastboot which I can then use to get into clockworkmod recovery. At that point however I run into a problem, clockworkmod recovery can't mount anything including my SD card. I tried reformatting the card in clockworkmod and outside of it and no go. My device is S-OFF and when its in fastboot i can connect it to my computer and execute fastboot commands but i don't have a nandroid backup to recover the img files from for a manual reinstall from fastboot.
Any information i can give you to help i will try to get and if i am confused about something please correct me I am kinda new to all of this so I could very easily be confused about something.
Click to expand...
Click to collapse
Are you saying you don't have a nandroid at all? You can always flash a new recovery image via fastboot using the command:
Code:
fastboot flash recovery <path to recovery image>recovery.img
From there you can reboot into recovery via fastboot (fastboot reboot recovery) and then you should be able to flash a ROM or restore a backup (if you've got one).
I would recommend trying 4EXT Recovery by Madmaxx82. It's based on CWM, but has more options and great support. Here's the thread: http://forum.xda-developers.com/showthread.php?t=1377754
Ditamae said:
Are you saying you don't have a nandroid at all? You can always flash a new recovery image via fastboot using the command:
Code:
fastboot flash recovery <path to recovery image>recovery.img
From there you can reboot into recovery via fastboot (fastboot reboot recovery) and then you should be able to flash a ROM or restore a backup (if you've got one).
I would recommend trying 4EXT Recovery by Madmaxx82. It's based on CWM, but has more options and great support. Here's the thread: http://forum.xda-developers.com/showthread.php?t=1377754
Click to expand...
Click to collapse
i already tried to flash a new recovery image but it was just a reflash of CWM which seems to be unable to mount anything on the device including the sd card which will mount in fastboot. I didnt however know that there was an alternative recovery image i will give that a try see if i have any better luck.
this is what i keep getting i tried to install the img file in the zip and the zip itself neither seemed to work
Julies-MacBook-Pro:~ Julie$ /Users/Julie/Desktop/android-sdk-macosx/platform-tools/fastboot flash recovery /Users/Julie/Downloads/vision_pre_rc1_testing/recovery.img
sending 'recovery' (5158 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Julies-MacBook-Pro:~ Julie$ /Users/Julie/Desktop/android-sdk-macosx/platform-tools/fastboot flash recovery /Users/Julie/Downloads/vision_pre_rc1_testing.zipsending 'recovery' (5305 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Julies-MacBook-Pro:~ Julie$
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
download the cwm recovery.img from the link and try again (3.0.2.4 is very stable)...
did you try to insert a different sdcard? maybe your sdcard is broken and it has nothing to do with recovery...
CollegeBound1987 said:
Okay so i have been looking all over the forums for help with my issue for the last like 6 hours and i have found stuff that is relevant but i have a weird twist.
I was installing google voice on the latest miui build for the t-mobile G2 and the device froze soo I restarted it causing this nightmare to begin.
I can not get back into android the phone freezes on the HTC screen, however i can get into fastboot which I can then use to get into clockworkmod recovery. At that point however I run into a problem, clockworkmod recovery can't mount anything including my SD card. I tried reformatting the card in clockworkmod and outside of it and no go. My device is S-OFF and when its in fastboot i can connect it to my computer and execute fastboot commands but i don't have a nandroid backup to recover the img files from for a manual reinstall from fastboot.
Any information i can give you to help i will try to get and if i am confused about something please correct me I am kinda new to all of this so I could very easily be confused about something.
Click to expand...
Click to collapse
Have you read this particular thread?
http://forum.xda-developers.com/showthread.php?t=1039504&page=2
Ditamae said:
Have you read this particular thread?
http://forum.xda-developers.com/showthread.php?t=1039504&page=2
Click to expand...
Click to collapse
i run into this error
md5sum: can't open '/dev/block/mmcblk0p27': No such file or director
~ # cd /dev/block/
/dev/block # ls
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p1
"adb shell ls /dev/block" whats your output? are the partitions listed?
http://forum.xda-developers.com/showpost.php?p=13895268&;postcount=48
to check your emmc
hoffmas said:
"adb shell ls /dev/block" whats your output? are the partitions listed?
http://forum.xda-developers.com/showpost.php?p=13895268&;postcount=48
to check your emmc
Click to expand...
Click to collapse
Julies-MacBook-Prolatform-tools Julie$ /Users/Julie/Desktop/android-sdk-macosx/platform-tools/adb shell ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p1
~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
cat: can't open '/sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name': No such file or directory
~ # cat /proc/kmsg | grep mmc0
<3>[ 4.155456] mmc0: No card detect facilities available
<6>[ 4.156005] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 4.156280] mmc0: Platform slot type: MMC
<6>[ 4.156402] mmc0: 4 bit data mode disabled
<6>[ 4.156646] mmc0: 8 bit data mode enabled
<6>[ 4.156799] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.157043] mmc0: Slot eject status = 0
<6>[ 4.157165] mmc0: Power save feature enable = 1
<6>[ 4.157318] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2ae95000
<6>[ 4.157562] mmc0: DM cmd busaddr 0x2ae95000, cmdptr busaddr 0x2ae95300
<3>[ 4.279235] mmc0: error -110 whilst initialising MMC card
CollegeBound1987 said:
<3>[ 4.279235] mmc0: error -110 whilst initialising MMC card
Click to expand...
Click to collapse
hm doesn´t look good... but to be sure i would swap to http://webchat.freenode.net/?channels=g2root and post is there again...
my knowledge is not good enough to go further
i think the issue has something to do with the missing block partitions is there anyway to recreate them?
Brick phone fix
I found a fix/workaround using an SD Card as an eMMC replacement i posted the information in the first post i hope this helps some of you peoples out there with bricked phones
That's incredible work there. Too bad about the sd but at least you didn't have to buy a new phone!
i figure that i could make one of the user partitions larger so that the phone can utilize the 8gb card it will just think its internal storage
good to hear
...but how is the performance? i can imagine you won´t be able to run sense roms anymore, or am i wrong?
hoffmas said:
good to hear
...but how is the performance? i can imagine you won´t be able to run sense roms anymore, or am i wrong?
Click to expand...
Click to collapse
I am currently running miui with out much of a problem but it does hang a little when its installing programs from the market place and programs like titanium backup and rom manager dont seem to work on the device because it doesnt recognize that you have an sd card in but i am trying to find a fix for that right now...
Is there any way I can do this as my emmc works just it dosnt detect my sdcard wen its plugged in. But in my storage settings it jus gives me the option to erase the sdcard and that's it so if I can do wat you did but just reversed to push the sdcard pation to my emmc so that it can read my actual sd card or try this link I fount to recreat the partions. And flash them with this tool http://faq.riffbox.org/index.php?action=artikel&cat=10&id=53&artlang=en just I dnt kno how to use it ...yu know
Sent from my T-Mobile G2 using XDA
~ # fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
This is what I keep getting in adb.
Any help? I tried your way but it's soo difficult for me.
Mb a step by step procedure. I really think this is the only way to solve the emmc problem we have.
raza1 said:
~ # fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
This is what I keep getting in adb.
Any help? I tried your way but it's soo difficult for me.
Mb a step by step procedure. I really think this is the only way to solve the emmc problem we have.
Click to expand...
Click to collapse
I thought fdisk only applies to FAT partitions (fat32, etc).
what about this instead :
busybox df -hm
For example on my phone that would show:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 183.2M 60.0K 183.1M 0% /dev
tmpfs 183.2M 0 183.2M 0% /mnt/asec
tmpfs 183.2M 0 183.2M 0% /mnt/obb
/dev/block/mmcblk0p25
549.2M 245.2M 304.0M 45% /system
/dev/block/mmcblk0p26
1.0G 414.1M 659.7M 39% /data
/dev/block/mmcblk0p27
295.3M 4.7M 290.5M 2% /cache
/dev/block/mmcblk0p28
20.6M 12.6M 8.0M 61% /devlog
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /sd-ext
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app-private
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/sdcard
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/secure/asec
Edit: though I tried fdisk myself (I'm currently booted into the phone though, not sure if you're calling that from recovery or what)
Code:
[email protected]:/ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275200.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2254 MB, 2254438400 bytes
1 heads, 16 sectors/track, 275200 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------
Gave it a shot under 4EXT recovery as well, shows output (numbers slightly different than when in boot, but close)
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275456.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2256 MB, 2256535552 bytes
1 heads, 16 sectors/track, 275456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
Command (m for help):
If it can't read the eMMC block at all, then quite possibly it's dead/corupt, and there ain't no coming back from that.
kbeezie said:
I thought fdisk only applies to FAT partitions (fat32, etc).
what about this instead :
busybox df -hm
For example on my phone that would show:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 183.2M 60.0K 183.1M 0% /dev
tmpfs 183.2M 0 183.2M 0% /mnt/asec
tmpfs 183.2M 0 183.2M 0% /mnt/obb
/dev/block/mmcblk0p25
549.2M 245.2M 304.0M 45% /system
/dev/block/mmcblk0p26
1.0G 414.1M 659.7M 39% /data
/dev/block/mmcblk0p27
295.3M 4.7M 290.5M 2% /cache
/dev/block/mmcblk0p28
20.6M 12.6M 8.0M 61% /devlog
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /sd-ext
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app-private
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/sdcard
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/secure/asec
Edit: though I tried fdisk myself (I'm currently booted into the phone though, not sure if you're calling that from recovery or what)
Code:
[email protected]:/ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275200.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2254 MB, 2254438400 bytes
1 heads, 16 sectors/track, 275200 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------
Gave it a shot under 4EXT recovery as well, shows output (numbers slightly different than when in boot, but close)
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275456.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2256 MB, 2256535552 bytes
1 heads, 16 sectors/track, 275456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
Command (m for help):
If it can't read the eMMC block at all, then quite possibly it's dead/corupt, and there ain't no coming back from that.
Click to expand...
Click to collapse
Yeah I think I have to replace the 'motherboard' totally with one out off a phone with a broken glass or something.
I'll keep searching for a software solution first.
My Desire HD is running CyanogenMod 7.0.3 and was working fine until recently. I ahve HBoot-0.85.2007 Radio-26.08.03.07_M installed. It shows ACE PVT ENG S-OFF in the bootloader.
I wanted to update to CyanogenMod 7.1.0 when my problems started. I used RomManager for the upgrade, but when the phone restarted I ran into the 7 vibrates in the HTC Logo. I pulled out the battery, put it back in and the device booted fine, but again with CyanogenMod 7.0.3.
The problem is that always when I try to do a restart of the device I get the 7 vibrates on the HTC Logo. I need to turn off the device completely or pull the battery and then start the device again to get into Android.
When I install a new App on the device or if I uninstall an app I already have on it, it seems to be doing what it should. I am able to use the app, or the uninstalled app really disappears. But after turning the device off and back on the new Apps are missing and the uninstalled Apps are there again.
When I try to flash a different Recovery system (currently using ClockworkMod 5.0.2.0) in the bootloader the feedback is that the flash was successful. But when I enter the recovery mode I always end up with my old ClockworkMod 5.0.2.0. I tried flashing newer versions of Clockwork and I tried 4EXT, but it just doesn't work.
Whatever I change on the phone seems to only last until I turn the device off. After turning it back on I am always getting back the state of the phone from 1 week ago.
Does anyone have any idea what might be the issue here?
Edit: I was looking around for some reason that this issue occurs. When I run fdisk -l /dev/block/mmcblk0 I get the following:
Code:
fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 284672 2272311 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 234368 1203199+ 83 Linux
/dev/block/mmcblk0p27 234369 272768 307199+ 83 Linux
/dev/block/mmcblk0p28 272769 275424 21247+ 19 Unknown
/dev/block/mmcblk0p29 275425 275456 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 234368 1203199+ 83 Linux
/dev/block/mmcblk0p52 234369 272768 307199+ 83 Linux
/dev/block/mmcblk0p53 272769 275424 21247+ 19 Unknown
/dev/block/mmcblk0p54 275425 275456 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
IlyaKol said:
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
Click to expand...
Click to collapse
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
macdaddie87 said:
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
Click to expand...
Click to collapse
I'm a system engineer (server support, etc.) so I should be able to handle it. Just needed to be pointed in the right direction. I shall post up tomorrow.
macdaddie87 said:
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Click to expand...
Click to collapse
Scratch that, evidently root is only available for the EU H815 and mine is the Taiwan one, from what I know. I'll see if I get lucky somehow, but by the looks of it I won't be able to provide the dump since I can't achieve root.
Some help
http://forum.xda-developers.com/g4/development/rom-docs-testrom-t3126728
Code:
major minor #blocks name
253 0 721772 zram0
179 0 30535680 mmcblk0
179 1 88064 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 1536 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 2048 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 49152 mmcblk0p37
259 6 40960 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 8192 mmcblk0p40
259 9 8192 mmcblk0p41
259 10 32768 mmcblk0p42
259 11 47104 mmcblk0p43
259 12 10240 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 4096 mmcblk0p46
259 15 4239360 mmcblk0p47
259 16 262144 mmcblk0p48
259 17 1261568 mmcblk0p49
259 18 24313856 mmcblk0p50
259 19 12271 mmcblk0p51
179 32 4096 mmcblk0rpmb
DDR -> /dev/block/mmcblk0p30
aboot -> /dev/block/mmcblk0p8
abootbak -> /dev/block/mmcblk0p14
apdp -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p38
cache -> /dev/block/mmcblk0p49
cust -> /dev/block/mmcblk0p48
devinfo -> /dev/block/mmcblk0p17
po -> /dev/block/mmcblk0p20
drm -> /dev/block/mmcblk0p40
eksst -> /dev/block/mmcblk0p33
encrypt -> /dev/block/mmcblk0p32
factory -> /dev/block/mmcblk0p43
fota -> /dev/block/mmcblk0p44
fsc -> /dev/block/mmcblk0p27
fsg -> /dev/block/mmcblk0p26
grow -> /dev/block/mmcblk0p51
hyp -> /dev/block/mmcblk0p6
hypbak -> /dev/block/mmcblk0p12
keystore -> /dev/block/mmcblk0p29
laf -> /dev/block/mmcblk0p37
limits -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p24
modemst2 -> /dev/block/mmcblk0p25
mpt -> /dev/block/mmcblk0p42
msadp -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p23
pmic -> /dev/block/mmcblk0p2
pmicbak -> /dev/block/mmcblk0p10
raw_resources -> /dev/block/mmcblk0p45
raw_resourcesbak -> /dev/block/mmcblk0p46
rct -> /dev/block/mmcblk0p34
recovery -> /dev/block/mmcblk0p39
rpm -> /dev/block/mmcblk0p7
rpmbak -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sbl1bak -> /dev/block/mmcblk0p9
sdi -> /dev/block/mmcblk0p5
sdibak -> /dev/block/mmcblk0p15
sec -> /dev/block/mmcblk0p31
sns -> /dev/block/mmcblk0p41
spare1 -> /dev/block/mmcblk0p21
spare2 -> /dev/block/mmcblk0p36
ssd -> /dev/block/mmcblk0p28
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p4
tzbak -> /dev/block/mmcblk0p11
userdata -> /dev/block/mmcblk0p50
I can't unlock the BL as I'm a TW phone not an EU phone. Sorry OP.
Code:
HWANE:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
254 0 2293760 zram0
179 0 61071360 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 2048 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 61440 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 2048 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 12288 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 24576 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 32768 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 28672 mmcblk0p34
179 35 4096 mmcblk0p35
179 36 98304 mmcblk0p36
179 37 1024 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 2048 mmcblk0p39
179 40 16384 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 131072 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 2048 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 4096 mmcblk0p46
179 47 32768 mmcblk0p47
259 0 2048 mmcblk0p48
259 1 16384 mmcblk0p49
259 2 14336 mmcblk0p50
259 3 5767168 mmcblk0p51
259 4 196608 mmcblk0p52
259 5 32768 mmcblk0p53
259 6 802816 mmcblk0p54
259 7 196608 mmcblk0p55
259 8 53043200 mmcblk0p56
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
179 192 62367744 mmcblk1
179 193 62366720 mmcblk1p1
253 0 4724684 dm-0
253 1 790064 dm-1
253 2 128924 dm-2
253 3 32172 dm-3
253 4 193424 dm-4
253 5 193424 dm-5
Code:
HWANE:/ $ ls -l /dev/block/platform/hi_mci.0/by-name/
[I][B]User friendly display[/B][/I]
/dev/block/mmcblk0p48 -> bootfail_info
/dev/block/mmcblk0p42 -> cache
/dev/block/mmcblk0p52 -> cust
/dev/block/mmcblk0p40 -> dfx
/dev/block/mmcblk0p35 -> dto
/dev/block/mmcblk0p34 -> dts
/dev/block/mmcblk0p27 -> erecovery_kernel
/dev/block/mmcblk0p28 -> erecovery_ramdisk
/dev/block/mmcblk0p38 -> erecovery_vbmeta
/dev/block/mmcblk0p29 -> erecovery_vendor
/dev/block/mmcblk0p5 -> fastboot
/dev/block/mmcblk0p4 -> frp
/dev/block/mmcblk0p26 -> fw_hifi
/dev/block/mmcblk0p3 -> fw_lpm3
/dev/block/mmcblk0p44 -> hisitest0
/dev/block/mmcblk0p45 -> hisitest1
/dev/block/mmcblk0p46 -> hisitest2
/dev/block/mmcblk0p30 -> kernel
/dev/block/mmcblk0p20 -> misc
/dev/block/mmcblk0p36 -> modem_fw
/dev/block/mmcblk0p18 -> modem_om
/dev/block/mmcblk0p17 -> modem_secure
/dev/block/mmcblk0p10 -> modemnvm_backup
/dev/block/mmcblk0p6 -> modemnvm_factory
/dev/block/mmcblk0p11 -> modemnvm_img
/dev/block/mmcblk0p12 -> modemnvm_system
/dev/block/mmcblk0p21 -> modemnvm_update
/dev/block/mmcblk0p7 -> nvme
/dev/block/mmcblk0p43 -> odm
/dev/block/mmcblk0p8 -> oeminfo
/dev/block/mmcblk0p47 -> patch
/dev/block/mmcblk0p16 -> persist
/dev/block/mmcblk0p55 -> product
/dev/block/mmcblk0p31 -> ramdisk
/dev/block/mmcblk0p32 -> recovery_ramdisk
/dev/block/mmcblk0p37 -> recovery_vbmeta
/dev/block/mmcblk0p33 -> recovery_vendor
/dev/block/mmcblk0p22 -> reserved2
/dev/block/mmcblk0p9 -> reserved3
/dev/block/mmcblk0p14 -> reserved4
/dev/block/mmcblk0p15 -> reserved5
/dev/block/mmcblk0p39 -> reserved8
/dev/block/mmcblk0p50 -> reserved9
/dev/block/mmcblk0p49 -> rrecord
/dev/block/mmcblk0p13 -> secure_storage
/dev/block/mmcblk0p25 -> sensorhub
/dev/block/mmcblk0p19 -> splash2
/dev/block/mmcblk0p51 -> system
/dev/block/mmcblk0p23 -> teeos
/dev/block/mmcblk0p24 -> trustfirmware
/dev/block/mmcblk0p56 -> userdata
/dev/block/mmcblk0p41 -> vbmeta
/dev/block/mmcblk0p54 -> vendor
/dev/block/mmcblk0p53 -> version
/dev/block/mmcblk0p1 -> vrl
/dev/block/mmcblk0p2 -> vrl_backup
Hello,
I want to flash a firmware for downgrade.
How i can make it without a dload method?
I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Yes me to dload not downgrade
Gesendet von meinem ANE-LX1 mit Tapatalk
Manflack said:
Hello,
I want to flash a firmware for downgrade.
How i can make it without a dload method?
I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Click to expand...
Click to collapse
SirusX said:
Yes me to dload not downgrade
Gesendet von meinem ANE-LX1 mit Tapatalk
Click to expand...
Click to collapse
This is a partition layout it can't help you with downgrade.
To downgrade without brick the phone you have to find a roll back firmware. In the picture is an example for p20 pro.
Hi all!
I cant open thread in other channel so i post here. sorry about it.
I've compiled a custom kernel for Samsung S9, but the kernel is bigger than the BOOT partition size. I want to create a new partition (over USERDATA partition) and boot from the new one.
This is the initial GPT /dev/block/sda partition:
Code:
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2677 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 15614335 53.1 GiB 0700 USERDATA
I've tried to re-partition /dev/block/sda with sgdisk like this:
Code:
~ # sgdisk --delete 25 /dev/block/sda
~ # sgdisk --new 25:1697152:1716972 /dev/block/sda
~ # sgdisk --change-name 25:BOOT2 /dev/block/sda
~ # sgdisk --typecode 25:0700 /dev/block/sda
~ # sgdisk --new 26:1716973:15614335 /dev/block/sda
~ # sgdisk --change-name 26:USERDATA /dev/block/sda
~ # sgdisk --typecode 26:0700 /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2678 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT2
26 1716974 15614335 53.0 GiB 0700 USERDATA
~ # exit
~ adb reboot recovery
~ adb wait-for-any && adb shell
~ # ~ # ls /dev/block/platform/11120000.ufs/by-name/ -la
drwxr-xr-x 2 root root 580 Nov 19 15:32 .
drwxr-xr-x 4 root root 720 Nov 19 15:32 ..
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT2 -> /dev/block/sda25
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CACHE -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 Nov 19 15:32 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CP_DEBUG -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 Nov 19 15:32 DQMDBG -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTB -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTBO -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Nov 19 15:32 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Nov 19 15:32 HIDDEN -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 Nov 19 15:32 KEYSTORAGE -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Nov 19 15:32 MISC -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Nov 19 15:32 NAD_REFER -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Nov 19 15:32 ODM -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 Nov 19 15:32 OMR -> /dev/block/sda23
lrwxrwxrwx 1 root root 15 Nov 19 15:32 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Nov 19 15:32 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RADIO -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RECOVERY -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Nov 19 15:32 STEADY -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Nov 19 15:32 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 Nov 19 15:32 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Nov 19 15:32 USERDATA -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 Nov 19 15:32 VENDOR -> /dev/block/sda19
~ # dd if=newboot.img of=/dev/block/sda25
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 7CE83C10-10C6-4E3D-A6B4-92B66586A716
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --partition-guid=10:R /dev/block/sda
~ # sgdisk --partition-guid=25:52444E41-494F-2044-424F-4F5400000000 /dev/block/sda
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 6F5BCACB-2AF9-4F16-B2A3-B4B12085EB8F
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --change-name 10:BOOT1 /dev/block/sda
~ # sgdisk --change-name 25:BOOT /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 13900040 sectors (53.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT1
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT
~ # exit
~ adb reboot
By this process I've written my custom boot image on the new BOOT partition, and replaced both the partition name and GUID with the original BOOT partition's.
After this, the phone still boots the real image (verified with /proc/version). What am I missing here?
I've also tried writing the original boot image to the new boot partition and zero out the original boot partition (sda10) to see what happens and the device didn't boot.
DuduFaruk said:
Hi all!
I cant open thread in other channel so i post here. sorry about it.
I've compiled a custom kernel for Samsung S9, but the kernel is bigger than the BOOT partition size. I want to create a new partition (over USERDATA partition) and boot from the new one.
This is the initial GPT /dev/block/sda partition:
Code:
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2677 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 15614335 53.1 GiB 0700 USERDATA
I've tried to re-partition /dev/block/sda with sgdisk like this:
Code:
~ # sgdisk --delete 25 /dev/block/sda
~ # sgdisk --new 25:1697152:1716972 /dev/block/sda
~ # sgdisk --change-name 25:BOOT2 /dev/block/sda
~ # sgdisk --typecode 25:0700 /dev/block/sda
~ # sgdisk --new 26:1716973:15614335 /dev/block/sda
~ # sgdisk --change-name 26:USERDATA /dev/block/sda
~ # sgdisk --typecode 26:0700 /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 2678 sectors (10.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT2
26 1716974 15614335 53.0 GiB 0700 USERDATA
~ # exit
~ adb reboot recovery
~ adb wait-for-any && adb shell
~ # ~ # ls /dev/block/platform/11120000.ufs/by-name/ -la
drwxr-xr-x 2 root root 580 Nov 19 15:32 .
drwxr-xr-x 4 root root 720 Nov 19 15:32 ..
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 Nov 19 15:32 BOOT2 -> /dev/block/sda25
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 Nov 19 15:32 BOTA2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CACHE -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 Nov 19 15:32 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Nov 19 15:32 CP_DEBUG -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 Nov 19 15:32 DQMDBG -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTB -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Nov 19 15:32 DTBO -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 Nov 19 15:32 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Nov 19 15:32 HIDDEN -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 Nov 19 15:32 KEYSTORAGE -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Nov 19 15:32 MISC -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Nov 19 15:32 NAD_REFER -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Nov 19 15:32 ODM -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 Nov 19 15:32 OMR -> /dev/block/sda23
lrwxrwxrwx 1 root root 15 Nov 19 15:32 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Nov 19 15:32 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RADIO -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Nov 19 15:32 RECOVERY -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Nov 19 15:32 STEADY -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Nov 19 15:32 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 Nov 19 15:32 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Nov 19 15:32 USERDATA -> /dev/block/sda26
lrwxrwxrwx 1 root root 16 Nov 19 15:32 VENDOR -> /dev/block/sda19
~ # dd if=newboot.img of=/dev/block/sda25
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 7CE83C10-10C6-4E3D-A6B4-92B66586A716
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --partition-guid=10:R /dev/block/sda
~ # sgdisk --partition-guid=25:52444E41-494F-2044-424F-4F5400000000 /dev/block/sda
~ # sgdisk --info=10 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 6F5BCACB-2AF9-4F16-B2A3-B4B12085EB8F
First sector: 19458 (at 76.0 MiB)
Last sector: 33537 (at 131.0 MiB)
Partition size: 14080 sectors (55.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT'
~ # sgdisk --info=25 /dev/block/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 52444E41-494F-2044-424F-4F5400000000
First sector: 1697152 (at 6.5 GiB)
Last sector: 1716972 (at 6.5 GiB)
Partition size: 19821 sectors (77.4 MiB)
Attribute flags: 0000000000000000
Partition name: 'BOOT2'
~ # sgdisk --change-name 10:BOOT1 /dev/block/sda
~ # sgdisk --change-name 25:BOOT /dev/block/sda
~ # sgdisk --print /dev/block/sda
Disk /dev/block/sda: 15616000 sectors, 59.6 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 52444E41-494F-2044-4D4D-43204449534B
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15615994
Partitions will be aligned on 2-sector boundaries
Total free space is 13900040 sectors (53.0 GiB)
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4.0 MiB 0700 BOTA0
2 2048 4095 8.0 MiB 0700 BOTA1
3 4096 9215 20.0 MiB 0700 EFS
4 9216 11263 8.0 MiB 0700 PARAM
5 11264 13311 8.0 MiB 0700 UP_PARAM
6 13312 13313 8.0 KiB 0700 KEYSTORAGE
7 13314 15361 8.0 MiB 0700 BOTA2
8 15362 17409 8.0 MiB 0700 DTB
9 17410 19457 8.0 MiB 0700 DTBO
10 19458 33537 55.0 MiB 0700 BOOT1
11 33538 50175 65.0 MiB 0700 RECOVERY
12 50176 62975 50.0 MiB 0700 RADIO
13 62976 63231 1024.0 KiB 0700 NAD_REFER
14 63232 63359 512.0 KiB 0700 PERSISTENT
15 63360 63615 1024.0 KiB 0700 MISC
16 63616 64639 4.0 MiB 0700 STEADY
17 64640 68735 16.0 MiB 0700 DQMDBG
18 68736 1195135 4.3 GiB 0700 SYSTEM
19 1195136 1361535 650.0 MiB 0700 VENDOR
20 1361536 1526911 646.0 MiB 0700 ODM
21 1526912 1680511 600.0 MiB 0700 CACHE
22 1680512 1683071 10.0 MiB 0700 HIDDEN
23 1683072 1695871 50.0 MiB 0700 OMR
24 1695872 1697151 5.0 MiB 0700 CP_DEBUG
25 1697152 1716972 77.4 MiB 0700 BOOT
~ # exit
~ adb reboot
By this process I've written my custom boot image on the new BOOT partition, and replaced both the partition name and GUID with the original BOOT partition's.
After this, the phone still boots the real image (verified with /proc/version). What am I missing here?
I've also tried writing the original boot image to the new boot partition and zero out the original boot partition (sda10) to see what happens and the device didn't boot.
Click to expand...
Click to collapse
you might need the big guns for this issue. @AthieN you got any words of wisdom for this?
For those who will experience it in the future.
After I reversed S-Boot I notice the bootloader load partition from internal PIT file and the boot section in the GPT is not connected to the boot order.