Samsung Galaxy S8 (SM-G950FD) firmware issue - Android Q&A, Help & Troubleshooting

Hi,
I have a serious issue with my Samsung Galaxy S8, 64 GB, dual sim. My phone has stock android, never rooted, never modified in any way. I run it in Australia but got it from overseas. After a system update (sometime in December) my phone rebooted (precisely on 29/12/2019), and after the reboot it got stuck at the android logo. Typical boot loop issue, so far so good.
Immediately after, I managed to boot into recovery mode with the intention to wipe the cache partition or do a factory reset, but neither functions worked. In fact, not a single function in recovery mode works. I can scroll up and down and select any option, but without actually executing the functions. And on top of that, after a few seconds the recovery mode freezes and I can't do anything but restart.
The only useful info in recovery mode is the following (on the top part of the screen):
"Android Recovery
Samsung/dreamltexx/dreamlte
/PPR1.180610.011/G950FXXU6DSK9" (please note that "G950FXXU6DSK9" is what it says there now, after flashing this particular firmware - see below. But the error messages were the same even before flashing).
and below, in the output part of the screen:
"fail to open recovery_cause(No such file or directory)#
Reboot recovery cause is [UNKNOWN]
Support SINGLE-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
verity verification failed...
E: [libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree
/firmware/android/compatible : no such file or directory"
When I attempt a factory reset (or any other function in the recovery menu), I get the following error message:
"wiping data...
formatting /data...
formatting /cache...
data wipe complete.
E: [libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree
/firmware/android/compatible : no such file or directory"
Apparently the firmware "G950FXXU6DSK9" doesn't work. So I got myself Odin (Odin3_v3.13.1) to flash a working firmware but cannot, for the life of me, figure out the right firmware - mostly because I don't know the right PDA and CSC.
In any case, here is the Odin log:
G950FXXU6DSK9_G950FOXM6DSK9_SMA
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5843 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> up_param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> userdata.img
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> modem_debug.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img
<ID:0/005> omr.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Here is what I know:
- Model of my phone, as seen on the back of the phone case (SM-G950FD)
- region of my phone, as seen in the download mode (XSG - United Arab Emirates).
- my IMEI, as seen on the back of the phone case
- my phone serial number, as seen on the back of the phone case
- Chipset: Samsung Exynos 9 Octa 8895, obtained via IMEI.info
- OS: Android 7.0 Nougat, Android 8.0 Oreo, obtained via IMEI.info
- I can enter the download mode
- I can enter the recovery mode, but not do anything
Here is what I don't know:
- my exact PDA
- my CSC
- and therefore, my exact firmware
Here is what I have tried, unsuccessfully:
- used the most current version of Kies; however my device is not supported.
- used the most current version of Frija (v1.4.2); however I got "error 102. unable to find firmware"
- downloaded and successfully flashed 3 different firmware versions, obtained from sammobile.com. these 3 versions are:
G950FXXS6DSL2_G950FOXM6DSK9_BTU
G950FXXU6DSK9_G950FOXM6DSK9_BRI
G950FXXU6DSK9_G950FOXM6DSK9_SMA
I have flashed AP, BL, CP, and CSC. I did not flash HOME_CSC. Then I tried also with HOME_CSC, but no difference.
however after successful flashing, the outcome in recovery mode was unchanged. I still couldn't use any of the recovery mode functions, and I still got the exact same error messages.
I also tried flashing G950FXXS5DSI1_G950FOXM5DSHC_XSG, which at least had the correct country code (XSG), but this one I couldn't flash using Odin, so I went back to a previous one (G950FXXU6DSK9)
Does anyone have any idea what my error messages mean, and how to overcome them? Can anyone tell me the exact firmware I have to use to get this to work again?

help
any ideas?

Related

[Q] S3 GT-I9300 stucks on boot logo.

Hi everyone,
My S3 stucks on boot logo ,and when i connect it to the charger i have just the grey battery with cirle inside it , no grenn battery after 3 hours.I'd tried several usb cable chargers but nothing. I tried to flash it with odin throught Download mode it always fail after NAND Write Start!! .Even with stock roms or custom ones .and i can't go in recovery mode.
In Odin mode appear like :
PRODUCT NAME :GT-I9300
CUSTOM BINARY DOWNLOAD :YES (7 COUNTS)
SYSTEM STATUT: Custom
Any suggestions Please: tnx:good:
Sounds like nand damage, you can try a rescue firmware & pit:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
But I wouldn't hold out too much hope.
Thank you very much, for your reply..
I'll try this night..
Regards
I followed all the instructions and always the same result No Pit partition ,here is the log :
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Any others suggestions PLZ
ID:0/005> There is no PIT partition.
Destroyed PIT requires a service centre paid for repair .
jje
If you added the pit file and ticked repartition then as jje says it needs a new motherboard, sorry.

[Q] Forgot to Turn on USB Debugging, ODIN not working

Hi Everyone,
I was trying to unlock my Samsung Galaxy S3 I-747M (I'm on Bell in Canada). Everywhere I looked on the internet instructed me to downgrade my version to 4.1.1 and then enter the magic numbers to unlock my phone.
So I followed the steps. Downloaded version 4.1.1 of the ROM, ODIN, etc., except a couple of things went wrong:
1) I forgot to turn on USB debugging mode
2) I've now learned that I should not downgrade from 4.3 back to 4.1.1
When I tried to install the ROM via ODIN it didn't work. Based on the other thread, downgrading from 4.3 will hard brick the phone, so I guess I'm lucky it didn't work.
My question is, where do I go from here? I am ready to give up on the unlock process. I just want the phone to work again at this point.
The phone has the following on the screen:
ODIN MODE
PRODUCT NAME: SGH-1747M
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
There is a warning symbol between an image of the device and a monitor and it states "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can get to the Downloading mode.
I got these messages in ODIN:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MUMBLL1_I747MPCTBLL1_688429_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

[HELP] My GT-I9300 now has the Product Name SGH-I747 and MTP Device fails to install

Sorry, currently a new member but being the noob I am- it seems I flashed my International I9300 to a different device (SGH-I747)...
My device is stuck on the Samsung start-up (no biggie), and I believe it's soft-bricked but currently I have no idea what to do.
I've been on Odin and followed many guides to get it back to stock but to no avail. It all fails. I believe something with the MTP failing to install is also a problem. I've done the CMD command and went into regedit and a number of other things.
Right now Kies can't even do an Emergency Firmware Recovery won't pick it up.
Also when I get it in Recovery Mode it exits out and turns to a black screen after a couple of seconds.
I follow this : http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
As the PIT seems to PASS but from there all the other PDA's I try to start fail.
---
I can get it into Odin Mode.
And currently has
Product Name : SGH-I747
Custom Binary Download: Yes (7 counts)
Current Binary : Custom
System Status : Official
QualComm SecureBoot: Enable
---
Help would be much appreciated.
How did this occur? Well actually, I just did a Factory Reset when it worked and then it got stuck loading for hours... Then tried to flash something in... Apparently got the wrong one. And here I am.
simonheros said:
Sorry, currently a new member but being the noob I am- it seems I flashed my International I9300 to a different device (SGH-I747)...
My device is stuck on the Samsung start-up (no biggie), and I believe it's soft-bricked but currently I have no idea what to do.
I've been on Odin and followed many guides to get it back to stock but to no avail. It all fails. I believe something with the MTP failing to install is also a problem. I've done the CMD command and went into regedit and a number of other things.
Right now Kies can't even do an Emergency Firmware Recovery won't pick it up.
Also when I get it in Recovery Mode it exits out and turns to a black screen after a couple of seconds.
I follow this : http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
As the PIT seems to PASS but from there all the other PDA's I try to start fail.
---
I can get it into Odin Mode.
And currently has
Product Name : SGH-I747
Custom Binary Download: Yes (7 counts)
Current Binary : Custom
System Status : Official
QualComm SecureBoot: Enable
---
Help would be much appreciated.
How did this occur? Well actually, I just did a Factory Reset when it worked and then it got stuck loading for hours... Then tried to flash something in... Apparently got the wrong one. And here I am.
Click to expand...
Click to collapse
it seems I flashed my International I9300 to a different device (SGH-I747)??? what does this mean? flashed SGH-I747 firmware in I9300? just want to make sure that what i understood is right because your post is making some confusion..
Can you tell me if your device is 16GB or 32GB or 64GB? pit file for all three of them is different. if you will use correct one than this should not fail.. i dont think that mtp has to do anything with odin but if it does than uninstall all the drivers that are currently install(your device drivers) and download and install samsung drivers from here: http://www.mediafire.com/?7iy79emc0bf1fb4 and then try to connect the device again.. I hope this helps you..
suyash1629 said:
it seems I flashed my International I9300 to a different device (SGH-I747)??? what does this mean? flashed SGH-I747 firmware in I9300? just want to make sure that what i understood is right because your post is making some confusion..
Can you tell me if your device is 16GB or 32GB or 64GB? pit file for all three of them is different. if you will use correct one than this should not fail.. i dont think that mtp has to do anything with odin but if it does than uninstall all the drivers that are currently install(your device drivers) and download and install samsung drivers from here: ----------- and then try to connect the device again.. I hope this helps you..
Click to expand...
Click to collapse
Thank you for the response.
Yes I flashed I747 firmware in I9300. I apologize for the poor wording. My device is 16 GB. The one from the thread I linked is said to be used by 16 GB variant, so I believe it works. (Passes)
I don't get that MTP driver error anymore, but now when I try to put a Bootloader in it says that it's an unsupported dev type.
A person got a similar problem here : s3forums.com/forum/galaxy-s3-help/5772-stuck-download-mode-diffrent-device-type-9300-sgh-i747 ( can't post link) but it appears to be bricked flat out...
simonheros said:
Sorry, currently a new member but being the noob I am- it seems I flashed my International I9300 to a different device (SGH-I747)...
My device is stuck on the Samsung start-up (no biggie), and I believe it's soft-bricked but currently I have no idea what to do.
I've been on Odin and followed many guides to get it back to stock but to no avail. It all fails. I believe something with the MTP failing to install is also a problem. I've done the CMD command and went into regedit and a number of other things.
Right now Kies can't even do an Emergency Firmware Recovery won't pick it up.
Also when I get it in Recovery Mode it exits out and turns to a black screen after a couple of seconds.
I follow this : http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
As the PIT seems to PASS but from there all the other PDA's I try to start fail.
---
I can get it into Odin Mode.
And currently has
Product Name : SGH-I747
Custom Binary Download: Yes (7 counts)
Current Binary : Custom
System Status : Official
QualComm SecureBoot: Enable
---
Help would be much appreciated.
How did this occur? Well actually, I just did a Factory Reset when it worked and then it got stuck loading for hours... Then tried to flash something in... Apparently got the wrong one. And here I am.
Click to expand...
Click to collapse
I think mate you should check if your bootloader in locked or unlocked. As you mention above about QualComm Secure boot :Enable. may be before you was using gt-i9300 firmware it must be unlocked but after you flashed wrong firmware may be your bootloader got locked.
try to download complete stock 4.3 firmware from sammobile.com for correct variant i.e GT-I9300.
Download it and extract it and you will get .tar files
download latest Odin ( google it ) and open it.
put your phone in download mode by pressing volume down + home key + power key for few deconds until download mode screen appear.
press volume up key to goto download mode. connect your phone to your computer and wait till it install all the necessary driver. if you drivers are not installed properly then you have to manually installe the driver for your phone. download galaxy toolkit for s3 from xda and install it. search for the folder name galaxy toolkit in your computer. basically it will be in c:/ drive. open that folder and you will find driver folder under it. Inside the driver folder there will .exe file of driver. but before installing disconnect your phone computer and then install the driver. after the installation of your driver plug in again and wait till it install all the drivers.
Inside odin you must have to see that there is COM ID in 1st box and below it is written attached. if you dont see that then your driver are not installed correctly. uninstall and install it again.
after the driver install click on AP and select the AP .tar file that we extracted after downloading. select the appropriate file associated with it.
click on start and wait few minutes till the process gets complete.
If all things goes right you may get your phone back again.
Mustakim_456 said:
I think mate you should check if your bootloader in locked or unlocked. As you mention above about QualComm Secure boot :Enable. may be before you was using gt-i9300 firmware it must be unlocked but after you flashed wrong firmware may be your bootloader got locked.
try to download complete stock 4.3 firmware from sammobile.com for correct variant i.e GT-I9300.
Download it and extract it and you will get .tar files
download latest Odin ( google it ) and open it.
put your phone in download mode by pressing volume down + home key + power key for few deconds until download mode screen appear.
press volume up key to goto download mode. connect your phone to your computer and wait till it install all the necessary driver. if you drivers are not installed properly then you have to manually installe the driver for your phone. download galaxy toolkit for s3 from xda and install it. search for the folder name galaxy toolkit in your computer. basically it will be in c:/ drive. open that folder and you will find driver folder under it. Inside the driver folder there will .exe file of driver. but before installing disconnect your phone computer and then install the driver. after the installation of your driver plug in again and wait till it install all the drivers.
Inside odin you must have to see that there is COM ID in 1st box and below it is written attached. if you dont see that then your driver are not installed correctly. uninstall and install it again.
after the driver install click on AP and select the AP .tar file that we extracted after downloading. select the appropriate file associated with it.
click on start and wait few minutes till the process gets complete.
If all things goes right you may get your phone back again.
Click to expand...
Click to collapse
Thank you for the response.
Drivers work and it's been able to connect to ODIN but it fails regardless of the stock firmware I flash via PDA.
I get this :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
For Bootloader
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----
It would help to mention that I have a second i9300 that works and hasn't been touched or anything. Can I do something with that?
edit* It says unsupported dev type on my screen when it fails..
simonheros said:
Thank you for the response.
Drivers work and it's been able to connect to ODIN but it fails regardless of the stock firmware I flash via PDA.
I get this :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
For Bootloader
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----
It would help to mention that I have a second i9300 that works and hasn't been touched or anything. Can I do something with that?
edit* It says unsupported dev type on my screen when it fails..
Click to expand...
Click to collapse
Looks like your Nand maybe corrupt try flashing the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735 <<
tallman43 said:
Looks like your Nand maybe corrupt try flashing the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735 <<
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
SECURE CHECK FAIL : PIT
Unsupport: dev_type
---
None of the PIT's work now... And pretty much none of the files passed... D:
simonheros said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
SECURE CHECK FAIL : PIT
Unsupport: dev_type
---
None of the PIT's work now... And pretty much none of the files passed... D:
Click to expand...
Click to collapse
Any progress??
suyash1629 said:
Any progress??
Click to expand...
Click to collapse
None what so-ever. I hit a dead end and had to get a replacement.
I'm just not going to mess with the new one anymore...

Kernel is not Seandroid enforcing

I'm currently having "Kernel is not Seandroid enforcing" error message.
First, I rooted my phone, then preparing into flashing a custom ROM and kernel.
I downloaded Extended battery (v 2.91.45) - N910C/H for Kernel and Nemesis for ROM.
Wipe cache and etc then flash the kernel via TWRP first while I was downloading the Custom ROM.
Rebooted after I flashed the Kernel (maybe I screwed up here because I don't have any ROM installed yet?)
Phone couldn't go anywhere past the boot screen which shown "Kernel is not Seandroid enforcing" error message.
After searching the internet, people suggested to flash the stock ROM via ODIN, but then I have these errors on Odin 3 v3.04
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COJ5_N910GOLB1COJ1_N910GDTU1COJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
And no response on Odin3 v3.12
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
I'm flashing with the latest stock ROM in my Country.
Tried different USB ports
Tried different USB cables.
Tried factory reset/ manual wipes
OS : 6.0.1
Model : SM-N910C - Samsung Note 4
What else can I do on my end before sending it to shops ?

Having trouble restoring stock firmware to my Samsung Galaxy Tab S3

EDIT, SOLVED: I downloaded the most recent verson of Odin (3.14.1) and was able to get everything flashed. I was also using the normal CSC file and not the HOME_CSC file, which may have also contributed to the problem.
So I wanted to try out putting a custom firmware onto my Samsung Galaxy Tab S3 (SM-T820). I managed to install LineageOS 17 successfully via TWRP, but after trying it out for a bit decided I didn't like the tradeoffs and wanted to go back to stock.
Well now I'm having some trouble getting the stock ROM flashed back onto the system. Long story short:
TWRP recovery boot is still working
LineageOS has been wiped and the internal storage re-formatted
I have downloaded several different stock ROMs and now identified what I am relatively confident is the correct one (SM-T820_1_20200501145641_h0dxr2w1l3_fac, region code XAR for USA), although it only includes the BL, AP, and CSC files (not CP, none of the stock roms I found included a CP file though)
I have all the Samsung drivers installed onto my computer
I have Odin v3.10.7 on my computer (used it to install TWRP to get LineageOS installed)
When I select the BL, AP, and CSC files in Odin and try to run it while my tablet is in download mode, this is the output I get:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn.lz4
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I have been on Google for quite some time and tried several things, but I haven't been able to make any progress. Most of the advice for the errors I found seem to relate to making sure I have the right ROM, but I've tried several different versions and finally downloaded the one I have through SamFirm so I don't think I have an incorrect ROM.

Categories

Resources