I have searched thoroughly through the various CWM and OC Kernel threads but it's not clear to me if I can achieve having ClockworkMod Recovery and an Overclocked Kernel running on a Sprint (CDMA) Tab without any issues with the GPS or Camera.
I am perfectly fine running the stock Samsung ROM, but want to be able to overclock to 1.4GHz and be able to run CWM so that I can at least be able to do nandroid backups. From what I gather some of these CWM solutions and OC kernels (which may be really designed for Verizon Tabs and not Sprint Tabs) may cause issues with the GPS and/or Camera. I cannot afford to lose those two functions of the Tab.
So for those Sprint owners out there, what has worked for you to get a working CWM and OC kernel without sacrificing the GPS and Camera? Thanks!
apparently this isn't possible? it's a shame...as if a CDMA Tab were bad enough, it looks like the Sprint one is the true ugly stepchild of the bunch.
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
ad720 said:
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
Click to expand...
Click to collapse
Awesome! So you are using a Sprint Tab? And you can run Google Maps or Navigation and it locks your location using GPS? I just want to be sure before I proceed down this path, since I've read about some users not being able to get their GPS to operate once they've borked it.
And if you don't mind me asking, how did you get the VooDoo CDMA Kernel on there? Did you first install v4 through SGS Kernel Flasher or perhaps Heimdall? And then you installed v5 through CWM?
Thanks!
Yes, Sprint Tab (I just got it from the most recent woot sale).
Google Maps locked to my location within 20 meters inside of my office, and then dead on my front door just now. I turned my WIFI off to make sure it was really the GPS. I started up Navagation and it showed waiting for GPS for a about 2 seconds before starting with the turn by turn.
I have taken pictures with the RF and FF camera but I haven't tried a video chat so that might not work. When I take a picture the preview does glitch out on the screen a bit but the picture is just fine.
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
The issue that I had was my auto-rotation wasn't working. I found the file to replace in the thread but root explorer wasn't recognizing my SD card until I turned off the VooDoo enhancements in CWM and then turned them back on as specified by the troubleshooting section of the OP. At that time I was able to replace the file to restore auto-rotate.
Please keep in mind that while I am not new to Android I am quite new to the SGS so do plenty of reading and keep in mind that this is just my experience (or inexperience) with it and I may just have gotten lucky.
Also, I do NOT have data services through Sprint, I am using WIFI only so I can't speak to the effects of the Kernel on that.
Good luck!
Thats pretty awesome, atleast we have an alternative until Samsung hopefully release the 3.34 for all G tab owners.
ad720 said:
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
Click to expand...
Click to collapse
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
onlinespending said:
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
Click to expand...
Click to collapse
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
ad720 said:
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
Click to expand...
Click to collapse
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
onlinespending said:
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
Click to expand...
Click to collapse
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
ad720 said:
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
Click to expand...
Click to collapse
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
The first OTA on my device is downloaded, but not installed, and I'm curious if I should even take them at all?
I currently have the following:
Hardware version: SPH-P100.08
Model number: SPH-P100
Firmware version: 2.2
Baseband version: S100.08 S.DJ29
Kernel version: 2.6.32.9
Build number: SPH-P100.DJ30
I'd like some type of recovery and eventually HC... boy these Sprint tabs, and tabs in general, are funky compared to my Incredible.
onlinespending said:
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
Click to expand...
Click to collapse
That is identical to mine.
I wish I knew more about the tab so I could be a help.
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
onlinespending said:
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
Click to expand...
Click to collapse
Maybe a format issue? That's interesting...
I had a similar issue with the 16gb card. put a 2gb card in, and was able to flash the kernel and then get into CWM. sadly once I got that far it didn't seem to matter what rom/kernel i tried it wouldn't boot past the samsung logo anymore. So back to stock rooted for now I guess.. Really want to play with the HC port, but not sure why it won't work. Also can't seem to get Heimdall to recognize my Tab, Odin works fine however.
another new Sprint SGT owner from Woot sale here. Also just flashed the Voodoo OC kernel last night, all seems well camera and GPS etc, I have no idea if 3g works as there is no Sprint in my state.
I flash the V5 using a guide I found over on the unlocker site. took several tries before I got it to go, lots of command line stuff and I think I had a few typos along the way.
Another woot sprint tab user here... I also have "KhasMek Voodoo Plus v5" installed on my tab but GPS does not work for me. Well, it has never worked for me even with stock kernel and EA24 ROM.
Any other woot user with a none working GPS straight out of box?
Update: GPS will not lock if Sprint tab is in airplane mode. Even though by the window works for my HTC hero phone but not the tab. It needs to be outdoor in order to get proper GPS signal.
Related
QQ regarding this:
Are all SGS devices sufficiently similar enough such that a custom ROM for one (say the VzW Fascinate, or a Euro version) will be directly usable by others, or will what differences there are in hardware build (e.g., internal memory, camera flash vs. none, etc.) fragment efforts in the developer community enough that custom ROMs will be slower to achieve?
The Captivate intrigues me since an unlocked version should be very usable in Europe (and for getting rid of ATT bloatware as well as all the other fixes a rooted phone is likely to get before ATT bothers to do so).
They should all be the exact same internally, meaning the same rooting procedure of the european galaxy S, should also apply on the att version or any other version for that matter, and i hope so cause on the 18th im getting a captive woot =]
rafyvitto said:
They should all be the exact same internally, meaning the same rooting procedure of the european galaxy S, should also apply on the att version or any other version for that matter, and i hope so cause on the 18th im getting a captive woot =]
Click to expand...
Click to collapse
im getting a captivate too, however, there are some differences between the hardware and internal guts between the phones. To name a few, Storage Space, Flash for rear camera, and the front facing camera.
These could affect the internal guts/firmware on the device.
But lets hope we can get a sweet and fast root
Non of the gsm versions have flash beside the camera, ROM capacity and the front facing camera hardware have nothing to do with the rooting of any android device, im almost 100% that the european samsung galaxy S rooting procedure will work on any other samsung galaxy S variation.
We'll know soon enough...perhaps even within a week of the Captivate's release (hey, that's an interesting play on words).
The rooting procedure will work - however the recovery mode my be crippled as the M110S (Korea) version is. Need to wait for a custom recovery - or use ODIN to flash.
But if you dont have backup of the old firmware it might be more difficult to root.
Anyways the samsung version of android is in general pretty easy to root. (no locked bootloader etc)
For all intents and purposes the Vibrant/Captivate should be identical in every aspect except for accessories. (Wonders why those forums weren't just merged together). TMobile's 3G bands are different, too.
There's already a quickie root file posted by justadude over in the Vibrant forum. One file in the .zip needs to be updated to reflect the Captivate model number (SGH-I897) but in theory, it should work.
http://forum.xda-developers.com/showthread.php?t=723479
Here is the edited and signed root update. Anyone with a Captivate care to try? It's the Vibrant root with the AT&T model added, so it should work
For reference the Captivate is the SGH-I897
so rename this to update.zip place in the root of the SD connect to adb and type adb reboot recovery and select "Reinstall Packages" using the volume keys and power to select
EDIT: removed the update.zip please see this post for the updated one
nvm 10char
**double post**
xdaapp crash :-0
tried the signed update.zip and it didn't work for me.
@chaoscentral - I think your updater script is using DOS-style CRLF end of line characters. Try changing it to LF.
@zakdeutsch - Is that a Fascinate? I see ro.build.fingerprint = "verizon..."
Nope, certainly a captivate
I tried it on a Samsung Captivate and also had no luck.
wimbet said:
I tried it on a Samsung Captivate and also had no luck.
Click to expand...
Click to collapse
How do you have one already?
Regardless I hope this thing is rootable fairly quickly.
TexUs said:
Regardless I hope this thing is rootable fairly quickly.
Click to expand...
Click to collapse
Ditto. I'm thinking, though, that we're not going to see much movement on the root front till after release...
Anyone wanna give this one a try? I had edited the update script in wordpad before which I'm sure added some kind of funky formatting. So I made this one in ubuntu and signed it in windows(since I cant figure that one out in ubuntu)
This should work though, and keep in mind it only has the model numbers for the Captivate, no fascinate or epic 4g or vibrant
Hi to All,
Is it feasible now to install the Nexus One Android 2.2 on the Captivate?
Thanks
Muhamadabdelaall said:
Is it feasible now to install the Nexus One Android 2.2 on the Captivate?
Click to expand...
Click to collapse
No. I don't even know if anyone has even had a good look at the Captivate bootloader yet. Reportedly there is a FroYo ROM dropping very soon for the Korean Galaxy S and possibly soon for the US versions as well. Bodes well for getting 2.2 on the phone in the not-so-distant future. Probably.
Hi,
Short story:
I'm bringing in my device (a Samsung Captivate i896) to get replaced at a Rogers store. However, I had installed a kernel (I think, I'm still new to this and I'm not sure which one it was) that flashes (i9000 Samsung Galaxy S) on the startup splash screen. How do I remove this from my startup screen so my device isn't voided?
Long story:
My phone dialler has, literally, just stopped working on me. When I dial out I hear no connecting tone, the other person's voice nor can they hear mine. I also can't receive calls. The only way my phone works is if I put it on speaker function (then I can hear everything) but the second I uncheck the speaker function, BAM the device dies on me. I'm trying to get it replaced.
Any help would be deeply appreciated.
Thanks!
Go back to a stock rom.
vbetts said:
Go back to a stock rom.
Click to expand...
Click to collapse
Can you give me instructions how to do that? I'm still really new to Android so I am quite lost. Thanks!
http://forum.xda-developers.com/showthread.php?t=731989
NewbDroid said:
Hi,
Short story:
I'm bringing in my device (a Samsung Captivate i896) to get replaced at a Rogers store. However, I had installed a kernel (I think, I'm still new to this and I'm not sure which one it was) that flashes (i9000 Samsung Galaxy S) on the startup splash screen. How do I remove this from my startup screen so my device isn't voided?
Long story:
My phone dialler has, literally, just stopped working on me. When I dial out I hear no connecting tone, the other person's voice nor can they hear mine. I also can't receive calls. The only way my phone works is if I put it on speaker function (then I can hear everything) but the second I uncheck the speaker function, BAM the device dies on me. I'm trying to get it replaced.
Any help would be deeply appreciated.
Thanks!
Click to expand...
Click to collapse
HAHAHAHA!!! DUDE i did this last night!!!! flashed a cw comatible kernel and my phone no longer recoginzed a sim was installed anymore! i lied my ass off and got it replaced because i forgot to backup first and NEEDED my phone that night. couldnt play forever...
So... any idea where we screwed up? besides not backing up? is the usa att kernels not compatible with canadian sims?
Nope, not compatible at all. Once it says AT&T on the startup screen you're totally screwed since the phone will not recognize your SIM anymore (it thinks you're in the States).
How did you manage to get it replaced? What did you tell them? I'm pretty stuck...
I told them that my phone was eracing my music files on the internal sim card. then it locked up well I was transferring files and wasn't able to make calls anymore...
with my new phone I flashed the phoenix 4.1 rom which has a new kernel, and everything is great. Pm me for advice and back up files
Sent from my SGH-I897 using XDA App
SGH i896 Captivate Rogers Canada Stock Flash Resources 2.1 2.2 froyo odin cwrecovery
heres the help you need:
some starter info:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896#Custom_ROMs
Rogers 2.1 stock rom
http://www.megaupload.com/?d=TT4RYLDZ
Rogers 2.2 stock roms
http://forum.xda-developers.com/showthread.php?t=905042
alternate download
http://forum.xda-developers.com/showpost.php?p=9096976&postcount=673
some info if you have installed 2.2 and now have e3 recovery and are having trouble installing update.zip's, where it "fails verification check" everytime
http://forum.xda-developers.com/showthread.php?t=909213
teach a man to fish...
Moved to Captivate Q&A
also, after my first experience, ive done everything possible WITHOUT odin. it took me forever to realize there is an Odin3 and an Odin 1step. have trouble finding info on how to use odin3.
so i use rom manager with clockwork mod (read the e3 link) or custom roms that have clockwork recovery in their kernel. Steam recovery kernels look good too.
Firebird 2.04 Kernel + Phoenix 4.1
Anyone know if the Firebird 2.04 Kernel works well with Phoenix 4.1? Can I use Clockwork to flash Firebird 2.04 Kernel to Phoenix 4.1? Thanks.
Ashyford said:
Anyone know if the Firebird 2.04 Kernel works well with Phoenix 4.1? Can I use Clockwork to flash Firebird 2.04 Kernel to Phoenix 4.1? Thanks.
Click to expand...
Click to collapse
wrong thread dude.. try the phoenix thread or the firebird thread.. are you a canadian captivate too? i896 not i897 ?? something tells me that you shouldnt be flashing your phone....
Trusselo said:
HAHAHAHA!!! DUDE i did this last night!!!! flashed a cw comatible kernel and my phone no longer recoginzed a sim was installed anymore! i lied my ass off and got it replaced because i forgot to backup first and NEEDED my phone that night. couldnt play forever...
So... any idea where we screwed up? besides not backing up? is the usa att kernels not compatible with canadian sims?
Click to expand...
Click to collapse
What did you guys do? I have been flashing ROMS like crazy and my Rogers sim is recognized.
I have changed kernels, roms and modems with no issue.
well im good now but with my first captivate i flashed a "cwcompatible" kernel with ODIN 3 into the *Phone* box. after that, couldnt make calls, and couldnt get into APN settings because it was telling me there was no SIM installed. i was too new and didnt backup properly.
Now i dont use ODIN and dont have problems. still not sure what i did wrong.
been extra careful ever since tho.
Trusselo said:
well im good now but with my first captivate i flashed a "cwcompatible" kernel with ODIN 3 into the *Phone* box. after that, couldnt make calls, and couldnt get into APN settings because it was telling me there was no SIM installed. i was too new and didnt backup properly.
Now i dont use ODIN and dont have problems. still not sure what i did wrong.
been extra careful ever since tho.
Click to expand...
Click to collapse
What you did wrong was use a CWcompatible kernal in ODIN.
The flash files go into the PDA section.
ah just figured out what i did.. and you helped. the kernel i had was for odin, from what i remember but it was going to flash a kernel that had cw in it. i was having trouble doing update.zip method because of e3 recovery.
I just opened oden for the first time since that day, and realized i confused PDA with PIT which i knew took a differnt type of file, and went with the next box that took tar... PHONE... my dumb mistake.
Trusselo said:
ah just figured out what i did.. and you helped. the kernel i had was for odin, from what i remember but it was going to flash a kernel that had cw in it. i was having trouble doing update.zip method because of e3 recovery.
I just opened oden for the first time since that day, and realized i confused PDA with PIT which i knew took a differnt type of file, and went with the next box that took tar... PHONE... my dumb mistake.
Click to expand...
Click to collapse
Glad I could help
The problem when I had AT&T running on my phone (instead of Rogers) is that there's no sideloading, hence, I was unable to enter download mode at all to put the Rogers ROM back on it. Therefore = screwed.
past tense? did you fix it? replace it? and you can always clockwork recovery flash anything.
shawn122 said:
What did you guys do? I have been flashing ROMS like crazy and my Rogers sim is recognized.
I have changed kernels, roms and modems with no issue.
Click to expand...
Click to collapse
Same been flashing a few roms, even base on ATT..
Using a Fido sim card..
And it works fine
Hello,
Sorry to sound like a complete noob in advance!
I have a new Samsung Captivate I896 on Rogers in Canada. I have ryans OCLF lagfix installed atm but i'm really interested in flashing this rom (will be my first one) and am wondering if it will work on this phone.
Also, is it just a backround fix? Will I still be able to use launcher pro, and will my phone still look the same with Froyo 2.2?
thanks in advance!
backdownup said:
but i'm really interested in flashing this rom (will be my first one)
Click to expand...
Click to collapse
Speedmod is not a ROM, but a kernel.
As to your other questions, you have a LOT of reading left to do.
Sent from my Captivate.
MikeyMike01 said:
Speedmod is not a ROM, but a kernel.
As to your other questions, you have a LOT of reading left to do.
Sent from my Captivate.
Click to expand...
Click to collapse
Agreed. Just to be save do alot of reading before attempting anything really lol. There are stickies in the Development section start there.
Ok so I did a little more reading. I896 and I897 are essentially the same. I'm not flashing a rom, just a kernel, so there should be no issue with the 3G problem mentioned in the wiki.
It won't change my rom or anything about the device other then how the filesystem works.
Thanks!
backdownup said:
Hello,
Sorry to sound like a complete noob in advance!
I have a new Samsung Captivate I896 on Rogers in Canada. I have ryans OCLF lagfix installed atm but i'm really interested in flashing this rom (will be my first one) and am wondering if it will work on this phone.
Also, is it just a backround fix? Will I still be able to use launcher pro, and will my phone still look the same with Froyo 2.2?
thanks in advance!
Click to expand...
Click to collapse
Hi, I'm pretty new here too, and I have to tell you that know one will give you a straight answer. There's a lot of' tribal knowledge', and it seems that people would rather teach you how to unbrick your phone than to flash it without issue.
First of all, hook up to Samsung Kies and update your phone to Froyo. If you are on Rogers it's an official update, don't worry about flashing any other roms yet.
Next, Use the option in the OLCF to unlagfix.
Next, you will need to root your phone. OCLF is practically obsolete, as the developer does not update anymore. Your best bet is Superoneclick. Read all instructions first. It is very easy and effective.
After you have the phone rooted, you can now install Titanium Backup. This will save all of your apps, contact info, settings, virtually everything on the phone, it will save them to a folder on your external SD. drop and drag this folder to your desktop in case anything goes wrong. I never had a problem.
You should backup your kernel. I used Neldar's SGS Kernel Flasher. It will save your kernel as an 'update.zip' in your root folder. Drag this to your desktop and put it into a folder called 'i897 orig kernel' or what have you, in case something goes wrong. I never had a problem.
Now you can flash SpeedMod. The developer's website, which is linked to in the thread's first post, will walk you though it. You will first need to install ODIN. The SpeedMod developer has a step-by-step on how to flash SpeedMod using ODIN on the developer's page. Make sure you choose a Speedmod Kernel that is intended for the Captivate, not the I9000, and that you chose the one for ODIN, not the ClockWorkMod version. Follow the steps in the Developer's page.
When you have done that, reboot into recovery mode and you should see Green Text. From here you can enable the lagfix and other tweaks. use the volume keys to select the option you want and the power button to select. under the options, it will show you which tweaks you have enabled or disabled.
Remember to select the most stable SpeedMod release, the one that is posted in the Forum (K12U-T4) is a TEST VERSION, hence the 'T'. The latest stable version as of this writing was K12T, as posted in the developer's page. I have had great results with this one.
You may find that you don't need to flash a custom ROM, I have found this setup very satisfying.
Good Luck!
Wow,
Thank you so much clemmie! That's was succinct and very helpful, especially the part about the proper way to back up my stuff.
I uninstalled OCLF just now, and it seems my phone runs at the same speed (aka fast) as it did with the lag fix installed!
Going to flash this kernel tonight or tomorrow, I'll let you know how it goes.
Thanks again!
Good to hear. There would be a lot less smoke and mirrors if people would just be straightforward and post step by step instructions with links, to give people what they want. I hope what worked for me will work for you, and I encourage you to share what you learn as well.
Kernel flash done! Screen is initially very different looking thanks to the amoled mod. Success! Backed up, thanks for all the help.
hey clemmie,
i heard that there's some issues with voice quality due to the Speedmod kernel being initially i9000-based and that it's recommended to flash a i9000-based modem. Are you having any issues with using a stock i896 modem or do you recommend something else?
Yeah, that is true, but I haven't had any problems with the stock modem. The phone works as well in-call as any other I've owned. I wonder if there is a difference between the AT&T build vs. the Rogers build. It seems that it's the AT&T folks that have issues.
Hi,
I've been wanting to do this but I'm a bit wary if this will put the ATT splash screen on boot as well. Also, I like how my phone looks like now with ADW launcher and beautiful widgets installed, I'm just wondering if installing this mod would change my appearance settings too.
olwe said:
Hi,
I've been wanting to do this but I'm a bit wary if this will put the ATT splash screen on boot as well. Also, I like how my phone looks like now with ADW launcher and beautiful widgets installed, I'm just wondering if installing this mod would change my appearance settings too.
Click to expand...
Click to collapse
Are you on Rogers? Earlier versions of the SpeedMod kernel had the AT&T splash screen, but newer versions have a simple black screen similar to the stock Samsung boot logo.
Installing the SpeedMod kernel will not change the configuration, apps, or settings of your apps. There are some settings that you can tweak in recovery mode but they are mostly file system tweaks. You will however notice that screen resolution is sharper. Your phone will run smoother and more efficiently with better battery life. You can still flash any custom or stock ROM with SpeedMod or without SpeedMod.
Yes I am on Rogers. However, I can't seem to find the stable version K12T that you mentioned on your instructions from the developer's page.
If you click on the hotlinked 'SpeedMod' in my 'tutorial' post, it will take you to the XDA page dedicated to the SpeedMod revisions. Right now there is a 13A Test version posted, but the latest stable version is now K12U. If you click where it says 'more info and downloads', it will take you to the developer's(Hardcore) blog, 'Tourist In Paradise'. The revisions are listed there. I would bookmark this page and check back frequently, as Hardcore is constantly updating. However, I'll link you to the latest stable release for ODIN, K12U:
https://docs.google.com/uc?id=0B-3n...WJmNTUtZDVmNThmMmNhZTRm&export=download&hl=en
Thanks for that! I just did this and although it didn't show the ATT boot screen, it shows the Galaxy S I 897 screen after the I 896 though. Thanks again!
Glad to hear you had success. Not so hard after all, eh?
After using this for a day or two:
I can't believe how fast my phone is. I thought it was fast before with (and then without) the oclf. I can barely keep up!
Battery life seems improved.
Screen is perfect. The lowest brightness setting is much better and more comfortable for low light usage.
I lost 1000 points off quadrant, but quadrant doesn't matter.
The only real downside is call quality took a hit. It's a bit static-y and echo-y.
I'll look into this though and see if I can find a solution, but if you have any tips let me know.
Looks like you are a candidate for a modem flash. Let me know if you find something that works, there is a lot of info on swapping modems for SpeedMod. Maybe I'll try one too!
Hey clemmie (or anyone), if I want to install voodoo lagfix - how abouts would I do that if the SpeedMod kernel already comes with / is based on sztupy's Universal Lagfix (enhanced) and if voodoo is a kernel itself (unless I'm wrong about this)?
If you flash the SpeedMod kernel, voodoo lagfix comes integrated with the kernel. It's a master of enabling it from the recovery menu.
Sent from my SAMSUNG-SGH-I896 using XDA App
Okay first of all, I would like to apologize if this is being posted in the wrong forum, or if I am upsetting anybody by posting this. I have searched all over for a couple days trying to figure this out. This is my last resort, and I'm hoping you guys can help. All of your time and understanding is much appreciated!
So a little background. About a week ago, I rooted my AT&T Captivate 2.2(build number 1012 if that helps) using Superoneclick, and then flashed CM7.1 using clockworkmod. I was not satisfied with CM7.1(terrible battery for me, other various reasons). I then downloaded MIUI (not sure which version, the one available on the premium version of clockworkmod) and flashed it using clockworkmod. This started with the cm bootscreen, and then went to an MIUI bootscreen that played a little tune. The miui screen looped, and it would not go past this.
After rebooting and running into the same thing, I went to f\attempt to find a solution. I thought I backed up my rom, but it had been erased (issue with the external sd I think). I used an odin one click I found on here, but this odin one click brought me back to eclair 2.1, instead of 2.2. Up until now, I could get into both download and recovery mode using the three button method, and now I can't. I am not sure what to do exactly. I have read about getting it into download mode using adb, but I'm not sure if that would work in my situation, and I'm not too educated on adb or android sdk. I stayed up almost all night last night, and now have researched most of today, not making much progress.
Thanks again for your time!
Just to clarify have you used all button methods in order to try to get into download mode. Seems as though flashing bootloaders may have f'ed up you combos. I have a couple suggestions. I'll edit my post as I find the urls to post for you
Stock GB ROM you should be using -- http://www.mediafire.com/?05nemq5yyn5fuqf, this one has bootloaders, but preferably you should use stock odin roms that don't mess with the BL's (after this of course, since yours are messed up right now).
Now of course this depends upon you getting into download mode. If you can use ROMmanager (btw, I don't recommend you download your roms from rommanager, as that will not always be the most up to date and may not be the one for you) to get into recovery mode, then from there go to advanced then reboot download. However some kernels do not support this. Try the cable methods before trying this method.
First of all, I appreciate your help Mikel.canovas. I have used all the button methods. I can no longer get into recovery or download. (Romtoolbox enables me to get into recovery(2E), but not download). I now have root access, but am not able to sideload apps, and apparently rommanager free isn't available on the market. I did buy rommanager premium, but unfortunately now that I basically reset my phone, it doesn't show up as bought (known issue, apparently not resolved?), and even after I bought it again, it says I need the free version to even use the premium version.
Should I go through the process to be able to sideload apps? Or will romtoolbox do the trick? Rom toolbox gives me the option to install a rom from my sd card. Should I use that, and select the GB ROM you provided? I'm not sure I understood exactly how you want me to get that GB ROM onto my phone.
What I want to eventually have is either MIUI or rom fasty on my phone. If possible, could you give me some steps on how to reach that goal?
Thanks again for your time. Eclair on the captivate is not pleasant, especially since I had a taste of CM.
Well first off I highly recommend Mosaic over CM or Fasty, solely because of performance and battery life. However that is all subjective.
Ah since you're rom is sending to 2E recovery, you're not rooted with cwm. You need to flash another kernel that supports this. Afterwards, If you can get into CWM, I recommend putting CM onto your sdcard and flashing from there. After booting into CM hold down the power button, press reboot, choose reboot download. See if that works. If not, does adb reboot download work for you? If not again, I recommend trying another USB port, reinstalling drivers, trying different button combos. I've had issues getting into download mode in the past and, trust me, it is VERY frustrating.
Well first of all, before you back into flashing stuff, don't flash to stock unless you have done everything possible with the tools on your phone. I'm assuming you gave it at least 5 minutes to boot up, as the first boot can variably take longer. You could go into recovery and wipe stuff, or you could have gone back to CM7. A flash to stock is probably never necessary in the situation you reported.
Anyway, if you can get into recovery, maybe try getting a kernel that allows you to reboot into download from recovery. Although that will depends on what kernel you are on right now, as I know speedmod kernel has that option, but you would need to get to download to flash that.
And as another poster wrote, have you tried all button combinations?
korockinout13 said:
Well first of all, before you back into flashing stuff, don't flash to stock unless you have done everything possible with the tools on your phone. I'm assuming you gave it at least 5 minutes to boot up, as the first boot can variably take longer. You could go into recovery and wipe stuff, or you could have gone back to CM7. A flash to stock is probably never necessary in the situation you reported.
Anyway, if you can get into recovery, maybe try getting a kernel that allows you to reboot into download from recovery. Although that will depends on what kernel you are on right now, as I know speedmod kernel has that option, but you would need to get to download to flash that.
And as another poster wrote, have you tried all button combinations?
Click to expand...
Click to collapse
Or download SGS Kernel Flasher from the market. You can then flash kernels with the app. without having to go into download mode. Very handy.
Once again guys, thank you for your time. A little more information:
Kernel:
2.6.29
[email protected]#12
Baseband:
I897UCJF6
Let me know if you need any other information.
I am able to get into download mode using the terminal emulator in rom tool box. (The free version of rom manager is no longer on the market)
I was hoping one of you could give me a step by step of what I need to do, with links to downloads.
And yes, I have tried all off the three button methods. Also, I probably should have researched more before I flashed back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
wwcjr91 said:
Once again guys, thank you for your time. A little more information:
Kernel:
2.6.29
[email protected]#12
Baseband:
I897UCJF6
Let me know if you need any other information.
I am able to get into download mode using the terminal emulator in rom tool box. (The free version of rom manager is no longer on the market)
I was hoping one of you could give me a step by step of what I need to do, with links to downloads.
And yes, I have tried all off the three button methods. Also, I probably should have researched more before I flashed back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If nobody beats me to it, I will post you some links tomorrow when I'm on my laptop.
Oh, and miui won't really give you better battery life than CM7. It basically is CM7 with a different UI. I loved CM7 a ton, so if you are having issues with it, let me know! With the right kernel and other settings, battery life is pretty decent, as long as you charge nightly.
Sent from my ICS i897 Captivate
wwcjr91 said:
Once again guys, thank you for your time. A little more information:
Kernel:
2.6.29
[email protected]#12
Baseband:
I897UCJF6
Let me know if you need any other information.
I am able to get into download mode using the terminal emulator in rom tool box. (The free version of rom manager is no longer on the market)
I was hoping one of you could give me a step by step of what I need to do, with links to downloads.
And yes, I have tried all off the three button methods. Also, I probably should have researched more before I flashed back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
What is the build number of your phone? It's located under your battery, looks something like 10.06,10.07, 10.08 and so on
Alright, thank you, I will be checking back tomorrow.
Eventually what I want is to have the working 3 button combos again for both download and recovery mode, and either the miui, mosaic or rom fasty on my phone.
Easy flash GB BL's and you won't have to worry about 3 button problems!
If you didnt do a Master Clear, now would be the time. Make sure you back up anything you want to keep. MC will erase EVERYTHING on your internal SD
Remove your Micro SD, and your SIM
Download:
OneClick Root
SideLoadWonderMachine This also has CWM, 3ButtonFix and ROM Manager in the zip
Make sure you have Debugging enabled
Connect to your PC
Run One Click Root, and follow the instructions, reboot
Run Sideload Wonder Machine and direct it to install ROM Manager
Copy the update.zip(CWM) and 3Button Fix to your phone
Open ROM manager and "reboot to recovery"
You'll go thru the boot twice to get to CWM
In CWM install the 3 Button Fix
I usually pop out the battery and check it before I put the ROM in.
VERY IMPORTANT!!!!! DO NOT TRY TO USE THE 3ButtonFix while you have a GB ROM installed you WILL brick your phone. It only works on 2.1, and 2.2 ROM's
using this one click package I now am able to manually enter download and recovery :
http://forum.xda-developers.com/showthread.php?t=1129821
However, The recovery is still 2e..
kangi26 said:
What is the build number of your phone? It's located under your battery, looks something like 10.06,10.07, 10.08 and so on
Click to expand...
Click to collapse
1012, do you think any of my problems would have to do with the build number? WHen I got it, it had froyo with the working button combinations.
Sorry, I didn't see that until now.
I now have clockwork recovery, and I'm about to try out fasty. Thanks again guys.
So can I delete this thread? And if so, should I? I've found plenty of threads that seem outdated, and fill up the search engine.
wwcjr91 said:
1012, do you think any of my problems would have to do with the build number? WHen I got it, it had froyo with the working button combinations.
Sorry, I didn't see that until now.
I now have clockwork recovery, and I'm about to try out fasty. Thanks again guys.
So can I delete this thread? And if so, should I? I've found plenty of threads that seem outdated, and fill up the search engine.
Click to expand...
Click to collapse
The only reason I asked about the build # is because the 10.08's were pretty commonly known to have 3 button issues. Also, anything above 1012 and using Odin1 Click could soft brick. I was just checking as I was offering info
kangi26 said:
The only reason I asked about the build # is because the 10.08's were pretty commonly known to have 3 button issues. Also, anything above 1012 and using Odin1 Click could soft brick. I was just checking as I was offering info
Click to expand...
Click to collapse
Trying to fix my buddys cappy. Its rooted on T-Mobile and running stock 2.1 rom. I'm not a Samsung guy so how do I get cwm and a 2.3 rom? The build number is ECLAIR.UCJH7
Sent from my Incredible 2 using xda premium
Go to this Stickied Thread in the Development Forum... http://forum.xda-developers.com/showpost.php?p=18370235&postcount=1
And u will have to use one with the Bootloaders included, because to run a gingerbread firmware u gotta have the gb bootloaders.
Post #3 has the "leaked" KK4 (Been confirmed to be the same as official).
4-2ndtwin said:
Go to this Stickied Thread in the Development Forum... http://forum.xda-developers.com/showpost.php?p=18370235&postcount=1
And u will have to use one with the Bootloaders included, because to run a gingerbread firmware u gotta have the gb bootloaders.
Click to expand...
Click to collapse
Since its already rooted do I need a computer?
Sent from my Incredible 2 using xda premium
Yep. Because these are Odin or Heimdall One Clicks.
You can't just flash to a GB firmware/rom from Eclair/Froyo without using Odin or Heimdall to at least get the Gb Bootloaders. You cannot just go through CWM recovery unless u already have the GB Bootloaders.
Of course u can get it all through mini Kies, the official GB 2.3.5 KK4 update that is.
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.
Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...
snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?