Related
Okay. So I pushed Axura final onto my phones internal sd card and booted into recovery mode. The damned Axura copy ( it downloaded properly via google chrome, no errors) had some issue with it and DID NOT install properly. I tried again and again to make it work, did not load flash from voodoo eclair 2.1 to axura which is 2.2.
Now I want to use ODIN and come back.
I get into download mode BEAUTIFULLY using youtubes """Samsung Vibrant download mode; Corntez" .
and then load Odin, load pit file, and the tar/jar file. detected as COM 6 Odin says "added" . then run it. RUNS perfectly. firmware update start; cache.rfs;modem.bin;factoryfs.rfs; and all, and the blue bar finished completely.
Then restarts, "VIBRANT" says "data wiping failed " , everything else succeeds...lots of small writing....restart' VIBRANT" ; then Samsung Galaxy S shiny logo.
Now.....the plot thickens and my vibrant does not move forward. Black, black screen.
If I touch the bottom touch keys---viz, home etc...they light up fine. But the screen. the beautiful screen, remains as dark as Lord Voldemorts heart.
What to do??
I forgot to mention that I moved from a forward port on my thinkpad to an aft port )); and the COM4 in ODIN changed to COM 6 , promptly.
Odin is causing some issues. seems like. Any suggestions and links for newer, better versions of the T mobile stock firmware.????
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
houston123 said:
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
Click to expand...
Click to collapse
Houston we have a problem. Voodoo MUST be disabled BEFORE you flash. There are plenty of info on the board on how to do this. Then ODIN to stock then FLASH. Not all ROM's need a lag fix, some just run smooth!
my phone is doing the same thing but all i did was hit the voodoo button that was available in the oclf app and it went dumb the women counted down and said complete after a while and then it stuck on the vibrant samsung screen. i flash with stock rom and now its doing what this guys phone is doing please help us
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
houston123 said:
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
Click to expand...
Click to collapse
For the dear love of [deity]/self-sufficiency, go read how to solve your problem
(You need to flash Eugene's "froyo that does not brick." Then flash whichever firmware you want.)
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
houston123 said:
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs
I have tried but doesn't work for me. Unfortunatly I too did not disable voodoo before flashing and now I am stuck and can not get into download screen. I guess I will have to take my stuff to a cell phone repair since I have ran out of options.
got eugenes software. Now I am going to try out this:
""""
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!"""
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
houston123 said:
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
Click to expand...
Click to collapse
My opinion on this is not to worry unless it doesn't work. But since you know how to use Odin and your phone can get into download mode okay, it should work.
With the insurance there is a hefty copay. But you should be fine.
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
Ok, I was restoring my phone to stock with odin following these stpes
Disable Voodoo
Odin to eugenes froyo that wont brick
sticks at vibrant screen
tried odining to JFD
odin completes but still hangs at the vibrant screen
I have tried with and with out repartition checked and I am able to enter and exit download mode freely, I have tried 3 differnt versions of odin and 2 different downloads of the pda and pits. Any help would be great.
EDIT, Odin is finishing at the pass stage when the phone attempts to boot Currently flashing the JI6 seeing if it works.
Still not getting anywhere, I have now tried to odin to eugenes froyo, JFD, JI6, all which end the same with out a boot screen, I can get download but no recovery.
From my understanding when you flash eugenes froyo that wont brick the boot animation should change to the international one, mine has not done that so I am starting to wonder if there is an issue with the flashes themself.
How long did you wait after flashing the stock firmware? The first boot usually takes a while after an Odin. Did Odin finish flashing everything to the point that it said restart in blue?
You can find instructions to revert to stock http://forum.xda-developers.com/showthread.php?t=734475
I've gotten myself out of some pretty bad "bricks" with JFD and ODIN... make sure you also use the stock .pit file and you can check repartition, use JFD and should fix you right up.
I have waited for 10-15 minutes after it says restart and then sometimes after it says pass, and I have done to jfd and stock pit.
left phone at boot fell asleep woke up hr or so later still at vibrant screen, still cannot access recovery but can access download mode.
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
iynfynity said:
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
Click to expand...
Click to collapse
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
ionic7 said:
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
Click to expand...
Click to collapse
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
iynfynity said:
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
Click to expand...
Click to collapse
Yes read the first post it says what i have flashed.
Charlie Brown said:
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
Click to expand...
Click to collapse
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
ionic7 said:
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
Click to expand...
Click to collapse
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
ionic7 said:
Yes read the first post it says what i have flashed.
Click to expand...
Click to collapse
try that again.
Sent from my SGH-T959 using XDA App
Im having the same issue with, "Data Wipe Failed" and have 0.00 space in Application storage but my phone reboots into eugenes 2.2 perfectly fine and works, but the application storage seems to be empty still...very frustrating.
cvibe88 said:
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
Click to expand...
Click to collapse
have changed usb cord, port, computer, have flashed jfd ji6 froyo that wont brick, 512 pit,513 pit,and they have not laughed at me in anyway they are sending my new phone now and a g2 to try out soo either way I have something soon. I also was going from axura to stock to a custom rom not from one to the other and I do know how to use odin, I know what I am doing just need help figuring this one out has to be something im missing or its just not gonna work. 50 odins and nothing kinda says it all.
I am in the same boat.. tried ODIN + stock ROM from various sources, nothing seems to work.. am I out of luck ??
My phone was working fine after installing the DOW14 kernel yesterday. This morning it was even working fine. Even my alarm went off this morning on the phone and I set it an hour ahead (for more sleep) and it didn't go off. I looked at my phone and the screen would not come on. The "buttons" at the bottom lit up, but nothing I had to hold the power button down to get it to reboot.
It got past the "Vibrant" text and shows the green robot for TeamWhiskey, but just sits there. Tried taking the battery out and still it will boot to the same place. Can anyone help?
I did not overclock, I never ran SetCPU.
If you can get it to download mode, try flashing another kernel through odin since you cant see anything. Just the kernel not a rom. Supercurio has some voodoo kernels for odin in the dev section. Just look for your base and odin the corresponding kernel. Goes in PDA. Dunno if there are any "stock" odin kernels or not.
jmcghee1973 said:
If you can get it to download mode, try flashing another kernel through odin since you cant see anything. Just the kernel not a rom. Supercurio has some voodoo kernels for odin in the dev section. Just look for your base and odin the corresponding kernel. Goes in PDA. Dunno if there are any "stock" odin kernels or not.
Click to expand...
Click to collapse
Hold vol up + down + power right? I can't seem to get into recovery/download mode. I am downloading Bay_wolf's AIO Vibrant Toolbox 2.5 right now.
raulcota said:
Hold vol up + down + power right? I can't seem to get into recovery/download mode. I am downloading Bay_wolf's AIO Vibrant Toolbox 2.5 right now.
Click to expand...
Click to collapse
Watch this video to get to download mode http://www.youtube.com/watch?v=D0aoabVtPJ8&feature=youtube_gdata_player
Sent from my SGH-T959 using XDA App
I had a similar issue and crazy enough, it worked. Then I just odined back to stock then rooted and flashing all over again
Sent from my SGH-T959 using XDA App
I can get it to reboot using adb reboot recovery, but it never actually boots into recovery still sticks at the teamwhiskey robot chick screen, lame
raulcota said:
I can get it to reboot using adb reboot recovery, but it never actually boots into recovery still sticks at the teamwhiskey robot chick screen, lame
Click to expand...
Click to collapse
not recovery...download mode w/the digging robot on the screen.. I'm not familiar with adb does it adb reboot download or anything of that nature?
Try this, it worked for me. Pop your battery, put it back in, hold vol up down and power. Wait for vibrant to pop up the second time and release. Should put you in recovery. Factory data reset, reflash you rom, wipe dalvik and fix permissions, then reboot. I had the same issue with the Bionix 1.2.1 update and the glasstopia theme w/ dragon 4. They didnt play well together. Hope this helps.
you may want to build a jig or buy one online in the future just in case you cannot get into the download mode.
http://cgi.ebay.com/ws/eBayISAPI.dl...25272&ssPageName=STRK:MESELX:IT#ht_595wt_1139
OK, I can get into download mode and I have been trying this method with no success:
http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Odin flashes the phone and it just comes back and reboots again. Man this sucks
I am wondering if there is a full flash file somewhere I found one Fascinate, but I am afraid to flash my Vibrant with it.
http://forum.xda-developers.com/showthread.php?t=867648 that is the fascinate one
Several people are having this problem including me... I worked on it all day yesterday. No matter what you odin, even eugenes no brick fix then JFD, nothing will work. I hate to tell you but your phone is toast.
Sent from my MB200 using Tapatalk
I agree man.
I've looked at every single thread with this same exact issue.
No avail. The file system, the ones that are reserved and locked for the bootloader and ROM are corrupted, is my guess.
I can load all the roms on there, but something isn't loading correctly, or is beyond corrupted, not allowing me to boot the phone at all.
My phone is toast too.
Damn, im not happy.
Nobody has a fix for this though. Nobody.
Anyway, sorry to hear about your phone. Mine is also bricked completely.
Keep in mind, this is from somebody who has bricked every possible way (apparently not this way), and ODIN at least once a week. I've also used Eugene's i9000 OC kernels, old DOW OC kernels, and TTBAL's OC kernel with NO PROBLEMS AT ALL!!! 1.4gHz stable.
Now this.
WTF Mate.
drewdude007 said:
Several people are having this problem including me... I worked on it all day yesterday. No matter what you odin, even eugenes no brick fix then JFD, nothing will work. I hate to tell you but your phone is toast.
Sent from my MB200 using Tapatalk
Click to expand...
Click to collapse
I see that in the DoW 14 thread now. I am not giving up yet, but that is discouraging.
Unbrick me!!!
ive bricked my phone before and ive used odin to get my phone running again but this time its diffrent it wont go into download mode it just keeps blinking at the VIBRANT samsung screen and when i connect it to my computer the battery loop turns on and if i let go of the buttons that take me to download mode it just goes back to flashing vibrant IM SCARED someone plz help!
posted by team whiskey
"Optional Kernels:
Optional kernels will be uploaded and posted when I get home.
They will include a Modded DOW and Modded Dragon to allow for mounting Internal SD. Do Not flash the current DOW/Dragon kernels or you will loose mounting functionality."
my girls phone is shot and i took the dow off mine real quick
no more oc for me thanks sold my bricked phone on ebay for 150$
maybe that will help for people to recover the loss a bit?
good luck i tried for days.
Still Broken...
Anyone ever get this fixed? I still have a broken phone
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
what rom are you running? did you check to see if it was even compatible with the kernel your flashing? I mean.... are you on gingerbread roms or froyo?
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