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
Related
I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it
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..!
Before going into the subject, I'll say that I have tried to seach this matter in XDA and Google, but nothing showed up.
Okay, so my matter is that I can't restore my backup of stock rom(8.0) after I flash a 8.1 rom. I've backuped with official TWRP "recovery-3.2.1-2-oreo.img".
My procedures are :
back up stock 8.0(system, data, cache, efs) with official TWRP "recovery-3.2.1-2-oreo.img"
flash oreo rom(with wiping internel, data, system, cache) and boot it fine.
restore my stock backup with same TWRP
boot system
The results are :
Goes past boot logo
Boot animation('android one' with colors sliding) shows up
and... just infinite loop of boot animation.
The ROM I used is RR.
I think the main problem is related with encryption.... Just my thought, tho.
So what I'm asking is :
1. If you face the same problem as me?
2. If you aren't and you restore goes fine, please tell me your procedures including ROM used and TWRP used.
3. Whether it is safe to decrypt stock rom?
Thanks in advance!
You don't need to flash stock ROM again. You have a system image backup(system, data, cache, efs), right? Wipe data , system, cache if you are coming from any other ROM. Then reboot to bootloader. Boot into latest TWRP from Fastboot (don't flash). Then go to restore and restore the system image you had backed up. Don't restore efs if you haven't lost your IMEI.
I've done exactly as ypu told, but it doesn't boot...
Did you manage to restore without problem with your method?
Yes I was able to. No problem here.
What TWRP did you use? Also, what ROM have you flashed?
Used the latest TWRP by MohanCM for Oreo. I did it when I was on Lineage os and wanted to go to stock
@guy_infinity Okay, thanks for your answer! Gonna try out later, once more.
Hmmm.... Still didn't boot up.
I thought I had to do everything from the begining, but flashing stock with save userdata option rescued me.
P.S. does anyone know about the error E: recv error on uevent?
try flashing stock rom using mi flash and after flashing restore normally using latest twrp/deadman's without system image voila everything will be back
@arjunbalan1994 Big thanks for your suggestion! Will try that too later
Hi, did you solve your restore problem? I have the same w/ my Redmi Note 5 and stock Miui backup after flashing RR.
Thanks for your help
I was use 8.1 root and twrp recovery. Yesterday fastboot flash may rom and update 2nd may OTA
Don't understand : May rom is Miui rom?
And did you restore your miui rom 8.0 backup ith twpr after the fastboot flash stock?
My phone was stuck in a bootloop where it could only get to recovery. Using the recovery I created a nandroid backup to the a USB stick using an OTG cable. I flashed the stock firmware and got things setup but I can't restore individuals apps from the nandroid. I copied the nandroid from the usb to sd card but it still doesn't work. I tried restoring apps using Nandroid Manager but when the app is launched it gives the error "app has stopped, close app". For some reasons sms succesfully restored but no user apps. I tried restoring with AppExtractor but it gives the error "unable to generate apk listing"
I also have titanium backup pro but couldn't get it to find the location of the nandroid to try extracting with it.
Any ideas? I really just want my messages back from Whatsapp.
My phone had stock Nougat with busybox installed and elementalx kernel. It should be the same environment now as when the backups were made.
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
twoplustwo said:
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
Click to expand...
Click to collapse
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
I am unable to copy the nandroid to internal storage. I tried using usb to computer and it just does nothing. I tried root explorer and it says 'copy failed' and file manager says 'cannot load'. This only happens with the TWRP folder inside the internal memory specifically.
____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
____Mdd said:
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
Click to expand...
Click to collapse
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
twoplustwo said:
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
Click to expand...
Click to collapse
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
____Mdd said:
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
Click to expand...
Click to collapse
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
twoplustwo said:
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
Click to expand...
Click to collapse
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
____Mdd said:
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
Click to expand...
Click to collapse
Just want to confirm everything is working perfect now. Thank you again!
So I was on stock rom that was unlocked plus rooted,I was also on a different kernel. Before flashing that kernel, I had taken a full backup(It had magisk installed) through TWRP. Full means I didn't leave any of the boxes unchecked,it was a 11GB+ backup. Then it was all well and fine until I found that these kernels weren't liking my 64gb sd card(I created a thread earlier). So I went back to TWRP to restore my backup, I did so, well and smooth no issues. Now when I booted my phone, my phone would just turn off after showing the Asus LOGO, I tried multiple times to no success. It would just turn off after showing ASUS logo. To get out of this mess, I flashed Stock rom through TWRP.
Now I'm clean and fresh, I want to take a good backup and then flash AEX rom! What partitions should I backup??
Backup
Deeptesh Basak said:
What partitions should I backup??
Click to expand...
Click to collapse
Backup:
Data
Boot img
System
You may have to flash magisk/SU again after restoring in some cases...
Deeptesh Basak said:
So I was on stock rom that was unlocked plus rooted,I was also on a different kernel. Before flashing that kernel, I had taken a full backup(It had magisk installed) through TWRP. Full means I didn't leave any of the boxes unchecked,it was a 11GB+ backup. Then it was all well and fine until I found that these kernels weren't liking my 64gb sd card(I created a thread earlier). So I went back to TWRP to restore my backup, I did so, well and smooth no issues. Now when I booted my phone, my phone would just turn off after showing the Asus LOGO, I tried multiple times to no success. It would just turn off after showing ASUS logo. To get out of this mess, I flashed Stock rom through TWRP.
Now I'm clean and fresh, I want to take a good backup and then flash AEX rom! What partitions should I backup??
Click to expand...
Click to collapse
Backup everything for your first backup.
For incremental backups - boot, system, vendor & data should suffice.
While restoring only select the above four i mentioned. For cross rom restore functionality vendor partition is required.
For restoring stock rom from stock - only boot, system and data should be enough.