Related
Hi,
I have two issues - firstly, three button recovery didn't work on my phone from new. The latest Android upgrade(2.3.3) has enabled it on 3e, but I think that's due to an error in the firmware(Three branded) - it says "can't access to '/system/csc/H3G/system'.'
I'm not getting on at all with Gingerbread(battery sucks, ogg files not playing properly, browser doesn't scroll nicely), and would like to downgrade back to an unbranded 2.2.1. I've been looking around and have grabbed some ROMs, odin, the "Aries_P-SBL" file needed to enable 2e recovery - but I'm also seeing things about updated bootloaders after the Gingerbread update, and I'm not totally confident in what I'm doing.
I'd like to downgrade to "I9000XWJSD", 2.2.1 released May 2011. The handset is Three(UK) branded, but has been SIM-unlocked(using the code provided by Three, and an alternative SIM does work). *#1234# gives PDA as I9000NEJVD, PHONE as I9000NEJV5, and CSC as I9000H£GJV6, with a build date of May 4th 2011. "About phone" gives a Build number of GINGERBREAD.NEJVD, Baseband version I9000NEJV5.
Will I be okay to do the 2e recovery, then the downgrade to the stock Samsung 2.2.1 flash? I have made the USB 3-resistor jig, and that puts me into download mode without a problem.
Sorry it was long-winded! Thanks!
The first thing you have to do is installing a 2.2.1 stock rom with froyo bootloaders(search for it in the forum, you'll find a couple of threads about it.
Very easy very simpel. Hope this will help you out.
Thanks for the reply. So I just drop down to 2.2.1 before thinking about installing the 2e recovery thing? Most things I've read indicate I need to have 2e recovery before flashing...
http://forum.xda-developers.com/showthread.php?t=1102881
On that page, "JSD" comes with bootloaders. Would that be safe to use on my handset?
Also, what is the "PIT" file for, and do I need to mess around with that?
EzBase is a good way of downgrading easily
http://forum.xda-developers.com/showthread.php?t=991792
^That? I shall bookmark it and have a look tonight.
Right, I've read through. The PDF guide for EZbase suggests 2e recovery is needed - how important is this? The guide for installing it suggests I need to root my device and check a string somewhere - but I can't root it using superoneclick, it just hangs.
How do I approach this? I have a working jig here, will that be sufficient to risk the flash without 2e installed? Should I just bite the bullet and go for EZbase 2.2.1, in the hope that I can then root the phone and check for that string?
Anyone, please? I'm technically minded and fairly competent, but as I get my internet through my handset(tethering) I'll be up the creek without a paddle if the phone ends up bricked... I need to be sure I'm not likely to mess things up!
I did it a couple of weeks ago, using this guide:-
http://forum.xda-developers.com/showthread.php?t=1100906
Went down to JPU, then straight to JSD. After gaining confidence by not c*cking it up, I chopped and changed modems a few times. ZSJPG had nice battery life but relatively sluggish/poor data connection and signal strength, so I used the Gingerbread 3UK modem from my last firmware - it works well for me.
Hey guys, first post after a couple days of reading.
I have to apologize for the length of this, but I want to explain a full history, as it seems as this can be very important in many occasions (with existing lagfix, roots, etc). If you just want to skip to my current issue, please scroll to bottom.
I have a GT-I9000m on Sasktel, in Canada, which I was given from a friend after she got the s2.
It was running 2.3.3
Code:
Phone model: GT-I9000HKABMC
Firmware version: 2.3.3
Baseband: I9000UGKG3
Kernel: 2.6.35.7-I9000UGKG3 [email protected] #2
Version number: GINGERBREAD.GKG3
I was having the somewhat-common issue with the phone taking screenshots when i pressed the middle button. I read this was resolved most of the time by a touchkey firmware update.
After doing this, I lost function in both the menu and the back keys.
Since then I tried the battery pull, and factory reset. Now I have read to re-flash to stock firmware, then update touchkey firmware then update kernel in KIES or wherever. I then I play on rooting, and running CWM and having multiple roms if possible.
I have now rooted my phone, in order to install some software to find information about my CSC etc.
My phone is also network unlocked now, as I have done it myself and verified.
So my question is, to follow guides which say to "flash to stock firmware", what to they mean by stock. Just because it's on 2.3.3 since i've known, that doesn't mean it was always on this version. IF i want to reflash with odin, can I just use "I9000UGKG3-homebinary.tar" to flash to 2.3.3, then try to update the touchkey firmware again? Thanks in advance, hope to become a helper guru one day, too.
Well to anyone interested, i'm going to just try flashing kg3 and go from there. Will update ya.
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9000&r=1#regiona
Sign up and find one for your country or open Europe.
Ya i tried KG3 and no good, did the touchkey firmware update after and no change. Looks like ill try KC1 and see how that flies. Thanks
Hi XDA developers,
I'm a newbie. I've been searching posts on xda and still couldn't remedied the problem. I currently have the i9000m from Bell Canada. I upgraded my i9000m to 2.3.3 Gingerbread earlier in Kies. Recently, I've been trying to unlock my phone and without rooting, the best solution seems to be going back to Eclair, so I followed the youtube tutorial by djeddieone and tried to go back to Eclair using Odie. It basically flashes a rom (I suspect that's a T-mobile rom that shouldn't be flashed onto my phone) in Odin. My phone no longer boots and cannot get into recovery mode. (When I try to start the phone, there are random colour dots showing on the screen.) The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Thanks in advance.
I highly doubt that Bell will release a new update for the i9000m. You are better finding a newer rom (JVT or newer) and flashing that via Odin. Im using CM9 nightlies (but I feel it has too many bugs for daily use). If you can find a newer rom that is tweaked, you should notice better battery, faster, etc.
Just my $0.02
Hey I had similar issue - tried flashing new firmware w/odin & stuck with download only... I finally went to a Bell store to send it in, but they were able to use new firmware recovery software to re-flash stock gb2.3.3! I just said Kies messed-up the phone... Anyway, it will get you back to stock functionality. Good luck!
Sent from my GT-I9000M
vassosman said:
I highly doubt that Bell will release a new update for the i9000m. You are better finding a newer rom (JVT or newer) and flashing that via Odin. Im using CM9 nightlies (but I feel it has too many bugs for daily use). If you can find a newer rom that is tweaked, you should notice better battery, faster, etc.
Just my $0.02
Click to expand...
Click to collapse
I have not found any bugs since I update to the latest update-cm-9-20120425-NIGHTLY-galaxysmtd-signed.zip
bioniceric said:
The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Click to expand...
Click to collapse
Since you can still get into download mode, you're OK.
You can download the UGKG3 ROM files from this thread:
http://forum.xda-developers.com/showthread.php?t=1102881
Search for UGKG3.
The file is in 7Zip format. If you don't have something to unpack it, get IZArc.
Flash the 3 files and you should be up and running.
bioniceric said:
Hi XDA developers,
I'm a newbie. I've been searching posts on xda and still couldn't remedied the problem. I currently have the i9000m from Bell Canada. I upgraded my i9000m to 2.3.3 Gingerbread earlier in Kies. Recently, I've been trying to unlock my phone and without rooting, the best solution seems to be going back to Eclair, so I followed the youtube tutorial by djeddieone and tried to go back to Eclair using Odie. It basically flashes a rom (I suspect that's a T-mobile rom that shouldn't be flashed onto my phone) in Odin. My phone no longer boots and cannot get into recovery mode. (When I try to start the phone, there are random colour dots showing on the screen.) The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Thanks in advance.
Click to expand...
Click to collapse
After you restore your phone to KG3 via Odin/Download mode per Black Rose's link earlier in this thread, you should be back where you started on KG3.
Then from KG3 ( 2.3.3),
I suggest:
1) Use SuperOneClick to root your phone (SuperOneClick can also UNroot your phone later if you want).
2) Use Galaxy_S Unlock by Helroz available on the G-store.
This worked well for me with no problems.
And just for reassurance, NEVER flash a ROM that is not explicitly for the i9000/i9000M to this device.
So I was trying to root my i9000m and I read a forum post that advised me to update the soft key fw before doing so... little did I know I was on a custom fw already so it broke my soft key functionality. I've read a few posts that have instructions to fix the problem, by rooting the stock fw for the model and updating soft key fw before rooting again. problem is my phone was originally on FROYO and I can't locate the original file anywhere. can anybody point me to a file dl for the stock fw, or maybe someone has the file on their computer they would be willing to share? it's a bit frustrating not having the keys to go back, and i can't use certain apps due to not having a menu key..
If you don't find what you are looking for, try updating to a custom ROM that includes a Navigation Bar, as shown in the attached pic.
What's the ROM in the screenshot?
It's SlimBean 3.1 = Jelly Bean 4.1.2
With this ROM you can have up to 5 soft keys in the Navigation Bar.
This way you could care less about the phone's soft keys.
There are sites such as this one where you can find official Samsung roms
http://www.sammobile.com/firmware/?page=3&model=GT-I9000M&pcode=0&os=1&type=1#firmware
If you did manage to root your phone, you could also try this: http://forum.xda-developers.com/showthread.php?t=1832638
Thanks nyloncrack, I didn't know that there were roms that included a nav bar! I will try that, and Marshian I've gotten the firmwares from sammobile but apparently my original firmware for the i9000m (Canada) was 2.2.1, which I have found, but apparently not found the proper version of the rom that came stock with my phone. I believe it was 2.2.1 froyo. I am currently running 2.2.1 froyo.xwjsd which seems to not be the correct version.
There's a thread here with a couple of roms for the I9000m, other than that I'm afraid I can't really be of any use to you. Good luck though!
Marshian said:
There's a thread here with a couple of roms for the I9000m, other than that I'm afraid I can't really be of any use to you. Good luck though!
Click to expand...
Click to collapse
I got the jl2 rom and reflashed and it worked! I downloaded UGJL2/UGJL2/BMCJL2/Sbl (MultiCSC): reflashed with pda, phone, and csc checked and then updated the touchkey firmware and voila! I got them from the same link you posted, just before you posted it, bang on Marshian!
It was actually really simple once I wrapped my head around it, now I just need to update to a newer, faster custom rom! now let's see if I can't get this rooted and unlocked again without messing it up . any suggestions for a good, bug free rom? I haven't looked into it too much yet but i hear ice cream sandwich and jellybean are recommended for my device?
trickassfoo said:
I got the jl2 rom and reflashed and it worked! I downloaded UGJL2/UGJL2/BMCJL2/Sbl (MultiCSC): reflashed with pda, phone, and csc checked and then updated the touchkey firmware and voila! I got them from the same link you posted, just before you posted it, bang on Marshian!
It was actually really simple once I wrapped my head around it, now I just need to update to a newer, faster custom rom! now let's see if I can't get this rooted and unlocked again without messing it up . any suggestions for a good, bug free rom? I haven't looked into it too much yet but i hear ice cream sandwich and jellybean are recommended for my device?
Click to expand...
Click to collapse
Good to hear!
I've got the I9001 so I don't really know what kind of roms are available for you, but in my experience for my own phone ICS is currently the best trade-off in features and stability. JB is still quite new and not fully ported yet, while ICS is nearly bug-free. It could be different for your model, that's just my two cents. Either way, as long as you don't brick your phone you could always try out a couple of roms and see what you like best. The only downside is changing a major version requires a full wipe.
I used this to go from gb to ics.
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version
This way your i9000m becomes a i9000 for searching out new ROMs.
For whichever ROMs (ICS or JB) you'll always need to flash the KG3 modem.
nyloncrack said:
I used this to go from gb to ics.
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version
This way your i9000m becomes a i9000 for searching out new ROMs.
For whichever ROMs (ICS or JB) you'll always need to flash the KG3 modem.
Click to expand...
Click to collapse
I've tried using that guide before but the JVP link is invalid. i did a quick google search am i just looking for Gingerbread? because I have a file already on my computer titled "CF-Root-XX_OXA_JVP-v3.7-CWM3RFS.tar"
Yes, that will work.
Looking at my notes from back then I actually also used:
CF-Root-XX_OXA_JVT-v4.3-CWM3RFS, and
CF-Root-XX-_OXA_JVU_2.3.6-v4.3-CWM3RFS
They were just later versions of GB.
JVU was Samsung's appeasement to i9000 users when they were told ICS wasn't coming. Had a couple of ICS features; window dressing.
Remember to make a full backup before touching anything this time
I've been trying for hours but I cannot for the life of me get windows to recognize the device in download mode. It was working fine until i updated the rom, then intermittently, then i updated the rom again and it has stopped working. i've uninstalled the drivers, tried with debugging on and off, restarted windows, installed the newest version of kies, bought a new usb cable, to no avail. this is maddening. is there a better alternative to do this on my mac? I'm using a virtual system running windows but I'm positive that isn't the problem, since it was working great before on vmware, and parallels. any ideas? I'm about a half hour away from selling this device and going back to the iphone haha.
so basically my question now is how do I downgrade back to the original firmware, so I can put this nightmare behind me? I had it unlocked and rooted on gingerbread before... don't ask me how it took many many hours. now the device isn't even being recognized in kies. If I don't get this figured out soon i'm flipping this b*tch for an iphone 4, because I do appreciate the one touch jb/unlock. I've literally wasted days of my life trying to figure this out and it doesn't seem to be getting me anywhere. too bad because I really appreciate the android system and all its capabilities but I don't have the time to waste on stuff like this
Another Edit! So, after fussing and fiddling, I decided to try one more time, I swear, I was actually going to give up at this point if it hadn't worked. so basically I removed kies, loaded the driver i was using, which was 1.3.450.0 and it didn't work, so I loaded 1.5.5.0 and it connected! My guess is that after updating the rom the driver was outdated, but I figured kies would give me the most up to date driver, seems it didn't oh well, I'm almost afraid to load ics since I've worked so hard and wasted so much time up to this point, but i've come this far...
one more edit, the kg3 modem kept crashing odin on me so I had to stick with the jl2 that was flashed earlier.. which doesn't give me network access, I'll try to find another file but is there any reason odin should be crashing like that due to this particular file?
hahaha, shouldn't speak too soon, jl2 works after reboot, should I update my modem firmware now, and what is recommended for my system {2.3.4} kernel {2.6.35.7} and if i flash to ics will I need kg3? Thanks for all the help with this seemingly never ending process
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.