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
Related
Need to return for warranty issue, used triangle away & reset counter
Downloaded stock rom from SamMobile
(I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5)
UK BTU I9300XXALF2 I9300OXAALF2 I9300XXLF2
Following the video here
[VIDEO]How to Root & Install CWM Recovery/How to Unroot and Get back the Warranty
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1715822&highlight=warranty
Did a full wipe, wiped cache partition, wiped dalvek partition etc
Running Odin3 v1.85
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
Seem to be getting nowhere, can somebody tell me what I am doing wrong, my phone is still displaying
Downloading
Do not turn off target
By the way I am in Ireland and the stock rom I downloaded seems to be the correct one, im a relative newbie by the way
Stock Rom LF2 posted here certainly works .
http://forum.xda-developers.com/showthread.php?t=1646610
Try that you may have a bad download from sammmy .
jje
http://www.hotfile.com/dl/159515882/30b51b3/I9300XXALF2_I9300OXAALF2_BTU.zip.html
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Thats the same source as the file I originally downloaded but thanks anyway, had an idea I was using the wrong lead from the PC to the phone, switched it is working as we speak, rebooted and now going to do a factory reset, ill let you know how it goes JJEgan, thought the phone may have bricked, phew
All ok now, everything working, thanks for ur input JJ....appreciate very much
I see Odin3 v3.04 is newer than the Odin3 v1.85 I was using so I downloaded this
Odin sometimes has issues and simply does not flash. Restart it, reconnect the phone and everything is fine
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...
These files are for the SM-S920L Straight Talk Variant. Do not use these on other variants!
Picked one of these up the other day and seen a lack of proper files, so I decided to make some.
Stock Boot:
http://archive.midnightchannel.net/zefie/files/cell/SM-S920L/Stock Odin/boot.zip
Stock Recovery:
http://archive.midnightchannel.net/zefie/files/cell/SM-S920L/Stock Odin/recovery.zip
Stock System (Untouched/Unrooted):
http://archive.midnightchannel.net/zefie/files/cell/SM-S920L/Stock Odin/system.zip
Stock System (Rooted with SuperSU, not KingRoot):
http://archive.midnightchannel.net/zefie/files/cell/SM-S920L/Stock Rooted Odin/system.zip
TWRP Recovery (Not my work):
http://androidforums.com/threads/twrp-3-0-2-0-sm-s920l-only.1023315/
TWRP Recovery (Fixed):
http://archive.midnightchannel.net/zefie/files/cell/SM-S920L/TWRP/TWRP v3.0.2.0.zip
This is a patched version of TWRP provided by edodson84 to fix bug #1 listed on his thread. It also fixes ADB.
--
To use these, unzip them, then flash in Odin (Available here: http://archive.midnightchannel.net/zefie/files/cell/SM-S920L/Odin_3.10.0.zip )
Choose AP, leave everything else default.
Odin/Download mode is Volume Down + Home + Power
You saved my phone ty
well crap
i have odin access but i am stuck in a twrp bootloop, but every attempt to flash to stock anything is met with SECURE CHECK FAIL
i'm hopeless and desperate, i have basically bricked my grand prime, does anybody know how i can just go back to good old comfy stock? i'm gonna freak out!
Thanks for posting these! Here I thought that our device would never see any development and now we have a mostly functional custom recovery at least.
Thank You
Thank you very much.These files totally saved my phone and my day.
the format the files unzip as are .img.ext4 and odin wont show them for selection when i try to choose them for flashing. what am i doing wrong?
Both system.zip files extract to system.tar.md5 which is what you need to flash in Odin. You are extracting the tar.md5 file which Odin will not flash.
bfoos said:
Both system.zip files extract to system.tar.md5 which is what you need to flash in Odin. You are extracting the tar.md5 file which Odin will not flash.=QUOTE]
rename tar.md5 to .tar and odin will install it.
Click to expand...
Click to collapse
Been some time since I've been here. Good to see progress.
I've been trying (and failing) to download the zips for recovery.Each time I try extracting,ES Explorer tells me files are corrupt.
Any other links 2 these files ?
Sent from my SM-S920L using XDA-Developers mobile app
dmbolsdboy said:
Been some time since I've been here. Good to see progress.
I've been trying (and failing) to download the zips for recovery.Each time I try extracting,ES Explorer tells me files are corrupt.
Any other links 2 these files ?
Sent from my SM-S920L using XDA-Developers mobile app
Click to expand...
Click to collapse
Extract with 7 zip on pc. The files are fine I use them myself
Thanks.Got it figured out.Anyyhing found out about OTG on these phones ? Everything I throw at it says OTG capable,but maybe not in the kernel ?
Sent from my SM-S920L using XDA-Developers mobile app
samsung galaxy grand prime sm-s920l of course...........phone was rooted with kingroot. then used supersu to remove kingroot and add superuser.......certain games wouldnt work on the rooted phone, so i used supersu to unroot. worked fine for 2 days but didnt reboot phone. phone battery died and caused shut down. now, phone freezes at blue trac phone screen right before the unlock screen. have pulled battery sincei cant shut it down, i have tried a factory reset, and nothing works...... this is what ive tried in odin3 v3.10 and even tried updating to odin v3.12.............no luck, please help me. i have to have my phone and cant afford another..........
ON PHONE SCREEN-----------------
odin mode
product name: sm-s920l
current binary: samsung official
system status: custom
reactivation lock (kk): on
qualcomm secureboot: enable (csb)
rp swrev: s1, t1, h1, r1, a1, p1
secure download: enable
secure check fail: boot
ON ODIN---------------------------------------------------------------------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tyrant46290 said:
samsung galaxy grand prime sm-s920l of course...........phone was rooted with kingroot. then used supersu to remove kingroot and add superuser.......certain games wouldnt work on the rooted phone, so i used supersu to unroot. worked fine for 2 days but didnt reboot phone. phone battery died and caused shut down. now, phone freezes at blue trac phone screen right before the unlock screen. have pulled battery sincei cant shut it down, i have tried a factory reset, and nothing works...... this is what ive tried in odin3 v3.10 and even tried updating to odin v3.12.............no luck, please help me. i have to have my phone and cant afford another..........
ON PHONE SCREEN-----------------
odin mode
product name: sm-s920l
current binary: samsung official
system status: custom
reactivation lock (kk): on
qualcomm secureboot: enable (csb)
rp swrev: s1, t1, h1, r1, a1, p1
secure download: enable
secure check fail: boot
ON ODIN---------------------------------------------------------------------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I am having the same problem due to almost the same reason, any time i try to flash with odin i get SECURE CHECK FAIL: BOOT, SECURE CHECK FAIL: RECOVERY or SECURE CHECK FAIL[FMM]: system depending on what i try to flash. I have tried multiple odin versions on two desktops (one windows 10 other 7) and a laptop
The lesson here being... Disable reactivation lock BEFORE messing around with your phone.
Tyrant46290 said:
samsung galaxy grand prime sm-s920l of course...........phone was rooted with kingroot. then used supersu to remove kingroot and add superuser.......certain games wouldnt work on the rooted phone, so i used supersu to unroot. worked fine for 2 days but didnt reboot phone. phone battery died and caused shut down. now, phone freezes at blue trac phone screen right before the unlock screen. have pulled battery sincei cant shut it down, i have tried a factory reset, and nothing works...... this is what ive tried in odin3 v3.10 and even tried updating to odin v3.12.............no luck, please help me. i have to have my phone and cant afford another..........
ON PHONE SCREEN-----------------
odin mode
product name: sm-s920l
current binary: samsung official
system status: custom
reactivation lock (kk): on
qualcomm secureboot: enable (csb)
rp swrev: s1, t1, h1, r1, a1, p1
secure download: enable
secure check fail: boot
ON ODIN---------------------------------------------------------------------
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
try to flash it using odin try to use the stock boot put it on bootloader and use Stock system(Rooted with SuperSU, not KingRoot) put it on the PDA = enjoy
how can i unlock the region of my phone ?? model sm-s920l
Thansk to the OP, my phone is saved :good: I flashed the wrong model and screwed up my phone, but after flashing the stock system and boot, its back to normal. Thanks for the files!
everytime i put the system.zip in odin. odin stops responding and says please wait any fix?
---------- Post added at 12:58 AM ---------- Previous post was at 12:55 AM ----------
i hope this thread isnt to dead
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
what order do i flash each file or dont it matter?
---------- Post added at 01:07 AM ---------- Previous post was at 01:02 AM ----------
nvm i got it. haha i was so worried my phone was bricked for a day all because i tried putting a custom rom on since 5.0.2 is so out dated lol
Velocity89 said:
everytime i put the system.zip in odin. odin stops responding and says please wait any fix?
---------- Post added at 12:58 AM ---------- Previous post was at 12:55 AM ----------
i hope this thread isnt to dead
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
what order do i flash each file or dont it matter?
---------- Post added at 01:07 AM ---------- Previous post was at 01:02 AM ----------
nvm i got it. haha i was so worried my phone was bricked for a day all because i tried putting a custom rom on since 5.0.2 is so out dated lol
Click to expand...
Click to collapse
Odin does that to me as well just wait it is just checking the md5 and yes it takes a few minutes.
Sent from my SM-S920L using XDA-Developers mobile app
No TWRP after flashing with ODIN
Ok, did a factory reset. Allowed unknown sources. Using Odin from this thread: Clicked "AP" and added the patched twrp "recovery.tar.md5 (also tried removing .md5 from extension), plug in phone while in ODIN/Bootloader and it's added to ODIN, hit "Start" flash shows it succeeds and phone restarts. I go back into bootloader (Vol Down+Power+Home)and there is no recovery option... Am I missing something?
NVM. VOL *UP* + Power + Home to get into Recovery. I'm rusty. lol
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.
Hi,
Odin don't recognize phone when in download mode. However, it recognizes when it is in normal boot mode. Why?
My phone is on initial configuration (first time use, after restore factory), I formatted why my son forgot google and PIN password. Can I help me? Thanks.
you have installed drivers for download mode? and rom reflash doesnt delete google password lock
KaroloBC said:
you have installed drivers for download mode? and rom reflash doesnt delete google password lock
Click to expand...
Click to collapse
I have installed "SAMSUNG_USB_Driver_for_Mobile_Phones". It´s that?
Odin recognizes a cell phone by turning on in normal mode (but I don't have google password or cell phone PIN). However, it doesn't recognize when I start in download mode.
"... rom reflash doesnt delete google password lock ..."
How to delete this? Broke my cell phone?
Thanks!
[i assume u not stole this phone]
to delete google password lock use frp bypass, you can find it on youtube
KaroloBC said:
[i assume u not stole this phone]
to delete google password lock use frp bypass, you can find it on youtube
Click to expand...
Click to collapse
Do not worry,
I didn't steal the cell phone. I bought it for my son on Christmas.
My son has his google account suspended because he changed his birth date. And now, you forgot your PIN.
I would like to resolve the impasse at home, avoiding sending the cell phone for assistance.
Could you point me to a reliable tutorial?
Best Regards.
denisxbr said:
Do not worry,
I didn't steal the cell phone. I bought it for my son on Christmas.
My son has his google account suspended because he changed his birth date. And now, you forgot your PIN.
I would like to resolve the impasse at home, avoiding sending the cell phone for assistance.
Could you point me to a reliable tutorial?
Best Regards.
Click to expand...
Click to collapse
on screen "download mode" you must click continue (volume up)!
this probably can work but i dont tested it
KaroloBC said:
on screen "download mode" you must click continue (volume up)!
this probably can work but i dont tested it
Click to expand...
Click to collapse
I didn't forget. ODIN doesn't recognize cell phone in download mode. It only recognizes when I try to start cell phone in normal mode. That is, drive is functioning properly.
Tonight I'm going to check out the video and try the procedure. I'll be back for a feeback.
@KaroloBC
Hi, My phone is A21s (SM-A217M) and doesn't go to that screen after sim pin lock part it stays on the screen with the three ringtones. I see quickly other, screen but stays on the screen with the three ringtones.
Unfortunately, I'm almost giving up.
Thanks for help!
@KaroloBC,
Works perfectly! I tried again and it worked!
Very thanks for indication.
My cell phone is A21s (SM-A217M) - Brazil.
want to unlock metropcs model number is SM-A215U.. downloaded odin , firmware as well as samsung driver. but unable to do unlock network... can some one guide me Thanks
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