OK, so just yesterday, I realized that for some reason, I cannot play any videos on my Vibrant. This includes both videos I have put on my phone as well as those I have taken with my camera.
I am running Bionix 1.3 ROM. I searched but didn't find anything. I have not had this issue before. Any help is appreciated.
Reflash,I suggest odin to stock and reflash or try just flashing the new vrs of the overstock kernal.
Carl
carlcj5 said:
Reflash,I suggest odin to stock and reflash or try just flashing the new vrs of the overstock kernal.
Carl
Click to expand...
Click to collapse
Agree flash back to stock, then reflash best way
Thanks
OK. I've never used Odin before. To be honest, I'm a bit intimidated. Would you suggest using that AIO Vibrant Toolbox to do it?
cccheel said:
OK. I've never used Odin before. To be honest, I'm a bit intimidated. Would you suggest using that AIO Vibrant Toolbox to do it?
Click to expand...
Click to collapse
toolbox is very simple and straight forward
cccheel said:
OK. I've never used Odin before. To be honest, I'm a bit intimidated. Would you suggest using that AIO Vibrant Toolbox to do it?
Click to expand...
Click to collapse
Don't be afraid of Odin....
true: you can screw up if you use the wrong files or disconnect before it finishes...but if used correctly Odin can be your Vibrant's best friend...
EDIT: I've been having that same problem since KB1.....might be a DRM issue pointed out by Br1ck'd in my thread here:
http://forum.xda-developers.com/showthread.php?t=961841
Yea, but the thing is, it's not just DRM files - it's any video file.
Fixed
Just rebooted, and it seems to be fixed...hm... Thanks anyways, guys.
cccheel said:
Just rebooted, and it seems to be fixed...hm... Thanks anyways, guys.
Click to expand...
Click to collapse
but it comes back after some time. yes when you do a reboot it goes away but i after some time it comes back then you have to do reboot again i don't want to do that. why does it keep on doing it in first place. any ideas?
Try a 2.2.1 rom
Sent from my T959 using XDA App
This happens no matter what if you haven't rebooted in a while. My buddy on his completely stock KA6 was complaining about it all the time, just reboot at least once a day and you will be fine. No Rom will fix this issue that I am aware of but to be honest I have NEVER had this problem by always doing the before mentioned fix.
Related
Hey guys, figured i would test out a semi-cleaned up rom for yall to flash. This is nothing too fancy, just removed most of the bloat from the /system.
Go here for the download: http://dl.dropbox.com/u/458252/Angel-i500-VZW-semiclean.tar.md5
install with odin, follow instructions in this post: http://forum.xda-developers.com/showthread.php?t=782204
I AM NOT RESPONSIBLE FOR WHAT YOU FLASH TO YOUR PHONE! YOU FLASH THIS KNOWING THAT IT COULD VERY WELL BRICK YOUR PHONE!
Now with Yahoo instead of Bing.. right?
namebrandon said:
Now with Yahoo instead of Bing.. right?
Click to expand...
Click to collapse
I thought we decided on using altavista?
fallingup said:
I thought we decided on using altavista?
Click to expand...
Click to collapse
That's right, I remember now. Altavista w/ Mosaic Mini.
i wont install unless theres an ask jeeves widget ; )
illtema said:
i wont install unless theres an ask jeeves widget ; )
Click to expand...
Click to collapse
Lol
Good job angel where can I get in on the action ?
Lets get a good rom going
Join in irc on freenode, #samsung-fascinate
And to the ones with root not showing up, can you 'ls /system/xbin' from adb and paste the results?
Sent from my SCH-I500 using XDA App
I cant activate google for the market with this nor the stock rom. I even did *228.
Any suggestions?
Sent from my SCH-I500 using Tapatalk
Solved issue once I did a reset in settings (found solution through Google for nexus one users)
This might be a dumb question but do u have ur gmail synched and set up?
Sent from my SCH-I500 using XDA App
Girlfriends Fascinate just decided to randomly stop doing anything except showing lights on soft keys after rooting and lag fix. Decided if I've got to restore should try this. First flash I got stuck at a similar issue after VZW logo. Wiped data and cache and was able to boot but entered in to FC hell. Working on flashing back to stock Odin posted in other thread as we speak.
Update: realized I had only wiped data and not cache as well. after doing that was able to flash back to stock, trying this once more.
Update 2: No go, still FCing like crazy. Flashing back to stock.
rstarr said:
Girlfriends Fascinate just decided to randomly stop doing anything except showing lights on soft keys after rooting and lag fix. Decided if I've got to restore should try this. First flash I got stuck at a similar issue after VZW logo. Wiped data and cache and was able to boot but entered in to FC hell. Working on flashing back to stock Odin posted in other thread as we speak.
Update: realized I had only wiped data and not cache as well. after doing that was able to flash back to stock, trying this once more.
Update 2: No go, still FCing like crazy. Flashing back to stock.
Click to expand...
Click to collapse
I had the same issue. Install stock and then Angels. Wipe cache only and it should work. If you cant activate Google do a reset in settings and all is fine.
I'm sorry, but that's exactly what I experienced rooting and running the lag fix on a Vibrant. There is something flawed with the lag fix. I don't know what it is, but this is the 4th experience I've read about that's the exact same as mine.
Could Samsung change the file system with an OTA update? Is that even possible?
BeeDubs said:
I'm sorry, but that's exactly what I experienced rooting and running the lag fix on a Vibrant. There is something flawed with the lag fix. I don't know what it is, but this is the 4th experience I've read about that's the exact same as mine.
Could Samsung change the file system with an OTA update? Is that even possible?
Click to expand...
Click to collapse
All the lag fixes have some issues right now. The best lag fix will come once samsung releases the source code for our phones. See here: http://project-voodoo.org/
Any chance we see this with an update to DI01?
Any chance this would fix my broken wifi ??? Other then that I love my Rooted de-binged and de-verizoned fascinate
Sent using Tapatalk
johnt2k said:
Any chance this would fix my broken wifi ??? Other then that I love my Rooted de-binged and de-verizoned fascinate
Sent using Tapatalk
Click to expand...
Click to collapse
I doubt it will fix wifi, what's wrong with it btw?
i lost it some how in the process of rooting and CW recovery ???
i actually got it resolved now i just went back to a stock nandroid that some one posted and now have re rooted and backed up ???
dont know if i had wifi on some how while in the process or what wifi teather worked but i could not scan for open wifi networks.
noob mistake
can someone please post stock rom my phone is trippn out nd i accidently forgot to do a backup thanx 2 whoevr saves my phone
salvy31 said:
can someone please post stock rom my phone is trippn out nd i accidently forgot to do a backup thanx 2 whoevr saves my phone
Click to expand...
Click to collapse
The stock rom is posted in a thread stickied in this forum with instructions on how to revert to stock as well...
salvy31 said:
can someone please post stock rom my phone is trippn out nd i accidently forgot to do a backup thanx 2 whoevr saves my phone
Click to expand...
Click to collapse
I recommend using odin and falling up's odin files. I'd link you, but my phone doesn't link.
I was trying to install axura custom ROM. So I copied it to the sdcard and then I rebooted to recovery. Everytime I choose "reisntall package" this what shows up :
i51.tinypic.com/212fpfa.jpg
you need to download rom manager and flash clockwork recovery first. You do not install rom's from the stock recovery. Read the noob guide if you have not already.
if you do have CWR, go to install from zip from sdcard and choose zip.
yes, I installed that already and chose Samsung vibrant after that i rebooted to recovery and that's what happened.
anyone who knows what the problem is?? been fixing it for a day.. but still can't make it work.
chase15 said:
anyone who knows what the problem is?? been fixing it for a day.. but still can't make it work.
Click to expand...
Click to collapse
Are you coming from stock 2.2?
not sure..i got this phone with 2.2 already installed.. im pretty sure its the stock..
chase15 said:
not sure..i got this phone with 2.2 already installed.. im pretty sure its the stock..
Click to expand...
Click to collapse
Ran into some crazy issues when rooting/custom flashing a friend's vibrant from stock 2.2. I ended up using ODIN back to 2.1 and then rooting and flashing a custom rom. The file system on 2.2 is different and CWM doesn't like it right away.
Also, that 3e recovery is a ****.
Read some of this...
http://forum.xda-developers.com/showthread.php?t=833423
http://forum.xda-developers.com/showthread.php?t=945294
and watch this
http://www.youtube.com/watch?v=AnY7P14JSWQ
Lots of work, but worth it. Please read up on other options too.
Good luck
ok.. so all this means... flashing ack to 2.1.. using odin.. then install custom ROM?
Essentially, yeah. Here's an OP that I just stumbled across. It should step you through it. I wish I had seen this when I was fumbling with errors messages like that on my friend's phone.
EDIT: This is a non-ODIN solution:
http://forum.xda-developers.com/showthread.php?t=925400
Good luck
chase15 said:
ok.. so all this means... flashing ack to 2.1.. using odin.. then install custom ROM?
Click to expand...
Click to collapse
Yeah, I had the same problem with my friend's phone. After you go back to stock, you can use z4root to apply a temporary root and then install CWR. Kind of a pain, but it gets the job done.
Sent from my SGH-T959 using XDA App
alright.. flashing 2.1 now.. ill come bck later.. if everything will work.
problem solved! Successfully flashed axura.. Thanks!
Rock on.
Congrats!
Vibrant on T-Mobile.
Powered by Whiskey and Voodoo magic while riding a Dead Horse.
chef_w said:
Rock on.
Congrats!
Vibrant on T-Mobile.
Powered by Whiskey and Voodoo magic while riding a Dead Horse.
Click to expand...
Click to collapse
thank you.. now waiting for my ffc.. gonna install it when it arrives.
Im trying to odin to jfd. Its keeps getting stuck at factory.fs.rfs Ive used odin several times with no issues. I could use some help please. Thanks
EDIT: Well after 3 hours messing with the Odin. I tried 3 different versions with every combo of checking repartion with no success. I had to leave to pick my son up and decided to try 1 more time and FINALLY it went thru. Thanks to all that responded.
Did you check the MD5 to make certain it was a good download?
Using the latest ODIN?
Don't rush it.... remain calm
s15274n said:
Did you check the MD5 to make certain it was a good download?
Using the latest ODIN?
Don't rush it.... remain calm
Click to expand...
Click to collapse
Yes its the same files Ive always used. Im using odin3 v1.70. Im freakin out here bro.
GreggoryD502 said:
Im trying to odin to jfd. Its keeps getting stuck at factory.fs.rfs Ive used odin several times with no issues. I could use some help please. Thanks
Click to expand...
Click to collapse
You should try using the toolbox
http://forum.xda-developers.com/showthread.php?t=954509
GreggoryD502 said:
Yes its the same files Ive always used. Im using odin3 v1.70. Im freakin out here bro.
Click to expand...
Click to collapse
Odin 1.3 always works for me.
Ive never used that before. The green bar is 1/3 full. Should I let it keep trying. It looks like it may be moving a tiny bit but im not sure.
Tried repartitioning?
Sent from my SGH-T959 using XDA Premium App
bigtom624 said:
Odin 1.3 always works for me.
Click to expand...
Click to collapse
Where is 1.3 at? I got 1.7 from the stickie.
Dang, stepped out for lunch and forgot to come back to this thread.... I assume you are all fine now?
EDIT, shooot... didnt read the updated post.
Curious, do you have other USB gadgets hooked up? I have NEVER had an issue with ODIN until last night. I was trying to record the steps to install CM7 and the recorder (hooked up via usb) was causing a TON of issues for me/ODIN.
I have not seen this issue anywhere else yet, and Jamezelle has personally tried to help, however as it is still not fixed, I figured I would try to see if as a collective anyone has any thoughts. Here it is, folks. I recently flashed the MIUI ROM, by Jamezelle, awesome ROM, however just not for me yet. SO, I wanted to flash back to Nitroglycerine's EC01/ED01 ROM, which works alright. It flashes, runs, etc. However, the SECOND that I try to flash a custom kernel, IE JT's newest Voodoo kernels, Imnuts voodoo kernel, etc. I get a boot loop and the FC vibrations. Also, part of the MIUI boot animation will reappear on flash of a new kernel, the graphical text that says "Android". This is all extremely frustrating, anything other than a stock kernel seems to do this. I cannot figure it out. Oddly enough, flashing a custom kernel over SC 2.9.2 seems to work alright, but not on any other ROM. I would appreciate any ideas or suggestions, however please keep in mind, all of the very n00b stuff I most likely already have known or tried. Formatting dbdata/data/system/boot, things like this, I have done, and to no avail. My main goal? Is to end up on Nitroglycerine's ED01 ROM with JT's latest voodoo kernel, any ideas on how to fix the custom kernel boot loops/FC vibrations upon trying this?
The easiest way would be to odin with a PIT file to anything you want, odin to dl09 and follow adryn's guide to get to ed01
Sent from my SCH-I500 using XDA App
micellis said:
The easiest way would be to odin with a PIT file to anything you want, odin to dl09 and follow adryn's guide to get to ed01
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I should have mentioned that I have done that a million times, it does nothing. I still get the same results, the same problems. :-( And I guess no one is interested in this issue, or no one knows a fix. ****ty.
Dread This Day said:
I should have mentioned that I have done that a million times, it does nothing. I still get the same results, the same problems. :-( And I guess no one is interested in this issue, or no one knows a fix. ****ty.
Click to expand...
Click to collapse
Are you wiping before flashing the Custom ED01 rom? This happened to me as well...it worked when i didn't wipe before flashing it
pootoss said:
Are you wiping before flashing the Custom ED01 rom? This happened to me as well...it worked when i didn't wipe before flashing it
Click to expand...
Click to collapse
Oddly enough, I had tried it both ways, wiping AND not wiping, both with the same boot loop results. However, good news. I simply Odin'ed to DL09, and updated to ED01 as Adynalyne posted about, flashed my kernel of choice, then flashed Nitroglycerine's newest ED01 ROM, and it actually booted. My newest conclusion: The version of Nitro's ROM I was trying to flash was probably ****ed, along with dbdata needing to be wiped in ADB. Thanks for the reply though!
Dread This Day said:
Oddly enough, I had tried it both ways, wiping AND not wiping, both with the same boot loop results. However, good news. I simply Odin'ed to DL09, and updated to ED01 as Adynalyne posted about, flashed my kernel of choice, then flashed Nitroglycerine's newest ED01 ROM, and it actually booted. My newest conclusion: The version of Nitro's ROM I was trying to flash was probably ****ed, along with dbdata needing to be wiped in ADB. Thanks for the reply though!
Click to expand...
Click to collapse
Glad to see you got it figured out Dread. I kept thinking the whole time that it was a bad/corrupted download. All in the past now though.
kidserious said:
Glad to see you got it figured out Dread. I kept thinking the whole time that it was a bad/corrupted download. All in the past now though.
Click to expand...
Click to collapse
Thanks bro, but oddly enough I do not think the download itself was corrupted. I read through a lot of Nitro's ED01 thread, and saw a lot of people were getting boot loops from that particular version, and I guess the fact that part of that MIUI boot animation was still there was throwing me in the wrong direction, you know? So I downloaded his newest ROM. But, finally, I'm on ED01, with the kernel I want, and everything is smoooooothe. Again, kidserious, thanks for the replies/help. Much appreciated.
Dread This Day said:
Thanks bro, but oddly enough I do not think the download itself was corrupted. I read through a lot of Nitro's ED01 thread, and saw a lot of people were getting boot loops from that particular version, and I guess the fact that part of that MIUI boot animation was still there was throwing me in the wrong direction, you know? So I downloaded his newest ROM. But, finally, I'm on ED01, with the kernel I want, and everything is smoooooothe. Again, kidserious, thanks for the replies/help. Much appreciated.
Click to expand...
Click to collapse
For sure. Hey man, if total functionality is not a must for you, you gotta try JT's CM7. I can't go back to any other rom. I even flashed his CM6 and still couldn't wait to get back to 7. Dude it's super snappy and silky smooth. IMO, the best the fascinate has ever seen (even in it's present condition). I can't wait to see when he squashes some of those bugs.
kidserious said:
For sure. Hey man, if total functionality is not a must for you, you gotta try JT's CM7. I can't go back to any other rom. I even flashed his CM6 and still couldn't wait to get back to 7. Dude it's super snappy and silky smooth. IMO, the best the fascinate has ever seen (even in it's present condition). I can't wait to see when he squashes some of those bugs.
Click to expand...
Click to collapse
Honestly, CM6 was amazing to me. The speed and stability was for the most part unrivaled...However, I just can't do without the MMS for a long period of time. :-( I hope he gets some of the bugs ironed out, I will FOR SURE switch then.
Okay.....Here's the situation: I have the Samsung Vibrant and wanted the new 2.2, so I tried doing it myself and just couldn't get it to work. So a guy I know came to the house and did it for me. He used something he was familiar with that he got from here. The phone works fine for the most part. I tried downloading and using GPSRestore from Samsung. When I ran the app it said it couldn't because I had a GT-I9000. How can I get the phone to show what it really is? Some information about the phone: Simply Galaxy 2.7.2 SweetHoney.zsjpj - Kernel ver.: 2.6.32.9 Overstock - v1.5.1 #1 - Firmware ver.: 2.2.1
I'd like to use the app from Samsung and other app's but I am wondering if this will happen again.
Well, that is because you have 2.2.1 which is a GT-I9000 build. To fix this go into root explorer, mount system as r/w, go into build.prop as the text editor and change everything that says GT-I9000 into SGH-T959. Hope that helps!
I'm going to print this out and give it a try right now. I'll be back shortly(if I dont screw it up) and let you know what happened. Thank.
I have a similar situation. I have a i9000 boot animation i would like to get rid of any ideas????
I just did it...it works...but u must reboot for the changes to take effect...
simply galaxy 2.8 vibrant
MikeJennni said:
I have a similar situation. I have a i9000 boot animation i would like to get rid of any ideas????
Click to expand...
Click to collapse
you probably flashed the GB bootloaders
^^AGREED^^
I9000 bootanimation is a known issue/non-issue after ODIN while using GB bootloaders. It is addressed in the OP of the GB bootloader thread.
------------
WOOT! +1 on "Root Explorer" that shiznit is tha bomb diggity!!
Good luck!
Well, I tried changing all of the GT-I9000's to SGH-T959 and after I did that I rebooted the phone. When the phone started up it started to vibrate every 3 seconds, would barely respond from the touch screen and would not accept anything from the keyboard.
At this point I thought I had ruined the phone because I couldn't get it back to the original settings. I finally got the keyboard to work by changing to a different one and got the original settings back. Where did I go wrong?
kawika said:
^^AGREED^^
I9000 bootanimation is a known issue/non-issue after ODIN while using GB bootloaders. It is addressed in the OP of the GB bootloader thread.
------------
WOOT! +1 on "Root Explorer" that shiznit is tha bomb diggity!!
Good luck!
Click to expand...
Click to collapse
What is the op of the gb section.....
Sent from my SGH-T959 using XDA Premium App
MikeJennni said:
What is the op of the gb section.....
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
"OP" = Original Post or Opening Post basically the First post of every thread.
I assume this is the GB bootloader thread everyone is referring to:
http://forum.xda-developers.com/showthread.php?t=1117990
This is posted in the "OP" of that thread:
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.
Click to expand...
Click to collapse
Thats all. Good luck!
I am having the same issue... i am not seeing a build.prop file I am running Malice_v4x_72011_EDT with GB boot loaders...
EDIT: NM I found it
yeah
I did something of the same thing....but it froze midway thru....totally freaked me out. Took me about 15minutes to try and figure out how to reboot the phone into recovery because it kept asking me to select with the OK key....and I dont have an ok key!! Once I finally got it to boot up, it would flash the GT-I9000 logo during bootup, THEN the Vibrant logo. I flashed it back to stock via Odin again and it finally went away. Dunno WHAT I did, but it was scary!
Well, I have given up on the whole thing. I have tried twice with the same results. I'm just going to live with and expect to not be able to run apps for the Vibrant. Thanks for everyones help.
outlawbiker619 said:
Well, I have given up on the whole thing. I have tried twice with the same results. I'm just going to live with and expect to not be able to run apps for the Vibrant. Thanks for everyones help.
Click to expand...
Click to collapse
theres a gps fix i think in sgstools, could try that ??
I was able to get the build.prop thing to work, but when all was said and done the swpe keyboard no longer responded... had to navigate through the market to find the basic gingerbread keyboard... all is well now...
as for the gps fix
i was able to get the one in sgstools to "run" (before i fixed the gt-i9000 thing), but i am running a GB rom, so it still doesn't work as well as it did with froyo...
Shouldnt matter if your phone is a GT-I9000
Its still a Galaxy S
And if it says GT-I9000, its because the ROM uses a GT-I9000 Kernel or its listed as such in the Build.prop.
Most Froyo ROMs dont even need the GPS restore because the GPS is pretty damn good on them all.
Try A Toxic or an EDT ROM
outlawbiker619 said:
Well, I tried changing all of the GT-I9000's to SGH-T959 and after I did that I rebooted the phone. When the phone started up it started to vibrate every 3 seconds, would barely respond from the touch screen and would not accept anything from the keyboard.
At this point I thought I had ruined the phone because I couldn't get it back to the original settings. I finally got the keyboard to work by changing to a different one and got the original settings back. Where did I go wrong?
Click to expand...
Click to collapse
ruined the phone??? Lol no you didn't..... just Flash back to stock and start over. read the stickies and bible if you need help
Finally!!!!!
Okay folks, thanks to the great posts on here, I tried one last time and it worked. I changed the keyboard first and then used sgstools which has a .prop editor in it. I rebooted and it works great now. Just have to get used to the GB keyboard now. Thanks again all.
You don't HAVE to get used to the Gingerbread Keyboard. Tons of after-market keyboards out there. I'd suggest Swype or Swiftkey X, but there are many more.
I was using the Swype and I think that was what was causing the problems I experienced. Since I switched to the Gingerbread keyboard it has been smooth sailing.