A while ago i decided to install Cyanogenmod 12.1 from here on my s3 neo (gt i9301i) and so i did. Everything went well i am publishing this from it actually. Before the cyanogenmod i had kit kat and i did a backup with twrp. I decided to restore the backup since i feel like this is not for me so easy right wipe data bla bla restore backup. First time it worked it got into my old kit kat but it started to rain with forced closed processes it kept closing proceses. So i decided id restore it again only this time i got a boot loop. I flashed back the cm and gapps so i can use the phone. Is there any chance to get my android back? If not if i wanna flash an official firmware with odin do i have to wipe the data before or anything?
Thank you!
Copy your backup in a pc do a wipe
Afterthat, cpoy the backup in the internal storage (it is faster) than go to restore
Restore everything except DATA
Boot the neo, set it up, reboot back in recovery.
Restore DATA only.
It must work because i do this every time we have a new rom
ziad311 said:
Copy your backup in a pc do a wipe
Afterthat, cpoy the backup in the internal storage (it is faster) than go to restore
Restore everything except DATA
Boot the neo, set it up, reboot back in recovery.
Restore DATA only.
It must work because i do this every time we have a new rom
Click to expand...
Click to collapse
Thanks man it worked just fine!
Related
I recently made a backup of my stock rom using TWRP, I then flashed cyanogenmod 12.1 and due some random reboots I wanted to restore my stock rom.. I went into TWRP, did a wipe on everything but the external sd card then restored the backup of the samsung rom boot, data, system. When it booted it said it was upgrading all the android apps then starting apps then all the apps it tried to start crashed and was left with a blank screen. Is there something you have to do, to be able to restore a stock rom after flashing cyanogen?
No, that should have worked, but I have seen that crash black screen after clearing caches in TWRP, I pulled the battery, booted again and it was fine
*Detection* said:
No, that should have worked, but I have seen that crash black screen after clearing caches in TWRP, I pulled the battery, booted again and it was fine
Click to expand...
Click to collapse
Wierd, yeah I tried a couple of reboots and it always crashes once it starts apps after a restore.
Try flashing a stock ROM with ODIN to get the phone back to 100% stock
Then root and flash TWRP again and see if you can restore the backup then, if not, try restoring the backup without restoring DATA which is where the apps are
If that works, you could use Titanium Backup to restore the DATA partition iirc, see if you can get around it that way
Hi,
yesterday I decided to install new ROM - Cyanogenmod 12.1 on my Galaxy S4 only for tests. Before that I done backup with every partitions:
boot
system
data
cache
EFS
I'm using TWRP 2.8.7.0 recovery
After tests I restored my backuped ROM, but unfortunately OS doesn't work, I cannot even put my PIN code. Every time I see pop-ups with apps stoped working.
What I am doing wrong or how can I restore properly my old OS.
You may have to perform a factory wipe after restoring your old ROM or you may need to flash stock recovery to perform a factory wipe.
Hello,
before I played around with getting root and flashing custom roms, I backup everything in Samsung Smart Switch.
After getting root and install TWRP, I backup the whole system (except the recovery partition) to the external sd-card from TWRP.
Now - after getting some experience with custom roms - I will go back to the stock rom from my TWRP-Backup. Set everything to factory default, wipe cache and dalvik and press restore. Select my backup... swipe to flash... everything seems ok. After reboot - no bootloop - a thousands of alert-messages pops up "blabla-app stopped"... Then appears only a black screen.
How can i restore my backup from TWRP? Or is there a stock-rom, so i can backup from smart switch? My System is a LRX21T.G900FXXU1BOJ1
Thanks alot!
Try clearing the caches from recovery and boot again
If it fails, try wiping everything again, then restore all partitions except DATA
See if it boots
If it boots - either reinstall apps etc manually, or use TiBu to restore the DATA partition
I've got it!
I flashed a stock rom with odin and restore with smart switch. Some settings are missing, but i think 90% is restored
Nice job
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'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