Related
Hi guys,
I have a Linux partition on my sdcard and I want to have it mount at boot. I checked out this page( a page that I am not permitted to link to that might or might not contain this text "wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images") on how to do it and I have put together a boot.img file I want to flash. The instructions call for this maneuver:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
but the Note 8 doesn't have a MTD device:
[email protected]:/storage/sdcard0 # ls -l /dev/mtd*
/dev/mtd*: No such file or directory
what do I do?
mounting at boot time
Hi guys,
It has been about a week since I posted this question here. The reason I am trying to edit the boot.img file is to add a persistent mount point to a Linux partition on my sdcard. After fussing with several third party kernels and not succeeding in creating my own working ramdisk, I tried adding init.d support and putting the mount command in a startup script. It looks like the sdcard is not mounted by the time the init process is finished. I tried editing the vold.fstab file. I tried adding this line to the end:
dev_mount debian /storage/extSdCard/debian 50 /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
No dice.
what is the format of this file? Where can I find a man page or a doc?
These are my partitions:
1|[email protected]:/sdcard # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 2621440 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10518528 mmcblk0p12
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 27343750 mmcblk1p1
179 50 2929687 mmcblk1p2
[email protected]:/sdcard #
these have changed since I updated to 4.2.2 about a week ago. Is there some way to have the config persist through device upgrades?
Hi,
recently i updated via CWM my unblocked, rooted xperia m (C1905). Phone has FXP317, earlier i updated radio installing stock 4.3 and it going well, besides fatal GPS, as usual
After upgrade form FXP317 to FXP319 and reboot phone, it running veeeryy slow and suddenly hangs up. After restart to CWM (it lasts couple minutes), i try to install it again (install from zip) and it failed - it shows problem with mounting /DATA.
Now i attempt to format /DATA but it failed - CWM says that partition can't be mounted.
Another try - flash stock rom (Flasher form Androxyde) gives
Code:
19/048/2014 07:48:57 - INFO - Device connected in flash mode
19/049/2014 07:49:06 - INFO - Selected Bundle for Xperia M C1905. FW release : Google Android 4.3 (Jelly Bean). Customization : 15.4.A.0.23
19/049/2014 07:49:06 - INFO - Preparing files for flashing
19/049/2014 07:49:53 - INFO - Please connect your device into flashmode.
19/049/2014 07:49:54 - INFO - Opening device for R/W
19/049/2014 07:49:54 - INFO - Reading device information
19/049/2014 07:49:54 - INFO - Phone ready for flashmode operations.
19/049/2014 07:49:54 - INFO - Current device : Unknown: Mar 7 2014/10:51:59 - YT910M7GB9 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59
19/049/2014 07:49:54 - INFO - Start Flashing
19/049/2014 07:49:54 - INFO - Processing loader.sin
19/049/2014 07:49:54 - INFO - Checking header
19/049/2014 07:49:54 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of loader.sin finished.
19/049/2014 07:49:55 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
19/049/2014 07:49:55 - INFO - Processing partition-image.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of partition-image.sin finished.
19/049/2014 07:49:55 - INFO - Parsing boot delivery
19/049/2014 07:49:55 - INFO - Phone boot version : S1_Boot_MSM_8227_5. Boot delivery version : S1_Boot_MSM_8227_5
19/049/2014 07:49:55 - INFO - Boot delivery up to date. Nothing to do
19/049/2014 07:49:55 - INFO - Processing kernel.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - ERROR - Processing of kernel.sin finished with errors.
19/049/2014 07:49:55 - INFO - Ending flash session
19/049/2014 07:49:55 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C ";
Soft from SONY - SUS, PC Companion, EMMA did't recognize my phone and gives up.
Meanwhile i flash kernel and i made fatal mistake (i thought so) - i tried to flash wrong kernel (it has 83 bytes), but after choosing the right file I could install the appropriate kernel.
Now i have CWM 6.0.4.8, and i can connect phone in flash mode, also in fastboot but i can't flash any rom because i can't mount /data
Command adb devices -l gives
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
How to mount /data or how to do the re-partition? What should I do to flash the stock rom?
Have you flashed the stock ROM again? Does it still show the same error?
elmkzgirxp said:
Have you flashed the stock ROM again? Does it still show the same error?
Click to expand...
Click to collapse
Yes, i did and same again. I have stock ROM 4.1.2, stock ROM 4.3. One thing - phone starts and - after maybe 30 min or so - stops on "Encryption unsuccessful bla bla bla". I try even recovery backup form http://forum.xda-developers.com/showthread.php?p=51574842 but it failed - folder /system cannot be restored.
I'm thinking about partitioning internal memory, but i don't know how. I have an access via flashmode and i'm looking for solution about using adb
Encryption? How'd that get there?
elmkzgirxp said:
Encryption? How'd that get there?
Click to expand...
Click to collapse
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
TomekParuszewski said:
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
Click to expand...
Click to collapse
Why not refer here... This might solve your problem.
elmkzgirxp said:
Why not refer here... This might solve your problem.
Click to expand...
Click to collapse
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Exact same problem
With fxp 18
TomekParuszewski said:
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Click to expand...
Click to collapse
Hmm, according to the definition of soft brick, and therefore that I can enter fastboot mode and flashmode and CWM, the phone is not soft bricked, but there is a problem with partitions or privileges SU, because I can not reflash rom. The system is still not able to mount the directory / data.
I will try connect to phone by the adb command and see, err, i don't know what - i must check available commands. Right now i'm waiting for CWM
After get into adb shell i get:
Code:
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
C:\SDK\sdk\platform-tools>adb remount
remount failed: Success
C:\SDK\sdk\platform-tools>adb devices -l
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6ndf -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 430.6M 128.0K 430.4M 0% /dev
tmpfs 430.6M 8.0K 430.6M 0% /tmp
tmpfs 430.6M 0 430.6M 0% /storage
tmpfs 430.6M 0 430.6M 0% /mnt/secure
tmpfs 430.6M 0 430.6M 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
246.2M 4.6M 241.7M 2% /cache
~ # ←[6nfdisk
fdisk
BusyBox v1.22.1 static (2014-04-06 21:24 +0200) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6n^C
C:\SDK\sdk\platform-tools>
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls
ls
boot logo.rle
boot.txt mnt
cache proc
charger property_contexts
data recovery
datadata res
default.prop root
dev sbin
emmc sd-ext
etc sdcard
external_sd seapp_contexts
file_contexts sepolicy
fstab.qcom storage
init sys
init.qcom.syspart_fixup.sh system
init.rc tmp
init.recovery.qcom.rc ueventd.qcom.rc
internal_sd ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6ncd data
cd data
/data # ←[6nls
ls
media
/data # ←[6n^C
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
I don't have any information about partitions (filesystem tmpfs)!
TomekParuszewski said:
I don't have any information about partitions (filesystem tmpfs)!
Click to expand...
Click to collapse
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Bonoboo said:
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Click to expand...
Click to collapse
Unfortunately, I can not mount / data or / system. After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears. is below:
(i'm wainting rught now - 14:29)
I have version 6.0.4.8 CWM and I see no formatting options. I tried to upload the CWM 6.0.4.7 from this post http://forum.xda-developers.com/showthread.php?t=2494793 but I could not do that. I still have my version. My bad, of course i have format command.
Does this mean that my phone died? Do I still have any chance to fix it?
TomekParuszewski said:
After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears.
Click to expand...
Click to collapse
Command from ADB? Try from recovery menu.
And output of command will be helpful.
TomekParuszewski said:
Does this mean that my phone died?
Click to expand...
Click to collapse
Don't give up for now.
UPD: I googled ERR_DYNAMIC=0x8020001C and found 7 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6, 7
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Bonoboo said:
Command from ADB? Try from recovery menu.
And output of command will be helpful.
Don't give up for now.
Click to expand...
Click to collapse
thank you for your words of encouragement - I'm gonna fight to the end
BTW - in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Bonoboo said:
UPD: I googled ERR_DYNAMIC=0x8020001C and found 6 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Click to expand...
Click to collapse
yes, most of them i've seen, thx
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
2. Try mounts and storage > format all
3. Try mount via menu in recovery
Bonoboo said:
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
3. You sure that in mounts and storage no format options?
4. Try mount via menu in recovery?
2. How about post error while mounting?
Click to expand...
Click to collapse
Answers:
If i'm wait long enough, phone boot to screen "Encryption unsuccessful", so i don't know - I do not encrypt the phone as I remember
Sorry, of course there is format command in recovery, my bad
I will try again and write exact message from the screen
Sorry for messing numbers, I edited post.
TomekParuszewski said:
in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Click to expand...
Click to collapse
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
FOTAKernel -> /dev/block/mmcblk0p23
LTALabel -> /dev/block/mmcblk0p16
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p6
alt_aboot -> /dev/block/mmcblk0p12
alt_rpm -> /dev/block/mmcblk0p15
alt_s1sbl2 -> /dev/block/mmcblk0p10
alt_sbl1 -> /dev/block/mmcblk0p8
alt_sbl2 -> /dev/block/mmcblk0p9
alt_sbl3 -> /dev/block/mmcblk0p11
alt_tz -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p17
cache -> /dev/block/mmcblk0p26
fsg -> /dev/block/mmcblk0p21
modem -> /dev/block/mmcblk0p18
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
persist -> /dev/block/mmcblk0p24
ramdump -> /dev/block/mmcblk0p22
rpm -> /dev/block/mmcblk0p14
s1sbl2 -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p5
system -> /dev/block/mmcblk0p25
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p27
Bonoboo said:
Sorry for messing numbers, I edited post.
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
Click to expand...
Click to collapse
ok, here the log from CWM - i don't know when each event occurred
Code:
persist.audio.low.latency.rec=false
persist.debug.wfd.enable=1
persist.radio.apm_sim_not_pwdn=1
persist.timed.enable=true
persist.fuse_sdcard=true
keyguard.no_require_sim=true
telephonu.lteOnCdmaDevice=0
DEVICE_PROVISIONED=1
I: Checking for extendedcommand
I:Skipping for extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
I:using /data/media for /sdcard/0/clockworkmod/.no_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:using /data/media for /sdcard/0/clockworkmod/.many_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
And here is the result of your command
Code:
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
YT910M7GB9 recovery
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 1955840 mmcblk1
179 33 1954816 mmcblk1p1
~ # ←[6nls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- 1 root root 179, 0 May 21 11:43 /dev/block/mmcblk0
brw------- 1 root root 179, 1 May 21 11:43 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 May 21 11:43 /dev/block/mmcblk0p10
brw------- 1 root root 179, 11 May 21 11:43 /dev/block/mmcblk0p11
brw------- 1 root root 179, 12 May 21 11:43 /dev/block/mmcblk0p12
brw------- 1 root root 179, 13 May 21 11:43 /dev/block/mmcblk0p13
brw------- 1 root root 179, 14 May 21 11:43 /dev/block/mmcblk0p14
brw------- 1 root root 179, 15 May 21 11:43 /dev/block/mmcblk0p15
brw------- 1 root root 179, 16 May 21 11:43 /dev/block/mmcblk0p16
brw------- 1 root root 179, 17 May 21 11:43 /dev/block/mmcblk0p17
brw------- 1 root root 179, 18 May 21 11:43 /dev/block/mmcblk0p18
brw------- 1 root root 179, 19 May 21 11:43 /dev/block/mmcblk0p19
brw------- 1 root root 179, 2 May 21 11:43 /dev/block/mmcblk0p2
brw------- 1 root root 179, 20 May 21 11:43 /dev/block/mmcblk0p20
brw------- 1 root root 179, 21 May 21 11:43 /dev/block/mmcblk0p21
brw------- 1 root root 179, 22 May 21 11:43 /dev/block/mmcblk0p22
brw------- 1 root root 179, 23 May 21 11:43 /dev/block/mmcblk0p23
brw------- 1 root root 179, 24 May 21 11:43 /dev/block/mmcblk0p24
brw------- 1 root root 179, 25 May 21 11:43 /dev/block/mmcblk0p25
brw------- 1 root root 179, 26 May 21 11:43 /dev/block/mmcblk0p26
brw------- 1 root root 179, 27 May 21 11:43 /dev/block/mmcblk0p27
brw------- 1 root root 179, 3 May 21 11:43 /dev/block/mmcblk0p3
brw------- 1 root root 179, 4 May 21 11:43 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 May 21 11:43 /dev/block/mmcblk0p5
brw------- 1 root root 179, 6 May 21 11:43 /dev/block/mmcblk0p6
brw------- 1 root root 179, 7 May 21 11:43 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 May 21 11:43 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 May 21 11:43 /dev/block/mmcblk0p9
brw------- 1 root root 179, 32 May 21 11:43 /dev/block/mmcblk1
brw------- 1 root root 179, 33 May 21 11:43 /dev/block/mmcblk1p1
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,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)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,re
latime,data=ordered)
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
~ # ←[6n
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>
If both partitions are incorrect, should I try to flash?
Hi everyone,
I was trying to flash an nightly update from cyanogen and was getting the error : CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system and so, troubleshooting the problem, I tried to extend the system partitions through the procedure I found in a thread that contained the code down bellow and I believe that was after that that I lost my recoverymode. After this I tried to flash an earlier ROM to see if I could get the phone back and that was the last time I was able to enter in the recoverymode. Now I just have a black screen and also when I try to start my phone it took about 2 min on a black screen and then the OS starts. Besides that, all network connectivity was lost (wifi, call signal, 4g/3g) and my user space (/data partition) too (althoug it seems to be mounted). It appears it that was all disabled. Without a recovery mode and internet I am completely stuck. I tried to install a cwm and a twrp through adb after install flash gordon and flashify apk but it did not worked it cannot recognize a file out my /data . And the idea I had to restore from rommanager apk failed in the moment it tried to connect on internet to download content.
Please help!! Follow details:
LG_E975
I did a full wipe partition / cache/ dalvik
cyanogemMod version: 11-20141115-SNAPSHOT-M12-E975
android : 4.4.4.
kernel version: 3.4.0-CM+
Code I found and ran when trying to solve CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
fi
Output from df command:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 905.8M 128.0K 905.6M 4096
/sys/fs/cgroup 905.8M 12.0K 905.8M 4096
/mnt/asec 905.8M 0.0K 905.8M 4096
/mnt/obb 905.8M 0.0K 905.8M 4096
/mnt/fuse 905.8M 0.0K 905.8M 4096
/system 1.5G 401.3M 1.1G 4096
/cache 788.4M 14.4M 774.0M 4096
/data 25.0G 271.0M 24.8G 4096
[email protected]:/ $
Output from /proc/partitions
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Output from /dev/block directory:
Code:
[email protected]:/dev/block $ ls -l
ls -l
brw------- root root 7, 0 1970-01-02 12:07 loop0
brw------- root root 7, 1 1970-01-02 12:07 loop1
brw------- root root 7, 2 1970-01-02 12:07 loop2
brw------- root root 7, 3 1970-01-02 12:07 loop3
brw------- root root 7, 4 1970-01-02 12:07 loop4
brw------- root root 7, 5 1970-01-02 12:07 loop5
brw------- root root 7, 6 1970-01-02 12:07 loop6
brw------- root root 7, 7 1970-01-02 12:07 loop7
brw------- root root 179, 0 1970-01-02 12:07 mmcblk0
brw------- root root 179, 1 1970-01-02 12:07 mmcblk0p1
brw------- root root 179, 10 1970-01-02 12:07 mmcblk0p10
brw------- root root 179, 11 1970-01-02 12:07 mmcblk0p11
brw-rw---- system system 179, 12 1970-01-02 12:07 mmcblk0p12
brw-rw---- system system 179, 13 1970-01-02 12:07 mmcblk0p13
brw-rw---- system system 179, 14 1970-01-02 12:07 mmcblk0p14
brw------- root root 179, 15 1970-01-02 12:07 mmcblk0p15
brw------- root root 179, 16 1970-01-02 12:07 mmcblk0p16
brw------- root root 179, 17 1970-01-02 12:07 mmcblk0p17
brw-rw---- root system 179, 18 1970-01-02 12:07 mmcblk0p18
brw------- root root 179, 19 1970-01-02 12:07 mmcblk0p19
brw------- root root 179, 2 1970-01-02 12:07 mmcblk0p2
brw------- root root 179, 20 1970-01-02 12:07 mmcblk0p20
brw------- root root 179, 21 1970-01-02 12:07 mmcblk0p21
brw------- root root 179, 22 1970-01-02 12:07 mmcblk0p22
brw------- root root 179, 23 1970-01-02 12:07 mmcblk0p23
brw------- root root 179, 24 1970-01-02 12:07 mmcblk0p24
brw------- root root 179, 27 1970-01-02 12:07 mmcblk0p27
brw------- root root 179, 28 1970-01-02 12:07 mmcblk0p28
brw------- root root 179, 29 1970-01-02 12:07 mmcblk0p29
brw------- root root 179, 3 1970-01-02 12:07 mmcblk0p3
brw------- root root 179, 30 1970-01-02 12:07 mmcblk0p30
brw------- root root 179, 31 1970-01-02 12:07 mmcblk0p31
brw------- root root 259, 0 1970-01-02 12:07 mmcblk0p32
brw------- root root 259, 1 1970-01-02 12:07 mmcblk0p33
brw------- root root 259, 2 1970-01-02 12:07 mmcblk0p34
brw------- root root 259, 3 1970-01-02 12:07 mmcblk0p35
brw------- root root 179, 4 1970-01-02 12:07 mmcblk0p4
brw------- root root 179, 5 1970-01-02 12:07 mmcblk0p5
brw------- root root 179, 6 1970-01-02 12:07 mmcblk0p6
brw------- root root 179, 7 1970-01-02 12:07 mmcblk0p7
brw-rw---- system system 179, 8 1970-01-02 12:07 mmcblk0p8
brw-rw---- system system 179, 9 1970-01-02 12:07 mmcblk0p9
drwxr-xr-x root root 1970-01-02 12:07 platform
brw------- root root 1, 0 1970-01-02 12:07 ram0
brw------- root root 1, 1 1970-01-02 12:07 ram1
brw------- root root 1, 10 1970-01-02 12:07 ram10
brw------- root root 1, 11 1970-01-02 12:07 ram11
brw------- root root 1, 12 1970-01-02 12:07 ram12
brw------- root root 1, 13 1970-01-02 12:07 ram13
brw------- root root 1, 14 1970-01-02 12:07 ram14
brw------- root root 1, 15 1970-01-02 12:07 ram15
brw------- root root 1, 2 1970-01-02 12:07 ram2
brw------- root root 1, 3 1970-01-02 12:07 ram3
brw------- root root 1, 4 1970-01-02 12:07 ram4
brw------- root root 1, 5 1970-01-02 12:07 ram5
brw------- root root 1, 6 1970-01-02 12:07 ram6
brw------- root root 1, 7 1970-01-02 12:07 ram7
brw------- root root 1, 8 1970-01-02 12:07 ram8
brw------- root root 1, 9 1970-01-02 12:07 ram9
drwx------ root root 1970-01-02 12:09 vold
[email protected]:/dev/block $
Output from cat /proc/mounts
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
Hello,
Have you given up on this, have you fixed it, or are you still trying?
You may be able to flash a new recovery from fastboot (hold volume up while powering on).
I have not had any luck with cm-12.1 either. I did successfully resize my system partition, but cm-12.1 still will not flash. cm-12, however works fine.
TH
This is how I got my data from my GT-I9192 with TWRP and CM13. I don't know if it works for the other GT-I91XX models or with other firmware, but if you are in a similar situation like me it is worth a try.
Background:
I installed Cyanogenmod 13 and TWRP successfully about two month ago.
About a week ago my phone suddenly was black and did not want to boot at all. I convinced it to restart after pulling battery/recharge cable some times and putting them back, sometimes whilest holding power button pressed at the same time, until it gave a life sign again.
Current situation:
My phone stucks at samsung logo splash screen and reboots.
When trying to boot into recovery (TWRP; VOL.UP+HOME(+POWER)) the TeamWinRecovery logo screen is shown but then reboots.
Download mode (VOL.DOWN+HOME) works, Odin recognizes phone, but flashing TWRP successfully again does not fix anything.
Fastboot and adb do not recognize phone while it is in boot loop/recovery start loop/download mode!
But the interesting part is:
I am able to get via adb shell onto the phone while it is offline! Pull battery, put it back again, connect the phone via USB to PC and leave it off. Battery charging screen shows up and about a minute later adb shell is possible. It is in a strange state then, neither sdcard nor any else partition besides system is mounted, but mounting sdcard and data partition manually is possible.
Required:
Installed Samsung drivers, downloaded ADB tools, CM13(?), root enabled for adb.
make sure phone is off (pull battery/cable, put it back again)
connect phone via usb to pc
at pc cmd type
Code:
adb wait-for-device
when prompt is back, type
Code:
adb shell
use the commands below to get to your data
list internal partitions by name:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
output:
Code:
total 0
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 param -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 system -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 userdata -> /dev/block/mmcblk0p24 [COLOR="red"]<<< there is your userdata[/COLOR]
list all partitions with size:
Code:
cat /proc/partitions
output:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 12288 mmcblk0p20
179 21 1536000 mmcblk0p21
179 22 204800 mmcblk0p22
179 23 36864 mmcblk0p23
179 24 5685231 mmcblk0p24 [COLOR="red"]<<< userdata partition has about 5.7 GB size[/COLOR]
179 32 30703616 mmcblk1
179 33 30703582 mmcblk1p1 [COLOR="red"]<<< this is your external sdcard partition[/COLOR]
get partition format
Code:
blkid
output:
Code:
/dev/block/mmcblk0p1: SEC_TYPE="msdos" UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p19: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p20: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p22: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p23: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" [COLOR="Red"]<<< userdata has ext4 format[/COLOR]
/dev/block/mmcblk1p1: UUID="02A3-21FE" LABEL="Volume" TYPE="exfat" [COLOR="Red"]<<< external sdcard has exfat format[/COLOR]
get currently mounted partitions
Code:
mount
output:
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,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)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)
none on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /dev/memcg type cgroup (rw,relatime,memory)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /sys/fs/cgroup/bfqio type cgroup (rw,relatime,bfqio)
/dev/block/mmcblk0p21 on /system type ext4 (ro,seclabel,relatime,data=ordered)
neither data nor external sdcard is mounted
mount your external sdcard
Code:
mkdir /mnt/sdext
mount /dev/block/mmcblk1p1 /mnt/sdext
extract your data partition as image to your sdcard
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata.img
important info: as your data partition is larger than 4GB, you can only put the whole image to your sdcard if it is in exFat or NTFS format (fat32 does not allow files larger than 4GB). You could copy the image splitted like follows:
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_1.img count=4000000
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_2.img skip=4000000
copy your images later to pc and put it together in windows cmd with
Code:
copy /B userdata_1.img + userdata_2.img userdata.img
Not tested though.
look if there is enough space on your external sdcard
Code:
df -H
H=human readable sizes with 1000 based system; use no option to list number of 1k blocks; use -P do list 512byte blocks, usefull as dd uses same block size per default
output:
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 708M 41k 708M 1% /dev
none 708M 0 708M 0% /sys/fs/cgroup
tmpfs 708M 0 708M 0% /mnt
/dev/block/mmcblk0p21 1.5G 986M 562M 64% /system
/dev/block/mmcblk0p24 [COLOR="red"]5.7G[/COLOR] 5.3G 423M 93% /mnt/userdata
/dev/block/mmcblk1p1 31G 14G [COLOR="red"]18G[/COLOR] 44% /mnt/sdext
or mount your internal data partition as well and copy only the data you need
Code:
mkdir /mnt/userdata
mount /dev/block/mmcblk0p24 /mnt/userdata
use cd and ls -al commands to find your desired data;
in a secondary cmd at your pc copy directly to your pc via e.g. (contacts, sms, photos, TWRP backup, ...)
Code:
adb pull /mnt/userdata/data/com.android.providers.contacts/databases/contacts2.db
adb pull /mnt/userdata/data/com.android.providers.telephony/databases/mmssms.db
adb pull /mnt/userdata/media/0/DCIM
adb pull /mnt/userdata/media/0/TWRP
However, copying whole directories often failed and resulted in reboot of phone...
So, what to do with this image?
Mounting it in windows as new drive worked very well with OSFMount. As windows can not read ext4 partitions, you might want to install a ext4 driver like ext2fsd. And there is your data. Interesting folders are /media/0 where your internal sdcard data (like photos) resides and /data where all your apps store its data. You can find your contacts here /data/com.android.providers.contacts/databases/contacts2.db and your SMS here /data/com.android.providers.telephony/databases/mmssms.db. You can copy this databases to your new phone or inspect them via sqlite3.exe from your Android Development Tools. Here is a macro that could convert your contacts to vcard.
Credits:
Many of these information can be found at various xda threads, i do not remember all threads where I got which information from. Everything here was written from mind. Google and Wikipedia is also helpfull when it comes to command details. However this thread contains also most of the commands i showed above. This thread might give some inspirations about reading ext4 partition images under windows. If you feel that another thread has to be mentioned here, please write a message and I'll add it.
Thank you for this clarify guide. I try it even if my phone isn't bricked.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
Hi.
I get a Nexus 7 2013. Problem is, it will not boot any rom.
Fastboot, TWRP, flash rom or factory image works fine, but i will bootloop every time with any rom.
Tried with CM14.1, CM13, AOSP, latest factory image and first factory image.
Someone has an idea? Can i log the boot somehow?
baggerbodo said:
Hi.
I get a Nexus 7 2013. Problem is, it will not boot any rom.
Fastboot, TWRP, flash rom or factory image works fine, but i will bootloop every time with any rom.
Tried wich CM14.1, CM13, AOSP, latest factory image and first factory image.
Someone has an idea? Can i log the boot somehow?
Click to expand...
Click to collapse
Hello, I think I know the problem but let's see some logs first. Start your OS and on the next bootloop turn it off and as quickly as possible turn it back on to TWRP recovery. The off/on must happen within max 2 seconds in order to preserve last_kmsg in RAM intact. Then while in TWRP attach an OTG USB drive with my get-logs.zip on it, 'install' it and post 'logs.tgz' which was created on the flashdrive.
If you don't have an OTG drive/adapter, have a look inside the zip and use ADB to get the logs manually.
That´s crazy. Now i havo no bootloops more but stuck on boot logo.
Anyway, here is my log after 15 minutes boot. (please remove .zip)
The kernel cannot communicate properly with LTE modem and constantly, repeatedly logs this sequence:
Code:
mdm_modem_ioctl: Powering on mdm id 0
mdm_do_soft_power_on: id 0: soft resetting mdm modem
It is either a software/data or hardware issue.
Apart from the 'radio' partition which you have reflashed many times, the modem also needs:
Code:
modemst1 mmcblk0p2 3MB
modemst2 mmcblk0p3 3MB
fsg mmcblk0p8 3MB
These partitions are never flashed from OS and I/we always back them up before any ROM changes on mobile phones.
I don't have the LTE N7 and can't help you if the partitions are corrupt or erased.
As for possible hardware issue I note on the pictures antenna sockets, so the modem seems to be next to SIM card reader on the daughterboard PCB. If so, then the fix is very simple. The wide silver flex cable which connects both PCBs is notoriously unreliable and needs to be re-seated on both connectors. I'd bet on it :fingers-crossed:
So you think i need a complete system dump?
Here are my partitiones.
Code:
179 0 30539776 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 28180463 mmcblk0p30
Code:
drwxr-xr-x 2 root root 640 Jan 1 00:02 .
drwxr-xr-x 4 root root 700 Jan 1 00:02 ..
lrwxrwxrwx 1 root root 21 Jan 1 00:02 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 1 00:02 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 00:02 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 1 00:02 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 00:02 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 1 00:02 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 00:02 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 1 00:02 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 1 00:02 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 1 00:02 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 00:02 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 00:02 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 1 00:02 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 00:02 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 1 00:02 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 1 00:02 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 00:02 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 1 00:02 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 1 00:02 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 1 00:02 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 00:02 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 00:02 tzb -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 1 00:02 userdata -> /dev/block/mmcblk0p30
Now i get bootloops again, please have a look in my logs.
baggerbodo said:
So you think i need a complete system dump?
Now i get bootloops again, please have a look in my logs.
Click to expand...
Click to collapse
I think you need to check the cable first.
The new logs don't offer more insights but if you are successful in capturing logcat during bootloop it would be very interesting:
http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
http://forum.xda-developers.com/showpost.php?p=47172724