Develop Bugs

[Q] odin on and off

It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.

BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
Odin is used in download mode. Are you trying to use it in recovery mode?

Larry2999 said:
Odin is used in download mode. Are you trying to use it in recovery mode?
Click to expand...
Click to collapse
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?

BigNoobee said:
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?
Click to expand...
Click to collapse
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?

Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?

Larry2999 said:
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?
Click to expand...
Click to collapse
The phone is a SGH-I747M ver. 4.3
I tried rooting based on a number of videos as to easily follow the process.

audit13 said:
Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?
Click to expand...
Click to collapse
I have a i747m, The situation is that odin only opens the com port when the phone is in operating mode.

BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
I should have stated my goal. My goal is to put kitkat on my phone. After talking to my provider (petro mobility) on the Rogers network no upgrades are going to be provided and at the very least I need an s4 or better s5 to run kitkat. Also this information I was given is NOT official but only the opinion of an employee"s personal opinion, having worked for the company for some time. The phone is not supported in any way by petro mobility but is only running on the Rogers network. If any upgrades are made it will be by Rogers. Rogers will not say anything because I am not a Rogers customer.

To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.

audit13 said:
To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.
Click to expand...
Click to collapse
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....

BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
Now you have custom recovery, you can flash a Kit-Kat based custom ROM. There is, of course, a difference between a Kit-Kat based custom ROM and official Kit-Kat 4.4. We have information and I'm sure they are reliable enough, that Kit-Kat 4.4 will be rolled out for Samsung GS III and all its variants including the i747U/M. The expectation has, however, been on for some time and no one really knows when and if. If you are using a custom ROM, you will not be able to get OTA updates for official firmware if the official version is rolled out but manual updates will still be possible, thanks to the development community.

BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
I don't personally use ROM Manager as I find it redundant. Now that you have Philz which can flash pretty much any KK ROM, you can just stick with using Philz to flash.
I like the Validus ROM on the i747m. I find it works well and has great battery life and performance.
BTW, you do not need to root in order to flash a custom ROM.

I need stock firmware from ANYONE SM-t807A it does not exist on the web.

I have spent days looking, turn on goes to kies firmware screen yet when i put in the model and s/n it shuts and the new samsung app to replace kies is of no help. I can get to the download screen and odin shows it up but no ATT 10.5 Tab S Sm-T807A firmware ANYWHERE.
Please help this is a very very expensive paperweight and im not affiliated with ATT so them helping me is out of the question.

Samobile.com

info.sven said:
Samobile.com
Click to expand...
Click to collapse
They dont have it for the SM-T807A

0 Results found
You searched for "sm-t807a"

It would better if you just explain what state the tablet is in and how it got to that state.
There is no official software for the t807a.

OK here how it goes,
The tablet was completely fine.
The original owner ( a family member) tried to root it and didnt accomplish it, somehow through his process it ended up softbricked.
I can enter he download mode for odin but no firmware for this LTE model.
When I turn it on it goes to the kies screen but kies doesnt recognize it, and when I enter the serial it buffers for 2 seconds then closes the process of kies.
Also it says device isnt supported and yes I have installed the right drivers and uninstalled kies numerous times.
The new replacement prog for Kies (forgot the name) is no help either.
Im terrified of what to do next as it does go to the odin screen just no firmware as I stated.

Any update, or could someone upload the stock firmware so i can use Odin on it.
Samsung told me ATT can flash it for free onto it so its deff a possibility however I do not have a ATT account so they cant help me.

It doesn't boot because the stock recovery has been wiped/replaced.
Thats assuming you have tried to boot recovery?
The att models are all bootloader locked.
I'm surprised a bootloader locked device even allowed an unsigned image to flash or did they use something like flashify?
The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image.

I was used with something like kingroot.
"The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image."
this i would highly appreciate as the firmwares not deleted just corrupted.

i have searched the whole web.
here is the link to the pulled stock sm-t807a files from a xda member
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing

PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files

synphonica said:
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
Click to expand...
Click to collapse
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.

I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.

also odin was used.

ashyx said:
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
Click to expand...
Click to collapse
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.

PowerfulJY said:
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
Click to expand...
Click to collapse
Please explain in more detail what you have done for the benefit of others.
---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------
synphonica said:
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
Click to expand...
Click to collapse
Did you use command line or gui?

I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.

PowerfulJY said:
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
Click to expand...
Click to collapse
The gui question was for synphonica about Heimdall.
Are you saying you flashed the images with odin? Which version and which images?
This has been tried before and failed.
Also what do you mean you tried a pc with the same firmware, same firmware as what?

I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.

cluver53 said:
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
Click to expand...
Click to collapse
You can only root with Kingroot, don't try any other method or you'll brick it nor can you install a custom kernel or recovery.
Once you have root you can pull the partition images with EFS PRO or PARTITION BACKUP.
The best way to have a back up is to catch the stock Firmware update.
This is tricky so research how to do it.
There is one backup I know of:
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing

HUGE Problem with s4 mini GT-9195

I recently rooted my I9195 successfully. i then flashed a custom kernel i found here on the forum (kernel v1 or sth like that) then my phone wouldn go past the boot white logo screen. i then tried flashing other kernels but they were apparently wrong as some features of my phone didnt work. i finally found the right firmware for my phone and tried to flash it with odin but it failed and now my phone only shows this message where it says that the firmware update failed and i have to use kies in recovery mode.
so i use kies and try the install firmware thing that asks you to put in your model and serial number. i do that and it says the device doesnt support initialisation. tried on another computer and it said that serial number was invalid.. i was very careful when typing it etc.
help.. what do i do?
btw last firmware i had was 4.4.2

Silvershot said:
I recently rooted my I9195 successfully. i then flashed a custom kernel i found here on the forum (kernel v1 or sth like that) then my phone wouldn go past the boot white logo screen. i then tried flashing other kernels but they were apparently wrong as some features of my phone didnt work. i finally found the right firmware for my phone and tried to flash it with odin but it failed and now my phone only shows this message where it says that the firmware update failed and i have to use kies in recovery mode.
so i use kies and try the install firmware thing that asks you to put in your model and serial number. i do that and it says the device doesnt support initialisation. tried on another computer and it said that serial number was invalid.. i was very careful when typing it etc.
help.. what do i do?
btw last firmwar i had was 4.4.2
Click to expand...
Click to collapse
I think you should put original back and start over and read forum more howto.
You use ODIN to flash custom rom, why? ODIN is for original rom. With custom rom need use TWRP or other recovery boot.

S3miniFin said:
I think you should put original back and start over and read forum more howto.
You use ODIN to flash custom rom, why? ODIN is for original rom. With custom rom need use TWRP or other recovery boot.
Click to expand...
Click to collapse
I used ODIN for past phones to flash custom kernels and it worked fine. i said i flashed someone that isnt supposed to be supported. i have no idea. i am not an expert and i thought someone can provide with a fast fix since there will surely be someone to have experienced this issue.
anyone else?

bump! please help.. i dont have another phone and I need to get this fixed asap!

You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420

S3miniFin said:
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
Click to expand...
Click to collapse
check my attached image.. i cant flash anything with odin. it gives me error fused 2 > binary 1

Silvershot said:
check my attached image.. i cant flash anything with odin. it gives me error fused 2 > binary 1
Click to expand...
Click to collapse
How about download-mode? Never seen ODIN-mode myself, so cannot understand what is going on there....
With download- mode i do all things with ODIN if need...

S3miniFin said:
How about download-mode? Never seen ODIN-mode myself, so cannot understand what is going on there....
With download- mode i do all things with ODIN if need...
Click to expand...
Click to collapse
that works, and it says downloading like normally when you try to flash something with odin, but it fails and gives me this error again: sw rev check fail: fused 2 > binarz 1
the rom im trying to flash is the DBT one in germany.
I am choosing AP btw, and not the other flash options.

S3miniFin said:
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
Click to expand...
Click to collapse
i flashed one of those roms and i got my phone to boot. i have no wifi. i guess it was the last rom i flashed which was the wrong one.
i now tried the one which is supposed to be the correct rom but i land on the same error again. can someone help me find the correct stock rom?
here are the current device info. it seems that there is no official 4.4.2 rom for my phone. so i ****ed up lol.

Your phone has official 4.4.2 Rom and you are currently using it. If you have Wi-Fi issues, your can try to flash custom kernel (Silviu, alexax)
Sent from my GT-I9190 using Tapatalk

Silvershot said:
that works, and it says downloading like normally when you try to flash something with odin, but it fails and gives me this error again: sw rev check fail: fused 2 > binarz 1
the rom im trying to flash is the DBT one in germany.
I am choosing AP btw, and not the other flash options.
Click to expand...
Click to collapse
But why you use F.Reset Time -option? Clear that and try again.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Silvershot said:
i flashed one of those roms and i got my phone to boot. i have no wifi. i guess it was the last rom i flashed which was the wrong one.
i now tried the one which is supposed to be the correct rom but i land on the same error again. can someone help me find the correct stock rom?
here are the current device info. it seems that there is no official 4.4.2 rom for my phone. so i ****ed up lol.
Click to expand...
Click to collapse
For Wifi problem could help if boot phone again after first setup.

ok now it wont go past the flashing SAMSUNG logo. i went and bought a huawei g play mini today. no more time trying to revive the s4 mini.
if someone wants to give it a try let me know and i'll ship it to you.

I will try it!
Plz sent me a PN (i'm german)
Sent from my GT-I9195 using XDA Free mobile app

S3miniFin said:
But why you use F.Reset Time -option? Clear that and try again.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
For Wifi problem could help if boot phone again after first setup.
Click to expand...
Click to collapse
i tried rebooting the phone but it still is as slow as before. it peaks on 27mbit when i start the speedtest but then drops down to 19 or sth..
actually the download speed seems to be the problem. not the upload. now i forgot the network and connected again and its even slower

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....