Develop Bugs

[Q] Device reboots after SIM unlock

Hi all,
recently my D855 with v20T (root/xposed) started to sort of randomly reboot. It seems like once the device gets too hot, it's gone.
Happens rarely during general usage, often while playing a game, and especially often when starting the camera.
But it behaves strangely in general: if I do *not* unlock the SIM (and thus can't use the phone), the device runs forever, without a reboot, no matter what the device temperature is. Same for recovery (TWRP), it can stay there for hours and heat up however it likes, no reboot.
Removing the SIM and/or microSD does not make a difference, battery level does not matter.
I pulled a backup of the stock ROM, wiped everything (system, data, cache, dalvik) and flashed Fulmics 5.
Unlocking worked once or twice, the next time I entered my SIM pin, the lock screen showed, then reboot. This behaviour (unlock SIM, reboot) repeats endlessly. If I leave it turned off for 10-15 minutes - or sitting at the SIM unlock screen - it most of the time works fine after unlocking.
Wiped again, flashed robalm's v30F ROM.
Guess what, exactly the same.
On both variants, the phone got rather hot during the "optimizing app x of 190" screen, but never rebooted, only after I unlocked the SIM.
Let it sit overnight on the unlock screen, no reboot at all. Unlocked this morning, added my google account, rebooted - same thing again.
It's starting to drive me crazy, now it froze right in the middle of setting up the google account after another clean flash.
Is the phone prone for repair, or can anyone think of another solution to this weird issue?
Edit: Fun fact: if I manage to do the lock screen swipe before the SIM lock screen comes up, the phone reboots instantly as well.
Edit2: Followed the instructions from this thread to go back to completely stock v20T. Rebooted after optimizing apps before I could even choose a language, ran seemingly fine after this, started bootlooping after the first manual reboot. A full wipe later (volDn+Power) it at least boots. What the hell?
Thank you and best regards,
Sub

I have similar problem. Cant connect issue with exact cause, but it restarts almost every few minutes of use. Camera launch causes restart almost immediately. Phone is unusable. My VolDn button is not working so I'm currently a bit afraid to try anything new... I updated from Fulmics4.1 (i havent got reboot problems since last 1,5week ago) to 5.1 but issue persists even after full wipe. Seriously dont know what to think about it.
At first I thought that reboots are caused by low power (much more frequent with battery under 30%), then maybe big cpu load or high brightness.... now basically everything causes reboots. Im really annoyed this phone been crap since day one...
I havent tried your sim unclocking method as my doesnt have pin security etc. Let me know if you will find out solution.

foxracer89 said:
I have similar problem. Cant connect issue with exact cause, but it restarts almost every few minutes of use. Camera launch causes restart almost immediately. Phone is unusable. My VolDn button is not working so I'm currently a bit afraid to try anything new... I updated from Fulmics4.1 (i havent got reboot problems since last 1,5week ago) to 5.1 but issue persists even after full wipe. Seriously dont know what to think about it.
At first I thought that reboots are caused by low power (much more frequent with battery under 30%), then maybe big cpu load or high brightness.... now basically everything causes reboots. Im really annoyed this phone been crap since day one...
I havent tried your sim unclocking method as my doesnt have pin security etc. Let me know if you will find out solution.
Click to expand...
Click to collapse
Try a new battery

Anik49 said:
Try a new battery
Click to expand...
Click to collapse
Just received the device back from LG, they replaced the mainboard, even got a new IMEI and v30c preinstalled.
It is the same case, with the protective glass on top and a dent on the left plus the 2-3 micro-cracks around the frame.
Not sure if they swapped the battery. The problem showed up again with anywhere between 50 and 15 percent battery left.
Unfortunately I only tested it after leaving the shop, after a long walk to the bus which I caught just in time.
Setup assistant completed -> reboot.
Google setup nearly completed -> reboot.
Removed SIM and MicroSD, started phone, started camera, made a movie -> reboot.
Wiped again (strange enough, v30c only has 61 applications to optimize while v20* has 190+?), tried again, same thing.
Next, after letting the back camera take a movie for 2-3 minutes, I wanted to adjust display brightness to the max.
Result: see screenshot. This also happened with the cable plugged in.
I will return it for repair once more tomorrow...
Anyway, thank you for your answers
Regards,
sub

subworx said:
Just received the device back from LG, they replaced the mainboard, even got a new IMEI and v30c preinstalled.
It is the same case, with the protective glass on top and a dent on the left plus the 2-3 micro-cracks around the frame.
Not sure if they swapped the battery. The problem showed up again with anywhere between 50 and 15 percent battery left.
Unfortunately I only tested it after leaving the shop, after a long walk to the bus which I caught just in time.
Setup assistant completed -> reboot.
Google setup nearly completed -> reboot.
Removed SIM and MicroSD, started phone, started camera, made a movie -> reboot.
Wiped again (strange enough, v30c only has 61 applications to optimize while v20* has 190+?), tried again, same thing.
Next, after letting the back camera take a movie for 2-3 minutes, I wanted to adjust display brightness to the max.
Result: see screenshot. This also happened with the cable plugged in.
I will return it for repair once more tomorrow...
Anyway, thank you for your answers
Regards,
sub
Click to expand...
Click to collapse
It's a common thing if you use camera specially if you take video in 4k mode your phone heat up and you can't use full brightness in stock rom it's a feature try moded thermal config...also try new battery if battery percentage suddenly dropped it seems battery issue because i face the same problem....

Anik49 said:
It's a common thing if you use camera specially if you take video in 4k mode your phone heat up and you can't use full brightness in stock rom it's a feature try moded thermal config...also try new battery if battery percentage suddenly dropped it seems battery issue because i face the same problem....
Click to expand...
Click to collapse
I used to have thermals installed, the 75 dregrees Celsius variant, iirc.
Everything else was at stock, except for one short excursion to CM12 and one to ... some custom ROM.
Think I never actually took 4k videos, and the first 1,5 years the phone got a bit warmer but never really hot. Only recently it started to get really hot especially when using the camera, this also consistently was what could cause the reboot loops for sure. Other candidates were a few games which use more processing power like Alto's Adventure.
The battery drops by 2-3% after a reboot, because of the load the phone has (and the heat it develops during boot).
Anyway, I added the screenshot to the next repair request, and the woman at the counter said they'd look into the battery specifically (it seems to give out too much voltage, she said), but also check everything else once more.
I'll let them repair up to three times, then ask for a replacement, should be legal within 2 years after purchase in Germany.
Also, next time I'll take the 15 minutes (before doing a 1h/direction trip) to factory reset the phone, set it up and start the camera. If it reboots during any of this -> return, repeat.
Regards,
sub

Received my phone back from LG, finally.
Battery's broken - it outputs too much power.
Ordered a new battery and just put it in, so far no reboots during setup.
At least this got me a new mainboard and new IMEI
Regards,
sub

Hahahahahahahahaha
I just wondered why the phone shows 25 GB free everywhere, even without SD.
Turns out, during repair instead of replacing the 16GB/2GB board with an identical one, they installed the 32GB/3GB board
\o/ for LG

The slow death of my Note 4

Hello!
Everything was working fine until my phone started acting up about 6 months ago. The screen began to become unresponsive, apps crashed when switching between them and random reboots occurred frequently. I thought back then it had to be software related, so I completed multiple factory resets, and completely removed everything on my phone. It became slightly more usable, but these crashed and random reboots still occurred.
Last week, my phone continued to reboot, but a new problem occurred-it no longer would turn on after the reboot. I tried plugging it into the wall, pressing the volume down + home + power to force bootloader mode, but it wouldn't turn on at all. The fix was I had to remove the entire case, take out the battery and put it back in the phone. After that it would turn on, but only for a few minutes before another random reboot occurred and I had to remove the entire battery again. My phone is now virtually useless as I cant before even the basic functions, calling and texting without it becoming unresponsive or shutting off and not turning on.
I narrowed it down to the eMMC chip. I am almost certain that is corrupt, because during some of the reboots it would fail and throw me into download mode with the error:
mmc0_read_fail
or something along those lines. My last attempt at recovering the phone was to the stock rom PE2 with a PIT file (I had created before I started flashing custom roms). Each time I would attempt to flash with ODIN it would result in a:
mmc0_write_fail
However, I was finally able to get the PIT and PE2 firmware to flash. Now I have a half-working phone that will randomly reboot still and in order to turn it back on, the battery has to be pulled out for a minimum of 15 seconds.
New Issue I just noticed: When the screen turns off when the phone is inactive, it won't turn on again after pressing the power or home buttons. Only solution to this is once again, pull battery and hope I boot into system again.
I am pretty sure there is no fix to this problem on the software side, but let me know if you have a suggestion! Thanks!

Same situation. This thing is a lemon!

Sounds like hardware failure.
Replaced the battery yet? My original didn't last fifteen months before it started shutting the phone down. It's the first thing I think of when someone reports having to pull the battery.
Are you checking battery capacity before the battery pull by plugging in when it shuts down? Mine showed 0%. Before the shutdown, it may have indicated as high as 30%. It gets worse.
You didn't mention capacity when plugged so I thought I'd ask.
Sent from my SM-N910P using Tapatalk

One of my note 4 had same issue. Its a hardware issue. I was able to get the phone working by using a heatgun on the motherboard to try and reflow the solder on the chips. The phone works like brand new after the heatgun but the phone would only work for like 3 or 4 days before crapping out again. Ultimately ended up buying a used motherboard on ebay with a clean esn and its working perfectly again.

My wife's Note 4 started the random reboot thing and screen being unresponsive thing last week. She said it randomly started after installing Snapchat, so she uninstalled it hoping that would fix it. It didnt. I put a new battery in it thinking the original was bad, but still same issues. Then did a factory reset but that didnt work. After a lot of searching I stumbled on to someone who mentioned downloading an app called Wakelock. I did and phone has been running smoothly for several days now.
I also recently did the most recent update hoping that would fix the issue, it didnt but during the install I did get one error of emmc read failure or something like that. May just order a used/new motherboard just in case.

Just be careful when swapping out the motherboard as it essentially is taking apart the whole phone including the removal of the LCD.

Random Reboots?

I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?

I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.

I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:

have you downgraded?
and can you help me with my problem?[

AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.

ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic

I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.

Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app

adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)

Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.

My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.

Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.

Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.

k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.

Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.

OnePlus 3 issues

I'm having the following issues with my OnePlus 3 (stock recovery, no root):
15 November: last known date without any issues
16-18 November: when I played games I noticed that screen won't rotate even when auto rotate was ON
19 November: I wanted to click some pictures when the camera app just stopped working
Tried rebooting and clearing cache, but didn't work
Thought a software update might fix these problems
20-27 November: when I answered calls the screen won't turn off. That's when I realized that all the sensors on the phone had stopped working (no lift up display, motion sensors,etc). Read online that I could get the official Oreo update just by changing my VPN to Germany/Canada. So I did the same and upgraded to Oreo
Still the issues were there and battery drain was significant. The phone would reboot on its own.
On contacting OnePlus support they asked me to do a hard reset which seemed to work only for 3-4 days
28-29 November: the sensors stopped working again & again and I did a hard reset every time
In the end the phone switched off and the white notification light was on continuously. Pressing or holding the power button didn't work. Contacted support
2 December: through a remote session the OnePlus support installed Oreo again and on rebooting I got DM-VERITY error. So the support asked me to visit a Service Centre
3 December: I visited the SC where they concluded it was a hardware issue (motherboard: 17000/-) so I asked them to just roll back to OOS 4.5.1. Worked fine for 10-11 days
14 December: started rebooting randomly. Noticed that the phone would hang and reboot when using the camera (in WhatsApp, CamScanner and stock camera), maybe I'm wrong.
So now there's minimal usage of a phone with such high capabilities knowing that I'll have to do a hard reset once a week.
How can it be a hardware issue if the phone works fine for 4-5 days after a hard reset before breaking down again? What does that white notification light mean? Any help would be greatly appreciated

"3 December: I visited the SC where they concluded it was a hardware issue (motherboard: 17000/-) so I asked them to just roll back to OOS 4.5.1. Worked fine for 10-11 days"
There is your answer, there is a problem with you motherboard, you need to get it replaced, we cant diagnose a hardware problem here!

How come it works normally for a week or more if there's a problem with the motherboard?
And a hard reset seems to return the phone to its normal state.

Shmt_18 said:
How come it works normally for a week or more if there's a problem with the motherboard?
And a hard reset seems to return the phone to its normal state.
Click to expand...
Click to collapse
That just means that it is faulty and will fail after some time. This most likely means there is a bad memory sector on the board. As suggested. Get it replaced or you will keep having these issues.

Okay. Thanks for clarifying.
May I know what may be the causes for the motherboard damage? How common is it that a motherboard malfunctions?
Because there was no physical damage at all. Thanks again!

Shmt_18 said:
Okay. Thanks for clarifying.
May I know what may be the causes for the motherboard damage? How common is it that a motherboard malfunctions?
Because there was no physical damage at all. Thanks again!
Click to expand...
Click to collapse
See that is the thing. China has no real quality control standards. So it could just have been a bad board. If you look around you will see that a range of random issues seem to pop up over a short time. Yet some are just fine. Like mine. It had a faulty USB port from day one to the point that I knew it was gonna fail. (expected) So I am replacing it.

SMT700 screen flicker & reboot issue - kinda solved

It started about 8 months ago, in retrospect, after an OTA update. I'd be looking at some app when the screen would flicker and shortly after it would either go blank, reboot or simply turn off, it was maddening and I thought the end of my little tablet. I tried a couple of different things, thinking that somehow the bootloader got corrupted I reflashed that, didn't work. I then flashed the previous version of the bootloader, that really didn't work so flashed back. I'd always kept the tablet with the stock Samsung ROM so flashed the latest Lineage ROM (great piece of work) but that didn't help and actually made it worse, when I would reboot it seemed like it would immediately flicker when things were updating, it wouldn't stay on for more than a minute. I read about the potential for cracked battery leads so changed the battery and reflowed the solder around the terminals, that didn't solve the problem either. After that I started to suspect some kind of memory/software issue so in desperation I flashed it back to the beginning of time, the original Samsung ROM and that worked. I have the TAR if anyone needs it just let me know. After you do this your back to Android 5 and you'll notice that it will notify you of OTA updates, I updated BUT I found that past the 4th update the flicker came back, this might just be an issue with my tab but just be aware. I only use this now to read the news or my Kindle books, I did notice that some apps would trigger the flicker like My Radar or Zillow so I uninstalled them.
Hope this helps.