Related
Hi Guys,
I got a Samsung S2 from Hong Kong, upon upgrading to the latest stock firmware (ice-cream) via Kies, my swype have lost many languages
I got a new Swype automatically from updating the firmware, but then I do not see the list of languages, for example, I need to type German, but I dont see it anymore, and there are no options for downloading.
Swyper verison = 3.26.92.37724.8882.GT_I9108
Phone Firmware = [email protected] #3
Android Versio = 4.0.3
Is there anyway I can uninstall this pre-installed version from stock firmware, and get the latest beta somewhere?
Edit: You can follow the solution of @ashyx through the following link to fix the problem can not flash twrp or boot via Odin. I think it will work
Link: https://forum.xda-developers.com/sa...g-sm-a520f-2017-kernel-source-t3557622/page31
Hello everyone,
After I updated the latest firmware, I was unable to flash BOOT or TWRP via Odin. It just returned the result that ONLY OFFICIAL BINARIES ARE ALLOWED TO BE FLASHED (RECOVERY / BOOT). I think samsung locked the bootloader. Today, I have found a way to fix this problem because knox 0x1 but can not root is not pleasant at all!
I only tested on my A520F, not tested on any other device. I am not responsible for any errors on your device.
1. Go to http://updato.com and download 2 firmware updates with your CSC.
+ Latest firmware 7.0 (November security).
+ Latest firmware 6.0 (MM).
2. Backup your important data
3. Reboot to download mode.
4. Add AP, CP, CSC of firmware 7.0 (November security) to the corresponding slot in Odin.
5. Add BL file of lastest firmware 6.0 (MM) to BL slot in Odin.
6. Start and wait a moment.
7. Setup and after that, you can flash TWRP or BOOT via Odin without bootloader errors.
Enjoy!
Sorry for my english...
Original info from this thread maybe?
https://forum.xda-developers.com/sa...g-sm-a520f-2017-kernel-source-t3557622/page31
.
Hi ahyx, i searched google about not being able to flash twrp or boot after security update in November and know the information is that maybe samsung has locked the bootloader. So, I just tried replacing the BL file of the old firmware that I saved on my laptop and it worked. I do not notice that you have found the solution first. Sorry for it as an act of plagiarism. I will link to your topic as a good faith (sorry for my english)
Oh man, thank you very much !! helped me here too! I had my a5 17 with this 'softbrick' but thank God I was able to install twrp, and so doing root haha I just can not downgrade to the MM.
this one are 100% work?
i need to download lates MM version and lates Nougat version? then i flash only BL of MM and CP,CSC and AP of nougat version? tia
kobejor said:
i need to download lates MM version and lates Nougat version? then i flash only BL of MM and CP,CSC and AP of nougat version? tia
Click to expand...
Click to collapse
Vou need to download the latest Nougat 7.0 firmware (A520FXXU2BQK4) and fw plus MarshMallow 6.0.1 (A520FXXU2AQG4).
I, as a Brazilian, downloaded the fw of Brazil.
And then in AP, CP and CSC you put the respective AP, CP and CSC files of the Nougat rom
and in BL the Marshmallow rom file.
It works, man!
At first I had some problems, the smart was out of system because before finishing the process I got some errors (old usb port, bad contact, etc.). Try to keep all the smart USB drivers on your PC, turn on the debug and also the OEM mode and restore your a5. Today I have been able to downgrade and I am using the stock rom 6.0.1
guys can someone please upload MM boot loader so we don't have to download the ROM completely (approx 2.1 GO )
THANKS GUYS
When i try to flash it says: SW REV CHECK FAIL DEVICE 2 BINARY 1
T-Rex said:
guys can someone please upload MM boot loader so we don't have to download the ROM completely (approx 2.1 GO )
THANKS GUYS
Click to expand...
Click to collapse
http://www.mediafire.com/file/8173e...911830_QB14224310_REV00_user_low_ship.tar.md5
BL MM (6.0.1) - From ZTO Brazil
caiquess95 said:
Vou need to download the latest Nougat 7.0 firmware (A520FXXU2BQK4) and fw plus MarshMallow 6.0.1 (A520FXXU2AQG4).
I, as a Brazilian, downloaded the fw of Brazil.
And then in AP, CP and CSC you put the respective AP, CP and CSC files of the Nougat rom
and in BL the Marshmallow rom file.
It works, man!
At first I had some problems, the smart was out of system because before finishing the process I got some errors (old usb port, bad contact, etc.). Try to keep all the smart USB drivers on your PC, turn on the debug and also the OEM mode and restore your a5. Today I have been able to downgrade and I am using the stock rom 6.0.1
Click to expand...
Click to collapse
I'm also Brazilian, and it worked for me! Thank you!
It turned out people were stuck with my A7 2017 using the rom of India nougat, I could not install nor the recovery much less to do the root, with your help here I got I'm from Brazil, I just installed via odin the file BL zto android 6, I entered the download mode and installed recovery and did the root, now only joy.
Download ROM quickly in Android Duniya site.
same problem hahaha, now it's root after the December patch
thangluong said:
Edit: You can follow the solution of @ashyx through the following link to fix the problem can not flash twrp or boot via Odin. I think it will work
Link: https://forum.xda-developers.com/sa...g-sm-a520f-2017-kernel-source-t3557622/page31
Hello everyone,
After I updated the latest firmware, I was unable to flash BOOT or TWRP via Odin. It just returned the result that ONLY OFFICIAL BINARIES ARE ALLOWED TO BE FLASHED (RECOVERY / BOOT). I think samsung locked the bootloader. Today, I have found a way to fix this problem because knox 0x1 but can not root is not pleasant at all!
I only tested on my A520F, not tested on any other device. I am not responsible for any errors on your device.
1. Go to http://updato.com and download 2 firmware updates with your CSC.
+ Latest firmware 7.0 (November security).
+ Latest firmware 6.0 (MM).
2. Backup your important data
3. Reboot to download mode.
4. Add AP, CP, CSC of firmware 7.0 (November security) to the corresponding slot in Odin.
5. Add BL file of lastest firmware 6.0 (MM) to BL slot in Odin.
6. Start and wait a moment.
7. Setup and after that, you can flash TWRP or BOOT via Odin without bootloader errors.
Enjoy!
Sorry for my english...
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------
I try this with the Android 6.0.1 BL but I recived the next error: SV REV. CHECK FAIL. DEVICE: 3. BINARY: 1
please help me.. my Phone is A5 2017 (SM-A520F)
RubenDGuerreroG said:
--------------------------------------------------------------------------------------------------------------------------------------
I try this with the Android 6.0.1 BL but I recived the next error: SV REV. CHECK FAIL. DEVICE: 3. BINARY: 1
please help me.. my Phone is A5 2017 (SM-A520F)
Click to expand...
Click to collapse
OK two things.
1. You can't have downloaded the boot image specified as it's a rev. 2 binary not 1.
2. Your device has been updated to rev. 3, so you're probably out of luck for downgrading.
ashyx said:
OK two things.
1. You can't have downloaded the boot image specified as it's a rev. 2 binary not 1.
2. Your device has been updated to rev. 3, so you're probably out of luck for downgrading.
Click to expand...
Click to collapse
Same problem here...
I can't root anymore
ashyx said:
OK two things.
1. You can't have downloaded the boot image specified as it's a rev. 2 binary not 1.
2. Your device has been updated to rev. 3, so you're probably out of luck for downgrading.
Click to expand...
Click to collapse
I just bought the A520F/DS (Malaysia) which still has MM 6.0.1. Can I use the procedure - Flash latest Nougat (Rev. 3 or later) in AP, CP, CSC) leaving BL blank - then do root? (Would I be correct to assume the bootloader will be unaltered, i.e. still be MM 6.0.1?) Thanks.
Just dropping by to leave some info, I successfully flashed TWRP on my single sim A520F with December bootloader updated to january after porting 7.1.1, and another one, same single sim, with January bootloader. Although, i have a friend with Duos that can't flash anything too since november patch.
So i think this issue is more like a bug, i don't see why samsung would lock only duos devices and not single too. N8 issue is actually the dissappearing oem unlock toggle, csc related. Some countries have it, some countries don't. But in our situation, this is more like a frp lock stuck on, no matter why oem toggle says. I surely hope i am right and future updates will bring duos users the freedom back.
Regards
Sent from my SM-A730F using Tapatalk
Has anyone tried updating to January Security Patch using the same trick? Say, Odin combination of rev 2 BL (from MM) + rev 4 January nougat update (AP+CP+CSC) and had their phones rooted after flashing?
Update: Done using this trick and had my device rooted successfully.
@ashyx
Hi
Is it possible to skip updating bootloader when flashing, to avoid rooting problems?
e.g. Can we update to android O with an unlocked bootloader of Android N or MM?
My own installation is currently outside the only link to find a situation such as the software does not find helde Turkey
Upload complete.....
OTA Screen Nougat to OREO
free image hosting
source:my sites https://www.androidatesi.com/threads/galaxy-note-8-oreo-turkiye-firmware-dosyasi-tek-link.1969/
Download TURKEY Firmware CRC1 OREO
https://androidfilehost.com/?fid=818070582850503294
Ota update was given out OFFİCALL OREO TURKEY-WARRANTY In addition you can download the latest version of the software you can install it via SAM
This will not cause any damage to your device, but DO NOT WAIT and LOOSE the android 8 experience too late to experience your note 8 device. ABSOLUTE DOWNLOAD
For those who do not know the installation methods
First of all, upload your sophisticated fast firmware to your pc
Type in the search part exactly as shown in the picture below
Model: SM-N950F
Region: TUR
Samfirim My Vıdeo
Odin İnstall Firmware MY Vıdeo
SOFTWARE INSTALLATION GUIDE
Hey,
I'm new here so greetings to everyone .
I'm using a SM-A520F (UK import) and it's still on Android 6.0.1.
Basically I'm considering flashing this update with odin but I got some questions first .
My device's baseband version is: A520FXXU1APLL -> Does the BB version matter when I install the new ROM?
Can I install Android software from all countries? (I've read this will work..?)
I found Android 8 for my device on sammobile (AUT Version) with BB version A520FXXU4CRD5.
Would this version work for my phone?
Greetings
For those who don't know, F707U is the model number of all of the US carrier versions of the Galaxy Z Flip 5G. The F707U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
These are used for converting from one carrier's U firmware to AT&T's, or from U1 firmware back to U firmware with AT&T features and bloat. These are much tougher to find than other carriers' files due to AT&T's policy against public hosting of their firmware files - they can't be obtained from SamFirm or Frija or SamMobile. But I pay for a subscription to a site that gets AT&T files, and also sometimes gets other carriers' firmware files before they hit SamFirm/Frija, so that's where my files come from.
So I'll be uploading at least one USERDATA for each bootloader version, and I'll do the full firmware (for at least one build per bootloader level) if AT&T was the only carrier to get that specific build.
Since firmware is universal on U models, for a full flash you can use the other 4 Odin files (BL, AP, CP, CSC) from any other firmware of the same build. You can probably even mix and match builds (as long as the Android version is the same), if you can't find files for the exact same build. You can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader level.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=318351
NOTES:
- I won't be providing detailed instructions on how to flash files in Odin. If you're not aware of how to do that, there are countless "beginner's guide to Odin flashing"-type threads here on XDA already
- I compress extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for AFH folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- If the phone doesn't do it automatically, the correct procedure for manually switching from one carrier's firmware to another is:
1. With no SIM inserted, flash the full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
- USERDATAs for any other CSCs/regions can be gotten from SamFirm or Frija - for the latest version. If you need an old USERDATA for a CSC/region that's not commonly found, let me know and I can probably get it.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Do you have the tmobile or the unlocked userdata?
BTW samfirm or freya do not have any f707u firmaware
jacllondon said:
Do you have the tmobile or the unlocked userdata?
Click to expand...
Click to collapse
iBowToAndroid said:
USERDATAs for any other CSCs/regions can be gotten from SamFirm or Frija
Click to expand...
Click to collapse
jacllondon said:
BTW samfirm or freya do not have any f707u firmaware
Click to expand...
Click to collapse
Yes, you absolutely CAN get F707U firmware from Frija
iBowToAndroid said:
Yes, you absolutely CAN get F707U firmware from Frija
Click to expand...
Click to collapse
thanks.
You were right. Iwas putting f707u with error. it needed to be sm-707u....Newby mistake lol
What is the csc of unlocked?
jacllondon said:
thanks.
You were right. Iwas putting f707u with error. it needed to be sm-707u....Newby mistake lol
What is the csc of unlocked?
Click to expand...
Click to collapse
XAA
Thank you. So I flashed everything with odin. Trying to de brand from att to unbranded. I flashed successful but the att logo and bloatware are still there. tried to use Tmobile user data, but does not overwrite theatt one. Am I doing something wrong? maybe forgetting a step to delete att userdata before flashing tmb's one? Thank you
---------- Post added at 05:47 PM ---------- Previous post was at 05:08 PM ----------
nevermind. I used a patched odin and flashed the XAA... thank you
iBowToAndroid said:
For those who don't know, F707U is the model number of all of the US carrier versions of the Galaxy Z Flip 5G. The F707U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
These are used for converting from one carrier's U firmware to AT&T's, or from U1 firmware back to U firmware with AT&T features and bloat. These are much tougher to find than other carriers' files due to AT&T's policy against public hosting of their firmware files - they can't be obtained from SamFirm or Frija or SamMobile. But I pay for a subscription to a site that gets AT&T files, and also sometimes gets other carriers' firmware files before they hit SamFirm/Frija, so that's where my files come from.
So I'll be uploading at least one USERDATA for each bootloader version, and I'll do the full firmware (for at least one build per bootloader level) if AT&T was the only carrier to get that specific build.
Since firmware is universal on U models, for a full flash you can use the other 4 Odin files (BL, AP, CP, CSC) from any other firmware of the same build. You can probably even mix and match builds (as long as the Android version is the same), if you can't find files for the exact same build. You can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader level.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=318351
NOTES:
- I won't be providing detailed instructions on how to flash files in Odin. If you're not aware of how to do that, there are countless "beginner's guide to Odin flashing"-type threads here on XDA already
- I compress extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for AFH folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- If the phone doesn't do it automatically, the correct procedure for manually switching from one carrier's firmware to another is:
1. With no SIM inserted, flash the full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
- USERDATAs for any other CSCs/regions can be gotten from SamFirm or Frija - for the latest version. If you need an old USERDATA for a CSC/region that's not commonly found, let me know and I can probably get it.
- For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Click to expand...
Click to collapse
What (if any) are the differences between the US models (F707U) and the European models (F707B)? Can European builds be applied to US models? I'm asking because Android 11 has been released for the European models but not the US ones yet.
Stuart R said:
Can European builds be applied to US models? I'm asking because Android 11 has been released for the European models but not the US ones yet.
Click to expand...
Click to collapse
Nope
AT&T USERDATA for Android 11 has been added - build TL6.
I also added the full firmware package because I didn't see that anyone else had uploaded it on AFH yet.
From now on, you can expect AT&T USERDATAs to be added right away, when new bootloaders and new Android versions are released
iBowToAndroid said:
Yes, you absolutely CAN get F707U firmware from Frija
Click to expand...
Click to collapse
Indeed. I've downloaded two Android 11 releases there!
Hey, I have a SM-F707U ATT and it doesn't have One UI 3 so what should I flash on it to get One UI 3? sorry of the question is too noob
bhoot1234567890 said:
Hey, I have a SM-F707U ATT and it doesn't have One UI 3 so what should I flash on it to get One UI 3? sorry of the question is too noob
Click to expand...
Click to collapse
Idk which update added One U1 3.0. I guess flash Android 11 and see if that has it
Bootloader 2 firmware has been added, along with the AT&T USERDATA - build ending in UD9
One UI 3.1.1 for U firmware was just added - go get it if you're interested!! Build UH4
One U1 3.1.1 has now been released for U1 firmware as well - available via the various firmware download tools
Android 12 full firmware and AT&T USERDATA has been added - build UL9
Hello, do you have the latest att firmware, thank you very much for sharing！！
luookeee said:
Hello, do you have the latest att firmware, thank you very much for sharing！！
Click to expand...
Click to collapse
I see you haven't read the OP.
"....any U or U1 firmware version can be flashed to any U or U1 device at any time...."
iBowToAndroid said:
I see you haven't read the OP.
"....any U or U1 firmware version can be flashed to any U or U1 device at any time...."
Click to expand...
Click to collapse
Of course I saw it. I'm just worried about what's different. Let me try it thank you！！