Database Develop

[Q] How do I root a Samsung Captivate with the basebuild KB1?

I having been trying to root and unlock my Samsung Captivate and I have constantly been hitting dead ends. I have tried various apps and YouTube clips and nothing seemd to work. I know someone out here can help me unlock this phone. I rather learn how to unlock it than pay $50. I NEED HELP!!!!
Phone Specs:
I don't have AT&T Sim Card
Base: i897uckb1
Firm: 2.2
Kernal: 2.6.32.9
I am new to this "unlocking and rooting" world, so I have been learning while i'm going, please bare with me in advance.
The last program I ran to unlock the phone was "OneClickUnlock." After it went through its whole deal, my phone read - "E:signature verification failed". I have no idea what to do from here...PLEASE HELP ME SOMEONE!!!!

There are plenty of threads that cover both these issues.

sensai62 said:
I rather learn how to unlock it than pay $50. I NEED HELP!!!!
Click to expand...
Click to collapse
what you need to do is read. thats how you learn

i would agree with pirateghost but i find that people do things all @$$ backwards around here and give out the most time consuming ways to do things.
ok you already have the odin one click installer, is that the one the brings it to jf6?
does the phone boot? or does it enter recovery and give you that message?
since setting up adb might be too much too soon the best way will be to get the phone back to a bootable state if it is failing to fully bootright now. if the phone is a newer model and came factory installed with kb1 it is posible that you need a different one click installer, infact dont bother with the one click installers, it is faster to use the full oding to flash a kernel with cwm installed by default.
http://forum.xda-developers.com/showthread.php?t=1007276&highlight=rogers+stock+rom
this is the rogers 2.2 rom, first one i found and better anyway. use the odin and pit and .tar in the downloads in that thread.
select repartition for good measure and flash the the above rom, the .tar goes in the pda slot. the 512.pit goes in the .pit slot, that's all that is needed.
after you flash your phone back to working condidtion, use odin to flash a custom kernel, the kernel must be in .tar format
http://forum.xda-developers.com/attachment.php?attachmentid=547852&d=1300708475
^this is speed mod, maybe the most popular and stable, if the phone will boot into the rom then you can start here.
put the kernel .tar file in the pad slot in odin and flash it in download mode, no .pit is needed.
with this kernel you can flash .zip files. you can root or skip strait to flashing a rooted rom, you may also have luck with one of the att kb1 kernels with modifications like skull cap or firebird if you like the stock rom, which the bluetooth calling needs an att or a rogers kernel and modem to work.
most people arent .tar-ing the kernels they build. yet all the users like to flash to stock before a flash, seems to me since you are sitting at odin, flash a kernel and shorten the whole process.

The reason you get the signature failed is because your recovery mode is a type called 3e the 3e recovery mode doesn't allow unsigned packages such as the unlock. What you need to do is get a kernal that has the 2e recovery mode in it and flash that, then you can root using anything and flash update. Zip files, you will need to follow a guide for that though, you can find one by searching "flash 2e kernal on captivate" in google
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Press thanks!

CWM Help?

So, just switched out my captivate because my warranty was still in effect. Rooted etc etc. But I remember installing CWM with rom manager to begin flashing my first rom back in the day.
But anywho, I have installed ROM Manager, clicked to flash CWM but when I go into recovery (vol + - & Power) All I get is the samsung one. (Blue text) and I only have the options to reboot, install packages, clear cache or wipe sd card.
Can anyone offer any advice?

^ Try reinstall packages. U may have to do it twice.

Gotta install the update.zip with install packages but you have signed bootloaders if you're on stock froyo. Odin to 2.1 and install cwm from there. You can find the update.zip for cwm on the cappy forums and just put that on the root of your internal memory to avoid using rom manager. Don't even have to root to flash.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Hmmmm do you have the stock odin pit file/pda or is the old school odin where you couldnt even do that shoot you right back to 2.1?

^ If u want to go back to Stock Eclair...use the first link in my signature below.

I typically use Odin jf6 one click rev0 from designgears. Its still on the forums I believe but might be dead link. Just make sure it has the pbl and sbl. If you are worried I can upload the one I have used for the past 9 months without fail( but ffailure is always possible, just be sure to follow directions and you should be alright. ) alternatively there is a guide to get to stock jh7 on the forums using the Odin that you have to manually select files for. Should be an easy search. I believe people consider this safer for the newer builds but I used oneclick on my 1010 tons of times and have used it once on my 1012 no problems.
Sorry for the long post hope I helped
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

You all have helped. Thank you so much. Running MiUi again and still loving it.

[Q] Questions about preventing a second hardbrick

This is how the story goes, bear with me.
I had an ATT Captivate 1012 running on S7 but it was rebooting on me during phone calls. I decided to go back to stock with odin oneclick as I had read it works with 1012s but the process hung. I managed to recover and flashed back to stock JH2 with the non-one-click version.
I followed this guide by Breakin' Ranh
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I had used it successfully to get to stock before many times.
This is where I think I screwed up, please correct me if im wrong.
I thought that taking me back to JH2 would restore my bootloaders and allow me to install the 3buttonFix.zip via CWM over stock JH2, but after installing that zip my phone didnt boot up since.
The 3ButtonFix.zip I used was from this thread http://forum.xda-developers.com/showthread.php?t=1134443 . Via CWM, not Odin.
My battery was not at 100% (checked with a friend's phone and it was at about 24% so I'm not sure if that was the issue.
The question is, wouldnt have flashing to JH2 wipe out the bootloaders S7 installed (i9000 GB loaders if im correct)
I can only think of few things and would appreciate, if possible, your thoughts about these, all in an effort to learn more about the process and to reduce my chances of hardbricking again (Got a new captivate, 1010 this time)
1) JH2 bootloaders are clearly not compatible with that 3ButtonFix.zip because it perhaps assumes an underlying JF6 base? I was on JH2 when i flashed the 3ButtonFix.zip linked above
For future reference, should i then go JH2->JH7
This is the JH7 i have used before the 'accident'
(it is linked in the thread above)
I897UCJH7 Firmware
http://www.ponack.net/designgears/JH7_OTA.zip
2) The JH2 .tar provided in that thread did not /*correctly*/ install all? captivate bootloaders?
3) The flash to stock with the above guide didnt clear out my bootloaders successfully. The first time i tried to flash with odin oneclick it failed so i had to start over with the non-oneclick, that's how i managed to successfully get into JH2.
4) Perhaps flashing with a low battery (30% or so) ruined the install of 3buttonFix.zip?
Maybe I botched my flash via odin only to ruin it further with 3buttonFix.zip via CWM.
Would you recommend heimdall for all my (new) flashing endeavours? I _reaally_ don't want to go through the jtagging/phone replacement experience again.
Would have flashing the Odin version of 3buttonFix have prevented this? or maybe using heimdall to get back to stock?
What do you recommend i do to avoid these problems in the future? Stay away from 3ButtonFix.zip and just use a usb jig (finally got one *AFTER* hardbricking).
TL;DR
I read on the forums that people have bricked by ruining their sbl.bin by coming from a gb bootloader. But I was under the impression (apparently incorrect) that flashing to stock (Any stock froyo/eclair?) would prevent such issues. What do you think went wrong?
Sorry for the 20 questions :|
Thanks!
-XercesBlue

That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Did you even try the button combos BEFORE you flashed the fix? You shouldn't have needed it at all...
Just forget that the 3 button "fix" even exists.

studacris said:
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Click to expand...
Click to collapse
Thank you for your reply studacris.
So the I897UCJH2.tar package I linked to does not contain bootloaders? If so this makes muuuuch more sense now. Should I find a package that contains those "stock" bootloaders to restore the phone into a stock state then ?
Will the packages linked at the bottom of this thread work then?
http://forum.xda-developers.com/showthread.php?t=731989
The "The internal beta's are NOT one-click, please read the linked threads
UPDATE: I897UCJH2 (Internal BETA)" ?
Do you have any ideas how that one is different from the I897UCJH2.tar I flashed following Breakin' Rahn's. If you follow the link you will see they link to the same files I had used during my first hardbrick.
Reading some more I stumbled upon your old reply,
http://forum.xda-developers.com/showpost.php?p=13581072&postcount=1798
So, If i get this right and to reiterate
For 1010s to get back to stock+bootloaders
1) OneClick (http://forum.xda-developers.com/showthread.php?t=731989)
OR
Use the internal betas "I897UCJH2 (Internal BETA)" linked at the bottom of the same thread ??
2) Do this http://forum.xda-developers.com/showthread.php?t=995143
If you run into a bootloop
OR this
http://forum.xda-developers.com/showthread.php?t=963403
?
I hope you understand how I can be a bit confused here.
I had no luck previously with OneClick on my 1012. Maybe the 1010 is different but i doubt it. The process hung at some point and had to start over with Breakin'Rahn's guide. Finally got to stock by perhaps without bootloaders.
---
As for the combos, when on s7 the combos worked. Volume down+power worked as expected for dl mode volume up + power for recovery. Upon flashing the new package I lost them leading me to assume incorrectly I was at a new factory mode.
The power down, remove battery, hold power, put battery, plug usb did not work either when on JH2. Of course, me being new at this I might have missed something.

only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.

studacris said:
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
Click to expand...
Click to collapse
Great, thank you for taking the time to read/reply!
Yes, I am definitely staying away from 3buttonfix.

XercesBlue said:
Yes, I am definitely staying away from 3buttonfix.
Click to expand...
Click to collapse
BUT, Im on a 1010 and the vol up + vol down and power buttons wont get me into recovery.
What method should I use to get into recovery?

If you have the gingerbread bootloaders the combo will work. The combo is in the secondary bootloader...

[Q] Galaxy S i9000 softbricked; won't enter recovery or reflash from download mode

Similar to Masterslackers issue.
The phone was originally a stock Optus Éclair 2.1. About 6 months ago I decided to customize the i9000 with a custom Froyo 2.2.1 Rom (Doc's Rom Docs_XWJS3_Wipe-v9_1) from “The ROM Kitchen”. It worked really well and was much faster and responsive..
Yesterday, I decided to look at a move to Gingerbread and cook another ROM @ the ROM Kitchen, this time a Gingerbread 2.3.4 iteration.
The phone was rooted so I used Rom Manager to get into recovery mode where I could flash my new, Doc's JVR_No_Wipe-v8-00-08-22-10-09-4e6a8e4e86718.zip Rom.
All seemed to go well, but after the Flash, as the phone booted the first screen became filled with 100s of random coloured lines, then it transitioned to the normal Samsung start animation, but soundless.
After booting, I noticed that I no longer had a notification bar where battery, time, signal strength etc. was normally displayed atop the screen. I tried several different launchers to see if that was the issue, but to no avail. I tried to enable the notification bar using Go Launchers gesture setting (no go)
I tried rebooting the phone over and over, the notification bar would not return.
I was starting to lament my decision to flash when the following occurred.
I tried to re-enter recovery mode via ROM Manager to install a different ROM, but the phone bypassed it and then hung @ the Samsung I9000 logo screen. I then had to power the phone off before it would reboot into its UI. I could no longer reach recovery mode by any means.
Because I was getting nowhere and I had read that after flashing a new rom, root would often be lost, so I tried rerooting with "XXJVP-Complete-Rooting-Package" from
http://androidadvices.com/how-to-root-galaxy-s-on-android-2-3-4-xxjvp-firmware/ This also failed but it has also left me with a soft bricked phone.
The phone will not boot up or boot into recovery now, however It would still boot into (3 button) download mode.
I have tried various versions of Odin from v1.0 to v4.28 to ReFlash the phone back to life but with no success yet.
Using Odin, the phone hangs with no sign of progress and reports the following when left for 30minutes or so.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
Anyone have any suggestions that might help to get the phone back.
Thanks, TeZ

So you didn't flash stock gingerbread before flashing custom rom? so you should first flash stock jvr and do hard reset after booting. Then you are safe to flash cwm capable kernel and custom rom.
For the odin problems, maybe you have kies running in background? Kill all kies processes and try again.
And I'd suggest reading all guides found in romkitchen thread..it saves lots of trouble. Hope that can fix your phone
Sent from my GT-I9000 using xda premium

Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.

After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck

Thanks for that, I did install kies after I bricked it, in the hope (probably missguided) that it would somehow help. Uninstalling

bigmadpete said:
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
Click to expand...
Click to collapse
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.

DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Your post looks promising, I'm going to try this method out and see where it leads. I'll reply back with the outcome, many thanks

No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/

bigmadpete said:
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
Click to expand...
Click to collapse
Thanks for the info, running out of time today, will try for tomorrow

When moving from a froyo (2.2) rom to gingerbread, (2.3), you need the gingerbread bootloaders or you'll get all sorts of crap when turning on your phone (ie what you have).
Use odin to flash back to froyo, or flash a gingerbread firmware that comes with bootloaders. (I would recommend going back to froyo first to make sure everything is ok, since flashing bootloaders is a bit risky, as messing it up can permanently brick your phone)

cobrasixtysix said:
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
Click to expand...
Click to collapse
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Ok, here's where I'm at:
For the sake of simplicity I will detail what gave positive results rather than a tirade of what didn't.
Uninstalled Kies, rebooted
As instructed, went to:
http://forum.xda-developers.com/showthread.php?t=1102881
downloaded: Odin v1.82
downloaded: Gingerbread 2.3.3 (Australia and New Zealand)
XWJVN/XXJVQ/XSAJV5/Sbl (CSC: XSA): Download (150 MB) (Build date: Sun Jul 10 11:30:54 KST 2011)
Loaded up Odin and followed instructions.
Flash went ahead as normal and I now have a working phone again, thanks to you DSGE, I'm a very happy man
So I now have Gingerbread 2.3.3 installed and running.
My only issue's now is, that.
1. Half my apps dont work now or force close even after a reinstall.
2. Some apps won't install at all IE; my fav launcher; Go Launcher
3. I no longer have root access so Rom Manager and Titanium backup wont work.
4. My Backup Pro, works after I rewrote the correct path to the External Sd, but do I want to do that just yet? and just how much data should I reinstate so I don't corrupt the new system?
What should I do now?
Install busybox?
do a hard reset?
Flash a different Rom that will work for me?
Thanks so very much for all the good advise.
Cheers

First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery

bigmadpete said:
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
Click to expand...
Click to collapse
OK, latest update:
Everything is working fine including all my progs.
Like you say, I just need to root it now.
Can you point me to the correct files to root?
Thanks

http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend

bigmadpete said:
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
Click to expand...
Click to collapse
Seems to relate to 2.1 to 2.2.1 didn't see any mention of 2.3.3. I'm afraid I'll stuff the phone if I use the old root files.

[Q] Unable to change Roms without going to stock

having a wierd problem, as the title says i am unalbe to change roms and have it boot.ever since i flashed the ROGERS 2.3.3 (containing i896 ROGERS bootloaders)
no big surprise i didnt like it.
while reading this keep in mind i have alot of experience flashing, and yes lagfix was disabled!
odin flashed a CWM kernel (one was using before rogers)
restored Nandroid. (of before ROGERS)
stuck at kernel screen
Flashed different kernel compatible with rom.
stuck at kernel screen
Loaded CWM to flash a custom rom.zip
flashed OK
reboot stuck at kernel screen
Odin flashed i9000 gingerbread (with i9000 GB bootloaders) from few months ago
stuck at kernel
Odin flashed ROGERS 2.1 eclair stock.
stuck at kernel
Odin flashed ATT one click
SUCCESS!!
Odin flahsed Rogers 2.1 eclair
SUCCESS!!
ODIN flashed i897 ATT GB bootloaders
ODIN flashed CWM kernel CWM flash ROM
Restore NANDROID
SUCCESS!!
finally back to normal...**never flashing rogers 2,3,3 again!
or so i thought.
got bored and went to flash a different ROM
STUCK AT KERNEL
had to repeat all above steps!! ALL before it was back to *normal* again
any thoughts to what got permanently messed up????

Did you try reformatting system and cache before flashing a new ROM in cwm? (i'm just guessing here)

yes and the Odin one click re-partitions - wiping everything known.but still the problem exists after flashing my 1st custom rom i am unable to boot into a second ANY rom (stock or custom)
and this is VERY frustrating as i just finnished my own custom ROM and am unable to quickly flash test versions.!!

I don't know. Odin one click should have fixed everything. Did you master clear/reformat the internal Sd?

no not the internal sd.
also i remembered at one point right after being on ROGERS stock 2.3.3
the first rom i tried flashing was a custom build I made with a kitchen tool using cygwin.
anyways after flashing and failing, i noticed the update script i created flashed the zimage to 2 different dev/bml blocks!! one i never seen before.
i stopped using that kitchen tool but is it possible it flashed something to a dev block that odin one click isnt clearing? but it repartitions. that should clear EVERYTHING!
still my problem presists...
flashing issues. cracked screen. might be time to buy a new phone.....

You could use Heimdall to dump your partitions and find out.

Heimdall print-pit...in case u didn't know
Sent from my SGH-I897 using xda premium