Good Morning Guys
After a lot of struggle I decided to post me and my friends problem here, I know on XDA Developers there are a lot of clever guys who might help us to solve this problem. Please note that I have a Galaxy S3 which is rooted and loaded with Custom ROM WanamLite Rom, so I am familiar with the process on how to do this and we have tried all options to fix the OS on this Galaxy S4 i9505 of my friend. Here are the details:
We are from South Africa and when overseas my friend bought a Galaxy S4 i9505 in Bangkok, he had the option between the clone and an Original, so he bought the ORIGINAL rather than the clone. Now once he got back to SA he started using the phone which wasn't network locked but we noticed that the OS version was a bit funny and that the phone was already rooted out of the BOX (Strange) so we thought he bought a clone and followed all the links on the the net showing how to determine weather its a clone or not. So we came to the solution that his phone is NOT a clone but it has a weird OS on it that we cant change/load another OS on. Here is what we tried:
1) We wanted to load a new OS or Custom ROM since the phone was already rooted, so we first tried to download the stock firmware from SAMMOBILE for South Africa and copied it to the Ext SDcard and rebooted the phone in Recovery mode. There we didn't have any option to install OS/ZIP from Ext SDcard ..... Not even under advanced. There is NO Mounts & Storage nothing, it just doesn't display any External Storage options. So this made us go to step 2
2) We thought okay lets try at least and load another custom ROM since its already rooted and see if we can fix the problem the other way around. So we installed Odin on PC and connected phone in download mode to install CWM recovery, ODIN pics up the device as "Unknown" and the port in ODIN doesn't become green. We have installed/uninstalled various S4 USB Drivers and when the phone is connected to Windows 7 PC is shows Unknown Device ...... You can access the phone Sdcard & ExtSDcard through Windows although its shows Unknown Device, but when rebooting in recovery mode it doesnt see the Ext SDcard - WTF?
This is where we gave up and decided to see if any of you guys can help or have any ideas to fix this and get a proper OS working on it ...... Cause I suspect that whatever OS is on the phone wont even receive OS updates and we want to be able to update the OS/Custom ROM for new OS versions like Android v5 thats on the way. Help would be appreciated guys
Take care
So I was trying to root my Verizon S8 in an attempt to get the mobile hotspot working since I am grandfathered in on the unlimited data plan. So while rooting it I soft bricked it. I then had to wipe the phone, cache and get into download mode. I went to sanmobile.com to get a working software version so I could use the phone. After I uploaded the sanmobile software to my phone, I tried to use the mobile hotspot. And it worked. This version basically unlocked the phone, took away the Verizon bloatware and their b.s.. very happy I tried to root my phone and found this, now I have total control of MY phone.
deleted.
nastybyz1 said:
So I was trying to root my Verizon S8 in an attempt to get the mobile hotspot working since I am grandfathered in on the unlimited data plan. So while rooting it I soft bricked it. I then had to wipe the phone, cache and get into download mode. I went to sanmobile.com to get a working software version so I could use the phone. After I uploaded the sanmobile software to my phone, I tried to use the mobile hotspot. And it worked. This version basically unlocked the phone, took away the Verizon bloatware and their b.s.. very happy I tried to root my phone and found this, now I have total control of MY phone.
Click to expand...
Click to collapse
So what version did you put on your phone? link to the version on sanmobile and proof would be great..
I went to sammobile dot com/firmwares/galaxy-s8/SM-G950U/ and down loaded the firmware and used ODIN to flash it. I'm not sure how to upload the pics but under the about phone it is showing that is a model SM_G950U1,
Running Android 7.0,
Baseband version [email protected],
Build number of NRD90M.G950U1UES2AQL1,
SE for android status: Enforcing
I had originally tried to use the Rootjunky root process from his youtube video but half way through it soft bricked the phone (I guess because it was for T-Mobile). I then had to figure out a way to undo the soft brick it and I was able to get into download mode and I then found Sammobile and downloaded the Verzion software. Once the phone booted up there was NO Verizon blotware. The only problem that I found is that I have to use a third party Visual Voice Mail since Verizon will not load onto the phone or you can use the old school *86 method. If you want screen shots Direct message me with an email and I can send verification pics. Hope this helps.
nastybyz1 said:
I went to sammobile dot com/firmwares/galaxy-s8/SM-G950U/ and down loaded the firmware and used ODIN to flash it. I'm not sure how to upload the pics but under the about phone it is showing that is a model SM_G950U1,
Running Android 7.0,
Baseband version [email protected],
Build number of NRD90M.G950U1UES2AQL1,
SE for android status: Enforcing
I had originally tried to use the Rootjunky root process from his youtube video but half way through it soft bricked the phone (I guess because it was for T-Mobile). I then had to figure out a way to undo the soft brick it and I was able to get into download mode and I then found Sammobile and downloaded the Verzion software. Once the phone booted up there was NO Verizon blotware. The only problem that I found is that I have to use a third party Visual Voice Mail since Verizon will not load onto the phone or you can use the old school *86 method. If you want screen shots Direct message me with an email and I can send verification pics. Hope this helps.
Click to expand...
Click to collapse
OK. Thank you. i am downloading the g955u and the g955u1. I am pretty sure Verizon did not sell the U1 version so i don't know if it will work on mine to be to root and get the hotspot working.
Does this also open up the LTE bands that are normally locked down by Verizon for the phone to work better on AT&T and T Mobile? Namely 12, 17, and 30?
Hi,
I just bought the A90 5G, I have followed tutorials and unlocked the bootloader & enabled developer options & USB debugging, I have installed Magisk Manager and patched the AP file, flashed with Odin 3.14.1 however when trying to reboot I get a screen saying "this phone is not running Samsung official software.You may have problems with features or security,and you won't be able to install software updates."
The phone will not boot to anything but this screen.
Please can anyone advise how to get beyond this message and root the phone so that it will boot correctly.
I was trying the canary debug manager.
I have flashed the standard rom meanwhile to use the phone.
Thank you for any assistance
Phil
Mine is SM-A9080 (China Version)
Mine is worse.
The model I've had is SM-A9080, China version.
I did the root with the same instructions (for multiple times), but failed, having a worse case that the phone had got boot loop!
I need the root very much since I need to full backup via Titanium Backup.
The possibility is that this China-version model is too new.
Thus, the phone expert(s) has/have to develop a specific TWRP for this model, or all models of Galaxy A90 5G.
However, this must take so long a time!
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?
I'm not at all experienced with Android or mobile devices in general, and I have an old T813 WiFi (2016) that I needed to root.
I flashed twrp-3.5.0_9-0-gts210vewifi and that worked fine. Except, TWRP couldn't see the download directory where I dropped the magisk zip. I didn't seem to see any internal storage besides the root FS (tab has 60 gig and no sd card).
So on the advice of the internet, I used TWRP to wipe and reformat, resulting in not being able to boot. It gets stuck at the pulsing Samsung logo forever.
I did a factory reset with TWRP and no change.
I then tried to flash stock 6.x firmware using Odin but it failed with an Auth error, I believe due to the device not permitting "downrgades".
So then I used Odin to flash the closest thing to a stock 7.0 ROM that I could find, which was T813XXS2BSJ3_T813XAR2BSA2_XAR from www.sammobile.com. That flashed successfully, the tab rebooted to the stock recovery and loaded the new image, but on the next reboot we were back to same old pulsing Samsung. I left it for a couple of hours, then tried rebooting again, but no change.
I hope it's just that that firmware was for the cell version of the tab, an. d I need the WiFi version. If anyone knows where I can find the right 7.0 firmware for the SM-T813 (2016) it would be greatly appreciated.
I would also welcome any other advice for dealing with this thing.
I'm from the US, and I still have boxes for 3 of my 4 T813s. The part numbers all end in XAR. That being said I went through my filers, and the last ODIN file I used was a XAC file. Looking at Sammobile, just looks like XAC is Canada, XAR is celluar south.
I'm assuming if TWRP couldn't see the directory, you had an encryption issue.
I know I'm still running Akipe's beta TWRP, found in this post. I know it's an "older" version, but I've never upgraded as it had a bunch of fixes that the official one didn't have. Not sure if that ever got corrected or not at this point. That's a question I will ask actually.
OhioYJ,
I have the WiFi version, so it has no sim and no LTE radio, I assume. I'm pretty sure the XAR file is for cellular tabs. I did try it, and it did flash OK via Odin, but it wouldn't boot.
I couldn't find the stock 7.0 version for WiFi anywhere, so I ended up flashing Lineage instead. The tab works now, rooted, so all is well.
I also used the modified TWRP version linked on the Lineage site, which allows MTP in recovery mode so I could dump files where TWRP could find them.
I do wish I could find the stock ROM for the WiFi tab, just in case.
bascc said:
I have the WiFi version, so it has no sim and no LTE radio, I assume. I'm pretty sure the XAR file is for cellular tabs. I did try it, and it did flash OK via Odin, but it wouldn't boot.
Click to expand...
Click to collapse
All the T813s in my house are wifi too, no LTE. Those boxes end in XAR, it's like that even on my newer Tab S5e. So I don't think cellular south necessarily refers to LTE. That being said, the one I have saved on my PC is XAC (Canada), and there are still plenty of XAC firmware files that site.
Either way glad you got it working.