Galaxy Player 5.0 Bootloader *ONLY* Hard Brick Recovery

Search This thread
By:
Advanced…
AdamOutler

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,827
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
Introduction
Hey guys.. I came up with a partial recovery method for black screen bricks. It's not a full recovery yet as the device won't get past booting the kernel. However, this is a matter of obtaining the proper firmware... So, until a better firmware is obtained the next best thing is to at least get the device into Download Mode.

Generally Hard bricks occur when the improper firmware is flashed on a device. When the wrong bootloaders are loaded, the device attempts to boot and fails. Instead of hanging, sometimes the device will enter a "Lucky Brick" state. These lucky bricks are very common on Galaxy Player.

The Galaxy Player tends to failover into a safe mode which we call UnBrickable Mod. This safe mode can only effectively be used in Linux because of a lack of decent windows drivers and a lack of any real development for Mac outside of Apple Corp ;).

Heimdall has not yet been upgraded to handle the Galaxy Player so a virtual machine is required for this procedure.


You Will Need:


Instructions
  1. First plug your Galaxy Player into the computer.
  2. Launch the UnBrickable Resurector R36 and observe the following image. If the device does not detect, hold the power and home button for 10 seconds to make the device reboot.
    1qiwcm.png

    Note: if you cannot get this screen, stop. You will not be able to continue. You've given it a shot and there are no other known methods which will currently work
  3. Select S5PC111 from the Device Type Dropdown List. Then click the "Download Mode" Button. Your device should be detected as the picture in the following displays. If your device is not detected, try again and ensure you have the proper Resurrector selected
    9kmj42.png

  4. Unzip the GalaxyPlayer-Bootloaders.zip to the Desktop folder in your Windows VM
  5. Launch Odin3 in the Windows VM
  6. Set the PIT option as "GalaxyPlayerPart.pit" Set the "Bootloader" option to GalaxyPLayerDownloadModeOnly.tar
  7. In the menu bar on your Windows VM, in Linux, select Devices>USB Devices>SAMSUNG Gadget Serial to attach the device to Windows.
    21jygr5.png

    Note: you should see the device connected and a "COM" assigned in Odin after the device has installed properly
  8. Click "Start" on Odin3. Note: If this fails, you will need to reinstall Samsung Drivers.
  9. This is where this guide ends. I have tried several firmwares but none have been effective at recovering the Galaxy Player...
Conclusion
Your device is now in Download Mode.. If anyone can help in locating a /data/ partition(Not dbdata), I could sterilizeit of your information and it would be helpful. If anyone can post up an EFS partition, I could remove the information from that and force it into a default...

Basically, I need a full dd dump of every single partition on the device in order to finish this resurrection DIY.
 

Attachments

  • GalaxyPlayer-Bootloaders.zip
    3.8 MB · Views: 8,351
Last edited:
  • Like
Reactions: alireza21, Tafelpoowt, Matoxxi and 11 others
R

rumirand

Senior Member
Oct 8, 2011
171
53
Madrid
OnePlus 8 Pro
Samsung Galaxy Watch 4
That's my question, lol.

On wednesday I can upload the dd dumps of every partition so they can be flashable via odin.

I've 'dd'ed that image to a sdcard. Checked partition table and it seems ok. So the only think needed is to dump the right partitions. Right now, I'm busy with exams, so I can't before.
 
Last edited:
AdamOutler

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,827
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
  • Like
Reactions: pmdisawesome
Zyxxeil

Zyxxeil

Senior Member
Apr 9, 2011
1,277
4,181
Ima post the md5 file needed to flash with odin in just a sec hold on.
 
gaad0701

gaad0701

Senior Member
Mar 7, 2011
201
41
Albertville, MN
Uh-oh

AdamOutler said:
Introduction
Generally Hard bricks occur when the improper firmware is flashed on a device. When the wrong bootloaders are loaded, the device attempts to boot and fails. Instead of hanging, sometimes the device will enter a "Lucky Brick" state. These lucky bricks are very common on Galaxy Player.
Click to expand...
Click to collapse

Ok so I have an issue that is between the hard brick and the lucky brick I think.

My Galaxy is stuck in Android Stock Recovery (My soft keys are not working) and I have attempted to get the Resurrector to work on my device, but it seems like it won't see my player correctly for me to bring it back.

If you know any kind of fix for this I would really appreciate it, my Wife is ready to kill me...
 
Jesse6749

Jesse6749

Senior Member
May 1, 2010
1,185
116
T.B.A
Adam, I have Ubuntu and the virtual machine setup and working. I just cannot get Ubuntu to allow me to open the resurector file as an executable, any idea why and how I can fix that issue, it tries to open it as a archived compressed file. I have the black screen and badly need to revive my Player.

Update: After searching on google I finally got Ubuntu to execute the resurrector file and I revived my player and have Froyo 2.2.2 running on it now, but the capacitive buttons do not work. I will dowload the soft button app to fix the buttons till someone finds a solution for the dead buttons which was caused on my player by the Korean 2.3.6 firmware leak that I flashed yesterday and caused all my problems. After searching some more I found the files I needed to get my capacitive buttons working again on the samfirmware.com web site, so now I have restored my player to the original working state.

Adam, you are a life saver, Thank You very much for the excellent recovery guide!!!!

Everyone on the forum, have a Happy New Year!!!!!!
 
Last edited:
azoller1

azoller1

Senior Member
Aug 4, 2011
1,928
1,807
My Room
OnePlus 8T
Jesse6749 said:
Adam, I have Ubuntu and the virtual machine setup and working. I just cannot get Ubuntu to allow me to open the resurector file as an executable, any idea why and how I can fix that issue, it tries to open it as a archived compressed file. I have the black screen and badly need to revive my Player.

Update: After searching on google I finally got Ubuntu to execute the resurrector file and I revived my player and have Froyo 2.2.2 running on it now, but the capacitive buttons do not work. I will dowload the soft button app to fix the buttons till someone finds a solution for the dead buttons which was caused on my player by the Korean 2.3.6 firmware leak that I flashed yesterday and caused all my problems. After searching some more I found the files I needed to get my capacitive buttons working again on the samfirmware.com web site, so now I have restored my player to the original working state.

Adam, you are a life saver, Thank You very much for the excellent recovery guide!!!!

Everyone on the forum, have a Happy New Year!!!!!!
Click to expand...
Click to collapse
How did you make it run as an executable I have this same problem it opens like a zip compressed file
 
M

Meticulus

Guest
java -jar whateverfile.jar

Sent from my YP-G70 using Tapatalk
 
I

ishish9

Member
Jul 18, 2007
16
2
I'm still unable to fully unbrick my device (YPGB70) even with all the proper files, it still just hangs at the logo, I can get into download mode just fine though. The only files missing from Samsungs official rom they released are efs.rfs, userfs_16G.rfs, inand_16G.bin these are the only file listed on the pit but aren't in the rom file. Are the userfs and inand crucial file and if so can I use files from the international or US models and do they have to be the same 16G size?
 
Jesse6749

Jesse6749

Senior Member
May 1, 2010
1,185
116
T.B.A
ishish9 said:
I'm still unable to fully unbrick my device (YPGB70) even with all the proper files, it still just hangs at the logo, I can get into download mode just fine though. The only files missing from Samsungs official rom they released are efs.rfs, userfs_16G.rfs, inand_16G.bin these are the only file listed on the pit but aren't in the rom file. Are the userfs and inand crucial file and if so can I use files from the international or US models and do they have to be the same 16G size?
Click to expand...
Click to collapse

What I did once I got it to the download mode using Adam's guide, then I downloaded the 2.2.2 froyo rom for the player found at www.samfirmware.com and flashed it using odin that got the player working but the capacitive key would still not work, so then I put the player back into download mode and downloaded and flashed the rom from Maticulus found here: http://xdaforums.com/showthread.php?t=1450013 using odin again and this got the player working like new again including the capacitive keys.

Good Luck!!! :p
 
NeoSmart

NeoSmart

Member
Jan 26, 2012
18
1
HELP

I have a samsung galaxy player 5.0 and I try to unbricked by fallowing your tutorial and it detect my device it said:"S5PC110 DETECTED !" and when I hit Perform Resurrection and said:"Failed to write 1310730 bytes" I try using the "Galaxy Player S5PC111 and it didn't work" then I try to use "S5PC110 GALAXY S" then I try "S5PC110 GALAXY S" " and it didn't work Please Help

My Model is a YP-G70CWY/XAA galaxy player 5.0
 
You must log in or register to reply here.

Similar threads

DoeBoi
[Q] Rooting Samsung Galaxy Player YP-G70 (5.0 wifi)
Replies
497
Views
263K
zaclimon
zaclimon
eng_matt
[ROM] Eryigit-GB-2.3.6 G70ZCKPA Galaxy Player 5.0 For USA and INT (Rls:3.5) {UPDATED}
Replies
381
Views
197K
kings121
kings121
JackpotClavin
[ROM] CM9 (ICS) for the Galaxy Player 5.0 USA
Replies
445
Views
138K
H
hanjosep
R
[KERNEL][CWM][OC&UV] rj's custom kernel for Galaxy Player 5.0 INTL (YP-G70) r14
Replies
232
Views
152K
necktru
necktru
zaclimon
  • Sticky
The Samsung Galaxy Players/S Wifi (All Variants) All-In-One Thread [25.06.2014]
Replies
172
Views
206K
yakapa40
yakapa40

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 14
    AdamOutler
    AdamOutler
    Introduction
    Hey guys.. I came up with a partial recovery method for black screen bricks. It's not a full recovery yet as the device won't get past booting the kernel. However, this is a matter of obtaining the proper firmware... So, until a better firmware is obtained the next best thing is to at least get the device into Download Mode.

    Generally Hard bricks occur when the improper firmware is flashed on a device. When the wrong bootloaders are loaded, the device attempts to boot and fails. Instead of hanging, sometimes the device will enter a "Lucky Brick" state. These lucky bricks are very common on Galaxy Player.

    The Galaxy Player tends to failover into a safe mode which we call UnBrickable Mod. This safe mode can only effectively be used in Linux because of a lack of decent windows drivers and a lack of any real development for Mac outside of Apple Corp ;).

    Heimdall has not yet been upgraded to handle the Galaxy Player so a virtual machine is required for this procedure.


    You Will Need:


    Instructions
    1. First plug your Galaxy Player into the computer.
    2. Launch the UnBrickable Resurector R36 and observe the following image. If the device does not detect, hold the power and home button for 10 seconds to make the device reboot.
      1qiwcm.png

      Note: if you cannot get this screen, stop. You will not be able to continue. You've given it a shot and there are no other known methods which will currently work
    3. Select S5PC111 from the Device Type Dropdown List. Then click the "Download Mode" Button. Your device should be detected as the picture in the following displays. If your device is not detected, try again and ensure you have the proper Resurrector selected
      9kmj42.png

    4. Unzip the GalaxyPlayer-Bootloaders.zip to the Desktop folder in your Windows VM
    5. Launch Odin3 in the Windows VM
    6. Set the PIT option as "GalaxyPlayerPart.pit" Set the "Bootloader" option to GalaxyPLayerDownloadModeOnly.tar
    7. In the menu bar on your Windows VM, in Linux, select Devices>USB Devices>SAMSUNG Gadget Serial to attach the device to Windows.
      21jygr5.png

      Note: you should see the device connected and a "COM" assigned in Odin after the device has installed properly
    8. Click "Start" on Odin3. Note: If this fails, you will need to reinstall Samsung Drivers.
    9. This is where this guide ends. I have tried several firmwares but none have been effective at recovering the Galaxy Player...
    Conclusion
    Your device is now in Download Mode.. If anyone can help in locating a /data/ partition(Not dbdata), I could sterilizeit of your information and it would be helpful. If anyone can post up an EFS partition, I could remove the information from that and force it into a default...

    Basically, I need a full dd dump of every single partition on the device in order to finish this resurrection DIY.
    View
    3
    AdamOutler
    AdamOutler
    rumirand said:
    Hi AdamOutler:

    You can find that here: http://xdaforums.com/showpost.php?p=19840746&postcount=420

    That's a full dump of /dev/block/mmcblk0
    Click to expand...
    Click to collapse
    and how do you upload that through download mode?
    View
    2
    C
    cvcduty
    It took many... many tries but I was able to take a fully bricked (black screen - sec s5pc110 test b/d) YP-G70 US 5.0 player and get it back to functioning as new.
    I have CM9 loaded now and runs it like a champ.

    I used this guide as well as few others that I found from other forums.

    Ultimately, I used a Ubuntu installation and Ressurector to get the player to display the phone (!) computer icon. The trick was (which the instuctions did was not quite clear on) was that the Download mode which the Ressurector get the player into, does not display the Andy with yellow triangle sign. It's the Phone (!) PC icon that is the download mode.

    Anyway, I was not able to get a VM session of the Windows within my Ubuntu box (spent 2 hours trying to figure out why!!!) but I had a dual boot session.
    I kept the player plugged into the USB port to keep the Phone (!) PC mode on and restarted my laptop to switch to the Windows session to run Odin.

    Here, I had to flash the device with Odin 3-4 times until it let me boot into Recovery mode.

    So the first time I flashed with Odin, I followed the direction from OP and flashed the pit and bootloader. This got me to the Download mode... problem was, when I flashed the Eryigit Rom (PDA), it successfully flashed but it was still stuck in Download mode when I rebooted.

    So next I got a Stock GB (2.3.6) from here - http://xdaforums.com/showthread.php?t=1520728 and flashed it. This file contained a pit file as well... and since I was stuck in Download mode, I figured that maybe my system was not seeing the right partitions. So I tried flashing the pit file from here and it got stuck in "Partitions". So When I yanked the cable and restarted my player, now I had the phone (!) pc icon again.
    Back to step 1 and this time, I flashed the pit and bootloader from OP... and then power down and power up to flash the Stock rom that I mentioned above without the pit file found with the rom.... just the stock rom.
    Now, I was booted into recovery mode and recovery mode only... so I got the player back to Download mode and flashed the pit file from the OP but this time, I used the SamsungPlayer Bootloaded found in the OP instead of the Download Mode only bootloader.
    Once this was done, I rebooted the player into Download mode yet again, and flashed the Eryigit's US rom... reboot... recovery... DANM!!!... here I accidentally pressed the restart system and this time I was seeing the Samsung logo... and then Android bootanimation... My player was alive...

    Anyway, this was not an easy task but THANK you for pointing me out a few things that I could try in order to get the player back to life.

    Sorry for the long post... I know a few on this thread are experiencing the same issues I saw... I am trying to point out that there is a way to fix the player... just got to try a bit harder... :)
    View
    1
    AdamOutler
    AdamOutler
    rumirand said:
    That's my question, lol.

    On wednesday I can upload the dd dumps of every partition so they can be flashable via odin.

    I've 'dd'ed that image to a sdcard. Checked partition table and it seems ok. So the only think needed is to dump the right partitions. Right now, I'm busy with exams, so I can't before.
    Click to expand...
    Click to collapse

    This is what we need: http://xdaforums.com/showthread.php?p=20201368#post20201368
    View
    1
    AdamOutler
    AdamOutler
    iJimaniac said:
    Hmm, it gets stuck at "set partition".
    Any advice?
    Click to expand...
    Click to collapse

    The problem is that we need a partition information table which is proper for each device. I started that thread here: http://xdaforums.com/showthread.php?t=1389873
    View

New posts