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
Related
CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?
NOTE: I have searched and reviewed the existing threads on items with similar wording. Several on how to recover corrupted files within the backup etc.. Although the questions and issues are similar none describe the issue that I am experiencing.
Samsung Galaxy Note
Rooted on AOSP xXx FJ,(Flappjaxxx) / FJ Mod of ICS UCLF6
Currently on CWM Recovery 5.8.4.3
Situation:
No prior issues experience with nandroid backup, had 2 other backups plus the one I'm referring to (one of AOSP xXx and FJ Modded)
Performed a nandroid backup to try out CM09 from FJ AOSP. All went well... including the CM09 install and apps.
Missed the S-pen functionality and wanted to flip back to FJ Modded ROM.
Attempted to restore the most recent backup... Failed. Booted into CM09 and went to Root Explorer and looked into the backup file. I noticed that the file has a lot of what appears to be random ASCII characters for file names etc... (indicated to me that this file was corrupted).
Since I had other backups, I went to one of the older ones and restored.
Problem: this corrupted backup is taking up about 1.9 GB and I want to delete but it will not allow me. Looked at permissions and it has RW
Question: how the heck do I delete this thing without having to take my SD card out and formatting the sucker?
Thanks in advance
You should be able to plug in your phone to your computer via USB and open folder to view files on the /sdcard. Make sure USB connection is set to "USB Mass Storage" option when connected. Once you opened the folder to view files, you can navigate to the clockworkmod folder, open, and find the backups within that folder and delete that way...
Sent from my MB865 using xda's premium carrier pigeon service
Did you try to delete it in recovery (sorry if there is no such option, never looked for it...) or in root explorer? You could always get a terminal like https://play.google.com/store/apps/details?id=jackpal.androidterm and do like this:
su (if you're rooted)
cd /sdcard/clockworkmod/backup
rm -r 2012-07-12.13.37
Same commands should work in adb as well
Try. Android Commander.
jje
Sent from my GT-I9300 using xda premium
I think that plugging the USB charger into your computer and manually deleting it should do the trick :fingers-crossed:
OK...
Thanks guys for your responses...
- did try connecting to a PC in mass storage mode and tried to delete... did not work
- use Root Explorer to do a delete as well... did not work
- looked to see if there was a delete option in recovery (first thing I looked for) did not find it
I'll try the other options and see where that goes.
JohnnyQ1964 said:
Thanks guys for your responses...
- did try connecting to a PC in mass storage mode and tried to delete... did not work
- use Root Explorer to do a delete as well... did not work
- looked to see if there was a delete option in recovery (first thing I looked for) did not find it
I'll try the other options and see where that goes.
Click to expand...
Click to collapse
If you download clockwork mod (rom manager) you can delete it in the android application in manage and restore backups.
Empty recycle bin on PC sometimes helps when deleted stuff sticks, make sure do this when plugged in ofc
If you're using Windows, run chkdsk ("Scan this drive for errors" in drive's properties) when connected as a mass storage device.
That should help.
If it won't, the guaranteed method is to copy the files you need somewhere else, format the card and put those files back.
to clairfy, you were able to locate the back up files in the folder "clockwork mod-backup" but then it would not delete when you tried?"
Thanks again for all your input.
PC crapped out this past weekend... new hdd installed and re-building with Windows 7 pro-64 (hmmm... maybe I should dual boot to Ubuntu), will need to reinstall some of the linux/android tools.
@frdd... already had terminal installed tried the commands but no luck... it reports back I'm missing files and i get a lot of errors. I guess I'm gonna have to learn Linux/Android
@icomrade... I've got the purchase ver of ROM Manager and haven't fully gone down that rabbit hole but will investigate
@NeverGone\RU... will leave that as a last resort as i've got a 32GB SD card (sucks up time)
@mankows5... yes did find all the directories and files as it should be... just can't delete that 1 backup
Yeah, try Rom manager. Manage and Restore Backups>Select the one you want to delete, then delete it.
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?
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.
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Can you tell me how you rooted the SM-T380 I tried rooting it using the 2018 guide but it's not working and I tried patching the Boot.img ( from Sammobile) with magisk but when i open the magisk app it says Installed: N\A Ramdisk: Yes A\B & Sars: no.
Or can you share the stock boot animation from the T830 since I'm not a big fan of the Marvel's avengers/iron man boot animation.
i just installed this and it works great, total life saver. i was about to toss my tablet in the trash
@xfk110, out of sheer desperation I want to try this. I understand why and how it should work, and I'm downloading your backup now. But a couple of questions first if I may:
1. Will Titanium Backup work with this rooted firmware? That's most important and my biggest frustration, after trying every other way described in the T380 threads, with both Oreo and Pie, TWRP or patched boot image. Nothing has worked well enough for me.
. . . My Tab A arrived with XAR 3CTH4 which meant I could downgrade it to the last Oreo update 3BSD1, and I've been back and forth between versions trying to make something work with TiBu. I'm a diehard Titanium user. I have tried 4-5 different root methods and every effort has failed somehow, if only that TiBu would not run. (Most efforts were even worse failures though.)
2. How important is the firmware version (and CSC) on my Tab A? . . . My T380 came with XAR firmware . . . Should I match the 3CSL2 version of your backup exactly, i.e., should I flash 3CSL2 first? Or if I'm on 3CSI5, would that be close enough? (I ask because I'm getting really really tired of changing firmware on this Tab lol, and I already have 3CSI5 downloaded and unpacked.)
3. You mention "all of those files" -- for a TWRP restore I would expect to select ONE FOLDER to restore from, so I'm a little confused about what you mean by "all of those files". Wouldn't it necessary to copy all of those files to one new folder under TWRP/BACKUPS/my-serial-number? Maybe named 2022-01-18, something short and simple.
I do truly truly hope this will work for me. Thanks in advance for however much you can help me understand everything I need to do to get a solid working root.
Just wanted to thank you for providing this guide. It worked first time for me and I'm very happy with the improved speed and space.
Thank you!
zfk110 said:
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Hello could you please make a video, the truth is that I do not understand anything.
Can this process be done using internal storage?
banistersmind said:
Can this process be done using internal storage?
Click to expand...
Click to collapse
No, unfortunately, this process can only be completed with a micro sd card and another computer with an sd card reader. the sd card must be at least 8gb to work.
Still works great as of 3rd May, 2023! Thanks mate.
@banistersmind @mehmeh.re I just did it without an SD card using internal storage. Works fine.