Database Info

[REF][INFO] SCH-I535 Partition Table

Google found this for me somewhere...
So I thought I'll share it with you. Not sure if this has been posted before, but I didn't find it in any search here.
I believe it's for the US SGS3 (SCH-I535), but I am not 100%, only ~85% sure.
{
"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"
}
@mods: Not sure this is the right place to post this, please move to appropriate place if necessary.
If you're looking for the 32 GB PIT file, you can look in this thread.
If you're looking for the GT-I9300 partition table, look in the thread:
"[REF] GT-I9300 PIT and Flash Analysis [WIP]"

E:V:A said:
Google found this for me somewhere...
So I thought I'll share it with you. Not sure if this has been posted before, but I didn't find it in any search here.
I believe it's for the US SGS3 (SCH-I535), but I am not 100%, only ~85% sure.
@mods: Not sure this is the right place to post this, please move to appropriate place if necessary.
If you're looking for the 32 GB PIT file, you can look in this thread.
Click to expand...
Click to collapse
Thank you for the table dude!
Sent from my SCH-I535 using xda app-developers app

Hey,
Is there a way to extract this kind of informations on a working device ? (i'm interested in HEX values for sectors)

vache said:
Hey,
Is there a way to extract this kind of informations on a working device ? (i'm interested in HEX values for sectors)
Click to expand...
Click to collapse
Check here: http://forum.xda-developers.com/showpost.php?p=30618458&postcount=57
You should be able to convert those bite sizes to hex (also, the table above has a column for hex and the number of sectors in each partition...)
I that what you're looking for?

In fact i want to find fist sector number for each partition to be able to write on it and try to restore my phone. (A bit off topic cause it's not a Samsung phone, but also using MSM8960)

For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!

E:V:A said:
For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!
Click to expand...
Click to collapse
You, sir, are big pimpin'. Thanks
Sent from my SCH-I535 using xda app-developers app

E:V:A said:
For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!
Click to expand...
Click to collapse
You're missing a few mmc blocks for the SCA-I535 (d2vzw). Here they are, but I hve no idea what they do:
Code:
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk1p1
/dev/block/mmcblk1p2
The latter two blocks suggest a second eMMC chip with its own NAND storage.
I working on a tool that backs up the SCH-I535 directly to your computer using adb. You can find it HERE. For now, Its only setup for partitions and data that one might use in recovery like CWM or TWRP or even ODIN. I haven't iterated out all the blocks into backup code yet, but I am working on it. I hope to have this list:
Code:
## BLOCK_LIST ##
# Conventions for the list o block are as follows
# [VAR_NAME]="/dev/blockmmcblk#p##" #-> [Known As] ([FS], [mount point if visible], [description]) == [odin img file]
MOD_BLK="/dev/block/mmcblk0p1" #-> CDMA Modem (vfat, mounts at /firmware, its the CDMA modem) == NON-HLOS.bin
SB1_BLK="/dev/block/mmcblk0p2" #-> sbl1 (samsung proprietary fs, sammys odd way of booting part1) == sbl1.mbn
SB2_BLK="/dev/block/mmcblk0p3" #-> sbl2 (samsung proprietary fs, sammys odd way of booting part2) == sbl2.mbn
SB3_BLK="/dev/block/mmcblk0p4" #-> sbl3 (samsung proprietary fs, sammys odd way of booting part3) == sbl3.mbn
ABT_BLK="/dev/block/mmcblk0p5" #-> aboot (unknown fs, this is the bootloader) == aboot.mbn
RPM_BLK="/dev/block/mmcblk0p6" #-> rpm (unknown fs, something to do with the radio) == rpm.mbn
BOT_BLK="/dev/block/mmcblk0p7" #-> boot (yaffs2, boot image contains the kernel) == boot.img
STZ_BLK="/dev/block/mmcblk0p8" #-> tz (porbably samsung proprietary fs, samsungs "Trust Zone" referenced in the sbl boot process) == tz.mbn
PAD_BLK="/dev/block/mmcblk0p9" #-> pad (unknown fs, aka PIT )
PRM_BLK="/dev/block/mmcblk0p10" #-> param (unknown fs, pretty much empty exept for one octet)
EFS_BLK="/dev/block/mmcblk0p11" #-> /efs (ext4, mounts at /efs, has device info like IMEI and MEID)
LT1_BLK="/dev/block/mmcblk0p12" #-> modemst1 (unknown fs, LTE modem 1)
LT2_BLK="/dev/block/mmcblk0p13" #-> modemst2 (unknown fs, LTE modem 2)
SYS_BLK="/dev/block/mmcblk0p14" #-> /system (ext4, everything under /system) == system.img.ext4
DAT_BLK="/dev/block/mmcblk0p15" #-> userdata (ext4. mounts at /data, contains internal sdcard as well at /data/media)
PST_BLK="/dev/block/mmcblk0p16" #-> /persist && /tombstones (ext4, contains very little data) == persist.img.ext4
CHE_BLK="/dev/block/mmcblk0p17" #-> /cache (ext4, its the cache baby) == cache.img.ext4
REC_BLK="/dev/block/mmcblk0p18" #-> recovery (ext4??, recovery image like CWM and TWRP?) == recovery.img
OTA_BLK="/dev/block/mmcblk0p19" #-> fota (ext4, found at /cache/fota, its where OTA updates are stored)
BAK_BLK="/dev/block/mmcblk0p20" #-> backup (unknown fs, where factory reset images are stored?)
FSG_BLK="/dev/block/mmcblk0p21" #-> fsg (unknown fs, may contain files used in factory wipe, somehow linked to the grow partition)
SSD_BLK="/dev/block/mmcblk0p22" #-> ssd (unknown fs maybe ramfs, "Secure Software Download" don't know what its used for)
GRW_BLK="/dev/block/mmcblk0p23" #-> grow (unknown fs, i think this has something to do with ext4 sparse images)
# WTF!?!?!?!?!?!!???
DK1_BLK="/dev/block/mmcblk0boot0" #-> may have something to do with booting (duh, but what)
DK2_BLK="/dev/block/mmcblk0boot1" #-> may have something to do with booting (duh, but what)
DK3_BLK="/dev/block/mmcblk1p1" #-> no idea
DK4_BLK="/dev/block/mmcblk1p2" #-> no idea
# NOTES:
# samsung seems to refer to 4 types of file systems; cgroup, ecryptfs, ext4, fuse
# could ecryptfs be the same as samsungs proprietary file system?
## END_BLOCK_LIST ##
Included in the tool, as options to backup. So far I have working code for System, Data (makes a tar and skips /data/media), Recovery, Userdata (HUGE), Modemst1, Modemst2, CDMA modem, Cache and Boot. But I do want to have all mmc blocks as options because I need a disaster recovery plan as well.
There's still alot of work to be done on it, but for now I use it to back up my device before flashing a rom. Saves on internal storage.
I'll try and convert my block list to you format used in the EL GRANDE Partition Table Reference as soon as possible. I dunno if you'll need it though. I do have alot of knowledge on GPT (GUID Partition Table) formatted storage as well as how EFI vs MBR can work withing such a table. But I can discuss that on the other thread.
I've read what you have so far in that thread and its very helpful.
Ta,
ALQI

Could you follow the instructions in post #2, of the thread I posted above, to obtain an output of parted and fdisk , for both mmcblk0 and mmcblk1?

E:V:A said:
Could you follow the instructions in post #2, of the thread I posted above, to obtain an output of parted and fdisk , for both mmcblk0 and mmcblk1?
Click to expand...
Click to collapse
Not a problem mate. I hope this fits your format.
Device info:
Code:
General Device Name: Samsung Galaxy S3
Manufacturer Product Name: SCH-I535
Processor: Snapdragon S4plus
AOS version: Android JB 4.1.1
Radio FW version: I535VRLHD
System FW version: I535VZWBLI5
Service Provider/ Branding: Verizon
Country: USA
ROM: Almost Stock JellyBean I535VRBLI5 (my own cooking from dsixda's andoid kitchen, added bash binary, nano, busybox and root)
fidsk output for mmcblk0:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 58.2M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61059087
Number Start (sector) End (sector) Size Code Name
1 8192 131071 120K 0700 modem
2 131072 131327 256 0700 sbl1
3 131328 131839 512 0700 sbl2
4 131840 132863 1024 0700 sbl3
5 132864 136959 4096 0700 aboot
6 136960 137983 1024 0700 rpm
7 137984 158463 20480 0700 boot
8 158464 159487 1024 0700 tz
9 159488 160511 1024 0700 pad
10 160512 180991 20480 0700 param
11 180992 208895 27904 0700 efs
12 208896 215039 6144 0700 modemst1
13 215040 221183 6144 0700 modemst2
14 221184 3293183 3000K 0700 system
15 3293184 59252735 53.3M 0700 userdata
16 59252736 59269119 16384 0700 persist
17 59269120 60989439 1680K 0700 cache
18 60989440 61009919 20480 0700 recovery
19 61009920 61030399 20480 0700 fota
20 61030400 61042687 12288 0700 backup
21 61042688 61048831 6144 0700 fsg
22 61048832 61048847 16 0700 ssd
23 61048848 61059087 10240 0700 grow
fdisk for those odd mmcblk0boot# devs:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk0boot0
Disk /dev/block/mmcblk0boot0: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0boot0 doesn't contain a valid partition table
sh-4.2# fdisk -l /dev/block/mmcblk0boot1
Disk /dev/block/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0boot1 doesn't contain a valid partition table
NOTE: I'm still not sure what these mmcblk0boot# blocks are, but they are there in the file system under /dev/block/ as well as /dev/block/platform/by-name.
fdisk output mmcblk1:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1872 15032320 b Win95 FAT32
/dev/block/mmcblk1p2 1872 1937 524288 82 Linux swap
NOTE: mmcblk1 is the external sdcard (i'm dumb cause I thought it was a seperate eMMC chip, but its just plain old MMC) THat little swap space is left over from when I had the OG Droid.
parted output for mmcblk0:
Code:
sh-4.2# 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) p
p
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Ignore
Ignore
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 12239 blocks) or
continue with the current setting?
Fix/Ignore? Ignore
Ignore
Model: MMC MBG8FB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 30.3GB 28.7GB ext4 userdata
16 30.3GB 30.3GB 8389kB ext4 persist
17 30.3GB 31.2GB 881MB ext4 cache
18 31.2GB 31.2GB 10.5MB recovery
19 31.2GB 31.2GB 10.5MB fota
20 31.2GB 31.3GB 6291kB backup
21 31.3GB 31.3GB 3146kB fsg
22 31.3GB 31.3GB 8192B ssd
23 31.3GB 31.3GB 5243kB grow
(parted)
NOTE: The second warning with parted, is because the device uses a hybrid MBR/GPT table (gdisk shows us this). This is kinda like dual booting a Mac with Windows and Mac OS X. Also, the "backup" error is because the gpt table backup is in "pad" (aka PIT).
WARNING: Be careful with parted, make sure you tell it to "Ignore" and errors it might find. Also you have to type "quit" to get it to exit from interactive mode.
parted output for mmcblk0boot0
Code:
sh-4.2# parted /dev/block/mmcblk0boot0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0boot0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Error: /dev/block/mmcblk0boot0: unrecognised disk label
(parted)
NOTE: No need to run parted on mmcblk1 (cause its the external sdcard) nor mmcblk0boot# cause its not part of the gpt. Same goes for gdisk.
gdisk output for mmcblk0
Code:
sh-4.2# gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61059087
Partitions will be aligned on 16-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 131071 60.0 MiB 0700 modem
2 131072 131327 128.0 KiB FFFF sbl1
3 131328 131839 256.0 KiB FFFF sbl2
4 131840 132863 512.0 KiB FFFF sbl3
5 132864 136959 2.0 MiB FFFF aboot
6 136960 137983 512.0 KiB FFFF rpm
7 137984 158463 10.0 MiB FFFF boot
8 158464 159487 512.0 KiB FFFF tz
9 159488 160511 512.0 KiB FFFF pad
10 160512 180991 10.0 MiB 8300 param
11 180992 208895 13.6 MiB 8300 efs
12 208896 215039 3.0 MiB FFFF modemst1
13 215040 221183 3.0 MiB FFFF modemst2
14 221184 3293183 1.5 GiB 8300 system
15 3293184 59252735 26.7 GiB 8300 userdata
16 59252736 59269119 8.0 MiB 8300 persist
17 59269120 60989439 840.0 MiB 8300 cache
18 60989440 61009919 10.0 MiB FFFF recovery
19 61009920 61030399 10.0 MiB FFFF fota
20 61030400 61042687 6.0 MiB 8300 backup
21 61042688 61048831 3.0 MiB FFFF fsg
22 61048832 61048847 8.0 KiB FFFF ssd
23 61048848 61059087 5.0 MiB 8300 grow
Again, be very careful when running these disk utilities because they are not meant to handle a hybrid boot. Samsung's odd way of booting makes this kind of analysis difficult because of the prorieray fs they use for sbl1 through sbl3.
Click to expand...
Click to collapse
Wow that's alot of formatting.
Ta,
ALQI

Thanks a lot! In particular to remind people of the "warnings". I'll add that to the other thread.

Hey guys,
I have a I535 S3 that was hard bricked because of a bad flash, I want to try and repair it with JTAG but I don't have the necessary partition boot files...and it's not a supported version either.
Does anybody have a backup of the first 10 partitions from Modem to Param in .bin format?
I know it's possible to do such a backup with adb. or can somebody point me in the right direction?
Thank you!

Sure, I'll dd those for you tomorrow and pm you a Dropbox link.
For the first 10 partitions it shouldn't matter, but do you have a 16GB or 32Gb?
Sent from my SCH-I535 using xda app-developers app

It's the 16Gb version.
Thank you very much... You're a life savor!
Sent from my SGH-I897 using Tapatalk 2

PM sent.

Thank you!
Got them.. Hopefully it works!
Sent from my SGH-I897 using Tapatalk 2

E:V:A said:
Thanks a lot! In particular to remind people of the "warnings". I'll add that to the other thread.
Click to expand...
Click to collapse
As this is GTP parition it uses differing handles for the partition type
here is a example snip of the qualcomm partition.xml for a gtp partition
Code:
<partition label="modem" size_in_kb="65536" type="EBD0A0A2-B9E5-4433-87C0-68B6B72699C7" bootable="false" readonly="true" filename="NON-HLOS.bin"/>
<partition label="sbl1" size_in_kb="128" type="[COLOR="Red"][B]DEA0BA2C-CBDD-4805-B4F9-F428251C3E98[/B][/COLOR]" bootable="false" readonly="false" filename="sbl1.mbn"/>
<partition label="sbl2" size_in_kb="256" type="8C6B52AD-8A9E-4398-AD09-AE916E53AE2D" bootable="false" readonly="false" filename="sbl2.mbn"/>
<partition label="sbl3" size_in_kb="512" type="05E044DF-92F1-4325-B69E-374A82E97D6E" bootable="false" readonly="false" filename="sbl3.mbn"/>
<partition label="aboot" size_in_kb="512" type="400FFDCD-22E0-47E7-9A23-F16ED9382388" bootable="false" readonly="false" filename="emmc_appsboot.mbn"/>
<partition label="rpm" size_in_kb="512" type="098DF793-D712-413D-9D4E-89D711772228" bootable="false" readonly="false" filename="rpm.mbn"/>
<partition label="boot" size_in_kb="10240" type="20117f86-E985-4357-B9EE-374BC1D8487D" bootable="false" readonly="true" filename="boot.img" />
<partition label="tz" size_in_kb="512" type="A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4" bootable="false" readonly="false" filename="tz.mbn"/>
<partition label="pad" size_in_kb="1" type="004A6838-062A-44DF-8152-4F340C05225D" bootable="false" readonly="false" filename="" />
<partition label="modemst1" size_in_kb="3072" type="2013373E-1AC4-4131-B0F8-9158F9654F4F" bootable="false" readonly="false" filename="" />
<partition label="modemst2" size_in_kb="3072" type="2013373E-1AC4-4131-B0F8-9158F9654F4F" bootable="false" readonly="false" filename="" />
<partition label="system" size_in_kb="262144" type="0FC63DAF-8483-4772-8E79-3D69D8477DE4" bootable="false" readonly="true" filename="system.img.ext4" sparse="true"/>
Click to expand...
Click to collapse
could we see if my compiled binaries for gtp partitions return the UUID for type ?
Original Post http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
Binaries
http://www.sendspace.com/file/5b3jdc
Example output from partx ( non gtp partition, i dont have gtp partition)
Code:
[email protected]:/ # /data/test/partx
Usage:
partx [-a|-d|-s] [--nr <n:m> | <partition>] <disk>
Options:
-a, --add add specified partitions or all of them
-d, --delete delete specified partitions or all of them
-l, --list list partitions (DEPRECATED)
-s, --show list partitions
-b, --bytes print SIZE in bytes rather than in human readable format
-g, --noheadings don't print headings for --show
-n, --nr <n:m> specify the range of partitions (e.g. --nr 2:4)
-o, --output <type> define which output columns to use
-P, --pairs use key="value" output format
-r, --raw use raw output format
-t, --type <type> specify the partition type (dos, bsd, solaris, etc.)
-v, --verbose verbose mode
-h, --help display this help and exit
-V, --version output version information and exit
Available columns (for --show, --raw or --pairs):
NR partition number
START start of the partition in sectors
END end of the partition in sectors
SECTORS number of sectors
SIZE human readable size
NAME partition name
UUID partition UUID
TYPE partition type hex or uuid
FLAGS partition flags
SCHEME partition table type (dos, gpt, ...)
For more details see partx(8).
1|[email protected]:/ # /data/test/partx -l /dev/block/mmcblk0
# 1: 1- 204800 ( 204800 sectors, 104 MB)
# 2: 204801- 205800 ( 1000 sectors, 0 MB)
# 3: 205801- 208800 ( 3000 sectors, 1 MB)
# 4: 208801- 30777343 ( 30568543 sectors, 15651 MB)
# 5: 212992- 213991 ( 1000 sectors, 0 MB)
# 6: 221184- 225279 ( 4096 sectors, 2 MB)
# 7: 229376- 234375 ( 5000 sectors, 2 MB)
# 8: 237568- 258047 ( 20480 sectors, 10 MB)
# 9: 262144- 263143 ( 1000 sectors, 0 MB)
#10: 270336- 271335 ( 1000 sectors, 0 MB)
#11: 278528- 279527 ( 1000 sectors, 0 MB)
#12: 286720- 307199 ( 20480 sectors, 10 MB)
#13: 311296- 511999 ( 200704 sectors, 102 MB)
#14: 516096- 522239 ( 6144 sectors, 3 MB)
#15: 524288- 530431 ( 6144 sectors, 3 MB)
#16: 532480- 538623 ( 6144 sectors, 3 MB)
#17: 540672- 741375 ( 200704 sectors, 102 MB)
#18: 745472- 751615 ( 6144 sectors, 3 MB)
#19: 753664- 759807 ( 6144 sectors, 3 MB)
#20: 761856- 767999 ( 6144 sectors, 3 MB)
#21: 770048- 790527 ( 20480 sectors, 10 MB)
#22: 794624- 815103 ( 20480 sectors, 10 MB)
#23: 819200- 839679 ( 20480 sectors, 10 MB)
#24: 843776- 3911679 ( 3067904 sectors, 1570 MB)
#25: 3915776- 8114175 ( 4198400 sectors, 2149 MB)
#26: 8118272- 8736767 ( 618496 sectors, 316 MB)
#27: 8740864- 9005055 ( 264192 sectors, 135 MB)
#28: 9011200- 10035199 ( 1024000 sectors, 524 MB)
#29: 10035200- 30777343 ( 20742144 sectors, 10619 MB)
[email protected]:/ #
lsblk output
Code:
[email protected]:/ # /data/test/lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 2.1M 0 loop
`-278cb90965c39ee2acfea003ec39e4f5 (dm-0)
254:0 0 2.1M 0 dm /mnt/asec/com.androirc-1
loop1 7:1 0 5.1M 0 loop
`-ce28924bd3284f292fdd7955925746bc (dm-1)
254:1 0 5.1M 0 dm /mnt/asec/com.quoord.tapatalkxda.activity-
loop2 7:2 0 16.3M 0 loop
`-2ef6fb57bc43988a90c9add8bc514237 (dm-2)
254:2 0 16.3M 0 dm /mnt/asec/com.loumasoft.amiga500musiccolle
mmcblk0 179:0 0 14.7G 0 disk
|-mmcblk0p1 179:1 0 100M 0 disk
|-mmcblk0p2 179:2 0 500K 0 disk
|-mmcblk0p3 179:3 0 1.5M 0 disk
|-mmcblk0p4 179:4 0 1K 0 disk
|-mmcblk0p5 179:5 0 500K 0 disk
|-mmcblk0p6 179:6 0 2M 0 disk
|-mmcblk0p7 179:7 0 2.5M 0 disk
|-mmcblk0p8 179:8 0 10M 0 disk
|-mmcblk0p9 179:9 0 500K 0 disk
|-mmcblk0p10 179:10 0 500K 0 disk
|-mmcblk0p11 179:11 0 500K 0 disk
|-mmcblk0p12 179:12 0 10M 0 disk
|-mmcblk0p13 179:13 0 98M 0 disk
|-mmcblk0p14 179:14 0 3M 0 disk
|-mmcblk0p15 179:15 0 3M 0 disk
|-mmcblk0p16 179:16 0 3M 0 disk
|-mmcblk0p17 179:17 0 98M 0 disk
|-mmcblk0p18 179:18 0 3M 0 disk
|-mmcblk0p19 179:19 0 3M 0 disk
|-mmcblk0p20 179:20 0 3M 0 disk
|-mmcblk0p21 179:21 0 10M 0 disk
|-mmcblk0p22 179:22 0 10M 0 disk
|-mmcblk0p23 179:23 0 10M 0 disk
|-mmcblk0p24 179:24 0 1.5G 0 disk
|-mmcblk0p25 179:25 0 2G 0 disk
|-mmcblk0p26 179:26 0 302M 0 disk
|-mmcblk0p27 179:27 0 129M 0 disk
|-mmcblk0p28 179:28 0 500M 0 disk
`-mmcblk0p29 179:29 0 9.9G 0 disk
mmcblk1 179:32 0 14.4G 0 disk
`-mmcblk1p1 179:33 0 14.4G 0 disk
[email protected]:/ #
sample output from blkid
Code:
blkid from util-linux 2.22 (libblkid 2.22.0, 04-Sep-2012)
Usage:
blkid -L <label> | -U <uuid>
blkid [-c <file>] [-ghlLv] [-o <format>] [-s <tag>]
[-t <token>] [<dev> ...]
blkid -p [-s <tag>] [-O <offset>] [-S <size>]
[-o <format>] <dev> ...
blkid -i [-s <tag>] [-o <format>] <dev> ...
Options:
-c <file> read from <file> instead of reading from the default
cache file (-c /dev/null means no cache)
-d don't encode non-printing characters
-h print this usage message and exit
-g garbage collect the blkid cache
-o <format> output format; can be one of:
value, device, export or full; (default: full)
-k list all known filesystems/RAIDs and exit
-s <tag> show specified tag(s) (default show all tags)
-t <token> find device with a specific token (NAME=value pair)
-l look up only first device with token specified by -t
-L <label> convert LABEL to device name
-U <uuid> convert UUID to device name
-v print version and exit
<dev> specify device(s) to probe (default: all devices)
Low-level probing options:
-p low-level superblocks probing (bypass cache)
-i gather information about I/O limits
-S <size> overwrite device size
-O <offset> probe at the given offset
-u <list> filter by "usage" (e.g. -u filesystem,raid)
-n <list> filter by filesystem type (e.g. -n vfat,ext3)
4|[email protected]:/ # /data/test/blkid
/dev/block/mmcblk0: PTTYPE="dos"
/dev/block/mmcblk0p13: SEC_TYPE="msdos" UUID="7365-DAB3" TYPE="vfat"
/dev/block/mmcblk0p17: SEC_TYPE="msdos" UUID="29B2-ACBF" TYPE="vfat"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="c63c0c30-700c-4874-9acd-fd507d02000a" TYPE="ext4"
/dev/block/mmcblk0p25: UUID="36caf8ff-15bf-4c24-92e0-0c84a21f3b0c" TYPE="ext4"
/dev/block/mmcblk0p26: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p27: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p28: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p29: UUID="887F-1DF5" TYPE="vfat"
/dev/block/mmcblk1: PTTYPE="dos"
/dev/block/mmcblk1p1: UUID="64A1-1B57" TYPE="vfat"
[email protected]:/ #
most will use sgdisk/partx on gtp based partitions. sgdisk also supports the partition info cloning like sfdisk does.
See sfdisk in util-linux sources for more info
darkspr1te

letinsh said:
PM sent.
Click to expand...
Click to collapse
By the way.. Those partitions worked great for jtag.
Thanks again!
Sent from my I897 AoCP CP 4.6

spagman72 said:
Hey guys,
I have a I535 S3 that was hard bricked because of a bad flash, I want to try and repair it with JTAG but I don't have the necessary partition boot files...and it's not a supported version either.
Does anybody have a backup of the first 10 partitions from Modem to Param in .bin format?
I know it's possible to do such a backup with adb. or can somebody point me in the right direction?
Thank you!
Click to expand...
Click to collapse
Hey, I have the sch-i535 Verizon. Do you want me to give it to you?

Israelleite said:
Hey, I have the sch-i535 Verizon. Do you want me to give it to you?
Click to expand...
Click to collapse
spagman72 said:
By the way.. Those partitions worked great for jtag.
Thanks again!
Sent from my I897 AoCP CP 4.6
Click to expand...
Click to collapse
already got him taken care of

[Q] Rooted Galaxy Note N7000

Hey guys.
I reccenty flashed my Galaxy note using Root_SuperSU.0.96-Busybox.1.20.2-S2, All went well expect now i cannot install any custom roms.
I have been trying to install Asylum_CM10.1_20130201_n7000 however i keep getting "Status 7, installation aborted"
here is my log:
Starting recovery on Fri Feb 1 09:16:56 2013
[initialize ui and event]
pixel format -> GGL_PIXEL_FORMAT_BGRA_8888
framebuffer: fd 4 (800 x 1280)
[collecting table information]
recovery filesystem table
=========================
0 '/tmp' 'ramdisk' '(null)' '(null)' 0
1 '/efs' 'ext4' '/dev/block/mmcblk0p1' '(null)' 0
2 '/boot' 'emmc' '/dev/block/mmcblk0p2' '(null)' 0
3 '/recovery' 'emmc' '/dev/block/mmcblk0p6' '(null)' 0
4 '/cache' 'ext4' '/dev/block/mmcblk0p7' '(null)' 0
5 '/system' 'ext4' '/dev/block/mmcblk0p9' '(null)' 0
6 '/data' 'ext4' '/dev/block/mmcblk0p10' '(null)' -16384
7 '/preload' 'ext4' '/dev/block/mmcblk0p12' '(null)' 0
8 '/sdcard' 'vfat' '/dev/block/mmcblk1p1' '/dev/block/mmcblk1' 0
9 '/sdcard1' 'vfat' '/dev/block/mmcblk0p11' '(null)' 0
emmc_checksum fail.
[initialize init-recovery]
#mount /system
stat() of /dev/block/mmcblk0p9 succeeded on try 1
/system sucessfully mounted
#unmount /cache
/cache sucessfully unmounted
#exec -f /system/bin/e2fsck -v -y /dev/block/mmcblk0p7
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p7: clean, 23/12800 files, 3094/51200 blocks
#insmod -f -v /system/lib/modules/exfat_core.ko
trace: insmod_main: /system/lib/modules/exfat_core.ko
trace: insmod_main: 1
trace: __out_return: _do_insmod :: can't open '/system/lib/modules/exfat_core.ko' (No such file or directory)
#insmod -f -v /system/lib/modules/exfat_fs.ko
trace: insmod_main: /system/lib/modules/exfat_fs.ko
trace: insmod_main: 1
trace: __out_return: _do_insmod :: can't open '/system/lib/modules/exfat_fs.ko' (No such file or directory)
#lsmod
exfat_fs 17079 0 - Live 0xbf013000 (P)
exfat_core 59555 1 exfat_fs, Live 0xbf000000 (P)
#mount /cache
stat() of /dev/block/mmcblk0p7 succeeded on try 1
/cache sucessfully mounted
#ls /cache/recovery/
-rw-r----- root root 9037 2013-02-01 08:57 last_log
-rw-r--r-- root root 43 2013-02-01 08:57 last_install
-rw------- root root 697 2013-02-01 09:16 11-rommanager.sh
-rw------- root root 3100489 2013-02-01 09:16 RomManager.apk
-rw------- root root 156 2013-02-01 09:16 restorerommanager.sh
-rw------- root root 704 2013-02-01 09:16 extendedcommand
-rw------- root root 33 2013-02-01 09:16 .salted_hash
-rw------- root root 34 2013-02-01 09:16 command
#mount /data
stat() of /dev/block/mmcblk0p10 succeeded on try 1
/data sucessfully mounted
#fcut --limited-file-size=64k -f /data/log/recovery_log.txt /tmp/recovery_backup.txt
trace: __out_return: _do_fcut :: failed lstat '/data/log/recovery_log.txt' (No such file or directory)
/system sucessfully unmounted
/cache sucessfully unmounted
/data sucessfully unmounted
running init-recovery time : 0.243s
[collecting command]
stat() of /dev/block/mmcblk0p7 succeeded on try 1
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=CACHE:update.zip"
previous_runs = 0
send_intent = (null)
update_package = CACHE:update.zip
att_fota_update = 0
tmo_fota_update = 0
wipe_data = 0, wipe_cache = 0,wipe_sdcard = 0,delete_data = 0,wipe_data_crypto = 0
show_ui_text = 0
update_factory_csc = 0,update_home_csc = 0
carry_out = (null)
(replacing path "CACHE:update.zip" with "/cache/update.zip")
[property list]
ro.boot.serialno=0019f1002f2cae
ro.sec_debug.enable=0
ro.serialno=0019f1002f2cae
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
stat() of /dev/block/mmcblk0p1 succeeded on try 1
[Installing package]
-- Installing package...
Finding update package...
I:Update location: /cache/update.zip
Opening update package...
I:2 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
signed len : 1879580
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
sh: you need to specify whom to kill
sh: invalid number 'root'
sh: can't kill pid 21096: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/recovery'
run_program: child exited with status 1
script result was [256]
Starting recovery on Fri Feb 1 09:17:00 2013
framebuffer: fd 4 (800 x 1280)
ClockworkMod Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /emmc vfat /dev/block/mmcblk0p11 (null) 0
9 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.serialno=0019f1002f2cae
ro.sec_debug.enable=0
ro.serialno=0019f1002f2cae
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
05c6f41850f6980d080d08215614ab6e
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.1.7");
ui_print("1 February 2013");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/11-rommanager.sh");
run_program("/tmp/recovery/11-rommanager.sh", "place");
run_program("/sbin/umount", "/system");
format("/data");
format("/sd-ext");
assert(install_zip("/sdcard/Asylum_CM10.1_20130201_n7000.zip"));
format("/cache");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/restorerommanager.sh");
run_program("/tmp/recovery/restorerommanager.sh");
run_program("/sbin/umount", "/system");
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.1.7
1 February 2013
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Formatting /data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Formatting /sd-ext...
-- Installing: /sdcard/Asylum_CM10.1_20130201_n7000.zip
Finding update package...
I:Update location: /sdcard/Asylum_CM10.1_20130201_n7000.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" ||
getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" ||
getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" ||
getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
E:Error in /sdcard/Asylum_CM10.1_20130201_n7000.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Asylum_CM10.1_20130201_n7000.zip")
Thanks for your help!

sensation XE make_extf4fs failed on /dev/block/mmc/...

Hi, I know that there are lots of topics like that but I didn't find any of those helpful.
I was just doing some basic changes to the settings of the phone, and then suddenly it rebooted to recovery mode, and it doesn't boot anymore.
I get this error when I want to format the data partition:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p23
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p23
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p24
E:format_volume: make_extf4fs failed on /dev/block/mmc/blk0p24
formating /sdcard/.android_secure...
Data wipe complete.
And I also get the same error when I want to format the system partition, except this time the blk0p22 block causes error.
The phone's s-off, with 4ext recovery touch, hboot 1.27.1111, and it was running viperS 5.3.0 when this happened.
what do I have to do?
thanks. :good:

Now I got to the /dev/block/mmc/ via the adb shell, the following files are in the directory:
Code:
ls
loop0 loop7 mmcblk0p14 mmcblk0p20 mmcblk0p27 mmcblk0p4 mmcblk1p
1
loop1 mmcblk0 mmcblk0p15 mmcblk0p21 mmcblk0p28 mmcblk0p5 platform
loop2 mmcblk0p1 mmcblk0p16 mmcblk0p22 mmcblk0p29 mmcblk0p6
loop3 mmcblk0p10 mmcblk0p17 mmcblk0p23 mmcblk0p3 mmcblk0p7
loop4 mmcblk0p11 mmcblk0p18 mmcblk0p24 mmcblk0p30 mmcblk0p8
loop5 mmcblk0p12 mmcblk0p19 mmcblk0p25 mmcblk0p31 mmcblk0p9
loop6 mmcblk0p13 mmcblk0p2 mmcblk0p26 mmcblk0p32 mmcblk1
As written in this link, I have put parted to the sbin directory, now when I try to format the directory I get this error:
Code:
~ # parted /dev/block/mmc/ mkfs ext4
parted /dev/block/mmc/ mkfs ext4
Error: Could not stat device /dev/block/mmc/ - No such file or directory.
Retry/Cancel?
what should I do now? am I doing the right thing?
thanks.

the system/data partitions are not even mounting:
Code:
mount -a
mount: mounting /dev/block/mmcblk0p23 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p22 on /system failed: Invalid argument
and when I try to mount the cache partition:
Code:
mount cache
mount: mounting /dev/block/mmcblk0p24 on /cache failed: Device or resource busy
Is there anyway that I can change the internal memory chip without changing the whole motherboard?
thanks.
edit:
I get this when I run the parted and then I send mkfs 1 ext3 or ext4:
Code:
(parted) mkfs 1 ext4
mkfs 1 ext4
mkfs 1 ext4
Error: /dev/block/mmcblk0: unrecognised disk label
(parted) mkfs 1 ext3
mkfs 1 ext3
mkfs 1 ext3
Error: /dev/block/mmcblk0: unrecognised disk label

any solution?

Unable to encrypt with CM12 on XT1031

Device: XT1031
Recovery: twrp-3.0.2-0-falcon.img
ROM: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip
Steps taken:
1. Factory wipe
2. Install Cm12
2. Set unlock PIN
3. Encrypt from Settings menu
The phone shows the animated CM logo, then briefly another animated logo. Then the encryption process appears to crash back to the PIN entry screen. The error message:
Unfortunately, the process "com.android.phone" has stopped
Click to expand...
Click to collapse
appears.
Here are the logcat results after I press the "Encrypt phone" button that kicks off the attempted encryption process:
http://pastebin.com/0jurEY8q
Some lines that stand out to me as potentially relevant:
Code:
19: E/Cryptfs ( 210): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
20: E/Cryptfs ( 210): Not a valid ext4 superblock
21: E/Cryptfs ( 210): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
115: E/Cryptfs ( 210): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
116: E/Cryptfs ( 210): Not a valid ext4 superblock
117: E/Cryptfs ( 210): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
2041: D/VoldCmdListener( 210): cryptfs getpw
2042: D/VoldCmdListener( 210): cryptfs clearpw
The E and D prefixes in logcat mean "Error" and "Debug", respectively.
I also tried using adb shell to run the "vdc cryptfs enablecrypto inplace (password here)" command to encrypt, but vdc isn't installed and I'm not sure how to install it.

After reading this thread https://web.archive.org/web/2016031...ryption-does-not-start-stuck-at-splash-screen
I also decided to try reducing my /data partition by 32768 blocks.
~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=446188k,nr_inodes=111547,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=446188k,nr_inodes=111547)
/dev/block/mmcblk0p33 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p36 on /data type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,active_logs=6)
/dev/block/mmcblk0p36 on /sdcard type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,active_logs=6)
Click to expand...
Click to collapse
my /data is mounted on /dev/block/mmcblk0p36
~ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
259 4 5791616 mmcblk0p36
Click to expand...
Click to collapse
size: 5791616 blocks. to reduce by 32768, 5791616 - 32768 = 5758848
From TWRP, I unmounted /data, then ran:
~ # mke2fs -T ext4 -L data /dev/block/mmcblk0p36 5758848
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: done
Filesystem label=data
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
360448 inodes, 1439712 blocks
71985 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1476395008
44 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Click to expand...
Click to collapse
After rebooting into normal mode, the animated logo took a minute or two to clear before going to the a series of "Android is starting... Optimizing app x of 86". The modification to /data appeared to wipe my files there, so I had to reconfigure the settings, setting the PIN for the lock screen again, and enabling encryption. After enabling encryption this time it entered a loop: show the animated CM logo for about a one to several minutes, and then went to the "Android is starting... screen" for about 10 seconds, reboot, and return to the animated CM logo to repeat the loop forever.
Next I will make the suggested changes in Recovery mode to wipe some data and re-flash.

huawei pra lx3 with LineageOS 14.1 sudden bootloop and no int sdcard

Hello,
First, sorry, my ROM is Resurrection Remix ROM 5.8.5,, but i don't know how to edit the title.....
yesterday my phone suddenly rebooted and got stock in bootloop.
I entered recovery and the first thing I tried was to wiped cache and dalvik, but I got this instead:
Code:
could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux is present
Failed to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount /data (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
So I tried to manually mount, and i selected "select storage" and all options says =Mb (Internal, MicroSD and usb otg)...
So i went to the file manager, entered into sdcard and its empty.
I read around, and i found that maybe next adb command might help to find the cause:
Code:
adb shell "dmesg | grep mmc0"
got me:
Code:
<6>[ 10.376129s][pid:1,cpu4,swapper/0]mmc0: SDHCI controller on hi_mci.0 [hi_mci.0] using ADMA
<6>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: MAN_BKOPS_EN bit is not set
<3>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd_emmc50: CMDQ supported: depth: 32
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd: eMMC FW version:84
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support STROBE_ENHANCED.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support CACHE_FLUSH_POLICY_FIFO.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support RPMB 8K Bytes read/write.
<3>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: EXT_CSD revision 0x08 pre_eol_info = 0x01 device_life_time_est_typ_a = 0x02 device_life_time_est_typ_b = 0x01.
<6>[ 10.479919s][pid:165,cpu7,kworker/u16:3]sdhci: =========== REGISTER DUMP (mmc0)===========
<6>[ 10.504150s][pid:165,cpu5,kworker/u16:3]mmc0: eMMC init card done, support bus_width=8 bit.
<6>[ 10.504180s][pid:165,cpu5,kworker/u16:3]mmc0: new HS400 MMC card at address 0001,manfid:0x13,date:2017/10
<6>[ 10.506164s][pid:165,cpu6,kworker/u16:3]mmcblk0: mmc0:0001 Q3J96V 14.7 GiB
<6>[ 10.506256s][pid:165,cpu7,kworker/u16:3]mmcblk0boot0: mmc0:0001 Q3J96V partition 1 4.00 MiB
<6>[ 10.506500s][pid:165,cpu7,kworker/u16:3]mmcblk0boot1: mmc0:0001 Q3J96V partition 2 4.00 MiB
<6>[ 10.506561s][pid:165,cpu7,kworker/u16:3]mmcblk0rpmb: mmc0:0001 Q3J96V partition 3 4.00 MiB
also:
Code:
adb shell "ls /dev/block"
and I got:
Code:
bootdevice
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
mmcblk0p39
mmcblk0p4
mmcblk0p40
mmcblk0p41
mmcblk0p42
mmcblk0p43
mmcblk0p44
mmcblk0p45
mmcblk0p46
mmcblk0p47
mmcblk0p48
mmcblk0p49
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
platform
ram0
ram1
ram2
ram3
zram0
And this is what i could grab from the logcat on the bootloop.
logcat.txt
But I don't know hot to read the outputs, or if they are helpful.....

kurokirasama said:
Hello,
First, sorry, my ROM is Resurrection Remix ROM 5.8.5,, but i don't know how to edit the title.....
yesterday my phone suddenly rebooted and got stock in bootloop.
I entered recovery and the first thing I tried was to wiped cache and dalvik, but I got this instead:
Code:
could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux is present
Failed to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount /data (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
So I tried to manually mount, and i selected "select storage" and all options says =Mb (Internal, MicroSD and usb otg)...
So i went to the file manager, entered into sdcard and its empty.
I read around, and i found that maybe next adb command might help to find the cause:
Code:
adb shell "dmesg | grep mmc0"
got me:
Code:
<6>[ 10.376129s][pid:1,cpu4,swapper/0]mmc0: SDHCI controller on hi_mci.0 [hi_mci.0] using ADMA
<6>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: MAN_BKOPS_EN bit is not set
<3>[ 10.462524s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd_emmc50: CMDQ supported: depth: 32
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: mmc_decode_ext_csd: eMMC FW version:84
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support STROBE_ENHANCED.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support CACHE_FLUSH_POLICY_FIFO.
<6>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: support RPMB 8K Bytes read/write.
<3>[ 10.462554s][pid:165,cpu7,kworker/u16:3]mmc0: EXT_CSD revision 0x08 pre_eol_info = 0x01 device_life_time_est_typ_a = 0x02 device_life_time_est_typ_b = 0x01.
<6>[ 10.479919s][pid:165,cpu7,kworker/u16:3]sdhci: =========== REGISTER DUMP (mmc0)===========
<6>[ 10.504150s][pid:165,cpu5,kworker/u16:3]mmc0: eMMC init card done, support bus_width=8 bit.
<6>[ 10.504180s][pid:165,cpu5,kworker/u16:3]mmc0: new HS400 MMC card at address 0001,manfid:0x13,date:2017/10
<6>[ 10.506164s][pid:165,cpu6,kworker/u16:3]mmcblk0: mmc0:0001 Q3J96V 14.7 GiB
<6>[ 10.506256s][pid:165,cpu7,kworker/u16:3]mmcblk0boot0: mmc0:0001 Q3J96V partition 1 4.00 MiB
<6>[ 10.506500s][pid:165,cpu7,kworker/u16:3]mmcblk0boot1: mmc0:0001 Q3J96V partition 2 4.00 MiB
<6>[ 10.506561s][pid:165,cpu7,kworker/u16:3]mmcblk0rpmb: mmc0:0001 Q3J96V partition 3 4.00 MiB
also:
Code:
adb shell "ls /dev/block"
and I got:
Code:
bootdevice
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
mmcblk0p39
mmcblk0p4
mmcblk0p40
mmcblk0p41
mmcblk0p42
mmcblk0p43
mmcblk0p44
mmcblk0p45
mmcblk0p46
mmcblk0p47
mmcblk0p48
mmcblk0p49
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
platform
ram0
ram1
ram2
ram3
zram0
And this is what i could grab from the logcat on the bootloop.
logcat.txt
But I don't know hot to read the outputs, or if they are helpful.....
Click to expand...
Click to collapse
i fixed it using:
https://forum.xda-developers.com/transformer-tf701/help/dead-mmc-ideas-t2830332