Related
Hello,
I have a unlocked and rooted Captivate. Recently in installed OCLF Lag Fix and did "OneClickLagFix V2+". It is safe to update to android 2.2 from 2.1? If yes, then what is the best way?
Thanks in advance.
Just disable lagfix and flash any custom 2.2 ROM you want inside CWM.
Sent from my SAMSUNG-SGH-I897
Reamer09 said:
Just disable lagfix and flash any custom 2.2 ROM you want inside CWM.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
Thansk for the reply. I will do it tomorrow. I am new to android, I hope all goes well. Will update my results.
OCLF is so 2k10
*If you're not on Gingerbread, you should be shot*
Don't forget to remove the ext2 tools after disabling lagfix.
cappysw10 said:
OCLF is so 2k10
*If you're not on Gingerbread, you should be shot*
Click to expand...
Click to collapse
The only time my phone has ever been on lagfix is when the ROM I flash comes with it. I really don't see any difference at all in performance with or without it. The only reason I'm not on GB is because I had TONS of problems with apps working and got fed up with it. If my signature still says KF1 then its old. I'm on XDA app so I can't tell.
Hello All, Finally I updated my Captiavte with Andriod 2.2 few days ago. I was not able to do that before because of some issues."
I un-lagfix my mobile and used Odin3 v1.0 to flash "I897UCKB1-homeBinary.tar ROM...
I feel now that my mobile is slower then before... But got some new features.
Can anyone tell me difference between "I897UCKB1-homeBinary.tar" and ''I896UXJL1-stock"?
hno866 said:
Hello All, Finally I updated my Captiavte with Andriod 2.2 few days ago. I was not able to do that before because of some issues."
I un-lagfix my mobile and used Odin3 v1.0 to flash "I897UCKB1-homeBinary.tar ROM...
I feel now that my mobile is slower then before... But got some new features.
Can anyone tell me difference between "I897UCKB1-homeBinary.tar" and ''I896UXJL1-stock"?
Click to expand...
Click to collapse
Look at the first
4 letters. I896 is a canadian Captivate. No idea what jl1 is (2.1 or 2.2).
Hello All,
I applied lagfix on my android 2.2 OS and wow!!! speed is now 200% increased!!!!
Is 2.3 available for captivate ?
Many flavors of 2.3, just be sure to read the installation instructions and understand GB bootloaders before trying.
2.1 to 2.2 to Black Screen to Semi brick to Working Captivate...
Hello All,
I had some heck of the experiences in last 2 weeks which I would like to share.
-> I had successfully updated my captivate from Android 2.1 to 2.2. Using "I897UCKB1-homeBinary.tar" ROM from BriefMobile site. After this update my three button combo for entering recovery mode stopped working. I could only go into downloading and recovery mode by using Android SDK.
-> And as written in my earlier post, I felt that speed is slow so i "lagfix"-ed it. This gave very good results and all was working fine...
-> Until one day... I was installing blik calendar widget after downloading it from site(I don't remember link now)... This installation never ended, it was continuing even after 15 mins so I used Task Killer to kill the installation... After that it became very slow... I restarted the mobile and what the hell!!!! mobile was stuck at boot screen... Mobile was stuck at "S" logo.
-> I tried all the combos I could find on net to enter into downloading mode but none work. Computer was not recognizing captivate while it was stuck as S logo.
-> After few days I used USB JIG method to bring my captivate into downloading mode.
-> Tried to flash earlier installed ROM "I897UCKB1" via Odin 3. It was successful but now after boot animation I was getting black screen. Lights on button were glowing on pressing and mobile was vibrating but ... It was in useless state.
-> Tried to flash "I896UXJI2" ROM, same condition as above.
-> Then I tried to Flash "I897UCJF6-final-OCD-REV0.zip" downloaded from xda... with repartition option checked. It stucked in between and i had to remove battery.
-> Now mobile was in Semi Brick state.
-> All this time mobile was "lagfix"
-> Then somehow I got back my captivate using :
http://forum.xda-developers.com/showpost.php?p=7614957&postcount=6
-> Now captivate is working find but still 3 button combo is not working...
Which ROM should I use now to upgrade to for 2.2?
Is custom ROM better? Cognition !!!
Should I install ClockworkMod Recovery?
Which ROM should I use now to upgrade to for 2.2?
Is custom ROM better? Cognition !!!
Should I install ClockworkMod Recovery?
Click to expand...
Click to collapse
First, if you are at stock 2.1 eclair, you can use the 3-button odin one-click. As long as you have the eclair/froyo bootloaders, that will work properly. But for the love of all that is sacred and captivatible, make 100000000% sure you have the proper bootloaders first. Flash back to stock eclair if necessary to make sure of this. I cannot stress this enough. If you do not have the eclair/froyo bootloaders in place before using the 3-button fix, you will murder your phone. It will die, and you will most likely have to pay real money to get it fixed. Make sure you have the eclair/froyo bootloaders before using the 3-button fix.
(Sorry. I just wanted to make sure that you avoid an all-too-common issue on the board.)
What may be a better option for you would be to upgrade to Gingerbread. Part of that upgrade process will flash the GB bootloaders, which will automatically have your button combinations fixed.
In either case, there is some level of bootloader flashing involved, which does mean some level of risk - make sure to read up on it thoroughly before you do anything.
And custom roms, in my opinion, are always better than stock. Clockworkmod Recovery is something you'll definitely want to have (and is usually included in the kernels that you'll flash along with custom rom upgrades).
hno866 said:
Hello All,
I applied lagfix on my android 2.2 OS and wow!!! speed is now 200% increased!!!!
Is 2.3 available for captivate ?
Click to expand...
Click to collapse
There are several roms that I897 GB based right now.
Like Atomic Fusion 1.5 and Cog v2, both are awesome roms.
Both will be developed even further, when source comes out! (The Official 2.3 update from ATT)
Ok I decided to root my phone. Now all hell has broken loose.
I had a working xxjvr working on my phone. All was well. So I decided to root the phone as per all the hype.
Following instructions to the letter, I proceeded. It failed. Some error message. I restarted the whole procedure and same thing. Now I get a little PC connection icon.
Toiok out battery. Managed to get into download mode, I think that is a good thing at least, and Reflashed the phone. Now it gets stuck at firmware update start. boot.bin and just hangs. No progress. Ive retried this 3x.
HELP I hope its not bricked now all cause of a damn root attempt.
I can get into download mode but NOT recovery mode. I thought I could at least clear the cache but attempting recovery mode and the yellow exclamation connction to pc just flashes back.
As long as you can go to the download mode, you have no brick. Just flash the stock JVQ (not the KIES variant) with PIT + repartition.
Edit: Can't find the thread, but the link was
http://www.multiupload.com/20DJFPXKL3
Edit2: A good, non-overloaded root kernel for JVQ is here (and on the next page for JVR also):
http://www.handy-faq.de/forum/samsu...36-kernel_ohne_schickschnack.html#post1580443
(Post #19) I use it with no issues and misbehaviour so far. After download, just rename the file from .tar.zip to .tar and flash it with odin.
I personally use JVQ + this kernel + JVR modem, cause GPS fix is much better with the JVR modem.
Ok Finally after 8 attempts it went through. One of the attempts was a locked green screen. Ugh.
Now im freaked about rooting the phone despite all the hype and i wanted to apply the lagfix.
So now the one that worked is xxjvr. Perhaps I should just leave it. Any otherway to fix the lag other than rooting the phone? Im very apprehensive of rooting now.
You may find your Bootloader is messed up i have had this on loads of Gingerbread phones.
To Fix you need a Three file flash to Froyo with repartion ticked JPO Or JPU will do then Flash JPY then Flash 2.3.4 JVQ again this puts the Gingerbread bootloader back on
I flash JPY then let Kies do the rest Yes i no!!!! Kies But i no then i have a stock Bootloader on.
Flashing Froyo removes the bootloader and puts the old froyo bootloader back on also removes root as well
Make sure the first Gingerbread Rom is stock not a Light version
Then your ready to start all over again
Oh and Buy a Jig from ebay safer to have one then not
Yes, flashing JVR reportedly may run into this. Read this here and in the other forum. Never had this with JVQ or any other firmware. I went back to JVQ.
And even if you see this little PC connection icon, nothing is lost. This normally appears, when ODIN initiated flashing, but did not finish.
Edit: just read this after i posted:
then Flash 2.3.3 JVQ again
Click to expand...
Click to collapse
This is confusing:
JVO is 2.3.3
JVQ is 2.3.4
just to make this clear
EditEdit: OK, you edited your post... now it says
then Flash 2.3.3 JVO again
Click to expand...
Click to collapse
SnoopyDog said:
Yes, flashing JVR reportedly may run into this. Read this here and in the other forum. Never had this with JVQ or any other firmware. I went back to JVQ.
And even if you see this little PC connection icon, nothing is lost. This normally appears, when ODIN initiated flashing, but did not finish.
Edit: just read this after i posted:
This is confusing:
JVO is 2.3.3
JVQ is 2.3.4
just to make this clear
EditEdit: OK, you edited your post... now it says
Click to expand...
Click to collapse
Fixed sorry for confusion to much Beer last night
Hehe, no problem
Sounds like you are all suggesting i go and flash back to JVQ. Can a flash be done at same time while rooting the phone in the process?
Otherwise Ill jusst keep it simple.
Right now everything is working JVR but there is noticeable lag whereas before lag wouldnt occur until months of usage.
Albeit the Quadrant standard benchmark yields me 1381 which isnt bad for a stock rom.
Hightower68 said:
Sounds like you are all suggesting i go and flash back to JVQ. Can a flash be done at same time while rooting the phone in the process?
Otherwise Ill jusst keep it simple.
Right now everything is working JVR but there is noticeable lag whereas before lag wouldnt occur until months of usage.
Albeit the Quadrant standard benchmark yields me 1381 which isnt bad for a stock rom.
Click to expand...
Click to collapse
I would first take it to stock first you can flash Darkeys resurrection edition After JVO That Routs for you Puts CWM on as well I put this on if a customer wants his phone setting up for a custom rom Its painless through odin
Its just the Gingerbread bootloader its a pain
And its a Case of Rolling it back to go forward again make sure you charge your battery up to 100% to avoid and battery glitches later
Hello, I am currently on Miui but I want to flash official Rogers 2.3.3 to get Rogers bootloaders, as i hate flashing AT&T stuff when I don't have an AT&T phone. What is the safest way to return to either 2.1 or 2.2? I have tried returning to stock from an i9000 based rom a long time ago, and ended up bricking so I'm very careful and kinda scared to do it again since I haven't flashed in a while lol I do have a jig now in case things get hairy, but I'd rather be safe then sorry. I do have Heimdall 1.3.0 and a Rogers 2.2 package with everything included, should i just use that?
Use the Rogers package and flash. You don't really have a choice since to go back from CM7 or MIUI you need to repartition your phone.
use the stock roms in my signature. herehttp://bit.ly/eqg4W2
because your are coming from miui / cm7 it is recomended to flash the att one click first then the rogers stock roms
i was on miui for 3 hours yesterday. i HATED it. buggy and iphone phanboy bs.
but i did a nandroid backup before flashing miui, that i restored after by flashing ATT one click, rogers 2.2, talon kernel, then my nandroid backup.
Last time I tried to get off the i9000 rom's I used the at&t one click, and it bricked my phone, it would show an at&t screen for a few seconds and then it would shut off and keep doing that, but I had no download mode or anything, the Heimdall package has the bootloaders and everything in it, isn't it safe just to use that?
Sent from my Miui Cappy with XDA Premium
ive never used heimdall never needed to.
if you had no download mode last time then how is it working now?
it works. everyone has done it. i did it twice yesterday.
ATT one click, 2.2 rogers with odin, flash custom kernel with odin, boot into kernels built in CWM, flash new rom. done,.
Well i ended up making my own jig to get it into download mode and then tried to flash to stock, and my phone's screen turned green, and stayed like that for a while, so I unplugged, pulled the battery, tried it again and it was hardbricked, as in the jig didn't work and nothing else did either, so I sent it into rogers for repair. Plus my phone is a 1010 model, which is why it doesn't play well if the AT&T one click. I don't want to use that. Why must i use odin? does Heimdall not do the exact same thing?
i updated from froyo to 2.3.5 kk4 gingerbread.rooted per instructions.
got root and all but when i turn on wifi it hangs then turns its self off.
in the instructions it says to reflash the kk4 kernel but when i do that i loose root.
i think im missing something when rooting. any help would be greatly apprec...
(not hijacking, you're just not alone)
I dusted off ye' olde Captivate and flashed from Cognition to stock Eclair, up to stock Froyo--> Gingerbread using Odin and Kies(respectively). I followed the KK4 kernel Root using Odin with "I897UCKF1-AutoRoot-DesignGears"(cant post links yet) to the "T". I DO have root, however do NOT have WIFI same as OP. My other car is a Thrill. So I'm not using Captivate for communication, But without WIFI, it's rendered useless. After you enable WIFI, it takes a bit to initiate then searches for networks, then shuts down. I tried to add mine manually but was told I was "Unable to save" it.
Kinda found a fix.
I searched and found an Odin 1 click which takes us back to 2.3.3. Then I flashed the Kernel using Odin as we did before and voila, root, and my WIFI functions. I am happy with 2.3.3 and root rather than the headache of fooling with it any more.
If you want, PM me...this forum won't let me post links yet
SAme problem here
Moving this over from the General. Bad poster...
The other day, I got a text from AT&T indicating that an official 2.3.5 kernel was available for my Captivate. Great, so I fire up Kies mini and install it over my rooted stock 2.2.
Update goes well, I have Gingerbread. All of my apps remain in place. Re-root (SuperOneClick) and my Titanium Backup works like a charm. (edit: Maybe SOC did it, not sure. It hung on step 6 thinking back, but I'm rooted currently. Could root have survived through the Kies update?)
However, I can't get my WiFi to connect to save my life. It scans for about 15 seconds then shuts back off. I can't even enter WiFi settings manually, because it shuts off and "fail to save" the settings.
IS anyone else having issues with WiFi on the AT&T stock Gingerbread kernel? (No, I don't feel the need to upgrade, since I just want to be able to use TiBU) I'm also having the dreaded "tetheringmanager" issue and a factory reset didn't help
That's exactly what happened to me other than not having rooted 2.2. WIFI worked with 2.3.5 before odin root of KK4. I went back to 2.3.3 and then rooted. Still Gingerbread and now fully functional.
Search for wifi manager in the market. I had the same problem, was using THS ICS at the time, but my situation was the same as you are all describing. It saved my wifi locations and never failed me. Give it a try.
when you tell someone something, it depends on what part of the united states you're standing in as to just how dumb you are--- Burt Reynolds
i actually tried wifi manager. it still would not connect or find any networks for me.
How very strange......
when you tell someone something, it depends on what part of the united states you're standing in as to just how dumb you are--- Burt Reynolds
This happened to me when I went from stock 2.2 to stock 2.3.5 using mini Kies and the offical ATT release. I then rooted my device using "DesignGears-AutoRoot" however this kernel breaks wifi...You'll need to reflash the stock KK4 kernel (you'll lose root) if you want your wifi back. I then found this thread explaining in detail what I went through:
http://forum.xda-developers.com/showthread.php?t=1444382
You'll have to wait until a stable rooted kernel for KK4 is released... :-/
Did you guys try one of these kernels?
http://forum.xda-developers.com/showthread.php?t=1294477
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.