Related
I just installed the latest Galaxy S Lagfix from Voodoo, but every time I start my phone I get a Galaxy S i9000 splash now. Is this normal? Is there a way to remove it?
I believe there is a way to remove it, I do not believe it is something you will be able to do, or is worth the effort
What kernel did you flash
I believe that image may be in the kernel. I might be wrong though.
I'm on Build 1010. Within 30 minutes of getting it out of the box I rooted and put Serendipity 2.0 on.
I used One Click Root and Odin3.
Almost a week and NO problems what so ever. Many re-boots and what not as well.
I have the Galaxy S load screen as well. Honestly, it has to be perfectly normal.
Can someone please help.
Noob here in flashing ROM. I have successfully flashed 2 ROM's and failed miserably with one (Serendipity 4.3).
Trying to see if anyone has some input/suggestions.
Day 1 -- Read, Read, Read spent 3 days, about 12-14 hrs a day reading
Day 4 -- Tried Serendipity 4.3 as my first ROM flash after going back to stock with odin and master clear -- After reboot anything i do with the phone, it freezes. Absolutely drove me crazy, I really like the theme, features etc... So i thought i was doing something wrong. Tried again, exact same problem. 4.3 freezes badly.
Day 5 -- Went back to stock, odin
Day 6 -- Downloaded Cezar's Continuum 2.0 ROM, Installed, worked perfect. No issues, good gps lock, calls never fail, awesome awesome.
Day 7 -- Flashed Cezar's new theme-- voila, awesome multiplied instantly by 10 times, very very kool.
But, wait, Continumm doesn't have Swype.
Day 8 -- Try Serendipity 4.3 after Odin to stock, fail again.
Day 9 -- Read, read again
Day 10 - Download Perception 10.2, Odin to stock, install, working smooth since last 3 days
Day 11 -- Reading to find help if I am missing any steps for Serendipity 4.3
Day 12 -- If nothing works, will go back to Continuum 2.0 with Sensation theme.
Is anyone having issues with Serendipity 4.3 install ?
Things can do --Can root without looking at instructions, very familiar with unix so adb commands not a biggie. Always used reboot download. Easily work with TiBU, CWM, switching kernels using SGS etc.
Should i spend time on it or move on trying other ROM's like di11igaf's 5.3 which just came out or Firefly or Phoenix etc. Is this a symptom of ORD
Thank you for your input.
Sagi
Mods : Sorry, just realized, posted in wrong forum, can you please move it to Captivate Q&A.
You should use a ROM that works. In this case, you seem to really like Cezar's, so use that. No one says you HAVE to use Serendipity. If you do want to try Serendipity, try reflashing after you flash it the first time if problems come back, sometimes it just doesn't flash properly. I actually just reflashed 4.3 yesterday with no problems after testing out a few other ROMs for an hour or two (was that bored ).
Your phone hates OC/UV. Those other two ROMs are not OC/UV, while mine is. Swap the zImage with the speedmod one, and delete the Voltage Control app.
Or, wait for 5.0 where I'm switch to speedmod anyway.
MikeyMike01 said:
Your phone hates OC/UV. Those other two ROMs are not OC/UV, while mine is. Swap the zImage with the speedmod one, and delete the Voltage Control app.
Or, wait for 5.0 where I'm switch to speedmod anyway.
Click to expand...
Click to collapse
Mike,
First, thanks for your efforts with Serendipity.
Is it really possible that some phone can hate oc/uv ?? I guess, i need to read more.... .
I will give it a try soon to swap with Speedmod and delete the VC app.
Good to know you are cooking 5.0, I promise, i'll give it a shot as soon as it is out. I like all the things you have in your rom. Any guess when it might be out..
Thanks again.
Serendipity 5.0 is smoooth.
Mike,
Guess what, I am on Serendipity 5.0 now and it has been working perfectly and it is fast.
Thank you, thank you.
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App
Hello astute folks on XDA!! My name is Brian and i'm a flash-a-holic. I'd like to share with you my experience that ultimately lead to me fubaring my beloved captivate.
I've flashed everything under the sun on this phone from roms to different kernels to modems. You name it, i flashed it with great success (after researching, never flashed on a whim.) UNTIL... Yesterday.. lol.. I was running a leaked 2.3.4 gingerbread rom and i noticed the problem first starting while trying to connect my phone to my computer via usb. The two didn't communicate when for the last 6 months, every single time i plugged in, my computer and phone recognized each other every single time. So that was my first clue that something aint right. Next thing i did was power the phone off. Went to turn it back on and NOOOOPPPEEEEE!!! Nothing!!!!! Held all three buttons and the little grey circular icon came on (the one that is initially in the battery icon when the phone is powered off but it's plugged in) but immediately shut off. Nothing turned my phone back on, but i was able to get into download mode. So thats what i did. I used odin3 oneclick to go back to stock eclair thinking that that will start everything all over, erase the bad/corrupt files and so forth. Flash was successful. Got back to stock eclair and got stuck in MTP initialization (you know, the screen in which you get if your debugging mode wasn't checked.) But it hung on that screen. No buttons would allow my to exit so, I pulled the battery. Then, the same damn thing.. I could NOT get the phone to power back on. Lesson learned for me. (today i learned that going back to stock is NOT a fresh install.) Used odin again, but this time unplugged my cord BEFORE i got to the eclair boot screen. As i'm peering at this home screen, i noticed that my USB connecting notification was flashing on, off, on, off yet my cord was unplugged. At this point i called tech AT&T tech support because i knew i was screwed. (i told them i tried to update to the 2.2 they provided on website and the phone cut out, lol).. I spent an hour on the phone and got no where other than determining that my phone is farked and they are gonna send me out a replacement (which will take 4 to 6 days) because luckily it was under warranty still. Tech support couldn't get my phone to turn on, but i could, lmao.. So... here i am stuck with a phone where usb debugging mode is buggin out!!!!!!! To wrap this story up, what i did was got back into download mode and flashed gingerbread bootloaders and a kernel and voila!! So long as i don't turn my phone off, i have a fully operational phone until my new cappy arrives in the mail in 4-6 days. (Dicks.. If i had been ordering a new phone, i'd have the option for next day shipping but thats another story.)
TLDR: Flashing too much will get you in a bad situation. Stick with a rom/modem/kernel setup that suits your needs because your next flash could be your last depending on the components in your phone.
EDIT: MAKE IT KNOWN THAT I HOLD NO ONE RESPONSIBLE OTHER THAN MYSELF FOR THE FUBARING OF MY CAPPY!!!!!!!!!!
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Things break...and ppl make mistakes... I'm still trying to figure out which one happened in your situation.
Sent from my SGH-I897 using XDA Premium App
That's a common hardware issue with the captivate. Happened to me twice. Its just the USB port spassing out thinking tthe cable is constantly getting plugged in and unplugged and freezing tthe phone with its craziness. Both times it was replaced under warranty. I'm paranoid it'll happen again now that I'm out of warranty.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
speedy_11 said:
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Click to expand...
Click to collapse
Oops, my bad!! It needs to be somewhere as a precaution to those that think flashing is completely harmless
EDIT: upon further contemplation, it really is a question of what went wrong
Sent from my GT-I9000 using XDA Premium App
I am a flash addict as well
i have flashed all froyo based roms on my cappy !
Can anyone confirm that excessive flashing may risk my phone?
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Thanks for the quick response....!
now i dont need to worry
xijar said:
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'm 99% sure my board failed because of cheap, unreliable components. However, that 1% is still in the back of my mind that it could have been from something I flashed. I suppose I'll never know.
Sent from my fubared, soon to be replaced cappy running GT-I9000 gb rom using XDA Premium App
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Accidental post. Please delete.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
As I started before, the phone is fully functional with gingerbread other than the occasional usb flickering..Only problem I have with it really is if I turn the phone off, it won't turn back on unless I hold power and volume up, enter cwm and then select reboot now.
Before I send it back, I'll odin back to jf6 first with oneclick. Without cwm on the phone, lol, it absolutely won't turn on by just using the power button. I made sure of this before I even called the warranty department and explained my dilemma
The nice thing is that I can use the phone while I wait fire the new one to arrive AND I can flash and experiment with everything now without worries!!!
Sent from my fubared chappy running GT-I9000 GB rom using XDA Premium App
I am also a flash-o-holic and I think that if you flash with odin lots with repartition checked or are enabling/disabling voodoo lots, it can mess up your phone. Has happened to me twice, just sent my phone today for the second time. Both times this happened to me it happened when successfully flashing back to stock with 512.pit and repartition checked. On boot up it stalls at the "S" screen and never goes past it and in recovery I get some errors like:
error: can't mount /dev/block/mmcblk0p1
error: can't mount sdcard
I flashed many different firmwares with different pit files and different android versions but all conclude the same, stuck at the "S" boot screen.
I have determined that the partition tables were messed up and I tried to fix it by putting parted on my phone and trying to repartition it from the shell. Both times I get the "unable to write to /dev/block/mmcblk0 - I/O error!" Also, from CWM Recovery I try repartition sdcard but it also comes up with an error. The last time I sent it into Samsung repair they had to replace the main board to get it working properly again. Think it is definitely a good idea to find a rom / kernel / modem you are happy with and stick with it for a while.
Hi,
I am really confused, yesterday I flash Alba LQ2 rom latest full with no problems.
I like ICS its very good but slight problems occurred today.
This all happened during my travels to London in the train.
so I noticed my note did not go to deep sleep, so read in the forums to put on flight mode, turn off phone. take out batteries for a few mins(in my case 5 mins), put it back in turn on phone and turn off flight mode.
I did that but when I attempted to turn on the phone it just stayed on the samsung logo flashing white and blue for 20 minutes. I restarted it and the same thing.
As this happened in the train i panicked. I went to CWM with no problems and tried to flash the same rom again without clearing any data or cache and so on.
the following came up:
CWM-based Recovery v5.0.2.7
-- Installing: /emmc/AlBa_XXLQ2_Full.zip
Finding update package...
Opening update package...
Installing update...
AlBa XXLQ2 Full
and the bar where it shows it working stayed empty for 15 or so minutes, so i got annoyed and tried it again, went back to cwm without a problem did the same and the same thing popped up. I've kept it till now and it is still the same for the past 1 hour and 20 or so minutes.
I don't want ICS anymore, I just want to go back to GB right now. Have I bricked my note? if not, can anyone guide me to get back to GB if possible.
Thanks in advance.
oh and my phone was not overheating whatsoever. it seems cool till now.
assuming no one has replied, just to say, ive sorted it out, i restored to a rooted gb rom via pc odin and then wiped data. and now its fine, may give paranoidandroid a shot.
You may have to give your flashing hobby a breather for now.. .you just came from a nearly brick experience and now you want to try to flash another ROM again?
Sooner or later, you may encounter that infamous HARD BRICK BUG that people are saying all over the Galaxy's Note's thread..
Just caveat in flashing or changing ROM always...
you never know what your gonna get until you will finally get it....
Cheers!.
From what I gather so far, you were smart enough to not wipe data or anything so you were not bricked at all with the eMMc bug and you knew what to do on your own (probably by reading the forums) which I would say I am proud of you for.
You did correctly by flashing to Gingerbread. Now, you want to try ParanoidAndroid (I must say it is fantastic). It's based on CM9 so it's easy. Since you are on GB, make sure you are rooted. Flash the CWM.zip file (in drketan's thread). Then, flash ParanoidAndroid. Wipe cache, dalvik cache, and data. Reboot. Enjoy awesome hybrid settings.
thanks both of you. oh my, i must paranoidandroid is really good, never thought i could witness so much from a community built rom.
yh I didn't wipe data when i was at ics, i knew the phone will die if I did. anyhow thanks.
@letters_to_cleo, i guess your right, ill stop flashing for a while.
the reason i do this, its just because I have some knowledge on the linux world coming from n900 maemo and so on its all good fun and interesting to see how open android really is.
If you read the OP and stickies, you will be fine. So, continue flashing! It's fun when you follow the rules given.