Database Info

Firmware files - what are the AP, BL, files for?

So I downloaded the latest XSA update which came out yesterday on SamMobile, and flashed all four files - only to find that my phone had been wiped, including my /data partition :'(
So my question is - what are the four categories of files to flash in Odin (AP, BL, CSC, HOME)? And which one is responsible for me losing my data?

If you flash CSC will wipe your data. If you flash CSC_HOME will not wipe your data.
AP: is your system partition with recovery and stuff.
BL: your bootloader
CP: your modem
CSC: this is what features you get in some countries or carriers like Wi-Fi Calling.

Eurofighter_ty said:
If you flash CSC will wipe your data. If you flash CSC_HOME will not wipe your data.
AP: is your system partition with recovery and stuff.
BL: your bootloader
CP: your modem
CSC: this is what features you get in some countries or carriers like Wi-Fi Calling.
Click to expand...
Click to collapse
Thanks for that. So can I flash the CSC file under CSC_HOME?
Sent from my SM-G930F using Tapatalk

Yes. In the CSC slot you put the HOME_CSC file
Sent from my SM-G930F using Tapatalk

Eurofighter_ty said:
Yes. In the CSC slot you put the HOME_CSC file
Click to expand...
Click to collapse
And if the CSC is the same, I can just omit this file?

tangcla said:
And if the CSC is the same, I can just omit this file?
Click to expand...
Click to collapse
No, you must always flash the 4 files!
If your CSC is XSA:
AP, BL, CP & HOME_CSC_XSA
Then your data will stay intact!
Note: this can only be done if you stay at the same CSC; if you want to change your CSC for any reason, you need to flash CSC-file of the new country/region (that will reset your device)

Re-partition?
Do I have to enable the "RE-PARTITION" option in ODIN when changing CSC?
henklbr said:
No, you must always flash the 4 files!
If your CSC is XSA:
AP, BL, CP & HOME_CSC_XSA
Then your data will stay intact!
Note: this can only be done if you stay at the same CSC; if you want to change your CSC for any reason, you need to flash CSC-file of the new country/region (that will reset your device)
Click to expand...
Click to collapse

eldavid39 said:
Do I have to enable the "RE-PARTITION" option in ODIN when changing CSC?
Click to expand...
Click to collapse
Hi mate
It is recommended , changing to a total different CSC may need a change in partition size...
For more info read here
https://www.sammobile.com/forum/showthread.php?t=30800

Mix and match?
Just wondering, could it be possible to mix and match?
Example: Flash the AP of T-Mobile and the CP of AT&T? To avoid incompatible band problems
MAX 404 said:
Hi mate
It is recommended , changing to a total different CSC may need a change in partition size...
For more info read here
Click to expand...
Click to collapse

eldavid39 said:
Just wondering, could it be possible to mix and match?
Example: Flash the AP of T-Mobile and the CP of AT&T? To avoid incompatible band problems
Click to expand...
Click to collapse
Hi
For what I understand all USA ( Snapdragon) versions are compatible , so that would possible BUT to be sure you should ask in the right forum , this is for the international version Exynos

What is the UMS
What is the UMS part of ODIN?

EVERYONE HAVING PROBLEMS TYPING EXIT
Before typing "setsid su<enter>?, type the following: "alias a='exit'<enter>" and THEN type "setsid su<enter>".
IF you do this, you can exit root shell by just "a<enter>", which is cake easy to do.

i made a mistake
cancel
i flashed bl instead of ap what should i do know because phone does't work anymore

I cant seem to find these firmware files anywhere anymore, can someone help me ? I need For Norway/Europe

stoffar87 said:
I cant seem to find these firmware files anywhere anymore, can someone help me ? I need For Norway/Europe
Click to expand...
Click to collapse
updato.com

Thanks
But how to I flash it. My brother has Galaxy S7 but he brings his phone to me and told me how do I flash it.
Fortunately I found this:
http://firmwarearena.com/howtoflash/how-to-flash-samsung-galaxy-s7-using-sp-flash-tool/
But I don't know how SP Flash tool works. Anyone?

haroonbro said:
But how to I flash it. My brother has Galaxy S7 but he brings his phone to me and told me how do I flash it.
Fortunately I found this:
http://firmwarearena.com/howtoflash/how-to-flash-samsung-galaxy-s7-using-sp-flash-tool/
But I don't know how SP Flash tool works. Anyone?
Click to expand...
Click to collapse
Read some threads, the instructions are literally everywhere, they are even under the download on sammobile site, which means you have not read anything

Better off using odin.

BL FAILED
Eurofighter_ty said:
If you flash CSC will wipe your data. If you flash CSC_HOME will not wipe your data.
AP: is your system partition with recovery and stuff.
BL: your bootloader
CP: your modem
CSC: this is what features you get in some countries or carriers like Wi-Fi Calling.
Click to expand...
Click to collapse
Hi
When i try to flash all 4 files together, ODIN fails, i unchecked BL and the flash passed, the phone working fine but i have a serious problem, my phone is French and i flashed Argentina region, now i lost IMEI and Baseband, please help. My phone is ( SM-G930F)
Note: 1. the S/N and IMEI is written on the box
2. I don't know anything about my previous CSC code and i have no idea which firmware was actually my original one.

BRAVE.DANDY said:
Hi
When i try to flash all 4 files together, ODIN fails, i unchecked BL and the flash passed, the phone working fine but i have a serious problem, my phone is French and i flashed Argentina region, now i lost IMEI and Baseband, please help. My phone is ( SM-G930F)
Note: 1. the S/N and IMEI is written on the box
2. I don't know anything about my previous CSC code and i have no idea which firmware was actually my original one.
Click to expand...
Click to collapse
Download XEF firmware for your phone, and flash all 4 files (BL, CP, AP and CSC). It should go back to normal state.

Failed Downgrading J700F

Hi all. I have Samsung Galaxy J7 2015 (SM-J700F). I just received the recent update (April 2017). However, I don't like it and want to downgrade to the previous one. I have downloaded Odin and the firmware which is J700FXXU2BPH3_J700FOLB2BPH2_XID or whatever you call it. It failed after trying to execute cm.bin file. I have done some research and I found that Samsung has locked the bootloader in order to prevent downgrading process. However, in those threads, they only mentioned about downgrading from Android 6 to Android 5. In my case, I just want to downgrade from the previous security update/patch in the same Android version which is Android 6. Is this still possible in my case to do downgrading to my desired version?

Samsung locks older bootloaders from being flashed. It is possible to downgrade the OS without downgrading the bootloader by just flashing all the .tar.md5 files in Odin EXCEPT for the "BL" one since that one is the bootloader. Good luck friend

NullaVisus said:
Samsung locks older bootloaders from being flashed. It is possible to downgrade the OS without downgrading the bootloader by just flashing all the .tar.md5 files in Odin EXCEPT for the "BL" one since that one is the bootloader. Good luck friend
Click to expand...
Click to collapse
Thanks for your reply. What do you mean by "BL"? I am new on this Odin thing.

alphamorpho said:
Thanks for your reply. What do you mean by "BL"? I am new on this Odin thing.
Click to expand...
Click to collapse
See attached picture. Your stock ROM should be a zip containing multiple files. ending in ".tar.md5" and beginning with "BL, AP, CP, and CSC" respectively. You just add and check all of the appropriate files EXCEPT for "BL"

NullaVisus said:
See attached picture. Your stock ROM should be a zip containing multiple files. ending in ".tar.md5" and beginning with "BL, AP, CP, and CSC" respectively. You just add and check all of the appropriate files EXCEPT for "BL"
Click to expand...
Click to collapse
My zip file only contains 1 file. And from the tutorial I have watched it belongs to AP section. But, I have resolved this problem by removing 3 files, sboot.bin, cm.bin & modem.bin.

[how to] FIX FOR: UPLOAD MODE/SUBSYSTEM CRASHED:modem/black screen of death

I've noticed a bunch of folks posting their problem after encounters with this demonic screen:
[UPLOAD MODE]
Subsystem Crashed: MODEM
------------------------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
MODEM INFO
err type: Fatal
Task: ml1_mgr
File: trm_rfm_path_srch.cpp
line: 1916
Invalid combination for LTE VCO selection. Num Rx: 3, Num Tx:
last_ns : 0x6d
Generating summary...
>General info
>DDR info
>DCVS Info
>RPM
>TrustZone
>Hypervisor
>APSS
>Modem
Done!
So I decided to start a separate thread to share what worked to get my Sprint S8 out of this hellish bootloop.
1.) Start off at a place where you get good reception and that has a STRONG Wi-Fi signal (I brought a laptop to Starbucks). It seemed to me the modem crash screen occurred most often in places where I had a weak signal.
2.) Start downloading your stock firmware from either (A)here or (B)herr. Either way, download Odin v3.12.7 found in hyperlink B.
3.) Follow the directions as described in the PWND thread https://forum.xda-developers.com/galaxy-s8/development/samsung-galaxy-s8-root-snapdragon-t3659305 using 7zip to extract your EXT4 file which will complete the rooting process.
4.) Now with the same options selected described in the procedure section, use the Odin 3.12.7 to flash the CSC and CP from the stock firmware you downloaded and be PATIENT. I took me about 20 minutes of anxiety, worrying that it had frozen up until "file analysis" finally popped up on the screen and Odin started to do its thing.
Hope this helps. It worked for me on Sprint. Peace.
Addendum: Read next post for additional info.

Curtex said:
I have been seeing a bunch of folks posting their problem with seeing this demonic screen:
[UPLOAD MODE]
Subsystem Crashed: MODEM
------------------------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
MODEM INFO
err type: Fatal
Task: ml1_mgr
File: trm_rfm_path_srch.cpp
line: 1916
Invalid combination for LTE VCO selection. Num Rx: 3, Num Tx:
last_ns : 0x6d
Generating summary...
>General info
>DDR info
>DCVS Info
>RPM
>TrustZone
>Hypervisor
>APSS
>Modem
Done!
Hope this helps. It worked for me on Sprint. Peace.
Click to expand...
Click to collapse
Couple things:
Flashing system or the sampwnd zip will delete all your data. Plan accordingly.
Also, if you are having modem crashes you apparently should also flash NON_HLOS.bin file in the BL archive. Apparently it's part of the lte modem software and you want those all to be thr same version, no more than one version older or a newer than sysyem, and as up to date as possible.
Thanks for posting this

All you have to do to fix this is flash the cp and csc file for the correct software version. Example when I rooted and updated to AQGL I got that error. I flashed the cp and csc for AQGL and that fixed it. Just use normal Odin.

wgorham said:
All you have to do to fix this is flash the cp and csc file for the correct software version. Example when I rooted and updated to AQGL I got that error. I flashed the cp and csc for AQGL and that fixed it. Just use normal Odin.
Click to expand...
Click to collapse
The people who are having modem crashes sometimes need matching lte drivers which is the NON_HLOS.bin file. It appears to differ greatly based upon drive itself and what version of firmware is installed on each part

partcyborg said:
The people who are having modem crashes sometimes need matching lte drivers which is the NON_HLOS.bin file. It appears to differ greatly based upon drive itself and what version of firmware is installed on each part
Click to expand...
Click to collapse
From a working root environment per the sampwnd instructions can we simply flash cp, CSC and non_hlos from BL file using old Odin?
Will data be lost?

Yes

I'm having the modem crash also. Anyone have a verified link to xfinity mobile S8 firmware? I was led to believe that CCT was the carrier code for them but when I used files from CCT firmware during root process, I was greeted by Cricket Mobile bloatware and modem crashes.

Curtex said:
Yes
Click to expand...
Click to collapse
That was a "Yes" to data being lost if those files are Odin'd?

wgorham said:
All you have to do to fix this is flash the cp and csc file for the correct software version. Example when I rooted and updated to AQGL I got that error. I flashed the cp and csc for AQGL and that fixed it. Just use normal Odin.
Click to expand...
Click to collapse
Did it erase data from the phone?
Edit: Yes it did, just like it said in the OP My bad.

partcyborg said:
Couple things:
Flashing system or the sampwnd zip will delete all your data. Plan accordingly.
Also, if you are having modem crashes you apparently should also flash NON_HLOS.bin file in the BL archive. Apparently it's part of the lte modem software and you want those all to be thr same version, no more than one version older or a newer than sysyem, and as up to date as possible.
Thanks for posting this
Click to expand...
Click to collapse
Sorry for updating this 30+ day old thread but I am stuck with a 'Subsystem Crashed: Modem!" error every time I leave home and don't have a strong Wifi signal which requires several reboots to get the phone back in a working state and I haven't found a better suggested resolution online than the one found in this thread which ...as is... isn't working for me. So I seek additional info....
So how exactly does one flash NON_HLOS.bin file from the BL archive? I extracted the NON-HLOS.bin file from the BL archive and followed the instructions for creating a custom tar.md5 file based on instructions from this and this posts.
With that newly created custom NON-HLOS tar.md5 file, I tried using odin to flash it along with the CP and CSC files referenced in the OP. I also successfully used odin to flash just the CP & CSC files by themselves and then tried to flash the custom NON-HLOS.bin tar.md5 file by itself. In both cases, I get "FAIL! SHA256 is invalid" and the custom NON-HLOS bin file is not flashed.
So how does one flash just the NON-HLOS.bin file in Odin? Do I just flash the entire BL file instead of just the NON-HLOS.bin file? If so then you end up using the BL, CP & CSC files from the original Stock Galaxy S8 firmware. In that case why even use the S8 odin images that came with SamPWND? You could have essentially used the stock s8 images for my carrier. [sprint]. No?

serendrewpity said:
Sorry for updating this 30+ day old thread but I am stuck with a 'Subsystem Crashed: Modem!" error every time I leave home and don't have a strong Wifi signal which requires several reboots to get the phone back in a working state and I haven't found a better suggested resolution online than the one found in this thread which ...as is... isn't working for me. So I seek additional info....
So how exactly does one flash NON_HLOS.bin file from the BL archive? I extracted the NON-HLOS.bin file from the BL archive and followed the instructions for creating a custom tar.md5 file based on instructions from this and this posts.
With that newly created custom NON-HLOS tar.md5 file, I tried using odin to flash it along with the CP and CSC files referenced in the OP. I also successfully used odin to flash just the CP & CSC files by themselves and then tried to flash the custom NON-HLOS.bin tar.md5 file by itself. In both cases, I get "FAIL! SHA256 is invalid" and the custom NON-HLOS bin file is not flashed.
So how does one flash just the NON-HLOS.bin file in Odin? Do I just flash the entire BL file instead of just the NON-HLOS.bin file? If so then you end up using the BL, CP & CSC files from the original Stock Galaxy S8 firmware. In that case why even use the S8 odin images that came with SamPWND? You could have essentially used the stock s8 images for my carrier. [sprint]. No?
Click to expand...
Click to collapse
You need to use comsy Odin the regular one won't work.
Also don't bother with the .md5 part. Just make tars with ustar and flash those direct.
The farther apart your individual ROMs are, the more likely it is that you will have some kind of issue, and sometimes even one apart is a bad idea.
As for the ROMs that are for root. Not all the files are from stock, some are from the "factory "combination" rom that is given somehow to service companies and is regularly sold online to the public. Whether or not all files come from the combination rom or not, at least abl.elf, devcfg.mbn, boot.img and recovery.img have to be from a factory/combo image or you will not get root and if you change system it will no longer boot. I personality source every subsequent file needed (minus system and userdata) from the latest stock image released, but that is just how I do it.
G950U right? Are you rooted? What version/carrier are you on?
I ask because I probably have files uploaded already that may fix whatever is wrong, or at least point out what already is

I think my issues are resolved. I'm posting this in the hope it will help someone else but also for myself so I remember what I did in the future if a new root process is not found. I apologize in advance for the length.
So, I did try the Prince Comsey odin. I also tried Odin 3.07, 3.10.6, 3.12.3 & 3.12.7. The instructions for creating a custom TAR Ball for flashing involved using a version of odin that had a 'Phone' button that was on older versions of Odin but on newer versions including PrinceComsey that button was renamed. No version was successful though. Or so I thought...
In the end, the second half [Part 2] of the SamPWND instructions call for you to use Flashfire to flash the stock system.img.ext4 and SamPWND_G950U. In one of my attempts, I unsuccessfully tried to get Flashfire to flash the custom NON-HLOS.tar.md5 file along with the other two files. I say it was unsuccessful but it is really hard to tell what's going on while Flashfire is doing its thing because the screen goes really dark and while you can see something happening, you can't actually read anything.
Anyway, in the process, I made a decision that I would have Flashfire NOT reboot back into Android [bootloader] but reboot into 'Download' mode immediately after flashing system.img.ext4 & SamPWND_G950U. In download mode I then used PrinceComsey Odin [which was still open from Part 1 of SamPWND instructions] and flashed the CP & CSC archives mentioned in the OP of this thread. I tried this a couple of times. Even though the flashing of NON-HLOS failed each time [or maybe it didn't; unclear], I noticed that after flashing the CP and CSC files with PrinceComsey the random reboots had stopped. I couldn't seem to recreate the 'Subsystem Crashed: Modem!' error and I was really trying.
So to make sure I understood what was going on, I started from scratch. I used Full Odin 3.12.7 to flash Samsung Galaxy S8 Original Stock firmware. Made sure that stock firmware and the phone's hardware were still functioning as expected. It was. I then followed the SamPWND instructions to the letter. Including using only PrinceComsey Odin. The only thing I changed was the very last step I had Flashfire reboot the phone into Download mode (without booting into Android) and then used PrinceComsey Odin to flash the CP & CSC archives as mentioned in the OP of this thread. This seems to have worked for me. I have manually rebooted serveral times. I have gone out to various stores and different WiFi environments that I know caused the Subsystem Crashed: Modem! Error.
I have been running for about 18hrs without any errors at all. I will test some more tomorrow but I have a good feeling about all this.
In the end, with my phone [Sprint Galaxy S8 (SM-G950U) - Snapdragon variant], I never had to use the NON-HLOS.bin file or the custom TAR I created. I only needed to have Flashfire avoid booting into Android and instead reboot into Download Mode as its final step and then use PrinceComsey Odin to flash the CP & CSC archives mentioned in the OP.
Note: Be Careful of other versions of the Samsung Galaxy S8 Root (Snapdragon) Instructions you may find on the internet. I ran into a couple that were wrong and caused me major headaches. Only use the Samsung Galaxy S8 Root (Snapdragon) instructions found on XDA-Developers. :victory: :fingers-crossed:
---------- Post added at 05:58 AM ---------- Previous post was at 05:44 AM ----------
By the way I used SamFirm_v0.3.6 to obtain the latest Samsung Galaxy S8 Sprint firmware directly from Samsung servers using the instructions located at the link below... The CP, CSC and System.Img.Ext4 files were obtained from the same download so there would not have been a difference in the versions
"How to download Samsung Galaxy Full Firmware Files Directly from Samsung Servers"
(I can't post external links, but google the above string of text and look for the site called, androidsage.com)

i need some help I have the exact same phone and with sprint I am rooted and I no longer have access to my phone other then the downloading part it is in a infinite boot to modem crash please help me

About all of this
I just rebooted into download mode and flashed twrp but didn't boot into recovery. Odin brought my phone back to life.

I got first modem crash today! Note 8 with samFAIL. =8 assertion : carrier data failed lol!
sam is a big time failure, should have recalled all the note 8's for not allowing 'carrier' brand direct purchased unlocked bootloaders after all it is the purchaser's phone after all, wow imagine buying a car and having it engine turn off if you got a custom dash cover or aftermarket led headlights!! Away with the same bot failures!!!! Haahahahahahahahahahahahahahahahahahahah. HA!

serendrewpity said:
Sorry for updating this 30+ day old thread but I am stuck with a 'Subsystem Crashed: Modem!" error every time I leave home and don't have a strong Wifi signal which requires several reboots to get the phone back in a working state and I haven't found a better suggested resolution online than the one found in this thread which ...as is... isn't working for me. So I seek additional info....
So how exactly does one flash NON_HLOS.bin file from the BL archive? I extracted the NON-HLOS.bin file from the BL archive and followed the instructions for creating a custom tar.md5 file based on instructions from this and this posts.
With that newly created custom NON-HLOS tar.md5 file, I tried using odin to flash it along with the CP and CSC files referenced in the OP. I also successfully used odin to flash just the CP & CSC files by themselves and then tried to flash the custom NON-HLOS.bin tar.md5 file by itself. In both cases, I get "FAIL! SHA256 is invalid" and the custom NON-HLOS bin file is not flashed.
So how does one flash just the NON-HLOS.bin file in Odin? Do I just flash the entire BL file instead of just the NON-HLOS.bin file? If so then you end up using the BL, CP & CSC files from the original Stock Galaxy S8 firmware. In that case why even use the S8 odin images that came with SamPWND? You could have essentially used the stock s8 images for my carrier. [sprint]. No?
Click to expand...
Click to collapse
I use chimera tool, you can actually check the specific files on the firmware that you want to flash and uncheck the ones you want left out

What is a USERDATA File???

hi im planning to downgrade the firmware of my Galaxy Note8 using odin. from Pie to Oreo. i downloaded an Oreo firmware, the zip contains 6 files.
AP, BL, CP, CSC, HOME CSC and a USERDATA.
im not familiar with USERDATA file. i dont know if i can skip that file or if it's really important also to flash that together with other files. what added to my worry is that my phone is already unlocked with other sim. originally its a tmobile but now im using it with a sim here at the philippines. im afraid that if i flash that Userdata file, my phone will be locked again with tmobile. hope someone can help. Thanks in Advance!

junio07 said:
hi im planning to downgrade the firmware of my Galaxy Note8 using odin. from Pie to Oreo. i downloaded an Oreo firmware, the zip contains 6 files.
AP, BL, CP, CSC, HOME CSC and a USERDATA.
im not familiar with USERDATA file. i dont know if i can skip that file or if it's really important also to flash that together with other files. what added to my worry is that my phone is already unlocked with other sim. originally its a tmobile but now im using it with a sim here at the philippines. im afraid that if i flash that Userdata file, my phone will be locked again with tmobile. hope someone can help. Thanks in Advance!
Click to expand...
Click to collapse
Userdata image is flashed onto the userdata partition, and if you did sometime unlock your device from the carrier, flashing it won't lock it again.
The real problem here is that usually, you can't downgrade unless the bootloader revision be the same in both firmware, (it just happens occasionally) this most likely will trigger the ARB protection.

SubwayChamp said:
Userdata image is flashed onto the userdata partition, and if you did sometime unlock your device from the carrier, flashing it won't lock it again.
The real problem here is that usually, you can't downgrade unless the bootloader revision be the same in both firmware, (it just happens occasionally) this most likely will trigger the ARB protection.
Click to expand...
Click to collapse
i thought i can easily revert back. if only i can root this phone. anyway thanks!

Question Broken AP patch - is TWRP out for this model yet?

Hey guys, I'm on an SM-F711B. Today when trying to update my rooted OS, I had Odin fail twice while trying to install the patched AP file. I also noticed that the patched AP file was about half the size of the original - 3.2gb instead of 8gb. I then tried to install with the stock AP file, but now (duh) it says the file system is corrupted and Android can't boot. Is there any way I can a) fix the patched AP file without access to my phone, or b) at least recover the files (especially images) from my device before having to factory reset? many thanks

Hi,
there's no twrp yet and I doubt that there will ever be. Can you download the firmware again and flash the stock rom to begin again?
Edit:
what size is the original AP file?

thanks for the response
is flashing the stock rom different from loading the stock AP/BL/CP/CSC from Odin? If so, how do I do it?
The AP file is 7.74 GB according to Windows

my AP file is 8.11 GB, which firmware are you trying to flash?
yes the stock rom is different words for stock firmware but if you've already flashed the CSC file (instead of HOME) then you've probably lost any photos as it wipes the storage

Oh, to clarify, I did flash HOME_CSC. my AP filename is AP_F711BXXS2CVG1_F711BXXS2CVG1_MQB53367836_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar if that at all helps narrow down the firmware? I just got whatever was latest from Frija

can you install magisk on a friend or family phone and try patching the AP file again and check the patched file size? it should be slightly larger than the original AP file

Thanks for the advice. I tried patching on my partners phone, a Pixel 2XL. Magisk printed
Code:
-- Copying: super.img.lz4
! Process error
! Installation failed
Do I need to run the patch on another Z Flip 3? Or is this a sign that the AP file i got from Frija is corrupt? It's interesting that it failed during super, as Odin also failed during super when trying to install the patched version
Edit: Her phone was full. We've cleared up some space and I'm trying again

yes I think the firmware might have a gremlin in it, I'd try downloading from a different website and start again
Download Galaxy Z Flip3 5G SM-F711B (O2C) F711BXXS2CVG1 in Samfw - Samsung firmware download
Galaxy Z Flip3 5G SM-F711B (O2C - Czechia) F711BXXS2CVG1 S(Android 12) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com

Hi, I've managed to patch the AP file using my partners phone. It is slightly larger than the original AP file (on Android, 8.39 instead of 8.31 GB). Can I use this patched AP file on my Z Flip 3? or is it model-specific?

yes you can flash it...good luck!

OMG it worked!!!! thank you so so much for your help!

lesbianpinkie said:
OMG it worked!!!! thank you so so much for your help!
Click to expand...
Click to collapse
Wait - spoke too soon. phone boots, but in my file manager, Internal Storage is being shown as 0b / 0b, and no apps seem to be able to access it..... any idea what to do now?

this has happened to me before and in twrp I would choose repair file system, but of course we don't have twrp hmm. did you try flashing the stock AP file to see if that fixes it, then can root afterwards