I followed the guide on Pathik Shah to put Froyo on Galaxy S phones. I assumed since I the Vibrant was a Galaxy S phone it would work. Now I'm stuck in the recovery screen. I can't select anything or get to downloader mode because there's no OK button to do the combination with.
What do I do? How can I possibly get any Vibrant FW back on my phone?
You can use adb to reboot when in recovery. I'm not sure what version of froyo you installed so I can't guarantee how to safely reflash original firmware--a few months ago a bunch of people messed up their phones by installing a European firmware then trying to reinstall our firmware.
Sent from my SGH-T959 using XDA App
shalpp said:
I followed the guide on Pathik Shah to put Froyo on Galaxy S phones. I assumed since I the Vibrant was a Galaxy S phone it would work. Now I'm stuck in the recovery screen. I can't select anything or get to downloader mode because there's no OK button to do the combination with.
What do I do? How can I possibly get any Vibrant FW back on my phone?
Click to expand...
Click to collapse
In development section go to the bible and download the froyo rom that does not brick and continue from there.
Related
I rooted my phone not too long ago and finally decided to add a custom ROM to my Vibrant. I went with the eugene373 Vibrant Hybrid after using the ROM manager to extract it the phone froze on the boot up screen I can hear the boot up sound but stays on the screen the rest of the time. I followed all the info on the rooting process but I don't know if there's a way I can just got back or fix the ROM. Thanks in advance!
MeximCivic said:
I rooted my phone not too long ago and finally decided to add a custom ROM to my Vibrant. I went with the eugene373 Vibrant Hybrid after using the ROM manager to extract it the phone froze on the boot up screen I can hear the boot up sound but stays on the screen the rest of the time. I followed all the info on the rooting process but I don't know if there's a way I can just got back or fix the ROM. Thanks in advance!
Click to expand...
Click to collapse
You have to use odin to go back to stock.
Sent from my vibrant.
MeximCivic said:
I rooted my phone not too long ago and finally decided to add a custom ROM to my Vibrant. I went with the eugene373 Vibrant Hybrid after using the ROM manager to extract it the phone froze on the boot up screen I can hear the boot up sound but stays on the screen the rest of the time. I followed all the info on the rooting process but I don't know if there's a way I can just got back or fix the ROM. Thanks in advance!
Click to expand...
Click to collapse
Please note "Q" means question not "DEV".
Instead of telling people "wrong thread" why not just help them. Go to the "Bible" in development thread download odin and stock jfd, once you downloaded those 2 run odin press PIT and click on the 512.pit file and for pda its the JFD you downloaded if you dont understand what im saying go look at threads of how to use odin back to stock its more detailed. Your phone itself has to be in download mode, easiest way since the 3 button dont work for some (like me) fully turn off your phone if it doesnt pull the battery out. Once its fully off press and hold the 2 volume keys and plug in the usb and your in the download screen and press Start for odin and your back at stock. (And now that I helped) next time post this into a Q&A or General thread so you dont get flamed. Good luck
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Please help! i tried searching for this, but can't seem to find a solution...
I currently have FROYO.UVJK2 with Kernel version of 2.6.32.9
in trying to load the Nero v5, i went to ROM manager and got the latest ClockworkMod Recovery to 2.5.1.2.
After this update, i push the reboot into Recovery. however, instead of going in to the ClockworkMod Recovery menu after reboot, it keeps just hanging on the Vibrant screen.
I tried to do the ClockworkMod manually with no success either, it just hangs on vibrant screen. -,-;
help!
Any suggestions? Thanks!
Also: i tried older clockworkmod recovery files with no success either. When every i try to manually get into the Recovery, the "vibrant" either just hangs or just keeps restarting. I have to do a battery pull to be able to get past the hanging vibrant stage.
sorry guys, i posted in the wrong forum. Could the mod move this to general?
again. my bad.
Odin back to stock and try again.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
serban954 said:
Odin back to stock and try again.
Click to expand...
Click to collapse
would Odin be the only solution?
After Odin, do i use a custom ROM to restart or is it just plug, load and i am good to go..? seems like the instructions i found so far just guide you to upload the Odin into your phone but doesn't say what to do next. I guess what i am wondering is, after Odin, does the phone revert back to stock ROM?
nahooneyya said:
would Odin be the only solution?
After Odin, do i use a custom ROM to restart or is it just plug, load and i am good to go..? seems like the instructions i found so far just guide you to upload the Odin into your phone but doesn't say what to do next. I guess what i am wondering is, after Odin, does the phone revert back to stock ROM?
Click to expand...
Click to collapse
i have same problem,,but the computer does not SEE the phone so i cant even odin....the computer SEE'S my other vib. phone just not this one,,wtf...i put the other phone back to stock and then did the ota 2.2 from kies,,but this phone is driving my crazy.
so im trying to help my cousin out he wanted me to return his phone to stock because he was having issues with mms and gps. it was on one of the bionix roms i cant remember which version thou. so i was reading all this morning trying to figure out the best way to unroot and odin seemed to be the easiest. i followed this guide (http://forum.xda-developers.com/showthread.php?t=734475) and everything went perfect and when the phone began to boot it showed the 3 boot screens (samsung vibrant, pink stick together, then the blue one with the lil jingle that says galaxy s) and then the screen just goes black and nothing happens.. i have to take the battery out and i can still get into download mode and the android system recovery but idk what to do. ive tried redoing odin back to stock but always the same outcome. for the past 2 hours ive been non stop searching but cant find anything that will help if someone could shed some light on what i need to do that would be awesome. ty
I'll grab the link in a minute and post it for ya. You should try flashing eugene's froyo that doesnt brick via odin, let it reboot to recovery. Pull the battery, boot back to dl mode, then flash the stock jfd via odin selecting repartition the last flash. Be sure you can get to dl mode with the volume button- plug in usb method before flashing the froyo that doesnt brick, you'll need to boot back to dl mode that way after the battery pull.
Edit: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Hope it helps
Sent from my Loki powered Vibrant on the XDA App
When the phone is rebooting how long does the screen stay black, after the first boot of changing a kernel or any system files the dalvik cache needs to be rebuilt and can take some time (upto 5 minutes) on the first boot. My suggestion is to make sure and use jfd tar file and 512 pit file and then just let the phone sit for about 15 minutes after odin says pass. Once you get a pass from odin the phone is going to work unless something in the tar or pit files was damaged. Just let the phone sit and all should be well.
thanks for the quick replys im going to try both suggestions now and ill get back to u when i find out if they work
Br1cK'd said:
I'll grab the link in a minute and post it for ya. You should try flashing eugene's froyo that doesnt brick via odin, let it reboot to recovery. Pull the battery, boot back to dl mode, then flash the stock jfd via odin selecting repartition the last flash. Be sure you can get to dl mode with the volume button- plug in usb method before flashing the froyo that doesnt brick, you'll need to boot back to dl mode that way after the battery pull.
Edit: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Hope it helps
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
+1 this is the sure way to solve this problem
well thanks for both replys Br1ck'd ur method worked his phone is now back on stock! just one last thing how should i go about updating it to the latest stock rom. when i hit software update it says nothing is available. i know there is a newer eclair update but since i dont have a vibrant im not to sure what the latest is. i see there is a froyo update out there but has tmobile released an official that i can load on there for him? and how will i go about getting it?
dylan6879 said:
well thanks for both replys Br1ck'd ur method worked his phone is now back on stock! just one last thing how should i go about updating it to the latest stock rom. when i hit software update it says nothing is available. i know there is a newer eclair update but since i dont have a vibrant im not to sure what the latest is. i see there is a froyo update out there but has tmobile released an official that i can load on there for him? and how will i go about getting it?
Click to expand...
Click to collapse
The only official 2.2 we have for the vibrant wasnt released as an ota. You can snag it through Kies or KiesMini, but it was my understanding that it messed up some peoples sd cards. If youre looking for 2.2, and you want it as stock as possible, your best bet is to dl and flash one of Whitehawkx Ka6, KA7, or KB1 roms in the developement forum. My Loki build is 2.2, but far from stock, and we have a bunch of roms out here that are going to run better than any ota update.
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
The only official 2.2 we have for the vibrant wasnt released as an ota. You can snag it through Kies or KiesMini, but it was my understanding that it messed up some peoples sd cards. If youre looking for 2.2, and you want it as stock as possible, your best bet is to dl and flash one of Whitehawkx Ka6, KA7, or KB1 roms in the developement forum. My Loki build is 2.2, but far from stock, and we have a bunch of roms out here that are going to run better than any ota update.
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
+1 Loki Rules
Hi all,
I bought this used Samsung Galaxy S vibrant with all manufacture software.
I need the instructions for root this device and then install a custom rom.
Thanks
Device Info:
Android 2.2
Kernel 2.6.32.9
estroked said:
Hi all,
I bought this used Samsung Galaxy S vibrant with all manufacture software.
I need the instructions for root this device and then install a custom rom.
Thanks
Device Info:
Android 2.2
Kernel 2.6.32.9
Click to expand...
Click to collapse
Everything you need to know should be right here:
http://forum.xda-developers.com/showthread.php?t=849028
In the early days of Vibrant, you could easily root via update.zip. Then that stopped working, I think because of the 3e recovery. Anyway, I just use one of the already rooted ROMS like the deodexed and rooted KB5 found in the development section.
But update.zip should still work for you if you are running an older stock vibrant rom.
Do you know what odin is?
This is what I did.
Odin to jfd
use update.zip to root JFD
Install clockworkmod recovery or it's update.zip
Then apply your ROM of choice... I run deodexed/rooted KB5. I'm a fan of stock.
just read everything in that link above it explains the different ways to root ur phone.
my fav method.
Check usb debugging and unknown sources in settings
Go to 4shared.com and dl z4root.
Root.
Simple.
Sent from my SGH-T959 using XDA Premium App
A few things u should check for right away because some sgs are hardware locked.
1-see if u can get into recovery mode via the 3 button mode
--a.turn off phone
--b.pull out the battery
--c.press the volume up + volume + power button down and keep holding
--d.insert battery
--e.**deleted my bad got ahead of myself
--f.wait for it to to turn on at this point u can let go of the power button - keep holding the volume buttons
--g.once u see the yellow text u can let go of all the buttons and it'll put u into recovery mode
2-see if u can get into download mode via the usb cable method
--a.power off phone
--b.remove battery
--c.plug in the micro usb cable into a computer that is on
--d.press and hold the volume up and down buttons
--d.plug in phone to micro usb while holding the volume buttons
--e.insert your battery while holding volume buttons
--f.wait for a few seconds then viola you should see the android dude with a shovel digging
Sent from my SGH-T959 using Tapatalk
ipetloudog said:
my fav method.
Check usb debugging and unknown sources in settings
Go to 4shared.com and dl z4root.
Root.
Simple.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
z4root doesn't work on the ota froyo rom from kies - you have to use the modded 3e update, SuperOneClick, or aio vibrant toolbox - least not when i last tried it anyways...
easiest way to root from 2.2 is to go back to 2.1 from odin and use the update package root method. If u cant root with the 2.1 method of installing the update package, i cant help u.....no need to be on 2.2 stock as ur gonna put on a rom anyway so it doesnt matter wht stock u have on.
superoneclick 1.9
shortfuse.org
Update.zip does not work
SamsungVibrant said:
Everything you need to know should be right here:
http://forum.xda-developers.com/showthread.php?t=849028
In the early days of Vibrant, you could easily root via update.zip. Then that stopped working, I think because of the 3e recovery. Anyway, I just use one of the already rooted ROMS like the deodexed and rooted KB5 found in the development section.
But update.zip should still work for you if you are running an older stock vibrant rom.
.
Click to expand...
Click to collapse
Update.zip did not work. I have a Samsung Vibrant purchased in 2010 w/Froyo. I am a newbie and am trying to root the phone in order to back it up using Titanium and then do a factory reset because the phone has slowly become unusable. I still don't know how to root the darn phone. Still reading forum after forum. Anyway, my two cents was that file doesn't work.
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
my phone got bricked the first time when i was trying to update the rom from SlimBean 4.2.2 Build 7 to Build 8 (had done the process many times and never had a problem) did the usual, put the Rom and the Gapps .rar files in the sd card and performed wipe data/ factory reset only this time i went into mounts and storage and wiped everything that was under there as well (dont know why) so when went to flash the rom it was no longer on the sd card (cause i wiped it) so rebooted my phone and it got stuck on the vibrant screen with i fixed already and my problem now is the one mentioned above
i have browsed the different forums and have tried many different methods to try to fix it for example: have brought it back to stock with Odin also with AIO Vibrant Toolbox and even tried UVKB5_Stock_Heimdall-One-Click wich is a froyo 2.2 that comes with CWM recovery with voodoo lag fix and root. even though all these methods work as far as bringing the phone back to stock i still get the same problem when trying to flash a rom, i also have installed CWM through Rom manager and also through the update.zip file i think im doing everything right and have tried multiple forums yet havent been able to find a forum about this specific issue so decided to create this thread as a last resource
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
This worked for me
elpromo01 said:
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
Click to expand...
Click to collapse
Mine would remove the root when I rebooted it not allowing me to install a rom also. I used the Super One Click and the root stuck. I suggest you give it a try.
Super One Click
seerenr since
Devil-Dog said:
Mine would remove the root when I rebooted it not allowing me to install a rom also. I used the Super One Click and the root stuck. I suggest you give it a try.
Super One Click
Click to expand...
Click to collapse
my problem is not really with rooting the phone, it is rooted i just cant flash roms. whenever i try to flash a rom it reboots and gets stuck on the vibrant screen (bricked) so i have to take it back to stock
thanks though
elpromo01 said:
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
my phone got bricked the first time when i was trying to update the rom from SlimBean 4.2.2 Build 7 to Build 8 (had done the process many times and never had a problem) did the usual, put the Rom and the Gapps .rar files in the sd card and performed wipe data/ factory reset only this time i went into mounts and storage and wiped everything that was under there as well (dont know why) so when went to flash the rom it was no longer on the sd card (cause i wiped it) so rebooted my phone and it got stuck on the vibrant screen with i fixed already and my problem now is the one mentioned above
i have browsed the different forums and have tried many different methods to try to fix it for example: have brought it back to stock with Odin also with AIO Vibrant Toolbox and even tried UVKB5_Stock_Heimdall-One-Click wich is a froyo 2.2 that comes with CWM recovery with voodoo lag fix and root. even though all these methods work as far as bringing the phone back to stock i still get the same problem when trying to flash a rom, i also have installed CWM through Rom manager and also through the update.zip file i think im doing everything right and have tried multiple forums yet havent been able to find a forum about this specific issue so decided to create this thread as a last resource
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
Click to expand...
Click to collapse
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
firefly6240 said:
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
Click to expand...
Click to collapse
i have re-flashed recovery multiple times i wish there was another type of recovery i could install
on another note im trying to install android 4.2.2 SlimBean and 4.3.3 and i dont know what bootloader i have nor how to check it, id appreciate it if u could show me how to check wich one i have and how to up it
thanks
firefly6240 said:
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
Click to expand...
Click to collapse
the combo i have to do for recovery is volume up and down and the power button simultaniosly
elpromo01 said:
the combo i have to do for recovery is volume up and down and the power button simultaniosly
Click to expand...
Click to collapse
Try flashing a 2.2 rom or below.
if that works you probably just need to flash GB bootloaders before flashing the 4.2 rom (See Below)
if that doesn't work I wouldn't worry about the step below until we figure out why its not working.
To flash GB bootloaders go here: http://forum.xda-developers.com/showthread.php?t=1117990
firefly6240 said:
Try flashing a 2.2 rom or below.
if that works you probably just need to flash GB bootloaders before flashing the 4.2 rom (See Below)
if that doesn't work I wouldn't worry about the step below until we figure out why its not working.
To flash GB bootloaders go here: http://forum.xda-developers.com/showthread.php?t=1117990
Click to expand...
Click to collapse
ok so i installed GB bootloader following the instructiones as shown in the forum, went ahead an tried to flash Slimbean 4.2.2 build 8 and the same thing happened my phone is stock at the boot screen only different is that instead of the vibrant screen im getting a semaphore screen (i guess is because of the gb bootloader) anyway flashed back to stock using Odin and im back where i started so it doesnt seem to be a bootloader related issue
thanks anyway
elpromo01 said:
ok so i installed GB bootloader following the instructiones as shown in the forum, went ahead an tried to flash Slimbean 4.2.2 build 8 and the same thing happened my phone is stock at the boot screen only different is that instead of the vibrant screen im getting a semaphore screen (i guess is because of the gb bootloader) anyway flashed back to stock using Odin and im back where i started so it doesnt seem to be a bootloader related issue
thanks anyway
Click to expand...
Click to collapse
Flash the rom again instead of going back to stock when it hangs. You have to flash JB roms twice most of the time when you are on stock 2.1, the first flash simply upgrades your recovery mode. Pull the battery after the first flash and boot back into recovery (should be blue now) and flash the rom again.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Flash the rom again instead of going back to stock when it hangs. You have to flash JB roms twice most of the time when you are on stock 2.1, the first flash simply upgrades your recovery mode. Pull the battery after the first flash and boot back into recovery (should be blue now) and flash the rom again.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
i just fixed, i tried to flash CM10.1 and it crashed during the process only this time instead of getting stuck on the Vibrant screen it rebooted back into the recovery mode wich is now blue and version 6.0.2.1 intead of 2.5.1.2.
im running CM10.1 right now and so far everything looks good :laugh: only thing different now is that it say Galaxy S GT-I9000 and is the t959, doesnt really bother me as long as the phone behaves im just sayin
thanks to everyone that took their time to help, never give up on a Vibrant cause it will never give up on you :good:
elpromo01 said:
i just fixed, i tried to flash CM10.1 and it crashed during the process only this time instead of getting stuck on the Vibrant screen it rebooted back into the recovery mode wich is now blue and version 6.0.2.1 intead of 2.5.1.2.
im running CM10.1 right now and so far everything looks good :laugh: only thing different now is that it say Galaxy S GT-I9000 and is the t959, doesnt really bother me as long as the phone behaves im just sayin
thanks to everyone that took their time to help, never give up on a Vibrant cause it will never give up on you :good:
Click to expand...
Click to collapse
Glad you figured it out. Just so you you know, your phone says GT-I9000 because you flashed gingerbread bootloaders. They provide better button combinations to recovery and download modes, much easier than stock combos.
Sent from my SGH-T959 using Tapatalk 2
Good to know, thanks!!
Sent from my SGH-T959 using xda app-developers app