[Black Screen Brick] Flashed i9000 bootloaders. - Samsung Galaxy Player 4.0, 5.0

So, I was thinking about giving a try the "serial console" way. Any instructions or directions on how to do it? Do I need the 623K resistor between pins 4-5 or in that state the player automatically allow the debug console?
Thanks in advance.

so wait, you flashed the wrong bootloader and now it's not working?
if so, try the ultimate resurrector thread in the dev section

I just used the guides found in the Dev section to resurrect a fully dead player... go there before you really break your player...

Actually, I accidentally flashed the wrong bootloaders & rom. I was dealing with a Galaxy S phone, at the same time. My bad. The problem is that the player is not recognized by my computer. Not even as a "S5PC110 Kit". It's like a real brick.
I think that the only way, is to go through serial console, upload the correct bootloaders and put it into download mode.
Maybe I can boot it by the SD card?! If so, anyone know how I can do it or what image I can use?
Thanks.

I don't think it allows SD card booting, but I could be wrong. When I've used the unbrickable resurrector before the device wasn't being recognized at all.. so if you haven't tried it yet it might be worth giving it a go.
If that doesn't work, you probably have to make or buy something to bring it back from the dead.

p34c3m4k3r said:
Actually, I accidentally flashed the wrong bootloaders & rom. I was dealing with a Galaxy S phone, at the same time. My bad. The problem is that the player is not recognized by my computer. Not even as a "S5PC110 Kit". It's like a real brick.
I think that the only way, is to go through serial console, upload the correct bootloaders and put it into download mode.
Maybe I can boot it by the SD card?! If so, anyone know how I can do it or what image I can use?
Thanks.
Click to expand...
Click to collapse
Have you tried this on a Linux box? The resurrector works in Linux.
If you are saying that your device is not even being shown as a SEC-S5PC110 when you plug into a usb port, I am not sure what you can do. If you flashed a wrong bootloader, I think you can still bring it back. Do a search and follow the directions found in the resurrector thread. I recovered a SEC-S5PC110 bricked device back from the dead using the method.
Good luck

Anyone with the jtag/uart diagram/pinout, at least?
Thanks.

Related

[Q] Soft bricked my friends vibrant:(

I apologize in advanced.
A friend handed me her vibrant and asked me to flash it so she could have the wi-fi hot spot ability.
I rooted it, then foolishly put one of the ROM's and now the phone is soft bricked... meaning I can get into recovery mode with the volume keys and power, but that's it.
I've tried to install a different rom from the external sdcard through recovery and it failed. (That is the only way I can get access a new update.zip file on the phone)
Can someone tell me exactly what to do to get a froyo rom on this phone working? I'd really really appreciate it.
P.S. I am on a mac, so I'm really looking for a solution that requires installing something from the external sd card. Is that even possible?
jameskever said:
I apologize in advanced.
A friend handed me her vibrant and asked me to flash it so she could have the wi-fi hot spot ability.
I rooted it, then foolishly put one of the ROM's and now the phone is soft bricked... meaning I can get into recovery mode with the volume keys and power, but that's it.
I've tried to install a different rom from the external sdcard through recovery and it failed. (That is the only way I can get access a new update.zip file on the phone)
Can someone tell me exactly what to do to get a froyo rom on this phone working? I'd really really appreciate it.
P.S. I am on a mac, so I'm really looking for a solution that requires installing something from the external sd card. Is that even possible?
Click to expand...
Click to collapse
Well you can go back to stock with Odin and try again...but since you're on a Mac....i think the Odin alternate is called Heimdall or something
EDIT: Found it....http://forum.xda-developers.com/showthread.php?t=834195
I'm sure it works just like Odin.....get the files needed to go back to stock here
http://forum.xda-developers.com/showthread.php?t=848737
this is good loool when can we expect to see i bricked my moms friend friends moms her sons phone
I'm glad someone is getting a kick out of this. I just downloaded Heimdall. I need to reboot and see if this can fix the problem. More to come...
I have to download something called qt which is a gig. Sucking internet from my epic at work... not going to happen today.
Note to self: NO MORE FLASHING FOR FRIENDS.
jameskever said:
I have to download something called qt which is a gig. Sucking internet from my epic at work... not going to happen today.
Note to self: NO MORE FLASHING FOR FRIENDS.
Click to expand...
Click to collapse
Thats weird... I dont even think Odin is more then 1MB, find it hard to believe that the Mac's alternate is so big. If you can find any windows machine it would be very easy to direct you on how to get her phone back up and running.
QT, which seems to be an environment like Java, is nearly a gig, and is necessary to run Heimdall on my mac.
The instructions for Odin says...
1. Open Odin3_v1.0
2. Load .512 into the PIT placeholder
(In this case s1_odin_20100512)
3. Load *FILE.tar* into PDA placeholder
(In this case Eugene_2E_JK2_Froyo.tar.md5)
4. Make sure COM port has a number in it
This means your phone is connected, if your phone is not connected make sure you have the correct drivers)
5. Press Start!
Click to expand...
Click to collapse
Using the image I've attached of Heimdall, which PDA/Code should I load the .md5 file under?
Thank you Odin, thank you Samsung USB drivers (which I had to google to find) and thank you mom's PC. I got my friend's phone working, unfortunately all her contacts were on the phone and not synced to google, and I didn't back her up. Whoops. Why would T-mobile transfer numbers from a black berry to an Android phone and not have it sync with google?
Heimdall was a waste of time and memory. I'm sure the developers worked very hard on it, but it totally didn't work for my mac book pro complicating a tense situation.
Problem solved.

[Q] IS my fascinate bricked beyond repair?

Hi guys im new to the forums and couldnt find any bricked fascinate info that could help so here i am. Forgive me if this has been discussed. Anyway my Samsung fascinate is really bricked bad. I cannot go into download mode to flash a stock through odin and i cant get to my nandroid backup in Cwm voodoo. Im stumped. Please help. And once again there's absolutely no way i can go into download mode, and none of my lights come on my buttons either. I fear shes done for. What i did before she bricked was like an idiot i flashed dorians ugjk3 v2? For captivates because i was under the impression it would work. WHAT DO I DO?
first search download mode "jig" in google. This will allow you to jumper certain pins on the usb port of your fascinate. If that dont work than you will have to give this a try.
http://forum.xda-developers.com/showthread.php?t=1288093
Im basing this off of the fact that you have tried every typical method of getting into dm...such as different computer, usb cable, uninstall/reinstall samsung drivers, heimdall instead of odin, etc...
Yea i cant use the jig because no samsung symbol comes up, and that second one I understand but Im not confident with a soldering iron. If thats the only possible way i will try it (after much practice elsewhere.) Ive never tried hiemdall because i read the walkthrough and its based the same as odin in requiring download mode am i correct? And thanx for your assistance
You are in luck my friend. Take a look at this post: http://forum.xda-developers.com/showthread.php?t=1288162. All you need is some soldering skills and vmware or virtual box to install Ubuntu if you don't alright have a computer running linux. Post back with your results if you attempt this, im curious if it works or not.goodluck

More Help!

If someone could provide me/direct me to a ROM with bootloaders, I'd be very thankful. Or if someone could tell me how to save my bricked player, that would be nice too. Thanks!
EcHoFiiVe said:
If someone could provide me/direct me to a ROM with bootloaders, I'd be very thankful. Or if someone could tell me how to save my bricked player, that would be nice too. Thanks!
Click to expand...
Click to collapse
I used the guide http://forum.xda-developers.com/showthread.php?t=1386669 to resurrect a player I bought fully bricked. No sign of life but now it's running normally. Go to the end of the thread and read my post.
I had to do a few attempts with diffent bootloaders and roms but at the end, I was able to get it back.
I am sure you have read most of the thread I pointed out to you already, but retry the steps since that is how I was able get mine to reboot normally.
Use the resurrector in Linux to get the player into Download mode (it went from black screen to showing Phone(!)PC icon). Trick is to keep it plugged in, since unplugging it shuts the player down and can't get Download mode with the button combos. So you will either need to have a Linux box with Virtual session of Windows to run Odin or, as my case, a dual boot. If you use the dual boot, when you switch from Linux to Windows, do not power down. Instead, reboot. It keeps the USB port powered and the player stays in Download mode (Phone(!)PC). In Windows run Odin to load bootloaders. You will need to flash a couple different bootloaders.
I flashed the Download mode only bootloader along with the pit file (included in the OP of the thread ^) to get the player into Download mode. It was stuck there until I flashed the SamsungPlayer bootloader (all found in the thread above) and got it to go into Recovery mode. Once there, I flashed a rom with CWM, factory reset and reboot... worked for me.
EcHoFiiVe said:
If someone could provide me/direct me to a ROM with bootloaders, I'd be very thankful. Or if someone could tell me how to save my bricked player, that would be nice too. Thanks!
Click to expand...
Click to collapse
As per the PM that I sent you, I'm also putting the link to the russian froyo firmware that I found, here. This firmware does have bootloaders in the firmware.
http://www.4shared.com/zip/VtAB8dCU/G70JKKE3_STOK_222RU_.html
Good luck and let me know how it goes.
Both of you guys helped me out, thank you so much!!
Sent from my Galaxy Nexus S using XDA

[Q] I might have messed up my bootloaders

So like title says, i think i might have messed up my bootloads on my galaxyplayer 4.0, it won't even turn on, or the screen won't turn on nor will it go to download mode, i hear jtag can fix this, but besides that, is there anything i can do that won't cost $40?
muji8u said:
So like title says, i think i might have messed up my bootloads on my galaxyplayer 4.0, it won't even turn on, or the screen won't turn on nor will it go to download mode, i hear jtag can fix this, but besides that, is there anything i can do that won't cost $40?
Click to expand...
Click to collapse
Maybe you could try the unbrickable resurector or a usb jig. Also could you describe what you did to get there.
idk y but i was jsut trying some stuff, tried to install some new o.s's on it and stuff, but it hink i got the bootloader for another phone and put it on it, i tried a usb jig but i can't get into download mode
muji8u said:
idk y but i was jsut trying some stuff, tried to install some new o.s's on it and stuff, but it hink i got the bootloader for another phone and put it on it, i tried a usb jig but i can't get into download mode
Click to expand...
Click to collapse
I'm not a professionnal but if you flashed another device bootloader onto your device I don't think there is really hope. I think JTAG is the only choice as it can flash bootloader (I think but not sure). Sorry but I can't help you anymore.
ti-pich said:
I'm not a professionnal but if you flashed another device bootloader onto your device I don't think there is really hope. I think JTAG is the only choice as it can flash bootloader (I think but not sure). Sorry but I can't help you anymore.
Click to expand...
Click to collapse
Not true, I flashed a 4.0 file unto my 5.0 player and I was able to fix it/get it working.
TheKryptonite said:
Not true, I flashed a 4.0 file unto my 5.0 player and I was able to fix it/get it working.
Click to expand...
Click to collapse
You probably flashed a 4.0 rom not a bootloader. Those are really different. I really doubt you could have done this if you flashed a bootloader even if the device are really the same as the bootloader is needed to get into download mode. Again, I'm not a professionnal but this is really unlikely to happen.
My 4.0 US player stopped working too. Got a 2 dollar jig off Amazon and went right into download mode. Make sure the jig is correct. And make sure you let you batter sit out of player about 20 seconds first.
Sent from my YP-G1 using Tapatalk 2

[Q] Hard Brick? Bootloader = dead?

Hey guys, big n00b here. I'll admit, I made a very fatal and somewhat idiotic mistake... ended up flashing a bad rom (illusions) to my phone. Unfortunately, after rebooting to test it, the phone completely stopped booting. Can't get into download or recovery mode. Does NOTHING when power is held. I have tried the microSD fix.. went out and got a 16GB card... no luck. This is why I think the bootloader is screwed up. I tried making a USB jig and that didn't work either... I have one coming in the mail, but that's going to be too long to wait.
My computer (running ubuntu by the way) detects the phone:
"Bus 003 Device 069: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)"
from lsusb.
Guys, PLEASE tell me that we can fix it ... without JTAG or replacing the EMMC... both of those are a bit too much. Would rather just say I spilled pop on it...
I have nearly lost all hope because NOTHING has worked. It isn't showing signs of life... Is there hope?
Is it possible that I didn't try the microSD fix enough times? I mean, I read that you may have to do the write a few times... which I did... :/
sci4me said:
Hey guys, big n00b here. I'll admit, I made a very fatal and somewhat idiotic mistake... ended up flashing a bad rom (illusions) to my phone. Unfortunately, after rebooting to test it, the phone completely stopped booting. Can't get into download or recovery mode. Does NOTHING when power is held. I have tried the microSD fix.. went out and got a 16GB card... no luck. This is why I think the bootloader is screwed up. I tried making a USB jig and that didn't work either... I have one coming in the mail, but that's going to be too long to wait.
My computer (running ubuntu by the way) detects the phone:
"Bus 003 Device 069: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)"
from lsusb.
Guys, PLEASE tell me that we can fix it ... without JTAG or replacing the EMMC... both of those are a bit too much. Would rather just say I spilled pop on it...
I have nearly lost all hope because NOTHING has worked. It isn't showing signs of life... Is there hope?
Is it possible that I didn't try the microSD fix enough times? I mean, I read that you may have to do the write a few times... which I did... :/
Click to expand...
Click to collapse
There is a guy over on android forums named shappypenguin, he may or may not be on XDA, but he has done magic on supposedly hard bricked phones. The fact that your computer recognizes the phone is a good thing. Does the phone go into download mode? If so, try downloading ODIN. It's literally a phone saver.
j61101 said:
There is a guy over on android forums named shappypenguin, he may or may not be on XDA, but he has done magic on supposedly hard bricked phones. The fact that your computer recognizes the phone is a good thing. Does the phone go into download mode? If so, try downloading ODIN. It's literally a phone saver.
Click to expand...
Click to collapse
I WISH it went into download mode, if it did I would be fine... and this thread wouldn't exist.
He is on XDA.
Microsd trick should still work, you sure you're doing it right?
DrFredPhD said:
Microsd trick should still work, you sure you're doing it right?
Click to expand...
Click to collapse
No lol, I'm not sure. I have a 16 GB Class 10 card and my phone is 16GB. I have tried multiple images and multiple different guides. I THINK the phone is trying to use the card... but not working for some reason.
Like I said, I have tried a lot of images... but I have no reliable way to confirm if they are the EXACT one I need.
One of the ones It tried was called debrick_sph_l710... but it doesn't seem to work.
To clarify, my phone is a Samsung Galaxy S3 on the Sprint network. Model SPH-L710.
I can keep trying the microSD...
Oh ok, I only know it should work on i9300. Not sure if it does for your model, you might get better help asking in your device specific forum.
Forgive me for bumping this early, but I have an expensive paperweight.
Is there any hope? Or will this require JTAG...?
If it doesn't go into download mode then usb jig, otherwise new motherboard.
boomboomer said:
If it doesn't go into download mode then usb jig, otherwise new motherboard.
Click to expand...
Click to collapse
Well, mine is in the main. I suppose I had better pray to the gods of Android that it works.
sci4me said:
No lol, I'm not sure. I have a 16 GB Class 10 card and my phone is 16GB. I have tried multiple images and multiple different guides. I THINK the phone is trying to use the card... but not working for some reason.
Like I said, I have tried a lot of images... but I have no reliable way to confirm if they are the EXACT one I need.
One of the ones It tried was called debrick_sph_l710... but it doesn't seem to work.
To clarify, my phone is a Samsung Galaxy S3 on the Sprint network. Model SPH-L710.
I can keep trying the microSD...
Click to expand...
Click to collapse
What version of Android were you running before you bricked it? It probably doesn't work because you aren't using the correct version.
TheKryptonite said:
What version of Android were you running before you bricked it? It probably doesn't work because you aren't using the correct version.
Click to expand...
Click to collapse
The rooted (and working) version was 4.4.2. Yes, this happened due to a incorrect version for the phone being flashed.
Ah, that explains why (I meant that it didn't work because you weren't using the correct version of your debrick image), click on the link below, write the debrick file to your SD card, and it should work.
http://forum.xda-developers.com/showthread.php?t=2740469
Sent from my SPH-L710 using XDA Free mobile app

Categories

Resources