Database Develop

[Q] Bell i9000m - Froyo

Hi,
Has anyone been using froyo (JPK, JPM) on the i9000m (Bell version only) for more than 20 days without issues.
If so what is the batch number on the sticker under your IMEI. 08/10, 09/10 etc...
The reason I ask is coz bell swapped my phone due to SD issue and I donot want to rebrick it.
Thanks

Same here, sd problem with JPK but cant tell S/N since phone got swapped.
Also looking foward for a froyo that do not mess with internal sd

Your problem is not Froyo. Internal SD issues are unrelated to firmware.
Any Froyo + Bell modem works just fine. There are other modems with 850 support that work just fine too.

rdenis said:
Your problem is not Froyo. Internal SD issues are unrelated to firmware.
Any Froyo + Bell modem works just fine. There are other modems with 850 support that work just fine too.
Click to expand...
Click to collapse
My SD dissapears once in a while - i just reboot it and it comes back
is this happening to everyone ?

I had an issue where I restarted my phone and everything was erased. The SD card was still recognized. I had to reflash my phone with Odin to get it to work again though. Even the factory reset in the boot menu wasn't doing anything. I think it had something to do with the OCLF.
I've been using it for about 15 days or so now without OCLF and everything works fine.

Just wondering if there's a video on how to install Froyo on the i9000m. All these posts about corrupted internal SD is making wonder if it's worth upgrading to Froyo since it looks like it's pretty risky. Worse is I'm a noob and I've got a bad feeling about doing it myself without any help from a video.
Thanks

juinny said:
Just wondering if there's a video on how to install Froyo on the i9000m. All these posts about corrupted internal SD is making wonder if it's worth upgrading to Froyo since it looks like it's pretty risky. Worse is I'm a noob and I've got a bad feeling about doing it myself without any help from a video.
Thanks
Click to expand...
Click to collapse
If it makes you feel any better, my i9000m corrupted itself, despite not having been rooted, not running any lag-fix and running the same ROM out of the box...I managed to save it by combining a bunch of tips I found for people recovering from a bad flash.

mattomatic said:
If it makes you feel any better, my i9000m corrupted itself, despite not having been rooted, not running any lag-fix and running the same ROM out of the box...I managed to save it by combining a bunch of tips I found for people recovering from a bad flash.
Click to expand...
Click to collapse
Okay. So you're saying the phone itself is just badly manufactured? I was really hoping that froyo will fix all this awful things. I'm also having trouble connecting to Kies. Is Froyo for the i9000m out on Kies yet?

Hey,
Ive been running froyo stable on an i9000m for a month now using the kies reg. hack that was available a couple of weeks ago. Have had 0 problems.

This I9000M SD thing is a hardware issue. If you have a phone from a bad batch, you'll eventually succumb to the SD card issue regardless of what firmware you decide to use. People have even experienced this without ever flashing/modding anything. If you have a good phone, froyo or any other firmware for that matter will be fine.

The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Also shouldn't there be a recall if this is happening to so many people?
Sent from my GT-I9000M

MaestroSeven said:
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Click to expand...
Click to collapse
i too bought mine on launch day, and i just sent it in for repair last week, so don't count it "safe" just yet.

MaestroSeven said:
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Also shouldn't there be a recall if this is happening to so many people?
Sent from my GT-I9000M
Click to expand...
Click to collapse
I bought mine in early August on launch weekend, and my SD card died this past weekend, even though I had never flashed any new roms.
I had to send it in for repairs.

kmkarim said:
Hey,
Ive been running froyo stable on an i9000m for a month now using the kies reg. hack that was available a couple of weeks ago. Have had 0 problems.
Click to expand...
Click to collapse
What registry hack ?
do you NEED to do a registry hack to get the official 2.2 froyo on your bell i9000m ?
if so, why ?
shouldn't we be able to upgrade officially without having to resort to hacks ?
or are you using this hack in the case that the official upgrade isn't out yet ?

15 days with doc's rom with lagfix ext4 no rfs

Funkadelick said:
What registry hack ?
do you NEED to do a registry hack to get the official 2.2 froyo on your bell i9000m ?
if so, why ?
shouldn't we be able to upgrade officially without having to resort to hacks ?
or are you using this hack in the case that the official upgrade isn't out yet ?
Click to expand...
Click to collapse
Currently there's pre release (dev roms) available via test mode on kies. It is in no way final but still pretty stable

rumy said:
The reason I ask is coz bell swapped my phone due to SD issue and I donot want to rebrick it.
Thanks
Click to expand...
Click to collapse
Just play and re-brick it. If it's going to fail it will fail and there is nothing IMO that you can do about it. If it needs to go in 5 times then so be it. I bought mine on a visa doubling the warranty. My guess is it will be going in at least 5 times unless they "actually" fix the issue which I doubt.

[Q] I9000 SD Card Problem fixed?

I am due to receive a new galaxy s today, after mine bricked in Dec "Damaged Internal SD Card" (recovery had cannot mount /dev/block/mmcblk0p1).
I have not really being watching the threads here since it has been gone, and wanted to know if the general consensus is that JL2 fixed the SD card problem or, it is as I fear, a hardware problem. If it is a hardware problem I will likely sell it and purchase a Desire HD to replace it. Either way I want to run CM7.
If I do keep it, I will likely run a rom from Doc's Kitchen until CM7 is stable, has anyone had any problems with the Internal SD card on replacement devices running a Doc Rom?

it's hardware

Some believe it to be hardware, others believe Bell and Samsung, who have stated that it's software. They go on to say the latest firmware, JL2, contains a new secondary boot loader which apparently fixes the issue.
Flash the SBL and you're free to flash any ROM you want safely.

seeARMS said:
Some believe it to be hardware, others believe Bell and Samsung, who have stated that it's software. They go on to say the latest firmware, JL2, contains a new secondary boot loader which apparently fixes the issue.
Flash the SBL and you're free to flash any ROM you want safely.
Click to expand...
Click to collapse
BTW seeARMS when do u plan to update ur ROM again???

[Q] Sprint Tab with CWM & OC Kernel w/ working Camera & GPS?

I have searched thoroughly through the various CWM and OC Kernel threads but it's not clear to me if I can achieve having ClockworkMod Recovery and an Overclocked Kernel running on a Sprint (CDMA) Tab without any issues with the GPS or Camera.
I am perfectly fine running the stock Samsung ROM, but want to be able to overclock to 1.4GHz and be able to run CWM so that I can at least be able to do nandroid backups. From what I gather some of these CWM solutions and OC kernels (which may be really designed for Verizon Tabs and not Sprint Tabs) may cause issues with the GPS and/or Camera. I cannot afford to lose those two functions of the Tab.
So for those Sprint owners out there, what has worked for you to get a working CWM and OC kernel without sacrificing the GPS and Camera? Thanks!

apparently this isn't possible? it's a shame...as if a CDMA Tab were bad enough, it looks like the Sprint one is the true ugly stepchild of the bunch.

The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.

ad720 said:
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
Click to expand...
Click to collapse
Awesome! So you are using a Sprint Tab? And you can run Google Maps or Navigation and it locks your location using GPS? I just want to be sure before I proceed down this path, since I've read about some users not being able to get their GPS to operate once they've borked it.
And if you don't mind me asking, how did you get the VooDoo CDMA Kernel on there? Did you first install v4 through SGS Kernel Flasher or perhaps Heimdall? And then you installed v5 through CWM?
Thanks!

Yes, Sprint Tab (I just got it from the most recent woot sale).
Google Maps locked to my location within 20 meters inside of my office, and then dead on my front door just now. I turned my WIFI off to make sure it was really the GPS. I started up Navagation and it showed waiting for GPS for a about 2 seconds before starting with the turn by turn.
I have taken pictures with the RF and FF camera but I haven't tried a video chat so that might not work. When I take a picture the preview does glitch out on the screen a bit but the picture is just fine.
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
The issue that I had was my auto-rotation wasn't working. I found the file to replace in the thread but root explorer wasn't recognizing my SD card until I turned off the VooDoo enhancements in CWM and then turned them back on as specified by the troubleshooting section of the OP. At that time I was able to replace the file to restore auto-rotate.
Please keep in mind that while I am not new to Android I am quite new to the SGS so do plenty of reading and keep in mind that this is just my experience (or inexperience) with it and I may just have gotten lucky.
Also, I do NOT have data services through Sprint, I am using WIFI only so I can't speak to the effects of the Kernel on that.
Good luck!

Thats pretty awesome, atleast we have an alternative until Samsung hopefully release the 3.34 for all G tab owners.

ad720 said:
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
Click to expand...
Click to collapse
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?

onlinespending said:
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
Click to expand...
Click to collapse
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.

ad720 said:
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
Click to expand...
Click to collapse
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?

onlinespending said:
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
Click to expand...
Click to collapse
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?

ad720 said:
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
Click to expand...
Click to collapse
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.

The first OTA on my device is downloaded, but not installed, and I'm curious if I should even take them at all?
I currently have the following:
Hardware version: SPH-P100.08
Model number: SPH-P100
Firmware version: 2.2
Baseband version: S100.08 S.DJ29
Kernel version: 2.6.32.9
Build number: SPH-P100.DJ30
I'd like some type of recovery and eventually HC... boy these Sprint tabs, and tabs in general, are funky compared to my Incredible.

onlinespending said:
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
Click to expand...
Click to collapse
That is identical to mine.
I wish I knew more about the tab so I could be a help.

Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.

onlinespending said:
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
Click to expand...
Click to collapse
Maybe a format issue? That's interesting...

I had a similar issue with the 16gb card. put a 2gb card in, and was able to flash the kernel and then get into CWM. sadly once I got that far it didn't seem to matter what rom/kernel i tried it wouldn't boot past the samsung logo anymore. So back to stock rooted for now I guess.. Really want to play with the HC port, but not sure why it won't work. Also can't seem to get Heimdall to recognize my Tab, Odin works fine however.

another new Sprint SGT owner from Woot sale here. Also just flashed the Voodoo OC kernel last night, all seems well camera and GPS etc, I have no idea if 3g works as there is no Sprint in my state.
I flash the V5 using a guide I found over on the unlocker site. took several tries before I got it to go, lots of command line stuff and I think I had a few typos along the way.

Another woot sprint tab user here... I also have "KhasMek Voodoo Plus v5" installed on my tab but GPS does not work for me. Well, it has never worked for me even with stock kernel and EA24 ROM.
Any other woot user with a none working GPS straight out of box?
Update: GPS will not lock if Sprint tab is in airplane mode. Even though by the window works for my HTC hero phone but not the tab. It needs to be outdoor in order to get proper GPS signal.

[Q] Downgrade 2.3.4 to 2.2 or earlier

hello. new to the forum. i've scoured the net for solutions but i haven't found anyt that applied directly to my situation and came here for help.
first off, im a bit new to the android world--being an iphone geek my whole life so here goes.
ive got a htc dream (g1) rooted running 2.3.4
Mod Version is COS-DS i wanted to test out. But i dont care for it and wanted to go back to an earlier version, maybe cyanogen 6.1 but that runs 2.2
i was wondering if it would be as simple as grabbing the 6.1 ROM and flashing it onto my phone from my sd card
my HBOOT version is 1.33.0013d
my Radio version is 2.22.27.08
I had 6.1 on my sd card and flashed the rom because i saw a video of someone else who had the same radio/hboot version as I and it was working so i thought it would be that simple, but when i flashed it i was caught in a bootloop at the G1 Tmobile screen.
Luckily i was able to recover, (i backed up my info using the Clockwork Recovery from Rom Manager)
Any ideas? Any are welcome. And once again my apologies for my blazing noobishness.

CM 6.1 is bootlooping due to your radio/SPL combination. You need a special kernel for this, which needs to be flashed on top on CM 6.1. Terry's kernel from the ezGingerbread thread should worl, I guess.
You can also downgrade your radio/SPL, but I do not suggest so, because you will lose the additional memory provided by that combination.
Sent from my Gingerbread on Dream using XDA App

[Q] Sorry folks - this is probably a dumb question

Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick

nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess

AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2

Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.

Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...

snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium

AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?