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
Related
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,
I am new to this site so sorry if I'm doing something wrong. My Dad recently somehow (soft?) bricked his S7. Sometimes it gets to the lock screen, but then completely freezes after a few seconds and it has to be forced off. Other times it has given me a black screen with the error:
Bootloader exception
[ RST_STAT = 0x1000000 ]
Exception: do_handler_sync: UNKNOWN(esr: 0x2000000)
! @ @ @ @ D @
pc : 0x8f000a00 lr: 0x8f000048 sp: 0x0206f (cut off here)
'
And other times it has frozen at the boot screen and the screen has become pixelated.
So, after trying Kies (useless), waiting 24 hours and attempting to connect it to adb and fastboot (which I presume isn't really possible), I have resorted to using Odin to flash TWRP 3 onto the phone. However, when I try to flash the .tar (twrp-3.0.0-0-herolte.img.tar and also the latest one), no matter what USB port or cable or PC I use, it always goes straight to "NAND Write Start!!" and goes no further.
Any help would be appreciated as my Dad needs his phone back ASAP.
Thanks.
Side Note: I'm flashing it so I can recover his data, then I'm going to flash the factory firmware onto it.
MCSulphate said:
Hello,
I am new to this site so sorry if I'm doing something wrong. My Dad recently somehow (soft?) bricked his S7. Sometimes it gets to the lock screen, but then completely freezes after a few seconds and it has to be forced off. Other times it has given me a black screen with the error:
Bootloader exception
[ RST_STAT = 0x1000000 ]
Exception: do_handler_sync: UNKNOWN(esr: 0x2000000)
! @ @ @ @ D @
pc : 0x8f000a00 lr: 0x8f000048 sp: 0x0206f (cut off here)
'
And other times it has frozen at the boot screen and the screen has become pixelated.
So, after trying Kies (useless), waiting 24 hours and attempting to connect it to adb and fastboot (which I presume isn't really possible), I have resorted to using Odin to flash TWRP 3 onto the phone. However, when I try to flash the .tar (twrp-3.0.0-0-herolte.img.tar and also the latest one), no matter what USB port or cable or PC I use, it always goes straight to "NAND Write Start!!" and goes no further.
Any help would be appreciated as my Dad needs his phone back ASAP.
Thanks.
Side Note: I'm flashing it so I can recover his data, then I'm going to flash the factory firmware onto it.
Click to expand...
Click to collapse
Hi mate
First what s7 model do you have?
Make sure you are using the latest odin?
oding settings?
flash same or newer firmware on the phone
What files are flashing?
Check this thread is a nice guide for flashing stock firmware
O
MAX 404 said:
Hi mate
First what s7 model do you have?
Make sure you are using the latest odin?
oding settings?
flash same or newer firmware on the phone
What files are flashing?
Check this thread is a nice guide for flashing stock firmware
O
Click to expand...
Click to collapse
Hey.
I can't check the model as the phone is bricked. All I know is there are only two versions and I'm pretty sure it's not Korea. I'm not flashing any firmware, because I want to get his data off the phone and I'm pretty sure flashing firmware will erase user data. Just trying to get TWRP onto the phone. Odin settings: F. Reset Time ticked, nothing else. Odin version: Odin 3 v3.09. Flashing the .img.tar file as specified in my post.
Thanks.
MCSulphate said:
Hey.
I can't check the model as the phone is bricked. All I know is there are only two versions and I'm pretty sure it's not Korea. I'm not flashing any firmware, because I want to get his data off the phone and I'm pretty sure flashing firmware will erase user data. Just trying to get TWRP onto the phone. Odin settings: F. Reset Time ticked, nothing else. Odin version: Odin 3 v3.09. Flashing the .img.tar file as specified in my post.
Thanks.
Click to expand...
Click to collapse
hi mate
there are more than two versions of S7...... how you know you are flashing the right image? at least you know if you have an Exynos version?
If the phone is bricked how you plan to recover the data the recovery alone may not give you access to the rest of the system and with a custom rom you may have to wipe ( format) the data partition to get access to it ( to disable samsung encryption)
there is a newer odin 3.12.3 try that
MAX 404 said:
hi mate
there are more than two versions of S7...... how you know you are flashing the right image? at least you know if you have an Exynos version?
If the phone is bricked how you plan to recover the data the recovery alone may not give you access to the rest of the system and with a custom rom you may have to wipe ( format) the data partition to get access to it ( to disable samsung encryption)
there is a newer odin 3.12.3 try that
Click to expand...
Click to collapse
All I know is that this is shown when I boot into recovery:
Android Recovery
MMB29K.G930FXXU1BPHJ
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1BPHJ
user/release-keys
I don't know if that helps at all. In terms of recovering the data, the site I'm following instructions from says there is a Mount > USB Storage option in TWRP, which is why I am doing it.
Thanks
MCSulphate said:
All I know is that this is shown when I boot into recovery:
Android Recovery
MMB29K.G930FXXU1BPHJ
samsung/heroltexx/herolte
6.0.1/MMB29K/G930FXXU1BPHJ
user/release-keys
I don't know if that helps at all. In terms of recovering the data, the site I'm following instructions from says there is a Mount > USB Storage option in TWRP, which is why I am doing it.
Thanks
Click to expand...
Click to collapse
Hi mate
Yes , you have a G930F (Exynos) the TWRP image you were using seem right , regarding this , if you install TWRP in order to access the System /data where all the user apps , info, pictures , mail , configurations ..... is you need to format it , that partition is encrypted only Samsung can access it , TWRP does not support it unless you disable it by formatting it ( AKA erasing everything), mount the phone as USB device it may give access to some partition but it will not give you access to the System/ data ( unless you had formated it before)
If you knew what was the phone CSC you could flash a stock firmware without loosing anything, you use home_csc instead of CSC
MAX 404 said:
Hi mate
Yes , you have a G930F (Exynos) the TWRP image you were using seem right , regarding this , if you install TWRP in order to access the System /data where all the user apps , info, pictures , mail , configurations ..... is you need to format it , that partition is encrypted only Samsung can access it , TWRP does not support it unless you disable it by formatting it ( AKA erasing everything), mount the phone as USB device it may give access to some partition but it will not give you access to the System/ data ( unless you had formated it before)
If you knew what was the phone CSC you could flash a stock firmware without loosing anything, you use home_csc instead of CSC
Click to expand...
Click to collapse
Ah ok. So there's no way for me to get the data off it without knowing the CSC?
MCSulphate said:
Ah ok. So there's no way for me to get the data off it without knowing the CSC?
Click to expand...
Click to collapse
Not that i know, can you boot at all? if so install this app
Open it and under the CSC code tab it will tell you the active CSC ( country code)
Which country are you from, Netherlands ?
MAX 404 said:
Not that i know, can you boot at all? if so install this app
Open it and under the CSC code tab it will tell you the active CSC ( country code)
Which country are you from, Netherlands ?
Click to expand...
Click to collapse
I'm from England. Can't boot to anything apart from recovery and download mode.
MCSulphate said:
I'm from England. Can't boot to anything apart from recovery and download mode.
Click to expand...
Click to collapse
Ok , and the phone you got it from an specific carrier? or it was unbranded ( no carrier specific)
MAX 404 said:
Ok , and the phone you got it from an specific carrier? or it was unbranded ( no carrier specific)
Click to expand...
Click to collapse
Specific carrier, EE.
MCSulphate said:
Specific carrier, EE.
Click to expand...
Click to collapse
Ok mate.......
based on what you showed me, this should be the firmware installed on your phone, only BTU , XEU and EE had a BPHJ firmware in UK
http://www.sammobile.com/firmwares/download/95186/G930FXXU1BPHJ_G930FEVR1BPH1_EVR/
is up to you ..... there should be safe almost 100% sure you should not lose any data.....but there is always a chance
Download firmware from the above link , extract ( un rar , use winrar 7zip) 5 files from the zip file , should be AP, BL, CP, CSC and home_csc , DO NOT USE CSC use all the other 4 files and flash them with Odin ( use the latest download link in the next link i will give you) with the same home_csc as is on your phone there should not be a factory reset .....all data is preserved........hopefully we have it
Follow instructions on this thread read post 1 and 2
MAX 404 said:
Ok mate.......
based on what you showed me, this should be the firmware installed on your phone, only BTU , XEU and EE had a BPHJ firmware in UK
http://www.sammobile.com/firmwares/download/95186/G930FXXU1BPHJ_G930FEVR1BPH1_EVR/
is up to you ..... there should be safe almost 100% sure you should not lose any data.....but there is always a chance
Download firmware from the above link , extract ( un rar , use winrar 7zip) 5 files from the zip file , should be AP, BL, CP, CSC and home_csc , DO NOT USE CSC use all the other 4 files and flash them with Odin ( use the latest download link in the next link i will give you) with the same home_csc as is on your phone there should not be a factory reset .....all data is preserved........hopefully we have it
Follow instructions on this thread read post 1 and 2
Click to expand...
Click to collapse
Alright, thank you very much for your active support. A few questions, obviously I cannot activate PIN in Secure Startup, will that affect anything? Also which slot do I put the HOME_CSC in? What exactly is the HOME_CSC?
Thanks again.
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
MCSulphate said:
Alright, thank you very much for your active support. A few questions, obviously I cannot activate PIN in Secure Startup, will that affect anything? Also which slot do I put the HOME_CSC in? What exactly is the HOME_CSC?
Thanks again.
Click to expand...
Click to collapse
Anytime mate
Your father did not have any pin or password set up before? if that is so use this password default_password when asked for
home_csc goes in the CSC slot in Odin , Country Specific Code it has specific information and or configuration for special services offered by your carrier plus determines when you get an OTA , when you change CSC you have to factory reset if you keep the same CSC ( home_csc) is not mandatory
MAX 404 said:
Anytime mate
Your father did not have any pin or password set up before? if that is so use this password default_password when asked for
home_csc goes in the CSC slot in Odin , Country Specific Code it has specific information and or configuration for special services offered by your carrier plus determines when you get an OTA , when you change CSC you have to factory reset if you keep the same CSC ( home_csc) is not mandatory
Click to expand...
Click to collapse
Thank you so much for your help I'm waiting 2 hours for the firmware to download because of free account speed restrictions. I'll update this post when I've tried it.
Wish me luck!
MCSulphate said:
Alright, thank you very much for your active support. A few questions, obviously I cannot activate PIN in Secure Startup, will that affect anything? Also which slot do I put the HOME_CSC in? What exactly is the HOME_CSC?
Thanks again.
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
Click to expand...
Click to collapse
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
Download the firmware from sammobile ( first link) extract the 5 files as i told , then you you have two options
1 Extract files ( sammobile) , use the home_csc ( plus the other 4) from them and flash with odin
2 Extract files ( sammobile) save home_csc , go to the second link ( guide) download the firmware from there BUT use the home _csc file you saved ( extracted) from the firmware from sammobile , this is key to not lose any data
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
MCSulphate said:
Thank you so much for your help I'm waiting 2 hours for the firmware to download because of free account speed restrictions. I'll update this post when I've tried it.
Wish me luck!
Click to expand...
Click to collapse
fingers cross !!!
MAX 404 said:
EDIT: Oh and also should I download the firmware from the thread to be safe and just replace the HOME_CSC? Or is the linked firmware 100% fine?
Download the firmware from sammobile ( first link) extract the 5 files as i told , then you you have two options
1 Extract files ( sammobile) , use the home_csc ( plus the other 4) from them and flash with odin
2 Extract files ( sammobile) save home_csc , go to the second link ( guide) download the firmware from there BUT use the home _csc file you saved ( extracted) from the firmware from sammobile , this is key to not lose any data
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
fingers cross !!!
Click to expand...
Click to collapse
Hey.
So I downloaded the firmware from the site, flashed it using Odin, it flashed successfully, but I'm still getting the same issue. Won't boot up at all :/ is it more likely in this case to be hard bricked?
MCSulphate said:
Hey.
So I downloaded the firmware from the site, flashed it using Odin, it flashed successfully, but I'm still getting the same issue. Won't boot up at all :/ is it more likely in this case to be hard bricked?
Click to expand...
Click to collapse
hey mate
Sorry to hear that , try something else , see if you can boot in safe mode
1. Power off the phone by holding down the power button for a few seconds.
2. Press and hold the power button until the Galaxy logo appears on screen.
3. Press and hold the volume down button and release the power button.
4. Hold volume down until the phone has fully booted.
5. You should see ‘Safe mode’ in the bottom left of the screen.
if that does not work my last oftion woul be a factory reset before of thinking on a hardware problem.....
I am buying a new cricket wireless galaxy s7(snapdragon) and to fix the one I messed up. I want to know how do I copy the stock image/rom from the new s7 and put it on the old s7. Obviously they are both snapdragon models and they are NOT ROOTED. My old s7 just reboots and reboots I can get to recovery mode and the download mode. It only boots up to the samsung galaxy s7 screen before it reboots again and again etc. the reason is because I tried to root it with the tutorial on the unlockr's site the name of the article is "how to root the samsung s7 & s7 edge (all snapdragon versions) (video)" rooting the snapdragon s7 which broke my phone so all it does is reboot. Any help with backing up my new s7(snapdragon) and uploading the stock rom/image to the old s7(snapdragon) would be greatly appreciated.
Did you try downloading an image of a stock rom from updato.com or samfirmware etc.?
If not, download it, aswell as ODIN 3.12.3 and do a complete reflash (BL,AP,CSC,CP with re-partition checked, it includes a loss of data though).
You could try AP, BL and CP only and don't tag repartition, which won't wipe your device, if you are interested in your data. If you extracted your data, a full install mentioned above is recommended though. Just to get back to a clean image and anything your root might've messed up.
It should revive your old device and you probably don't need to buy a new one. Especially if i read correctly, just for extracting a stock image, which can be found on the internet already.
Given that you might already have triggered Knox, which will probably void any warranty from Samsung, you could try re rooting or leave it stock, which should be running good on Snapdragon still.
For other G930AZ Cricket Users I went through the samething. I used odin to flash the Engboot and then the phone just kept rebooting. To fix it I did the following.
The first step is to get the G930AZ stock image using samsung switch Here.
NOTE: Using the samsung switch Emergency Software Recovery to return to stock did not work for me, but I was able to get the stock firmware from it.
The model number is SM-G930AZ.
To get the serial number (took me forever to figure this out) go to the download mode on your phone (hold the power, volume down, and home buttons) and press the home button. The S/N is the serial number
After getting the firmware flash ONLY the BL, CS, and CSC (leave out AP) using this version of odin
http://www.mediafire.com/file/2t2sjqxtogbkafk/odin_3.12.3.rar
If that successfully flashes then things are looking good. The phone will restart and probably still boot loop but thats ok. Go back into Download mode but this time Flash the BL, AP ,CS ,CSC (Include the AP). IT should flash successfully and everything should be back to normal after that.
I was able to repeat this process twice with my G930AZ cricket phone so hopefully it works.
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
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.