I'm trying to extract boot, recovery, system from my Rogers Notes, and need some clarification. Do I need to be rooted first? When I try now, I cannot access /dev/block to extract any image.
It seems all the root methods available somehow modifies the kernel or recovery or system, which kinda makes it impossible to extract stock images?
Help please
I have used adb to shell into the Note and extracted the various images. I'm looking for stock Rogers images. The ones DAGr8 posted still has the Telus brand on them.
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
ha! i'm on the boat, i'm trying to extract all the original stuff before going crazy on it
just a few min ago i PMed DAGr8 for details
seems like you beat him to it
i know the radio was already done
so i'll just do those 3 mentioned above
firefly9 said:
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
Click to expand...
Click to collapse
firefly9 said:
I have used adb to shell into the Note and extracted the various images. I'm looking for stock Rogers images. The ones DAGr8 posted still has the Telus brand on them.
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
Click to expand...
Click to collapse
Once I get adb running do I just input the above commands into the command prompt?
Does the "adb pull" command just copy the images from the device or does it remove them?
Sorry for the basic adb questions. I've always had Nexus phones so I'm not sure if things work differently on other phones.
Once in the shell on the device, denoted by the "$" prompt, enter the commands outlined. After the "dd" commands have been completed, enter "exit" (twice, actually) and then the "adb pull" commands to copy the images from the device to you local computer. The images are copied so they will remain on the device until you delete them.
i find this easier...
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb shell dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
adb shell dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
if you had a v20b FACTORY install, can you please respond to this thread. we need your x-loader and u-loader to unlock specific phones that meet specific conditions ( http://forum.xda-developers.com/showthread.php?t=2461483 ). you can get them on your internal OR external sdcard by being rooted with busybox installed, and typing:
Code:
# internal sdcard
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/p1.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/p2.bin
# OR external
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
they are very small files and won't take you but a second to upload. it HAS to be FACTORY, other wise, you will NOT truly have the v20b's x-loader and u-boot. you can be rooted and install busybox (actually, you will HAvE to, if you want to copy those files), and it won't hurt - but your phone has to have been SHIPPED with v20b. you may be helping us to help you later down the road - because i don't know that those EXACT files exist any where on the internet (i've been looking).
thanks in advance.
I think the x&u of P760 is the same, whether it is extracted from KDZ (as Lelus did and provide) or it is from a phone that comes with v20b factory.
Before 4.0 and 4.0
* Need IT's Rooted Device *
1. adb shell su -c "mount"
2. adb shell su -c "cat /proc/mtd
Now show list of your system img where stay
example : boot.img = /dev/block/mtdblock7
so you can pull out from there .. here ..
3. adb shell su -c "chmod 777 /dev/block/mtdblock7"
4. adb shell su -c "dd if=/dev/block/mtdblock7 of=/storage/sdcard0/boot.img"
(of=/storage/sdcard0/ .. this location may b change you can look at "mount" )
-----------------------------------------------------------------------------------------
After 4.1 or mmc
1. adb shell su -c "mount"
2. adb shell su -c "cat /cache/recovery/last_log"
Now show list of your system img where stay
example : boot.img = /dev/block/mmcblk0p7"
so you can pull out from there .. here ..
3. adb shell su -c "chmod 777 /dev/block/mmcblk0p7"
4. adb shell su -c "dd if=/dev/block/mtdblock7 of=/storage/sdcard0/boot.img"
(of=/storage/sdcard0/ .. this location may b change you can look at "mount" )
For someone dont' know
thanks all ...
I can't find any info on whether or not it's imperative , or possible to back up efs on this device. I typically always back them up when I am rooted bc it's my biggest fear in somehow getting corrupted or lost, and not having anyway to restore. There doesn't seem to be a topic anywhere on These boards (DNA) so I'm thinking it's either impossible to lose or very easy to restore lol. Anyone know for Sure ?
adb shell su -c "cat /proc/partitions"
adb shell su -c "cat /proc/emmc"
adb shell su -c "mkdir /sdcard/img"
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p18 of=/sdcard/img/radio_config.img"
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p22 of=/sdcard/img/modem_st1.img"
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p23 of=/sdcard/img/modem_st2.img"
mkdir efsbak
adb pull -p /sdcard/img/radio_config.img .\efsbak
adb pull -p /sdcard/img/modem_st1.img .\efsbak
adb pull -p /sdcard/img/modem_st2.img .\efsbak
I have a question here. Recently the LG G PRO 2 android handphone received OTA update. If I let the OTA run. After OTA updated, if I still want to re-install Philz Touch Recovery, is that mean the latest newer file provided by OTA update will be overwrite when I re-install the recovery that released 1 yr ago?
Below is the command that will install the files if I re-install the recovery. I dont know if these file important or not if replaced by recovery installation. I have no idea the purpose of these files. Please advice.
What I hope is to make sure latest stable file running on my phone.
adb shell su -c "dd if=/sdcard/img/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
adb shell su -c "dd if=/sdcard/img/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
adb shell su -c "dd if=/sdcard/img/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot"
adb shell su -c "dd if=/sdcard/img/dbi.img of=/dev/block/platform/msm_sdcc.1/by-name/dbi"
adb shell su -c "dd if=/sdcard/img/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf"
adb shell su -c "dd if=/sdcard/img/persist.img of=/dev/block/platform/msm_sdcc.1/by-name/persist"
adb shell su -c "dd if=/sdcard/img/rpm.img of=/dev/block/platform/msm_sdcc.1/by-name/rpm"
adb shell su -c "dd if=/sdcard/img/sbl1.img of=/dev/block/platform/msm_sdcc.1/by-name/sbl1"
adb shell su -c "dd if=/sdcard/img/tz.img of=/dev/block/platform/msm_sdcc.1/by-name/tz"
adb shell su -c "dd if=/sdcard/img/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem"