Note 3 Neo (SM-N750) keeps getting bootloop after a few days!? - General Questions and Answers

Hi,
Since lollipop was not available in India, I installed the russian 5.1.1 rom in feb 2016. Everything was smooth and I had no problems with it. Immediately after flashing the rom, I rooted it and put twrp recovery. I also uninstalled all the bloatware using ES file manager. I didn't have any problems with this russian (the rom's title ends in SER) rom till August.
In August, the phone started losing battery rapidly, the smaller (1300mhz) CPU would not goto deep sleep for some reasons. The phone would be shown as awake constantly in the battery graph on few days. I couldn't find any culprit from the battery graph, even wake detector apps didn't find the reason.
I knew the problem must be rom related, so I downloaded the Indian version of 5.1.1 and installed it. I again put twrp and rooted it, removed bloatware using ES file manager. No battery problems anymore, the phone would goto deep sleep always, as expected. BUT, as soon as I finished doing some root level activity, the next reboot (done manually, it would never crash on its own) would result in bootloop.
The bootloop goes like this, First the "samsung note 3 neo" logo appears (as expected), then the Samsung logo flashes BUT the samsung jingle doesn't start with this animation, the logo keeps flashing for around 5-8 seconds, THEN the samsung jingle starts, which only plays halfway when it reboots, this loop keeps repeating unless I pull out the battery!
I can/could always solve this bootloop by restoring my previous twrp DATA backup. Occasionally I would restore the system as well, but a basic twrp data restore is enough to end the bootloop problem temporarily.
I uninstalled the Indian rom and put the russian rom again 2 weeks back. For the battery problem, I installed "kernel aduitor" app and put the smaller cpu on powersave profile. This solved the battery problem.
Yesterday, after killing tasks in "ES task manager" (I don't remember doing anything else specifically root related), I restarted it manually and again got the bootloop! Earlier I never got bootloop with the russian version, this was the first time.
What could be the CAUSE of bootloop? I'm tired of twrp data restores repeatedly, I need a cause and/or solution badly!
I suspect it to be a hardware problem. I do wish to downgrade it to 4.4 stock rom to see if the bootloop is lollipop rom related or not, but I couldn't find decent stock 4.4 rom sources. Also there's the risk of losing EFS/IMEI while downgrading.

Hello
We are same problem. Have you resolved it already? I hope We can fix it.

Related

Still Reboots in Marshmallow

Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360
Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.
Likely defective power button
My nexus 5 32gb is also randomly rebooting on android 6.0
The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.
There is no random reboot software bug, only faulty key
GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.
its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.
SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.
i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).
I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.

Galaxy S6 - freezing and rebooting 50+ times a day

I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Maybe a battery issue?
a friend just gave me his very same model phone with the very same issues.. if I find out anything I'll tell you here, or if you solve it first please write down what you did.
Thanks Vibbuz.
I've been trying to download a stock firmware to flash via Odin, but download speeds from Updato are really bad.
So I managed to flash a firmware after installing Odin on a Windows laptop (painful trying to get it to work on my Mac)
Firmware installed OK, but after boot I was getting a constant "com.sec.epdg" pop-up box that wouldn't let me use the phone at all. Not sure if that's due to the tsar3000 firmware?
Wiped the cache and did a factory reset after booting into recovery, and now it's stuck in a boot-loop again (95% of the time it hangs at the Samsung logo animation)
Just tried using SamFirm v0.3.6 to find the correct file. Downloaded a 4gb file, but several attempts to extract only gives BL, CP, CSC files but no AP (throws up an Unknown Error during process).
So still stumped!
Yet another update. Left Updato running overnight and downloaded a firmware.
Flashed it with Odin, claims to have succeeded but phone then reboots and hangs at "Erasing" stage (Android logo is spinning, then stops)
I'm starting to think it's pretty broken...
I've been having this exact same issue since June. If your phone happens to boot try activating power saving mode (to reduce cpu speed) as soon as possible.
It seems that doing that diminished the frequency in which my phone rebooted. If it also helps you it might be a faulty battery that can't provide enough voltage. (I'm not 100% sure on this part though, just thought of it because of the apple batteries drama)
Please post your results! Looks like a lot of people are affected by this and it would be great if we could find the cause of the problem.
I just read your thread actually! Sounds very similar to mine.
I've got nowhere. I don't think it's hard-bricked as I can still access Odin mode on the phone, and sometimes boots to Recovery, but it freezes and various different points and is currently unusable (either freezes at Samsung logo, "Erasing" part after installing firmware, or once it started to run though new device setup then froze).
Went ahead and bought an S8, but still want to fix the S6!
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Does it have twrp? Try a non stock ROM and kernel
So did anyone manage to find an issue in this rebooting. I am having the same issue.
damir_nis said:
So did anyone manage to find an issue in this rebooting. I am having the same issue.
Click to expand...
Click to collapse
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Hello,
anyone found some kind of solution? Happened to me also - freezing, restarts and then my S6 stopped working.. Sometimes I can boot to recovery menu, sometimes it boots up to android (and then freezes again), but the chances are almost non existing. Service man told me the same thing as @ghasemzm - eMMC failure. Yes, it is completely possible, but i don't wanna believe it, because they only tried to reflash the rom. I've made some "google research" and found that there were some issues in power IC on S6/S6E. Could this be related to it?
ghasemzm said:
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Click to expand...
Click to collapse
Will test the theory and let the group know.
So i have installed philipines latest update 6.0.1 i think with PIT file provided on Sammobile.
I have tested it for a day with normal ussage like i set up every other phone and it still continued restarting.
Figured out let me test with no google account signed in and the phone is working perfectly. For a full day.
So i dont know what the problem is but i will try again with google account tomorrow for a day see what happens.
After that will install 7.0.1 uk update with PIT file for it and test with that.
I have the same problem and I am quite sure that it is the mobile hard drive.
I tried to use F2FS but didn't find a working rom for that.
Samsung refused repair because of root.... Never Samsung again!
same issues here - any solutions found? My best guess is hardware fault...

bootloop after weeks of normal usage

bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed

Debugging J7 Prime Restart issue

Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S
Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.

J700m rebooting problem

yo guys!
So, months ago I flashed a custom ROM on my j700m, it was EnigmaUX, it worked fine for quite a long time, but I had a issue with it that bothered me: sometimes, when the phone rebooted, it just wont accept my pattern and kept saying it was wrong until I rebooted the phone again. With that in mind, I decided to flash a new ROM to try fixing this problem, I flashed the NOUGAT 7.1.1 - SE 8.5 & GAMING and along with the previous issue I had, I also got a new one: my phone kept rebooting randomly, sometimes the system wont even start back, I had to remove the battery in order to start, it's like the phone reboots in the middle of the start process. My next attempt was to flash the stock rom, which is: J700MUBU2BRC2, and the problem is still happening. The pattern bug stills happens too, that's the weird thing, I removed the ROM and I still have the same glitch... like it was not completely removed.
Does anyone have any ideia what's causing that?

Categories

Resources