I have a Note 4 on Sprint, still running KitKat. Here's my problem:
I really don't want the Lollipop update. I don't want it because I love KitKat so much and I tried Lollipop out on my friend's phone and hated the look and feel of it. I don't want it to finish downloading because I hardly have any space on my phone as it is.
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry because I'd like to use WiFi, but can't because every time I turn it on the update starts to download. I tried going into settings and turning off auto update, but that didn't stop it. I also tried filling my device storage so that there were less than 800 megabytes left, but that had no effect on the update either, it just continues downloading. I realize that there are similar posts on this issue, but none of them really apply to me. Thank you in advance for any help.
Just update it then use a kk theam the update will help i dont think you can stop the ota update
chad.420.419 said:
Just update it then use a kk theam the update will help i dont think you can stop the ota update
Click to expand...
Click to collapse
Thank you for replying, but that really doesn't help me at all. As I said several times over in my original post, I don't want the update at all. I'm constantly hearing about people choosing to keep KitKat, so there must be some way. And even if I could apply a theme to my whole phone without being rooted, it wouldn't fix all the other problems that I have with lollipop.
But the 3 things to consider or note before you begin:
1) if you update beyond OB7, the bootloader gets upgraded to one with a reactivation lockable bootloader. That will prevent you from being able to Odin back to KitKat. You need to disable auto update and stop the update notices before they start; otherwise the nags persist and you may accidentally update.
2) the lollipop file system is different than KitKat do better off formatting your data and wiping cache and dalvik-cache and powering down and pulling battery prior to Odin OB7 stock tar. Let it boot and setup wizard prior to Odin of TWRP (uncheck auto reboot for recovery flash only), boot into TWRP recovery and flash the ROM.
3) dalvik gets built on initial boot of lollipop ROMs; the stock tar still not much quicker. You'll likely see the phone hang at the second boot splash screen with blue LED slowly blinking before you see the app optimization and app start pop-ups. You can expect that with lollipop. Give it 30 minutes to boot before you panic. To avoid CPU heating and slowing the process, remove your phone from its case and ventilate if it gets too warm. You need to start with battery charged to about 80% to full to be safe. It's best to not try and update apps or restore apps until you've flashed and booted the custom ROM. More apps means the process takes longer. You can format the data again prior to flashing the custom ROM to speed things along. If possible, backup your media, and downloads that you want to keep and wipe internal sdcard to get a cleaner start with lollipop. That's optional but don't lose your keepsakes. What you flash should be on extSdCard to avoid the wipe-loss if it.
BTW, the post you're referring to may have been an attempt to recover phone after attempting to downgrade to OB7 or KitKat. It's since been discovered that although Odin wouldn't downgrade, there's a possibility to flash older ROMs in recovery and immediately flash a 5.1.1 rooted kernel to get it to boot without looping. That doesn't have to apply to you; the general rule is to Odin flash the tar that matches the ROM you want to flash in recovery. But again, if you upgrade beyond OB7, you cannot go backwards with Odin. Only few exceptions apply; generally it is forward, not backwards. OB7 is the divide that separates the simple from more complex conditions. So these last 3 paragraphs shouldn't apply to you as long as you're wanting to stay with OB7 or KitKat.
Just for an idea of what to consider in other lollipop updates. The ram optimization got a bit crazy after OB7 and continued until it improved in OJ6. Personally, I think OJ6 and OK1 updates are the best lollipop updates yet. You'll certainly find more security updates in those updates. But lollipop 5.1.1 also introduced the need to root the kernel but Chainfire has recently brought us a patch to use stock kernel again; it's married from experimental to beta. I've mostly ran with stock kernel on my phone, especially before lollipop 5.1.1
Things were once simpler but got a tad more complex as time and updates followed OB7.
Sent from my SM-N910P using Tapatalk
7H3N3RD said:
I have a Note 4 on Sprint, still running KitKat...
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry...
Click to expand...
Click to collapse
That's a tough ask for a definitive answer, IMO. IDK if it can be done but I'll offer an idea for discussion. Consider pros and cons and alternatives and even constructive differing because l don't know if it's been tried and proven to stop the persistent update on stock KitKat. There are root alternatives but your request is taken into some consideration below.
Odin stock tar will not trip Knox or require root. There are 2 stock tars for KitKat (those end with NIE and NK2, last 3 letters only, NIE being the original, NK2 the last KitKat update).
My theory is that you could...
1) Odin the first tar, NIE stock tar is linked below, let it download the OTA for NK2 but postpone the update long enough to go into Settings/System update/Auto update and uncheck the option.
2) Turn phone off and boot into recovery. It should find the NK2 update and prompt to apply it. If not there's an option to apply from cache, I think.
3) Once booted, make sure the auto update is still unchecked.
https://www.androidfilehost.com/?fid=95784891001612590
The instructions for Odin stock tar are found here but early posts in that thread may be relative to Odin if stock KitKat tar. The stock tar above is actually linked in post #2
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If auto update resets during the process, it most likely promptly starts the OTA download, negating the effort. No guarantees but reason the risks before you proceed. That's the whole theory, if someone knows the system update gets reset to auto or if that's not enough to prevent it, please advise. On a rooted Lollipop phone, uncheck auto update seemed to be enough to prevent the OK1 update from downloading and being persistent to update... I may have overlooked something in my simple theory. Did I?
Don't be angry with me if it doesn't work. Your data may not be lost but backup what you can on PC via USB, particularly photos, media and downloads on internal memory before you start. KIES may actually work to backup a lot on a stock un-rooted phone but be careful about what you restore; don't want to start the persistent update again if you succeed in preventing it.
Sent from my SM-N910P using Tapatalk
You definitely can stop it from nagging you to update by turning off notifications (I think you turn it off for Google services framework, and if not that, it's Google play services). This worked for me when I stayed on kitkat.
But deleting the downloaded update file is an issue without root. It lies in /cache or /cache/FOTA directory I believe, which you can't access without root. You may be able to wipe cache with stock recovery, but I'm not sure if it has that option (I'm not on stock recovery so can't check) or if it even works for what you want. Perhaps you can try deleting the cache for Google services framework or Google play services, not sure if the works either. Just some thoughts which may help you
Related
I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
n01un0 said:
I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
If you are on stock and have a valid AT&T SIM card in the device with full access to Wi-Fi and the AT&T network, you should be able to get an OTA update. Root could, however, indeed prevent an OTA update so your best bet may be to unroot. You could unroot and uninstall SuperSU from the SuperSU app just as you suggested. This should do it. However, if it doesn't and you would really want to avoid Odin and custom recovery, then you could do a 2-step manual update to 4.3 via stock recovery - first to 4.1.2 and then to 4.3. This will naturally update your phone to (full) stock 4.3 and we can then see if the phone will take the Kit-Kat OTA update from there.
You can see the instructions for the 2-step update via stock recovery in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2387423
1) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
2) Copy the zip files to a good quality (micro) SD card
3) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
4) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
5) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
6) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
7) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
8) Repeat the process for the second update file.
Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
n01un0 said:
Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357
Larry2999 said:
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357
Click to expand...
Click to collapse
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?
n01un0 said:
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?
Click to expand...
Click to collapse
Glad to know you were finally able to update. To try to answer your questions ....
1. Towelroot indeed comes well recommended for rooting on Kit Kat. You could, however, first try CF Auto Root which is one of the simplest approaches to rooting. If this doesn't work, you could try Option 2 in the thread below ... The thread also contains instructions to CF Auto Root.
http://forum.xda-developers.com/showthread.php?t=2538991
2. I'm not sure what that battery indicator is. I run 4.4.2 also on my S3 but I cant see this. Can you try a reset to see if it would go away?
3. You can try removing this from settings.
Im glad you asked this...
I too noticed Im on 4.1.1 stock but rooted. I wondered if you could go to 4.4.2 as my phone tried to OTA update on its own last week and failed. I did not know if it was worth it to try or not another way. About the only thing I see that would want me to try is Google Wallet now working with S3 on 4.4.2 without having to jump through all kinds of hoops, mine used to work fine, but now GW will not open up all the way. Im not sure its worth doing if I have to re setup all my crap as I will be upgrading my phone whenever I want, just holding out to see if the Nexus 6 will be out end of the year and on AT&T..Im not liking that all the new phones are getting so freakin big, the S3 is just right and I dont want to have to end up with a damn Note sized phone but that is a whole other discussion
If you're still on 4.1.1, BEFORE ANYTHING ELSE, UNLOCK YOUR PHONE IF HASN'T ALREADY
otherwise you'll regret it
then the rest, tbh, you don't need to unroot at all to upgrade, just flash the firmware in ODIN or recovery..
edit: nvm it seems like you've already upgrade yours to KitKat
Hi. I downloaded Lollipop but have not installed it yet and don't want to. I didn't know it was Lollipop I was downloading. How do I get rid of the possibility of it installing? I keep having to delay it for 24 hours. Do I have to do a factory data reset?
What version of anroud are you on and are you rooted? If so you can simply go to the /cache folder and delete the .cfg file file.
If you reboot before doing that the update will be installed.
I'm on 4.4.2 and not rooted. If I do a factory data reset before I install Lollipop would that get rid of the download ?
"Luke" don't fight it, grab the lollipop and feel the Force.
The force never tasted better.
Pp.
What is your reason for not wanting to update? Anything particular?
Rhino_7 said:
I'm on 4.4.2 and not rooted. If I do a factory data reset before I install Lollipop would that get rid of the download ?
Click to expand...
Click to collapse
From what I know , when you try a factory reset it will reboot your phone to recovery and perform the reset there. It may successfully do so, or it may immediately install the update in recovery. I can't say for sure.
If it is absolutely necessary for you to avoid this update, backup your files, download a firmware from Sammobile that matches your current 4.4.2, very carefully reset to download mode (you will only have one shot at this) and Odin that old firmware into your system. Hopefully that will overwrite all your files and remove the update. On the first boot enter recovery and do a reset. That is the most likely solution I can think of which may have a remote chance of working.
Another possibility is that if your firmware has a date before Jun 5 2014, you can run towel root version 3 to root it (doesn't require a reboot) then go to the cache directory and delete the update file. Of course all of this should be done before rebooting. This should work but you will end up with a rooted system.
Finally if your were forced to take the update you can almost downgrade it back to 4.4.2.
Thanks. I just did a factory data reset and it worked fine.
The reason is I like the phone now just as it is. No WiFi issues,great battery life,ect. From what i have read even though Lollipop is a big update there is nothing new that makes me want to have it.
Anyone want to try and convince me?
Android updates seem to always be buggy. I "might" try it later.
I went straight up Kies update and the phone never ran smoother.
Running stock /rooted / debloated and everything works the way it's supposed to.
No bells, no whistles, no exposed, just straight up touchwiz.
Knox shmox, never gave it a second thought after the warranty ran out.
Pp.
This is NOT ROOTED. Its the original TAR file for people who need an Emergency Recovery for their phones, and don't want to wait hours for it to download from slow file hosts.
Edit: New link added 6/21/16
Download Link: Google Drive
Do NOT rename the tar file, it may cause Odin to fail the md5 check.
Code:
(N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5)
Instructions:
1. Download and Extract tar above and download Odin
2. Put phone into download mode (power off, then power button + Volume Down, then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load stock tar into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
7. Profit
@random45, PSA: more direct link available here - http://forum.xda-developers.com/showpost.php?p=61880147&postcount=14
itskapil said:
@random45, PSA: more direct link available here - http://forum.xda-developers.com/showpost.php?p=61880147&postcount=14
Click to expand...
Click to collapse
That is not for the Note 4...
random45 said:
That is not for the Note 4...
Click to expand...
Click to collapse
@random45 Corrected.. ! pls check now.
Here's the OF5 TAR: http://www.theandroidsoul.com/download/download-sprint-galaxy-note-4-update-n910pvpu3bof5/
I just used this and it worked flawlessly. Thank you.
Thanks alot
This link is dead, it's actually deemed "dangerous", which of course is crap... Does anyone have a link to this firmware?
grmcrkrs said:
This link is dead, it's actually deemed "dangerous", which of course is crap... Does anyone have a link to this firmware?
Click to expand...
Click to collapse
No but the next update up though
http://forum.xda-developers.com/showthread.php?t=3250864
Sent from my Not4 Mod using Tapatalk
Does anybody still have this firmware version available? The latest marshmallow updates are destroying Galaxy phones left and right with no solution other than paying Samsung to fix the problem and waiting 2 weeks without your device.
random45 said:
This is NOT ROOTED. Its the original TAR file for people who need an Emergency Recovery for their phones, and don't want to wait hours for it to download from slow file hosts.
Download Link: MediaFire
Do NOT rename the tar file, it may cause Odin to fail the md5 check.
Code:
(N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5)
Instructions:
1. Download and Extract tar above and download Odin
2. Put phone into download mode (power off, then power button + Volume Down, then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load stock tar into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
7. Profit
Click to expand...
Click to collapse
tommacco said:
Does anybody still have this firmware version available? The latest marshmallow updates are destroying Galaxy phones left and right with no solution other than paying Samsung to fix the problem and waiting 2 weeks without your device.
Click to expand...
Click to collapse
Its still in my mediafire folder. I'll upload it to another site since mediafire has flagged it
Edit: Here is the new link
Thank you so much. I will let you know if this actually fixes my woes.... this ROM may become a major fix for a lot of people while Samsung continues to argue with us that there isn't a problem worth filing a bug report for.
random45 said:
Its still in my mediafire folder. I'll upload it to another site since mediafire has flagged it
Edit: Here is the new link
Click to expand...
Click to collapse
Bah, giving me a software revision check error in odin. I guess this means I have to replace the bootloader? samsung is killing me here, they issued a faulty update and blocked off all means of recovery... won't buy one of these devices again.
tommacco said:
Bah, giving me a software revision check error in odin. I guess this means I have to replace the bootloader? samsung is killing me here, they issued a faulty update and blocked off all means of recovery... won't buy one of these devices again.
Click to expand...
Click to collapse
Don't know what problem you're experiencing but most likely you can't go back to Android 5.0 through Odin.
Did you try OG5 or higher stock tar? Actually, I'd recommend OK1 or latest. If older ROMs are your goal, backup, wipe everything but extSdCard and Odin OG5 and up to match bootloader of ROM, flash the ROM. Do not Odin any tar below OG5.
If the ROM is Android 5.0 or KitKat, I think you still need to flash an Odin tar that's Android 5.1 and you need to flash an Android 5.1 kernel, like Beastmode 2.2 Flash ROM and then kernel before booting.
Can't imagine latest ROMs are to blame for ruining your phone. Marshmallow is a bit if a prude until you get familiar with it and setup properly. But if that's not to your liking, give Moar 2.1b a try. Backup and wipe as above and Odin back to OK1 if you don't have a backup. Follow the OP install instructions.
Sent from my SM-N910P using Tapatalk
samep said:
Don't know what problem you're experiencing but most likely you can't go back to Android 5.0 through Odin.
Did you try OG5 or higher stock tar? Actually, I'd recommend OK1 or latest. If older ROMs are your goal, backup, wipe everything but extSdCard and Odin OG5 and up to match bootloader of ROM, flash the ROM. Do not Odin any tar below OG5.
If the ROM is Android 5.0 or KitKat, I think you still need to flash an Odin tar that's Android 5.1 and you need to flash an Android 5.1 kernel, like Beastmode 2.2 Flash ROM and then kernel before booting.
Can't imagine latest ROMs are to blame for ruining your phone. Marshmallow is a bit if a prude until you get familiar with it and setup properly. But if that's not to your liking, give Moar 2.1b a try. Backup and wipe as above and Odin back to OK1 if you don't have a backup. Follow the OP install instructions.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
The stock OTA update from Sprint (PE1) started all these shenanigans with the phone, and it's done the same for many people across a few different carriers from what I've seen on the internet.
tommacco said:
The stock OTA update from Sprint (PE1) started all these shenanigans with the phone, and it's done the same for many people across a few different carriers from what I've seen on the internet.
Click to expand...
Click to collapse
I updated bootloader and baseband only to PE1 and flashed a custom ROM. Later flashed a custom PE2 ROM. The ROMs are Note 4our by @freeza beta 2 and beta 3.
I see nothing wrong with PE1 or PE2. Did you try a factory reset? It does seem data from Lollipop can interfere with custom ROMs on Marshmallow. Main issue I saw with that was ItsOn on the root folder: /carrier/ItsOn The apk in that folder can partially activate on a factory reset and continually reboot a phone trying to setup the ItsOn bootstrapper but cannot so the cycle continues until you fix it. Wiping internal memory and factory reset prior to custom ROM (especially after stock tar update) will help but the developers may have removed that possibility in recent ROMs.
OTA may be suspect too but may only apply if rooting it. ItsOn and Knox don't play nice with root.
I'm not aware of cross carrier issues though?
Sent from my SM-N910P using Tapatalk
samep said:
I updated bootloader and baseband only to PE1 and flashed a custom ROM. Later flashed a custom PE2 ROM. The ROMs are Note 4our by @freeza beta 2 and beta 3.
I see nothing wrong with PE1 or PE2. Did you try a factory reset? It does seem data from Lollipop can interfere with custom ROMs on Marshmallow. Main issue I saw with that was ItsOn on the root folder: /carrier/ItsOn The apk in that folder can partially activate on a factory reset and continually reboot a phone trying to setup the ItsOn bootstrapper but cannot so the cycle continues until you fix it. Wiping internal memory and factory reset prior to custom ROM (especially after stock tar update) will help but the developers may have removed that possibility in recent ROMs.
OTA may be suspect too but may only apply if rooting it. ItsOn and Knox don't play nice with root.
I'm not aware of cross carrier issues though?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I've done factory reset, wiped cache partition, reflashed PE1 and PE2 to no avail. This all started with OTA updates- I didn't touch the software or try flashing anything myself until these problems persisted and didn't go away with factory resets. I've seen others report these same issues in sprint/other forums, seems they ran into similar issues with recent OTA updates of the S5 as well. Sprint claims they're aware of this and are working with Samsung, Samsung support claims it's my problem and I have to pay to get them to reflash the latest update (which I've proven to myself is futile), in the meantime I'm left with a device that is essentially crippled by these frequent restarts and crashes. That's what I get for sticking with stock software ::sigh::. I may start exploring custom ROMs, which I tend to not trust due to the obvious security concerns, so I'm not left with a $700 brick as Sprint and Samsung worry exclusively about devices launched in the last 6 months.
tommacco said:
I've done factory reset, wiped cache partition, reflashed PE1 and PE2 to no avail. This all started with OTA updates- I didn't touch the software or try flashing anything myself until these problems persisted and didn't go away with factory resets. I've seen others report these same issues in sprint/other forums, seems they ran into similar issues with recent OTA updates of the S5 as well. Sprint claims they're aware of this and are working with Samsung, Samsung support claims it's my problem and I have to pay to get them to reflash the latest update (which I've proven to myself is futile), in the meantime I'm left with a device that is essentially crippled by these frequent restarts and crashes. That's what I get for sticking with stock software ::sigh::. I may start exploring custom ROMs, which I tend to not trust due to the obvious security concerns, so I'm not left with a $700 brick as Sprint and Samsung worry exclusively about devices launched in the last 6 months.
Click to expand...
Click to collapse
It's things like Carrier IQ, ItsOn, Knox, infrequent kernel updates (well that may be corrected now with monthly security updates) and bloat that prohibits my trust of carrier and manufacturer to get things right where my battery doesn't drain, phone doesn't lag and get warm for no apparent reason. Just hate the feeling that someone else just used my phone when I wake it out of standby.
I may have to agree to those terms to run the software but it doesn't prohibit developers from using open source code and methods to make things work better. IMO, that improves personal security rather than put me at risk. It may only be network meta data that Sprint retrieves with ItsOn but that doesn't come without a loss of battery and resources (induced drain and lag).
I trust little but the ROMs I run are mostly stock. Just have the garbage removed or under control with some added custom features. But I still can't deal with Sprint Zone running on my phone but I may not be in the majority on that one. I freeze it.
You mentioned checking custom ROMs out, freeza has a PE1/PE2 ROM out that takes an additional step to prevent some of the things I've brought up with rooted phones. It may help with your frequent reboots. I'm running it with PE1 bootloader and baseband until those flashes are available for PE2 in the bootloader baseband thread.
Sent from my SM-N910P using Tapatalk
samep said:
It's things like Carrier IQ, ItsOn, Knox, infrequent kernel updates (well that may be corrected now with monthly security updates) and bloat that prohibits my trust of carrier and manufacturer to get things right where my battery doesn't drain, phone doesn't lag and get warm for no apparent reason. Just hate the feeling that someone else just used my phone when I wake it out of standby.
I may have to agree to those terms to run the software but it doesn't prohibit developers from using open source code and methods to make things work better. IMO, that improves personal security rather than put me at risk. It may only be network meta data that Sprint retrieves with ItsOn but that doesn't come without a loss of battery and resources (induced drain and lag).
I trust little but the ROMs I run are mostly stock. Just have the garbage removed or under control with some added custom features. But I still can't deal with Sprint Zone running on my phone but I may not be in the majority on that one. I freeze it.
You mentioned checking custom ROMs out, freeza has a PE1/PE2 ROM out that takes an additional step to prevent some of the things I've brought up with rooted phones. It may help with your frequent reboots. I'm running it with PE1 bootloader and baseband until those flashes are available for PE2 in the bootloader baseband thread.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah I don't really trust Sprint at all to be honest with you, or any US carrier for that matter... my options seem to be limited toward trying to deal with this nonsense, flashing custom ROMs for which I can't verify the security integrity (sure a lot of folks doing this stuff mean well, but it only takes one bad actor and all of the sudden what little privacy I have is gone), or switching to Apple who thoroughly QAs all of their releases, gives loaners out when problems arise, etc. None of those options are particularly appealing to me unfortunately.
---------- Post added at 05:30 PM ---------- Previous post was at 04:51 PM ----------
samep said:
I updated bootloader and baseband only to PE1 and flashed a custom ROM. Later flashed a custom PE2 ROM. The ROMs are Note 4our by @freeza beta 2 and beta 3.
I see nothing wrong with PE1 or PE2. Did you try a factory reset? It does seem data from Lollipop can interfere with custom ROMs on Marshmallow. Main issue I saw with that was ItsOn on the root folder: /carrier/ItsOn The apk in that folder can partially activate on a factory reset and continually reboot a phone trying to setup the ItsOn bootstrapper but cannot so the cycle continues until you fix it. Wiping internal memory and factory reset prior to custom ROM (especially after stock tar update) will help but the developers may have removed that possibility in recent ROMs.
OTA may be suspect too but may only apply if rooting it. ItsOn and Knox don't play nice with root.
I'm not aware of cross carrier issues though?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
It seems as though the PD1 firmware (had to remove the cache.img.ext4 and repackage it) has since fixed these problems. I will update this thread if I noticed the problems again, but if anyone else is coming across the problems I noticed I would highly suggest atttempting this line of remediation since Sprint and Samsung support will not help you.
tommacco said:
Yeah I don't really trust Sprint at all to be honest with you, or any US carrier for that matter... my options seem to be limited toward trying to deal with this nonsense, flashing custom ROMs for which I can't verify the security integrity (sure a lot of folks doing this stuff mean well, but it only takes one bad actor and all of the sudden what little privacy I have is gone), or switching to Apple who thoroughly QAs all of their releases, gives loaners out when problems arise, etc. None of those options are particularly appealing to me unfortunately.
---------- Post added at 05:30 PM ---------- Previous post was at 04:51 PM ----------
It seems as though the PD1 firmware (had to remove the cache.img.ext4 and repackage it) has since fixed these problems. I will update this thread if I noticed the problems again, but if anyone else is coming across the problems I noticed I would highly suggest atttempting this line of remediation since Sprint and Samsung support will not help you.
Click to expand...
Click to collapse
Why did you repackage cache? It only contains csc related things and I assume won't flash with odin unless the entire tar is repacked with a different md5
Like many other sprint users, I experienced serious problems with 5.1.1. This resulted in battery pulls and even a downloading boot. I starting looking into a fix. After flashing about every ROM for sprint N910P on this website, I either result in bootloop or the same problems persist. The problems are as follows:
-Can't boot, so I have to wait ~5 minutes to try again
-Boots straight to downloading, mmc read fail
-Boots fine
-Crashes to black screen around 80-90% battery (back to problem 1)
I cannot figure how to use odin anymore because it fails on nearly every rom I attempt. My reactivation lock is OFF.
I'll try to provide as much detail as I can, but I'm at my wits end with this phone.
Thanks!
If you can Odin OK1 stock tar, there is another root alternative: root stock with Chainfire Auto Root. CFAR has been updated for Android 5.1.1 Note 4
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Custom ROMs will take longer than 5 minutes to boot initially after flash. TWRP has been known to fail to flash or not properly flash after trying repeatedly to flash wrong tar with Odin or flash with reactivation locked. Which, if any, apply to you? I hope it's not hardware failure...
Sent from my SM-N910P using Tapatalk
Chainfire was going to be my next option. I think the first time I attempted using chainfire through odin, it ended in a bootloop. I haven't tried the update version though. I'll give that a shot.
Is there any way to fix this problem with TWRP (delete it and reflash)?
I'm starting to think its a hardware failure, which would suck because knox is tripped and warranty expired a few days ago anyway I believe.
I downloaded the updated CFAR last night to verify it was updated. It's bundled with Odin 3.10.6 Use the defaults with that for stock OK1 tar.
You should know that CFAR is primarily for rooted stock.
If you want a custom ROM, you may have to use Philz CWM touch recovery for Note 4. TWRP just gets inoperative for some time for some users when tars fail in repeated attempts. Philz' seems to flash where TWRP doesn't if that's the case.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
Sent from my SM-N910P using Tapatalk
Sorry to be the bearer of bad news, but this is most likely a hardware problem. I've had two Note 4's do exactly this. Flashed the stock rom on both with Odin, problems still persisted. It would just get random restarts and sometimes boot into "panic mode", whatever that is. The quality control on these phones is terrible. I baby them and never rooted any of them, yet two of them messed up like that, and all 3 of course have GPS issues. If it worked like it's supposed to it would be amazing, my friend has had one since my first Note with 0 issues, super jealous.
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
bigbabo said:
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
Click to expand...
Click to collapse
To fix the WiFi and camera focus, get the bootloader for OG5 from OP in this thread and flash it in Odin.
https://forum.xda-developers.com/showthread.php?p=66352412
The ones labeled firmware are bootloaders. You don't have to flash the whole OG5 stock tar but you still could. Just make sure the flash restores that bootloader and you should be set.
Likewise, you could still restore a MM backup and restore its bootloader.
I think you should backup your keepsakes in internal memory and wipe internal memory before restoring a backup that crosses Android versions. With backups on extSdCard, you could wipe everything but that but I'd think you could factory reset, wipe internal memory plus the Android folder on extSdCard and have a good transition with the bootloader flash. Otherwise, a factory reset would be the minimum step but may leave some residual information you may not need cluttering your memory along with what you want to keep. Seems I recall some having issues coming back to lollipop from MM without wiping internal memory?
Just curious, do you recall what you wiped going back to lollipop?
Sent from my SM-N920P using Tapatalk
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
bigbabo said:
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
Click to expand...
Click to collapse
Gotcha. Just an old question in the back of my mind from early days of MM. I researched the TWRP thread, the developers recommended a factory reset.
If you've ever noticed internal memory available seemingly smaller than usual, it could be the extraneous folders.
Thanks.
Sent from my SM-N920P using Tapatalk
I'll try this again (this website crashed when first posting this)
Leased phone (January 2017) use for my business. Has had (3) OTA updates since April. Started having issues after 3rd update mid-June (freezes / reboots). Most times have to pull the battery to get it to boot. Have wiped & restore several times, from Settings and Recovery boot menu. Cleared App cache and partition cache. Had the local Sprint Store 'supposedly' flash the OS from a PC but nothing improved. Described these issues below but was only met with a blank stare and an offer to open my wallet to replace with a refurbished phone without knowing what is causing the issue.
On some occasions when the device is not responding it heats up. Messages of Apps that stop responding include System UI, Package Access Helper, Touchwiz and Gmail, among others.
When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '
Further trying to diagnose, Sprint Zone / Device Diagnostics / Flagged / System Updates - always states 'Update now', but Settings / System Update / Software update message reads 'The latest updates have already been installed (N910PVPS4DPE2 / N910PSPT4DPE2 / N910PVPS4DPE2).
Investigated alternatives with Samsung (they replied the same day, Sprint Community message July 20th still hasn't replied) I can take it to a service center to have the hardware checked for a fee but it is not nearby and I'd like to first understand what the issue is.
From what I've described does anyone know what could be causing these issues? I have read where some updates were causing problems but I've tried most of those remedies and nothing has helped yet. Perhaps the Sprint Store, in an effort to extract more money (this is how it seemed) did not or was not able to flash the OS?
Any help would be greatly appreciated.
best thing to do is odin back to an older version and retake the update if you wanna go thru that again
but id recommend reverting back to OG5 and then flashing a rom you will have less reboots....as least on my end i did
JLFitzpatrick said:
...When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '...
Click to expand...
Click to collapse
The stock recovery you describe, it's normal for the Android guy to fall down and display the red x or whatever you saw when there's no update to apply but the dm-verity failure isn't normal. It could indicate bad repair or maybe it was rooted at some point? Wiping and Odin flash doesn't always rid the phone of that but Knox trip remains always until Samsung repairs a rooted phone. Dunno the cause of your dm-verity failure but maybe, if it was stock un-rooted all along, it may a read only partition failed or corrupted?
As suggested above, you may fix the dm-verity by taking a couple of OTA updates after Odin flashing an older one. Don't go back any older than OG5 though.
I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times.
That may solve some issues but it could be hardware failure or a corrupt partition. If the dm-verity goes away, see if your problems are resolved. If you didn't root and have a warranty, make whoever warrants it replace it; the failure is legit.
Sprint Zone and ItsOn is garbage IMO. Bloat that kills the experience that Samsung intended. Albeit, Samsung isn't so innocent with bloat ruining the experience either. Just my opinion on the bloat. By the time users add their own bloat, there's but enough RAM and with all the services running, battery takes a hit and phone lags. Run package disabler (search in Google Play) or root to manage it is what I'd suggest. FWIW, I have no random reboots or phone heating up while in standby running Marshmallow. My phone sleeps like a baby.
If no warranty applies and root is an option, you could try rooting with Chainfire Auto Root for Note 4 and then full un-root. The developer removes the dm-verity flag if it's there for modified read only partition reasons. But of coarse that also trips Knox warranty bit, so be aware. Dm-verity can prevent OTA's from updating but that's an alternative with root and Knox trip risks. No warranty should mean less risk unless the phone belongs to your employer.
Sent from my SM-N910P using Tapatalk
Thank you for your replies.
I had pointed out the 'dm-verity verification failure' text to the goof-offs at the Sprint Store, you'd think I was speaking in a foreign tongue. Phone is leased on our personal family plan and used for my business. I've never rooted it myself, not sure what the Sprint people did at the store but that text was there before they supposedly flashed the OS.
I apologize but am in over my head with the suggested repairs. Although having upgraded PC's am familiar with the process; revert to previous clean OS and upgrade over that. I'll take your suggestions and just have to study a little more to understand the correct procedure.
Yesterday afternoon I tried the folks at Samsung again since their support team had replied the same day before (still waiting for a support response from Sprint since July 20th) and went to a live support chat. The woman was very helpful but unfortunately, I had to jump off for a meeting. Before I jumped off she had me put the phone into Safe Mode. I had tried to get there before but the instructions I was given were incorrect (not found in recovery boot). It has since been in that mode and has been much more stable, still freezes occasionally but doesn't reboot itself and runs zippy as hell except for momentary freezes. I have the Chat ID # and will try again today to see what they can do before trying other suggestions. I gave them the HEX DEC numbers and it sounded like they could access the phone with those, this morning their Chat was full so I'll have to try later.
samep, if you don't mind can you give me some clarification on your suggestion:
"I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times."
My interpretation:
Settings / Security / disable reactivation lock
Remove accounts (first back up phone log & sms to samsung account, back up wifi passwords to google account)
Settings / Backup and reset / Factory data reset
Boot to recovery menu / factory reset again (partition and dalvik cache evidently get cleared through reset)
Boot to recovery menu / 'flash an older tar' ? (Is this 'Apply update from ADB (Odin)' or SD card? This is where things get fuzzy. Can I load the stock tar (OS?) to a formatted sd card and apply the update from there or do I have to install Odin on a PC? Where is the best place to get a 'stock tar' (or Odin) from and which version(s) should I use for a Note 4, or is that explained on a particular website. There are many sources of information on Odin and firmware but I'm not sure which to trust if I need to do this would prefer to do this just once.)
Thank you again for your help, and I apologize for my ignorance on this subject.
But the best thing about ignorance is that it can be overcome with a little effort and knowledge.
To answer the question, boot into download mode from powered down state by holding volume down, menu and power. Yes, you use Odin installed on PC for that. But first you need the Samsung USB driver and Odin installed, plus the stock tar.
This thread will get you going with resources and brief instructions.
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
I'd suggest PC1 stock tar, then let it OTA.
(Your interpretation was mostly right up to the question about how to flash the tar after the factory reset and power down.)
Sent from my SM-N910P using Tapatalk
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
JLFitzpatrick said:
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
Click to expand...
Click to collapse
If you're feeling overwhelmed, you could bring it in. There's a chance it is hardware and the steps may prove redundant.
Up to you. At least you have something to point to as an issue.
Sent from my SM-N910P using Tapatalk
So I've gone through all the steps, phone is wiped, reinstalled Samsung USB Driver, have Odin open as Administrator and the phone in 'Android Recovery', Phone does not show up in Odin.
Have seen a couple versions of setting a connection (Odin open first, phone connected first); tried all of those and tried Odin open not as administrator. There is no connection. Tried other instructions to put into Developer Mode and enable USB bugging. Nothing, disabled USB bugging and booted back to recovery. Still nothing.
In Recovery mode it does not state 'Odin mode'. Tried the Recovery menu option 'Apply update from ADB' message reads 'Update from external storage diabled'. Tried 'Reboot to bootloader' (WTH), that does show Odin Mode at top of screen but phone still does not show up in Odin on PC. Then have to pull battery to reboot to Recovery mode. What steps am I missing here?
When phone is booted up normally it connects to PC without issue.
Finally got Odin to recognize the phone. Through a few searches I tried one remedy that suggested manually updating the samsung usb drivers in device manager which did the trick. Realized earlier that from recovery mode you do need to select boot to bootloader to get into Odin mode (listed on top).
Installed 6.0.1 - PD1 currently phone is installing OTA updates, hopefully this does the trick. Thanks again for your help.
On Tuesday the phone updated OTA from PD1 (April 27, 2016) installed via Odin to PE1 (June 1, 2016) then PE2 (June 29, 2016). Recovery Mode screen no longer shows dm-verity failure message so that's fixed. Phone is mostly stable, however still not as stable as it was on PE1 from what I recall by the release dates. Phone still freezes although it usually does not crash if I leave it alone but still does crash at least once a day. Safe Mode does not help, as the worst culprits are system Apps (Gmail, Drive are the worst).
It seldom overheats now but did yesterday. 3rd Party CPU cooler found Package Access Helper, Context Service and System UI as causing an issue. Cleared App Cache for all three but problems persist. Clearing App Cache in Settings / Storage takes at least three tries to clear all but 4.00 KB. I have been clearing Partition Cache every morning just to get through most of the day otherwise it will freeze when I first start to use it. Battery is also draining faster than before.
Any suggestions? OTA updates were at work on a stable WiFi signal. I'm thinking of Odin flashing back to PE1 (or PD1) and stopping further OTA updates. Anybody tried this? Will be traveling for a couple of weeks and need a stable phone, like I used to have. Thank you.
Samsung has been having memory management issues. IMO, this is the reason they keep increasing RAM in recent phones and getting help from Google. But 3 gigs of RAM should be sufficient.
A custom ROM may resolve that but you could try a package disabler from Google Play to freeze some unneeded bloat.
I couldn't say which stock version is best because I've ran all of them without random reboots and lag is minimum. The custom ROMs have been daily driver stable for me. I use them when traveling too.
Sending PM to OP as well with additional info.
Sent from my SM-N910P using Tapatalk