Related
I have a T-Mobile UK Galaxy S and would like to back up the stock firmware before flashing anything new to it. It has:
Baseband: I9000XXJF3
PDA: I9000XXJF4
PHONE: I9000XXJF3
CSC: I9000TMUJE6
Obviously I can download I9000XXJF3 so I can get back to the correct baseband/PHONE. However, I've not seen any JF4 firmware files, and obviously the CSC is custom for T-Mobile's APN settings.
Therefore, if I make a nandroid backup and restore that onto I9000XXJF3, will it restore the PDA and CSC to those versions? I'm not sure how, exactly, what nandroid backs up correlates with those parts of the ROM (although I think it doesn't back up PHONE?).
Thanks!
I have the same versions as you and made a nandroid backup of my rom and then upgraded to other roms (currently SamSet 1.9b) but I can confirm Nandroid backs up CSC and PDA. To get it back to stock (including modem) I just flash back to I9000XXJF3 and restore Nandroid backup and then modem, PDA and CSC are the same as when I received the phone.
On a side note, any chance you could upload your csc folder (or at least the TMU folder) I don't know if mine got messed up before I backed up as customer.xml references files such as "/Customer/TMU/Messagetone/TMO Message tone.mp3" that don't exist?
Hm, where would I find these files? The csc folder doesn't contain them, and I don't see a /Customer/ directory off the root. Indeed, I've never seen a T-Mobile ringtone as an option anywhere, and if I search for "TMU" in Astro I can't find anything. It's also not listed in /system/CSCFiles.txt, which I assume is a list of files contained in the CSC, and only contains:
Code:
/system/csc/customer.xml
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/csc/contents.db
/system/app/VoiceSearch.apk
/system/SW_Configuration.xml
/system/CSCFiles.txt
I could pull out those files, and perhaps dropping those onto the device (with root) would give it I9000TMUJE6 CSC? I don't know how to make it into an update.zip.
Anyway, I did a factory reset followed immediately by a nandroid backup, which I've uploaded in case that's useful:
http://www.megaupload.com/?d=G033UEH5
I don't see a /Customer either on mine and the CSCFiles.txt doesn't list it but in CSC/customer.xml it references them... maybe they were going to put them in but never did?
As for creating the update.zip I did manage to make one but it didn't seem to apply (the CSC version changed to TMU but the bookmarks/settings etc didn't get applied) until I followed http://forum.xda-developers.com/showthread.php?p=7338830#post7338830 to change it to TMU.
To be honest though, I have never bothered doing it as no matter what I flash, MMS and 3G internet and everything works without me doing a thing. I just keep it incase I need to send it back for any reason.
Accidentally created new post instead of editing old one, sorry.
So... does nandroid backup everything?
I mean, if I do a backup (let's call it original).
Then I install a ROM with a different baseband/MODEM.
If I restore the backup... Will I have the original baseband/MODEM?
Thanks!
Hi Guys , New to the forum but I have learned a lot in the last few weeks, from the excellent guides and information in the forum ,however there is a question that somehow no one seems to answer, I have a samsung galaxy s with the following firmware
PDA : I9000XWJM3
Phone : I9000XXJM2
CSC :I9000OXXJM2
The phone is about 2 months old, anyways I have done a few Custom rom Installs and flashed newer versions of android, and I find that every time I revert to a nandroid backup, of the orignal firmware , the baseband (I9000XXJM2) will never restore back i.e will always keep the baseband of the custom rom or the newer firmware, now the problem is that I cant find this stock firmware anywhere on the net, neither can I backup the orignal baseband. the versions are always either older or newer than my stock firmware... the phone had a dead pixel so sent it back to samsung and it came back flashed with my old original firmware. now to get to the point is there anyway to backup the baseband ? or can anyone point me in the right direction ? samfirmwares definitely doesn't have a copy of this original firmware. I sent the phone back to samsung with the incorrect baseband not even available in my country I may not be so lucky the next time something goes wrong so id like to keep a full stock version of the original firmware. any help will be cool
don't forget to back up the /efs folder. so that if your phone's /efs folder gets corrupt and you can't make calls, you can restore it easily.
by the way, your modem (baseband) can be found on samfirmware and it must be contained in I9000XXJM2 firmware.
the guy who flashed your firmware mixed 2 firmwares, that is the reason why you couldnt find it.
by the way, your modem (baseband) can be found on samfirmware and it must be contained in I9000XXJM2 firmware.
Can you find XXJM2 save the OP looking for the invisible firmware .
Looks like you have odd original, firmware .
Save baseband file downloaded from sam will include the baseband/modem file in the zip/tar file . You can just save that or extract the modem .Its possible to just flash the modem or swap modem in custom roms .
Can you open the Nandroid backup and see if modem is in that .
jje
thanks , I have backed up the EFS folder already , but as I said I cant find that version of firmware, samfirmware does not have a XXJM2 firmware rather a XWJM2 firmware package the has a XXJM1 modem file in it
legend-zn said:
thanks , I have backed up the EFS folder already , but as I said I cant find that version of firmware, samfirmware does not have a XXJM2 firmware rather a XWJM2 firmware package the has a XXJM1 modem file in it
Click to expand...
Click to collapse
hi buddy
can u tell me or post a link on how to backup baseband?
Hello,
1) if I wanted to flash to JVO with Odin, is the setup in the attached pic correct (especially the files on PDA, PHONE, CSC and repartition ticked)?
2) Wasn't there a bootloader I needed to flash? I think I read somewhere the bootloader changed with GB.
Landorin said:
Hello,
1) if I wanted to flash to JVO with Odin, is the setup in the attached pic correct (especially the files on PDA, PHONE, CSC and repartition ticked)?
2) Wasn't there a bootloader I needed to flash? I think I read somewhere the bootloader changed with GB.
Click to expand...
Click to collapse
1)Yup
2)The bootloaders are included in the file you have ( See where it says sbl in the file name of the PDA )
Yeah saw that SBL and that made me suspicious whether that file really should go into the PDA slot and leave the bootloader slot blank.
Landorin said:
Yeah saw that SBL and that made me suspicious whether that file really should go into the PDA slot and leave the bootloader slot blank.
Click to expand...
Click to collapse
Nope leave it EXACTLY as you have it there mate and you are good to go.
and repartition has to be ticked as well, right?
Landorin said:
and repartition has to be ticked as well, right?
Click to expand...
Click to collapse
Yes.
You are using a pit file so you need repartition ticked.
Thanks a lot for the quick help!
Landorin said:
and repartition has to be ticked as well, right?
Click to expand...
Click to collapse
no don't repartition unless you want to in which case you need ONE EXTRA FILE: 512.pit!! You sound like a newbie so depending where you are coming from -stock firmware-wise, by all means repartition but you must obtain the 512.pit that you add to odin and flash with the rest of the rom. WARNING: this will wipe all your data and apps and repartition your phone including the sd card. make sure that you remove any external SD cards if you have one and the SIM card too...for peace of mind
UPDATE: oops! England has beaten Algeria...in cyberworldcup
I'd consider myself as noob, yep.
I thought I have to repartition when upgrading from JPY (2.2.1) to JVO? I don't know when this has to be done. Just saw the PIT file recommended for JVO on samfirmware and somehow assumed I have to repartition.
So what should I do, what's the difference if I do or not do it?
I backed up all data and wiped the phone before so there's not much on it right now (and no lagfix or so used, just stock rom with CF kernel).
Landorin said:
I'd consider myself as noob, yep.
I thought I have to repartition when upgrading from JPY (2.2.1) to JVO? I don't know when this has to be done. Just saw the PIT file recommended for JVO on samfirmware and somehow assumed I have to repartition.
So what should I do, what's the difference if I do or not do it?
I backed up all data and wiped the phone before so there's not much on it right now.
Click to expand...
Click to collapse
if you're sure that you used the same pit file as before i.e; 512.pit then you don't have to repartition at all.....if in doubt then repartition. BTW which pit file did you see on samfirmware.com? Should I assume that this is your first rom flashing from stock JPY? Also, make sure that you use the JVO rom that includes GB bootloaders.
Before? I never flashed a full ROM via Odin, only kernel (CF), thus I never re-partitioned myself.
Until now I used KIES always to flash ROMs.
If re-partitioning works like on a HDD I guess then this can be skipped unless something changed partition wise from Froyo to GB?
So do I need to re-partition at all?
Hey guys, gonna steal the end of this thread.
Currently I am on 2.2:
PDA: JPA / PHONE: JPP / CSC:JP7 (MET)
I want to use ODIN to upgrade to STOCK 2.2.1 and for it to change the CSC to XEU so that 2.3.3 (and future updates) will be done through kies automatically.
Can somebody confirm how I do this? Which file do i need to d/l - all three? And do I (and why) need to repartition?
Thanks in advance
Unregistered. said:
Hey guys, gonna steal the end of this thread.
Currently I am on 2.2:
PDA: JPA / PHONE: JPP / CSC:JP7 (MET)
I want to use ODIN to upgrade to STOCK 2.2.1 and for it to change the CSC to XEU so that 2.3.3 (and future updates) will be done through kies automatically.
Can somebody confirm how I do this? Which file do i need to d/l - all three? And do I (and why) need to repartition?
Thanks in advance
Click to expand...
Click to collapse
If you used Kies anyway, why not use it now to update to 2.2.1? Afaik you can change the CSC with market apps (think I read that somewhere but someone may want to confirm this). Anyways, you could just stick with your normal CSC as GB will be released to the rest of Europe anyway.
Currently, it's uncertain whether there will be more updates after GB afaik.
But yes, our question remains: do we have to re-partition at all if we only used Kies so far to update ROMs?
Landorin said:
If you used Kies anyway, why not use it now to update to 2.2.1? Afaik you can change the CSC with market apps (think I read that somewhere but someone may want to confirm this). Anyways, you could just stick with your normal CSC as GB will be released to the rest of Europe anyway.
Click to expand...
Click to collapse
Tried changing the CSC but it's didn't work. I'm with meteor and they are useless. So what i want is the stock 2.2.1 for UK and ireland as if it was d/l form kies and be on my way
Unregistered. said:
Hey guys, gonna steal the end of this thread.
Currently I am on 2.2:
PDA: JPA / PHONE: JPP / CSC:JP7 (MET)
I want to use ODIN to upgrade to STOCK 2.2.1 and for it to change the CSC to XEU so that 2.3.3 (and future updates) will be done through kies automatically.
Can somebody confirm how I do this? Which file do i need to d/l - all three? And do I (and why) need to repartition?
Thanks in advance
Click to expand...
Click to collapse
Official Samsung GB for UK has already rolled out, it's called XXJVO and believe me once you've done your first ODIN rom flashing you will never stop flashing other..(custom roms and kernels) if there're any geeky tendencies inside you and just waiting to be released... see this thread and all your fears will be assuaged!
http://forum.xda-developers.com/showthread.php?t=1011901
Widget21 said:
see this thread and all your fears will be assuaged!
http://forum.xda-developers.com/showthread.php?t=1011901
Click to expand...
Click to collapse
Thanks! There it says:
"Note: Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all." question answered.
@Unregistered: you could use I9000XXJPY from samfirmware, JPY was the one that was offered to me by Kies back then (German unbranded SGS). But someone may want to confirm this to you first, as I see lots of others 2.2.1 ROMs there and not sure what the difference is. Samfirmware offers a single file and once extracted you should have 3 files.
I just wonder why the 2.2.1 ROM files do not show on that website which CSC is used, maybe it's universal or something?
Well, I guess Widget21 has a point here. If you are willing to flash now with Odin, you might be willing to do it with GB too, then the CSC won't matter (it doesn't matter much anyway as I learned).
Just be sure your 3 button combo is working and that you connect with direct USB.
Landorin said:
Thanks! There it says:
"Note: Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all." question answered.
@Unregistered: you could use I9000XXJPY from samfirmware, JPY was the one that was offered to me by Kies back then (German unbranded SGS). But someone may want to confirm this to you first, as I see lots of others 2.2.1 ROMs there and not sure what the difference is. Samfirmware offers a single file and once extracted you should have 3 files.
I just wonder why the 2.2.1 ROM files do not show on that website which CSC is used, maybe it's universal or something?
Well, I guess Widget21 has a point here. If you are willing to flash now with Odin, you might be willing to do it with GB too, then the CSC won't matter (it doesn't matter much anyway as I learned).
Just be sure your 3 button combo is working and that you connect with direct USB.
Click to expand...
Click to collapse
Is it JPY or JPX for UK (XEU)?
I dont want to flash gingerbread. Not yet anyway.
Landorin said:
Thanks! There it says:
"Note: Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all." question answered.
@Unregistered: you could use I9000XXJPY from samfirmware, JPY was the one that was offered to me by Kies back then (German unbranded SGS). But someone may want to confirm this to you first, as I see lots of others 2.2.1 ROMs there and not sure what the difference is. Samfirmware offers a single file and once extracted you should have 3 files.
I just wonder why the 2.2.1 ROM files do not show on that website which CSC is used, maybe it's universal or something?
Well, I guess Widget21 has a point here. If you are willing to flash now with Odin, you might be willing to do it with GB too, then the CSC won't matter (it doesn't matter much anyway as I learned).
Just be sure your 3 button combo is working and that you connect with direct USB.
Click to expand...
Click to collapse
JVO has multiCSC and UK's xeu is included in it so no need to worry about changing CSCs...remember the 'Thanks' button is there for a reason
@Unregistered: yeah, sorry, that's what I meant. If you wanna flash GB in the future you might want to do it with Odin and then the CSC shouldn't matter anymore.
For some reason, I'm unable to find out the CSC on the file and it's not listed. The JPY I downloaded from samfirmware recently has DBT as CSC (Germany). If you download the JPX file and extract it the CSC file might tell which region it is (as in my case).
@Widget21: I used my thanks feature up for today (5 max). I'll try tomorrow again.
I just downloaded this:
http://hotfile.com/dl/100618077/49a97b4/I9000XXJPY.rar.html
JPY_JPY_JPY.tar. I thought i was getting the three files. Where do i go from here
Does anybody have a CWM flashable CSC for stock DXJPC firmware?
DXJPC CSC
Thanks,Noxxious.
I can't stand the suspense,went ahead and flashed the DX fw
over the Italian fw and guess what--- no pda and csc from *#1234#.
Applied your csc file from CWM. now I have PDA XJPC and CSC OLBJPC,,,,
Under Kies it is still showing ITV though.....I tried from *#272*IME# to change to XTC the tab rebooted and I saw some RED TEXT stating that the "E:rfs cannot be formatted" or something like that.
What is this E drive? and how to apply CSC to enable the correct one to show up in Kies?
try reflashing the dxjpc firmware again. that did the trick when i encountered that before.
This is exciting!
should I reflash thru Odin without repartition or repartition with pit and pda?
you could also try doing a factory reset first...
i think it would be better to flash with .pit file
No luck,kabayan.
2 problems: 1. no pda and csc:
Tried everything-flash with pit, flash with no pit, factory reset using recovery mode,factory reset from settings/privacy,using samfirmware fw, using your dbdata file,etc- everything resulted in BLANK PDA AND CSC from *#1234#.
Went back to Italian using chainfire files and there it is complete info.
I researched the problem and found that on the galaxy s thread this CSC problem is extensively discussed. It has something to do with nv_data file not matching the csc. When during boot the fw finds the nv_dat file to be missing it creates a blank one thereby resulting in a blank csc when the 1234 is called. I don't do programming so I don't have a clue on how to resolve this problem.
Also present on the tab is the "E: efs unable to format data" error when changing csc from the *#272*.....
Problem 2. when rooting the dx firmware using CF-root the bootsplash becomes corrupted. The sound disappears from the samsung galaxy tab logo animation, followed by a BLANK screen and the sound comes just before the home screen appears and it is broken. I tried to apply the available bootsplash animation restore from this forum but it has no effect.
--I have now got back to the Italian stock. These 2 problems don't happen at all in this now unofficial fw(since it was pulled out by samsung). I think there definitely is something wrong with the dx fw.....
the DX 2.3.3 firmware is stable enough, the problem seems to be in how the filesystem gets updated/corrupted during the update process..
the only problem i got with the gingerbread firmwares (JQ1 and JPC) was this:
"verifing intermal MMC block...
checksum confirmation - check(1)
E:MBR checksum Error
Internal MMC checksum verify failed"
though i was able to fix that.
noxxious said:
the DX 2.3.3 firmware is stable enough, the problem seems to be in how the filesystem gets updated/corrupted during the update process..
Click to expand...
Click to collapse
not unstable but minor bugs are there (to discover)...felt okay to me but no different from the Italian fw.
noxxious said:
have you tried looking into the /efs in root?
mine contains 2 folders 1. (.android) and 2. (imei) and 6 files .nv_data.bak, .nv_data.bak.md5, .nv_state, nv_data.bin, nv_data.bin.md5, and updated_filesystem.
access dates for the files are as follows:
.nv_data.bak, .nv_data.bak.md5 was the date i made a backup of my efs folder (i was tinkering with the said files because samsung service forgot to reinput my tabs serial number)
Click to expand...
Click to collapse
Yes 2 folders-.android and IME. 7 files same as yours plus nv.log.
the hidden (.nv prefix) files were dated 25 jan 11 while the 2 others (nv) dated 11 jun while the updated_filesystem dated 4 jun
I wonder if there is a check on the md5 hash? or the dates?
seems you still have a safe copy of your EFS. i recommend you back it up somewhere. i myself have it on my pc and the tab's external sd.
I am now on the Italian gb....is this a safe copy? I'll put it on the external sd then....What will I do with it? should I put it in when flashing the dx?
keep it as backup as sometimes flashing firmwares might corrupt it, you ending up with a phone with bogus imei.
do you remember what the dates for .nv_data.bak and .nv_data.bak.md5 mean to you by any chance? say first time you held your tab, the date your tab left the factory even (lol)?
wait I'll check my receipt....I hope the missus did not throw away the box.....
Wait, I am learning something here:
You mean when flashing a new firmware the tab is not completely erased? I was assuming it is reformatted clean....
noxxious said:
keep it as backup as sometimes flashing firmwares might corrupt it, you ending up with a phone with bogus imei.
do you remember what the dates for .nv_data.bak and .nv_data.bak.md5 mean to you by any chance? say first time you held your tab, the date your tab left the factory even (lol)?
Click to expand...
Click to collapse
I got my tab in march so must be manufacture date
Sent from my GT-P1000 using Tapatalk
I think I can confirm now that there is something in the samfirmware file that causes the partition E errors I get. I have flash to DXKJ2 then updated thru Kies. No more errors!
I have been reading your post guys , and I also had the same problem in partition E: when I flashed gingerbread to p1000n, how did you solve the partition e: issue? Have tried everything and still with the same problem! (Obs.: the firmware also was form samfirmware.com)
vettorodrigo said:
I have been reading your post guys , and I also had the same problem in partition E: when I flashed gingerbread to p1000n, how did you solve the partition e: issue? Have tried everything and still with the same problem! (Obs.: the firmware also was form samfirmware.com)
Click to expand...
Click to collapse
I did not really "solve" it...I used Kies to get gingerbread.
I also have missing CSC and PDA, how to I flash using CWM. I root with CF-root and it comes with CWM manager, can it be used? Is it under option flashed an update.zip for csc?
Thanks!
yes you can use cwm.but select zip file not update zip
Sent from my GT-P1000 using Tapatalk
Hey everybody,
Im kinda new to droid development, and have played around with it a little (flashing roms, kernels, rooting etc) however, im curious why there are roms based on pretty much every other firmware other than GKG3. I might sound like a n00b for asking about this but its mainly for my knowledge. I figured KG3 would be fairly common as it is one of the North American firmwares, but I must be incorrect? Anyways any insight on this would be great. Also a quick question, seeing as I am a Bell I9000m SGS owner does it matter if I put firmware from say Europe on my phone? I have noticed that my signal decreases when I put a rom on that is JVR based? Curious if this causes my phone, seeing as the modem is being changed to JVR, to think that I am out of country and will inflict long distance charges. This probably sounds like a dumb question, and I dont really believe LD charges will apply, but some confirmation would be nice as google didnt really help me out on this one.
Thanks!
KG3 is 2.3.3 and although it was just issued to Bell and other N.American customers, the rest of the Anfroid world has been using 2.3.4 for 6 months and some have moved to 2.3.5. The roms you see here are cutting edge and most use the latest firmware. The last official and stable release was JVR a 2.3.4 firmware and there are many good roms for JVR. It is easy to keep your KG3 modem in place and the KG3 CSC file and just upgrade your system to a custom JVR kernel and JVR rom.
I tried flashing galaxian's jvr kernel and it just bootlooped so maybe I'm doing this wrong? I kept my stock modem and CSC, flashed kernel using oden, factory reset was done as well as a cache clear prior to the flash and all I'm getting is a bootloop so I'm not entirely sure what I'm doing wrong any advice would be appreciated! And again thanx for the info in the previous post!
Sent from my GT-I9000M using XDA App
yes you flashed just the kernel, you must first flash the stock rom and then any custom kernel for the same firmware -- you need the stock rom to install the correct bootloaders prior to flashing the custom kernel
so in odin, flash JVR stock in pda, KG3 in phone and CSC
tick auto re-boot
then flash the custom kernel of choice in odin under pda
Awesome thanks for the tips! Will give this a try
Hi guys - you guys might be able to help with a wee problem.
upgraded FW today via kies to 2.3.3 KG3 from froyo 2.2 with speedmod kernel.
in the process though i lost root but worse is i now don't have 3BR, when i used to. I still have 3 button download mode though.
I want to root again and flash a different kernel (for root but also for performance/tweaks) but worried to without 3BR ie. how will I access tweaks/enable root etc without it!?
Any ideas/advice please? Thanks
first flash a complete 2.3. firmware, either 2.3.4 JVR or 2.3.5 JVT. This should re-install basic 3BR functionality. I think you have not got the necessary bootloaders in the jump from froyo to GB and a complete stock install should correct this. Do tick re-partition and use 512 pit, do check auto-boot: let the phone boot and right itself. Check for 3BR and do a system reset.
Then flash KG3 modem and CSC. Your phone should then be functional.
Then flash a kernel with root inbuilt to it.
If you use the GTO Tornado kernel you can also clean your system completely as this stage instread. If you use another kernel, do the factory reset, davlik cache clean etc. prior to flashing the kernel as suggested above.
Do the clean prior to re-installing your apps.
lgsshedden said:
first flash a complete 2.3. firmware, either 2.3.4 JVR or 2.3.5 JVT.
Click to expand...
Click to collapse
Thanks! will give this a go but have only ever really flashed a kernel before with odin so want to be doubly sure about these steps if that's ok? apologies for my noobish ignorance
- only found a 2.3.4 JVR at samfirmware - getting this and the 512pit file. This should be fine?
- then flash a KG3 modem and CSC - any idea where I get those files from? - the ones i've got now i only got through kies (and when i do get em, when i do this in odin do i only use the phone/csc boxes and leave pit empty/uncheck re-partition?
thanks again mate.
Edit: forgot to say my reason for questioning the JVR is because the one i have is listed as European...where as I have a bell mobility but in australia - does this matter? latest FW for aus/america is JVN 2.3.3
no problem: always better to ask for help first then assitance fixing a problem when it all goes pear shaped.
There is a thread on the KG3 firmware with lots of these questions answered: http://forum.xda-developers.com/showthread.php?t=1211939 and also the basic resource for firmware posted by Ramad here: http://forum.xda-developers.com/showthread.php?t=1102881 -- scroll down and you will find KG3 under N.American, he also has a nice set of illustrations for using odin.
You can also source a cwm zip for the KG3 modem from perka's stash here and on the market (free app) -- useful to havce the modem in cwm zip form as then you can just install a new stock firmawre such as JVR or JVT and add the modem in recovery.
lgsshedden said:
no problem: always better to ask for help first then assitance fixing a problem when it all goes pear shaped.
Click to expand...
Click to collapse
Thanks so much again - that looks like a hefty bit of reading to be done there via your links so before I do that, just one more Q please - and apologies if the answer for this is somewhere in the links you've provided.
i was just trying to read up about why the samfirm file extracts only to a single .tar file called JVR_JVR_JVR and how to use that in Odin and came across this thread:http://forum.xda-developers.com/showthread.php?t=1075278
my Q is - in this thread he makes a strong point of stating not to tick repartition and not to put the .pit file...but you say to do so.
am i missing something obvious?
well different people different perspectives on re-partition and pit.
Tick re-partition and flash the pit file. Leave it un-ticked and do not flash pit file. That's the only key: do one or the other.
As I understand it, the reason to re-partition is that it re-sets the base file system upon which you are now flashing the stock firmware -- seems a basic step whenever you move firmware versions e.g. 2.2 to 2.3, 2.3.3 to 2.3.4 to 2.3.5 -- not so much if you are installing a rom or kernel within that family of firmware.
Since I always then convert the file system to ext2 to speed up the system and I use damain's kernel to clean the system, I do use the pit file whenever I flash a new stock firmware to clear the basic file system and further aid removal of legacy files that could complicate the install.
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
BTW the samfirmware files do extract using 7zip into the component parts for use in odin: pda (rom) phone (modem) and CSC. You then flash a custom kernel in the pda section if you use one for performance and root.
thanks lgssheddon, for the info here and in the PM.
Will crack on now with reading all the links you provided.
I just have to say a big fat D'oh! - why oh why could I not find the answer to what was bothering me most ie. apparent loss of recovery mode. The very first post in the first thread you linked gave me the answer - that it is now a 2BR (and tried it on my phone et voila, by magic I can get into recovery again!). Don't know how I could not find this thread even when I searched "KG3"!!
Thanks again for your help. i'l llet you know how i get on once i digest all this info
doktorV said:
Hi guys - you guys might be able to help with a wee problem.
upgraded FW today via kies to 2.3.3 KG3 from froyo 2.2 with speedmod kernel.
in the process though i lost root but worse is i now don't have 3BR, when i used to. I still have 3 button download mode though.
I want to root again and flash a different kernel (for root but also for performance/tweaks) but worried to without 3BR ie. how will I access tweaks/enable root etc without it!?
Any ideas/advice please? Thanks
Click to expand...
Click to collapse
The 3 button recovery has changed for KG3. I believe it used to be upvol home and power. I do believe now it is volup, voldown, and power. This should work for you to get you into recovery to flash whatever you like. Also the samfirmware for JVR is branded with Swisscom and doesnt work very well for using it with a KG3 modem and CSC, with my experience anyway. I would recommend to go to a JVQ PDA and use KG3 for your Phone and CSC. Also after you have installed this make sure to check what your country code is and install it. Hope this helped
lgsshedden said:
[/COLOR]BTW the samfirmware files do extract using 7zip into the component parts for use in odin: pda (rom) phone (modem) and CSC. You then flash a custom kernel in the pda section if you use one for performance and root.
Click to expand...
Click to collapse
The firmware that he is referring to doesn't. It is only one file meant for the PDA section of ODIN. Not entirely sure why they did this but i was running into problems with it as well. If you know how to play around with the core files you could in theory extract it to its root and put multiple files into .tar files (ex. select factoryfs.rfs, param.lfs etc. and place it under one .tar) but thats a lot of playing around and potentially dangerous if not done correctly.
not sure which download you are referring to but there was a branded version of JVR and a generic one on samfirmware: I have the one that does not have the swisscom logo and it certainly was extracted by 7zip into its component files (pda/phone/CSC) as they are still on my pc in that format.
You can also source stock firmware from Ramad's thread.
And I stand by my comment that for anyone using KG3 as a modem, JVR is the most stable official release available, much better than JVQ. JVT has a lot of promise and will be a better firmware than JVR but it is not yet had all the bugs sorted and while there are Gold Rom version for JVR any JVT rom is still at a beta stage and should not be used yet by someone just starting to flash custom firmware (IMO).
Hi again,
Q for lgssshedden really but if anyone can help i'd appreciate it!
have had 2 crashes now with Tornado Aureus RC1 - few little bugs/glitches eg with ringtone changing etc then on a reboot it won't go past the Tornado start screen with the big flame.
First time I just reflashed stock KG3 then reflashed the Tornado kernel, no problem. This time when I try to flash the Tornado kernel (either Aureus RC1 or Gold) it just bootloops at startup even though the flashing seems to go ok.
So now i'm back to (yawn) stock KG3 2.3.3. Really just want to root it again but with Tornado not seeming an option i'm finding it hard where to turn to root.
Thanks in advance!