What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
DeafScribe said:
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
Click to expand...
Click to collapse
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Worth a try...
KennyG123 said:
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Click to expand...
Click to collapse
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
DeafScribe said:
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
Click to expand...
Click to collapse
I just hooked one of my old ones up to freedompop through the BYOD program. Nice to see the old girl getting use at least as an emergency phone.
Related
Hey everyone, I looked around and didn't find anyone having my particular problem, but If I put this in the wrong place, or someone has already solved it, just let me know. Don't want to waste your time!
I got my DINC the day they came out in stores...the first one my local store sold in fact. It was working great, but I hated the bloatware and the fact that the Bluetooth stack was not up to date...couldn't connect with a new hands free speaker phone I just bought (Parrot mini-kit slim). I had occasional random reboots, but not too many. Once or twice a week maybe.
So when the unrevoked one-click came out I tried it. Worked great.
Then I started trying ROMs. With everything I've tried I get random reboots...a lot of them. Sometimes it reboots once and works fine for a couple hours. Other times, it will loop until I do a battery pull. When it loops it will sometimes make it all the way to the lock screen, sometimes it will only make it to the boot animation, and sometimes it won't get past the white HTC screen.
I've used a couple different nightly builds of CM6, with and without google apps. I've used Skyraider 1.8 and 1.9 with and without sense. I've tried "touch of photons". Same results and activity on all of them.
Last night I gave up and downgraded to unrooted 2.1 with sense...factory fresh. I reformatted my SD card with the phone, reformatted the phone storage, and I've done factory resets. It still isn't working right.
At this point, I'd be happy to get it back to pre-Unrevoked and just wait for the official OTA Froyo which is supposed to come out soon. Rooting and using a stable rom is fine with me too. I just need a phone that works consistently.
Any ideas? I'm pretty desperate.
sounds like you needed to return it and get a new one since it was doing random reboots from the day you bought it.
have you used any of the hydra kernels to try and OC it, the 1.15 OC would cause mine to reboot. a good stable rom that i tried was JagerRom, 1.7.4 is without sense, and chocolate is with sense. don't try the OTA one because that is for people who updated to the OTA leak and im going to assume you aren't one of thoes people. haha
http://incredibleroms.com/roms/jager/
hope this helps
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Does anyone know if there is something that could have gotten messed up with unrevoked or the roms I tried?
Is there another downgrade method I can use? I just installed the PB31IMG.zip you can find in a few places out there...is there a known reliable source for the downgrade zip?
If I can avoid fighting with Verizon on this I'd like to. I'm obviously outside my 30 days, and I don't want to wait a week or 2 or three or more for a new incredible (if I can convince them to get me one). I'm not even sure warranty or Asurion will do anything with this kind of a problem either...I fear I'm stuck with a $500 reboot roulette machine.
re
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
I also have had a reboot issue. I rooted the phone the day I got it and installed a senseless rom. It worked perfect the 1st day then started into a downward spiral of reboots till it went into a full boot loop. I did a nandroid back up of the original rom. No real issues since. Im still rooted and have only had one random reboot in about a week that I know of. I know the first issue was because of the rom but what causes the random reboots. Is it aloss of signal? Im a noob so Im just trying to get some insight.
Im on #2
I got my 2nd Incredible on Friday. Prior one would just get hotter and hotter (possibly due to signal issues) until it would enter a reboot loop. Hoping # 2 fares better.
johnsquared said:
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Click to expand...
Click to collapse
ya everything works in jager. but from what everyone else is saying it seems like it could be the signal (or lack there of) that's causing the reboots. have you tried the hybrid prl? it uses the verizon and altell towers instead of just the verizon ones. i haven't tried it because im in cali and there aren't any altell towers near me, but if your stuck with the phone you might as well give it a shot if you live in the supported areas. good luck man.
Link to PRL thread:
http://forum.xda-developers.com/showthread.php?t=723829
If you don't have problems with signal don't bother with the hybrid prl... it kills your data speeds because it switches you from Verizon data network to Sprints data in most areas. I know in the Carolinas phones randomly reboot a lot because thats Alltel country and phones don't work properly without the hybrid. But down south its mostly Verizon. Out west Texas/Ok is mostly Alltel.
But man honestly - I have the same issue on custom roms. My stock Sense rom does fine though. Sometimes I'll be on a custom rom typing a text and the keyboard just freezes and its over. lol nandroid time to me - I can't take the reboots but hate not having the features of newer software.
re
i have tried the hybrid prl and it did not help my rebooting issues.
i have also tried switching to the the cdma codec to -b the higher quality compression... with no luck in fixing the reboots.
I have also made sure there was not an issue with an app causing it, i have tested mine with a clean / factory reset with absolutely no apps installed.
I have had 100% good luck with the leaked ota update, the one upped the camera to 720p recording as well as a hand full of other fixes, and not once did my incredible reboot or crash.
I'm pretty confident that htc has fixed this issue for me, once they drop the 2.2 update that everybody seems to be speculating will be released in a handful of weeks.
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Me Too
johnsquared said:
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Click to expand...
Click to collapse
Same EXACT thing happened with me and telesales. No scripts, no hard reset, no task killer; NOTHING. Said "my phone gets hot and reboots" and they said (last Thurs), let's get you a replacement overnight so you can try the new one out of the weekend. No muss, no fuss. Got here 10:30AM the next day, and my evil super-heating 4-to-13-reboot-try prone phone is going back.
sprintrjm said:
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
Click to expand...
Click to collapse
I don't believe towers/signal would have any effect on shutting down or booting. Basically once you're on a current PRL, you really shouldn't even have to update it. Unless you're having that poor service deal where an Alltell/Vzw hybrid would benefit you.
Has anyone else had this problem? Mine seems to randomly restart every couple of days. Most recently last night at 8:26pm. I had just hung up a phone call and pressed on another contact to dial someone else. When the screen was supposed to change to the connecting screen instead it reset and went through the Sprint boot screen. After 2-3 minutes it was back to normal.
I am on 2.2 (unofficial)
Looking for suggestions.
Ben
Are you on 2.2 or what? I know this was an issue when the EVO first came out, not sure if any OTA software updates fixed it (mine stopped happening when I rooted and went to another ROM)
Yep left that out. I am on 2.2 unofficial release.
wipe, wipe, wipe
It's your ROM/kernel. Simple as that.
Has anyone suggested you wipe and reflash the rom/kernel yet?
Sent from my blah blah blah blah
Mine has been doing the same thing at least once a day. I have tried Damage Control 3.5, Cyanogen RC1, and Sprint Final 2.2 Rooted. I wipe between each flash (factory, cache and Dalvik). I upgraded my recovery and even switched recovery because I read that one of them doesn't wipe Dalvik properly. Nothing seems to help. I swapped batteries tonight to see if maybe the stock battery was to blame, and it rebooted with the after market battery. I have been watching my temp closely thinking it might be overheating, but it will reboot at under 110 degrees. I reflashed the radio to the latest, wiped and reflashed DC 3.5 and it rebooted. I am now trying to run it without 3G on to see if it has anything to do with the 3G radio.
Not having much luck yet, but I will keep trying to isolate the problem. Any other suggestions besides wipe and reflash? I am running stock kernel.
are you oc'd? overclocking too high can result in random reboots.
Nope, no OC.
I just RUU'd back to stock, non-rooted 2.2 and it rebooted within 10 minutes of usage. I was actually trying to update the PRL when it rebooted. This is getting frustrating.
Flash the eng PC36IMG
I'm in the same boat as you, and I have also wiped and cleared everything multiple times.
I did notice it happens most when phones been locked and im going to unlock it, or when I plug it into the car charger.
also after it does this if I have the USB plugged in it wont go past the first boot screen until I unplug it /shrug I havent the slightest as to why.
Same
I actually had zero problems up until about the time that the official dropped, I was running multiple versions of 2.2 unofficial and out of no where (after flashing a rom based off of the 2.2 official) the phone randomly started but it was still usable, after some time went by and I re flashed back to nightly release 8/4/09 cm, it went back to only doing it about once a day, then literally out of no where it started constantly. It restarts 3 times in a row never getting past the htc screen, and then gets stuck at the htc screen. I have to pull the battery for about a day and then it will work for a few hours before doing it all over again. I tried multiple roms, multiple kernels, and both recoveries, after getting completely fed up with it, I relocked nand protection and restored back to stock 2.1......updated all the htc updates, and then its back to doing the constant reboots, called bestbuy(where I bought it from) and because I got it on release day and didn't purchase the N.E.W (insurance) at the time (it was 14.99 per mo) or the GSBTP their not willing to do anything. Fought it out with sprint until I got to a supervisor for account services (or something like that) he advised me that maybe rooting it would help, that I could drive 2 hrs to the closest sprint repair center, or contact htc. He said he would love to replace the phone but their sold out, I suggested maybe replacing it with the epic, but apparently they tried to pre-order that phone and their already extremely oversold their stock weeks before its release date and that the pre-order only lasted about 18 hours before they were 25% oversold on their stock. So I contacted HTC and they said they would be more than happy to have it sent in and repaired, but heres my issue, its most likely a software/radio/firmware/wimaxradio issue, so htc needs to figure out something or hopefully one of the dev. here will realize that this is a huge issue effecting a lot of supersonic users....so where do we go from here? I want my 200 dollar phone working again, please someone look into this and figure out whats going on with us that have no where else to turn, PLEASE i BEG you!!!!!
update
So after battling it out with sprint i decided to drive 2 hrs to the sprint repair center in this area....they literally looked at it for 2 seconds and made sure that it wasn't rooted....and said a new one(manufactured) would be here in 3 days. This will be my third evo since launch date...so i expressed my concern to the manager at the sprint store, and she said that if this one still had problems she would authorize it to be exchanged for an epic (once the epic hype calmed down, and once it was released), just FYI if your experience the same hell i have, just make sure you unroot/relock the phone, google how to do this, and take it to your local sprint store/repair center....thanks!
You know em, you love em, random semi-reproducible problems!
I have been playing with my phone and enjoying the freedom of root access every since the original 2.2 OTA root method was posted (the downgrade unrevoked method). Its been great, but I started to have an annoying reboot issue that popped up every now and then. At first it was annoying, but now it is getting worse.
It SEEMS like it is temperature related. It started happening while the phone was charging, 4g was on, and wireless tethering (pre8) was running. First the connection between my computer and the phone would drop, then I'd reconnect, surf for another 5 mins or so, and the phone would reboot. Battery temp was reporting ~44C. After I let the phone cool down everything was fine.
I found that if I didn't have the phone on the charger or if I put the phone (battery side down) on top of a cool metal surface, the problem would not arise.
But then it started happening more often and under circumstances where it had previously not had any problems. Things like turning off my alarm, answering a call, playing alchemy. Under those cases, the battery was sometimes warm, but usually cool.
Last night it entered a reboot loop, where it just returned to the white HTC EVO screen over and over and over. It eventually turned off and the green light began to flash. I could not boot it up until I removed the battery and cooled both the phone and battery down. It was charging with a file downloading over 3g.
The problem is defiantly getting worse.
--------------------
I know that people are going to fire at me to wipe and reinstall (like in all the other threads) but that is the craziest part: I have. Many times. When it started to happen I thought it was the ROM, so I would change ROMS when it happened, but now I realize the problem is independent of the ROM in use.
I have used (and hit rebooting issues while the batter is hot and cold)
Stock (rooted) 2.1 and 2.2
Ava V5, V6, and V7
Fresh 3.2 (and a previous version, I don't recall which)
BakedSnack 1.6 and 1.7
Evo Zone 8.29
Vaelpak 1.3 and (I believe) 1.2
A couple of Virus' ROMs
I have used the stock 2.1, 2.2, and 3.2 HTC kernels and King's #s 6, 8, and 5, all with the same problems.
I even nandroided to backups that I had previously NOT had the issue with, only to immediately reboot. It really looks like software is not the issue, but I'm not sure.
As you may gather from this, it has been an on going issue for quite some time. I always do a full wipe (all caches, dalvik, et all) between ROMS. I'm out of ideas, do I need to S-ON and OTA then return this bad boy to sprint? Any ideas?
EDIT
Forgot to add, I am using ClockWork recovery, and flashing ROMs manually (through recovery, not a ROM manager app)
Quick bump for interest and posible solution. I'm pretty sure it's a hardware issue, but I just want to be sure.
Even though I'm always going on about how clockwork always works fine for me, and wipes everything correctly, I'll be the guy here to suggest trying to flash with amon ra a few times. If you still run into issues, I'd say that your battery is borked. But before returning the whole thing, maybe pick up a cheap extra battery off of ebay, and see how it works with that?
Just so I am clear on what to do, if I want to return the phone for service, I need to run the S-ON tool from unrevoked, then accept the OTA and I should be good to take it in, right?
Yes flash s-on then run RUU
i am having exactly the same issue
i've been on cm6 for over a month and it started about 2-3 weeks ago, at first i thought it was the temperature too but recently it started rebooting at completly random moments. I flashed baked snack yesterday and put a new battery in, same thing, random reboot
i flashed deoxed newest update with no mods today to see if that would fix the issue, 3 minutes after i did, i was signing in to my google account - reboot
turned the phone on, and 1 minute later reboot and loops....
any ideas?
using RA recovery btw, wiped everything before i flashed.
It's the HARDWARE
Guys,
Just thought I'd share a little of my experience with this phenomenon.
I had a HW003 Nova since the release of the Evo. I started experiencing random reboots every so often about a month or so later.
These progressed regardless of what version of Android, or which rom, or which kernel, bootloader, OTA update, S-ON, S-OFF, Bone stock or rooted.
After barely managing to get the phone back to it's factory state, I replaced it no questions asked on my second visit to Sprint repair center.
My refurbished replacement (Also HW003) was fine for a whole 5mins before it started doing the exact same thing. I gave it back to the technician, and put in the order for my second replacement. As per the advice of the technician, if my next replacement has any problems at all, I'm supposed to call Sprint customer service directly in hopes of a longstanding solution (read: Ask for a brand new phone)
Not trolling or starting ****, because I love my Evo, but let's be realistic.
These phones are built like garbage. At least the original crop of them is.
They use some good parts, but they are manufactured in a cheap manner.
Probably in cheap factories using cheap labor, and cheap materials.
While not every Evo is junk (my girlfriend hasn't had any problems with her's in over 3 months) you have to figure that one out of every few thousand is probably going to have some kind of defect, be it light leakage, bad screen grounding, broken USB connector, or even the infamous nonsensical, irrational, arbitrary reboot/power-cycle.
Sounds like what was happening to me too. I just took it to repair center and after a couple trips they replaced it. First they put a new battery in, said they couldn't reproduce the reboot but in three minutes I did. After that they ordered a new one.
In the beginning it was so random and appeared to be a heating issue too, then it just got worse and worse. Seemed like I could use the phone without issues if I wasn't taxing the phone too much but it progressively got worse and got to the point of it being maddening. Then it was hanging on splash screen and boot looping. Uprooted and took her in. Sounds like thats your best bet. I tried different ROMs, stock, etc etc.
Just take it in after doing what you need to do. Good luck.
SWYPED from my SUPASONIC
hey, i have had my Galaxy S3 sence black friday of 2012, and it is not rooted or anything. but just recently within the last few weeks, it has randomly restarted, like im texting or playing on FB and then screen goes black then i see samsung logo. any sugestions on how i can fix this?
Mine recently started doing the same thing. After being rooted about a year ago, and being stable on the same ROM for the last 6 months or so, it randomly started rebooting itself 10-20 times a day.
I tired installing a stock ROM, stock kernal, etc. but nothing helped. I eventually unrooted it using QBKing77's video (on this site) and used Odin to install the stock tar image. This was in preparation to take it back for what I could only assume was a hardware issue. After a *lot* of automatic OTA updates (maybe 8 -10 or more!) it seems to have solved the issue. The phone has been stable without a restart for the last 48 hours.
In addition to that, I also pulled my sd card and ran it through the windows disk tools which said it found a few errors and corrected them. So at this point I don't know if it was ROM/kernal related, card related, or a perfect storm of a combination of each. I'd suggest you pull your sd card and use windows to check it 1st since that'd faster and easier. If that doesn't work, unroot.
I plan on waiting another day or two before I unroot again, just to be sure it's still stable. Hope this helps.
** Just saw that you're unrooted. If you're still in warranty, take it back. If not, try rooting it, and installing a new kernal or ROM and see if that helps.
i am not in warrenty, i wish but im not. i dont want to root it,
Check if your battery is swollen, the spin test works pretty well if you're unsure just by looking at it. A swollen battery is one of the most common reasons for frequent reboots if you're running stock.
Power button failure known defect with S3. They replace them at Sprint. It's referred as Sudden death syndrome.
Sent from the future via Tapatalk 4
Hi there,
I have been having quite a few problems with my note 4. It keeps rebooting and gets stuck in a boot loop. Sometimes when it does come out of it, if the phone is put under much load it gets stuck. Then it reboots and is stuck again on the boot logo. I don't know if this is a software or a hardware problem but it has made it quite hard to use my phone. Any help is appreciated so thanks. On another note(no pun intended) which aosp rom is the best for note 4 right now?
P.S
I am new to this forum so if there has been any mistake I apologize in advance.
SkipDeath said:
Hi there,
I have been having quite a few problems with my note 4. It keeps rebooting and gets stuck in a boot loop. Sometimes when it does come out of it, if the phone is put under much load it gets stuck. Then it reboots and is stuck again on the boot logo. I don't know if this is a software or a hardware problem but it has made it quite hard to use my phone. Any help is appreciated so thanks. On another note(no pun intended) which aosp rom is the best for note 4 right now?
P.S
I am new to this forum so if there has been any mistake I apologize in advance.
Click to expand...
Click to collapse
id say run it back to stock you can start @ QB3 which is the latest 6.0 tar i seen around
once you go back to stock factory reset it from the actual phone itself and then take a few updates and see if you still have issues?
:fingers-crossed:
Tha_Dynasty2049 said:
id say run it back to stock you can start @ QB3 which is the latest 6.0 tar i seen around
once you go back to stock factory reset it from the actual phone itself and then take a few updates and see if you still have issues?
:fingers-crossed:
Click to expand...
Click to collapse
Tried that but it still doesn't work. I thought of using an another rom so I wiped the system and data and tried flashing, but the same thing happened in recovery. Just like before it got stuck and rebooted into a bootloop. Its taking alot of restarts and taking the battery out again and again to get back to recovery.
SkipDeath said:
Tried that but it still doesn't work. I thought of using an another rom so I wiped the system and data and tried flashing, but the same thing happened in recovery. Just like before it got stuck and rebooted into a bootloop. Its taking alot of restarts and taking the battery out again and again to get back to recovery.
Click to expand...
Click to collapse
yea id say flash maybe the Hybrid 3.0 OG5 rom
some how that tends to remap my partitions correctly and then go to stock.
For me, I started experiencing Random Reboots....My battery is new so that can't be the problem but most of the time it's when I'm under load or multitasking between tasks or just in general , I used google maps and it just flat out rebooted...
This was on QC1 Latest Stock Tar then Flashed TWRP 3.1.1.0 and then Flashed the QC3 Deodexed Debloated ROM.... when this would happen.... Stock Kernel, before flashing the Deodexed version.
None of this happened when I was using PJ1 or PK1, Stock Tars and then using the PK1 Deodexed Debloated Rom.
and going from there.
Note 4 Reboot
Same problem here. I just started getting these random reboots when the phone seemed to be under heavier load. As soon as it starts to reboot, it gets caught in a boot loop and it takes forever to get back up and running. Usually takes a battery pull and about 10 minutes of waiting with either the battery out, or putting battery back in and letting reboot boot loop happen until it gets to operating system.
The sad part is I just bought this one, to replace my 3 year old note 4 that got the dreaded MMC_Fail. I was trying to hold out on buying a new phone, since I love my note 4 with my Zero Lemon battery. However, it seems these good ol' phones are just beginning to die.
Anyone find a kernel or rom that has fixed either of these issues? Either the MMC_Fail issue or (my latest problem) the reboot, boot loop problem?
saaammme here
dickiedawildman said:
Same problem here. I just started getting these random reboots when the phone seemed to be under heavier load. As soon as it starts to reboot, it gets caught in a boot loop and it takes forever to get back up and running. Usually takes a battery pull and about 10 minutes of waiting with either the battery out, or putting battery back in and letting reboot boot loop happen until it gets to operating system.
The sad part is I just bought this one, to replace my 3 year old note 4 that got the dreaded MMC_Fail. I was trying to hold out on buying a new phone, since I love my note 4 with my Zero Lemon battery. However, it seems these good ol' phones are just beginning to die.
Anyone find a kernel or rom that has fixed either of these issues? Either the MMC_Fail issue or (my latest problem) the reboot, boot loop problem?
Click to expand...
Click to collapse
This literally happened to me today, I later figured out that I do have mmc issue aswell...beccause my phone would just randomly reboot on me and be warmer than usual...even when its not underload. I bought my note 4 Used but in, Near mint, good condition on May 28, 2017...and this is now just happening to me 9-25-2017, but back then i only experience few random reboots because i had a faulty battery....
1st one lasted me about 3 years and then began dying from MMC_Fail about 2 months ago. I thought of waiting and buying a new Note 8, but really like my note 4 and my 10,000 mAh battery. So, I found a used one online and bought it from a guy for $125.00 and its been working fine till last week when this whole mess started. I immediately flashed a custom kernel hoping to fix, but no luck. I am currently still using the phone, but get a couple reboots a day under heavy load and sometimes it takes a half hour to get it back up and running.
The one thing that strikes me as odd about this whole situation, is why all of us are having the same problems around the same time? Like Indaid this is my 2nd one and I don't think I'm going to invest in a third. Probably wait till Holidays or Black Friday to get a new Note 8 or maybe even finally make the dreaded switch to the new iPhone X coming out. (Cringe at the thought of not having my customizable Android) Ive never had an iPhone, not been an apple fan boy, but the wife and kids like em, so cross communication would be simpler, as well as app sharing I guess.
If anyone finds a fix, maybe removing latest security patch, or custom kernel or Rom, please let me know! Love my Note 4 and will rock it forever if I can. Sad part is my old Note 2 is still rocking with a ZeroLemon battery in it as well, but its just so ancient now. ..LoL..
My stock UNrooted Note 4 (with ZeroLemon) with T-Mobile started boot looping, and I tried clearing cache, and factory resetting to no avail, messing with it for days, lost all my data and photos too. I was considering flashing to the factory ROM when I tried changing back to the original worn out battery. That worked. No more boot loops. It works fine. I think Im going to buy a new stock battery. However, The ZeroLemon lasted for at least 3 years. Just a FYI.