Related
Does anyone know where I can find the CWM Recovery for the viper?
Sent from my LG-P999 using XDA
Bump
Sent from my LG-P999 using XDA
You can install the recoveries for the vs840 or the ms840 (lucid and connect respectively) through ROM Manager since all the sprint reps say they have the same coding but so far I haven't been able to do much other than boot into CWM. I can't make backups as it won't mount /system and when I manually mount /system for it it seems to backup but then the files just disappear :/ By the way you wouldn't happen to know the partition # of the recovery partition would you? I have a vague table laid out but it may not be 100% accurate so that info would help, or just let me know how to get into the bootloader/fastboot if you know how.
P.S. here's the table I've gotten so far with the file layouts (not 100% sure what files correspond to each partition)
Code:
/dev/block/mmcblk0p1 >IMAGE/MODEM*
/dev/block/mmcblk0p12 >Gaspra,LostFound,WCN1314_qcom_wlan_nv.bin,qcom
/dev/block/mmcblk0p14 >image/*.MBN
/dev/block/mmcblk0p22 >lost+found/,lpass/,mdm/,modem/
/dev/block/mmcblk0p23 >lost+found/
/dev/block/mmcblk0p27 >app/,bin/,build.prop,etc/,fonts/,framework/,lib/,media/,recovery/,sounds/,tts/,usbautorun.iso,usr/,xbin/ (/ ?)
/dev/block/mmcblk0p28 >lost+found/,recovery/
/dev/block/mmcblk0p29 >amit/,anr/,app/,app-private/,backup/,dalvik-cache/,data/,dontpanic/,fonta/,gesture/,img/,lgdrm/,local/,logger/,lost+found/,misc/,property/,qcks/,radio/,secure/,shared/,sutest/,system/,time/,tombstones/,wiper/,wmdrm/,wpstiles/ (/SYSTEM)
/dev/block/mmcblk0p30 >lost+found/
/dev/block/mmcblk0p31 >MPT_*,aat_result.txt,acc_calibration.dat,enable/,lost+found/,pid/,started/
Rom Development?
My wife just upgraded her EVO for this phone. I was able to find the rooting method with the superoneclick, and it worked slick. I was able to remove the sprint apps like NBA and NASCAR... but was looking for any custom rom. I had ICS running on her EVO, and since this comes with GB... I hate to go backwards. Is there anyone working on rom development for this phone yet?
some get me a dump of the stock recovey please
Also do
Code:
adb shell
Code:
cat proc/mounts
and
Code:
cat proc/partitions
Sounds like the viper has a different mount for system than its cousins.
In terminal emulator:
df to get list of partitions, if possible, and mount each on a temporary directory with loop options.. Hopefully the stock kernel supports fs wraps..
Just barely got this phone for my fiance, and I'm waiting for someone to nail this sucker to the wall.. Hopefully someone can come up with a working recovery..
Hope the above helps, because if you can df on su, especially with the -a option, if I remember right, it tells you the file systems used on each part.
Maybe once stuff settles down (because hectic is an understatement at this particular point irl, lol), I can jump in and be of more help, but right now.. It's just not the best time as I'm trying to keep a roof over our heads here..
Good luck all!
-----
Sent from my phone
using my finger... ;-)
-----
this needs testing and I still need the above mentions.
http://d-h.st/GFZ
# df -a
Filesystem Size Used Free Blksize
-a: No such file or directory
# df
Filesystem Size Used Free Blksize
/dev 400M 48K 399M 4096
/mnt/asec 400M 0K 400M 4096
/mnt/obb 400M 0K 400M 4096
# df
Filesystem Size Used Free Blksize
/dev 400M 48K 399M 4096 /mnt/asec 400M 0K 400M 4096
/mnt/obb 400M 0K 400M 4096
/mnt/extasec 400M 0K 400M 4096
/mnt/extobb 400M 0K 400M 4096 /system 1009M 348M 661M 4096
/tombstones 71M 4M 67M 4096 /firmware 1G 28M 1G 32768
/data 1G 579M 1G 4096 /persist 7M 4M 3M 4096
/cache 314M 5M 309M 4096 /LGE_RC 4M 24K 4M 4096
/mpt 15M 9M 6M 1024 /system/etc/firmware/misc_mdm 199M 22M 177M 4096 /mnt/sdcard 14G 4G 9G 32768
/mnt/secure/asec 14G 4G 9G 32768 /mnt/asec/com.droidemu.game.lite-1 12M 10M 1M 4096 /mnt/asec/com.diotasoft.spark-1 28M 26M 1M 4096
/mnt/asec/com.nelphy.android.heavenhell-1 32M 30M 1M 4096
/mnt/asec/com.mojang.minecraftpe.demo-1 8M 6M 1M 4096
#
Here are the proc/ results
Code:
# cat proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p27 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,noatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /LGE_RC ext4 rw,nosuid,nodev,relatime,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.droidemu.game.lite-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.mojang.minecraftpe.demo-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.nelphy.android.heavenhell-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.diotasoft.spark-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.nelphy.android.crazyshuttle-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
# cat proc/partitions
major minor #blocks name
7 0 12506 loop0
7 1 8348 loop1
7 2 33296 loop2
7 3 29138 loop3
7 4 28098 loop4
179 0 3780608 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1048576 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 1843200 mmcblk0p29
179 30 5120 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 5120 mmcblk0p32
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
254 0 12505 dm-0
254 1 8347 dm-1
254 2 33295 dm-2
254 3 29137 dm-3
254 4 28098 dcode
?
sooo did you guys manage to find a cwm recovery?
im a total noob and i managed to root this phone but now i cant find a recovery :/ im still in GB
note:this is a study log,i'am not sure if blow is all right:cyclops:
Code:
major minor #blocks dev format name mount note
179 1 2048 mmcblk0p1 ext2 CF /configs
179 2 393216 mmcblk0p2 ext4 A0 /system system.img flash here
179 3 393216 mmcblk0p3 ext4 A1 /system backup system?
179 4 524288 mmcblk0p4 ext4 CC /cache
179 5 2048 mmcblk0p5 ???? MC /misc can't mount
179 6 49152 mmcblk0p6 ???? UP /staging hidden.img flash here
179 7 1024 mmcblk0p7 ???? BF /blflags can't mount
179 8 393216 mmcblk0p8 ext4 DP /datapp manel mount
179 9 16384 mmcblk0p9 ext4 LG /log
179 10 4194304 mmcblk0p10 ext4 UA /data
179 11 9368576 mmcblk0p11 vfat SC /sdcard
here mmcblk0 is first mmc-block device,that is inner storage
mmcblk0p1 is first partition of mmcblk0
block size is 1 KB,so block count 2048 means size is 2MB
there are 2 system partition(p2,p3),p2 is main system partition,if something wrong with p2,system will use p3 for backup.
my tablet first boot will stop at sony logo(use p2),2nd boot will ok(use p3)
if i flash ics,it will flash to p2,and can't use in forst boot,but after wipe,it will back to 3.2.1 again,then next boot to ics....
??system rember what system used in blflag(p7)+0xC.
(in updater-script read_index("/blflags") and code in update-binary)
if the byte is 0,use p2,else use p3,my is 1
content of p7:all zero but 0x03C -- 0x1FB is 0xFF,and
Code:
0x0C:1
0x14:1
0x1fC:0xD2A7AA14
0x1000:BL_VERSION_INFO\0
0x1010:_BL\0 0x00000008
0x1020:_RM\0 0x0000001E
0x1030:_LX\0 0x07334EFF
0x1040:_E1\0 0x00000009
a wipe data will format partition:
data,cache,log,staging
when flash rom,system.img flash to p2 or p3,hidden.img flash to p6
condi's double flash roms flash both to p2 and p3
some cmd:
get partion list
Code:
cat /proc/partitions
p3,p6,p8 is only use in update-script,but you can mout it by cmd
Code:
mount -t ext4 /dev/block/mmcblk0p3 /dir-name
p5,p7,format is unknow,mount fail,but you can dump it's data by cmd
Code:
cat /dev/block/mmcblk0p3 /some-name.bin
or
Code:
dd if=/dev/block/mmcblk0p3 of=/some-name.bin
in theory,you can restore partition by dd cmd,but it's very dangers!
you can check what system you use by cmd mount
Code:
# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[COLOR="Red"]/dev/block/mmcblk0p3 /system ext4 rw,relatime,barrier=1,data=ordered 0 0[/COLOR]
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0
0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatim
e,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remoun
t-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-
ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=rem
ount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
View attachment partitions.7z
Have anyone treis to flip this blaflags partition flag which tells which partition to reboot from? It could allow more versatile flashing...
According to Chainfire's floating performance monitor application the Disk I/O is mmcblk0.
Sent from my Nexus 4 using xda app-developers app
Where is the kernel? In the system partition, because i can´t see a boot partition in your list...
Partitionator said:
Where is the kernel? In the system partition, because i can´t see a boot partition in your list...
Click to expand...
Click to collapse
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery
lopezk38 said:
mmcblk0p6
Thats also where recovery is, hidden.img is kernel + recovery
Click to expand...
Click to collapse
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..
;45311156 said:
no,no,no
in normal case mmcblk0p6 is empty
1,mount it,will get only "lost+found" dir
2,dump it by dd,it's almost 50M of zero
as it's name,mmcblk0p6 is only a staging,when update system,hidden.img(kernel + recovery) will flash to mmcblk0p6,
but after reboot,the data will be cut to some place else.maybe a hidden partition we don't know
ánd the file used in recovery is not in the list too..
Click to expand...
Click to collapse
Robin, we need you to join the Sony Tablet Bootloader Discussion on Google Hangouts, can you PM me with your email with the subject "STBD"?
Sent from my Nexus 4 using Tapatalk 4
Hi All!!
I have a Qmoible A5Classic and I want to develop its CWM Recovery. I want to fetch its recovery by
Code:
dd if=etc of=abc
but the problem is i cannot find which partition is my recovery partition.
Code:
cat proc/partitions
shows:
Code:
major minor #blocks name
7 0 1254 loop0
179 0 3815552 mmcblk0
179 1 1 mmcblk0p1
179 2 163840 mmcblk0p2
179 3 1064960 mmcblk0p3
179 4 2028784 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 524288 mmcblk0p6
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 1949696 mmcblk1
179 25 1948672 mmcblk1p1
and
Code:
cat proc/mounts
show these:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:4 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:25 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:25 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Can anyone please point out the right partition?
PS: It is rooted.
Regards
ssm14293 said:
Hi All!!
Can anyone please point out the right partition?
PS: It is rooted.
Regards
Click to expand...
Click to collapse
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
cmd says /recovery emmc recovery (null) 0
shimp208 said:
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
ssm14293 said:
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
Click to expand...
Click to collapse
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
shimp208 said:
[/HIDE]
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
Click to expand...
Click to collapse
Jahan panha tussi great ho taufa qabul karo!
Click to expand...
Click to collapse
Translation: Dude!!!! Ur great!! please accept my humble gift :victory:
I dont have a by-name folder but only by-num, which really doesnt help. So now I will try your second method, extracting a part of the main image!! I'll tell you the result!!!
Regards
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
ssm14293 said:
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
Click to expand...
Click to collapse
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Some Luck with it...
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Few Questions
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
ssm14293 said:
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Click to expand...
Click to collapse
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
ssm14293 said:
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
Click to expand...
Click to collapse
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Found a way!
shimp208 said:
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Click to expand...
Click to collapse
Hi again!!
I just got myself an 8GB memory card. I also searched more about nandroid backups for non-CWM phones. I got across onandroid, it creates img files of all partitions. It was created by someone from XDA Forums, can't remember the name. So at the moment it is generating MD5 Checksum.
After this I will create my OWN Rom and CWM for this phone :victory: , well after my finals .
Thanks for your help! :highfive:
For all Qmobile Rooted users, use onandroid to create backups, but at your own risk. I can confirm for QMobiel A5 Classic
where to copy symphony CWM recovery.img using dd command
I am Moniruzzaman from Dhaka, Bangladesh...
Please forgive me for my weak English.
I have created a CWM recovery img (Latest Touch Version) for my rooted Symphony W85. My device partitions is similar to the Qmoible A5Classic. Now I have failed to copy it to the recovery partition as i could not figure out which is my recovery partition.
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
I have flashed the recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery. Everything was fine except my gsm signal was gone.
Then I tried flashed stock recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery - everything works fine again.
I have come so far and now i can't fine the right partitions. I am very frustrated.
Can any one please help me how to flash my CWM recovery img (Latest Touch Version) to my device as it is combined partitions.
shimp208 said:
.
Click to expand...
Click to collapse
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
jazzespresso said:
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
Click to expand...
Click to collapse
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
shimp208 said:
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
Click to expand...
Click to collapse
thank you very much...what about boot.img?
jazzespresso said:
thank you very much...what about boot.img?
Click to expand...
Click to collapse
For boot you would run the command:
Code:
cat /dev/block/platform/intel/by-label/boot > /mnt/sdcard/boot.img
Hope this helps you!
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
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
Follow info:
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]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
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 $
dihhedessa said:
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
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
Follow info:
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]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
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 $
Click to expand...
Click to collapse
@shimp208 and @jazzespresso maybe you guys could please help me? I am desperate!
Hi there,
I've the same problem, recovery is in mmcblk0, someone can help me please ? I can't find any solutions.
AndroGeek
Partion info of a my 6735 rooted android device
How can I get "dumchar_info", or "Part_Name ,Size ,StartAddr,Type,Map,To" info with adb command of a rooted mt6735 device with 5.1 lollipop? Thanks a lot in anticipation.
I had to do a factory reset on my wife's Galaxy S4 SGH-I337. Now I'm trying to find some pictures that were lost in the format. I know how to mount things in linux but for the life of me I cannot figure out how to get to the /storage/emulated/0 part
here are some outputs that may help someone else figure this out
Code:
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,
gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,
gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 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/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/data/knox/sdcard /mnt/shell/knox-emulated sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1000,gid=1000,derive=none 0 0
/data/media /mnt/shell/emulated sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /mnt/media_rw/extSdCard vfat rw,dirsync,seclabel,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,
gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/media_rw/extSdCard /storage/extSdCard sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1023,gid=1023,derive=unified 0 0
/data/media /storage/emulated/0 sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,seclabel,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 903.6M 100.0K 903.5M 4.0K
/sys/fs/cgroup 903.6M 12.0K 903.6M 4.0K
/mnt/secure 903.6M 0.0K 903.6M 4.0K
/mnt/asec 903.6M 0.0K 903.6M 4.0K
/mnt/obb 903.6M 0.0K 903.6M 4.0K
/firmware 86.0M 11.5M 74.4M 16.0K
/firmware-mdm 86.0M 49.7M 36.3M 16.0K
/system 2.7G 1.6G 1.1G 4.0K
/data 9.7G 1.2G 8.6G 4.0K
/cache 2.0G 61.7M 1.9G 4.0K
/efs 13.4M 4.2M 9.2M 4.0K
/persdata/absolute 8.8M 4.1M 4.7M 4.0K
/mnt/shell/knox-emulated 9.7G 1.2G 8.6G 4.0K
/mnt/shell/emulated 9.7G 1.2G 8.5G 4.0K
/storage/emulated 903.6M 0.0K 903.6M 4.0K
/mnt/media_rw/extSdCard 14.9G 11.8G 3.1G 32.0K
/storage/extSdCard 14.9G 11.8G 3.1G 32.0K
/storage/emulated/0 9.7G 1.2G 8.5G 4.0K
/storage/emulated/0/Android/obb 9.7G 1.2G 8.5G 4.0K
/storage/emulated/legacy 9.7G 1.2G 8.5G 4.0K
/storage/emulated/legacy/Android/obb 9.7G 1.2G 8.5G 4.0K
[email protected]:/ # cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 15605760 mmcblk1
179 33 15604736 mmcblk1p1
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2014-04-05 08:43 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-05 08:43 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-05 08:43 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-04-05 08:43 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-04-05 08:43 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-04-05 08:43 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-04-05 08:43 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-05 08:43 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-04-05 08:43 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-04-05 08:43 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-04-05 08:43 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-05 08:43 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-05 08:43 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-05 08:43 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-04-05 08:43 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-05 08:43 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-05 08:43 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-05 08:43 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-04-05 08:43 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-04-05 08:43 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-04-05 08:43 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-04-05 08:43 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-05 08:43 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-05 08:43 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-05 08:43 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-05 08:43 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-04-05 08:43 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-05 08:43 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-05 08:43 userdata -> /dev/block/mmcblk0p29
Maybe I'm just tired but your very last line seems to point to the userdata partition, this should be what you want
And hopefully it wasn't a true format and just a simple erase so you can get some back
Also you can try some apps on the market, diskdigger comes to mind, but often the sooner the better as you don't want to overwrite anything
Best of luck
Hey.
I would like to port CWM to Goclever Quantum 500
I use the official documentation from cyanogenmod website
Compilation goes flawlessly.
Code:
Install: /home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery/root/sbin/recovery
----- Making recovery ramdisk ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat '/home/mazur/android/system/out/target/product/java_gfive_wg5002g/root/init.recovery.*.rc': No such file or directory
----- Making uncompressed recovery ramdisk ------
----- Making compressed recovery ramdisk ------
----- Making recovery image ------
+/home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery.img maxsize=34197504 blocksize=135168 total=8536064 reserve=405504
Made recovery image: /home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery.img
#### make completed successfully (32:32 (mm:ss)) ####
But after flashing (flash goes flawlessly too - I tried flashify and fastboo btw) and trying entering the recovery I see only a black screen and nothing more.
Before flashing CWM I have generated stock recovery using flashify. Reflasing stock recovery works perfectly.
I have edited recovery.fstab based on recovery stock
recovery.fstab
Code:
# mount point fstype device option
/dev/block/platform/sdhci.0/mmcblk1p1 /sdcard vfat defaults wait
/dev/block/platform/sdhci.1/by-name/sdcard /sdcard0 vfat defaults wait
/dev/block/platform/sdhci.1/by-name/system /system ext4 rw wait
/dev/block/platform/sdhci.1/by-name/userdata /data ext4 rw wait,length=-16384
/dev/block/platform/sdhci.1/by-name/cache /cache ext4 rw wait
/dev/block/platform/sdhci.1/by-name/misc /misc emmc rw wait
/dev/block/platform/sdhci.1/by-name/boot /boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/recovery /recovery emmc rw wait
/dev/block/platform/sdhci.1/by-name/u-boot /u-boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/dt-blob /dt-blob emmc rw wait
/dev/block/platform/sdhci.1/by-name/cp-boot /cp-boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/cp-image /cp-image emmc rw wait
/dev/block/platform/sdhci.1/by-name/dsp-dram /dsp-dram emmc rw wait
/dev/block/platform/sdhci.1/by-name/dsp-pram /dsp-pram emmc rw wait
/dev/block/platform/sdhci.1/by-name/sys-parm-ind /sys-parm-ind emmc rw wait
/dev/block/platform/sdhci.1/by-name/parm-spml-ind /parm-spml-ind emmc rw wait
/dev/block/platform/sdhci.1/by-name/ubootlogo /ubootlogo emmc rw wait
/dev/block/platform/sdhci.1/by-name/abi /abi emmc rw wait
/dev/block/platform/sdhci.1/by-name/abi-sec /abi-sec emmc rw wait
/dev/block/platform/sdhci.1/by-name/hwconf /hwconf emmc rw wait
/dev/block/platform/sdhci.1/by-name/loader /loader emmc rw wait
/dev/block/platform/sdhci.1/by-name/parm-spml-dep /parm-spml-dep emmc rw wait
/dev/block/platform/sdhci.1/by-name/sys-parm-dep /sys-parm-dep emmc rw wait
/dev/block/platform/sdhci.1/by-name/umts-cal /umts-cal emmc rw wait
BoardConfig.mk generated by mkvendor.sh
[..]
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE :=891289600
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1614807040
BOARD_FLASH_BLOCK_SIZE := 131072
[..]
some info from adb shell:
Code:
[email protected]_gfive_wg5002g:/ # df
Filesystem Size Used Free Blksize
/dev 479.0M 128.0K 478.8M 4096
/sys/fs/cgroup 479.0M 12.0K 479.0M 4096
/mnt/secure 479.0M 0.0K 479.0M 4096
/mnt/asec 479.0M 0.0K 479.0M 4096
/mnt/asec/com.koushikdutta.rommanager-1 5.0M 3.6M 1.4M 4096
/mnt/asec/zip.me-1 6.1M 4.2M 1.9M 4096
/mnt/asec/me.kuder.diskinfo-1 3.0M 1.1M 1.9M 4096
/mnt/asec/com.cgollner.flashify-2 17.2M 14.1M 3.0M 4096
/mnt/asec/org.xbmc.kore-1 4.0M 2.9M 1.1M 4096
/mnt/asec/com.cpuid.cpu_z-1 4.0M 2.4M 1.6M 4096
/mnt/obb 479.0M 0.0K 479.0M 4096
/mnt/media_rw/sdcard0 1022.0M 686.0M 336.0M 4096
/mnt/media_rw/sdcard1 12.7G 674.4M 12.0G 4096
/storage/emulated 479.0M 0.0K 479.0M 4096
/storage/sdcard0 1022.0M 686.0M 336.0M 4096
/storage/sdcard1 12.7G 674.4M 12.0G 4096
/system 823.3M 632.6M 190.7M 4096
/cache 143.6M 232.0K 143.4M 4096
/data 1.5G 1.3G 183.1M 4096
/storage/emulated/legacy 479.0M 0.0K 479.0M 4096
Code:
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/zip.me-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/me.kuder.diskinfo-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.cgollner.flashify-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/org.xbmc.kore-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.cpuid.cpu_z-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,size=0k,mode=700,uid=1023,gid=1023 0 0
/dev/block/vold/179:32 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:169 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=0k,mode=751,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/sdhci.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/sdhci.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,data=ordered 0 0
/dev/block/platform/sdhci.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
Code:
[email protected]_gfive_wg5002g:/ # ls -la /dev/block/platform/sdhci.1/by-name/
lrwxrwxrwx root root 2013-01-01 01:02 abi -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-01 01:02 abi-sec -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-01 01:02 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-01-01 01:02 boot-parm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-01 01:02 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2013-01-01 01:02 cp-boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-01 01:02 cp-image -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-01-01 01:02 cp-pod -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-01-01 01:02 custom-cert -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-01-01 01:02 devinfo -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-01-01 01:02 dsp-dram -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-01-01 01:02 dsp-pram -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-01-01 01:02 dt-blob -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-01-01 01:02 hwconf -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-01 01:02 kpanic -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2013-01-01 01:02 loader -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-01 01:02 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-01-01 01:02 mobicore -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-01-01 01:02 oeminfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-01-01 01:02 parm-spml-dep -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-01 01:02 parm-spml-ind -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-01 01:02 ramdisk-broadcom -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2013-01-01 01:02 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2013-01-01 01:02 sdcard -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2013-01-01 01:02 sys-parm-dep -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-01 01:02 sys-parm-ind -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-01 01:02 system -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2013-01-01 01:02 u-boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-01-01 01:02 u-boot-env -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-01-01 01:02 ubootlogo -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-01-01 01:02 umts-cal -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-01 01:02 userdata -> /dev/block/mmcblk0p31
Code:
[email protected]_gfive_wg5002g:/dev/block/platform/sdhci.1/by-name # for x in `ls`;do busybox fdisk -l $x;done
[....]
Disk boot: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Disk boot-parm: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Disk cache: 157 MB, 157286400 bytes
4 heads, 16 sectors/track, 4800 cylinders
Disk cp-boot: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders
Disk loader: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Disk misc: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Disk ramdisk-broadcom: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Disk recovery: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Disk sdcard: 1073 MB, 1073741824 bytes
4 heads, 16 sectors/track, 32768 cylinders
Disk system: 891 MB, 891289600 bytes
4 heads, 16 sectors/track, 27200 cylinders
Disk u-boot: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Disk ubootlogo: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Disk userdata: 1614 MB, 1614807040 bytes
4 heads, 16 sectors/track, 49280 cylinders
[..]
my CWM recovery image dropbox.com/s/1r4bkppweenkmxs/recovery.img?dl=0
my Stock recovery: dropbox.com/s/imndi2fg5t9vr54/Stock%20Recovery?dl=0
Sorry for post splitting and weak link. I was unable to send one so long post and links
Can you help me solve this problem?