[Q] Extract recovery.img from your phone - General Questions and Answers

Hey everyone,
I'm having trouble extracting a recovery.img from my phone. More specific I can't seem to find which file I have to 'dd' to create the img file.
Some commands with the output
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
Code:
[email protected]:/ # mount
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 ro,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 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:97 /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:97 /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
/dev/block/vold/179:6 /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
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 85216 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15110144 mmcblk1
179 97 15106048 mmcblk1p1
Code:
[email protected]:/ # cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0000ac40 00002800 "sec_ro"
emmc_p3: 00010740 00100000 "android"
emmc_p4: 00110f40 00100000 "cache"
emmc_p5: 00211740 00500000 "usrdata"
emmc_p6: 00711f40 000299c0 "fat"
Even by running the commands above I'm still not able to determine where I can extract a recovery.img.
Ive been looking around and can't seem to find anything so I hope someone can point me in the right direction.
PS: Phone in question is a Star B92M (chinaphone)
Thanks for the help!
~Whookid
EDIT: I'm looking for a way to do this without SP Flash tool

Is your phone rooted? If so, you can create a backup by using a script made available by our fellow Russian users from forum.china-iphone.ru. Give it a shot... here.

I've just remembered that you can also use MTK Droid Root & Tools for that.

Related

[Q] HTC Sensation, Flashing offical ROM, branded, SIMunlock, rooted

Hi I know im new to this forum, but I am technically knowledgeable, however I have a question, I bought a HTC Sensation, that was branded and locked to three UK network..
After thinking about this, is it not the case that network locks are applied by the network operator when they brand the device, if so, whats to stop me from flashing a Europe version, which I assume would get rid of all that, since it would then function as if it was not from any specific carrier right ?
My Sensation has been, s-off, permanently rooted, and super CID, with complete success, and i have done a backup with clockwork..
I mean the whole point to doing all this is so you are able to modify and have complete access to the set, i have seen people manually hex edit a specific file to make the phone unlocked on all networks, but that was for a different HTC model..
Any advice would be welcome.. !
List of defualt mounts HTC Sensation
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
/dev/block/mmcblk0p22 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p27 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022 ,codepage=cp437,iocha
rset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs 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 /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/data/d /data/d debugfs rw,relatime 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allo w_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=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:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso 8859-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.androirc-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=02 22,dmask=0222,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.svox.pico.voice.eng.gbr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=02 22,dmask=
0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
List of defualt files in /dev/block/
mmcblk1p1
mmcblk1
mmcblk0p31
mmcblk0p30
mmcblk0p29
mmcblk0p28
mmcblk0p27
mmcblk0p26
mmcblk0p25
mmcblk0p24
mmcblk0p23
mmcblk0p22
mmcblk0p21
mmcblk0p20
mmcblk0p19
mmcblk0p18
mmcblk0p17
mmcblk0p16
mmcblk0p15
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
Will find out soon..
Im going to pay my three network to give me the code to unlock my phone, when thay do, ill serch for that code in the files on my device and tell you where you can also get yours.. thats if its not encoded or something..
will be looking forward to this, I also have a 3(uk) locked phone, which i installed a custom rom on, was expecting the phone to open onto all networks (like my old htc touch hd).
good luck, will be checking progress.
sa2am said:
will be looking forward to this, I also have a 3(uk) locked phone, which i installed a custom rom on, was expecting the phone to open onto all networks (like my old htc touch hd).
good luck, will be checking progress.
Click to expand...
Click to collapse
help me here, thanks.
http://forum.xda-developers.com/showpost.php?p=16816803&postcount=1
Ok ive held off paying £15 quid to get the code at the moment, im looking for the code my self.. at the moment the codes ive used dont work, including the date in mmcp6 file..
If you want to try your self.. use ADB..
Open a CMD window and type:
adb shell
su
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
then mount ur sdcard, and open the drive in windows.. and copy the files over.. and open them in hex edotor or notepad dosent really matter what.. and try numbers.. it should be 8 digits..
This is the output from copying the files over for me.. so you can see the byte sizes etc
# dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
2+0 records in
2+0 records out
1024 bytes transferred in 3.160 secs (324 bytes/sec)
# dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
512+0 records in
512+0 records out
262144 bytes transferred in 0.163 secs (1608245 bytes/sec)
# dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
512+0 records in
512+0 records out
262144 bytes transferred in 0.086 secs (3048186 bytes/sec)
#
Heres more info on this subject:
http://forum.xda-developers.com/showthread.php?p=16933050#post16933050
Method one is not the same on my device, though there is a date its not in the same place.. and dosent work..
so im tempted to try mothod 2.. but a bit hessitant to try things that i dont know what damage it would do..
Ok screw it just did method 2 in here:
http://forum.xda-developers.com/showthread.php?p=16933050#post16933050
And POW indeed my sim is now unlocked.. and whats great it it also removed the dumb boot branding screen of Three network as well...

[Q] cat /proc/mtd or emmc not working, EXT4 partitions, not YAFFS

A Chairde
Having a problem extracting partitions using DD ....
Start of the process involves either CAT /PROC/MTD or /PROC/EMMC , but neither command works .. they are not in /PROC directory , and no CAT commands I ran there give a similar output to types I got off different phones ...
Ran these commands, outputs below ... ls /dev/mtd/mtd* is not working ..... no such files ... anyone give me some help on this ?
[email protected]:/system/media # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 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
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:1 /mnt/extsd fuseblk rw,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=asci
i,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/system/media # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd
93 32 819200 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 131072 nandi
93 72 13762560 nandj
179 0 31166976 mmcblk0
179 1 31162880 mmcblk0p1
[email protected]:/system/media #

Cant find stock recovery.img to pull.

This is what I get I dont see recovery?
Code:
I cant find my recovery.img
cat /proc/partitions
major minor #blocks name
31 0 114688 mtdblock0
31 1 665600 mtdblock1
31 2 512000 mtdblock2
31 3 358400 mtdblock3
31 4 2527232 mtdblock4
179 0 15632384 mmcblk0
179 1 15628288 mmcblk0p1
$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 07000000 00200000 "reserved"
mtd1: 28a00000 00200000 "system"
mtd2: 1f400000 00200000 "misc"
mtd3: 15e00000 00200000 "cache"
mtd4: 9a400000 00200000 "userdata"]
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=100
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/ubi3_0 /cache ubifs rw,nosuid,nodev,relatime
/dev/ubi2_0 /misc ubifs rw,relatime 0 0
/dev/ubi1_0 /system ubifs ro,relatime 0 0
/dev/ubi4_0 /data ubifs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,re
023,default_permissions,allow_other 0 0
/dev/block/vold/179:1 /mnt/sdcard1 vfat rw,dirsync
uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utim
t=cp936,shortname=mixed,utf8,errors=remount-ro 0 0
Code:
I cant find my recovery.img
cat /proc/partitions
major minor #blocks name
31 0 114688 mtdblock0
31 1 665600 mtdblock1
31 2 512000 mtdblock2
31 3 358400 mtdblock3
31 4 2527232 mtdblock4
179 0 15632384 mmcblk0
179 1 15628288 mmcblk0p1
$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 07000000 00200000 "reserved"
mtd1: 28a00000 00200000 "system"
mtd2: 1f400000 00200000 "misc"
mtd3: 15e00000 00200000 "cache"
mtd4: 9a400000 00200000 "userdata"]
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=100
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/ubi3_0 /cache ubifs rw,nosuid,nodev,relatime
/dev/ubi2_0 /misc ubifs rw,relatime 0 0
/dev/ubi1_0 /system ubifs ro,relatime 0 0
/dev/ubi4_0 /data ubifs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,re
023,default_permissions,allow_other 0 0
/dev/block/vold/179:1 /mnt/sdcard1 vfat rw,dirsync
uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utim
t=cp936,shortname=mixed,utf8,errors=remount-ro 0 0

Having difficulty in finding system mount point

As an experimentation, I'm trying to take a full ROM backup of my Karbonn A35 (a little known MTK based phone) using this method. However, I'm unable to find the "by-name" folder inside /dev/block/platform. There is only one folder there called mtk-msdc.0. This is the output when I run cat /proc/partitions from the adb shell:
Code:
major minor #blocks name
7 0 5920 loop0
179 0 3845120 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1382144 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
And here is the output of cat /proc/mounts
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/secure tmpfs rw,relatime,mode=700 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 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:7 /storage/sdcard0 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:7 /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 /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Is there any easy way to backup the ROM using dd command from inside the shell?
The reason I want to backup the ROM is that later on I want to root and install CWM, CyanogenMod, etc. The said phone (Karbonn A35) is I think a rebranded version of HTC FairPhone First Edition because that's what it says in the lsusb.

How to recover partition layout?

Hi there all,
some time ago I was able to unlock my TF700T and install a custom ROM with TWRP. Then suddenly I messed up with something and I wiped the system and all. After a while, I wanted to recover the tablet and I upgraded TWRP to version 3.4.0, but then I discovered that system partition layout is all gone: no system, no data, no cache. I tried to format the partitions, but nothing works, I surfed in the forum for a couple of days and I couldn't find a solution. I think I have to recreate the partition table, but I don't know how.
This is the scenario when I run `cat /etc/fstab` and other commands:
Code:
/system ext4 rw 0 0
/cache ext4 rw 0 0
/data ext4 rw 0 0
/dev/block/mmcblk1p1 /external_sdcard vfat rw 0 0
/dock_sdcard vfat rw 0 0
`cat /proc/partitions`
Code:
179 0 62087168 mmcblk0
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 625221344 mmcblk1
179 49 62520320 mmcblk1p1
`cat /proc/mounts`
Code:
rootfs / rootfs rw 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
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk1p1 /external_sdcard vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
I have no backup, or rather I think I lost it, do you have any suggestion? Thanks in advance!

Categories

Resources