Related
Ok, here it goes: I have tried searching for the answer, and haven't quite found the answer that pertains to my situation. I recently flashed Obsidian on my Vibrant and decided to revert back to my backed up stock rom using ClockworkMod Recovery app. My phone then failed to boot past the Vibrant/Samsung screen. I have tried to get into recovery, but the phone only stays on Vibrant/Samsung screen and fails to go to recovery screen. No matter what method is tried to get to recovery, the phone gets stuck on the Vibrant/Samsung screen and will not boot past that or go to recovery. This being said, my question is: When my phone goes back to T-Mobile for warranty, will they be able to tell if its rooted if it doesn't boot and can't get to recovery? Or will they just do their thing and reflash the stock rom thus wiping any evidence?
BULLITT3200 said:
Ok, here it goes: I have tried searching for the answer, and haven't quite found the answer that pertains to my situation. I recently flashed Obsidian on my Vibrant and decided to revert back to my backed up stock rom using ClockworkMod Recovery app. My phone then failed to boot past the Vibrant/Samsung screen. I have tried to get into recovery, but the phone only stays on Vibrant/Samsung screen and fails to go to recovery screen. No matter what method is tried to get to recovery, the phone gets stuck on the Vibrant/Samsung screen and will not boot past that or go to recovery. This being said, my question is: When my phone goes back to T-Mobile for warranty, will they be able to tell if its rooted if it doesn't boot and can't get to recovery? Or will they just do their thing and reflash the stock rom thus wiping any evidence?
Click to expand...
Click to collapse
Another person trying to scam a company..
That being said, It is a 50/50 chance of them knowing, and I hope they do know.
Why dont you odin back to stock and not claim a warranty exchange for something that is your own fault
Sent from my SGH-T959 using XDA App
Go to the Vibrant android development section and look for the vibrant bible.
once there read up on using ODIN.
USE IT.
Than put down the phone and never flash a rom again until you learn to read directions.
oh and by the way, how bout you NOT try and scam ppl cuz you cant follow simple directions. going to tmobile and filing a claim is BS. YOU are the one responsible for your phone no longer working. Ppl wonder why prices on data plans and other costs go up. They have to keep paying out the ass on other crap that could easily have been avoided had the end user had any durn sense
BULLITT3200 said:
Ok, here it goes: I have tried searching for the answer, and haven't quite found the answer that pertains to my situation. I recently flashed Obsidian on my Vibrant and decided to revert back to my backed up stock rom using ClockworkMod Recovery app. My phone then failed to boot past the Vibrant/Samsung screen. I have tried to get into recovery, but the phone only stays on Vibrant/Samsung screen and fails to go to recovery screen. No matter what method is tried to get to recovery, the phone gets stuck on the Vibrant/Samsung screen and will not boot past that or go to recovery. This being said, my question is: When my phone goes back to T-Mobile for warranty, will they be able to tell if its rooted if it doesn't boot and can't get to recovery? Or will they just do their thing and reflash the stock rom thus wiping any evidence?
Click to expand...
Click to collapse
Can people ever take responsibility for their acts? The warnings posted on all the ROM threads are there for a reason. If you cannot bring your phone back to live with the information available online including these forums just suck it up, be a man.
I know I should take resposibilty for my own actions, but when a phone is supposed to be able to boot into recovery by using the 3-button method, but that method isn't funtioning because Samsung disabled it (like many other people have experienced) how do I take responsibilty for equipment that doesn't do what its supposed to? When the phone doesn't boot into recovery like it is supposed to, how do I fix my own actions. My brick is partly my fault and I know that, but partly a faulty phone.
BULLITT3200 said:
I know I should take resposibilty for my own actions, but when a phone is supposed to be able to boot into recovery by using the 3-button method, but that method isn't funtioning because Samsung disabled it (like many other people have experienced) how do I take responsibilty for equipment that doesn't do what its supposed to? When the phone doesn't boot into recovery like it is supposed to, how do I fix my own actions. My brick is partly my fault and I know that, but partly a faulty phone.
Click to expand...
Click to collapse
Not at all! They released a fix for that (JI6)
You were the one who bricked your phone & are trying to scam T-Mobile.
Adb into download mode, use odin, flash to stock
Sent from my SGH-T959 using XDA App
Master™ said:
Not at all! They released a fix for that (JI6)
You were the one who bricked your phone & are trying to scam T-Mobile.
Click to expand...
Click to collapse
So if J16 was supposed to fix that, why was it that even T-Mobile couldn't get it to boot into recovery?
BULLITT3200 said:
So if J16 was supposed to fix that, why was it that even T-Mobile couldn't get it to boot into recovery?
Click to expand...
Click to collapse
Ok, first off, you bricked it because JK2 and JI6 or any 2.1 version run on different kernels, and clockwork doesnt install kernels (and this is why you can't go into recovery, not because the phone is faulty.). I did this before and ODIN will fix it right up. Use it.
It will only take about an hour to get everything back the way you want rather than waiting a week or so. No need to file a warranty complaint, this is your fault but very easy to fix.
BULLITT3200 said:
So if J16 was supposed to fix that, why was it that even T-Mobile couldn't get it to boot into recovery?
Click to expand...
Click to collapse
Because YOU modified your phone, and messed up!
Odin will fix one of your problems. The other can't be fixed...
recovery won't do you any good because it needs the kernel to load.
you need download mode.
with the phone completely off and not connected to the computer, press and hold the vol + and vol - buttons at the same time. then plug in the usb and you'll boot into download mod.
You then go about flashing w/ odin to get your phone working again.
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?
I sold my friend my Samsung Vibrant and I've never had any problems flashing it, he tried flashing the cyanogenmod rom (tried being the operative word...) and I'm not sure what he did to but when I try to turn it on its has the I9000 boot screen and it goes to the vibrant splash screen and turns off, if it's plugged it gets to the vibrant screen and then has the cycle icon for the battery then it shows the battery and it infinitely loops like this when its plugged in (when I had it, it would be completely dead and I could plug it in and turn it on at the same time and it would boot fine and didn't die). I tried flashing JI6 via ODIN, which seemed to flash correctly (gets to zImage and says removed and then pass), but nothings changed (still I9000 boot screen and still crashes on splash screen with battery loop). Any idea what I can do to fix this?
I think your friend flashed the I900 Version of the Rom. Try odin-ing to stock.
EDIT: You already odin-ed JI6. Try odining to stock JFD with both pit and tar files. That should restore everything (bootloader, kernel, baseband, etc...)
its shows i9000 on boot with the GB bootloaders
http://forum.xda-developers.com/showthread.php?t=849028 have a read through there
if you do have the GB bootloaders its vol up and power for download mode
odin to stock will fix it
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
the jfd.tar doesnt have the bootloaders i dont think so you'll still be on GB bootloaders on 2.1, they're backwards compatible anyway so it doesnt matter
demetris_I said:
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
Click to expand...
Click to collapse
I've tried to get into recovery mode for this but I can only get into download mode (tried VOLUP+HOME+POWER (and without home) boots to download mode, tried VOLDOWN+HOME+POWER (and without home) and it does nothing, I've tried to use adb on the download screen but it doesn't find the device). Is there another method that I'm missing?
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
demetris_I said:
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Click to expand...
Click to collapse
Sorry about that, my bad. But I tried just tried that, and when I flashed the Froyo file it booted to recovery (like it sounds like it should have, still with GB bootloader and reversed controls on recovery and not able select since vibrant doesn't have an ok button) and then flashed JFD with the pit and repartition selected and it goes back to turning off after the vibrant screen. I tried redownloading both froyo and JFD thinking one might be corrupt and I still get the same result as before. I've checked the instructions 10+ times and I've used odin for the life of this phone more times than I have counted, and I can't figure out why it doesn't seem to be taking it, it doesn't fail in odin so it doesn't make sense.
After doing what i recommended your phone would be in fully functioning order.
Your problem lies on the bootloader so i would recommend to flash froyo bootloader from here:
http://forum.xda-developers.com/showthread.php?t=1117990
but before md5 check the downloaded file and follow exactly the guide there.
If this dont fix it then i think your phone is a pita.
I kinda agree that its probably just the Bootloaders that is the culprit for the I9000 splash. As mentioned flashing the original FROYO should fix it. At least it did for me. I had to do both these links in the GB bootloader thread for it to take though. 1st one 1st - then either of the 2nd links 2nd.
adyscorpius said:
jfd odin file - for use after installing gingerbread bootloaders
http://www.multiupload.com/hryjkflkfq "thanks to laylovj"
md5: 977e2136996e7138945447a8245d6776
if you have gingerbread bootloaders installed and you end up odining to stock (jfd), you will notice it changes the bootsplash to i9000. You can either reflash a gb bootloader again, or simply use the odin package above to do so.
vibrant stock (froyo) bootloader download link
- dropbox download link
- mediafire download link
md5 sum - 754ecbd8e76d4f81bec49240031f3262
Click to expand...
Click to collapse
Now as far as ODIN. The yellow triangle and android dude digging should be there throughout the entire ODIN flash. If I understand you correctly and the phone goes black during the ODIN flashthats no good. If its doing it after the ODIN flash, then maybe you still have the "reboot after flash" button ticked. Either way the phone needs to stay in download mode during the entire ODIN flash.
*EDIT*
- If all else fails JTAG! but that should be the last option. There is a fix!
- BUY A USBJIG you can get them from either TeamWhiskey or EDT on their sites. If everyone had one we would never see another
"NO DOWNLOAD MODE!!! HELP" thread again. And at the same time you'd be supporting developers which is a good thing.
Good luck!
You should try the "froyo that does not brick" in the early days of froyo eugene released a froyo package that came with bootloaders. Google ftdnb, it may also be in either bricked or eb's threads
Beware of angry gingerbread man
I was trying to go from my current ROM Perception v1-RC1 back to UnNamed v2.21 and got stuck in a clockwork mod recovery loop.
None of the blue menu options work, they just go to the CWM icon. All I can do is power off my phone and it just boots back to the same place.
I did get to the ODEN option somehow at one point but haven’t been able to get back…(screen I came to when I first rooted.)
I have switched from ROM to Rom in the past but never had this issue. Yes I’m a noob and I have been searching for the answer and did find exitrecovery.zip recommended for other devices but not a SGS2 and don’t want to do any more harm. Also it sounds like those people have their CWM menu working in some fashion but just couldn’t reboot. Should I go back to ODEN and start from scratch like I am re-rooting? ANY help would be great. (Walk through, point me in the right direction, anything.)
Thanks
KC37
Here is my info (what I can get)
Phone: AT&T Galaxy S2
CWM: Recover Version 5.0.2.3
Kernel: (Whatever came with Perception v1-RC1)
(If you can tell me how to get more info that could help let me know)
**Update**
when "trying" to turn the phone off it goes to a battery icon and back to CWM. I can't get back to ODEN reader mode ( Vol Down+power)
Ancient kernels use home/back instead of power.
Yeah, I was dumb and back to the Odin mode...I thought I would start from scratch so I flashed the .tar file I started with a while back: SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar
Passed in Oden, good right?
Reboot went right back to CWM loop...
Am I looking to redo everything? Phone DPA ect? 100% new firmware?
Entropy512 said:
Ancient kernels use home/back instead of power.
Click to expand...
Click to collapse
Like entropy said you use the home key to make your cwm selection. Also to get into download mode your phone needs to be unplugged , then you hold power + volume down and plug it in to usb.
Sent from my SGH-I777 using xda premium
Correction on my last post its just volume down and plug it in. No power button.
Sent from my SGH-I777 using xda premium
FIXED!!!!!
flashed SiyahKernel v2.6.14 in ODEN on a whim and I'm back!
Zedo's kernel is also ancient - definitely does not work with UCKK6, and probably doesn't have the fixed recovery keymap either.
I just use the pre rooted stock odin roms in Dev section and return the device to stock (No BL). Then flash CWM. Saves a lot of headache when jumping different roms.
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