Database Develop

Need a fix ASAP PLEASE!

I'm pretty sure my phone isn't bricked.
Ok, this is what I've done...
I'm on official Froyo for UK, unbranded handset (i think jpo/jpp firmware).
I tried to install Voodoo Lagfix (stable, released today) by Odin.
I started Odin up, put PDA as the Voodoo file, put my phone into download mode, connected the usb, waited for odin to detect it and then clicked start.
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> zImage
<ID:0/009> Complete(Write) operation failed.
That's what Odin said, so I presumed it failed.
The screen was black and not doing anything so I unplugged it and removed the battery. When I put in battery and tried to start up phone, I get a logo of a flip phone on the left, with a line dash to a yellow triangle with black explanation mark, and then another dashed line to a computer.
Can I have a set of instructions on how to continue please!

which ROM did you install?
make sure the TAR is not corrupted
even if it failed, you can flash it again
the only way to find out if it works is to unplug and reboot it
there is always the JIG option if you don't have the 3 button modes

AllGamer said:
which ROM did you install?
make sure the TAR is not corrupted
even if it failed, you can flash it again
the only way to find out if it works is to unplug and reboot it
there is always the JIG option if you don't have the 3 button modes
Click to expand...
Click to collapse
It's not a ROM, I tried to put on Voodoo Lagfix 5 (stable) onto my stock firmware from Kies (JPP/JPO).
Shall I try to reflash the Lagfix? I think I need to flash a firmware, can someone please tell me, starting to get a little stressed haha.

BTW, Download Mode is working.

I would imagine you are going to have to flash stock firmware to it, you can try flashing it again or perhaps a different kernel

got it working now guys
just reflashed it and it worked

[Q] Please help this frustrated soul. 2e recovery / Custom Rom

Model GT-19000
Firmware 2.2
Baseband I9000DDJP2
Kernel 2.6.32.9 root at SE-S605 # 1
Build Froyo.DDJP6
Rooted phone with z4 root.
Unable to install custom roms/backup current rom using ROM Manager
It kept saying signature verification failed in recovery mode when i tried to use update.zip
I understand that it is due to 3e recovery on my phone
So I tried CF-Root: (download mode and pda flash)
CF-Root-JP6-v1.2-Busybox-1.17.1
CF-Root-JP6-v1.2-Busybox-1.15.3
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1
None of them worked. Got All threads completed (0 succeed/1 failed) everytime.
I just want to install custom rom.
This is beyond frustration.
First the lagging Eclair and Froyo and this.
Plus I had to write this post twice cos this site thought that there is an email link somewhere.
Please Help. Anyone?
What do I need to do to get a custom rom.

Best thing to do to be sure it works fine is update to 2.2.1 JPY using the reg hack.
Flash speedmod kernel with CWM built into it via Odin.
Flash custom rom such as Darkyy rom via CWM recovery.
I will be posting some video tutorials later tonight in the development section showing how to flash etc.
Good luck

Trueblue.08 said:
Model GT-19000
Firmware 2.2
Baseband I9000DDJP2
Kernel 2.6.32.9 root at SE-S605 # 1
Build Froyo.DDJP6
Rooted phone with z4 root.
Unable to install custom roms/backup current rom using ROM Manager
It kept saying signature verification failed in recovery mode when i tried to use update.zip
I understand that it is due to 3e recovery on my phone
So I tried CF-Root: (download mode and pda flash)
CF-Root-JP6-v1.2-Busybox-1.17.1
CF-Root-JP6-v1.2-Busybox-1.15.3
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1
None of them worked. Got All threads completed (0 succeed/1 failed) everytime.
I just want to install custom rom.
This is beyond frustration.
First the lagging Eclair and Froyo and this.
Plus I had to write this post twice cos this site thought that there is an email link somewhere.
Please Help. Anyone?
What do I need to do to get a custom rom.
Click to expand...
Click to collapse
I think you should try to flash the latest Hardcore's Speedmod kernel with Odin (PDA + repartition unticked). It comes with CWM Recovery.
What version of Odin do you have? And it said "Added" when you plugged in the phone?

thanks zolah and rytkonen.
So I am installing speedmod-kernel-k13a-500hz.zip via ODIN (PDA).
Lets see if this sorts it out and enables me to install darky's/doc's magic rom

i have Odin3 v1.3. Yeah it mentions added and removed and the works.

<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get.
I'll do the reg hack thing too now, I suppose. Whatever is that missing piece!! (aargh!)

Trueblue.08 said:
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get.
I'll do the reg hack thing too now, I suppose. Whatever is that missing piece!! (aargh!)
Click to expand...
Click to collapse
Have you tried different usb-port already? And you have the latest kies installed and not any kies processes active when using Odin? There seems to be some kind of problem with the connection to PC.
e. You also might want to try the Odin 1.7 (exe says Odin3 v1.7).

<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> zImage
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
I killed all the Kies applications and got this.
And guess what my phone now has a black screen with the phone connected to a computer with a yellow exclamation mark in the middle.
All hands to the deck!!
Please tell me this is not the end and I have not bricked my phone. I cant go into recovery. Am I screwed?

Trueblue.08 said:
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> zImage
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
I killed all the Kies applications and got this.
And guess what my phone now has a black screen with the phone connected to a computer with a yellow exclamation mark in the middle.
All hands to the deck!!
Please tell me this is not the end and I have not bricked my phone. I cant go into recovery. Am I screwed?
Click to expand...
Click to collapse
This phone is relatively hard to brick for real. Pull out the battery for few minutes and try to boot to download mode. What did you try to flash? Did you try different usb port?
Did you try flashing through these steps:
1. Kill all Kies processes
2. Open Odin
3. Select the tar to pda section and make sure re-partition is unticked
4. Boot to download
5. Connect phone through usb
6. Flash
?

ok i figured that orange triangle out and my phone is working again.
Also I was able to install speemod kernel.
It now reads 2.6.32.9 [email protected] #32
However it still is 3e Android system recovery which means I am still not able to backup my rom install a new rom. - Same thing
E:failed to verify whole-file signature
E:signature verification failed.
EDIT: yeah, i followed the exact same steps. so after the orange screen i was lucky to go to download mode and did the odin install again. This time it worked. That's great, but the initial problem still remains - 2e recovery and custom rom

Trueblue.08 said:
ok i figured that orange triangle out and my phone is working again.
Also I was able to install speemod kernel.
It now reads 2.6.32.9 [email protected] #32
However it still is 3e Android system recovery which means I am still not able to backup my rom install a new rom. - Same thing
E:failed to verify whole-file signature
E:signature verification failed.
EDIT: yeah, i followed the exact same steps. so after the orange screen i was lucky to go to download mode and did the odin install again. This time it worked. That's great, but the initial problem still remains - 2e recovery and custom rom
Click to expand...
Click to collapse
Great, you are already a huge step closer to a custom rom.
Are you sure you were rooted before flashing? Something strange is still happening because I restored my phone to it's out-of-the-box state few days ago and I can confirm that you get the CWM when you flash succesfully the Speedmod kernel.

Rytkonen said:
Have you tried different usb-port already? And you have the latest kies installed and not any kies processes active when using Odin? There seems to be some kind of problem with the connection to PC.
e. You also might want to try the Odin 1.7 (exe says Odin3 v1.7).
Click to expand...
Click to collapse
I think this was the reason, I wasn't able to get it flashed. My Kies processes were on at the time. Now I redid the CF-Root after my success with the speedmod (again the kies processes were killed this time) and now I have 2e Android System Recovery.
Thanks again, mate. Super advice

Yeah, it is rooted all right. The second time around, it is actually creating a backup. So I just have to save the CWM folder on my computer and then I can add new custom roms right?
Thanks for the patience btw.

Trueblue.08 said:
Yeah, it is rooted all right. The second time around, it is actually creating a backup. So I just have to save the CWM folder on my computer and then I can add new custom roms right?
Thanks for the patience btw.
Click to expand...
Click to collapse
Are you speaking of Nandroid backup? You can save it on your computer but I think it is not very recommended to restore a nandroid backup. If you get your phone to a state that it wont boot (but Download mode is working) you can always just flash a new rom with Odin. Now when you got it working.
With CWM you can flash custom roms and kernels easily from recovery. Just remember to read the developer's instructions carefully before flashing.
e. I think this is an excellent thread to keep in mind when you want to flash back to stock or make a clean start (or in case of "brick"): http://forum.xda-developers.com/showthread.php?t=818556

Trueblue.08 said:
ok i figured that orange triangle out and my phone is working again.
Also I was able to install speemod kernel.
It now reads 2.6.32.9 [email protected] #32
However it still is 3e Android system recovery which means I am still not able to backup my rom install a new rom. - Same thing
E:failed to verify whole-file signature
E:signature verification failed.
EDIT: yeah, i followed the exact same steps. so after the orange screen i was lucky to go to download mode and did the odin install again. This time it worked. That's great, but the initial problem still remains - 2e recovery and custom rom
Click to expand...
Click to collapse
Do you have Rom manager app installed?
If you do then delete the app and boot into recovery mode again and see if you have CWM recovery.

[Q] i9000m stuck in boot screen after odin flash

Trying to get my Bell Vibrant i9000m phone back to stock. I had a problem earlier today with a custom rom and force closes and now I think Odin is my only option to get my phone working again.
I'm using Odin 1.7 and trying to flash stock I9000UGJK3.tar. This a "one file" type of Odin flash, no need to pick PIT file, everything is in this file.
I can put my phone in download mode (vol down / home / power keys pressed), odin recognizes my phone and proceeds to flash phone. Here is the odin progress window:
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> cache.rfs
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
All this seems OK to me, after completing the above, phone reboots. Then just cycles back to boot screen flashing i9000m, never gets to samsung animation.
I'm wondering how to get past this. Any help would be appreciated.
Thanks,

Did you remove any lagfixes or tweaks before flashing back to stock?

I never had any lagfixes. I did do a data wipe before trying to install romkitchen V10 rom. Pervious to this I had the following working:
2.6.32.9 [email protected]#24
FROYO.DocRom_9.6.6_XWJS5
2.2.1
I9000BVJJPA
I started getting force closes on a number of apps, to me usually an indication that it's tiime to upgrade. I tried to go to: ZSJPJ_Wipe-v10-17-33-22-01-04-E8UWZEutAA.zip. I had some problems, tried to restore to previous backup roms I saved with ROM manager which did not work. So I figured would be the best to try to get to a stock base. Now my phone is stuck in rotating i9000m boot screen.

Well, tried everything I could think to do with odin with no luck. Brought the phone into the local bell service center and now have a loaner until my phone gets back. Using a HTC Desire Z, seems fine. I did a OTA OS upgrade to 2.2.1 while driving back to work.

i've the same problem but I try to flash with the Samsung firmware 2.1...
this is the same same problem. before, I've the Original galaxy S I9000M 2.2 update Froyo.UGKC1 kernet 2.6.32.9 Base on I9000UGKC1
version 2.2
i've make error to flash with 1 file:
I9000UGJH2-PDA-Kernel-Bootloader-CL490514-Low.tar
and 1 PIT.. (pit: 512)
who have Idea? thanks alot..
[MOD]: I've found

Bricked phone, can't access download mode. Please HELP!

OK So,
I recieved a Galaxy S today, and having some experience with a HTC Desire HD I knew how rooting/flashing roms work. But this is different.
I have flashed twice so far. Once trying to get to CM7 MIUI but that failed, leaving me in a recovery loop. So I panicked. I then used someones one click odin restore on these forums, however being the idiot I am didn't read that that was vibrant firmware and not i9000 firmware. Download mode was working 100% before I did this, and now I can't get it to work for the life of me. Can someone please help? I am stuck at the AT&T boot logo and I can't do anything. I have the correct firmware from my carrier, I know how to flash it back to stock, but I can't get into the freaking download mode. Why is this? Is it disabled for good?
Please don't tell me my phone is a brick now....

Try the jig method. You can make your own or plenty on eBay. But I think you are in the 'not good ' realm. But usually you don't get to the boot screen either so there is some hope.
Sent from my GT-I9000M using XDA Premium App

I've bought a jib off ebay so I will see if that works. What I am trying to understand is why would doing what I did somehow disable download mode? That makes no sense to me. And the phone isn't fully bricked since the boot screen comes up.

Download mode is software based and you flashed new software on the wrong hardware. It's on the bootloader I believe. The jig tries to get it forced as I think there is a backup bootloader but not at all sure on the details.
Sent from my GT-I9000M using XDA Premium App

I see. Well I will try the jig and see what happens. If that doesn't work I will send back to Samsung and blame Kies for the problem. Which will be a bit sus since I have an at&t bootlogo and I live in Australia but oh well
One other question I have is if I do get into download mode, I have all the stock firmware files from SAMfirmware, however the files are only a pda file and a 512 pit file. I was under the impression I needed a csc file and something else? Or is it all included in the .tar PDA file?
Thank you for all your help I really appreciate it!

Usually what you need is in the tar for the pda spot. The others are more for mix and match. Just be aware that some firmware does not have all the files as they aren't meant to be flashed with pit. You will want to flash a pit so you'll need a complete one. My stock has no dbdata.rfs for example and if you use a pit then you get a mounting error as no partition is created.
Sent from my GT-I9000M using XDA Premium App

I had a look inside the .tar file which is for I9000DTJP5 (exact firmware that I had on stock) and there is no dbdata.rfs like you said. So you are saying this firmware that I got from samfirmware.com is incomplete? And if I flash with the PDA + 512.pit I will get mounting errors? So do I just flash the PDA firmware by itself and tick re-partition?
Thanks.
PS I used this http://forum.xda-developers.com/showthread.php?t=731989
So I'm guessing this changed my kernal and modem? I beleive the kernel does not come included in the pda .tar... or does it?

The pda will have the zImage in it (which is the kernel).
But try to find one with the dbdata.rfs file. For some reason I think jpy is one people use (anyone else following this thread). There are some roms that people describe as 'working everytime' and I think that its because they are complete roms. I'd also look at ezboot thread as you will want to make sure that any capivate bootloader gets removed and updated with an i9000 one but stock roms usually have the bootloader I believe.
Have you (out of curiousity) tried the captivate download sequence (vol down and power - I think - maybe while battery is inserted)?
Also might try the ADB method of prompting download for captivate.

Yeah none of samfirmware comes with the dbdata.rfs file. Other option would be to flash to something like Darky's rom. I must have screwed the boot loader since I came from froyo > CM7 bootloader and that's when things went wrong. What file removes & affects the bootloader from Odin?
Yes I've tried the captivate download mode which is Volume Down + Power like you said. ADB is impossible since the phone isn't operational.
So that easy one click odin that I used flashed the modem, the bootloader, and the rom. This is going to be hard to fix.
I need to use firmwares from my country... and JPU isn't listed under australia on samfirmware website

Well the bootloader for froyo and cm7 are the same but the problem was the file system was not (cm7 uses yaffs or something - not a linux person...) so you had to do a full flash with pit (and of course not with captivate rom in retrospect) which did screw up the bootloader and more.
You can also get a service (professional shops) called JTAG that opens up the phone and reflashes just the bootloader from point on the motherboard. Some information here on XDA. Its a specialized deep hardware fix but it solves even hard bricks that won't turn on (unless there is physical damage of course). Might cost $100 or so though.... Might be worth a search for local shops that do that.

found this post (and it references another thread).
http://forum.xda-developers.com/showthread.php?t=749641
But its not good news... These are from last year but it looks like people were hooped in similar situations though i think the JTAG method has been formalized since then.

OK! The Jig works!!!!!!!!!! SO happy. However I am facing the problem of flashing now. Odin gets stuck at cache.rfs for about 20 minutes until I disconnect the phone and try again.
The files I am using with a 512.pit with re-partition checked are...
Phone:MODEM_I9000DTJP3.tar.md5
PDA:CODE_I9000DTJP5.tar.md5
CSC:CSC_I9000XSAJP4.tar (my countries correct csc file)
Here is my log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> param.lfs
<ID:0/004> modem.bin
<ID:0/004> cache.rfs
What am I doing wrong?
Thanks

Try another version of odin? Or another rom I've had bad versions of both.
Looks like more lines about md5 stuff than I recall too.
Sent from my GT-I9000M using XDA Premium App

Found the culprit... the csc file which I obtained from XDA was corrupt... so I used a different one. My phone is now up and running. I just want to say a big thanks for your time and advice. Thanks

[Q] I messed up my girlfriend’s GalaxyS ….

Pleaseeee help ….. I am stuck in the downloading mode
Dear experts
I have messed up my girlfriend’s GalaxyS ….
I rooted her phone by following ChainFire’s thread http://forum.xda-developers.com/showthread.php?t=1056334
Followed every step and rooted phone ….Things went smooth…then suddenly phone keep dying in few hours even if its fully charged …. I thought of reapeting the whole process incase I made mistake at any stage
I run the Odin v1.85, selected “CF-Root-XX_OXA_JVO-v3.2-CWM3RFS.tar” file in PDA and click on start…..Suddenly my phone died and Odin said successful 0/ Failed 1
I got in panic mode and start the whole process again…. Since then phone is in Downloading mode.....
Then Magic happen and i got following msg frm Odin
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/004> Added!!
Then as per instruction after phone get rebooted i run superoneclick and click on Root... Its been almost 2 hours and i am having following msg on superoneclick...
Running psneuter....
Pleaseeeeeeeeeeeeeeeeeeeeeeee help me to get it up & running
Waiting for experts to save my relationship
Pleaseeeee help me guys
What to do next?

If you flash cf root kernel you will get root.You don't need superone click.
Try reboot your phone it should work.
Sent from Galaxy on latest nightly with neo kernel

First of all... what was the original firmware?
Second: I hope you have not messed with repartition and bootloader?

yeah, check what version she's running and flash cf-root, since you allready are capable of flashing with Odin you dont need one-click root.
Sent from my GT-I9000 using XDA App

Dear all,
Many Many thanks for your time & reply...
I did reboot at least 3 times... Still having same problem... very strange problem
I have fully charge the phone. Everything is working fine, did my msgs, reply to email, took few pics...upload them....SO far so good, happy happy happyy so put the phone on side & had dinner, picked up phone again and it was off...have to press power button long enough to start the phone... Works fine, shows little drain on battery..put it aside for while and it will be off strangely... Have to restart it by pressing power button on for long enough and it does start, work well and once put it on side for while it goes off .... (My girlfriend is mad at me ;-p ... Dont know how to solve this )
Please help guys ... Here is the required details...
Original-->
Firmware 2.3.3
Kernel 2.6.35.7 I9000xxJV0-CL182937
Build number Gingerbread.XXJVO
Does this info will help you to find the fault?
Really need help...
Many Thanks

Reflash the stock rom again just to be on the safe side.