Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
jdelforge5684 said:
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
Click to expand...
Click to collapse
1.to unlock bootloader you need special key lock.bin from LG..
not sure how i got mine locked. ... why. because of the bootloop issue.. and unlocking bootloader will void warranty so says LG on their website..'
2.like i said never tried unlocking. am itching to..
3. i think as long as you are in a stock based rom.. not
aosp or CM youll have wificalling.
4. cm is nice but alot of bugs not good camera quality.. i would only go CM if i ever wanted to try new android version.. why go CM when you get MM.?
jdelforge5684 said:
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
Click to expand...
Click to collapse
Follow this guide.you lose wifi calling if not on stock rom.there are custom stock roms that are very good.my favorite is from turbo2012(just my opinion)that are slim and optimized.
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its the same if you are on 20o.just follow the guide you dont need any special key from lg.
Related
I recently purchased a used droid 4 on ebay. Unfortunately it has been upgraded to the OTA release of ICS 4.04. Anyone working on lifting the simlock associated with the version of the bootlocker included with ICS (I'm assuming the bootloader is the origin of this simlock but technically I could be wrong)? Or is it a lost cause because it is signed? I know it's written to protected ram so any workaround would be nontrivial but does anyone have any possible exploit ideas? Motorola is unlocking a couple other models that they have out. Would petitioning them to include the droid 4 in their list of unlockable devices be a surefire path to getting the simlock lifted? Or should I consider this a lost cause and return my droid 4 to the ebay ether?
If anyone is considering working on this issue I would be more than glad to contribute. While I'm no Android expert I have a decent understanding of the OS and work in command line Linux for a living so I'd be glad to help. The selection of qwerty phones today is beyond attrocious.
One last thought. Is the idea of spoofing the carrier a possibility?
Sent from my SGH-T839 using Tapatalk
Hi blackstar,
So, I recently got a Droid 4 off of CraigsList that I wanted to use on StraightTalk, but found out that what I had perceived (that 2G/Edge was working on GSM North America) was incorrect.
They're not completely sure WHERE it's broken at the moment as far as SIM lock. Some have suggested it might be baked in the ROM -- but more than likely it is built into the modem.
Here have been some stabs at it -- and what to do in regards to getting the modem setup/altered.
http://forum.xda-developers.com/showthread.php?t=1916869
A thought, though -- since we have SafeStrap and Root, doesn't that let us essentially bypass the bootloader in some ways? My understanding is that the bootloader was required to boot the device to a "correct" image and lock the load to Motorola's firmware, but SafeStrap/root gave us access to actually overwrite the RAM/memory and replace the existing kernel with a new one for the chance at custom ROMs. So, I'm not entirely sure it has to do with the bootloader.
To me, it seems like something that's potentially baked into their ROM or in the modem firmware. If it's in the modem firmware, it's a matter of figuring out what keys/values need to be adjusted and then run it. There have been talks about AT&T getting the Photon Q (Asanti) -- rumors that were back around April of this year... but we have yet to see it there and no news about it showing up anytime soon. Not sure if they scrapped the keyboard and then shipped it as a different device.
I would imagine that if we can have the lowest level debug logging enabled and plug in an American SIM, you might be able to figure out what is breaking. Not sure how low logcat can go...
That's my understanding of the current situation, from a programmer's point of view (though I don't code for Android). Spoofing might be interesting -- but if it's locked at the radio firmware, I don't think spoofing can adjust the frequencies. But more power to you if you can figure it out (and force me to find ANOTHER Droid 4, haha).
Good luck! Definitely talk with the OP of the Topic I sent you, since s/he has a pretty deep interest in this as well.
OH, and one more thought -- there was a thought to grab an AT&T version of the Bionic and Verizon version, wherein they had the same radios, but different firmware, and do a diff on them to figure out if some settings had changed, and then potentially patch that into the D4. That might be a good strategy, but that would require us to get dumps from a few different people -- something you might be able to facilitate if you guys all work together.
One final thought -- is there any way we could have a sticky'd topic for people to post their findings, so we don't have to keep scanning and finding this?
Much thanks terinfire.
Let me start off by saying I don't have any definitive information with regards to any of the good questions you posed but if I find out anything I'll be sure to update the thread.
I spent a good chunk of the weekend trying to educate myself on the situation. From what I understand (anyone feel free to correct me or point me to the appropriate thread if I'm completely reinventing the wheel), it seems like it comes down to two most likely scenarios. Either Verizon added an MCC/MCN lock in the baseband when pushing out the OTA ICS release or they placed a restriction in the radio interface layer (RIL) of the ICS ROM. My research hasn't quite enabled me to determine which scenario is more likely. My unscientific intuition (and wishful thinking) is that the restriction is in the ROM somewhere in the RIL (if that makes any sense, still learning the Android OS architecture).
I will post what I've mentioned above in the the forum you mentioned; hopefully I can garner an audience. I will also look into getting a sticky topic created.
Not too sure how to implement any of my intuitions noted above with regards to this problem but I will try and learn as it goes.
One more note - so it is claimed that the Samsung Galaxy III for Verizon can be unlocked to use domestic GSM carriers. I've found no confirmation. (https://plus.google.com/103583939320326217147/posts/b7JbBKjJVSQ)
Pertinent links I came across in my research that may be useful:
MCC/MCN Codes: http://en.wikipedia.org/wiki/Mobile_Network_Code
Radio Interface Layer: http://en.wikipedia.org/wiki/Radio_Interface_Layer, http://www.kandroid.org/online-pdk/guide/telephony.html
RIL Header: https://code.google.com/p/linux-on-android/source/browse/radio/headers/ril.h
Qualcomm MDM660Device Specification: http://www.scribd.com/doc/54154049/...odem-Device-Specification-Advance-Information
Question 1: Seems like Focus S is never getting as much love as HTC Titan for some reason, why is that?
OK, I just got two extra WP phones I got back in 2012 SIM unlocked, sammy focus S and HTC Titan. I plan to give one to my parents in China to use, who are not tech savvy nor heavy cellular data user at all. I have a few questions based on what I skimmed through several WP forums (XDA etc) that I need you experienced users' help.
1. Which one is more idiot-proof for old users, focus S or Titan?
2. Once I SIM unlocked it, I assume they can just pop a local SIM to talk and txt, right? Anything else that needs to be manually set up?
3. I noticed a few threads talking about tricks of setting APN with Straight Talk. How about TMobile? And I assume that's only used for data usage right? If my parents just use it to talk and txt plus WIFI, it should be fine just leave the settings unchanged?
4. Also a lot of threads were debating whether to upgrade to WP7.8 or not and how to do it. Now it's 2014, is WP7.8 upgrade pushed automatically by MS already or I still need to follow the instruction and use 3rd party tools to do it?
5. Is there any custom ROMs for this phone at all? And what are the immediate updates/mods you guys suggest if I boot up the phone for the first time.
Thanks so much.
5.
The focus s was unfortunately an ATT exclusive , meaning one of the best designed windows phone 7 devices ever made was also only available to a tiny number of users, hence the lack of love!
As for setting it up,network unlock it, interop unlock, setup apn , update to 7.8 an your done
Sent from my arc 10HD using xda app-developers app
Focus S to android Os
So noone can get the Focus S to run any android Os ?
Bennyscrewz said:
So noone can get the Focus S to run any android Os ?
Click to expand...
Click to collapse
Dude,
With the exception of ONE device, the immortal HTC HD2, there has never been any (current) device that has had cross platform support, and lets be clear about the HD2, it was a WM device, that was opened up, and rather handily was also used as a test platform for WP. its android life started out as a hack that ran (initially) from within windows, later moved to its own ROM via MAGLDR. There was a lot of very cleaver people using a single device thus it had a lot of support to do these wonderful things.
OEMs shipping android then went nuts and made so many new devices it diluted the support available to specific phones and effectively killed off any further "HD2 Moments"
So no, the focus S doesn't have Android support. No one is working on it, no one tried to and to my knowledge no one will ever work on it, the same can probably be said about most phones.
Besides that, I cant remember which one because there was so many different versions it is but its essentially the same as the Samsung Galaxy 2(s?) so why not buy that if you want android on it?
and Finally
This has been asked So many times about so many devices, even googling it brings up an answer within the first few posts. Just take this as a wee helping hint, try search for your questions, this site has so many users over so many devices that statistically, its likely any question you may have has probably been answered somewhere by someone else
Answers to this question are either totally unanswered or vague.
Can/will the M7 support VoLTE (Voice over LTE) or not? Three in the UK is upgrading it's network to support VoLTE in the 800mhz frequency range. It would be nice to have it if at all possible. Sadly there is very little info on whether the hardware supports it and if the software (Lolipop and mods) will support it or not on the M7.
Can we have a thread with solid answers as this is quite important for some of us who have reception issues.
deadman3000 said:
Answers to this question are either totally unanswered or vague.
Can/will the M7 support VoLTE (Voice over LTE) or not? Three in the UK is upgrading it's network to support VoLTE in the 800mhz frequency range. It would be nice to have it if at all possible. Sadly there is very little info on whether the hardware supports it and if the software (Lolipop and mods) will support it or not on the M7.
Can we have a thread with solid answers as this is quite important for some of us who have reception issues.
Click to expand...
Click to collapse
I've been searching and curious (without avail) about the same question. I'm currently using Viper/Venom ROM v9.0.0 that uses a base from the M9. The M9 supports VoLTE and thus the option appears in the menu on the M7. However it does not function and if you try to interact with it the phone service crashes. This makes sense since it was developed for M9 hardware. Does this mean it's totally not supported on the M7 from a hardware standpoint - nope. But without the proper software it's not going to happen. Is T-mobile (or whoever your carrier is) going to develop the feature? Probably not. Will google? Maybe, seems to be appearing on google phones as a standardized feature. Same for wifi calling...
sensati13 said:
I've been searching and curious (without avail) about the same question. I'm currently using Viper/Venom ROM v9.0.0 that uses a base from the M9. The M9 supports VoLTE and thus the option appears in the menu on the M7. However it does not function and if you try to interact with it the phone service crashes. This makes sense since it was developed for M9 hardware. Does this mean it's totally not supported on the M7 from a hardware standpoint - nope. But without the proper software it's not going to happen. Is T-mobile (or whoever your carrier is) going to develop the feature? Probably not. Will google? Maybe, seems to be appearing on google phones as a standardized feature. Same for WiFi calling...
Click to expand...
Click to collapse
With the AICP MM ROM for the m7, I called my mom and it said "VoLTE" in blue letters. I never really took notice of it until after I went back to Sense... I'm going to flash that ROM again and give you an update soon (if not I probably forgot, sorry). And btw I know this thread is very old but I just wanted to chime in and say what I've found
firedroidx said:
With the AICP MM ROM for the m7, I called my mom and it said "VoLTE" in blue letters. I never really took notice of it until after I went back to Sense... I'm going to flash that ROM again and give you an update soon (if not I probably forgot, sorry). And btw I know this thread is very old but I just wanted to chime in and say what I've found
Click to expand...
Click to collapse
So, that was an interesting and timely reply. I recently upgraded my M9 (s-on) to a firmware that is too new for MM CM so I went back to my M7 for a while. It's still on a sense based rom but I may give AICP MM a spin on my M7- thanks!
:edit
Now that I think about it, the only reason I upgraded to the M9 was for VoLTE, the M7 is the perfect size phone, god how ridiculous new phones are these days, every iteration just a liiiiitttle bit bigger. enough already lol /rant...
sensati13 said:
So, that was an interesting and timely reply. I recently upgraded my M9 (s-on) to a firmware that is too new for MM CM so I went back to my M7 for a while. It's still on a sense based rom but I may give AICP MM a spin on my M7- thanks!
:edit
Now that I think about it, the only reason I upgraded to the M9 was for VoLTE, the M7 is the perfect size phone, god how ridiculous new phones are these days, every iteration just a liiiiitttle bit bigger. enough already lol /rant...
Click to expand...
Click to collapse
I flashed AICP last night and called my mom again, but unfortunately no VoLTE... It's odd because I clearly remember seeing those blue letters when I was about to hang up :/ If I find anything new I'll post it here!
firedroidx said:
I flashed AICP last night and called my mom again, but unfortunately no VoLTE... It's odd because I clearly remember seeing those blue letters when I was about to hang up :/ If I find anything new I'll post it here!
Click to expand...
Click to collapse
Maybe, you didn't remember well, what you've seen? Because I think, it's impossible.
So this thread is a year old (time to re-activate it?), and I wonder about the same issue. I tried on the M7 with different firmwares (european latest hboot 1.61, GPE hboot 1.54), using LineageOS 14.1 (Android N 7.1.2), but with no constellation it's possible to activate VoLTE.
I figured out, that it depends on "the hardware", but IMHO that's not really the reason because the LTE radio chip performs LTE correctly. So I expect it depends in reality on the "radio firmware" to active VoLTE.
And I have never seen a radio firmware for the M7, which is able to perform VoLTE.
If somebody knows about a "patched" or "modified" radio firmware for the M7, to activate VoLTE, please let me know!!! (Because LOS 14.1 runs well, and is -- from the OS side -- able to perform VoLTE).
Thanks a lot,
samhhmobil
samhhmobil said:
Because LOS 14.1 runs well, and is -- from the OS side -- able to perform VoLTE)
Click to expand...
Click to collapse
Thats not true, Lineage in general doesnt support VoLTE. You can read about exacly this on AICP G+ page because a lot of people asked for VoLTE Support. Official answer was "as long as lineage doesnt implement it we dont have it" There are some unofficial Roms for other devices where the maintainer did implement VoLTE. The big problem with VoLTE is, in nearly every country and provider it has a different standard so its not just add something and it works for everyone.
But Guys, do you realy need LTE while your in a Call and 3G isnt enough? I think 42mb/s should be enough for everything and thats what you actually get while in a call. Btw our m7 only has an internal read and write speed at about 5-15mb/s so its useless :silly:
You're a power user. Can the LG V20 keep up? Rate this thread to express how "healthy" the development scene is for the LG V20. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
Well, seeing as though there is NO comments, I will be the first to say that I am hoping that we get root as quick as possible! Judging by the great people we have working on this phone, I have ZERO doubts!
M only concern is carrier specific development. T-Mo is doing well, as well as any HK based v20; however, AT&T/Verizon/Sprint models are yet to get as much attention.
ohblindone said:
M only concern is carrier specific development. T-Mo is doing well, as well as any HK based v20; however, AT&T/Verizon/Sprint models are yet to get as much attention.
Click to expand...
Click to collapse
what this guy said^^^^
I'm on Verizon...I do see that bootloader unlock was achieved with the pixel on Verizon... so I'm sure it's possible with this device, on Verizon, I just don't know if the verizon variant will get the needed support from the development community. I wish I had a clue...
Seems like real development is about to start for Tmobile! @Chainfire confirmed that the LG V20 has been rooted. And i also have seen some users concerned with other variants even if it is not the variant they are using >> good solidarity. So , we all hope that each variant find the path to the root. The more the merrier!
I plan on picking up the VZW version in the next couple day. Hopefully more people will do the same.
What would the devs need from the VZW version to start work on the boot loader unlock / getting root?
Willing to try and help with that. I am fairly familiar with Linux and somewhat with adb, so just tell me what you need, how to pull it, and I will do my best to pitch in.
Dk if I will root mine specifically because I will use it for work also, and some of our software will not currently accept a rooted Android phone onto the network. Can't say what it is, other than it is in-house proprietary software.
Development is very weak on all carriers except T-Mobile.
Sent from my LG-LS997 using Tapatalk
for now development for Tmobile model is pretty decent. I just hope it wont die too early
We got root and future look bright. Other models not so lucky with development just because they are locked
I hope we can get development on the factory unlocked non carrier specific version as well!
KingKash420 said:
I hope we can get development on the factory unlocked non carrier specific version as well!
Click to expand...
Click to collapse
I think you're pretty much in the clear
Sent from my LG-LS997 using Tapatalk
I'm offering up my Verizon device for testing.
Maaaan i hope they manage to make Resurrection Remix and ACIP roms for the LG V20. Those 2 are my favorite roms on every device i have had. and if the 2nd screen is the problem, they can drop that behind (at least for a while, i wouldnt mind) lol. Of course, first someone need to start with CM14 for this device. (I have been looking all over the web, including github and there is not a single trace of CM14 for LG V20) on the other hand, at least we have root for the h918, ( i also hope other variants get root too). It is odd that no one have asked the question of: "Will there be CM14 for the LG V20?".... at least none existen threads, nor comments could be found while googling. but well. I guess i turned out to be the first, lol. Although i saw on CM website there is a subforum of the LG V20, however it is totally empty.
Compared to when I first bought this phone, the development has really picked up.
I'm on the Resurrection Remix ROM for Verizon and i'm loving it.
I wish there was some developing going on for version H990ds
axaman943 said:
I wish there was some developing going on for version H990ds
Click to expand...
Click to collapse
Once it get root and open bootloader life will be much easier
Same thing for 990.
Its almost there ?
Very quiet in this thread for the last 3 months.
I've had my V20 for a day and I'm loving it. I researched a lot beforehand and knew development was pretty much nonexistent but I hope there may be a root exploit in the future.
I have the H990ds Taiwan model.
Hey guys! I have been scouting around for Note 8 help but thought it was time to join myself.
Hopefully if I am able to solve my specific problem or get my questions asked it can help someone else.
Specifically, right now, I picked up and refurbished a Samsung Galaxy Note 8 since I have one currently that is phenominal, and wanted one in the back pocket in case anything happens but it is locked to ATT, which isnt the real problem. The real problem is that it is still on Android 7.1.1 and I would like to get it to Android 9 Pie.
I am unsure of a few things like whether I need all updates between 7 and 9, or if I can jump straight to it. But things of that sort.
It sucks that its ATT locked but I feel its worse that its on old Android since I refurbed it, (fixed screen and replaced with fresh samsung battery) but its being held back in certain functional capabilities. Either way, I am a techy, not yet able to solder, but definitely able to troubleshoot my way around a Windows Blue screen of death.
Looking forward to learnin more!
MethudMann said:
Hey guys! I have been scouting around for Note 8 help but thought it was time to join myself.
Hopefully if I am able to solve my specific problem or get my questions asked it can help someone else.
Specifically, right now, I picked up and refurbished a Samsung Galaxy Note 8 since I have one currently that is phenominal, and wanted one in the back pocket in case anything happens but it is locked to ATT, which isnt the real problem. The real problem is that it is still on Android 7.1.1 and I would like to get it to Android 9 Pie.
I am unsure of a few things like whether I need all updates between 7 and 9, or if I can jump straight to it. But things of that sort.
It sucks that its ATT locked but I feel its worse that its on old Android since I refurbed it, (fixed screen and replaced with fresh samsung battery) but its being held back in certain functional capabilities. Either way, I am a techy, not yet able to solder, but definitely able to troubleshoot my way around a Windows Blue screen of death.
Looking forward to learnin more!
Click to expand...
Click to collapse
Welcome to XDA! As for updating your phone, could you please tell me your model number?
ethical_haquer said:
Welcome to XDA! As for updating your phone, could you please tell me your model number?
Click to expand...
Click to collapse
Yeah, sorry for long response time.
For the important info:
Model: SM-N950U
Android. 7.1.1
Build:NMF26X.N950USQU1AQH7
CSC: ATT
I'll monitor more closely so let me know if you need any other info
MethudMann said:
Yeah, sorry for long response time.
For the important info:
Model: SM-N950U
Android. 7.1.1
Build:NMF26X.N950USQU1AQH7
CSC: ATT
Click to expand...
Click to collapse
Alright, there are two versions of firmware available for your device. One is "branded" and has carrier bloat, whereas the other does not have carrier bloat but might have issues with VoLTE (probably not, but there is a chance). What one would you prefer? Let me know if you have any questions regarding the difference.
ethical_haquer said:
Alright, there are two versions of firmware available for your device. One is "branded" and has carrier bloat, whereas the other does not have carrier bloat but might have issues with VoLTE (probably not, but there is a chance). What one would you prefer? Let me know if you have any questions regarding the difference.
Click to expand...
Click to collapse
Thanks for the research and yes I do have questions if its not too much of an issue:
1.) Carrier bloat is like the usual and can just be deleted anyways correct?
2.) In what scenarios (in case everything was working fine with OTA updates) would the phone have downloaded a version without bloat?
3.) Would updating to the non-bloated version cause any issues since the phone is still carrier locked?
4.) Lastly, for the firmware, would I need to download multiple updates until that point or just straight to the firmware?
If not, I can research the answers as I have been on it on and off for a month with research but other than that, you're a god send.
By the way, if #1 is true, I'll just take the bloatware no doubt just to be as safe as possible.
Thanks again for all the help @ethical_haquer
Been busy researching in the Samsung Note 8 ATT threads and I was able to find the answer to number 4 in that using Full ODIN files is a complete flash and different than just an update which requires the previous updates.
The answer to number 3 from what I have seen no. The only thing is that certain features may NOT work such as VoLTE; pretty much you already answered 3 and I was literally too dumb to see that until I started writing this message. *face palm
Question 2 is pretty much inconsequential so don't worry answering that. Its was just curiosity. But for anyone who does see this possibly, my speculation is that NO, the carrier version would never download the non-carrier version. The non-branded update is for those unlocked phones that receive over-the-air (OTA) updates that were not associated with any carrier, in other words buying a phone directly from samsung's website.
For 1, I am guessing it is "Yes" since I was able to do that in the past with all my other phones. But either way it is not a make it or break it so it doesn't matter.
I have been able to find some full ODIN files for the updates I was looking for, so will be attempting my first flash soon. Will be posting all my findings to the thread I was reading just to potentially help anyone else (though rare since this device is getting real old) who has the same questions I had and I can get them up to speed without having to search everything
Just finished flashing the ATT Note 8 to and the Answer to Number 1 is that NO, you cannot Uninstall the bloatware
Again, will post all these findings to the proper thread in after completed
Sorry for the late reply! I would try installing the firmware for the SM-N950U1 (notice the 1). It should work and won't have carrier bloat.
ethical_haquer said:
Sorry for the late reply! I would try installing the firmware for the SM-N950U1 (notice the 1). It should work and won't have carrier bloat.
Click to expand...
Click to collapse
You're all good!
I may but I actually have to find one more update I am looking for (Full ODIN FILES). My daily driver note 8 is on N950USQS7DTE5 and it is a T-Mobile Version (though it bein g TMO is inconsequential at the moment. Just thought I might mention it).
That is the update I would like for ATT just so that I know there wont be any differences (or less differences) between my daily driver and this.This is me being picky at this point but isn't the point of life getting what you want? I found one update above that but different bootloader. So for whatever reason may happen, no going back.
What I currently flashed to was N950USQS3BRA8 so it's still on Android 7.1.1 but I did this just to test to the process (my first flashing). Now I am ready.
So I will look for that then flash it and update as usual
Just found, or couldnt find, that ATT has the same update so will just go with what I have. Close as I can get