I'm running Overcome currently. Is it possible to flash to a stock system from Clockworkmod, such that the system I'm running is stock?
I don't need the tablet itself to be bone stock, but I'd just like to switch back to the stock system, with none of the Overcome modifications.
Ideally, I'd love to be able to keep Clockworkmod and still use Clockworkmod to flash modified kernels. Even more ideally, being able to stay on ext4 would be great.
The reason I ask is I've been seeing some weird bugs lately, mainly with my AT&T wireless account mysteriously breaking down and not working until I reselect the APN and reboot, as well as 30 second hanging on boot, and I'd like to try stock again to see if those problems go away.
I think you can apply Clockworkmod afterwards, if you have already successfully applied Overcome. This means that you have Odin ready on your PC, drivers for USB ready and your tablet is rooted.
I applied stock_safe ROM included in Odin package to fix my freezing tablet. Lost CWM, but right now I am looking how to apply it separately of Overcome.
edit: I think I have just found it on the market, you have free and premium version. I think this guy deserves free coffee, so let's buy premium.
For my at&t tab i use JQ1, which is stock gingerbread, then i applied the CF-Root v3.3 to have root and CWM. Then I flashed Dip7 kernel for speed improvements.
I was having the lag issue too so I reverted to this set up, and I really like it.
As for the connection issue, you have your apn correct, but remind me what modem you have? Maybe an experiment is in order.
rangercaptain said:
For my at&t tab i use JQ1, which is stock gingerbread, then i applied the CF-Root v3.3 to have root and CWM. Then I flashed Dip7 kernel for speed improvements.
I was having the lag issue too so I reverted to this set up, and I really like it.
As for the connection issue, you have your apn correct, but remind me what modem you have? Maybe an experiment is in order.
Click to expand...
Click to collapse
Okay, so I can flash to Overcome's stock safe (which will change me back off of ext4), and then using Odin flash one of the stock firmwares, and then apply CF-Root to get root/CWM. Does that sounds right?
It's actually pretty disappointing that AT&T still hasn't released or even announced its own Gingerbread update yet, which I hadn't realized while typing this, since I had really wanted to flash back to stock to fix the AT&T connection issue, but it may still work on other firmwares. Going back to Froyo seems like too much of a step backwards.
I'm currently on the KM2 modem. What do you recommend?
Flash stock safe then flash CF root, overcome kernel (only kernel), or Koxudaxi or dip7 or whatever pleases you then flash the modem that works best for you.
Related
I have a Bell SGS, GT-I9000m. I'm considering installing hardcore kernel only, i.e. no custom ROM. If later I want to revert to the stock kernel, how would I do that?
Thanks for your help.
Sent from my GT-I9000M using XDA App
I'm not quite sure if it is possible with the stock-kernel but if you can make a full backup (like with CWM) you could restore it later. But why do you want to get back to stock-kernel?
If the backup-possibility does not work you have to find the stock-kernel for downloading and flash it via Odin or you have to flash the whole stock-ROM with Odin.
Thanks for your answer. I can't make a Nandroid backup while I'm on stock (because I can't install CWM recovery because I'm on 3e stock recovery, not 2e)
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong? I guess I just wanted to know if it was possible.
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Sent from my GT-I9000M using XDA App
I should add, the site/repo question is for kernels and stock ROMs...
Thanks.
Sent from my GT-I9000M using XDA App
site1ca said:
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong?
Click to expand...
Click to collapse
Well, then just flash the whole stock-ROM and flash it (look at samnfirmware.com for firmwares).
site1ca said:
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Click to expand...
Click to collapse
Don't know if you'll find it anywhere cause nobody needs it.
Possible scenario
Alright, thanks for your help. I guess the one scenario that is bothering me is as follows:
1) Bell - FINALLY - releases their official Gingerbread update.
2) I've installed Hardcore kernel, which according to - http://forum.xda-developers.com/showthread.php?t=822756 - "works on all 2.2 and 2.2.1 ROMs".
3) Would I be able to install the Bell Gingerbread update with Hardcore kernel?
This is why I keep asking how I would revert from Hardcore because I obviously don't want to lock myself out of Bell updates forever.
It doesn't matter which kernel you are using when you are flashing with Odin. And Bell releases the updates later than Samsung, so you'd have the advantage of getting updates earlier with a 'free' firmware.
One solution to flash back the stock kernel is to extract the zImage (the kernel) from the stock rom and flash that with Odin or Heimdall.
But as far as I know having a custom kernel would not cause problems with installing a stock upgrade.
Done
I've installed Hardcore's kernel. Everything seems to be working fine, phone started up and picked up service.
I booted into recovery, enabled lagfix, turned on all of the recommended tweaks and then ran the Quadrant Standard. Things seem a bit faster, so I guess it's all good.
Next step, Darky's 10.1.
Thanks for your help, everyone.
One more question:
I did a Nandroid backup of everything (so data, dbdata, cache AND system). The restore option says "Be careful!". What's up with that? I mean, what's the caveat?
Thanks.
I've already made some NANDROID-backups, but never seen 'Be careful!'.
If the backup was succesful I wouldn't care about that.
*sigh*, I hate to keep adding questions on to this thread, but I must.
After installing the hardcore kernel and enabling tweaks and lagfix, I'm running into exactly this problem: http://forum.xda-developers.com/showthread.php?t=851970
My phone was extremely hot for a while, then I got a warning indicating that my internal phone storage was running low, etc.
Eventually, I found this file (/data/local/tsprsp) to be the culprit. I deleted it and rebooted and now my phone is fine. However, vibration just doesn't work at all!
Any ideas? Has anyone else run into this problem?
I was told that if you do a 'full' backup, in some cases restoration will fail with some error. But it depends on the version of the ROM you are using.
That is the reason why it is recommended to backup only data and if you want to restore, then first reflash your rom, then restore the data.
Thanks, zsori. That explains the "Be careful!".
Sent from my GT-I9000M using XDA App
After trying MIUI, a stock ROM will never touch my SGS again.
meresis said:
After trying MIUI, a stock ROM will never touch my SGS again.
Click to expand...
Click to collapse
you will have to flash back a stock rom via odin if anything wrong happen during the flashing of custom roms, although chances are low if you follow the instructions carefully.
good luck and have fun flashing custom roms!
Which Gingerbread?
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
site1ca said:
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
Click to expand...
Click to collapse
you got it wrong.
PIT is for mapping the partitioning of the phone. In most cases you should only use 512 pit file. and only use it when you want to wipe the phone.
the three parts is "pda" (which is the rom), "phone" (which is the modem), and "csc" (which is the carrier customization and apns)
the kernel is in the part of pda (the rom)
check the thread in xda of the kernel to see if its a gingerbread kernel or froyo kernel.
hope this clear things up
Yes, that helps. That's really good to know. So now, in Darky's guide to flashing Flash Ficeto_JVH_Odin, I see that only PIT and PDA are specified. This is reassuring, knowing that the modem and carrier stuff isn't touched.
Many thanks.
There are firmwares with three parts (Phone, PDA, CSC, including bootloader) and with only one part (PDA, no bootloader(?)). The one-part-FW is just an 'update', the one with three parts an 'upgrade'.
Hey Guys,
I have a couple of questions in regards to going back to stock from DarkyROM 10.2.
After using 10.2 for about a month now, I have noticed that while the rom is fast, There are quite alot of glitches in my day to day operations. My 3D HD games no longer work smoothly (as they did in 2.3.3 with CWM), the phone will randomly freeze up when using the browser/gallery/calender etc. After multiple re-flashes I am coming to the conclusion that to get back to my original performance I may need to flash a stock JVQ and then mayby just us CF ROOT or something of the like to get CWM access.
My question is, what preparations need to be done before preforming this flash. Also, can the stock files be flashed with ODIN? Also, if anyone has any input on why DARKYROM 10.2 seems to have these issues, please feel free to let me know. Any help will be greatly appreciated, thanks in advance!!
Phone Specs:
Samsung Galaxy Vibrant (i9000m)
DarkyRom 10.2 RE -w- KC1 Modem
Only Mod preformed after flashing RE was updating the SMS application to the SGS2 App to restore the chat bubble colors. The issues were present before this update. Did the update through DarkyRom Tool.
If you guys need any more information, just let me know..
Anyone??????
Alright, I'll take this one if no one else will. I too have the i9000m, and have learned all I can about keeping it alive and well. Going back to stock is easy. Go to general and look for the stock firmware thread. You will get instructions there on how to flash with odin. I've never used darky before but I did use CM7 and flashed back no problem. You could also look for Ramad's prerooted roms. I'm running one right now, UGKG3. Works great as I couldn't root it myself.
Sent from my GT-I9000M using XDA App
Getinaf said:
Alright, I'll take this one if no one else will. I too have the i9000m, and have learned all I can about keeping it alive and well. Going back to stock is easy. Go to general and look for the stock firmware thread. You will get instructions there on how to flash with odin. I've never used darky before but I did use CM7 and flashed back no problem. You could also look for Ramad's prerooted roms. I'm running one right now, UGKG3. Works great as I couldn't root it myself.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Hey Dude, Thanks alot for your response! One more question before making the switch....Should the voodoo lag fix that comes with Darky 10.2 be disabled before flashing with Odin back to stock?
If you want to go back to stock ROM. Before flashing disable the lagfix (for safe). You can download the firmware from www.samfirmware.com. and its an odin base installation.
Post your problem in www.darkyrom.com some expert will help you...
Hey guys.
I have flashed stock ROM (2.3.4) via Odin and worked absolutely fine. Didn't need to fiddle with the lagfix or anything. Simply popped phone into DOWNLOAD mode and flashed (with re-partition/wipe and backing up "stuff" beforehand).
The lagfix menu I think, is in the RECOVERY mode in the extended power options menu. I think thats the CWM with the DarkyROM maybe? Either way, you can enable/disable the lagfix in that menu.
Hope this helps!
Akhtar
Hi all,
over the last couple of weeks I've been experimenting with Firefly 3.0 on my Rogers I896 Samsung Captivate. Then I put CM7 on the phone, but decided I liked Firefly better so I tried to switch back. Trouble is, it looks like I did something wrong because now I can no longer root my phone. I have searched a lot on line, and tried several root methods including z4root (which is what I was using during the Firefly installs - worked great) and SuperOneClick - no joy. Z4root runs for a few seconds, and finally just returns to the home screen rather than re-booting; and SuperOneClick goes through a lot of commands and finally hangs with the message "waiting for phone" (or something close to that).
I've used Odin 1.81 to flash back to the stock Rogers 2.1 image, then to 2.2. (I used the images from here.) When I dial *#1234# I get CSC="unknown" and when I dial *2767*4387264636# I get PCode = "SGH-I896ZKAATT" but I think this is wrong, I think it should display "SGH-I896ZKARWC". I tried the fix documented here and following this procedure I can get the CSC code to read "I896rwcjl1". But I can't load a custom ROM because none of the root tools will root the device.
One other problem I ran into - don't know if it's related, but I think it is - if I try to set up the stock e-mail client to use our Exchange server, it is not able to connect to the mail server even though I know FOR SURE the credentials are correct. (The same setup works like a champ on other Android phones.) I think that the firmware is sending some phone-related info to a Samsung server to validate the license for the Exchange client software, and this is actually the part that is failing rather than the connection to the mail server.
Can anyone provide some direction to a long-suffering Android noob who just wants his Firefly (and exchange e-mail) back?
Thanks in advance
Just go into download mode, Odin/Heimdall a CWM-based kernel onto the phone, then don't even bother with standard rooting procedures; just reboot to CWM recovery, flash a custom ROM and go.
Flashing to stock is largely unnecessary for this.
Aus_Azn said:
Flashing to stock is largely unnecessary for this.
Click to expand...
Click to collapse
NOT true coming from an aosp rom you HAVE to flash back to stock with either a one click or use a .pit with the firmware .tar. cm7 and miui use a completely different partitioning table if you try to flash a tw rom over them it will not work.
but yes you are right about just flashing a kernel with odin/heimdall that has cwm baked in. no need to root before you flash a rom.
studacris said:
NOT true coming from an aosp rom you HAVE to flash back to stock with either a one click or use a .pit with the firmware .tar. cm7 and miui use a completely different partitioning table if you try to flash a tw rom over them it will not work.
but yes you are right about just flashing a kernel with odin/heimdall that has cwm baked in. no need to root before you flash a rom.
Click to expand...
Click to collapse
I thought he meant oneclicking back to full stock (2.1 or 2.2), which is unnecessary due to bootloader rubbish. 3File to GB is pretty much the only way to go.
Thanks! 2 more follow-up questions
Thanks all for your helpful feedback. Two more questions:
what ROM(s) would you recommend that has CWM built-in?
I'm assuming once this ROM was loaded, I could replace it witl Firefly fairly easily?
Thanks again
embsyntax said:
Thanks all for your helpful feedback. Two more questions:
what ROM(s) would you recommend that has CWM built-in?
I'm assuming once this ROM was loaded, I could replace it witl Firefly fairly easily?
Thanks again
Click to expand...
Click to collapse
a ROM doesnt have CWM built in....a kernel does
READ, READ, then READ some more
please read the new user guide (below in sig)find out what stickies are and find said stickies.
also if needing rogers stock roms (one clicks and non one clicks with pit....) also look in my sig.
they call me mr. rogers.
Thanks for the clarification. I installed CM7 using the guide on their wiki page and everything works.
Sent from my SGH-I897 using XDA App
So I looked all around and could not find this specific question. I upgraded the wifes cappy to the AT&T Gingerbread KK4 release via Kies the other day. I found a thread to assist in rooting which went fine. But for the life of me i cannot find how to get cwm on this thing without changing the kernel. I used a file based cwm on the sdcard when it was froyo that i would flash for use when needed and it would revert back to stock 3e after rebooting, that exist for KK4? She's insisting I keep hers stock as she's worried about it bricking so I have to follow orders lol!
U can't do the update.zip to get cwm like in eclair days because of the 3e recovery. If u want cwm on kk4 u gotta at least flash a kk4 kernel with cwm baked in. I have been using Corn Kernel version 6.03 and it is excellent.
Why do u want cwm if she wants to keep it Stock ? To flash different modems... U can't flash mods etc. because it is stock and odexed...
Just curious.
Sent by XDA Premium App
So I can flash clock mods and such from the kitchen, unless of course KK4 doesn't allow it. It did allow on stock 2.2 and worked just fine without issue. My thing with flashing a different kernel is I don't want anything that's overclocked or such on her phone.
What you need to do is get a kernel with CWM already baked into it.
So start with this. Flash the Corn 7.03 kernel. I used it for the entire day today with a great experience. It was just released today as well. This kernel has CWM already in it and works great with the stock rom.
I also suggest flashing this rom: http://forum.xda-developers.com/showthread.php?t=1358180 This is Trusselo's: 【stock】【kk4】 rooted deodexed debloated rom. Its basically a stock version of the rom with root already in it. It is missing a few ringtones but who really cares about that. Its also stripped out of the stuff that slows your phone down and paired with the kernel it makes for a much better experience on the captivate.
So if you want stock this is about as stock as it gets with a mix of high performance.
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.