Related
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post on the samsungvibrantforum. c o m. It had instructions on how to reset the phone using Odin with the .pit file and T959UVJFD.tar
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
rtekbillabong said:
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post on the samsungvibrantforum. c o m. It had instructions on how to reset the phone using Odin with the .pit file and T959UVJFD.tar
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
Click to expand...
Click to collapse
Have you looked here?
http://forum.xda-developers.com/showthread.php?t=849028
Have you tried using the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Yes I have tried both.
Both methods, pass in Odin3, but when the phone reboots, it always says in the list of actions, Wipe Data failed.
Both methods take me to a black screen after the S screen, and nothing happens.
Download Mode works. Recovery is 2E. Only 4 options though. reboot system now, reinstall packages, delete all user data, delete cache data.
Dude, just reboot, your phone's fine.
laylovj said:
Dude, just reboot, your phone's fine.
Click to expand...
Click to collapse
No it's not. I've rebooted the phone several times since last night. It still goes to a black screen.
Same problem here i tryed a over stock kernel and ended up the same as u! I was running bionix v i havent found no solutions .
Sent from my SGH-I897 using XDA Premium App
look for eugene's JK2 froyo that doesn't brick - flash it, then flash stock JFD. should fix it.
Ok, so I do the .pit/T959UVJFD.tar thing right? That's what you mean?
Ok, I did it, and it worked. Thank you very much for the advice. It's most appreciated.
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
Early yesterday I launched Kies and hit the update firmware option from the tools menu to see if the alleged ICS update was available for my phone. It appeared it was with, a message promoting that it would clear all personal data from the phone, which I then selected cancel so I could do a backup of pictures/videos on the phones internal SD.
Without doing any sort of backup yet I shutdown the phone, only for it to freeze on the shutting down screen. After 20 mins I pulled the battery and let the phone cool down since it had gotten warm trying to shut itself down. After replacing the battery and turning on it was stuck in a bootloop with only the SGS2 logo, never reaching the ATT logo.
At that point I came to XDA, which I frequently browse but have yet to root, and began reading and searching everything I could find.
Hours later I decided to attempt to flash the stock firmware from sammobile.com using Odin. The flash took a long time and I assume never completed. I left it overnight since I didnt want to unplug it mid-flash. Checking back in the morning the phone is black, Odin says failed/disconnected, and I find the battery completely drained. I charged it for a while then tried turning it back on and got the yellow triangle "firmware upgrade encountered an issue..." screen.
Now i'm attempting once more to flash the firmware but again it has been 30 mins on Sbl.bin. I've had a hard time finding stock firmware in different varieties with working links, so to not increase the flash counter in the event I ultimately have to send it in for repair.
Any suggestions on where to go from here? I've followed every direction I can find for flashing stock firmware and nothing has been successful.
Glad to help if I can. Please tell me exactly what package you flashed from sammobile, with a link if possible.
You should change the title of the thread.... I killed my phone. LOL!
http://forum.xda-developers.com/showthread.php?t=1313659
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
Try this.....
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile. Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
SOURCE: http://forum.xda-developers.com/showthread.php?t=1311081
creepyncrawly would know better. It's his thread.
Download the file from below post to go back to stock I777UCKH7. Follow the instruction written in the post. I just had the same a while ago using the mobile odin to go back to stock. Got stuck on Samsung Galaxy SII screen. Pulled the battery and then followed the instructions from this post. I selected the one that says no BL 'I777UCKH7 OCD No BL'.
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
Once you are done with the stock restore. To upgrade to ICS LE5 follow the instructions from below post. Make sure you read and follow the instructions as mentioned in the post.
http://forum.xda-developers.com/showpost.php?p=27707563&postcount=83
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
You downloaded I777UCKH7_I777ATTKH7_ATT and extracted I777UCKH7-rev02-home-low-cl503881.tar.md5?
Flashed the .tar.md5 in the pda slot?
What version of Odin are you using?
Edit: You're getting lots of advice here. Let me know if you need me to help troubleshoot your issues.
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
nett3 said:
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
Click to expand...
Click to collapse
Try using another micro usb wire if you have one. If not then get one from radioshack or bestbuy. I had the almost similar issue on my captivate with the original USB cable. Then I got a Rocketfish one from bestbuy and it worked like a charm.
I'm sure you might have already done this. Make sure you first run the ODIN and then put your phone in download mode.
krips your a genius!
The one click is now working thanks to the suggestion to pay attention to order of operations. I must have never plugged the phone in AFTER starting the one click. This was easily overlooked when I've been switching the phone between 2 PCs and 3 micro usb cables.
I now have a progress bar and have had made more progress than in the last 24 hours. Even after searching I did not find this solution, even though it's stated in the directions and it seems trivial, maybe it should be emphasized the one click needs to phone plugged in after it's running.
Thanks again. I'll update this post when it's back to being a phone again.
PS. BROKKANIC: you were right, if I didn't kill my phone then I sure was the impeding factor in its recovery.
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Is this a bootloader problem, kernel problem, or something else?
LOL!. Glad you got it working.
nett3 said:
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Click to expand...
Click to collapse
Flash back to stock first.
BROKKANIC said:
LOL!. Glad you got it working.
Flash back to stock first.
Click to expand...
Click to collapse
I believe that what I have been doing. I ran I777UCKH7 OCD With Root.exe, which resulted in bootloop, then ran I777UCKH7-CL503881-No-BL.exe, which also resulted in bootloop. Both completed successfully, but resulted in the same bootloop.
Odin appears unable to flash anything without it being a one click. I'm trying to flash Siyah-v2.6.14-att.tar. But Odin hangs at zImage with no progress bar.
What operating system you using: if windows 7 are you running as administrator ?
hd779 said:
What operating system you using: if windows 7 are you running as administrator ?
Click to expand...
Click to collapse
I've resorted to my WinXP laptop which has been more successful than my Win7 desktop. On the Win7 attempts everything is run as admin, but has many time bluescreened and hard reset the whole PC when attempting to flash anything with Odin. Maybe a separate issue, maybe not. But the XP machine is atleast successfully flashing the Odin one clicks.
Update: Odin standalone (non-one click) appears to be unable to flash anything, it will only hang when trying to write. One click Oden packages seem to work. Is there a one click with full stock sbl, param, kernel, etc?
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
gefox4vn said:
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
Click to expand...
Click to collapse
I haven't flashed a package with a bootloader yet. The only ones that work for me are Odin one click packages, and the two I've tried do not have bootloaders. I've been looking for one WITH a bootloader but no such luck yet, since maybe that would solve the problem.
The guide/link you've suggested will not work for me at this time. I do not have the ability to boot into any andriod OS. The only capability my phone has is executing Odin one click packages for some reason, even Oden standalone firmware flashes do not work.
I had a similar issue...I eventually got mine stuck at the ATT droplets....
Finally I flashed back to 2.3.4 stock....did the ota...then upgraded to ICS.
Its all on my work laptop so I wont be able to post any specific files or their names until monday...
Good luck!
Once your phone gets to the boot screen try to get into stock 3e (both volume buttons + power till 2nd SGSII splash screen) recovery and do a factory reset. Should boot after that. Good luck.
Sent from my SAMSUNG-SGH-I777 using xda premium
Why not try a custom ics rom? What else do you have to lose? Staying stock is overrated anyways. You may also have an antivirus stopping Odin but I doubt it. Just turn off your antivirus and try.
Sent from my SGH-I777 using xda premium
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
We need more info like what did it specifically say. Be as specific as possible
Sent from my Nexus 4 using xda app-developers app
RedJack117 said:
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
Click to expand...
Click to collapse
that's "usually" an error you get when the zip is corrupted.
but occasionally you'll get it if your running an i9000 roms (I've had it interchangeably with status 7 before)
I would try re-downloading and flashing the zip again.
if that doesn't work try downloading and flashing fluid kernel
then go to "advanced" and select "reboot recovery".
then try flashing the rom again.
Status 0 error on anything I try to flash using CWM
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
After you PM'd me, I started looking around about the Status 0 error being thrown. All signs point to the Updater Script that in the ROMs that you are flashing. My hunch is that once you flashed the CyanAOSP, that changed your build.prop from T959 to i9000 and that is why you are getting the error. I'm pretty sure there is a way to fix it (see below)
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
The zips that you mentioned are probably the standard Root.zip and the CWM zip from s15274n's thread stickied at the top of the Q&A section. Keep those handy.
Click to expand...
Click to collapse
Some answers in-line above.
**********************************
Let's get a few things straight before we start. I am still looking for the Heimdall JFD package, but I think that I know where it is. Pretty sure I put it on one of the external HDDs that I have. I'll try to upload it tonight or tomorrow night, as I am away all weekend with the family. I really don't think that you'll need it, but best to have it and not need it, than need it and not have it.
Theoretically, once you Odin'd back to JFD, I would think that it would've reset your device ID back to T959, but I guess that it didn't. This is what I would do. Odin to stock JFD and then boot it up and let it settle. Root it using the Root.zip that you have already used before. At some point you'll need to pick a ROM to settle on, even if only to get past this hump. (I use Sada's CM11 for my sons' Vibrants. Not that there is anything wrong with any of the others, but I just basically set it and forget it for my boys. I think though that he may have stopped development for it though, so I guess I'll be looking through the dev section myself here in the near future.) Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). My issue was a Status 7 because of the device ID being changed and the Recovery/Kernel combo weren't letting me flash. I basically opened up the ROM.zip and deleted those line and re-zipped it up and then flashed it (did it all on the phone and no PC, but I'm crazy like that).
Let's let a few of the current device Devs weigh in and see what they think. Already mentioned nirogu325 above, but let's try @epicboy and @dzee206 and @sada23. If they are inclined to come and help, it would be much appreciated.
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
Click to expand...
Click to collapse
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
The phone only had one major issue before I started messing with it - back & home buttons not working. I honestly can't remember how and what I did to put CyanAOSP on it but I ended up with 2 issues after putting it on. Only the Menu button works (eventhough all 4 lights up) and the USB seems to be grounded. I managed to work with it the past year up until I Odin-ed it back to JFD. When the phone is off and battery still has charge, the loading button would come up followed by the empty batt image at the background. This will loop until the batt dies. The only way to turn it on is by connecting the USB to a power source. Accessing download is easier because all I needed to do is remove batt then press and hold the vol up & down before putting the batt back in. Getting into recovery is a bit trickier. You'll need to wait until you actually see the phone charging before doing the 3-button combo.
Last Saturday, my daughter had a school event and I brought this along because it took better pictures than my S3 knock-off. During the parade, after shooting a video, it would automatically take me to the preview. Since, both back and home buttons were not working, I was stuck. Only option was to reboot it. What makes it interesting is that there is no reboot option on the JFD. It was a good thing that I had my power bank with me. I really did not want to constantly reboot it so I thought of installing one of those virtual button apps. I managed to install ToucherPRO before their presentation which made it much easier. To my surprise, it somehow revived the back button on the device itself - I noticed it when I got home that night to transfer the photos and vids.
I mentioned this so that you guys will have an idea on what I need to go through to get it fixed - somewhat, at least to a more tolerable state. (you won't believe it but the tips of my fingers hurt due to the number of times I have to go into recovery or download)
@Woody
Woody said:
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
Click to expand...
Click to collapse
Yup. I actually find it both weird and interesting - which games work and how they work.
Woody said:
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
Click to expand...
Click to collapse
Remember I mentioned my hesitation using Heimdall and Bay_wolf's AIO toolkit regarding hijacking drivers and stuff, Kies on this PC is now useless. It won't even recognize the phone after I tried the toolkit - which is good, I guess.
Woody said:
... Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). ...
Click to expand...
Click to collapse
I read about this when I started going back through the threads. As you mentioned, this is an old phone. Old phone = old threads. What I do is I read everything on page 1 then skip over to the last page, going back. Seems to be more effective specially for DL links.
I was actually reserving this one as part of my 'last option' fix. From experience, editing scripts is far more dangerous than flashing a 'working' one. I managed to root my other DD this way, but went downhill from there - ended up bricking it 3 times.
Anyway, I think I got it - or at least, the correct way of doing it. It took me 3 days....
After day 1, I ended up with 8 update.zips (7 CWM and one ROOT) and at least 2 copies of ROMS, GAPPS, MODEMS, and KERNELS on my SD card - only the update.zips worked, the rest either gave me status 0 or leave me with the 'Vibrant Samsung' bootloop. I had some progress on DAY 2. I read something like what epicboy said:
epicboy said:
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
Click to expand...
Click to collapse
I tried several JB ROMS listed on the Bible but, the problem was, I can't get into recovery - it was all 'blurry'. When I tried a different JB ROM, it also worked but was still 'blurry' during start up and on recovery. That's when I remembered Woody's post regarding rainbows and bootloaders.
DAY 3: For some reason, everything was flawless. I was able to install JB then KK. EFFORTLESSLY, if I may add.
@epicboy
I'm planning to spend a couple of days more on this Vibrant before I mess with my other phone - a knock-off SGS3. I was drawn to L-Droid because the screenshots and contents of page 1 of their thread was specifically for the T959 and not the I9000. I know it's not really a big deal because the ROM will work and changing the build.prop for 'cosmetic purposes is easy. What really concerns me is the camera. Sadly, the T959 only has only one camera and if the camera app that you're using (stock or otherwise) has a feature to switch from back-to-front and you accidentally press that, it messes it up to the point that you can't use it anymore. I have downloaded the ROM and will try it out in a couple of days. Will send you a PM or reply on the thread regarding my feedback. I've flashed it several times but really haven't been able to do it flawlessly like in DAY 3 - which I find really weird.
Tnx peeps!