Database Users

[Q] borked internal sd card on Atrix

Hi all,
I posted this in the Atrix Q&A but it doesn't seem to have had many hits, thought I'd try my luck here (here is the original thread: http://forum.xda-developers.com/showthread.php?t=1594675) ...basically my Atrix emmc internal memory card is borked and I am trying to find a way to restore it other than SBFing to factory (which is risky and a hassle...).
rickywyatt kindly told me to execute these commands in an adb shell and to post the results:
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
well my results are as follows:
1|[email protected]:/ $ su
su
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2048 loop0
253 0 98304 zram0
179 0 15541760 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 7772160 mmcblk1
179 33 7771136 mmcblk1p1
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6np
p
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Command (m for help): ←[6nq
q
[email protected]:/ #​
anyone know what I need to do next? If anyone can interpret the output for me I'd be so grateful.
Thanks,
Mark

I'd say flashing an sbf is alot easier then that haha.
Sent from my MB860 using XDA

If i where you i'd try to leave it as if was new and take it to motorola service, they change it to a new one. If you did unlocked the bootload (i guess you did) i think that there was a way to hidde the unlocked at boot.
GL with that!

Cyanogenmod Caused Corrupted Internal SD-Card. How to reformat?

So, today I was transferring some files to my phone using the latest Cyanogenmod nightly in MTP mode. In this mode, there is no splash screen that allows you to disconnect your phone from USB mode, so I assumed that it was safe to just disconnect the USB cable when no transfer is occurring. I have done this many times with no problem.
Well, after disconnecting this time, the phone won't mount the internal SD either in the phone itself, by USB or in CWM. I did the following and it looks like the internal SD has a corrupted partition.
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[email protected]:/ # cd /dev/block
[email protected]:/dev/block # ls | grep mmcblk0
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
[email protected]:/dev/block # fdisk -l mmcblk0
Disk mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
[email protected]:/dev/block # fdisk -l mmcblk0p11
Disk mmcblk0p11: 11.8 GB, 11895046144 bytes
4 heads, 16 sectors/track, 363008 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk mmcblk0p11 doesn't contain a valid partition table
[email protected]:/dev/block #
What command would I use to reformat mmcblk0p11? mkfs.vfat /dev/block/mmcblk0p11?
Also, just a warning for others to not use MTP mode in Cyanogenmod due to this bug.

So, I did a factory reset in Cyanogenmod with the erase SD card option ticked and it looks like everything is working now. Hopefully they will soon fix the MTP splash screen so that others will not have this issue again.

[Q] [L5] [E612F] Can KDZ update change (apparent) internal SD size?

Hello!
TL/DR version: I updated a L5 (E612F - Vivo BR) with a V20 KDZ file and the internal storage, that was 8GB is seen by fdisk as ~3GB. There seems to be something wrong with the partition table. Is it possible to revert it back to the original value?
Detailed version:
My girlfriend bought a L5 (E612F - Vivo BR) and urged me to remove all the LG crap that came with the phone.
E612f is known for not being easily rootable and so on, so it was a struggle to put CM10.x in it. After many attempts and a few boot loops, I managed to use an E610 KDZ + E610 recovery and other images from this thread: http://forum.xda-developers.com/showthread.php?t=2186161
The problem is that fdisk reports that the internal SD has only ~3GB of size, but the device ghas 8GB internal SD. Because of that, she gets low space errors all the time:
Code:
1|[email protected]:/ # 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 128 1003+ 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 256 1024 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 257 465152 3719168 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8193 8704 4096 47 Unknown
/dev/block/mmcblk0p6 8705 9216 4096 2c Unknown
/dev/block/mmcblk0p7 9217 9728 4096 58 Unknown
/dev/block/mmcblk0p8 9729 12800 24576 77 Unknown
/dev/block/mmcblk0p9 12801 13824 8192 48 Unknown
/dev/block/mmcblk0p10 13825 14336 4096 4a Unknown
/dev/block/mmcblk0p11 14337 14848 4096 4b Unknown
/dev/block/mmcblk0p12 14849 18432 28672 49 Unknown
/dev/block/mmcblk0p13 18433 22016 28672 6c Unknown
/dev/block/mmcblk0p14 22017 100096 624640 83 Linux
/dev/block/mmcblk0p15 100353 101376 8192 83 Linux
/dev/block/mmcblk0p16 101377 114176 102400 83 Linux
/dev/block/mmcblk0p17 114177 115200 8192 60 Unknown
/dev/block/mmcblk0p18 115201 116224 8192 83 Linux
/dev/block/mmcblk0p19 116225 117760 12288 6b Unknown
/dev/block/mmcblk0p20 117761 470656 2823168 83 Linux
/dev/block/mmcblk0p21 471041 471552 4096 ff Unknown
/dev/block/mmcblk0p22 471553 471680 1024 ff Unknown
/dev/block/mmcblk0p23 472065 474112 16384 83 Linux
Could the KDZ from another version (E610) be the culprit for this? Any idea how to deal with it? Thanks!

boot.img too large lenovo vibe p1ma40 [MT6735M]

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.

Where is the BCT image on the TPT?

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?