Database Develop

Update Failing

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

Update N6 AT&T to Marshmallow?

I know AT&T hasnt released the 6.0 update yet but I just got the November LMY48Y security update. Is there anyways I can flash or manually update to 6.0? I'm on the international N6 so its not carrier locked or anything, I'm just not sure which build of Marshmallow to flash as all of them come from different builds (LM48T - MRKxxx)

none
Are you rooted? If your rooted you shouldn't be getting, nor receiving any OTA. I don't know much about the International version but as long as your rooted with an unlocked bootloader flash the version you want to. The great thing about the Nexus 6 is all the developement you see. Any other questions shoot me a PM if you want to

USMC retired said:
Are you rooted? If your rooted you shouldn't be getting, nor receiving any OTA. I don't know much about the International version but as long as your rooted with an unlocked bootloader flash the version you want to. The great thing about the Nexus 6 is all the developement you see. Any other questions shoot me a PM if you want to
Click to expand...
Click to collapse
Not rooted right now but bootloader has been unlocked since the day I got it. I just didnt know if I can flash any 6.0 build. Will have to give a try tomorrow, any problems I'll be sure to PM you. Thanks for the info man, take care.

CavyS, I'm in the same boat as you... Also, I was told that flashing from the wrong OTA could cause problems. Please let me know if you tried flashing something. I'm stuck on LMY48Y...
Thanks!

There is no OTA to flash, for the Nexus 6 that has an AT&T sim. It hasn't been released yet. If you want to go to MM (6.0), you should flash the full 6.0 image that Google released back on October 5th, which was MRA58K and then let the security updates install WITHOUT the AT&T sim installed. "N" and "R" have since been released that contain the security updates. You could probably go directly to "R" without an issue. I'm backing up all of my data tomorrow morning and flashing "MRA58R" and if I run into problems, I'll flash back to LMY48Y. From what I gather, there is no issues with FULL IMAGE of MM on the Nexus 6 with AT&T, it's that there is no OTA yet available to go from 5.1.1 LMY48Y to 6.0 MRA58? because Google or AT&T is still trying to figure it out. Personally, I'd rather flash a full, clean image than get an OTA and still have to do a factory data reset (FDR) to fix all the issues that seems to come with an OTA update, especially one as comprehensive as going from Lollipop to Marshmallow.

UPDATE: I used the NRT (Nexus Root Tool Kit) from Wugfresh and following this video, I unlocked my bootloader and installed MRA58R. It installed quickly and painlessly, although I did a complete backup of all my data using Helium before I started the process. So far, so good. I'll report back if I have any issues.
https://www.youtube.com/watch?v=Emyd6od3tGs
http://www.wugfresh.com/
BEFORE:
{
"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"
}
AFTER:
And here is another tip...once you install MM on your N6, if you want to re-lock your bootloader, lock it BEFORE you put back all of your user data. On previous versions of Android, locking the bootloader did not wipe user data, but on MM, it does! I wish I had known that before I set everything up. See this thread for more info: http://forum.xda-developers.com/nexus-6/general/locking-bootloader-wipes-data-t2947916

Doesn't really matter which build.
CavyS said:
I know AT&T hasnt released the 6.0 update yet but I just got the November LMY48Y security update. Is there anyways I can flash or manually update to 6.0? I'm on the international N6 so its not carrier locked or anything, I'm just not sure which build of Marshmallow to flash as all of them come from different builds (LM48T - MRKxxx)
Click to expand...
Click to collapse
Just use any build you like from the Google Developers page https developers.google.com/android/nexus/images
On the site are various instructions on how to flash the image(s). Not that you need your bootloader unlocked (if it isn't, doing so will delete all your data, so make a backup first).
Have fun with Marshmallow!

BartmanJax said:
UPDATE: I used the NRT (Nexus Root Tool Kit) from Wugfresh and following this video, I unlocked my bootloader and installed MRA58R. It installed quickly and painlessly, although I did a complete backup of all my data using Helium before I started the process. So far, so good. I'll report back if I have any issues.
https://www.youtube.com/watch?v=Emyd6od3tGs
http://www.wugfresh.com/
BEFORE:
AFTER:
And here is another tip...once you install MM on your N6, if you want to re-lock your bootloader, lock it BEFORE you put back all of your user data. On previous versions of Android, locking the bootloader did not wipe user data, but on MM, it does! I wish I had known that before I set everything up. See this thread for more info: http://forum.xda-developers.com/nexus-6/general/locking-bootloader-wipes-data-t2947916
Click to expand...
Click to collapse
@BartmanJax, is your N6 on AT&T still working smoothly. I heard of some issues with reboots and/or dropping connection when going to MM. If you are not having issues I'm going to use the WUG RootKit and do the same!

Genghis1227 said:
@BartmanJax, is your N6 on AT&T still working smoothly. I heard of some issues with reboots and/or dropping connection when going to MM. If you are not having issues I'm going to use the WUG RootKit and do the same!
Click to expand...
Click to collapse
Working perfect! No issues at all!
And I learned a trick this morning when I flashed my N7 (2013) with a fresh image. You don't have to do an OEM Unlock first by clicking the OEM Unlock button on NRT. It will be done for you automatically if you follow the steps below.
First, make sure your have USB Debugging turned on on your N6 AND have your USB connection set to PTP. (Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check PTP box).
With your N6 connected, launch NRT, answer the questions about YOUR model and the current build (probably Nexus 6 (Moto XT1100, XT1103) for your device and for the build, probably SHAMU-SHAMU: Android 5.1.1 - Build LMY48Y). Make sure your information is correct for what is CURRENTLY on your phone). NRT will want to download some files. Let it. It only take a minute or so on a high speed connection.
When you get to the main NRT window as shown here, click on "Flash Stock + Unroot" shown here highlighted.
On this next screen, just click OK.
Assuming you're on the AT&T network using a Nexus 6, on this screen, select MRA58R (MMB29K if you want to go straight to 6.0.1) in the drop down and in the "Choice" section, select Automatically download and shown in this image. This is what you will be adding to your phone. The new image. Then click OK.
That's all you have to do. If the phone is connected to your computer correctly and is communicating with the computer, it will automatically launch the bootloader and ask you if you really want to unlock the phone, That takes an action from you (Volume up button once to "Yes" and then the power button to select). When you do this, you have to go back into the phone (skip all those annoying steps) to get to the home screen and go back to Settings > About Phone > press on the Build 7 times to get the Developers Options and turn on USB debugging again and your also have to go back to PTP. NRT will guide you through the steps. It will then automatically download the MRA58R .tgz file, unzip it, push it to your phone and install the new image. It's truly painless.
Once everything is done, if you want to OEM Lock your phone, do it BEFORE you start putting your data back.
One side note. After you unlock the phone the first time and you have to go in to turn on USB debugging AND after you install 6.0, both of the those boot times are long (maybe 5-10 minutes). Don't worry. After 6.0 is installed and booted up the first time, subsequent boots are much faster. And shutdown is very fast in 6.0.

Will give it a try tonight probably. Thank you!
Sent from my Nexus 6 using Tapatalk

Genghis1227 said:
Will give it a try tonight probably. Thank you!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you do, let me know how it goes. Good luck! :good:

BartmanJax said:
Working perfect! No issues at all!
And I learned a trick this morning when I flashed my N7 (2013) with a fresh image. You don't have to do an OEM Unlock first by clicking the OEM Unlock button on NRT. It will be done for you automatically if you follow the steps below.
First, make sure your have USB Debugging turned on on your N6 AND have your USB connection set to PTP. (Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check PTP box).
With your N6 connected, launch NRT, answer the questions about YOUR model and the current build (probably Nexus 6 (Moto XT1100, XT1103) for your device and for the build, probably SHAMU-SHAMU: Android 5.1.1 - Build LMY48Y). Make sure your information is correct for what is CURRENTLY on your phone). NRT will want to download some files. Let it. It only take a minute or so on a high speed connection.
When you get to the main NRT window as shown here, click on "Flash Stock + Unroot" shown here highlighted.
On this next screen, just click OK.
Assuming you're on the AT&T network using a Nexus 6, on this screen, select MRA58R in the drop down and in the "Choice" section, select Automatically download and shown in this image. This is what you will be adding to your phone. The new image. Then click OK.
That's all you have to do. If the phone is connected to your computer correctly and is communicating with the computer, it will automatically launch the bootloader and ask you if you really want to unlock the phone, That takes an action from you (Volume up button once to "Yes" and then the power button to select). When you do this, you have to go back into the phone (skip all those annoying steps) to get to the home screen and go back to Settings > About Phone > press on the Build 7 times to get the Developers Options and turn on USB debugging again and your also have to go back to PTP. NRT will guide you through the steps. It will then automatically download the MRA58R .tgz file, unzip it, push it to your phone and install the new image. It's truly painless.
Once everything is done, if you want to OEM Lock your phone, do it BEFORE you start putting your data back.
One side note. After you unlock the phone the first time and you have to go in to turn on USB debugging AND after you install 6.0, both of the those boot times are long (maybe 5-10 minutes). Don't worry. After 6.0 is installed and booted up the first time, subsequent boots are much faster. And shutdown is very fast in 6.0.
Click to expand...
Click to collapse
I remembered I had to do OEM unlock in developer menu... Did you do this before anything?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:35 PM ---------- Previous post was at 10:42 PM ----------
Just finished the update to MM and everything so far is very smooth. The only thing I would say is to enable the Allow OEM Bootloader Unlock before pushing the Flash Stock + Unroot. Makes it that much quicker so that you don't have to boot back into the device and enable it later. Otherwise, setting up the apps and then going to put the SIM back on. Will report back if I get any issues while using it on the AT&T network when I put my SIM back on.

I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
---------- Post added at 07:49 AM ---------- Previous post was at 07:36 AM ----------
Genghis1227 said:
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
Click to expand...
Click to collapse
After a second reboot I now have LTE.

Genghis1227 said:
I put in my SIM and unfortunately I cannot connect via LTE, only HSDPA. I wonder if it just isn't showing LTE but really connected via LTE. In the 5.1.1 it showed LTE...
---------- Post added at 07:49 AM ---------- Previous post was at 07:36 AM ----------
After a second reboot I now have LTE.
Click to expand...
Click to collapse
Excellent! :good:

Anybody try the 6.0.1 update and use the no wipe mode?
Looks like the 6.0.1 released https://developers.google.com/android/nexus/images
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
Genghis1227 said:
Anybody try the 6.0.1 update and use the no wipe mode?
Looks like the 6.0.1 released https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Perhaps will it OTA with pulling the SIM?

Genghis1227 said:
Anybody try the 6.0.1 update and use the no wipe mode?
Click to expand...
Click to collapse
Yep! I did yesterday morning. I went from MRA58R to MMB29K using the No Wipe Mode and it seems to have worked fine. Luckily, I had not locked my bootloader from the previous install of 58R. If I had, then it wouldn't have mattered since you wipe the phone as soon as you unlock the bootloader.
29K is working fine on my N6 on AT&T.
Genghis1227 said:
Perhaps will it OTA with pulling the SIM?
Click to expand...
Click to collapse
Probably not. AT&T is driving the release of OTA's, just like Verizon, Sprint and T-Mo is driving the release of OTA's of phones on their network.

So because you left the bootloader unlocked it just basically upgraded (aka sideloaded the OTA) right? Data and everything else intact? I'm just going to keep it unlocked from now on. AT&T is horrible at updating.

Genghis1227 said:
So because you left the bootloader unlocked it just basically upgraded (aka sideloaded the OTA) right? Data and everything else intact? I'm just going to keep it unlocked from now on. AT&T is horrible at updating.
Click to expand...
Click to collapse
Correct! Just be sure and select the "No Wipe Mode." I decided to leave mine unlocked as well. Makes updates easier. I don't really want to leave the bootloader unlocked, but like you said, AT&T is horrible at updating.

Downgrade back to marshmallow

So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no ota back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app

sookieball said:
So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no it's back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
well, to flash stock, you dont use twrp, you use fastboot while youre in the bootloader. and in N, allow oem unlock is automatically enabled.

It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app

sookieball said:
It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
how? did you do fastboot oem unlock?

Maybe you've already tried this, and I don't know if it will work, but have you tried re-enrolling and unenrolling in the hope that it will jog the revert mechanism into life?

I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app

sookieball said:
I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
you pribably cant oem unlock while on N then. that probably why they made it unavailable. im not on N now, so cant test.

What about trying a sideload of the full OTA? I thought (I might be wrong) that it's independent of a locked bootloader.
https://developers.google.com/android/nexus/ota#instructions
It's worth a shot, especially as it doesn't overwrite your data.

On a related note, I'm on preview 3 - battery drain when idle is higher than what it was on stable M, so thinking about reverting back to M.
1. To avoid a factory wipe, can I just flash the img files from the stable M (skipping userdata) on top of the preview 3?
2. If so, to avoid getting the N preview update notification, I guess I will need to un-enroll from the beta program. Will that cause an OTA to be sent back to my phone (causing factory wipe as described on the beta page)? Or does it recognize that I'm already on 'M' and skip the OTA?
3. Before I do this, is it possible to flash the radio only from the latest "M" image on the "N" preview? (could that help with the drain when idle?)

Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104

dahawthorne said:
Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104
Click to expand...
Click to collapse
LOL! Yes, I did! And thank you for that as well - the part that I didn't understand (and unless I missed it in your response, I don't think we talked about in that post) was - since I'd still be enrolled in the preview/beta program, how do I get out of the program, without getting factory reset.
(I do have a nandroid backup as a last ditch option - trying to do this the 'clean' way first)
The preview is working well for me as well - skype is the only app giving me grief, but I can live with that. The battery drain on idle seems to be significantly higher than what I encountered with "M" stable. With barely any usage this morning (screen on for 11 minutes), my battery is at 77% (full charge and off the charger at 10 pm last night). Cell Standby is the the highest drain (6%). Phone idle and Android system tied for 2nd place at 3%.
With the latest M build, I'd be at over 90% battery remaining (with similar usage).

You're right on all counts...
I think the answer to your wipe question is that you'd have to agree to do it - if you unenrol and have already reverted manually to M, the downgrade OTA may be downloaded (though from my experience, as I said, I think the developers are smart enough to recognise that it's a waste of time and even that won't happen) but you would still have to push the button to accept it. They won't unceremoniously dump it on you without your permission.
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Looks like Google have a bit more work to do on their power management...
Edit: And in the 5 minutes since I wrote this, with the phone sitting beside me, screen off, nothing running, it's already down to 74%. Not at all impressive. Despite being relatively happy with it, I may have to renege on my previous comment that I can't see myself reverting to M.
And before you ask, I'll be reverting using my TWRP backup of M which I took immediately before I installed N...

Thank you
I'll wait for the June security update (factory image) and install that directly (skipping userdata). If that fails, I'll revert to the TWRP backup. (restoring TWRP on my old N5 has given me grief in the past, so going to avoid that if possible)
Edit: maybe I'll try flashing the radio from the May image onto "N" and see if that helps. The battery drain appears to be radio related.

Done. No problem at all. TWRP took about 12 minutes to restore 7GB of data, then a rather nerve-racking 5 minutes with the Google quad-icon swapping bits, and I'm back to MOB30I.
Seven updates waiting; BBC Radio, Skype, Google Drive, Sygic, all the broken apps working again, still have root.
Welcome back, old M world...
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
I've also just unenrolled from the Beta program, and checked for a system update. Exactly as I thought, "Your system is up to date" on MOB30I. I know that the OTAs have been slow for some people, but I don't expect to see the revert OTA - I'll post in this thread if I ever do.

dahawthorne said:
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
Click to expand...
Click to collapse
Would the fact that I'm rooted cause any issues with sideloading the OTA? (I realize the new OTA is essentially a full image, so it should just overwrite the system, and I'd have to reroot after that)

No problems at all, no. My N5 was rooted & encrypted, and the OTA slid in easily. As I said in another thread, it boots into TWRP but the OTA is designed to handle that. I installed TWRP again anyway, probably pointlessly but just to be on the safe side, and then used it to install SuperSU 2.74.
Easy as pie...

I unenrolled, got a prompt for system "update" back to MM, it downloaded, and now I am going on 30 minutes on the install part....been stuck on the reboot screen with 4 colorful circles....
How long does it take to re-install MM? TIA
EDIT: Decided to hold down power button for about 5 seconds and it rebooted to setup screen

dahawthorne said:
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Click to expand...
Click to collapse
I ended up flashing the radio (only) from MOB30I on to the N preview, and so far, the battery life on idle is back to how it was on M. I think I have a reason to stick on to the N preview a bit longer now
banditsw said:
How long does it take to re-install MM? TIA
Click to expand...
Click to collapse
Looks like you got it sorted out, but just for future reference, the reason it took long is because it essentially factory reset your phone - a factory reset with full wipe on the encrypted N6 cane take 20-30 minutes.

I'm impatient, me, so by the time I read this I was already back on MOB30I, but in any case I'm happier to have all working apps without the rash of library errors and force-closures. Interesting thread...
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8

dahawthorne said:
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8
Click to expand...
Click to collapse
I ended up reverting back to the "M" stable image yesterday (was waiting for the June image to be available). No issues with the "N" to report, except one custom app that I use was giving me some issues.
Anyway, thought I'd share my "downgrade" story
If you do the downgrade the right way (un-enroll from the Beta program), and get the OTA back to the latest "M", it will likely go well - because it performs a factory reset on your phone.
I however, didn't wait to set my phone up from scratch (lazy), so I flashed the factory image for the latest "M" (and skipped userdata.img). Bad idea. Flash went thru' successfully, but I ended up with pretty much an unusable phone because two system processes kept crashing in a loop after booting up. I then tried ADB sideload for the new OTA image file - same results. Wiped cache partition - no difference.
I then remembered that some apps (like Google Maps) had different versions for "N", and realized that the issue must be because of apps like that not being compatible with "M". Thankfully, I had a nandroid backup of the "M" (May security release) from before I installed "N", and I installed that - and then, updated to the June security release of "M".
Whew!
So, in summary, If you are rooted, take a nandroid backup in TWRP before you install "N" preview. If not, plan to factory reset your device after going back (or while going back) to "M" - no shortcuts.

MAJOR phone issues, reboots/freezes... but improves on stock firmware?

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

How has been your experience with OTA Oreo for exynos?

Hello, I have seen a mixed bag of opinions about Oreo, some saying is excellent, others stating that only marginal improvements, and, a bunch reporting problems af all kinds, even regretting that they updated, many did not receive Ota, but installed the firmware via Odin, I would really like to hear about your experiences about OTA Oreo, in Mexico oreo is not yet available, and maybe I would not accept it, depending on your opinions, but only about OTA Oreo, thanks in advance for your useful inputs

So, you already heard a lot of opinions, but now you want to hear even more opinions. Interesting !
Many have downgraded. So, once you get it and if you don't like it...
I like it. No problems. Few changes in phone settings. Slightly better battery.
Sent from my Galaxy Note 8 using XDA Labs

It's been great. No issues and very good performance.

Dejan Sathanas said:
So, you already heard a lot of opinions, but now you want to hear even more opinions. Interesting !
Many have downgraded. So, once you get it and if you don't like it...
I like it. No problems. Few changes in phone settings. Slightly better battery.
Sent from my Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Yes, because in most cases the opinions I read do not tell how oreo was installed, that is why I ask to those who received OTA

You should just update for the security, if nothing else. I flashed Oreo via Odin, once booted I factory reset. 0 problems for me. Feels snappier for sure.

winol said:
Yes, because in most cases the opinions I read does not tell how oreo was installed, that is why I ask to those who received OTA
Click to expand...
Click to collapse
Do you think it matters how you install it ? I think it doesn't matter. If you install it either way and then do a factory reset, which in my opinion is a must, you're good to go. But that's just my opinion.
Sent from my Galaxy Note 8 using XDA Labs

stonedpsycho said:
You should just update for the security, if nothing else. I flashed Oreo via Odin, once booted I factory reset. 0 problems for me. Feels snappier for sure.
Click to expand...
Click to collapse
So, you recommend to hard reset after the OTA?, This would be the first time I update via OTA, As I rooted all my devices before this one

winol said:
So, you recommend to hard reset after the OTA?, This would be the first time I update via OTA, As I rooted all my devices before this one
Click to expand...
Click to collapse
It is just something I have always done. The amount of times I have seen a bug or issues fixed by a factory reset, sod setting the phone up, get all your apps on then find a bug. I am sure it would be fine by OTA but if that fails you always have Odin as a backup. Even if you decide you do not like it you can go back to N.
If you are rooted and have custom recovery the OTA will fail anyway. If so just flash with Odin.

stonedpsycho said:
It is just something I have always done. The amount of times I have seen a bug or issues fixed by a factory reset, sod setting the phone up, get all your apps on then find a bug. I am sure it would be fine by OTA but if that fails you always have Odin as a backup. Even if you decide you do not like it you can go back to N.
If you are rooted and have custom recovery the OTA will fail anyway. If so just flash with Odin.
Click to expand...
Click to collapse
Ok, it is reassuring to know that I can downgrade, as I remember from my older dvices that downgrading was not possible at least not easily

winol said:
Hello, I have seen a mixed bag of opinions about Oreo, some saying is excellent, others stating that only marginal improvements, and, a bunch reporting problems af all kinds, even regretting that they updated, many did not receive Ota, but installed the firmware via Odin, I would really like to hear about your experiences about OTA Oreo, in Mexico oreo is not yet available, and maybe I would not accept it, depending on your opinions, but only about OTA Oreo, thanks in advance for your useful inputs
Click to expand...
Click to collapse
I've got an exynos with oreo i received OTA, in my opinion everything is a bit faster, and the whole interface has been refined just a bit. Better battery life by just a little. Definitely update for the new emoji style though! ?