Develop Bugs

[Q] Backup/Restore using DD and ODIN

Any help will be appreciated :good:​
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So all we need the block device list for note 2
/dev/block/mmcblk0 Whole Internal Storage
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT (Kernel)
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO (Modem)
/dev/block/mmcblk0p11 4194kB TOMBSTONES
/dev/block/mmcblk0p12 1434MB CACHE
/dev/block/mmcblk0p13 2147MB SYSTEM
/dev/block/mmcblk0p14 587MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 11.4GB USERDATA (User Accessible Storage and /DATA folder)

[email protected] said:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So I need all the block device list for note 2
So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
Perhaps you should find out what the mount command does before you start using dd to read and write directly to the partitions. These sort of commands don't take prisoners

I said I'm not a linux expert, it doesn't mean I'm totally noob. I'm using Lubuntu on my netbook.
I'm well aware of risks, I'm using dd on PC time to time.
Mount only shows mounted partitions. I'm asking those partitions. I couldn't find a full partitions list anywhere
There are many partitions and I want to know what they are
Code:
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 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 90112 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1400832 mmcblk0p12
179 13 2097152 mmcblk0p13
179 14 573440 mmcblk0p14
179 15 8192 mmcblk0p15
259 0 11141120 mmcblk0p16
179 16 62367744 mmcblk1
179 17 62351360 mmcblk1p1
[email protected]:/ # ls -l /dev/block/mmcblk*
ls -l /dev/block/mmcblk*
brw------- root root 179, 0 2013-04-01 00:14 mmcblk0
brw------- root root 179, 1 2013-04-01 00:14 mmcblk0p1
brw-rw---- system radio 179, 10 2013-04-01 00:14 mmcblk0p10
brw-rw---- system radio 179, 11 2013-04-01 00:14 mmcblk0p11
brw------- root root 179, 12 2013-04-01 00:14 mmcblk0p12
brw------- root root 179, 13 2013-04-01 00:14 mmcblk0p13
brw------- root root 179, 14 2013-04-01 00:14 mmcblk0p14
brw------- root root 179, 15 2013-04-01 00:14 mmcblk0p15
brw------- root root 259, 0 2013-04-01 00:14 mmcblk0p16
brw------- root root 179, 2 2013-04-01 00:14 mmcblk0p2
brw------- root root 179, 3 2013-04-01 00:14 mmcblk0p3
brw-rw---- system radio 179, 4 2013-04-01 00:14 mmcblk0p4
brw-rw---- system radio 179, 5 2013-04-01 00:14 mmcblk0p5
brw-rw---- system radio 179, 6 2013-04-01 00:14 mmcblk0p6
brw-rw---- system root 179, 7 2013-04-01 00:14 mmcblk0p7
brw------- root root 179, 8 2013-04-01 00:14 mmcblk0p8
brw------- root root 179, 9 2013-04-01 00:14 mmcblk0p9
brw------- root root 179, 16 2013-04-01 00:14 mmcblk1
brw------- root root 179, 17 2013-04-01 00:14 mmcblk1p1
For some reason listing partitions by-label doesn't work either for android or block devices.
Code:
[email protected]:/ # ls -l /dev/block/by-label
ls -l /dev/block/by-label
/dev/block/by-label: No such file or directory

[email protected] said:
...So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)

cargobr151 said:
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
Click to expand...
Click to collapse
Thank you a lot, parted is not working on mine. Probably busybox related?
Edit: Nevermind I found the executable file of parted . Worked fine. Thanks again.

You must have installed a custom recovery. (with parted command included)
Like cwm or twrp v2.4.4.0. I use twrp v2.4.4.0.

@OP updated my thread with this thread info...You can visit here

@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?

dr.ketan said:
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
Click to expand...
Click to collapse
Roger that
here http://forum.xda-developers.com/showthread.php?t=1777579 @das7982 well explained the instructions for Galaxy SIII
According to his post, he's recommending to make an ODIN package from only system.img
To make system.img of note 2
Code:
dd if=/dev/block/mmcblk0p13 of=/storage/extSdCard/system.img bs=4096
Here we need a linux pc or Cygwin for Windows. If we going to use Cygwin, we need to install it along with tar, md5sum commands
Code:
tar -H ustar -c system.img > system.img.tar
Then we need to make Md5 checksum
Code:
md5sum -t system.img.tar >> system.img.tar
rename it
Code:
mv system.img.tar system.img.tar.md5
I haven't tried this yet but I'll try soon

I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium

dr.ketan said:
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You're correct, stock kernel and recovery shouldn't increase the flash counter.
To backup /data we can use
Code:
adb shell
stop
busybox tar -cZvf /storage/extSdCard/data.ext4.tar --exclude media --exclude dalvik-cache /data
reboot
To restore
Code:
adb shell
stop
busybox tar -xvf /storage/extSdCard/data.ext4.tar -C /
reboot

[Q] Fastboot can't find partition table

I do fastboot erase data, and get
erasing 'data'... FAILED (remote: Partition table doesn't exist)​
Background: N-7 works on several roms. Now running stock KOT49H ota, all of them fairly reliable but after 4.4 I get stuck in the splash screen on reboot/power on. I've had to wipe data etc to get it to reboot at all. Have not tried to go back to pure stock.
Plan was/is to wipe data partition and restore data from computer through fastboot (has worked before on other 4.3+ roms/devices), but fastboot is seeing something it does not like. With recovery I can see that
dev/block/mmcblk0p30 on /data type ext4 (rw,seclabel,relatime,data=ordered)​but of course that does not mean there -is- a data partition. I can't find any reference to partitioning an N7, etc. So - stuck. Any insight appreciated.

Is it possible that the new bootloader has changed the name of the partition to maybe userdata? But i doubt it. You can try
fastboot erase -w
This may work for you
Otherwise a wipe from recovery should give similar results - also in recovery you should be able to grab a log and check ftab to see partition table or you can access adb shell and check from there
ls -a -l /dev/block/platform/msm_sdcc.1/by-name
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Is it possible that the new bootloader has changed the name of the partition to maybe userdata? But i doubt it. You can try
fastboot erase -w
This may work for you
Otherwise a wipe from recovery should give similar results - also in recovery you should be able to grab a log and check ftab to see partition table or you can access adb shell and check from there
ls -a -l /dev/block/platform/msm_sdcc.1/by-name
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
Oooh - did not know about how to see the /dev stuff - nice.
~ # ls -a -l /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
drwxr-xr-x 2 root root 640 Dec 16 16:18 .
drwxr-xr-x 4 root root 700 Dec 16 16:18 ..
lrwxrwxrwx 1 root root 21 Dec 16 16:18 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Dec 16 16:18 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Dec 16 16:18 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Dec 16 16:18 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Dec 16 16:18 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Dec 16 16:18 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Dec 16 16:18 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Dec 16 16:18 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Dec 16 16:18 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Dec 16 16:18 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Dec 16 16:18 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Dec 16 16:18 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Dec 16 16:18 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Dec 16 16:18 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Dec 16 16:18 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Dec 16 16:18 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 16 16:18 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Dec 16 16:18 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Dec 16 16:18 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Dec 16 16:18 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Dec 16 16:18 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Dec 16 16:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Dec 16 16:18 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Dec 16 16:18 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 16 16:18 tzb -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Dec 16 16:18 userdata -> /dev/block/mmcblk0p30​Look like data is now userdata!
Using TWRP, data is mounted on mmcblk0p30 but earlier I flashed the latest CWM recovery and now using adb shell, it shows
rootfs on / type rootfs (rw)
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 /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,nodev,noatime,nodiratime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)​
Thought I semi-understood what was going on in the partition/mounting world. Clearly not.
Anyway, thanks! Maybe I can move forward with this now.

Was it ever named "data"? Since my first-gen N7, if memory serves, it was always "userdata" that I'd erase with fastboot.

Pandae said:
Was it ever named "data"? Since my first-gen N7, if memory serves, it was always "userdata" that I'd erase with fastboot.
Click to expand...
Click to collapse
Actually great to know that. All prev. phones etc I've used had "data". Thnx!

Lost recovery mode after resizing system partitions

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

[GUIDE][GT-I9192][stuck at splash] how to get your data back

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

Pushing a ROM.zip file always fails to complete to 100%

I am using a Linux machine and adb.
Nubia NX503a (25S)
Code:
[email protected]:~$ adb devices
List of devices attached
MSM8974 recovery
[email protected]:~$
Code:
~ # ls -la
drwxr-xr-x 22 root root 0 Jan 3 18:48 .
drwxr-xr-x 22 root root 0 Jan 3 18:48 ..
drwxr-xr-x 2 root root 0 Jan 3 18:46 boot
drwxr-xr-x 4 root root 4096 Jan 3 18:03 cache
drwxr-xr-x 5 root root 4096 Jan 3 20:15 data
drwxr-xr-x 2 root root 0 Jan 3 18:46 datadata
-rw-r--r-- 1 root root 5785 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 15160 Jan 3 18:46 dev
drwxr-xr-x 2 root root 0 Jan 3 18:46 emmc
drwxr-xr-x 2 root root 0 Jan 3 18:46 etc
drwxr-xr-x 2 root root 0 Jan 3 18:46 external_sd
-rwxr-x--- 1 root root 113592 Jan 1 00:00 init
-rwxr-x--- 1 root root 1417 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 3 18:46 internal_sd
drwxrwx--x 6 system system 4096 Jan 2 00:30 persist
dr-xr-xr-x 158 root root 0 Jan 1 00:00 proc
drwxr-xr-x 2 root root 0 Jan 3 18:46 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 30 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 3 18:46 sd-ext
drwxrwxrwx 2 root root 8192 Jan 1 00:00 sdcard
dr-xr-xr-x 15 root root 0 Jan 3 18:46 sys
drwxr-xr-x 16 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 3 18:46 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ #
It can be seen that the sdcard is 0% used:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 924.0M 48.0K 924.0M 0% /dev
/dev/block/platform/msm_sdcc.1/by-name/cache
492.6M 8.7M 483.9M 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/userdata
2.5G 424.5M 2.0G 17% /data
/dev/block/platform/msm_sdcc.1/by-name/grow
9.8G 8.0K 9.8G 0% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/system
1.2G 485.0M 726.5M 40% /system
/dev/block/platform/msm_sdcc.1/by-name/persist
4.9M 4.1M 812.0K 84% /persist
~ #
The sdcard:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 32 mmcblk0p4
179 5 512 mmcblk0p5
179 6 500 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 500 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1536 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 1258290 mmcblk0p14
179 15 2621440 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 512000 mmcblk0p17
179 18 153600 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 1 mmcblk0p21
179 22 8 mmcblk0p22
179 23 10276838 mmcblk0p23
179 32 4096 mmcblk0rpmb
~ #
Is 179 23 10276838 mmcblk0p23, but I forget how I linked the sdcard to mmcblk0p23
Using:
adb push -p /home/makem/Downloads/update2.zip /dev/block/mmcblk0p23/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /data/media/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /sdcard/
Each fail by stopping anywhere between 5% and 47%. I have wiped the cache, data and delvik cache prior to pushing.
When I check the sdcard again with df I find it is still at 0%, except for the last push which stopped at 10% and showed 1% used sdcard.
EDIT: After the last push the file update2.zip showed in the sdcard when I went to install it. However, it stopped with a 'bad' error. Obviously an incomplete upload but why????
Tearing my hair out here lol.