Database Develop

Wierd phone -- not sure if its G900A ior G900F

Hello every one here is my story
i bought G900F HongKong Version.
started the rooting method as in this Thread http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
after reading and collecting the file, i restarted my phone to the download mode, and there i found the gateway to what seems to be a new phone nightmare.
in the download mode it show the model G900A (not G900F) the phone is brand new came with all G900F package and software. i also checked the IMEI and it show that my phone is G900F.
an hour ago i decided to go with rooting method in the above link, but odin wont flash the kernel. so i posted the issue in the above Thread, and i been told that my phone bootloader might be looked, and in this case its not G900F but instead it G900A, also i been told to search in the AT&T on how to check my boot loader status, but i could not find any clue, also google has no info on how to check my bootloader status.
Attached some photos of my phone details via Phone info app, and also attached the error from the download mode on the phone.
So fat my phone is still a live, i have not put my sim card inside yet (need to change it to nano sim first)
Thank you all

You try this @ command prompt.
getprop ro.bootloader

screem_3 said:
Hello every one here is my story
i bought G900F HongKong Version.
started the rooting method as in this Thread http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
after reading and collecting the file, i restarted my phone to the download mode, and there i found the gateway to what seems to be a new phone nightmare.
in the download mode it show the model G900A (not G900F) the phone is brand new came with all G900F package and software. i also checked the IMEI and it show that my phone is G900F.
an hour ago i decided to go with rooting method in the above link, but odin wont flash the kernel. so i posted the issue in the above Thread, and i been told that my phone bootloader might be looked, and in this case its not G900F but instead it G900A, also i been told to search in the AT&T on how to check my boot loader status, but i could not find any clue, also google has no info on how to check my bootloader status.
Attached some photos of my phone details via Phone info app, and also attached the error from the download mode on the phone.
So fat my phone is still a live, i have not put my sim card inside yet (need to change it to nano sim first)
Thank you all
Click to expand...
Click to collapse
according to the BL screen its an G990A (which is the AT&T US model complete with Locked bootloader) but according to the other screens it seems to be a Canadian version which i believe is a W8 the baseband is ND3 which either the Canadian or U.S. model have. unfortunately it look like you may have bought brick. Try using Odin to flash everything back to Stock but Im not even sure what firmware to tell you to look for. my best guess would be to go by the Download screen and use the AT&T U.S. firmware try using this thread as a guide http://forum.xda-developers.com/showpost.php?p=55133105&postcount=1

deleted

Thank you all for your replies, i talked with the seller and even he does not know how this happen, my guess it might be a refurbished phone, anyway i am returning it, and will try to get G900F European version.

[i537]New Easier Sim Unlock Method 4.4.2/5.0.1

Sim Unlock Method 4.4.2/5.0.1
Disclaimer: i AM not resposile for anything that happens to your phone in the unlikely event something does happen.
this has only been tested lightly but it should work all-right. this is for the i537 S4A only.
You Need to start out on either NE3 or NH3. Downgrade now if you need to. Just remember when downgrading don't flash bootloader. This needs Odin and root to succede. Now That thats out of the way you need to download some files to deal with later on.
MF1 Odin flashable
regionlockaway go to the second post and download the apk to install on your phone.
this method uses an old method in a new way.
here is the guide
1. install regionlockaway and reboot to download mode
2. Flash modem.bin with odin in download mode
3.reboot to system and use regionlockaway. follow the instructions in the app.
4. profit?
As far as my understanding after you do this you can update your modem without it reverting back to being locked. I am running oc7 modem on a T-Mobile MVNO without issues( if you want aws unlock you are going to have to use this then the appropriate modem for that and not allow for the modem to update when updating to oc7 by modifying the oc7 installer and removing the modem from it)

I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
mateo121212 said:
hey guys i have created an easy sim unlock that should work for 4.4.2 and for 5.0.1
for the 5.0.1 sim unlock you have to do it on 4.4.2 and flash a modified partitions file to upgrade to 5.0.1 while keeping sim unlock.
if you guys are interested in it let me know and i will set up a few beta testers for it. i cant say for certain that it works because i dont have a non ATT sim card to test it with.but it should work. it should also allow you to enable aws for those on T-Mobile by following a secondary guide.
let me know and i will start having people beta test. i only need between 1 and 5 testers
Click to expand...
Click to collapse

nrgyitguy said:
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
Click to expand...
Click to collapse
ok ill pm you with a guide once i have it written up.
EDIT: it should be in your inbox

i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.

Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
mateo121212 said:
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Click to expand...
Click to collapse

nrgyitguy said:
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
Click to expand...
Click to collapse
so before you did the guide did it give you issues with the verizon sim? and now it dosent?

It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
mateo121212 said:
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
Click to expand...
Click to collapse

nrgyitguy said:
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
Click to expand...
Click to collapse
sweet thank you for the feedback man. i did the 5.0.1 upgrade method i detailed in the PM after i finished doing the unlock on my phone and it worked the same as what you described (i only had access to vzw lte sim also) so i belive i made the update file correctly also. im not really getting any bites on more testers so if it pans out well for you i will polish up my guide and post it here to have people test it instead of making them PM me.
thanks again for being my beta tester. if we get this working well we can save alot of people alot of money
ps for voice and sms verizon lte sims are useless because they still use CDMA for those features

Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....

nrgyitguy said:
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
Click to expand...
Click to collapse
thank you for your work. im glad it worked for you. i will be posting the guide up here soon.

In reference to....
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!

jaksback said:
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
Click to expand...
Click to collapse
your welcome man. i figured your problem could be fixed with my method. have fun with 5.0.1

partially completed downloads
Never mind. The downloads on dev-host work from my computer but not from tablet or phone.

I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?

spyke70 said:
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
Click to expand...
Click to collapse
Odin back to Ne3 and start over

so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??

Jsturg1990 said:
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Click to expand...
Click to collapse
odin ne3
flash mf1 modem with flash fire
make sure you are rooted and have busybox
use region lock away. try with att sim in phone.

Trying to do this for my s4a but flashfire is being uncooperative, it just crashes any chance it gets. Any other flash apps this will work with?
Edit: do I need safestrap for FlashFire?
Edit2: Fixed the issue with flashfire, If anyone runs into this issue you need to flash stock NE3, and re-root.
Rest of tutorial went perfectly. Cannot test unlock status atm, but no errors.
Thanks Matteo, you're a top lad.

Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!

sunilbeforezod said:
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
Click to expand...
Click to collapse
edit to the edit:
go back to NE3 with odin.
then flash mf1 modem
then try this
[GUIDE] AWS Unlock for i537 I537UCUBML2 (4.3)
read the posts to make it work
also check out this post if you have issues with getting qpst to work. dont follow the whole post just qpst part http://forum.xda-developers.com/showpost.php?p=56023258&postcount=68
then follow the guide i posted in my last edit to keep the aws unlocked modem while on 0C7
edit:
you can use the oc7 deodexed rom. you just have to remove the modem from the rom file useing winrar or 7zip. also you have to remove it from the updater script useing a text editor. drag it out of winrar edit it and then drag it back into winrar. that way if you flash in this order you will be fine
partitions mod file
oc7 deodexed rom.
that way you keep the modem
from when you installed and unlocked mf1 modem on 4.4.2

Flashing TMO firmware onto Verizon Note 8 - Need help identifying correct firmware.

I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!

leprkon said:
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
Click to expand...
Click to collapse
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.

Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
Thanks for the prompt reply! I am downloading the file right now from sammobile. Let's hope it has everything needed! Thanks again!

Please let me know what worked, didn't. I may be doing the same very soon.

Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.

leprkon said:
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
Click to expand...
Click to collapse
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better

BlueFox721 said:
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
Click to expand...
Click to collapse
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.

I failed to mention that you needed the modified Odin. I think it is normal for it to stop at 32% and then start erasing. It did the same when I went from unlocked variant to vzw. Keep us updated on your progress.

leprkon said:
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
Click to expand...
Click to collapse
The boot to bootloader is In the main recovery menu, but yeah...you need to use the modified odin

Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
Support SINGLE-SKU
Supported API: 3
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
-- Installing package...
Finding update package...
opening update package...
Verifying update package...
Update package verification took 1.1 s (result 2).
Installing update...
Successfully installed package.
-- Resizing data...
E:failed to mount /data (Invalid Argument) can't mount '/data', rc = '-1'(Invalid Argument)
E:failed the resizing-data-- omc_binary_download...
-- Deleting selective files
Successfully deleted files selectively
-- Deleting RSU selective file
Successfully deleted RSU selective file
-- amazon_symlink_vze...
-- Deleting VZW's apn file
Successfully deleted VZW's apn file
Successfully verify for dmverity hash tree.
Click to expand...
Click to collapse
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.

leprkon said:
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
Click to expand...
Click to collapse
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator

BlueFox721 said:
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
Click to expand...
Click to collapse
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.

leprkon said:
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
Click to expand...
Click to collapse
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck

BlueFox721 said:
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
Click to expand...
Click to collapse
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.

leprkon said:
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
Click to expand...
Click to collapse
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...

BlueFox721 said:
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
Click to expand...
Click to collapse
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?

leprkon said:
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
Click to expand...
Click to collapse
Good to know....I try to use updato when available...how is that one?

BlueFox721 said:
Good to know....I try to use updato when available...how is that one?
Click to expand...
Click to collapse
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?

leprkon said:
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
Click to expand...
Click to collapse
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...sorry I didn't think of it sooner...hope it helps.
Looks like we need factory binary and Canadian firmware...

BlueFox721 said:
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...
Click to expand...
Click to collapse
I've done version 3.12.7 and PC 3.12+
I'll try the carrier switching instructions again, but I couldn't get it to work properly. I'll let you know how it goes.
Edit -
It looks like those instructions require a factory binary firmware flash. Is there a way of doing it without that?

Desperately Need Help - Samsung SM-N960F/DS + T-mobile PUK and other issues.....

Hi. I am a complete noob when it comes to rooting Android.
**************************UPDATE************************************************
THIS ISSUE HAS BEEN SOLVED. PLEASE SCROLL TO POST #89 ON PAGE 9 TO SEE THE SOLUTION.
https://forum.xda-developers.com/showpost.php?p=77950935&postcount=89
***************************************************************************************************
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".​
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.

orsonwells456 said:
Hi. I am a complete noob when it comes to rooting Android.
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.

bober10113 said:
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
Click to expand...
Click to collapse
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.

orsonwells456 said:
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
Click to expand...
Click to collapse
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker

bober10113 said:
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
Click to expand...
Click to collapse
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.

orsonwells456 said:
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
Click to expand...
Click to collapse
nothing like
SM-N960FOYAU1MYM or something?

bober10113 said:
nothing like
SM-N960FOYAMYM or something?
Click to expand...
Click to collapse
Ah ok. SM-N960FZBDMYM

bober10113 said:
nothing like
SM-N960FOYAU1MYM or something?
Click to expand...
Click to collapse
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it

bober10113 said:
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
Click to expand...
Click to collapse
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.

I went to a site with all "official" downloads and I don't see anything for ZBDMYM........

orsonwells456 said:
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
you can also download it using samfirm tool
enter 960F and MYM in settings it should also be a faster download then the web links

bober10113 said:
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
Click to expand...
Click to collapse
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.

orsonwells456 said:
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
Click to expand...
Click to collapse
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
and in Odin fill in all slots and for csc use CSC but not HOME csc file.
good luck

bober10113 said:
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
Click to expand...
Click to collapse
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.

orsonwells456 said:
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
Click to expand...
Click to collapse
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
check for a folder called .backup and or for a file like:
efs_backup.img.gz
efs_backup.img
or anything similar

bober10113 said:
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
Click to expand...
Click to collapse
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......

orsonwells456 said:
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
Click to expand...
Click to collapse
probably a date code of some sort. Samsung mashes a bunch if letters to come up with country,date code. just Google it.
but try samfirm 3.6 tool to dl
https://1drv.ms/f/s!AhXVLDDj8g3AgdJZClzJmsN17YL2CQ

I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4

If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......

orsonwells456 said:
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
Click to expand...
Click to collapse
yeah looks good. its October 1st build
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
orsonwells456 said:
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
Click to expand...
Click to collapse
well ure screwed either way. the goal is to restore everything back to stock and see if you can get a line working
btw was there a seal on the box that you had to break in order to open the box when you first got it?

SM-N960U Stuck In Roaming After Moving From Sprint To Verizon

Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?

quackmaster said:
Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?
Click to expand...
Click to collapse
Since you've already done a factory reset I would think the next logical step is to flash the Verizon or the unlocked firmware. What about the SIM card, did they try a new one?

They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?

quackmaster said:
They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?
Click to expand...
Click to collapse
There is a thread somewhere in the guide section I recall seeing before from daillcyruz (I think was the OP). Search it and you will find instructions on how to install the VZ firmware.

I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.

quackmaster said:
I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.
Click to expand...
Click to collapse
Maybe try using Odin?

BladeRunner said:
Maybe try using Odin?
Click to expand...
Click to collapse
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.

quackmaster said:
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.
Click to expand...
Click to collapse
I ran across a thread where someone had posted a version of Odin that ran on Linux.
Here's one: https://forum.xda-developers.com/android/general/utility-odin-linux-jodin3-casual-t3777030
and another: https://forum.xda-developers.com/android/general/odin4-v1-0-linux-t3782930

None of these work. I am not able to get the PIT from device.

quackmaster said:
None of these work. I am not able to get the PIT from device.
Click to expand...
Click to collapse
you might be able to use odin in wine.. i never tried it tho.. heimdall i havent got to work either..
what firmware are you on? pie is pretty good at switchin csc based on sim inserted.. also crk3 i think it is you can access the csc.apk and change csc easily to any csc.. i havent found any other firmware it works on tho besides crk3..
if u can manage that, theres update.zips you can adb sideload but u need to b on specific firmware versions to update to certain firmwares..
i was messin around with firmwares and changed my csc to sprint.. i have vzw.. although it says roaming i am connected to verizon network so dont think its actually roaming but im not 100% sure

OK
Thanks everyone for help!
I was able to successfully flash using a Windows 10 VM running in Oracle VirtualBox VM. I used Odin v3.13_B. I did not re-partition.
I used this firmware:
https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U/VZW/download/N960USQS1ARJ9/242777/
There were no errors though after the phone rebooted it said there was an "unauthorized attempt" to install software.
It then tells me to connect to Wifi in order to verify my identity.
I cannot skip this process.
The Sprint firmware still seems to be present as I see Sprint applications. I am still roaming on Verizon though the port request was completed at least that's what they said at the store.
Interestingly the Sprint logo does not appear upon booting phone. Only the Samsung logo.
To remove Sprint firmware do I need to flash to the non-carrier firmware first before trying Verizon?

I sounds like someone else had the same problem with the SM-N960U.
The solution in that thread seems to be using the SM-N960U1 firmware.
Can anyone confirm this would be a safe fix to try?

SamMobile is a horrible website
I paid the 8 euro fee and the download for https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/VZW/download/N960U1UES1ARJ9/244757/ still takes like an hour.

It seems there's some Google phone protection targeted to deter thieves. That could be why it requires me to sign into the previous Google account after flashing.
I am removing my Google account from the phone, doing factory reset, then will try to flash Verizon firmware.

After flashing again it looks like some software called "Sprint OMDAM" still present on the phone. This loads after flashing. When I try to activate on network it comes up while the phone remains in roaming. Again Sprint unlocked the phone.
Should I re-partition?

OK
I wiped the cache partition and did factory reset.
I will yet again try another flash.

The Sprint logo is gone but Sprint apps still remain.
Should I try to re-partition the phone? I don't understand why Sprint applications are showing up when I flash Verizon firmware using Odin.

Make sure you have a Verizon SIM card in the phone.
1. Remove your accounts (Google and Samsung) under settings.
2. Factory reset under settings.
3. Download the U1 firmware using the SamFirm tool
4. Using modded ODIN 3.13.1B flash all four files (use CSC_OYN not the HOME_CSC file).
Optional, if you want WiFi calling and VoLTE:
Download the VZW N960U firmware using the SamFirm tool and flash it the same way using modded ODIN, but this time include the USERDATA file as well.

I think now on Verizon network after using U1 firmware!