Odin sucks - Galaxy S I9000 General

I tried flashing a firmware with Odin.
It got stuck on "setup connection".
I tried again, same problem.
I tried again, flash went trough, but got stuck on flashing modem.bin
I rebooted, phone didn't boot
I tried flashing again, stuck at the same place.
Then I gave up and tried Heimdall, everything worked fine.

Constructive thread. Thanks.
Sent from my Galaxy S using XDA Premium App

Kies is even worse!!!

zorxd said:
I tried flashing a firmware with Odin.
It got stuck on "setup connection".
I tried again, same problem.
I tried again, flash went trough, but got stuck on flashing modem.bin
I rebooted, phone didn't boot
I tried flashing again, stuck at the same place.
Then I gave up and tried Heimdall, everything worked fine.
Click to expand...
Click to collapse
You can really see the intelligence oozing out of you.
Oh wait, no... That's definitely not intelligence.

Seriously guys, am I the only one facing such issues? Is it common for Odin to fail?

Do you have Kies installed? if so, was it running in the background? (it has two processes visible in task manager)
These have caused me issues unless killed. Otherwise, can I ask which version of Odin you were using?
Flake x

zorxd said:
Seriously guys, am I the only one facing such issues? Is it common for Odin to fail?
Click to expand...
Click to collapse
It has failed on me in the past. Of course, solving it was only a matter of retrying. I've used in more than, I'd say, 500 times. I believe it has failed me twice.
If Heimdall works for you, I'd suggest sticking with that.

n99flake said:
Do you have Kies installed? if so, was it running in the background? (it has two processes visible in task manager)
These have caused me issues unless killed. Otherwise, can I ask which version of Odin you were using?
Flake x
Click to expand...
Click to collapse
I looked in the process list for anything kies or nps but didn't find any.
I think I removed kies from the startup some times ago.
I tried Odin 1.82

zorxd said:
Seriously guys, am I the only one facing such issues? Is it common for Odin to fail?
Click to expand...
Click to collapse
Why not be happy that you got Heimdall to work?...
Sent from my MB860 using xda premium

I've never had any trouble with Odin, are you sure you use it correctly? you know, like getting your phone in download mode first, installing drivers, use a Odin firmware and not a CWM one, etc.

I think in task manger theit kiestrayagent and another one. Kill them before launching Odin and attaching USB cable to your laptop. Odin works fine although sticking on setupconnection is normal nd happens.
hit thankxx if i helped. sent from my mind through telepathy (ya its possible)!

gtluis said:
I've never had any trouble with Odin, are you sure you use it correctly? you know, like getting your phone in download mode first, installing drivers, use a Odin firmware and not a CWM one, etc.
Click to expand...
Click to collapse
Yes. Or the transfer wouldn't even start.

Never any issues with Odin or Kies. And I flash alot. Also I like to reinstall windows pretty often, reinstalling KIES and Odin still no problems.

Never had any problems with Odin, 4 or 5 flashes now without incident.
Sent from my GT-I9000 using XDA App

zorxd said:
I looked in the process list for anything kies or nps but didn't find any.
I think I removed kies from the startup some times ago.
I tried Odin 1.82
Click to expand...
Click to collapse
Odin 1.82? As I know there's 1.0, 1.3 and 1.7. Maybe you're using Odin made for other Samsung device...
Sent from my GT-I9000B using XDA App

I use Odin 1.82 since a few month: never have issue (and never have issue with previous version...)

Related

I need help restoring my phone - odin wont flash it

Background is, I was flashing JAC's latest kernel onto my phone, which I had done twice before. Unfortunately, ODIN was getting stuck at zimage. After trying a few times, I decided to go back to the version of the kernel I was running previously, which I knew worked. I tried to flash the kernel but odin kept getting stuck on zimage again.
I tried restarting the computer, battery pulls on the phone, different usb ports and nothing has worked.
In desperation I tried to flash the stock firmware back, but ODIN gets stuck at cache.rfs.
Did I brick my phone?
Which version of windows are you using? Try from a different computer.
the3dman13 said:
Which version of windows are you using? Try from a different computer.
Click to expand...
Click to collapse
Windows 7 32bit. I've also tried a computer running xp home.
My main pc runs windows 7 64 bit, but odin doesn't work on it, even in compatibility mode.
The phone is f'ed. Im going into the tmo store this morning, I hope they dont give me a hard time.
ArbitrageMan said:
My main pc runs windows 7 64 bit, but odin doesn't work on it, even in compatibility mode.
Click to expand...
Click to collapse
BS! Heh, I restored my phone using ODIN flasher. I have windows 7 64 bit. I don't have to do anything special, just followed directions and it worked. Make sure you have 64 bit Samsung Drivers.
zaduma said:
BS! Heh, I restored my phone using ODIN flasher. I have windows 7 64 bit. I don't have to do anything special, just followed directions and it worked. Make sure you have 64 bit Samsung Drivers.
Click to expand...
Click to collapse
Done. The phone is detected by odin in 7 - 64, but when I try to flash, odin throws up a couple of messages in chinese and then sits there doing nothing. It never starts the flashing process.
hey did you fix your phone...im having the same issue
You guys try flashing anything via clockwork recently? There are recovery images for stock inside the odin thread from jac and stock I images for a kernel in his kernel thread... That's if you can even get into recovery now.....
Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...
on the same boat any other solutions
have you guys tried the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Here is another good thread to check out.
http://forum.xda-developers.com/showthread.php?t=1013967
Flag eugenes froyo that doesn't brick. Look it up it will fix it
Sent from my SCH-I500 using XDA App
No idea if this will help, but make sure you are using a later version of Odin (1.7 or above).
Also might try flashing with Heimdall. Works very well in my experience.

Can not update Manually

I have tried to update manually but cant. I have downloaded the file from samsung, put on root of card as update.zip and tried to install from clockwork. Is this the wrong way to do it.
I am on all stock and have clockwork installed. I downloaded from the link that has been provided from samsung It says E:Error in /sdcard/update.zip
Firmware version-2.1-update1
Build Number-SPH-D700 ECLAIR.DI18
So is there something I am doing wrong?
If you're using clockwork, you aren't on stock. Last resort is to use the flash utility that Samsung provided. It completely wipes your phone (not your sd card).
nubsors said:
If you're using clockwork, you aren't on stock. Last resort is to use the flash utility that Samsung provided. It completely wipes your phone (not your sd card).
Click to expand...
Click to collapse
Is there a way to remove clockwork besides going back to stock? Also since I do have clockwork installed, will I not get the ota update to work correctly?
I can tell you what I know.
1) The official OTA update does not work with non-stock roms. In your case, your rom became non-stock once you installed CWR.
2) The flash utility provided by samsung will take any epic and clear it of user data and the existing rom and then flashes the 2.2.1 official rom. Your SD card will be untouched, at least mine was.
3) You can always re-root after you've flashed the official release. Do a search in this forum and you can find threads that explain how.
Good luck sir.
Just go get the cwm flashable pre-rooted eb13 rom that dameon87 posted in the dev section. There's also a link to it in the wiki.
DiGi760 said:
Just go get the cwm flashable pre-rooted eb13 rom that dameon87 posted in the dev section. There's also a link to it in the wiki.
Click to expand...
Click to collapse
Any difference between that and the one you can download from samsung or what you would get from OTA?
mynewepic10 said:
Any difference between that and the one you can download from samsung or what you would get from OTA?
Click to expand...
Click to collapse
Need to know too.
DiGi760 said:
Just go get the cwm flashable pre-rooted eb13 rom that dameon87 posted in the dev section. There's also a link to it in the wiki.
Click to expand...
Click to collapse
That one did not work. Do I need to try to get the one that is not signed. I dowloaded the signed one and it did not work. After the install it tried to boot up, but went to the samsung screen and then into the official factory restore mode and tried to reboot and stuck on samsung screen.
Use the unsigned one. The only difference betwen the flashable and the one from samsung is the flashable is deodexed.
Sent from my SPH-D700 using Tapatalk
s9ortner said:
Use the unsigned one. The only difference betwen the flashable and the one from samsung is the flashable is deodexed.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks doing that now.
I had the same problem. Will try odin method when I get home, but I doubt that will work. Didn't work with the developers froyo.
Sent from my SPH-D700 using XDA App
I can't get the manual to work - mine is rooted and rommed, but my husband's is stock.
I have downloaded direct from Samsung 3 times. Once loaded on computer and opened, the Eula doesn't even have the Next button which is needed to proceed.
So strange, guess he will wait for the OTA and drain his battery at an inconvenient time!!
s9ortner said:
Use the unsigned one. The only difference betwen the flashable and the one from samsung is the flashable is deodexed.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I tried both of them and neither one of them worked.
nmoreman said:
I can't get the manual to work - mine is rooted and rommed, but my husband's is stock.
I have downloaded direct from Samsung 3 times. Once loaded on computer and opened, the Eula doesn't even have the Next button which is needed to proceed.
So strange, guess he will wait for the OTA and drain his battery at an inconvenient time!!
Click to expand...
Click to collapse
I'm getting the same problem with the samsung update software. I click yes to accept
And there is nothing that says next, just exit. I am getting errors using odin too. My computer
will see my phone just fine.....until I put it in download mode and try to connect with odin.
I keep trying to repair modem and restart computer to no avail. Its just weird how it all changes for the worse in DL mode. I don't know what to do....
Sent from my epic that is stuck forever on 2.1
funeralplanner said:
I'm getting the same problem with the samsung update software. I click yes to accept
And there is nothing that says next, just exit. I am getting errors using odin too. My computer
will see my phone just fine.....until I put it in download mode and try to connect with odin.
I keep trying to repair modem and restart computer to no avail. Its just weird how it all changes for the worse in DL mode. I don't know what to do....
Sent from my epic that is stuck forever on 2.1
Click to expand...
Click to collapse
If you are using odin try this.
Start odin on your PC first and have it up.
Put phone into download mode
Plug in your phone via usb and see if that helps.
It already sounds like you have the samsung drivers installed, but check to make sure.
mynewepic10 said:
If you are using odin try this.
Start odin on your PC first and have it up.
Put phone into download mode
Plug in your phone via usb and see if that helps.
It already sounds like you have the samsung drivers installed, but check to make sure.
Click to expand...
Click to collapse
Well I gave that a try. No go. I have tried everything I know. Two different computers, both xp. I can't even use the samsung utility because I keep getting the cant connect to usb. When it isn't in download mode i can connect to the computer, both computers just fine. It will tell me what phone I have and all. I just don't get it. Maybe I will just delete driver and install again. Is it a phone problem?
funeralplanner said:
Well I gave that a try. No go. I have tried everything I know. Two different computers, both xp. I can't even use the samsung utility because I keep getting the cant connect to usb. When it isn't in download mode i can connect to the computer, both computers just fine. It will tell me what phone I have and all. I just don't get it. Maybe I will just delete driver and install again. Is it a phone problem?
Click to expand...
Click to collapse
I have used a different version of odin with no issues at all. I have never used this one before.

HELP phone, yeild, computer sing! (BRICKED?)

PLEASEEE!!! help me out i tried upgrading from kies mini to froyo. I did this with success earlier in the past on my old vibrant but had it replaced to a referbished one and i tried upgrading it now.. but my vibrant was stuck at downloading the uprade on kies mini at 1% for half an hour... and the vibrant had the android shoveling yellow sign saying do not turn off target... for half an hour as well.. I knew something was wrong there because it didnt take even close to that long last time..
NOW I tried unplugging the usb wire restarting the phone in emergency mode still nothing... now all i have is a cellphone...yeild sign... computer icon showing..
PLEASE HELP!!!
Dont worry you totally didnt brick your phone. Its pretty common, can you get your phone into download mode? If you can then just odin to stock.
1.Take your battery, sim card and SD card out
2. Plug in USB Cable
3. Hold volume up/down and plug in battery (There are a few ways of doing download mode and I believe its phone specific, or if you have bootloaders installed its different as well, google around a bit...
4. Start odin and presto, your phone works again!
hey thanx... I just did that.. I never used odin but i installed odin with all the files... I believe my vibrant is hardware locked because i was trying to get into download mode for 2 hours with different techniques.. such as just volume keys and power button... taking out the battery holding volume keys then putting it back in.. but nothing put me into a downlaod mode... somehow odin still found my phone while i was still stuck under that picture...
I loaded the .pit file without the jfd image.... becuase i didnt know what window i was suppose to load the jfd image from... like pda.. or etc???
anyway so i just loaded the .pit file and clicked start it reset the phone and the phone went into restart mode and it turned on fine i checked it works fully... lol.
It makes no sense... was i suppose to load the jfd file somewhere?????
i still want to upgrade my vibrant to 2.2... but now whenever i turn on the keis mini it promps me to emergency recovery upgrade... so i tried doing that and went into download mode since now i can.. and plugged in my phone but the progress bar on my computer for upgrading never moved from 0%... its odd... am i doing something wrong?
so again i disconnected and "bricked" my vibrant again lol... went into odin followed the same steps just loading the .pit file and it reset the vibrant back to normal again lol...
Im so confused yet happy that i have my phone working but i still want my froyo... i love the fact that i can use yahoo video messaging on it with froyo and have flash and other benefits..
any advice?
Thanx again
try this...........
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
put pit in pit and tar in pda on odin
Connect it to the PC and see if ODIN recognizes it.
If it does, you are safe, flash stock.
EDIT: nvm, didn't notice the third post was yours.
Anyways, if ODIN can STILL recognize it, get the first from the link on the post above, FOLLOW INSTRUCTIONS and enjoy your again-useful phone.
I had that same issue once.
Try a JIG. And do a search, I see like 50 posts a week like this.
First.
Thank you all for taking your time to help. I have one last question... since I used Odin but it just reset my phone and I didn't flash the old firware on it..... ever since that now I tried to update my phone with kies mini and it says phone unregistered... in that place before it used to say new firmware available and showed old forward numbers/letters.
So if I use odin all the way will this resolve "unregistered device" problem?
Thanx again
Sent from my SGH-T959 using XDA App
AlexSochi8 said:
First.
Thank you all for taking your time to help. I have one last question... since I used Odin but it just reset my phone and I didn't flash the old firware on it..... ever since that now I tried to update my phone with kies mini and it says phone unregistered... in that place before it used to say new firmware available and showed old forward numbers/letters.
So if I use odin all the way will this resolve "unregistered device" problem?
Thanx again
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It should.
Sent from my GT-I9000 using XDA Premium App
Bricked
I have a similar issue, was soft bricked, Odin to stock then, while using Mini Kies to upgrade back to Froyo the phone turned off and never came back on. I cannot get any response from the phone as far as light's or sounds. Checked a few batteries and still no use. I'm curious if anybody else has had a similar experience?
so if it should solve the unregisted problem... where I put in the pda file... is it possible to put in the last froyo there so odin could flash froyo on my phone so basically i wont have to go through kies process?
odin back to 2.1 then root and then flash a 2.2 rom way better then a stock 2.2 rom
Dan_Brutal said:
Try a JIG. And do a search, I see like 50 posts a week like this.
Click to expand...
Click to collapse
I might be late to the party but I've built a jig and I can't believe how quickly this thing saved my ass...
Sent from my GT-I9000 using XDA Premium App
dsuycott said:
I might be late to the party but I've built a jig and I can't believe how quickly this thing saved my ass...
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yeah man. Jigs are the balls. Saved my ass this morning with a bad bootloader flash. I got lucky though.....
Sent from my GT-I9000 using XDA Premium App
Make sure you have the right odin files, once you have gotten back to normal just do a factory reset on your phone if that is possible. Then root, flash, and do whatever you want to do. Without your proper files for odin you'll get bricked or get something different.
How screwed am I? Odin doesn't recognize phone, vibrant aio toolkit can't adb phone into recovery or download mode. Flashing different rom screwed up during kernal phase and I stupidly rebooted phone. I CAN use a jig I bought to get into download mode but computer Odin doesn't 'see' it.
Sent from my GT-I9000 using XDA Premium App
dcboi said:
How screwed am I? Odin doesn't recognize phone, vibrant aio toolkit can't adb phone into recovery or download mode. Flashing different rom screwed up during kernal phase and I stupidly rebooted phone. I CAN use a jig I bought to get into download mode but computer Odin doesn't 'see' it.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Do you have the drivers installed on your PC?
Sent from my GT-I9000 using XDA Premium App
Dan_Brutal said:
Do you have the drivers installed on your PC?
Yes, not sure what changed but I plugged the phone in again and Odin recognized it, the file I loaded is PDA_T959UVKB5.tar.md5, the process has hung up at SetupConnection...
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA Premium App
id keep trying it odin is finicky! maybe try different usb ports
ok guys i know i aksed for a lot of help.. but i have a newly discovered problem.. when i connect my vibrant thru the original usb port to transfer files back and forth it never lets me transfer even the smallest picture image... on both internal 16gb or sd... the phone computer just constantly shows transferring animation.... i tried many times.. i even scanned the phones hard drive and sd card for errors... nothing... could it be i messed something up with kies? or thats why kies in general never went with the upgrade past 1%?
its a refurbished phone.. when i got it.. i uploaded my old pics without a problem with the same usb cable..... its weird.... i dont know what to do? what is it likely the phone itself or i messed it up with kies upgrade????
please help.. its frustrating me

Can't update after soft brick recover

So I just recovered from a softbrick using the Heimdall method. I'm stoked because I'm no longer bricked but I cannot flash anything via Odin now, even after I have re-installed my Samsung USB drivers. It always gets to SetupCS connection or something like that and just stays there. Is there something I'm missing?
What driver is on your system? Is it the fascinate or the nexus s? If you're coming back to some level of stock from a GB rom you might still have the GB (nexus s) drivers. You might have to reload the froyo fascinate drivers for odin to work.
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
So I just recovered from a softbrick using the Heimdall method. I'm stoked because I'm no longer bricked but I cannot flash anything via Odin now, even after I have re-installed my Samsung USB drivers. It always gets to SetupCS connection or something like that and just stays there. Is there something I'm missing?
Click to expand...
Click to collapse
as long as you get the yellow "com" with a number underneath the box in odin, drivers are not the issue.......try re-downloading the odin package and then flashing it again
kidserious said:
as long as you get the yellow "com" with a number underneath the box in odin, drivers are not the issue.......try re-downloading the odin package and then flashing it again
Click to expand...
Click to collapse
That was my thought as well but its doing it with 3 different Odin packages. This is where I get lost but am I supposed to put the atlas.v2.2 pit in with everything now? I'm at a loss I guess. Phone is functional on ED03 currently but I'm stuck at stock it seems...
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
That was my thought as well but its doing it with 3 different Odin packages. This is where I get lost but am I supposed to put the atlas.v2.2 pit in with everything now? I'm at a loss I guess. Phone is functional on ED03 currently but I'm stuck at stock it seems...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
the atlas 2.2 pit file goes in the "PIT" section at the same time as the tar.md5 file goes in the "PDA" section and re-partition checked......when those two files are placed in their respective slots and re-partition is checked, THEN you hit start on odin. If that doesn't work, place this file on the root of your SD card and rename it "update" but without the quotation marks lol: http://forum.xda-developers.com/attachment.php?attachmentid=556632&d=1301538910 Once you do that, boot in the stock blue recovery using the 3 finger method and select "apply SDcard/update.zip" and let me know what happens
Many thanks to you sir. I'm at work currently but ill try this out as soon as I get home.
Sent from my SCH-I500 using XDA App
By the way... what file is that? I'm just curious
kidserious said:
the atlas 2.2 pit file goes in the "PIT" section at the same time as the tar.md5 file goes in the "PDA" section and re-partition checked......when those two files are placed in their respective slots and re-partition is checked, THEN you hit start on odin. If that doesn't work, place this file on the root of your SD card and rename it "update" but without the quotation marks lol: http://forum.xda-developers.com/attachment.php?attachmentid=556632&d=1301538910 Once you do that, boot in the stock blue recovery using the 3 finger method and select "apply SDcard/update.zip" and let me know what happens
Click to expand...
Click to collapse
Alright so I just tried adding the PIT, repartition checked, and added my ODIN package, but still had the same problem. About to install the CWM All file you gave me and try that out.
*edit* Well something just happened. My SD card just got corrupted and I cant even format it now. What the hell is going on?!
*edit 2* OK so the SD card issue fixed itself. Just had to hit format a billion times. I'm now running an OTA update to my phone from Verizon as I had to go all the way back to DI09.
*edit 3* I'm now sitting on ED04 fully stock but away from my computer. I will try again once I get home later on tonight. Just out of curiousity... has anyone else other than kidserious and the other guy had this problem or have experience in dealing with it?
So checking in again. I am still freezing at "SetupConnection..." in Odin. No luck at all with flashing the CWM ALL file as "update". I'm completely out of options at this point. Help?
MR H3LLMAN said:
So checking in again. I am still freezing at "SetupConnection..." in Odin. No luck at all with flashing the CWM ALL file as "update". I'm completely out of options at this point. Help?
Click to expand...
Click to collapse
Let me rack my brain and think........I will get back to you.
RESOLVED
Alright so I finally figured out my own way around this. It was actually fairly simple and I'm a bit ashamed I didn't think to try this earlier.
Hopefully this will be of assistance for any future issues. Thanks Kidserious for your help.
*edit* So I just found some instructions for uninstalling the Heimdall driver from your phone. I'm booting up after a fresh flash of DI01 and hopefully this will work. I'm guessing that even though I'm installing the samsung usb drivers back to my computer, they arn't reaching my phone, and this may be the issue I've been facing. *pauses for a bit to test theory* Yep. That was all it was. Sorry for taking up so much room on here... just FYI to everyone though. If you soft brick and recover via Heimdall you HAVE TO UNINSTALL THE HEIMDALL DRIVER OR NOTHING WILL WORK.
FML. So it didnt work as I had planed. After I flashed my edify rom I samsung bootlooped. And Odin still isnt working for me.
I'm giving up for tonight. Functioning on DI01 stock ): at least it works...
Alright so I'm fairly certain I've narrowed it down to one fix but I seem not to be able to fix it. I need to install the samsunflg husband drover back to my phone and uninstall the heimdall driver. I've tried it twice and or hasn't worked either time
Sent from my SCH-I500 using XDA App
---actually resolved----
Sorry for spamming this thread everyone, even though I've really been the only person posting in it anyways.
I have found my fix. So I was never able to fully uninstall the Heimdall drivers so Odin wouldn't recognize my phone and would hang at "Initalization."
So I took a weird strategy and actually purposely soft bricked my phone. Scary to do but the outcome was well worth it. Here is what I did.
1.) Puropsely soft bricked phone
2.) Put it in to download mode
3.) Went to device manager
4.) Contrary from Heimdall Uninstall instructions phone will now show up under the general usb devices areas. Find this area, expand, and right click on Samsung Composite USB Device.
5.) Go through the options of manually picking the usb driver you want to use.
6.) Install chosen standard samsung USB driver. You may get many options in the list but pick the Digitally Certified one.
7.) I didnt unplug the phone after I flashed the new driver so open up Odin and flash your DI01 Stock Recovery with Atlas v2.2 PIT and Repartition checked.
8.) Once finished phone will be on DI09 fully bloated stock and should work with Odin for any further flashes.
*edit* It appears as if you need to flash the samsung driver to phone evrytime you want to flash something via Odin.

Stuck on boot, need some help

ok, so I am not a noob on rooting and such, but this one has me stumped. Have the i337 on mdl baseband. Wanted to return it to stock. I tried to Odin (v3.09) the factory tar from the samsung site, i got a failure, then it went to recovery mode saying to connect kies. I have tried kies 2.6 and 3.0, neither recognize the device. I have tried redownloading samsung firmware thinking it was corrupted and mk2 firmwares in odin, neither worked, they go immediately to fail when i try to execute Odin. I can get into download mode or the kies recovery mode, not sure what to do since it will not take odin. Any ideas?
aawshads said:
ok, so I am not a noob on rooting and such, but this one has me stumped. Have the i337 on mdl baseband. Wanted to return it to stock. I tried to Odin (v3.09) the factory tar from the samsung site, i got a failure, then it went to recovery mode saying to connect kies. I have tried kies 2.6 and 3.0, neither recognize the device. I have tried redownloading samsung firmware thinking it was corrupted and mk2 firmwares in odin, neither worked, they go immediately to fail when i try to execute Odin. I can get into download mode or the kies recovery mode, not sure what to do since it will not take odin. Any ideas?
Click to expand...
Click to collapse
1. Kies and Recovery mode aren't same thing. Kies never will recognize your device being in Stock Recovery Mode. Don't mix things.
2. Find the error now is difficult coz maybe you update your bootloader with the MK2 firmware (that's android 4.3 no android 4.2.2).
3. Get me the errors or one screenshot that appears in ODIN when you try to flash the MK2 firmware pls.
I'll see what I can do, it happens so fast I don't think anything updates, and it shows me no errors, just fail
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
I'll see what I can do, it happens so fast I don't think anything updates, and it shows me no errors, just fail
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe Kies was in your task bar when you tried to flash through ODIN?
Not the first but maybe the last ones, what does that do?
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
Not the first but maybe the last ones, what does that do?
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Close completely Kies before run ODIN and try again to flash the old bootloader. Tell me how works
Joku1981 said:
Close completely Kies before run ODIN and try again to flash the old bootloader. Tell me how works
Click to expand...
Click to collapse
ok, ran it, failed again, hereare the screenshots with the complete message portion.
aawshads said:
ok, ran it, failed again, hereare the screenshots with the complete message portion.
Click to expand...
Click to collapse
1. Try other version of ODIN. I recommend you the latest one -> HERE
2. And pls.... MK2 isn't firmware for your device, it's for i337M. Don't mix things. Flash MDL again if you had that baseband and show me what errors you will have in ODIN. Good luck
Still failed. Let me know what you see. thanks
Bump, anyone see what I is wrong?
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
Bump, anyone see what I is wrong?
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you're on the mdl bootloader?
Sent from my Nexus 5 using XDA Free mobile app
Pit file
I see youre trying to flash the mk2 file but you dont have the pit file for the repartition head over here and download the mk2 pit file and then rerun it I also see that you have auto reboot checked, uncheck the auto reboot and then once iit finishes flashing and say reset unpluget you're device and pull the battery then put it back in and go into stock recovery by holding volume up power and home all at the same time and wipe data factory reset and cache partition http://d-h.st/5gz
Thanks, but that did not work either. I have never had a problem I couldn't odin out of, but I have tried everything I can think of and still nothing will work. I just want to sell the phone so I even tried the nb1 which should install no matter what bootloader I am on, and still nothing.

Categories

Resources