Hi all,
Thrilled and surprised to see we finally got an update for our AT&T Note 8s, but I'm having issues.
I had my Note rooted and unlocked (in an attempt to use TMo's free tablet data promo) previously, but no custom ROM. I don't recall ever disabling knox or any system apps. I first unrooted within SuperSU, but the update failed. I then tried it both with the AT&T SIM and the TMo SIM, both failed. I tried a standard factory reset, still failed.
I started escalating options then, and used Odin to flash a completely fresh and stock 4.1.2, update still failed. I'd love to use Odin to flash the 4.4.2 image, but I can't find an Odin compatible download of it. I did find a cfg of the OTA update someone uploaded, bu I'll admit to having no idea how to manually apply that.
I had thought I got everything back to completely stock, so I'm not sure what's causing the failure. The info on the Odin screen seems to suggest that too:
odin mode
product name: SGH-I467
custom binary download: no
current binary: Samsung official
system status: official
Any ideas of how to get this updated?
Thanks!
edit: I don't have AT&T service any more (although I still have the SIM), would that have anything to do with it?
IIRC 26% is the file ddexe, which is overwritten by the rooting process. Probably this file didn't get restored properly. If the automagical processes aren't doing it you'd need to go into /system using root explorer or similar to delete the invalid one and rename the _original one to replace it.
Well there was progress, but now it error'ed at 31%. Any other files in particular that I'd need to manually revert? I didn't see any others in system/bin that were _real.
Exact steps were: re-root, used ES File Explorer (with root permissions) to rename ddexe to ddexe_root and then rename ddexe_real to ddexe, removed root via SuperSU, attempted OTA update, got excited when it passes 26%, then got said when it failed at 31%.
Thanks!
There's a log that's generated during the OTA update process, off the top of my head I forget exactly where it is, but some googling should point you in the right direction. Examine the log and you'll see an error along the lines of:
file xxxxxxx: signature does not match
Well, I'm not quite sure which part of my tinkering did the trick, but I've successfully gotten my Note 8 (i467) to update OTA to 4.4.2.
I hadn't tried since December, so I started with just a regular update. It of course failed again, like it had been doing previously.
I then downloaded the 4.1.2 firmware file from sammobile and used odin 3.09 to flash the AP. I was surprised that doing that didn't wipe the device (it was late and I was sleepy), so I decided to try again. This time I added the firmware file to BL, AP, CP and CSC, trying to completely reset everything possible to stock. After 5-10 minutes, odin gave a fail message, but it wasn't clear exactly where or when it failed. The Note also would not boot, it asked for a Kies recovery.
I then used odin one last time to flash just AP. This succeeded and the Note was back up and running, with all my previous data intact. Next I did a factory reset within the Android Settings screen. Once that finished and I connected to wifi, it began to download the OTA update on it's own. And low and behold, it rebooted and got past the 31% mark it kept failing at... and made it all the way to 100%! Success!
So I know a lot of that wasn't necessary (and probably not even correct) but I was fed up with months of trying to get this to update so I just said to hell with it and started tinkering with random things. Just in case someone has the same issue I did and stumbles upon this thread, I wanted to record exactly what I did, even though I'm sure most of it was redundant and unnecessary.
So i just spent the last 4+ hours trying to figure out what the latest firmware for the Samsung Galaxy S3 SPH-L710 since google was not my friend tonight.
So i had L710VPUDNJ2 installed on my phone... rooted, TWRP, unlocked bootloader.
I kept getting prompts about an update for the phone, and finally decided i couldn't ignore it anymore, so my journey began to get rid of it.
1st Headache; What is the latest firmware for the phone?
Well according to Sprint's Website for the SPH-L710 the latest version available is L710SPTBMK5.
OK, cool, this should be easy.
Go find a flashable ROM; [ROM][MK5][STOCK][ODEXED/DEODEXED] and flash it to my phone.... Stuck on boot... ****...
2nd Headache; Latest Flashable ROM is CRAP!
Boot back into TWRP and decide to say **** it and do a full wipe.
Wipe System/Data/Dalvik/Cache
Flash MK5 Rom
Reboot phone
Success!
Phone boots up and i can start tweaking it back to my standards... but wait... what's this? No cell signal at all...
Ok this is strange, but it's Samsung after all, so i expect it to be **** and have issues.
I go into Settings and look at the Mobile Networks settings... No Network mode selected.
I choose LTE/CDMA, the phone says it needs to reboot, i tell it OK
Thinking this was the problem and i am smarter than i apparently am, i started to smile and give myself a good pat on the back when the phone booted back up and still no signal.. WTF!?!?
At this point i'm convinced that XDA forums has the dumbest people in the world posting Roms on it and i decide to take on a new approach.
3rd Headache; Finding and downloading everything
So i know that L710VPUDNJ2 is a legit version for the SPH-L710 to work with Sprint.
So i find the ODIN download for it; [STOCK][ODIN][TAR] L710VPUDNJ2 PC Odin Flashable ( Sprint )
I download the latest version of Odin; Odin3 v3.10.7 (this version might change over time just fyi)
I downloaded the latest version of USB drivers for the phone; USB (Driver) ver.1.5.45.0 (this version may also change over time)
And then proceeded with the following
Install Latest drivers
Reboot PC
Put phone into "Download Mode" (Vol Down + Home + Power)
Ran Odin3
Clicked on AP and selected the NJ2 tar file (after extracting it from the .zip file of course)
Connected the phone to my PC
Clicked START after Odin3 recognized the phone
Well, low and behold after 20 mins or so, i have a working phone again! :good:
I go into the phone's settings and force it to check for an update, and wouldn't you know it, it found one!
I download and install the update, wait for it to come back up, and then immediately go to check what version it's on.... L710VPUDOH1
Well that's nice and all, the sprint website did say that was a version after L710VPUDNJ2, but it's not the LATEST version according to Sprint.
So, i go back and force the phone to check for updates.... Nothing!
So there you have it. Don't believe everything you read on the internet.
TL;DR: Sprint website lies. Use the links above to get on the latest version.
Well, you can't update with a rom zip. To update, you always have to use a .tar in odin. The .tar files contain the modem and bootloader files, which are required for an updated phone to boot.
You are lucky you didn't try an mk5 tar, you would have a hard brick. That is pre Knox firmware (4.3 jellybean). I heard there was a new mk5 too, I don't know for sure. But the first mk5 was the boost and virgin Mobile version of mk3. But someone posted they got an mk5 update that said stagefright patches, so.... Not sure. But oh1 and oj1 are the newest, I believe, for sprint, and boost/vm. Respectively
That thread you linked for the mk5 flash able zip clearly said jellybean 4.3 and that date was a couple years ago. Clear indication that it was not new.
There is supposedly a new MK5 that is supposed to fix Stagefright completely as opposed to a half fix from OH1.
L710SPTBMK5
Previous was L710VPUDOH1.
However, I suppose at this point, most of the userbase has already upgraded to a new phone or installed a custom ROM, so anything on this forum that's not 2015 and says MK5 is too old.
So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.
All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.
ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.
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