Hi,
After many months with Lineage 16 installed with no issues suddenly freezes and switched off.
I have checked battery (seems to be ok, unplugged and plugged again), I have updated to Lineage 17.1... same behaviour, updated TWRP, trying clean & dirty installations... no changes. Installed again Lineage 16, wiped all partitions, no changes.
After reboot system hangs and power off. I have noticed the phone is hot when this happens.
In recovery the phone works well with no issues, I can do everything but when reboot to system hangs after the sim lock screen (I have tried without SIM, same behaviour).
Where's the problem? Maybe a hardware issue?
Regards.
SOLVED!
Seems the internal storage was encrypted. I have wiped all partitions before with no success including internal storage but this time I have done 'Format data' which removes encryption. Once finished I have rebooted and everything is working fine.
Related
Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").
Hi!
I have been facing freezes(then reboots) and my computer not able to detect my internal storage(Windows was unable to install drivers)
This occurred randomly, everything was working just fine. The freezes started after my internal storage vanished. (I'm still able to transfer files through AirDroid) Have switched 3 ROMs, just flashed AICP and it crashed in titanium backup, so this is not a ROM problem.
Could my storage/partitions be corrupted? I am able to flash ROMs just fine though
Will flashing 6.6.10 through fastboot fix this?
(On a side note, formatting the cache partition used to take a few seconds, but it takes about 5 minutes these days, this has been happening for a few months now )
Thanks in advance
EDIT: Flashing the stock ROM did nothing. The problem persists. Internal battery short circuit...?
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516
Hi,
since my old M7 is having more and more annoying issues, I tried to move to a One A9.
The problem:
The phone gets stcuk on LOS boot screen. Looks like it's loading but it never finishes and I can't even turn it off by holding power button pressed for 10s, 1m or even 10m!
BUT this happens only sometimes! Last night I just left it in this state to get the battery empty and this morning it was turned off. "On the way" to recovery (TWRP 3.1.1) I pressed the wrong button and it rebooted. Without any issues! Used it all day until I wanted to reboot it to insert a microSD-card. Since then: stuck on bootscreen! Can't get out...
Any ideas?
What I did:
Unlocked the phone
Factory reset
Installed TWRP
Flashed LOS 14.1
Flashed Magisk 14.0
Help appreciated
Somehow I'd consider this thread as solved:
I went back into TWRP and:
- formatted DATA
- made a full wipe
- made another full wipe
Now suddenly I don't get neither bootloops nor "Can't mount" errors in recovery (which I forgot to mention in the opening post :silly
I write "somehow" since I have formatted DATA before, as well as made a full wipe, because I couldn't even install LOS before that
Whenever I try to encrypt my device, it reboots. The android line-art image appears for about ten seconds. Then the device reboots without encrypting. I've tried as root, non-root, with wifi on, and off. I've tried it in portrait mode and landscape (read somewhere that this helps). 100% power, somewhat less power. I've tried reinstalling, and with two different roms: Cyanogen Unofficial 13, and Paranoid 6 (both run Marshmallow). I've even tried reflashing the recovery (currently using TWRP 3.1.1-0). Of course I've also wiped my internal storage. Everything else that I can see seems to work fine, except for encryption.
I'm honestly at my wit's end. Does anyone have any advice on how to reconcile this issue? Thanks ahead of time for any input.