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?
Related
just rooted my evo3d, everything went great and i even git CWM to install the first time correctly. heres where i think i went wrong-
i downloaded rom manager and i attempted to use it and it worked great. to me it seemed like it worked because i was able to choose my phone and even flashed the CWM over the original one i had. i made a backup of my stock rom and tried a rom from the dev forum, didnt like it and tried to switch back and got the MD5 mismatch error when i tried to restore my stock rom. now, i thought i would try to flash the original CWM which was blue over the CWM(orange) and then attempted to get the rom to restore. that was also a fail. what can i do? i read that installing busy box could effect this? any help would be appreciated.
sucks but it happens download the RUU from here and reroot if you need too
FIXING MD5 MISMATCH
adb shell
# cd /sdcard/clockworkmod/backup/name_of_backup
# rm nandroid.md5
# md5sum *img > nandroid.md5
gaaah i dont have ADB installed on my mac. is there not a simpler way? anyway to fix this?! i dont think i need to reroot honestly..
Nope sorry.
I may have found a way to fix the MD5 issue.
Well, it worked for mine.
I saved a backup of the stock ROM before I installed the needle kernel.
it was named 2011-08-01-23.53.47
The I saved another backup of the ROM with the needle kernel/
it was named 2011-08-02-19.06.28 w/ needlekernel
What happened was that on the sd card the backup folder was named 2011-08-02-19.06.28 w/ then inside that folder was another folder named needlekernel . And that folder contained the backup files.
It seems that putting the space in the name caused it to create another folder within the backup folder instead of just having the backup files in there. I kept getting the MD5 mismatch when I tried to restore that backup.
So I took the files out of the needlekernel folder and put them in the 2011-08-02-19.06.28 w/ folder. I then deleted the needlekernel folder. The last thing was to take the (space)w/ off of the end of the folder name so it was just as the program named it to begin with.. 2011-08-02-19.06.28
After doing that I was able to restore the backup through ROM Manager. So apparently it's best not to add anything to the backup name when saving it.
One other thing I'll mention. When I restored the backup with the needle kernel in it it put the stock kernel back in the ROM.
Hope this helps anyone with the MD5 issue.
I recently tried a new ROM and made a Rom Manager recovery restore file prior to changing. Things didn't work out as well as I had hoped and when attempting to restore, it fails at the checking MD5 sum process.
Any way to work around this? I really would like to restore to the previous ROM without starting over.
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
sandiegopaneraiguy said:
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
Click to expand...
Click to collapse
depending on the type of file format used to backup, the restoring could be done manually but a changed md5sum generally means the files are not the same as the original. this could result in corruption and generally it isnt recommended to restore corrupted files as you run the risk of nothing working.
if you're still wanting to proceeding with attempting to restore files which are different than the original and could be corrupted, off the top of my head, you can probably dd the .img files back and untar the .tar files back.
i would suggest starting over and perhaps copying the backup files over to your desktop instead of only leaving on the sdard. this should help ensure at least one of the copies maintains their integrity.
hope that helps!
You can boot into recovery, and run nandroid via adb shell command line, no md5 checksum file needed. Now if the image is bad, you of course get bad results, but if the checksum is just hosed for some reason, it will work fine.
Put the .win files for the partitions you want to restore in /sdacrd
then issue the command "tar xvpf /sdcard/data.win" or "tar xvpf /sdcard/system.win" from the adb shell while in /data or /system respectively. .win files are what TWRP creates for backups.
I had this happen with TWRP 1.01 or 1.02 once on a good backup that passed the checksum tests when I backed it up.
I was testing the reliability of the TWRP package's nandroid and first one failed.
Once I moved to the newer version, I've not had that issue.
Hey!
Intro:
Bought a new tablet for my granny since she seemed to like the prestigio a lot.
I haven't had any luck selling this junk.
My idea is to make it into a GPS for my Ford Focus.
I want to edit the lessen the boot time (of 1 minute), to change boot logos, to remove ads, to do a ton of stuff.
I'm a C/Cpp developer, I'm still an amateur in Cpp and I've recently started a course on C#.
Problem:
I rooted the tablet and I gained access to the root directory.
I tried editing some system files and added a reboot command at the end of init_charging, so it would boot when I connect it.
It turns out those files get replaced with fresh copies after each restart, so that did nothing.
I tried changing permissions in twelve different ways following youtube vids.
Nothing worked.
I found 2 files - "BOOT" and "bootimg" both without a file type and with 0kb size (using Solid Explorer).
I figured these are the images or archives that the tablet extracts on every boot hance the long boot times.
After buying and downloading an app for putting the tablet in "insecure mode", I could pull root files.
Using ADB, PULLed a file called "bootimg" that had no file type.
I couldn't pull "BOOT" as it told me "wrong argument".
I extracted "bootimg" with bootimg.exe program, NOTE that the bootimg file was 3GB and the tablet somehow had a total of 1GB root memory, 4GB sd memory.
The extracted files were only the system files and it was about ~5mb.
Only bootimg.exe worked for extracting the IMG for some reason, and I have no idea why it extracted so little.
I edited them trying with the _charging again, packed the bootimg, replaced the one on the tablet.
So now instead of 3GB bootimg file, the tablet had a 4mb bootimg file.
Now.. I'm not kidding when I say that the tablet managed to restore the whole 3GB bootimg file that I replaced with a new one.
If it restores the alleged archive it uses to restore everything else, then... what now?
On top of all, it has a "reset" button on the back, which I'm guessing is a bridge to some extra ROM backup.
I have no idea why I can't get the BOOT file or what's in it. I mean, the bootimg file should be the boot.img that is known on other android operating systems.
I can get a ROM for this tablet's system, but it won't be super easy, nor does it make sense at this point.
Alternatives?:
I'm starting to lose hope, modifying the OS seems impossible if it can reset a whole 3GB file that was deleted.
If there's a more mod-friendly tablet out there, can you recommend it to me?
Very simply, how do I browse and extract the contents of a TWRP Nandroid backup on my Windows PC?
I am trying to browse a TWRP backup but I have a feeling I need to do a bit more fussing around. The backup is split into data.ext4.win000 through data.ext4.win007 and each of the parts has an accompanying .md5 with the same naming structure (ie. data.ext4.win000 and data.ext4.win000.md5.) There's also a data.info file as well.
The system backup is the exact same as described above for the data, except it's only 2 parts (system.ext4.win000 and system.ext4.win001, with the accompanying md5 files and the info file.)
Can someone provide a bit of guidance? I'm using a Windows 7 Home Premium machine.
kwest12 said:
Very simply, how do I browse and extract the contents of a TWRP Nandroid backup on my Windows PC?
I am trying to browse a TWRP backup but I have a feeling I need to do a bit more fussing around. The backup is split into data.ext4.win000 through data.ext4.win007 and each of the parts has an accompanying .md5 with the same naming structure (ie. data.ext4.win000 and data.ext4.win000.md5.) There's also a data.info file as well.
The system backup is the exact same as described above for the data, except it's only 2 parts (system.ext4.win000 and system.ext4.win001, with the accompanying md5 files and the info file.)
Can someone provide a bit of guidance? I'm using a Windows 7 Home Premium machine.
Click to expand...
Click to collapse
Simply rename the file to data.ext4.tar and use winrar to extract it.
I'm revamping this thread because I'm...desperate!
I have a nandroid backup (TWRP 2.8.7.0) and I would like to browse it on my PC. I'm focusing on files with structure data.ext4.win000x (where x goes from 0 to 2).
I'm able to open with 7-zip (should be equivalent to winrar) every individual file but size is faulty: every file is nearly 1.5 Gb while the content of the zipped file that I see it's around 50 kb. If I concatenate the files with the command copy /b data.ext4.win000? outputfile regardless the extension I give to "outputfile" I'm no longer able to open it with 7-zip.
Any suggestion/hint please ????
Not finding entire folders/files while browsing backup
I find the same thing regardless of the mechanism I am using to browse the backup. I am looking in /data/data for my own apps' data. Here is what I have tried so far:
1. Nandroid Manager app
2. TWRP Explorer app
3. ZArchive app
4. In a terminal, cat data.ext4.win??? | tar -tv > less (and then searching for my apps' package names
I was looking inside my nightly full backup to extract and recover some files I accidentally deleted. Cannot even find folders for the package names (except for 1 app). However, when I do a full restore from the same backup inside of TWRP Recovery, the missing files are indeed restored. So I know they are in the backup.
Why can I not find them and get at them any way else? I must be missing something simple.
Thanks
BTW - in the recovery.log file in the backup folder, I see the folders/files in question being "added". Very odd.
BTW2 - at least with regards Nandroid Manager app, I noticed that I was seeing some files I know I had removed from my apps some time ago. How could that be? I decided to clear data/cache for Nandroid manager and try again. It took much longer to process the backup for exploring. But now at least that app seems to be doing the right thing and I can see all folders/files.
Hope this is in the right place ..
I have a couple of Tanix TX3 mini TV boxes that I would like be able to backup and recover across devices.
I have put S905-TWRP3-VIT.zip onto a micro SD card and can load TWRP from the boot recovery menu.
I can then backup ROM, system and data partitions to a USB flash drive.
if I now go into the restore menu I can see the backup file.
My problem is that if I now start TWRP from a different device I can no longer see the backup file.
If I create a very small backup, I can see the new backup but not the old one.
If I reboot normally, I can see both backup files within the same directory via any file explorer app.
Obviously, this stops me from being able to restore the system to the target device.
I can't see anything obviously wrong, can someone tell me where I am going wrong please?
Many thanks
Baldplumber said:
Hope this is in the right place ..
I have a couple of Tanix TX3 mini TV boxes that I would like be able to backup and recover across devices.
I have put S905-TWRP3-VIT.zip onto a micro SD card and can load TWRP from the boot recovery menu.
I can then backup ROM, system and data partitions to a USB flash drive.
if I now go into the restore menu I can see the backup file.
My problem is that if I now start TWRP from a different device I can no longer see the backup file.
If I create a very small backup, I can see the new backup but not the old one.
If I reboot normally, I can see both backup files within the same directory via any file explorer app.
Obviously, this stops me from being able to restore the system to the target device.
I can't see anything obviously wrong, can someone tell me where I am going wrong please?
Many thanks
Click to expand...
Click to collapse
Solved