Here's the rundown of what I did:
Using Odin 3.0.7 on Windows, I flashed a kernel from Sakuramilk, don't quite remember which one. The flashing succeeded according to ODIN but the phone wouldn't boot and I would get the Docomo Logo with the yellow triangle.
Following that I downloaded the stock kernel from Sammobile and tried to flash that (SC02COMMP4/SC02CDCMMP4), but since it didn't work I tried to flash + re-partition using a stock PIT file I found at some thread. The re-partitioning went through but the flashing failed half-way. The result of that was that now, when I try to power on the phone there's no logo, only a message on the top of the screen in green text:
'nps_fail_ntt.jpg' draw failed
Click to expand...
Click to collapse
my guess is that my re-partitioning with the PIT file broke the partitions and now it can't find the logo (or any other file).
So this is an almost bricked phone that can go into download mode and is seen by odin but now odin can't upload anything (I've tried a few stock kernels from sammobile). I always get:
<ID:0/003> Added!! <---- phone is .. recognized I guess...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SC02C-JB-KBC-20121031#36-SAM-odin.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Any advice on how get this phone flashed back to it's original state or any other working state for that matter would be very much appreciated.
Turns out that Odin 3.07 I had wasn't working well with sc-02c. I used Odin3 v1.85 and the flashing worked!
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...
Hi,
A few days ago, my device spontaneously soft-bricked itself (haven't installed any mods or stuff), and after a quick regression, it is now only able to boot into download mode (recovery mode sends it to a screen with white horizontal and diagonal lines..)
In download mode, it reads:
ODIN MODE:
product name: GT-I9300
Custom binary download: NO
Current Binary: samsung official
System status: custom
I have tried setting up cyanogenmod but haven't been able to flash their provided custom recovery, due to my computer being unable to download the PIT from the device.
I also tried using the master version of heimdall to do that, with no success.
I also tried recovering my device with KIES, but after downloading the firmware update to my computer, it gets into a load where it would be uploading said update into my device, but just hangs at 0%
I tried uploading a stock firmware using odin 3.07, and I recieved some error regarding my PIT file.
Finally I tried repartitioning with a downloaded PIT file but I got this message: <ID:0/003> Can't open the serial(COM) port.
My phone's status remained the same so I am pretty certain that I haven't caused any further damage to it.
Sooo, any ideas?
If possible, I would very much prefer to install CM on it, and am considering rooting it, but most importantly i'm dissapointed with samsung's default os.
Thanks in advance,
Macro
If odin cant see it you've buggered it proper.
The method was
Install cfautoroot
Install clockwork recovery (official, custom borks your phone).
Install cyanogenmod (via cwm).
The error with the pit file would most likely be a bad file or wrong version. Playing with the partition table is a no-no and a last resort only.
If you can get odin to see the device in download mode you can flash stock and start over. If not, you have an expensive paperweight.
Samsungs "os" is bada. I think you mean "overlay". I agree. Touchwiz is rubbish but i think samsung only do it to grate some apple.
I wish I stole my HTC M9.
Hi! Thank you for the reply
I tried earlier to download a stock and flash it with odin (3.07) and got the same pit file error, specifically this:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGMK1_I9300JKUGML1_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
What kind of wrong files would I have? Are you talking about the cfautorout version for my model, or do you mean that I should use a different odin version?
macrokrome said:
Hi! Thank you for the reply
I tried earlier to download a stock and flash it with odin (3.07) and got the same pit file error, specifically this:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK7_I9300OJKGMK1_I9300JKUGML1_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
What kind of wrong files would I have? Are you talking about the cfautorout version for my model, or do you mean that I should use a different odin version?
Click to expand...
Click to collapse
As I see you should send your device for a repair. It says there is no pit partition that as I know it mean there is no pit partition in your device!! So you totally messed it up and don't know what you have done but it needs a repair.
As oddly as it sounds, I had practically nothing on it. Never messed with it or anything. Barely any apps, no root/mod/whatever.
After looking into it with a friend, it seems like this problem is called SDS, and I saw some references to it over here:
http://forum.xda-developers.com/galaxy-s3/general/ultimate-gs3-sudden-death-thread-t1993044
I will look into it tomorrow afternoon once I'm free, but according to my friend, this would require a replacement motherboard... Might as well buy a new phone, lol
Still, if you have any ideas, I'd be happy to hear them. Thanks for your help up until now
Hey guys, I have this Verizon Fascinate that I used to use when I was wayyy younger. Back then I was using it, deleted a wrong folder when I was browsing through the My Files app, and it hasn't turned on since. If I try to power it on, all I get is a white screen that continues to flash. I've looked at all of the other threads about resetting the Fascinate to stock with Odin and Heimdall, and I've tried the steps given there, but it hasn't helped. I can still set it to download mode, and I can still charge it with the charging battery screen, but no recovery/boot up what so ever. I tried flashing multiple stock firmwares in Odin with the stock pit file or the atlas pit file, but this is all I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
The phone wasn't rooted before and didn't have any sort of custom rom on it. Any help would be greatly appreciated by those still browsing these forums.
MexicanBRUHH said:
Hey guys, I have this Verizon Fascinate that I used to use when I was wayyy younger. Back then I was using it, deleted a wrong folder when I was browsing through the My Files app, and it hasn't turned on since. If I try to power it on, all I get is a white screen that continues to flash. I've looked at all of the other threads about resetting the Fascinate to stock with Odin and Heimdall, and I've tried the steps given there, but it hasn't helped. I can still set it to download mode, and I can still charge it with the charging battery screen, but no recovery/boot up what so ever. I tried flashing multiple stock firmwares in Odin with the stock pit file or the atlas pit file, but this is all I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
The phone wasn't rooted before and didn't have any sort of custom rom on it. Any help would be greatly appreciated by those still browsing these forums.
Click to expand...
Click to collapse
To do it, get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
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