On Ani2 rooted. 64gb card not mounting. Card mounts and reads fine in note3, gs3 and computer. Tried formatting ntsc,Exfat,fat32. 4 and 8 gig cards mount fine in gs5. Hit mount says card is blank or has unsupported file sys. Card is three weeks old. What gives?
jasonbtx said:
On Ani2 rooted. 64gb card not mounting. Card mounts and reads fine in note3, gs3 and computer. Tried formatting ntsc,Exfat,fat32. 4 and 8 gig cards mount fine in gs5. Hit mount says card is blank or has unsupported file sys. Card is three weeks old. What gives?
Click to expand...
Click to collapse
I had similar problems see this link http://forum.xda-developers.com/verizon-galaxy-s5/help/4-4-4-ni2-update-sd-card-blank-t2885047
Only fix I found was to rollback to NE9
Roger
That did the job. Shame ya gotta roll back to fix it.
Agreed.
jasonbtx said:
That did the job. Shame ya gotta roll back to fix it.
Click to expand...
Click to collapse
I had this problem also a month ago or so. Rolled back to fix the issue. Later found out that it was the phone hardware. Had VZW replace it, all is working well now.
Running NI2 and not a problem with a new 64g
128 GB ftw #flashingromsforlife
This is a common problem with the NI2 OTA update. You can use Odin to flash the NI2 Full Stock Tar and it should fix the issue. Here it is if you'd be interested in doing it.
https://www.androidfilehost.com/?fid=23622183712474060
Also encountering this problem. I backed out to NCG and all my SD cards started working, Installed one of the NI2 Roms from Andoid Dev and it stopped working again.
I'll try the full stock one next to see what happens and update the thread accordingly.
---------- Post added at 06:31 AM ---------- Previous post was at 05:38 AM ----------
Made no difference even using the full official rom.
lordcalin said:
Also encountering this problem. I backed out to NCG and all my SD cards started working, Installed one of the NI2 Roms from Andoid Dev and it stopped working again.
I'll try the full stock one next to see what happens and update the thread accordingly.
---------- Post added at 06:31 AM ---------- Previous post was at 05:38 AM ----------
Made no difference even using the full official rom.
Click to expand...
Click to collapse
Wow that's crazy! Samsung really needs to get their crap together and fully test everything before they release updates. It's still very odd how it works on some phones with NI2 firmware, but it doesn't work on others. There was a similar problem with the original Motorola OG Droid. I can't recall the exact issue it's been so long, but some would have the issue and others wouldn't. It turns out that some had a slightly different chipset, even though they were the same exact model phone. I wonder if Samsung has cut some corners on some of the devices and it's a similar situation.
So I was nagging verizon over twitter about this...
"Thanks for clarifying! I apologize for the inconvenience. An update for the issue we be addressed w/ the next software update"
Lets see if it really is fixed with the next update, or if they were just trying to get rid of me.
lordcalin said:
So I was nagging verizon over twitter about this...
"Thanks for clarifying! I apologize for the inconvenience. An update for the issue we be addressed w/ the next software update"
Lets see if it really is fixed with the next update, or if they were just trying to get rid of me.
Click to expand...
Click to collapse
Lol... I think they just wanted to get rid of you JK. I'm not really sure if the hardware differences are present in any of the Samsung phones, but theoretically it's a possibility, because I've personally witnessed it on other devices before. It's weird though because mine was able to read a 128GB card while I was on NI2 firmware. I'm sure it's just a little kink that will be worked out in an update though.
P.S. You never have to apologize for asking questions or think you're being inconvenient. You can never learn if you don't make an effort to, and asking questions is just part of that.
A very short batch hardware difference is the only thing I could think of as-well. It otherwise makes no sense that for the vast majority of people there was no problems, but a select few (at least who posted about it) can be found if you dig deep enough. In all cases so far that I've read about they took the phone to Verizon and it was replaced with one that works. Unfortunately since i'm not in the U.S I don't have that option so I'm praying on it will get fixed.
Related
Just got my OTA for the Verizon update. Given the success in the P-605 thread with achieving root post install, I'm taking the update and will report back.
Here's some more info - http://www.verizonwireless.com/support/samsung-galaxy-note-10-2014-update/
Ran into an install error (the infamous error 402), so having to use Verizon's Software Updater to try to get it to install.
Can you root after install?
Sent from my SM-N910V using Tapatalk
tolymatev said:
Can you root after install?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Can't get installed. It is a 2 step update and I got a 402 error on the 2nd update. Thought from searching that I could use the built in Verizon Software Update utility but getting an incompatible Firmware error from it. The new versions aren't up on Kies yet and trying to Odin back to the previous is erroring out (though trying once more now).
So at this point I'm stuck until they release the latest through Kies or I find a chunk of time to get on the phone with Verizon tech support.
i get an error also. i even factory reset my device to see if itll go through and still a no. "Update failed, 402"
---------- Post added at 08:59 AM ---------- Previous post was at 08:42 AM ----------
Im talking to Verizon support right now. will update with the answers i get
---------- Post added at 09:22 AM ---------- Previous post was at 08:59 AM ----------
What a useless ***** on the chat. she's so stupid i don't understand how she got a job at support.
Unfortunately I suspect we are stuck until they either update the Verizon Update app to recognize the new firmware versions or Samsung releases it through Kids..... I don't remember what the normal delay is between OTA and Kies but suspect it will be a week or so.
rgerrans said:
Unfortunately I suspect we are stuck until they either update the Verizon Update app to recognize the new firmware versions or Samsung releases it through Kids..... I don't remember what the normal delay is between OTA and Kies but suspect it will be a week or so.
Click to expand...
Click to collapse
Ummm...Last time I checked, Samsung doesn't release updates through kids...
Shawn5162 said:
Ummm...Last time I checked, Samsung doesn't release updates through kids...
Click to expand...
Click to collapse
I don't know, my 14 great old can be pretty sharp I even caught that the first time spell check "corrected" it, guess it decided even after two times I still didn't want to spell it Kies....
So here is the latest. After chatting with a helpful Verizon rep, they said that due to the device having been previously rooted (even though I had uninstalled root prior to updating) that might be causing the issue and that I'd have to talk with Samsung. The Samsung rep said that yes, the reported baseband is 5.1.1 so that is likely causing the issue that it took the 1st OTA but not the second. Unfortunately they can't update it through Smart Switch (their Kies replacement) and said I'd have to take it into a Samsung service center in a Best Buy since they'd have the tools to get it on the right firmware. Heading there today or tomorrow so will report back.....
i went to bestbuy and the samsung guy tried to be very helpful but he couldn't, his programs dont show an update for our devices yet. He wouldnt believe me when i told him im suppose to get 5.1.1. Note pro 12 doesnt have 5.1 theres no way note 10.1 is getting it is what he told me.
Then i inserted my phones sim into the note 10.1 and we checked for an update, he saw the error and he saw that there was an update 5.1.1 available for download. We tryed to update it again but it also failed.
So i went home after spending 1 hour at bestbuy without success.
The tech I met with ran a diagnostic and identified that I had a "binary mismatch" which requires 2 hours to fully reflash the device. He unfortunately didn't know how to do it so I have to go back when the more experienced tech is working.
I think we are all in the same boat. I received and installed the first OTA update, then the second one failed with the 402 error. I tried Kies and it states that I have the latest firmware. The 402 error seems common with Verizon OTA updates. I may try a trip to Best Buy also, but I don't think that the update is in full effect yet. One positive for me, the tablet seems a bit better after the first OTA received yesterday.
I was told once they get the update on their computers they can push it to any device. Hopefully thats the case.
I wonder if we can odin back to the previous version we had. If it works it'll be all stock without any root history. Maybe it'll work that way.
Just thinking out loud
Sent from my SM-N910V using Tapatalk
tolymatev said:
I was told once they get the update on their computers they can push it to any device. Hopefully thats the case.
I wonder if we can odin back to the previous version we had. If it works it'll be all stock without any root history. Maybe it'll work that way.
Just thinking out loud
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Tried Odin with 4.4.2 but ran into the same binary mismatch. Assumed it was from a changed bootloader, but not technical enough to know.
Likewise think that might be a path forward once they publish the firmware, but no sign of it yet (I know it normally takes a week or so to see it show up on SamMobile)
How did you root? Has anyone had success with this? Is your tablet still usable?
Sent from my SM-P605V using Tapatalk
I got the update. It was available through Kies this morning. Installed without any problems.
cajun456 said:
I got the update. It was available through Kies this morning. Installed without any problems.
Click to expand...
Click to collapse
Thanks for the heads up. I'll see if it will install and save me a trip to Best Buy today
KwestJones said:
How did you root? Has anyone had success with this? Is your tablet still usable?
Sent from my SM-P605V using Tapatalk
Click to expand...
Click to collapse
Haven't yet. After the headaches of getting it installed may take a breather before rooting. Here's a good summary from the P605 thread (obviously skipping the first couple of flashes and starting with the permissive kernel flashing) - http://forum.xda-developers.com/gal...xy-note-10-t3215876/post63187053#post63187053
rgerrans said:
Haven't yet. After the headaches of getting it installed may take a breather before rooting. Here's a good summary from the P605 thread (obviously skipping the first couple of flashes and starting with the permissive kernel flashing) - http://forum.xda-developers.com/gal...xy-note-10-t3215876/post63187053#post63187053
Click to expand...
Click to collapse
My bad...my question was how did you root before the update? With towelroot? Does that make a difference or was it just a bad update from vzw?
Sent from my SM-P605V using Tapatalk
Mine was rooted with towelroot. The first update wiped out root. The OTA error for the second update can happened whether you are rooted or not.
Since people turned the original OTA thread into a **** show, and the current one has the thread locked I'm creating this. Before the thread was closed we had multiple users complaining of a repeated error after attempting to sideload the OTA involving the device looking for incorrect version numbers.
I don't know if anyone found a solution yet but knowing how impatient most of us are to get this update I decided to make a discussion thread and see if we can't get it working or at least find out a solution.
Solution: Flash the latest 1gb firmware in fastboot, skip through setup wizard but be sure to add a wifi access point, then check for updates, you should get the OTA, everything is fine so far, no issues whatsoever. Thanks to @hp420 for making the suggestion
l3ones said:
Since people turned the original OTA thread into a **** show, and the current one has the thread locked I'm creating this. Before the thread was closed we had multiple users complaining of a repeated error after attempting to sideload the OTA involving the device looking for incorrect version numbers.
I don't know if anyone found a solution yet but knowing how impatient most of us are to get this update I decided to make a discussion thread and see if we can't get it working or at least find out a solution.
Click to expand...
Click to collapse
The only things you really need to make sure flashing the OTA manually works perfectly is to
1. Have the stock recovery installed
2. Have the right firmware installed (matching the firmware number with the one in the OTA)
3. Have an unmodified system partition (i.e. no root/busybox/mods etc.)
4. Flash the OTA that matches your SKU ID (e.g. Flashing an XT1540 OTA on an XT1540 Moto G3)
And the only reason my thread is locked is to give the users the links to the OTA without the **** show
dd98 said:
The only things you really need to make sure flashing the OTA manually works perfectly is to
1. Have the stock recovery installed
2. Have the right firmware installed (matching the firmware number with the one in the OTA)
3. Have an unmodified system partition (i.e. no root/busybox/mods etc.)
4. Flash the OTA that matches your SKU ID (e.g. Flashing an XT1540 OTA on an XT1540 Moto G3)
And the only reason my thread is locked is to give the users the links to the OTA without the **** show
Click to expand...
Click to collapse
The issue was with #2. When trying to flash the 2gb version of MM on the phone it was asking looking for 23.72-65, now there is one for the 1gb but not the 2gb, at least not posted. From the info I gathered it seems that the 72-65 firmware for the 2gb version was the soak test version. I think, I could be wrong but from other posts that I saw the soaks for 2gb ended in 65.
dd98 said:
The only things you really need to make sure flashing the OTA manually works perfectly is to
1. Have the stock recovery installed
2. Have the right firmware installed (matching the firmware number with the one in the OTA)
3. Have an unmodified system partition (i.e. no root/busybox/mods etc.)
4. Flash the OTA that matches your SKU ID (e.g. Flashing an XT1540 OTA on an XT1540 Moto G3)
And the only reason my thread is locked is to give the users the links to the OTA without the **** show
Click to expand...
Click to collapse
The issue is that the OTA is looking for a version number never released for the 2gb version. I'll try it again and type up the error output.
l3ones said:
The issue is that the OTA is looking for a version number never released for the 2gb version. I'll try it again and type up the error output.
Click to expand...
Click to collapse
To be exact it's looking for "motorola/osprey_retus_2gb/osprey_u2:5.1.1/LPI23.72-65/51:user/release-keys".
Could I just edit the metadata.json to look for the proper version and repack/resign?
l3ones said:
To be exact it's looking for "motorola/osprey_retus_2gb/osprey_u2:5.1.1/LPI23.72-65/51:user/release-keys".
Could I just edit the metadata.json to look for the proper version and repack/resign?
Click to expand...
Click to collapse
If I knew how to do this I would give it a try
Well, since it has to be signed by the OEM, I've decided to just pull the files and get cooking on a rom for it. I forgot how long it takes cygwin to install
Person who grabbed that ota here. I guess it's too late for me to go through and try to dump the firmware that apparently I'm the only one to have?
New to this whole business, are we sure the 2gb LPI23.72-65 firmware was "never released" or just "never caught"? The firmware dl thread has only two listed for the 2gb version, but four for the 1gb version.
(re: cygwin I'm running linux native on my end if there's anything I should be messing around with)
Just flash the 1gb factory image it wants you to have, then the ota
Gotolei said:
Person who grabbed that ota here. I guess it's too late for me to go through and try to dump the firmware that apparently I'm the only one to have?
New to this whole business, are we sure the 2gb LPI23.72-65 firmware was "never released" or just "never caught"? The firmware dl thread has only two listed for the 2gb version, but four for the 1gb version.
(re: cygwin I'm running linux native on my end if there's anything I should be messing around with)
Click to expand...
Click to collapse
Im not 100% sure about the whole never release part, Im going by the official firmware page that we have here. Im just thinking it would have been captured by now if it was out there.
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
hp420 said:
Just flash the 1gb factory image it wants you to have, then the ota
Click to expand...
Click to collapse
If you flash 1gb firmware on the 2gb and then do the OTA, im guessing its going to be the 1gb MM firmware?
Do you think it would be possible to the run the 2gb MM update through stock recovery after?
hp420 said:
Just flash the 1gb factory image it wants you to have, then the ota
Click to expand...
Click to collapse
Did you wind up doing this? Everything normal in the end?
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Gotolei said:
Person who grabbed that ota here. I guess it's too late for me to go through and try to dump the firmware that apparently I'm the only one to have?
New to this whole business, are we sure the 2gb LPI23.72-65 firmware was "never released" or just "never caught"? The firmware dl thread has only two listed for the 2gb version, but four for the 1gb version.
(re: cygwin I'm running linux native on my end if there's anything I should be messing around with)
Click to expand...
Click to collapse
Only thing im thinking is that the 6.0 ota somehow patches to 65 then up to the 6.0
minieod said:
Did you wind up doing this? Everything normal in the end?
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Only thing im thinking is that the 6.0 ota somehow patches to 65 then up to the 6.0
Click to expand...
Click to collapse
So far everything seems normal. I ran the newest 1gb firmware, got the OTA, saved the link, Installed it. Phone is currently optimizing apps. Will keep you posted. If all seems well I will try to run the 2gb Update on top of this one, if possible.
UPDATE: All seems to be running fine, in system options it does show that im on the 1GB versus the 2GB of Marshmallow (not sure how this will effect anything in the long run). Seems a bit smoother, but that could just be placebo. As everyone posted, everything looks pretty much the same. Lock screen has a new font, IMO it looks cleaner.
pl4life52 said:
So far everything seems normal. I ran the newest 1gb firmware, got the OTA, saved the link, Installed it. Phone is currently optimizing apps. Will keep you posted. If all seems well I will try to run the 2gb Update on top of this one, if possible.
UPDATE: All seems to be running fine, in system options it does show that im on the 1GB versus the 2GB of Marshmallow (not sure how this will effect anything in the long run). Seems a bit smoother, but that could just be placebo. As everyone posted, everything looks pretty much the same. Lock screen has a new font, IMO it looks cleaner.
Click to expand...
Click to collapse
This is exactly as I suspected. The person who pulled this URL has a 2gb device, which was bought used. The owner before them must have flashed the 1gb factory image to have it on the newest firmware, since the only way to be fully updated on the 2gb is via the most recent 5.1.1 ota....so they flashed a 1gb factory image to take the easy route and shipped it out.Then when the ota notification came through it was for the 1gb variant since it was running 1gb firmware.
Simple solution....flash the most recent 1gb factory image and hit the update button. It seems to be working for everyone.
hp420 said:
This is exactly as I suspected. The person who pulled this URL has a 2gb device, which was bought used. The owner before them must have flashed the 1gb factory image to have it on the newest firmware, since the only way to be fully updated on the 2gb is via the most recent 5.1.1 ota....so they flashed a 1gb factory image to take the easy route and shipped it out.Then when the ota notification came through it was for the 1gb variant since it was running 1gb firmware.
Simple solution....flash the most recent 1gb factory image and hit the update button. It seems to be working for everyone.
Click to expand...
Click to collapse
Got it from Best Buy, actually. Not used.
Just got it for Christmas, and I'm guessing the people around here have had their phones for a while?
Gotolei said:
Got it from Best Buy, actually. Not used.
Click to expand...
Click to collapse
Well I got nothin' then lol
I got mine in September from motomaker
Gotolei said:
Got it from Best Buy, actually. Not used.
Click to expand...
Click to collapse
Does your system options show 1gb or 2gb version?
yoyoche said:
Does your system options show 1gb or 2gb version?
Click to expand...
Click to collapse
2gb all around.
Well nuts
pl4life52 said:
So far everything seems normal. I ran the newest 1gb firmware, got the OTA, saved the link, Installed it. Phone is currently optimizing apps. Will keep you posted. If all seems well I will try to run the 2gb Update on top of this one, if possible.
UPDATE: All seems to be running fine, in system options it does show that im on the 1GB versus the 2GB of Marshmallow (not sure how this will effect anything in the long run). Seems a bit smoother, but that could just be placebo. As everyone posted, everything looks pretty much the same. Lock screen has a new font, IMO it looks cleaner.
Click to expand...
Click to collapse
when you get into about phone and all that. it shows 1GB. what about when you go to settings > memory ... does it show XXXMB / 1.0 GB being used, or 2.0?
Updated the OP with solution for visibility. It worked great for me.
Tested right before replacing my N7 (v1)...
After upgrading to latest API4 "Green Battery" Update...
Confirmed:
- Unable to Odin Sprint "Root" Firmware...
- Unable to downgrade to APGC...
Result...
No root & stuck with API4... (Not bricked)
so... in other words... IF you want root... stay with APGC and simply wait for an API4 ROM... (with APGC bootloader)
Get the new phone... and DO NOT update...
[email protected]!
Sent from my SM-G928T using Tapatalk
Soon as my v2 comes in, I'm downloading the package disabler app first and blocking updates
---------- Post added at 10:59 PM ---------- Previous post was at 10:58 PM ----------
I'm not losing my only chance at root with this phone.. why would they revert back to the jelly bean battery color...like wtf
To make it easier to identify version 2 phones.
OP care to explain how you updated to the V2 update on a V1 device ? e
MOD EDIT:
Please do not quote the whole OP when posting.
t0dbld said:
OP care to explain how you updated to the V2 update on a V1 device ? e
Click to expand...
Click to collapse
The API4 update is available to V1 phones. I took it, knowing I'd be getting a new phone in a couple of days.
As I understand it, they'll make you take it one way or the other.
i can confirm do not update your v2 note 7 to the new firmware. you cannot downgrade and they have blocked the sprint userdebug firmware from even flashing.
if you want to keep root. don't do it.
wht are the chances that the update comes straight from the box..
It does bro....i got mines today and it automatically started down loading...i just asked this question to @jovy23 in another thread
Yep, mine installed right out of the box. what a bunch of a-holes. wifes did the same thing, no root now welp, perhaps its time to return it and buy a different phone. this is retarded.
Chr0nicDreamz said:
Yep, mine installed right out of the box. what a bunch of a-holes. wifes did the same thing, no root now welp, perhaps its time to return it and buy a different phone. this is retarded.
Click to expand...
Click to collapse
what about restocking fee?
twe90kid said:
what about restocking fee?
Click to expand...
Click to collapse
why would I worry about that? tmobile owes me so many credits at this point I should have credit enough to cover my next bill
Saw someone mention it, and will try the same, but boot without sim card and wifif then disable the update app.....root then add sim.
Hopefully that will work cause I need my root. Dammit Samsung how dare you "burn" us again !!!
louforgiveno said:
Saw someone mention it, and will try the same, but boot without sim card and wifif then disable the update app.....root then add sim.
Hopefully that will work cause I need my root. Dammit Samsung how dare you "burn" us again !!!
Click to expand...
Click to collapse
as long as the phones don't come preinstalled then it's fine.
Well... I just updated to API4 intentionally, to try out the new update on my v1 device. I gotta say it's much more snappier now and lag is completely gone after it fully boots everything. But it's still not worth losing root over. So I'm either gonna get a refund or buy the international version, better yet might just say goodbye to sammy all together.
I don't know why anyone is still surprised about non-Nexus devices being locked down. Sure, a device might get root access, but it's the OEMs job to fix it in future builds because it's an exploit that needs to be fixed.
My update downloaded but I disabled, anyone know where the update file is? What folder? I can't find it.
the update ran as soon as it connected to their wifi network to set up the phone. crap, can't root now.
drum747 said:
My update downloaded but I disabled, anyone know where the update file is? What folder? I can't find it.
Click to expand...
Click to collapse
Same here, it downloads on its own but it can be postponed up to 3 times before it automatically installs the update, so what do I have to disable so the update won't install, or where can i find the update and delete that sob? Any info would be much appreciated as I don't have access to a computer to root or have the time at this very moment.
---------- Post added at 05:22 AM ---------- Previous post was at 05:20 AM ----------
drum747 said:
My update downloaded but I disabled, anyone know where the update file is? What folder? I can't find it.
Click to expand...
Click to collapse
What exactly did u disable?
You can go into settings and turn off auto updates, or download package disabler from the play store and disable the 2 software updates lines. I still have a v1 phone and no update here because of that
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
I got the same.
Sent from my HTC 10 using XDA-Developers Legacy app
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Mispelling
nanofoxx said:
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Click to expand...
Click to collapse
Sorry for the misspelling. I meant to say "without any problems" not "without many problems". In fact, the whole update process was smooth and fast. Everything works fine. I understand, however, that everyone's setup is different and my experience should not be the absolute rule.
Nothing here on my device. Although it might be because I'm in Sweden.
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
dingnecros said:
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
Click to expand...
Click to collapse
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Maris_ said:
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Click to expand...
Click to collapse
There's a whole new Lollipop firmware on the San mobile firmware site.
Yes...problems
My tablet updated and now the OS boots super slow and then does a soft shutdown and reboots a second time. It takes more than 60 secs to get to the home screen. Anyone know how to uninstall this update?
ADRz said:
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
Click to expand...
Click to collapse
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
I also have a SM-P605V but have Verizon as my carrier. I got the notification to update today. I don't see anything on VZW site about it nor under the specific SKU on SamMobile (still has 10/15/15 as the last official update). When looking at the SM-P605 model, there are some in the list (even today's date), though they are for non-USA countries.
Even so, it looks like they are still all Android 5.1.1, so it's likely just some minor tweaks. To my understanding, you would need to pop in an activated Verizon SIM to get the update for your specific tablet, as Verizon is the one that issues it. You can also wait until it's posted on SamMobile and manually do it. https://www.sammobile.com/firmwares/database/SM-P605V/
---------- Post added at 12:02 PM ---------- Previous post was at 11:33 AM ----------
I think I found the official from Verizon: https://www.verizonwireless.com/support/samsung-galaxy-note-10-2014-update/
Software Version: LMY47X.P605VVRSDPL1
The current software update gives you the most up to date Android™ security patch on your device.
Click to expand...
Click to collapse
(I called VZW and she confirmed that it was an Android Security patch, no MM, darnit!)
Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
You should be able to flash this now that Sammobile posted it... https://www.sammobile.com/firmwares/database/SM-P605V/
I got this a couple of days ago - managed to odin flash after I put the wrong file and got the boot loader triangle a day before.
Its extremely stable and the tablets working like a dream - the only issue is no root.
Edit: I noticed a great improvement in battery management and it will charge to 100% from 30% in 4 hours before I flashed the 5.1.1 rom it took nearly 8 hours with a new(second hand) USB Flex connector and nearly 20 hours with the old usb flex connector to go from 30% to 100%.
I really like this tablet - it reminds me so much of my SM-N910F note 4.
You can root the latest firmware and also install twrp. I have a 600.
louvass said:
You can root the latest firmware and also install twrp. I have a 600.
Click to expand...
Click to collapse
did it actually do anything? or is it not worth it
graffix31 said:
did it actually do anything? or is it not worth it
Click to expand...
Click to collapse
Probably just a security update
Please excuse my silly question but I have P600 with 5.1.1 and never rooted. Do I need to install twrp before I update or it doesn't matter? Updates always make me uneasy with locking bootloader or needing new root methods.
If you just want to update then flash with Odin and the appropriate file. Try looking at sammobile.com for the appropriate rom file.
If you want root then you will need to install a custom recovery using CF auto or Twerp - the latter will NOT work on the SM-605v version as the bootloader is locked and will result in the yellow triangle and stating that the tablet has a strange recovery and that you should see a verizon technician. By installing the recovery you can then update the system or even try out new roms created by the people of this wonderful community.
Rooting will potentially stop business application with built in security from working - i.e. HSBC application, Virgin Media app and Sky Movies apps will not work on rooted phones to name a few.
I updated and rooted and everything is working ok. I had trouble with 64gb Sandisk microsd with "sd card unexpectedly removed" error. Then it mount itself back. Sometime it shows empty and asks to format and sometime it works. Also the lockscreen flicker and that usually when the card error happened. I suspect they are related and it happens only when waking up the device. The card works fine with all my other devices including my note 4 on stock 5.1.1. I'm not sure what caused it because I just used this sd card with the note 10.1 and then updated and rooted all in the same day.
Anyway, I removed the Sandisk and now I'm using 32gb Samsung and it only happened once for maybe 12 hours (could have been 100 times with Sandisk). Also, I don't notice the lockscreen flickering anymore. I will see if this problem comes back or it just that Sandisk doesn't play well my note. I have seen many people here reported similar problem with other Samsung devices for too many reasons. I don't believe file format is the issue but I'm using exFAT.
In November I had bought 2 Samsung Galaxy S5's from Walmart through Straight Talk. One for me and my Wife. They worked perfectly until about the middle of March, and my Wife's phone had kept restarting non stop whether she was on it or not. Sometimes more than once in a 30 second span. Then one day it didn't do it for about 2 days.. then MY PHONE starts doing it. Non stop all throughout the night and just die from battery drainage. I eventually contact Straight Talk to do a swap for a different one since I still had warranty. It takes them about 10 days total for me to get my replacement. The entire time my phone was sent out my Wife's never restarted or acted up once. I get my replacement yesterday and mine phone is running great and hers tonight just RESTARTED ON IT'S OWN. I'm very confused because it seems are phone's are making one another restart? I have heard problems of the S5's restarting for no real reason at all, but why would hers be doing it only when I had gotten mine back up and running? I'm seriously out of answers and tired of this restarting issue happening. We have tried factory reset, freeing up space, deleting all apps, safe mode, clearing cache often, and the problem still persists. If anyone could help, I would be truly thankful!
is this the G902VL? if so, you can try to flash the tar.md5 specifically for it via Odin. Its the old boot-n-nuke method. Your other thought of one phone affecting the other, I seriously doubt that is even possible, much less a likely thing
youdoofus said:
is this the G902VL? if so, you can try to flash the tar.md5 specifically for it via Odin. Its the old boot-n-nuke method. Your other thought of one phone affecting the other, I seriously doubt that is even possible, much less a likely thing
Click to expand...
Click to collapse
It is the S903VL. Someone awhile ago uploaded the tar.md5 for this phone and while it successfully flashed and then boots, the problem still persists about 30 minutes after doing this.
Brandon.Black said:
It is the S903VL. Someone awhile ago uploaded the tar.md5 for this phone and while it successfully flashed and then boots, the problem still persists about 30 minutes after doing this.
Click to expand...
Click to collapse
you could root it, but that would void the warranty. I know that the verizon version of MOAR 7.0 works on this phone and is pretty stable, but from what youre describing, it sounds like a hardware issue
youdoofus said:
you could root it, but that would void the warranty. I know that the verizon version of MOAR 7.0 works on this phone and is pretty stable, but from what youre describing, it sounds like a hardware issue
Click to expand...
Click to collapse
I would have already rooted if I could. There is no available root method for this phone on 6.0.1. I'm very confused how this could be a hardware issue even after the phone being replaced. My buddy has had the same phone for about a year and a half and he has said that he never encountered any issue with this device.
Brandon.Black said:
I would have already rooted if I could. There is no available root method for this phone on 6.0.1. I'm very confused how this could be a hardware issue even after the phone being replaced. My buddy has had the same phone for about a year and a half and he has said that he never encountered any issue with this device.
Click to expand...
Click to collapse
i wasnt aware that they released 6.0.1 for the 902VL. Ill have to check some more
---------- Post added at 08:30 AM ---------- Previous post was at 08:10 AM ----------
is it the 902VL or just L? If its the L, then there isnt a 6.0.1 firmware for it
https://www.sammobile.com/firmwares/database/SM-S902L/
youdoofus said:
i wasnt aware that they released 6.0.1 for the 902VL. Ill have to check some more
---------- Post added at 08:30 AM ---------- Previous post was at 08:10 AM ----------
is it the 902VL or just L? If its the L, then there isnt a 6.0.1 firmware for it
https://www.sammobile.com/firmwares/database/SM-S902L/
Click to expand...
Click to collapse
It's the SM-903VL. It's the newest version of the S5.
Brandon.Black said:
It's the SM-903VL. It's the newest version of the S5.
Click to expand...
Click to collapse
oh, ok. well, sammobile.com doesnt even have that model listed, so no help there