Is there a way to completely backup the phone? All partitions (kernel/system etc.)? Preferably something that I can run with the phone connected to a PC.
I thought this might have been possible with FlashTool, but it only seems to be capable of pushing stuff onto the phone rather than pulling, which seems a bit odd.
Is TWRP or similar the only method?
Mroid said:
Is there a way to completely backup the phone? All partitions (kernel/system etc.)? Preferably something that I can run with the phone connected to a PC.
I thought this might have been possible with FlashTool, but it only seems to be capable of pushing stuff onto the phone rather than pulling, which seems a bit odd.
Is TWRP or similar the only method?
Click to expand...
Click to collapse
i was have tool here but it under upgrading to support z3+ and z5
maybe release it and maybe not
you can do it manually if you have minimal adb
by
Code:
adb shell
su
1. for Boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
2. for System
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
3. for Data
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/sdcard/userdata.img
4. TA
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
this will make dump of your partition to your sdcard
to pull it to pc use
adb pull /sdcard/your_partition.img .[COLOR="Red"]\[/COLOR]
Remember
1. you must have space for backup on your internal storage
2. i recommend you Backup-TA by DevShaft for TA partition
hit thanks if helped
Related
I have a very decent working ROM at the moment (4.4.4 rooted xposed gravitybox etc.) and I'm not sure I can live with Lollipop without al those tweaks. So before upgrading to Lollipop (whenever that may be), I want to make a decent backup of my current ROM.
Normally I would do this with TWRP, but the backup doesn't seem to work at the moment. And there doesn't seem to be a properly working version of TWRP.
So how do I make a proper backup of my ROM?
Adb?
A confirmed working version of TWRP?
CWM?
Another?
Jeltel said:
I have a very decent working ROM at the moment (4.4.4 rooted xposed gravitybox etc.) and I'm not sure I can live with Lollipop without al those tweaks. So before upgrading to Lollipop (whenever that may be), I want to make a decent backup of my current ROM.
Normally I would do this with TWRP, but the backup doesn't seem to work at the moment. And there doesn't seem to be a properly working version of TWRP.
So how do I make a proper backup of my ROM?
Adb?
A confirmed working version of TWRP?
CWM?
Another?
Click to expand...
Click to collapse
You can use standard tools installed on the phone to dump your partitions. See here for a rundown. I'd recommend backing up /boot, /recovery, /system, /pds, /modem and /fsg.
Ah yes, that's what I was looking for. Thanks
When I restore the mentioned items, will I get back my old installation? Or should I backup more? i.e. userdata for example?
And how to restore all these items? (I know to flash the boot, recovery and system.img via adb).
Yeah, you'd need to backup the data partition too, if you want to keep settings and user data. Remember, dd produces a 1:1 copy of the partition... I prefer to backup personal data selectively. The quick way to do it is by using a backup app: Most use Titanium Backup, but I find Chainfire's Helium does the job well, too. The other way is to use the built-in 'backup' command directly to select a range of files to save (i.e. 'adb backup')...
The partition images can be restored from adb using the reverse version of the command you used to make to the backup, i.e. use dd but with the 'if' and 'of' parameters switched:
Code:
dd if=/path/to/source.img of=/path/to/block/device
Be careful though; if you write the wrong image to the wrong partition, you can damage -- or even hose -- your software environment.
In the case of most partitions, restoring images should be done whilst booted into recovery for safety reasons, rather than overwriting a filesystem whilst it is mounted and in use. If you have the stock recovery installed, you can temporarily boot into TWRP or CWM recovery from a recovery image stored on your computer (i.e. 'adb boot /path/to/recovery.img') and then enable adb from within the custom recovery environment. Then you just use 'adb shell', followed by the 'su' command to switch to the root user account.
For the same reason, you should write the recovery partition backup back to disk from adb within the normal android environment. Again, you must do this after switching to the root user account by issuing the 'su' comand.
Alternatively, you should be able to write all the images from fastboot mode (i.e. 'adb reboot lootloader'). For example:
Code:
adb fastboot flash recovery recovery.img
AFAIK, fastboot will accept standard images created with dd, but I have never tried it on a Moto G, so YMMV... Maybe someone else would care to comment on this?
Hello,
I am hoping someone can assist with interpreting my log file or provide suggestions on how to convert my backups into a usable format that can be flashed back to the phone thus recovering it to a usable state. I have a logcat and dmesg in a text log file. I have put the file up on Google drive, the link is here-
https://drive.google.com/file/d/0B9e...ew?usp=sharing
I also spent time reading and studying the post about using logcat and dmesg posted here-
http://forum.xda-developers.com/showthread.php?t=2274119
I believe the last operation I tried before softbricking was installing the Xposed framework module for my device (running Lollipop 5.1.1).
I have tried one solution so far, go into recovery, clear cache and reboot.
To recover from this issue I think I have two basic options-
#1 restore from backup
#2 locate the problem that is causing the system to hang at startup in the first place
At the end of the day I am trying to find the simplest, quickest method to get back up and running. Both methods are acceptable to me. I am not worried about losing any data.
My phone is a BLU Studio C 5+5 LTE and therefore can't use TWRP or CWM (At least that is my assumption, maybe someone knows different). Before getting into the softbrick state I took 3 different types of backups in the hopes that one of them could be used in case it was needed. (like this)
Type 1 - I did an ADB shell backup from a completely stock device (unrooted). I used this command-
adb backup -apk -all -f fullbackup.adb
For this method I followed this guide here-
https://linuxiswonderful.wordpress.com/2015/04/04/full-backup-of-nonrooted-android/
Type 2 - I used Titanium backup and performed a complete system and application backup
Type 3 - I rooted the phone and backed up all partitions using dd after reviewing the partition layout of the device. For example, to backup the system partition I did the following at an ADB shell-
dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/firmware-img/system.img
I am able to still communicate to my device using ADB and I can get an ADB shell or enter fastboot mode.
My challenge/sticking point is how to turn my backups into a usable format to get me back on track or understand the boot process enough to get out of the boot loop. I am familiar with how Linux boots as I am a SysAdmin. I know Android is similar but just different enough to make me research this further.
The first thing I tried was mounting my raw image files created from the dd process. I followed this guide-
https://samindaw.wordpress.com/2012/03/21/mounting-a-file-as-a-file-system-in-linux/
I ran these commands-
#losetup /dev/loop0 /path/to/my/system.img
# mkfs -t ext3 -m 1 -v /dev/loop0
# mount -t ext3 /dev/loop0 /mnt
# cd /mnt
# ls
The various image files I created all seemed to mount "ok" OK meaning that the loopback mount process worked but it appears there is nothing but a lost+found folder in the mounted image. (I'm not sure why that is.)
I am still researching methods to turn my other backups into something usable for recovery purposes.
For using the adb backup file I created, this is what my understanding is-
Adb backup uses a type of compression (don’t remember what kind). I would need to uncompress the file first. After uncompressing and being able to view the file contents I would think I should be able to put together a flashable zip file of some sort.
I think the process for Titanium backup would generally be the same- uncompress/convert file format, create/assemble a flashable zip file
If there is any other info you need to see, please let me know. I made a lot of notes about the system architecture, partition layout, etc.
Many Thanks in Advance for your Advice!
Found my answer. Used ADB shell and mounted /system in RW mode. Changed /system/bin/dex2oat filename and the device booted normally. Issue solved!
I made a script to backup any partition in our A7:
YOU HAVE TO BE ROOT, TO USE IT.
To run it simply push to the sdcard fire up adb shell to launch the script.
from the computer while connected to the A7 with usb debugging turned on
Code:
adb push PATH_to_the_script/full-backup.sh /sdcard
and
Code:
adb shell
su
cd /sdcard/
sh full-backup.sh
you will see a menu to choose which partition to backup.
As in the attachment.
enjoy, and please hit the thanks button.
the script v1.00
and a terminal screenshot.
Could you use terminal emulator to run this from on the phone thus cutting out the need for a pc?
ultramag69 said:
Could you use terminal emulator to run this from on the phone thus cutting out the need for a pc?
Click to expand...
Click to collapse
yes you could run it directly form the device:
fire up a terminal emulator app:
RUN IT AS ROOT
Code:
su
sh /sdcard/full-backup.sh
thank you. we can backup unmodified firmware via this tool right?
RealSchule said:
thank you. we can backup unmodified firmware via this tool right?
Click to expand...
Click to collapse
So you need to be root to use this script, so not really..
RealSchule said:
thank you. we can backup unmodified firmware via this tool right?
Click to expand...
Click to collapse
The root modifed just the boot partition so you could backup every stock partition but the stock boot... but you could get the stock boot from other places...
manu7irl said:
The root modifed just the boot partition so you could backup every stock partition but the stock boot... but you could get the stock boot from other places...
Click to expand...
Click to collapse
we can backup all images except boot.img with this tool but we can find boot.img from other topic. so we have full stock images right?
If you have root you can backup every single partition. This is not full stock rom! This is for backup and restore easily.
manu7irl said:
If you have root you can backup every single partition. This is not full stock rom! This is for backup and restore easily.
Click to expand...
Click to collapse
So what is the process to restore these images? Is it as simple as flashing in twrp?
Go in TWRP, fire up adb shell on your PC, then do:
Code:
dd if=/sdcard/[backup_folder]/[partition].img of=/dev/block/bootdevice/by-name/[partition_name]
example:
Code:
dd if=/sdcard/backup-part/[date-folder]/system.img of=/dev/block/bootdevice/by-name/system
I will also make a restore part in this little script. If you are intersting in one to do so.
Sure that would be great. Thanks.
manu7irl said:
Go in TWRP, fire up adb shell on your PC, then do:
Code:
dd if=/sdcard/[backup_folder]/[partition].img of=/dev/block/bootdevice/by-name/[partition_name]
example:
Code:
dd if=/sdcard/backup-part/[date-folder]/system.img of=/dev/block/bootdevice/by-name/system
I will also make a restore part in this little script. If you are intersting in one to do so.
Click to expand...
Click to collapse
Been waiting for just that.
Hi everyone,
I wanted to unlock the bootloader on my OP3T but I don't want to lose all the data. So I wondering if I could back my phone with the command,
adb backup -all -apk
and then unlock the bootloader and then restore the backup that I made. Are there any disadvantages to this? Will I lose out on updates? Will I lose any data? Anything else I should know?
I think you will in the end need root via adb to accomplish this. Imagine this, if without unlocking phone you can use adb to make a backup then anyone can do that(who have enough knowledge) and this can be a major security concern.
Soo I think it is not possible.
It is possible. As stated on Titanium Backup's webpage:
1. How to make your first backup WITHOUT root:
Before beginning, you need to setup your ADB and have your device detected. You must also running Android version 4.0 and above. Also, make sure you have a file manager installed. Our favorite is the ES File Explorer.
Connect your device and make sure its listed with the following command:
Code:
adb devices
Run a FULL backup with the following command:
Code:
adb backup -f FullBackup.ab -apk -all
This will create a “package” called “FullBackup.ab” on the current location in your command prompt. This is your backup package.
Now you can root your phone.
Once finished rooting, insert the “FullBackup.ab” package on your sdcard
Hit the menu button and look for “Extract from ADB backup” option. This will prompt you to search for the file. Use the file manager that you installed earlier and navigate to the directory and select the FullBackup.ab file.
Now restore like as if the backup was made with Titanium Backup. Don’t forget to make a fresh copy of the backup using Titanium Backup. You’re Done!
Click to expand...
Click to collapse
As there is no decryptable TWRP, it isn't as easy as before to bakcup the EFS partition. But doing it via Terminal isn't too difficult. I didn't find a good tutorial that isn't burried somewhere on the internet. And none for the 7T Pro (though the commands and partitions are the same on older OnePlus devices.
If you already know how to boot TWRP or you already have it, go to the second instructions list and skip the first one.
I am not responsible if anything goes wrong. You do this at your own risk!
Requirements:
- An unlocked bootloader
- Working adb and fastboot (e.g. Google's Platform Tools)
- Download a bootable TWRP
Instructions to boot TWRP:
- Connect your device via USB
- Go to Settings > Developer Settings > Enable Advanced Reboot Menu
- Hold down the power button and select "Bootloader"
- In the bootloader use (It won't modify anything, you simply boot into TWRP once and after a reboot it's "gone".)
Code:
fastboot boot NameOfTWRPImage.img
Instructions to backup EFS:
If TWRP has booted, type the following into your computers' terminal one after the other:
Code:
adb shell
dd if=/dev/block/sdf2 of=/tmp/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/tmp/modemst2.bin bs=2048
exit
adb pull /tmp/modemst1.bin modemst1.bin
adb pull /tmp/modemst2.bin modemst2.bin
This will copy modemst files to the temporary folder on the phone (which can be accessed though the data is lost after a reboot) and "adb pull" copies them from the device to the user's profile folder on Windows or Mac. You have successfully backed up the EFS partition!
Please note that this could be performed with root permissions on a booted device. Though I always prefer backing up files with a non-booted system. Also this guide will work if you're not rooted.
Is it possible to backup all system and data so we dont have to setup everything in the device after a factory reset? I mean, that backup we all were used to in TWRP.
Best regards
lucfig said:
Is it possible to backup all system and data so we dont have to setup everything in the device after a factory reset? I mean, that backup we all were used to in TWRP.
Best regards
Click to expand...
Click to collapse
Unfortunately not. Backing up EFS doesn't require decryption as it's not stored on /data. Everything on /data can't be backed up afaik.
Also /vendor and /system can't be mounted as of now making a Nandroid backup impossible.
Macusercom said:
Unfortunately not. Backing up EFS doesn't require decryption as it's not stored on /data. Everything on /data can't be backed up afaik.
Also /vendor and /system can't be mounted as of now making a Nandroid backup impossible.
Click to expand...
Click to collapse
Thanks.
That is a shame. At least titanium backup still working great.
Enviado de meu HD1903 usando o Tapatalk
Macusercom, thank you for the guide!
Now how do we restore them? With the opposite dd command?
Or we can just flash them directly via fastboot?
Also, what is the full list of partitions which contain data unique to this specific device?
I mean all these EFS, persist, IMEI, screen/touch calibration data, all sensors factory calibration data, fingerprints, etc.
Is it only EFS + persist or there are more of them?