My Samsung Galaxy Player 5.0 YP-G70 was working perfectly up until a couple of weeks ago. I had connected it to the PC to download a couple of pics and when I went back in to disconnect and turn it on it was essentially dead. I have tried charging for 24 hours+ with no results except the player back gets warm. There is no vibration, no battery charge icon, nothing to indicate it has power. After looking at the error I get when I connect it to the PC and researching what I found, it appears that it's stuck in S5PC110 development mode. I have read and reread the info elsewhere on this site about UnBrickableMod/UnBrickableResurrector Revision 37, but didn't know if it would work for the YP-G70 especially since it refers to taking out the battery and putting back in which isn't an easy process with the player as opposed to a phone.
http://forum.xda-developers.com/showthread.php?t=1841250 option 25
I also read this link about what looks like a different option (http://www.androidauthority.com/unbrick-samsung-galaxy-player-5-48449/) but in the directions it tells you to turn the player off -- I can't even turn it on to turn it off.
Does anyone have any direction as to what I can do to fix my player?
karnor said:
My Samsung Galaxy Player 5.0 YP-G70 was working perfectly up until a couple of weeks ago. I had connected it to the PC to download a couple of pics and when I went back in to disconnect and turn it on it was essentially dead. I have tried charging for 24 hours+ with no results except the player back gets warm. There is no vibration, no battery charge icon, nothing to indicate it has power. After looking at the error I get when I connect it to the PC and researching what I found, it appears that it's stuck in S5PC110 development mode. I have read and reread the info elsewhere on this site about UnBrickableMod/UnBrickableResurrector Revision 37, but didn't know if it would work for the YP-G70 especially since it refers to taking out the battery and putting back in which isn't an easy process with the player as opposed to a phone.
http://forum.xda-developers.com/showthread.php?t=1841250 option 25
I also read this link about what looks like a different option (http://www.androidauthority.com/unbrick-samsung-galaxy-player-5-48449/) but in the directions it tells you to turn the player off -- I can't even turn it on to turn it off.
Does anyone have any direction as to what I can do to fix my player?
Click to expand...
Click to collapse
UnbrickableResurrector should work see here: http://forum.xda-developers.com/showthread.php?t=1386669
thanks so much
Meticulus said:
UnbrickableResurrector should work see here: http://forum.xda-developers.com/showthread.php?t=1386669
Click to expand...
Click to collapse
Thanks so much for the info specific to player. I already had ubuntu downloaded but was hesitant to go any further since the instructions were for phones. I'll update here when I get a chance to try it out.l
stuck
I set up VM Workstation 10, installed Ubuntu 12.04, Java, went through the steps in the link above several times with differing results. The furthest I have gotten is to having the device recognized in Odin, but getting a "fail" message. I tried posting to the link with the unBrick instructions, but I cannot since I'm a jr member. Any help would be appreciated.
karnor said:
I set up VM Workstation 10, installed Ubuntu 12.04, Java, went through the steps in the link above several times with differing results. The furthest I have gotten is to having the device recognized in Odin, but getting a "fail" message. I tried posting to the link with the unBrick instructions, but I cannot since I'm a jr member. Any help would be appreciated.
Click to expand...
Click to collapse
It's hard to say without more detailed information but the generally, once you get it into Download mode you flash the "bootloaders" in the thread and that should get you to download mode every time. Once there you can flash a "FULL" factory ROM and that should get you back up and running... The "FULL" ROM will flash normal bootloaders so that it boots normally.
If your having trouble with that then... need more details :good:
What's happening is...
Most often what's happening is the Win7 machine gives an error when SGP 5 is connected (SEC S5PC110 - can't find drivers). It *is* recognized by Linux running on VM Workstation.
Although it sometimes hangs up at "Please wait -- uploading", a few times I have been able to get UnBrickable Resurrector Rev. 40 to complete the process as indicated by the screen shot in Adam Outler's step-by-step process. When I disconnect from Linux on the VM to connect to Win7, most times I get an error message. On the rare occasion (twice) when the Win7 machine has actually recognized it and loaded Samsung drivers, and Odin finally shows the COM port, I get a red "Fail" message in Odin when I click on Start. If I unplug and replug the SGP, it goes back to the unknown device/SEC S5PC110 message on Win7.
I'm still trying to get it back to where the Win7 machine recognizes the device as Samsung so Odin will recognize it.
Update
By selecting Galaxy S in resurrector instead of Galaxy Player, the device icon changes to Samsung USB device in Linux and remains that way when I switch the device to Win7 and open in Odin. Otherwise, even though it shows it's in download mode in resurrector, the device icon in Linux shows S5PC110 and when I switch it to Windows, it gives USB errors.
The times it's recognized when opening Odin, get a message that the repartitioning failed.
Related
Hello community,
I have been trying for 8 hours (5 last night and three so far today) to get this to work but have failed utterly each and every time. I own the Samsung Galaxy Tab 10.1 (the Verizon 4G LTE model), and I'd like to revert back to the stock Honeycomb 3.1 that came with my tablet when I first purchased it from my local Verizon Wireless store.
I've followed this guide as closely as my understanding of it allowed me to (http://forum.xda-developers.com/showthread.php?t=1171089), and I also followed the video linked to in that topic (http://www.youtube.com/watch?v=krQDP7xYlWg) but I was not able to get Odin to work properly. After trying this on three different computers, I was able to get the third computer to recognize my tablet plugged in via USB and the yellow "COM4" box appeared in Odin, but when I clicked "Start" in Odin, it went all the way up to "Setup Connection" and then sat there for at least 10 minutes, showing no signs of a connection having been established. I've installed the Samsung USB drivers from both the topic linked to previously and from the video linked to previously (uninstalling one before trying to install the other, of course), and my tablet is recognized by the computer, yet Odin still stalls at "Setup Connection". I have not been able to push past this first step to rooting my device in order to revert back to stock Honeycomb 3.1, and this is very frustrating. I did have Download Mode open and the terminal that appeared on my tablet did say "Connected to USB, click [Start] in Odin" (or something to that effect). For what it's worth, all three computers I've tried this on were running Windows 7 64-bit (Ultimate and Professional editions).
Please, if anyone could help me, I'd greatly appreciate it. Also, once this is all sorted out, I am not exactly sure how to proceed after getting Odin to push past "Setup Connection". I don't even know if I'm following the correct path to reverting my device back to stock Honeycomb 3.1... as I mentioned before, I am a complete and utter Android noob (just got this tablet for Christmas) and I need all of the assistance that I can receive.
Thanks again, community. Hopefully we can get this sorted out and I can get back to using my tablet soon.
Excellent news: I was able to accomplish my goal without any problems using this concise, yet effective, tutorial: http://forum.xda-developers.com/showthread.php?t=1342995
I successfully reverted my Samsung Galaxy Tab 10.1 (SCH-I905, Verizon 4G LTE model) back to stock Honeycomb 3.1, removing the TouchWiz UX update completely. It's as though I've just picked it up out of the box for the first time, and I am thrilled.
I realized that Windows 7 was creating some issues that was leading Odin to stall at "Setup Connection", so I tried it again in the Windows XP Mode VM on my machine and, after a couple of hours of tinkering and reinstalling Kies, it finally worked. Thanks to XDA for such great tutorials and developers! Hopefully this topic will help others in my shoes in the future.
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
Hi everyone, i hope to find a solution writing there, since i'm kinda desperate about my situation.
So, i got this telephone, a s2 I9100g, but only the day after i noticed the browser was in chinese. Looked up a bit better inside and i found it is a chinese version of the telephone (original one, but made for chinese market).
So i tryed to pull in an original rom, but it failed; i found a guide to how to fix this problem, and become able to flash the italian rom on it.
Basically, i followed this guide http://forum.xda-developers.com/showthread.php?t=1702479%22 I did all the steps using the CHN version of the bootloader and.. i know, i was so stupid there, but since it got stuck at NAND writing (i did not see the progress bar after 15 minutes), i simply unplugged the cable.
Well, after that the phone didn't enter reset/download mode, but it started showing the yellow phone---!---pc screen, with wrote above "software update fail", and something else in chinese.
There is what i tryed to do:
-Flash another rom (tryed 2) with different versions of odin, 1.3,1.6 and 3.07.
odin does recognize the telephone with the drivers installed, but if i start it, it gets stuck at setup connecting phase and failing after. Same with all versions.
-use OneClickUnbrick, i tryed to start it normally and from CMD.
with the drivers which odin and windows use to recognize the telephone (last ones available on samsung website), it says "usb drivers are not properly installed attempting to install drivers". So, it starts Zadig. I follow the steps there, and the installation completes succesfully. But at this point, when i plug in the telephone windows recognizes it but fails installing the device with drivers, and odin doesn't recognize it at all, while oneclick keeps showing the "usb drivers are not properly installed" window, time after time even if i keep reinstalling with success the drivers using Zadig.
-delete everything and install Kies.
none of the programs above does see the telephone now, neither windows.
Tryed to follow the steps i did before after having it installed, nothing changed.
Every of this tryes, i did the following "changes":
-removing and inserting the battery
-changing usb port
-changing cable
-changing computer
-trying to enter reset/download mode by holding vol up/down+mid button+power
Would be enough to make odin go over the setup connecting phase, or kies to recognize it, or OneClick to stop showing the window about drivers.
I read that seems i'm in a hard brick case, but since the phone is seen by odin and windows and the battery does recharge, i got still a bit of hope.
Thanks
Click the link in my signature, there's more troubleshooting steps to try. You've done a few but not all of them.
I would usually say that pulling out the cable leaves you with no hope, but you seem to have gotten a little lucky. Don't hold your breath though.
Sent from a galaxy far, far away
Hopper8 said:
Click the link in my signature, there's more troubleshooting steps to try. You've done a few but not all of them.
I would usually say that pulling out the cable leaves you with no hope, but you seem to have gotten a little lucky. Don't hold your breath though.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Tryed all the steps.
Nothing changed.
You can either keep trying or take to a service centre & pay to have it fixed *shrugs*
I'm Fairly New To The Android Concept, And I See Its A Little Bit More To Trying To Jailbreak It Vs. The iPhone, I'm Getting Stuck Using The Casual "NoYouVerizon" Concept Of The "One-Click" Method, But As Going On, I Don't Understand The Log's, I've Tried Searching For It Constantly, And I've Been At This For A Week Straight Now, I Need STEP by STEP Instructions On What To Do, Because I'm Reading Alot Of Different Things, And It's Not Really Helping Me At All, I Have A Verizon Samsung Galaxy Note 2, With Version 4.1.2 On It, and I Have *Correct Me If I'm Wrong* VRAMC3? If Thats The Right Thing. Please Somebody Help Me. Send Me A Message For My Contact Information. I Wanna Get This Done Pleasee!!!
theres the step by step guide
http://forum.xda-developers.com/showthread.php?t=2024207
One click root not working XDA. Someone needs to go back in and put the fix in for ERROR: No partition with identifier "60" exists in the specified PIT
Ive tried everything so far, even uninstalling the phone driver driver to allow samsung driver to reinstall, even manually installed the dev driver. I even tried to use odin3 to install via xda instructions. Odin can detect device if I just plug the phone in but if I put the phone in down load mode and connect, nothing. I checked device mgr and it shows the device in usb connections. WTF, XDA is verizon winning??????
Update:
Well I did discover after all this that I am rooted but I think that s all. When I plugged my phone into the computer Casuals usb showed in the Device Mgr screen instead of Samsung. To confirm I downloaded root checker from the play store and I am rooted via super user. Theres an issue though with putting the phone in download mode and odin detecting.
Update 2
Well it finally just worked and I was able to get odin to detect the phone while in download mode. I am now on root66 !! Help for others: Be persistent, I think it took time for my pc to accept and activate the changes IE: the casual driver replacing the samsung. It literally just happened after about 5 or 6 failed attempts of running the one click root. And it happened after a couple of samsung driver deletions. When the phone was plugged in, I went to device manager on the pc , usb devices and deleted the samsung drivers. I wound up doing this about 3 times. I restarted my computer after this to. Then I plugged the phone in again and there was casual usb controller appearing in device manager, replacing samsung. That was when I discovered I was rooted even though I had gotten the error message that started this post. Later, I went ahead and was able to install root66 by following the xda directions. wow......it was an all day affair but hopefully this will take some of the grey area out for others with this problem.
Thank you XDA for working to [email protected]^! this phone that verizon and google so graciously shoved up our #$% with a warm smile. The wi fi button for the notification bar is not available, I believe this is due to verizon when they put their stink on the phone. I would like to get that back if possible. Also the google search popping up when you plug the headset jack in is still there, but you can go into settings/task mgr/ all aps and scroll down to google search and disable it. The annoying pop up voice search hasnt showed up since I did this.
I am literally having the worst time. I have to go to work in 30 minutes and my phone is now broken. All I wanted to do was update it so I found a rom for my Infuse but now that I installed it, my phone seems to be broken.
Now I am trying to get it back to its normal state, but the only way to do that is put it in download mode(which works fine) and plug it into Odin. But Odin will not detect it no matter what I do. I have tried everything and I am literally pulling out my hair because this is frustrating me so much.
I hear my pc detecting it. I download drivers. I tried installing drivers through kies, but it just sits at 0%. Then I downloaded the galaxy s drivers, which does nothing when I click the setup file(or at least I can't tell that it is doing something), and then I tried finding the download specifically for my device on the samsung website, but when I run that setup file it says Samsung Android USB Modem Software not installed succesfully (9).
I just want to fix my damn phone and this software will not detect it for the life of me.