Develop Bugs

[Q] How to restore images which are backuped with dd via ADB

First of all I'm still exploring Androide and Linux = bit of a noob still
I rooted and then saved those images like this:
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/backup/recovery/recovery_dd.img
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/backup/efs/efs_dd.img
How can I restore them ?? (via ADB, Odin, Flashify)

In the opposite way
dd if=/storage/extSdCard/backup/recovery/recovery_dd.img of=/dev/block/mmcblk0p10
dd if=/storage/extSdCard/backup/efs/efs_dd.img of=/dev/block/mmcblk0p3

radkor said:
In the opposite way
dd if=/storage/extSdCard/backup/recovery/recovery_dd.img of=/dev/block/mmcblk0p10
dd if=/storage/extSdCard/backup/efs/efs_dd.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
THX, didnt know that it is that simple. Can this be done during the device is in normal ON mode or do I have to set the device into a special mode after boot ?
How would you restare a system.img made with dd ? (I think ist not such a good idea to do it in normal ON mode ??)

How would you restore a system.img ?
a) extracted from StockROM package (does it need any conversion first ?)
b) made with dd
I think ist might not be a good idea to do it in normal ON mode ?? (Odin, ....???)

How to make image backup of system & user partition of VZ LG G4...

I am about to flash the rooted system image for the LG G4, using the "Low Effort" root method at http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
Before I do that, I would like to back up my system (and perhaps my user) partitions. Since I don't have a custom recovery, I am not sure how to do that.
Can someone help me?
Thanks!
nPQ9nP

To backup the system partition on the VZ LG G4 VS986, After you've got the drivers loaded on your PC and and have installed the G4root send commands and have adb loaded, but before you use dd to push the pre-rooted image, run the command:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img
This is dump your original system partition to the system.img file on the internal SD card.

and what would be the command to backup system 815?

Please provide partial eMMC dump!

Hello!
The fact is, I somehow hard-bricked my M9 (international version, MID: 0PJA10000, CID: originally HTC__A07, but probably any will be OK) - when flashing one of the firmwares it (I don't know why) flashed the 64 GB partition table instead of a 32 GB one and went into reboot, now I'm in 9008 BULK mode). My only hope now is to find an SDCard - on some of Qualcomm SoCs it is a safeguard - and try to boot from it - but for that I need an image of the working system.
Can somebody help me getting this - anyone with rooted 32 Gb version and S-OFF (S-ON dump didn't helped)? The command is very easy:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=768
If it doesn't work, just:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=768
Then just give me pls that 768 Mb backup.bin file (it shouldn't have any personal information).
Help me please! This is my last hope.

Evengard said:
Hello!
This is my last hope.
Click to expand...
Click to collapse
[30;[email protected]:/ # busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=768
ybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=768 <
tmp-mksh: 0: not found
tmp-mksh: 120Rbusybox: not found
127|[email protected]:/ #
not sure what I'm doing wrong.

try without "busybox", just
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=768

S-ON dump didn't helped, seeking now an S-OFF dump!

Evengard said:
S-ON dump didn't helped, seeking now an S-OFF dump!
Click to expand...
Click to collapse
one sec.. Figured it out.

You have S-OFF?

Evengard said:
You have S-OFF?
Click to expand...
Click to collapse
Ya mon.
https://drive.google.com/file/d/0B9bgIP18PHxZLVluM2ZfYjhnVzg/view?usp=sharing

Wow thanks will try!

Evengard said:
Wow thanks will try!
Click to expand...
Click to collapse
If your phone explodes, you can't have mine.

It didn't explode but didn't helped neither

[Q] H815L root ?

Hello,
I tired to root my phone, (lg g4 ,marsllmow v20f)
when i do this command
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
Code:
C:\Users\danie\Desktop\ROT>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
FAIL
#
thanks for help, if have some tut in video step by step , i will help
Thanks !!!!!

Try:
Code:
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0

Danic0 said:
Hello,
I tired to root my phone, (lg g4 ,marsllmow v20f)
when i do this command
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
Code:
C:\Users\danie\Desktop\ROT>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
FAIL
#
thanks for help, if have some tut in video step by step , i will help
Thanks !!!!!
Click to expand...
Click to collapse
With that method, it's not possible to root LG G4 with MM. In MM, first you need modify kernel, and then install SuperSu throu Custom Recovery (so you need unlocked bootloader). The latest versions of SuperSU, are able to patch kernel and then apply root.

lept_2014 said:
With that method, it's not possible to root LG G4 with MM. In MM, first you need modify kernel, and then install SuperSu throu Custom Recovery (so you need unlocked bootloader). The latest versions of SuperSU, are able to patch kernel and then apply root.
Click to expand...
Click to collapse
have some tutrial for this ?

Danic0 said:
have some tutrial for this ?
Click to expand...
Click to collapse
You can't. Right now there's no option to unlock the H815L bootloaders,
so.. no root for MM soon...

Moto E4 Guide To Backup Stock ROM Rooted Device Only

This guide will help you to take backup of your device Stock ROM manually. For this you need a Moto E4 Device.
Requirements :
• Moto E4 Any Variant
• Unlocked Bootloader
• Rooted
• Installed Terminal Emulator Application​
Procedure :
Install Terminal Emulator
--- After Installing Follow These Commands ---​
Terminal commands :
Type :
PHP:
su
After getting Superuser permission type all the below commands
---- For Mediatek Variant ----​
Boot image​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/sdcard/boot.img
Expdb​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb of=/sdcard/expdb.img
Frp​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp of=/sdcard/frp.img
Logo​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo of=/sdcard/logo.img
Preloader​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk of=/sdcard/lk.img
Nvram​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram of=/sdcard/nvram.img
Nvdata​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata of=/sdcard/nvdata.img
OEM​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/oem of=/sdcard/oem.img
Protect1
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 of=/sdcard/protect1.img
Protect2
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 of=/sdcard/protect2.img
Persist​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/persist of=/sdcard/persist.img
Proinfo​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo of=/sdcard/proinfo.img
Para​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para of=/sdcard/para.img
Recovery​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/sdcard/recovery.img
Secro​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/secro of=/sdcard/secro.img
Seccfg​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg of=/sdcard/seccfg.img
Tee1​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1 of=/sdcard/tee1.img
Tee2​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2 of=/sdcard/tee2.img
System​
PHP:
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system of=/sdcard/system.img
---- For Qualcomm Variant ----
System
PHP:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard/system.img
Keystore
PHP:
dd if=/dev/block/bootdevice/by-name/keymaster of=/sdcard/keymaster.img
Boot image
PHP:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Recovery
PHP:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
OEM
PHP:
dd if=/dev/block/bootdevice/by-name/oem of=/sdcard/oem.img
Persist
PHP:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Radio
PHP:
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.img
Misc
PHP:
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img
Nvram
PHP:
dd if=/dev/block/bootdevice/by-name/nvram of=/sdcard/nvram.img
Nvdata
PHP:
dd if=/dev/block/bootdevice/by-name/nvdata of=/sdcard/nvdata.img
Here in these commands i use *.img format. You can change *.img format to *.bin format.​

What's the need when you have twrp recovery to backup.
Moderator Edit:
I have deleted your quote of the entire OP (the post above this). There is no need to do this - apart from being unnecessary, it can cause issues for those members on limited bandwidth or when Mobile. Thanks for your future consideration.

drganbds said:
What's the need when you have twrp recovery to backup.
Click to expand...
Click to collapse
TWRP is limited.
you can only take backup of system, data, cache & boot with TWRP recovery. you cannot take backup of nvram with twrp recovery. If you accidently wiped nvram data, you will lost all your device wireless functionality like wifi, radio, bluetooth & etc. so only this guide will going to help you.

You should specify this guide as being for the mtk variants, not all variants because the commands are not the same as the Qualcomm variants

amarc78 said:
You should specify this guide as being for the mtk variants, not all variants because the commands are not the same as the Qualcomm variants
Click to expand...
Click to collapse
Yes qualcomm variant of Moto E4 have different "block device path" and thanks for your suggestion will update the OP when i get free time.

If anyone has a backup of the XT1766 Boost Mobile Qualcomm variant I would love to have a copy of it

PimpMy5Ton said:
If anyone has a backup of the XT1766 Boost Mobile Qualcomm variant I would love to have a copy of it
Click to expand...
Click to collapse
Their's a qualcomm subforum ask there for help or stock backup :good:

Worked great, though there were no nvram partitions to back up on my metro model.
Nice to have a full stock backup just in case, thanks!
Sent from my XT1765 using Tapatalk

nekomancey said:
Worked great, though there were no nvram partitions to back up on my metro model.
Nice to have a full stock backup just in case, thanks!
Sent from my XT1765 using Tapatalk
Click to expand...
Click to collapse
-OP- is dead now.
No thanked to him. LOL
---------- Post added at 08:18 AM ---------- Previous post was at 08:16 AM ----------
nekomancey said:
Worked great, though there were no nvram partitions to back up on my metro model.
Nice to have a full stock backup just in case, thanks!
Sent from my XT1765 using Tapatalk
Click to expand...
Click to collapse
*Radio* is your device nv partition.

Francesco Franz said:
Their's a qualcomm subforum ask there for help or stock backup :good:
Click to expand...
Click to collapse
I'm asking here because this is a backup thread, I will not ask elsewhere.