a while back (about 3 weeks) i bought me a galaxy player us version 4.0. great player.
love it honestly.
but of course i wasnt satisfied.
so i rooted.
that was two weeks ago.
and tonight. i found myself trying to flash a custom kernel. called
"steves kernel" or something like that. and to my surprise using odin, it worked. rebooted. looked around. and the only thing different was the boot logo. booted to home screen. and worked naturally. wanted to boot into te CWM recovery that came with the custom rom to backup. "obviously was too late". and i backed up and rebooted. and of course. it was stuck in a bootloop. witht he fireworks looking thing. i looked for hours on end. for a stock rom of the 4.0 US version. i found what claimed to be 4.0 but either didnt match the md5 or were intl versions or WTF EVER.
(pretty damn steamed over here)
i unplugged my galaxy from my computer. and it instantly shut off. and now what seems to be a (from my experience with a psp; correct me otherwise) in a full brick. because it wont power on. it wont flash. it wont be recognized in windows. or any OS for that matter. nothing. tried battery pulll. nothing. someone.
please.
anyone.
help.
(also think i could get my money back from bestbuy if all else fails??)
When posting things like this, post EXACT links to what you actually flashed.
Flashing something without bootloaders in Odin shouldn't have done this.
try this - forum.xda-developers.com/showthread.php?t=1386669
the unbrickable recovery should be able to get your device back into download mode. when I bricked my player to the point that it wouldn't turn on it was able to save it.
I think it works under windows, download the unbrickable resurrector and the
Samsung bootloaders from the link. you need to have Java runtime installed for it to work too.
open the unbrickable resurrector ".jar" file, and select "galxay player" from the dropdown in the bottom left. plug your player in ane above the text box it should say "device detected." or something to that effect.
now hold the "volume down" button on your player and hit the download mode button in the program. keep holding the download mode button until your device comes on in download mode. if after 5-10 seconds the screen is still black, unplug your player, restart the program and try it again. it took me 4-5 tries sometimes but it always managed to bring it back.
when you do get it into download mode, fire up Odin and flash the player bootloader from the "galaxyplayer-bootloader.zip". make sure to check the flash bootloader box on the left side or Odin. if just the bootloader was screwed up, your device might boot now.. if it gets stuck at the Samsung logo you need to put it back in download mode (power + volume down) and reflash a good rom or recovery rom (not just a kernel). if it doesn't want to go back into download mode you can use the unbrickable process again.
good luck.
i am going to try this method. do you think it will help with my 4.0 though? the tut is for the 5.0.....
this isnt the EXACT link. however this is the exact software i used. (odin was 1.83 i do believe)
http // www anythingbutipod com/forum/ showthread php?t=66820
(fill all spaces with .)
That's why in the notes section for each of Steve's kernels it says not to use CWM
Try following logo20heli's work on it here http://forum.xda-developers.com/showpost.php?p=21302504&postcount=41 since he did the same thing and got stuck in a boot loop
woer said:
That's why in the notes section for each of Steve's kernels it says not to use CWM
Try following logo20heli's work on it here http://forum.xda-developers.com/showpost.php?p=21302504&postcount=41 since he did the same thing and got stuck in a boot loop
Click to expand...
Click to collapse
i looked there. however, i couldnt find any proper download links for anything.
macdomerocker said:
i am going to try this method. do you think it will help with my 4.0 though? the tut is for the 5.0.....
this isnt the EXACT link. however this is the exact software i used. (odin was 1.83 i do believe)
http // www anythingbutipod com/forum/ showthread php?t=66820
(fill all spaces with .)
Click to expand...
Click to collapse
I'm not sure if it'll work with the 4, I doubt trying it would hurt anything though.. just wouldn't work.
exodus454 said:
I'm not sure if it'll work with the 4, I doubt trying it would hurt anything though.. just wouldn't work.
Click to expand...
Click to collapse
well if anyone can help me out. this would be tremendous. i will post the results to that in a wee bit. gotta try it first
Read my thread in development.
Hyperrunner said:
Read my thread in development.
Click to expand...
Click to collapse
yes. however if you have read my problem it is FULLY BRICKED. so i have NO clue on how to get it unbricked. meaning that i couldnt get it to go into download mode if you were here in person. now if you know a way to unbrick me. please say so. THEN i can follow your tutorial.
lol just got back from bestbuy. they swapped me out because i bought it within the last 30 days.. so im good
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Hey, so I was trying to flash my friend's s3, and apparently, I did something wrong which got me stuck up at odin mode.
Initially, I could hold the vol up + home + power button to go to recovery, but now, even that won't work as it would just show me
Samsung's logo and a red exclamation mark on top left corner.
I've downloaded the firmware stock and tried to flash it using odin however it just won't work.
It says "NAND Write Start!!!" and it just stops there (stuck forever). It should (as I know it) show a progress bar on my android and
on it's interface to tell how much it has been done, but as soon as I start, the progress bar instantly fills up (on my android, the blue line)
and its just stuck there.
I've tried to take out the battery, clear cache/reset factory, take out sd and sim. But it simply won't work.
It's just stuck on "Downloading....do not turn of target!!!"
I cannot even get the flash counter to reset (I don't know how, since I can only open up odin mode)
counter: 4
binary: yes
Currently, I don't even know if it's suppose to be charging or the battery is just draining out.
Region for this phone is Turkey.
Yes I've also unrooted the phone using KingoRoot (previously, when it could go into recovery) but no luck.
Note: I have searched other threads on this forum but I cannot get anywhere around even close to fix my device.
It's soft-bricked (I assume, of course it is).
Any idea how to fix this?
Odin Screenshot (since it's my first post, it won't allow me to post outside links, sigh,):
http: // i.imgur .com/eBVZ3NN . png
^^ Just been stuck there....
Meanwhile on my android, it just shows a full-blue progress bar. And that downloading do not turn of target.
UPDATE:
THE PROBLEM HAS BEEN RESOLVED. I DOWNLOADED A CUSTOM FIRMWARE, (LUCKILY, CLOCKWORK MOD WORKED, JUST HAD TO WAIT AFTER GOING TO RECOVER)
FLASHED IT THROUGH THERE, WAITED FOR IT TO INSTALL, RESTART. BAM.
Did the 'something wrong' include flashing a firmware for another model?
What does the model number in download mode read?
You can try the rescue firmware, search general forum,.
Yeah, wrong firmware I suppose
boomboomer said:
Did the 'something wrong' include flashing a firmware for another model?
What does the model number in download mode read?
You can try the rescue firmware, search general forum,.
Click to expand...
Click to collapse
I was seeing this tutorial on how to install KitKat (4.4.4) on Galaxy S3. I must've made a mistake while trying to do so.
In other words, yes, flashing a firmware for another model.
You have a hard brick, sorry.
Yeah, no.
boomboomer said:
You have a hard brick, sorry.
Click to expand...
Click to collapse
No I don't lol. The problem has been solved anyway.
Im' glad to see you didn't give up on this, and came back to let us know what was wrong
I know this could be seen as off-topic, but the reality of devices becoming bricked isn't really possible luckily, it just takes longer to get around sometimes. If the item is worth fixing, then I always say keep at it, because I've never had an android device stay stuck so far. The only thing that really went nuts and refused to work, were 2 of the Iconia A500 tablets that lost access to their memory - but this is a common hardware fault as the RAM chips break away and need reflowing before you can even format the internal memory (it cant even see the SD cards either because the RAM comes and goes - same idea as plugging/unplugging a USB drive in Windows/Linux - it just doesn't know what to believe lol).
Great forum by the way, there's so much great information on here I get lost reading
Hello,
I know, my question is not new for the most of you and I think it is asked over 1000 times. I tried but I can't find the right working answer for me.
I have a problem, with my old Samsung Galaxy SIII GT- I9300 with T-Mobile branding.
Sorry for my english, but I did not found something useful on german websites but much useful in your forum, so I hope you may help.
The Phone is old, so I have no guarantee any more. I got it from a friend and for him it worked very well till now. It started with freezing on pages and the friend tried to recover the device and I think he did something wrong. The device ended up bricked.
Now, when I want to switch on the device it shows a white screen, with grey and black snow everywhere. Only thing I still can do is going in download mode, then it shows:
___________________________________________________________________
odin mode
Product name: GT-I9300
Custom binary download: No
Current Binary: Samsung Official
System Status: Custom
The robot picture
Downloading...
Do not turn off target !!
________________________________________________________________________
The friend who owned the phone said it is broken and buys a new phone.
I am new to modification phones and all things like that and I haven't got a clue what I'm doing, but I'm interested in learning and don't want to give up.
I read and read and read and looked at google and everywhere and the more I looked, the more different advices I found, but I don't know what will work for my device.
There is another problem, since I don't have a windows or Mac machine, I can't use odin. I work with linux, kubuntu 14.04 ( this is another project,I haven't a clue from, but I'm learning for fun) and I just managed to download JOdin3 Causal, working with heimdall-frontend 1.4.0-0.
I tried to flash firmware with one part and firmware with 3 parts, and I always get from Jodin: that the phone is connected, but there is no pit-file.
I added plenty of pit-files I found in the net, but Jodin said the pit-file was corrupt or broken or Jodin shows on top, left side: „running“ but nothing happens for hours.
Can someone help me. I think I need a firmware and the right pit-file for this firmware. What kind of firmware is not interesting for me, I just want to see the device come back to life again.
I found in the internet, that there is still hope, if the phone shows in odin mode a product name.
Because of this I think that my phone isn't scrap jet. Am I right?
Thanks in advance for your replay.
nina
No, your phone is dead. Try the dead boot recovery thread in general forum for a test but you will need a box.