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
Related
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.
It looks like Samsung and AT&T have released the SM-P907A's first software update. It's still Android 4.4.2 but fixes a really major bug that caused the System UI process to go into an infinite crash loop when you would adjust the volume while connected to a Chromecast.
As far as the BSOD goes, so far, I have not experienced it with this new firmware. That said, I want to use it for at least a week before I say for sure that it's fixed.
One bug that doesn't seem to be fixed, though, is with VPN. Using the standard Android VPN functionality, I can connect to my work's Cisco VPN via IPSec Xauth PSK on any Android device except on the P907A. If I set it up, it connects, then immediately disconnects. Annoying.
AT&T also added a bigger, more gaudy 4G LTE icon.
Sent from my Galaxy Note Pro 12.2 using Tapatalk
Mine is still BSODing after the update. No difference, and maybe worse...
Yep my SM-P907a also getting the blue screen the update hasn't fixed the issue.
This update seems to have unrooted my tablet and now towelroot says its unsupported... has anyone else experenced this?
---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------
xigam said:
This update seems to have unrooted my tablet and now towelroot says its unsupported... has anyone else experenced this?
Click to expand...
Click to collapse
But now I can cast my screen with chromecast
Every OTA is going to unroot your device. That's just a fact of life with Android.
Sent from my Nexus 6 using Tapatalk
xigam said:
This update seems to have unrooted my tablet and now towelroot says its unsupported... has anyone else experenced this?
---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------
But now I can cast my screen with chromecast
Click to expand...
Click to collapse
It unrooted mine also, I even had the box checked in SuperSU to try to maintain root. Guess I may have to look into reverting back to old firmware...
EDIT: I ended up using ODIN to go back to stock. After doing so, I rooted using towelroot then before installing SuperSU I used the debloat script to disable Knox and the updater. This has allowed me to have root without Knox tripping plus no random reboots. In short use the debloat script and not SuperSU to disable Knox and you will be good to go.
dragunbayne said:
It unrooted mine also, I even had the box checked in SuperSU to try to maintain root. Guess I may have to look into reverting back to old firmware...
EDIT: I ended up using ODIN to go back to stock. After doing so, I rooted using towelroot then before installing SuperSU I used the debloat script to disable Knox and the updater. This has allowed me to have root without Knox tripping plus no random reboots. In short use the debloat script and not SuperSU to disable Knox and you will be good to go.
Click to expand...
Click to collapse
What is this debloat script you speak of? I am sending my note 12.2 back for the second time tomorrow....so I have to Odin back to stock and reroot when it gets back.
wojo797 said:
What is this debloat script you speak of? I am sending my note 12.2 back for the second time tomorrow....so I have to Odin back to stock and reroot when it gets back.
Click to expand...
Click to collapse
I am working up a post here in general outlining how to do everything I talked about.
I just got mine back from Samsung repair for the 3rd time. So in total, they have replaced the motherboard twice, the screen twice and updated the sw each time. It is still doing the blue screen nonsense! I'm really discouraged. I can't find much online about this problem. I will keep up with this forum in hopes of someone being able to come up with a solid solution. I have lost my faith in Samsung. Lol and that's sad because every device I own is Samsung. Over the past few months, I have managed to teach myself how to root my tablet...any further than that gets really confusing. Lol so any help would be appreciated!
Davideo86 said:
I just got mine back from Samsung repair for the 3rd time. So in total, they have replaced the motherboard twice, the screen twice and updated the sw each time. It is still doing the blue screen nonsense! I'm really discouraged. I can't find much online about this problem. I will keep up with this forum in hopes of someone being able to come up with a solid solution. I have lost my faith in Samsung. Lol and that's sad because every device I own is Samsung. Over the past few months, I have managed to teach myself how to root my tablet...any further than that gets really confusing. Lol so any help would be appreciated!
Click to expand...
Click to collapse
Weird most of the post I read said once the motherboard was replaced that fixed the issue.
wojo797 said:
Weird most of the post I read said once the motherboard was replaced that fixed the issue.
Click to expand...
Click to collapse
I know right?! It's just weird. I'm going to try Samsung again, that's about all I can think to do at this point...
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.
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
Sounds like to me that something in your rom became corrupt which isn't uncommon with rooted and modded roms. I might have wiped the caches before bombing it, typically it's a good practice to make regular complete backups of your phone incase of things like this so you can just flash your backup and keep it moving without starting over. Sorry to hear you had to start over!
Sent from my SAMSUNG-SM-G935A using Tapatalk
kokyleod said:
Sounds like to me that something in your rom became corrupt which isn't uncommon with rooted and modded roms. I might have wiped the caches before bombing it, typically it's a good practice to make regular complete backups of your phone incase of things like this so you can just flash your backup and keep it moving without starting over. Sorry to hear you had to start over!
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
That's the next thing I did, wiped the cache from the recovery. Still had the problem, what I didn't do was force stop google play and wiped the data and cache from the app. But then again, after I rebooted, there was no way of doing that since it would never get past the carrier screen. I would have to do it before rebooting (I didn't actually think this would put me in a bootloop). Redownloading a new firmware from sammobile as we speak just in case it happens again. I'm also gonna have to try and see if it works during stock
btort1 said:
Ok so I rooted 7 days ago from a clean install from odin and did all the trickster/interactive, force gpu etc to make it running smooth. But today I started experiencing apps like soundcloud crashing and giving me notifications it stopped, and then finally google play did it, now I just figured restarting the phone would normally fix it. But no, all it did was reboot, after the carrier sign it just vibrates and keeps vibrating and never boots up even after 15 minutes.
So I decided to just do a clean install and unroot again with my sammobile download. So I rooted AGAIN and shortly after, it started doing it.
Then I did a clean install again and rooted, now it's working fine for now. Anyone experience this? I have 20 days to return the phone, I got it from swappa
Click to expand...
Click to collapse
Same thing happened to me on the S7E. Had the phone powered off for a day while I used another phone. When I turned it back on I couldn't open Google Play at all and was getting other fcs as well. Rebooted and it just stayed at the AT&T logo. Did a factory reset but after going through the device setup again, SuperSU wasn't there, so no root.
It all made no sense. I did nothing different than I ever did before. It seemed completely random.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
Same thing happened to me on the S7E. Had the phone powered off for a day while I used another phone. When I turned it back on I couldn't open Google Play at all and was getting other fcs as well. Rebooted and it just stayed at the AT&T logo. Did a factory reset but after going through the device setup again, SuperSU wasn't there, so no root.
It all made no sense. I did nothing different than I ever did before. It seemed completely random.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's weird, I been rooting since my S4 days and nothing like this ever happened to me. I just hope it doesn't happen again, it'll force me to start over and potentially lose some of my data
btort1 said:
It's weird, I been rooting since my S4 days and nothing like this ever happened to me. I just hope it doesn't happen again, it'll force me to start over and potentially lose some of my data
Click to expand...
Click to collapse
its happened to me 3 times on my galaxy s7 at&t model. I'm now on stock until someone figures out this issue.
FreshIce21 said:
its happened to me 3 times on my galaxy s7 at&t model. I'm now on stock until someone figures out this issue.
Click to expand...
Click to collapse
Have you tried clearing the data and cache of the google play store before restarting the s7?
btort1 said:
Have you tried clearing the data and cache of the google play store before restarting the s7?
Click to expand...
Click to collapse
yes, sadly the play store would still not open and the phone still went into a boot loop after i restarted it.
btort1 said:
Have you tried clearing the data and cache of the google play store before restarting the s7?
Click to expand...
Click to collapse
Clearing the cache, data, etc., does nothing.
Sent from my VK815 using XDA-Developers mobile app
Any fix yet?
FreshIce21 said:
Any fix yet?
Click to expand...
Click to collapse
No, this is the 2nd time it happened to me in two weeks. such a bummer, maybe it's force gpu that's causing this? IDK but I just went back to stock and selling this phone. I only need root just to switch around the back button and recent apps anyways...hate how samsung doesn't let you change it to whatever you want...or even on screen buttons
btort1 said:
No, this is the 2nd time it happened to me in two weeks. such a bummer, maybe it's force gpu that's causing this? IDK but I just went back to stock and selling this phone. I only need root just to switch around the back button and recent apps anyways...hate how samsung doesn't let you change it to whatever you want...or even on screen buttons
Click to expand...
Click to collapse
I'm sorry man, its bummer your getting rid of the phone because of this issue but I understand rooting is pretty much neccisary for me too but I'm just gonna wait it out for fix. I wish you the best of luck my friend
Have you guys tried using the U fw? I never had that problem when I was using it. It happened only on the stock rooted fw.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
Have you guys tried using the U fw? I never had that problem when I was using it. It happened only on the stock rooted fw.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm gonna try that rn, did you have this problem on the stock root? Or have you never rooted stock and its just not happening on the U firmware?? It could be a phone issue.
---------- Post added at 02:35 AM ---------- Previous post was at 01:38 AM ----------
Skizzy034 said:
Have you guys tried using the U fw? I never had that problem when I was using it. It happened only on the stock rooted fw.
Sent from my VK815 using XDA-Developers mobile app
Click to expand...
Click to collapse
did you install xposed on the g930u fw? if so how? did u use the g930 method?
rooted on g930u firmware with xposed installed, gonna see if my phone holds out. I'm really hoping it will!!
FreshIce21 said:
I'm gonna try that rn, did you have this problem on the stock root? Or have you never rooted stock and its just not happening on the U firmware?? It could be a phone issue.
---------- Post added at 02:35 AM ---------- Previous post was at 01:38 AM ----------
did you install xposed on the g930u fw? if so how? did u use the g930 method?
Click to expand...
Click to collapse
I had this problem on stock when rooted. I didn't have it when rooted on U.
Sent from my VK815 using XDA-Developers mobile app
---------- Post added at 03:39 AM ---------- Previous post was at 03:39 AM ----------
FreshIce21 said:
I'm gonna try that rn, did you have this problem on the stock root? Or have you never rooted stock and its just not happening on the U firmware?? It could be a phone issue.
---------- Post added at 02:35 AM ---------- Previous post was at 01:38 AM ----------
did you install xposed on the g930u fw? if so how? did u use the g930 method?
Click to expand...
Click to collapse
Sorry I have the 935A.
Sent from my VK815 using XDA-Developers mobile app
Skizzy034 said:
I had this problem on stock when rooted. I didn't have it when rooted on U.
Sent from my VK815 using XDA-Developers mobile app
---------- Post added at 03:39 AM ---------- Previous post was at 03:39 AM ----------
Sorry I have the 935A.
Click to expand...
Click to collapse
Alright hoping this will work for me then
I'm glad to hear I'm not the only person having this issue. This is the second time it's happened to me.
I'm going to try flashing that G930UUEU2APEH FW and then try rooting and reinstalling xposed to see if it happens again in the future.
For those of you that tried it, did using the G930A firmware work on your G935A?
Sideways02 said:
I'm glad to hear I'm not the only person having this issue. This is the second time it's happened to me.
I'm going to try flashing that G930UUEU2APEH FW and then try rooting and reinstalling xposed to see if it happens again in the future.
Click to expand...
Click to collapse
I did what you did and so far so good about a week in (knock on wood).
How are you doing? How long has it been and any problems??
Are you noticing the battery life is not as good?
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.