I'm having major issues with my Note 4 across a variety of ROMs and kernels. I decided to post in general instead of a specific ROM thread because I cannot narrow down my problem for the life of me. Slightly different symptoms than other Note 4 failures I've seen lately, but many of the same.
A couple weeks ago I started to see the dreaded Note "mmc_read failed" message at times. Randomly reboots into download mode, displays the message, but I can reboot and the phone will boot normally. Some say this is a sign of hardware failing/failure. Haven't been able to correct it but it's rare that this happens. Maybe just a sign of issues to come.
The biggest issues:
—When in Android (OvrDriVE's 6.0.1 ROM, Note4UXEdge... and BeastMode and Xceed kernels), I get random hangs and reboots. When scrolling fast through Facebook, Instagram, often on Snapchat, sometimes just when Swiftkey opens and I'm typing, it'll hang for 5... 10... sometimes 20 seconds, I'll have to press buttons to get out of it, sometimes it'll just reboot on its own.
—Sometimes I'm just sitting down at my desk, the screen has been off for a while... the phone just randomly reboots out of nowhere.
—At times, it happens in the morning. I turn on my screen for the first time, open Facebook, scroll down... it freezes or restarts. (I say that to say... it doesn't seem heat-related. No load on the CPU, etc.)
—My battery will charge normally to about 85%... then it only accepts 120-220mA beyond that point and slows down the charge to a crawl. Yesterday I could barely get it to 89%. Perhaps an unrelated issue? But this JUST started happening in the last couple weeks. Seems very sudden since battery degradation is usually gradual.
So to troubleshoot, I wiped clean, ODIN'd stock EPG2 6.0.1 firmware. ODIN TWRP. That's it. No root. Restored my 80 apps from Play Store. Battery issue still remains... stuck around 85%. During restore, phone randomly rebooted a couple times. Aside from that, interface is snappy. No noticeable lags, hangs, freezes, and no restarts since. All in all, MUCH better performance.
Hopefully someone who knows a lot more than me can chime in and narrow this down a bit. The only thing I haven't really done is use the PIT file and repartition internal storage, but not sure if that would help anything. It just makes no sense that when I'm stock + TWRP, everything is mostly fine... but with root, a ROM, Xposed... it goes haywire.
I've encountered the same issue here, with stock EPG2 and also the dev-base 6.0.1 build flashed with TWRP. Seems like it's happening to a lot of folks.
Thing is, the other day I downgraded to DOK2 and installed Mega's PopRocks5V4XxXZ build of 5.1.1 and while the problem isn't as bad as any 6.0.1 ROM, I'm still experiencing long lags and occasional reboots.
I have not experimented going without root. I'm not seeing any battery issues. I don't use Xposed.
I'm thinking that it's time to try repartitioning with the PIT file. I really don't want to give up root -- I hate seeing all the bloat in stock ROMs and I need root to make the junk go away
SteveRiley said:
I've encountered the same issue here, with stock EPG2 and also the dev-base 6.0.1 build flashed with TWRP. Seems like it's happening to a lot of folks.
Thing is, the other day I downgraded to DOK2 and installed Mega's PopRocks5V4XxXZ build of 5.1.1 and while the problem isn't as bad as any 6.0.1 ROM, I'm still experiencing long lags and occasional reboots.
I have not experimented going without root. I'm not seeing any battery issues. I don't use Xposed.
I'm thinking that it's time to try repartitioning with the PIT file. I really don't want to give up root -- I hate seeing all the bloat in stock ROMs and I need root to make the junk go away
Click to expand...
Click to collapse
The battery just seemed normal charging to 80s and then I kept checking my phone and noticing it hadn't really gone anywhere. I just took a 3-hour nap and woke up and it was on 100%. So although slow (not sure how slow), it did reach 100 finally, so that's good.
My issues are still nonexistent with stock. I'm going to cf-autoroot here in a while and keep testing. Then add Xposed and test again to see what may be causing the issues. Perhaps I'll try a CM ROM as well, since the two ROMs I mentioned above are from the same base. Maybe I'll downgrade too. I was a big fan of Mega's ROMs on LP and KK.
I agree, a repartition would confirm it's probably a software issue. Haven't seen the mmc_read message in a while now.
My mmc_read errors have also disappeared.
I just noticed something -- in "About Device," my baseband is DOK2. Which is, in fact, the baseband and bootloader I flashed. However, Mega's ROM shows DOG1. I wonder if I should flash that baseband and bootloader?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm also kinda curious if EPE3 exhibits the same problems that EPG2 has.
SteveRiley said:
My mmc_read errors have also disappeared.
I just noticed something -- in "About Device," my baseband is DOK2. Which is, in fact, the baseband and bootloader I installed. However, the ROM shows DOG1. I wonder if I should flash that baseband and bootloader?
I'm also kinda curious if EPE3 exhibits the same problems that EPG2 has.
Click to expand...
Click to collapse
Hmm, yeah if you're still having issues, I'd say matching them up is a good place to start.
I just went to flash TWRP (for some reason, I guess it didn't take on the first go) and got the mmc_read. Rebooted back into download mode and it was fine. Flashed SuperSU and now EPG2 is still running great. Figuring out what else to do from here.
EPG2 was reportedly just a security update to EPE3 so, I'm not sure. EPG2 is really smooth for me now, still, with root... but one of the devs noticed quite a few issues once he based his ROM on it, so he went back to EPE3.
forbidinjustice said:
Flashed SuperSU and now EPG2 is still running great. Figuring out what else to do from here... EPG2 is really smooth for me now, still, with root
Click to expand...
Click to collapse
In my experiences, the lagginess and reboots didn't occur immediately. I could get through my usual routine of going through settings, installing my apps, and deleting the bloat all with extreme smoothness. The problems would begin appearing after I put down the phone for an hour or so.
In all my years of messing around with Android (started with a G1 in 2009), I've never seen anything like this. Makes me suspicious of Samsung.
SteveRiley said:
In my experiences, the lagginess and reboots didn't occur immediately. I could get through my usual routine of going through settings, installing my apps, and deleting the bloat all with extreme smoothness. The problems would begin appearing after I put down the phone for an hour or so.
In all my years of messing around with Android (started with a G1 in 2009), I've never seen anything like this. Makes me suspicious of Samsung.
Click to expand...
Click to collapse
Suspicious is right because none of this software chaos began to happen until the official Marshmallow firmware was released. It seems mmc_read has been around for almost 2 years though.
I keep swiping like crazy, opening apps as fast as I can, trying to put a load on the CPU to see if it will give me any issues... but, nothing. If no issues by the end of the night, I'm going to flash a random CM ROM and see what happens inside that environment.
Have you tried a lot of data traffic, like more Facebook?
SteveRiley said:
Have you tried a lot of data traffic, like more Facebook?
Click to expand...
Click to collapse
Sure have. That's what always triggered the hangs/freezes on OvrDriVE's EPG2 and EPE3-based ROMs. Now, no problem at all. Instagram pulls even more data than Facebook and even that's smooth. I've been scrolling both apps really fast and not one problem.
forbidinjustice said:
EPG2 is really smooth for me now, still, with root
Click to expand...
Click to collapse
I just noticed this from your post #5.
So you're rooted this time, and everything's behaving normally? What's different from the previous time when you were getting all the lags and reboots then?
EDIT: Nevermind. The difference is you Odin'd stock, whereas before you were on OvrDriVE's ROM. See, I've had these strange problems even when I Odin'd stock.
SteveRiley said:
I just noticed this from your post #5.
So you're rooted this time, and everything's behaving normally? What's different from the previous time when you were getting all the lags and reboots then?
EDIT: Nevermind. The difference is you Odin'd stock, whereas before you were on OvrDriVE's ROM. See, I've had these strange problems even when I Odin'd stock.
Click to expand...
Click to collapse
Rooted and all is well in the world. The difference is that I'm running a straight stock EPG2 firmware. I've been running OvrDriVE's Marshmallow ROMs and have also tried Note4UXEdge ROM. Again, I believe they are created from the same base. That's when the issues were happening. I kept blaming the kernel... but I switched from BeastMode to Xceed, same problems. Haven't tried AEL or Emotion though.
The next test will be to flash a ROM that I know isn't affiliated or related to either of the above 2. I'll see if I get the issues... then I'll know it's likely ROM or kernel related. However, others in OvrDriVE's thread aren't getting these issues... so it's really frustrating because he can't help. There's no hard evidence that it's the ROM's fault...
Which version of Odin are you using?
3.09 ... but prior to that, I was using 3.11.1, the newest release. I've never understood why some people use (and recommend) older versions of ODIN. Seems like they function differently or something?
forbidinjustice said:
3.09 ... but prior to that, I was using 3.11.1, the newest release. I've never understood why some people use (and recommend) older versions of ODIN. Seems like they function differently or something?
Click to expand...
Click to collapse
Take a look at this:
http://forum.xda-developers.com/note-4-tmobile/help/csc-folder-stock-mm-t3437091
First time I tried flashing stock MM, I used 3.09. You'll note that my result was a missing /system/csc folder and was experiencing several flash failures. The lack of a /system/csc folder meant that some T-Mobile specific functionality was missing. Another XDA member suggested that Odin 3.09 wasn't aware of the file cache.img.ext4 and suggested I try 3.11.1 Also had some flash failures, but this time cache.img.ext4 flashed fine and I had the /system/csc folder.
Do you have this folder on your phone?
I do have /system/csc ... I see customer.xml and sales_code.dat in there so I assume it's definitely related to something T-Mo specific.
This stock ROM was flashed with 3.09... so maybe I should try flashing a clean copy of OvrDrive's ROM with a different version of Odin. He recommends 3.11.1 on his ROM OP though. I'm just not sure what I used previously... might end up being trial and error here.
Now that's a real mystery! Why were you getting a /system/csc with 3.09, and I wasn't?????
Not sure. With this stock ROM, I didn't wipe internal storage but I definitely wiped data and system x5, so if any CSC folder existed prior to, it should have been gone before the ROM installed.
Well, I'm gonna take the plunge and try 3.09. I always wipe internal storage. Nothing there I need to keep -- music and photos are on an SD card.
I'll keep you updated. I'll flash the ROM on a couple different versions of ODIN and see if that's the culprit. I'll also try another ROM. Just doesn't make sense why this stock ROM is so smooth, but I guess that's a good sign.
Have you debloated anything yet? I use SD Maid (or sometimes Titanium Backup) and remove some stuff:
Google and Youtube and Amazon and Dropbox and others I can download from the store (they just clutter the ROM when they get updated anyway)
the Facebook apps (I don't use it)
Milk
non-English fonts
Allshare and nearby devices bits
Related
I just got a regular S6 through T-Mobile and for some reason, the initial update is failing. It will download (177 mb), reboot to install, get to 25%, fail, and reboot. The phone is working perfectly other than that. Any idea what I can do to fix it? Thanks.
Since you just got it, why not do a factory reset, then see if the update takes.
roger1955 said:
Since you just got it, why not do a factory reset, then see if the update takes.
Click to expand...
Click to collapse
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
BTow1105 said:
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
Click to expand...
Click to collapse
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Alarand said:
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
Click to expand...
Click to collapse
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mikeyinid said:
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Click to expand...
Click to collapse
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
BTow1105 said:
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
Click to expand...
Click to collapse
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
mikeyinid said:
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
Click to expand...
Click to collapse
The drivers are installed, Odin recognizes the device, but it just seemed frozen on the blue screen. Odin did a few things and said "started" or something and it said that for about 20 minutes before I decided that couldn't be right. Rebooted it and it went right back to normal.
Have another computer to try, just to cancel out that computer being the problem?
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
BTow1105 said:
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
Click to expand...
Click to collapse
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
5.1 the dream
mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
altimax98 said:
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
Click to expand...
Click to collapse
Well , to be honest, they should be doing all warranty work and claims and things right there as well. They have such ****ttty customer service that I'd much rather go somewhere so that I could actually discuss things in person. Kinda like......... APPLE!! That's really the only reason I keep these Crapple devices around, because they will swap out anything 4 me on a dime and it can be done in less than an hour. No 2-3-4 weeks without a phone. It seems like being 2015, Samsung should be able to compete in that sense. Oh well, Sorry, I am just daydreaming over here. :cyclops:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
PS4AndroidHacker said:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62486197
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
KingBeef said:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
Click to expand...
Click to collapse
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
I have not tried a stock run without third party apps installed. I will try a fresh install of stock COD6 with root and see how that fairs. It normally happens the first time within an hour of flashing so it won't take long to see if it happens I believe.
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Jammol said:
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
Click to expand...
Click to collapse
So I tried stock rooted without third party apps installed. Got 2 reboots but no loss of data. Seems like it's something with the device itself or should I try just running without root?
dkb218 said:
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Click to expand...
Click to collapse
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
KingBeef said:
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
Click to expand...
Click to collapse
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Jammol said:
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Click to expand...
Click to collapse
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
KingBeef said:
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
Click to expand...
Click to collapse
Yes but it is not recommended. Using Synapse from the playstore will do such a thing but it requires a custom Kernel. If it is a thermal issue your device may be defective seeing that it's spiking so much so quickly and just crashing.
Definitely give the process of elimination a try that I suggest in my previous post. If it fails at the first step of being pure stock no SDCard then I'm afraid you need a new device.
Hi KingBeef,
Unfortunately, I have the exact same issues you do. Except I've tried literally everything. Even Odin back to stock KitKat. Seems to reboot or randomly shut off if more than 3-4 apps are running at completely random times. No SD card as well to confirm it's not that. The only difference I see with your situation is my phone will degrade after 3rd day of use. First 2 days are flawless, then almost like a failing hard drive, things start to domino progressively worse. My last attempt was to run it only in wifi mode, no SIM card.
The only thing left is to consider unfortunately is swapping again under warranty. I myself am waiting until I go back to the US (Cad user here) to swap with TMo for another handset.
Good luck!
Sent from my D6503 using Tapatalk
My wife and I both have H811 G4s. I've gone through and rooted both of our phones with Low Effort, flashed twrp, debloated, updated to 10n debloated. Everything has been great until last week. My wifes phone started randomly rebooting. It's actually random. I can't find anything consistent. I removed apps with updates, factory reset and it would reboot during the setup wizard. Yesterday I did a full return to stock 10n, and it behaved all day.
Today I try to root with the 10n debloat , and now it's rebooting again. I have a hard time thinking it's bad hardware as the full stock works fine, and with it not rebooting on stock how would I prove it for the replacement?
What else can I check or do to fix this, and why is it only happening to one of the phones?
Bad download.
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Bad download.
Click to expand...
Click to collapse
Good idea, but I've used the same file on multiple phones without issue. It's only the one device having problems. Also the md5 matches, just double checked.
As I work my way backwards I'm pretty sure this it turning into failed hardware. I've had it reboot a few times on stock during the setup wizard. But it's nowhere as frequent as the rooted roms.
Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!
mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493
I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.
N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!
I use my phone for business and it absolutely destroyed my phone. I am losing 15% on idle with no SOT and have tried everything. Letting it "settle", clearing dalvik/cache, et al. I'm not sure if it's apps I use for calling and business haven't adjusted. Either way, I can literally watch it tick away when I'm actually using the phone. GPS, BT, SYNC make no difference and didn't before. My phone was perfect before the update and the only thing that changed was taking OREO.
It's been a long time. I go back to the Beans Roms on Note 2, but I can't brick this phone. Is there any possible way to downgrade from the OTA back to Nougat.? I've spent two days googling and it's pretty unclear between, here, reddit, other android forums. Randomly non ESL speakers saying "yes, did, this software, odin, success"
Can anyone give me a quick rundown of the steps and software versions/Odin versions etc that are known to work. I've flashed many times before but it's been a hot minute since Sammy shut down all our fun with custom Roms. I took my phone off the charger an hour ago, checked a few emails, and it's already down to 72 percent. The thing I show most is "android" system but it doesn't give me any more info. I give up, I have to go back.
Thanks a ton in advance!
Factory resetting your phone is probably your best option.
If you Odin back to a previous os, it has to be a "3" version. Only issue is the phone will always prompt you to update, and that you will be stuck at that last security update. Which as a business who needs would be undesirable.
Sent from my SM-N950W using Tapatalk
This would be your previous software. The 3 is indicated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N950W using Tapatalk
rrupert said:
This would be your previous software. The 3 is indicated View attachment 4477255
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
Ok. So how do I restore?
Downloaded mode
Odin
Flash?
Which Odin? What slot do I put it in in? Just trying to get a step by step, it's been a long time.
Edit: okay so one file in PDA and the other in Csc? In download mode? Which Odin is safe for this?
Also, if there is a way to back up in case something goes wrong I should ask now.
Thanks!
rrupert said:
Factory resetting your phone is probably your best option.
If you Odin back to a previous os, it has to be a "3" version. Only issue is the phone will always prompt you to update, and that you will be stuck at that last security update. Which as a business who needs would be undesirable.
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
Frankly, I don't give a damn about Android security right now. It wrecked my phone and the factory reset did nothing. Obviously there is something happening where my apps run terrible on Oreo or some New processes that are sucking battery life.
Someone mentioned online there is an AAS service running that he killed From Sammy that really helped. I don't have a days to tinker with disablers.
The poster below noted the correct software. Can either of you give me the step by step on downgrading?
Thanks
Have to use all 4 files. Home CSC I believe keeps internal memory while CSC deletes.
Sent from my SM-N950W using Tapatalk
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
I'm not by my computer, so unfortunately I cannot give you much more info. Sorry.
After you factory reset, did you restart from a backup of your apps. If so, a fresh restart should be done fresh. Starting with your most necessary apps from the app store, not from backup. Backups can reinstall all your problems just like they were before
Sent from my SM-N950W using Tapatalk
Well my case is opposite. After upgrading to oreo. My device got lot smother. And the battery is just awsome. Before on nougat i used to have max 4hrs sot. And now 5.30 or even 6 hrs of sot. While the same use as before.
I am happy with oreo.
Try reseting and again update may be it get better.
rrupert said:
Have to use all 4 files. Home CSC I believe keeps internal memory while CSC deletes.
Sent from my SM-N950W using Tapatalk
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
I'm not by my computer, so unfortunately I cannot give you much more info. Sorry.
After you factory reset, did you restart from a backup of your apps. If so, a fresh restart should be done fresh. Starting with your most necessary apps from the app store, not from backup. Backups can reinstall all your problems just like they were before.
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
Ok is there a specific Odin I have to use or will "any version" work. I know there are specialized types like Prince? for certain devices or Roms. I can do this process not being rooted at just stock?
Yeah I tried going fresh, going from Smart switch back ups. Whatever calling apps, corporate apps, etc I use is just not working with Oreo (or sammies new processes that are sucking battery). I keep all my apps updated so that shouldn't be a problem.
junniscorpio said:
Well my case is opposite. After upgrading to oreo. My device got lot smother. And the battery is just awsome. Before on nougat i used to have max 4hrs sot. And now 5.30 or even 6 hrs of sot. While the same use as before.
I am happy with oreo.
Try reseting and again update may be it get better.
Click to expand...
Click to collapse
I have been trying to solve this for two weeks. I haven't heard one person mention "better" performace or "better" battery but at best, about the same.
If you google Oreo battery there are thousands of compalints. I've reset, i've cleared cache /dalvik, I've factory rest, I've let it "settle".
It's just not happening. I'm trying to verify the process from above before I do it. I've always been rooted/bootloader unlocked when I was playing with ROMs and flashing.
I used Prince Odin. (googled modded Odin) pretty sure was first on list.
No need for root.
My downgrade went flawlessly.
Sent from my SM-N950W using Tapatalk
rrupert said:
I used Prince Odin. (googled modded Odin) pretty sure was first on list.
No need for root.
My downgrade went flawlessly.
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
Thanks so much for your information. One last thing.
Do I need to do some sort of backup in case things go bad?
Out of curioisity, what caused you to downgrade?
Thanks!
I made a backup just in case.
I had to downgrade because I was on a leaked Oreo build which made my N950W into a N950U. Because of this I was unable to recieve any future OTA's. Wanted the official, so the only way was to go to an earlier build and update from there.
I never use backup after major updates. Start completely fresh from app store. Only thing I may need backup for is my contacts.
Sent from my SM-N950W using Tapatalk
rrupert said:
I made a backup just in case.
I had to downgrade because I was on a leaked Oreo build which made my N950W into a N950U. Because of this I was unable to recieve any future OTA's. Wanted the official, so the only way was to go to an earlier build and update from there.
I never use backup after major updates. Start completely fresh from app store. Only thing I may need backup for is my contacts.
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
Ok and what I've read the emergency software recovery from smart switch is adaquate for a backup? I already "backed up" my phone just in case, but don't plan on restoring from it.
You download the firmware from sammobile and extract, then good to go. Phone in download mode start Odin by right click admin privileges. Add files in corresponding slots. Done
Sent from my SM-N950W using Tapatalk
rrupert said:
You download the firmware from sammobile and extract, then good to go. Phone in download mode start Odin by right click admin privileges. Add files in corresponding slots. Done
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
Yeah Unfortunately I can't without premium till tomorrow, I'm using abother site right now but itll be tomorrow by the time the download completes
Yea was a 5 hr download for me
Sent from my SM-N950W using Tapatalk
I am glad to read this, I've been thinking about downgrading as well.. not just battery, but it seem nougat has better cell signal than oreo on the N950U1..
Sent from my SM-N950U1 using Tapatalk
jr_718 said:
I am glad to read this, I've been thinking about downgrading as well.. not just battery, but it seem nougat has better cell signal than oreo on the N950U1..
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
Yeah it's night and day. I'm not sure if Oreo was rushed, or many of my apps don't play nice with the new software. Either way there is very little difference on the outside between Oreo and Nougat, I'll take the better smoothness and batteryall day everyday.
thechaoz said:
Yeah it's night and day. I'm not sure if Oreo was rushed, or many of my apps don't play nice with the new software. Either way there is very little difference on the outside between Oreo and Nougat, I'll take the better smoothness and batteryall day everyday.
Click to expand...
Click to collapse
That's exactly how I feel, that Oreo was rushed to be released for the Note 8. Hopefully we'll see 8.1. Not much different from Nougat, many incompatibilities, and a number of issues that need work arounds to get working again. I get much better battery life on Nougat. But to be fair some of the imcompatibilities need to get worked out by devs if possible & maybe some apps are not optimized for Oreo yet. I've been sticking with Nougat so far.
Well, I also took an update on my unlocked note 8 950U1. As soon as It boots up, battery keeps draining like crazy, then I factory reset, wipe clear cache in recovery mode, after that I reinstall every app. Now battery lasts longer than Nougat 7.1.1, phone boots up and runs much faster. You also have an option to turn off background running apps. I think I am happy with Oreo, picture in picture is awesome. I'm glad I did not Odin back to 7.1.1 after I downloaded the firmware 7.1.1. You should try to factory reset and wipe clear cache again in recovery mode. Turn off app running in background, you will notice battery is better than Nougat.
luckyfate said:
Well, I also took an update on my unlocked note 8 950U1. As soon as It boots up, battery keeps draining like crazy, then I factory reset, wipe clear cache in recovery mode, after that I reinstall every app. Now battery lasts longer than Nougat 7.1.1, phone boots up and runs much faster. You also have an option to turn off background running apps. I think I am happy with Oreo, picture in picture is awesome. I'm glad I did not Odin back to 7.1.1 after I downloaded the firmware 7.1.1. You should try to factory reset and wipe clear cache again in recovery mode. Turn off app running in background, you will notice battery is better than Nougat.
Click to expand...
Click to collapse
I've done both of those, and I never had to stop my apps from running in the background on nougat. I need them active for my business applications.
Everyone has reported that wide variety of results which is strange, but in my particular case, it's not something I can deal with right now
Sent from my SM-N950U1 using Tapatalk