Please help i bricked my phone while installing another rom. Always failed - Fascinate Q&A, Help & Troubleshooting

First of all,I did everything step by step to install a custom rom to my Samsung Fascinate but odin says "Setup connection....
"All threads complete (success 0/failed 1)
Then,after my phone got bricked,I tried installing a stock rom, but the same thing happened :
<ID:0/006> 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/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP NEEDED I AM REALLY TENSED :crying:

Did you ever find a solution to your issue? I am having the same issue but I paid OneClickRoot to Root my device for me and they screwed it up and are pretty much throwing their hands up about it. I am still giving them the chance to make it right but my patience are wearing real thin.

To save you as long as it is not hard bricked, follow these steps.
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.
And please make sure you got the drivers and that a COM port does show up in odin.

Related

[Q] Can anyone help me with HUGE issues with encryption.

Hello, I've had huge issues trying to unbrick my tab.
When attempting a factory reset nothing happens. I suspect this is where the storage was encrypted on the last working rom... I'm struggling to get the tab to boot up now.
Can get into recovery but again, cannot do a full wipe as the storage will not mount.
Have tried reflashing back to stock via Odin and I'm getting the following in log.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XWALG7_N8000BTUALG6_N8000XXLGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Running out of things to try now. Anyone have any ideas of what to try next?
Let me know if you require any more information too please. Really tearing my hair out over this one, never had issues like this before that I couldn't resolve myself. Feels a little shameful having to ask tbh
What cwm do you use? And what ROM did you use? Did you just install it or are you using the ROM for a while?
Maybe, and i hope...this guide will help you any further, good luck
http://forum.xda-developers.com/showthread.php?t=1133590

[Q] Samsung Galaxy SIII Soft Brick Desperate Situation

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!

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

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

Fascinate won't turn on

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.

ODIN stuck on SetupConnection on Windows 10 trying to flash a GT-I9060I

ODIN is getting stuck at SetupConnections. I have twied diffrent USB cables and ports, diffrent ODIN versions, diffrent drivers, and 3 PC's. NOTHING WORKED. The phone is a budget Samsung Galaxy Grand Neo Plus(GT-I9060i). I am trying to reflash the bootloader after it decided to stop working randomly, but it is just refusing. Any help would be greatly appreciated.
radostin04 said:
ODIN is getting stuck at SetupConnections. I have twied diffrent USB cables and ports, diffrent ODIN versions, diffrent drivers, and 3 PC's. NOTHING WORKED. The phone is a budget Samsung Galaxy Grand Neo Plus(GT-I9060i). I am trying to reflash the bootloader after it decided to stop working randomly, but it is just refusing. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Send me a screenshot of your phone in download mode.......then I'll do something for you....
Sent from my GT-I9500 using Tapatalk
I can't post a image on here, but what is says is
ODIN MODE
SECURE DOWNLOAD: ENABLE
MDM DOWNLOAD BLOCK: 0
PRODUCT NAME: GT-I9060i
CURRENT BIN: Samsung Offical
SYSTEM STATUS: Custom
And in the middle of the screen there is a android and under it says "Donwloading..." and under that "Do not turn off target!!!"
And yes, i did try turning off and on... everything.
And yes, it was rooted before all of this started happening. It was actually rooted for a couple months by now
Bumpity Bump Bump
Bump, bumpity bump bump bump bump
another tiny bump
Ok. MOAR Info. The odin (after settupconnections) says "Can't open the serial(COM) port.". Why it is not able to open the COM port i have no idea.
radostin04 said:
Ok. MOAR Info. The odin (after settupconnections) says "Can't open the serial(COM) port.". Why it is not able to open the COM port i have no idea.
Click to expand...
Click to collapse
You had tried 3 PCs, different drivers,odins versions but have tried to change your Rom file which you are flashing, just download other Stock Rom package from sammobile and flash it via odin......
(And goto settings-> developer option-> enable usb debugging........then flash......your rom..)
I am gonna try to download a diffrent stock firmware, but i cannot boot up the phone to get to the developer settings in the first place.
Ok. so, I downloaded the new stock firmware from SamMobile (Which took around half an hour). But my last firmare came as 4 files, and this one came as 1. That didn't matter as ODIN STILL got stuck on SetupConnections forever.
This is what it says(I attached the same file to all 4 slots and this was using the oldest version i had - 1.85)
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_HOME.tar.md5 is valid.
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_HOME.tar.md5 is valid.
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_HOME.tar.md5 is valid.
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
radostin04 said:
Ok. so, I downloaded the new stock firmware from SamMobile (Which took around half an hour). But my last firmare came as 4 files, and this one came as 1. That didn't matter as ODIN STILL got stuck on SetupConnections forever.
This is what it says(I attached the same file to all 4 slots and this was using the oldest version i had - 1.85)
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_HOME.tar.md5 is valid.
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_HOME.tar.md5 is valid.
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_HOME.tar.md5 is valid.
<OSM> I9060IXXS0APH2_I9060IVVT0AOG1_I9060IXXU0APH1_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Do you have installed kies in your pc??
If yes, just completely unstall kies and drivers then restart your PC...
After PC boot up install drivers only (not kies)....
Finally, then open odin and flash your device.....
I hope it should work.....
I did uninstall KIES, but i didnt reinstall the drivers after that. Gonna do that as soon as my PC decides to start up(it's like the most unstable build ever)
Did everyting - still the same problem -
<ID:0/003> Odin engine v(ID:3.1203)..
<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)
Bumpity bump
Bumpity
bump
Buuuuuuuuuump
According to all known laws
of aviation,
there is no way a bee
should be able to fly.
Its wings are too small to get
its fat little body off the ground.
Ok enough, WHY IS NOBODY HERE?

Categories

Resources