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
Related
Hello, i'm a XDA noob and i have a Problem with my i9100.
I figuered out that i have a Soft Brick and thanks to the Guide i fixed that one.
The battery was full when i went sleeping. And half an hour ago everything seems to be fine. 95% battery, phone is working. I had flight mode activated and just deactivated it. I got an Error that the SMS app was closed, but everything was still fine. I locked the Screen, 5 minutes later i came back and it Soft Bricked again. (The first Soft Brick came from out of nowhere, too).
i Had the Original Samsung Stock 4.0.3 (the download from in the Guide) installed. It worked fine after Step 4.
Symptoms:
Does not boot
No Recovery
Download mode works if connected with USB
Loading works partially, the symbol apears, but after 9 seconds it disapears and after 6 seconds it apears again...
If i try to enter Download mode with low battery and no USB conection, i get a Screen warning that Battery is low
I Randomly get a Screen flicker which lasts about 0.1 - 0.5 seconds. The 0.5 ones show the Andorid logo who is installing something . I Think the 0.1 second ones show the same thing but i'm not sure.
Odin Flash works ! Here's the log
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_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> I9100_CODE_I9100XXLPH_CL118559_REV02_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_I9100XXLPH_REV_02_CL1104396.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> GT-I9100-MULTI-CSC-OXALPH.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> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> factoryfs.img
<ID:0/003> data.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After Odin it wont boot directly nor Recovery works, but if i wait a few minutes and change battery ( i have 2 batterys ) multiple times, it somehow starts to show the same old "andoird is working" screen and then boots in a nice stock Android 4.0.3.
Additional Information
I had installed CM 10.1 (with CWM) before. And it worked fine for months.
Someday the battery usage became extrem (there is a Problem with the SD card, because it's always saying the SD was removed and installed, checking for errors, and that costs a lot of battery power...
I deleted all the data/data manually and some system folders --> Boot Loop , so i decided to swich back to Stock Android 4.2.2. That worked fine, Memory usage is high too if using with a SD card. But OS was stable, till yesterday...
I neither connected my phone with Google yesterday, nor did i sign up with Samsung services, nor did i changed anything, nor did i installed apps.
Now my Question is:
What should i do to get a stable system? Is there any option to get my phone back to factory status? (no i don't mean factory reset, because this only change a few folders but not all on the phone...)
Thank you.
Search for a nuke script in order to get rid of previous ROMs leftovers.
Sent from the little guy
That seemed to work.
I installed CWM and CM 10.1, then i ran the script and after that reinstalled the newest version of CM10.1.
mac.2013 said:
That seemed to work.
I installed CWM and CM 10.1, then i ran the script and after that reinstalled the newest version of CM10.1.
Click to expand...
Click to collapse
Please add [SOLVED] to the title of ur post then.
"To err is human, to forgive is divine"
Sent from my SGS II
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...
Hey,
I am new here so feel free to move this thread if it's not in the right spot.
note:
So first things first. I own a Samsung s7 that's originally from the UAE(bought it on vacation). I live in the Netherlands so I guess there is a warranty issue with EU and MID-Asia.
Problem:
1. During web browsing, the screen turned off, the phone vibrated and the Samsung logo boot up screen popped up. Pressing the volume down and power button does restart the phone but I do not get passed this screen. I can not enter the recovery menu and the same goes for starting up in safe mode. So naturally, I googled and found out I had to flash the stock firmware with Odin. I did this followed the steps and it worked.
2. Fast forward one night. I wake up to find my phone died so I charge it up and voila, I am back to the same boot screen. I tried flashing again but this time it did not work. I went to a phone dealer(also does repairs), the guy looked at it, did the same thing I did and got the same results(did not work). His conclusion: motherboard fried.
But having the phone for less than a month I highly doubt it. I did not drop the phone, and it has not gotten wet. I do have a warranty but like is said in the beginning warranties are not international. And I am not going back anytime soon.
Question:
Is there anyone who can help me with the issue? Underneath you will find other specifics and also where I think things might have gone wrong.
Odin log file:
<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..
<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.1210)..
<ID:0/003> File analysis..
<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> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Things might have gone wrong:
Some old part of the previous flash files is on the phone which interferes.
Flashed the file of a wrong region (i used the Netherlands instead of UAE)
fast charger adapter fried the motherboard (going with the hypothesis the men gave at the store (motherboard fried))
I still can enter download mode
power button + volume down does seem to work
no response from volume up +home+power button
Any help or suggestions will be greatly appreciated.
Kind regards.
Try a flash stock firmware with odin
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
hey guys I'm need of some assistance, i tried to root my samsung A21s using odin after operation was done and exited download mode my phone keeps looping at bootloader and displaying with red on the left top corner 'fingerprint protection failed'.
i tried installing firmware but no change so far Please anyone who can Help?
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
Ramgalaxy said:
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
Click to expand...
Click to collapse
@Ramgalaxy is it possible for you to access your Recovery and is there a Red notification the top right?
kym605 said:
@Ramgalaxy is it possible for you to access your Recovery and is there a Red notification the top right?
Click to expand...
Click to collapse
top left i mean