Related
Any assistance troubleshooting my issue is greatly appreciated.
Background:
I have AT&T SGH-317. It was stock/unlocked/unrooted. I traveled to Thailand and signed up with TrueMove to get new SIM card to use while in that country. Upon inserting the new SIM card and powering device up, I receive Unlock prompt. I contacted AT&T to get unlock code, but they refused to give me one because I'm still under contract (even though it's for another phone and my SGH-317 is already paid for).
I took the phone to a shop (MBK) to get it unlocked. But they were not able to do it without rooting the device. I mention this because I don't know what method they used to unlock the device. So at that time, I had unlocked/rooted device running Stock Android 4.4.2 Baseband I317UCUCNJ1. I installed the new SIM card but not able to connect to 3G, H+. I changed Network Mode to WCDMA only and adjusted APN to TrueMove settings, still no 3G, H+ connectivity.
I came to this forum to search for solutions and have done the following:
1. Flashed ROM to DN3(Ditto Note 3) ROM using Odin 3.07 and openrecovery-twrp-2.8.0.0-t0lteatt.img.tar
2. Set Network Mode to WCDMA only
3. Set APN to TrueMove parameters
I tried to Flash modem file suggested in One-Stop Shop Thread but failed miserably. I tried both I317UCUCNE5 and CWM-I317UCUCNJ1. Both files were .zip, so I unarchived and then rearchived using 7Zip to make .tar file so Odin would be able to utilize. Both attempts failed when I tried to flash.
I checked with my brother who has the same phone to see what modem he is using since his device works. He is using I317UCBMK6 baseband. I tried to download that baseband from link provided in One-Stop Shop thread, but it's an .exe and my virus protection software flagged it as virus and immediately deleted it off my computer.
The Ask:
1. Appreciate it if anyone is able to provide I317UCBMK6 baseband as .zip or .tar
2. Inform me on why the other two basebands failed flash and assist with proper methodology
3. Inform me on best option to solve my issue of not being able to connect 3G, H+ on my SGH-317 running DN3(Ditto Note 3) ROM with current baseband I317UCUCNJ1.
Thank you, community!
Hey guys. I'm very new and have spent the last few days researching about how the whole rooting, unlocking sim, unlocking bootloader, flashing radios and installing customer ROM's work.
From what I understand the process all start with having an unlocked bootloader so that you can install a recovery like TWRP. From there, you can flash ROM's, radios and kernels (if you want to) via zip files, from an micro sd card.
**please let me know if I understand this process correctly**
The problem is, I can't find a single place online (searched on this site and on google for over an hour straight last night) that actually tells you specifically for my model I317M with 4.1.1 (if that matters, I'm not sure) HOW to unlock the bootloader. I've seen a lot of people asking and no answers.
If someone could please tell me exactly HOW to unlock the bootloader for my phone that'd be amazing.
Is flashing the bootloader done via odin? (there is an option in odin for it) If not, how do you flash a bootloader?
Jay26Canada said:
Hey guys. I'm very new and have spent the last few days researching about how the whole rooting, unlocking sim, unlocking bootloader, flashing radios and installing customer ROM's work.
From what I understand the process all start with having an unlocked bootloader so that you can install a recovery like TWRP. From there, you can flash ROM's, radios and kernels (if you want to) via zip files, from an micro sd card.
**please let me know if I understand this process correctly**
The problem is, I can't find a single place online (searched on this site and on google for over an hour straight last night) that actually tells you specifically for my model I317M with 4.1.1 (if that matters, I'm not sure) HOW to unlock the bootloader. I've seen a lot of people asking and no answers.
If someone could please tell me exactly HOW to unlock the bootloader for my phone that'd be amazing.
Is flashing the bootloader done via odin? (there is an option in odin for it) If not, how do you flash a bootloader?
Click to expand...
Click to collapse
You are lucky to have the device you do because the bootloader isn't locked! Some carriers lock the bootloader on some devices (it varies, like note 2 on at&t is unlocked but note 4 is locked). Some manufacturers even offer instructions or tools to unlock (ie htc offers Dev tools, on Google's nexus line it's a simple adb command "fastboot oem unlock").
Now for the i317, the procedure is simple. Gain root access with cf auto root (it's a tar.md5 file you flash with Odin. As a side note: Odin is a tool you will come to love because it can fix nearly anything you break. Just load the stock firmware for your device in Odin, flash and done. From there you can reroot or remain stock). Once you have root access after flashing cf auto root, have your custom recovery tar.md5 on hand to also flash in Odin.
So Odin, cf auto root, and recovery of your choice. (To flash the phone with Odin, the phone must be in download mode: vol-, home, power. Connect to computer and load up Odin)
Once you have flashed your root files and recovery, you can then enter recovery by holding vol+, home, and power, make a backup of your current stock setup, and then flash whatever rom you like as long as it's compatible with your device.
One more piece of advice: if you want to do anything like carrier unlock the device, I would do it now while you're on 4.1.1. In kitkat 4.4.2 and above some of the built in functionality of dialer codes and such were removed by Samsung... and people looking to carrier unlock who have already updated have to go through the tedious downgrade procedure to do so. Therefore, if that is something you are planning on needing at some point (or to just up the resale value of the device a bit), go ahead and root + recovery, then carrier unlock the device using dialer codes as specified in some of these threads. Then you can flash whatever you want and nothing can undo that unlock (mine is an att i317 on tmobile, so I highly recommend carrier unlock, you never know when you might need it!) Just do it before you move from 4.1.1 if you do want to do it
Good luck
absinthesummer said:
You are lucky to have the device you do because the bootloader isn't locked! Some carriers lock the bootloader on some devices (it varies, like note 2 on at&t is unlocked but note 4 is locked). Some manufacturers even offer instructions or tools to unlock (ie htc offers Dev tools, on Google's nexus line it's a simple adb command "fastboot oem unlock").
Now for the i317, the procedure is simple. Gain root access with cf auto root (it's a tar.md5 file you flash with Odin. As a side note: Odin is a tool you will come to love because it can fix nearly anything you break. Just load the stock firmware for your device in Odin, flash and done. From there you can reroot or remain stock). Once you have root access after flashing cf auto root, have your custom recovery tar.md5 on hand to also flash in Odin.
So Odin, cf auto root, and recovery of your choice. (To flash the phone with Odin, the phone must be in download mode: vol-, home, power. Connect to computer and load up Odin)
Once you have flashed your root files and recovery, you can then enter recovery by holding vol+, home, and power, make a backup of your current stock setup, and then flash whatever rom you like as long as it's compatible with your device.
One more piece of advice: if you want to do anything like carrier unlock the device, I would do it now while you're on 4.1.1. In kitkat 4.4.2 and above some of the built in functionality of dialer codes and such were removed by Samsung... and people looking to carrier unlock who have already updated have to go through the tedious downgrade procedure to do so. Therefore, if that is something you are planning on needing at some point (or to just up the resale value of the device a bit), go ahead and root + recovery, then carrier unlock the device using dialer codes as specified in some of these threads. Then you can flash whatever you want and nothing can undo that unlock (mine is an att i317 on tmobile, so I highly recommend carrier unlock, you never know when you might need it!) Just do it before you move from 4.1.1 if you do want to do it
Good luck
Click to expand...
Click to collapse
Wow! Thanks a lot for that detailed reply. I wasn't expecting that
I managed to get a recovery installed and working. I've tried two ROMs today and that was neat. ( I put them on the external sd card and flashed the .zip from recovery ). Now my main problem is, finding a ROM that actually works decently (any suggestions would be nice) and unlocking the sim.
Now, I was on 4.1.1. and when I was there, I followed these steps http://forum.xda-developers.com/showthread.php?t=2014982 and it seemed to have worked. It went just like the steps said it would.
Then, I actually went to a WIND mobile store today and asked if I could use a SIM to see if it would work with their network. It didn't (their network didn't show up on my phone )
I've since then tried that old method again but I am getting this error "connection problem or invalid mmi code" So I couldn't try doing that again.
Now I'm kinda stuck. I have been trying to find out if I can flash the radio with some firmware to fix it but I've had no luck finding anything.
I know this is a newish problem, but if you can guide me in the right direction or help me out I'd appreciate it. Otherwise, I might just have to buy a new phone.
Jay26Canada said:
Wow! Thanks a lot for that detailed reply. I wasn't expecting that
I managed to get a recovery installed and working. I've tried two ROMs today and that was neat. ( I put them on the external sd card and flashed the .zip from recovery ). Now my main problem is, finding a ROM that actually works decently (any suggestions would be nice) and unlocking the sim.
Now, I was on 4.1.1. and when I was there, I followed these steps http://forum.xda-developers.com/showthread.php?t=2014982 and it seemed to have worked. It went just like the steps said it would.
Then, I actually went to a WIND mobile store today and asked if I could use a SIM to see if it would work with their network. It didn't (their network didn't show up on my phone )
I've since then tried that old method again but I am getting this error "connection problem or invalid mmi code" So I couldn't try doing that again.
Now I'm kinda stuck. I have been trying to find out if I can flash the radio with some firmware to fix it but I've had no luck finding anything.
I know this is a newish problem, but if you can guide me in the right direction or help me out I'd appreciate it. Otherwise, I might just have to buy a new phone.
Click to expand...
Click to collapse
Im at work so I don't have a lot of time to explain, but the unlock probably worked fine. However, when you add a new Sim, you also have to program the access point name (or more commonly, APN). If you don't set the apn, the phone won't know which network to connect to. You may use a wind sim but if you still have the apn set for tmobile, it's gonna look for tmobile's network.
Apns can be configured under settings > more networks > mobile networks > access point names. You can have multiple apns programmed and switch between them as often as you switch sim cards. Search for wind apn and you'll figure it out (I keep a text file with lists of tmobile and at&t apns just in case.
Also you probably flashed a newer rom where Samsung/Google have removed the built in dialer codes, so you won't be able to use them anymore, but you can launch the codes you need using shortcut master (an app) where you can find the code you need and launch it fine with root permissions.
So I was on Oreo and accidentally flashed back to 7.1.
Didn't brick it but now it doesn't recognize my sim even after flashing back to Oreo.
I tried to fastboot the tmo baseband but no luck there.
Anyone run across this or have any suggestions?
That was one of the 1st thing I ran across in the Oreo update thread. With development just really getting fired up I'll be surprised if you find a fix. If. I was you I would flash the mod that hides the unlocked bootloader warning and take it to TMobile. It's only a 5 dollor charge for defective devices. I've returned a total brick before.
So I am on the same board. The problem is I'm in UK and I cant claim warranty repair. Also my warranty was void in December soon when I generated bootloader unlock key.
SO what have I tried so far?
Hard brick bootloader to state when it is Qualcomm loader- only blank flash and Oreo Flash All is able to bring it back to live.
Ive also tried boot from B slot in twrp but it looks like my B partition is messed up. Fastboot will show red warning about no flashable A/B slot and only oreo flash can get it back to boot because it will oem lock itself.
When I get back fully on unlocked bootloader to 7.1.1 I cant update via adb sideload or update menu in settings. Both will fail.
Sim looks like it is detected on start but when taken out and slided back in it wont show up.
I have QCN area backed up with nv data but it wont help me.
Please note when boot is bricked oreo flash all will flash it on locked bootloader and will not show warning screen at all about botloader. However I was unable to boot to recovery from that point so I had to unlock it and flash 7.1.1 then oreo again.
So if someone could do nandroid backup of clear not set up rom it would be great. I can try restore it. I dont even know if twrp is able to do backup on A/B device.
Also if someone could read NV data from phone and share it ( from phone with working radio of course) would be really appreciated.
Can someone PM me NV backup? I need urgently qcn file. I think my hw partition is messed up. Please don't share it in this post as it can contain IMEI.
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
byt3b0mb said:
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
Click to expand...
Click to collapse
Sorry but warning isn't clear. I did not enjoy Oreo and was looking for unlock method.
Also bootloader match to my current Oreo rom and radio but still no sim detected so I think it is hw partition messed up. When I flash retail Oreo on it bootloader just change itself to retail Oreo version. Still no sim.
Device is useable as paperweight with WiFi
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Everything about the phone works 100% except the Sim slot. It's like it can't read the Sim. It knows there is a sim in, but it can't access it.
On Oreo oem retail version.
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
robdevil said:
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
Click to expand...
Click to collapse
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Kaesberg said:
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Click to expand...
Click to collapse
pm sent. i could use this
Please let us know if it works
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
breakerfall said:
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
Click to expand...
Click to collapse
Where did you get this modem?
mattlowry said:
Where did you get this modem?
Click to expand...
Click to collapse
from the tmo oreo zip here (bottom of the OP):
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
it's the NON-HLOS file
this is the retail oreo:
https://forum.xda-developers.com/showpost.php?p=75250794&postcount=82
I swapped the NONHLOS file from the tmo oreo into the retail oreo and I currently have working tmo service/SIM on the retail (tmo-less) oreo
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
My Moto Z Play is bricked, after downgrade of oreo to nougat, my imei not work. so i decided go to oreo again, when i reboot my phone bricked. help me please!!!
Try this. Updated my Sprint only thread to be a little more universal.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
bricked moto z2 force tmobile
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
Hello,
I've been trying to find my answers on how to flash a AT&T GS9 SM-G960U with a T-Mobile S9 Stock Firmware\ROM.
I found this thread and although it's fairly close to what I am trying to do, I didn't want to post this there because they are talking about flashing U1 to U and I'm not sure if that is what I need to do exactly. https://forum.xda-developers.com/galaxy-s9/how-to/how-to-flash-u1-firmware-to-device-t3765200 from this thread, I've followed the initial steps and although Odin (Moded Odin v3.13.1 Raymonf ) tells me that the flash passed, upon reboot, the phone does not have the TMO firmware, it's still the original AT&T firmware. The only thing that it did do was add the TMO Visual VM icon\app.
I was informed of being able to download the TMO firmware from here: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html
Am I doing something wrong here? It seems that maybe these US models do not offer the OEM Bootloader unlocker option in developer settings unless you purchase the U1 version direct from Samsung that does not have a locked boot loader? I got this phone at no cost so that is also why I did not purchased from Samsung directly.
Any guidance and help would be appreciated.
Thank you
US carrier models have locked bootloaders, no way to root or install custom roms.
We should be able to flash between carrier versions/CSCs like we could with the S8, but the process is different and I've only read of a few people finding success in trying. The voicemail app you're seeing is due to flashing the T-Mobile userdata partition. This is the bloat partition - doesn't actually change device features, etc.
Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,
I've done it!
dovid said:
Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,
Click to expand...
Click to collapse
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here: https://androidfilehost.com/?w=files&flid=257063
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: https://devfiles.co/download/PDYvOWBg/platform-tools-latest-windows.zip. Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin: https://drive.google.com/file/d/10dSyPTuccP8Km9MnDrvbRdS-CAcgFZB3/view
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html
Switching from U -> U1 -> U
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.
dovid said:
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.
Click to expand...
Click to collapse
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.
ajairola said:
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.
Click to expand...
Click to collapse
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks
Savebig said:
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks
Click to expand...
Click to collapse
Go to this thread (thanks @iBowToAndroid) and then look in the RB7 folder on Android File host.
Question
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!
B AdamsHxC said:
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!
Click to expand...
Click to collapse
Have the same question, but on my Verizon Note 8...
PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
I would check if your phone is already unlocked, Most Verizon phones come unlocked (unless you bought them from a Verizon Tent at Cosco or stores like that) Just put in another carriers sim card and check, if it is unlocked then you shouldnt have to flash anything, once you put in a different carrier sim it will tell you to restart your phone and once you do it will come up with the new carriers splash logo and apps
PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
In my experience all the carrier S9s are locked. You will need an unlock code from your carrier or an unlocking service.
Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?
Xamuyees said:
Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?
Click to expand...
Click to collapse
Yes! All 965U's, 965U1's, and 965W's are the exact same hardware, just different firmware.
For those of you that use TMO or U1 firmware on an unlocked ATT phone on TMO network, do you get a <Subject: NoSubject> before other people's texts in group texts? I've tried flashing U and U1 firmware several times as well as factory reset without being able to get rid of the subject line. Anyone have any insight or suggestions?
I was able to go from U1 to the att firmware. My question is why does samsung pass not work? I can see that the knox is not tripped and google play store is certified. Device status says official. Device is not rooted but Samsung pass thinks it is rooted. Why would this happen when all I did was install the carrier bundle?
(Newbie) doing what jrockz3000 did would allow root to be possible?
MFmvrdoc said:
(Newbie) doing what jrockz3000 did would allow root to be possible?
Click to expand...
Click to collapse
Unfortunately not. All North American S9s are not able to be rooted at this point.
ajairola said:
Unfortunately not. All North American S9s are not able to be rooted at this point.
Click to expand...
Click to collapse
Thank you man~
Odin link down
jrockz3000 said:
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here:
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: . Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin:
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files:]
Click to expand...
Click to collapse
Odin link down.
Hi guys I got a Verizon N975U note 10 plus and its stuck on Verizon I'm trying to flash it with U1 so I can pop a sim in and changes it to that carrier. Do I just need to flash it with the U1 file here https://androidfilehost.com/?w=files&flid=297980 or will it need something special the build # is SQS2ASJ8
johntudd said:
Hi guys I got a Verizon N975U note 10 plus and its stuck on Verizon I'm trying to flash it with U1 so I can pop a sim in and changes it to that carrier. Do I just need to flash it with the U1 file here https://androidfilehost.com/?w=files&flid=297980 or will it need something special the build # is SQS2ASJ8
Click to expand...
Click to collapse
Can't say for sure it would work on U firmware (lack of first hand experience to verify) as it would for U1.... As long as the phone is network/sim unlocked then you should be able to just put the new sim card in it (and the phone will read the sim card settings and apply them).
Flashing the U1 firmware instructions on flashing U1 firmware have been at link below (bottom of first post). You can get the firmware from that thread also.
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
Of course keep in mind that none of this will matter unless the phone is sim/network unlocked. As long as you meet the requirements from Verizon (or the phone was blacklisted for either non payment, lost/stolen or a warranty/insurance exchange that wasn't sent in) then this shouldn't be an issue.
its locked to Verizon at the moment when I put a sim in it will work for a bit then say its not allowed to use another carriers sim at this time.
johntudd said:
its locked to Verizon at the moment when I put a sim in it will work for a bit then say its not allowed to use another carriers sim at this time.
Click to expand...
Click to collapse
Either wait until the phone is able to be unlocked by Verizon, or call them and request that they unlock it for you. Until that happens you will not be able to use a non-verizon sim card.
I would also advise keeping the U firmware for Verizon installed and not flashing the U1 firmware, as the Verizon sim/network unlock requires the carrier firmware... At least that is what I am gathering from various discussions/threads.
johntudd said:
Hi guys I got a Verizon N975U note 10 plus and its stuck on Verizon I'm trying to flash it with U1 so I can pop a sim in and changes it to that carrier. Do I just need to flash it with the U1 file here https://androidfilehost.com/?w=files&flid=297980 or will it need something special the build # is SQS2ASJ8
Click to expand...
Click to collapse
Is your phone carrier locked to Verizon? Has it been activated on Verizon's service for 30 days? If not, I'm pretty sure firmware flashing won't help anything. I'm on a Verizon MVNO and they wouldn't even unlock it for me to use on their own network. I had to activate with them for 30 days.
However, now that mine is unlocked, it's still locked down to Verizon in a lotof ways. My SIM card for my current carrier can't apply an APN, for example, so I have to do it manually. I'm contemplating flashing U1 to fix that issue (I hope).
I have a very similar situation. I bought a Note 10+ N975U (Verizon Unlocked) and I want to take it to U1 and then maybe to Sprint. I tried to go to the OP here and follow instructions. So I downloaded and selected all the files for U1 and apparently I did the "no-no" and got stopped with the SW Rev Check Fail : abl Fused 2 > Binary 1. I looked at what my phone is on and it is the SJ8 (November?) from Verizon. I'm guessing that means the BL file (bootloader?) in the U1 folder (SGO?) is older than what is on my phone? What do I need to do differently? I already tried without selecting the BL file, but it still gives the same error. Any help is appreciated! Thanks in advance!
baumanbt said:
I have a very similar situation. I bought a Note 10+ N975U (Verizon Unlocked) and I want to take it to U1 and then maybe to Sprint. I tried to go to the OP here and follow instructions. So I downloaded and selected all the files for U1 and apparently I did the "no-no" and got stopped with the SW Rev Check Fail : abl Fused 2 > Binary 1. I looked at what my phone is on and it is the SJ8 (November?) from Verizon. I'm guessing that means the BL file (bootloader?) in the U1 folder (SGO?) is older than what is on my phone? What do I need to do differently? I already tried without selecting the BL file, but it still gives the same error. Any help is appreciated! Thanks in advance!
Click to expand...
Click to collapse
The bootloader of the U1 firmware you were trying to flash is lower then what is currently on your phone. So yes you are correct that is the no-no. Also you can not skip the bootloader file when flashing, so that wouldn't have worked.
If you read through that thread you will have found others asking how to go from U to U1 firmware. Also the error within regards to trying to flash a lower bootloader version firmware was also asked and answered. I would encourage you to browse that thread and the Q&A forum because this process has been discussed on more then one occasion... It might contain helpful/useful info for you.
In short you need to get a newer firmware release. Using samfirm or frija apps, or the sammobile website look for the firmware your seeking. Google searching will show you how to obtain samfirm, frija is posted the forum here if I recall correctly.
For U1 the model is SM-N975U1 and the region is XAA.