Develop Bugs

LG G4 H815 Permanent Debranding - How to make it Generic

Hi,
I have LG G4 H815 - 3 UK variant. I flashed it with Europe General H81510B_00.kdz software and now I have like 100 carrier apps installed. Most of them can't be removed. I think it's caused by some carrier files on the phone - there's an error message when phone boots up:
Current version is not available for user. Can't find matched cust for NT-code mcc/mnc[23420], subset[FF]
Is there any way to remove all carrier files and make it Generic Variant?
I've tried to flash it with: Europe H81520C_00_1218.kdz, Europe OPEN H81510D.kdz and UK H81510B_00.kdz and installation fails at 5%

I think the problem here is Software version on this phone - it is similar to CID on HTC and CSC on Samsung. Anybody knows how to change it to Generic?
My current software version is: V10c-234-20
Also it looks like these carrier apps are being stored on a different partition. Flashing with Generic software is not removing them. Do you know where these files are stored so I can remove them? Future OTA update won't restore them?
BTW. I know I can eaisly disable all of those apps by using Debloater, but I want to permanently remove them from this phone.

karoltom said:
Hi,
I have LG G4 H815 - 3 UK variant. I flashed it with Europe General H81510B_00.kdz software and now I have like 100 carrier apps installed. Most of them can't be removed. I think it's caused by some carrier files on the phone - there's an error message when phone boots up:
Current version is not available for user. Can't find matched cust for NT-code mcc/mnc[23420], subset[FF]
Is there any way to remove all carrier files and make it Generic Variant?
I've tried to flash it with: Europe H81520C_00_1218.kdz, Europe OPEN H81510D.kdz and UK H81510B_00.kdz and installation fails at 5%
Click to expand...
Click to collapse
Have you tried these: http://forum.xda-developers.com/g4/development/stock-h815-20d-images-kdz-flashable-t3301366
LG-H81520D 100% stock untouched system, boot, modem and bootloader.
Direct link: http://downloads.codefi.re/autoprime/LG/LG_G4/H815/H81520D/H81520D_00_0115.kdz
I'm also in the UK and using this. My device was debranded and factory unlocked though.

It's not the software fault. NT Code causes this. I've got a really easy workaround. No carrier apps now and no NT Code error.
What I did:
1. Root
2. Install app FX File Explorer + File Explorer (Root Add-On)
3. Mount /cust folder for Read/Write
4. Edit file /cust/cust_path_mapping.cfg
5. Add line: 23420,FF=/cust/OPEN_COM
NT Code error is gone, also phone is not installing these all crap apps. It will be probably gone after flash or software update. I've tried factory reset and it stays generic
If you don't have NT Code error, but your phone is installing all this carrier crap, you can edit this file and change path only to /cust/OPEN_COM. I think you have to flash your phone with Europe General H81510B_00.kdz first.
You can find your carrier code in Service menu: *#546368#*815#* >SVC menu >Version info > NT Code OR Settings > About phone > Software info > Software Version

Sammobile Image not working?

I did a firmware replacement on an s7 last month using the firmware on sammobile and when I did it there was a specific ap, cp and bl file I had to add for the flash to work.
Now, trying to do one for a verizon note 4, the file I downloaded from sammobile under n910v for 6.0.1 only has one file in the zip with a tar.md5 extension and the instructions say to add it to the ap and pda options in Odin...but there is no pda option in odin?
I've tried the file in every checkbox available and one at a time as well and it does nothing on start, just shows all threads completed (success 0 / failed 0) and it shows that result immediately having done nothing with the phone?
What am I missing?

mcdonsco said:
I did a firmware replacement on an s7 last month using the firmware on sammobile and when I did it there was a specific ap, cp and bl file I had to add for the flash to work.
Now, trying to do one for a verizon note 4, the file I downloaded from sammobile under n910v for 6.0.1 only has one file in the zip with a tar.md5 extension and the instructions say to add it to the ap and pda options in Odin...but there is no pda option in odin?
I've tried the file in every checkbox available and one at a time as well and it does nothing on start, just shows all threads completed (success 0 / failed 0) and it shows that result immediately having done nothing with the phone?
What am I missing?
Click to expand...
Click to collapse
If it's a .zip file make sure you've unzipped it. In later versions of ODIN just drop it in the AP block. You want everything unchecked except for F.reset and possibly auto reboot. It'll populate all of the other boxes once it starts.

[Help?] Bootloop on flash official firmware (SM-G9600)

I got my new SM-G9600/DS in the mail today and it had the G9600ZCU1ARBG firmware on it (Updato). I wanted to check out the Hong Kong firmware, so I fired up Odin 3.13, set the phone to download mode, and tried to flash it with the AP, BL, CP, and CSC (not HOME_CSC, I wanted a clean wipe) files from the G9600TGY2ARE6 firmware (Updato), but that failed; it hung on "SetupConnection..." for a few minutes and then gave a "Complete(Write) operation failed."
After that, I tried the same flash but without the CP, and it seemed to work: it rebooted a few times, then went to the welcome screen (in Chinese). However, it was very unstable, and SystemUI crashed several times while I tried to set it to English. Even after a reboot, it was still unstable like that, so I decided to reflash again (maybe the flash was slightly corrupt?). This time I enabled the "Re-Partition" option in Odin, hoping it would overwrite everything and make it clean again, but without any other changes (BL, AP, and CSC). However, this time it failed, hanging on "SetupConnection..." like the first time I tried to flash it. Since then I've tried just about every combination of firmware files (BL and AP, BL and CSC, AP and CSC, etc) but all of them fail to establish a working connection.
I'm currently downloading the G9600ZCU2ARE6 firmware (Updato) which is the most recent firmware actually for my device. I will try flashing that when it's done (hopefully in the next 30-60 mins), but if that fails I'm at a loss. What should I do?

Update: I tried entering recovery mode (holding power + volume up + bixby), but it crashed as soon as it passed the blue android screen; I think I saw a screen flash by quickly that said something like "connection failed"? When I rebooted it and failed a few more flashes, I tried to boot up normally and got most of the way to the welcome screen, but it also crashed, so I rebooted into recovery mode again, and this time it worked! I wiped the cache partition and did a factory reset, but that didn't seem to work. Now it bootloops to the beginning of the welcome screen (the white nav bar with a back arrow appears at the bottom of the screen, but the SystemUI crashes [I think; all the error messages are in Chinese]).
EDIT: I finished downloading the G9600ZCU2ARE6 (CHO with v2 bootloader) firmware and tried to flash all four (BL, AP, CP, and CSC; not HOME_CSC) files and re-partition, and the log quickly spat out the following, then stopped (because it failed).
Odin3 v3.13 said:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6643 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Thoughts? I'm currently trying it without the re-partition option enabled, but I suspect it won't work because it's been hanging on "SetupConnection..." for a long time, it usually passes that quickly if it's going to succeed. If this fails, I'll try the same two tests but omitting the CP file.
EDIT2: It didn't work when omitting the CP file. What should I do next? I'm currently downloading the original firmware that came with the device (G9600ZCU1ARBG linked in OP) and will try that when this it finishes downloading, but that may be a task for tomorrow.

Update 2: I managed to wait out all the crashes and get the phone "set up", past the welcome screen. It still bootloops, but I get about a minute or two of use before it reboots itself. I managed to get this photo of the software information screen before it crashed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interestingly, the "Baseband version" is only 1ARBG, while the "Build number" is 2ARE6. I suspect this is the source of the instability? In order to fix this, I tried to flash it with the original firmware (all four files of the 1ARBG stuff, the same it was supposed to come with), but I got the following failure in Odin:
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 6556 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone itself gave me this info:
That last line, where it says "Fused 2 > Binary 1" makes me think that I've upgraded enough things to v2 that it won't let me downgrade everything to the stock v1 that it came with.
What should I do now? Maybe try to get it to do a factory reset?
...Or am I missing something obvious in the flashing process that would make it work?
EDIT: I did a factory reset, not sure if it did anything useful. It still reboots itself after 1-2 minutes of usage. I managed to connect it to my wifi, but it doesn't seem to do anything when I tell it to check for a software update. I'm pretty lost. Any suggestions? Is there a way I can at least get it back to stock Samsung?

Flashing between different CSCs for the same device model usually doesn't cause problems, the problem is likely from the bootloader
You'll probably need to flash back to the entire Hong Kong firmware with the Version 2 Bootloader until your own firmware updates to version 2 also, not sure of any way to downgrade bootloaders if Odin won't do it, factory reset after flash should fix the crashing if it is just system apps crashing
You could try enabling OEM Unlock from developer options first which unlocks the bootloader (if you have that option, might have 7 days since last flash to wait for it to appear though)
Setup connection errors is an error between phone and PC, you cannot break Download mode by flashing firmwares, so that is not the problem, more likely drivers, USB cable, PC itself / Windows / PC USB port
Try another machine / port on the PC, or remove drivers from device manager while phone is connected, then disconnect and connect it again to reinstall them

*Detection* said:
Factory reset after flash should fix the crashing if it is just system apps crashing
Setup connection errors is an error between phone and PC, you cannot break Download mode by flashing firmwares, so that is not the problem, more likely drivers, USB cable, PC itself / Windows / PC USB port
Try another machine / port on the PC, or remove drivers from device manager while phone is connected, then disconnect and connect it again to reinstall them
Click to expand...
Click to collapse
I'll try the factory reset today, not sure it can complete before the device reboots though. Or should I do it from recovery mode?
I'll also try flashing it again and make sure I have the right drivers installed. Something I noticed before was that windows installed drivers for "Galaxy S9" (or maybe "Samsung S9"? don't exactly remember) when the phone was on, but "SM845" when I connect it in Download mode. Could that be the issue?
*Detection* said:
You could try enabling OEM Unlock from developer options first which unlocks the bootloader (if you have that option, might have 7 days since last flash to wait for it to appear though)
Click to expand...
Click to collapse
Will that trip Knox?

nelsyv said:
I'll try the factory reset today, not sure it can complete before the device reboots though. Or should I do it from recovery mode?
I'll also try flashing it again and make sure I have the right drivers installed. Something I noticed before was that windows installed drivers for "Galaxy S9" (or maybe "Samsung S9"? don't exactly remember) when the phone was on, but "SM845" when I connect it in Download mode. Could that be the issue?
Will that trip Knox?
Click to expand...
Click to collapse
Drivers will auto install the correct ones
Recovery factory reset yes
No it won't trip KNOX

Success! I managed to get it to flash all 4 firmware files (BL, AP, CP, and CSC) for CHO! (G9600OWO2ARE6 Updato)
The only things I did differently were: I let the phone reboot a few times to take a look at things (took about 2 minutes to get to lock screen, and about 1..5 to 3 minutes after that before it would reboot), and I ran ODIN as my normal user account on Windows (not as administrator). Maybe running it as administrator (as I did yesterday) messed up the USB drivers somehow...?
Software information after reflash, reboot, and setup:
The baseband, build number, and service provider SW all match the CHO files, so everything seems to have flashed successfully! :victory:
However, I downloaded Samsung Pay from the Play Store and when I try to open the app it gives an error popup: "Unable to connect to Samsung Pay temporarily. Try again later."
What should I do? I have yet to add a Samsung Account or insert a SIM card. Would one of those be helpful? Or should I reflash with a different CSC?

I downloaded the "Phone INFO Samsung" app and checked the CSC page. The app is listing the phone as from Trinidad/Tobago...
Honestly I have no idea how that happened lol. What's the best way to change it to something that will support Samsung Pay? Can I flash the US unlocked (U1 I think) (just the HOME_CSC, even?) without reflashing the other parts? Or should I completely reflash to factory from a different region?

That firmware has a version 2 bootloader too which will be why it flashed OK
Samsung pay probably requires a samsung account attached to the device, set it up normally as a new phone
EDIT - Was your device 2nd hand? Or originally on TTT CSC?
If the CSC you flash is Multi and includes the original CSC, it will default to the original CSC of the phone

*Detection* said:
That firmware has a version 2 bootloader too which will be why it flashed OK
Samsung pay probably requires a samsung account attached to the device, set it up normally as a new phone
EDIT - Was your device 2nd hand? Or originally on TTT CSC?
If the CSC you flash is Multi and includes the original CSC, it will default to the original CSC of the phone
Click to expand...
Click to collapse
I set up a Samsung account and it didn't help, even after restart, even after restart with USA AT&T SIM card inserted.
I'm pretty sure the device was brand new when I got it. I believe the original CSC was UNE? I'm not sure--the device was originally in Spanish (and was packaged with the Spanish quick-start guide) and I remember it being a Mexican CSC, but unfortunately it seems I forgot to write it down specifically.
I'm not sure I really understand how Multi-CSC works. Do you know of a good resource that explains it?

nelsyv said:
I set up a Samsung account and it didn't help, even after restart, even after restart with USA AT&T SIM card inserted.
I'm pretty sure the device was brand new when I got it. I believe the original CSC was UNE? I'm not sure--the device was originally in Spanish (and was packaged with the Spanish quick-start guide) and I remember it being a Mexican CSC, but unfortunately it seems I forgot to write it down specifically.
I'm not sure I really understand how Multi-CSC works. Do you know of a good resource that explains it?
Click to expand...
Click to collapse
Not sure of any CSC info resources, googling is your best bet, my best explanation:
Multi-CSC is basically just a pack of CSCs which the device can use any of the CSCs included, imagine a driver pack for windows, you tell the device that needs the driver to search the pack and choose the driver it wants to use, it picks and installs the one that best matches that device and the rest remain in the pack unused
BTU is Multi-CSC, it contains about 10 different CSCs, if your phone was originally shipped with one of the included CSCs, when you flash BTU it will not switch to BTU it will find and switch to the devices original CSC
If the devices CSC is not included, it will switch to BTU
This causes a problem when trying to switch from say XEU to BTU as XEU is included in BTU's Multi-CSC
Single CSC only contains one CSC, so the device is forced to switch to that as there are no other choices
There used to be a trick of switching to a single CSC not included in the Multi you are trying to flash, then flashing the Multi and it would change, but seems that doesn't work now
Reason I'm asking about new or 2nd hand is it is possible it was already flashed to a different CSC when you bought it, so by not knowing it was originally TTT, flashing a Multi that included TTT would revert it back to TTT

*Detection* said:
Not sure of any CSC info resources, googling is your best bet, my best explanation:
Multi-CSC is basically just a pack of CSCs which the device can use any of the CSCs included, imagine a driver pack for windows, you tell the device that needs the driver to search the pack and choose the driver it wants to use, it picks and installs the one that best matches that device and the rest remain in the pack unused
BTU is Multi-CSC, it contains about 10 different CSCs, if your phone was originally shipped with one of the included CSCs, when you flash BTU it will not switch to BTU it will find and switch to the devices original CSC
If the devices CSC is not included, it will switch to BTU
This causes a problem when trying to switch from say XEU to BTU as XEU is included in BTU's Multi-CSC
Single CSC only contains one CSC, so the device is forced to switch to that as there are no other choices
There used to be a trick of switching to a single CSC not included in the Multi you are trying to flash, then flashing the Multi and it would change, but seems that doesn't work now
Reason I'm asking about new or 2nd hand is it is possible it was already flashed to a different CSC when you bought it, so by not knowing it was originally TTT, flashing a Multi that included TTT would revert it back to TTT
Click to expand...
Click to collapse
That's a good explanation of it, thank you. :good:
Should I try to flash with the MXO (Mexico unlocked) AP/BL/CP and use the (single) CSC from the (USA unlocked) U1? Or would that brick things?
EDIT: It seems there isn't a v2 firmware for the U1 yet. Should I try using a CSC from a U variant? Which one? I don't see anything for AT&T on Updato, just "CCT", "TMK, and "USC", should I use one of those?

nelsyv said:
That's a good explanation of it, thank you. :good:
Should I try to flash with the MXO (Mexico unlocked) AP/BL/CP and use the (single) CSC from the (USA unlocked) U1? Or would that brick things?
EDIT: It seems there isn't a v2 firmware for the U1 yet. Should I try using a CSC from a U variant? Which one? I don't see anything for AT&T on Updato, just "CCT", "TMK, and "USC", should I use one of those?
Click to expand...
Click to collapse
Personally I wouldn't mix and match CSC's with the wrong firmware but it's up to you, not sure of the consequences as I've never tried it or seen anyone else do it yet

*Detection* said:
Personally I wouldn't mix and match CSC's with the wrong firmware but it's up to you, not sure of the consequences as I've never tried it or seen anyone else do it yet
Click to expand...
Click to collapse
I'm going to attempt with the XAC (unlocked Canada, correct?) firmware's CSC—the XAA firmware hasn't updated to the v2 bootloader yet. Updato is pretty slow rn so it will be a few hours before that finishes downloading. I suspect I'll have to use Raymonf's modified Odin from the guide to flashing U1 firmware to U devices, but I'll try it with stock Odin first to see what happens.
I figure that even if this bricks, I can't break Download Mode, so I can always flash back to stock G9600, correct?

I just tried flashing the XAC CSC (2ARE6) with the MXO BL/AP/CP (2ARC6).
With stock Odin, it threw an error, saying "SECURE_CHECK_FAIL : PIT" in red text on the Download Mode screen, and Odin's log:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6777 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
With Raymonf's modded Odin, the Download Mode screen gave the same redtext error, and Odin's log gave me the following:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6777 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I suspect this is because the MXO firmware is based on the 2ARC6 bootloader, while the XAC firmware is based on the (slightly newer?) 2ARE6 bootloader, so the partition tables don't quite match up. Thoughts?
Next steps: I'll try the CHO Chile (2ARE6) BL/AP/CP with XAC (2ARE6) CSC. Might get further, since it's the same 2ARE6. I might also try the TGY Hong Kong (2ARE6) BL/AP/CP in similar fashion.

nelsyv said:
[...]
I suspect this is because the MXO firmware is based on the 2ARC6 bootloader, while the XAC firmware is based on the (slightly newer?) 2ARE6 bootloader, so the partition tables don't quite match up. Thoughts?
Next steps: I'll try the CHO Chile (2ARE6) BL/AP/CP with XAC (2ARE6) CSC. Might get further, since it's the same 2ARE6. I might also try the TGY Hong Kong (2ARE6) BL/AP/CP in similar fashion.
Click to expand...
Click to collapse
None of the mixed firmware flashes (BL/AP/CP from CHO or TGY, CSC from XAC) worked, all threw the same errors in Odin (stock and modified both failed) that the MXO/XAC flashes did. It might be possible if I knew more about how the files were structured and could modify the XAC CSC so its PIT would match the others, but I'm not totally sure how these work under-the-hood; I'll leave that to the more serious developers
Now I'm flashing the TGY (Hong Kong) firmware (all four parts). I'm going to put my AT&T SIM into it, factory reset, and see if it changes the CSC. I'll also check the VoLTE menu that @sentron was asking me for in another thread.

Flashing the TGY firmware did change the CSC! Here's some screenshots from the Software Information page.
I also tried sideloading an older version of Samsung Pay, as described in the following quote (for S7 Edge, but I thought it worth a shot).
spielnicht said:
I also have XSG variant . The only way is to downgrade back down to the previous version of the Samsung Pay Framework, but that's not going to happen. Your only option is to factory reset and start from scratch, making sure that you install the previous version of both APKs. That's what I just finished doing. Samsung Pay will force you to update to the latest app before you can use the app (modal keeps popping up). I did that, but kept the older version of the Framework (2.2.03).
To Recap (what I did):
Factory Data Reset
Installed Samsung Pay version 2.0.32
Installed Samsung Pay Framework 2.2.03
Updated to Samsung Pay version 2.1.04 (forced into update via app)
Follow the above and don't update the Framework and you should be good to go.
Click to expand...
Click to collapse
Unfortunately, Samsung bundles a recent version of the Samsung Pay Framework into the HK firmware, so it won't let me install either of those old versions. However, since I'm on the TGY CSC, when I first opened up Samsung Pay (downloaded from Google Play Store, I checked the box for it when I did the first-time device setup), it gives a popup that prompts me to download "Samsung Pay (Hong Kong)", which I agreed to. This installed the Hong Kong version of Samsung Pay, which works! However, it's pretty crippled for American users: it only supports the banks/cards supported by Hong Kong Samsung Pay (honestly this really should be the same app worldwide, Samsung smh ). Here's the chart they post on their support site, listing the supported banks/cards:
Any ideas on how I can try to get either the USA Samsung Pay app, or load an American Card into the Hong Kong system? If I were to open a new account at, e.g., Citibank, would that account need to have a Hong Kong address to use it with this version of the app?

Update: I just tried to add some American credit/debit cards and... they just worked! :victory::victory::victory:
Even though they're definitely not on the Hong Kong list I posted above, it still accepted them. I'll go shopping later and see if payment actually works, but it says that they're activated and ready to go (well, one of them; the other has to be verified by the bank and they said it would happen "within 1 business day"). Maybe the app is more international than it appears... Although the ads are still in Chinese lol.

I went shopping today and paid with a US credit card (a Visa rewards card from a US airline) and it worked without a hitch.
Also, I found a little toggle in my notification tray for VoLTE, and here's what happened when I tapped it:
However, I've noticed my device getting pretty warm, even hot, during normal use while charging. Is this normal? CPU-Z says the "ac" temp is at about 44 C, "battery" temp at about 39 C.

Thanks @nelsyv for reporting back. I'm thinking about flashing the T-Mobile US CSC on top of the OWO ARE6 that I have on my G9600. I'll read up a bit first. The T-Mobile US phone is SnapDragon (Single SIM), so the CSC should be compatible, right? Though I didn't find it stated exactly, it seems like any CSC should work on firmware? Is this correct?

[G960F] Flashing, what is what?

Hi freinds,
thanks for this forum and the fellow help around here.
By flashing my G960F and reading endlessly through threads, I still haven't cleary understood what's going on and I am trying to figure it out and you are asked for help. So many questions...
PIT (Partition Information Table)
It holds the information how the memory/disk is being split into partitions. Usually this is done by naming start and end secor of a partition.
Usually, one never needs to change that. I once hat to change it on my i9100 (Galaxy S2 from 2011 with Android 2), whose system partition of 500MB was not able to handle Android 7 (of 2017), which hat 600MB - repartitioning with pit files was neccessary.
Is there a documentation für the structure of the pit file?
I remeber that this pit is a samsung specifc thing, is that right?
BL (Bootloader, 3MB)
This is the software that runs at bootup time. It displays a logo (e.g. "Samsung with knox") and scans for key combinations that are pressed during boot. It contains the (software for the) download mode and can start as well the AP partiton, more precise: the Android in the Android in the AP partition as well as the TWRP in the AP partition.
True?
The BL can be locked and encrypted to introduce a not-so-strong factory reset, that does not reset the device from being linked to it's google account (making it useless for pickpockets). This device protection is called 'Factory Reset Protection' (FRP). For OEMs, there is an ability to disable the FRP, more precise: to unlock the BL. Some devices offer that unlock on the developer options.
True?
PDA of a ROM
In its log files, TWRP reports the bootloader to be the string that SamMobile.com calls the PDA of a rom. (in my e.g.: ro.boot.bootloader=N910FXXS1DPK3).
True?
One-week-waiting-RMM/KG-State-Prenormal
This happends here somehow as well.
I read in a german forum about the G960F, that someone flashed the CSA2 (of Samfirm in 4 parts with odin) and triggerd the KG-lock by that. But by flashing "the BL of the BRJ8 without auto-reboot" with odin, and entering the download mode at once, the KG-lock was gone without waiting a week.
So, the lock must be stored in the BL partition or CSA2 and BRJ6 store the lock in different positions outside the BL.
Does anyone know more of that?
Flashing which partitions triggers that lock?
CP (Communication Processor, 26MB)
To me it looks as if this provides an API for the OS by containing a driver for the modem and it's parameters which can be hardware related, but also e.g. frequencies, depending on the law of your country.
Is that true?
Are all custom systems in AP basically compatible with all modems in CP?
Do stock roms (in AP) check for "their" version of modem data?
CSC (Consumer Software Customization, 500M)
I read it would contain the localization (geographical version of that phone), carrier branding (including carrier features like wifi calling). Is that true?
ROMs usually contain two versions of that partition: Flashing CSC will wipe the directory /data/, HOME_CSC will not.
How do they differ? I noticed that the HOME_CSC.tar file contains a .pit file. Is there a remapping done while flashing to spare out the data dir?
AP (Android Processor or PDA)
The Android Operatin System, e.g. a custom rom is flashed here. Might have e.g. 4300MB.
BUT: TWRP with about 40MB is being flashed here as well.
How does that work? Is TWRP an alternate 40MB of the AP partiton?
True? Does flashing stock-rom-AP with odin remove TWRP?
Thank you very much!

How to Change CSC of a non-rooted Note10+? Is there any working way?

I've recently bought an SM-N975F Note 10+, which has an OXM multi-CSC ROM and a current CSC set as: SER/SER, SER/XXV. The security patch level is August 2021. The device is not rooted, Knox is 0x0, which I'd like it to stay for a while.
I'm looking for a way to change the current CSC to some value supporting native call recording, like XXV.
So far, I've tried:
* Dialer codes (both *#272*IMEI# and *#*#28262726#*#*, or whatever they are) – no luck opening the preconfig menu;
* Opening the preconfig menu with some other way, like launching it via adb using am start-activity – it seems like the device is missing the com.android.Preconfig package altogether;
* Changing CSC with Samkey: I disabled lock screen security and ejected the SIM card as per the instruction, and despite the tool having said that the operation was successful, the phone rebooted with the same SER/SER, SER/XXV CSC.
Is it possible that flashing a non-multi-CSC firmware (like the XXV one) might help here? Is it possible that I did something wrong with Samkey?
Do you know about any other working way to change CSC in modern Note10+ devices? I consider paid solutions as well (like Samkey I mentioned above).
Thanks.

Whats your android version and binary version ?

The Android version is 11, 7FUH3 OneUI 3.1 firmware.

h0tkey said:
* Dialer codes (both *#272*IMEI# and *#*#28262726#*#*, or whatever they are) – no luck opening the preconfig menu;
Click to expand...
Click to collapse
as I remember this only works with the Google dialer - make a search for this - and you can choose a CSC from there;
when you do this, be ready to loose all data, the phone will factory reset
you can also choose a stock firmware from samfirm.com and flash it with Odin - you need to choose CSC to change it and not HOME_CSC
CSC or HOME CSC? Which CSC File to Flash in Samsung Odin?
Should you flash CSC or HOME CSC in Odin? Using our list of CSC codes, you can easily change it on your Samsung Galaxy phone or tablet.
technastic.com