Obviously, I am very new to these forums. Just registered and all that jazz. I've been reading here trying to figure out how to root my Galaxy Player 4.2 (US version), but it is my first time trying to root a device. I've read up on the FAQs here, and have read through a lot of the posts here.
So, I started to follow the instructions within these two posts: here and here. I downloaded the files for the US version. Have Odin and Heimdall downloaded and ready to use. Also read through this post to make sure I knew what I was doing. Followed the instructions.
Only problem is, Odin or Heimdall can't seem to recognized that I've plugged in my player in download mode. Odin doesn't respond, Heimdall reports "Failed to access device. libusb error: -12", much like in this post. I made sure to uninstall Kies, have wiped the device drivers. Restarted the PC and device. Same thing keeps happening. Does anyone have any ideas or advice? I've tried looking around the forums, and there doesn't seem to be too much on the subject. That, and I could be a really bad researcher... but I've gotten tired to looking and reading and reading some more...so I'm posting this question. If I've neglected to provide some information, please let me know.
geexter said:
Obviously, I am very new to these forums. Just registered and all that jazz. I've been reading here trying to figure out how to root my Galaxy Player 4.2 (US version), but it is my first time trying to root a device. I've read up on the FAQs here, and have read through a lot of the posts here.
So, I started to follow the instructions within these two posts: here and here. I downloaded the files for the US version. Have Odin and Heimdall downloaded and ready to use. Also read through this post to make sure I knew what I was doing. Followed the instructions.
Only problem is, Odin or Heimdall can't seem to recognized that I've plugged in my player in download mode. Odin doesn't respond, Heimdall reports "Failed to access device. libusb error: -12", much like in this post. I made sure to uninstall Kies, have wiped the device drivers. Restarted the PC and device. Same thing keeps happening. Does anyone have any ideas or advice? I've tried looking around the forums, and there doesn't seem to be too much on the subject. That, and I could be a really bad researcher... but I've gotten tired to looking and reading and reading some more...so I'm posting this question. If I've neglected to provide some information, please let me know.
Click to expand...
Click to collapse
For heimdall, you need to install the drivers. Please see this thread for more info about this:
http://forum.xda-developers.com/showthread.php?t=1922461
Also you can flash CWM for the 4.2 to get root easier here:
http://forum.xda-developers.com/showthread.php?t=2198444
Hope it helps!!
zaclimon said:
For heimdall, you need to install the drivers. Please see this thread for more info about this:
http://forum.xda-developers.com/showthread.php?t=1922461
Click to expand...
Click to collapse
I'll have to make sure I did that. I know I uninstalled the drivers, but I could very well have not re-installed them.
zaclimon said:
Also you can flash CWM for the 4.2 to get root easier here:
http://forum.xda-developers.com/showthread.php?t=2198444
Hope it helps!!
Click to expand...
Click to collapse
I will also try this and report on how things went. Thanks!!
Alright, so a little update. I've been uninstalling the drivers with USBdeview, but when I use the samsung USB driver installer (from the thread you provided) it reports back the error: "windows could not load the installer for Modem. Contact your hardware vendor for assistance". Currently looking through the forums to find a solution, but that is where I am at right now.
Got it working
So, I figured out the issue. Bad usb ports. Switched computers, and it worked like a charm. Sometimes the simple things work.
Related
Hello everyone,
I wanted to take some time today to make a very clear and concise guide on how to complete the root process for the EVO3D. I understand that there is at least one other floating around at this point. If you don't have a firm grasp of how all of this works though, you may run into problems or have questions. I commissioned my guide to try and add clarity to the process and to also teach our communities newest members some of the ins and outs of modding our phones. The guide is far too large to post in a thread, therefore I've created a PDF of it and am offering it for download.
Feel free to mirror my guide and provide me with the link so that I can add it below.
Below is a Preface and Contents of the Guide. Feel free to ask questions or address any concerns you may have as I will be revising the guide.
The Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D
Authored by: sidepart of the
XDA-Developers Forum
Revision 1.1 - Published July 30, 2011
Preface
Prior to reading this document, please be aware that as a disclaimer, I am not responsible for anything that goes wrong in this guide. Some people will run into issues that others do not. This is especially true with the differing versions of the Android-SDK. Some advanced users are using an older version which uses different commands than are offered by the latest Android-SDK. I encourage you to ask questions and keep an open mind. Try to understand the commands that are given here, and how you might have to be flexible in changing them to work for your situation. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
What this Guide Assumes
I assume that you will be downloading the latest version of the Android SDK which at the time of this document’s creation is R12. I also assume that you are using Windows 7, but this translates very easily into Windows Vista or XP.
Disclaimer
I am not responsible for any problems or fatal errors that may or may not occur through the process of performing the instructions of this guide. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
Contents of this Guide
What is S-OFF, Recovery and Root?
It’s not Just “ROOT”. Getting Past Outdated Nomenclature.
When I Say, “Do this”, Perform the Following Steps
Going to HBOOT
Booting into Recovery
Enabling USB Debugging
Install the Android-SDK
Obtaining S-OFF Status
Obtaining “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Running “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Flashing a Recovery Program
Flashing the TeamWin Recovery Project Recovery Program
Flashing or Installing the Superuser Management Program (Root)
Conclusion
Acknowledgements
Click Here to Download
Changelog
Revision 1.1 - July 30, 2011
Fixed some glaring grammatical and spelling errors.
Added a Common Questions section under item 4b.
Added a common question to 4b,i. It instructs users on how to paste their Beta key-code into the Revolutionary EXE program.
Fixed some formatting.
Used your guide and had no problems thank you!
Have not used it yet but this is very helpful... will be rooting my wifes e3d tonight... wasn't going to do it off of the other thread... I had no idea what it was talking about. Thanks for taking the time to put this together
Sent from my SPH-D700 using XDA App
Kind of hilarious to see my access.log right now. Lots of people looking at the guide interspersed with a few people discovering my site's index.html.
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
So much info!!! love it.. nice
Sent from my PG86100 using www.psvitahacks.co app
bryangene said:
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
Click to expand...
Click to collapse
I think they may have updated since I first published. I might see if I can emphasize that you're supposed to use the downloaded filename in the command.
Excellent guide!
Sent from my PG86100 using XDA Premium App
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
zander145 said:
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
Click to expand...
Click to collapse
I actually tried to load the zip from http://goo-inside.me/superuser and it wouldn't work. Retried it quite a few times and got the same error. I found an unsigned version of it in clark44's guide and that one worked just fine. Not sure what the problem was, hence my recommendation to grab superuser from the market and follow it's instructions instead. Seems to be working out well.
I think I might add something about this to the guide if too many people are running into the problem.
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
SBERG117 said:
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
Click to expand...
Click to collapse
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Neogenx said:
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Click to expand...
Click to collapse
The only related issue that I've come across is the "Error 16" when provisioning the phone after s-off. As you found, this usually fixed with a call to Sprint. I'll never say, "never" though. Be aware that making modifications to the phone always carries with it an inherent risk, however small or unlikely. The risk of course is part of what makes it fun, but girlfriends (mine) seem to seldom understand this.
If the root method is ever released, there is potential for it to become more of a one-click procedure, but I don't think there's a guarantee of course.
Thanks for the guide!
I'm stuck though!
The Revolutionary Command Window says:
"Waiting for fastboot..."
And my phone rebooted into the HBOOT screen but it shows: S-ON
What should I do?
Is this in your guide?
1. Install drivers: http://www.multiupload.com/2OFYWZFCCR
2. Put phone in full boot, usb debugging on , charge only.
3. Uninstall HTC Sync if installed.
4. Profit.
sidepart said:
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Click to expand...
Click to collapse
Updating the driver worked..im good to go now.. thnx..
Hi Guys
This is my first attempt at Rooting my N8000. Kindly let me know if any more information is needed to help me out.
I'm currently on Stock 4.1.2 and I've never tried my hands on rooting, off late my device was lagging alot so i finally decided to go for the Root and make it faster.
My Cable & Drivers are perfect & up to date. The device ( int SDcard as well as the ext SDcard ) gets detected upon connecting to the computer.
However, when I connect the USB cable to the computer after entering into Recovery Download mode to use 'High on Android CWM' placed along with Android Revolution ROM on the root of my internal SDcard, the device fails to get detected.
ODIN detects the device on the respective COM port, i've tried by changing the port as well, but to no use. And, when I proceed and try to choose the PDA tab and select the internal SDcard. Device is missing.
The Tablet fails to get recognized at all. It does not even show up in Windows explorer.
I've searched a lot already but couldn't find any solutions. Any help would be appreciated.
Thanks in advance.
Raj
riturajgill said:
Hi Guys
This is my first attempt at Rooting my N8000. Kindly let me know if any more information is needed to help me out.
The Tablet fails to get recognized at all. It does not even show up in Windows explorer.
I've searched a lot already but couldn't find any solutions. Any help would be appreciated.
Thanks in advance.
Raj[/QUO
I think you need to read this post and follow the link in method 2 http://forum.xda-developers.com/showthread.php?t=1831152 ...Lots of info on rooting you're device..watch the video and I think you will see what you're doing wrong..Hope this helps..
Click to expand...
Click to collapse
Thanks a lot brother..... I was actually downloading the video walk through from the same post you referred when you replied here.
I'm getting the hang of things now.
Going to follow the process mentioned there and then take up the Android Revolution HD ROM.
My first attempt at rooting.... hope all goes well.... thanks again.:good:
riturajgill said:
Thanks a lot brother..... I was actually downloading the video walk through from the same post you referred when you replied here.
I'm getting the hang of things now.
Going to follow the process mentioned there and then take up the Android Revolution HD ROM.
My first attempt at rooting.... hope all goes well.... thanks again.:good:
Click to expand...
Click to collapse
No problem at all.. Being able to help people is why we're all here.. I seen you have been a member since 2011, but only have 3 posts.. Don't be afraid to jump in and ask questions and get involved in forum discussion's.. And here is you're first thanks..Good Luck.
Gil81 said:
No problem at all.. Being able to help people is why we're all here.. I seen you have been a member since 2011, but only have 3 posts.. Don't be afraid to jump in and ask questions and get involved in forum discussion's.. And here is you're first thanks..Good Luck.
Click to expand...
Click to collapse
Surely brother.
I joined xda long time when i had taken an S2 but had to change to Blackberry for official purposes, so could never follow Android Development.
Now that i've my N8000. I'm here to stay....
By the way, I just finished rooting my phone.
The trouble I was having in rooting since yesterday was because I was following the written directions in Android Revolution HD ROM.
I was trying to locate CWM's .tar file on my internal SD card. But it was not getting mounted since it was in Download mode. And i feared to brick my TAB by selecting the file from the Comp HDD. Watching the video solved that confusion in my head. Also, they didn't mention to untick Auto-boot in the video. First attempt, I didn't do it and Stock recovery replaced CWM. Next time, I unticked Auto-boot and manually booted into CWM recovery.
Anyway, All good now.....! time to taste real Android Power.
riturajgill said:
Surely brother.
I joined xda long time when i had taken an S2 but had to change to Blackberry for official purposes, so could never follow Android Development.
Now that i've my N8000. I'm here to stay....
By the way, I just finished rooting my phone.
The trouble I was having in rooting since yesterday was because I was following the written directions in Android Revolution HD ROM.
I was trying to locate CWM's .tar file on my internal SD card. But it was not getting mounted since it was in Download mode. And i feared to brick my TAB by selecting the file from the Comp HDD. Watching the video solved that confusion in my head. Also, they didn't mention to untick Auto-boot in the video. First attempt, I didn't do it and Stock recovery replaced CWM. Next time, I unticked Auto-boot and manually booted into CWM recovery.
Anyway, All good now.....! time to taste real Android Power.
Click to expand...
Click to collapse
Glad to hear it...now flash that thing like you stole it....lol
[SUMMARY] - If you're bored or find this kind of thing funny you could read this post from the bottom up and watch a noob go from freaking out, to learning how to troubleshoot then finally resolving his issue... all of this just by reading the FAQ thread and following some advice found there. I've learned my lesson... read XDA *before* trying to flash a new ROM.
[SOLVED] - Solution was to flash the boot.img from stock ROM. Once I did that the phone rebooted and went into the typical device setup. Now I guess I can update my ROM.
[FIRST UPDATE]
Turns out a lot of exactly what I was looking for is on the FAQ page (first bullet in Q15, no less). Trying what I found there. Please don't blast me with, Maybe you should have read the FAQ... I've been all over the place trying to find something that would work quickly... I only have one phone and I commute into Philly for work so I need a working phone... Now that I've found the XDA HTC ONE X + FAQ, I think I'll be fine. Thanks for the great site... so much info on here to read... good for long train rides.
[ORIGINAL POST]
Hi, I ran into a problem trying to flash CM to my HOX+ (AT&T). I followed the instructions here (wiki.cyanogenmod.org/w/Install_CM_for_enrc2b), but that was for the International version, not the AT&T... Dumb? Guess so, I don't know much about the difference, but it's what happened. I've tried to connect to the phone (per the instructions on the wiki) to adb push the ROM I want to flash, but I keep getting the device not found error. The instructions warn of possible driver error on the PC, but I haven't found a driver yet that will allow me to connect. I can get into recovery (CWM-based Recovery v6.0.2.7) but with no ROM on the sdcard I have nothing to flash and can't figure out how to get the file onto the device. The wiki should probably mention putting the ROM on the device prior to going through the HTC unlock steps, just in case, but maybe they assume a more cautious user than I am. I've tried to flash from sideload, but don't know if that is even possible?
Can someone point me in the right direction, or start asking questions to help me figure out what my next step is? Just want to get back to a working phone...
Thanks!
Signature?
Hi all,
I'm trying to install Cyanogemod on my i9100 (S2 intl). I'm quite experienced with flashing, rooting and Cyanogenmod in general as I've had it on both my Nexus 7 and my S3 for years. For the S3 I flash it via Heimdall cmd line; quite simple. For the S3, the recovery downloads as an img and just works. But for the S2, Clockworkmod's Recovery downloads as a zip, and not one of the tutorials explain how to use it. Do I flash the whole zip, just part of it or do I need to convert the zip to something else? And is kernel the correct partition to use?
The wiki guide doesn't give any help whatsoever. Everyone talks about zImage, but no where can I find what this is. There's a link on the wiki to download an img but it's broken and I can't find the image anywhere else. I think the wiki needs updating.
Drat, I can't put links in yet. I did have "wiki guide" linked.
I also posted my question to the Cyanogenmod forums, and they replied more quickly. This surprised me a bit; I may be a new account, but I've been a huge fan of XDA-Developers for a long time, and I was expecting a super quick answer. Maybe I posted in the wrong section for this, haha
For future reference, and to provide an answer for this question (and for ways around simple problems after that too):
forum.cyanogenmod.com/topic/96781-how-to-flash-latest-cwm-recovery-via-heimdall/
Turns out I was using the wrong kind of file for flashing via Heimdall. So glad my S3 was easier than this to flash Cyanogenmod.
So problem solved Any questions, I would be happy to elaborate.
1) This phone was released over 3 yrs ago, the S2 forums simply don't see the traffic they saw even 12 mths ago; 9 hrs is nothing.
2) Also, very very few people here use Heimdall as most are running Windoze machines. On Windoze you use Odin, there's no need to complicate things by attempting to use Heimdall.
So that's why you ended up with the first world 'problem' of not getting a response after 9 hrs.
You can elaborate on exactly what you did if you want; you never know, someone might come here one day & actually search for info rather than posting a thread purely because they can and expecting an immediate response.
1) This phone was released over 3 yrs ago, the S2 forums simply don't see the traffic they saw even 12 mths ago; 9 hrs is nothing.
So that's why you ended up with the first world 'problem' of not getting a response after 9 hrs.
Click to expand...
Click to collapse
I guess so. I hope you didn't think I was being too serious; I was only joking that I expected a reply that quickly Some areas of this site, people often reply in minutes, that's all
2) Also, very very few people here use Heimdall as most are running Windoze machines. On Windoze you use Odin, there's no need to complicate things by attempting to use Heimdall.
Click to expand...
Click to collapse
Really? I'm using Windows and I've never had any problems with Heimdall. In fact, I found Odin to be buggy and confusing. Heimdall seems far better (it's not leaked software, for a start), and I like the cmd-line interface.
You can elaborate on exactly what you did if you want; you never know, someone might come here one day & actually search for info rather than posting a thread purely because they can and expecting an immediate response.
Click to expand...
Click to collapse
I can't tell if you're annoyed that I didn't search or if you're joking. In fact I did search but couldn't find any information. And I wasn't going to elaborate here because all this info is in the Cyanogenmod forum thread, but if you insist:
1) Begin by reading the instructions on the wiki page: wiki.cyanogenmod.org/w/Install_CM_for_i9100
1-a) This means READ THE WARNINGS
2) When it tells you to download the recovery, ignore - the link is broken. Download from here: forum.xda-developers.com/galaxy-s2/orig-development/kernel-clockworkmod-recovery-6-0-2-9-t1118693
3) Extract the zImage file from inside and continue with the wiki instructions
4) When it tells you to click replace driver (which, btw, is badly worded - you must select "Install Driver" from the drop-down and it'll turn into "Replace Driver"), use the up-down arrows next to WinUSB to select libusbK. Otherwise you may get errors with Heimdall
5) After flashing the first CWM recovery, if you want to flash CM11, download the newer CWM from here: forum.xda-developers.com/galaxy-s2/development-derivatives/cwm-clockworkmod-recovery-kit-kat-4-4-t2628412
5-a) Start your S2 into Recovery and connect it via USB. On your PC, open a cmd and check that your device is showing up properly (adb devices). It it's not, download and install the Samsung USB drivers from here forum.xda-developers.com/showthread.php?t=2038555 or here forum.xda-developers.com/showthread.php?t=2038555 (or Google it - they're everywhere)
5-b) Use "adb push [recovery-zip-name-here] /emmc"
5-c) On your S2, find and flash the new recovery zip, then reboot into recovery again. You'll now be using the newer CM11-compatible CWM recovery
5-d) Now the device will no longer show up in ADB, even with the drivers installed (if it does for some reason, you can ignore this step). Open Device Manager on your PC and find either something called "i9100" or "Unknown Device" (of which there may be many on some computers - you'll have to work out which). Right-click > update driver software > browse my computer > let me pick > have disk.
5-e) Browse to the file and click ok "SAMSUNG\USB Drivers\16_Shrewsbury\ssadadb2.inf". This folder is normally in Program Files (not x86)
5-f) Continue by clicking next or whatever it is (I forget) to finish the installation of the driver. Test that it was successful (after it's finished) by doing "adb devices" again
6) If you're using the older CWM recovery: Use "adb push [cm<11-zip-name-here] /emmc" and flash it via the recovery
7) If you're using the newer CWM recovery: Use "adb push [cm11-zip-name-here] /storage/sdcard0" and flash via recovery
8) Push the correct gaps package (if using CM11, remember the warnings on the wiki - get the one that's small enough to fit on the S2's system partition) and flash it
9) At this point, you should be safe to wipe the cache and do a factory/data reset. I didn't (not immediately - I did a little later on), and just booted up, and it worked fine, but you'll probably want to do it at some point anyway to get rid of the crapps that are probably still on your S2 and it wipes all your data and settings, so best to do it now
10) Reboot an enjoy a freshly CM'd device! Remember that the first boot can take 5-10 mins. I'm currently using cm-11-20140609-SNAPSHOT-M7-i9100.zip, and so far it's been very stable, fast and reliable, only I've had issues trying to connect to the wifi. As there was a new snapshot released yesterday, I'm going to be updating to cm-11-20140708-SNAPSHOT-M8-i9100.zip shortly
There. It's not a complete beginner's guide, but it may help someone who's having problems with their S2 and Cyanogenmod. Hopefully this will show I don't expect anyone here to do all my work for me or to be at my beck and call; I should rarely be taken too seriously, and while I was genuinely surprised that no one replied faster, it was entirely a happy, curious surprise, not in any way an annoyed or unhappy surprise. Kinda feel like I got off to a bad start with that post
If anyone has any specific questions, I'll be happy to elaborate
Very good! Thanks!
btw, did you ever solved the wifi problema?
Genialt said:
Very good! Thanks!
btw, did you ever solved the wifi problema?
Click to expand...
Click to collapse
You're very welcome
What wifi problem? I've had no issues with the wifi (although, having said that, I don't believe I've actually tested the wifi with the phone since we're just using it as a 3G tether).
[Q&A] [10/13]Brick Station! Here to solve your brickable needs! BOOTLOADERS AVAILABL
Q&A for [10/13]Brick Station! Here to solve your brickable needs! BOOTLOADERS AVAILABLE!!!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [10/13]Brick Station! Here to solve your brickable needs! BOOTLOADERS AVAILABLE!!!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Still stuck.
EcHoFiiVe said:
READ EVERYTHING BEFORE YOU TRY THIS! TRY AT YOUR OWN RISK! IT'S NOT MY FAULT IF YOU MESS UP ON THIS AND IT GOES TERRIBLY WRONG FOR YOU!
This works.
I will help anyone whenever possible to solve their problems concerning their bricked players. If you can't get it showing up in Odin3 after the Unbrickable Mod, then I'm sorry I can't help you. Every computer is different. Just try to follow the advice. New links are available, so sorry for those that have requested new links! One of the links also contains the bootloaders for the Galaxy Player! Yay! I've saved all the files onto my computer so if a link goes dead, let me know and I'll put it up. Also, if one of the firmwares doesn't work, also let me know and what you tried doing with it.
IF AND ONLY IF you still can't get your player to boot after following this guide, let me know in the comments section what you did in the format:
1.US or INTL
2.What you flashed, with a link to it,
3.What happened AFTER you flashed the above
4.What your device does currently, eg, download mode, CWM only, partial boot, bootloop, no logo.
5.What you tried doing to solve this problem
If you do not follow this format, I WILL NOT RESPOND.
I had my Samsung Galaxy Player hard bricked and I thought all was lost and I thought I had tried everything but I started looking around for some help and ideas on what I could do to fix this problem.
The first thing I did was follow AdamOutlers guide for getting into recovery mode, and that thread can be found here: http://forum.xda-developers.com/showthread.php?t=1386669
Follow those directions and get back to this thread after you've successfully gotten it into download mode.
#Note: If you can't open the Ressurector, install Java onto your flavor of Linux. Then right-click on the resurrector, hit properties and check the Use as executable box or something similar.
*If you already have it in download mode, skip the first step!*
Okay, now that you have it in download mode, you have to get Odin3 for virtualbox. You don't need virtualbox if you can get it into download mode and if youre running Windows XP or higher. If your running Ubuntu or any other flavor of Linux, Heimdall won't work with the SGP and you're going to need virtualbox. The one I used and that worked can be found by going here: http://www.4shared.com/file/10JA2Dsu/Odin3_v183.html--You can get virtualbox for Linux by going here: https://www.virtualbox.org/wiki/Linux_Downloads--YOU WILL NEED YOUR OWN COPY OF WINDOWS FOR VIRTUALBOX!!
Once you have Odin3 running either in Windows or in Virtualbox, then go ahead and plug it into a USB port and a yellow box in Odin3 with a COM number should show up. If not, make sure you have the Samsung USB drivers installed in your copy of Windows in Virtualbox. You can get those here: http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-for-Mobile-Phones-1560.shtml-- I had a lot of trouble for my laptop to recognize that my player was plugged in and I had other people tell me the same. I think that in Virtualbox there are settings that have to do with USB devices and getting them recognized inside of Virtualbox. If not, someone let me know. So once you get it into download mode using the resurrector, flash this, IT HAS THE BOOTLOADERS NEEDED, NO MORE SCAMMBLE FOR CORRECT BOOTLOADERS!!!!!!!!!!!!--http://www.4shared.com/get/VtAB8dCU/G70JKKE3_STOK_222RU_.html Flash the one with All-Low or something of the sort.
If you can get it into download mode (Pwr+VolDown+Home) then install this with Odin3: http://forum.xda-developers.com/showthread.php?t=1863004
The first link comes with bootloaders and can get your SGP back up to booting. Once you install that, which is I believe, a Russian Froyo ROM, you must install from the link at the top, which is a stock ROM for us SGP that gets your home button working and is meant for the US variant of the Galaxy Player. It also includes Entropy's Daily Driver kernel and can get you back into CWM if you have a backup available.You need to be in download mode for this too.
BEFORE you install stock though, make sure your Samsung Galaxy Player boots! After that, flash the stock ROM back with download mode using Odin3.
If you have any questions, comments, concerns, feel free to write down below!!
NOTE: I need stock firmware for the 5.0 INTL version, if anyone has it please link it to me and I will post it in the OP.
IF I HELPED YOU, REMEMBER THE THANKS BUTTON!!!!!!!!
Thanks to: AdamOutler, gmillz, Entropy512
Click to expand...
Click to collapse
I've tried exactly what this said, and other variations of this guide and nothing is working. Odin gives a pass ( on 1.81, 1.83, and 1.85 all work) but when it reboots i still have lucky brick. im not sure waht to do...