Hi everyone,
A couple of weeks ago put lineage 14 on my 7 (mustang).
It's like new device! But has recently started crashing overnight. This is sub-optimal as I use it as my alarm clock among other things.
Is there any way to diagnose what's going on (a crash log etc)
Symptoms are that:
(1) it goes unresponsive, needs the power button held for 20secs and then charger inserted to bring it back to life.
(2) When it does come back, my installed apps are missing from the pixel launcher bar, and need to be re-added
Any help would be appreciated
Update on this. I suspected the SD card adopted storage. So:
- Did a fresh install of lineage 14
- Formatted the SD card as external only
However this issue persists. The tablet will go black, and require a soft reset (power held for 40secs) and reboot to come alive again
Related
Hey guys,
My tilt suddenly began giving me the black screen issue, after running the same installed programs (and nothing added or changed for more than 2 months) without issues.
I updated to the new HTC released ROM intended for the AT&T TILT and that did not help.
After testing different things I found out that the same Micro SD card that I had since day 1 was suddenly freezing my device. I tried using a new card and it gave the same result (even if there are no files or programs on the card)
I can run my device without it ever freezing without a storage card, but as soon as I put one in it will freeze after some minutes of not touching the device. As long as I am working on the device, it will not freeze. As soon as I leave it for some minutes it will freeze.
HELP!!!!!!!!!!!!!!
Did you changed anything in the Power Management of the device or SD card?
Hey SVCBLOBAL,
No I did not as far as I know. Is there another way then START> SETTINGS> SYSTEM> POWER.?????
Also note that I did a factory reset, inserted the empty storage card without installing any programs or making any changes on the device and as soon as I leave the device lying around for more than 3 minutes or so, it will freeze. I will have to reset it to work on it again.
Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!
Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!
Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.
Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!
Wow. This just gets weirder and worse(r). We've been running first CM 11 and then CM 12.1 on this HD for awhile and all was fine. Suddenly the battery indicator became wonky, dropping from 50-ish% to 1%, precipitating a shutdown unless the tablet was immediately plugged in. Then suddenly the battery indicator would return to normal and you could unplug the tablet.
Next, after running a backup on the CM 12.1 ROM the tablet started crashing during boot (the cyan android phase) UNLESS it was plugged in to the power supply (USB to computer is not sufficient). This, despite a good charge level on the battery. After a minute or so when the boot was complete, you could unplug the tablet and go on your way.
Today the screen flashing began. Makes the tablet completely unusable. Sometimes you can calm it down for awhile by connecting via USB to computer, sometimes not. This thing is freaking me out. I just recently took the tablet all the way back to stock and resintalled CM 12.1 from scratch, including building a new SD card from new files. Before someone asks, it's a class 4 card. I've always been fine with Class 10 or UHD cards when working with my Nook Tablet, but for some reason I decided to play it "safe" with the HD and hunted around for a lower class. Maybe a mistake?
Finally I took the tablet back to stock again today, completed the sign-in process to the old B&N account and everything is fine. No screen flashing, no funny business with the battery indicator, no problem booting without the power cable.
I just ordered a "new" (out of box) replacement for the tablet on ebay, but it doesn't seem like this is an actual hardware issue.
What scares me now is a potential repeat of this process with the new tablet. I've never had any experiences like this with my old Nook Tablet. I'm at a complete loss.
Help!
Edit: OK, we seem to have tracked down the general source of the screen flashing. The backup we have been restoring is from July 2017 so quite a few apps want updating. We noticed things would be fine for awhile and then the flashing would start. At one point "Unfortunately Google Play Services has stopped" kept popping up. I began to suspect either a bad or incompatible update was messing with the system. So...we did another restore of the same backup but immediately turned off auto-updates from the PlayStore. Three days later and no display flashing. One small victory.
Could the shutdown during the boot animation be caused by a corrupted file? I don't see how since it boots OK when plugged in, just not on battery, but I'm willing to pursue any possibility.
Edit.Edit: Well, well.... We got a "new" open-box HD from ebay and I started working on it. I noticed in making new SD cards that one I had been working with was not properly set to 0x0C FAT32 LBA. I fixed that. This time the tablet will boot into the OS without being plugged in! Yay! Still have to test that on the old one after I finish building a duplicate system.
I'm restoring apps and everything is fine until suddenly the flashing starts up again. But now I know when it did. The offender seems to be the 0.15 version of Lithium Epub reader. I managed to uninstall that via ADB (with screen flashing you can't do much with the tablet except ADB). Voila, no more screen flashing. I found a copy of version 0.13 and installed that. No flashing screen. Needless to say I've set the app to not auto-update.
Edit.Edit.Edit: Well, $40 later we now have a second Nook HD and both are running fine. Hard to imagine that the goof that somehow happened to the SD card would manifest as only being able to complete boot when plugged in, but that must be it. Returning to stock (tried that...) and reflashing with the newly prepared SD card did the trick. Moral: sweat the small stuff.
I have been the owner of this Samsung Galaxy S9 for about 13 months now, and earlier today my battery died. When I turned the phone back on after partial charging, it acted extremely strangely. It rebooted to the secure boot pin screen a few times, and even to recovery mode a couple of times, rebooting about every 3 minutes. But that isn't it; wifi and cellular refused to connect, the screen would not go off if I pressed the power button, the settings app would not open, many other apps barely works, and the device was very slow for the time it was on.
I did the usual troubleshooting steps, clearing the cache in recovery mode, booting into safe mode, uninstalling recently installed apps, scanning with Knox and Malwarebytes, nothing. But, I remembered the day before, inside Samsung Gallery, there was a little text box before my images that said "SD Card has corrupted information, please back up your SD card and consider replacing it." I didn't think too much about it, or screenshot it. Well, to try something, I removed the SD card and booted normally. The only thing I changed that time was the lack of the SD card and voila, it worked fine. Haven't had an issue since, and I honestly think it might be running better.
For my amateur speculation/hypothesis: I believe when Android starts up, it tries to index installed SD cards. The card I am using is an old Samsung Evo 32 GB card, to the tune of 5+ years. Possibly, with the age of the card, there was light corruption in one folder or cell, and Android didn't know what to do with it. I can't find any corrupted files, but I guess Android hung on parsing the microSD card. I just wanted to share my experience and see if anyone had heard of something similar; I sure cannot find anything on it.
TL;DR: A corrupted microSD card in my Galaxy S9 caused Android to lose most function, and bootloop. Usual troubleshooting did nothing, however, removing the card returned the OS back to normal.
Hi,
A few days ago, I replaced a USB socket on friend's old Samsung Note 1 (GT-N7000). Soldering may not be very professional, but it does the job - the phone is charging and it can connect to the computer.
Today (3 days after replacing the USB) he came back to me with another problem -
after turning on the phone, only the white brand name and model appear at the start and then nothing, a black screen. I think it's turning off. He says he had some problems with the battery in the meantime and the screen was flickering strangely.
He had a custom ROM loaded for a long time that worked normally and worked well on this phone.
Today, despite not starting the system, I was able to enter TWRP recovery and DL mode. However, if I wanted to do anything in recovery (backup, factory reset, etc), the screen turned off. After a few attempts, it stopped going into recovery.
I have restored the original software using Odin and N7000XXLSZ_OXELS7_4.1.2_Repair_Firmware
- still after the white inscriptions at the start, the screen goes black and nothing
- trying to enter recovery, overturned android appears for a moment and the screen goes black
- DL mode works
Maybe someone knows what could have happened and most importantly how to get this phone work? Preferably on some "custom ROM" to have at least Android 7.
I was thinking, I was looking, I was tearing my hair out of my head. I searched half the internet and suddenly stumbled upon this - https://forum.xda-developers.com/t/...bricked-only-download-mode-available.3096409/
The phone is the same, the problem is the same - the battery is to blame. I immediately called the owner to give all the batteries he has.
OH, OF COURSE! The one I got along with the phone and its problems was the only one that caused all the restarts and errors. After inserting a different battery, the problems were resolved.
All that's left is to clean up Android and the case is closed.
By the way - I have collected in one place the files and information (Polish language only) on how to install NightOwl LineageOS 14.1 Android 7.1.
2 on this phone. If anyone needs this information, please visit here - https://drive.google.com/drive/folders/1libYpWC4qJbjGJRE1Szf8L3eTdoHPTpE?usp=sharing