Hi,
I have my captivate for 1 years and I had no problem with signal and multiple rom. Monday, I wanted to install a new custom rom on 2.3 (I was on a 2.2 rom before), but I had some trouble installing it. After multiple hour of trying to install I was finally able to use it, but it was not able to connect to the mobile network
I tought maybe the 2.3 rom doesn't work so I used the stock rom odin3 one click to put it back in 2.1 : http://forum.xda-developers.com/showthread.php?t=731989
Still everyting was working except it wasn't able to connect to the mobile network ...
So I decied to try cognition.
I installed the 2.3.3 stock still not working http://forum.xda-developers.com/showthread.php?t=1127249
After cognition also not working. http://forum.xda-developers.com/showthread.php?t=1127578
There is 1 place that I got signal but it was very low (only 1 bar) when before I had signal everywhere in my city ...
I will now try to go back to Serendipity (i think I was on this rom before monday) but now I have the gingerbread bootloading, do I need to put someting else or when I will flash the serendipity it will remove it??
http://serendipity7.weebly.com/download.html
or maybe if I can install a differend baseband version? But I don't understand what baseband is compatible with wich rom ...
Now I'm on Firmware version: 2.3.3 Baseband version: I897UCKF1 Kernel version: 2.6.35.7-I897UCKF1-CL273832 Build: Cognition v2
thank you for reading and helping
Install a Gb Rom Try a different modem.
I played around alot with I9000 roms but could never really find a compatible modem (low volume, less than normal signal). Finally went back to I897 specific Roms with Cog5 (GB). Back to very good volume and signal but couldn't tether so I just flashed DLEVROM v5 (http://forum.xda-developers.com/showthread.php?t=1146176) and except for a slight in call volume reduction it seems very good so far. Best yet, since Cog5 had GB bootloaders already, I just wiped data/factory reset and wiped cache, installed DLEVROM from zip and it fired right up!
It's been problem free as I've been playing with it today. Bootloaders can mess things up so since you already have GB bootloader try DLEV after a full wipe. It loads rom, kernel, and modem for I897.
Anything else, just read the OP for the ROM of your choice and follow it exactly. If Serendipity uses Captivate or I9000 GB bootloaders it should work the same.
Any one else have other suggestions....
well i tryed serendipity VII and still no service ... (except the very one place ...)
now I just installed Dlevrom v5 ... same thing ... no service
Now i'm on the firmware 2.3.4
baseband I9000UGKC1
rkkaranrk: GB stock rom and after I use CWM to update with different modem?
in this post? http://forum.xda-developers.com/showthread.php?t=876391
The reason I left the I9000 ROMs (Darky JVR) was because out of the blue I lost all signal. I soft bricked it trying to change a couple of things. Ended of OneClicking all the way back to Eclair. After everything was back to normal I flashed Cog5v2 then straight to DLEV (liking DLEV ALOT!).
Might be other things to try but I find it easier to start from scratch because I don't have alot of "customizing" to redo when I change ROMs. I can't much help with the small things to try first.
Sorry....it's all I got.
still not resolve
I tryed lot of roms and now I'm back with stock 2.1 with the one click http://forum.xda-developers.com/showthread.php?t=731989 and I have no service
anyone have an idea how to solve?
where is the antenna of the phone?
I did the secret code: *#1234#
it says the version installed on the phone:
PDA: I9000XWJS7
Phone: I9000UGJK4
CSC: I897ATTJF6
Is it normal that I have different version I897 with I9000 ?
Use this link and follow these directions to get back to ATT stock.
http://forum.xda-developers.com/showthread.php?t=731989&highlight=odin+1+click
Ensure you use the file in the link, this will set you back to stock and probably fix your issue, you will then need to root your phone again
I've had the same issue but one click back to eclair has always fixed the issue. Did you flash then try a master clear. You may want to try the newer 2.3.4 Captivate ROMs. I've had better signal that the I9000 ROMs.
I solved this problem before by changing to KH3 rom!
Now the signal is really better than before!
I did the stock rom and master clear 2 times. I did it again and still no service
Now I have this
PDA: I897UCJF6
Phone: I897UCJF6
CSC: I897ATTJF6
Related
I am in a pickle here. I want to try this as my first custom ROM made especially for bell users.
http://forum.xda-developers.com/showthread.php?t=846237
However I am on froyo with JK3 which has a 3e recovery console. Several threads on the board point me to this kernel to enable 2e recovery console which is required for this custom ROM install.
http://forum.xda-developers.com/showthread.php?t=788108
However it doesnt appear to me that this can be used by jk3 users. I am really new to this and have spent several hours reading. Am I wrong or am i missing something ?
My phone reads as follows:
PDA: I9000UGJK3
PHONE: I9000UGJK3
CSC: I90000BMCJK3
FIRMWARE VERSION 2.2
KERNAL VERSION 2.6.32.9 [email protected] #1
Any help would be much appreciated. I have read over 200 pages on the forum tonight alone and I am stuck
Thx
A lot of people have been there You have 2 options:
1) Flash an older firmware known to use 2e. The easiest thing to do is probably flash JH2 using Odin. JH2 was the last 2.1 official firmware for Bell. Get it from samfirmware.com
2) Flash a kernel that allows you to run clockwork. Check this post of mine where I installed SpeedMod on JK3.
http://forum.xda-developers.com/showpost.php?p=9777680&postcount=53
I don't know what others would say but it might be better for your app data to stay with Froyo 2.2. In that case, go with option 2. Be sure to backup your data just in case
Good luck with that ROM. On my phone, I'm running his Doc RomMOD v2 (JPU) and it's great!
what am I missing ? I thought that if you have jk3 on your phone you could only apply jk3 roms and kernels? is that incorrect ?
Some, kernels and root solutions are not compatible with all firmwares. If you're not concerned with data loss, I believe you can flash any firmware you want (ignoring device specific requirements).
The options I described above are ones that worked for me.
I have a I9000t on CellularOne (MTPCS). It's original firmware was I9000tubjg5. I updated to Darky's 9.0.3 and it worked great. However the Wifi would not work. So, I told it to do a factory reset, and this bricked it. So next I used Odin to put a stock 2.1 firmware on it from the XDA forums. This worked, but then I could not connect to CellularOne, only roaming with T-Mobile. I then tried Darky's 8.0, then stock 2.2, and now back on stock 2.1. Does anyone have an idea to fix it back to CellularOne(MTPCS)?
I guess the experts on here don't have a clue about my problem.
clyfe said:
I guess the experts on here don't have a clue about my problem.
Click to expand...
Click to collapse
More like you are in to much of a hurry .
Your problem is you installed Darkys rom it broke something and you compounded the problem by further upgrades .
Take it back to a clean install using Odin Block 2 method .
http://forum.xda-developers.com/showthread.php?t=818556
I presume you set your network up manually and you may well have to do it again .If their is no CSC file for your network .
In which case i would personally use Odin to update to Eclair 2.1 and then use Kies for the official update and back up that rom .
jje
I'm also on MTPCS, and i used Darky's procedure from v5 to install. That included an ODIN to 2.1 with clockwork and some other reflashes.
Your best bet is to odin back to 2.1 factory, then start from there. It will take a while, but Darky has the best roms I've seen so far.
Thanks everyone for the info. Nothing worked. I called CellOne and got a replacement. Guess What? The replacement is an I9000 with 2.2.1 preinstalled! Firmware I9000XXJPU.
OK, so I've been reading guides, FAQs, how-tos, and various forum posts, and thought I had a pretty good handle on how to flash FW to this machine. So, last night I backed up everything important, and downloaded from here ( http://forum.xda-developers.com/showthread.php?t=1102881 ) the following:
2.2 UGKC1/UGKC1/BMCKC1/Sbl. This is the stock FW as currently installed on my I9000M from upgrading through Kies.
2.2.1 XWJS8/XXJPY/OXXJS5 (MultiCSC) (no sbl)
So just as a sanity test I first tried flashing the UGKC1 PDA file over to my I9000M using Odin. This worked as expected, since it's the same kernel.
Next, I tried to flash over just the XXJPY PDA file over to my I9000, using Odin. No re-partition, no PIT, no modem or CSC. No go - it just repeatedly displays the GT-I9000M screen and never boots the kernel. Couldn't get into recovery mode from this state, but was able to access 3-button download mode.
So, tried flashing over the 2.2.1 XXJPY PDA, Phone and CSC files. Same as before - no actual boot.
I flashed it back to the 2.2 UGKC1 PDA, phone and CSC files, and did a factory data reset and cache clear, and everything was fine running 2.2 again.
From reading here it appears that others have successfully installed 2.2.1 or even 2.3.x kernels on Bell Canada GT-I9000M phones. So, what important step did I miss?
Do I need to re-partitiion? Do I need to use a 2.2.1 FW that includes the boot loader?
For now I'm OK running 2.2, but would eventually really like to be on 2.3.x and don't want to wait for Samsung to make 2.3.x (what happened to 2.2.1) available to GT-I9000M phones. I'll leave it alone for now as I'm going on vacation in a couple of weeks and don't want a hosed phone.
What happens if you flash just a kernel like CF root or speedmod? My only other thought is to redownload jpy and try again as maybe the download was corrupted.
Also with another kernel like speedmod you could download and install a custom rom on cwm (clockwork mod) via recovery that is 2.2.1
I've had some problems with 2.3.4 (never tried 2.3.3) so I am back on Froyo for a bit until things get sorted out a bit more.
G
I don't know if there is a suitable version of CF Root for the UGKC1 firmware - they mostly seem to be oriented to the more international versions. As usual, in Canada we get something a little weird. Don't know about speedmod.
I don't think there should have been any problem with the downloads, as the files themselves are in md5 format, which means they are getting verified by Odin 1.8 when it goes to use them, as I understand it. If they were corrupted Odin should complain about it.
With the announcement ( http://forum.xda-developers.com/showthread.php?t=1158492 ) that Gingerbread is supposed to get an official release to Bell phones soon (which mine originally was), I might just let this lie, for now.
There is a gentleman on youtube by the name of AndroidGalaxyS (original, I know) that has some excellent and detailed walkthroughs and reviews of various ROMs for the I9000M.
youtube.com/user/AndroidGalaxyS
Specifically in your case, you'll want to watch this one that shows how to install 2.3.4 JVP:
youtube.com/watch?v=cLXQn0gOBuA&feature=feedu
Good luck.
I agree that the source maybe lacking. I just found out that the JL2 firmware from samfirmware.com is missing db_data file so I would always get an error after flashing that. KC1 would also not always boot for me so it might be missing something too.
That said what are you trying to accomplish? If you are just trying to go to another stock rom I'd just leave it and put a custom kernel on to give you root and CWM recovery.
Most any other Froyo rom is flashable from CWM in recovery and you do not need to worry about odin except to recover from bad things and it looks like you can do that. Gingerbread is different because they changed the bootloaders and that means Odin.
Of course its getting harder to dig back and find those Froyo roms since the rest of the i9000 world has been on GB for a while.
G
Thanks for the replies, so far. Mostly I was just experimenting, and trying out XXJPY was just a first step in my experimentation before moving on to GB. Part of the reason for this is that it seems like a lot of the modified kernels and so on are meant to be flashed over certain versions of the firmware, and those versions don't include the Bell/Virgin-specific ones. Or maybe I've misunderstood how this stuff works.
Yes, while my attempts to install XXJPY have been a complete failure, even when re-partitioning with a PIT file, when I re-flashed back to the stock UGKC1 FW everything was fine.
At this point I'm just trying to get a better understanding of where this went wrong. I've never specifically updated the SBL - the JPY package I installed didn't include it, and I didn't check off the "Update boot loader" box when re-installing KC1.
I've seen a number of posts here from people who updated I9000Ms to other FW, but unfortunately they don't seem to have detailed exactly where they started from, or exactly what they installed, or how.
Hi all, so I recently sent in my I9000M Bell Vibrant to the service centre in Montreal to get it fixed (it had a fried internal SD) and they sent it back to me with a replaced motherboard (that's what I'm assuming because the phone's mac address changed and the internal SD is in working order now) but as a result the phone is no longer unlocked, which is a problem because I'm not with Bell.
They shipped the phone back to me with 2.3.3 installed, kernal version 2.6.35.7-I9000UGKG3 and I was wondering if anyone could help me root this thing so I can get it unlocked. I looked around the forum and tried SuperOneClick which didn't work and was unsure of where to go from there.
Any help would be greatly appreciated, thanks!
try flashing one of the kernels designed to install root e.g. Chainfire's kernel (basically stock plus root)or Hardcore's kernel (custom kernel but very robust) -- as you are on KG3 you will need a kernel designed for 2.3.3, not one for jvr or jvs.
Both CF and HC are very good at listing all their kernel variants with the right number of the firmware.
Flash using Odin with the kernel as pda, HC especially has some some clear instructions posted. It will leave you on KG3 stock rom and CSC.
You can also jump some steps, flash stock JVR as pda, leaving your KG3 modem and CSC in place, then flash a more recent JVR 2.3.4 version of either the HC or CF kernel or one like Damian's if you want to move further away from stock.
There are some further questions and answers in the thread on KG3 -- Bell users finally got a GB modem but not the latest GB firmware yet. Some have chosen to customize and go with thelatest firmware, some just wanted to root and stay on stock KG3.
adslee said:
Hi all, so I recently sent in my I9000M Bell Vibrant to the service centre in Montreal to get it fixed (it had a fried internal SD) and they sent it back to me with a replaced motherboard (that's what I'm assuming because the phone's mac address changed and the internal SD is in working order now) but as a result the phone is no longer unlocked, which is a problem because I'm not with Bell.
They shipped the phone back to me with 2.3.3 installed, kernal version 2.6.35.7-I9000UGKG3 and I was wondering if anyone could help me root this thing so I can get it unlocked. I looked around the forum and tried SuperOneClick which didn't work and was unsure of where to go from there.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
hi did you ever figure out how to root this? i'm tryign to figure it out too
I have the same question.
I have the same question. All I really want to do is root the phone and keep the stock GKG3 kernel. However, I can't find a tool that works on the Bell i9000m running this 2.3.3 version of Android.
I've tried superoneclick and the Gingerbreak tool from Chainfire but nothing works.
Is the only way to root this to update the kernel? I was looking at the CF-ROOT downloads and not sure which one I would use if I used this option.
Kernel
thanks igsshedden. I found Hardcores kernel for the i9000m here
http://forum.xda-developers.com/showthread.php?t=822756
Updated Oct 27:
Found this method to update the I9000M http://blog.brahm.ca/2011/08/install-android-233-with-root-on.html
Will try and post my results.
Think it was cf-root 3.7 kernel that I flashed with Odin to get root then from there tried a bunch of roms now I'm using what's in my Sig and its wicked
Daily I9000M
Powered by
Semaphore 2.9.0s
Live OC 114%
Smartass V2, Smooth Ui
Running
SlimBean 4.2.1 Beta 1
Torlugic said:
Think it was cf-root 3.7 kernel that I flashed with Odin to get root then from there tried a bunch of roms now I'm using what's in my Sig and its wicked
I flashed stock jvp gingerbread with odin so the phone became an i9000, instead of i9000m then you can flash a rooted rom,I then used Galaxy S Unlock from the market to unlock. took a lot of figuring but it worked. good luck
Click to expand...
Click to collapse
I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by @BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
dawgdoc said:
I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
Click to expand...
Click to collapse
1: don't need to flash cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flashing stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
BWolf56 said:
1: don't need to flag cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flagging stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
Click to expand...
Click to collapse
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
dawgdoc said:
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
Click to expand...
Click to collapse
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
BWolf56 said:
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
Click to expand...
Click to collapse
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
dawgdoc said:
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
Click to expand...
Click to collapse
While it's an old device, it's really great and some of us keep supporting it
Mixed Results with increased understanding
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
dawgdoc said:
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
Click to expand...
Click to collapse
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
BWolf56 said:
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
Click to expand...
Click to collapse
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
dawgdoc said:
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
Click to expand...
Click to collapse
BT not working can be cause it wasn't updated in so long or kernel issue. Or could simply be that it doesn't work with your specific devices.
I flashed mine off stock KK4 (same one you flashed), tried to boot without flashing it twice, which of course didn't work but then went back in recovery, re-flashed and it booted just fine.