another ji6 problem please help - Vibrant Q&A, Help & Troubleshooting

I flashed the accurate battery mod with the ji6 update and now it won't boot. I'm stuck in force closes during the boot process. I downloaded the stock battery file to my pc, but can't figure out how to get it on the sd card. currently I am able to boot into recovery mode, but it won't let me access my files to put the stock battery zip back on the phone. Can someone please help me with this

jstein222 said:
I flashed the accurate battery mod with the ji6 update and now it won't boot. I'm stuck in force closes during the boot process. I downloaded the stock battery file to my pc, but can't figure out how to get it on the sd card. currently I am able to boot into recovery mode, but it won't let me access my files to put the stock battery zip back on the phone. Can someone please help me with this
Click to expand...
Click to collapse
should have read to see if it's compatible with JI6 before flashing
you need to flash back to stock with Odin

flash froyo from euguene that won't brick with odin then downgrade to ji6 i suggest you after you downgrade flash bionix 1.7 with ji2 modem is the best rom and fastest out there

Intel_x said:
flash froyo from euguene that won't brick with odin then downgrade to ji6 i suggest you after you downgrade flash bionix 1.7 with ji2 modem is the best rom and fastest out there
Click to expand...
Click to collapse
why?
just reflash JI6 with Odin
problem fixed
his framework file is ****ed up, that's it

hydrogenman said:
should have read to see if it's compatible with JI6 before flashing
you need to flash back to stock with Odin
Click to expand...
Click to collapse
I was told in another thread that it should work. Do I need to flash back to stock, couldn't I just put the stock battery back on to essentially undo what I did?

hydrogenman said:
why?
just reflash JI6 with Odin
problem fixed
his framework file is ****ed up, that's it
Click to expand...
Click to collapse
That worked! thanks for the help

Re-Boot to "Recovery Mode" and "Wipe" Menu 3, 4
then reboot the phone again. It's work for me.

Please post questions in the Q&A forum or as part of the thread in which you found the item that caused the problem. This keeps the development forum from getting crowded.
Thread moved.
As far as modifications to the themes or anything else related to the framework, they tend to be VERY framework specific and frameworks change on each ROM version.

Related

[Q] Flashed Stock Firmware via ODIN

So i unrooted my phone. And flashed true stock firmware for the vibrant via ODIN, it said PASS,and completed at the bottom.But now all it shows is a black screen. It loads up normal, passes the vibrant screen, after that its just a black screen. Any suggestions on how to fix this? also when it boots into recovery it says ''DATA WIPE FAILED''
I would like to ask what stock rom or nanroid did you flash? Was it original stock and what pit file in odin?
Yea, i found out i flashed over Bionix rom & didn't disable VOODOO lag fix..So i searched a bit more after posting and found the problem..
Flash the froyo rom through odin then flash back to stock. That will fix your issue.
^^^ to be more specific flash "eugene's froyo that doesn't brick" ROM, then the true stock.
esebrown23 said:
Yea, i found out i flashed over Bionix rom & didn't disable VOODOO lag fix..So i searched a bit more after posting and found the problem..
Click to expand...
Click to collapse
Hey, i'm experiencing the same exact problem.
can you please share your wisdom with details?
thx

Anyone know of a custom ROM....

That can be flashed through Odin?
Im unable to flash any ROMs through CWM or through recovery since I have a problem with the SD card (had this problem after flashing a stock Froyo ROM) also after doing this I cant get into recovery or download through the 3 button combo, used to be able to do it but cant anymore for some reason (I think its also because of the Froyo flash), I have CWM installed and every time I try to flash any ROM it gives me an E:Error cache/sd (Status 2)
I havent been able to fix this issue, so I thought of trying to work around it, I am able to get into download mode using ADB, so I was hoping to find a custom ROM that can be done through Odin, by trying a new custom ROM Im hoping to get rid of my SD card issue (card says its write protected but its not)
Your best bet would be to odin back to stock and go from there. Start back off with a clean slate and be able to use ClockworkMod. Just check the stickies for the proper procedures.
Oh, and just for reference, you are putting the .zip ROM file on the root of you internal memory? If not, try that with ClockworkMod again and see what happens.
Sent from Andromeda Galaxy!
I would have to second the Odin back to stock recommendation as well.
Last thing you want to do is soft brick the phone while it's hardware locked. That's a recipe for hard brick if I ever saw one.
offdutyninja808 said:
Your best bet would be to odin back to stock and go from there. Start back off with a clean slate and be able to use ClockworkMod. Just check the stickies for the proper procedures.
Oh, and just for reference, you are putting the .zip ROM file on the root of you internal memory? If not, try that with ClockworkMod again and see what happens.
Sent from Andromeda Galaxy!
Click to expand...
Click to collapse
Ok thanks for the advice, ya I had it in the root of my internal SD card
Drewstein said:
I would have to second the Odin back to stock recommendation as well.
Last thing you want to do is soft brick the phone while it's hardware locked. That's a recipe for hard brick if I ever saw one.
Click to expand...
Click to collapse
When you guys say stock... do you mean back to stock 2.1 or 2.2?
All my issues have started from flashing a stock 2.2 ROM
Do you guys have a link to a stable stock ROM?
I think I still have the stock ROM that I flashed but Id rather not use that one
Thanks for the help guys
DT3CH said:
Ok thanks for the advice, ya I had it in the root of my internal SD card
When you guys say stock... do you mean back to stock 2.1 or 2.2?
All my issues have started from flashing a stock 2.2 ROM
Do you guys have a link to a stable stock ROM?
I think I still have the stock ROM that I flashed but Id rather not use that one
Thanks for the help guys
Click to expand...
Click to collapse
I am referring to stock 2.1. All the Froyo builds are unofficial. Just do a search in the vibrant Android dev section for JFD. That is the latest official Rom, which 2.1.
Sent from Andromeda!

[Q] Stuck at vibrant screen after odin

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 ??

need help quick cant figure out what is wrong?

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

Can't Flash any Rom

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

Categories

Resources