Hello
Today, my phone was working perfectly fine until I got new update. After the update popped up, I decided to install it. My phone was not rooted or anything, was totally stock. After the update, the wifi wasn't working anymore. It connected to the wifi but it said "no internet access, try another wifi". I tested hotspot etc, all same. All my other devices worked just fine. So I decided to factory reset through recovery mode, which didn't help. I still couldn't connect to the wifi. Then I was going to try to reinstall firmware with Smart Switch, but apparently the big brains from Samsung removed the "device initialization" option from it.
The last resort was, Odin. I searched up the corresponding firmware for my phone (SM-G925F, from Belgium). I downloaded the firmware from sammobile, but after I only got 1 MD5 file, I assumed it was the AP (I searched on internet to confirm). After I tried to flash the new firmware with Odin, it failed. Now my phone wouldn't even start, I could blue screen "An error has occured while updating the device sofware. Use emergency sofware... blabla on smart switch". Ofcourse, we can't use that now anymore. I also tried installing older version of smart switch, but It said that the device is not supported.
So my question is, how can I fully reset my phone to stock with Odin? I am also using SamFirm to get the latest software with these options:
Firmware: SM-G925F
Region: PRO (Proximus provider - Belgium)
PDA/CSC/Phone: Auto
Binary nature: checked
PRO (Proximus) is set as the region. Proximus is a provider in Belgium. This is also the only region I can use in Belgium, all other regions don't work. My provider at this moment is Orange, but I don't know how to find the one from Orange.
I hope I'm doing something wrong and overseeing, otherwise I have no idea how to fix this anymore.
My firmware info:
PDA G925FXXU5EQH6
CSC G925FPRO5EQI2
My odin version: v3.12.3
Kind regards
Rekso
Edit 1: I finally got the files from SamFire. It passed CRC32 check, succesfully extracted the files. I fired up odin, put my phone into download mode, put all the AP, BL, CP and CSC files. When I clicked start, it failed, here is the log message:
<ID:0/006> 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..
<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/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit 2: When I try to flash, this is what appears on the phone: odin SW REV. check fail DEVICE 6 binary 5. I guess the firmware isn't correct? I also have the latest version of the 7.0 firmware for SM-G925F from SamMobile(and before my phone broke, I was also on 7.0).
FIX
So, after 8 hours of searching, even before I made this thread, I finally found the solution.
Alll you have to do is:
1. get the correct software from SamFire or sammobile.
2. Open Odin and put all the 3 files (AP, CSC and CP) in Odin. Make sure you do NOT put DL or it will not work.
3. Click start and your phone will be back to fresh start.
Hope this helps for people with same problem.
There is one problem though: I have no service. Is it because this firmware is from proximus? My phone was not branded (it was lockfree), now after I installed the firmware it became branded and I see proximus logo when the phone starts. This was not the case before. I also don't see my imei and basebrand anymore. Is there any way to fix this?
Regards
Unbranded firmware
Hello
As I mentioned in the post above, I got now problem with carrier. i did not want to create a new post so thats's why I am posting this here. Looks like I flashed a branded firmware (of proximus) on my unbranded samsung. Is there any firmware I can use which is unbranded and will not affect my carrier? At this moment I don't have any signal.
Will XEU / BTU firmware work?
Regards
-------------------------------------------------------------------------------------
EDIT: Fully fixed now, all you have to do is use XEU firmware (europe).
Related
Hi There,
After using temasek's stock android rom a while without any problem my galaxy s3 won't turn on anymore. About a month ago my S3 suddenly shutted down and now I get a bootloop where I only see the samsung logo reappearing every 5 seconds. I can't go into recovery mode, only into download mode. So my phone is soft bricked i supposed.
I tried almost everything, I searched for weeks for a sollution on XDA and I didn't found anything that could help me. So now i'm asking you guys because i'm a little bit desperate and i'm using my old nokia 3310 for a couple of weeks now.
I tried to reinstall my original firmware which I downloaded on sammobile with odin but there is always some kind of error.
I tried several versions of odin (new one's, olders one's) And still no progress.
Here's the log from odin v 1.85 :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_PHN_I9300XXALE8_I9300PHNALE4_I9300XXLE8.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>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I just checked off the box "PDA" and "AUTO REBOOT" and "F. RESET TIME" . When I use a pit file this is the log of odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_PHN_I9300XXALE8_I9300PHNALE4_I9300XXLE8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I'm sure that i used the right firmware, I've tried different pc's, i've also tried differend firmwares... Always a damn error in odin...
Can anyone help me?
ID:0/006> There is no PIT partition.
If you use a PIT file it has to be the right PIT file .
jje
JJEgan said:
ID:0/006> There is no PIT partition.
If you use a PIT file it has to be the right PIT file .
jje
Click to expand...
Click to collapse
I used the GT-I9300_mx_20120329.pit file which was suggested in this topic: http://forum.xda-developers.com/showthread.php?t=1894548&highlight=stock+firmwares
Weird. Sounds like SDS. What kernel were you using aling with Temasek s ROM?? And which version??
dhirend_6d said:
Weird. Sounds like SDS. What kernel were you using aling with Temasek s ROM?? And which version??
Click to expand...
Click to collapse
Version 77 and his kernel!
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...
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.
I have a s10plus which when i flash gets a error binary system blocked by oem lock. I am trying to flash stock rom but still it gives the same error. I have used odin and when it gets stuck and the error shows on my device screen. I am stuck in download mode however i can go into recovery if my battery dies . Please help me i will donate 50 dollars if my problem is fixed
Custom Binary Blocked by OEM lock
I bought a Note 9 (SM-N960F) second-hand and it turns out it was rooted in the past. I wanted to update the buildprop so that S Health would work so re-rooted the phone, made the necessary changes, which worked fine and then started removing...
forum.xda-developers.com
jwoegerbauer said:
Custom Binary Blocked by OEM lock
I bought a Note 9 (SM-N960F) second-hand and it turns out it was rooted in the past. I wanted to update the buildprop so that S Health would work so re-rooted the phone, made the necessary changes, which worked fine and then started removing...
forum.xda-developers.com
Click to expand...
Click to collapse
That didnt help
Jalapeno123 said:
I have a s10plus which when i flash gets a error binary system blocked by oem lock. I am trying to flash stock rom but still it gives the same error. I have used odin and when it gets stuck and the error shows on my device screen. I am stuck in download mode however i can go into recovery if my battery dies . Please help me i will donate 50 dollars if my problem is fixed
Click to expand...
Click to collapse
first i want to know what tou did to your phone.
how it all started.
did you bought it new or second hand.
was it rooted, did it had custom recovery or unlocked bootloader when you got the phone.
and from fully working ROM, what steps you did to do flashing, and what you were flashing and where.
when i get answers to these questions, how it all started, we can start troubleshooting problem
]
Thanx for replying i was normally updating my software from the settings and then it ran into a problem and went into odin mode
The device was 1.5 years old and had bought it brand new box packed
It is not rooted nor has usb debugging on as well as oem unlocked
I tried to flash it but every time it gets stuck either in system.img or vendor.img or dtbo
I am flashing stock rom and the oem block shouldnt have come
in ODIN while trying to flash, do you see log (left hand side)
copy/paste that log to here, so i can see what it says when you try to flash
also, download latest stock ROM
if it blocks on system, and you say it blocked while upgrading, then find latest available stock ROM (not original, like you had before upgrade, but newest stable stock ROM (issued by samsung, as a OTA update))
Because sometimes newer phones dont allow downgrade in android version, so if phone upgraded to android 11, it must be android 11 from now on, because kernel is updated, and kernel maybe have some important security patches, that should not be downgraded)
so flash newest stock ROM
also, if that doesnt work try installing twrp, also using ODIN (same method as flashing stock ROM):
UPDATE (FLASH THIS TWRP, AS OTHER ONE CAN CAUSE PROBLEMS TOO):
[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)
[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07) This project provides the TWRP recovery for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte). This recovery...
forum.xda-developers.com
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 8253 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> uh.bin
<ID:0/003> vbmeta.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> dt.img
<ID:0/003> dtbo.img
Now it stuck here and phone say custom binary blocked by oem lock
Where can i get the stable stock version?
I am flashing the newest update
Jalapeno123 said:
I am flashing the newest update
Click to expand...
Click to collapse
Try an older one. The one you originally had before trying to upgrade.
Also, your warrenty is expired, right?
Yes my warranty is expired
Try flashing just the bootloader.
Should i go to recovery and press reboot to bootloader?
Jalapeno123 said:
Should i go to recovery and press reboot to bootloader?
Click to expand...
Click to collapse
No. Just use Odin and only select BL then flash.
Ok i am in bootloader it says error validating footer 6
Now flash all files including bootloader again.
Same as before it is stuck at dtbo and phone says custom binary (boot) blocked by oem lock
What is the firmware you are trying to flash and where did you get it from?
I am flashing stock firmware of sm-g975f and i downloaded from frija tool
Please someone help, i just replaced LCD screen on my a21s, and offcorse fingerprint does not work anymore, so i try to flash older version of firmware, but odin keeps stuck on boot.img, what im suposed to do ? drivers are installed
lol, u cant flash older version of soft, it's locked by samsung and their bootloader
Only with custom ROM or GSI.
try flashing the software old or latest without marking the BL file "BootLoader" in odin... and for csc pick home csc... its a real slight chance.
i cant get past vefiry screen lock i hard reset but stikll asking what do i need to do
Crixellio said:
try flashing the software old or latest without marking the BL file "BootLoader" in odin... and for csc pick home csc... its a real slight chance.
Click to expand...
Click to collapse
it never works that easy , only combination or gsi custom roms which requires u5 or 1 for combination , especially if you are on the latest binary , i really want to know if you can anyhow downgrade without these two like with softwareboxeftpro or something.
beginner148 said:
it never works that easy , only combination or gsi custom roms which requires u5 or 1 for combination , especially if you are on the latest binary , i really want to know if you can anyhow downgrade without these two like with softwareboxeftpro or something.
Click to expand...
Click to collapse
it actually worked for me more than 2 times, bootloader blocked its own replacement, so i just replace others and hard reset, i don't know if it works for everyone i just said what i already tried more than once, but not always success.
kas0 said:
Please someone help, i just replaced LCD screen on my a21s, and offcorse fingerprint does not work anymore, so i try to flash older version of firmware, but odin keeps stuck on boot.img, what im suposed to do ? drivers are installed
Click to expand...
Click to collapse
What binary are you on ? If you are on binary 5, you can downgrade
Crixellio said:
it actually worked for me more than 2 times, bootloader blocked its own replacement, so i just replace others and hard reset, i don't know if it works for everyone i just said what i already tried more than once, but not always success.
Click to expand...
Click to collapse
Well, when i tried it(s7/u7) it gave me the infamous smartswitch erm cyan screen whenever you boot no way back but to flash the current official binary again with odin.
Crixellio said:
it actually worked for me more than 2 times, bootloader blocked its own replacement, so i just replace others and hard reset, i don't know if it works for everyone i just said what i already tried more than once, but not always success.
Click to expand...
Click to collapse
can you clarify how you have been able to flash old versions
what exactly do you mean by "replace others" and "hard reset"
Somebody knows a way to downgrade to binary 3 or 5? I just want to install a custom rom but get stucks with an binary error
hey guys,
I kind of got the same problem with my Samsung Galaxy A40.
It started last summer but was a little different back then.
As I restarted my phone my phone got stuck into a bootloop and on the top left there was written in red letters: could not do normal boot.
Until this day I kept researching what actually was the problem and how to fix it.
My solution turned out to be flashing the stock firmware on my device again.
But after some tries my frp lock turned "off" and I wasn´t longer in download mode, more like a cyan background and some data on the top left.
Odin showed me this text:
<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/003> 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..
<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/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> omr.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 6038 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> omr.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 6038 M
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> omr.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 6038 M
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyone who could tell me what my oppurtinities right now are, I will accept anything that lets my phone work again. So I I`m open to flash any Custom or Stock ROM onto my deviceif they can fix my problem.
Thank you and have a lovely afternoon