Related
Seeing as I`m still a relatively noobish poster I`m unable to ask this question in the relevant thread. I`ve just debranded the phone following the 8 step guide but I had issues following step 8 where you change the CSC code. I couldnt quite figure it out so step 8 never got followed. As a result, despite losing the Three branding on the phone I now have a phone that displays the CSC as "unknown" and may well explain why Kies cannot pick up the firmware version on the phone. If I follow step 8 and key in *#272*<your IMEI># on my phone it then shows me a screen headed "Preconfig" with "Sales Code" underneath and "H3G" in the box to the right. Underneath is a radio button thats deselected. if I press to highlight it then press "install" at the bottom of the screen I keep getting an error saying "Must be THREE chars".
Can anyone shed any light on this and give me any hope of rectifying?
Will I need to manually input the Three APN settings once I successfuly change the CSC code?
Thanks in advance. I have spent ages scouring the web but there`s not a great deal of info out there about the CSC part of the debranding process.
id like some more info on how important the csc is too, im got told it hold some carrier information but i dont know if that is true or not.
the reason you cant pick on is probably as since debranding you havent flashed the csc you need, you could find the one you need for your firmware over in the dev section.
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
RedAl said:
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
Click to expand...
Click to collapse
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
redbullman said:
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
Click to expand...
Click to collapse
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
RedAl said:
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
Click to expand...
Click to collapse
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
redbullman said:
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
Click to expand...
Click to collapse
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
redbullman said:
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
Click to expand...
Click to collapse
Cheers Redbullman. I can get into Kies now but on the firmware information section it says "Current Firmware Version : PDA:KDD / PHONE:KDH / CSC:KD1 (H3G)"
Its not telling me there`s a firmware update available so I have a horrible feeling something`s still not quite right but I`ve flashed it twice now and done 2 factory resets.
Would it be easier to find the stock KE7 kernel (forgive me if I`m using the wrong words) in Odin to flash it that way? If I can manually do it then I`d rather do it that way. Only problem is I`ve not yet found any tutorials on doing that, unless its the same (mostly) as the tutorial for debranding, except using a different .tar file (KE7).
Hey.
I was wondering, How do I change my product code from Spain FOP to UK Three H3G
Kies won't update my device because it's on FOP code on Three firmware Is there any way I can restore H3G or use Kies to do it? Would the Emergency Firmware Recovery work for me?
Thanks/ Jamie.
*shameless bump *
I'm not sure if the product code is the only thing Kies checks -perhaps it checks the IMEI as well like LG does.
As far as I can tell, once you've flashed some firmware via Odin you have no hope of ever getting a firmware update from Kies again.
davew said:
I'm not sure if the product code is the only thing Kies checks -perhaps it checks the IMEI as well like LG doe.
As far as I can tell, once you've flashed some firmware via Odin you have no hope of ever getting a firmware update from Kies again.
Click to expand...
Click to collapse
Thanks for replying
I've NEVER used Odin, and don't plan to :L.
I checked the CSC on my phone through the secret code and it clearly says H3G
So im going to install Kies on another computer and see
Because my product code in Registry is GT-S5830OKAFOP
Thanks anyway
I'm sorry, I'd assumed you'd flashed the spanish firmware yourself.
So your CSC and your Product Code don't match through no fault of your own?
davew said:
I'm sorry, I'd assumed you'd flashed the spanish firmware yourself.
So your CSC and your Product Code don't match through no fault of your own?
Click to expand...
Click to collapse
Partially haha, I flashed CM7 last weekend, Didn't like it, and tried to restore to Stock Firmware backup in CMW, which didn't work because of EXT4 FS, So I had to go to GingerReal, which is clearly where the FOP Product code came from, I then discovered how to revert to RFS, and did so, and back to Stock firmware. I haven't changed anything from then though, But yeah my Product Code is found as FOP but CSC is H3G, which is really confusing! :S can you provide any help haha, Not used to all the CSC, Odin and EFS, last phone was the GT540, Simplest phone ever to change rom on! no need to worry about IMEI etc
*#272*IMEI# - To change the salescodes and reset the user data (by blade2011)
If I do this, do you think it'll work? Quite scared of breaking my Ace, so going to make a backup now
I don't fully understand just yet what Kies checks to determine if your firmware is official or not. Flashing a firmware will change your CSC, but not your product code. I think if your Product Code, IMEI, CSC and firmware version don't agree, Kies will assume your firmware is unofficial.
If your firmware is multi-CSC you can change your CSC code with:-
*#272*???????????????#
where ??????????????? is your 15 digit IMEI
It will perform a hard reset though, you'll lose all your user data. The other big problem with this is working out, given a product code, your CSC should be. You could go through the whole process and still not be able to get updates from Kies.
There's a thread here for the galaxy, but how much of that will work on an Ace I don't really know. I haven't tried any of the stuff in the thread.
http://forum.xda-developers.com/showthread.php?t=787163
HTH
Dave
EDIT: I see you got this far already
Yeah, My CSC, Firmware and IMEI should all Agree, because I've flashed the Three rom back, and I checked on my PC which I used to sync my phone with before CM7, the codes are all the same APART from the Product code I'm trying what I posted and what you posted now
EDIT: My firmware is Stock, so will NOT be Multi-CSC, but because it's the Stock ROM, it should have my original Product Code etc right?
Okay. Tried entering the code, but Im given the screen to select Sales Code, but it's stuck on FOP and I CANNOT do anything with the code, Look at the attachment below
I guess (and this is only a guess) that when you restored your backup, your CSC and Product code didn't get changed back to what they should be.
I had no idea that flashing a ROM could change your product code. I knew it would change the CSC, which is why I've been careful only to flash firmwares that match my product code. Even then, I still can't (and have never been able to) get updates through Kies.
Yeah, I was thinking that somethings messed up here, because my CSC is definitely right, (I hope) but my product code is in Spain.. geez :L
So the executive summary is:-
1. Rooted and installed CWM, took a backup
2. Flashed CM7
3. Flashed GingerReal
4. Your product code and CSC were changed to FOP (spain) at some point along this process
5. You restored your backup, and the CSC changed back to H3G but (and this is the important bit) your Product Code is still reading as FOP
What's weird is when I flashed my Ace with Odin, although the CSC changed, the product code did not. I had no idea flashing a ROM could change your product code - that'd cause a problem if you need a warranty repair and its something people really need to be aware of.
My advice - see if the guy that wrote GingerReal has a clue why this might have happened. There could just be a simple file somewhere that holds the product code which you could get to with Root Explorer or ADB. I'm really just guessing though.
I was in your shoes but from no fault of my own - my new Ace wouldn't update from Kies no matter what, so I flashed S5830XWKPW (OXX/TPH) and haven't really looked back. Uninstalled Kies, forgot about it. I have every confidence that if a new stock firmware comes out, it'll make it out in Odin flashable format for everyone
Yeah, pretty much
I know from the Galaxy S forums that the product code is changeable .. I noticed that the guy who actually develops GingerReal comes from Spain and therefore where FOP has came from .. I think its the bootloader though.. because before flashing GingerReal or CM7 I NEVER had the green triangle in the top left when going into Recovery.. and now I do.. so thats tthe only thing left custom, recovery and possibly bootloader, although the kernel is stock as I remember it having Dell in it,
Swyped from my GT-S5830 using XDA App
I NEED someone on Three UK 2.3.3 KPN Stock to take a screenshot of a Kies registry key for me tomorrow to check if I definitely have H3G CSC, and if not.. how to get it back.. I rang Three and they want to send it to Samsung, which is a bad idea as they will see CMW recovery and charge me probably :/
Swyped from my GT-S5830 using XDA App
Jamielawther said:
Yeah, pretty much
I know from the Galaxy S forums that the product code is changeable .. I noticed that the guy who actually develops GingerReal comes from Spain and therefore where FOP has came from .. I think its the bootloader though.. because before flashing GingerReal or CM7 I NEVER had the green triangle in the top left when going into Recovery.. and now I do.. so thats tthe only thing left custom, recovery and possibly bootloader, although the kernel is stock as I remember it having Dell in it,
Swyped from my GT-S5830 using XDA App
Click to expand...
Click to collapse
The triangle you see at the corner is an indication that you're using CF-ROOT or an equivalent .
Forever living in my Galaxy Ace using XDA App
Yeah I know that, would that be the bootloader im using because CF-Root kernel is not installed, and kernel version shows this,
Swyped from my GT-S5830 using XDA App
You can flash 2.2 with multi CSC (i think that KB7 is right one). When phone boot's up, change CSC with *#272*IMEI...#. Phone will reboot, and after that KIES will report the right values and it will update your phone if there is an update.
You can flash 2.2 with multi CSC (i think that KB7 is right one). When phone boot's up, change CSC with *#272*IMEI...#. Phone will reboot, and after that KIES will report the right values and it will update your phone if there is an update.
Click to expand...
Click to collapse
Do you mean S5830XWKB7/MULTI-CSC-OXXKB6 (9th on the list at samfirmware)?
I tried that and still couldn't get Kies to get updates. When I checked my CSC it was what it should have been (TPH).
Yes that one. Did you change CSC with that FW? I tried and it worked. For example, I changed to XEN and after 2 restarts, KIES was able to recognize phone and offer a update.
And of course, are you sure that there is update in your country?
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
its a verizon tablet so thats normal.. u need to change csc is all
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
jmwfl2000 said:
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
Click to expand...
Click to collapse
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Gotcha, so change the CSC first, then flash the matching firmware? What's the best method for changing the CSC on the S7+? This process? https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/
Any suggestions on how to change the CSC? I've hit a wall and haven't been able to find a way to change it and then flash the desired firmware.
elliwigy said:
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Click to expand...
Click to collapse
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
bs3pro said:
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
Click to expand...
Click to collapse
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
jmwfl2000 said:
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
Click to expand...
Click to collapse
jmwfl2000 said:
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
Click to expand...
Click to collapse
dunno wat ur flashing but all the firmware is the same.. theyre all multi csc.. so simply flashing different firmwares wont change csc lol
I don't know if this will help but on some samsung phones you can change the csc by opening the dailer and typing "*#272*IMEI number#"
edit: IMEI must me copied from the about tablet section in the settings. Press on the IMEI for a second and it will be copied to clipboard. Typing the IMEI will not likely not work.
After entering this in the dailer a menu pops up and you can select csc. Note this will usually factory reset the device.
Yes if you try this, please let me know if it works. I have the T878u 5g from Tmobile.
Any update on this? I purchased an SM-T978U (on Samsung website that is t-mobile S7+)
I expected it to not be carrier or network locked but it was locked to the t-mobile network.
Would love to flash an unlocked firmware but I can't find SM-T978U firmware, let alone U1 firmware...... I realize that flashing U1 firmware won't unlock the network but T-mobile support tells me the device can't possibly be truly carrier locked because the IMEI isn't even in their system. So I thought maybe the carrier lock is in their app tied to the system instead of the actual device??
Anyway has anyone found the firmware for these devices? Sammobile doesn't seem to list SM-T978 as a device
These devices don't have a dialer so entering the IMEI method mentioned above won't work unless there is a trick?
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
not sure y u tagged me lol.. i know hiw csc works.. in fact, in my last comment before this one you can see I clearly said just flashing firmware won't change the csc? seems like basically what you said but in a few words
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
Where is this U1 XAA firmware to download? Specifically for the SM-T978U?
RE: jmwfl2000 -I always untick the "Auto-Reboot" box when flashing new TWRP images to prevent stock recovery from being reapplied.After the first boot all should be well.
K3N422 said:
in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
I'm pretty stumped like OP. Where are you finding U1 XAA for Tab S7+? Doesn't seem to turn up anywhere. Would definitely appreciate it if you could provide a link. Thanks.
I tried resetting before flashing and unchecked the auto-reboot but mine still returns to Tmobile. I just want the call and text on other devices feature.
Edit: I go the feature to work without flashing a new firmware but I am still looking for U1 XAA for the tab if anyone found it.
jmwfl2000 said:
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
Click to expand...
Click to collapse
I bought an unlocked Verizon Tab S7, probably same seller. Its brand new, stil has plastic on it. Are you wanting to unlock Tmobile 5G bands?
I want to do a factory reset on my Samsung Galaxy J7 2016 (J710FXXU6CSK1),not previously flashed, however I need to use a password when factory resetting through Settings, which I cannot recover, even after confirming using my email adress. My best bet is to wipe everything, and manually install the firmware through Odin. I did not find the firmware for the exact version I currently have, however I am currently downloading a similar version through updato (J710FXXU6CSK2) . Now,this version is localised for India, and I live in Europe. Would installing this version risk bricking my phone? A barely usable device is better than an unusable device.
I'd like to mention that I have searched for the same issue on XDA , and I have not found anything so far, at least concerning this device/model. Secondly, even though I am not completely new to flashing with Odin(I managed to save a bricked Samsung Galaxy Core II a few months ago),I'm still unfamiliar with how to use Odin,and don't really remember exactly what I did the last time.
1)I heard that specific versions of Odin work on specific models. Is that true? I have "Odin3 v3.13.1_3B_PatcheD.exe" downloaded,will that work for my device?
2)Once(if) I have the firmware downloaded and everything connected ,where should I "put" the firmware on Odin?(It is in the AP box if Iremember correctly, though I could be completely wrong, please correct me if I am)
3)Will I be asked to enter the same password I mentioned earlier if I do it manually?(Through the android boot menu)
4)If I am required to enter a password, is there any way I could bypass it?
5)I know I could have searched for this last question on my own, but if anyone could be kind enough to link me to an Odin tutorial, I would really appreciate it! Last time, I had to gather small bits of how it worked from many different sources.
------------------ said:
I want to do a factory reset on my Samsung Galaxy J7 2016 (J710FXXU6CSK1),not previously flashed, however I need to use a password when factory resetting through Settings, which I cannot recover, even after confirming using my email adress. My best bet is to wipe everything, and manually install the firmware through Odin. I did not find the firmware for the exact version I currently have, however I am currently downloading a similar version through updato (J710FXXU6CSK2) . Now,this version is localised for India, and I live in Europe. Would installing this version risk bricking my phone? A barely usable device is better than an unusable device.
I'd like to mention that I have searched for the same issue on XDA , and I have not found anything so far, at least concerning this device/model. Secondly, even though I am not completely new to flashing with Odin(I managed to save a bricked Samsung Galaxy Core II a few months ago),I'm still unfamiliar with how to use Odin,and don't really remember exactly what I did the last time.
1)I heard that specific versions of Odin work on specific models. Is that true? I have "Odin3 v3.13.1_3B_PatcheD.exe" downloaded,will that work for my device?
2)Once(if) I have the firmware downloaded and everything connected ,where should I "put" the firmware on Odin?(It is in the AP box if Iremember correctly, though I could be completely wrong, please correct me if I am)
3)Will I be asked to enter the same password I mentioned earlier if I do it manually?(Through the android boot menu)
4)If I am required to enter a password, is there any way I could bypass it?
5)I know I could have searched for this last question on my own, but if anyone could be kind enough to link me to an Odin tutorial, I would really appreciate it! Last time, I had to gather small bits of how it worked from many different sources.
Click to expand...
Click to collapse
Hi,
If your device is working correctly i suggest to do a factory reset from recovery menu instead of flashing again. thats simple, no password required. https://www.verizon.com/support/kno...old the Volume,Select Wipe data/factory reset.
you have to flash firmware specific to country. you can find a specific firmmware here - https://samfw.com/firmware/SM-J710FN
Even if you flash a different firmware, you may not get network, but that can be corrected by flashing a correct firmware again.
you have to extract the firmware downloaded and specify files in odin. https://www.youtube.com/watch?v=p6gyc5wsuE0&ab_channel=GSM-ABC
I have been searching high and low across the internet for many days now and can't seem to find an answer to this issue.
Previously, Samsung devices could use a dialer code to enter the pre-configured menu of the CIDmanager to change the CSC using either of two codes containing "272". As of now, neither of these codes work anymore to enter this menu. Things like quickshortcutmaker don't work due to issues with permissions.
ODIN as well, does not work to flash other CSC firmware, and I have seen elsewhere on the xda forums that the new firmware must be flashed along with changing the CSC.
I have tried things like cheetah tool and magma tool, (chimera tool being much too expensive) and even an unlocking service that states explicitly that they are able to work with my CSC (TMK), yet the credits for the tools are impossible to get, and the unlocking service refuses to respond to my inquiries about payment, as their websites interactions with PayPal are totally broken.
What I need to know is how I can flash the stock XAA CSC firmware using TWRP because currently ODIN will not allow it.
I have stock firmware in two different compatible baseband, but these firmwares are naturally tarballs.
I can't flash tarballs with TWRP.
How can I make the 5 ODIN flashable firmware tarballs (CP, AP, CSC, BL, and the other one.... forget off the top of my head) into TWRP flushable ZIP files?
I have searched endlessly for days and all I come across are stupid answers that don't answer the questions that people have asked.
"Flash with odin" is NOT an answer when someone asks "how to flash these files with TWRP".
Edit: clearly I'm missing something, but I have no clue what that is.
Update: some patience and installing apps I've never used (whatsapp and telegram), which for some esoteric reason are the only means of support for the professional tools, i was able to find a company that sold credit for cheetah tool sim killer pro, through trial and error going through the official list of companies that are ALL supposed to sell the credit, and would sell less than $100 at a time, 10 being minimum for this company who's name I forget, and who's buying process is like pulling teeth by tieing a string and sinker to each one and waiting for gravity to do the trick. Seriously never seen a company that made it so hard for me to give them my money, as they all want it in crypto (for supposedly legal businesses...), and I was eventually able to pay with my debit card, but charged about 2 percent of the total as a special fee. I got 11 credits for the sim killer pro, and the CSC change was only 1 credit, which is only 89 cents, and also which somehow never got charged to my account after the csc change, so hey, In the end, totally worth the 0 i actually paid out to change the csc, but unfortunately did not actually carrier unlock the phone.
So I broke down and spent the $80 for a Samsung license for chimera tool.
(at this point, I've spent so much money to unlock this phone I could have bought a brand new unlocked one, but it's the PRINCIPLE that matters to me in that circumstance, soo.....)
The chimera tool is really awesome software, supports nearly any samsung ever made, including specifically my model, for flashing, imei, csc, etc.
Only to find that using it to flash ONLY this specific model still gives secure check failure for pit, aboot, modem, etc so I cannot flash any version of it at all on this phone, and fails at csc changes.
I eventually got a partial flashing by using the pit file that was already on the phone,and using that with my new firmware. It's sort of unlocked. It's very goofy. It was a10 before now its Android 11.