TWRP Cannot backup, reboots. - Nexus 10 Q&A, Help & Troubleshooting

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.

Related

Made backup in TWRP 2.3.4, won't restore in 2.5.0

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

[Q] Problems restoring a backup of the stock rom

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

Stuck at boot screen after restoring ány Nandroid backup.

Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.

TWRP restore does not work

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.

Lineage stuck on boot loop on startup

Hi,
I have LineageOS 14.1 installed on my Moto G4 Plus. All of a sudden it rebooted and was stuck on the booting screen. I can get to TWRP. Things I tried that didn't help
wait 30 minutes
plug in phone to charger
clear cache
fully power off then on
If it comes down to it, I could flash a new ROM, but would like to save/backup the text messages/whatsapp messages.
@lightningglasses
Anything you installed/flashed before rebooting ?
try to dirty flash ROM and check if it boots or not.
____Mdd said:
@lightningglasses
Anything you installed/flashed before rebooting ?
Click to expand...
Click to collapse
nothing.an mp3 player app
try to dirty flash ROM and check if it boots or not.
Click to expand...
Click to collapse
will that loose the text messages etc?
lightningglasses said:
will that loose the text messages etc?
Click to expand...
Click to collapse
wiping "Data" deletes everything, dirty flashing does not not.
Just wipe delvik-Art and cache (*not data*), Then install ROM (plus gapps and root if you need), reboot, it will take around 10 minutes to re-generate delvik data, then it should boot..
____Mdd said:
wiping "Data" deletes everything, dirty flashing does not not.
Just wipe delvik-Art and cache (*not data*), Then install ROM (plus gapps and root if you need), reboot, it will take around 10 minutes to re-generate delvik data, then it should boot..
Click to expand...
Click to collapse
hmm didn't work, any other ideas?
lightningglasses said:
hmm didn't work, any other ideas?
Click to expand...
Click to collapse
I forgot to mention in previous post, did you wipe system? Try with that and install rom.
Reinstalling ROM heals damage made to /system partition and to boot, but not to /data.
so if still doesn't boot, that means damage happened to /data and you need to clean it, result in lost of data of apps (whatsapp and message you mentioned in your post.)
Still if you know what apps you installed last, delete it from /data/app/xyz-app (boot TWRP > advance > file manager)
____Mdd said:
I forgot to mention in previous post, did you wipe system? Try with that and install rom.
Reinstalling ROM heals damage made to /system partition and to boot, but not to /data.
so if still doesn't boot, that means damage happened to /data and you need to clean it, result in lost of data of apps (whatsapp and message you mentioned in your post.)
Still if you know what apps you installed last, delete it from /data/app/xyz-app (boot TWRP > advance > file manager)
Click to expand...
Click to collapse
It is still stuck in a boot loop after I
cleared cache, dalvic/art and system
used twrp's file manager to delete all recently installed apps from /data/app
flashed newest lineageos rom
clear davilink again
waited 15 minutes with phone plugged in
When should I wipe cache/dalvik/system? Before or after flashing rom?
lightningglasses said:
It is still stuck in a boot loop after I
cleared cache, dalvic/art and system
used twrp's file manager to delete all recently installed apps from /data/app
flashed newest lineageos rom
clear davilink again
waited 15 minutes with phone plugged in
When should I wipe cache/dalvik/system? Before or after flashing rom?
Click to expand...
Click to collapse
There is no other way to get your device back without losing data.
I have never used Titanium backup app but i know there is feature to restore data from TWRP backup, you can take backup of /data and restore backup of whatsapp.
I am still not sure about that feature, if you have time then i can test that feature, otherwise there is no way to keep data.
Edit: whatsapp makes chat backup every night at 2AM, if you haven't had any important chats after that, you can go for wipe.
If you can pay for titanium backup there might just be a way. I am not 100% sure but take a backup of the "data" partition(you can backup everything but data is most important) in twrp in internal storage only. Then clean flash everything. Then install titanium backup and buy the pro key. Then restore from twrp. If you find an option to restore only data then that's a better option. Downloading the app and restoring the data is better than restoring app and data. I'm not sure if it will work. But if nothing is working and your data is 100% vital you may wanna try this.
Another tip, don't restore blindly everything cuz bootloop may occur again

Categories

Resources