Related
greetings,
I recently inherently a Samsung Note Edge (SCL24). The phone is showing its age. It is on its default rom (4.4.4) but many things aren't work. For example, it is extremely slow; it won't remember wifi passwords, etc. I am hoping that by flashing a new rom I may bring it back to life.
The spec is listed below:
SCL24
Adroid 4.4.4
Baseband: SCL24KDU1ANJ3
as I am browsing through this forum, I am a bit confused as to the flashing procedure. Assuming it is the same as every other phones I have flashed, I suppose I would need to root it, install a recovery, possibly a new basebank, and then a new rom.
Is there a guide as to how to do this for this particular phone? It has been a while
any help, and suggestion as to which rom to flash, would be very much appreciated.
ps. I am not looking for anything fancy, but in the past I've always used slim rom.
regards,
mikec_ca2 said:
greetings,
I recently inherently a Samsung Note Edge (SCL24). The phone is showing its age. It is on its default rom (4.4.4) but many things aren't work. For example, it is extremely slow; it won't remember wifi passwords, etc. I am hoping that by flashing a new rom I may bring it back to life.
The spec is listed below:
SCL24
Adroid 4.4.4
Baseband: SCL24KDU1ANJ3
as I am browsing through this forum, I am a bit confused as to the flashing procedure. Assuming it is the same as every other phones I have flashed, I suppose I would need to root it, install a recovery, possibly a new basebank, and then a new rom.
Is there a guide as to how to do this for this particular phone? It has been a while
any help, and suggestion as to which rom to flash, would be very much appreciated.
ps. I am not looking for anything fancy, but in the past I've always used slim rom.
regards,
Click to expand...
Click to collapse
Try a factory reset first.
done that many times
This phone was purchased in Hong Kong and other than the model number "SCL24" I couldn't find any other information. Judging from this forum, looks like there are many variations on this phone (vendors in North America, Japan, and others common in south asia). Also from this forum I realized that I probably need to update the baseband in order to flash any new ROMS (post kitkat).
Hence I seek your help,
regards,
The Radius Kid said:
Try a factory reset first.
Click to expand...
Click to collapse
mikec_ca2 said:
done that many times
This phone was purchased in Hong Kong and other than the model number "SCL24" I couldn't find any other information. Judging from this forum, looks like there are many variations on this phone (vendors in North America, Japan, and others common in south asia). Also from this forum I realized that I probably need to update the baseband in order to flash any new ROMS (post kitkat).
Hence I seek your help,
regards,
Click to expand...
Click to collapse
Interesting.
Is this an international phone?
I tried asking about custom ROMS for my phone (don't want brick it) and didn't receive any responses.
I did do a Google search and didn't find much of anything.
I did download Marshmallow from Sammobile and have been gutting pretty heavily.
I guess after this much time, interest is fading.
problem solved, for now
As I mentioned earlier, this phone was purchased in Hong Kong and the model number was listed as SCL24. Following the thread on Project_ECSTASY (https://forum.xda-developers.com/no...rojectecstasy-custom-rom-galaxy-note-t3545658), I managed to flash the "Global edition stock rom without any bloatware from carrier au" using odin. The step I followed was:
1) installed samsung USB drivers for the phone (directly from samsung website),
2) downloaded and executed Odin,
3) rebooted the phone into Odin mode (vol down, home, and power),
4) connected the phone to computer via USB,
5) updated the rom through Odin.
6) once the phone rebooted, factory reset
I have not had much opportunity to play with the phone but it seemed to be working thus far. I have not had a chance to put a SIM card into it so I don't know if the new rom/Odin also flashed a new baseband and if the radio works.
will report back tonight,
mikec_ca2 said:
problem solved, for now
As I mentioned earlier, this phone was purchased in Hong Kong and the model number was listed as SCL24. Following the thread on Project_ECSTASY (https://forum.xda-developers.com/no...jectecstasy-custom-rom-galaxy-note-t3545658), I managed to flash the "Global edition stock rom without any bloatware from carrier au" using odin. The step I followed was:
1) installed samsung USB drivers for the phone (directly from samsung website),
2) downloaded and executed Odin,
3) rebooted the phone into Odin mode (vol down, home, and power),
4) connected the phone to computer via USB,
5) updated the rom through Odin.
6) once the phone rebooted, factory reset
I have not had much opportunity to play with the phone but it seemed to be working thus far. I have not had a chance to put a SIM card into it so I don't know if the new rom/Odin also flashed a new baseband and if the radio works.
will report back tonight,
Click to expand...
Click to collapse
Cool.
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
SIGMAxB said:
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
Click to expand...
Click to collapse
Won't flash on T-Mobile - it expects AT&T firmware (SM-G930A) - not anything else. I tried it (SM-G930T) and got error 7 in second stage with that exact reference (expected SM-G930A; got SM-G930T). This would have to be edited to take that second-stage reference out to work.)
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Death Cookie Firmware in Non-DeathStar Phones - Yes; However
SIGMAxB said:
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Click to expand...
Click to collapse
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
PGHammer said:
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
Click to expand...
Click to collapse
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
SIGMAxB said:
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
Click to expand...
Click to collapse
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Beginning of Round Two - CRB6
PGHammer said:
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Click to expand...
Click to collapse
I reset the phone, and kicked off testing of CRB6, and I did one thing differently; I left the SIM in the phone. I had a purpose for that - I was looking for bugbears that apply to non-AT&T carriers (T-Mobile, VZW, Sprint, et. al.) Amusingly, there aren't any. I did the flush (U Firmware version of BRA1) then applied the AT&T version of BQL1 (back-to-back via ODIN). Then came the ADB via SD card single-file updates (recovery mode for these) and there are only two - BQL1 to BRA1 (from Round One) and the new CRB6 update (courtesy of Samsung Firmware Science) labeled update_2.zip. It replaces update.zip, and is not opened or extracted - apply it as-is. After this update applies, follow the new-customer steps as you did for Round One - no changes here.
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
bkup said:
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
Click to expand...
Click to collapse
Can I get a copy please
Why I Did It The Way I Did
SIGMAxB said:
Can I get a copy please
Click to expand...
Click to collapse
When someone gets a proper copy, link it to the thread - the very reason I did NOT do it that way was because a proper copy of AT&T BRA1 didn't exist. (You can't get it from SamMobile or UPDATO either - much to my frustration; the latest ODINable AT&T firmware was BQL1.)
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
ecc25 said:
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
Click to expand...
Click to collapse
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
cooltt said:
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
Click to expand...
Click to collapse
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
ecc25 said:
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
Click to expand...
Click to collapse
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
cooltt said:
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
Click to expand...
Click to collapse
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
ecc25 said:
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
Click to expand...
Click to collapse
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
cooltt said:
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
Click to expand...
Click to collapse
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
ecc25 said:
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
cooltt said:
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
Click to expand...
Click to collapse
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
ecc25 said:
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
Click to expand...
Click to collapse
Well you could flash G930U which opens up all of the radios for the US and you may have less issues but US and European devices have different chips so your never going to be able to flash any EU generic firmware. I'm addition the US and Europe are different cellular regions with different operating frequencies. You can get by with what you have but never get full functionality.
I think you were just unlucky with this phone on ebay, there are plenty which are genuine EU region devices.
I Present The Galaxy A71_5G Guide for Flashing Unlocked Firmware.
Here are some useful reminders:
All download links are at the bottom of this post.
Make sure you follow the "Prerequisites For Anything You decide To Do In This Guide" section.
Don't copy quotation marks, unless I tell you to in this guide.
You will need a Windows computer in order to utilize the software provided.
This is an A71_5G guide, not an A71_5GUW guide.
WARNING: Anything you do in this guide will erase your phone completely. It's recommended that you back up before you do anything and that you remove your google account from your phone (so you don't have to go through FRP).
Disclaimer:
I am NOT responsible for any damage done to your device if you decide to use this guide.
Prerequisites for anything you decide to do in this guide (Required):
Standard Odin
Samsung Drivers
Steps:
1) Uninstall Samsung Switch and/or Samsung Kies, if present on your computer. This helps removes any conflicts with Odin.
2) Extract the Samsung Driver zip and the Odin zip to somewhere safe on your computer.
3) Double click on the extracted "SAMSUNG_USB_Driver_for_Mobile_Phones" executable (SAMSUNG_USB_Driver_for_Mobile_Phones.exe) and complete the installation wizard.
3) Navigate to your extracted Odin folder and double click on the Odin3 v3.14.1_3B_PatcheD.exe.
All About Bootloaders (Required Reading):
As Wikipedia puts it, “A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests.” In other words, a bootloader is what loads you operating system. In most Samsung phones (including the S8 and S8+), there’s an e-fuse that prevents downgrading of the bootloader. This means any firmware or firmware update containing a lower Bootloader version than the one you have, will FAIL to be applied. There is really no way to circumvent this.
I’ll be explaining how to properly identify your current Bootloader version.
How to identify Bootloader version:
Steps:
1) Open “Settings” on your phone.
2) Scroll down to “About Phone”.
3a) If you are on a standard, carrier firmware, under “Baseband version” you should see something similar to this: “G950UXXXXXXXX”.
3b) If you are on an unlocked firmware, under “Baseband version” you should see something similar to this: “G950U1XXXXXXXX”.
4) No matter which firmware you're on, the fourth “X” would be either a “1” or a “2”, which means you will have either Bootloader version 1 or Bootloader version 2, respectively.
Note: As stated in the last section attempting to flash firmware that contains Bootloader v1 onto a phone that already has Bootloader v2, will fail. You can update a phone on Bootloader v1 to a firmware that has Bootloader v2, however.
Flashing Unlocked Firmware:
NOTE: The unlocked firmware does NOT unlock your phone for use on other carriers, it only removes bloatware. Some carrier specific features, such as Wi-Fi Calling and VOLTE will not work with the Unlocked Firmware.
Prerequisites: What's listed in the "Prerequisites for anything you decide to do in this guide" section
Odin3 v3.14.1_3B_PatcheD.exe.zip
Unlocked Firmware from site listed below.
Steps:
1) Extract the Odin3 v3.14.1_3B_PatcheD.exe and the Unlocked Firmware you downloaded from below.
2) Turn off your A71_5G.
3) Once off, hold the Power button while holding the Volume Down button, and the Volume Up button until you feel a vibration then let go of the power button.
4) Press the Volume Up key to enter Download Mode.
5) On your PC, navigate to your extracted Odin3 v3.14.1_3B_PatcheD.exe folder.
6) Double click on the "Odin3 v3.14.1_3B_PatcheD.exe" executable.
7) Connect your phone to your PC with your USB cable.
8) You should see Odin3 v3.14.1_3B_PatcheD output "Added!!" in the "Log" tab and underneath the "ID:COM" section, you should see an empty box turn blue.
9) Now it's time to add your firmware files that were extracted earlier. Individually add an appropriate firmware file for each box on the right. The "BL" box will require a firmware file that starts with "BL", the "AP" box will require a firmware file that starts with "AP", the "CP" box will require a firmware file that starts with "CP", and the "CSC" box will require a firmware file that starts with "CSC" (DO NOT USE THE "HOME_CSC" file for the "CSC" box).
10) Go to the "Options" tab and make sure that only the "Auto Reboot" and "F. Reset Time" checkboxes are ticked.
11) Go back to the "Log" tab.
12) Click the "Start" button on bottom right.
13) Sit back and relax for a while. Odin will output what is being flashed in the "Log" and on a box in the top left.
14) The box in the top left will become green and in black letters say "PASS" once the flash was successful.
15) Once the flash finished, disconnect your phone from your computer.
16) Your phone will do an erase at this point, so don't mess with your phone until you reach the setup screen.
17) Continue with the setup on your phone and enjoy!
DOWNLOADS:
Standard Odin/Patched Odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Samsung Drivers: http://developer.samsung.com/galaxy/...er-for-windows
Google Platform-Tools (ADB): https://developer.android.com/studio/releases/platform-tools
Unlocked Firmware (Bootloader v1): https://samfw.com/firmware/SM-A716U1/XAA
CREDITS
Credit goes to each respective site/developer for the tools required to complete this.
If you would like to be added to the credits and are one of the developers or owners of the tools used please feel free to Private Messege Me!!!
This Will Be Updated To The Latest Firmware When The U1 Varient Gets Updates
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
cubano2031 said:
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
Click to expand...
Click to collapse
you should be able to find it using sammobile.com or frija https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
andrewNY said:
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
Click to expand...
Click to collapse
5G works just fine. pretty much everything works minus the chat features in samsung messages.
---------- Post added at 11:03 PM ---------- Previous post was at 10:49 PM ----------
SmileyMorgue said:
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
Click to expand...
Click to collapse
That's great to hear! I look forward to the patch. Yes, from the digging I did, chat features were not included in the XAA version, but they were working when I was using TMB before switching.
Update to ATH3 Available on phone still a U1 Bootloader.
For those that wish to download full firmware here is the link to it https://samfw.com/firmware/SM-A716U1/XAA/A716U1UEU1ATH3
allenjthomsen said:
Update to ATH3 Available on phone still a U1 Bootloader.
Click to expand...
Click to collapse
Wow, build date was only 2 weeks prior to release. Recently came from a Moto Z4 where we were lucky to have 6 month old security updates.
Unfortunately still can't get the chat feature working; maybe it'll take some time to register the update.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
If its like previous Samsung phones, you'll need to be on the carrier specific firmware to run the unlock. Once unlocked you can flash back to the unbranded/unlocked firmware.
Anyone tired these firmwares with AT&T
so there is no unlocked version firmware for bootloader V2 right now?
Is anyone else able to access the firmware file on the link? It mentions something about the download under construction.
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
No unlock needed
foamhead said:
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
Click to expand...
Click to collapse
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Rwmega said:
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Click to expand...
Click to collapse
Thanks for the reply. I added another APN. Your right cant delete the defaults ones. Im with sprint was trying to do the ,dun to get my hotspot to work. I have it on 3 other phones.
I have a Sprint version.
If I flash the T-Mobile software will it open up all of the T mobile bands?
It could already have them, but have not been able to find specific s on the bands on the sprint version of the phone to see.
Phone looks to be manufactured before the merger?
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
I haven't sim unlocked the phone yet since it's not paid off so couldn't tell u if I can still access that feature.
I turned off and then restarted the developer's mode in my S7 yesterday. When I went to turn it on today, I got the message "Custom binary blocked by FRP Lock. I used power / start / vol down holding all three and came to a screen that wanted to know if I wanted to download (probably Odin). I then pushed two buttons of which one was the start button (the one in the middle of the bottom) and the vol up button, which started the phone trying to download. It got the message Downloading "Do not turn off target". I figured out how to stop that, but when the phone rebooted, it was back to "Custom binary Blocked ..."
The information I need to download firmware (like the CSC), is either in my phone or not common enough to exist in the country lists with their respective phone companies. My phone is an S7 and probably a G930F, although I can't verify that because I can't get into the phone. I would not mind downloading Odin, but I understand that the information regarding CSC_home with regard to who my provider is and what country I'm in is necessary in order to install Odin and I don't know how to find that information or to find the complete model number for the phone.
Thank you for any advice you can give me. I would prefer not to have to use a factory reset on the phone to get it up and running again.
Changing OEM Lock does trigger FRP sometimes, like 2 years ago my friend had the same on his Note5, it wasn't that hard to solve.
You need to verify your device model (written in the download mode's top left corner), then download a recent firmware, flash it via Odin, after booting, it'll ask you about your Google account and in some cases, your Samsung account, too.
Unless you've forgotten them, you should be good.
Mohamedkam000 said:
Changing OEM Lock does trigger FRP sometimes, like 2 years ago my friend had the same on his Note5, it wasn't that hard to solve.
You need to verify your device model (written in the download mode's top left corner), then download a recent firmware, flash it via Odin, after booting, it'll ask you about your Google account and in some cases, your Samsung account, too.
Unless you've forgotten them, you should be good.
Click to expand...
Click to collapse
Thanks very much. I got the info off the download screen.
Do you mean I should go ahead and download Odin and then hope to find the right firmware? That's giving me part of the problem. I downloaded two different versions of Odin
3_v3.11.1
3_v3.12.3
I think to get the right firmware, I would need to know the country 3-letter code, if the phone is dual sim or not and the service provider? Since my service provider is not among those listed (like telekom or O2), can I use "unbranded" for my country? Or is this information for the CSC entry something my provider could provide?
Also, if I enter that into CSC, will I still have the option for Home_CSC? I'm quite interested in trying to keep my data.
And finally, I don't think I set up any account which had to do with the cloud. If an account was needed to verify the operating system, then I hope to be able to figure out what that was.
nidozu said:
Thanks very much. I got the info off the download screen.
Do you mean I should go ahead and download Odin and then hope to find the right firmware? That's giving me part of the problem. I downloaded two different versions of Odin
3_v3.11.1
3_v3.12.3
I think to get the right firmware, I would need to know the country 3-letter code, if the phone is dual sim or not and the service provider? Since my service provider is not among those listed (like telekom or O2), can I use "unbranded" for my country? Or is this information for the CSC entry something my provider could provide?
Also, if I enter that into CSC, will I still have the option for Home_CSC? I'm quite interested in trying to keep my data.
And finally, I don't think I set up any account which had to do with the cloud. If an account was needed to verify the operating system, then I hope to be able to figure out what that was.
Click to expand...
Click to collapse
It doesn't matter. Any firmware will get your phone booting, that's the point, if it was FRP cause you forgot the Google account, then perhaps you should be picky, but since you're not, then it's fine.
CSC gets activated when the phone detects your SIM card, that's how it knows where you are and that's how it sets CSC features provided for your region. If you pulled the SIM out, it won't apply CSC just yet. If you travelled to another country, your CSC will be changed (once you boot into recovery).
What model your phone has, so I can find you some files?
Mohamedkam000 said:
It doesn't matter. Any firmware will get your phone booting, that's the point, if it was FRP cause you forgot the Google account, then perhaps you should be picky, but since you're not, then it's fine.
CSC gets activated when the phone detects your SIM card, that's how it knows where you are and that's how it sets CSC features provided for your region. If you pulled the SIM out, it won't apply CSC just yet. If you travelled to another country, your CSC will be changed (once you boot into recovery).
What model your phone has, so I can find you some files?
Click to expand...
Click to collapse
I'm making some progress. I learned you can get the model number off of the recovery screen which I got to with power / vol up / Home and by waiting for the Recovery screen to appear.
I then found a very close firmware in updato, but the last letter was a y instead of a c, so not the perfect model-number-match. That one with the wrong last letter was for my region in the EU. The actual matching firmware ends with a c and I found that firmware on multiple websites, but listed as being from Thailand.
Now, the strange thing is that I bought the phone in Germany for a trip to Thailand and got it unlocked before I went there. Since I'm in Germany and most likely Telekom, and since I've read to trust no website except Updato, which doesn't have the firmware for my exact model number, I've been wondering how to proceed?
You asked for my model numberOne of the non-Updato websites offers the firmware with a checksum with the file, but since updato doesn't have that firmware file, I couldn't know if the checksum was the right one.
So I think what you asked for was the model which is G930FXXU1DQHC
Thanks very much.
nidozu said:
So I think what you asked for was the model which is G930FXXU1DQHC
Thanks very much.
Click to expand...
Click to collapse
That's a very old firmware, it has U1, latest has U8, I had the same device, too.
A trusted, reliable site would be AFH, search for G930F and find large files, that's the firmware.
Hi,
I found the big file of 1.8 gb called G930FXXU1DQHC_DevBase_v4.3.zip and downloaded it and extracted it to a folder I created myself called odin. It's not what I was expecting. It is a whole lot of folders within folders within folders, but none of the files that I would expect to be able to click on for an installation by odin. I was actually expecting three files that were clickable, which I've seen in instructions that utilize Odin to flash the firmware.
The two main folders it produced were ALEXNDR and META-INF. There's a single file at the same level as these two folders called options.prop.
Edit, I will try to attach a screen shot of what I was expecting to get.
More Edit: I'm not finding an installation file, so I think I'm at the point where I need to install Odin, but I don't know whether I install it on my pc or on my phone and if I should install that before I install the firmware. That's the point, isn't it? That Odin is in place to install the firmware?
Also, I can't see any exe files in the zip file I extracted, so I don't know what could be installed.
What is it I should be looking for?
Thank you. You're helping me keep going.
I see you did not get what U1 and U8 means. For an example, this is the latest firmware for Galaxy S7.
But, you downloaded a U1 firmware, which is very old to be believed. Forget about that, download this one, extract it, and flash it via Odin.
Thank you for that information.
The short version: I'm back in! All the stuff below is my journey which was rocky. Had to do some more internet searches, which brought me to another thread here in the forum:
Can't flash firmware, RQT Closed.
Hi! I need help, I was trying to flash Indian firmware (latest) on my Note8 (N950FD) with french rom. But when tried to flash the rom with Odin, start the procces and less than a minute, finished and appears as success, but nothing happened...
forum.xda-developers.com
For others who come after me:
I downloaded the firmware files, started Odin, put the phone in download mode (power / vol down / home), then plugged the phone into the computer and clicked on the boxes one at a time in Odin and was directed to firmware files in Windows Explorer and clicked on the correct one. I wanted to save my data so in the box called Userdata, I entered the CSC_Home file. They were all accepted. Then I clicked on Start in Odin and after a short time, the scrolling of files on the left side ended. That's where the above link comes in which says to try using a more recent Odin, so I tried again with Odin 3.13.1 (with the Chinese figures).
This attempt went better, took longer and then my phone sat and blinked Samsung at me for a very long time. I finally turned Odin off with Exit and then waited some more while the phone was still plugged into the computer. Then it started installing what it had downloaded. At least by now the little Android robot wasn't keeling over anymore.
After that finished, it asked for my pin and accepted it and I got back to the home screen. It then asked if this was my phone number, which it was. And I could see! that it had a charge of 44%.
I then went into Settings and looked for the developers setting and found that OEM was indeed turned off and that probably caused the FRP lock to occur. I turned the developers setting off for now.
I was able to keep my data with one annoyance. Some of the less standard apps are giving me a pop-up when I open them that says the apps are always on, do I want to close them, and there's a feedback button which simply shuts the popup off. You have to keep turning this off. It seems to affect non-standard apps, so I may have to reinstall those. I'll look into that ... tomorrow.
Many many thanks! It was so great to find someone who knew how to help me! I really appreciate it.