Database Info

[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

Downgrade Samsung Galaxy A6 from Android 10 to Android 8

Hello,
We have a big issue. We have a custom application that was installed on Samsung Galaxy A6 phones. After upgrading Android the application won't install anymore.
I need to downgrade operating system from Android 10 to Android 8 on these phones, as they came original.
The big issue is I cannot downgrade the bootloader in order to install stock firmware of Android 8 from sammobile.com
Can anybody help me?
Thank you

Doesn't the stock firmware contain bootloader?

Tab E said:
Doesn't the stock firmware contain bootloader?
Click to expand...
Click to collapse
Yes, contain bootloader but I cannot revert from a higher bootloader version to a previous bootloader version using Odin

Oh yes you will get SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2." error

Extract the andorid 8 firmware with 7 zip. Delete all files ending with
".bin" repack the firmware to ".tar and flash it with odin

Tab E said:
Extract the andorid 8 firmware with 7 zip. Delete all files ending with
".bin" repack the firmware to ".tar and flash it with odin
Click to expand...
Click to collapse
the stock files have extension .tar.md5(5 files: BL, AP, CP, CSC)
I tried what you said, but when I repack with .tar extension ODIN do not read the files. Anyway, I did not found system.bin, image.bin, recovery.bin or files like this. Are just two .bin files(modem.bin and another one)

robertanisoiu said:
the stock files have extension .tar.md5(5 files: BL, AP, CP, CSC)
I tried what you said, but when I repack with .tar extension ODIN do not read the files. Anyway, I did not found system.bin, image.bin, recovery.bin or files like this. Are just two .bin files(modem.bin and another one)
Click to expand...
Click to collapse
Delte the BL
This is the bootloader file.

Tab E said:
Delte the BL
This is the bootloader file.
Click to expand...
Click to collapse
And I load in Odin only AP, CP and CSC files wihout any modification?

robertanisoiu said:
And I load in Odin only AP, CP and CSC files wihout any modification?
Click to expand...
Click to collapse
Yes

Tab E said:
Yes
Click to expand...
Click to collapse
I tried but, unfortunately, I receive the error: "kernel rev check fail device 6 binary 2(boot)". The actual bootloader is 5, the Android 8 bootloader version is 2.

Combination firmware.

Hey guys and girls I'm really confused by combination firmware . I'm looking for some for a galaxy S10 lite .
Current firmware is g770fxxs4euf6
I've found some combination files but I'm not sure which one I need I read about numbers and codes having to match and don't want to get the wrong one so how do I know which is the right one please ?

hainguyenthao said:
Here it is G770FXXU4AUA1
But you will need pit token to flash it cause it is a new device model
Click to expand...
Click to collapse
Thank you appreciate it can I get that from original firmware ?

teamtatty11 said:
Hey guys and girls I'm really confused by combination firmware . I'm looking for some for a galaxy S10 lite .
Current firmware is g770fxxs4euf6
I've found some combination files but I'm not sure which one I need I read about numbers and codes having to match and don't want to get the wrong one so how do I know which is the right one please ?
Click to expand...
Click to collapse
If you look at the build number of a Samsung firmware, the 5th character from the right end of the build number is the "Binary version". In the build number of the firmware that you posted above, the 5th character from the right in that build number is a 4. This means that your firmware is a binary 4 firmware.
The binary version is important because it prevents a user from downgrading the firmware. When flashing a firmware file, if the binary version of what you are trying to flash is lower than the binary of the currently installed firmware, then you can not flash the lower binary firmware. You can only flash a firmware that has a binary version that is equal to or higher than the binary of the currently installed firmware.
In your case, you have a binary 4 firmware currently installed, this means you can not flash a binary 3, 2 or 1 firmware, you can only flash a binary 4 firmware or higher. If you ever flash a higher binary, for example, from binary 4 to binary 5, you could never go back to binary 4 and if you flash from binary 5 to binary 6, you could never go back to 5 or 4. You can never go back, you can stay where you are or go higher.

Droidriven said:
If you look at the build number of a Samsung firmware, the 5th character from the right end of the build number is the "Binary version". In the build number of the firmware that you posted above, the 5th character from the right in that build number is a 4. This means that your firmware is a binary 4 firmware.
The binary version is important because it prevents a user from downgrading the firmware. When flashing a firmware file, if the binary version of what you are trying to flash is lower than the binary of the currently installed firmware, then you can not flash the lower binary firmware. You can only flash a firmware that has a binary version that is equal to or higher than the binary of the currently installed firmware.
In your case, you have a binary 4 firmware currently installed, this means you can not flash a binary 3, 2 or 1 firmware, you can only flash a binary 4 firmware or higher. If you ever flash a higher binary, for example, from binary 4 to binary 5, you could never go back to binary 4 and if you flash. You can never go back, you can stay where you are or go higher.
Click to expand...
Click to collapse
Ahh thank you for the explanation I understand that now and have the correct firmware I believe .
Any idea how I can get a pit file ? I've got the stock firmware and tried adding .zip on the end but this didn't work for me .

teamtatty11 said:
Thank you appreciate it can I get that from original firmware ?
Click to expand...
Click to collapse
You should not need the PIT and if you do, it should be packed in the firmware file somewhere.
hainguyenthao said:
Here it is G770FXXU4AUA1
But you will need pit token to flash it cause it is a new device model
Click to expand...
Click to collapse

teamtatty11 said:
Ahh thank you for the explanation I understand that now and have the correct firmware I believe .
Any idea how I can get a pit file ? I've got the stock firmware and tried adding .zip on the end but this didn't work for me .
Click to expand...
Click to collapse
Your firmware should be in .tar format, if it isn't, you probably need to extract it until you get a .tar.md5, then flash that via Odin.

Droidriven said:
Your firmware should be in .tar format, if it isn't, you probably need to extract it until you get a .tar.md5, then flash that via Odin.
Click to expand...
Click to collapse
when i tried installing via odin it said i needed the pit file i'll keep playing and see where i can get appreciate the help .

teamtatty11 said:
when i tried installing via odin it said i needed the pit file i'll keep playing and see where i can get appreciate the help .
Click to expand...
Click to collapse
The PIT is usually packaged in the firmware file somewhere. Try extracting the files in the firmware then extract those files and keep extracting the files down, look through the extracted files until you find the PIT file.
Or
Do some Google searches for:
"PIT file for (your specific model number"
Or
If there are older versions of firmware for your model number that you can download, download one of them and extract it and keep extracting those files while looking through them until you find the PIT file.

teamtatty11 said:
when i tried installing via odin it said i needed the pit file i'll keep playing and see where i can get appreciate the help .
Click to expand...
Click to collapse
If none of that works, there is also a way to pull a PIT file from the device itself by using adb shell commands but I'm not sure if it requires rooting the device or not.
Yep, requires root.
https://www.getdroidtips.com/how-to-extract-pit-files-for-any-samsung-galaxy-device/

Droidriven said:
The PIT is usually packaged in the firmware file somewhere. Try extracting the files in the firmware then extract those files and keep extracting the files down, look through the extracted files until you find the PIT file.
Or
Do some Google searches for:
"PIT file for (your specific model number"
Or
If there are older versions of firmware for your model number that you can download, download one of them and extract it and keep extracting those files while looking through them until you find the PIT file.
Click to expand...
Click to collapse
Thank you the person above who commented said that only people with access to Samsung servers can get the pit file and it will cost 64 dollars so I'm not sure . I did try extract from firmware I got from sammobile but it was password protected and I couldn't seem to find a password anywhere . I'll keep digging though I've not got anything to lose at this point . All a learning curve . Really appreciate the help

Question help: SM-a125U stuck in Hash of data does not match digest in descriptor

Previous android version: Android 11
Previous base-band version: A125USQU2BUG5
company: wireless cricket
In the context of flashing with the new firmware I used :
- Odin version: 3 v3.14
- Firmware used: Samfw.com_SM-A125U_USC_A125USQU2BUL1_fac_2

The error is related to the vbmeta check. Did you used a sock firmware or you have patched it with magisk? Btw i reccomend to use frija to download the firmware.
If i can suggest I would make this steps:
1) download latest firmware with frija
2) Flash the stock and see if it work
Otherwise if this not help:
1) download latest firmware with frija
2) patch the whole ap and not only boot.img with magisk
3) open odin and flash it using the patched ap on the ap slot
If nothing above works, I think you can try this... not sure it will work. Replace inside the ap the vbmeta.img with the attached one that have the disabled verified boot.

Oneplus# said:
The error is related to the vbmeta check. Did you used a sock firmware or you have patched it with magisk? Btw i reccomend to use frija to download the firmware.
If i can suggest I would make this steps:
1) download latest firmware with frija
2) Flash the stock and see if it work
Otherwise if this not help:
1) download latest firmware with frija
2) patch the whole ap and not only boot.img with magisk
3) open odin and flash it using the patched ap on the ap slot
If nothing above works, I think you can try this... not sure it will work. Replace inside the ap the vbmeta.img with the attached one that have the disabled verified boot.
Click to expand...
Click to collapse
Thanks for the reply.ok
1- The firmware is stock.
2- I didn't patch any of the files I got ( any recommended guide on how to proceed>?)
3- I' so new at this
But anyways, yesterday I kind of sorted out the stuck by adding BL file, and CSC file along the AP file to ODIN, the phone restarted ok but found out it hasn't been unlocked from the carrier yet, so I guess that by judging what u just said, there are few thing I need a guide to
- Flashing the stock
- Patching the AP file
Ps Frija opens up when executed, but it closes in less than 1 second. (Pc 's OS: win 10 enterprise 64 bits)

leonardo07746 said:
Thanks for the reply.ok
1- The firmware is stock.
2- I didn't patch any of the files I got ( any recommended guide on how to proceed>?)
3- I' so new at this
But anyways, yesterday I kind of sorted out the stuck by adding BL file, and CSC file along the AP file to ODIN, the phone restarted ok but found out it hasn't been unlocked from the carrier yet, so I guess that by judging what u just said, there are few thing I need a guide to
- Flashing the stock
- Patching the AP file
Ps Frija opens up when executed, but it closes in less than 1 second. (Pc 's OS: win 10 enterprise 64 bits)
Click to expand...
Click to collapse
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?

Oneplus# said:
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Click to expand...
Click to collapse
thanks for all that
- it s sim block

Oneplus# said:
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Click to expand...
Click to collapse
Mannn thanks!
I rooted my tab 5Se a long time ago and deleted the firmware files except the AP.
I got stuck on the same screen today when I re-locked my bootloader after a stock AP-only flash
Then I saw your reply here and got the rest of the files flashed and it worked and booted
And for those who are reading if you don't have a SIM on your tablet you don't need a CP that's why you won't find it in your firmware zip file
Cheerios

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