• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The I borked my SF support group thread

nitsuj17 said:
S



Sorry i should have qualified that by saying its not official its basically a cm6 port of 2.2 made to work on the eris and flash doesn't work i don't believe
Click to expand...

Bah. The one phone that's still extremely common out there, and REALLY REALLY NEEDS Froyo won't get it officially. Sad. Crappy crappy support.

I mean we're talking WORSE THAN APPLE support. As an Eris owner it will be a LONG time before I consider another HTC device again.
 
I dove headfirst into this club this past week, although I hope to somehow avoid the problems associated with all these processes (fingers crossed). I just rooted/de-bloated my Fascinate a couple days ago and am now proceeding to go forward with one of Dirk's voodoo kernels. Which one, I am presently trying to decide...
 
Mazeraski said:
I dove headfirst into this club this past week, although I hope to somehow avoid the problems associated with all these processes (fingers crossed). I just rooted/de-bloated my Fascinate a couple days ago and am now proceeding to go forward with one of Dirk's voodoo kernels. Which one, I am presently trying to decide...
Click to expand...

I'm having great results with the D02 LV 1100 kernel. Boot animations and all. Definitely recommend it. It's a mild overclock while still giving you the extended battery life of the lower voltage. 1200 LV is not running for everyone. I'll test it again soon, but so far I've had the most stability with LV 1100.
 
SirKronan said:
I'm having great results with the D02 LV 1100 kernel. Boot animations and all. Definitely recommend it. It's a mild overclock while still giving you the extended battery life of the lower voltage. 1200 LV is not running for everyone. I'll test it again soon, but so far I've had the most stability with LV 1100.
Click to expand...

Yeah, I ended up going with the D02 LV 1100 kernel figuring that would be a good place to start. A bit of overclock with lower voltage seems like the best of both worlds (at least, to start :D). The only problem I ran into was now my boot animations are not showing. The Galaxy S/Verizon music plays but it's a black screen. So now I'm looking to replace the boot animation file with something from here (that you posted):

http://androidforums.com/fascinate-...-fascinate-boot-animation-links-requests.html

From what I understand for that, you can put the bootanimation.zip file into either /data/local OR /system/media (so long as you tack .old onto the old boot animation), correct? Also, where is the original boot animation located? In /system/media? All I see in there is bootsamsung.qmg and bootsamsungloop.qmg, which I am assuming are not the correct ones for this.

If you wanted to change the startup sounds, you would have to rename "PowerOn.wav" to "PowerOn.wav.old" and place the wanted replacement file (as a .wav) in that same folder (/system/etc)?

Also, if you wanted to change the shutdown sound, you would have to rename "shutdown.ogg" to "shutdown.ogg.old" and place the wanted replacement file (as a .ogg) in that same folder (which I found to be /system/media/audio/ui)?

If anyone knows if that's right or wrong, let me (and others interested) know. I got that info from this thread at XDA (~halfway down):
bootanimation.zip links - Page 3 - xda-developers
 
Mazeraski said:
From what I understand for that, you can put the bootanimation.zip file into either /data/local OR /system/media (so long as you tack .old onto the old boot animation), correct? Also, where is the original boot animation located? In /system/media? All I see in there is bootsamsung.qmg and bootsamsungloop.qmg, which I am assuming are not the correct ones for this.
Click to expand...

yeah just drop it in data/local as bootanimation.zip and you ll be good to go, dont worry about system/media (i used to be all about system/media but data/local is easier on the sf). The original is in system/media but as d13 and others have pointed out, the phone looks in data/local first so its easier.

Mazeraski said:
If you wanted to change the startup sounds, you would have to rename "PowerOn.wav" to "PowerOn.wav.old" and place the wanted replacement file (as a .wav) in that same folder (/system/etc)?
Also, if you wanted to change the shutdown sound, you would have to rename "shutdown.ogg" to "shutdown.ogg.old" and place the wanted replacement file (as a .ogg) in that same folder (which I found to be /system/media/audio/ui)?
Click to expand...


you got it :D but just make sure the file your putting in there is the right format (obviously)
 
nitsuj17 said:
yeah just drop it in data/local as bootanimation.zip and you ll be good to go, dont worry about system/media (i used to be all about system/media but data/local is easier on the sf). The original is in system/media but as d13 and others have pointed out, the phone looks in data/local first so its easier.
Click to expand...
Well putting it in data/local isn't working for me :confused: it did on the X but not on the SF
 
Piiman said:
Stock right now. I even made sure to dnload one that said it was confirmed to work. Didn't work ;-( I renamed the old one also.
Click to expand...

hmmm, ive never tried to on stock sorry :( just on voodoo, maybe someone else knows (its been pretty quiet here today)
 
i guess I'm lucky of all the phones I've had, D1, Eris, Ally, X.. I've only bricked once and that was on the X. But it was my fault and I know exactly what I did wrong.
 
jreed2560 said:
i guess I'm lucky of all the phones I've had, D1, Eris, Ally, X.. I've only bricked once and that was on the X. But it was my fault and I know exactly what I did wrong.
Click to expand...

Well I never bricked anything but I've had some scares bork does not equal brick:rolleyes: The worse was this kernel thing but I knew we could fix it one way or another so I was too scared. :cool:
 
i try and avoid using "brick" to describe the state of a phone now cuz that tends to indicate its not fixable and thus "bricked" i usually go with screwed up because thats what is usually is until i work through a fix for it.
 
yeah so far no one here has bricked by trying to flash another galaxy s rom on the fascinate. (someone at xda tried flashing an i-9000 one) but crazily the phone was brought back to life.

looks like as long as the radio/firmware isnt flashed over, there isnt much that can truly kill this phone. :D
 
nitsuj17 said:
i try and avoid using "brick" to describe the state of a phone now cuz that tends to indicate its not fixable and thus "bricked" i usually go with screwed up because thats what is usually is until i work through a fix for it.
Click to expand...

What's worse? Bricked or borked??
 
Well, I got the startup and shutdown sounds to change. And now I have the scribble droid animation on bootup :)

To those of you doing these processes, make sure the boot animation file is named "bootanimation.zip". Mine wasn't the first time and I booted it up and low-and-behold; no animation. I was left wondering what went wrong when it dawned on me that I hadn't changed the name of the file. Gotta love those moments.
 
Mazeraski said:
Well, I got the startup and shutdown sounds to change. And now I have the scribble droid animation on bootup :)

To those of you doing these processes, make sure the boot animation file is named "bootanimation.zip". Mine wasn't the first time and I booted it up and low-and-behold; no animation. I was left wondering what went wrong when it dawned on me that I hadn't changed the name of the file. Gotta love those moments.
Click to expand...
Greta stuff new Club member, although membership is somewhat contingent upon having an actual bork incident ;):p.
Seriously though, nice work and nice personal reports. The kernels are a funny thing. I have concluded you literally have to try them all to find the right one for you phone. I settled with 1200LV. But until you try them all you dont really know which is best for your circumstances
 
saps said:
Greta stuff new Club member, although membership is somewhat contingent upon having an actual bork incident ;):p.
Seriously though, nice work and nice personal reports. The kernels are a funny thing. I have concluded you literally have to try them all to find the right one for you phone. I settled with 1200LV. But until you try them all you dont really know which is best for your circumstances
Click to expand...

Yeah, I was actually thinking "hmm...I haven't technically borked anything yet". I just didn't want to jinx myself :). I'm sure sometime in the future, something along those lines will happen. It is only my second smartphone so I'm a bit of a noob (first was the X which I had for all of two weeks). I do plan on trying out other kernels in the near future to see which I like best, but for now I'm testing out the 1100LV.


nitsuj17 said:
haha definetly bricked...to me that means it can t be fixed
Click to expand...

That's what I've gathered from the term bricked too.
 
Haven't become a full member of this group yet, right now I've been hanging around step five. Thought I accidentally (because people often do it on purpose) screwed it up yesterday installing something without disabling Voodoo, but a battery pull and reset and it's fine. I know it's only a matter of time, though..
 
Moonfire said:
Haven't become a full member of this group yet, right now I've been hanging around step five. Thought I accidentally (because people often do it on purpose) screwed it up yesterday installing something without disabling Voodoo, but a battery pull and reset and it's fine. I know it's only a matter of time, though..
Click to expand...

yeah, i think at some point all of us soft-brick or think we do, but the more people it happens to and see what caused it, the more likely you are to avoid it.

I'll be good to go until froyo or the next generations of kernels come out at which point it ll prolly be an odin reset or two :rolleyes:
 
You must log in or register to reply here.
Back
Top Bottom