I have a Stock 2.1 Samsung Galaxy S I9000M from Bell and suddenly I noticed it would not boot anymore. It shows the model number, then the "M" would disappear and go on with the boot movie (for a good 5 min) then just blank out and freeze.
I had the Voodoo lag fix applied to it but it has been working fine until today.
What should I try doing on it?
Thanks!!
knightdaemon said:
I have a Stock 2.1 Samsung Galaxy S I9000M from Bell and suddenly I noticed it would not boot anymore. It shows the model number, then the "M" would disappear and go on with the boot movie (for a good 5 min) then just blank out and freeze.
I had the Voodoo lag fix applied to it but it has been working fine until today.
What should I try doing on it?
Thanks!!
Click to expand...
Click to collapse
That is strange. From what I read here in the fourms, the symptom of the missing "M" is related to flshing an international firmware but you say your device is stock... Is that correct?
I would start by removing the voodoo lag fix and then doing a factory reset. If that does not work then you may be one of the unlucky people (mostly us here in Canada with the i9000M) whos internal sd card has failed after applying the lagfix.
If anyone else has any info to share or if Im incorrect then please let me know.
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
SO I have disabled Voodoo and then performed a reset in recovery mode. Then another reset through the phone's normal interface.
Currently restoring everything through Titanium then reapplying Voodoo.
knightdaemon said:
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
SO I have disabled Voodoo and then performed a reset in recovery mode. Then another reset through the phone's normal interface.
Currently restoring everything through Titanium then reapplying Voodoo.
Click to expand...
Click to collapse
The other thing to keep in mind is that the voodoo lag fix actualy flashes a "non stock" kernel to your device so again... It MAY be the voodoo fix that is causing the "M' to disappear as it is compiled on an "international" kernel.
Perhaps if you NEED a lagfix you should use oe that does not modify the kernel itself but be warned... It seems that the lagfixes contribute to the internal sd card deaths that I previously mentioned.
PS... I thought Titanium coul only be used on a rooted device? Are you rooted? If so then your device is NOT "stock".
It would make sense for the "M".
Yes, I'm rooted, I thought root doesn't redefined stock
knightdaemon said:
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
Click to expand...
Click to collapse
Wait, "updated through unhacked Kies"? Is it on JH2 eclair, or on some froyo variant? If the m disappears, it sounds like you used the reg hack on kies to update to an i9000 version of froyo
It is JH2, I bought the first batch of Samsung Galaxy S in Canada, it had another version beforehand. I do not have froyo yet, waiting on the official version.
knightdaemon said:
It is JH2, I bought the first batch of Samsung Galaxy S in Canada, it had another version beforehand. I do not have froyo yet, waiting on the official version.
Click to expand...
Click to collapse
Ah, ok, I understand now. I have no idea. I've only seen the m disappear when you run a i9000 firmware
Related
First a bit of background. I have a i9000m Bell breed running JH2, I rooted it to unlock the SIM at first and have been running on Telus. I had RyanZA's OCLF installed on it. One day it shut down on it's own a few times and then it wouldn't boot. So I restored it and reinstalled OCLF, then I removed the lag fix in the program. Today I was going to add it back on but it says unavailable.
Now a could things, I think I undid the lag fix in OCLF but I can't remember if I did for sure or not. I know the phone is still rooted. What can I do?
op, the first thing you can do is to post this in the right forum.
my take is to reflash to jh2. of course, if you have the 3-button combination working.
g00ndu said:
op, the first thing you can do is to post this in the right forum.
my take is to reflash to jh2. of course, if you have the 3-button combination working.
Click to expand...
Click to collapse
Sorry about posting in the wrong forum, wasn't sure which one to use.
So it says I have a lagfix installed already. It there anyway to check this? Because I am not 100% sure that I was using RyanZA's fix from the start.
I do have the 3 button working and I did reflash JH2 not too long ago when my phone messed up on me. After installing I lost everything but still have the Superuser. But the lagfix has not worked since.
Use apps2sd to Check if you have anything installed in the sdcard, & move them back. then try.
ragin said:
Use apps2sd to Check if you have anything installed in the sdcard, & move them back. then try.
Click to expand...
Click to collapse
Does that come installed on the phone? I can't find it?
you can install it only if you have Froyo 2.2 which is not released for the public yet
AllGamer said:
you can install it only if you have Froyo 2.2 which is not released for the public yet
Click to expand...
Click to collapse
OK, I'm still on 2.1
So what can I do? Or check?
I got a 2nd hand Bell Galaxy S Vibrant off craigslist. It is rooted (when I got it). It's still running 2.1 and the 2.2 update is available.. Now before I proceed with updating it, I want to make sure that there's no lagfix installed. How can I tell? I already did a factory reset. I also went to recovery mode and wiped the phone from there. Anything else I should do?
Could just run quadrant, unlagfixed phones would probably be about 1k or less, those with the fix are way higher
thanks for the tip!
Hello Experts,
I'm looking for some sort of check list when I receive my phone to ensure that my phone does not brick again or that I have a solid phone at that.
What sort of things should I be looking for in terms of firmware date, what type of firmware is installed etc?
Should I be seeing JL2 on it? Should the date be 10.12 or higher? Should I ensure download recovery works? etc, ,,, Does anything else come to mind?
Previous phone was an unlocked Bell GT-I9000M with stock JK4 installed, Froyo 2.2, rooted with lagfix. No other custom roms installed.
Thanks in advance.
You might want to tell us 'how' you bricked it?
sturmeh said:
You might want to tell us 'how' you bricked it?
Click to expand...
Click to collapse
Updated the phone to Froyo 2.2 via keis.
Rooted it with SuperOneClick
Installed OCLF.
That's it. Worked great for 3 weeks, then noticed some force closures occurring. Reformatted the phone, pulled down all my apps from myroot backup. Updated all the apps that I had installed. Apps kept crashing and FC's still occurred. Pulled the battery, restarted the phone and that was it.
Hi,
Short story:
I'm bringing in my device (a Samsung Captivate i896) to get replaced at a Rogers store. However, I had installed a kernel (I think, I'm still new to this and I'm not sure which one it was) that flashes (i9000 Samsung Galaxy S) on the startup splash screen. How do I remove this from my startup screen so my device isn't voided?
Long story:
My phone dialler has, literally, just stopped working on me. When I dial out I hear no connecting tone, the other person's voice nor can they hear mine. I also can't receive calls. The only way my phone works is if I put it on speaker function (then I can hear everything) but the second I uncheck the speaker function, BAM the device dies on me. I'm trying to get it replaced.
Any help would be deeply appreciated.
Thanks!
Go back to a stock rom.
vbetts said:
Go back to a stock rom.
Click to expand...
Click to collapse
Can you give me instructions how to do that? I'm still really new to Android so I am quite lost. Thanks!
http://forum.xda-developers.com/showthread.php?t=731989
NewbDroid said:
Hi,
Short story:
I'm bringing in my device (a Samsung Captivate i896) to get replaced at a Rogers store. However, I had installed a kernel (I think, I'm still new to this and I'm not sure which one it was) that flashes (i9000 Samsung Galaxy S) on the startup splash screen. How do I remove this from my startup screen so my device isn't voided?
Long story:
My phone dialler has, literally, just stopped working on me. When I dial out I hear no connecting tone, the other person's voice nor can they hear mine. I also can't receive calls. The only way my phone works is if I put it on speaker function (then I can hear everything) but the second I uncheck the speaker function, BAM the device dies on me. I'm trying to get it replaced.
Any help would be deeply appreciated.
Thanks!
Click to expand...
Click to collapse
HAHAHAHA!!! DUDE i did this last night!!!! flashed a cw comatible kernel and my phone no longer recoginzed a sim was installed anymore! i lied my ass off and got it replaced because i forgot to backup first and NEEDED my phone that night. couldnt play forever...
So... any idea where we screwed up? besides not backing up? is the usa att kernels not compatible with canadian sims?
Nope, not compatible at all. Once it says AT&T on the startup screen you're totally screwed since the phone will not recognize your SIM anymore (it thinks you're in the States).
How did you manage to get it replaced? What did you tell them? I'm pretty stuck...
I told them that my phone was eracing my music files on the internal sim card. then it locked up well I was transferring files and wasn't able to make calls anymore...
with my new phone I flashed the phoenix 4.1 rom which has a new kernel, and everything is great. Pm me for advice and back up files
Sent from my SGH-I897 using XDA App
SGH i896 Captivate Rogers Canada Stock Flash Resources 2.1 2.2 froyo odin cwrecovery
heres the help you need:
some starter info:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896#Custom_ROMs
Rogers 2.1 stock rom
http://www.megaupload.com/?d=TT4RYLDZ
Rogers 2.2 stock roms
http://forum.xda-developers.com/showthread.php?t=905042
alternate download
http://forum.xda-developers.com/showpost.php?p=9096976&postcount=673
some info if you have installed 2.2 and now have e3 recovery and are having trouble installing update.zip's, where it "fails verification check" everytime
http://forum.xda-developers.com/showthread.php?t=909213
teach a man to fish...
Moved to Captivate Q&A
also, after my first experience, ive done everything possible WITHOUT odin. it took me forever to realize there is an Odin3 and an Odin 1step. have trouble finding info on how to use odin3.
so i use rom manager with clockwork mod (read the e3 link) or custom roms that have clockwork recovery in their kernel. Steam recovery kernels look good too.
Firebird 2.04 Kernel + Phoenix 4.1
Anyone know if the Firebird 2.04 Kernel works well with Phoenix 4.1? Can I use Clockwork to flash Firebird 2.04 Kernel to Phoenix 4.1? Thanks.
Ashyford said:
Anyone know if the Firebird 2.04 Kernel works well with Phoenix 4.1? Can I use Clockwork to flash Firebird 2.04 Kernel to Phoenix 4.1? Thanks.
Click to expand...
Click to collapse
wrong thread dude.. try the phoenix thread or the firebird thread.. are you a canadian captivate too? i896 not i897 ?? something tells me that you shouldnt be flashing your phone....
Trusselo said:
HAHAHAHA!!! DUDE i did this last night!!!! flashed a cw comatible kernel and my phone no longer recoginzed a sim was installed anymore! i lied my ass off and got it replaced because i forgot to backup first and NEEDED my phone that night. couldnt play forever...
So... any idea where we screwed up? besides not backing up? is the usa att kernels not compatible with canadian sims?
Click to expand...
Click to collapse
What did you guys do? I have been flashing ROMS like crazy and my Rogers sim is recognized.
I have changed kernels, roms and modems with no issue.
well im good now but with my first captivate i flashed a "cwcompatible" kernel with ODIN 3 into the *Phone* box. after that, couldnt make calls, and couldnt get into APN settings because it was telling me there was no SIM installed. i was too new and didnt backup properly.
Now i dont use ODIN and dont have problems. still not sure what i did wrong.
been extra careful ever since tho.
Trusselo said:
well im good now but with my first captivate i flashed a "cwcompatible" kernel with ODIN 3 into the *Phone* box. after that, couldnt make calls, and couldnt get into APN settings because it was telling me there was no SIM installed. i was too new and didnt backup properly.
Now i dont use ODIN and dont have problems. still not sure what i did wrong.
been extra careful ever since tho.
Click to expand...
Click to collapse
What you did wrong was use a CWcompatible kernal in ODIN.
The flash files go into the PDA section.
ah just figured out what i did.. and you helped. the kernel i had was for odin, from what i remember but it was going to flash a kernel that had cw in it. i was having trouble doing update.zip method because of e3 recovery.
I just opened oden for the first time since that day, and realized i confused PDA with PIT which i knew took a differnt type of file, and went with the next box that took tar... PHONE... my dumb mistake.
Trusselo said:
ah just figured out what i did.. and you helped. the kernel i had was for odin, from what i remember but it was going to flash a kernel that had cw in it. i was having trouble doing update.zip method because of e3 recovery.
I just opened oden for the first time since that day, and realized i confused PDA with PIT which i knew took a differnt type of file, and went with the next box that took tar... PHONE... my dumb mistake.
Click to expand...
Click to collapse
Glad I could help
The problem when I had AT&T running on my phone (instead of Rogers) is that there's no sideloading, hence, I was unable to enter download mode at all to put the Rogers ROM back on it. Therefore = screwed.
past tense? did you fix it? replace it? and you can always clockwork recovery flash anything.
shawn122 said:
What did you guys do? I have been flashing ROMS like crazy and my Rogers sim is recognized.
I have changed kernels, roms and modems with no issue.
Click to expand...
Click to collapse
Same been flashing a few roms, even base on ATT..
Using a Fido sim card..
And it works fine
Hello guys.
Official Gingerbread is finally available on Portugal.
I have currently Stock Froyo + Speedmod installed on my Galaxy S, so how can i update to Gingerbread?
Can i just update and Speedmod will still work?
Or should i install a stock kernel, then update, then install the Speedmod (Gingerbread version)?
Or i shouldn't update at all?
i'm interested in this too,i'm in the same situation (froyo+speedmod) and i'm quite a noob
is there someone who can patiently give us an hint about that? also about a good battery life gingerbread rom?
This is what I did.
1. Disable any lagfix - convert back to rfs (very important).
2. Back up all apps, contacts, data, photos etc from internal memory. Use something like Titanium backup or Mybackup pro.
3. Update through Kies for an official update.
4. Install latest Speedmod kernel for gingerbread (not Froyo version). Use odin.
5. Install superuser from clockwork mod recovery.
6. From recovery, do a factory data reset (make sure you have everything backed up first!)
7. Restore previously backed up apps, data etc, sync with google calendar.
8. Redo lagfix from recovery (convert to ext4).
Battery life at first seemed all over the place but has now settled down and is similar to Froyo/speedmod.
The phone is smoother and faster to use.
Thank you a lot!
That's exactly what i'm going to do!
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
skeletonboy said:
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
Click to expand...
Click to collapse
If Kies is showing that there is an update available then I think you should be ok.
If not then it is a case of flashing the whole firmware with odin. Open phone dialer and enter *#1234# and you will see the firmware details you are on now. It is worth making a note of these so you can reflash your current firmware if there is a problem.
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Everything is working better than ever, except for one little thing: The GPS.
Today i turned on GPS and tried to use my navigation software (CoPilot) and the GPS signal just didn't fix at all!
I ended by not using it, but i don't know why it doesn't work. It always worked wonderfully well before this update...
skeletonboy said:
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Click to expand...
Click to collapse
Still try kies first. If no luck there is a lot of info in this thread.
http://forum.xda-developers.com/showthread.php?t=723596
Make sure you can get into recovery mode first. Power button, volume up and home pressed all at once. Let go home button when Samsung logo appears.
ok thanks for the infos! i'll do it all when i can have a bit of relax,i am relocating so i need a working phone during these days
so i did it then!
flashed darky's resurrection 10.2 and then updated to doctorz rom jvt leaving ext4 enabled with no probs: another phone
just needs a good theme now..