Database Develop

[Q] Help! Whats wrong with JPC's recovery?

Hi, I just flashed JPC to my Samsung Galaxy S international version using odin with 512 pit file(Not sure if i'm suppose to use 512 or the new 803 pit file). Everything went fine and I simply love the froyo. Have not encountered any problems but instead, lots of new features.
Then i started wanting to use the stock recovery(3e) to apply update.zip to use the spitfire's mod batt, wpa_adhoc and clockworkmod recovery. But non of these can be applied. The stock recovery always shows error 'Failed to verify whole file Signature' , 'Signature verification failed'. But when I got the mod batt and wpa_adhoc update.zip files, they were said to be signed and i choose the correct files for JPC firmware. What is wrong?

hxxp://forum.samdroid.net/f49/root-superuser-2-3-5-working-recovery-i9000xxjpc-froyo-2148/
Root the phone again with the method listed above..basically change the recovery section that accept unsigned update.zip.
I dont know will it work..but it should.

Thanks for the link, will try when I get home - not much point having a custom froyo rom if you can't flash unsigned update.zip's!

hmanxx said:
hxxp://forum.samdroid.net/f49/root-superuser-2-3-5-working-recovery-i9000xxjpc-froyo-2148/
Root the phone again with the method listed above..basically change the recovery section that accept unsigned update.zip.
I dont know will it work..but it should.
Click to expand...
Click to collapse
my JPC is currently rooted, should I just redo the steps right away ?

EarlZ said:
my JPC is currently rooted, should I just redo the steps right away ?
Click to expand...
Click to collapse
Yes, simple do all steps again

I downloaded the firmware XXJPC in update.zip in the same topic, you can try to install it via recovery. And now do not need to flash a special kernel with Odin to update XXJPC

Ok. Will try when i get home. Thanks for the link.
Sent from my GT-I9000 using XDA App

Flashed jpc via Kies a couple of days ago. The rom is not stable and reverted back to stock DDJG4.
Since I flashed via kies, i never had problems with recovery.
Sent from my GT-I9000 using XDA App

I tried the method and i got the latest superuser. However, i still get errors running update.zip on the recovery (2e). I was trying to update the wpa adhoc file. Anyone had luck updating update.zip files?
Sent from my GT-I9000 using XDA App

siaoz85 said:
I tried the method and i got the latest superuser. However, i still get errors running update.zip on the recovery (2e). I was trying to update the wpa adhoc file. Anyone had luck updating update.zip files?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I have no problem using recovery 2e. I deodexed my rom and placed them in the update.zip, to replace those odex files. It ran well without the error message.
CWM will not work at this moment, because the file structure between 2.1 and 2.2 is different. CWM looks for /sdcard/ but froyo 2.2 is mounted as /mnt/sdcard, hence it just stops there.
I believe CWM can be tweaked to enable a full backup for froyo.

somberi said:
Flashed jpc via Kies a couple of days ago. The rom is not stable and reverted back to stock DDJG4.
Since I flashed via kies, i never had problems with recovery.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Of course, because the recovery is 2e for DDJG4. ZSJP2 and XXJPC uses recovery 3e, which there is a form of signature verification implemented.

g00ndu said:
I have no problem using recovery 2e. I deodexed my rom and placed them in the update.zip, to replace those odex files. It ran well without the error message.
CWM will not work at this moment, because the file structure between 2.1 and 2.2 is different. CWM looks for /sdcard/ but froyo 2.2 is mounted as /mnt/sdcard, hence it just stops there.
I believe CWM can be tweaked to enable a full backup for froyo.
Click to expand...
Click to collapse
Can you assist me to see if u can.install the update.zip for the wpa adhoc hack? Coz i got an error running it.
Sent from my GT-I9000 using XDA App

[Q] What's the relationship between Odin and Rom Manager

Could anyone told me what's the relationship between Odin and Rom Manager
I wanna upgrade captivate from 2.1 to 2.2, so i read some guides
It seems that some guides told me use odin and need the adb shell or combine keys to enter downloading mode.And then flash the pit,and csc,phone,pda.
But meanwhile, some guides said just put the rom in sd card and reboot the phone by Rom Manager.
So i get confused,could anyone told me which should i listen?
By the way,if the phone is locked 3 keys, does rom manager still work?

Odin is the a flashing tool that is run from the PC. Rom Manager is a tool that is run from the phone itself. It depends on what rom you want to flash, some of them are built to be flashed from Odin, and as such won't flash with Rom Manager and vice versa. Other than they are both flashing tools they don't really have a connection.
As to the question regarding if rom manager will work with no-button-combo phones, I'm pretty sure it will, but don't quote me on it.

Trump211 said:
Odin is the a flashing tool that is run from the PC. Rom Manager is a tool that is run from the phone itself. It depends on what rom you want to flash, some of them are built to be flashed from Odin, and as such won't flash with Rom Manager and vice versa. Other than they are both flashing tools they don't really have a connection.
As to the question regarding if rom manager will work with no-button-combo phones, I'm pretty sure it will, but don't quote me on it.
Click to expand...
Click to collapse
Thanks,you means these two tools can do exactly the same thing,but the rom source is different?
The rom manager can use a .zip rom contains data/META-INF/system etc. folders?
And the Odin should flash the rom which contains *.pit,*.tar,*.tar.md5 ?
By the way, i saw the 2.1 don't support the recovery etc. from apps, does that means rom manager doesn't work in 2.1? (I already read the 2.2 guide, and it said just use the rom manager)

Yeah, both are tools used to flash roms to your phone. However a rom made to be flashed by odin can't be flashed with Rom Manager, and a rom made to be flashed by Rom Manager can't be flashed with Odin. Some developers make two versions of the same rom so that you can flash it with your preferred method.
The last thing you mentioned is backwards... 2.1 uses recovery 2e which allows for the use of self-signed update.zips (this is what RomManager uses to get into clockwork recovery which is a modified recovery that does the actual flashing). However 2.2 uses recovery 3e which doesn't allow for this.
This means that if your on 2.1 presently you can flash with RomManager (you can even use RomManager to flash from 2.1 to 2.2), but if your using 2.2 your only flashing option is to use Odin.
Once on 2.2 you can use Odin to flash a modified 2e recovery that works with froyo and you will once again be able to use self-signed zips. (some of the unofficial roms like cognition do this automatically so you don't have to)

Trump211 said:
Yeah, both are tools used to flash roms to your phone. However a rom made to be flashed by odin can't be flashed with Rom Manager, and a rom made to be flashed by Rom Manager can't be flashed with Odin. Some developers make two versions of the same rom so that you can flash it with your preferred method.
The last thing you mentioned is backwards... 2.1 uses recovery 2e which allows for the use of self-signed update.zips (this is what RomManager uses to get into clockwork recovery which is a modified recovery that does the actual flashing). However 2.2 uses recovery 3e which doesn't allow for this.
This means that if your on 2.1 presently you can flash with RomManager (you can even use RomManager to flash from 2.1 to 2.2), but if your using 2.2 your only flashing option is to use Odin.
Once on 2.2 you can use Odin to flash a modified 2e recovery that works with froyo and you will once again be able to use self-signed zips. (some of the unofficial roms like cognition do this automatically so you don't have to)
Click to expand...
Click to collapse
Hmmm, can this be the problem i got? Flashed from JH to Cognition 2.2B6 via rom manager, and made a backup before. Now when i'm trying to flash back the backed up JH (2.1) rom my phone is stuck on AT&T screen....
edit: with cognition 2.2 i still got 2e recovery and not 3e....

Thanks,I think i got it. It seems that developer in China always package the rom into Odin struct, so i didn't tried Rom Manager.
And dimab, I think what you need is search "Captivate JI6 kernel with "2e recovery" enabled" (I can't post link since i was new user)

rogerhe said:
Thanks,I think i got it. It seems that developer in China always package the rom into Odin struct, so i didn't tried Rom Manager.
And dimab, I think what you need is search "Captivate JI6 kernel with "2e recovery" enabled" (I can't post link since i was new user)
Click to expand...
Click to collapse
thanks
I've seen this topic, but i do actually got the 2e recovery running, so what's the point?

dimab said:
Hmmm, can this be the problem i got? Flashed from JH to Cognition 2.2B6 via rom manager, and made a backup before. Now when i'm trying to flash back the backed up JH (2.1) rom my phone is stuck on AT&T screen....
edit: with cognition 2.2 i still got 2e recovery and not 3e....
Click to expand...
Click to collapse
well first off you still have 2e because Cog 2.2 Beta 6 uses a modified 2e recovery (its modified to work with froyo)
I think that when you create a backup of your rom with RomManager it doesn't include a backup of the kernel. If so when you tried to flash your 2.1 backup it never switched your kernal back to a 2.1 compatible version. hence the not booting past the att screen.
You might want to try flashing just the kernal (not the whole rom) with ODIN... Or even easier if you have your backup on your computer you can odin 1click back to stock, put your backup back on your phone, and flash the backup again with RomManager.

Trump211 said:
well first off you still have 2e because Cog 2.2 Beta 6 uses a modified 2e recovery (its modified to work with froyo)
I think that when you create a backup of your rom with RomManager it doesn't include a backup of the kernel. If so when you tried to flash your 2.1 backup it never switched your kernal back to a 2.1 compatible version. hence the not booting past the att screen.
You might want to try flashing just the kernal (not the whole rom) with ODIN... Or even easier if you have your backup on your computer you can odin 1click back to stock, put your backup back on your phone, and flash the backup again with RomManager.
Click to expand...
Click to collapse
Woah, this did helped! HUGE thanks! First time used Odin 1Click and it was smooth, and then restored my 2.1 backup.
Didn't needed to backup on computer the rom backups, since everything was left the same...
Dima

anyone please,

ive tried so many of all of your roms and cant find the answer for this. i just came back from being on a gingerbread rom (simply honey) and i tried going to toxic music but tokic got stuck for 20 minutes on the bali kernel screen. now i cant get into the recovery option (reinstall packages) so i can root. it wont let me. it says no such file or directory. ive done this about 60 times and never came across this problem. i cant get root access to add other roms. can someone please point me in the right direction...PLEASE!

Wrong place! But gb roms have a diff method for getting into download mode
Sent from my SGH-T959 using XDA Premium App

Did you install GB Bootloaders?
Edit: Read OP wrong

childspsongs said:
ive tried so many of all of your roms and cant find the answer for this. i just came back from being on a gingerbread rom (simply honey) and i tried going to toxic music but tokic got stuck for 20 minutes on the bali kernel screen. now i cant get into the recovery option (reinstall packages) so i can root. it wont let me. it says no such file or directory. ive done this about 60 times and never came across this problem. i cant get root access to add other roms. can someone please point me in the right direction...PLEASE!
Click to expand...
Click to collapse
Yep. This certainly will occur after coming from gingerbread. Load up Odin and flash back to stock, reroot your phone as you normally would. Flash a 2.2 kernel and a 2.2 modem and try to flash. Its seems like you might have some Ginger Ghost left from gingerbread rom and its causing conflict coming back to 2.2 or 2.2.1. Are you able to get in download mode? If so you'll be ok.

Saxysaxplayer said:
Did you install GB Bootloaders?
Edit: Read OP wrong
Click to expand...
Click to collapse
That's what I'm thinking...

deleted post

I did use gb bootloaders. Please point out where the print modem and kernel are please. I already am on stock. And I can get into download mode fine. Thank you guys. I know im not inthe right thread but you guys are the right people.

childspsongs said:
I did use gb bootloaders. Please point out where the print modem and kernel are please. I already am on stock. And I can get into download mode fine. Thank you guys. I know im not inthe right thread but you guys are the right people.
Click to expand...
Click to collapse
go into download mode and odin to stock
http://www.youtube.com/watch?v=l3K9my9kAvI
you will use same files but different key combination to get into download mode...

That key combination is vol up+power for download mode...at least I'm pretty sure.

jcc332006 said:
Yep. This certainly will occur after coming from gingerbread. Load up Odin and flash back to stock, reroot your phone as you normally would. Flash a 2.2 kernel and a 2.2 modem and try to flash. Its seems like you might have some Ginger Ghost left from gingerbread rom and its causing conflict coming back to 2.2 or 2.2.1. Are you able to get in download mode? If so you'll be ok.
Click to expand...
Click to collapse
that is the problem though. I can get to download mode. I can go back to stock. I can download the root file. I can go to recovery . ....but I can not load it. red typing comea up when I try to reinstall packages and it says It cant install from sd. how can I obtain root if I cant load it from recovery? Can I use odin for your music rom? I just need root. Killing myself trying to figure this out.

Did you put the update.zip on the root of your SD. or in some other file.?

That is also my suspicion. You probably don't have the update.zip in the main directory of your phone's sd card. If its not there, you can simply transfer it back in via usb...

that was it. i had a file called rootupdate.zip and i thought that was the one but i guess it wasnt because nothing was happening. so i looked again in my external sd and still had the original update.zip file, transferred it and it worked. happily rooted again! thank you guys for your help. maby i should delete this thread now.

Instead of rooting JFD and flashing CWM just flash a voodoo+stock kernel. you'll have cwm faster than rooting then getting cwm

philliple97 said:
Instead of rooting JFD and flashing CWM just flash a voodoo+stock kernel. you'll have cwm faster than rooting then getting cwm
Click to expand...
Click to collapse
is there a stock voodoo kernel .tar though ??
cant flash without root

[Q] Captivate ODIN doesnt see Cappy, in DL mode too

In normal running mode ODIN sees the Cappy, but when I switch to download mode it doesn't see it any more. I am trying to put my phone back to factory default so I can install CM7 but running into all kinds of problems. I did get the base system reinstalled using a One Click JAR that I found here on XDA. The phone seems to be ok with that.
ADB doesnt think there are any devices attached either when I am in download mode.
I did also try the Heimdall install methods and used their drivers, but that doesnt work either
All I am trying to do so far is get CWM installed
Any ideas?

Did you ever use Heimdall?

MarkWorsnop said:
In normal running mode ODIN sees the Cappy, but when I switch to download mode it doesn't see it any more. I am trying to put my phone back to factory default so I can install CM7 but running into all kinds of problems. I did get the base system reinstalled using a One Click JAR that I found here on XDA. The phone seems to be ok with that.
ADB doesnt think there are any devices attached either when I am in download mode.
I did also try the Heimdall install methods and used their drivers, but that doesnt work either
All I am trying to do so far is get CWM installed
Any ideas?
Click to expand...
Click to collapse
If you used a one-click jar file, I believe you used Heimdall, as Odin-based one-clicks would be .exe files. That being the case, if one of the one-click heimdalls worked, other ones should work as well.
If you don't mind me asking, which one-click did you use? What rom were you on when the other one worked, and what rom are you on now?

I installed this "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" to get it to work in what I think is a factory default.
I am now trying to get the downloading to be recognized by Odin or Heimhall or anything/.
They all see the phone in normal mode but when in download they do not see it

Have you tried all of the USB ports on your computer? If you're on a desktop, make sure it's one of the ones in the back (directly attached to the motherboard). Also, if you haven't rebooted your computer, do that, and then see if the UCKB2 one-click sees your device.
You can also try the full heimdall package, as that has a tool that will quickly check to see if it sees a device in download mode.

ODIN doesnt see Cappy
Looks like the drivers from Heimhall mess up the ODIN drivers. I removed the drivers from System Drivers that the Heimhall installed and now the ODIN seems to see the device again.
Now I need to figure out what I need to put on the device to make it work

MarkWorsnop said:
I installed this "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" to get it to work in what I think is a factory default.
I am now trying to get the downloading to be recognized by Odin or Heimhall or anything/.
They all see the phone in normal mode but when in download they do not see it
Click to expand...
Click to collapse
einstall the Samsung drivers. The zadig driver you installed for Heimdall causes problems with dl mode if you then try to use Odin.

mrhaley30705 said:
einstall the Samsung drivers. The zadig driver you installed for Heimdall causes problems with dl mode if you then try to use Odin.
Click to expand...
Click to collapse
I just figured this out. Now what CWM file does ODIN want? After all of this I am lost! I will start back at the first post on adding CWM I guess...!!

It's going to want a kernel with CWM baked into it, or you can flash the JF6-based one click file to get back to stock without the 3e recovery error. From there you can just root, then copy the rom you want to install to your internal SD card. Rename it "update.zip", and flash that.
If memory serves me correctly, that's the simplest way to flash from Eclair. You can also try to Odin in a CWM-friendly Froyo kernel, or copy the cwm file out of the AIO captivate toolbox (copy it out, don't directly use the tool).

To get cwm, use a kernel with cwm as jimtheiss said, in a tar format. Older Talon kernels were in tar, as was Speedmod, and I think xcal's reoriented kernel had a tar version.
Open Odin, use the pda slot for the kernel, uncheck reboot. Connect phone. When the yellow box lights up, hit start. When completed, pull the battery,reinsert battery, use button combo to get in recovery.

jmtheiss said:
It's going to want a kernel with CWM baked into it, or you can flash the JF6-based one click file to get back to stock without the 3e recovery error. From there you can just root, then copy the rom you want to install to your internal SD card. Rename it "update.zip", and flash that.
If memory serves me correctly, that's the simplest way to flash from Eclair. You can also try to Odin in a CWM-friendly Froyo kernel, or copy the cwm file out of the AIO captivate toolbox (copy it out, don't directly use the tool).
Click to expand...
Click to collapse
I can't seem to find Eclair with CWM. I did find a I897UCJF6-final-OCD-REV0 EXE with ODIN built into the EXE but whatever happens on that version ODIN didnt see the phone.
The ODIN 1.85 sees the phone, but I do not know what to download and what there downloaded file goes in ODIN.
I also ran the JAR file again and it did get back to 2.2 but then I dont seem to be able to get CWM working.
All I wanted to do it put CM7 on the phone. I guess I have to have Eclair or Froyo first to get the CM7? I think that is what I read. I havent tried it from GB

I would suggest following mrhaley's directions about flashing the kernel.
And here is the speedmod kernel.

MarkWorsnop said:
I can't seem to find Eclair with CWM. I did find a I897UCJF6-final-OCD-REV0 EXE with ODIN built into the EXE but whatever happens on that version ODIN didnt see the phone.
The ODIN 1.85 sees the phone, but I do not know what to download and what there downloaded file goes in ODIN.
I also ran the JAR file again and it did get back to 2.2 but then I dont seem to be able to get CWM working.
All I wanted to do it put CM7 on the phone. I guess I have to have Eclair or Froyo first to get the CM7? I think that is what I read. I havent tried it from GB
Click to expand...
Click to collapse
My 2 cents....if you have so much difficulty using Odin/Heimdall, I would highly recommend staying away from CM7 or MIUI until you are really comfortable flashing stuff without hiccups. CM7 and MIUI are quite different beasts, compare to the ROms ur flashing.

chappatti said:
My 2 cents....if you have so much difficulty using Odin/Heimdall, I would highly recommend staying away from CM7 or MIUI until you are really comfortable flashing stuff without hiccups. CM7 and MIUI are quite different beasts, compare to the ROms ur flashing.
Click to expand...
Click to collapse
The only thing he needs to flash with Odin/Heimdall is the kernel to get cwm. Its the same for most other GB roms. After you get cwm, its just flashing from cwm, with an extra factory reset and ROM flash.

Cant enter into recovery/cwm after flashing franco

Hi, i installed franco kernel the r1 a few days ago using cwm, today i saw the r3 and wanted to install it,
when i enterned the cwm program i got this:
"This version of cwm manager should be used with cf-root v5.0 or newer .it appears you are running a different kernel.various features have been disabled."
When i ask it to reboot into recovery, it asks me i say yes and nothing happens
I tried to enter the recovery manually but there was no succes,
What can i do?
Sory for my english, thanks for your help.

vovagershon said:
Hi, i installed franco kernel the r1 a few days ago using cwm, today i saw the r3 and wanted to install it,
when i enterned the cwm program i got this:
"This version of cwm manager should be used with cf-root v5.0 or newer .it appears you are running a different kernel.various features have been disabled."
When i ask it to reboot into recovery, it asks me i say yes and nothing happens
I tried to enter the recovery manually but there was no succes,
What can i do?
Sory for my english, thanks for your help.
Click to expand...
Click to collapse
Follow the instruction in the website:
http://forum.xda-developers.com/showthread.php?t=1329360
You can put back the appropriate kernel into your SGN.

Can it be possible that my rom kingdroid 1.6 cant work with this kernel?

franco kernel ics(r1/r2/r3) is ok for ICS stock rom and also for kingdroid ICS
check your root

And how do i do that?

vovagershon said:
And how do i do that?
Click to expand...
Click to collapse
If you can paste a file into the system folder then you have root. You need a root file manager like es explorer available free in the Market. You need to go into the setting of this program, enable root and allow write on the system folder.

I checked and my phone is rooted, when im trying to flash the kernel from cwm app it says zlmage not found.
Whar should i do?
Install a kernel using the odin?

Can u just extract zimage and flash it using mobile odin... pc odin wud increase the flash counter and even bring triangle with exclamation on boot screen...

OK, that's what i did,
i downloaded the r3 kernel zip, turned it into a tar file using this method
http://forum.xda-developers.com/showthread.php?t=1644240
flashed via odin and that's it. everything is back to normal, i can enter the recovery
By the way, that yellow triangle, i got it since my first custom rom, what that means? and the counter to?
Thanks for the help guys.

that means, your warranty has been voided if you show up to a service center with that yellow triangle. there are ways to remove, but that includeds re-flashing kernels and/or roms, removing the triangle notice (and flash counter) and doing everything from scratch.
search the forum.