So I'm used to doing backup of devices in TWRP but it seems that nandroid is the way you do it with these. I downloaded and ran a backup to SD Card. I chose the option for TWRP backup, will that allow me to do a restore of the image I created here from recovery or would i need to install TWRP recovery to recover? If I chose the backup type Clockworkmod would that be restoreable from stock recovery? The directory it created is only 1.6GB w/o compression which doesn't seem right to me.
I did read the idiots guide to root first BTW.
Thanks guys.
Tried to do a recovery restore using optin recover system from backup but I have no idea the path it is looking for, it doesn't say just says no system.img so ignore. So it appears nandroid creates a system.ext4.tar so I suppose I could decompress this and see if there is a system.img file that the recovery is looking for and put it in the root of the sdcard if recovery is actually looking /external_sd.
Anyone have any input?
Dave
Related
I have a couple questions about CWM and backups:
Is there a difference between flashing update.zip and installing a zip from the sdcard in CWM?
Also, let's say I make a change to boot.img and system.img and something goes wrong. Instead of flashing the backups of those two images from my computer to my phone using fastboot, can I just place them both in a zip file and install it from CWM? Would I need to include any other files?
How come a nandroid backup makes a system.ext4.tar and not a system.img? How do I turn that into a system.img?
How come I need unyaffs to read cache, data, and system.img files? I thought the filesystem was ext4 and not YAFFS?
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
marko! said:
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
So I found some links about the update-script and I'll be reading those shortly, but after skimming them I didn't see any mention of the binary. Is the binary an executable version of the same script or something else? Any links?
So what your saying is I could just skip the update.zip stuff, extract the images from the zip, and use advanced restore to flash each image? Obviously more work but it's good to know if these two processes are equivalent.
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
And also the last question about ext4 and YAFFS is still there. Thanks.
Most of those I'm really not sure. The update binary is the same for every zip. Just grab it from a rom or theme
I would go with the cwm zips. Way easier once you get them working.
sent from my Atrix via XDA premium
gsingh2011 said:
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
Click to expand...
Click to collapse
I was just looking at this too. My old recoveries from before atrix4.1 was released were all .img files and the post atrix4.1 backups are .ext3.tar (except for boot.img and recovery.img). I'm on a stock deodexed GB ROM, so I don't have any ext4 partitions. I think he changed this with the newest update so CWM can recognize the ext type and mount them appropriately.
This post should hopefully clarify a bit more than I can. I'm relatively new to all this so I'm still learning different aspects of modding. I'm guessing you have some ext4's because you're running one of the newer custom ROM's?
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?
Unfortunatelly I haven't found any support for this watch (system img, or saved full Twrp backup, factory img...) to repair the softbrick. I have found the ota.zip file, but I can't use it because of the system7 error. I have a Twrp on my watch, but I can't find any way to restart my wach. I'm so sad because I can't use my watch.
me too. I stuck with the smaller model because I thought that it looked much better with my Nemesis leather cuff band than the larger model. But no one seems to have the original system image or a recovery I could use for it since I bricked mine. I've gone back to my Misfit Shine, which is not even close to being a smartwatch
Take a look to my thread, I uploaded a twrp backup, but for WI501Q (system+boot)
TWRP BACKUP
https://www.dropbox.com/s/6d51x7mkub6e5ag/TWRP-2016-03-08.zip?dl=0
matze19999 said:
Take a look to my thread, I uploaded a twrp backup (system+boot)
---------- Post added at 21:25 ---------- Previous post was at 21:16 ----------
TWRP BACKUP
https://www.dropbox.com/s/2dcjdeen58kz0qy/asus2.zip?dl=0
Click to expand...
Click to collapse
I downloaded the file and unzipped it. I booted to twrp recovery and used ADB PUSH to send the files to /sdcard/ on the watch. I then used Install in twrp to install the recovery and boot img files (there is no option in twrp to install system.img). After all of this I still cannot boot the watch, it goes to CSC Fastboot.
Am I doing something wrong?
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
matze19999 said:
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
Click to expand...
Click to collapse
Thank you for all the steps.
I tried the steps and I noticed that when I selected the restore option only BOOT was able to restore. So I looked at the backup that twrp made and the filenames were actually boot.emmc.win, recovery.emmc.win, and system.emmc.win. So I took your three files and renamed the img extensions to emmc.win extensions and moved them directly to the backup folder that twrp created. This allowed me to be able to select all three options for restore (boot, recovery and system). The restore completed without errors. However when I reboot the watch it continues to quickly show "Recovery Mode!" and go to "CSC Fastboot Mode!"
Am I still doing this wrong?
download the backup file again and test it
matze19999 said:
download the backup file again and test it
Click to expand...
Click to collapse
I downloaded it again using the same method I described earlier, but I get the same result.
I have the wren device WI502Q.
Backup file is only for sparrow
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Welp i'll just buy a new watch. My CAVS just won!!!! Wooooo!!!!!!
cland216 said:
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Click to expand...
Click to collapse
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
matze19999 said:
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
Click to expand...
Click to collapse
I get an Error 7:
"this device has omni_wren wren:6.0.1/MHC19J"
I updated the watch to MM before I bricked it. Where can I find MHC19J image?
I have a stock Wren on mm, you still need a backup?
couchlock said:
I have a stock Wren on mm, you still need a backup?
Click to expand...
Click to collapse
I am thinking of rooting and would really appreciate a backup just in case. I really would appreciate it and I know others would appreciate it as well.
I'll be off in a couple days. I'll post a link from my mega account when I get it.
https://forum.xda-developers.com/zenwatch-2/general/wi502q-how-unbricked-watch-twrp-backup-t3521916
Unbrick guide I made.
So what do you need a back up of and how do I make the backup. Sorry so long but I finally have time. And a PC again
Hello,
does any of you know how to access "storage/emulated/TWRP/backups/" path via TWRP recovery file manager? I made backup with nandroid and now i want to delete it, but I can't find this path. Nandroid file manager does nothing when I press 'trash icon'
I'm able to see this backup via fx file root manager, but when I wan't to delete it returns error 'this operation could not be completed'
Hi,
I stuck with this problem too.
Can't find the way to delete the backup yet. It eats up my storage for 16gb.
Hope anyone can help.
Thank you in advance,
Ed
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