Database Develop

[Q] Please help me update my SGS from JP2 to JP6

Hi I updated my SGS from Eclair to what I thought was the latest Froyo firmware. It turned that I had updated it to JP2. Now really nothing works anymore. Not even 3G.
My phone is not branded it any way but since Samsung turned off the update to JP6 I can't update using Kies. So I need to make the update using Odin or being able to get it to accept 2e files so I can install Clockwork Mod. Thing is I have no clue how to make it run 2e files. I did root it but that didn't work so obvious there is something else I need to do.
I guess my JP2 version is the stock JP2, and I would like to update it to stock JP6 or Tayutama's custom mod.
Is there something I need to do before I try updating my phone to JP6, or would it work to simply load the .tar file in Odin using the 803.pit file and re-partion and click "Start"?
PDA: I90000XXJP2
PHONE: I90000XXJP2
CSC: I90000XXJP2
Build Info: 2010.07
TIA
Daniel

Eh. Best way is downgrade to jm8 using the 512 pit file and set it to re partition. Once that's done install jp6 with 803 pit but do not use re partition. It will take too long to explain why you need to downgrade. But if you want to save time then try this method. Install jp6 as normal with 803 pit and don't re partition but this method isn't safe
Sent from my GT-I9000

I hope you made a backup first.
The way i do flash jpm or jp6 is safe and simple.
First you need a clean system.
I do this with jpk. Using pit 512 and with re-partition.
Then flash with odin.
Then i let the phone boot up.
I then format the internal sdcard.
Then i reboot in recovery mood.
There do i wipe the catch and do a factory reset.
Now is the phone almost clean.
Next i flash jpm or jp6. Use no pit file and do NOT re-partition.
People that tell you to use pit file here don't know what they are talking about.
Flash now with odin.
Start the phone and let it boot up.
Format the internal sdcard again and restart the phone in recovery again. Wipe the catch and do a factory reset. Restart the phone.
Now you got a working phone with latest froyo.
Sent from GT-I9000 jpm My own kernel for z4mod and with 341MB Ram

OK and by backup you mean backup of contacts, photos, sms's and so on? And a clean system is a system that has just been factory resetted, right?

Svantesson666 said:
OK and by backup you mean backup of contacts, photos, sms's and so on? And a clean system is a system that has just been factory resetted, right?
Click to expand...
Click to collapse
No. I mean a real backup. The efs folder is very important. There you have you personal code for the phone.
The rest of the backup is just good to have.
A clean system need more than a factory reset. If you do the steep i wrote it will be clean.
Sent from GT-I9000 jpm My own kernel for z4mod and with 341MB Ram

I didn't do a real backup before I used Odin to update to JP2. By doing so have I now lost something I can't retreive?
How do you do a real backup? Is that done in Odin too?

I am not sure if posting external links are allowed. My apologies if not allowed.
http://www.androidpolice.com/2010/0...nandroid-backup-and-clockworkmod-rom-manager/

Cheers mate, I'll go ahead and make a complete backup using the tutorial above once I'm back from work.

No worries man as long as it helps
Sent from my GT-I9000 using XDA App

Hmmm it didn't work as my phone is 3e and doesn't run update.zip. I know you have to reflash your Kernel to make it support update.zip files I just don't know how to do it. Man I'm rubbish when it comes to Android phones! haha

Hmmm you don't need to patch any kernel man.. Hope your phone is rooted the backup thing works with most of my friends' phones.. What is a 3e..? Just curious .
Sent from my GT-I9000 using XDA App

No I can't run update.zip as my phone doesn't support unsigned files in recovery mode. In recovery mode it says 3e at the post instead of 2e as it said when there was Eclair 2.1 on it.
My phone is rooted but even so I can't get it to actually create the backup. All things before that went smooth though. Superuser gave Nandroid root access and everything.

Go to the z4mod tread and download jp6 kernel and flash it with odin.
Then you got a recovery that works with update script.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram

Is it this kernel, by RyanZA, I should flash onto my SGS? - http://forum.xda-developers.com/showpost.php?p=8645069&postcount=162
If so should I simply apply this in Odin as PDA leaving everything else as default, put my phone in download mode and press start even though I don't run JP6 but JP2?
And after the update is done, then flash PHONE and CSC from JP6 using 803.pit leaving Re-Partion unchecked and click start?
Or should I apply the z4mod.ext2.update.zip from here - http://forum.xda-developers.com/showthread.php?t=797672 - first in recovery mode and then flash PHONE and CSC?
Or should I actually flash ALL three files, PDA, PHONE and CSC?
I must say I really appreciate all the help guys and I'm sorry if I'm abit slow, but smartphones are really a new area for me and I know nothing about Linux for that matter.

2.2 finally out for galaxy s!!
Sent from my GT-I9000 using Tapatalk

I bump this thread to get an answers to my "hopefully" final questions.

You should update the phone to the latest froyo. Don't se any reasons not to.
Then flash a kernel. After that use a filesystem, lagfix you want.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram

DamianGto said:
You should update the phone to the latest froyo. Don't se any reasons not to.
Then flash a kernel. After that use a filesystem, lagfix you want.
Click to expand...
Click to collapse
So I should just flash the PHONE and CSC before I flash the kernel (PDA) you say?
And are those files I posted in a few posts above the correct ones?

No.
You should use kies to upgrade if you can. ;-)
Then you can do other stuff.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 341MB Ram

I tried Kies yesterday. Sadly after putting in JP2 that ruined Kies, It says, this device can't be updated. I even tried to fool Kies by registry hack, but Samsung has obviously done something to provoke that as it didn't work.

[Q] Has anyone ever successfully restored a Roto Backup?

I've been asking for help after screwing up my Tab while trying to restore my Roto Backup with Odin, and the thread has been completely quiet.
I just wanted to ask an easier question, and see if that might tell me everything I need to know: Has anyone other than rotohammer ever actually successfully restored their Roto Backup? Second question, has anyone, including rotohammer, ever restored their Roto Backup with Odin?

The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.

DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
Thanks for the help. So you've managed to get your Roto Backup to work before?
So if I can't flash a bootloader from Roto backup, how do you recommend I flash back to the Froyo bootloader?
Also, any recommendations on a Froyo standard stock firmware image I can flash safely on an AT&T tab?

Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).

DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
and
I'll explain
=-=-=-=-=-=
I got 2 Tab's same STOCK ROM's...
on one of them installed overcome...
then i took roto backup the other and restored with odin on the overcome..
wait wait... i restored a stock GB from samfirm first and then used my Froyo backup...
kinda the same like you explained not to do... and guess what?!
tab died needed jtag... after jtag they gave me back the tab with stock froyo from samfirm...
now i'll explain
=-=-=-=-=-=-==
i restored again my backup with odin and original rom is now installed perfectly.. i did had an error when it reached boot.bin though..
but i restarted the tab and it's up and running...
too bad i didn't saw your message before...
i just have a question..
so lets say i'm now in overcome.. want to install 2.2
you say that i'll should use lets say stock rom from samfirm
with odin... with p1 pit file
check repartition, areboot, freset and start...
when done restore using my backup created using RB
with odin... areboot, freset and start (pda with the tar file and no pit)
but in the 'tar' file not to include boot.bin and SBL.bin files? just those files?
sorry for bad english...

I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.

nevermind it's working...

cymagnus said:
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
Click to expand...
Click to collapse
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.

manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...

avishai0528 said:
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
Click to expand...
Click to collapse
I have a Roto Backup, made from my own tab right after I got it, just no stock AT&T ROM to use as a base.

manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
That is correct. The backup made does not contain all the files.

DarkPal said:
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
Click to expand...
Click to collapse
I've done some research based on your recommendations. JK5 is actually no good I think, since it isn't a full ROM, and can't be used to re-partition.
JJ4, however, worked a charm. I downloaded it from samfirmware.com, and it came with all files necessary in the rar. Re-flashed pit, pda, modem and csc. Everything booted up as expected in Russian.
Then I used my Rotobackup, and re-flashed my pit and pda.
For the most part, everything is working, and restored, but for whatever reason, the boot animation is missing, and after the Galaxy Tab screen, it just turns black, and then after a while if I turn the screen off and on, I find it's already booted up (but booted with screen off). Any thoughts on why this occurs or how I can fix it?
My situation is that I'm increasingly beginning to suspect that my data connection is fritzy because of a hardware defect. I was on Overcome, and the data would just not be working when I turned on the Tab. The symptoms are one of the following: (1) data shows as connected and you can see the Tab sending but not receiving on the status bar, or (2) data shows as disconnected and then will show as connected for a moment and then show as disconnected again, or (3) data shows as disconnected, period. To fix any of these, I would have to either cycle the data or sometimes re-select the APN and reboot and then it would work. I then flashed to and used JPE for a few days, and observed today that my data showed as connected but would only send and not receive until I cycled the packet data setting.
Flashing back to stock, which I've now (mostly) done, is pretty much a last resort. I want to confirm whether this problem still exists on stock firmware, and if it does, I want to be in a condition to send in my Tab for repairs.

Just an update, I found this thread, which sounded a lot like my problem:
http://forum.xda-developers.com/showthread.php?t=899196
However, flashing jj4_bootloaders hasn't helped my missing logo problem. There is sound now, but still a black screen on bootup.

and none from samfirm are working? couldnt be.

Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?

cymagnus said:
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
Click to expand...
Click to collapse
As with the people that had the white line problem, with the corrupted graphics on the bootloader, I can't see recovery, just a black screen.

How can I revert to original kernel?

If I upload custom kernel on my Galaxy S with 2.3.4 JVQ, is it possible to revert to original JVQ kernel in order to check if same issue will appear on original kernel to detect if custom kernel has bug?
Thanks.

Flash as pda with odin.
Sent from my GT-I9000 using XDA Premium App

To get just the stock kernel in a flashable state you need to extract the zImage file from stock ROM (either one file or PDA of 3-file), then put it in a tar file by itself. Then you flash that as PDA with Odin.

I'm just going to expand a bit.
Find a single file tar of the stock firmware that is meant to be flashed as a PDA. Use winrar to look inside the .tar file to get the zImage and put it in a tar by itself. You can then flash it as PDA in Odin.
Sent from my GT-I9000M using XDA App

I thought that it is proper way to extract zImage from original ROM but I wasn't sure that it is good way. Thanks, I will try in this way.

I created zImage.TAR with 7-zip but Odin cannot load it. It comes to step when zImage should be loaded but upload is not happening. Do I have to exec some certain parameters when zipping it in TAR with 7-zip or how can I do it?
EDIT: I managed to make proper (flashable) TAR with IZarc application. Nevertheless, I uploaded stock zImage but I still have root access although other mooded kernel specific applications are gone. So, basically, I didn't revert it to original state. Or I am wrong? Please, advise.
Thanks.

Rooting doesn't necessarily mean changing kernel. You can root a completely stock phone and still use stock kernel. You can also unroot the phone.
You can use the SGS kernel flasher free app to flash a zImage directly from the phone.

eLtOnI0 said:
Rooting doesn't necessarily mean changing kernel. You can root a completely stock phone and still use stock kernel. You can also unroot the phone.
You can use the SGS kernel flasher free app to flash a zImage directly from the phone.
Click to expand...
Click to collapse
He's right, root often stays behind. To get back to stock just do a factory reset.
Make sure you can get into download mode before flashing just in case.
Sent from my GT-I9000M using XDA App

eLtOnI0 said:
Rooting doesn't necessarily mean changing kernel. You can root a completely stock phone and still use stock kernel. You can also unroot the phone.
You can use the SGS kernel flasher free app to flash a zImage directly from the phone.
Click to expand...
Click to collapse
I've read through many threads, but in most they discribe to root a phone via flashing the kernel
like here.
and i also would like to have a backup of my stock kernel, if i would flash it, but i'm not sure from which version i should take it. i do have JVH, but i can't find a fitting csc (it's MOBJV2) on samfirmware or google.

[Q] Flash RevolutionRom on SGS I9000

Hi guys,
I'm really interested in flashing Revolution Rom to my SGS1. It currently has CyanogenMod7 on it.
I've looked at the instructions here: http://forum.xda-developers.com/showthread.php?t=1236432
but can't figure out if I'm meant to just flash the rom or if I somehow need to flash a stock Gingerbread first before then flashing the REvolutionROM.
Can anyone assist?
Apologies if this question's already been asked, I did a thorough search but couldn't find anything. Happy if you just point me to another thread if it's already answered.
thanks
Aaron

To revert from CM7 to any other samsung rom you need to first flash a full PDA stock rom with odin. with repartition. and 512 pit.
then you can change to what ever rom you want.

Bork84 said:
To revert from CM7 to any other samsung rom you need to first flash a full PDA stock rom with odin. with repartition. and 512 pit.
then you can change to what ever rom you want.
Click to expand...
Click to collapse
Hi Bork84, thanks for the reply. Where do I get the stock GB rom that will allow me to then flash RevolutionROM?
Am I able to just flash nandroid backup that I took before I flashed CM7? It's stock Froyo with Voodoo LF (rooted)
thanks

Hi mate u just go to www.samfirmware.com make an account and chk the firmware sec in toolbox and then select ur model and download the latest formware...JVR is the latest firmware on samfirmware download it and download odin extract that downloaded folder and u have 4 file 1 pit file 2 code 3 csc 4 modem.
Now open odin and put these file respectively ( dnt forget to closr kies if u have even from running services on windows) now put ur phone in download mode and connect through odin and tick the repartition on leftside and then start odin...
Of all goes well u r on stock GB
wait phone to phone to boot
now choose any kernel to root ur phone and again turnoff ur phone and get in download mode and choose that kernel in pda option of odin and this time unchk the repartition and start odin
now ur rooted
then download custom rom and put in ur internal sd and go to recovery or cwm mode and flash that rom.
Sent from my GT-I9000 using XDA App

LA1 to LA4

Hi Guys,
Need help on that one.
Flashed via Mobile Odin Pro from LA1 (rooted/cwm/cf-kernel la1) to LA4 keeping Ever ROOT option ON, but did not check to inject superuser/cwm/mobile odin.
Since LA4 is not a wipe rom all the above apps remained, but Mobile Odin, Titanium Backup keep on saying that they can't access root.
Lost CWM app also. Did a full backup before the whole thing, but recovery mode seem to be lacking backup restore now

You could flash back to KK4 using Odin(PC) and root it with zergrush.. Install mobile odin again.. Flash LA4 properly with mobile odin this time.. And you shouldnt lose any of your data or apps...
Thats what i did once..

OK, but it does not make sense to put so much effort knowing that have not lost root. I have flashed LA4 on to top of LA1 via Mobile Odin Pro with Ever Root option ON.
Because of not injecting CWM, I've lost recovery and busybox su binaries. Now I need to find the way to flash them back.
Maybe I should wait for LA4+CMW kernel from this thread
http://forum.xda-developers.com/showthread.php?t=1329360
and then flash it using:
Execute "already-rooted.bat" and follow the instructions
or maybe I can flash LA3+CWM kernel to get CWM back, restore backed up LA1 and the flash LA4 again having all injection options turned on this time.
Correct mi if I'm wrong.

Its not much of an effort.. The process is rather quick(a few minutes).. Its perhaps the downloads that can take some time..
Edit: waiting for a quickfix often takes more time

Yeah, you're probably right, will flashing via Odin (PC) increase flashing counter?

stantheboss said:
Yeah, you're probably right, will flashing via Odin (PC) increase flashing counter?
Click to expand...
Click to collapse
If the rom you use is stock rom then it should not increase the counter.