I had a full backup image in twrp.
Whenever i try to restore it auto reboot around 15% while restoring system partition ?
which partion to restore.
any issue if i chose to restore all partion
boot/system/system image/vendor/vendor image/data/cache/recovery/efs
any advice.
Thanks
kakabobo said:
I had a full backup image in twrp.
Whenever i try to restore it auto reboot around 15% while restoring system partition ?
which partion to restore.
any issue if i chose to restore all partion
boot/system/system image/vendor/vendor image/data/cache/recovery/efs
any advice.
Thanks
Click to expand...
Click to collapse
,,,You have to backup EFS once (via non-buggy twrp) and keep it stored on mobile and PC
... For ROMs..You just BACKUP system data boot
And restore them
... when shifting () different builds marshmallow to nougat... nougat 7.0 to 7.1 or whatever.. you need to INSTALL (not backup or restore) the CORRESPONDING vendor
That's it
Related
Hi Everyone,
I have an P5110 running stock Samsung 4.04 ICS firmware it's rooted and has cwm touch recovery installed and titanium backup pro (root) installed.
My question is this how do i verify a Nanodroid backup ?
I have read it checks the backups before a restore.
However, When running version 5.xx of CWM recovery it failed twice to restore data and since i couldn't i find a way to check the data before i restored it.
Data was overwritten, however cwm reported a fail to write to data, and sure enough no data had been written but /data had been formatted.
Is their a way to verify a backup before i choose to restore it ?
i am now using ClockworkMod-Recovery_6.0.1.0
thanks
Col
Hi everybody...
I'm an old user but new member of XDA...
I'm use 3.24.40.87 Rom + 2.8.7.0 TWRP recovery...
My phone was restarted when I was working with it A few days ago then it stayed on Asus logo...
I flash boot but it does'nt work!! so I flash TWRP and backup from my files and I was forced to reflash Rom (With great difficulty)
but now my backup will not restore and it shows Error 255!!
what should I do now?
same thing happened with me, what I did I flashed the same ROM and then used Titanium Backup to restore my apps and app data into the ROM from the TWRP backup.
R_Seen said:
Hi everybody...
I'm an old user but new member of XDA...
I'm use 3.24.40.87 Rom + 2.8.7.0 TWRP recovery...
My phone was restarted when I was working with it A few days ago then it stayed on Asus logo...
I flash boot but it does'nt work!! so I flash TWRP and backup from my files and I was forced to reflash Rom (With great difficulty)
but now my backup will not restore and it shows Error 255!!
what should I do now?
Click to expand...
Click to collapse
This thing happens to me when I select "Enable compression" and "Skip MD5" options in TWRP 3.0...
kloroform said:
same thing happened with me, what I did I flashed the same ROM and then used Titanium Backup to restore my apps and app data into the ROM from the TWRP backup.
Click to expand...
Click to collapse
thanks bro...
how should i restore twrp backup with titanium bachup?
R-seen said:
thanks bro...
how should i restore twrp backup with titanium bachup?
Click to expand...
Click to collapse
Goto Menu in Titanium Backup you will find an option Extract from Nandroid Backup
255 error due to no space in your Internal Storage , try to wipe Internal Storage after that copy your backup to Internal Storage and restore
Hi, this is my problem:
I want to change the rom of my zenfone from stock to a custm one. The issue i have is that every time i factory reset i have to spend 2 hours downloafing everything and changing the settings of my phone. How can i avoid that when switching rom? If i do a nandroid backup with twrp, can i restore only the data on the other rom? Or this is a problem? Should i use titanium backup? Id like to save photos and every setting too
biondo_92 said:
Hi, this is my problem:
I want to change the rom of my zenfone from stock to a custm one. The issue i have is that every time i factory reset i have to spend 2 hours downloafing everything and changing the settings of my phone. How can i avoid that when switching rom? If i do a nandroid backup with twrp, can i restore only the data on the other rom? Or this is a problem? Should i use titanium backup? Id like to save photos and every setting too
Click to expand...
Click to collapse
You can't restore just the TWRP's /data backup from Stock to, let's say CM or from CM to Stock, the system's phone won't boot.
TWRP's Data Factory Reset or flahsing a custom Rom using TWRP won't erase the internal memory, so the files you have in the internal memory will be there.
Yes, you should use Titanium Backup when possible to restore your apps or some setting/data.
TWRP's nandroid backup is usually used to restore the "hole" Rom (data, system and boot, at least).
Regards.
elperroderoke said:
You can't restore just the TWRP's /data backup from Stock to, let's say CM or from CM to Stock, the system's phone won't boot.
TWRP's Data Factory Reset or flahsing a custom Rom using TWRP won't erase the internal memory, so the files you have in the internal memory will be there.
Yes, you should use Titanium Backup when possible to restore your apps or some setting/data.
TWRP's nandroid backup is usually used to restore the "hole" Rom (data, system and boot, at least).
Regards.
Click to expand...
Click to collapse
Many thanks, I'll use Titanium then.
Anyway i want to save a nandroid backup just in case
If i have a nandroid backup saved on my phone, and i factory reset, will it stay or will be erased?
I don't have an sd now, and looks like i cant copy it on my PC
biondo_92 said:
Many thanks, I'll use Titanium then.
Anyway i want to save a nandroid backup just in case
If i have a nandroid backup saved on my phone, and i factory reset, will it stay or will be erased?
I don't have an sd now, and looks like i cant copy it on my PC
Click to expand...
Click to collapse
TWRP makes the backup in the /TWRP folder placed on the internal memory, external memory/SD and maybe (I have not tried on this device and his TWRP version), OTG USB storage, at your choice.
As I told you before TWRP´s Data Factory Reset won't erase the internal memory, so TWRP folder won't be erased neither, but maybe have a copy of the /TWRP folder from your internal memory in your PC is a good option too.
But keep in mind that the stock recovery's Data Factory Reset will erase all the internal memory (not only /data).
Regards.
Hi i tried to restore my Dirty unicorns backup and now i am stuck at the google screen. I booted to twrp and tried to erase the efs but it didn't work, still stuck at google screen. Also if I recollect i did not backup and restore the efs partition so i don't know what else it could be i did backup the vendor and the rest. Using twrp 3.1.0.0
Solved, flashed the vendor the the phone booted up. can somebody please write what you can backup up in twrp so i know to not bootloop again, thank you.
AndrewM3 said:
Solved, flashed the vendor the the phone booted up. can somebody please write what you can backup up in twrp so i know to not bootloop again, thank you.
Click to expand...
Click to collapse
To backup your current setup:
Boot
System
Data
Vendor
Is enough
Just in case: https://twrp.me/faq/whattobackup.html
If you switch to another ROM, wipe the above + dalvik/ART cache, data and cache partitions.
Then flash whatever you want with matching vendor. Redo the complete wipe above and restore your backup if you want to switch back. Backup your EFS at least once and keep it in a safe place...
Hopefully you won't end up bootlooping anymore! :good:
I have never succussfully restored a nandroid backup on this phone with any version of TWRP. I don't even try anymore because it's just a waste of disc space and time.
jhs39 said:
I have never succussfully restored a nandroid backup on this phone with any version of TWRP. I don't even try anymore because it's just a waste of disc space and time.
Click to expand...
Click to collapse
I'd be glad to help you if you wish..!
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info