Database Info

Is my phone bricked?

Hi guys,
I'm posting searching for some assistance. I have a Galaxy S6 SM-G920i that I've been trying to flash a stock rom using Odin with no success.
I've tried flashing 5.02 versions, but read here that it won't work since it has an older bootloader.
Tried flashing 5.11 versions, but get stuck in boot screen/samsung logo.
Tried 6.01 versons, but get a DRK error after flashing.
Aldo tried with different versions of Odin, to no avail.
What else can I do to get my phone to work? I've tried ZTA and ZTO rom versions, but there seem to be no difference.
Also, I didn't make a backup of any folder, unfortunately. Read about many people that managed to get their phone working again, can anyone shed some light?
Thank you very much.
Edit: some more details:
- Odin v3.09 apparently gets stuck at "NAND Write Start!!" everytime. I'm trying with v10.6 and 12.3.
- Already tried changing the USB port, but I don't have another PC to try it.
- Tried flashing these roms already:
5.02
G920IDVU1AOD1_G920IZTO1AOD1_G920IDVU1AOD1_HOME.tar
G920IDVU1AOD1_G920IZTO1AOD1_G920IDVU1AOD1_HOME.tar
5.11
G920IDVU3DOJ6_G920IZTO3DOJ6_G920IDVU3DOJ6_HOME.tar
G920IDVU3DOJ6_G920IZTA3DOJ6_G920IDVU3DOJ6_HOME.tar
6.01
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
G920IDVS3EPK2_G920IZTO3EPIF_G920IDVU3EPIF_HOME.tar
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar
G920IDVS3EPG4_G920IZTO3EPFC_G920IDVU3EPG3_HOME.tar
G920IDVU3EPL6_G920IZTA3EPL1_G920IDVU3EPL1_HOME.tar

Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920I
Region: INU
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Once it finished, you'll have DRK problem again.
To fix that, download and extract this;
https://download.chainfire.eu/736/CF-Root/CF-Auto-Root/CF-Auto-Root-zeroflte-zerofltedv-smg920i.zip
Open the "Odin3-v3.10.6" file in extracted zip folder, then press AP and select "CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5"
Once you've set the file to Odin, connect your phone to your PC in download mode and click "Start" on Odin.

Thanks for the help, I'm going to follow those steps!
But one question: why should the region be INU? Shouldn't it be ZTO or ZTA (I live in Brazil, it's a brazilian model)?

Thanks, it worked!
The phone is running again, but there is still a problem: when I try to use 3G/4G it doesn't work, and if I try to make a call, it says it's "not registered to network".
I tried the same chip on another phone and it was working, so it's not a faulty chip. How can I fix this?

luckysquall said:
Thanks, it worked!
The phone is running again, but there is still a problem: when I try to use 3G/4G it doesn't work, and if I try to make a call, it says it's "not registered to network".
I tried the same chip on another phone and it was working, so it's not a faulty chip. How can I fix this?
Click to expand...
Click to collapse
Is your IMEI still intact?

No, it's not the same number as the back of the phone. It shows 3500000000006. How do I return it to it's original value?

luckysquall said:
No, it's not the same number as the back of the phone. It shows 3500000000006. How do I return it to it's original value?
Click to expand...
Click to collapse
I think the IMEI was written with a box (like Z3X) and it needs a patched modem firmware. You flashed stock modem while flashing the stock ROM, thats why the "IMEI" can't read by modem.
So, you need a box (like Z3X) to patch the modem again.

I see... so there's no way to change the IMEI without a box?

luckysquall said:
I see... so there's no way to change the IMEI without a box?
Click to expand...
Click to collapse
Yes, there's no way to change the IMEI without a box.

ahh the ole efs corruption. Seems to be common on this phone, and is essentially the worst thing that can go wrong from flashing :/

G920F no wifi after ODIN update 5.1.1 -> 7.0 stock

Hi
my G920F was 5.1.1 but OTA update after download 1.8gb of new firmware didn't finish update.
wifi work OK in 5.1.1
i used odin 3.12.3 and FIRMWARE XEO: G920FXXU5EQD7_G920FXEO5EQD1_G920FXXU5EQCD_HOME.tar.md5 after this phone powerON normally but can't enable wifi, it stuck on "enabling..." info but don't switchOFF just ...enabling..... and nothing more. Is switch off after 2minutes not faster like i saw on youtube videos.
i tried to use OTA but then phone said this update was made by: "unauthorized..bla bla... and USE: Smart Switch to download correct firmware"
i used smart swich tool which again download 7.0 firmware and upload it with ERASE option but nothing change still WiFi can't be enabled but bluetooth, network both work ok
wipe via recovery also done
now firmware flashed by smart switch is:
AP: G920FXXU5EQD7
CP: G920FXXU5EQCD
CSC: G920FXEO5EQD1
maybe i should use another firmware via odin with different modem?

psg said:
Hi
my G920F was 5.1.1 but OTA update after download 1.8gb of new firmware didn't finish update.
wifi work OK in 5.1.1
i used odin 3.12.3 and FIRMWARE XEO: G920FXXU5EQD7_G920FXEO5EQD1_G920FXXU5EQCD_HOME.tar.md5 after this phone powerON normally but can't enable wifi, it stuck on "enabling..." info but don't switchOFF just ...enabling..... and nothing more. Is switch off after 2minutes not faster like i saw on youtube videos.
i tried to use OTA but then phone said this update was made by: "unauthorized..bla bla... and USE: Smart Switch to download correct firmware"
i used smart swich tool which again download 7.0 firmware and upload it with ERASE option but nothing change still WiFi can't be enabled but bluetooth, network both work ok
wipe via recovery also done
now firmware flashed by smart switch is:
AP: G920FXXU5EQD7
CP: G920FXXU5EQCD
CSC: G920FXEO5EQD1
maybe i should use another firmware via odin with different modem?
Click to expand...
Click to collapse
Make times before a full wipe.
If that does not help, then load a 4tlg firmware with SamFirm down, which you also then with Odin flasht.
Example Picture:

Thanks for reply. I will test it but also could you give me a link to this samfirm tool which you used on screen shoot?

psg said:
Thanks for reply. I will test it but also could you give me a link to this samfirm tool which you used on screen shoot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Download

You had right, today (I left phone alone for weekend) I made hard reset again (via recovery) and wifi starts to work again. This is very strange I've never face such thing before.

I can't flash any firmware into my G930F - Please Help!

Hi Guys,
I have a British Galaxy S7 (SM-G930F). I flashed (using the latest ODIN) a Dutch firmware on it that I downloaded from sammobile, but during the proces it was stuck on system.img. The phone doesn't start anymore. I triend to flash back the original firmware but it also was stuck on system.img. I also tried other firmwares, but no luck. The only thing I can do with the phone is getting to the Download mode.
I have done a lot of research online to get it working but no chance. The phone had FRP LOCK before I flashed it. Does that cause the problem?
Could you please advise me at this matter? It is really frustrating.

Hello,
Use Smart switch for restore, there're many tuto on Youtube
Smart Switch is app by samsung, it's available on their website.

zamalia59 said:
Hello,
Use Smart switch for restore, there're many tuto on Youtube
Smart Switch is app by samsung, it's available on their website.
Click to expand...
Click to collapse
I have tried that but smartswitch does not recognize the phone at all :$

What version of ODIN are you using?
Sent from my SM-G930F using Tapatalk

I have noticed you are using DRA9 firmware. You need to use software that also has bootloader in same version. Any other will not work.

Cholek3 said:
I have noticed you are using DRA9 firmware. You need to use software that also has bootloader in same version. Any other will not work.
Click to expand...
Click to collapse
Is that new since DRA9?
First I've heard for the unlocked G930F, always been able to flash any firmware to it regardless

coto39 said:
What version of ODIN are you using?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I used ODIN 3.12.3 and 3.12.7 and I got the same result with both.

Cholek3 said:
I have noticed you are using DRA9 firmware. You need to use software that also has bootloader in same version. Any other will not work.
Click to expand...
Click to collapse
I tried to flash the original firmware back but no luck.
United Kingdom (H3G) - G930FXXS2DRA9 (7.0)
I assume that this one has the same bootloader version.

*Detection* said:
Is that new since DRA9?
First I've heard for the unlocked G930F, always been able to flash any firmware to it regardless
Click to expand...
Click to collapse
How do you flash firmware then if you just have access to the Download mode on a phone and FRP LOCK is ON?

From what I've read FRP only affects the system and your ability to use android and access the partition data after performing a Factory Reset from outside the system (using for example a custom recovery). It should not stop you from flashing a rom in Download mode. I remember myself being in the same trouble as you are, with system getting stuck while flashing. I can't remember how I solved it. I'll search my chrome bookmarks and report back.
Have you tried changing the usb port (the one your are connecting the phone to) and/or the usb cable?
Sent from my SM-G930F using Tapatalk

riffina said:
How do you flash firmware then if you just have access to the Download mode on a phone and FRP LOCK is ON?
Click to expand...
Click to collapse
Same way you would if FRP lock was off, as that is the way to fix FRP lock
ODIN 3.12.3 or newer
Put phone in download mode
Connect to PC USB
Check Re-partition in ODIN options if changing CSC (Might be an idea anyway)
Flash AP, CP, BL and CSC together
Allow phone to reboot

*Detection* said:
Is that new since DRA9?
First I've heard for the unlocked G930F, always been able to flash any firmware to it regardless
Click to expand...
Click to collapse
Newest bootloader (DRA#) locks phone for changing csc and downgrade, but that mainly fails at loading "param.bin" in odin. There is still a possibility to change CSC or downgrade, but you have to mix and match two different firmwares.
riffina said:
I tried to flash the original firmware back but no luck.
United Kingdom (H3G) - G930FXXS2DRA9 (7.0)
I assume that this one has the same bootloader version.
Click to expand...
Click to collapse
Try flashing BTU then.
coto39 said:
From what I've read FRP only affects the system and your ability to use android and access the partition data after performing a Factory Reset from outside the system (using for example a custom recovery). It should not stop you from flashing a rom in Download mode.
Click to expand...
Click to collapse
That is totally correct.

Cholek3 said:
Newest bootloader (DRA#) locks phone for changing csc and downgrade, but that mainly fails at loading "param.bin" in odin. There is still a possibility to change CSC or downgrade, but you have to mix and match two different firmwares.
Try flashing BTU then.
That is totally correct.
Click to expand...
Click to collapse
I have just tried to flash BTU (G930FXXS2DRAA)... I got the same result as by the original firmware. See attachement

Next step... Another computer.

*Detection* said:
Same way you would if FRP lock was off, as that is the way to fix FRP lock
ODIN 3.12.3 or newer
Put phone in download mode
Connect to PC USB
Check Re-partition in ODIN options if changing CSC (Might be an idea anyway)
Flash AP, CP, BL and CSC together
Allow phone to reboot
Click to expand...
Click to collapse
Do you mean that I have to Check re-partition? I thought that I'm not supposed to do that!
I tried to flash just the AP, but still the same problem. see attachment.

In case it helps somebody to see the problem, I took a picture of the info I see on the Download mode. See attachment.

That System Status: custom makes me wonder if this could be the issue? That should not really have anything to do with it, but did you try doing "Wipe Cache Partition" and "Wipe Data/Factory reset" in recovery?

Cholek3 said:
That System Status: custom makes me wonder if this could be the issue? That should not really have anything to do with it, but did you try doing "Wipe Cache Partition" and "Wipe Data/Factory reset" in recovery?
Click to expand...
Click to collapse
Tried it. No luck!

Hi Guys,
I have tried other USB-cables... I have tried 4 of them and one them solved the issue.
I can now conclude that the USB-cables I was using were not good.
Thanks for the answers guys.

Well. nice that you found the culprit. Try to buy an official USB cable from one of the Samsung Service Centers near you. The offcial cable is cheap.. like 5-6 USD the 1m long and 8USD the 1.5m long ones
Sent from my SM-G930F using Tapatalk

Samsung Galaxy S7 - Germany (DBT) - Custom Binary FRP Lock workaround

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

Question Secure check failed: PIT during firmware flash via Odin.

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.