Step 1. Player in Download mode
Step 2. Search for device on Heimdall
Step 3. Name file to save too
Step 4. Start Download
Step 5.. Fail
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
I have tried everything!
I am trying to backup my PIT from my EURO Galaxy Player 4.0 YP-G1CW/XEZ
I damaged another one..
I am trying to fix the Digitizer that touch sensor is flipped.. Digitizer is operating in reverse..
Absolutely no one has done or shown proof to fix this problem..
I don't need ideas or theories.. please
If you can, please show me how to repair this problem..
thank you..
have you tired using Odin instead, or uninstalling all 4.0 drivers, and just installing heimdalls? Or maybe just remove all drivers, let the kids drivers install fully, then run zagig.exe a few times. The entire theory behind xda support is getting helpful theories/ideas from members that have experienced similar issues. Your issue seems to be isolated, so not many people will have step-by-step solutions for you.
Also, thus *does* belong in general, not development. I want to help you, but can you please post this kind if thing in general in the future?
Yes wrong section!
but quick answer:
Pit is the same for every 4.0 int'l sized version.
All the pits and everythings are available here
http://forum.xda-developers.com/showthread.php?t=1720457
Thanks Zaclimon
Forget using Heimdall if you are not Heimdall expert like me (kidding), come back to odin, like me .
Rgds
lolo9393 said:
Yes wrong section!
but quick answer:
Pit is the same for every 4.0 int'l sized version.
All the pits and everythings are available here
http://forum.xda-developers.com/showthread.php?t=1720457
Thanks Zaclimon
Forget using Heimdall if you are not Heimdall expert like me (kidding), come back to odin, like me .
Rgds
Click to expand...
Click to collapse
Heimdall isn't that necessary for intl devices.
To use heimdall on a windows PC, you need to install Zadig's libusb drivers. I've posted a step-by-step walkthrough over in the Q&A section. It covers the entire process of flashing a new rom on a USA device, but the section on heimdall and libusb drivers should work for any device.
Related
I'm a mac user, and Kies is still in beta and can't perform updates, (its a pos anyways and I wanna refrain from using it either way).
So the only other alternative for Kies is Heimdall which is similar to Odin, but doesn't have much documentation for the newer version 1.3 other than the readme file that came with it that I have read but still am not confident enough to flash anything.
So can someone please write up a tutorial on how to use it or link me to one. I mainly only want to update my firmware keeping it stock and possibly root with CF-Root while I'm at it, if CF-Root is gonna even work with heimdall.
Thanks in advance.
This should cover it
Woaw. Thank you very much buddy ^_^
Not to hijack the OP's thread, but I have another and related question regarding Heimdall for mac:
When unraring archives either from Intratech or Samfirmware, all the extracted files are of the type .bin and/or .img. I really can't figure out how to get the proper .rfs files that should be used for flashing. Anyone able to show me in the right direction for the answer? I've searched up and down both on the forum and on Google
As of the time being I have a Bootcamp partition only for the sake of using Odin, and I would really like to have those 20GB's back as it should be unnecessary to use Odin in Windows when Heimdall looks like a great tool for the mac (when the proper files are used )
Hrti said:
Not to hijack the OP's thread, but I have another and related question regarding Heimdall for mac:
When unraring archives either from Intratech or Samfirmware, all the extracted files are of the type .bin and/or .img. I really can't figure out how to get the proper .rfs files that should be used for flashing. Anyone able to show me in the right direction for the answer? I've searched up and down both on the forum and on Google
As of the time being I have a Bootcamp partition only for the sake of using Odin, and I would really like to have those 20GB's back as it should be unnecessary to use Odin in Windows when Heimdall looks like a great tool for the mac (when the proper files are used )
Click to expand...
Click to collapse
Heimdall should flash the .bin's or .img's, Heimdall should flash just about anything.
I dont have an OSX machine and havent had time to build a virtualbox img so i cant test
I tried to follow your instructions @veyka but heimdall won't work
When I try to get heimdall to detect my phone it just says "FRONTEND ERROR: Heimdall crashed!"
I tried uninstalling/reinstalling heimdall, still didn't work, then uninstalled Kies cuz it might be interfering but it still doesn't work!
Man I really want this to work....
hank00k said:
I tried to follow your instructions @veyka but heimdall won't work
When I try to get heimdall to detect my phone it just says "FRONTEND ERROR: Heimdall crashed!"
I tried uninstalling/reinstalling heimdall, still didn't work, then uninstalled Kies cuz it might be interfering but it still doesn't work!
Man I really want this to work....
Click to expand...
Click to collapse
Just.. weird...
I do wish I could be more help, but I have no OSX machine to test it on.
Are you on 10.5? As another thread says that it wont run on it, but just crashes, but an upgrade to 10.6 made it work.
Yeh.. Im recommending upgrading your OS to fix a flashing issue, go me.
veyka said:
Just.. weird...
I do wish I could be more help, but I have no OSX machine to test it on.
Are you on 10.5? As another thread says that it wont run on it, but just crashes, but an upgrade to 10.6 made it work.
Yeh.. Im recommending upgrading your OS to fix a flashing issue, go me.
Click to expand...
Click to collapse
I'm on 10.7
I think its not compatible with 10.7 cuz some other apps had to be updated to work properly, including stupid Kies... So I guess downgrading is the solution lmao or waiting for it to be updated
And you've been plenty help by linking me to your other post, now at least I know that it should work...
hank00k said:
I'm on 10.7
I think its not compatible with 10.7 cuz some other apps had to be updated to work properly, including stupid Kies... So I guess downgrading is the solution lmao or waiting for it to be updated
And you've been plenty help by linking me to your other post, now at least I know that it should work...
Click to expand...
Click to collapse
Well, Im not sure, no one in that thread got it to work in the end, but I know people on linux who have flashed with it, and I have on windows so it should work!
Odin might be a iffy PoS but its a iffy PoS that works most of the time.
I've got Ubuntu Linux on an old ibm laptop, so I'll give it a try later.
And I only dream of using Odin but I don't have Windows unfortunately...
Hey guys I was hoping you could help me out.. So last night I tried to flash Steve's kernel for the US version and I followed all the directions correctly. I put my samsung in download mode made sure re partition was unchecked etc. Is there a certain version of Odin I should have used? Well anyways it bricked up my samsung now all that shows up is a connect to computer image with a !. Any help would be greatly appreciated.
Try flashing again - you're in "forced download mode" which is what happens when a flash goes wrong.
If it fails agian, try the version of Odin from AdamOutler's resurrection thread - you don't need the full resurrector (you only need it if the screen doesn't even turn on), but you def. need to try flashing again in Odin.
Entropy512 said:
Try flashing again - you're in "forced download mode" which is what happens when a flash goes wrong.
If it fails agian, try the version of Odin from AdamOutler's resurrection thread - you don't need the full resurrector (you only need it if the screen doesn't even turn on), but you def. need to try flashing again in Odin.
Click to expand...
Click to collapse
I think it may be a driver issue. It's likely the Samsung driver on the computer I used was/is corrupted. Now I just have to find another computer. Do you know how I would go about fixing the driver properly on that computer? I tried uninstalling both the Samsung driver and Kies from remove programs but this morning when I went to install the driver package(found in XDA) it said it was already installed. I'm thinking maybe I need to uninstall something in device manager?
EDIT: could you possibly link me to that thread? I can't seem to find it.(Adam's res. thread)
http://droidangel.blogspot.com/2011/07/one-click-unbrick-tool-for-samsung.html
It works. I personally use the heimdall command line interface to do this, but this method will work for you.
apapousek said:
(link that im not allowed to repost)
It works. I personally use the heimdall command line interface to do this, but this method will work for you.
Click to expand...
Click to collapse
Is there a possible method that doesn't require administrative privileges? I'm on a public computer and admin access is prohibited.
UPDAAAAAAAAATE!
It was a driver issue. THANKS for the help guys!!
Semi-bricked: PIT upload failed in Heimdall/Odin, cannot flash anything; cannot mount/wipe cache in CWM...any ideas, how do I check whether the eMMC chip is fried or not? Thanks.
You probably have done all this a thousand times but I would redownload your files again and follow droudstyles guide to the t and see if you catch a mistake or something. These are pretty hard to brick.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
You probably have done all this a thousand times but I would redownload your files again and follow droudstyles guide to the t and see if you catch a mistake or something. These are pretty hard to brick.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, it's still alive, I can get into CWM and download mode. The experts out there...please?
Based on trying to help in your previous thread I know I can't do much more to help you get your device working again. All I can do at this point is point you in the direction of Gizmodroid who was a pretty regular and reliable guy around here for awhile before his screen shattered. I have no idea if he is still looking for a replacement, but you might want to reach out to him if you decide to sell it for parts.
Since everything else has failed, Unbrickable Mod may be your only option. But it is not for the feint of heart and won't help you if the flash memory is truly corrupted.
The weirdest thing. I tried to flash the ED05 Heimdall package AGAIN today, and IT WORKED (repartition unchecked). But, then I tried flashing CWM with Heimdall and it failed. I had to reboot the device and of course it's semi-bricked again (now it's back to stock recovery) and I get this error when I try to re-flash ED05 (or anything):
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor
What is going on??
anybody knows of this error message (Failed to retrieve config descriptor) in Heimdall, please?
Let me just start out by saying that I am a noob at this stuff, and that I don't have much experience, hence why I am here, cause i screwed up.
Basically, I have a player 4.0 that i am trying to get the stock ROM reinstalled on that is not being "cooperative". I have followed many different XDA forum guides, downloaded about a dozen different files, and nothing is working. Here is what works/doesnt work:
- I can access the Download function (hold down volume and plug into computer)
- I have a windows 7 computer
- I downloaded and tried three different versions of Odin, all with no success.
- Downloaded about 6 different files of the stock rom, each in a .tar or other compressed (i think) file type (even tried Icy Fusion, no luck).
- Downloaded heimdall and tried to make the partitions myself, no success.
I am hoping someone on this forum can please help me through the process of restoring my droid back to either the stock ROM or some other ROM, I just want my droid working again.
Also, I have read a multitude of similar XDA forums on this issue (yes I saw the "your a noob XDA" video and i am only making a thread because im desperate) and have had no luck.
Thanks in Advance,
TechnoD11
TechnoD11 said:
Let me just start out by saying that I am a noob at this stuff, and that I don't have much experience, hence why I am here, cause i screwed up.
Basically, I have a player 4.0 that i am trying to get the stock ROM reinstalled on that is not being "cooperative". I have followed many different XDA forum guides, downloaded about a dozen different files, and nothing is working. Here is what works/doesnt work:
- I can access the Download function (hold down volume and plug into computer)
- I have a windows 7 computer
- I downloaded and tried three different versions of Odin, all with no success.
- Downloaded about 6 different files of the stock rom, each in a .tar or other compressed (i think) file type (even tried Icy Fusion, no luck).
- Downloaded heimdall and tried to make the partitions myself, no success.
I am hoping someone on this forum can please help me through the process of restoring my droid back to either the stock ROM or some other ROM, I just want my droid working again.
Also, I have read a multitude of similar XDA forums on this issue (yes I saw the "your a noob XDA" video and i am only making a thread because im desperate) and have had no luck.
Thanks in Advance,
TechnoD11
Click to expand...
Click to collapse
Well first of all, welcome to XDA. Hmm, it's better that you use the heimdall method of reflashing to stock ROM.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Well first of all, welcome to XDA. Hmm, it's better that you use the heimdall method of reflashing to stock ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the welcome! I would like my droid working ASAP, so where do i start? remember, i can access the download function. i have the samsung usb drivers installed. If someone could post some detailed, step-by-step instructions, that would be great!
TechnoD11
TechnoD11 said:
Thanks for the welcome! I would like my droid working ASAP, so where do i start? remember, i can access the download function. i have the samsung usb drivers installed. If someone could post some detailed, step-by-step instructions, that would be great!
TechnoD11
Click to expand...
Click to collapse
Check on the reference(all-in-one) thread in the development section. In the recovery section, click the first link. I can't post the link because I'm on my tablet.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Check on the reference(all-in-one) thread in the development section. In the recovery section, click the first link. I can't post the link because I'm on my tablet.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
This link (from the recovery section) brings me to a guide i already tried that did not work for me. when i perform those instructions, my droid boots into "android system recovery <3e>". from there, i reboot, or try to wipe the cache, or data (factory reset), or both. after reboot, just goes back into recovery. There is an option for applying update from SD card. is it possible i can load the rom on my SD card and flash it through there?
TechnoD11
Don't call an android device a droid unless you actually own a droid device (Motorola Droid Razr, Droid X, etc.) It drives people like me bonkers
Anyways, the best way to handle this is to solely use Heimdall. This thread should take you through the steps quite nicely, thanks to zaclimon. However, you have to read everything carefully, as you don't want to flash the wrong files within heimdall. If you own an International device (the one with the physical home button), follow the INTL walkthrough. If not, use the US one.
All you will need is the PIT file and the full recovery package, never the Odin. I recommend you try it again if you already have, as you may have done something wrong. If the problem still prevails, I will give you step by step instructions, if not done so already.
LuthicaBlue said:
Don't call an android device a droid unless you actually own a droid device (Motorola Droid Razr, Droid X, etc.) It drives people like me bonkers
Anyways, the best way to handle this is to solely use Heimdall. This thread should take you through the steps quite nicely, thanks to zaclimon. However, you have to read everything carefully, as you don't want to flash the wrong files within heimdall. If you own an International device (the one with the physical home button), follow the INTL walkthrough. If not, use the US one.
All you will need is the PIT file and the full recovery package, never the Odin. I recommend you try it again if you already have, as you may have done something wrong. If the problem still prevails, I will give you step by step instructions, if not done so already.
Click to expand...
Click to collapse
First try: Heimdall Crashed
Second try: heimdall crashed again
I have included the Status log for viewing:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
(removed link cause im a noob)
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
(removed link cause im a noob) lol
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
here is the list of files i am using (that I downloaded from a different post):
PIT: ypgi1cb.pit
CACHE: cache.rfs
PARAM: param.lfs
DBDATA: dbdata.rfs
FACTORYFS: factoryfs.rfs
KERNEL: zImage (listed in windows as just a 'file')
following the heimdall crash, my SAMSUNG GALAXY PLAYER (cough cough droid cough) reboots and enters...drumroll.... recovery mode!
If someone could explain to me what i might have done wrong, or if there is something else i should try, let me know
thanks for the help,
TechnoD11
THANK YOU COMMUNITY!!!
well, i decided to try it for a third time, and third time is the charm!. It, for some unknown reason, decided to work, and the stock ROM is now back on my droid!
Again, thanks all for your help.
Lesson learned: don't download stuff for the Galaxy player 5.0 thinking it will work on yours (4.0).
TechnoD11
Oh, and administrators, you can delete this thread.
To start, I am a newb and my sincerely apologizes for my ignorance.
I bricked my YP-G1 player trying to flash a kit kat rom on it.
At this point I bought a jig and restored it with odin.
The current problem -
No touch functions work. All the hard buttons work fine but the touch screen does nothing along with the back and home button, etc.
At one point I had it working with the touch screen almost as if it was inverted in regard to accepting the input.
Did I do something that fried the hardware or is this a software issue. I greatly appreciate your guys help.
The last things I did to get it working:
I used a jig to get to download mode then Odin to flash one of the many roms available (including stock)
I tried custom kernels like steve's and also no luck
Please help
Have you tried reflashing the stock ROM with heimdall?
Sent from my YP-G1 using XDA Free mobile app
Thank you for reply. I tired using heimdall however I kept getting libusb -12 error. I tried getting the drivers etc and gave up on heimdall in windows. At this point I am just looking for a stock tar file to use odin. Do you have one by chance?
obscuresword said:
Have you tried reflashing the stock ROM with heimdall?
Sent from my YP-G1 using XDA Free mobile app
Click to expand...
Click to collapse
nirmalbk said:
Thank you for reply. I tired using heimdall however I kept getting libusb -12 error. I tried getting the drivers etc and gave up on heimdall in windows. At this point I am just looking for a stock tar file to use odin. Do you have one by chance?
Click to expand...
Click to collapse
Yes I do have the stock tar file for Odin, but you can also find it in this thread here http://forum.xda-developers.com/showthread.php?t=1531850. The link to the Galaxy Player 4.0 (US) is this one http://d-h.st/oH3 (so please thank Zaclimon).
Sent from my YP-G1 using XDA Free mobile app
Hi there,
I used Heimdall 1.4.0 on windows 7. I tried all the attempts with heimdall to get the drivers with zadig.exe, etc. I was was able to detect the device but get this:
Heimdall v1.4.0
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
The furthest I get anywhere is doing the following:
Using Odin3 v1.85
I check Re-partiation, autoreboot, and f. reset time. Then I use the Samsung Galaxy Player 4.0 U.S. 8gb.pit pit file found on forum. I flash the YPG1USRestoreOdin.tar.md5 by clicking under the PDA section.
This gets me to boot with the samsung logo and little chime. Then I go all the way through and boot to the OS. At that point no touch functions work at all, including the menu button, home screen or back button.
So i was thinking, is it a kernel issue? Does the kernel tell the touch screen to work?
So then I go back to download mode by taking out battery and placing it back in with a jig
Now i flash steve's kernal (STevEs-3.0-USA.tar) successfully and still no touch functions
SO THEN:
Instead I try STeVEs-3.0-EU.tar kernel and I get touch functions that are not mapped correctly.
That is the best that I have been able to get it to function.
Please help
obscuresword said:
Yes I do have the stock tar file for both Odin and heindall. What OS did you use with heimdall and what heimdall version did you use?
Sent from my YP-G1 using XDA Free mobile app
Click to expand...
Click to collapse
nirmalbk said:
Hi there,
I used Heimdall 1.4.0 on windows 7. I tried all the attempts with heimdall to get the drivers with zadig.exe, etc. I was was able to detect the device but get this:
Heimdall v1.4.0
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
The furthest I get anywhere is doing the following:
Using Odin3 v1.85
I check Re-partiation, autoreboot, and f. reset time. Then I use the Samsung Galaxy Player 4.0 U.S. 8gb.pit pit file found on forum. I flash the YPG1USRestoreOdin.tar.md5 by clicking under the PDA section.
This gets me to boot with the samsung logo and little chime. Then I go all the way through and boot to the OS. At that point no touch functions work at all, including the menu button, home screen or back button.
So i was thinking, is it a kernel issue? Does the kernel tell the touch screen to work?
So then I go back to download mode by taking out battery and placing it back in with a jig
Now i flash steve's kernal (STevEs-3.0-USA.tar) successfully and still no touch functions
SO THEN:
Instead I try STeVEs-3.0-EU.tar kernel and I get touch functions that are not mapped correctly.
That is the best that I have been able to get it to function.
Please help
Click to expand...
Click to collapse
I don't use heimdall 1.4.0 because I find it a bit too complicated. I guess you can try following my instructions found here http://forum.xda-developers.com/showthread.php?p=51762484, since you have a Galaxy Player 4.0 (YP-G1) and see if that lets you get the drivers installed correctly. I can't comment on if it controls touch screen controls, but why did you need to use a USB jig to go back to download mode?
Hi there,
I did exactly what you recommended. Successfully reinstalled OS however same issue, touch does nothing. I cant seem to boot into recovery so thats why have have been using the jig to go into download mode to reflash stuff. I just dont understand... when I used a different custom kernel I only had the ability to use the touch function in a weird way, it appeared as though it was inverted.... If you have any other thoughts please let me know. I thank you for your help already.
obscuresword said:
I don't use heimdall 1.4.0 because I find it a bit too complicated. I guess you can try following my instructions found here http://forum.xda-developers.com/showthread.php?p=51762484, since you have a Galaxy Player 4.0 (YP-G1) and see if that lets you get the drivers installed correctly. I can't comment on if it controls touch screen controls, but why did you need to use a USB jig to go back to download mode?
Click to expand...
Click to collapse
nirmalbk said:
Hi there,
I did exactly what you recommended. Successfully reinstalled OS however same issue, touch does nothing. I cant seem to boot into recovery so thats why have have been using the jig to go into download mode to reflash stuff. I just dont understand... when I used a different custom kernel I only had the ability to use the touch function in a weird way, it appeared as though it was inverted.... If you have any other thoughts please let me know. I thank you for your help already.
Click to expand...
Click to collapse
Wow that is weird. Have you tried using the other 2 kernels for our player, which are Klin's R3 and Terraailent? I find it odd that the EU kernel gave that back. Also it seems that your recovery is damage, even though that flash with heimdall should have fixed it. Try flashing one of the other kernels and then try flashing one of the latest kikkat builds.
@zaclimon have you seen anything like this?
Sent from my YP-G1 using XDA Free mobile app
obscuresword said:
Wow that is weird. Have you tried using the other 2 kernels for our player, which are Klin's R3 and Terraailent? I find it odd that the EU kernel gave that back. Also it seems that your recovery is damage, even though that flash with heimdall should have fixed it. Try flashing one of the other kernels and then try flashing one of the latest kikkat builds.
@zaclimon have you seen anything like this?
Sent from my YP-G1 using XDA Free mobile app
Click to expand...
Click to collapse
Well depends on the variant of his device. If it's the US version, then it could be possible that good digitizer might have been inverted. Though I don't recommend it, in last resort the intl bootloaders could be used to restore completely the device. In this case it is possible that he won't have access to the recovery by the three finger method anymore.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Thank you guys for your assistance. I am in the midst of a move to a new home which has been busy. I will give your guys recommendations a try asap and let you know what happens. Thanks again!
zaclimon said:
Well depends on the variant of his device. If it's the US version, then it could be possible that good digitizer might have been inverted. Though I don't recommend it, in last resort the intl bootloaders could be used to restore completely the device. In this case it is possible that he won't have access to the recovery by the three finger method anymore.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Click to expand...
Click to collapse