Has anyone tried using the i9000 Froyo rom (like this) with the new Froyo kernel? Could I try it, using the following procedure? I would like to try it, but don't want to brick my phone.
1) Remove SIM and MicroSD
2) Open Odin, load the i9000 Froyo PDA file and the i9000 Froyo CSC file.
3) Leave auto reboot checked and repartition unchecked.
4) Boot the phone into download mode.
5) Flash.
6) After reboot, get back into download mode.
7) Reopen Odin and load the stock Captivate kernel (From this thread) in the PDA box and a pit file (which one???).
8) Ensure auto reboot is checked and repartition is not checked.
9) Flash.
Would this work? Also, what if any PIT file would I use?
Thanks in advance
I'm trying this now. First attempt from the Cappy leaked Froyo failed. I just flashed back to JF6. Gonna try above with the I9000 pit and see what happens.
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
TMC_Sherpa said:
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
Click to expand...
Click to collapse
but i dont think the reorient kernel was NEEDED. i ran the i9000 with stock captivate kernel (as instructed in that post) for a week or 2 and didnt have any problems whatsoever.....BT and HSUPA didnt work, but small price to pay
now that we have a kernel from 2.2 build, we should be able to apply 2.2 captivate kernel with JPK and run it...
i think i will give it a shot today
I just tried it using the steps I outlined above. I would *not* reccomend doing it; it didn't work for me. Once I flashed the kernel, the phone would get stuck at the AT&T "World Phone" screen (formerly the i9000 splash, but I guess the kernel changes that). Being stuck at this screen, it would intermittently vibrate 1-buzz, 2-buzzes, and repeat about every second. I assume that's some sort of error message? After trying to reboot it a few times, I eventually got the "phone-!-computer" screen, and was only able to successfully reflash it by removing the battery, holding volume down, and plugging in USB, and was able to get into download mode to flash with Odin. Heads up.
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
boomerod said:
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
Click to expand...
Click to collapse
Basically, same here. I guess we'll have to wait for someone to figure this out.
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Pirateghost said:
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Click to expand...
Click to collapse
2.2 and 2.1 are different software so its easily possible that Samsung changed whatever allowed it to work.
Sent from my SAMSUNG-SGH-I897
the 2.2 leak is basically an i9000 rom, its not fully tweaked to ATT wants yet... thankfully
yeah I can't understand why on earth you would want to run an i9000 firmware which is at least just as buggy but not designed for your device at all... JPK (latest i9000) was built the same day as JI6...
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
boomerod said:
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
Click to expand...
Click to collapse
I was running i9000 ROM as well with captivate Froyo kernel (in which I noticed a slight increase in performance) but there was no voice while calling only a hiss. I installed the modem.bin from Captivate froyo and it worked.. for 10 sec and then I got reboot loop and decided to go to stock froyo. Wondering if there is a possibility to make it work with a modem from 2.1, but I believe is highly improbable.
Now I am back at the AT&T build but I must say that there are few things which I really don't like. Like the lag when changing home screens. If I go to 7 and press home button it takes 1-2 seconds to get back to the main one.
I indeed found it much faster in opening gallery and loading the thumbnails plus very good results in Linpack. Quadrant still doesn't give me more than 985 which is half of 2.1 with lag fix but that's not relevant.
I want to run i9000 rom because I am from Europe and I would like to have Swype in Romanian for example + that the i9000 rom doesnt mind if I have the "Use wireless networks" On or Off, GPS will still connect in less than 10 sec, thing impossible to achieve with ATT ROM (from my experience).
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
han.azuki said:
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
Click to expand...
Click to collapse
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Pirateghost said:
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Click to expand...
Click to collapse
+2 I love the i9000 rom and I'm not sure I'll update to 2.2 until we get one. I had Froyo on my N1 so I've used it before but after getting rid of the stock rom I don't want to go back. I don't want to update just to update.
Quite an adventure
OK, so even though this is embarrassing at some level, I'm still going to share this experience with the forum (just in case someone else does this to themselves).
So, as the OP posted (had been thinking about it since 3AM this morning after I found that this leaked Cappy Froyo does not have BT voice commands implemented) I decided to try out the I9000 Froyo (most recent posted on samfirmware.com) and then try flashing the Cappy Froyo kernal to see if I could get a working combo. Well, I never got as far as the OP in that I was never able to successfully flash the Cappy kernal.
I ended up stuck (for most of the day) with a very unstable combo: I9000 Froyo with Cappy JF6 baseband. Originally, the problem was I could not get in to download mode using all the normal, well-know methods. I was then able to - see my earlier post - but was unable to get past File Analysis in Odin. I then tried rebooting and then was not able to get back in to download mode to save my life, not even using the method that originally worked for me. So, here is the lesson I learned (other than not screwing around too much with my phone):
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
I still had issues getting past File Analysis; what ultimately worked was JF6 on-click solution. So, after all day screwing around with this, including trying to get into download mode through adb (to no avail), I've learned my lesson. I'm back to where I've been for the past month: really thinking about abandoning AT&T and this crappy, broken GPS, slow to get Froyo Cappy (which otherwise I like very much) and switching to Sprint and the Evo. Sigh...I'm under contract and don't want to pay a cancellation fee, damn!!
Here's a snipped from logcat while the phone is stuck at the AT&T logo. If anyone knows what to do about this...
http://pastebin.ubuntu.com/504711/
boomerod said:
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
Click to expand...
Click to collapse
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
damis648 said:
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
Click to expand...
Click to collapse
Did you ever get back to stock? I think we had a good thought...
I guess I have to admit that I like to tinker. What I need to do is get another phone that I leave alone so I don't loose my communication to the world.
-Edit-
Back at the leaked Cappy Froyo...guess I'll just live with this until we finally get a fully functional Froyo.
Related
Hi guys,
I'm in real need of someone who can help me out, a friend at work asked me to give him my phone (we both have the same galaxy s I9000) because he had a lag fix for it that was really easy... ok i thought... he ran it and now the phone is really fast!! great I think! The then problems started.
When it boots up it shows a new screen that says vibrant (this isn't a vibrant phone its a aussie model i9000)the first sign that things were wrong, then the headphone detection wasn't working, and worst of all i can connect it to a usb or even a power charger without the phone turning off and the battery icon appearing then turning off again indefinably. ohh shiiiit!
I think he may have run the vibrant file not the correct one for the international i9000 i have, so i find the voodoo website and rerun the update with the correct one (used a removable sd card get the files from my pc to the phone) BUT still have the same problems I also tried the “disable lagfix” to roll back but no luck.
SO if anyone can tell me how to dig myself out of this ever deepening hole I will be hugely indebted to you...BIG TIME!!
Are you sure he didn't switch his phone with yours.The lagfix doesn't need a new rom.
From my pov.
He installed vibrant firmware, then installed Voodoo.
Browse flash guides. You still have boot.
flash a new firmware, 2.1 imo. is the best, add voodoo and/or oclf v1.
Must ofc have root priv.
.hacker
It's obvious that these Bell i9000m GXS phones are messed up with their faulty SD cards.
It's been reported the Nexus S will be coming to Bell (and later on the SGS2)
Should I try and sell my phone via craigslist / Kijiji when the Nexus S comes out ? or should I wait for the SGS 2 ?
What are you guys thinking?
These faulty SD cards are a joke of a phone, only slightly less embarrassing than the support/software
I've been trying to upgrade by 2.1 eclair to 2.2 froyo for over a month now -- tried everything and no luck. This is a f*cking joke since my old palm pre could even do OTA upgrades
Funkadelick said:
I've been trying to upgrade by 2.1 eclair to 2.2 froyo for over a month now -- tried everything and no luck.
Click to expand...
Click to collapse
Thousands of people on this forum flash to a different ROM everyday. Explain how you have tried to upgrade, maybe we can see if you are doing something wrong.
As for getting a different phone, the only differences in specs between the SGS and the Nexus S is the lack of a SD card on the Nexus S and it will have Gingerbread. The Nexus S works on HSDPA 1700, the SGS on HSDPA 1900
http://www.gsmarena.com/compare.php3?idPhone1=3620&idPhone2=3115
Ian
w98seeng said:
Thousands of people on this forum flash to a different ROM everyday. Explain how you have tried to upgrade, maybe we can see if you are doing something wrong.
As for getting a different phone, the only differences in specs between the SGS and the Nexus S is the lack of a SD card on the Nexus S and it will have Gingerbread. The Nexus S works on HSDPA 1700, the SGS on HSDPA 1900
http://www.gsmarena.com/compare.php3?idPhone1=3620&idPhone2=3115
Ian
Click to expand...
Click to collapse
Well I have been following Kies "fixes" for a month and a half now, and trust me, there isn't anything I haven't read. Nothing works. I've done the 16 character deletion fix, nothing. I've uninstalled Kies and the drivers and done registry hacks, etc. for days and days. Rebooted about 500 times. Reinstalled software. Nothing.
It says everything is connected and working fine - but when I connect my phone to the USB cable KIES (2.0) just says "connecting" with an never ending loop.
I think it's a crying shame this software sucks so bad.
As stated, I may need to resort to using ODIN and flashing, which I don't want to do (because of warrenty issues)
What's the best ROM to use? I want something fast and stable. Are people flashing Gingerbread ROMS ?
Atrix
I agree that Kies is an awful program. There's just too many tweaks that you have to do just to attempt to get your phone connected.
I'd suggest getting the Motorola Atrix 4G. It's already announced on Bell and it's by far the most interesting phone yet.
I do not use Kies V2, I hate it. It also does not try to update my phone, it gets to the update window but then it freezes. I still use Version 1.5.3.10103_102 of Kies. I also use the registry patcher with 1.5.3. it works great.
Here is Kies and the Registry Patcher I use.
What version of Android are you running at the moment?
Funkadelick said:
Well I have been following Kies "fixes" for a month and a half now, and trust me, there isn't anything I haven't read. Nothing works. I've done the 16 character deletion fix, nothing. I've uninstalled Kies and the drivers and done registry hacks, etc. for days and days. Rebooted about 500 times. Reinstalled software. Nothing.
It says everything is connected and working fine - but when I connect my phone to the USB cable KIES (2.0) just says "connecting" with an never ending loop.
I think it's a crying shame this software sucks so bad.
As stated, I may need to resort to using ODIN and flashing, which I don't want to do (because of warrenty issues)
What's the best ROM to use? I want something fast and stable. Are people flashing Gingerbread ROMS ?
Click to expand...
Click to collapse
I wouldn't worry about "waranty" issues personally just do your research before flashing is all.
Samsung S2 S3 S4 no thanks the first samsung and no more
w98seeng said:
Thousands of people on this forum flash to a different ROM everyday. Explain how you have tried to upgrade, maybe we can see if you are doing something wrong.
As for getting a different phone, the only differences in specs between the SGS and the Nexus S is the lack of a SD card on the Nexus S and it will have Gingerbread. The Nexus S works on HSDPA 1700, the SGS on HSDPA 1900
http://www.gsmarena.com/compare.php3?idPhone1=3620&idPhone2=3115
Ian
Click to expand...
Click to collapse
juinny said:
I agree that Kies is an awful program. There's just too many tweaks that you have to do just to attempt to get your phone connected.
I'd suggest getting the Motorola Atrix 4G. It's already announced on Bell and it's by far the most interesting phone yet.
Click to expand...
Click to collapse
But I heard the Atrix is coming with a bootloader locked and you can't mess around with it etc.
w98seeng said:
I do not use Kies V2, I hate it. It also does not try to update my phone, it gets to the update window but then it freezes. I still use Version 1.5.3.10103_102 of Kies. I also use the registry patcher with 1.5.3. it works great.
Here is Kies and the Registry Patcher I use.
What version of Android are you running at the moment?
Click to expand...
Click to collapse
Stock vanilla 2.1, no root, no OCLF, never touched it
I9000UGJH2
Funkadelick said:
But I heard the Atrix is coming with a bootloader locked and you can't mess around with it etc.
Click to expand...
Click to collapse
As per Moto they might change that
http://androidcommunity.com/motorol...eir-statements-on-bootloader-policy-20110120/
Funkadelick said:
Stock vanilla 2.1, no root, no OCLF, never touched it
I9000UGJH2
Click to expand...
Click to collapse
Install the Kies I uploaded and plug in your phone. If you still 2.1 on your phone, it should upgrade it to JL2. If you are still having trouble, download this JL2 here. This is the stock JL2 ROM
Use Odin to flash it, it's super easy.
Uncompress the JL2 file you downloaded
In Odin, click on PDA and choose the uncompressed JL2 file.
Nothing else gets ticked in Odin.
Plug in your phone and when Odin recognizes the phone click on start.
I have noticed that sometimes there is a fail on the first attempt, but I close Odin, unplug the phone, restart Odin, plug the phone back in and try again and it always works on the second attempt.
Ian
w98seeng said:
Install the Kies I uploaded and plug in your phone. If you still 2.1 on your phone, it should upgrade it to JL2. If you are still having trouble, download this JL2 here. This is the stock JL2 ROM
Use Odin to flash it, it's super easy.
Uncompress the JL2 file you downloaded
In Odin, click on PDA and choose the uncompressed JL2 file.
Nothing else gets ticked in Odin.
Plug in your phone and when Odin recognizes the phone click on start.
I have noticed that sometimes there is a fail on the first attempt, but I close Odin, unplug the phone, restart Odin, plug the phone back in and try again and it always works on the second attempt.
Ian
Click to expand...
Click to collapse
When he says the uncompressed file hes talking about the JL2 Tar file so there's no confusion and when he says plug in your phone and when it recognizes your phone click start your phone has to be in Download Mode. To get into download mode turn the phone off then press and hold Vol Down,Home and power.
Nexus S is a big disappointment
definitely not recommended if you are coming from a SGS
might have better luck wiht SGS v2.0 if they ever release it
Funkadelick said:
It's obvious that these Bell i9000m GXS phones are messed up with their faulty SD cards.
It's been reported the Nexus S will be coming to Bell (and later on the SGS2)
Should I try and sell my phone via craigslist / Kijiji when the Nexus S comes out ? or should I wait for the SGS 2 ?
What are you guys thinking?
These faulty SD cards are a joke of a phone, only slightly less embarrassing than the support/software
I've been trying to upgrade by 2.1 eclair to 2.2 froyo for over a month now -- tried everything and no luck. This is a f*cking joke since my old palm pre could even do OTA upgrades
Click to expand...
Click to collapse
Personally I'm really happy with my I9000m. I did fall victim of the sd card failure but when this phone works it's awesome, Im not running stock roms though. So far I only had minor problems with my replacement.
Its nice and snappy very little lag with no lag fix 150+ apps and with super curio's latest voodoo sound it's an amazing mp3 player.
I just like to point out as well that my i9000 plays flash 10x better then my ps3. I wish it had hd out though that just be amazing. As I watched quite a few movies using rogers ondemand online and the ability to stream the movies would be awesome although they are wathable on this screen . Oh yea and my 2 year daughter loves it as well . , load up some toopy and Binoo for those long car rides
Sent from my I9000m using XDA's app.
Samdroid_G_S said:
Personally I'm really happy with my I9000m. I did fall victim of the sd card failure but when this phone works it's awesome, Im not running stock roms though. So far I only had minor problems with my replacement.
Its nice and snappy very little lag with no lag fix 150+ apps and with super curio's latest voodoo sound it's an amazing mp3 player.
I just like to point out as well that my i9000 plays flash 10x better then my ps3. I wish it had hd out though that just be amazing. As I watched quite a few movies using rogers ondemand online and the ability to stream the movies would be awesome although they are wathable on this screen . Oh yea and my 2 year daughter loves it as well . , load up some toopy and Binoo for those long car rides
Sent from my I9000m using XDA's app.
Click to expand...
Click to collapse
curio's latest voodoo sound? explain please
Samdroid_G_S said:
When he says the uncompressed file hes talking about the JL2 Tar file so there's no confusion and when he says plug in your phone and when it recognizes your phone click start your phone has to be in Download Mode. To get into download mode turn the phone off then press and hold Vol Down,Home and power.
Click to expand...
Click to collapse
Thanks, I can't believe I forgot the download mode part.
Ian
You complain about the SD cards but it sounds like your real problem is Kies. Yes Kies is junk, couldn't get it to recognize the phone at all on my laptop but my desktop was randomly fine.
The SD card issue actually seems mostly resolved. Not sure if it is the new JL2 bootloader or the new hardware (new phone or new PBA like I got) but I'm not seeing many reports of SD cards dying lately.
As far as Kies I'm not letting it anywhere near my phone now. Odin'd a new kernel and now flashing ROMs is dead easy just put them on the SD card and install in recovery mode.
Yes the SD card issue was disappointing, I was without my phone for 4 weeks, but these things happen the important thing is that we get a proper fix and it seems we did. Otherwise I'm very happy with the phone, JL2 stock was good and custom ROMs are even better.
I don't see Nexus S as a good choice for SGS users even if you really hate the SGS. Not really an upgrade while the lack of microSD and video recording are downgrades. The S2 looks awesome, we'll see how the moddability and reliability are. Myself I think I will wait for the next Google-branded phone which should deliver both next-gen hardware and no-holds-barred customization.
Funkadelick said:
curio's latest voodoo sound? explain please
Click to expand...
Click to collapse
Yes Voodoo Sound Voodoo App (from the market) + Power Amp = Amazing sound quality.
Check it out here.
http://forum.xda-developers.com/showthread.php?t=806195
w98seeng said:
I do not use Kies V2, I hate it. It also does not try to update my phone, it gets to the update window but then it freezes. I still use Version 1.5.3.10103_102 of Kies. I also use the registry patcher with 1.5.3. it works great.
Here is Kies and the Registry Patcher I use.
What version of Android are you running at the moment?
Click to expand...
Click to collapse
I had flashed to a version of 2.2 but then flashed back to JH2 after my phone acting strange. (Already had it replaced once for corrupt SD). I had thought I had official Bell (BMC) version of firmware on the phone but Kies was still recognizing it as (KOR) and would not upgrade me to JL2. Anyway, thank's to your Reg Patcher I am currently getting JL2.
Many thanks
i sent my second 9000m back for repair (they replace motherboard) but on stock jl2 it was terribly laggy.. gallery would not open fc's and other apps would fc'''... and when they put in new motherboard they forgot to reflash the imei.. ..
hopefully can get a replacement.. to another phone.. my i9000t on the otherhand has been steller with no issues whatsoever..
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
everett1911 said:
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
Click to expand...
Click to collapse
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
prbassplayer said:
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
Click to expand...
Click to collapse
last time I had bothered to update cyanogen, it was a week ago. I don't remember the exact nightly build. The other roms I tried were miui, apex and something else that wouldn't boot and which I deleted quickly (apex wouldn't boot either but I spent a couple hours trying to make it work). I wiped everything prior to flashing.
as for the stock rom, it's a stock rom for the SGH-I896 (I896UXJI2), my phone model. before, the stock rom worked fine. I just can't figure out why it's suddenly not working now.
anyone? I really want to put the stock rom back into my phone.
Are you using a PIT file when flashing? If not try using this one with that package then report back.
I've already did that with odin.
and just out of curiousity, what are pit files for?
everett1911 said:
I've already did that with odin.
and just out of curiousity, what are pit files for?
Click to expand...
Click to collapse
I dont know what it exacly does BUT I know if you want to repartition your phone and you are on a AOSP like CM7 or MIUI you need a pit.
P.i.t.
Partitioning
Information
Table
Lol makes sense now
Sent from my SAMSUNG-SGH-I897 using xda premium
studacris said:
P.i.t.
Partitioning
Information
Table
Click to expand...
Click to collapse
*windows user* so it's a bit like a batch fdisk?
if so, is the internal sd card itself supposed to be wiped clean? because it didn't happen when I used mine.
Ok so using the PIT file didn't work for you. I've seen several Samsung devices suffer from a problematic internal OneNAND in the past but never one a Captivate. It's always been a TAB, i9000 or Vibrant. Can you try flashing the base files used in the Serendipity ROM? It's the stock Gingerbread installed before flashing the Serendipity ROM itself. You can find them in that thread. It will help distinguish whether you have an actual issue or whether you just need some in depth CSC scripts to help clean it up. In general that ROM has a very nicely built CSC cleanup script that is able to correct what I call "partition bricking" on the Captivate, i9000 and Vibrant. Give it a shot and report back...
Also, if that won't work, I have been able to correct this via JTAG. PM me if it comes to that. If JTAG won't correct it, then it is indeed a case of a partially dead OneNAND. It's rare but does happen.
I'll give that CSC script thing a try. What's JTAG, by the way?
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
anyone, please?
everett1911 said:
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
Click to expand...
Click to collapse
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
For2ndtwin said:
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
Click to expand...
Click to collapse
thanks but I think it's too late. while trying to flash serendipity two days ago, I used the odin flasher that site linked to, and it flashed my phone with at&t's firmware, which somehow completely ruined my phone. now, the phone won't boot, and I can't enter download mode at all. I'm not sure even a usb jig would help, and right now I don't have money for that, so I'll have to wait till I do.
And if this doesn't work, then what? All the phone does is show a spinning little circle, immobile for 3 seconds, and the phone turns off. when I insert the battery (after pulling it out), the phone automatically starts with the same screen, same result. if I plug in the usb cable, it shows the charging battery indicator, freezes, and reboots. This repeats over and over, with no end at all, and since I can't enter download mode in any way so far, I can't do anything about that. It's so bad that not even windows detect my phone, and I've plugged it into two separate computers, so I know it's not just my pc pulling a trick on me.
The worst part is that since I was using wifi tether on my phone (hello, pdanet), now I'm without any internet (right now I'm typing this on my little sister's laptop, from my dad's place.)
So... yeah.
By the way, the heimdall link is for i897 phones, even in the post for i896 phones. Is there any risks my phone will react as badly as it did with the at&t firmware?
^ I've read good things about Heimdall. Btw, if ur phone has any signs of life, then a Jig should get u back into download mode.
The fact that it was at&t firmware has nothing to do with it. Running I897 firmware on an I896 is fine. **** you can run I9000 firmware...
so many days after, I still can't get it into download mode at all. all it shows is a spinning circle, a spinning circle and then the charging battery image for a second when the usb cable is plugged in, and the AT&T world logo when the battery is low.
I could go for a solderless usb jig but even then I don't have cash for that right now (next week.), so until then I'm screwed.
I tried everything minus the usb jig, looked for many threads on the topic, and nothing works. nothing.
no matter how many times I do the battery trick or the three finger salute or the odin stuff, and it still doesn't work.
so... yeah. that usb jig better damn work.
I'll call it magic
First, I'd like to thank 4-2ndtwin for providing a complete stock rogers rom.
Second: how does a usb jig work, really? my thing's computers, software and hardware in general but not to the point of knowing how capacitors, resistors and all that stuff works, so for me the usb jig bringing back my phone from firmware limbo... that's magic. seriously.
Ok I have a stock KB2 Cappy. I used Odin to flash back to 2.1 KB1 JF6
Then I used Odin 3 to flash a kernel so I can put on CM7. I am now stuck in the Boot screen.
I have no 3 button, I cannot get into download mode (my jig is homemade should i order one?)
I tried to change usb and remove the sim card to try odin again to get back into stock.
Nothing seems to work the only thing is my jig is not good either for DL Mode. I want to get back to stock so any suggestions. I tried heimandall did not work either.
I am really stuck on this galaxy s I897 screen.
Is the jig soldered? If its not make sure you are connecting the correct pins and use some black tape or something to isolate your fingers from the resistors (might screw up the actual ohms making it to boot up normally and not in to dl mode.
The bootloop was expected, you are supposed to check that you have a working button combo both before you flash the kernel (because it will bootloop and you boot into recovery and flash whatever) and before you ever flash cm7 because that is the only way to get into download mode besides a jig on aosp roms.
so, fiddle around with your jig some more and if you get it in download mode just flash the captivate gingerbread bootloaders, that will fix your button combo and allow you to proceed flashing cm7.
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
This is probably the easiest guide on how to make one. Layman Jig First one I did I butchered a pare car charger to make it. You can just grab one from MobileTechVideos.com for about $8.
AlphaJ1 said:
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Click to expand...
Click to collapse
Hi guys,
Thanks for the link.
From what I understand, a jig is an improvised connection that allows your phone to go into DL mode. What if my phone is still capable of going into DL mode? My apologies, as I am at work.
Im not sure what you mean with your question. What the jig does is give the signal for it to go to download mode as was intended by samsung. Same theory on how your phone knows its connected to your computer, or the wall or the car charger. Its by manipulating the current between 2 pins. Keep in mind your phone should always be capable of going in to download mode assuming the hardware is working and your bootloaders are in working order.
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Read my post after yours...
studacris said:
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
Click to expand...
Click to collapse
^What he said. If that fails could be a faulty cable.
AlphaJ1 said:
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Click to expand...
Click to collapse
You are correct, if you can get into download mode you are not bricked. Make sure you are using the usb cord that came with your phone, plugged directly into the back of your computer. Make sure your SIM card is out, you're logged in as an administrator, and that you start odin before you plug your phone in.
If it still doesn't work, try another computer and/or another cord.
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
That is a practice from way back in the winmo days, sometimes the flash would corrupt the Sim itself. Not the case anymore for the most part. I'm with you never take mine out either.
Thanks guys, I will try this at home; hopefully it works.
prbassplayer said:
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
Click to expand...
Click to collapse
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
apbthe3 said:
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
Click to expand...
Click to collapse
Did you get a red "FAIL" message on ODIN? Because thats what I got several times. My buddy also tried and he got the same thing. The green progress bar completes up till about 80 percent and gives up on me. I'll try taking out the SD and SIM cards when I get home, hopefully it works.
Hi guys, little update:
I found this on the forums and used it:
http://forum.xda-developers.com/showthread.php?t=731989
Anyways, this worked after my second try. Interestingly enough, it worked once i removed the Sim card, which is what apbthe3 suggested..great! I'm just glad my phone is no longer bricked. Minor issue though, my phone is now an AT&T phone, but unfortunately, I am a Canadian Samsung user. New problem now. My phone is no longer rooted (never was actually, but was bricked in the process), I'm happy it works, but i need to know if there are any Canadians out there that know how to revert my device back to Rogers.
Any help would be great. Anyways, the link I provided works great, so its a great resource for our American friends.
Why don't you look at Cognition 4.x.x? Froyo stock ish looking rom tweaked out the ass very fast. Good rom.
Look in development. There are a couple of threads there just for Rogers users.
Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
anarchybob6 said:
Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
Click to expand...
Click to collapse
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
BWolf56 said:
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
Click to expand...
Click to collapse
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
anarchybob6 said:
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
Click to expand...
Click to collapse
Start by flashing Odin KK4 from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 - That will clean your phone of w/e was on it before.
From there, you can flash Corn Kernel to get back to a JB ROM. Although, know that if you had the wrong bootloaders, your phone wouldn't boot and it would show color stripes.
Also, before flashing a ROM, you should wipe system and factory reset to make sure everything is clean (Backup your stuff first).
BWolf56 said:
...your volume down is probably stuck or dirty, making your phone go in download mode all the time...
Click to expand...
Click to collapse
I had a similar problem with my Sprint Galaxy S2 D710 (Epic 4G Touch) - my phone would randomly reboot every few days, and it kept getting more frequent. I thought it was the ROM, the overclock, etc. I flashed back to a stock ROM, and stock clock speeds. Eventually, I noticed that even brushing the power button would wake the screen, and about 10 seconds later the phone would reboot. I cleaned the button with some 95% isopropyl (rubbing) alcohol, and it worked better for a few weeks. It started acting up again, so I bought and installed a replacement power button.
Long story short, I got a new power switch, soldered it in place, and have had zero problems since!
The i897 Captivate uses the same switches for power and volume up/down. These switches are notorious for failing, so that's probably the issue with your phone. Try cleaning them, or you can buy a new switch for about ten bucks on ebay.
YouTube has numerous "teardown" or "disassemble" videos and several eBay sellers offer the switch you'll need.
(They don't include the skills needed to replace it. It's a tiny switch - about 4mm long, and you'll need a good soldering iron and a steady hand. Do you have a friend who's pretty good at soldering stuff?)