I've used TWRP to create backups of ROMs on my onyx device. However, every time after restoring a backup; upon boot into the ROM it stays at the loading screen. I've found ways to get around this by installing the specific ROM I was using and just restoring /data . However, this doesnt work properly as some apps are broken.
Nonetheless, has this happened to anyone else? Did you fix it? How can I fix?
Did you wipe System, Data, Cache & Dalvik before restoring ?
If not then try that.
I reflashed TWRP using fastboot method and restores work fine now. Previously, I was flashing TWRP using .img method from the recovery.
Related
I can't seem to be able to create a nand backup with TWRP, after around 30 seconds to a minute of starting the backup, it reboots back into the main page of the recovery. I have tried reinstalling TWRP several times through goo manager. I can do everything else fine with TWRP, flashing nightlies and all that, but as soon as I start a backup it reboots. I have enough space available as well for the backup. I've used TWRP on all my other devices and never have had this problem. Any ideas?
Varekai said:
I can't seem to be able to create a nand backup with TWRP, after around 30 seconds to a minute of starting the backup, it reboots back into the main page of the recovery. I have tried reinstalling TWRP several times through goo manager. I can do everything else fine with TWRP, flashing nightlies and all that, but as soon as I start a backup it reboots. I have enough space available as well for the backup. I've used TWRP on all my other devices and never have had this problem. Any ideas?
Click to expand...
Click to collapse
I'm having the same problem. Also restoring backups is acting flaky. Flashing and wiping is fine. I guess I will try CWM instead..
After reinstalling twrp, wiping cache and dalvik cache, fixing permissions, twrp is working correctly now.
(probably just wiping cache is what fixed it.)
I don't know, I always wipe cache's when flashing new nightly's, I think it was more the fixing the permission thing. Either way working now, so all good.
Hi,
I have flashed a new rom and i wanted to restore my data via twrp.
It was successfull, but my N7 was not able to reboot, because just booting and it havent done anything.
I made a wipe cache and dalvik cache but they couldn't help.
Any idea how can i solve this issue?
im using twrp 2.4.4.0
thx your help!
szabadgy said:
Hi,
I have flashed a new rom and i wanted to restore my data via twrp.
It was successfull, but my N7 was not able to reboot, because just booting and it havent done anything.
I made a wipe cache and dalvik cache but they couldn't help.
Any idea how can i solve this issue?
im using twrp 2.4.4.0
thx your help!
Click to expand...
Click to collapse
You're confounding variables here... you're trying to use TWRP like Titanium (apps/data).
TWRP (like CWM) is a MONOLITHIC backup system, pretty much everything gets restored. Titanium is GRANULAR... and selected apps/data are restored WITHIN the ROM you've just flashed... not OVER THE TOP of the ROM, as you've just attempted to do... which will cause no end of problems.
--------
Here's what I would do.... restore your NANDROID backup as normal (factory reset, etc.)... Get TITANIUM from PlayStore. Backup your apps/data using that.
Flash your ROM... restore your apps/data using TITANIUM.
Rgrds,
Ged.
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Coronado is dead said:
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Click to expand...
Click to collapse
Well, have to say, thanks matt. The included RSD helped.
I forgot I was also restoring stock over CM10, which may have also been the issue, but I am back into the phone now.
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
RikRong said:
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
Click to expand...
Click to collapse
I have no idea what caused the issue. I did a backup of CM10, wiped data, cache, dalvik, and system. Hit restore on my old Stock backup (created in TWRP, not safestrap), wiped dalvik and cache again, and rebooted (and allowed TWRP to fix root first). It booted to the droid eye, but then just hung there for about 10 minutes.
I used Matt's utility to restore the system and it failed (tried to install the same part of system over and over again, 3mb in 4 seconds, 100k in .4 seconds, over and over again). So I had to force stop that and use RSD which worked fine.
No idea what all that was about.
So I think I found the culprit. My backups from the older version of TWRP don't have BOOT, only SYSTEM and DATA. So I was probably having my stock rom install while the CM10 BOOT was still in place.
The more you know
My Nexsus 4 was at 5.0.1 updated OTA, I rooted and installed recovery and created a nandriod backup on the internal SD card. The phone was working fine for the most part except it was having issues with the screen going black when making a call and would not come out of that state. I wanted to revert back prior backup so I did a nandriod restore with CWM v6.0.4.7 and now my phone is in a bootloop. I've tried wipe data/factory reset, also tried wipe cache partition, but still stuck in bootloop. I'm not sure what else I can do to get out of this bootloop state/ Any suggestions would be greatly appreciated.
Fixed it by using Nexus Root Tool Kit to flash stock image. Not sure what happened but I'm switching to TWRP. First time using CWM and things didn't work out well for me using 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