I have a full adb backup which I made when I was on Cyanogenmod which I'm attempting to now restore after having installed either RR or Lineage.
There are no errors except that "music has stopped", some other app also stops, and then eventually as the restore finishes, trebuchet itself stops. It keeps stopping and renders the device useless, with the screen blinking as it attempts to restart continuously.
I reboot the device through adb, hoping it is just something intermittent which will be resolved after a reboot. However, the same problem occurs as the device restarts. The screen keeps blinking, trebuchet crashes and restarts continuously and the device cannot be used.
While this happens and I'm connected to it by adb, there is nothing in dmesg to indicate anything is crashing. I was expecting to see trebuchet or some relevant program crashing with segfault, but there is nothing like that, so it almost seems it is terminating gracefully, for whatever reason.
Related
So I unrooted my Kindle Fire and got back on the official 6.3.1. I have no TWRP or FFF anymore, but the Fire keeps crashing every 10-30 seconds. I have no idea what to do and, honestly, the device seems ****ed. Can't get into fastboot, can't get into recovery, can't do anything.
Acore crashes, calendar storage crashes, the system reboots, repeat forever. Any way to fix this? I can't get into fastboot mode, it says "failed to copy files\fbmode to /data/local/fbmode: permission denied" and then just reboots into regular mode.
Well it may take many attempts but you need to reach settings factory reset and reset it it`s a race some people win. Most often when I say this some some respond with " I cant do it it fc`s before I can". Then within a day or so it`s " I finally managed to beat it and its fixed". So anything you can do to shave time will help, try starting with the device completely powered down and race from there.
Not quite sure exactly what's happening, but it's repeatable and noticeable and for anyone less-tech savvy might convince them they're bricked.
It seems to be when a zip comes with an installer (such as Android Revolution) - once the install starts it's fine as long as I touch the screen every few seconds, however if I don't touch it for a while, say when it's loading system files and then continue on with the installer and get to the end - the installer will exit gracefully then I will see the usual "unlock" for TWRP, and before I can hit it the screen will go completely black.
While it's in this state, the phone will not respond to anything. Even a hard reset (power+down) doesn't do a thing. The only way it signifies it's still alive is by running 'adb devices' when plugged into a computer, then adb reboot.
You have enable screen timeout unchecked?
"Unfortunately Bluetooth has stopped" repeatedly - can't access anything on phone
After a reboot I, getting this error message popping up repeatedly (literally every 2 seconds), so I am effectively locked out of the user interface. Several reboots haven't helped.
This happened immediately after I followed these instructions to enable write permissions on my external SD card:
http://forum.xda-developers.com/showpost.php?p=60417230&postcount=2
Essentially I edited /system/etc/permissions/platform.xml and rebooted.
Assuming that this has caused the problem, is there any way of restoring this file to its original state using ADB?
itm said:
After a reboot I, getting this error message popping up repeatedly (literally every 2 seconds), so I am effectively locked out of the user interface. Several reboots haven't helped.
This happened immediately after I followed these instructions to enable write permissions on my external SD card:
http://forum.xda-developers.com/showpost.php?p=60417230&postcount=2
Essentially I edited /system/etc/permissions/platform.xml and rebooted.
Assuming that this has caused the problem, is there any way of restoring this file to its original state using ADB?
Click to expand...
Click to collapse
It looks like ADB may not be an option, as I can't boot into download mode. I've tried holding down Power+VolDown then plugging in the USB cable, but it will only boot into normal mode. I also tried using FastBoot to get into Recovery mode, but it reboots to a Android icon with ax exclamation mark in a red triangle. I have a horrible feeling this might be bricked.
Any ideas???
Edit: So I also did a factory reset, and the Bluetooth error message is still repeatedly popping up over the initial setup screen.
HELP!!!
itm said:
After a reboot I, getting this error message popping up repeatedly (literally every 2 seconds), so I am effectively locked out of the user interface. Several reboots haven't helped.
This happened immediately after I followed these instructions to enable write permissions on my external SD card:
http://forum.xda-developers.com/showpost.php?p=60417230&postcount=2
Essentially I edited /system/etc/permissions/platform.xml and rebooted.
Assuming that this has caused the problem, is there any way of restoring this file to its original state using ADB?
Click to expand...
Click to collapse
OK so I finally managed to open Root Explorer and restored the original platform.xml file. Now the problem I have is that Bluetooth will not turn on. I enable it in settings, then after less than 10 seconds it disables itself. Reboot and Safe Mode don't help.
Has anyone else had this problem?
So I had the RR-N-v5.8.5-20170926-n7100 custom os installed on my GTn7100 phone. Yesterday, the battery was drained. I had the wifi on and it was consuming battery very fast. So when I charged it to nearly hundred percent, the phone lagged crazily. I even noticed that the arrangements of the icons of my apps were changed. Then it hanged for about 5 seconds (the screen was on home) and then it went off. I was really confused as to what just happened. And turned it on, the phone is not booting anymore. It's just stuck on the "samsung galaxy gt n7100" boot screen (it's not on loop). I thought it's just some random bug and went to restart it again but to no avail. I had the TWRP 3.0.2-0 installed and thankfully it's still working after pressing the combination. At the start, there is a prompt about 'unmodified system partition...' and I thought factory resetting the device might resolve it, but to no avail again. The process was succesful but in the terminal, there are errors in blue line that says that there is no storage to wipe or something like that. And there is also a prompt that the device has no os installed. Even in the mount settings, when i select a storage, the prompt says that the 'Internal storage (0mb)'
What to do?
I recommend flashing the latest stock ROM with Odin as a first step. If the phone boss properly, then you know it was a software problem.
I am trying to understand why a particular LG G4 is hanging during boot.
Previously, LOS 14.1 (7.1.2) worked fine, with no notable problems. The phone would sometimes get warm during use (primarily when location services were active), but this seemed to be manageable.
Then, the battery was accidentally allowed to discharge to zero. After the battery was recharged, the phone became unable to boot past the Lineageos "bubble on a string" animation (first bubble). The animation of the first bubble simply continues forever.
The phone can boot to TWRP, fasboot, download mode, etc.
I am looking for info on how to retrieve the logs produced during boot so that the problem can be identified.
I tried attaching to computer and launching "adb logcat" during animation, but the device is never found. If I remember correctly, "USB debugging" was off when the device died. (ADB does work in TWRP.)
Further information here: https://forum.xda-developers.com/t/is-this-ilapo-or-something-else-g4.4211343/