Related
First of all, sorry if this has been answered here, I simply can't find a definitive answer for our S6, let me explain better.
As you may know, I'm not a newbie here or in other forums, I've rooted most of my phones (Not this one) and have installed custom roms dozens of times to all of them, BUT, I'm definitely a newbie about what I need here, I'm trying to see if I can change my SM-G920i region from XSA (Australia) to any other one, India in this case. I have read tons of threads and posts and that's what is confusing me, in some threads there are people saying that they did it and is working great, in that same threads there are people saying that they did it but Knox got tripped, there are others that say that the device is soft bricked and others are saying that they have read somewhere that changing the CSC from it's original one may brake future Samsung pay.
So, this phone is paid by my office, they allow me to do what I want to it while I'm able to just put it back as it came from factory, so that means that I can root it if it doesn't trip Knox, that I can install anything while I can simply go back anytime they need me to, and obviously, Samsung pay works when it finally comes. With this in mind, can somebody answer me a couple of questions?
1-) I know it's possible to do it, but is it true that by doing this I'll have Samsung pay issues? I doubt that knox will be tripped if I do it with odin, but besides knox, is there any possibility that Samsung Pay will not work in certain regions (India in this case) and that's why some are saying that it will break it?
2-) If I download the firmware and flash it via Odin, I'm reading that it won't brick the phone is done via Odin, but in worst case scenario I assume that I can always go back to original one and it gets factory reset, am I right?
3-) If I flash it correctly as I expect an it doesn't brick, does this means that it will change PDA and CSC versions all together, that it will basically become a device from the new flashed region? So if I flash the India one to my XSA (Australia) now it will work completely as an India device and should get future OTA like the rest?
Again, sorry if this has been asked and answered but going back a lot of pages here can't give me definitive answer, thanks in advance for those of you kind enough to answer to this.
Flash a G920i ROM via odin other than your own region/country:
http://www.sammobile.com/firmwares/database/SM-G920I/
roydok said:
Flash a G920i ROM via odin other than your own region/country:
http://www.sammobile.com/firmwares/database/SM-G920I/
Click to expand...
Click to collapse
Thanks.
In another thread that I have posted (Brazilian one) I was replied to, so because of that I decided to do it, so far everything is working great as expected. Mine was an Australian baseband (XSA), only thing you I noticed is that when I connect it to Smart Switch app for PC or MAC it will still detects the Original CSC, I was curious about it and installed Phone info apk and it shows correctly the information, both PDA and CSC are now from India but it shows that the Original CSC was XSA (In my case), Firmware's CSC code is INU (India) and Active CSC code it says XSA/INU, so I'm assuming that it's showing multiple CSC.
Does somebody know if having the Active CSC showing XSA/INU causes future OTA issues?
After flashing a ROM its good practice to go to recovery mode and do a full wipe of cache and full reset to change CSC to the default of the ROM you flashed.
roydok said:
After flashing a ROM its good practice to go to recovery mode and do a full wipe of cache and full reset to change CSC to the default of the ROM you flashed.
Click to expand...
Click to collapse
Well, in that case I think I will pass for now, as I did a Full wipe cache and Full reset before the Flash but just did a Wipe cache after I flashed it.
The issue is that I basically just finish setting everything back as it was before (about 3 hours and I still haven't set my Contacts Ringtones and Accounts links) so begin again it's a PITA. Once I finish this I'll do a full nandroid backup to have everything as I want, but if I do the Wipe Data/Full Reset and then restore from the Full backup, does this put everything as it was including CSC again? I've been always confused about how deep this restore goes in the system files. Do you know about it?
Thanks.
Try restoring from your backup after the full wipe from recovery. If everything works then you should be ok. Otherwise start from scratch and reinstall everything one by one.
Will try that later today, thanks.
Goodluck.
roydok said:
Goodluck.
Click to expand...
Click to collapse
I tried that and nothing, still the same, then I decided to remove the Re-activation Lock in Find My Mobile settings, and after that and enter to recovery mode, it changed the CSC to India, so for those of you with same issues, remember about Re-activation lock.
Thanks for your help.
Did you have a SIM card inserted when you flashed your ROM with removed reactivation lock?
I had the SIM card on the phone today all the time as I forgot to bring with me the SIM removal tool and didn't have anything to open the Sim card tray, but last night I didn't have the Sim card installed when I flashed the ROM.
So today after I did the Wipe cache Partition and Data and saw that it still had the same issue, I flashed a UK ROM into a SM-G925f that had some African country ROM (have never heard of it before in my life but for the name it sounded like an African country), anyways I did that and everything went great, so that's when I thought what was different between the devices and then I remember that I had turned on the Reactivation lock in my S6 and not in the S6 Edge, so I turned it off, then went to Recovery mode and for my surprise the CSC was already changed without any other reset or anything.
erasat said:
I had the SIM card on the phone today all the time as I forgot to bring with me the SIM removal tool and didn't have anything to open the Sim card tray, but last night I didn't have the Sim card installed when I flashed the ROM.
So today after I did the Wipe cache Partition and Data and saw that it still had the same issue, I flashed a UK ROM into a SM-G925f that had some African country ROM (have never heard of it before in my life but for the name it sounded like an African country), anyways I did that and everything went great, so that's when I thought what was different between the devices and then I remember that I had turned on the Reactivation lock in my S6 and not in the S6 Edge, so I turned it off, then went to Recovery mode and for my surprise the CSC was already changed without any other reset or anything.
Click to expand...
Click to collapse
can you post a screen of CSC page of Phone ** info ** just for reference?
I see you said that CSC changed to India, but Active CSC or also Original CSC?
What I mean is that, now I have a S6 which has Original, Active CSC as MRU...I'd like to put a European fw on it since I'm based in Europe (got this Middle East / Africa phone just because Dual sim it's not available in europe) but I'm in doubt if putting an european fw will still show that CSC has changed from original one and maybe OTA updates won't work.
thanks
Changing csc!!!
I succesfully installed a G920I indian INU rom in my device which had a XSA rom but when i go to recovery it still shows as XSA ....How do i change that to INU?
Hi i am using a galaxy s6edge+ and i am really struggling with the region lock. I have tried a few options of the factory full reset changing the Apn's to the ones needed and using different sim cards.when it used to go into emergency mode "h+" now it won't connect to any internet at all. Can i possibly have any basic assistance with the rom and resetting options to change the csc when i do a hard reset the csc says it's 'multi'. what does that mean? Any region unlocking help would be appreciated so much!
Thanks guys
Hello
I have the official version of Android 5.1.1 SK region and would like to upload Officiální Android version 5.1.1 CZ region. Flash Odin FAIL. Please someone help? Thank you.
JABV90 said:
Hello
I have the official version of Android 5.1.1 SK region and would like to upload Officiální Android version 5.1.1 CZ region. Flash Odin FAIL. Please someone help? Thank you.
Click to expand...
Click to collapse
Had a similar issue yesterday when I tried to update my rooted 5.0.2 to an official 5.1.1. I have used ODIN many times before since SGS3, and back then you were able to mix your system image from other regions, but that apparantly has been locked down by Samsung. Now you can only update an official version of the rom if it exactly matches your existing region. Because you updated your SK international S6 and tried a region set rom from Czech it most likely failed towards the very end of flash with "FAIL".
Your options are: 1) you download the 5.1.1 version for your region in ODIN format from SAMMobile or 2) you use Smart Switch and let it do it for you - in this case you will need to know the SN of your phone as it is used for verification.
Samsung has locked down the serial number with the regions that come with it. So if you have to install, you should update it or use same region odin file. There is a way to break this chain if you are rooted and some additional files are being used in the odin but I am not completely sure as I have not tried it yet. But there are chances that you may void your warranty if you try that or the worse hard brick as it can sometimes change your serial number if not used properly. but I wouldn recommend that. I'll let you know once I understand the usage correctly.
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
ok
sinbrad said:
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
Click to expand...
Click to collapse
Is your phone international unlocked out of the box? I dont believe it was, because as far as I've read international unlocked phones come with "unbranded" firmware. The unlocked ones I know can be pretty much flashed with "any" international firmware, which is what you are trying to do.
If you dont know for sure. Odin the stock German Vodaphone. Let the phone boot. Boot back to stock recovery, then factory reset and clear cache.
Then let the phone boot...Download phone info app by vndnguyen (free version is fine)...Open the app, go to CSC Code tab. Then that will tell you the active CSC code and your firmware CSC code...you are looking for the line that says Available CSC Codes. If it only lists German Vodaphone (VD2), then I believe you are stuck til the phone is unlocked.
Anyone, jump in here if I'm mistaken. I am using this as reference as, I've checked my G920F. Mine is unlocked tho and I can flash any firmware from any region with no problem. Hopefully I've answered your question.
I had no luck with the firmwares on the firmware page either.
If you are on OI9 check http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533
And try flashing the first stock firmware https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list (not the android M one!) via ODIN.
Basic process is:
Download the above file, extract, there should be 4 files inside (AP,BL,CP,CSC), simply select each one to go in the relevant box on ODIN, then go into download mode on your phone and click start...
N.B. Be aware that the above firmware contains a PIT file which will reformat and resize the partitions on your phone, so make sure you have a copy of the stock firmware that works before trying the flash (i.e. the one which Smart Switch downloads). You can grab it from your windows %TEMP% directory during the smart switch download (it first downloads a file to TMPxxx, then extracts it into a directory of the same name, its these files you want. They should be the four files beginning with the type of ODIN file you are flashing (AP,BL,CP,CSC). The files get deleted after the firmware has flashed so make sure you watch the process. If things go wrong you can re-flash these files via ODIN
As far as I was led to believe and when I purchased the phone it did state factory unlocked. I was able to put in any sim when I received it and didn't have to go through any aftermarket unlock process?
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
So, seems this is not uncommon?
ok the way to do it is download this file
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
its BTU firmware of 5.1.1
and flash this firmware you'll have 4 files AP,BL,CP,CSC,put it in the respective boxes in odin.I have tested this right now and it works
Press "thanks" if i have helped
Well downloaded the app for CSC info and it states available CSC codes are...
ATL, AVF, CNX, CYV, MOB, MTL, OMN, SIM, SWC, TCL, VD2, VDC, VDF, VDH, VDI, VGR, VIP & VOD
Any ideas?
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
sinbrad said:
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
Click to expand...
Click to collapse
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
No probs here
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
sd_N said:
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
Click to expand...
Click to collapse
Which file and which method?
aaronjp said:
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
Click to expand...
Click to collapse
Ok, Got it this time, all four files. Will give the method above a go and if it fails at least I've got the stock firmware to fall back on?
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
sinbrad said:
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
Click to expand...
Click to collapse
Glad you are sorted
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Paachan said:
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Click to expand...
Click to collapse
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
Well this reply isn't really that helpful...
1st she doesn't care anymore because as mentioned she already has a new phone and said I can just keep it or throw it away.
2nd even if it's bricked there are ways to get it back to working, I soft bricked my old HTC M8 once and restored it.
3rd If you're a noob with this just don't reply, I've never had experience with Samsung phones before thats why I'm seeking for help, if it comes to HTC or LG phones I usually get things done myself. Not in this case tho.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
*Detection* said:
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
Click to expand...
Click to collapse
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
audit13 said:
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
Click to expand...
Click to collapse
so in this case with the DBT version it's just the default customization file from Samsung, am I right?
Flashing either Home_CSC or CSC didn't had any effect on the S7 tho, it's still stuck in Boot loop with FRP Lock.
Let's say the phone is soft bricked, is there any way to get it back working, so I can flash the stock firmware afterwards`?
Paachan said:
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
Click to expand...
Click to collapse
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
*Detection* said:
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
Click to expand...
Click to collapse
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
audit13 said:
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
Click to expand...
Click to collapse
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Sounds like you have tried all you can on your own. Maybe take it to a cell repair shop and have them try to force flash the phone using hardware such as an octopusbox?
Paachan said:
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
Click to expand...
Click to collapse
Yep G930F is International Exynos so you should be good
Some people have problems downgrading from 7.0 to 6.0, what I meant was flash the latest available firmware for DBT, which is 7.0
2018-04-23
Germany
7.0
G930FXXS2DRDI
As above, the bootloader can be a pain to downgrade, so always try unbricking with the latest firmware available
Same process as I posted above, only using the firmware in this post ^^
Good luck
---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------
Paachan said:
I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an indicator)
Click to expand...
Click to collapse
Yea that doesn't sound good, possibly a faulty motherboard, they seem to be quite a high % of hardware faults of the S7 on XDA, at least that is the outcome of sending them in for repair, but also could be the repair centres way of making the most £
Paachan said:
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Click to expand...
Click to collapse
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Matty1993 said:
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Click to expand...
Click to collapse
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
{
"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"
}
Sorry for my late reply!
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
I'm not 100% sure about this, but that firmware states S2 not U2
See here, my BL is B:2 but all of the firmware files I can successfully flash are U2
Matty1993 said:
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Click to expand...
Click to collapse
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Also maybe download U2 firmware aswell as S2 firmware
Matty1993 said:
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Click to expand...
Click to collapse
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
*Detection* said:
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
Click to expand...
Click to collapse
Or that also maybe yeah try U2 firmware instead of S2 as far as im aware S2 is the first of the B:2 binary updates
I bought the S22 ultra Korean version with KT branding. I really don't like their bloatware.
I downloaded the non-branded Korean firmware (KOO) and also the non-branded US firmware (XAA).
I tried to flash both using Odin but no luck. It continuously shows the "Secure check failed: PIT" error.
What am I missing?
My first priority is to flash the US non-branded firmware. Both of the models are Snapdragon. So, is it possible to do so?(2nd question)
Original Baseband: S908NKSU1AVCH
Downloaded Korean Baseband: S908NKSU1AVCK_S908NOKR1AVCK_KOO
Downloaded USA Baseband: S908U1UEU1AVC8_S908U1OYM1AVC8_XAA
Odin: 3.14.1
update: Finally successfully flashed Korean non-branded firmware. But CSC didn't change. It is still KT branded one. What did I miss?
You have to look for chimeratool or Samkey to change csc.
did you flash the CSC file ? or just the AP
gav83collins said:
did you flash the CSC file ? or just the AP
Click to expand...
Click to collapse
I used all the four files (BL, AP, CP, and CSC). I didn't use HOME_CSC, used CSC instead.
yeah i was just checking, i dont know then did you try chimeratool or Samkey
gav83collins said:
yeah i was just checking, i dont know then did you try chimeratool or Samkey
Click to expand...
Click to collapse
Sorry, I didn't try Samkey or chimeratool. Is it possible to change CSC by flashing the ROM via odin?
well usually, you can choose to just flash the csc on its own, i dont know why its not working without insulting you with questions like "is usb debugging" enabled lol
gav83collins said:
well usually, you can choose to just flash the csc on its own, i dont know why its not working without insulting you with questions like "is usb debugging" enabled lol
Click to expand...
Click to collapse
Haha, there is nothing to get insulted about. We, humans, are prone to make silly mistakes. I didn't make this mistake this time maybe.
Checklist:
1. USB debugging enabled
2. Samsung driver reinstalled
3. Downloaded Odin's latest version
4. OEM lock disabled
5. Bootloader lock enabled/disabled (tried both).
I was able to flash the firmware once but didn't change CSC. But don't know why.
Then I tried to flash the firmware again but didn't work. It fails to write. Tried more than 20 times with different configurations but no luck.
have you tried the patched versions of odin ? check my thread "here" for links
Thank you for the patched app. If I used patched Odin, will it trigger Knox?
And can I flash US non-branded firmware to Korean branded phones?
Both are single sim snapdragon phones.
i would assume so, but you know what presumption did......... if its a stock rom i dont think it will trigger knox, aslong as its an unmodified official release firmware you should be ok
ive been out of the game for a while due to the pleasure of her majesty, so wait to see what other people say that have been more current than me
I have tried using patched Odin. But it's stuck at Setup Connection.
the only other thing im thinking is maybe there is an error in the download, back in the day they used to come with md5 checksums, they dont seem to now, how confident are you the download isnt corrupted ? have you tried to extract it to see that it unpacks properly
gav83collins said:
the only other thing im thinking is maybe there is an error in the download, back in the day they used to come with md5 checksums, they dont seem to now, how confident are you the download isnt corrupted ? have you tried to extract it to see that it unpacks properly
Click to expand...
Click to collapse
Finally, I was able to flash using Odin. The problem was I tried to flash the US version first which returns with PIT error. But then I tried to flash Korean ROM without restarting the phone. Which caused the problem. But if I flash with a fresh start inside download mode, it works fine.
But the pit error problems are still there for the US ROM. Is there any way to flash US ROM on Korean model?
Thanks a lot for all the replies.
nazmulnsu said:
Finally, I was able to flash using Odin. The problem was I tried to flash the US version first which returns with PIT error. But then I tried to flash Korean ROM without restarting the phone. Which caused the problem. But if I flash with a fresh start inside download mode, it works fine.
But the pit error problems are still there for the US ROM. Is there any way to flash US ROM on Korean model?
Thanks a lot for all the replies.
Click to expand...
Click to collapse
ive only ever owned australian and uk devices, so i couldnt tell you with any certainty, but one would assume if its the same chipset / processor the region of the rom shouldnt make any difference
Yes, I assumed that too. But seems like Samsung added some extra layer of security for different pit files. I tried many ways to flash US firmware. But, it always says "Secure check fail: pit".
Hope someone can crack that. Thanks a lot for your kind replies.
However, I was able to flash KOO ROM a few times but it didn't change the CSC. My phone still remained KT branded.
I tried to cleared cache and did factory reset before booting and after flashing, but no luck.