I will give this a last chance before I am throwing this piece of junk out of the window.
Galaxy S3 i9300 doesn't turn on at all. Stuck on logo.
Recovery mode (VOLUME UP) doesn't work at all. Shows white and black screen. Before that used to be stuck at DOWNLOAD MODE forever.
Custom mod (VOLUME DOWN) works.
I am connecting it to the PC, it is recognized.
I don't manage to do anything with ODIN.
Trying ODIN 2.10, tried also older one's. Newer one has different fields for some weird reason.
It shows that the phone is connected: 0:[COM3]
I am loading the PDA file and clicking START, it says NO PIT FILE found.
What pit file? no one talks about any PIT file anywhere. Everyone just says to load the PDA file.
If I click on START again it will say <ID:0/003> SetupConnection.. endlessly.
Tried to load some PIT file I found for S3, of course that fails also.
in Kies it connects endlessly.
Any other ideas?
Thanks
Are you using the original Samsung USB cable and a USB 2.0 port? Try Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
audit13 said:
Are you using the original Samsung USB cable and a USB 2.0 port? Try Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Click to expand...
Click to collapse
I think so, but i will try with another cable and report back.
The link you provided doesn't work.
Thanks
Hmm, try this: http://d-h.st/hSj
I tried another cable and nothing changed. Both should be original, yes. Besides how is it related to the PIT error?
Exactly the same on this version also. (I am trying without PIT file)
Without a data cable that is compatible with Odin, Odin can't read the partition information table in the phone.
Pull your battery, replace then try again, it should then work
Sent from my A0001 using Tapatalk
racky29 said:
Pull your battery, replace then try again, it should then work
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I probably did it around 50 times in the past couple of hours, when I was playing with Odin.
audit13 said:
Without a data cable that is compatible with Odin, Odin can't read the partition information table in the phone.
Click to expand...
Click to collapse
I just tried with a 3rd cable. It doesn't seem to be the issue.
What is the exact error message in Odin? You can copy and paste the log here.
I know that I would get pit errors when I would used random USB cables to flash s2, s3, s4, note 2, note 3, etc. Going back to a short, original, Samsung USB cable always worked for me.
Before pasting, I have to choose just the PDA and that's it, right?
No need to provide the PIT file?
Yes, flash stock ROM in pda. Pit file isn't needed unless you need to partition the memory.
I tried with a 4th cable now.
I get the same error.
Could it be that i am using the wrong PDA or something?
<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)
Re-Partition was not selected. Tried it on 1.85
Another confusion is that I have downloaded 2 firwmares from different sites (both claiming it's official) and they have completely different sizes:
1. International-GT-i9300-StockRecovery.tar - 5521KB
2. GT-I9300_Boot_Recovery.tar - 870KB
Now I am downloading a 3rd one:
PRO-I9300XXALF5-20120620165344.zip - 740.23 MB
What size should be??
whatever61 said:
<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)
Re-Partition was not selected. Tried it on 1.85
Click to expand...
Click to collapse
Try with Odin 3.07 and use the original Samsung USB cable.
It's same on all versions and all cables.
I don't think a version or a cable is the problem.
All I can say is that I would sometimes get the same error when flashing s2, s3, s4, s5, note 2, note 3, and note 4 until I used a short, original, Samsung USB cable on a USB 2.0 port with Win7 x64.
Related
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
hhp_211 said:
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
Click to expand...
Click to collapse
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
uslacson1 said:
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Click to expand...
Click to collapse
zachsx said:
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey thanks for quick responses.
I currently have the 'Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate.msi' Driver installed
I believe I had installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe before when I was trying to get it rooted.
I have not yet tried a different USB port... I will and get back to you...
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
I have downloaded 3 different times both files, so I don't know ????
different USB port ... same result...
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
When you say odin patch I guess you mean the 'CWMrecovery.tar'
I can unpack it and I have a 'recovery.bin' and a 'zImage' inside the file.
both 5081 KB in every 'CWMrecovery.tar' that I have.
Weird. My old copy from Nov. 26 is 9.93MB (10,414,130 bytes). It contains zImage and recovery.bin, each 5,202,168 bytes. I must be wrong, then.
EDIT:
Just for sake of good practice, I did look up the md5 for that file and I did download it again, and they do match. There are a lot of ways to get MD5s, I used a program called digestIT 2004 to generate it.
http://goo.gl/HELdr
ecfeb7b1633786c1ae9dfb276bfeb231 CWMrecovery.tar
I had no problems downloading it, the hosting is good. It's highly unlikely that I was right about resolving your Odin error.
Sorry I can't be more helpful. I did this once way way back when and had no issues. I did have an issue with a modem.bin packed in a tar later on, and the errors looked a lot like what you are getting now, so I assumed it was the same problem. Thanks for humoring me, and good luck.
I'm a nub.. help..
So I've been trying to follow directions here, but I feel I'm missing something very simple... I cant even get this restore started, it keeps telling me "Invalid Image Type" when i select the CWMrecovery.tar file?? help??
it could be that Kies, or other application that uses USB connection is active.
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
New to rooting btw
However i do get this error come up;
screensnapr.*com/e/ZXruBp.png
xSirAKx said:
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
Click to expand...
Click to collapse
Try this guide - it is tried and tested. http://forum.xda-developers.com/showthread.php?t=1075278
Cheers!
Now its working but it shows FAIL
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> PK
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you make sure you are in Download mode, and the drivers were installed correctly? Also, did you make sure you added the kernel file in the correct section? (without ticking any unnecessary things)
Yes.
Now it wont switch on.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Did you tick the PIT box?
Edit - sorry, just reread, you haven't. I hope..
No i didn't. I restored the original firmware but it still wont turn on normally.
Did you have kies running in the background? Make sure you end all kies applications - end process
Nope had shut kies.
Could be a cable failure. Try a different USB cable.
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
xSirAKx said:
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
Click to expand...
Click to collapse
You can get a new USB cable for a couple of bucks. I've got like 6 due to all the devices I've had over the years, and 2 of them are bad. They don't last forever.
Managed to restore device using tutorial i found on google androidcute.*com/install-android-2-3-6-gingerbread-for-samsung-galaxy-s2.html
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
xSirAKx said:
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
Click to expand...
Click to collapse
ROM Manager is the devil. I don't think it plays well with CWM. How are you rooting? If you root using a CF-Root kernel, it will auto-install the CWM app, which I believe does everything ROM Manager does.
I used S2 Root, i uninstalled rom manager though.
xSirAKx said:
I used S2 Root, i uninstalled rom manager though.
Click to expand...
Click to collapse
Is it still rebooting?
Sent from my GT-I9100 using XDA App
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
xSirAKx said:
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
Click to expand...
Click to collapse
Last time I had this issue, it was some app I installed, but I couldn't figure out which one. I flashed back to stock and was more selective in which apps I chose to reinstall. I've also made sure that all the apps are on phone memory instead of SD card as there was some speculation flying around that this could also contribute to this issue. Haven't had a random reboot in months now.
Hey everyone, so I've been using a Cyanogenmod S2 for the past few months and everything was great.
Until recently it started to reboot by itself,
until one day when I woke up "Kernel panic upload mode" was on the screen.
I rebooted the phone,
and then was greeted with a black screen after the Samsung Galaxy S2 screen.
The buttons do light up, but nothing else could be done.
I entered download mode to flash a new firmware,
but then somehow it failed and then it says connect to computer to redownload firmware or something when I boot it on right now.
I can't get it to flash anything at all, whenever I use odin it gets stuck at setup connection,
I installed Kies but it doesn't recognize my phone as well, neither does my computer....
Need help. Desperately. :crying::crying::crying:
Can u enter cwm
Sent from my GT-I9100 using xda premium
stopro said:
Can u enter cwm
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No I can't..
Can only enter Download mode
Then you need to flash a stock rom with Odin. You don't really have any other option.
MistahBungle said:
Then you need to flash a stock rom with Odin. You don't really have any other option.
Click to expand...
Click to collapse
<OSM> T989UVMC6_T989TMB_T989UVMC6_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> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's the problem, I can't seem to get Odin to flash no matter what, I've already tried different versions of Odin,
but they always end up with either this (failure) or stuck at setup connection..
Any ideas, please?
There's been many threads re: this issue on here over the past week listing the troubleshooting steps to go thru when Odin won't work, search for those threads (Immortalneo has listed them, go through his posts as a shortcut).
Edit - Hang on a minute, what model number do you have; what's the sticker on the phone chassis under the battery say ?
MistahBungle said:
There's been many threads re: this issue on here over the past week listing the troubleshooting steps to go thru when Odin won't work, search for those threads (Immortalneo has listed them, go through his posts as a shortcut).
Edit - Hang on a minute, what model number do you have; what's the sticker on the phone chassis under the battery say ?
Click to expand...
Click to collapse
I'm using a GT-i19100
I'm going through immortalneo's posts but so far nothing's up..
Am currently following this guide but to no avail, (no .pit file in the compressed .rar file) http://forum.xda-developers.com/showthread.php?p=40154030&highlight=+pit#post40154030
Edit: I think it's a GT-i19100G because I vaguely remember such a thing on the startup screen...
If you've got an I9100, why are you trying to flash firmware for T-989 ?? I suggest you go back to Samfirmware & get an I9100 stock rom for starters.
Ignore that guide; your phone isn't bricked. However, it may well be if you try & flash a PIT file (Although, if you've somehow flashed firmware for a different model including PIT, you may need to at some point. Just not yet). OK. This is the first & last time I'm posting this stuff for the next month:-
Stuff to try when Odin doesn't work
-----------------------------------
*Must run Odin as administrator in Windoze.
*Ensure Kies & all it's processes aren't running in Windoze task manager. Kill them if they are (choose 'kill process tree').
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Check the rom/kernel you download for corruption. Programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all this fails, try a different PC. And if it won't work first time on another PC, go thru the above steps on that PC.
Hello everyone ..
It could solve the problem? I am in a very similar, and have helped me a lot, but none of the options so far have been effective. I'm starting to resign myself to use it as a paperweight, but still have not lost hope.:crying:
Geeenie said:
I'm using a GT-i19100
I'm going through immortalneo's posts but so far nothing's up..
Am currently following this guide but to no avail, (no .pit file in the compressed .rar file) http://forum.xda-developers.com/showthread.php?p=40154030&highlight=+pit#post40154030
Edit: I think it's a GT-i19100G because I vaguely remember such a thing on the startup screen...
Click to expand...
Click to collapse
Stop Now :0 ! You are trying to install a T-Mobile T989 firmware.It's a Galaxy s2 too,but from T-Mobile.It's not the same.Search on Sammobile for an I9100 firmware,preferable Android 4.0.3 or 4.0.4.Of course it gives an error,because it's not the right firmware.
Now this thread is just fun!
Sent from the little guy
I've been trying to convert the firmware on my M250S to I9100. I've followed the guide to the letter and all the drivers are installed as well as Kries. I also made sure Kries was inactive while Odin was up. This is how far I get before it fails.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If anyone has any ideas I would appreciate it. I've tried everything I can think of including using different firmwares, pits, as well as versions of Odin. That's as far as I get before it fails.
How are you trying to do it? As I recall (I don't have an M250 so didn't pay crazy attention) there's two ways to convert one to an i9100. One involves Odin failing intentionally. Although, the method involving a pit file doesn't intentionally fail. If you're flashing pits and they're failing that's definitely not good... Potential brick.
Search for a guide in the s2 general section, I read one a couple weeks back which members were using with success.
You can also click the link in my signature and follow the steps there. As you're not doing a 'regular' Odin flash bear in mind some things will be a little different.
Sent from a galaxy far, far away
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Edit: I tried another computer and it worked flawlessly. So now I'm running on i9100. Although I'm having a few issues. It doesn't show my battery charging when the usb is plugged in. Also when I shut down my phone it doesn't completely shut down. It goes to a screen with a green battery. This actually happened before but I thought perhaps changing firmware would fix it. Before this the device would come back on automatically when I tried to shut it down and I read it could be the usb port so I cleaned the usb port with alcohol.
Slywolf15 said:
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Click to expand...
Click to collapse
Ah so it may not be a case of what you're trying to do, it might be a case of how the flash is set up/what hardware (pc, cable etc) you're using. In that case, use the link in my signature to troubleshoot it. Perseverance is key. Also have a look here : http://forum.xda-developers.com/showthread.php?p=45131292
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
ZivC12 said:
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
Click to expand...
Click to collapse
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Slywolf15 said:
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Click to expand...
Click to collapse
it happened to me with bad uk unbranded rom, try to flash new rom, if you cant turn on the phone switch battery
Hi all,
A classmate of my son has a bricked GPS 4.2 (YP-GI1CW/XEN). Another classmate tried to root it. But it got wrong.
By reading and searching guides here, i have rooted some htc phones and succesfully tried several roms, so i offered to take a look.
I did not know this player before and i dont know what happened to it. The only think my son has heard is: someone rooted it, installed a rom, made it empty again, searched for the right software (rom), but could not find it.
When we got the phone it only showed the logo of galaxy S2. There is no sd-card inside.
I spend hours of reading, finding the download mode (3-button), odin, heimdall, kies etc.
Tried everything, but can't get it done
Could anyone please help me?
Download method works
The 3-button method works and gets the player in download mode.
Info on screen: (WITHOUT usb connection!)
Odin mode
Product name: YP-GI1
Custom binary download: yes (13 counts)
Current binary: custom
downloading....
do not turn off target!!
Click to expand...
Click to collapse
I tried and maybe did stupid things
I have tried heimdall and kies. Kies does not see the player. Heimdall does, but it did not work or i could not work with it.
Installed and uninstalled Heimdall following their textfile.
I unstalled Kies also. Cleaned up my computer. Updated java. Used ccleaner. etc. Removed unused devices, with 'device remover'
Once or twice i clicked the "re-partition" in odin. With or without PIT-file. Now I read, that this could brick your phone. :silly:
I tried all tabs, now i know i should only use the PDA-tab.
I might have done more stupid things.
I found "one-click" in http://forum.xda-developers.com/showthread.php?t=1153310
It took me a while before seeing that not all things where good for this player type. When rooting htc, a wrong rom won't brick your phone, so i did not take it too seriously.
I tried 1 or 2 roms, before seeing that they where for other player versions.
I tried the GalaxyPlayer-Bootloader.zip from http://forum.xda-developers.com/showthread.php?t=1386669
Now i see it is specially for player 5.0.
Here i also used the partition file.
At last i did:
Installed samsung usb drivers again: "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe"
From: http://forum.xda-developers.com/showthread.php?t=961956
When connecting the player to the computer (while already in download mode), windows start 'downloading' the samsung drivers again...
Dont know why and if this can be a problem.
Tried ADB in command, but 'adb devices' does not give a list, but odin seems to work at first.
Odin (3 v3.07) recognizes it and says:
<ID:0/010> Added!!
and: "0:[com100]"
Now in Odin I first uncheck ALL checks like: repartition, auto reboot and refresh time and the others.
I did try the "NAND ERASE" option. Erasing looks to hang, but at last Odin comes back and gives a fail on flashing.
Between every odin try, I remove the battery, unconnect usb and restart the download mode, then connect again, then start Odin again.
Now I tried 3 roms/kernels:
- CWMStockGI1 kernel.tar (http://forum.xda-developers.com/showthread.php?t=2198444)
- yp-gi1cw.factoryfs.rooted.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
- yp-gi1cw.kernel.stock.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
Odin responds when flashing:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> normalboot.img
<ID:0/010> NAND Write Start!!
Click to expand...
Click to collapse
Then nothing.....
On unconnecting:
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
I am out of options
Please help. :crying:
Stop before you actually brick it!!!
STOP EVERYTHING RIGHT NOW!!! First thing's first, this is a samsung device and not a HTC device. You screw up flashing this with the wrong device rom and you are screwed. right now, you are lucky in that the state of the device is currently in the state of what is called a softbrick or download only. you need to get stock files for this exact device, preferably able to be used with odin. then after that you can focus on rooting the device. honestly, dont touch the device right now, post a fourm under q and a asking for who has stock recovery files for a 4.2 international version, (i am guessing that you have the international version due to what your location is set as.) once you get those, then flash them with odin. then once it is working again, you can use this exploit to root it.
http://forum.xda-developers.com/showthread.php?t=1312859&highlight=rooting
good luck.
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
joly said:
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
Click to expand...
Click to collapse
in terms of the recovery images, your going to need to ask someone with a 4.2 to get them off of theirs and send them to you. odin and hemidall are avaiable in the galaxy player all in one forum at the top of the development page.
interms of the wrong image hard bricking a device, it is possable with samsung devices (i've done it once before and have learned to be carefull). Most samsung galaxy player roms not only contain the rom, but also a kernel. if a kernel that was not made for your device is flashed on to it. it might as well be a hard brick because with out a jtag box, you will never get it working again.
I hope you are able to obtain the files and i wish you the best of luck.