I had LineageOS 17.1 + TWRP running fine on my Galaxy S5 klte, then the glue on the top part of the screen came away and disconnected the screen while the phone was on. After that it would only boot to part way through the Lineage animation, dimming to low brightness in the middle of it and rebooting into recovery.
Wiping the cache in recovery did nothing, but wiping the data partition fixed it, so I guess the data partition became corrupted. Restoring the data partition from an old TWRP backup of the same install works too. The hardware and ROM seem fine.
I made a full backup of the bad install, so is there anything I could do to try to get that working again or diagnosing what happens at boot? Any cache/settings files I could try deleting from the image if that's possible? I did find stuff about getting the last kmsg output but that doesn't seem to work with this phone/Android build. I wish I'd though about running fsck on the partition before I wiped it. No idea if the screen thing is a red herring or not.
Related
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Try re-loading recovery via Odin.
Check out this thread close to your issue
I am attempting this now. I did not realize that you meant stock recovery when I first wrote this post.
czahrien said:
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Click to expand...
Click to collapse
I'm having this same issue on my gf's Kindle Fire I w/CM10.2, but without the prompt for password. So annoying! Did you ever fix it? - http://forum.xda-developers.com/showthread.php?t=2563695
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.
Hi Guys,
Hoping someone can help and tell me that Ive not bricked my brand new S7 edge
I have experience in rooting / flashing a number of android devices so I was quite confident in what I was doing.
So I was trying to root my stock rom, I flashed TWRP using Odin which worked fine then I flashed the Super SU. When I booted it then asked for a PIN to boot, it definitely wasn't what I set and would have only set it to 1 thing. So I did some googling and found that I could clear data or remove the pin key files but in TWRP it couldnt mount data and I tried re-formatting but it sat there for over half an hour and I had to hard reboot. TWRP now just freezes at the splash screen during boot which confuses me cause even if I switched off during re-formatting, I was only on the userdata so surely that shouldnt affect TWRP? I then got to the stage where I thought entering the max PIN attempts would just wipe data but no it tried to boot into TWRP which is useless cause it doesnt get past the splash screen.
I can still get into Odin mode, is there something else I can try flash? I had tried reflashing TWRP before but it was still freezing at the splash screen
I thought of maybe wiping data over adb but I dont think I can do that unless the phone boots or gets fully into TWRP?
Any help much appreciated.
Thanks
Stewart
Have had my OnePlus 2 since 2015, and it's been a solid performer up to today.
I had the crDroid ROM (8.1) installed, along with Magisk, and it's been working fine for over a month with zero issues.
Today, I went to remove an app that was being troublesome, and then rebooted. And it just bootlooped. Animation is playing, but that's it. It sits there for 10-15 mins doing nothing. I hold the Power button to shut it down, and then try booting again. Same thing, just a straight bootloop for 15 mins. So I reboot to recovery (TWRP 3.2.1.0) and flash the Magisk uninstaller, to see if restoring the stock boot partition would help. It didn't, and just gave the same bootloop. So I go back into TWRP, wipe /system /cache and /dalvik and reinstall the ROM and gapps. Reboot. Same bootloop.
Now I'm starting to get a little concerned. Right now I'm restoring a backup from 10 days ago that I made before I last updated the ROM, but assuming this fails, does anyone have any good ideas? I'm not an expert, but I'm not a novice either, and this isn't making much sense. Unless my OnePlus 2 is getting ready to check out, which would suck...
idk if you had any mods like kernel or whatever or what app you removed (and if it had root acces) but first make sure you are on latest twrp, then try to clean flash a rom like normal. try to boot it it should work.
Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.
Gaffadin said:
Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.
Click to expand...
Click to collapse
This means that a date/time overflow occurred in your system
You restored a backup from 10 days ago, I'm assuming an older version of the ROM? So the newer version has an overflow bug
Even if nothing changes on the system your system time is always changing and if the ROM or kernel is somehow messed up then this value can cause an overflow and if a security module of some sort (like fortify_source or stack_buffer_protection) finds out about the overflow it can prevent boot from happening
Note: below example not completely valid in the real world, I've removed some stuff and is just for clear understanding.
Let's elaborate, "signed int" accepts values from -32768 to +32768 (0 inclusive)
What do you think happens when a value below -32768 is passed? That's an underflow and it's not defined what would happen below that limit (actually stuff does happen but see below notice)
If you pass a value over 32768 you cause an overflow
Note: I'm not going to go into details about what exactly happens. This would add too much information and cause more confusion than it would clear
What does this have to do with the date? Well every second your system date increases and if you got one of these limits you're going to run into problems
This is the only possible explanation for what could have happened
Thanks for the explanation. i think I understood most of it.
The backup from 10 days ago was from an older version of the ROM, though I have since installed the latest ROM version on top of the restored backup without issue, as I did when I first made the backup.