Related
So i bought a used s6 sm920f internation version with android 6.0.1 and a samsung acount lock. The guy on ebay said he bought it and the guy he bought it from won't help hom, so he sells it now.
Because it was cheap and I often flashed some phones I thought it would be easy to bypass. But I haven't found a way even after houndret tutorials, so I wanted to flash a stock firmware through odin, but when I started the download and failed with the message: " fail device: 3 binary: 2" and I don't know what to do now. It was a 5.1.1 rom and I checked the drivers and it was recognized as Samsung Mobile USB CDC Composite Device and as com4 or com3 in odin.
I can enter the recovery and download mode.
How can i get th device working normal now. I don't care if I have to install a custom rom and not a stock rom, just anything that works!
Thanks in advise!
Kantastisch said:
So i bought a used s6 sm920f internation version with android 6.0.1 and a samsung acount lock. The guy on ebay said he bought it and the guy he bought it from won't help hom, so he sells it now.
Because it was cheap and I often flashed some phones I thought it would be easy to bypass. But I haven't found a way even after houndret tutorials, so I wanted to flash a stock firmware through odin, but when I started the download and failed with the message: " fail device: 3 binary: 2" and I don't know what to do now. It was a 5.1.1 rom and I checked the drivers and it was recognized as Samsung Mobile USB CDC Composite Device and as com4 or com3 in odin.
I can enter the recovery and download mode.
How can i get th device working normal now. I don't care if I have to install a custom rom and not a stock rom, just anything that works!
Thanks in advise!
Click to expand...
Click to collapse
Flash twrp.
Sent from my SM-G925F
Rosli59564 said:
Flash twrp.
Click to expand...
Click to collapse
With odin? Don't you think I will get the same error
Kantastisch said:
With odin? Don't you think I will get the same error
Click to expand...
Click to collapse
Possibly will get flash successfully. Yes with odin of course.
Sent from my SM-G925F
Rosli59564 said:
Possibly will get flash successfully. Yes with odin of course.
Click to expand...
Click to collapse
Okay, thanks for the fast awnser. Can I reply to you when something goes wrong or to ask you what di do when I have twrp?
Kantastisch said:
Okay, thanks for the fast awnser. Can I reply to you when something goes wrong or to ask you what di do when I have twrp?
Click to expand...
Click to collapse
Ok you may pm me.
Sent from my SM-G925F
Rosli59564 said:
Ok you may pm me.
Sent from my SM-G925F
Click to expand...
Click to collapse
Thanks. But don't you need root first to get twrp working, because many people get bootloops.
Rosli59564 said:
Flash twrp.
Sent from my SM-G925F
Click to expand...
Click to collapse
He can't flash TWRP, cuz of FRP lock.
forumber2 said:
He can't flash TWRP, cuz of FRP lock.
Click to expand...
Click to collapse
Yes, it's even worse than frp. It's the samsung account lock not google.
I can't flash twrp. PLS HELP
Kantastisch said:
Yes, it's even worse than frp. It's the samsung account lock not google.
I can't flash twrp. PLS HELP
Click to expand...
Click to collapse
Sorry. Did it show reactivation lockn in download mode?.
Edit: Again sorry. As the title say it is.
You need to find the last firmware the phone on. That's an issue because you'll never know without booting into android. Have tried smart switch?.
Sent from my SM-G925F
Rosli59564 said:
Sorry. Did it show reactivation lockn in download mode?.
Edit: Again sorry. As the title say it is.
You need to find the last firmware the phone on. That's an issue because you'll never know without booting into android. Have tried smart switch?.
Sent from my SM-G925F
Click to expand...
Click to collapse
YAY! Because I was able to change the samsung mail before I flashed my phone, but it said processing fail. But after I downloaded the rom I had to put in the password but for my own mail and IT WORKED!!!
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
The things i tried so far:
1- Reflash with the latest stock firmware. Ticking the NAND erase all and repartition it with pit file also didn't work.
2- Samsung Smart Switch and Kies3. Flash completed but no effect.
3- Flashing any recovery files returns with "Custom binary(recovery) Blocked by R/L".
4- Sent it to my nearest Samsung service centre, they did try to repair it but only to be told that my S6 need a new motherboard the next day, which is out of my budget limit. But i am still hoping to find some other way to fix it, i believe this is just a "soft-brick" not a hard brick device.
Ideas guys? thanks.
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
thereassaad said:
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
Click to expand...
Click to collapse
Already tried that, still no luck..
mrkage said:
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
Ideas guys? thanks.
Click to expand...
Click to collapse
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
mrkage said:
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
Click to expand...
Click to collapse
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
mrkage said:
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
Click to expand...
Click to collapse
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Only did for my specific model number and carrier
mrkage said:
Only did for my specific model number and carrier
Click to expand...
Click to collapse
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
mrkage said:
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
Click to expand...
Click to collapse
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Didn't try that... but nevermind. I accidentally damaged my screen while trying to dissasemble it last night, a very stupid mistake from me.
Thank you for trying to help me mate. Forum mods can close this thread now. Thanks all.
problem
i have too but with A/L
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
esjames said:
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
Click to expand...
Click to collapse
How long do you think that will take since this is my only phone?
You will have to wait until an Odin flashable package of CRD4 or another bootloader 3 firmware becomes available. Without a complete BL3 system flash you are SOL
I think I'll hold off on the OTA update until I hear some safe reports
LordAbolition said:
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Nitefire77 said:
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Click to expand...
Click to collapse
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Do you have z3x?
You dont need z3x to flash the tmobile variant, but it makes it far simpler. Which version of odin are you using? If its the prince comsey you will more than likely get the mismatch error.
LordAbolition said:
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Click to expand...
Click to collapse
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
SprintBama said:
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
Click to expand...
Click to collapse
No worries. I fixed the situation. Thanks for reading!
I am clarifying this, this is s8 plus now stuck on rev3? I got an s8 and went to another forum thread and was told this isn't true. I am stuck on rev3. FYI, updato has the new s8plus firmware if you haven't got it already.
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
details
Another note: AP SW Rev is identified as B:2 K:1 S:1
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
JeffDC said:
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
Click to expand...
Click to collapse
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
same problem here... If an solution available pls write here
anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
Flashing stock rom and waiting 7 days would be the safe option.
I am not exactly sure what you are trying to achieve.
https://www.samsung.com/us/support/frp/
anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier, and when the phone setup was completed and booted into system, the OEM unlock was available.
Re: CRED I believe once it has been installed on a phone, you can not go back to a previous version (pre CRED).
JeffDC said:
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier,.
Click to expand...
Click to collapse
I wonder if I can do this date trick with combination FW to enable OEM unlock.
anonan said:
I wonder if I can do this date trick with combination FW to enable OEM unlock.
Click to expand...
Click to collapse
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Hi, could you send me a link of the combination firmware please Can't find it anywhere My email address is [email protected] I currently have similar experience of yours I thought everythings gonna be okay but it was too good to be true Help
anonan said:
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
Click to expand...
Click to collapse
anonan said:
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Click to expand...
Click to collapse
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Excellent.
I still can't get this to work. Have you purchased Samsung tool Pro to do the flashing of individual boot files? What version?
Hi there. I already bypassed the frp.. If you need. Hp with android 8.0 even with the binary 2. I have some comb files and working stock roms through odin. Feel free to pm me via my email [email protected]. Thanks!
how
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
oz_ezekiel said:
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
Click to expand...
Click to collapse
Download latest odin and try again. I too got stuck in similar situation. Realised the issue is due to Odin. If you are using latest and encountered this error, try one version earlier.
I too can confirm that the combination-ROM works like a charm with odin. FRP kinda unlocked itself
I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?
eddieofny said:
I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Try with patched odin, not normal odin.
TheWorldYT said:
Try with patched odin, not normal odin.
Click to expand...
Click to collapse
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
Oh, you have to use BROM, which involves opening up phone. You can search a tutorial how to do BROM mode in your phone.
eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
If the bit version of your phone is 3, flash the earliest bit 3 U package files. Then after flash bit 3 U1 package.
When flashing the U package just leave off the user data file. Must be using patched modded odin.
If you are bit 4, then you will be out of luck for a while.
I only know this because I ran into this same issue and that is how I resolved it on bit 3.