Hello Awesome community of xda.
I have a problem and I would like to post it in here in order to gain tips on how to solve it
This is my problem.
I had CWM installed on my lg optimus l9 P760 device. I wanted to put it back to my stock software and i tried doing this by the use of KDZ_FW.
I was able to get into the FW updating mode on my device and connect it to my computer. I installed the drivers, msxml, and so i opened the program kdz_fw_upd. I tried flashing the stock .kdz file but then it said exactly this:
17:56:00 : Launching SW update
17:56:00 : Unpacking KDZ
17:56:05 : KDZ file extraced
17:56:07 : Files were extracted.
17:56:07 : LGMobileDL Load.
17:56:07 : Port = -1
17:56:07 : Connecting to phone
17:56:07 : PHONE WAS NOT FOUND!
17:56:09 : ===FINISHED===
I have tried windows enabler but it didnt work so I gave up.
Then I came up with the idea to install my stock from a winrar file using the recovery mode of CWM. I did this and it succeeded succesfully, then I tried to reboot and it was stuck on the loading screen. I can still get in fw updating mode but recovery seems to be impossible too.
I also tried flashing a recovery with the help of odin. this doesnt seem to work(the way I did it) neither here are the messages:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I need yar help and i hope you guys can come with a solution to fix my LG telephone^^
Thanks in advance!
Greetings, Keagon.
Related
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!
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...
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?
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.
Hello
Today, my phone was working perfectly fine until I got new update. After the update popped up, I decided to install it. My phone was not rooted or anything, was totally stock. After the update, the wifi wasn't working anymore. It connected to the wifi but it said "no internet access, try another wifi". I tested hotspot etc, all same. All my other devices worked just fine. So I decided to factory reset through recovery mode, which didn't help. I still couldn't connect to the wifi. Then I was going to try to reinstall firmware with Smart Switch, but apparently the big brains from Samsung removed the "device initialization" option from it.
The last resort was, Odin. I searched up the corresponding firmware for my phone (SM-G925F, from Belgium). I downloaded the firmware from sammobile, but after I only got 1 MD5 file, I assumed it was the AP (I searched on internet to confirm). After I tried to flash the new firmware with Odin, it failed. Now my phone wouldn't even start, I could blue screen "An error has occured while updating the device sofware. Use emergency sofware... blabla on smart switch". Ofcourse, we can't use that now anymore. I also tried installing older version of smart switch, but It said that the device is not supported.
So my question is, how can I fully reset my phone to stock with Odin? I am also using SamFirm to get the latest software with these options:
Firmware: SM-G925F
Region: PRO (Proximus provider - Belgium)
PDA/CSC/Phone: Auto
Binary nature: checked
PRO (Proximus) is set as the region. Proximus is a provider in Belgium. This is also the only region I can use in Belgium, all other regions don't work. My provider at this moment is Orange, but I don't know how to find the one from Orange.
I hope I'm doing something wrong and overseeing, otherwise I have no idea how to fix this anymore.
My firmware info:
PDA G925FXXU5EQH6
CSC G925FPRO5EQI2
My odin version: v3.12.3
Kind regards
Rekso
Edit 1: I finally got the files from SamFire. It passed CRC32 check, succesfully extracted the files. I fired up odin, put my phone into download mode, put all the AP, BL, CP and CSC files. When I clicked start, it failed, here is the log message:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit 2: When I try to flash, this is what appears on the phone: odin SW REV. check fail DEVICE 6 binary 5. I guess the firmware isn't correct? I also have the latest version of the 7.0 firmware for SM-G925F from SamMobile(and before my phone broke, I was also on 7.0).
FIX
So, after 8 hours of searching, even before I made this thread, I finally found the solution.
Alll you have to do is:
1. get the correct software from SamFire or sammobile.
2. Open Odin and put all the 3 files (AP, CSC and CP) in Odin. Make sure you do NOT put DL or it will not work.
3. Click start and your phone will be back to fresh start.
Hope this helps for people with same problem.
There is one problem though: I have no service. Is it because this firmware is from proximus? My phone was not branded (it was lockfree), now after I installed the firmware it became branded and I see proximus logo when the phone starts. This was not the case before. I also don't see my imei and basebrand anymore. Is there any way to fix this?
Regards
Unbranded firmware
Hello
As I mentioned in the post above, I got now problem with carrier. i did not want to create a new post so thats's why I am posting this here. Looks like I flashed a branded firmware (of proximus) on my unbranded samsung. Is there any firmware I can use which is unbranded and will not affect my carrier? At this moment I don't have any signal.
Will XEU / BTU firmware work?
Regards
-------------------------------------------------------------------------------------
EDIT: Fully fixed now, all you have to do is use XEU firmware (europe).