How do you Emulate the Old Android Backup Roms on PC - Android Q&A, Help & Troubleshooting

Hello Guys,
I am having few android rom backup's from my old Xperia Arc S, Wilfire, Galaxy S.
All were rooted and saved their nandroid backup.
The need of hour is to retrieve some data out of the Roms. But I am not having any device at the moment.
So the thing I wished to do is to emulate those roms and run them on PC.
Is it possible?
Let me know.
Thank You.

Not possible
I think its not possible....
if u wanted to get android experiance on pc go to android x86

Everything is possible! The nandroid backups are actual images from the partitions of the phone. The partitions are in jffs2 format (which is a file system optimized for flash storage), what actually nandroid does is a byte-by-byte copy of them. Because Android is basically a small linux machine, you can mount these img files on Ubuntu, for example with the commands described in this site:
http://www.plugcomputer.org/plugforum/index.php?topic=59.msg831#msg831
Go get your data!

Wow...
Sent from my Nexus S using Tapatalk 2

BirdyOfPrey said:
Everything is possible! The nandroid backups are actual images from the partitions of the phone. The partitions are in jffs2 format (which is a file system optimized for flash storage), what actually nandroid does is a byte-by-byte copy of them. Because Android is basically a small linux machine, you can mount these img files on Ubuntu, for example with the commands described in this site:
http://www.plugcomputer.org/plugforum/index.php?topic=59.msg831#msg831
Go get your data!
Click to expand...
Click to collapse
any solution for windows?

I can use winrar on windows to open the backups made from twrp on my wfs. I pulled a bootanimation that way.
This worked for me, but I knew exactly what I was looking for.

Related

Issues: new rom, back up?

Hi everyone. I've just rooted my galaxy s 2, running on gingerbread XWKE8. I'm planning to install a new rom.have heard about various rom available.
1. Is villain 2.0 rom okay? The main purpose for installing a custom rom for me is to save battery as I'm outdoor most of the time. as of now my gingerbread is working well except for this battery issue. Is it worth changing the rom?
2.Was reading about titanium backup
I've done back up of my custom apps + system data on phone' s external sd card. I don't have paid version of titanium. Can't buy it either. (no credit card).anyway, shall i be get nandroid backup too, just in case? when i install new rom n use TB for restore, since it*
Has system data as well, won't it overwrite the old data on the new rom? it sounds un believable coz it thwarts the whole purpose of installing a new rom. So will there be an option of ticking individual files to restore as per my choice? (no pro version of . titanium). If so, how do i know which one to be restored?
3. If clockworkmode has a back up option why do we need a titanium backup? cos it gives a nandroid type backup?
4. Can clockworkmode be used to upgrade to a new firmware (custom our stock) or odin should be used as in rooting with a little modification (depending on if firmware has one file or 3 files)?
Please enlighten.
Thank you very much
Sent from my GT-I9100 using XDA App
1) See for yourself if it's worth it.
2) Yes do a nandroid and check this before changing rom.
3) Nandroid is a exact copy of your current set-up, restoring it would undo the custom rom flash.Titanium backs up your apps so you can restore them after changing rom.
4) Depends on how the files are provided. Both should be possible.
For a credit card alternative I use this.
Hi.thanks a lot for replying. How do I get nandroid backup? Do I've to use rom manager in order to do nandroid backup? Cos when I search for nandroid in market, it doesn't return any nandroid app as such.
Sent from my GT-I9100 using XDA App
No boot in to recovery, go to backup and restore and backup.
TheGhost1233 said:
3) Nandroid is a exact copy of your current set-up, restoring it would undo the custom rom flash.Titanium backs up your apps so you can restore them after changing rom.
Click to expand...
Click to collapse
So if I happen to dislike or have problems with a custom rom, I just restore the backup of my rooted stock rom and all is back to the way it was (all, data/boot/apps/settings ...)? I think it will be, but I just want to be sure.
Hi.thanks again. I've read that recovery mode back up or titanium backup doesn't backup efs folder . One needs adb our terminal emulater or root explorer to do so.is there any link that explains efs folder backup using terminal emulater step by step?
Regards
Sent from my GT-I9100 using XDA App
dav pahwa said:
Hi.thanks again. I've read that recovery mode back up or titanium backup doesn't backup efs folder . One needs adb our terminal emulater or root explorer to do so.is there any link that explains efs folder backup using terminal emulater step by step?
Regards
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
EFS post in Dev section probably .
jje
I already linked to the right thread, in the thread there are different commands. All you have to do is pick a method, create the efs folder, copy the command to the terminal emulator and hit enter.
Sent from my Transformer TF101 using XDA Premium App
VillianRom is nice I've been using VR since release and tried many roms en route and keep coming back to VR for some reason!
Best to do a nandroid via CWM Recovery so if any of your new installs have problems you can always wipe and go back to a working config.
I only use TB to backup app data, I don't like backing up system data as when moving from one rom to another if you restore you may encounter issues so always best to start from scratch to save any hassles.
Default [REF] Backup /efs folder. IMPORTANT.
This guide is based on a guide by Candanga on the i9000 forums, and some commands from supercurio
Please hit thanks on their posts and show them some love for the write up.
-----------------------------------------------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centres.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
What you will need:
* Rooted SGS II to get permissions as a SU (Super User) and perform the backup
* I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile. <- Busybox Commands(or Google them)
* Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS II during this process, because it may request SU permissions [currently doesn't on CF-root]; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS II.
Here are 3 methods, I recommend that you do both Clean and RAW.
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD in sdcard/efs/, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can greatly support in recovering your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
Hi theghost & thanks for replying. Yes, i had read that link . But being a starter in androids, i had some doubts n thought if someone else knows a more simplified thread. Eventually i followed the same thread only.
As the author said, there r two methods - clean & raw n he advises to use both. when u used raw , in the end comes- no such file directory exists. When i checked my files->sdcard , i could see efs folder n some files inside it (which wasn`t happening even with astro file manger) I copied the efs folder N pasted it into Externalsd folder (default Ext. sd card folder ?)
R my efs folder files safe now ?
Is there any other precaution to be taken , any files to be saved before i embark on installing New villain rom 2.0 as per instructions given here http://forum.xda-developers.com/showthread.php?t=1081368 .
Strangely efs folder saving point isn`t mentioned here , even though its so important. (But then may be its very basic) Is there any other basic that i should know ?
Thanks a lot again.
with regards.
Create the efs folder with astro, then use the raw method and copy the .img to your pc.
Sent from my Transformer TF101 using XDA Premium App
How n where to create ef folder using astro? When i click on app
The home page shows
(folder icon)/mnt
(Home icon)(search icon) etc.
Folder-ifs
Asec
Obb
Sdcard
Secure
Usb
On this home page I should crate folder-efs ?
Sent from my GT-I9100 using XDA App
No in sdcard
Sent from my GT-I9100 using XDA Premium App
But sdcard already has efs folder with some files in it . This was created when I used the emulator. But the RAW step had failed as I told u earlier.
Sent from my GT-I9100 using XDA App
nikzDHD said:
VillianRom is nice I've been using VR since release and tried many roms en route and keep coming back to VR for some reason!
Best to do a nandroid via CWM Recovery so if any of your new installs have problems you can always wipe and go back to a working config.
I only use TB to backup app data, I don't like backing up system data as when moving from one rom to another if you restore you may encounter issues so always best to start from scratch to save any hassles.
Click to expand...
Click to collapse
Thanks mate. I'm backing up only custom apps, not custom apps.
Sent from my GT-I9100 using XDA App
Mist that you already had the efs folder. If you already have something there your probably good. If you still want the raw method to work make sure you type su first and hit enter and than exactly copy the cat command (ChromeToPhone is great for this) it should work.
Didn't work out mate .
Sent from my GT-I9100 using XDA App
I'm comfortable with it. Thanks for yo support mate
Sent from my GT-I9100 using XDA App

[Q] Access nandroid backup content (.win files)

hey guys,
I have made a nandroid backup of my nexus 7 (2012) and I need to get access to contents of the data partition without actually applying the nandroid backup to the device. I found this "unyaffs" tool, but it requires .img files if I understood it correctly. However, in my nandroid backup directory, I have a couple of files that end in ".win" or ".win000" etc (along with corresponding md5-files)...these must be image files of some sort I guess, but Windows describes them as "Adobe CMS Extensions" for some reason.
So...anyone knows how I can access this data? Any help appreciated!
cheers
brokaaa

[GUIDE][Lollipop]Dual Boot CM and/or Stock OS

This guide is show you how to install second OS in SDCard, so you can have two complete separate OS (each have their own /system, /data and /cache), this will be useful if you want to try out a new ROM or a new version, like CM or latest Stock build etc. I have pre-build 2 ROMs in this guide. and list the instructions of how to do it in post #2.
The whole method is just an implementation of @SHM (Modding.MyMind) guide that inside the post here, so all the credit goes to him:
http://forum.xda-developers.com/showpost.php?p=62460895&postcount=325
Highlight of the steps:
1. Partition a SDCard (32GB or bigger) to have 3 ext4 partitions after regular FAT32 partition
2. Flash two customized flashable zip in twrp so that:
boot image flashed to /dev/block/mmcblk0p18 (regular boot partition)
system image flashed to /dev/block/mmcblk1p2 (sdcard)
The boot image contains the fstab file, it has been updated to use partitions on sdcard as the /system, /data and /cache for the 2nd OS.
And of course, the flashable zip has updater script changed so that, it will flash they system image to correct partition on SDCard.
Note / Limitation:
1) After boot to 2nd OS on the SDCard, theoretically, while you are in Android OS, everything should work. The speed/performance may differ depends on the SDCard read/write speed.
2) TWRP, except flash the zip to install the customized system image to SDCard, all other function will not work for the 2nd OS, The backup/restore function is still working on the primary OS /system, /data etc.
3) Boot partition (/dev/block/mmcblk0p18), this partition will decide which OS it will boot, and the boot image should corresponded to your OS system partition. So if you flashed above boot image for 2nd OS, it will find /system on SDCard and boot it. And if you flashed (or restore) your primary OS boot image, then it will boot to your primary OS /system.
Things you need before you start:
1. MT2L03 with Lollipop installed, TWRP installed, and have a backup of your primary OS (at least /system, and /boot partitions)
2. An empty SDCard that is 32GB or bigger, strongly recommend class 10 or faster. (16GB will work, then you don't have much external space left)
Steps to install 2nd OS to sdcard:
(Note, I will call the empty SDCard as sdcard#2, and your current sdcard in the phone as sdcard#1.)
1. Make a backup of your current OS using twrp, include at least /system and /boot, to your sdcard#1.
2. Install the PartitionWizard (files location below) on windows, and put the empty SDCard#2 to computer sdcard reader.
3. Launch Partition Wizard, and carefully re-partition your SDCard#2 to following:
(pls refer to xda wiki about the usage: http://forum.xda-developers.com/wiki/SD_card_partitioning )
1st Partition: FAT32 primary size: (Total size minus 15000MB), for example, for 64GB(60000MB) card, choose 45000MB
2nd: ext4 primary size: 1800MB (/system for 2nd OS)
3rd: ext4 primary size: 12500MB (/data for 2nd OS)
4rd: ext4 primary size: rest space, should be great than 200MB (/cache for 2nd OS)
Since partition 2/3/4 total size is 14320MB, thus the 1st partition size is (Total size minus 15000MB)
4. Apply the change, this will take some time (like 20 to 30min).
5. Once sdcard#2 is re-partitioned and formatted, unplug and re-plug sdcard#2 to windows again. Right click the sdcard drive letter, and click "Open" to open the FAT32 partition. ( I found double click the drive letter will give error if the FAT32 is bigger than 32GB, but right click and open works)
Copy two flashable zip (file location below) to the sdcard#2.
6. Reject the sdcard#2, and remove it from windows machine.
7. In Mate2 phone, go to settings, storage, and un-mount your current SDCard#1, after it is unmounted, take out the sdcard#1 and put it to a save place. Do not mess the two sdcards!!
8. Put in the sdcard#2 to the phone, and reboot to TWRP.
9. Install the two zip you download in step 5 from sdcard#2. Reboot.
How to go back to your primary OS:
a. Put in sdcard#1 to the phone, boot into TWRP, restore your /boot partition from the backup you took in above step 1. then reboot.
How to switch to the 2nd OS on the sdcard again:
a. Put in sdcard#2 to the phone, boot into TWRP, flash the "MT2L03_xxx_BootOnly.zip" you downloaded in step 5.
Files to download:
PartitionWizard in above step 2:
http://tinyurl.com/q62m68x
location: under Lollipop/SD_Partition_Tools
FileName: pwfree91.exe
This tools is mentioned in XDA wiki: http://forum.xda-developers.com/wiki/SD_card_partitioning
You can use any tool you know to do the re-partition, above tools is what I used and it works.
Customized flashable in zip in above step 5:
http://tinyurl.com/q62m68x
location: under Lollipop/OS_on_SDCards
FileName:
If you want install B309 as 2nd OS, please download "MT2L03_B309_DBoot_BootOnly.zip" and "MT2L03_B309_DBoot_SystemWithRoot.zip"
If you want install CM12 as 2nd OS, please download "MT2L03_CM12_0820_DBoot_BootOnly.zip" and "MT2L03_CM12_0820_DBoot_SystemWithRoot.zip". (Please note the GApp is already included in the zip)
Attached two screenshot of the partition tool, one for 32GB, one for 64GB. Please note though the pic showing in GB, but when config the size, please use MB to make sure the partition size is accurate and big enough.
//reserved
I am not sure how many people is interested in dual boot, so for now, I have pre-built B309 and CM12 only.
In order to build a customize ROM for installing in SDCard, as detailed in SHM original post, two steps are required:
1) For Mate2, after split the original boot image, and unpack the ramdisk, only need following cmd to update the fstab:
cd ramdisk
sed -i 's/platform\/msm_sdcc.1\/by-name\/system/mmcblk1p2/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/userdata/mmcblk1p3/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/cache/mmcblk1p4/g' fstab.qcom
Then repack it back to boot2.img. Please note the un/repack boot image tool need support DTB section.
2) Then in the updater script of /META-INF/com/google/android/updater-script, install system.img to /dev/block/mmcblk1p2, and still install the new boot2.img to /dev/block/mmcblk0p18.
@SHM, Unfortunately, many tools mentioned in original post, the Aparted tool, and the android binary mkbootimg etc all have problem running under Lollipop, so for now, I am doing all the ROM modification under linux.
Lol. You just had to do it. Lol awesome work. And you picked up on that fast. Thanks Xordos.
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
MikeyLee said:
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
Click to expand...
Click to collapse
I think if huawei mention 64gb probably because they didn't have 128gb to test when they release the phone. 128gb has nothing special compare with 64gb card. But I could be wrong since I don't have 128gb.
For general use, no need to partition 128gb card unless you want to do something like this thread.
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
SHM said:
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
xordos said:
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
Click to expand...
Click to collapse
Yea, it's pretty nice. You can even modify the TWRP recovery for use with making backups and restoring to each Rom specific to their partition. Look at TWRP Unified and check out it's script inside the ramdisk. Modify the script to check some stuff and tell it which fstab to use . This way when you jump back and forth between roms just by the boot.img you flash TWRP will automatically recognize the change upon it booting up and target the partitions properly when you make a backup/restore. Put some thought into all of this and I am sure you could take this thread a bit further.
There are projects out there that are designed for multibooting on android devices but you would need to port one of them.
Sent from my C525c using Tapatalk
Just an update that the AParted app works for Lollipop now. Tested it out on my external sd tonight by resizing my fat partition without losing any of my contents and adding additional partitions with multiple filesystem's such as f2fs and ext4. Quick and effective .
Sent from my Ascend Mate 2 using Tapatalk
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Can't waiting.
MT2-User said:
Can't waiting.
Click to expand...
Click to collapse
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
You run all three (or four including stock one)?
MT2-User said:
You run all three (or four including stock one)?
Click to expand...
Click to collapse
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Could they or some of them share Data?
MT2-User said:
Could they or some of them share Data?
Click to expand...
Click to collapse
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
oh ic
MT2-User said:
oh ic
Click to expand...
Click to collapse
The app implements this feature but I'm working it out if that makes you feel better lol.
Sent from my Ascend Mate 2 using Tapatalk
Damn nice work SHM.. Congrats. And thanks!
Moody66 said:
Damn nice work SHM.. Congrats. And thanks!
Click to expand...
Click to collapse
I have it working %100 now. Its 3:35 am where I am at so time for bed. Sharing apps works as well between roms.
Sent from my Ascend Mate 2 using Tapatalk

Anyway to Clone a Rooted Android Tv Box?

I'm looking for a way to clone a Rooted android box to other android boxes. I want to clone my Tv launcher and apps plus settings.. I have tried a few programs Titanium backup but it seemed to back it up and restore fine but fails to recovery the settings for each app. If there is a faster way of doing this please let me know. The boxes are all different, but have the same processors s905x amlogic. Is there a way to make a IMG then use the usb burning tool to write to each box?
I Used Filezilla to grab files but it also fails to load all the files from the entire box?
Use twrp to create a image then flash that image to the other
I'd agree with Bcoates84, I've been testing out the process of cloning some Samsung tablets by simply restoring TWRP backups and so far everything's worked out pretty well.
It would be a good idea to backup the target ones just in case before trying it since you mentioned they are different boxes.
If you look up TWRP for your specific model(s) there should be some good information to get you heading in the right direction.
So i have done my backup on the box i want to clone, ill call it A-box. I got a Folder called TWRP/Backups With a few files
Boot.emmc.win
data.ext4.win000
data.ext4.win001
data.info
recovery.log
system.ext4.win
system.info
I plugged the stick into the box i want to clone, ill call it b-box went to restore this time and it fails to see the backup?
So I copied the TWRP folder with it's contents this time to my desktop and deleted the TWRP folder from the USB stick. Decided to do a Backup on b-box even know i didn't need the backup just wanted the folder structure to compare the two which i then got.
Boot.emmc.win
data.ext4.win
data.info
recovery.log
system.ext4.win
system.info
So I removed all the FILES from the usb only leaving the folder structure TWRP/BACKUP/SERIALNUMBERS I'm guessing? Also the p212-userdebug_6.0.1 folder. Then copied my files from A-box into the file structure and went to do a restore and it sees the image! Restore went smooth, went to reboot and it's stuck on android splash screen for 30mins now so guessing it's bricked. I can flash stock img back thats not a issue. Just trying to figure out how to clone this damn thing lol.
Is there anyway to simply make a Img so i can flash it via the amlogic usb burning tool. I saw this guide https://forum.xda-developers.com/showthread.php?t=2746044 which i can extract the system.ext4 seeing all the system files, fast_preinstall, addon.d, app, bin, fonts, usr ect... But i don't see boot.emmc.win anywhere? I'm assuming this methods for phones only?

How to make a complete copy of my android?

I have 45 android devices lenovo tab2 a10-30
I am configuring 1 tablet with all the necessary applications and with root installed, I want to create a complete copy of the tablet to install it in all the other tablet, how can I do it?
newmesis said:
I have 45 android devices lenovo tab2 a10-30
I am configuring 1 tablet with all the necessary applications and with root installed, I want to create a complete copy of the tablet to install it in all the other tablet, how can I do it?
Click to expand...
Click to collapse
Install a custom recovery like TWRP on all devices. Make a backup. Copy it to your computer and then move it into the TWRP directory. (/sdcard/TWRP/deviceID/buildnumber/) Boot TWRP and restore the backup.
This can only be done if all models are the same and if twrp or cwm is available for the device.
So I've been doing it since twrp I create a backup by selecting all the items, then I save it in the sd card. When going to the other device (all the devices are the same) I select to recover from the sd but it does not read the folder it is only read from the device that I know.
newmesis said:
So I've been doing it since twrp I create a backup by selecting all the items, then I save it in the sd card. When going to the other device (all the devices are the same) I select to recover from the sd but it does not read the folder it is only read from the device that I know.
Click to expand...
Click to collapse
Because of the device ID part. When you make the backup, don't grab the whole TWRP folder.
It should be something like /sdcard/TWRP/(device id)/(build number)
You want to navigate to the build number folder and copy it. Then you copy it into the same place on the other device. The only thing different is the device id part of the path. If you copy it there it will read it.

Categories

Resources