Develop Bugs

[Q] bricked -i747.

i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this

ghjsdf9 said:
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
Click to expand...
Click to collapse
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?

Larry2999 said:
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Click to expand...
Click to collapse
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions

ghjsdf9 said:
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
Click to expand...
Click to collapse
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.

Larry2999 said:
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Click to expand...
Click to collapse
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]

ghjsdf9 said:
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
Click to expand...
Click to collapse
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.

Larry2999 said:
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Click to expand...
Click to collapse
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......

ghjsdf9 said:
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
Click to expand...
Click to collapse
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.

Larry2999 said:
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Click to expand...
Click to collapse
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????

ghjsdf9 said:
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
Click to expand...
Click to collapse
I've seen this particular problem reported several times and it's always been a problem with the pit file. Flashing a complete stock system should fix all partition problems though. If the stock file you are using is an Odin flashable file, you may try using Odin 3.09. Otherwise, I'd suggest you find a recovery flashable image and flash via (custom) recovery.

Completely bricked S6 Edge G925T - any help?

I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FRP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
EDIT: Good news! Flashing the stock 5.1.1 odin image worked . (link: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841)
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working.

whittikins said:
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FAP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
Click to expand...
Click to collapse
SmartSwitch disaster recovery mode.

whittikins said:
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FAP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
Click to expand...
Click to collapse
More info, how did you get to this state of brick?
What was flashed, odined or installed.
Files, links. Etc.
Pp.

PanchoPlanet said:
More info, how did you get to this state of brick?
What was flashed, odined or installed.
Files, links. Etc.
Pp.
Click to expand...
Click to collapse
I was running the G925T (edge) leaked 5.1.1 rom ([5.1.1][ROM][TW][OE6] Blck/TW), which worked well for the month that I used it. I had TWRP from that thread installed as well (I think it was 2.8.6.x). Everything was good at this point.
Where I am now:
When I power the device on, it says:
KERNEL IS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
When I try to enter Recovery, it says:
RECOVERY IS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
What I did to get here:
SHORT VERSION - flashed latest modem and bootloader for G925T (edge) via Odin.
LONG VERSION
Last night I attempted to flash (via ODIN) the G925T bootloader, modem, and TWRP for this ROM: http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
G92xF(D)/T Galaxy S6 Universal Odexed Pure edition ROM
Based on the latest Samsung Stock G925F XXU2BOFJ Lollipop 5.1.1 firmware (Base build date: 20-JUN-2015)
NOTE: I didn't ever get to flash the ROM because the trouble started when trying to flash the bootloader/modem via ODIN.
- Odexed Pure Edition: Odexed & 100% original/Stock files!
Steps followed:
Do exactly step-by-step the following things:
- Unplug your Phone (IMPORTANT!)
- Turn your Phone completely off (This is IMPORTANT)
- Start your Phone in download mode on this way: Press Vol down + Home + Power buttons till the screen turns on, press Vol Up to continue (Only enter download mode on this way, otherwise it won't work!!)[/B]
- Open Odin 3.10.6 on your PC (Make sure you're using this version of Odin, other versions won't work correctly maybe!)
- Click on the 'BL' button, and load in your BOOTLOADER tar.md5 file for your model
- Click on the 'CP' button, and load in your MODEM tar.md5 file for your model
- DON'T TOUCH ANYTHING ELSE (you can brick your phone if you choose other settings in Odin)
- Now Connect your phone to your computer (DO NOT connect your phone before this step, otherwise it won't work!)
- Click on the Start button
- Wait till it finish flashing.
- Your phone reboots automatically after flashing. <--- device never rebooted because ODIN said Failed instead of Successful.
I then tried to flash TWRP 2.8.7.1 (link below) since maybe that had to be flashed before the bootloader/modem, but it failed too.
Links:
Odin 3.10.6
DOWNLOAD - https://www.androidfilehost.com/?fid=95916177934555153
[G925T] Odin Bootloader/Modem Packages:
5.1.1 Bootloader: G925T-UVU2COF6
DOWNLOAD - https://www.androidfilehost.com/?fid=24052804347766210
5.1.1 Modem: G925T-UVU2COF6
DOWNLOAD - https://www.androidfilehost.com/?fid=24052804347766211
You also have to update your TWRP to the latest version (2.8.7.1 or newer) when flashing this.
DOWNLOAD - http://build.twrp.me/twrp/twrp-2.8.7.1-zeroflte.img.tar

Is there a file I can Odin flash to disable FRP Lock? I can't boot up to turn it off.
If not, what are my options from here? Any way to preserve SDCARD or even /Data?
If all else fails, what Odin file should I flash to get back to stock?
EDIT: Regardless of what I try to flash in Odin (recovery, kernel, TWRP, modem), it begins the process but then fails because the phone states "_______ is not SEANDROID enforcing" and states FRP lock is on.

NexVision said:
SmartSwitch disaster recovery mode.
Click to expand...
Click to collapse
SmartSwitch isn't detecting my phone (although Odin does). What mode should it be in? I can get into Download Mode, but that's about it!

Your biggest problem right now is getting past FRP / factory reset protection, the only way to avoid this would have been to turn on bootloader unlock in "developer options"
OEM unlocking.
The security system is protecting your phone from you.
You need to be able to smartswitch back to stock but since your device status was not official, custom after running odin, root or anything else you may have done with root, smartswitch won't recognize your phone.
Without "OEM unlocking" on, the phone will turn on you.
The purpose of this security is to prevent your lost or stolen phone from been modified in any way and activated with another carrier.
Maybe tmobile has a procedure for returning phone back to normal.
Pp.

PanchoPlanet said:
Your biggest problem right now is getting past FRP / factory reset protection, the only way to avoid this would have been to turn on bootloader unlock in "developer options"
OEM unlocking.
The security system is protecting your phone from you.
You need to be able to smartswitch back to stock but since your device status was not official, custom after running odin, root or anything else you may have done with root, smartswitch won't recognize your phone.
Without "OEM unlocking" on, the phone will turn on you.
The purpose of this security is to prevent your lost or stolen phone from been modified in any way and activated with another carrier.
Maybe tmobile has a procedure for returning phone back to normal.
Pp.
Click to expand...
Click to collapse
Guys at the store couldn't do anything unfortunately. I guess it's just a brick now?
EDIT: The leaked 5.1.1 didn't have that option in dev options either. I guess running the leaked 5.1.1 is where I screwed up, even though it worked great while actually using it. I didn't have root, but I had TWRP recovery.

Would flashing the stock image work since it's not a custom one? I'm downloading it now from here: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
I'm guessing it won't work or else you would have suggested it. If anyone has a suggestion, I'm open to it!
It seems like there must be a way to disable FRP with an Odin flash, but maybe not.

whittikins said:
Would flashing the stock image work since it's not a custom one? I'm downloading it now from here: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
I'm guessing it won't work or else you would have suggested it. If anyone has a suggestion, I'm open to it!
It seems like there must be a way to disable FRP with an Odin flash, but maybe not.
Click to expand...
Click to collapse
After looking over article I give it a thumbs up, it may work for you.
Thats the problem with leaked updates or firmware, sometimes devs take shortcuts in order to package it for flashing and security stuff gets left out.
The ota 5.1.1, shows the option to turn on unlock bootloader .
Keep us posted, good luck.
Pp.

Screenshot showing option for bootloader unlock.
Pp.

PanchoPlanet said:
After looking over article I give it a thumbs up, it may work for you.
Thats the problem with leaked updates or firmware, sometimes devs take shortcuts in order to package it for flashing and security stuff gets left out.
The ota 5.1.1, shows the option to turn on unlock bootloader .
Keep us posted, good luck.
Pp.
Click to expand...
Click to collapse
Good news! Flashing the stock 5.1.1 odin image worked .
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working. Thanks for taking the time to help out!

whittikins said:
Good news! Flashing the stock 5.1.1 odin image worked .
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working. Thanks for taking the time to help out!
Click to expand...
Click to collapse
Glad to hear, don't forget about the oem unlocking in developer options.
Read carefully before you flash, and setup smartswitch on your pc, do a backup just in case.
Pp.

I had the same issue. I try to download stock firmware, download link just keep loading, doesn't work.
Is there any other links? samobile link doens't work neither. Thanks.

drakegao said:
I bricked my phone as well, same situation, I headed to that page try to download stock firmware, download link just keep loading, doesn't work.
Is there any other links? samobile link doens't work neither. Thanks.
Click to expand...
Click to collapse
Try a different pc, check your WiFi connection, or maybe Starbucks.
Pp.

Just checked link works and download works.
Pp.

PanchoPlanet said:
Just checked link works and download works.
Pp.
Click to expand...
Click to collapse
Thanks for replying, by the way. I got locked when i am still on 5.0.2 and i flash the bootloader and the modem. It was the modem of 5.1.1 didn't go through.
Will it be flashed through the 5.1.1 firmware, if not, any other options can solve the frp locked? Thanks

You need to flash 5.0.2 stock firmware with Odin, then maybe.
You can't flash anything that's 5.1.1 on your phone.

PanchoPlanet said:
You need to flash 5.0.2 stock firmware with Odin, then maybe.
You can't flash anything that's 5.1.1 on your phone.
Click to expand...
Click to collapse
tried, still failed in odin. I think is may be because my bootloader is actually 5.1.1's.
However, I saw above said flash 5.1.1 odin image ? what is that? Thanks.

solve it by flash 5.1.1 tar via odin as above said. thanks.

Help! boot loop - Custom binary blocked by FRP Lock

Hello, i have a SM-G920P model, its on a boot loop with the message on the top in red:
KERNEL ITS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
factory reset using the stock recovery and its the same.
i downloaded the latest firmware from sammobile and tried to flash it with odin 3. but odin always gets stuck on "Nand Write Start!!".. and doesnt do nothing for hours. i also tried an older version of Odin (1.3) and its stuck also on the flash. also tried to flash custom recovery..
i read somewere that using kies "fimware upgrade and initialization" works.. kies said that my phone was no supported, but the tool did accepted my phone model, but not my serial no. located on the back of phone (in odin mode is the same number). if somebody have the same model can give me their s/n so kies can download the firmware and i can flash using kies.
or does somebody know any good tricks i can do??
thanks

I need help too!
Robert4321 said:
Hello, i have a SM-G920P model, its on a boot loop with the message on the top in red:
KERNEL ITS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
factory reset using the stock recovery and its the same.
i downloaded the latest firmware from sammobile and tried to flash it with odin 3. but odin always gets stuck on "Nand Write Start!!".. and doesnt do nothing for hours. i also tried an older version of Odin (1.3) and its stuck also on the flash. also tried to flash custom recovery..
i read somewere that using kies "fimware upgrade and initialization" works.. kies said that my phone was no supported, but the tool did accepted my phone model, but not my serial no. located on the back of phone (in odin mode is the same number). if somebody have the same model can give me their s/n so kies can download the firmware and i can flash using kies.
or does somebody know any good tricks i can do??
thanks
Click to expand...
Click to collapse
I'm having this same problem, does anyone have a solution?

d'veldt said:
I'm having this same problem, does anyone have a solution?
Click to expand...
Click to collapse
Yes, use Odin to install the latest stock ROM. There are numerous threads right here explaining how to do this and providing links. But....
Download Odin from here: http://www.samsungodindownload.com/
Download the latest stock: https://www.androidfilehost.com/?fid=24343351889231947
Follow this: https://www.youtube.com/watch?v=tv0BnfpNxEs

Dude! You are a lifesaver! Thanks

Updated Bootloader: Bootloop, cannot access recovery, can access download mode !

After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.

Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.

audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks

1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.

audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.

It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.

audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.

You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.

audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.

How did you update the bootloader? Did you update the bootlaoder without updating anything else?

audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).

Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.

audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)

Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?

audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.

The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.

Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.

audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?

Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.

audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.

Pie root, twrp fail, odin fail and Emergency Recovery Function

Hi, community
I tried to root my SM G-9600 but it all went wrong. First i went on twrp, it worked, but wiped my entire data. Then i tried make a factory reset o installation with odin and the latest firmware for my device, but it failed and showed this message labeled in red color: "sw rev check fail device 4 binary 3 error". then i found in this and other forums that it was because i used not the latest firmware. I downloaded the latest one, tried once to flash it via ODIN, and it failed again. Then when it restarted this message was shown : " An error has occurred while updating the devide software. Use the Emergency recovery function in the Smart Switch PC software. I donwloaded the smart switch, installed it, plugged my devide, but it shown that my device was "Unsupported". IDK what to do by now, so i need help from anyone on this forum. PLS
Greeting from Peru.

i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.

Cant install a custom rom
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)

dimitrispas22 said:
i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.
Click to expand...
Click to collapse
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)

Stevie1997 said:
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)
Click to expand...
Click to collapse
do you want to install a custom rom or revert back to stock?

For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.

Xspidera said:
For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.
Click to expand...
Click to collapse
i think he is out of lack it looks like he doesn't know exactly his model snapdragon samsung devices are different from our g960f exynos version and it may brick his device
i think hes only option is to flash the stock firmware and yea just that....