Develop Bugs

Any Updates on Unlock for 4.4.2

Are there any updates on an unlock method for 3.11.605.1? I'm having a pretty serious problem with streaming Internet Radio apps cutting out with the screen off after about 5 minutes. The app Data Connection Fix has helped out a lot, but I wanted to try out other ROMs to see if I can find 1 without this issue. It's such a shame that I'm having this issue because the HTC One seems like such a great phone. Unfortunately, streaming Internet Radio at work is the main thing that I use my phone for and my older Droid X2 on 3g outperforms this phone in that aspect. It's so sad a newer 4g device has this issue and makes me wonder if I should ever mess with another HTC device or Android device period. I wanted to get away from iOS, but I'm finding that almost every Android device I've been using needs to be unlocked/rooted to fix really simple features that should work right out of the box and with every update. The Bluetooth A2DP quality problem with most JellyBean devices has been a nightmare. That's what made me ditch my LG G2. I tried just about every custom ROM and music through bluetooth was horrible no matter what I tried, even on the newer KitKat ROMs.

pda48428 said:
Are there any updates on an unlock method for 3.11.605.1? I'm having a pretty serious problem with streaming Internet Radio apps cutting out with the screen off after about 5 minutes. The app Data Connection Fix has helped out a lot, but I wanted to try out other ROMs to see if I can find 1 without this issue. It's such a shame that I'm having this issue because the HTC One seems like such a great phone. Unfortunately, streaming Internet Radio at work is the main thing that I use my phone for and my older Droid X2 on 3g outperforms this phone in that aspect. It's so sad a newer 4g device has this issue and makes me wonder if I should ever mess with another HTC device or Android device period. I wanted to get away from iOS, but I'm finding that almost every Android device I've been using needs to be unlocked/rooted to fix really simple features that should work right out of the box and with every update. The Bluetooth A2DP quality problem with most JellyBean devices has been a nightmare. That's what made me ditch my LG G2. I tried just about every custom ROM and music through bluetooth was horrible no matter what I tried, even on the newer KitKat ROMs.
Click to expand...
Click to collapse
I'm pretty sure there's just a setting you're missing that keeps the radio from cutting out. I used to stream Sirius XM and had the problem but I remember getting it fixed somehow. If I think of it I'll let you know. And no, you can't gain s-off on 4.4.2. If you read at all on here, you'll know when you can.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
I'm pretty sure there's just a setting you're missing that keeps the radio from cutting out. I used to stream Sirius XM and had the problem but I remember getting it fixed somehow. If I think of it I'll let you know. And no, you can't gain s-off on 4.4.2. If you read at all on here, you'll know when you can.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Could you please tell me what setting? I get great service where I work and haven't had a problem with any other phone. I even went to Verizon and got a new SIM card. I've tried everything, starting with factory resets and clearing the cache. I have sleep mode off, app data sync on, mobile data is not restricted or limited, I've tried with and without beats audio enabled. The audio cuts out about every 5 minutes for 5-10 seconds and comes back on, just to cut out again for 5-10 seconds every 5 or so minutes. It's very annoying. The only thing that really helps is the data connection fix app, but that's not 100% reliable. I even called HTC and Verizon about the issue and they are looking into it. I would have normally just tried a different ROM, but I'm unable to unlock/s-off/root my phone because I'm on 4.4.2(3.11.605.1). That's the only reason I even called them. I currently have my phone up for sale and I'm seriously thinking about switching my service to sprint. I'm tired of paying top dollar for used phones to keep my unlimited data on Verizon. For all I know, there could be a problem with the phone, but it seems like a software issue to me. Everything else works and runs great. It's just that streaming Internet Radio is the thing I use most.

Have you tried this?
http://androidforums.com/htc-one/732481-beats-audio-setting-interrupts-streaming-audio.html

https://twitter.com/TeamAndIRC/status/443850349678321664
Sent from my HTC6500LVW using Tapatalk

BhRaElEfD said:
Have you tried this?
Yes I've tried. It has nothing to do with beats audio. For some reason it just drops the data connection for like 5-10 seconds with the screen off every 5 minutes or so. I don't know if it's incompatible apps with 4.4.2 or 4.4.2 itself. It could also have something to do with the HTC sense software. It could just be the way this phone communicates with the Verizon towers. I have no idea and it's very frustrating. The last time I had a problem similar to this was when I had an LG Optimus V on Virgin Mobile and it would lose 3g and I would have to turn off the data connection and turn it back on. This is different, though, because I have 4G LTE all the time. There just seems to be a delay in receiving my data to where the Internet Radio cuts out before it signals for more data. Then by the time I receive more data, it's too late and the sound has already cut out. I did a speed test and I'm getting about 30mbps download and around 15mbps upload so I know I'm not being throttled. The only thing that helps is the data connection fix app.
Click to expand...
Click to collapse

I did some more testing and I don't have any issues on WiFi and I don't have any issues if the screen stays on. It's only on cellular data with the screen off when I'm having issues. I noticed the Power Saving feature was removed in 4.4.2 and instead there's a sleep mode option. I have the sleep mode option off, but I'm thinking my issue might be because of a power saving bug in the HTC software for 4.4.2. If anybody knows anything about this, please post. Thanks

Think it will ever be unlocked?
I would SO much love to have airplay enabled on my HTC One. I came from iPhone, and have a full home surround sound based on Airplay, which I now can't use. Airplay is available only through a root application, although i have my phone on 4.4.2. Any thoughts on if and when this will ever be unlocked? Otherwise it's a huge reason for me to not have this phone...

BBooch said:
I would SO much love to have airplay enabled on my HTC One. I came from iPhone, and have a full home surround sound based on Airplay, which I now can't use. Airplay is available only through a root application, although i have my phone on 4.4.2. Any thoughts on if and when this will ever be unlocked? Otherwise it's a huge reason for me to not have this phone...
Click to expand...
Click to collapse
Well it took beaups and crew about 1 month + to get 4.3 unlocked. Plus it seems more devs are having issues with 4.4.2 so it could be longer. At this point hope for the best and expect the worse.

I seriously don't know why all of these companies continue to try and lock out everyone's phones (and spend unnecessary money doing so) when someone will just outwit them almost every time. If a dev REALLY wanted this done right away it would be done! Point blank... It's a cat n mouse game and Verizon will lose. I just purchased an HTC One on 4.4.2 and have full faith that it will be cracked wide open anytime now. No one can stop somebody that is determined and smarter than the person who created the bottleneck. Here's hoping to a quick S-off method soon :victory:

shojus said:
I seriously don't know why all of these companies continue to try and lock out everyone's phones (and spend unnecessary money doing so) when someone will just outwit them almost every time. If a dev REALLY wanted this done right away it would be done! Point blank... It's a cat n mouse game and Verizon will lose. I just purchased an HTC One on 4.4.2 and have full faith that it will be cracked wide open anytime now. No one can stop somebody that is determined and smarter than the person who created the bottleneck. Here's hoping to a quick S-off method soon :victory:
Click to expand...
Click to collapse
It's not unnecessary money to them honestly. In Samsung's case they are trying to prove that their devices are secure enough to use for government agencies. Do you think they care that a few rogue hackers find exploits from time to time? No, they just need to convince some corporate goon that his e-mails to his mistress won't get intercepted. Speaking of the S4, it's been locked down now for about 8 months so I'd say they're getting pretty damn good at it. They have root I believe, but the bootloader is locked down tight on every S4 other than the very first firmware that came with the phone. I'm not sure what HTC's motivations are but I'm guessing they need to play ball with companies like Verizon in order to be able to sell their devices in the future.
Another thing that is hurting us is that Android itself is getting more secure. They are adding features that prevent exploits so it makes it harder for your average dev to find a way in. In the future we may be forced to buy developer editions to be able to do anything. That's worse case, but you never know.
Just like you I had "faith" that a developer would crack the S4 and I could finally have freedom. It never happened. It still hasn't happened. That's the main reason I switched to HTC. I'm not saying you should give up hope, but if you can't stand a phone to be locked down you should be looking into buying a different phone just in case...

Crawshayi said:
It's not unnecessary money to them honestly. In Samsung's case they are trying to prove that their devices are secure enough to use for government agencies. Do you think they care that a few rogue hackers find exploits from time to time? No, they just need to convince some corporate goon that his e-mails to his mistress won't get intercepted. Speaking of the S4, it's been locked down now for about 8 months so I'd say they're getting pretty damn good at it. They have root I believe, but the bootloader is locked down tight on every S4 other than the very first firmware that came with the phone. I'm not sure what HTC's motivations are but I'm guessing they need to play ball with companies like Verizon in order to be able to sell their devices in the future.
Another thing that is hurting us is that Android itself is getting more secure. They are adding features that prevent exploits so it makes it harder for your average dev to find a way in. In the future we may be forced to buy developer editions to be able to do anything. That's worse case, but you never know.
Just like you I had "faith" that a developer would crack the S4 and I could finally have freedom. It never happened. It still hasn't happened. That's the main reason I switched to HTC. I'm not saying you should give up hope, but if you can't stand a phone to be locked down you should be looking into buying a different phone just in case...
Click to expand...
Click to collapse
Valid points! That's why I said "almost every time"... I really just need root and I would be happy but I switch devices so much that I probably won't even have the One (my 3rd HTC One) by the time it gets exploited (if) it does. And I do understand that Google has to close a lot of security holes so that they don't look like they are such a terrible company by allowing all of these terrible "viruses" into our phones which I have never had any issues with. I do agree with you though that we will probably all be buying dev phones sooner than later. Thanks for the insight!

Just another reason to leave Verizon and go get a Nexus device.

[Q] SIM Card Crash/Unlock/Downgrading

Hi!
Apologies if repost/noob question/.
Recently I've been having issues with my phone. In the past, when using it for streaming videos and such on YouTube, my phone would start to overheat. It used to do this all the time but it was never seemed like a serious issue to me. However, for the last 2-3 weeks, whenever I used apps such as YouTube, browser, messaging etc. or anything else that might overexert the phone, it would heat up almost immediately followed by the message "no SIM card detected". I've tried rebooting the phone which occasionally fixes it (but most of the time does nothing) but the same message would pop up again within a few minutes. The only success I've had with dealing this issue is leaving the phone off for ~30min to a few hours to let it fully cool and then it would work fine again until I used an app for a prolonged period.
SO, here comes the question(s):
I've torn apart almost all the forums I could get my hands on through the glorious thing we call the internet..but to no avail. So, right off the bat, does anyone have a solution to this? I've already tried the typical 'cleaning the SIM' and 'slipping a piece of paper in with the SIM'. I've also tried the SIM on other phones (which worked fine but I wasn't able to test it to the point where it overheated as it did on mine).
TL;DR: My phone's SIM doesn't work and I need a solution.:silly:
Anyways, if noone has a solution, I have a plan of action (outlined below) but would like some advice before acting on it.
Ive tried my SIM on OTHER phones and it seemingly works fine. I HAVEN'T tried another SIM on MY phone because its not unlocked. I'm with Mobilicity and they charge $50 to unlock (given how crap their service and reception already is, I refuse to give them any more money). So, I plan on unlocking the phone myself and then test with another SIM. Sounds like alotta effort but I'm dirt poor (which is also why I'm with Mobilicity because their plans are dirt cheap) and I also find this stuff fascinating/interesting.
Research (good news)has told me I can unlock myself if my phone is on the firmware 4.1.1 (using the PersoSHA256Off method). The problem is, I'm on 4.3, which, (bad news) research has also told me, attempting any downgrade from 4.3 to 4.1.1 can result in a hardbrick. HOWEVER, (good news) I heard that this only happens if you have a locked bootloader. But (bad news), I'm totally new to android and everything I've said is simply self-educated due to research so I don't actually know how to determine if its locked (also, I get so lost in the jargon other forums use so I'm not sure I fully understand). I've heard say that Canadian S3's have unlocked bootloaders and/or come locked but can be unlocked, but again, if that's the case, how do I find out/or unlock it myself ? (I said 'lock' quite a few times, sorry if I lost anyone there).
I thank any fellow who was able to persevere through this wall of text and still has the desire to help me.:laugh:
I apologize to the mods/developers/community if the answers to my questions are blatantly obvious and have fuelled anger from their hearts with its stupidity.
Here are the specs on my phone:
Model Number: SGH-T999V
Firmware: 4.3
Kernel Version: 3.0.31-2159044
Build Number: JSS15J.T999VVLUEMK5

Unfortunately, there is no way back. It used to be you just hsd to flash the 4.1.1 modem, but I am not certain thatd work anymore. Up to you if you want to try, but I make no guarantees. You can buy unlock codes on eBay and elsewhere for a few bucks though.
Sent from my SM-N900T using Tapatalk

DocHoliday77 said:
Unfortunately, there is no way back. It used to be you just hsd to flash the 4.1.1 modem, but I am not certain thatd work anymore.
Click to expand...
Click to collapse
Regardless of whether or not the bootloader is unlocked or not?

The bootloader isn't locked. You just are prevented from flashing back to older firmware.
Sent from my SM-N900T using Tapatalk

I see. Do you (or anyone else) perhaps have a reason/solution to the main problem as to why the SIM fails after a period of time then?

[Q] SGH-I747M No Longer Connecting To Network After Unlock

Hi everyone,
So earlier today I was standing in Walmart when my phone froze and I restarted it, after booting up it indicated that the Public Mobile network was unavailable, since then I've been unable to connect to any networks. I can scan for networks, select public mobile, it sits there for five minutes trying to connect and then says "Please Try Again Later".
Now a couple of months ago I had my phone unlocked by a local place, they initially did a bad update because my WiFi stopped working, and then I noticed that they put a Rogers Firmware onto my phone which originally comes from Telus. Could this pose an issue ?.
I've also noticed that my IMEI number on the back of the phone is completely different from what is on screen. What can I do to get my phone working again or am I f***d ? I have no experience rooting or flashing my phone but if someone could walk me through it that would be awesome.
My phone is a Samsung Galaxy SIII (SGH-I747M) Telus, running android 4.4.2
Thanks !

You could try re-injecting the original IMEI using nvwriter.
http://forum.xda-developers.com/showthread.php?t=1804117

audit13 said:
You could try re-injecting the original IMEI using nvwriter.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thanks, I tried following the steps but couldn't figure it out, I don't have the original IMEI number backed up, but I do have it, is there a way I can go in and change it ? When I tried to use nvwriter it tells me my phone isn't responding.

Oh boy.......I'd go to wherever you had it serviced and find out exactly what they did. Sounds kind of like they put a different motherboard in and did not tell you. They probably did something to really screw up the original but didnt want to admit it or pay for it, so they gave you whatever they had on hand. This just a guess of course, but it would explain the firmware and the IMEI being different. You shouldn't be able to flash the Rogers firmware on any other carriers device or vice versa. So I find all of that extremely suspicious.
Check the IMEI's to see if they're blacklisted. (Im worried the one you see in settings will turn up to be so....hopefully not).
Do not try to change the IMEI though. If my suspicions are correct, it means the one its using is the one belonging to that board. Not only does changing the IMEI often cause a lot of ither issues, it is also almost always illegal.
***(And just fyi, be careful posting the tools or instructions for doing so, is against XDA rules. Same for just about every forum on the net.)
Even if all of that were not anything to be concerned about, you have to consider that if they did swap your motherboard, they may have fixed it later and now someone else has it with that IMEI. If you put it on your device, and both are seen on the network with the same one, it'll get blacklisted.
I really hope I am wrong....I really really do. But if I am not, i don't know if you will be able to do much without more info from whoever worked on it.
I am sorry btw, Im not trying to scare you about it, that's just what I see as the most likely scenario based on the info provided. Like I said, I could be wrong.

DocHoliday77 said:
Oh boy.......I'd go to wherever you had it serviced and find out exactly what they did. Sounds kind of like they put a different motherboard in and did not tell you. They probably did something to really screw up the original but didnt want to admit it or pay for it, so they gave you whatever they had on hand. This just a guess of course, but it would explain the firmware and the IMEI being different. You shouldn't be able to flash the Rogers firmware on any other carriers device or vice versa. So I find all of that extremely suspicious.
Check the IMEI's to see if they're blacklisted. (Im worried the one you see in settings will turn up to be so....hopefully not).
Do not try to change the IMEI though. If my suspicions are correct, it means the one its using is the one belonging to that board. Not only does changing the IMEI often cause a lot of ither issues, it is also almost always illegal.
***(And just fyi, be careful posting the tools or instructions for doing so, is against XDA rules. Same for just about every forum on the net.)
Even if all of that were not anything to be concerned about, you have to consider that if they did swap your motherboard, they may have fixed it later and now someone else has it with that IMEI. If you put it on your device, and both are seen on the network with the same one, it'll get blacklisted.
I really hope I am wrong....I really really do. But if I am not, i don't know if you will be able to do much without more info from whoever worked on it.
I am sorry btw, Im not trying to scare you about it, that's just what I see as the most likely scenario based on the info provided. Like I said, I could be wrong.
Click to expand...
Click to collapse
Thanks, I just took it back to the place that serviced it. They said to leave it with them for an hour or so and I should be good, didn't sound like he's going to charge me anything either since he remembered when I was in last and he said he had to reinstall the OS. So fingers crossed, otherwise I'm just going to grab a new Moto G to use with my network. I'm kind of over the SIII anyhow, so if its not fixable its not the end of the world, still sucks nonetheless lol

"Tampered" screen. S-On. HBOOT-1.57 with loop. Is there any way to save this phone?

"Tampered" screen. S-On. HBOOT-1.57 with loop. Is there any way to save this phone?
So I was trying to follow the guide to completely return a phone to stock to return it to a seller due to hardware issues (they sent me a not so great repair job. I tried to live with it for a while but just couldn't.) But with missing files and etc I was having troubles getting it all to work. I probably should have just downgraded completely down to 1.10 or something. Anyway, I had the odexed full 4.10 installed but forgot that it wasn't quite 100% stock because I had to grab the TWRP flashable version. The intent was to let it do the OTA upgrade to 5.28 and be 100% stock (plus I wanted to be sure that the OTA function worked so the next person to get the hardware could get the 5.0 update whenever it hits. If. I didn't want them to be stuck with a partially working phone any worse than the already existing hardware problems.) Before the OTA update finished I thought I should S-On since all was working. Ok, I screwed up and I don't deny it. But now what do I do? From what I understand, the only way around the "tampered" bootloop is to flash a stock RUU. But thanks to Verizon's bloody bootloader lockdowns, options are extremely limited there and I can't just flash an older RUU. Since it's HBOOT 1.57, that means that the old 2.10 and lower RUUs aren't going to cut it and I'm not finding anything newer for the Verizon models anywhere. It's ridiculous that this situation even exists IMO since the whole goal here is to go back to 100% stock and their system to force people to stay stock is the very thing stopping me from doing so. But worse, it's now basically a brick...
Is there any way at all to save this phone, or am I utterly hopelessly screwed?

Nazo said:
So I was trying to follow the guide to completely return a phone to stock to return it to a seller due to hardware issues (they sent me a not so great repair job. I tried to live with it for a while but just couldn't.) But with missing files and etc I was having troubles getting it all to work. I probably should have just downgraded completely down to 1.10 or something. Anyway, I had the odexed full 4.10 installed but forgot that it wasn't quite 100% stock because I had to grab the TWRP flashable version. The intent was to let it do the OTA upgrade to 5.28 and be 100% stock (plus I wanted to be sure that the OTA function worked so the next person to get the hardware could get the 5.0 update whenever it hits. If. I didn't want them to be stuck with a partially working phone any worse than the already existing hardware problems.) Before the OTA update finished I thought I should S-On since all was working. Ok, I screwed up and I don't deny it. But now what do I do? From what I understand, the only way around the "tampered" bootloop is to flash a stock RUU. But thanks to Verizon's bloody bootloader lockdowns, options are extremely limited there and I can't just flash an older RUU. Since it's HBOOT 1.57, that means that the old 2.10 and lower RUUs aren't going to cut it and I'm not finding anything newer for the Verizon models anywhere. It's ridiculous that this situation even exists IMO since the whole goal here is to go back to 100% stock and their system to force people to stay stock is the very thing stopping me from doing so. But worse, it's now basically a brick...
Is there any way at all to save this phone, or am I utterly hopelessly screwed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=

santod040 said:
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
Looks like the thread number didn't make it in that URL either.

Nazo said:
Looks like the thread number didn't make it in that URL either.
Click to expand...
Click to collapse
I was mobile, laying down.
Got up to get on the PC to repost the link for you.....
http://forum.xda-developers.com/ver...-3-s-users-t2919442/post56302410#post56302410

Oh, gotcha. I for some reason thought from all those guides and such that you had to specifically flash a RUU zip file manually. I'll grab that and give it a shot. It sounds like just what I need.
EDIT: Thank goodness. This did it. 100% stock. I was afraid I wouldn't even be able to return it. I just hope the next user feels better about the incomplete repair job the seller (or whoever they got it from) did on it than I did. (Though the lack of a LED is a pretty significant problem. They really should have fixed that.)

Nazo said:
Oh, gotcha. I for some reason thought from all those guides and such that you had to specifically flash a RUU zip file manually. I'll grab that and give it a shot. It sounds like just what I need.
EDIT: Thank goodness. This did it. 100% stock. I was afraid I wouldn't even be able to return it. I just hope the next user feels better about the incomplete repair job the seller (or whoever they got it from) did on it than I did. (Though the lack of a LED is a pretty significant problem. They really should have fixed that.)
Click to expand...
Click to collapse
Did the led work at all...? Like when charging?

dottat said:
Did the led work at all...? Like when charging?
Click to expand...
Click to collapse
No LED under any circumstances at all. I can't even imagine how they managed to damage a phone in such a way that the LED would utterly stop working, yet it wouldn't require a new mainboard or something. I guess the only way to repair that would have been to replace said mainboard though. Well, no matter. This time around I decided it just wasn't worth trying to save the money buying a used phone and got one sold as new, sealed in box. If anything is wrong with this one I'll be amazed. (Well, barring the camera issue. *Fingers crossed*) One thing I can say though, the top speaker barely worked at all, so whatever they did probably did a decent amount of damage to the entire top section. I wouldn't be surprised if there were other troubles such as the front camera (I never use it) or maybe the sensors (though the light sensor seemed ok.)
BTW, the program did, in fact, work. I had it restored 100% to factory, tested it out, and found absolutely nothing wrong (at least nothing besides the problems the seller sent it with. I can't fix those...) I really hope the next person who gets stuck with it is happier than I was with those issues. I guess that's what one gets into buying used, but my previous experiences with such things were a lot better. (For instance, I fried my SGS3 via circumstances I don't want to get into right now. I bought one with a broken screen, swapped out the main board from it into mine, and presto, I had a once again working SGS3. Actually, it happens I ended up perhaps better off as it never seems to have had modem issues some others have had and the SoC seems to be stable at ridiculously low voltages if I were so inclined -- well, there's no real reason not to lower the voltage if it's 100% stable IMO, so I went ahead, but I didn't do an in-depth test to get the minimums.)

Firmware advice - SM-N975U - Note 10+

Hi All,
Been a while on here - please be gentle!
I have spent the last 6 hours looking into updating my firmware from Android 10!
I have done this on previous phones, but my current phone is proving a little more difficult. For the life of me, I cannot find the correct ROM to flash. Whenever I come to something I think I have found I seem to have another issue.
I've tried using various tools (Bitfrost) but got errors.
I'm in the UK, and as far as I can tell, my phone is “XAA”, “USA unbranded (default)”. I'm not bothered about changing the region code (unless it can be done easily).
Details::
SW ver.: SAOMC_SM-N975U_OYN_XAA_PP_0001
XAA/XAA/ATT
I would really appreciate some help from you guys who are way more informed and cleverer than me!
Thanks guys and gals!
Simon
EDIT: I have found a bit more informstion - I think I would be ok using SM-N975U1 - is this correct?

That's the umlocked Snapdragon variant...
I have two N10+'s; N975U/Pie, N975U1/Android 10. I would stay on Android 10 unless you want cpu cycle sucking scoped storage in all its glory.
Personally I prefer Pie to 10, better functionality and usability. With 11 you lose even more and 12 is fubar... in my opinion.
The best way to trash a stock N10+ is to mess with its firmware.
Rule #1 if a OS is fulfilling its mission, let it be!
Upgrades/updates can and do break things.

blackhawk said:
That's the umlocked Snapdragon variant...
I have two N10+'s; N975U/Pie, N975U1/Android 10. I would stay on Android 10 unless you want cpu cycle sucking scoped storage in all its glory.
Personally I prefer Pie to 10, better functionality and usability. With 11 you lose even more and 12 is fubar... in my opinion.
The best way to trash a stock N10+ is to mess with its firmware.
Rule #1 if a OS is fulfilling its mission, let it be!
Upgrades/updates can and do break things.
Click to expand...
Click to collapse
Thanks for that info ... I actually have no beef with A10 other than one issue which I thought maybe a firmware issue.
My NFC works (I can transfer files between phones) however, I cannot use Google Pay, or Samsung Pay. I have read somewhere that this was a firmware issue, hence my desire to update.
I have tried literally everything to get it working (cleared cache, re-booted). NFC Tools confirms it works, but it just does nothing at the checkout.
If I can fix this issue, I'll be happier!

Ratzz2 said:
Thanks for that info ... I actually have no beef with A10 other than one issue which I thought maybe a firmware issue.
My NFC works (I can transfer files between phones) however, I cannot use Google Pay, or Samsung Pay. I have read somewhere that this was a firmware issue, hence my desire to update.
I have tried literally everything to get it working (cleared cache, re-booted). NFC Tools confirms it works, but it just does nothing at the checkout.
If I can fix this issue, I'll be happier!
Click to expand...
Click to collapse
You're welcome. It may be doing that because big sister Google thinks you need to upgrade to be secure. May have to do with the region you're using it in. I don't know. I never use those features and don't want them on the phone. Don't want anything to back door in using that route.
Depends how hell bent you are on having those features. You could easily lose more than you gain by upgrading, worse it may not resolve the issue. The N10+ is a valuable and reliable work horse that will run for years... just as it is. If it's running well otherwise I would try to find the root cause of this issue or simply use other workarounds rather than the shotgun approach.

Yeah, I was wondering about being in the UK with a phone registered in the US. But NFC doesn't read my credit card either. Would have thought that would be an option.
I'm not necessarily a huge NFC user, but the other day I forgot my wallet at the petrol station after filling my car. If I'd have had my NFC working, I'd have been able to fire it up and avoid the embarrassment!
Anyway, thanks for your help!

Be glad you have the Snapdragon variant. They are very reliable and run well stock when optimized. If you do upgrade to 11 a rollback to 10 isn't possible if you upgrade the boot loader.
There's always at least a small risk when flashing firmware which can trash the device. The only time I would flash a N10+ is if the rom was corrupted which barring a hardware failure is a very rare SUE, single upset event.
I never tried mine to see if Pay works nor have I ever set a screen lock. The fingerprint scanner could be dead for all I know.
The flip side to that is never being locked out* of my own device, no data lose, and double tap on/off. The device is glued to me as physical security is the only real security. I realize this may seem extreme to some, but it works well in the real world.
*a SEU or partial hardware can lock you out of your device. Had no lock been set, no lockout would have occurred. Got locked out of a PC bios like that. The password -was- correct
That caused a mountain of trouble...

Thank you my friend. Wise words indeed and duly noted...