Database Users

New JH2 official firmware upgrade Firmware in Canada i9000m Bell.

Kies tonight said there was an update for my phone current JG9 to a new firmware JH2..This might fix the 3 button combo for people that have issues. as the recovery screen is a bit different. give your a warning now that you have entered the system menu. This is a full flash so remember to backup everything.

Someone that can't get into recovery should try this update..

it sounds promising!
i wish i could give you the result but since my sgs can go into download mode....

karakake said:
it sounds promising!
i wish i could give you the result but since my sgs can go into download mode....
Click to expand...
Click to collapse
if you use kies it should. even if the 3 combo does not work.

well I meant I can't tell you whether this new firmware can fix download mode issue since mine can go into that mode using 3 buttons
But I wonder if it is still possible to upgrade mine becuase I flashed it with European rom and it is now I9000! All Bell bs apps are gone and even the boot screen shows i9000 haha

Should be able to flash to UGJG8 and then do the update via Kies.
I'm installing it now over JG9. Will be interesting to see if the RyanZA lagfix lives through the process. This is just an update, not a re-flash.
Notice also that the firmware is JH2, same last three as the "leaked" Captivate firmware that showed up on samsung-firmwares.com. The Captivate people have been pretty happy with it.

And it's not just an update, it's a full flash.
Be sure you back your **** up before doing this.

will be trying this out shortly, it's complaining that my battery isn't charged enough at 75% though. Will report back although I already have recovery mode.

litobro said:
will be trying this out shortly, it's complaining that my battery isn't charged enough at 75% though. Will report back although I already have recovery mode.
Click to expand...
Click to collapse
lol wow 75% and complains it is not enough?

I'm not getting any lag with this update... i'm really liking it.. and I checked the SPL is different. a newer version.. but it does have the recovery screen but its a new version with a little warning when you go into it.

litobro said:
will be trying this out shortly, it's complaining that my battery isn't charged enough at 75% though. Will report back although I already have recovery mode.
Click to expand...
Click to collapse
Thats odd it let me flash and my battery was at 40% and I didn't get a warning.

you know what will be the next question eh?......
"does that fix the GPS problem?"
i sincerly don't care, but the bunch of people that has been complaining about it, will biatch about that for sure.
personally both GPS, actually now 3 SGS i've tested it on, have been working great.

Here's a weird one for ya.
My IMEI SV changed from 03 to 04

So has anyone (without the download mode) tried the flash yet?
Does the FW somehow enable it again?
To be honest, the ideal solution would be a software hack that can somehow enable the 850 band and disable the 900 band so we can all stop dealing with this bell ****

AllGamer said:
you know what will be the next question eh?......
"does that fix the GPS problem?"
i sincerly don't care, but the bunch of people that has been complaining about it, will biatch about that for sure.
personally both GPS, actually now 3 SGS i've tested it on, have been working great.
Click to expand...
Click to collapse
hehe. i lucked out and got 2 phones on the first day. the 3 button sequence works on them both and the gps is reasonably accurate (compared to my garmin gpsmap60). i'm just hoping this update doesn't screw with anything that's working for me

sorry for goin off-topic but i have a queastion!
My europeanized(!) Bell sgs won't come back to i9000m even I flashed it with JG8 from Samsung-firmwars.com. Given the JG8 file only contained PDA file (no CSC, no MODEM), I flashed CSC and MODEM with those from JM2 and JM5, and my sgs still recognizes itself as GT-I9000, not I9000M... Is there any way to fix this? I can't find Canadian CSC version anywhere on the web.

Well, I think the problem was related to my Windows 7 desktop and instead am trying it on a Windows XP laptop, but referring to the i9000m not coming back to the proper form, is it due to the fact that we shipped with stock JG9 and are now updating to JH2 never having touched JG8?

karakake said:
sorry for goin off-topic but i have a queastion!
My europeanized(!) Bell sgs won't come back to i9000m even I flashed it with JG8 from Samsung-firmwars.com. Given the JG8 file only contained PDA file (no CSC, no MODEM), I flashed CSC and MODEM with those from JM2 and JM5, and my sgs still recognizes itself as GT-I9000, not I9000M... Is there any way to fix this? I can't find Canadian CSC version anywhere on the web.
Click to expand...
Click to collapse
Flash back to JG8, but use PDA only. It's an all-in-one, if you look inside the archive there are modem and CSC files in it. You did a flash within a flash.

Croak said:
Flash back to JG8, but use PDA only. It's an all-in-one, if you look inside the archive there are modem and CSC files in it. You did a flash within a flash.
Click to expand...
Click to collapse
OMG that explains why it took SOOOO long to reboot the phone..double flashing LOL
Thank you very much Croak

I did the update from UGJG9 and everything went fine. Seems faster and smoother. However, protected apps are no longer showing in the market.
Can someone else verify if Tapatalk Pro is showing for them or not? It has disappeared for me.

Phone not resonding whilst doing the Upgrade

Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.

Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!

Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................

The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.

Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....

I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.

Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.

As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.

sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.

Doesn't work to flash with odin either?

xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.

Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D

Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.

sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.

Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.

When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M

Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...

Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1

Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??

Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.

4th Replacement....Just want to scream!!!

Hello everyone!
Just wanted to show my depreciation of samsung products over the past few months...
It's the 4th GT-I9000M I get since august (in fact first exchange was done in october)
I got the phone 45 minutes ago by mail, it was probably a refurb (of course it was...). Inserted my sim inside (Phone was already unlocked as I didn't have to do it)....
Then I've started installing my apps and stuff than phone froze.....
Rebooted and.....
-----------------------------------------------------------------------------
Update Media, Please Wait
E:Can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:Can't mount DBDATA:
You storage not prepared yet. please use UI menu for format and reboot action
-----------------------------------------------------------------------------
This is completely retarded.....aren't they testing the phone before shipping it to customers?
How could this be possible....
I don't know what to do between throwing the phone on the wall, crying, don't think about it and use an other phone or call them back.....maybe all of this once at a time.....
What enrage me the most is that currently there is absolutely no solutions to Dead Memory for the GT-I9000M.......I saw some for GT-I9000, tried it for my older buggy GT-I9000M but didn't get anything better thand "can't mount...."

Teranox said:
-----------------------------------------------------------------------------
Update Media, Please Wait
E:Can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:Can't mount DBDATA:
You storage not prepared yet. please use UI menu for format and reboot action
-----------------------------------------------------------------------------
Click to expand...
Click to collapse
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.

Electroz said:
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Click to expand...
Click to collapse
+1
This happened to me in my earlier days of SGS flashing (albeit with the standard UK I9000) but my phone is fine now, you should be fine just flashing older firmware via Odin as quoted above.
Don't worry - all is not lost

Electroz said:
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Click to expand...
Click to collapse
correct that is just a corrupted internal SD partition message
it can be fixed, but flashing back to JH2 or JM8
then flash back to JL2

Electroz said:
This is not the failed internal SD card error. I'm assuming this happened when you tried to flash a JP? rom with repartition checked in odin....
Flash the phone back to JH2 and then flash back to whatever 2.2 rom you were trying WITHOUT repartition rechecked.
Click to expand...
Click to collapse
holly **** I LOVE YOU MAN!!!!
Phone is back to normal....
wanted to install Darky 8.0 as same as i did with previous phone. but then something went wrong
While installing 2.1 stock from bell with odin (to get 2e recovery working) something was different, phone logo was just flashing on/off so went back to 2.2 and error code was there....
So do you know what has caused 2.1 not running? first time i did it partition was cheked with previous phone and it worked
If I install speedmod kernel would I have to downgrade to apply darky 8 slim ROM
So do you know what has caused 2.1 not running? it was the same than

Teranox said:
holly **** I LOVE YOU MAN!!!!
Phone is back to normal....
wanted to install Darky 8.0 as same as i did with previous phone. but then something went wrong
While installing 2.1 stock from bell with odin (to get 2e recovery working) something was different, phone logo was just flashing on/off so went back to 2.2 and error code was there....
So do you know what has caused 2.1 not running? first time i did it partition was cheked with previous phone and it worked
If I install speedmod kernel would I have to downgrade to apply darky 8 slim ROM
So do you know what has caused 2.1 not running? it was the same than
Click to expand...
Click to collapse
Can't comment on the other queries but if you want to install SpeedMod kernel then make sure the Voodoo lagfix is disabled (do this by going into recovery and lagfix options) and then flash SpeedMod with ClockworkMod recovery

Teranox said:
holly **** I LOVE YOU MAN!!!!
Phone is back to normal....
wanted to install Darky 8.0 as same as i did with previous phone. but then something went wrong
While installing 2.1 stock from bell with odin (to get 2e recovery working) something was different, phone logo was just flashing on/off so went back to 2.2 and error code was there....
So do you know what has caused 2.1 not running? first time i did it partition was cheked with previous phone and it worked
If I install speedmod kernel would I have to downgrade to apply darky 8 slim ROM
So do you know what has caused 2.1 not running? it was the same than
Click to expand...
Click to collapse
Bell's UGJL2 rom has an updated bootloader that supposedly fixes the internal SD failures. This bootloader has compatibility issues with the 2.1 firmwares. There is a full version of JH2 going around that includes the old bootloader, but must be installed with the "Phone Bootloader Update" option checked in Odin. This will allow you to go back to 2.1
However, since you are aiming for a 2.2 rom, I suggest sticking with JL2, Flashing a custom Kernel that includes clockworkmod (ex. Speedmod or Voodoo) and installing Darky's with clockwork.

Electroz said:
Bell's UGJL2 rom has an updated bootloader that supposedly fixes the internal SD failures. This bootloader has compatibility issues with the 2.1 firmwares. There is a full version of JH2 going around that includes the old bootloader, but must be installed with the "Phone Bootloader Update" option checked in Odin. This will allow you to go back to 2.1
However, since you are aiming for a 2.2 rom, I suggest sticking with JL2, Flashing a custom Kernel that includes clockworkmod (ex. Speedmod or Voodoo) and installing Darky's with clockwork.
Click to expand...
Click to collapse
I'm now using Speedmod Kernel (the on that just got released today loll) so I can flash with this one.
I think before messing up again with everything i'll just let it like it is with speedmod (that claim to help the battery, increase speed, and have BLN enabled)....
Darky release rom so fast anyway loll that even i i install it today next week there gonna be 2-3 new relase loll
soooooooooooooo happy to get back my android device.....was using my old BB 9000 for a week.....needed a little more speed

Nice work Teranox.
"I got the phone 45 minutes ago by mail, it was probably a refurb (of course it was...). Inserted my sim inside (Phone was already unlocked as I didn't have to do it)....
Then I've started installing my apps and stuff than phone froze....."
It's bad enough you probably lie to Samsung/Bell about the situation surrounding the death of your phone, but lying to us here is sick.

Looks like your the one who actually messed up the phone on the first, second and third time. Conisder your self lucky that you still got a replacement.. Technically flashing those kernels and non samsung official release is already voiding your warranty.

It's one of the advantage of being a Samsung Mob!lers ;-) but the first one really died while never customised it. Second one same thing third one 3 days after normal.use under darky rom 7 with lagfix.
The one is just got (the fourth) crashed because i was not informed about the re-partion check/uncheck difference with the last firmware from bell.
Anyway, stock rom with speedmod is perfect from me since it is fast without lag and bln enabled. Will see in the coming weeks if Darky release something tempting enough to flash loll
Sent from my GT-I9000M using XDA App

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk

\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.

Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!

you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY

Yep, updated, thanks!

Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.

Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???

sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse

on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!

icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?

sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?

icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?

sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.

icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.

Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.

Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.

WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK

Has anyone flashed the three button fix? I really want to. just wanna verify its ok.

likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here

double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard

[Q] Having some (basic) questions about i5800L

Hi all,
I've just got my new i5800L, and I've already rooted it with z4root. Here are my qs:
What's all that of XXJPM and all that stuff? Which one should I use for mine? (actual one is I5800LVIJG7 (Eclair)).
Is there any way of doing a nandroid (full copy of the actual rom which can be flashed easily) so if I mess things up or want to get back to Eclair I'd just have to flash it back?
I guess that's all by now. Thank's in advance.

JPM is the latest froyo rom...you cant backup ur whole rom as if nw we dont have any alternative for this...check flashing guide in sticky and see vdos on youtube. ...happy flashing...
Sent from my GT-I5800 using XDA App

Thanks..
I've downloaded 2 files (2 diferent versions). One was a zip file with 3 files inside and the other one was a rar file with 4 .tar.md5 files. The zip i don't know how to apply it because odin will only take .tar or md5 files and in the other one I don't know what to do with all the .tar.md5 files. What should I do? :S

moikop said:
Thanks..
I've downloaded 2 files (2 diferent versions). One was a zip file with 3 files inside and the other one was a rar file with 4 .tar.md5 files. The zip i don't know how to apply it because odin will only take .tar or md5 files and in the other one I don't know what to do with all the .tar.md5 files. What should I do? :S
Click to expand...
Click to collapse
Take a look at rudolf895 youtube channel
http://www.youtube.com/rudolf895
All you need to know is on his Videos
Hope this helps

Thanks, now it's booting (on the samsung screen). I think it worked. But now it's "orangeized" XD. I'll keep looking for the right tar XD
PD: is it ok if it takes a while on the "samsung" (the one with the glow, after the GT-I5800l screen) screen? cause it's past a few minutes and still on that screen and I'm starting to panic XD
EDIT: It's been more that 15 minutes since it's stuck at that screen. What should I do? Please, second day with it and already screw it XD

Flash the JPM firmware...you shud get it as a tar package...a single file...
but sometimes u will have 4 files
1. bootloader
2. pda
3. csc
4. phone
dont ever flash the bootloader file in odin with pda csc n phone tar files...because the risk of bricking goes high...
just flash the 3 remainin files...n when ur fone has booted...just do a hard reset

katkoriaarpan said:
Flash the JPM firmware...you shud get it as a tar package...a single file...
but sometimes u will have 4 files
1. bootloader
2. pda
3. csc
4. phone
dont ever flash the bootloader file in odin with pda csc n phone tar files...because the risk of bricking goes high...
just flash the 3 remainin files...n when ur fone has booted...just do a hard reset
Click to expand...
Click to collapse
Great, now it works again! Thank you a lot. And now I finally understand how odin works :-D
which custom rom do you guys recomend?

Don't forget the i5800L is different from the i5800, but the only difference is the 3G antenna frequency. If you install JPM you MIGHT have 3G connection problems, or then again you might not. You MOST LIKELY will see a battery life decrease because of this issue. If you want really badly to have Froyo (android 2.2) you can flash a JPM ROM. If you want your battery to last a couple of days, either wait for an american release of froyo, or keep your Eclair version.
I have a i5800L from VIVO, originally with JG7 as well. When I installed JPF (previous froyo release) I had issues with the 3G network, when I flashed Kyrillos custom JPM ROM i also had problems. When I flashed Lestatious custom JPF ROM I didn't have problems, and when I flashed clean JPM i didn't have problems either.
So really, its a question of luck.. although let me tell you, my battery lasted way way longer on the original JG7 firmware than any other release (including the JK1 Eclair, said to be the best Eclair released before froyo).
Remember though, if flashing separately (not as one package), avoid flashing the BOOT file or BOOTLOADER. Flashing this increases the chance of bricking your phone. Not flashing it decreases the change by 1000000000000 times.

IonAphis said:
You MOST LIKELY will see a battery life decrease because of this issue. If you want really badly to have Froyo (android 2.2) you can flash a JPM ROM. If you want your battery to last a couple of days, either wait for an american release of froyo, or keep your Eclair version.
Click to expand...
Click to collapse
Yeah, I can see that. I'm with Kryllos v3.3 and the battery only lasts like about 16 hours :S. I guess I'll go back to I5800LVIJG7 (The one which it came with).
IonAphis said:
Remember though, if flashing separately (not as one package), avoid flashing the BOOT file or BOOTLOADER. Flashing this increases the chance of bricking your phone. Not flashing it decreases the change by 1000000000000 times.
Click to expand...
Click to collapse
About that, if I flash the bootloader (with all the others too, of course), and it upgrades ok, then there's no problem, right? I mean, if I try to downgrade again, it'll work fine? (Yes, before I read the comment telling me not to flash the bootloader, I did it and it was successfull. But now I don't know if it'd make it fail when I'll downgrade to I5800LVIJG7 :S)

It's not about upgrading or downgrading. When you flash, pratically all the memory on your phone gets erased, which means you can upgrade or downgrade at will with no problems.
The problem is, when you flash a bootloader, and say, for example, you have a power outage, or your computer decides to give more resources to your MSN or winamp you have running on the background (or whatever else), or even there is a problem with your cable connection or a spike in power, or whatever other mishap that can occur, the bootloader might not be able to transfer successfully. If that happens, you won't be able to boot your phone. If you flash everything except the bootloader and something happens, you will be able to at least go back into download mode and reflash the files needed.
Basically the bootloader tells your phone to start. If that gets corrupted, it simply won't. If you avoid flashing this and even if the transfer gets corrupted, you can always do the process again by going into download mode (which is installed along with the bootloader)

Great, thank you so much

moikop said:
Great, thank you so much
Click to expand...
Click to collapse
So when you were running on Kyrillos' ROM, did you have any connections problems with the 3G band?? thank you for your answer

fedee13 said:
So when you were running on Kyrillos' ROM, did you have any connections problems with the 3G band?? thank you for your answer
Click to expand...
Click to collapse
No, I haven't. I'm now in Kyrillos v5.7 and it goes great (battery consumption, performance, etc)

Remember to backup your IMEI so we may have one less "help my imie is 000000000" thread.
Sent from my GT-I5800 using XDA App

moikop said:
No, I haven't. I'm now in Kyrillos v5.7 and it goes great (battery consumption, performance, etc)
Click to expand...
Click to collapse
Fantastic! thank you very much Now it's time to learn how to do it haha
dilzo said:
Remember to backup your IMEI so we may have one less "help my imie is 000000000" thread.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
How do i do that??

fedee13 said:
Fantastic! thank you very much Now it's time to learn how to do it haha
How do i do that??
Click to expand...
Click to collapse
Go to terminal emulator and type this..
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Wait for few seconds. Then copy efs.rfs from sdcard to pc and keep it safe.

arunmcops said:
Go to terminal emulator and type this..
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Wait for few seconds. Then copy efs.rfs from sdcard to pc and keep it safe.
Click to expand...
Click to collapse
I'm sorry but where I find this "terminal emulator", I'm new at this.
Thanks in advance!

fedee13 said:
I'm sorry but where I find this "terminal emulator", I'm new at this.
Thanks in advance!
Click to expand...
Click to collapse
Market dude......