Database Users

TWRP Cannot backup, reboots.

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.

I fixed a used-to bricked Nexus 4. Need explaination!!!

You dont have to say I am silly or noob or stupid, cause I know that already. This is what has happened in case someone stucks in the same situation.
Three weeks using Nexus 4 (my first smartphone and first android phone ofcourse) and I have restocked 2 times (succesful, not count the fail one). Sometimes I felt frustrated and desperate, sometimes happy like I win lottery tickets )
- I used 4.2.2 franco kernel r80, nominal CPU. It sounds crazy but I UV -200 for all frequencies (the lowest one from 900 to 700). And everything run completly normal, I have tested ASpahlt 7 for 4 hours. NO reboot. 2 days without any reboot.
- I turned off the phone to charge it. Then opened again. UV -200, but it rebooted this time.
- Bootloop.
- I have tried to flash boot.img. It passed the X, then stuck at "Upgrading apps, starting apps" or something like that, I dont remember exactly.
- Then tried to reset to stock kernel. Stuck at Upgrading again.
- I try to restore my nadroid through CWM recovery mode, but the d*** recovery said MD5 checking failed.
- I restocked to 4.2.1 by Nexus Root tool kit, option: bootloop. After finishing, it stayed at fastboot for 15 minutes (i can still choose to recovery or reboot) while the tool says wait for the device to boot or something similar. I restart manually --> still stuck at Upgrading apps. I knew something was wrong here. Restart --> bootloop
- I restocked to 4.2.2 --> bootloop. (followed this guide http://forum.xda-developers.com/showthread.php?t=2010312)
- I restocked to 4.2.1 ---> bootloop.
- I restocked to 4.2.1 by NExus Root tool kit --> bootloop.
- I restocked to 4.2.1 by fastboot again --> still bootloop.
- About to call Google for RMA.
- I have no idea why I did the following thing. I went to recovery mode (the one with the android lying with a red triangle).
- Wipe cache partition
- Wipe data/factory reset. (maybe this is what saved me)
- Reboot.
- Huray, my darling comes alive again.
- But what has happened? Would you mind explaning for me please.

When you get a boot "error" due to a great UV the first thing to do is to reflash a kernel-> wipe cache and dalvik. If it doesn't work then you should Wipe data-> cache-> dalvik and here you go.
Important: Reflashing stock images without doing a wipe cache and dalvik cache often cause a bootloop, because you have the cache of the OLD ROM on your device.
These are my experiences, i may have said a lot of bulls***s

I can't give a good explanation, only an incomplete one. But when /cache contains bad data, reflashing /system and /boot will do nothing to solve the problem. Restoring a nandroid backup would work if you didn't encounter the md5 failure. The real question is why /cache got populated with bad data.
I got stuck in a bootloop when I first rooted my phone (by flashing CWM, then installing a .zip that contained SU). Wiping /cache cleared up the problem. It seems /cache is more prone to corruption on the N4 than my previous phone.

sorcio91 said:
When you get a boot "error" due to a great UV the first thing to do is to reflash a kernel-> wipe cache and dalvik. If it doesn't work then you should Wipe data-> cache-> dalvik and here you go.
Important: Reflashing stock images without doing a wipe cache and dalvik cache often cause a bootloop, because you have the cache of the OLD ROM on your device.
These are my experiences, i may have said a lot of bulls***s
Click to expand...
Click to collapse
I did wipe the cache and davilk when I reflashed the stock kernel, but I didnt wipe the data, maybe I should try this in the first time.
Thanks for your replying I am still a fresh man, so everything has its value, no bulls___s here :good:

fenstre said:
I can't give a good explanation, only an incomplete one. But when /cache contains bad data, reflashing /system and /boot will do nothing to solve the problem. Restoring a nandroid backup would work if you didn't encounter the md5 failure. The real question is why /cache got populated with bad data.
I got stuck in a bootloop when I first rooted my phone (by flashing CWM, then installing a .zip that contained SU). Wiping /cache cleared up the problem. It seems /cache is more prone to corruption on the N4 than my previous phone.
Click to expand...
Click to collapse
Thanks for this too
I am rooting my phone. Such a long night.

Failed installing Lineage 14.1, wiped system, now restoring stock won't boot

Attempt 1 to install Lineage
Tried installing the Lineage 14.1, it kept doing a blank-but-illuminated screen, then turned off and back on, resulting in a boot loop.
We tried a couple of things - first the more conservative wiping of just data, dalvik and cache.
This did the boot loop described above. I then restored the stock backup and all was well.
Attempt 2 to install Lineage
The second time we wiped the system partition in addition to the above. Same bootloop.
Went to restore the backup of stock again, but now it's getting stuck at "I'm not a phone I'm a comprehensive yada yada" screen. It never progresses past this.
Attempts to get Stock Restore working
We've tried restoring just the system, data and dalvik
We've also tried System Image in addition to these.
No joy.
We don't have a laptop or other device to hand for a few days so we have just what's on the phone - the Lineage 14.1 zip, the stock backup and TWRP.
Any ideas how we can get back to a working phone with either OS?

What type of LePro3 do you have?
X720,X722,X727?

It's the X722

kenbw2 said:
It's the X722
Click to expand...
Click to collapse
The X722 model is not supported by Lineage.
I think that you have a problem. Hope anyone can help you to go back to stock successfully.

When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?

kenbw2 said:
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
Click to expand...
Click to collapse
Yes, you could try it. Please, write, was it useful or not)

Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!

kenbw2 said:
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
Click to expand...
Click to collapse
That is great. So, is bluetooth works fine after that?

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

What did I do wrong?

My phone was building up too much cache so I decided to go on TWRP and do a wipe of cache and dalvik cache, but after that it started to lag *a lot*. After booting the phone takes a lot of time to load the launcher, Google feed works after 5 minutes of the boot, everything lags, it doesn't detect the Sim card unless I pull it out and in again. What did I do wrong? I what cache is and why does it exist but I didn't think this would do so much harm.

Should I reflash the ROM or something like that? Don't know what to do.

I thought after a few boots it would build up enough cache again to work properly but it has been a week already and every boot is the same, it takes at least 10 or 15 minutes to work properly

E11101101 said:
I thought after a few boots it would build up enough cache again to work properly but it has been a week already and every boot is the same, it takes at least 10 or 15 minutes to work properly
Click to expand...
Click to collapse
Are you sure you haven't wiped any other partition?
Are you on stock ROM?
Anything installed to cache like the loopback bug fix for magisk?
Usually the wipe of cache and dalvik causes no problems, the first boot will take longer but after that everything should turn back to normal again.
If the problems persist a factory reset or if that doesn't help a reflash of the ROM may solve the issues.

Wolfcity said:
Are you sure you haven't wiped any other partition?
Are you on stock ROM?
Anything installed to cache like the loopback bug fix for magisk?
Usually the wipe of cache and dalvik causes no problems, the first boot will take longer but after that everything should turn back to normal again.
If the problems persist a factory reset or if that doesn't help a reflash of the ROM may solve the issues.
Click to expand...
Click to collapse
I decided to flash the ROM again, I am on the Pixel Experience rom, didn't have any fix or anything like that, but after reflashing it has been working better, guess I'll wipe dalvik only when flashing something like a Magisk module.

E11101101 said:
I decided to flash the ROM again, I am on the Pixel Experience rom, didn't have any fix or anything like that, but after reflashing it has been working better, guess I'll wipe dalvik only when flashing something like a Magisk module.
Click to expand...
Click to collapse
I haven't wiped dalvik/cache for over a year now while flashing magisk, different modules and other stuff. I personally think wiping cache and dalvik is overrated on newer devices.

Wolfcity said:
I haven't wiped dalvik/cache for over a year now while flashing magisk, different modules and other stuff. I personally think wiping cache and dalvik is overrated on newer devices.
Click to expand...
Click to collapse
I'll surely not do it again because it ruins the launcher an awful lot.