Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.
I have been looking for 3 days now for the US firmware for the SM-T550NZASXAR (might be the same as SM-T550NZAAXAR) and I can't find it. Sam mobile has the files for many countries but fails to show the US version. Am I missing something?
The digitizer keeps losing the touch sensing ability but I'm pretty sure it's a software problem as it comes back after maybe 15 minutes then it stops again after about 20 minutes of use. I want to try and re-install the OS with Oden and see if it clears whatever is going on. I'm hoping it's just bad cache or something.
The Canadian version is usually the same but double check just in case
Sent from my SM-T350 using XDA Free mobile app
Same Issue. I been also looking for US firmware for my SM-T350 Samsung Galaxy Tab A. I see it available for all other countries but not for USA. For all people that live in the US like me. We need to all nag Samsung & complain cause obviously they only support it for all other countries & not US. It pisses me off & it's so unfair. I need the firmware for part of the procedure to fix my rooted tab that's in bootloop
Upset with T-350 firmware situation
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
weaselleaf said:
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
Click to expand...
Click to collapse
http://www.thegalaxytabforum.com/index.php?/topic/33026-recovery-twrp-2871-tab-a/
Twrp tested on sm-t350
weaselleaf said:
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
Click to expand...
Click to collapse
twrp for SM-T350 is file name twrp-28.71-t350.tar
I can't link or i would link you it. Just google search that file name and there is one from android file host
Flash with Odin 3.10.7
Tested and works perfect
Seth50 gets all the credit just confirming it works
WOW! i have been messing with this for hours and cant believe that the samsung smart switch offered such an easy solution.
i made the mistake of flashing a rooted firmware file before unlocking the bootloader and soft bricked it. the smartswitch asks for the model# (SM-T350) and the serial number (no, im not putting mine here), tells you to enter odin mode and then it does all of the dirty work for you... amazing!
one thing to keep in mind is that the install for smart switch will not work on newer machines unless you install legacy software that you can find here https://www.microsoft.com/en-us/download/confirmation.aspx?id=5582
qixiixiq said:
WOW! i have been messing with this for hours and cant believe that the samsung smart switch offered such an easy solution.
i made the mistake of flashing a rooted firmware file before unlocking the bootloader and soft bricked it. the smartswitch asks for the model# (SM-T350) and the serial number (no, im not putting mine here), tells you to enter odin mode and then it does all of the dirty work for you... amazing!
one thing to keep in mind is that the install for smart switch will not work on newer machines unless you install legacy software that you can find here https://www.microsoft.com/en-us/download/confirmation.aspx?id=5582
Click to expand...
Click to collapse
I realize this is an old thread, but looking for help. Purchased a Wifi-only Galaxy Tab A, and looking for the stock 6.0.1 ROM. The Smart Switch software doesn't downgrade it anymore. They've since updated the software to remove that capability, but even older versions still reapply Nougat. Sammobile.com doesn't seem to have it. Has anyone had success finding the stock MM US ROM for this tablet? If you're asking why, adb restore doesn't work on Nougat and I'm trying to restore backups without root. I have a second SM-T350 fresh out of the box, and restore is working. So, want to downgrade to official MM to restore, then maybe upgrade again if I feel like it....
Edit: Embarrassingly, it's in this same forum.... Download it now...I'll see myself out....
https://forum.xda-developers.com/ga...m-stock-builds-sm-t350-ghost-project-t3529439
OK I'm a complete newbie here. I bought the 8" S2 International unlocked version from Amazon and will take it to AT&T to activate it tomorrow. It's on 5.0.2 and is not seeing any OTA updates. Does anyone know if there's a way to get 5.1.1 OTA? If not, does anyone know if Samsung has commented as to whether they'll release 5.1.1, or even Marshmallow, for this device or will I have to go to a custom ROM?
Also, is there an absolute beginners guide to this site? I've been reading through the threads and keep seeing terms like odin, twrp, and many others that I don't know what they mean and I'd like to figure out.
Thanks.
CincyTriGuy said:
OK I'm a complete newbie here. I bought the 8" S2 International unlocked version from Amazon and will take it to AT&T to activate it tomorrow. It's on 5.0.2 and is not seeing any OTA updates. Does anyone know if there's a way to get 5.1.1 OTA? If not, does anyone know if Samsung has commented as to whether they'll release 5.1.1, or even Marshmallow, for this device or will I have to go to a custom ROM?
Click to expand...
Click to collapse
i just received the same device yesterday and so far, it's working just fine on at&t: including data full phone features (i wasn't aware that this version of the Tab S2 had a full fledged phone). i inserted my nano sim from my dual-sim note5 and the S2 configured everything automatically. also, i didn't see an OTA when i checked yesterday and there's nothing at sammobile.com which is where one can generally find firmware (stock ROM) for Samsung devices. any custom ROM right now will likely be 5.0.2.
CincyTriGuy said:
Also, is there an absolute beginners guide to this site? I've been reading through the threads and keep seeing terms like odin, twrp, and many others that I don't know what they mean and I'd like to figure out..
Click to expand...
Click to collapse
Odin = Windows based application used to flash firmware to Samsung devices.
TWRP = a custom recovery that - once your phone is rooted (similar to admin privileges on windows pc) - allows one to flash a custom ROM or other components/features not on a stock device. you can also create backups/nandroids of your device so you can restore your device if something goes wrong (similar to resorting a windows system image to a new hard drive). always, always backup when trying things out. tutorials are here, but sometimes not easily located via search. :good:
Hello everybody,
a friend of mine has recently come back from a 12 months work experience in NY (we live in Italy) and gave me his american Galaxy S6 Edge since he has just got a brand new Iphone 7.
This S6 is AT&T version (SM-G925A), sim unlocked, still Lollipop installed.
My question: is there a way to flash SM-G925F international firmware and get OTA here in Europe?
I already read about people trying to do this for using in USA, but posts are 2 years older or without replies.
I read also about compatibility of LTE network...but I just want to give a try.
Any advice?
Thank you guys
I have the same phone as i used to work overseas.
I would not suggest you would change to F version as you might brick it, or since it is built for AT&T it should stay on the AT&T. Think of specific drivers and so on. This version has slightly different hardware from the European version.
Why not update the firmware with Odin. start with lollipop updates go to marshmallow and nougat.
Thanks my friend, you were right (almost brick the phone). Now I'm on MM At&T but with DRK error, something about dm-verity.
Phone always reboot in recovery with this error; I had to flash a special stock kernel found here that, I suppose, disables dm-verity, just to boot it up.
Maybe the EFS folder got corrupted...no way to install Nougat via Adb, I'm unable to mount system as RW.
I actually didn't know that there were Samsung phones around the world with bootloader locked down...shame on At&t!
My friend didn't even want it back, now it's on my desk taking dust...what a waste of good hardware!
Thanks anyway
aluks1982 said:
Thanks my friend, you were right (almost brick the phone). Now I'm on MM At&T but with DRK error, something about dm-verity.
Phone always reboot in recovery with this error; I had to flash a special stock kernel found here that, I suppose, disables dm-verity, just to boot it up.
Maybe the EFS folder got corrupted...no way to install Nougat via Adb, I'm unable to mount system as RW.
I actually didn't know that there were Samsung phones around the world with bootloader locked down...shame on At&t!
My friend didn't even want it back, now it's on my desk taking dust...what a waste of good hardware!
Thanks anyway
Click to expand...
Click to collapse
Good ole US carriers. Gotta love em. I aint seen the light of root or unlocked bootloader in a few years now other than my g4. Which no roms no twrp. But root only.
Hi everyone! Hope everyone is safe and healthy. Been out the rooting game for a bit but I decided on this. Unfortunately for me the 950U has an unlockable bootloader so I got the 950F since I still want to root and install a custom ROM. I just started reading and it seems (correct me if I'm wrong) there is a CSC mod (for Pie) to get your wifi calling and VoLTE working on the 950F if its to be used on the T-Mobile network. That's a relief since my main fear is what network specific features where going to be unusable if I went with the F instead of the U for T-Mobile usage. It seems also that (again, please correct me if I'm wrong) CSC mod is already implemented on some custom ROMs. I'm looking to try out DeluxeROM since it seems like a well stable ROM that has been out for a minute. I understand I have a TONS to read so I won't be even touching my new phone until I feel informatively ready. I'm just asking that if any of you would like to spare some of your precious time to share any info, tips, precautions, limitations (by not having a US model for T-Mobile), or anything in the matter...or if you want to say "[email protected]#k off and go read" I will welcome that too . Thank you much!
mrrobc97 said:
Hi everyone! Hope everyone is safe and healthy. Been out the rooting game for a bit but I decided on this. Unfortunately for me the 950U has an unlockable bootloader so I got the 950F since I still want to root and install a custom ROM. I just started reading and it seems (correct me if I'm wrong) there is a CSC mod (for Pie) to get your wifi calling and VoLTE working on the 950F if its to be used on the T-Mobile network. That's a relief since my main fear is what network specific features where going to be unusable if I went with the F instead of the U for T-Mobile usage. It seems also that (again, please correct me if I'm wrong) CSC mod is already implemented on some custom ROMs. I'm looking to try out DeluxeROM since it seems like a well stable ROM that has been out for a minute. I understand I have a TONS to read so I won't be even touching my new phone until I feel informatively ready. I'm just asking that if any of you would like to spare some of your precious time to share any info, tips, precautions, limitations (by not having a US model for T-Mobile), or anything in the matter...or if you want to say "[email protected]#k off and go read" I will welcome that too . Thank you much!
Click to expand...
Click to collapse
Although I can't answer your specific questions my precaution advice is to make sure you read the whole OP before you flash anything, and as soon as you have flashed TWRP make sure to backup your EFS file and keep a number of copies of it. Also take note that flashing TWRP trips Knox so Samsung Pay will never, ever work again. Tripping Knox does break other things like secure folder but most custom roms (based on stock filmware) have fixed it.
Deluxe Rom is a good choice!
stonedpsycho said:
Although I can't answer your specific questions my precaution advice is to make sure you read the whole OP before you flash anything, and as soon as you have flashed TWRP make sure to backup your EFS file and keep a number of copies of it. Also take note that flashing TWRP trips Knox so Samsung Pay will never, ever work again. Tripping Knox does break other things like secure folder but most custom roms (based on stock filmware) have fixed it.
Deluxe Rom is a good choice!
Click to expand...
Click to collapse
Thank you very much for your response. Yes I've been fully aware of all that. That's the reason I never sporting a newest-n-greatest phone that I would have to get out in payments from T-Mobile. I always buy cash new, couple of gens back flagships for my daughter and I (I'm getting her the S9+) so I could do whatever I want to them w/o worrying about warranty service. I'm not a fan of anything Samsung when it comes to software so I do debloat most of it...including health, pay, galaxy store, knox, etc. My common sense is my own security...at the least its been so far. Yes I'm also aware about backing up the EFS files (I do keep separate TWRP backups for my devices also in my PC just in case). Again, thank you for replying and be safe .