Forum Home
Press F1
Thread ID: 126776	2012-09-17 22:36:00	Galaxy S i9000 firmware problems	dugimodo (138)	Press F1

Post ID	Timestamp	Content	User
1301716	2012-09-17 22:36:00	Some of you may recall about 4 weeks ago I flashed a custom ROM onto my Galaxy S to get Jelly Bean on it. It was a hellybean ROM based on CM10. It's been running perfectly ever since until last night. The CM boot screen kept popping up all the time and interupting whatever I was doing making the phone almost unusable. I tried a factory reset, rebooting, pulling the battery out etc with no luck, so I decided to revert back to stock ROM. then the real fun started. I can't find a Stock Vodafone NZ ROM anywhere, so I decided to revert to 2.3.6 I got as part of the process to get hellybean. I believe it's an official samsung ROM. I flashed 2.3.6 with Odin, phone then went into endless boot cycles no matter what I tried, reflashed, reset, wiped etc - all no go. thought I'd killed it. After a bit of research I found Darky's 10.2 restoration ROM and flashed that with Odin, thankfully that worked and the phone was back in action with Darky's version of 2.3.4. I think it worked properly but I didn't use it long enough to be sure. All this put me off the Idea of custom ROMs so I tried 2.3.6 again and this time it worked, except it's not behaving properly. The home button wakes the phone up but does nothing else, the lock screen isn't locked no matter what I set, and the facial recognition option does nothing. Other than this it seems to be working ok. So My questions: Is there a stock Vodafone ROM available somewhere? I'd like to be able to revert to standard between trying these. Is there some way to completely remove all traces of a ROM before applying a new one? because flashing over top seems to behave differently depending on what is currently on there Is anyone using 2.3.6 and can confirm the Home button should take me home when I'm in an app etc (just to check it wasn't changed to behave this way on purpose) Any other comments?	dugimodo (138)
1301717	2012-09-17 22:44:00	Whatever program you used, you should have made a backup of the rom, if it had the option. What version was the stock rom?? 2.2.1? You could try this (forum.xda-developers.com)	Speedy Gonzales (78)
1301718	2012-09-17 23:05:00	Actually touch wood It looks like it's all back to normal, I did another factory reset on the current 2.3.6 and everything appears to be back to how it should be. I didn't see an option to backup the ROM in Odin, but if it's there then you're right I should have used it. Hindsight and all that. I'd still like a copy of the standard Vodafone NZ ROM if anyone has a link, When I search I find overseas ROMs that would probably work but If I'm going back to stock I'd prefer it to be the correct local ROM. It's been a fun experiment, and the 2.3.6 I have ended up with is a little nicer than Vodafones official version while still being a standard Samsung ROM so that's good. Not sure if I'm game to try going back to jellybean now that it's working again.	dugimodo (138)
1301719	2012-09-18 00:15:00	If you do try again, first install clockwork recovery mod fro, the play store and make a full backup. Then if you have problems you can boot into clockwork recovery and just go back to how it was whe the backup was made. Saved my hide when I tried mucking around with my phone.	Nick G (16709)
1301720	2012-09-18 02:31:00	Yeah there's nothing in Odin to *do* a backup. As Nick G mentioned, do everything from ClockworkMod Recovery once it's there. The only time I've ever used Odin is to flash a ROM with CWM included. All ROMs thereafter, do them through CWM (Flashing the .zip). Going between ROM vendors (Such as stock / darkys / CM10) you always need to factory reset. Personally I'd have been more interested to find what was causing the reboots, potentially something Radio / Modem related? What radio version are you running?	Chilling_Silence (9)
1301721	2012-09-18 03:00:00	I did have ClockworkMod on but nowhere in the searches I did about how to fix it did anyone mention using that so I used Odin again. Next time maybe, I still have the CWM file for this ROM version I have no Idea about the radio or where to find it. I kinda expected to have to find that out but everything has worked without me touching the radio. Would it have changed each time I flashed a ROM ? My current Kernal Version is 2.6.35.7-I9000XXJW4-CL1043937 se.infra@SEP-62 #2	dugimodo (138)
1301722	2012-09-18 03:28:00	to boot into clockwork recovery mod, turn the phone off. Start it up by pressing and holding the power, home button, and one of the volume keys. Think for the galaxy s its the vol+ one, but not sure.	Nick G (16709)
1301723	2012-09-18 03:52:00	I did have ClockworkMod on but nowhere in the searches I did about how to fix it did anyone mention using that so I used Odin again. Next time maybe, I still have the CWM file for this ROM version I have no Idea about the radio or where to find it. I kinda expected to have to find that out but everything has worked without me touching the radio. Would it have changed each time I flashed a ROM ? My current Kernal Version is 2.6.35.7-I9000XXJW4-CL1043937 se.infra@SEP-62 #2 Yes, it would have changed. That's your kernel, but not specifically your Radio. It may be called the modem firmware version? Something along those lines, it's been a while. I presume you're on Vodafone / 2Degrees?	Chilling_Silence (9)
1301724	2012-09-18 03:54:00	The behaviour you experienced is consistent with not wiping the Delvik cache or doing a factory set where required. I had a similar problem when fixing a water damaged i9100 with a friend, it would bootloop and we were unable to get the stock ROM on (failed with errors relating to dbdata.rfs, when flashing a stock ROM make sure it is a complete ROM, IE contains all the .rfs images for an in install instead of a partial update. We had to flash back to stock to correct a problem with the efs folder :p he mucked around with it without a backup :p So what fixed it for us was: Flash stock using ODIN Flash dbdata.rfs with ODIN Boot... All running normal and stable Flash CWM and ROOT Kernel Boot CWM and Wipe ALL cache Install Custom ROM + Wipe Cache + Fix permissions DONE Now this seems a bit lengthy but we wanted to be PERFECTLY sure that what we were doing was gonna be right this time!! I had a weird issue with AOKP for i9100 where it worked fine 3+ weeks then randomly crashed + booted and crashed etc. Then the nvdata.bin must have got corrupted or something because it network locked itself and was asking for SIM PASS. Nothing would generate a key to unlock so I had to manually patch the nvdata.bin file :p Took a lot of sorting because I had no idea what was going on and had to start from scratch troubleshooting. IMO with custom ROM's there can be some fun/tears but if you find a nice stable ROM and stick with it (ICS is probably more stable than JB at this stage) then you'll be sweet. Most devices only get updates per year, think iOS so stay with ICS for a while. Keep up to date within the ROM disto then move over to a stable JB build when you think it looks stable enough for you. Happy flashing!	The Error Guy (14052)
1301725	2012-09-18 04:29:00	Yep SkodaFone Nothing in the phone info mentions the modem or radio. Now that it's stable again I may just leave it be, Jelly bean was good to look at and pretty smooth but I don't think it really does anything better than gingerbread on my phone to be honest. Also I kinda like the samsung supplied Video and music players which don't seem to be available on the app store and my Onkyo remote app keep stalling. Come to think of it the Onkyo app is the last thing I was playing with before the problems started. It's a really nice app, gives you full remote control of the receiver and allows you to stream any music on the phone over wireless - I think it's using DLNA. On the helly bean ROM the music kept stopping after one or two tracks. My tablet running ICS works perfectly with it, and so does the phone with Stock gingerbread.	dugimodo (138)
1 2 3