So, I ordered a refurb sm-p600 Wifi-only tablet from Amazon, but I received a Verizon sm-p605v. Now they show out of stock on the Wifi model. Am trying to arrange a swap, but don't know how successful I'll be.
It's my first tablet and I absolutely LOVE it and don't want to give it up.
So, it's basically the same thing, but there are issues:
1.) Has Verizon junk all over it.
2.) Complains about no SIM card - if I put in a SIM card it complains about activation. (These don't appear to ever go away)
3.) Have to keep it in airplane mode or it will drain the battery trying to connect, if I keep it in airplane mode, at least one app (Accuweather) complains about no network
4.) And this is the biggest issue - can't check for new updates - I really want Lollipop so it matches my phone, but it basically says update is unavailable. I assume Verizon has it set up so that you have to pull updates only from them.
I'm never going to put this on a mobile plan and I'd really prefer to have the non Verizon tablet, but if I can't, is it possible to flash the stock wi-fi sm-p600 firmware onto this so that it thinks it's a sm-p600 - or is this a recipe for brick making?
I also haven't been able to find a sm-p605v lollipop image, so I may be out of luck assuming the answer is no.
I'm in a similar situation. I purchased what I thought was a SM-P605 (international version) and I got shipped a SM-P605V (Verizon edition). In my case, the vendor listed the device as an SM-605, but it was an SM-P605V. Further down in the listing it listed it as a Verizon edition, so that's the reason they declined the return.
Unfortunately, you cannot use SM-P600 firmware, as it is a different processor.
There is a way to update it to 5.1.1 though. When plugging the tablet into the PC, there is a Verizon utility for Windows on the tablet that lets you update the software. (it's based on Samsung Kies). I just did it yesterday. Works fine. I'm trying to figure out if I can put a non-Verizon factory Samsung image on it so I can at least have the option to put my own custom image on it (the Verizon edition has a locked bootloader, which prevents you from putting non-Samsung ROM images).
I personally am sick of vendors customization of Android to the point where it is not recognizable. Give us the option for stock Android...
After 3 attempts I finally got them to send me the correct Wifi only model, which works great!
Related
Hi there guys,
long story short, i got Samsung Galaxy note 10.1 2014 (sm-p600xzwebtu) Live Demo Unit from work, which i believe is specifically manufactured for retail and comes with quite a lot of limitations, so i need to flash it and install either custom os (i was thinking cyanogenmod) or at least official android.
First of all, it does have developers mode, and it allows me to volume down+power to get it to "downloading os" screen, so i assume i should be able to flash it with odin, but before i do try, maybe someone has dealt with same problem before and has ready to go solution?
reason i am asking is that last year i got couple of Archos devices, those as well were made for retail demo, and they had hardware limitations on ability to flash roms
Staypoh said:
Hi there guys,
long story short, i got Samsung Galaxy note 10.1 2014 (sm-p600xzwebtu) Live Demo Unit from work, which i believe is specifically manufactured for retail and comes with quite a lot of limitations, so i need to flash it and install either custom os (i was thinking cyanogenmod) or at least official android.
First of all, it does have developers mode, and it allows me to volume down+power to get it to "downloading os" screen, so i assume i should be able to flash it with odin, but before i do try, maybe someone has dealt with same problem before and has ready to go solution?
reason i am asking is that last year i got couple of Archos devices, those as well were made for retail demo, and they had hardware limitations on ability to flash roms
Click to expand...
Click to collapse
Yeah, you should have no problems. what i would personally do first is download the stock samsung firmware for consumer/non demo mode tablets and flash that. then just follow root procedures and all that.
I could be mistaken, but I don't believe that's an actual LDU device. LDUs usually have an X at the end of the model number (ie SM-N900X), and I've only seen LDU phones, never any LDU wifi-only tablets. BTU is the region code for the UK, you probably just have a normal UK tablet with retail mode software on it. The hardware and firmware on the device are no different than a retail UK device, but it's running a special Samsung Retail Mode that restricts a lot of functions.
If you know the proper passwords, you should be able to remove the retail mode. Flashing a stock firmware might not work, as the retail mode software is a user app and NOT part of the device's firmware (unless you DO have an LDU, but based on the model number I don't believe that's the case), but it's worth a try. A factory reset would remove the retail mode, but some of the newer retail mode software prevents you from doing that.
I bought a refurb N7 from Groupon months ago. They stated it was a verizon unit and it came in a verizon box. They stated that only a verizon sim would work with it anything else would only achieve 3g speeds. I bought it anyway to try with my grandfathered unlimited At&T sim and it's been working fine with LTE. However it is still running 4.4.2. and every time I check for updates it states I'm completely up to date. I've never had an update since owning it, about 6 months. I had read somewhere that the Verizon N7 will not receieve an OTA unless it has a Verizon sim in it. Does anyone know if this is true? Or is it common for people to still be running 4.4.2 and I shold see lollipoop soon? Also when it boots up, there is a unlocked padlock icon which I believe means unlocked bootloader, it came like this. Would that affect any OTA updates? Thanks
Don't quote me on this and double check, but I'm pretty sure the nexus toolkit has a option for the lte version.
What happens when your nexus is powered off and you long press volume down and power, then use volume rocker to select recovery, then power to select? If it reboots then you don't have CWM or TWRP. If it takes you to TWRP or CWM then ur already unlocked with a custom recovery.
If you aren't unlocked you'll have to wipe you're entire tablet to unlock it. The toolkit is really easy. It let's you install the drivers for your pc. Then you can download and install the latest firmware available.
I bet you anything Groupon used some weird system to mass wipe their tabs. And something in that prevents it updating. My friend that got samsung galaxy gear live smartwatches had the exact same problem.
Just search around and you should find your answer. Let me know if you need help with the nexus toolkit.
And if u are anti tinkering, u could also relock the bootloader after getting it current. Then u will definitely get updates.
Sent from my LG-VS985 adorned w/ Illusion ROM
Hi Guys,
I've just spent the last 8 hours trying to get an Canadian Note 7 to custom recovery and ROM with NO luck !
I've done a couple of Note 7s of UK spec but this is the first Note 7 from Canada, and so far i've had no luck at getting it to accept anything.
The handset has received the cripple code that has disabled wifi, blutooth, 4G, tethering and reduced the battery capacity to 15%
I have tried several files and different methods of loading in a custom recovery so i can then load a custom ROM.
The favorite is to use ODIN and then either load CWM or TWRP.
When trying to load either CWM or TWRP i get an "Auth Fail" or "QTQ Close" error
I tried to use the Sprint method to get into the system and allow a custom ROM and all this did was brick the phone... Its currently stuck in no boot state which just takes me into the standard android recovery with errors of "dirty targets", "check DRK files" and "dm-Verity verification failed"
At the moment i cant find a way to get the handset to load a custom recovery and then a rom, stock or custom.
If anyone can help with fixing This-POS Canadian Telus Note 7 Handset i would greatly appreciate it before i stamp on it and send it back to samsung !
cheers guys
The Canadian variant has a locked bootloader, so no custom recovery and no root. There are workarounds to get the older firmware back that doesn't cripple the phone. There are threads on here for that if you search around.
Sevael said:
The Canadian variant has a locked bootloader, so no custom recovery and no root. There are workarounds to get the older firmware back that doesn't cripple the phone. There are threads on here for that if you search around.
Click to expand...
Click to collapse
Correct, no root yet unless its first gen N7 with first firmware but im sure non around anymore.
Best bet is to find a firmware and downgrade to 100% battery. Then block all the packages to prevent future updates from samsung. If you IMEI was blocked then that is a whole different ball game in which Samsung is winning so far in Canada
Thanks for the info guys
I spent 9 hours in the end attacking this thing from all angles and just managed to corrupt it so it doesn't even boot now.
The Canadian phone companies and samsung have done a dam good job at taking these phones down or rendering them totally useless.
Own31,
Do you have any recommendations on what i should use / try to rectify this
Hi, can you put it in download mode? Power +home+volume down
Sent from my SM-N920T using XDA-Developers Legacy app
Can someone link me the sprint engineering guide for the snapdragon phones?
I accidentally tried to flash a exynos rom and bricked it before realising there were multiple variants durrr
Managed to find my stock rom for my rogers note 7 and used odin to flash it in download mode to reset it. Currently turns on and has the 100% battery but every time I turn on wifi it prompts for the 60% battery update and I don't know how to block the package.
Edit: Caved and bought package disabler pro and no longer get prompts
GlitchZenfone2 said:
Can someone link me the sprint engineering guide for the snapdragon phones?
I accidentally tried to flash a exynos rom and bricked it before realising there were multiple variants durrr
Managed to find my stock rom for my rogers note 7 and used odin to flash it in download mode to reset it. Currently turns on and has the 100% battery but every time I turn on wifi it prompts for the 60% battery update and I don't know how to block the package.
Edit: Caved and bought package disabler pro and no longer get prompts
Click to expand...
Click to collapse
What firmware are you on? Unless its APH1 you cant root.
Sent from my Note 7, S7 Edge or S6
jopa7 said:
Hi, can you put it in download mode? Power +home+volume down
Click to expand...
Click to collapse
Hi Jopa, yes i can still get into download mode
GlitchZenfone2 said:
Can someone link me the sprint engineering guide for the snapdragon phones?
I accidentally tried to flash a exynos rom and bricked it before realising there were multiple variants durrr
Managed to find my stock rom for my rogers note 7 and used odin to flash it in download mode to reset it. Currently turns on and has the 100% battery but every time I turn on wifi it prompts for the 60% battery update and I don't know how to block the package.
Edit: Caved and bought package disabler pro and no longer get prompts
Click to expand...
Click to collapse
I don't suppose you've seen a rom for a Telus Note 7 have you?
the one i'm trying to flash reports as:
6.0.1/MMB29M/N930W8VLU3APL1
Darkstorm_G4 said:
I don't suppose you've seen a rom for a Telus Note 7 have you?
the one i'm trying to flash reports as:
6.0.1/MMB29M/N930W8VLU3APL1
Click to expand...
Click to collapse
I'd have to refind it. There was a link I found for all the canadian roms but I only downloaded the one I needed of course.
force70 said:
What firmware are you on? Unless its APH1 you cant root.
Sent from my Note 7, S7 Edge or S6
Click to expand...
Click to collapse
Nop... I'm on API3.
I'm using package disabler right now to avoid the OTA updates. I had a notification today that the update was downloading so I just turned off wifi and disabled almost everything under the sun (besides core services) relating to samsung and it no longer seems to be connecting to the update server which is what I want in the end.
Well the saga continues...
I managed to trick it into letting me sideload from ADB.... only problem is i couldn't find any files in .zip format to side load and those that i could it wouldn't accept.
I did manage to get a partial sucsess with odin and got a CP file to install properly... sadly it rejected the BL, AP and CSC files and now its really screwed things up as it just boot loops now and the android recovery kinda doesn't work now.
So any ideas on how to defeat this POS, i refuse to let Samsung Canada and the phone companies beat me, but i think i am fighting a losing battle...
Only half decent firmware files i could find were N930W8VLU1APH1_N930W8OYA1APH1_ESK
Ok really screwed it now ! GERRRRRR
Managed to get it to take a new Bootloader ! all completed in ODIN and the phone rebooted, started to load then crashed and now wont turn on at all - TOTALLY BRICKED !
but the strange thing is, when you plug it in windows still sees it, you would expect nothing to happen like if the phone were switched off completely, but Windows 7 sees it as a device and set up drivers for ELINK HS-USB QDLoader 9008 (COM5)
very odd, and incredibly frustrating !
Darkstorm_G4 said:
Well the saga continues...
I managed to trick it into letting me sideload from ADB.... only problem is i couldn't find any files in .zip format to side load and those that i could it wouldn't accept.
I did manage to get a partial sucsess with odin and got a CP file to install properly... sadly it rejected the BL, AP and CSC files and now its really screwed things up as it just boot loops now and the android recovery kinda doesn't work now.
So any ideas on how to defeat this POS, i refuse to let Samsung Canada and the phone companies beat me, but i think i am fighting a losing battle...
Only half decent firmware files i could find were N930W8VLU1APH1_N930W8OYA1APH1_ESK
Click to expand...
Click to collapse
That file is useless unless that is what was on the device prior to it getting messed up.
So what was it on when you tried messing with it PI3?
Sent from my Note 7, S7 Edge or S6
---------- Post added at 04:19 PM ---------- Previous post was at 04:03 PM ----------
Darkstorm_G4 said:
I don't suppose you've seen a rom for a Telus Note 7 have you?
the one i'm trying to flash reports as:
6.0.1/MMB29M/N930W8VLU3APL1
Click to expand...
Click to collapse
I think that was the firmware which came with the device, the first original firmware which shipped with it from samsung before the APH1 OTA.
Of course you cant flash that, no surprise there
Sent from my Note 7, S7 Edge or S6
APH1 Note 7 Rogers with 15% update, no WiFi/Cellular
New user here. I've got an APH1 Note 7 first edition without the green battery icon on Rogers in Canada in the same situation - 15% battery, no WiFi, no cellular. I've tried a few package disablers but it seems all the free ones require WiFi to activate the product license (which I can't exactly do). It's failed every Odin flash attempt I've made, usually stopping at recovery.img or a couple of steps after that. I've tried flashing firmware from all US variants and multiple Canadian ones as well. Any ideas on how to recover the phone? It still boots (even though I semi-bricked it twice). I'm thinking that there might be some options through ADB - could anyone guide me on how to do that?
moldee5 said:
New user here. I've got an APH1 Note 7 first edition without the green battery icon on Rogers in Canada in the same situation - 15% battery, no WiFi, no cellular. I've tried a few package disablers but it seems all the free ones require WiFi to activate the product license (which I can't exactly do). It's failed every Odin flash attempt I've made, usually stopping at recovery.img or a couple of steps after that. I've tried flashing firmware from all US variants and multiple Canadian ones as well. Any ideas on how to recover the phone? It still boots (even though I semi-bricked it twice). I'm thinking that there might be some options through ADB - could anyone guide me on how to do that?
Click to expand...
Click to collapse
Your lucky man...original firmware means you can still root with the engineering firmware. That should kill any OTAs. Check out the development forum in the Tmo note 7 area.
In addition check out note7alliance.com they have a working disabler.
Is yours still working on the network? I had thought all note 7s here were blocked from cellular networks...mine is from rogers
Sent from my Note 7, S7 Edge or S6
force70 said:
Your lucky man...original firmware means you can still root with the engineering firmware. That should kill any OTAs. Check out the development forum in the Tmo note 7 area.
In addition check out note7alliance.com they have a working disabler.
Is yours still working on the network? I had thought all note 7s here were blocked from cellular networks...mine is from rogers
Sent from my Note 7, S7 Edge or S6
Click to expand...
Click to collapse
Just like you, running on Rogers with no network connectivity.
Seems like the N7A package disabler requires WiFi to authenticate, so I can't use that method sadly.
Right now I'm trying to use a spare rooted phone to put a package disabler app onto my SD, to see if I can then run the app in the Note 7. It's one of the few options I have left, but I'll still try it, as I can't flash firmware without blocking updates.
moldee5 said:
Just like you, running on Rogers with no network connectivity.
Seems like the N7A package disabler requires WiFi to authenticate, so I can't use that method sadly.
Right now I'm trying to use a spare rooted phone to put a package disabler app onto my SD, to see if I can then run the app in the Note 7. It's one of the few options I have left, but I'll still try it, as I can't flash firmware without blocking updates.
Click to expand...
Click to collapse
If you follow there directions having wifi on briefly isnt a problem.
I think i have the firmware your running saved somewhere if you need it.
Sent from my Note 7, S7 Edge or S6
force70 said:
If you follow there directions having wifi on briefly isnt a problem.
I think i have the firmware your running saved somewhere if you need it.
Sent from my Note 7, S7 Edge or S6
Click to expand...
Click to collapse
I've got the Rogers APH3 firmware lying around, so I should be good on that front.
I'll see how far I can get with the N7A method. Thanks for the advice.
i have a rogers note 7 still. thought about trying to make it work but seeing everyones struggles, doesnt seem worth it. anyone have luck selling these things?
The market for Note 7s is mixed. Some units requiring more software work sell for as little as $200 (that's what I paid); decently working units (e.g. 60% limited units) fetch ~$600; and perfect condition units without any disabling updates can still for $1000. Some brand new in box units can still sell for $2000.
That said, is selling even legal? What are the implications around that?
Hello,
I am currently with Freedom Mobile, but my phone was purchased through Rogers, has the open Network Bands to use the Freedom network, and a new P6 Freedom Mobile SIM Card. My phone is also running as HTC_001.
Before modifying my phone and having to re-do everything I may have done in the past:
Can anyone on either Freedom Mobiles network with their stock RUU confirm they have the Wifi Calling option and it works?
To be able to use services of a carrier, like WiFi calling etc, you MUST be using a firmware that came from that carrier. If freedom issue a specific firmware for the m9 you must use it. If they don't and their phones come "network unlocked/debranded", ie using the 401 firmware, then you should be able to access the WiFi etc on any device. Another example is if you want to use tmobile features then you need a tmobile firmware.
So the question you need to find the answer to is "does freedom carrier have a branded firmware for the m9".
You are correct. Based on my research earlier, I came across that same conclusion.
I think the best/only way to test this however, is a) if someone has a latest version of their branded firmware and can check this or b) I get a TWRP restore and install this on my phone (I assume this is possible and not IMEI restricted) or c) I find another way to get to a stock firmware.
I changed my CID back to the Freedom Mobile one and downloaded the stock TWRP backup from the old Canadian Stock ROM thread, but it is either too large or possibly too old and incompatible with my phone.
I had to use ADB commands through computer to restore, and it looked like it would accept. However, the computer was stuck at "unlock phone screen to continue" and TWRP said "MTP enabled."
Those backups are most likely too old. You can try to find a suitable RUU on easy-firmware or you need to contact llabtoofer's RUU service since at the moment there is no freely available RUU for your phone. The links can be found in the FAQ of the ReadMe thread.
Sent from my Motorola XT1572 using XDA Labs
Just a quick update. I ended up aborting this "project" of mine.
Despite using Mac OS, encountering corrupt zip files and other files issues where I would get an 22 RU_HEADER_ERROR, I ended up finding my biggest issue.
My MID was set to OPJA10000, instead of 0PJA10000. This issue caused multiple hours of frustrations. I have now flashed my phone back to stock 4.28.401.3. I will most likely have to reinstall TWRP and restore my previous backup.
On another note, is anyone else unable to find the HTC Mail app in Google Play store? Mine crashes every time I try to reply to emails or create a new one. Google Play Store on the computer shows my M9 is not compatible.
Get rid of Google Chrome. I don't know what's exactly the reason but current chrome versions break the HTC Mail app.
Sent from my HTC One M9 using XDA Labs
Same for me. Not compatible.
Just an update to this.
They released a new version of HTC Mail v10.70.1031252.
Based on quick trials, this has resolved the recent issues regarding HTC Mail and Google Chrome being at the latest version, regarding crashing when creating a new email or replying, but I have not tested it extensively.
I know this should be a new thread with a proper title instead of piggybacking on an old one, so if a mod can create one (or prefers I do), that would be great.
Context: I have a Verizon branded Note 10+, trying to use a Mint mobile connection. Wi-fi calling doesn't work, connection speed is atrocious, but everything works swimmingly out of the box when I put the same SIM in my unlocked Pixel. I am quite sure my Note 10+ is unlocked because it is fully paid off and well past the 60 day period, and more importantly because the Mint SIM DOES work in it, just very poorly.
So it's quite evident that I have to flash TMB firmware to get a serviceable reception.
Trying to follow the steps outlined here - https://forum.xda-developers.com/galaxy-note-10+/how-to/n975u-n975u1-firmware-links-t3957648
Based on what I understand I have to flash unbranded firmware first and then my desired carrier firmware which is T-Mobile. Can someone please help me understand what firmware I should be looking for?
My current baseband version N975USQU3CTE7.
My question is when downloading through Frija, should I be looking for SM-N975U1 (VZW) firmware or SM-N975U1 (XAA) firmware for the first step? Or can I use either?
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
TheXev said:
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
Click to expand...
Click to collapse
To anyone reading this in future, I followed this guide to the letter and worked flawlessly for me..every feature that I wanted now works without any additional configuration..signal quality has improved drastically..
Thanks for taking the time to write this..took me a couple of days to set everything up and prepare..I am glad I didn't rush it