UPDATE:
Working on QPST tools now:
* Need to find prog_emmc_firehose_8x10.mbn
The goal of this project is to gather all the information and tools required in unbricking a hard bricked Moto E (1st Generation).
Possible methods:
1. Blankflash
Requires: singleimage_8x10.mbn, qboot utility for Moto E, programmer_8x10.mbn
2. MiFlash
Requires: fastboot script, fastboot or mfastboot, MPRG8x10.hex, 8x10_msimage.mbn, rawprogram0.xml, patch0.xml
3. QPST
Requires: QPST tool, rawprogram0.xml, patch0.xml, prog_emmc_firehose_8x10.mbn, flat build/single image, multi build/sparse images.
Click to expand...
Click to collapse
XDA:DevDB Information
Unbrick Moto E, Tool/Utility for the Moto E
Contributors
206bone
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-02-05
Reserved
Creating partition.xml file:
1. Post from senior member darkspr1te:
http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
2. Another post from a blog.
Reserved
For reference:
eMMC Partition tool (QPST tools)
Qcom Partition Type Cross Reference (To find Partition IDs for creating partition.xml)
Moto G blank flash tutorial
Creating PIT
Moto E PITs
Moto G PIT
R&D on using Qualcomm
Unbrick Qualcomm Snapdragon devices
Decompiler
GPT Parser
PartitioningTool.py
Moto E source code distros
Sparse Converter
R&D Building Qualcomm Bootloaders
GUID Partition Table (GPT)
Master Boot Record (MBR)
EFI System Partition
Unified Extensible Firmware Interface (UEFI)
UEFI Programming
Test Boot loader
X86_Assembly/Bootloaders
Tell me how I can help and i'll try my best dude
iTudorS said:
Tell me how I can help and i'll try my best dude
Click to expand...
Click to collapse
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
206bone said:
Thank you so much bro... Could you please provide me the full partition information table? More the information, more better..
Here's the link on how to do it: Partition table
I've just dissected a 8x10_msimage.mbn file. And I found 4 partitions:
1. SBL1
2. DDR (No info on DDR.)
3. RPM
4. TZ
I don't know what this DDR file is. I'd like to see the size of this file(in Kb) on the partition table.
Click to expand...
Click to collapse
Hi, I love to help and more in electronics field. Here's my contribution for MotoE XT1022 Condor Device.
Code:
major minor #blocks name
7 0 85648 loop0
7 1 22980 loop1
7 2 32380 loop2
7 3 91916 loop3
7 4 27160 loop4
7 5 4180 loop5
7 6 15668 loop6
7 7 3136 loop7
253 0 524288 zram0
179 0 3866624 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 465024 mmcblk0p33
259 2 917504 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 2350464 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 30466048 mmcblk1
179 65 30465024 mmcblk1p1
254 0 85648 dm-0
254 1 22980 dm-1
254 2 32380 dm-2
254 3 91916 dm-3
254 4 27160 dm-4
254 5 4180 dm-5
254 6 15668 dm-6
254 7 3136 dm-7
7 8 20892 loop8
254 8 20892 dm-8
7 9 61628 loop9
254 9 61628 dm-9
7 10 19848 loop10
254 10 19848 dm-10
7 11 36560 loop11
254 11 36560 dm-11
7 12 35516 loop12
254 12 35516 dm-12
7 13 7312 loop13
254 13 7312 dm-13
Here is the detailed partition info obtained from msm_sdcc.1:
Code:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
boot -> /dev/block/mmcblk0p31
cache -> /dev/block/mmcblk0p33
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p28
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p27
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p29
recovery -> /dev/block/mmcblk0p32
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p12
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sdiBackup -> /dev/block/mmcblk0p14
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p34
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p13
userdata -> /dev/block/mmcblk0p36
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
Here is the detailed partition info obtained from msm_sdcc.2:
Code:
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
DDR partition contain DDR.bin. This image addresses the Physical RAM Memory in the device... common on Elpida Ram Powered Devices. Correct me if I'm wrong please.
Tell me anything that you need.
try this files
206bone said:
Can you please help me out with finding the IDs of each partition in mmcblk0 in the boot record?...
Click to expand...
Click to collapse
Hi friend, as requested:
IDs from mmcblk0:
Code:
Disk /dev/block/mmcblk0: 7733248 sectors, 3776M
Logical sector size: 512
Partition table holds up to 36 entries
First usable sector is 34, last usable sector is 7733214
Number Start (sector) End (sector) Size Code Name
1 256 131327 64.0M 0700 modem
2 131328 132351 512K 0700 sbl1
3 132352 132415 32768 0700 DDR
4 132608 133631 512K 0700 aboot
5 135608 136007 200K 0700 rpm
6 136608 137407 400K 0700 tz
7 137608 137671 32768 0700 sdi
8 137672 138695 512K 0700 utags
9 138696 142791 2048K 0700 logs
10 142792 147455 2332K 0700 padA
11 147456 148479 512K 0700 abootBackup
12 150456 150855 200K 0700 rpmBackup
13 151456 152255 400K 0700 tzBackup
14 152456 152519 32768 0700 sdiBackup
15 152520 153543 512K 0700 utagsBackup
16 153544 155647 1052K 0700 padB
17 155648 158719 1536K 0700 modemst1
18 158720 161791 1536K 0700 modemst2
19 161792 162767 488K 0700 hob
20 162768 162831 32768 0700 dhob
21 163072 166143 1536K 0700 fsg
22 166144 166145 1024 0700 fsc
23 166146 166161 8192 0700 ssd
24 166162 168209 1024K 0700 sp
25 168210 168465 128K 0700 cid
26 168466 174609 3072K 0700 pds
27 174610 182801 4096K 0700 logo
28 182802 190993 4096K 0700 clogo
29 191232 207615 8192K 0700 persist
30 207616 208639 512K 0700 misc
31 208640 229039 9.9M 0700 boot
32 229040 249599 10.0M 0700 recovery
33 249600 1179647 454M 0700 cache
34 1179648 3014655 896M 0700 system
35 3014656 3031039 8192K 0700 kpan
36 3031040 7731967 2295M 0700 userdata
Info from mmcblk0p1:
Code:
Disk /dev/block/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders, total 131072 sectors
Info from mmcblk0p2:
Code:
Disk /dev/block/mmcblk0p2: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p3:
Code:
Disk /dev/block/mmcblk0p3: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p4:
Code:
Disk /dev/block/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p5:
Code:
Disk /dev/block/mmcblk0p5: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p6:
Code:
Disk /dev/block/mmcblk0p6: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p7:
Code:
Disk /dev/block/mmcblk0p7: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p8:
Code:
Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p9:
Code:
Disk /dev/block/mmcblk0p9: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Info from mmcblk0p10:
Code:
Disk /dev/block/mmcblk0p10: 2 MB, 2387968 bytes
4 heads, 16 sectors/track, 72 cylinders, total 4664 sectors
Info from mmcblk0p11:
Code:
Disk /dev/block/mmcblk0p11: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p12:
Code:
Disk /dev/block/mmcblk0p12: 0 MB, 204800 bytes
4 heads, 16 sectors/track, 6 cylinders, total 400 sectors
Info from mmcblk0p13:
Code:
Disk /dev/block/mmcblk0p13: 0 MB, 409600 bytes
4 heads, 16 sectors/track, 12 cylinders, total 800 sectors
Info from mmcblk0p14:
Code:
Disk /dev/block/mmcblk0p14: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p15:
Code:
Disk /dev/block/mmcblk0p15: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p16:
Code:
Disk /dev/block/mmcblk0p16: 1 MB, 1077248 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2104 sectors
Info from mmcblk0p17:
Code:
Disk /dev/block/mmcblk0p17: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p18:
Code:
Disk /dev/block/mmcblk0p18: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p19:
Code:
Disk /dev/block/mmcblk0p19: 0 MB, 499712 bytes
4 heads, 16 sectors/track, 15 cylinders, total 976 sectors
Info from mmcblk0p20:
Code:
Disk /dev/block/mmcblk0p20: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders, total 64 sectors
Info from mmcblk0p21:
Code:
Disk /dev/block/mmcblk0p21: 1 MB, 1572864 bytes
4 heads, 16 sectors/track, 48 cylinders, total 3072 sectors
Info from mmcblk0p22:
Code:
Disk /dev/block/mmcblk0p22: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders, total 2 sectors
Info from mmcblk0p23:
Code:
Disk /dev/block/mmcblk0p23: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders, total 16 sectors
Info from mmcblk0p24:
Code:
Disk /dev/block/mmcblk0p24: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors
Info from mmcblk0p25:
Code:
Disk /dev/block/mmcblk0p25: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders, total 256 sectors
Info from mmcblk0p26:
Code:
Disk /dev/block/mmcblk0p26: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders, total 6144 sectors
Info from mmcblk0p27:
Code:
Disk /dev/block/mmcblk0p27: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p28:
Code:
Disk /dev/block/mmcblk0p28: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Info from mmcblk0p29:
Code:
Disk /dev/block/mmcblk0p29: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p30:
Code:
Disk /dev/block/mmcblk0p30: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders, total 1024 sectors
Info from mmcblk0p31:
Code:
Disk /dev/block/mmcblk0p31: 10 MB, 10444800 bytes
4 heads, 16 sectors/track, 318 cylinders, total 20400 sectors
Info from mmcblk0p32:
Code:
Disk /dev/block/mmcblk0p32: 10 MB, 10526720 bytes
4 heads, 16 sectors/track, 321 cylinders, total 20560 sectors
Info from mmcblk0p33:
Code:
Disk /dev/block/mmcblk0p33: 476 MB, 476184576 bytes
4 heads, 16 sectors/track, 14532 cylinders, total 930048 sectors
Info from mmcblk0p34:
Code:
Disk /dev/block/mmcblk0p34: 939 MB, 939524096 bytes
4 heads, 16 sectors/track, 28672 cylinders, total 1835008 sectors
Info from mmcblk0p35:
Code:
Disk /dev/block/mmcblk0p35: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders, total 16384 sectors
Info from mmcblk0p36:
Code:
Disk /dev/block/mmcblk0p36: 2406 MB, 2406875136 bytes
4 heads, 16 sectors/track, 73452 cylinders, total 4700928 sectors
Hope it helps!
Thanks dude...
Ready To Help
Hey Friend I dont know how to make this files But I hav trust on You so Please If you Make this File I have a hard Bricked Moto E and I an Ready to Test jst Give Me File And Instructions What to Do ... Thank You
206bone said:
Thanks dude...
Click to expand...
Click to collapse
You're welcome. :good:
Maybe its helpfull
Will this method mentioned for LG G2 with Qualcomm(QHSB BULK) fix the file or here it's totally different thing? I am really keen in this project because my device has been dead since 5 months.
Have you got a solution?
I would like to participate in this project
Can i be of some use in this project ? Ive tried all possible ways to get my phone to life but failed .
Keep it up Guys..... We all are waiting. ..
Thanks guyzz to start the project of reviving moto e back to life i too bricked it 2-3 month ago. ill help u guzz in testing and collecting data and giving it here.lets unbrick our device....
[Edit]- if u need files from moto e tell me ..... i have a spare working moto e also.
You can recreate all the files needed, but you can't sign them. Non-signed files won't pass verification and it won't work.
Don't let that demotivate you though, you may come up with something that we didn't see when the first Moto G bricks came around more than year ago.
Try and report back
Did anyone try this method for One Plus, please report back.
Klock2 said:
Did anyone try this method for One Plus, please report back.
Click to expand...
Click to collapse
those files are for one plus one, wont work on moto e
iTudorS said:
those files are for one plus one, wont work on moto e
Click to expand...
Click to collapse
Its not even proper for OnePlus One but ColorOS plays is its role here. So I think it might work as Qualcomm Device i.e QHSBULK
Having issues with compiling recovery(cyanogenmod) for Lenovo Vibe P1MA40 (MT6735M),
here's my BoardConfig.mk
github.com/pareshchouhan/android_device_lenovo_p1ma40/blob/master/BoardConfig.mk
Code:
[ 57% 24/42] Target boot image: /home/paresh/android/android/system/out/target/product/p1ma40/boot.img
FAILED: /bin/bash -c "(/home/paresh/android/android/system/out/host/linux-x86/bin/mkbootimg --kernel /home/paresh/android/android/system/out/target/product/p1ma40/kernel --ramdisk /home/paresh/android/android/system/out/target/product/p1ma40/ramdisk.img --base 0x40080000 --pagesize 2048 --cmdline \"bootopt=64S3,32N2,64N2 buildvariant=userdebug\" --os_version 7.1 --os_patch_level 2016-11-05 --output /home/paresh/android/android/system/out/target/product/p1ma40/boot.img ) && (size=\$(for i in /home/paresh/android/android/system/out/target/product/p1ma40/boot.img; do stat --format \"%s\" \"\$i\" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); printname=\$(echo -n \"/home/paresh/android/android/system/out/target/product/p1ma40/boot.img\" | tr \" \" +); img_blocksize=17301504; twoblocks=\$((img_blocksize * 2)); onepct=\$(((((17301504 / 100) - 1) / img_blocksize + 1) * img_blocksize)); reserve=\$((twoblocks > onepct ? twoblocks : onepct)); maxsize=\$((17301504 - reserve)); echo \"\$printname maxsize=\$maxsize blocksize=\$img_blocksize total=\$total reserve=\$reserve\"; if [ \"\$total\" -gt \"\$maxsize\" ]; then echo \"error: \$printname too large (\$total > [17301504 - \$reserve])\"; false; elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; then echo \"WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)\"; fi ) && (echo \"Made boot image: /home/paresh/android/android/system/out/target/product/p1ma40/boot.img\" )"
/home/paresh/android/android/system/out/target/product/p1ma40/boot.img maxsize=-17301504 blocksize=17301504 total=7809024 reserve=34603008
error: /home/paresh/android/android/system/out/target/product/p1ma40/boot.img too large (7809024 > [17301504 - 34603008])
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
If someone can pinpoint the makefile which contains this check I can comment it out, or better yet give me a solution to this.
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0p7
fdisk -l /dev/block/mmcblk0p7
Disk /dev/block/mmcblk0p7: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ # fdisk -l /dev/block/mmcblk0p20
fdisk -l /dev/block/mmcblk0p20
Disk /dev/block/mmcblk0p20: 2684 MB, 2684354560 bytes
4 heads, 16 sectors/track, 81920 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p20 doesn't contain a valid partition table
[email protected]:/ # fdisk -l /dev/block/mmcblk0p22
fdisk -l /dev/block/mmcblk0p22
Disk /dev/block/mmcblk0p22: 12.3 GB, 12303466496 bytes
4 heads, 16 sectors/track, 375472 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p22 doesn't contain a valid partition table
[email protected]:/ # fdisk -l /dev/block/mmcblk0p23
fdisk -l /dev/block/mmcblk0p23
Disk /dev/block/mmcblk0p23: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Code:
cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00001800 "proinfo"
emmc_p2: 00001c00 00002800 "nvram"
emmc_p3: 00004400 00005000 "protect1"
emmc_p4: 00009400 00005000 "protect2"
emmc_p5: 0000e400 00000400 "lk"
emmc_p6: 0000e800 00000400 "para"
emmc_p7: 0000ec00 00008000 "boot"
emmc_p8: 00016c00 00008000 "recovery"
emmc_p9: 0001ec00 00004000 "logo"
emmc_p10: 00022c00 00005000 "expdb"
emmc_p11: 00027c00 00000400 "seccfg"
emmc_p12: 00028000 00001000 "oemkeystore"
emmc_p13: 00029000 00003000 "secro"
emmc_p14: 0002c000 00004000 "keystore"
emmc_p15: 00030000 00002800 "tee1"
emmc_p16: 00032800 00002800 "tee2"
emmc_p17: 00035000 00000800 "frp"
emmc_p18: 00035800 00010000 "nvdata"
emmc_p19: 00045800 00012800 "metadata"
emmc_p20: 00058000 00500000 "system"
emmc_p21: 00558000 000d4000 "cache"
emmc_p22: 0062c000 016eac00 "userdata"
emmc_p23: 01d16c00 00008000 "flashinfo"
Code:
cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 16384 mmcblk0p7 //boot Disk /dev/block/mmcblk0p7: 16 MB, 16777216 bytes
179 8 16384 mmcblk0p8 //recovery Disk /dev/block/mmcblk0p8: 16 MB, 16777216 bytes
179 9 8192 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 512 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 6144 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 37888 mmcblk0p19
179 20 2621440 mmcblk0p20 //system Disk /dev/block/mmcblk0p20: 2684 MB, 2684354560 bytes
179 21 434176 mmcblk0p21
179 22 12015104 mmcblk0p22 //userdata Disk /dev/block/mmcblk0p22: 12.3 GB, 12303466496 bytes
179 23 16384 mmcblk0p23 //flash info Disk /dev/block/mmcblk0p23: 16 MB, 16777216 bytes
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 15630336 mmcblk1
179 129 15629312 mmcblk1p1
PS: If you need any other info let me know.
Solved: I resolved this issue with the help of friendly people in #cyanogenmod-dev @ freenode
Thanks to (in no particular order)
evilracer
nailyk
gladiac
pareshchouhan said:
Solved: I resolved this issue with the help of friendly people in #cyanogenmod-dev @ freenode
Thanks to (in no particular order)
evilracer
nailyk
gladiac
Click to expand...
Click to collapse
Can you tell me how have you solved this issue please ? I really need a fix for this issue too. Thanks.
Can someone explain me how the TPT does the booting? According to the nvidia manual there should be a BCT image somewhere on the device, either in SPI or in eMMC but I can not find it. According to this post: https://forum.xda-developers.com/showthread.php?t=2318140 there should be 16 partitions, but it looks like I only have 10:
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 15387648 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 786432 mmcblk0p3
179 4 921600 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 143360 mmcblk0p8
259 1 20480 mmcblk0p9
259 2 12939264 mmcblk0p10
[email protected]:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2018-08-16 09:07 AP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-08-16 09:07 CC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-08-16 09:07 LX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-08-16 09:07 MC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-08-16 09:07 PA -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-08-16 09:07 SC -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-08-16 09:07 SS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-08-16 09:07 UA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-08-16 09:07 UP -> /dev/block/mmcblk0p8
As p1 is the recovery image and p2 is the kernel, I do not see any more partitions where the BCT image could be.
nvflash does not work on my device, as the APX mode is locked.
What I find a little bit worrying, is that fdisk says I have no partition table:
Code:
[email protected]:/ # fdisk -l mmcblk0
Disk mmcblk0: 15.7 GB, 15756951552 bytes
4 heads, 16 sectors/track, 480864 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk mmcblk0 doesn't contain a valid partition table
Should this command fail?
But there must be the configuration somewhere, right?
I have a TPT 1839-22G
I imaged now the whole eMMC using dd and found out that in difference to the posted partition table, the partitions BCT, PT, EBT and GP1 are missing. the Partitions SOS starts 0x100000 bytes earlier as given in the other thread.
Between 0x0 and 0x00d00000 I can find some non zero bytes but nothing which caught my attention.
Using gdisk I could restore the partition table:
Code:
GPT fdisk (gdisk) version 1.0.3
Unsupported GPT version in backup header; read 0x00000000, should be
0x00010000
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): p
Disk mmcblk0.img: 30775296 sectors, 14.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30775262
Partitions will be aligned on 2048-sector boundaries
Total free space is 30775229 sectors (14.7 GiB)
Number Start (sector) End (sector) Size Code Name
Command (? for help): r
Recovery/transformation command (? for help): b
Recovery/transformation command (? for help): p
Disk mmcblk0.img: 30775296 sectors, 14.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30775262
Partitions will be aligned on 2048-sector boundaries
Total free space is 30775229 sectors (14.7 GiB)
Number Start (sector) End (sector) Size Code Name
Recovery/transformation command (? for help): c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): y
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): p
Disk mmcblk0.img: 30775296 sectors, 14.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30775262
Partitions will be aligned on 2048-sector boundaries
Total free space is 30653 sectors (15.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 26624 38911 6.0 MiB 0700 体S
2 38912 55295 8.0 MiB 0700 乌X
3 55296 1628159 768.0 MiB 0700 偁P
4 1628160 3471359 900.0 MiB 0700 䅃C
5 3471360 3475455 2.0 MiB 0700 卍C
6 3475456 4524031 512.0 MiB 0700 䥐A
7 4524032 4564991 20.0 MiB 0700 䕓C
8 4564992 4851711 140.0 MiB 0700 单P
9 4851712 4892671 20.0 MiB 0700 䑐A
10 4892672 30771199 12.3 GiB 0700 䑕A
Which also shows, that there are no partitions before 0xd00000.
But where is the BCT stored then?