(sdcard/nandroid/openrecovery)
recovery boot
nandroid -restore- xtmiuioptimized-restore all
boot not backed up
bpsw not backed up
lbl not backed up
logo not backed up
devtree not backed up
system not backed up
data not backed up
cache not backed up
cust not backed up
cdrom not backed up
ext2 not backed up
restoring finished successfully
done
Why does this happen ... thanks
I'm using V2froyoXToptimized update v2 v3 update
sorry translation
did you unrar the file and then place it in sdcard/nandroid/openrecovery or just place the rar. you must first unrar khals rom down to just the folder with boot.img boot.md5 system.img and system.md5 in it then place the folder with those in the sdcard/nandroid/openrecovery folder
the procedure that you're saying I have performed and the result is that in post....
so inside the Xtmiuioptimized folder there is 4 items? boot.img boot.md5 system.img and system.md5? and in open recovery when you select xtmiuioptimized in the restore menu it should say only boot and system in the restore options.
yes..the files are 4
restore option for xtmiuioptimized
go back
restore all
restore selected
The directory structure on the sdcard should be...
Code:
/sdcard
/nandroid
/openrecovery
/xtmiuioptimized
boot.img
boot.md5
system.img
system.md5
if your folders match these I would try coping them from your pc again.
Çheck restore all and if that doesn't work your file might be corrupt so try tranfering the folder again.
is the path and just... 3rdstring...Thank you
easye420.. I had already tried I'll try again tomorrow...Thank you
did you try checking the boxs next to system and boot in the partitions sections of the restore menu in open recovery. try that and if that doesnt work and you say you already tried replacing the folder and that didnt work id say your download must have been corrupt id try to redownload it and try again. this happened to me before and if that doesnt work try try making a back up of your current phone and restoring that back up and see if that works. and if that doesnt work try reistalling Open recovery thru the system recovery app and try again. lot of trial and error unless anyone else has better ideas
The ROMs we're flashing only update boot and system. When nandroid restore says "not backed up" it just means it's skipping restore of a partition because there isn't a backup to restore. It's harmless.
Mioze7Ae said:
The ROMs we're flashing only update boot and system. When nandroid restore says "not backed up" it just means it's skipping restore of a partition because there isn't a backup to restore. It's harmless.
Click to expand...
Click to collapse
if you reed his first post its says all partitions are not back up boot and system included. so its like theres nothing in the folder to restore like restoring a empty folder.
exact is just so happens to me
solved
extract rar folder then take the (sub xtmiuioptimized folder) and put the SD card installed .... ok .......sorry
Related
Hey all,
So I did a nandroid backup yesterday as I normally do, reboot into CWM>backup and restore>backup to external, and when it was finished I rebooted and went into the clockwork folder on my external SD to make sure it worked. I found out that the actual backup file was made but no blob folder was created.
I first discovered this last week when I went to restore and an error came back saying there was an MD5 error. Before any of this occurred I deleted the blob folder to free up space and after deleting it, I did a nandroid thinking that another blob folder would be created in the process of the nandroid.
This is probably a small issue thats easy to fix, but I am unaware of the fix. Can anyone assist me please?
My Mum's managed to mess up her tablet (seems to have reset it but not factory reset, as it's still encrypted, password protected, etc, just all her apps and even Apex Launcher have vanished) and the only recent backup I can find is a TWRP backup made with Online Nandroid Backup.
TWRP doesn't seem to recognise the files however, as it doesn't list any backups. I looked at the log and see that when pointed to the internal storage (which it can't mount as it's encrypted), it looks in /data/media/TWRP/ and I've recreated that structure on the microSD (where the backups are), giving me /data/media/TWRP/BACKUPS/0000000000000000/2015-04-05--07-14-50/
In that folder I have:
boot.emmc.win
cache.ext4.win
data.ext4.win
recovery.emmc.win
system.ext4.win
and .md5 files for each of those.
The .win files I can open with 7-zip, to show the files without that extension (e.g. data.ext4).
If anyone could help me restore this backup I (and more importantly my Mum) would be very grateful!
I tried installing Nandroid Manager and ES File Explorer and both failed, so something's clearly messed up. SU 2.46 is installed and I checked root with Root Checker and updated Busybox.
OK, I found a good tip to make a new backup (I just ticked boot to make it quick) and check where TWRP puts it. It turned out to be /micro_sd/TWRP/BACKUPS/Lenovo_A5500-HV/
So I moved my existing backup folder there, formatted /data to remove the encryption and then I was able to restore the backup. Now the tablet's stuck in a boot loop though and I can't even boot into recovery, so I'll have to start from scratch and then try and restore just /system and /data.
hello guys,
i have a problem with restoring my nandroid backup.
so the digitzer of my s3 mini is broken and does not work partially. e.g. i cant enter my pin to unlock screen lock and i cant use twrp. so i used cwm (i guess it was 6.0.2.8.) to backup everything to my ext sd card. i dont know exactly if the backup was successfull but i cant remember any error messages and my backup is about 3,5gb big and there r following files:
boot.img
cache.ext4.tar
cache.ext4.tar.a
data.ext4.tar
data.ext4.tar.a
data.ext4.tar.b
data.ext4.tar.c
data.ext4.tar.d
nandroid.md5
recovery.img
system.ext4.tar
system.ext4.tar.a
now i wanted to restore only data on a new device: moto g peregrine via cwm. i installed cm12.1 on my moto, the backup comes from cm12.1 too.
error: md5 checksum mismatch -> i cutted nandroid.md5 and created an empty file named nandroid.md5 and copied it into the backup folder. then cwm restored. well... it says it was restored. but when i start android no data is restored.
so i tried to restore it via tatanium backup. this app finds my backup, but only system apps r listed. no user apps. (i just tried it again, no apps at all)
then i tried to open/browse the tar archives with a shell extension in windows. they are empty.
then i wanted to extract them with appextractor but it doesnt find a backup to extract.
then i tried nandroid manager. it finds the backup, it says, its 3,44gb big. when i browse the data.ext4.tar its empty. then i click on restore nandroid backup. it boots into recovery but then it says:
sd card marker not found
.....
E: unknown volume for path [/mnt/sdcard1/clockworkmod/backup/2012-01-01.00.00.35]
cant mount backup path
im using cwm 6.0.4.8
so can sum1 plz help how to restore it? or is it broken? is everything gone?
and another question: twrp has adb sideload-support. i could make a twrp backup via the openrecovery adb script but my internal storage has not enough space. if i could tell twrp to backup on the ext sd card perhaps it works
greetz
daemonicvs said:
hello guys,
i have a problem with restoring my nandroid backup.
so the digitzer of my s3 mini is broken and does not work partially. e.g. i cant enter my pin to unlock screen lock and i cant use twrp. so i used cwm (i guess it was 6.0.2.8.) to backup everything to my ext sd card. i dont know exactly if the backup was successfull but i cant remember any error messages and my backup is about 3,5gb big and there r following files:
boot.img
cache.ext4.tar
cache.ext4.tar.a
data.ext4.tar
data.ext4.tar.a
data.ext4.tar.b
data.ext4.tar.c
data.ext4.tar.d
nandroid.md5
recovery.img
system.ext4.tar
system.ext4.tar.a
now i wanted to restore only data on a new device: moto g peregrine via cwm. i installed cm12.1 on my moto, the backup comes from cm12.1 too.
error: md5 checksum mismatch -> i cutted nandroid.md5 and created an empty file named nandroid.md5 and copied it into the backup folder. then cwm restored. well... it says it was restored. but when i start android no data is restored.
so i tried to restore it via tatanium backup. this app finds my backup, but only system apps r listed. no user apps. (i just tried it again, no apps at all)
then i tried to open/browse the tar archives with a shell extension in windows. they are empty.
then i wanted to extract them with appextractor but it doesnt find a backup to extract.
then i tried nandroid manager. it finds the backup, it says, its 3,44gb big. when i browse the data.ext4.tar its empty. then i click on restore nandroid backup. it boots into recovery but then it says:
sd card marker not found
.....
E: unknown volume for path [/mnt/sdcard1/clockworkmod/backup/2012-01-01.00.00.35]
cant mount backup path
im using cwm 6.0.4.8
so can sum1 plz help how to restore it? or is it broken? is everything gone?
and another question: twrp has adb sideload-support. i could make a twrp backup via the openrecovery adb script but my internal storage has not enough space. if i could tell twrp to backup on the ext sd card perhaps it works
greetz
Click to expand...
Click to collapse
You can connect a USB mouse and keyboard to navigate and select whatever you need to select or do in CWM or TWRP, it will work with either recovery.
As for transferring user installed apps and their data, you can try backing them up to your google account and then restoring them from google on the new device. Or use the USB mouse/keyboard along with ES File Explorer to go to your /data/app folder and create copies of your installed apps, the backups will be in your backup/app folder on internal, copy them to PC then go your Android folder on the device and copy the app data for those apps to PC, then transfer the app copies to the internal on the new device and install them or use adb to sideload each of those apk files to the new device, then transfer the copied app data for those apps to the Android folder on the new device, then boot to recovery and wipe only cache, do not factory reset in recovery then reboot.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
hi,
You can connect a USB mouse and keyboard to navigate and select whatever you need to select or do in CWM or TWRP, it will work with either recovery.
Click to expand...
Click to collapse
but for this i need a special otg adapter cause the s3 mini doesnt support otg originally. and dont i need to install an app or something on my device and confirm a message on my screen? like u wanna do an adb backup. havent tried it yet. i will do i i guess.
As for transferring user installed apps and their data, you can try backing them up to your google account and then restoring them from google on the new device. Or use the USB mouse/keyboard along with ES File Explorer to go to your /data/app folder and create copies of your installed apps, the backups will be in your backup/app folder on internal, copy them to PC then go your Android folder on the device and copy the app data for those apps to PC, then transfer the app copies to the internal on the new device and install them or use adb to sideload each of those apk files to the new device, then transfer the copied app data for those apps to the Android folder on the new device, then boot to recovery and wipe only cache, do not factory reset in recovery then reboot.
Click to expand...
Click to collapse
this presumes that i can unlock my lockscreen. doesnt it?
i will try to backup my data with cwm again. perhaps the backup is corrupted. and i will try to do an adb backup and control the phone via keyboard and mouse if i can unlock the screen and/or confirm a popup message.
can anyone say if i can make a twrp backup to my ext sd oder pc via adb shell? i know the command "twrp backup <options> <foldername>" but can i change the path where the backup will be stored?
thx for your reply
daemonicvs said:
hi,
but for this i need a special otg adapter cause the s3 mini doesnt support otg originally. and dont i need to install an app or something on my device and confirm a message on my screen? like u wanna do an adb backup. havent tried it yet. i will do i i guess.
this presumes that i can unlock my lockscreen. doesnt it?
i will try to backup my data with cwm again. perhaps the backup is corrupted. and i will try to do an adb backup and control the phone via keyboard and mouse if i can unlock the screen and/or confirm a popup message.
can anyone say if i can make a twrp backup to my ext sd oder pc via adb shell? i know the command "twrp backup " but can i change the path where the backup will be stored?
thx for your reply
Click to expand...
Click to collapse
You can use adb to remove lockscreen. There's a couple different ways using adb, research them.
As for OTG capability, you can try adb side loading an app called Stickmount by Chainfire if you can find a way to enable it after installing it.
Sent from my SCH-I535 using Tapatalk
ok thx.
i wanna use the openrecovery script with "adb shell twrp backup DO" but it says not enough space. so i want to store the backup on my ext sd. but how can i change the backup location to my ext sd? i only can specify a foldername within the backup path. but noch path :/
like here
http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html
hope sum1 can help me
I am trying to restore my twrp backup(around 7 gb) but it is always failing around 55% giving error
I:extractTarFork() process ended with ERROR=255
When trying to restore another twrp backup(around 1.5 gb) it do just fine.
I have googled a lot but had no luck.
I have attached recovery log in the post.
Any help will be appreciated.:good:
Try fully wiping first, then reboot recovery and restore nandroid.
hossman said:
Try fully wiping first, then reboot recovery and restore nandroid.
Click to expand...
Click to collapse
Already tried.Still give same error.
I'm pretty certain that error is due to lack of space.
If wiping doesn't resolve you may be out of luck.
hossman said:
I'm pretty certain that error is due to lack of space.
If wiping doesn't resolve you may be out of luck.
Click to expand...
Click to collapse
Lack of space in data partition?
But how this is possible? I have taken a twrp backup of a running version of my phone, so how space can be insufficient?
P.S.
I was able to restore this twrp backup only once after that it started giving me this error.
What is this error 255 actually about ?
SuperSaket said:
Lack of space in data partition?
But how this is possible? I have taken a twrp backup of a running version of my phone, so how space can be insufficient?
P.S.
I was able to restore this twrp backup only once after that it started giving me this error.
What is this error 255 actually about ?
Click to expand...
Click to collapse
Error 255 is insufficient storage space...
Is your TWRP backup in internal storage or an SD card? If it is on internal space, move it to the SD card and try again.
acejavelin said:
Error 255 is insufficient storage space...
Is your TWRP backup in internal storage or an SD card? If it is on internal space, move it to the SD card and try again.
Click to expand...
Click to collapse
Tried putting TWRP on External SD card but still gives same error.
Tried using Nandroid Backup and Restore, Apps force closes.
Tried Using Titanium Backup but I don't it working or not can't say much about it.
P.S. The backup I want to restore was orignally a compressed backup which I decompressed using Nandroid Backup and Restore
Compressed Size: 4.52GB
Uncompressed Size: 7.45GB
Pic is attached.
SuperSaket said:
Tried putting TWRP on External SD card but still gives same error.
Tried using Nandroid Backup and Restore, Apps force closes.
Tried Using Titanium Backup but I don't it working or not can't say much about it.
P.S. The backup I want to restore was orignally a compressed backup which I decompressed using Nandroid Backup and Restore
Compressed Size: 4.52GB
Uncompressed Size: 7.45GB
Pic is attached.
Click to expand...
Click to collapse
Yeah... I am not sure why the error 255, I was always under the impression that is a space error, but the your backup is corrupt:
tar_extract_file(): failed to extract //data/app/org.videolan.vlc-1/base.apk !!!
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/ZY2224PF42/2017-02-23--17-54-51/data.f2fs.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/ZY2224PF42/2017-02-23--17-54-51/data.f2fs.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
Click to expand...
Click to collapse
The recovery.log pretty clearly shows a tar extraction error...
acejavelin said:
Yeah... I am not sure why the error 255, I was always under the impression that is a space error, but the your backup is corrupt:
The recovery.log pretty clearly shows a tar extraction error...
Click to expand...
Click to collapse
Any wayout to extract apps and apps data?
SuperSaket said:
Any wayout to extract apps and apps data?
Click to expand...
Click to collapse
TBH, I don't know... you would try to do some research in tar file repair.
Actually, if it was me I would just factory reset and start clean.
Problem Solved (well kind of..)
For me , the problem was kinda solved. As per the suggestion by @acejavelin , I reset my phone and was only able to restore apk from my 7 GB TWRP Backup.
Titanium Backup doesn't restore my backup as it force closes whenever I tried to restore.
Nandroid Backup restore appdata but it eventually leads to force closes.
For anyone who wants to extract TWRP backup can use Cygwin
(By @carl1961)
"____________________________
CYGWIN Unpacking TWRP Backup Files
Thanks @Optikmike for CYGWIN tip
here's what I did..
CYGWIN Unpacking TWRP Backup Files
rename:
data.ext4.win to data.ext4.win.tar
system.ext4.win000 system.ext4.win000.tar
system.ext4.win001 to system.ext4.win001.tar
Make a directory in your CYGWIN Home [Username]folder
Example: untar
Use Windows File Explorer go to your CYGWING Home
C:\cygwin\home\carl (your user name will be here)
make any folder you choose
Example:
C:\cygwin\home\carl\untar
and C:\cygwin\home\carl\untar\data ( for data files)
put your renamed data files in a folder named data
C:\cygwin\home\carl\untar\data (this is to keep files separate when unpacked)
While in Explorer put your renamed system files in untar folder
start CYGWIN ( Use the Cygwin Terminal and then you can copy and paste these commands)
cd to untar folder
example:
cd\untar
do these commands one at a time, it will extract to a folder named system
tar -xvf system.ext4.win000.tar
tar -xvf system.ext4.win001.tar
cd to data
do this command
tar -xvf data.ext4.win.tar
___________________"
SOURCE : https://forum.xda-developers.com/showthread.php?p=53913623#post53913623
For me problem is solved . Anyone interested can continue this thread.
I am a newbie!
So I wanted to start flashing custom ROMS on my device...
So I flashed the Custom Recovery(TWRP) and downloaded compatible Custom ROM...
Ok so by following some blogs and videos I took the system backup of boot, system.
And yes I am able to restore it...
I also read about Android Partitions(https://forum.xda-developers.com/general/general/android-partitions-explained-t3657183)
But when taking the Backup I saw a System Image partition there.
So I am wondering what is its use and should I backup that for pure Stock ROM Backup?
And also does it include the boot partition files or I also need to backup the boot partition with it?
And if I create this file using which option can I install this type of Backup?
Thanks in Advance
Tanmay_B said:
I am a newbie!
So I wanted to start flashing custom ROMS on my device...
So I flashed the Custom Recovery(TWRP) and downloaded compatible Custom ROM...
Ok so by following some blogs and videos I took the system backup of boot, system.
And yes I am able to restore it...
I also read about Android Partitions(https://forum.xda-developers.com/general/general/android-partitions-explained-t3657183)
But when taking the Backup I saw a System Image partition there.
So I am wondering what is its use and should I backup that for pure Stock ROM Backup?
And also does it include the boot partition files or I also need to backup the boot partition with it?
And if I create this file using which option can I install this type of Backup?
Thanks in Advance
Click to expand...
Click to collapse
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank You Bro So Much for explaining this:laugh:
Ok So I can keep the backup of the system image if I want a complete stock rom backup, right?
But what about the other partitions like Recovery, IMEI, FRP, Pinfo, Logo?
I mean to say if I clear all these partitions for eg IMEI, will my device's IMEI number be deleted?
Or after flashing the system img these partitons will be regenerated?
And yes I am using the default TWRP backup and I am able to restore my android backup...
Tanmay_B said:
Thank You Bro So Much for explaining this[emoji23]
Ok So I can keep the backup of the system image if I want a complete stock rom backup, right?
But what about the other partitions like Recovery, IMEI, FRP, Pinfo, Logo?
I mean to say if I clear all these partitions for eg IMEI, will my device's IMEI number be deleted?
Or after flashing the system img these partitons will be regenerated?
And yes I am using the default TWRP backup and I am able to restore my android backup...
Click to expand...
Click to collapse
The default TWRP backup is all you really need. It will completely backup everything you need to backup/restore your ROM, the system.img backup isn't necessary. It is no different than the system.img that can be extracted from your stock firmware file.
As for IMEI, the method of backing up and restoring IMEI doesn't involve TWRP, there are other tools for that. Do a Google search for:
"How to backup and restore IMEI"
I suggest that you don't mess with any of the other partitions
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Droidriven said:
The default TWRP backup is all you really need. It will completely backup everything you need to backup/restore your ROM, the system.img backup isn't necessary. It is no different than the system.img that can be extracted from your stock firmware file.
As for IMEI, the method of backing up and restoring IMEI doesn't involve TWRP, there are other tools for that. Do a Google search for:
"How to backup and restore IMEI"
I suggest that you don't mess with any of the other partitions
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
OK Thanks Bro...