Database Info

32 Gb PIT file

I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
EDIT:
Problem solved: See post#57

Bump
Sent from my SCH-I535 using xda app-developers app

letinsh said:
I am in need of the PIT file for a SCH-I535 32Gb version.
Anyone willing/able to rip one for me? My 32Gb phone got JTAG'd back to life but using files from a 16Gb version, so it's kinda confused as to how much internal storage it has. I'm hoping I can flash the PIT from a 32Gb phone, then do a reinstall of the ROM and it'll recognize all of my available storage....
Thanks for your help!
-Andy
Click to expand...
Click to collapse
do you have a pit from the 16 gb version

man that would be great if somebody would post a pitfile for both versions...I know that would help a few folks that corrupted thier emmc internal memory and get the "e cant mount" errors in recovery.

I am game ... how would I extract the PIT file?
Sent from my SCH-I535 using xda premium

Standby. Getting confirmation, then I'll post instructions.
Sent from my SCH-I535 using xda app-developers app

bump...

il gladly dump my 32gb blue if there's instructions.

here is some info from the i9300 forum
http://forum.xda-developers.com/showthread.php?t=1742668

What I'm trying to get confirmation on is using darkyy's dd command from the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=960946
Just trying to verify that's the correct place to get it for the SGS3 and that that would produce a flashable .pit file.
Sent from my SCH-I535 using xda app-developers app

please post as soon as you get the ok because i think then we would also be able to use heimdall but i might be wrong.

Bump
Sent from my SCH-I535 using xda premium

aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.

letinsh said:
aight, darkyy's method won't work as /dev/mount/bml2 (or any of the bml's) doesn't exist on the GS3. I think I posted without knowing enough info.
I don't know where the PIT file's located on the GS3, and whether it's a function of the phone or the OS (ie ICS vs Gingerbread). I didn't have time over the weekend to look into it, too much. Going to look on that i9300 thread posted and also try to learn a little about Heimdall, as I've only ever used Odin.
To sum up:
Goal is to have a .pit file for SCH-I535 for both the 16Gb and 32Gb versions.
Needed:
I don't know enough about Android/SGS3 to know where the .pit is located. Once that's determined, we'll figure out how to extract it and make a functional flash.
Sorry for the false start, still learning here.[/QUOTE\]
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse

joka10 said:
Maybe try the code won't work is you have to use with yaffs2 in the middle or somewhere, i know that the phone runs off of that but that's pretty much all i say since i don't know much.
Click to expand...
Click to collapse
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.

letinsh said:
What I was saying is that /dev/block/bml2 doesn't exist in our file structure on this phone.
Code:
C:\Users\my_computer>adb shell
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 mmcblk0boot0 mmcblk0p16 mmcblk0p3 platform ram2
loop1 mmcblk0boot1 mmcblk0p17 mmcblk0p4 ram0 ram3
loop2 mmcblk0p1 mmcblk0p18 mmcblk0p5 ram1 ram4
loop3 mmcblk0p10 mmcblk0p19 mmcblk0p6 ram10 ram5
loop4 mmcblk0p11 mmcblk0p2 mmcblk0p7 ram11 ram6
loop5 mmcblk0p12 mmcblk0p20 mmcblk0p8 ram12 ram7
loop6 mmcblk0p13 mmcblk0p21 mmcblk0p9 ram13 ram8
loop7 mmcblk0p14 mmcblk0p22 mmcblk1 ram14 ram9
mmcblk0 mmcblk0p15 mmcblk0p23 mmcblk1p1 ram15
/dev/block #
As you can see, no bml's of any kind.
I don't know if that's because darkyy was messing with a GB version of Android, or because the phone (Samsung) has put the PIT file in a different location. I've got a PM out to Odia from that I9300 thread and he should have some helpful info as to where it's stored and how to get it.
Stay tuned.
Click to expand...
Click to collapse
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.

joka10 said:
Yea your right it's because he's using a exynos processor instead of the one we have, have you tried replacing the command with those listed above. I know from the odin thread it can't be mmcblk0p1, mmcblk0p15, mmcblk0p18,mmcblk0p14, mmcblk0p12, mmcblk0p13, mmcblk0p17, nor mmcblk0p7.
Click to expand...
Click to collapse
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?

letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
Heimdall has never been able to recognize my phone...and I was looking somewhere and the developer said it wasn't working and to try 1.3.1 which was not successful either. I had to borrow a computer to use Odin...I know this isn't a solution for getting heimdall to work but I personally don't think it will...if you do get it to work the steps you took would be appreciated
Sent from my SCH-I535 using xda premium

letinsh said:
Here's the partition table as seen when using the "parted print" command on a properly formatted VZW SGS3 32Gb:
Code:
Disk /dev/block/mmcblk0: 31268536320B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
So, from this, we know it's not any of the mmcblk0p1 through mmcblk0p23 partitions.
If you notice, partition 1 starts 4Mb into storage. I think the PIT is located somewhere in the first 4Mb, but I don't know what memory addresses/file to look under to grab it.... is it in one of the other locations listed above under /dev/block ? Is it in /dev/block/mmcblk0/ ? I just don't know....
After looking at Heimdall, the tool has an option to rip the PIT, but I haven't been able to get it to recognize my SGS3. I've tried both 1.3.2 and 1.3.1
Once that's ripped, can we flash it using Odin in the PIT field? Or do we have to use Heimdall to to put it back?
Click to expand...
Click to collapse
We can use either or I thin for odin you flash using repartition checked and placing it in the pda field but it will allow us to flash with heimdall using that pit since it can't find the one on the phone. Lastly internal flash /dev/block/mmcblk0 becomes /dev/block/mmcblk1 is what i have found so it looks like either im wrong or it has to be one of the 24 blocks.

Can someone with a working 32 run this in a Terminal? It should pull the PIT from your phone and place it in the SD card. I'm sure those with a 16gb would love to have their PIT file as well.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/pit.bin bs=4096 count=1 skip=4
Info from HERE (International device, but the blocks should be the same)

MyTouch 4G Slide eMMC Partition Info

Hi All,
Through some stupidity I've managed to completely destroy the eMMC partition table on my MT4GS. I've already sent away for a RiffBox to fix this (via JTAG if I really have to), however whilst I wait for that I've like to pursue a bit more on the Qualcomm QPST emergency download side of things.
This essentially requires a bunch of .MBN files, and is similar to what HTC themselves might do during an engineering boot-up or similar (if they're not using JTAG). I've done quite a bit of research, and it seems that getting the various .MBN files might be borderline impossible (all our files seem to be in a non-standard .IMG format, and I can't work out the conversion), I'm hopeful that if I can just get the partition table back up and running then all the remaining data on the eMMC would still be workable.
Would it be possible for someone to get an fdisk record of the start, end and size (plus 'friendly' name would be great) of each of the partitions on the eMMC?
I believe this would require something like:
adb shell
su
fdisk -l /dev/mmcblk0
I've looked through all the development stuff, however it seems that the partition table info is still quite lacking on that front.
If someone could give this a try then it would be greatly appreciated.
Thanks all
Bevan

bevanweiss said:
Hi All,
Through some stupidity I've managed to completely destroy the eMMC partition table on my MT4GS. I've already sent away for a RiffBox to fix this (via JTAG if I really have to), however whilst I wait for that I've like to pursue a bit more on the Qualcomm QPST emergency download side of things.
This essentially requires a bunch of .MBN files, and is similar to what HTC themselves might do during an engineering boot-up or similar (if they're not using JTAG). I've done quite a bit of research, and it seems that getting the various .MBN files might be borderline impossible (all our files seem to be in a non-standard .IMG format, and I can't work out the conversion), I'm hopeful that if I can just get the partition table back up and running then all the remaining data on the eMMC would still be workable.
Would it be possible for someone to get an fdisk record of the start, end and size (plus 'friendly' name would be great) of each of the partitions on the eMMC?
I believe this would require something like:
adb shell
su
fdisk -l /dev/mmcblk0
I've looked through all the development stuff, however it seems that the partition table info is still quite lacking on that front.
If someone could give this a try then it would be greatly appreciated.
Thanks all
Bevan
Click to expand...
Click to collapse
If you will go here... http://forum.xda-developers.com/showthread.php?t=1254518 and then click on the "post 3" link I believe you'll find what you're looking for.
Good LUCK! :good:

WeekendsR2Short said:
If you will go here... http://forum.xda-developers.com/showthread.php?t=1254518 and then click on the "post 3" link I believe you'll find what you're looking for.
Good LUCK! :good:
Click to expand...
Click to collapse
Thanks for the link. But it's not really enough info available there.
The information I'm after is really:
Start address, End address and Size for each partition. Plus ideally some 'friendly' description of the partition contents (ie boot / system / cache), but I don't actually need this last part right now.
The page you referenced has block names ie mmcblk0p01, however this isn't actual partition table information.
It also doesn't show the start address, end address and size of all the partitions (there is the cat /proc/emmc output, but this isn't all the partitions, and doesn't show start or end addresses)
Thanks anyway, it would be great if you could perform the adb commands though
That would hopefully give me the info I need to get my phone back up and running.

I have another command which seems it would work better, since it's a lower level command...
fastboot oem listpartition
Can someone please run this and let me know the results?
Thanks

I'm afraid all that one gives me is <waiting for device>
fdisk -l /dev/mmcblk0
this one gives me no such file or directory

WeekendsR2Short said:
I'm afraid all that one gives me is <waiting for device>
fdisk -l /dev/mmcblk0
this one gives me no such file or directory
Click to expand...
Click to collapse
Are you S-OFF and rooted?
I got the 'fastboot oem listpartition' command from an HTC Sensation forum, I was hoping it would work on most modern Android HTCs.
Could you please try the following:
fastboot partition getvar-layout
fastboot oem h <-- this one should list all the available fastboot oem commands available (assuming you're S-OFF)
Thanks for the help so far
It would be great to get more information on these phones. I still think it's a great phone, I wish that there were more slider style phones available on the market

bevanweiss said:
Are you S-OFF and rooted?
I got the 'fastboot oem listpartition' command from an HTC Sensation forum, I was hoping it would work on most modern Android HTCs.
Could you please try the following:
fastboot partition getvar-layout
fastboot oem h <-- this one should list all the available fastboot oem commands available (assuming you're S-OFF)
Thanks for the help so far
It would be great to get more information on these phones. I still think it's a great phone, I wish that there were more slider style phones available on the market
Click to expand...
Click to collapse
Depending on the results from the 'fastboot oem h' command... I believe the command I actually wanted before was
fastboot oem list_partition_emmc

bevanweiss said:
Are you S-OFF and rooted?
I got the 'fastboot oem listpartition' command from an HTC Sensation forum, I was hoping it would work on most modern Android HTCs.
Could you please try the following:
fastboot partition getvar-layout
fastboot oem h <-- this one should list all the available fastboot oem commands available (assuming you're S-OFF)
Thanks for the help so far
It would be great to get more information on these phones. I still think it's a great phone, I wish that there were more slider style phones available on the market
Click to expand...
Click to collapse
Then that must be my issue. I didn't realize S-Off was a requirement to realize all ADB commands. I am unlocked & rooted but I haven't run the wire trick yet. I replaced my phone a couple of weeks ago and got the new bootloader. :crying:
I WAS planning on that this evening though after I repair a friends computer and get the rest of this danged yard mowed. Hopefully someone else will step up and help you with that though. If not, I'll be happy to a little after dark. (Eastern time)

[email protected] ~/android/android/platform-tools $ ./fastboot oem list_partition_emmc
...
(bootloader) index, type, start, num
(bootloader) 0, 0x4D, 0x1, 0x100
(bootloader) 1, 0x51, 0x101, 0x200
(bootloader) 2, 0x5D, 0x301, 0xFCDE
(bootloader) 3, 0x5, 0xFFDF, 0x470020
OKAY [ 0.017s]
finished. total time: 0.017s
[email protected] ~/android/android/platform-tools $
here is what you get when running fastboot oem h
[email protected] ~/android/android/platform-tools $ ./fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.041s
*i know them are just optional commands but since i ran it anyways to make sure the command you wanted ran was right, i figured i would post them so we have them for everyone to see if they want

That's great stuff. But a little confusing about the partition info listed. You're definitely on a MyTouch 4G Slide right?
That partition list only seems to show 4 partitions, yet I'm sure there is more than this... I was thinking more in the 30partitions range.
I'm thinking perhaps there's some strange stuff going on with extended partitions here.
Can you please try the following command?
fastboot partition getvar-layout
This might not provide any real information, but every little piece will help

and actually the adb shell command
fdisk -ul /dev/block/mmcblk0
would still be really really good
I think I got the device descriptor wrong the first time I asked for this information.. which is probably why it didn't work..

bevanweiss said:
and actually the adb shell command
fdisk -ul /dev/block/mmcblk0
would still be really really good
I think I got the device descriptor wrong the first time I asked for this information.. which is probably why it didn't work..
Click to expand...
Click to collapse
Yeah I am def on the slide lmao. I kinda host a couple ROMS for my personal phone. . The fdisk command from the op says no file or directory. I'm s-off with junoptbear or whatever the. Wire trick is called. Also I won't be around my computer untill tomorrow after work. When I go to my parents house, I was just there for a hot minute today and figured this is what you needed. But are you even sure what you need because it seems like the help we are giving isn't good enough?
Sent from my HTC MyTouch 4G Slide running MikXE

Still not much luck from here either......
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Steve>cd\
C:\>adb shell
[email protected]:/ #
[email protected]:/ # fdisk -ul/dev/block/mmcblk0
fdisk -ul/dev/block/mmcblk0
fdisk: invalid option -- /
BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
Options:
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
1|[email protected]:/ #
---------- Post added at 09:47 PM ---------- Previous post was at 09:37 PM ----------
bevanweiss said:
and actually the adb shell command
fdisk -ul /dev/block/mmcblk0
would still be really really good
I think I got the device descriptor wrong the first time I asked for this information.. which is probably why it didn't work..
Click to expand...
Click to collapse
BINGO!!! (at least I think this is what you're looking for)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
1|[email protected]:/ # 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 291166 122871+ 83 Linux
dev/block/mmcblk0p25 291166 291678 4096 4a Unknown
dev/block/mmcblk0p26 291678 292190 4096 4b Unknown
dev/block/mmcblk0p27 292190 294750 20480 19 Unknown
dev/block/mmcblk0p28 294750 294750 4 0 Empty
dev/block/mmcblk0p29 294750 294782 256 23 Unknown
dev/block/mmcblk0p30 294783 294784 16 0 Empty
dev/block/mmcblk0p31 294785 294912 1022+ 76 Unknown
dev/block/mmcblk0p32 4095 4096 16 5a Unknown
dev/block/mmcblk0p33 4097 4129 256 73 Unknown
dev/block/mmcblk0p34 4129 6684 20442+ 0 Empty
dev/block/mmcblk0p35 6684 6716 256 0 Empty
dev/block/mmcblk0p36 6716 6844 1024 45 Unknown
dev/block/mmcblk0p37 6844 6876 256 47 Unknown
dev/block/mmcblk0p38 6876 7132 2048 46 Unknown
dev/block/mmcblk0p39 7132 7260 1024 4c Unknown
dev/block/mmcblk0p40 7260 7264 32 0 Empty
dev/block/mmcblk0p41 7264 8032 6144 34 Unknown
dev/block/mmcblk0p42 8032 8160 1024 36 Unknown
dev/block/mmcblk0p43 8161 8192 256 76 Unknown
dev/block/mmcblk0p44 8193 13313 40960 77 Unknown
dev/block/mmcblk0p45 13313 14336 8190+ 74 Unknown
dev/block/mmcblk0p46 14337 16384 16384 0 Empty
dev/block/mmcblk0p47 16385 18433 16384 48 Unknown
dev/block/mmcblk0p48 18433 20480 16383 71 Unknown
dev/block/mmcblk0p49 20481 122880 819199 83 Linux
dev/block/mmcblk0p50 122881 275807 1223409 83 Linux
dev/block/mmcblk0p51 275807 291166 122871+ 83 Linux
dev/block/mmcblk0p52 291166 291678 4096 4a Unknown
dev/block/mmcblk0p53 291678 292190 4096 4b Unknown
dev/block/mmcblk0p54 292190 294750 20480 19 Unknown
dev/block/mmcblk0p55 294750 294750 4 0 Empty
dev/block/mmcblk0p56 294750 294782 256 23 Unknown
dev/block/mmcblk0p57 294783 294784 16 0 Empty
dev/block/mmcblk0p58 294785 294912 1022+ 76 Unknown
dev/block/mmcblk0p59 4095 4096 16 5a Unknown
dev/block/mmcblk0p60 4097 4129 256 73 Unknown
Partition table entries are not in disk order
[email protected]:/ #
Hint: It looks like the leading "/" was the killer. It was actually "dev/block/mmcblk0" as you can see. That's pretty cool. I know it wasn't fun for you but it was for me! :laugh:

That's awesome
Thanks for that. It's exactly what I was looking for.
I'll try to get this added to the development section also, as this is the more important partition info than what is shown there..
It should be noted that the Extended partition info isn't correct... there is an endless loop in their references. It should actually stop at dev/block/mmcblk0p31, but the next record reference for this partition links back to the first extended partition record dev/block/mmcblk0p5.
So the actual MBR is just the first four entries, which is what we were seeing on the previous fastboot command (list_emmc_partitions).
Now I just need to work out the MBN format from Qualcomm (which is seeming harder than I'd like), and get some information on the NAND flash device that is inside our phones.
If anyone knows the part number and manufacturer of the NAND flash it would be so greatly appreciated. This would then hopefully let me generate a MBN file which I could feed into QPST to correct my MBR record.

Wonderful! ALWAYS glad to help when I can because I learn in the process myself. :good:
If anyone knows the part number and manufacturer of the NAND flash it would be so greatly appreciated. This would then hopefully let me generate a MBN file which I could feed into QPST to correct my MBR record.
If I knew what you were refering to I'd be happy to try but unfortunately you're way over my head right there. Good Luck though...

Hopefully this will lead you to a solution to the error that resulted in flashing the faulty recovery.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Tried all sorts of things but i still get the same error. I think the only way around this is to reformat the whole partition table. Unless theres a known fix.
Wish you all the best with the task you are trying to achieve! :good:

[GUIDE][Xiaomi Mi-One] Changing size of /system partitions

Disclaimer: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or anything else. YOU doing this at your own risk.
This guide is taken from 4pda.ru forums and tested on my own device.
I strongly recommend you to make Nandroid backup with CWM Recovery v6.0.3.0 so after repartitioning ALL DATA (/system, /system1, /data, /cache) WILL BE ERASED.
1. Connect you phone to PC via USB. (USB debugging must be turned on)
2. Install MiFlash. Remember installation path. It will install drivers for "Android Composite ADB Device". If there's still one "Android" device without drivers - just ignore.
3. Run Command Prompt (cmd) and go to the %FOLDER_WHERE_YOU_INSTALLED_MIFLASH%\Google\Android (For me it was C:\Program Files (x86)\Xiaomi\MiPhone\Google\Android)
4. Type adb devices and press enter. It should start adb daemon and show your device with status offline. Check phone for dialog and allow USB debug from your computer.
5. Type adb devices again. Now it should show your phone with status device. Close Command Prompt.
6. Download and unpack to any folder attached archive tadb.zip
7. Run tadb shell.bat. If everything fine it will show something like "[email protected]:/ $"
9. Type su and press enter. If requested allow root access on phone.
10. Now enter busybox fdisk /dev/block/mmcblk0 to start repartiotioning program (All changes are virtual until written)
11. Delete all partitions from 20 to 15 inclusive. For this enter d, enter 20, enter d, enter 19 till 15th partition.
After this enter p. Your partition table must be like this
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 488448 3803183+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13052 13114 500 47 Unknown
/dev/block/mmcblk0p6 13114 13370 2048 45 Unknown
/dev/block/mmcblk0p7 13370 13683 2500 4c Unknown
/dev/block/mmcblk0p8 13683 14963 10240 48 Unknown
/dev/block/mmcblk0p9 14963 16243 10240 64 Unknown
/dev/block/mmcblk0p10 16243 16305 500 46 Unknown
/dev/block/mmcblk0p11 16305 16368 500 65 Unknown
/dev/block/mmcblk0p12 16385 16768 3072 4a Unknown
/dev/block/mmcblk0p13 16769 17152 3072 4b Unknown
/dev/block/mmcblk0p14 20481 20864 3072 58 Unknown
12. Recreate needed partitions table. Press n, enter start block, end block. You can use attached partitions.xls to calculate needed values. Also You can change size of system partitions in this file as you wish (Make them 384Mb for example). Values will be recalculated.
13. Now we must return System type for 17th block (recovery). Enter t, enter 17, enter 60. After this operation your partiotion table will be like this (If you left 256Mb):
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 488448 3803183+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13052 13114 500 47 Unknown
/dev/block/mmcblk0p6 13114 13370 2048 45 Unknown
/dev/block/mmcblk0p7 13370 13683 2500 4c Unknown
/dev/block/mmcblk0p8 13683 14963 10240 48 Unknown
/dev/block/mmcblk0p9 14963 16243 10240 64 Unknown
/dev/block/mmcblk0p10 16243 16305 500 46 Unknown
/dev/block/mmcblk0p11 16305 16368 500 65 Unknown
/dev/block/mmcblk0p12 16385 16768 3072 4a Unknown
/dev/block/mmcblk0p13 16769 17152 3072 4b Unknown
/dev/block/mmcblk0p14 20481 20864 3072 58 Unknown
/dev/block/mmcblk0p15 20866 53633 262144 83 Linux
/dev/block/mmcblk0p16 53635 86402 262144 83 Linux
/dev/block/mmcblk0p17 86404 87683 10240 60 Unknown
/dev/block/mmcblk0p18 87685 88708 8192 83 Linux
/dev/block/mmcblk0p19 88710 111749 184320 83 Linux
/dev/block/mmcblk0p20 111751 488448 3013584 83 Linux
14. Time to save changes. If you not sure, you can just enter q to leave without saving changes. Enter w to write new partition table. Program will show error about using old partition table - that's normal. After you reboot phone - changes will be applied, so it will not load anything except fastboot.
15. Load phone in fastboot mode (Power + Volume Down + Mi-Button), go to folder with tadb and run flash_recovery.bat. It will flash CWM 6.0.3.0 to your device.
16. Go to mounts & storage menu and format /cache, /system, /system1 and /data
17. Now you can restore your nandroid backup.
NOTE: All operations been made on Windows 7 32-bit and Xiaomi Mi-One Plus with MIUIv5 3.7.19

Waiting for move to right forum section. Report sent.

What is the point to do all these? Are some benefits from this change?

dancer_69 said:
What is the point to do all these? Are some benefits from this change?
Click to expand...
Click to collapse
Some custom ROMS (MoKee OS for example) have very few free space in /system after installation. Not enough even to flash GApps.

Yes, I know about that but there is already a tool for repartition. I thought that this was more than that. It' s nice that you can customise the size though. But isn't dangerous? I'm saying this because I've hard break my device twice using gparted. I had a full linux backup of device though so I recovered it but was the only way to do it. I succeed once though.

What's the name of the repartition tool? I'm caught in a wicked cloning loop that duplicates my partitions periodically and I haven't tracked down the cause. Ota JB Feb. 1st is the day it started. Thanks
A Charge of $17.99 Was Applied To Your Mobile Account For Browbeating The Author's Questions. Albeit, Most Likely a Foolish, Ignorant, Uneducated Compilation of Useless Quibble. But He Is Less Than 1 Year With Me and Is Bashing Adb, Scripting, Rooting, Romming Like a Red Headed Stepchild With No Thumbs, Herpes Type 4.2.2. Flashaholicism! Give My Poor TTS Owner A Hand Would ya? Sent From His Overclocked Porn Providing ClapaTalk Razr Maxx Xt-912.

I mean Genocolar' s and Forumber' s update zips for repartition.

dancer_69 said:
I mean Genocolar' s and Forumber' s update zips for repartition.
Click to expand...
Click to collapse
Can you give links to them?

Here is the topic:
http://forum.xda-developers.com/showthread.php?t=1112857&highlight=partition
As for Forumber' s modified way to larger /system, search on U8800 developing section, it' s in a lot roms threads.

just a note:
On M1S phones the last END block is 477184 and not 488448 like M1+ and M1 C1
all is equal except that
So M1S users take in mind when repartitioning your phones.

ehrans said:
just a note:
On M1S phones the last END block is 477184 and not 488448 like M1+ and M1 C1
all is equal except that
So M1S users take in mind when repartitioning your phones.
Click to expand...
Click to collapse
Well, when creating last partition (/data) you can just hit Enter when prompted for last END block to use Default value. I think tadb automatically will use 477184 instead of 488448 for M1S. Not sure.

i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html

eilegz said:
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
Click to expand...
Click to collapse
yes, is my tutorial for an automated way to do the changes from a recovery instalable .zip
just download, flash a compatible recovery (any cwm with busybox for M1/S should work) then install the zip for ur phone model.

eilegz said:
i dont know if this its related but here it seems that there are a easier method to change the size
the author have it set on 280mb but it could be increased
link: miui.es/index.php/topic,7965.0.html
Click to expand...
Click to collapse
You can restore a broken link?

r.dave said:
You can restore a broken link?
Click to expand...
Click to collapse
check your pm

Could somebody refresh link for instalable.zip ?
thx

thankyou

CLOSE, please

All important information/ links will be moved to an INFO thread, since this is a question thread, we do not need it anymore.

Still looking.
Bump, can anyone help?
Saw this page:
forum.xda-developers .com/showthread.php?t=1959445
Was wondering if it's worth a shot.

Kernel released by Huawei.
For kernel/Rom Developers, Huawei has released the kernel for the Huawei Prism II online.
Attached is a notepad document with the links in them, since I am not allowed to post links. I apologize for the inconvenience.
ALSO
For anyone else with a Huawei device that has not released their kernel, I used the email format below:
Emal 1:
I would like the source code for my phone that is available to me. I am an android developer, and it would be useful to me if I have the
source code(that is offerred by Huawei).
The reply you will get:
Dear Customer,
Thank you for contacting Huawei device. The open source is under our technical department to make. Since the procedure is a little more complex, so please kindly be a little patient. We will keep you informed once available.Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.
Give them 2-3 days, then E-mail once again! Be persistent!
2nd email:
Any new information about the source code?
The reply I got:
Dear Customer,
Thank you for contacting Huawei device. Please kindly check the source code link for your reference:
(link given above)
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.

Parted/FDisk Output on /dev/block/mmcblk0
streetdev22 said:
Bump, can anyone help?
Saw this page:
forum.xda-developers .com/showthread.php?t=1959445
Was wondering if it's worth a shot.
Click to expand...
Click to collapse
Tried the guide on my Prism II. Parted gave me an error. Possible reason for parted error is explained here: http://forum.xda-developers.com/showthread.php?t=2169709.
However, fdisk worked, but it doesn't clearly identify the partitons:
Edited to include gdisk output
parted:
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Unable to satisfy all constraints on the partition.
fdisk:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
1 heads, 16 sectors/track, 477184 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 3 41 300 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown
gdisk:
Code:
[email protected]:/ # gdisk -l /dev/block/mmcblk0
gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Exact type match not found for type code 4D00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4500; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6A00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4600; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6300; assigning type code for
'Linux filesystem'
Exact type match not found for type code 5800; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4A00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4B00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4700; assigning type code for
'Linux filesystem'
Exact type match not found for type code 4800; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6000; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6C00; assigning type code for
'Linux filesystem'
Exact type match not found for type code 6B00; assigning type code for
'Linux filesystem'
Warning! Main partition table overlaps the first partition by 33 blocks!
You will need to delete this partition or resize it in another utility.
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/block/mmcblk0: 7634944 sectors, 3.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E271C8D6-2001-435D-A466-BEFE7ED158CD
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7634910
Partitions will be aligned on 1-sector boundaries
Total free space is 9599 sectors (4.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 1 40 20.0 KiB 8300 Linux filesystem
2 41 640 300.0 KiB 8300 Linux filesystem
3 641 266880 130.0 MiB 0700 Microsoft basic data
5 270336 294911 12.0 MiB 8300 Linux filesystem
6 294912 303103 4.0 MiB 8300 Linux filesystem
7 303104 311295 4.0 MiB 8300 Linux filesystem
8 311296 317439 3.0 MiB 8300 Linux filesystem
9 319488 325631 3.0 MiB 8300 Linux filesystem
10 327680 333823 3.0 MiB 8300 Linux filesystem
11 335872 344063 4.0 MiB 8300 Linux filesystem
12 344064 360447 8.0 MiB 8300 Linux filesystem
13 360448 401407 20.0 MiB 8300 Linux filesystem
14 401408 409599 4.0 MiB 8300 Linux filesystem
15 409600 802815 192.0 MiB 8300 Linux filesystem
16 802816 966655 80.0 MiB 8300 Linux filesystem
17 966656 3063807 1024.0 MiB 8300 Linux filesystem
18 3063808 5423103 1.1 GiB 8300 Linux filesystem
19 5423104 7634943 1.1 GiB 8300 Linux filesystem
[email protected]:/ #

Partition Layout
streetdev22 said:
Recently rooted and unlocked the bootloader on my Huawei Prism II, but there is no custom recovery nor custom roms for this phone. I have tried determing the partition layout in order to dump the recovery, but I am unable to do so.
Tried earlier versions of romdump, but they returned with a segmentation failure.
Click to expand...
Click to collapse
I believe I've found the partition layout based on the /etc/recovery_mmc.fstab extracted from mmcblk0p13, but am not sure. The excerpt of my /etc/recovery_mmc.fstab file from mmcblk0p13 shows some partition names correlated to device names. Could someone verify this is a legitimate way to determine the partition layout? I've also attached the whole recovery_mmc.fstab file.
recovery_mmc.fstab excerpt:
Code:
/boot emmc /dev/block/mmcblk0p12
/cache ext4 /dev/block/mmcblk0p15
# /* < DTS2012062603367 lizhigang 20120626 begin */
/data ext4 /dev/block/mmcblk0p18 length=-16384
#/* < DTS2012062603367 lizhigang 20120626 end */
/recovery emmc /dev/block/mmcblk0p13
/misc emmc /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p17
/sys_boot vfat /dev/block/mmcblk0p3
/fat vfat /dev/block/mmcblk0p3
/HWUserData vfat /dev/block/mmcblk0p19
#/*< DTS2012020804291 weizhonghui 20120208 begin */
/cust ext4 /dev/block/mmcblk0p16
#/* DTS2012020804291 weizhonghui 20120208 end >*/
#/* DTS2012011906026 chendeng 20120120 end > */
# /* DTS2012031506621 lishubin 20120321 end > */
Easier to read (joined fdisk and the recovery_mmc.fstab)
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 3 20 4d Unknown /sdcard
/dev/block/mmcblk0p2 3 41 300 45 Unknown
/dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LBA) /sys_boot and /fat
/dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended
/dev/block/mmcblk0p5 16897 18432 12288 6a Unknown
/dev/block/mmcblk0p6 18433 18944 4096 46 Unknown
/dev/block/mmcblk0p7 18945 19456 4096 63 GNU HURD or SysV /misc
/dev/block/mmcblk0p8 19457 19840 3072 58 Unknown
/dev/block/mmcblk0p9 19969 20352 3072 4a Unknown
/dev/block/mmcblk0p10 20481 20864 3072 4b Unknown
/dev/block/mmcblk0p11 20993 21504 4096 47 Unknown
/dev/block/mmcblk0p12 21505 22528 8192 48 Unknown /boot
/dev/block/mmcblk0p13 22529 25088 20480 60 Unknown /recovery
/dev/block/mmcblk0p14 25089 25600 4096 6c Unknown
/dev/block/mmcblk0p15 25601 50176 196608 83 Linux /cache
/dev/block/mmcblk0p16 50177 60416 81920 83 Linux /cust
/dev/block/mmcblk0p17 60417 191488 1048576 83 Linux /system
/dev/block/mmcblk0p18 191489 338944 1179648 83 Linux /data
/dev/block/mmcblk0p19 338945 477184 1105920 6b Unknown /HWUserData

Very nice!
Correlates with the hints found in other files as seen above, so I think we have successfully found the partition layout! I will take a look when my device gets here(originally was working on my relative's phone, but now I purchased it for myself). If this method is confirmed,we can to port CWM, thank you all!! After CWM, we should be able to make custom ROMs freely.

streetdev22 said:
Correlates with the hints found in other files as seen above, so I think we have successfully found the partition layout! I will take a look when my device gets here(originally was working on my relative's phone, but now I purchased it for myself). If this method is confirmed,we can to port CWM, thank you all!! After CWM, we should be able to make custom ROMs freely.
Click to expand...
Click to collapse
Great. I'm glad that someone can verify part of the partition layout. Hopefully, this means that the new information is credible too.

Prism 2 said:
Great. I'm glad that someone can verify part of the partition layout. Hopefully, this means that the new information is credible too.
Click to expand...
Click to collapse
How exactly did you extract the file? Did you extract it from mmcblk0p13? Have the device on hand, so I am trying to verify the findings.
Thanks.

Unpacking Recovery Image
streetdev22 said:
How exactly did you extract the file? Did you extract it from mmcblk0p13? Have the device on hand, so I am trying to verify the findings.
Thanks.
Click to expand...
Click to collapse
First, I made a selective backup using a google store app called Online Nandroid Backup https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en to make a backup on the "recovery" partition. Even though the app does not specify which block it copies, I believe the app makes a backup of /dev/block/mmcblk0p13 because it uses /system/partlayout4nandroid to determine the partition layout. If you look at the "cat /system/partlayout4nandroid" output below, you'll see that mmcblk0p13 corresponds to recovery.
Then I transferred the recovery.img from the sdcard to my computer.
From there, I followed the directions in Step 1 and Step 2 of http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html to unpack and extract recovery.img.
Online Nandroid Backup Partition Layout:
Code:
[email protected]:/ # cat /system/partlayout4nandroid
cat /system/partlayout4nandroid
dev: size erasesize name
mmcblk0p1: 010000 000000 "modem"
mmcblk0p2: 000008 000000 "ssd"
mmcblk0p3: 000080 000000 "sbl1"
mmcblk0p4: 000100 000000 "sbl2"
mmcblk0p5: 000200 000000 "sbl3"
mmcblk0p6: 000200 000000 "aboot"
mmcblk0p7: 000200 000000 "rpm"
mmcblk0p8: 000200 000000 "tz"
mmcblk0p9: 002800 000000 "pad"
mmcblk0p10: 000c00 000000 "fsg"
mmcblk0p11: 002000 000000 "persist"
mmcblk0p12: 002800 000000 "boot"
[B]mmcblk0p13: 002800 000000 "recovery"[/B]
mmcblk0p14: 0b8000 000000 "system"
mmcblk0p15: 0d0000 000000 "cache"
mmcblk0p16: 000c00 000000 "modemst1"
mmcblk0p17: 000c00 000000 "modemst2"
mmcblk0p18: 040000 000000 "tombstones"
mmcblk0p19: 000400 000000 "misc"
mmcblk0p20: 001000 000000 "logo"
mmcblk0p21: 001000 000000 "logo2"
mmcblk0p22: 54c000 000000 "userdata"
mmcblk0p23: 00ffef 000000 "grow"
[email protected]:/ #

Probably correct.
My father(the owner of the phone) has once again left on a trip, so I will have to wait until Monday/Tuesday, when I receive my phone, to confirm these results.
My only issue with this is is why nandroid shows a different partition layout then what is shown in other files.
If partition 13 is recovery, there is no coincidence that you would find that fstab file in the extracted recovery.
Do you mind dumping all the extracted files from the recovery and uploading them to 4shared, mediafire, or any other cloud service as a compressed file(zip, tar)? I think the file is not coincidental, and that we have indeed found the partition layout(or at least the important partitions for our purposes).
Also, try dumping the boot partition that is currently identified (block 12) without using online nandroid backup(I think via dd should still work) and see if you can find similar files to that explained in the guide(.png, ramdisk directory, etc). If these files match up to what would be typically found in a boot.img or recovery.img, then the layout is most likely correct.
If these files match up to typical boot.img or recovery.img files, we can test the layout by changing something simple like a background before working on serious stuff.
Also, thanks for helping! Once we conclusively identify that this partition layout is correct, we can start to port clockworkmod.

streetdev22 said:
My father(the owner of the phone) has once again left on a trip, so I will have to wait until Monday/Tuesday, when I receive my phone, to confirm these results.
My only issue with this is is why nandroid shows a different partition layout then what is shown in other files.
If partition 13 is recovery, there is no coincidence that you would find that fstab file in the extracted recovery.
Do you mind dumping all the extracted files from the recovery and uploading them to 4shared, mediafire, or any other cloud service as a compressed file(zip, tar)? I think the file is not coincidental, and that we have indeed found the partition layout(or at least the important partitions for our purposes).
Also, try dumping the boot partition that is currently identified (block 12) without using online nandroid backup(I think via dd should still work) and see if you can find similar files to that explained in the guide(.png, ramdisk directory, etc). If these files match up to what would be typically found in a boot.img or recovery.img, then the layout is most likely correct.
If these files match up to typical boot.img or recovery.img files, we can test the layout by changing something simple like a background before working on serious stuff.
Also, thanks for helping! Once we conclusively identify that this partition layout is correct, we can start to port clockworkmod.
Click to expand...
Click to collapse
The extracted files in partition 13 can be found in post #44 of http://forum.xda-developers.com/showthread.php?t=2546455&page=5 labeled as "ramdisk.tar.bz2". I will make a dump of the boot partition using dd and run the tests tomorrow.

Looks validated, Also more tools
There are other guides on the matter of porting cyanogenmod..for example
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
which even mentions a recovery.fstab file in recovery.img! So, that means the partition layout in the fstab file you found is most likely correct.
Another guide:
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Also, there is an automated tool to porting cyanogenmod for new devices..
http://builder.clockworkmod.com/ (I would recommend avoiding the touch recovery for now, simple is all we need and we don't need more complications)
I am really feeling pretty confident about the partition layout found in the recovery.fstab, because one guide mentions it to be found in the recovery.img!
I would recommend making the changes to a recovery.img instead, because boot.img is still kinda scary (possible bricking )
Also, I think there is a command to try booting from a recovery.img without flashing the .img to the actual partition.
I think the command is mentioned here: http://forum.xda-developers.com/showthread.php?t=2233477
fastboot boot recovery.img is the command and it will not overwrite your existing recovery.
By using this command, you can try booting the stock recovery you extracted(to validate that we have a stock recovery available if we need it), and then boot the recovery.img you make with small edits, and then boot the recovery.img made from the automated CWM porter.
Thank you for replying so fast! We have made real progress in the last few days.
Edit:In the ramdisk that was extracted, another fstab exists on the root of the directory that is named fstab.msm7627, which is the same name from the file I located in post 1! They are the same file! I think this is validated.

Testing Recovery Partition
streetdev22 said:
I would recommend making the changes to a recovery.img instead, because boot.img is still kinda scary (possible bricking )
Also, I think there is a command to try booting from a recovery.img without flashing the .img to the actual partition.
I think the command is mentioned here: http://forum.xda-developers.com/showthread.php?t=2233477
fastboot boot recovery.img is the command and it will not overwrite your existing recovery.
By using this command, you can try booting the stock recovery you extracted(to validate that we have a stock recovery available if we need it), and then boot the recovery.img you make with small edits, and then boot the recovery.img made from the automated CWM porter.
Click to expand...
Click to collapse
I've made
a regular recovery.img using "dd if=/dev/block/mmcblk0p13 of=/sdcard/recovery.img" to make a copy of the recovery partition
a test recovery.img that is the same in every way to the original recovery.img except that all the images under /res/images is rotated 90 degrees. You can see the difference yourself by looking in res.rar attached below.
a clockworkmod recovery image from the clockworkmod recovery builder website
These images can be found attached below:
recovery.rar = original Huawei recovery image
recovery-test.rar = edited recovery image
recovery.img = clockworkmod recovery automatic builder image from http://jenkins.cyanogenmod.com/job/recovery/52069/
Unfortunately, I cannot test this image myself, because I do not want to unlock my bootloader yet.
If anyone with a rooted, unlocked Huawei Prism 2 is interested in helping to further the development of recovery roms for the Prism 2, I have made 3 tests to see if
the recovery partition is located in /dev/block/mmcblk0p13
the command "fastboot boot recovery.img", which we will be using extensively, can be used to boot the specified image file
the Clockworkmod Recovery image made from automated CWM porter successfully boots
The files you will need are provided below. I've also given instructions to the best of my ability without actually having done this.
To test if the recovery partition is located in /dev/block/mmcblk0p13:
Go into fastboot mode (step 2f in post #1 of http://forum.xda-developers.com/showthread.php?t=2546455)
Download the recovery.rar file below and extract it to get recovery.img.
Open up terminal
change directory to where you extracted recovery.img
type
Code:
fastboot boot recovery.img
See if phone boot into recovery
Next we test an edited recovery.img to see if "fastboot boot recovery.img" is truly letting us boot the image we've specified.
To find out, we're going to use the edited recovery.img and do pretty much the same thing except now with recovery-test.img:
Go into fastboot mode (step 2f in post #1 of http://forum.xda-developers.com/showthread.php?t=2546455)
Download the recovery-test.rar file below and extract it to get recovery-test.img.
Open up terminal
change directory to where you extracted recovery-test.img
type
Code:
fastboot boot recovery-test.img
See if any pictures are upside down (the battery symbol, numbers, or the android robot)
After completing the 2 tasks above, and verifying that we have a valid original recovery.img and that we can use
Code:
fastboot boot recovery.img
to boot a specific image file, we can start testing a very, very, very EXPERIMENTAL Clockworkmod Recovery image using fastboot. I would not rely on this image to make backups and I honestly do not know what kind of damage it might inflict on the phone so make a backup of everything before starting.
output from CWM automatic recovery builder: http://jenkins.cyanogenmod.com/job/recovery/52069/
To test if this CWM recovery image will boot and have the right partition layout:
Go into fastboot mode (step 2f in post #1 of http://forum.xda-developers.com/showthread.php?t=2546455)
Download the recovery.img.
Open up terminal
change directory to where you downloaded recovery.img
type
Code:
fastboot boot recovery.img
If the cwm recovery image boots, type
Code:
mount
See if /sdcard is mounted to the right partition)
If you're feeling lucky, make a backup to /sdcard **this step can cause damage to phone if /sdcard is mounted to the wrong partition**
Thanks for volunteering and bringing the Huawei Prism 2 one step closer to custom roms.

Will test as soon as I get the phone.
I should be getting my phone in the mail Tuesday-Wednesday, but I will test as soon as I get it in the mail and I get my bootloader unlocked. I shouldn't have an issue booting it, since it will boot without effecting my current recovery partition. Hopefully the cwm recovery boots as well.

streetdev22 said:
I should be getting my phone in the mail Tuesday-Wednesday, but I will test as soon as I get it in the mail and I get my bootloader unlocked. I shouldn't have an issue booting it, since it will boot without effecting my current recovery partition. Hopefully the cwm recovery boots as well.
Click to expand...
Click to collapse
Great! I really hope it works. Let me know if I can help with anything in the meantime.

Getting my phone today
My phone is coming today! I will let you know the results either later today or tomorrow. Also, could you pull a build.prop using ADB from your phone? This guy needs it: http://forum.xda-developers.com/showthread.php?p=49494728

niceeeee
Prism 2 said:
Great! I really hope it works. Let me know if I can help with anything in the meantime.
Click to expand...
Click to collapse
I tried them today and they work fine siiiiir. both booted while i was stuck in a boot loop from deleting my settins apk

Cjantolak said:
I tried them today and they work fine siiiiir. both booted while i was stuck in a boot loop from deleting my settins apk
Click to expand...
Click to collapse
Thats good news! Could you state specifically which 2 of the 3 images booted though? I'm assuming the original (recovery.rar file) and the edited (recovery-test.rar file) recovery.images, but want to make sure
In other words, did you test the clockworkmod recovery image?

first two
Prism 2 said:
Thats good news! Could you state specifically which 2 of the 3 images booted though? I'm assuming the original (recovery.rar file) and the edited (recovery-test.rar file) recovery.images, but want to make sure
In other words, did you test the clockworkmod recovery image?
Click to expand...
Click to collapse
I did just boot the clockworkmod recovery and i just booted up fine. os is running as it should other than the whole missing settings app. im stuck without root, without wifi, and usb debugging.
adb not installing the app either so idk.

Thanks for straightening out the confusion. Can you check the mounted partitions are correct? Afterwards you can use update.zip to install your settings.apk
---------- Post added at 01:11 AM ---------- Previous post was at 01:04 AM ----------
Never mind about checking the partition layout. I just remembered you don't have adb. I will try to make a better recovery image.

[Kindle Fire HD 7] 3rd Gen (2013) SOHO - Bring it back alive with emmc adapter flash

Hello,
I need some help. At the moment I am connected with the eMMC flash of my SOHO 3rd GEN tablet.
I used the exploitee.rs emmc adapter.
The problem:
-The tablet want not booting anymore. Stuck fw was on it (no idea wich fw).
-I try to bring it back with a fastboot cable but something burned on the mainboard (If you had a 3rd gen device and a microscope pls help)
What I want to try:
-I want to reflash the bootloader (are there two on this device???) and the recovery with my emmc adapter to be able to flash the stock fw again. I want to give him just manually 3.7V with a power adapter, at the battery connector.
The problem now:
I really dont know how to extract the right img-files from the stock-bin file. There are some different img files: (md5 sum at begining)
Code:
f82a8c5518a76b96b95dc0448b772d81 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/boot.img
Code:
a5224737ba83a65d40e3049ba6d71582 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/boot-prod.img
Code:
4e6181ea47c7868c2104147dc0b2fce6 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/u-boot.bin
Code:
38cfffa45008955f2887f7998dbd1c4e /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/images/u-boot-prod.bin
Code:
aa4b135a185e5486656893f4c7101271 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/recovery_images/recovery-eng.img
Code:
5cba5636109eec7c7e5faa35104d65c0 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/recovery_images/recovery-prod.img
Code:
Here is recovery from the old system:
7e781998261c22852f6bae53e02335c6 /media/galliumos/MULTIBOOT/Amazon_Kindle_Fire_HD_3rd_gen_SOHO/recovery.img
I really think the bootloader was broken and that was the reason why the device was still black.
So I really would like to flash with
Code:
sudo dd if=/sdcard/bin-extract-stock/images/the-right.img of=/dev/sda2
the needed partitions. Like when I let the device making an update.
Can you help me to get the 100% right image files for the right partitions.
Here are some informations about the current partitions:
Code:
Disk /dev/sda: 14.6 GiB, 15634268160 bytes, 30535680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F9F21FFF-A8D4-5F0E-9746-594869AEC34E
Device Start End Sectors Size Type
/dev/sda1 256 511 256 128K Microsoft basic data
/dev/sda2 512 1023 512 256K Microsoft basic data
/dev/sda3 1024 1151 128 64K Microsoft basic data
/dev/sda4 1152 1183 32 16K Microsoft basic data
/dev/sda5 1184 1187 4 2K Microsoft basic data
/dev/sda6 2048 34815 32768 16M Microsoft basic data
/dev/sda7 34816 51199 16384 8M Microsoft basic data
/dev/sda8 51200 67583 16384 8M Microsoft basic data
/dev/sda9 67584 2623487 2555904 1.2G Microsoft basic data
/dev/sda10 2623488 4466687 1843200 900M Microsoft basic data
/dev/sda11 4466688 30535679 26068992 12.4G Microsoft basic data
Code:
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): i
Partition number (1-11): 1
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F00-A8D4-5F0E-9746-594869AEC34E
First sector: 256 (at 128.0 KiB)
Last sector: 511 (at 255.5 KiB)
Partition size: 256 sectors (128.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'xloader'
Command (? for help): i
Partition number (1-11): 2
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F01-A8D4-5F0E-9746-594869AEC34E
First sector: 512 (at 256.0 KiB)
Last sector: 1023 (at 511.5 KiB)
Partition size: 512 sectors (256.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'bootloader'
Command (? for help): i
Partition number (1-11): 3
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F02-A8D4-5F0E-9746-594869AEC34E
First sector: 1024 (at 512.0 KiB)
Last sector: 1151 (at 575.5 KiB)
Partition size: 128 sectors (64.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'idme'
Command (? for help): i4
Partition number (1-11): 4
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F03-A8D4-5F0E-9746-594869AEC34E
First sector: 1152 (at 576.0 KiB)
Last sector: 1183 (at 591.5 KiB)
Partition size: 32 sectors (16.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'crypto'
Command (? for help): i
Partition number (1-11): 5
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F04-A8D4-5F0E-9746-594869AEC34E
First sector: 1184 (at 592.0 KiB)
Last sector: 1187 (at 593.5 KiB)
Partition size: 4 sectors (2.0 KiB)
Attribute flags: 0000000000000000
Partition name: 'misc'
Command (? for help): i
Partition number (1-11): 6
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F05-A8D4-5F0E-9746-594869AEC34E
First sector: 2048 (at 1024.0 KiB)
Last sector: 34815 (at 17.0 MiB)
Partition size: 32768 sectors (16.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'efs'
Command (? for help): i
Partition number (1-11): 7
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F06-A8D4-5F0E-9746-594869AEC34E
First sector: 34816 (at 17.0 MiB)
Last sector: 51199 (at 25.0 MiB)
Partition size: 16384 sectors (8.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'recovery'
Command (? for help): i
Partition number (1-11): 8
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F07-A8D4-5F0E-9746-594869AEC34E
First sector: 51200 (at 25.0 MiB)
Last sector: 67583 (at 33.0 MiB)
Partition size: 16384 sectors (8.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'boot'
Command (? for help): i
Partition number (1-11): 9
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F08-A8D4-5F0E-9746-594869AEC34E
First sector: 67584 (at 33.0 MiB)
Last sector: 2623487 (at 1.3 GiB)
Partition size: 2555904 sectors (1.2 GiB)
Attribute flags: 0000000000000000
Partition name: 'system'
Command (? for help): i
Partition number (1-11): 10
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F09-A8D4-5F0E-9746-594869AEC34E
First sector: 2623488 (at 1.3 GiB)
Last sector: 4466687 (at 2.1 GiB)
Partition size: 1843200 sectors (900.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'cache'
Command (? for help): i
Partition number (1-11): 11
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: F9F21F0A-A8D4-5F0E-9746-594869AEC34E
First sector: 4466688 (at 2.1 GiB)
Last sector: 30535679 (at 14.6 GiB)
Partition size: 26068992 sectors (12.4 GiB)
Attribute flags: 0000000000000000
Partition name: 'userdata'
gparted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings by I_did_it_just_tmrrow

overlode said:
Edit - SUCCESS!!! It seems I may have had one wire touching another so I tidied up the soldering and the eMMC was recognised straight away
I have successfully accessed the Soho eMMC and can see all partitions as in the attached image!!!
Now if only I could find the commands to backup the entire eMMC...
Click to expand...
Click to collapse
overlode said:
Ok, files uploaded -
Bootloader - https://drive.google.com/file/d/0BwMwdZJ36fBoVTNRVmNjX2FmZTQ/edit?usp=sharing
eMMC Dump - https://drive.google.com/file/d/0BwMwdZJ36fBoNTQyUENvbmVGY1E/edit?usp=sharing
Enjoy
Click to expand...
Click to collapse
I found this post here.
So now I had a 100% bootloader partition and my recovery partition.
What is about 'xloader' partition name?
And the partition 8: "boot". It that "u-boot.bin" from my source?
Pls, I need some answers.
Greetings by Idijt

its been awhile since i got mine revived! soo all this is like something new to me! howeveer ill provide what little that i have

abatoir said:
its been awhile since i got mine revived! soo all this is like something new to me! howeveer ill provide what little that i have
Click to expand...
Click to collapse
Did you still own your device? Can dump your partitions with dd?
Greetings by Idijt

No I don't own it anymore. But mine was an 8gb version, seems like yours is a 15gb version or something like that. I do have photos of my complete partitions.
Sent from my Redmi Note 2 using XDA Free mobile app
---------- Post added at 05:07 AM ---------- Previous post was at 04:48 AM ----------
this is my partiton table after succesfully uploading to emmc

Hello, I'm soho everything is normal, but then teardown accidentally short after the motherboard usb boot don't boot, but the computer have a reaction, but did not show for help how to solve the screen is black, from youdao translation

Hope this helps...
I did something similar. I was using a cheap cable so I swapped them out. I got a LG cable and plugged it in, well it borked my tablet. Black Screen, I took cable apart and found a resistor soldered to a pin! Tested it and it was sending odd pulses, whatever it broke mine. Here is a list of what I backed up before testing.
KF3_p1-xloader.img
-rwxrwxrwx 1 root vboxusers 35002 Sep 3 17:35 KF3_p1-xloader.rar
-rwxrwxrwx 1 root vboxusers 262144 Sep 3 17:27 KF3_p2-BootLoader-Orig.img
-rwxrwxrwx 1 root vboxusers 65536 Sep 3 17:35 KF3_p3-idme.img
-rwxrwxrwx 1 root vboxusers 16384 Sep 3 17:35 KF3_p4-crypto.img
-rwxrwxrwx 1 root vboxusers 2048 Sep 3 17:35 KF3_p5-misc.img
-rwxrwxrwx 1 root vboxusers 16777216 Sep 3 17:35 KF3_p6-efs.img
I assume you need to dd a original image to xloader &or bootloader.
I can only get mine in usb boot mode, which shows as omap4470 windows and Linux as:
Bus 002 Device 005: ID 0451:d012 Texas Instruments, Inc. I suspect I may need to mod & recompile the usbboot source. I think its hardcoded for 4430 or 4460.
*Your Method is even more promising.
I will upload the files if you need them. All except idme & efs as it contains my serials, etc. I *assume* those 2 files will work as they are stock and should have signatures intact.
Would You Post a Pic of the rs device connected to your Kindle?
I would love to find the serial and JTAG pinouts...?

any try this and did can repier of this problem

can you help me please
unimatrix725 said:
I did something similar. I was using a cheap cable so I swapped them out. I got a LG cable and plugged it in, well it borked my tablet. Black Screen, I took cable apart and found a resistor soldered to a pin! Tested it and it was sending odd pulses, whatever it broke mine. Here is a list of what I backed up before testing.
KF3_p1-xloader.img
-rwxrwxrwx 1 root vboxusers 35002 Sep 3 17:35 KF3_p1-xloader.rar
-rwxrwxrwx 1 root vboxusers 262144 Sep 3 17:27 KF3_p2-BootLoader-Orig.img
-rwxrwxrwx 1 root vboxusers 65536 Sep 3 17:35 KF3_p3-idme.img
-rwxrwxrwx 1 root vboxusers 16384 Sep 3 17:35 KF3_p4-crypto.img
-rwxrwxrwx 1 root vboxusers 2048 Sep 3 17:35 KF3_p5-misc.img
-rwxrwxrwx 1 root vboxusers 16777216 Sep 3 17:35 KF3_p6-efs.img
I assume you need to dd a original image to xloader &or bootloader.
I can only get mine in usb boot mode, which shows as omap4470 windows and Linux as:
Bus 002 Device 005: ID 0451:d012 Texas Instruments, Inc. I suspect I may need to mod & recompile the usbboot source. I think its hardcoded for 4430 or 4460.
*Your Method is even more promising.
I will upload the files if you need them. All except idme & efs as it contains my serials, etc. I *assume* those 2 files will work as they are stock and should have signatures intact.
Would You Post a Pic of the rs device connected to your Kindle?
I would love to find the serial and JTAG pinouts...?
View attachment 3866692
Click to expand...
Click to collapse
can you help me please

Nit an expert, mine is still bricked sitting on shelf.
arikurdi said:
can you help me please
Click to expand...
Click to collapse
I would suggest reading from first post. I don't know allot about the kindle. I spent many hours reading the threads to try and fix mine. I would suggest googling for an identification guide, since kindles are hard to tell apart. To make sure you are in the correct place. The second thing when needing help is to provide a detailed description of your problem. You increase chances of more than one person helping.

kindle fire soho
unimatrix725 said:
I would suggest reading from first post. I don't know allot about the kindle. I spent many hours reading the threads to try and fix mine. I would suggest googling for an identification guide, since kindles are hard to tell apart. To make sure you are in the correct place. The second thing when needing help is to provide a detailed description of your problem. You increase chances of more than one person helping.
Click to expand...
Click to collapse
my problem is my kindel fire soho is just read on pc omap4470 and idont know how to make short
and install driver on linux ihave linux but idont how is work iflashed wrong bootloader file

Hi, I also have Kindle Fire HD 7 Soho (2013). I was attempting to unlock the bootloader and install TWRP, following this thread:
https://forum.xda-developers.com/ki...ment/unlock-kfsowi-bootloader-unlock-t3262770
I was able to get into fastboot mode, then proceeded to flash boot with the hijack image, but in the next line, where the system partition is flashed with a system image, I mistakenly flashed system image to the boot partition. I then did continue, before I realized my mistake. It doesn't boot anymore, but I believe the card reader emmc access would be able to get me back in business again.
I've read this thread, and the thread for the HD 7 2012 Tate emmc, I don't see anything pointing to the connections for the card reader to the 2013 soho motherboard. If there is something that has been posted, could someone put a link in this thread? I think it will be very helpful for those of us that want to try that method to unbrick our Kindles (2013, 3rd generation). Thank you.
EDIT: After more reading, I came across a thread which shows the points to connect an sd card reader to the motherboard of a Kindle Fire HD 7 Soho (2013, 3rd gen) in order to access the emmc of the kindle, it will show up as a usb drive when the card reader is connected to the usb port.
https://forum.xda-developers.com/showthread.php?t=2674737&page=3
Here is another related link, it shows the connections using the pins of a micro-sdcard adapter, you should read the entire article because it mentions a 50k-ohm pull up resistor that is required between pins 2 & 4. This was used on a Kindle Fire HD 7 Tate (2012)
https://forum.xda-developers.com/kindle-fire-hd/7-inch-help/kindle-fire-hd-7-emmc-access-t2828906
I am waiting on a fastboot cable first, and it should arrive soon. If I can't get into fastboot mode with the new cable, then I will try the card reader method.

@crackitopen any news?
I found a pin decription for the SOHO and I got a image.
Currently I had still the broken SOHO-8GB from the first post. But I got a second SOHO-16GB version. I could imagine that the bootloader ist the same but I am not sure how to read it and flash it in the right way. Could anybody help with that?
Greetings by Idijt

I_did_it_just_tmrrow said:
@crackitopen any news?
Click to expand...
Click to collapse
Hi Sorry for the late reply, but yes - I waited for the fastboot cable to arrive, and when it did, I was able to get into fastboot mode, so I had only to reflash those 2 partitions. I was very careful this time around, and I was successful in updating the Soho to CyanogenMod 12 unofficial Soho, Android 5.0.2 as described in that other post that I referenced.

crackitopen said:
Hi Sorry for the late reply, but yes - I waited for the fastboot cable to arrive, and when it did, I was able to get into fastboot mode, so I had only to reflash those 2 partitions. I was very careful this time around, and I was successful in updating the Soho to CyanogenMod 12 unofficial Soho, Android 5.0.2 as described in that other post that I referenced.
Click to expand...
Click to collapse
Did you have some tipps for me?
I own 2 SOHO devices and grab from the first one the following partitions:
Code:
=========================================
soho:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 470440 480 469960 1% /dev
tmpfs 470440 0 470440 0% /mnt
/dev/block/mmcblk0p10 1251544 707172 544372 57% /system
/dev/block/mmcblk0p12 5316696 2888156 2428540 55% /data
/dev/block/mmcblk0p11 907096 15708 891388 2% /cache
/dev/fuse 5316696 2888156 2428540 55% /mnt/runtime/default/emulated
/dev/fuse 5316696 2888156 2428540 55% /mnt/runtime/read/emulated
/dev/fuse 5316696 2888156 2428540 55% /mnt/runtime/write/emulated
=========================================
soho:/ # ls -la /dev/block/platform/omap_hsmmc.1/by-name
total 0
drwxr-xr-x 2 root root 280 2017-10-22 01:35 .
drwxr-xr-x 4 root root 380 2017-10-22 01:35 ..
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2017-10-22 01:35 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 crypto -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 efs -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 exploit -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 idme -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2017-10-22 01:35 system -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2017-10-22 01:35 xloader -> /dev/block/mmcblk0p1
The following partition was to big ofr internal memory:
Code:
lrwxrwxrwx 1 root root 21 2017-10-22 01:35 userdata -> /dev/block/mmcblk0p12
What would I like to do next:
I wanna solder my gtv-Hacker emmc adapter to my SOHO mainboard to fix it. Then I would like to flash "bootloader -> /dev/block/mmcblk0p2" & "recovery -> /dev/block/mmcblk0p7" & "exploit -> /dev/block/mmcblk0p9".
Commands to flash the 3 partitions?
Greetings by Idijt

Jesus christ you fixed it? You are a god to me OP.

Galaxyninja66 said:
Jesus christ you fixed it? You are a god to me OP.
Click to expand...
Click to collapse
If you mean me, no I dont fix it yet. I was on the right way but then my noob-Linux knowledge or any other reason seems to destroy the one mainboard. I had SOHO mainboard, one with hardware error and one with software-Brick error.
But I think you have another kindle, I had 2 SOHO boards and you seems to have a TATE:
Code:
>KFHD 7 2012 (tate) - CyanogenMod 13 (Considering an SFOS port)
Greetings by Idijt

I_did_it_just_tmrrow said:
If you mean me, no I dont fix it yet. I was on the right way but then my noob-Linux knowledge or any other reason seems to destroy the one mainboard. I had SOHO mainboard, one with hardware error and one with software-Brick error.
But I think you have another kindle, I had 2 SOHO boards and you seems to have a TATE:
Code:
>KFHD 7 2012 (tate) - CyanogenMod 13 (Considering an SFOS port)
Greetings by Idijt
Click to expand...
Click to collapse
I know we have different kindles, but raising a messed up board from the dead is an accomplishment no less
On a side note, and SFOS port might not be possible due to the nature of the Kindle fire bootloader. Each build just goes straight to fastboot which is un heard of on any other device.

Just wanted to say thank you to @overlode and @unimatrix725. Thanks to you I was able to bring my hard bricked Fire HD 3rd gen (soho) back to the land of living. I've made a mistake of flashing a wrong bootloader.
After a bit of googling I came across a thread on xda where @overlode shared an immensely helpful photo with eMMC pins mapped out - you rock! Using this mapping I was able to solder an usb sdcard reader to the eMMC and access it from gparted. Then I've found this thread where @unimatrix725 shared his original bootloader.img which I then subsequently flashed to my device. Now my Fire HD is happy again - thank you!

Glad you were able to sort it @pfoltyn, I haven't looked at this for a couple of years and have since moved on to other projects but glad it's still helping people