Hello
I own a French Galaxy S for more than a year, it's an unlocked unbranded one bought in Pixmania
Model number is I9000 and PCode is GT-I9000HKYXEF
Installed firmware is 2.3.3 updated officially by Kies one year ago
PDA: I9000XWJVH
PHONE: I9000XXJVO
CSC: I9000XEFJV2
It seems to be the latest version released for my phone in France (CSC XEF)
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do
You could use this guide for rooting your phone:
http://www.theandroidsoul.com/fuguroot-galaxy-s-how-to/
Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.
albertocastillo2001 said:
Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.
Click to expand...
Click to collapse
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app
AlwaysDroid said:
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thank you.
why donn't you upgrade it to 2.3.6
for root use cf root kernel or semaphore kernel
I cant post in this thread for some reason. Ill try later
albertocastillo2001 said:
I am going to split this post in two cause there is alot...
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
- Being upgraded to 2.3.6 or whatever isnt really that great. A few changes were made, but really not much. Like some sgs devices have 2.3.4, mine came with 2.3.3 and you really cant tell the difference. here is a complete list of the changes if you want.
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
-I am to lazy to type how it works so go here. I learned off of that website. As for the other part, You can return to stock and never have samsung notice because we dont have a flash counter.
Click to expand...
Click to collapse
There you go. /Part 1
---------- Post added at 04:15 PM ---------- Previous post was at 04:01 PM ----------
albertocastillo2001 said:
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
-Technically all roms use root. The difference here is that what you are referring to is the user having root acess. And of course Samsung doesnt really want uneducated people messing with the phones software, so it is locked away from the user. But the system still has to use it. But you do not have to have a custom rom rooted, but fact is that almost all are. For example I tried out a new jellybean port early on and it had no root access. The only thing in this case is that you must flash anything via odin instead of CWM.
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
- I dont know where you heard this, but the bootloaders so not change on flashing a custom rom. Anyway, when you flash back to stock with odin, EVERYTHING goes. It will be 100% stock, not a single trace of you being rooted, having kernel and recoverys installed etc. Totally new.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
- Indeed, they tell odin how to partition your device. There is no advantage to either or. Read here.
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do
- Indeed each country seems to recieve a different version for some reason.
Click to expand...
Click to collapse
Part two. Hope that helped!
Hello
Thank you very much.
I'm at work but I will read it again when I get home. It really helped, the rooting technical guide was pretty clear, and the PIT file information as well.
About the other questions:
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
Click to expand...
Click to collapse
It's ok, the GPS is driving me nuts
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
Click to expand...
Click to collapse
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
Click to expand...
Click to collapse
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
Few more questions
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
What's the [Dump] option in Odin? Haven't seen that anywhere
I have to read some more info about the bootloaders first before being able to ask more.
Thanks
albertocastillo2001 said:
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
-I very much so agree, i dont know why you would want to use that. But Odin is the official samsung flash tool, so i bet that samsung uses it in their repair centers for something.
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
-Yes they are separate partitions
- This is not bad at all. Usually before i do nandroids in will do a /cache clear to make it smaller. I think it might actually be beneficial to clear it once and a while anyway. Sometimes i just clear it. Your phone will boot fine. Keep in mind that clearing cache does not clear the dalvik cache, as this is kept on /data and has to be cleared from the advanced menu. Also a word of caution, i wouldnt clear the dalvik while your phone is on, everything will force close. So just do it from recovery
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
-What more details so you want? and yes whenever you perform a factory reset, the dalvik cache, /cache and /data partitions are cleared. But just wiping /data will be the same, but the cached reminants will still be there, which isnt an issue, its just wasted, thats all.
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
-Ah i get it, and yes you are correct. Even though there will never be another update for your device.
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
-Yes, i believe that the 10mb is transfered between the two. But when you install cyanogenmod 9, it gets rid of /dbdata. There should NEVER EVER EVER be a risk of messing with /efs. It is a rare occasion for it to go corrupt. Possible though, so do your backups.
- As for being the most important partition, it is hard to say. Your phone will boot with no /efs, it will just lag like hell, have no service or imei. Kinda hard to explain that one to the repair center since nothing touches that partition, ever.
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
-I believe that the kernel parts are mainly stores in /sys, although there are pieces in other places as well. (ex: /data/local/devil for devil kernel settings)
-Also, unlike my old galaxy gio, the recovery is packaged with the kernel on galaxy s. So changing the kernel replaces the recovery as well. You cant do it individually.
-Yes, all aftermarket and stock roms come packaged with a kernel. For example, i use devil kernel with my cm9. But when i flash a new version of cm9, it replaces the kernel and i have to flash devil kernel again.
What's the [Dump] option in Odin? Haven't seen that anywhere
-DONT take my word on this, i am not 100 sure. But i think dump, performs a dump of all the partitions to your computer. Not sure, so i dont advise trying it without research.
I have to read some more info about the bootloaders first before being able to ask more.
-Okay, let me know!
Thanks
Click to expand...
Click to collapse
.......
Hello
Thanks again
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
I guess these are all the questions I need to ask to cover all doubts.
Thanks!
albertocastillo2001 said:
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
-Nothing unless otherwise stated messes with the bootloaders on most devices. But our bootloaders are unlocked, meaning the partitions arent signed and the bootloader doesnt check for sigantures, so it doesnt care if we have a custom recovery. When we use the three button combo, all it does is trigger the bootloader to boot into the recovery partition. But since they arent locked (bootloaders) and partitions arent signed the bootloader doesnt care whats there. Itll boot whatever is there. So no mods needed for custom recovery.
********NOTHING MESSES WITH BOOTLOADERS UNLESS OTHERWISE STATED ***********
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
- Yes everything you need to go **********100000000000000000000000000000000000000000000000000000% back to stock ************ is in there, even bootloaders. The primary bootloader isnt, cause nothing will ever touch it.
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
-The only thing you should backup is /efs
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
-Odin only will repartition /data /cache /dbdata and /system back. Removing things like /datadata in the process.
****************NOTHING EVER EVER EVER MESSES WITH YOUR EFS> EVER****************************
Except unlock attempts
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
-This is a question i wish someone had answered for me when i was new here. Odin wont format the /data and /cache and dbdata(i think?) when flashing back to stock, so if you try to boot, you will bootloop. Only the stock recovery can format to rfs and knows how to handle it, so you must do a factory reset to format the rest of the partitions back to RFS.
Click to expand...
Click to collapse
Hope that helps you out
Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added
Samsung stopped genuinely supporting this phone quite a while ago. The burden of updating the device has fallen onto the development community. Given that the I9000 is one of the most popular Android phones, LOTS of development has taken place since then.
The kernel on this device is part of the boot image, on its own partition. Recovery is coupled to that partition.
Rooting a device adds a new binary (su) to the system partition. This file is given permission to run as user 0 (root) and acts as a proxy for other processes to perform privileged actions (deleting system files, mounting partitions, accessing all data, etc).
Most custom ROMs come pre rooted since rooting is quite popular. Titanium Backup is the exemplar for what an application can use root privilege for.
Installing a custom ROM does not require the stock ROM to be rooted, it requires a custom kernel (with a cwm or twrp based recovery).
Most high quality custom ROMs (read CyanogenMod) have scripts to protect the efs partition while flashing.
As long as you can get into download mode on your phone you can always get back to stock firmware. The service centre won't know the difference.
The bootloaders are provided by Samsung, these are not replaced by custom ROMs.
Personally I run a modified build of CM10 and use a radio from the Nexus S (KJ1). I'm very happy with the overall battery life of my phone, signal quality is good in Australia (can't say with certainty for any other part of the world) and performance is quite snappy.
Sent from my Nexus 7 using Tapatalk 2
albertocastillo2001 said:
Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added
Click to expand...
Click to collapse
Jus read things that come up in the questions/answers forum. Learn from other peoples mistakes
Sent from my GT-I9000 using xda app-developers app
Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs
albertocastillo2001 said:
Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs
Click to expand...
Click to collapse
Baseband/modem (samething,)is the little piece of software that talks to the cellphone towers. And because each area uses a different frequency, there are many different ones.
Also good to note that it is not ATS all related to GPS or WiFi.
Sent from my GT-I9000 using xda app-developers app
Related
Hello people !
Since I'm living in Tokyo, I'm the happy owner of a Galaxy S, but unfortunately it doesn't seem to be exactly the same like the other devices.
Anyway, since 2 days ago, I had some fun (and cold sweat also) trying to root it, unbloat it, etc... Some difficulties and questions left without answers, so if anyone has a guess, please be my guest !
My phone as I got it :
SC-02B, with OMJJ1 firmware (Froyo 2.2)
1) Rooting
The easiest thing ever.
The SuperOneClick pack did a wonderful job.
http://forum.xda-developers.com/showthread.php?t=803682
2) Getting a "safe" firmware
Just in case anything would go wrong, I wanted to be able to flash back to an official firmware.
The ones from this post work without any problem so far.
http://forum.xda-developers.com/showpost.php?p=10558974&postcount=134
However, problem 1 : I couldn't get Heimdall flash my device. Since I'm mainly working on Linux and OSX, that would have been of a great help.
But the "handshaking with Loke" step is always failing...
Actually, I even though I had bricked the phone, since I was stucked with a black screen (1PC and 1GSM in orange) and it took me ages to figure out how to get rid of that.
Solution : get myself a Win 7 computer at office and use Odin. No problem so far with this one.
Problem 2 :after flashing with the official update, I get complains in the recovery mode (when unpacking the apps I think), saying that /dev/block/mmcblk0p3 cannot be mounted, because it does not exist.
After searching on japanese sites, it seems that there is a 3rd partition in addition to the one for /sdcard and /data that is used (as far as I know, only for that) by an app called DioDict (japanese / english dictionary).
Not that this is a great loss, but I don't know where and why this 3rd partition was deleted. I tried to restore one, but after a while I just gave up, since I don't have any dump of the data that was there anyway...
Could anybody confirm/infirm this ???
3) Recovery 2e
Since I wanted to test to other roms, I needed to get back to the recovery 2e.
I gave a try to CF-root, which included that also.
http://forum.xda-developers.com/showthread.php?t=788108
Once again, Odin was the only one that could do the job, Heimdall still ignores me.
Problem : the update is successfully done, but for a reason I ignore, I lose my SIM card in the process.
Flashing back an official ROM makes it available again, but CF-root won't allow me to phone in Japan.
How did you people handle that ? Unfortunately I couldn't afford staying too long without a working phone, so I didn't investigate much further, but did other people have the same kind of problem ?
Conclusion :
As of now, I have a rooted device, and am pretty happy with it.
However, I wish I could give a try to the nice work I've seen around (CyanogenMod on Galaxy S seemed very yummy), while still being able to use my SIM card here.
Any feedback is welcome !
I haven't played around that much with DioDict to tell you right away how to solve this, but maybe there's some answer getting the first firmware:
SC02BOMJJ1 (10/10/13) :
http://fus.samsungmobile.com/Phone_...2BDCMJJ1_SC02BOMJJ1_SC02BOMJJ1_OM_DCM.zip.enc
BINARY_ENCRYPT_STRING 1662317
thanks a lot for this link ! just a question, where did you guys find them ??? the site itself seems very dummy
but as far as I could read on japanese threads, that seems to be some prefab settings
in my case, that third partition has been deleted, so I think I would have to recreate again beforehand.
as for the "how", I must confess I don't know... I' had somehow succeeded in running parted to create one, but for a reason I ignore couldn't assign it to the block
I could install a Cyanogen Beta3 today, and though everything is alright, still got no 3G.
SIM card is not recognized, and it seems impossible to input the appropriate APN information. Could it be that the modem embedded in the SC-02B is different from the mainstream one ?
EDIT : seems that indeed the SC-02B has a different modem. At least the firmware has a different size, hence the need of a different PIT file when you flash from an "international" ROM.
I'm starting to wonder whether I'll see the end of it someday >_<
things that seem to work
Now that we have the capability to recover after we trash our ROM what can we do.
Super Oneclick root - works
Z4Mod "because we all have the need for speed" -works after you use titanium backup to remove some of the bloat-ware from /system
Z4Control works if you use Z4Mod to patch the kernel and convert /data to ext2 first.
The UOTKitchen will work to change the battery icon and other status bar icons if after you have completed these steps http://forum.xda-developers.com/showpost.php?p=9318973&postcount=1290 you extract the framework-res.apk from the resulting zip file and use adb to push the new framework-res.apk to /system/framework/framework-res.apk followed by an adb reboot recovery command before you do anything with the phone. From the recovery menu wipe cache and then reboot now. If you don't do this last step it could lead to having to reflash the factory firmware happened to me about 6 times this weekend. DO NOT TRY THIS IF YOU HAVEN'T CLEARED ENOUGH SPACE ON /SYSTEM BECAUSE IT WILL KILL YOUR PHONE!!!!!
For all those who want a pit file, here I leave you a custom pit file created for the sc-02b.
I must make this clear, this PIT file was made for those who flashed their devices with a rom for some other galaxy s version and want to reflash their devices back to the original SC02BOMJJ1 rom. I cannot ensure you it will be useful or that it will work for anything else.
Also, when using this PIT file with odin, be sure to check the "Re-partition".
@shikigamild :
is this PIT file the same that came from komugi.net ?
at the same time, could you tell me how you got the stock rom file links please ?
@dejanet :
so you say that with the Z4mod you have a fully working device ?
has anyone tried the CF-root package ? after applying it I lost my SIM card, so I wonder if you experimented the same kind of inconvenient there
Oh yes went through all of the fun of trying the various kernels everyone leaves you with sim not recognized.
Sent from my SC-02B using XDA App
Aaarghh,that sucks donkey balls...
Guess that means we won't get any, custom rom any time soon will we?
I'm new to all this stuff, so apologies for the noob questions.
I rooted my SC-02B using the tool in this thread. I was able to install and use the Barnacle Wi-Fi tethering app from the market, so I know it was a successful root. Now when I go to install and use Titanium Backup from the market, it tells me I don't have root access or don't have BusyBox installed. When I go to install BusyBox from the market it shows my phone as being rooted, but when I tap install it gives me a failed message saying my phone isn't NAND unlocked.
How do I do that? Once I get that problem solved, what are the next steps for installing the Z4Mod?
So far I've never installed BusyBox through the market. Just install it with Titanium and it should work fine (click the "Problem ?" button).
Then, I suggest that before doing ANYTHING involving a custom initramfs (like ClockWorkMod), you dump somewhere your mmcblk0p3 partition, in case you want to restore your phone exactly to the same state you got it.
If your not that paranoi, you can skip this part, but as I wrote myself a dozen times here, I forgot it and would be interested also ^^
Ok, thank you for the info. Does Z4Mod cause any problems with this phone? I read in dejanet's signature that the lagfix seems to cause problems. Z4Mod is the lagfix he's talking about right?
bnr32jason said:
Ok, thank you for the info. Does Z4Mod cause any problems with this phone? I read in dejanet's signature that the lagfix seems to cause problems. Z4Mod is the lagfix he's talking about right?
Click to expand...
Click to collapse
z4mod is just a rooting app. There's no lagfix. He's probably referring to OCLF which is made by the same developer. It's obsolete now, so do not use it.
About the rom problem, can't you just flash the modem from a Docomo rom after installing the custom rom?
No, z4root is only for rooting, but z4mod is a lagfix application. As far as i know, it will convert your phone system to ext2. However, i scare it will affect the DioDict application in SC-02B, so i haven't tried it yet.
Trojan,if you fear losing diodict,you can still dump your mmcblk0p3 partition.
It is the one containing diodict data.
I would actually be very grateful for an upload of that one (^-^)/
Sent from my SC-02B using XDA App
trojan111 said:
No, z4root is only for rooting, but z4mod is a lagfix application. As far as i know, it will convert your phone system to ext2. However, i scare it will affect the DioDict application in SC-02B, so i haven't tried it yet.
Click to expand...
Click to collapse
Opps. Didn't realise there are two apps with similar names.
Still, wouldn't suggest it. EXT2 is unstable.
Hi, bebert218. Actually, i am a noob, i don't know how to do it. Can you tell me how to view the partitions in the internal memory? I suppose DioDict application contains a database file somewhere in the internal memory, but i don't know where and what the file name is. Appreciate if you could give me a hand on it. Thanks.
Custom Kernel and Roms
From reading through the forums it seems custom roms present issues with the either the sim card or modem on the sc-02b. Are custom kernels causing issues as well on this phone?
Yes it is the kernel that causes the problem. I think a couple of us have tried them all.
Sent from my SC-02B using XDA Premium App
disappointing Other than rooting and using Galaxy tuner to do some tweaks there isn't really much else to do. At least the upgrade to omka5 showed much improvement from 2.2
Hey XDA
I've been flashing numerous kernels + roms for the past few days, some went well, others, not so well. After all this, for now I've settled for a kernel which is easy to get to + a rom I really like.
My concern now is, what is the impact of all this on the filesystem. Meaning, what exactly does flashing do? Overwrite the important things such as /sys, /system when it comes to flashing a kernel would be one I guess, but does it completely delete the previous contents and write the new data or just overwrite it, thuus files created after one flash that weren't part of another flash remaining there ?
Any info is appreciated!
Always disable lagfixes before flashing
Sent from gt i9000 insanity 8.5/fugumod
yes as said above, always disable lagfix before flashing a new rom, this will prevent the majority of corruptions.
also if you ever run in to problems, the best way to fix is to flash a full 3 file firmware along with pit file and repartition, this will restore the filesystem to as it was when it was new. leaving everything as it should be all nice n clean
And in my experience, some Roms / Kernels Overwrite and leave traces of the older version and some completely remove all traces of the older version..
but ive been on MIUI for ages and ages, and roms and kernels have progressed A LOT since then, so this may no longer be an issue
Happy flashing
Hi all,
Had my GS a few weeks now but am in a bit of a predicament. When I received this phone I thought that Three had announced the availability of Gingerbread. However, I had not realised that to update the phone with Kies would require that I had a landline broadband connection as I use the phone with usb tethering for my internet use. This being the case I contacted Three who told me I could take the phone into a certain Car Phone Warehouse that has a service center. I had to leave my phone with them the whole day and when I collected it, they had flashed a rom which is not one of Three's and also took me back from 2.2.1 to 2.2. I also no longer have an option in Settings>About phone, for Check for updates.
I have since used super one click and managed to root it (my first time rooting) and done a backup of /efs as I read that is good as it contains IMEI info etc. Also now have Titanium Backup Pro and done a batch backup of all user apps & system data.
Phone has become quite laggy but reading info on using a different kernel it didn't seem to make sense to do that until after updating the rom.
Is there anything here to explain what the rom file name convention means please? I found the following link on here to the stock firmwares but don't know how to differentiate between the rom names? i.e. how do the following two differ?
http://forum.xda-developers.com/showthread.php?t=1102881
XXJVQ/XXJVQ/OXAJVQ/Sbl (MultiCSC)
XXJVP/XXJVP/OXAJVP/Sbl (MultiCSC)
Is it possible to root gingerbread 2.3.4 after flashing to one of the above?
As I rely on the phone as my only way to connect to the internet should I also do a Nandroid backup? I've only heard a little of this, my understand is, this is a way of creating an image of the phone as it is now so that it can be re-imaged from this somehow if something goes wrong? Any guides on creating a Nandroid backup please? This isn't the name of an App is it, rather a term or something to do with using terminal?
Am guessing I need to move my Titanium Backup files from /mnt/sdcard/TitaniumBackup somewhere else before flashing or does that not wipe this area?
I've downloaded odin from the thread above so I have v1.82 along with the 3 .pit file versions.
Is there anything else I should do or need before proceeding?
Thanks in advance for any assistance with my understanding of this.
Currently my phone info reads;
Firmware version: 2.2
Baseband version: I9000NEJP2
Kernel version: 2.6.32.9 [email protected] #1
Build number: FROYO.NEJP5
Lol.amazing i was.in the same predicament like u two days bak hahahaha but instead my fne was brand new lol....
Anyway i got gingerbread astock now runnin on me fne so do this as.i.did.it like this
Download the JVQ file of 2.3.4 and then extract it... Use odin to flash ure fone... Im pretty sure on that thread it shows how.to use.odin and flash but here goes
First open odin and go into download mode with ure fne( by switching ure fne off then wait til it vibrates...then preaa.altogether the volume down key ure home key and power key.... Then plug in usb then flash yhe rom like.how.it is.sed on that thread which u founf the firmware on.... Hope this helpa
..::XDA RocK::..
Sorry for spelling mistakes lol still gettin used to the virtual keyboard lol
..::XDA RocK::..
Nandroid backup is a name of app which you can use for complete ROM backup useful in times of complete crash.
Just be careful when flashing. Normally it shouldn't screw up your phone but you need to be careful and ALWAYS read the Instructions in full. I have seen people ruining their phones just because they never read the what they were supposed to BEFORE starting.
All the best!
Thanks for the info.
I've found this guide now to Nandroid, which says the easiest way to get it onto the phone is to install ClockworkMod Rom Manager from the Android Market. I'd previously been looking for Nandroid in the Market.
http://www.androidpolice.com/2010/0...nandroid-backup-and-clockworkmod-rom-manager/
Trouble is when auto detecting my model it gives a couple that could relate to my model and I don't know what the difference is...
Galaxy S i9000
Galaxy S i9000 (MTD)
Does anyone know what the significance of the MTD is please?
Use the one without mtd as that is the originak international version....
..::XDA RocK::..
Hi
Thanks, I did some googling and came to the same conclusion, I think the MTD has something to with Cyanogen.
Anyways, am stuck at the moment at the next snag now in that I appear to have the more recent version of recovery i.e. the 3e instead of 2e needed.
This guide says I need to flash a custom rooted kernel (a CF-Root one) but my Menu > Settings > About Phone, ‘Build Number’ says ‘FROYO.NEJP5’ and I can't see which is the corresponding CF-Root kernel.
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/
http://forum.xda-developers.com/showthread.php?t=788108
Besides I am still on the original file system also and would prefer to be on ext4 to fix lag.
More rethinking required.
You dont nid root to flash a new firmware such as the jvq gingerbread.... If u flashed that u cn hav both ext4 and root support for ure fne so why dnt u flash ure fne to 2.3.4 first then root then ext 4 it.... Step by step i guess
..::XDA RocK::..
Prior to this thread I had read the following advice that before you do anything, you should back up your /efs folder containing not least your IMEI info.
http://androidforums.com/galaxy-s-a...d-19-18-pm-est-apr-08-2011-major-cleanup.html
http://forum.xda-developers.com/showthread.php?t=859914&highlight=restore+imei
To do that requires root as I understand and whilst the above suggests that on 2.2 you should use z4root, I actually used super one click which worked and has an unroot option too.
I also wanted to be rooted because I already lost my user apps and data when it was flashed to 2.2 by the service center and concluded that the only decent back up apps all required root.
I wish I had rooted while I had the carrier version of 2.2.1 on my phone and made a Nandroid backup of that so I could return the phone to that state in case of warranty issues. I never foresaw that the service center would flash a non carrier branded type rom onto it.
Although I'm not overly keen on 2.2 or the lag issue, it works and therefore I think the prudent thing to do is do a Nandroid backup of this so I can at least get back to this if something ever goes wrong. However, I think I have read somewhere that Nandroid requires the ext4 file system too, so I think I need a kernel that does this as well as one that has recovery 2e and all for my existing 2.2 rom.
I don't know how already being rooted or that busybox is already installed (think either super one click did that or titanium backup) affects flashing a new kernel?
Since reading some other threads of people who have flashed up to 2.3.x this was prior to it being officially released in the UK and I see some now wanting to get back to 2.2.x so they can update to the official release.
So it might be better to get things to a state where I can upgrade to that via Kies in an internet cafe or something.
Anyways have a bit of a headache now so not doing any more today.
Completely rom'd, kernel'd and flashed out.
Just a quick update as I had to give up on Kies in the end.
However, I did discover, for others like me without a separate broadband connection, enabling the Mobile AP and connecting the phone in Kies mode was possible, whereas the usb tethering is not. This allowed Kies to recognise that an update was available and also downloaded it. I had to use an app from the Market Place called Spoof FW prior to connecting the phone to the laptop which allowed me to choose my carrier so that Kies offered the correct download.
I then had a problem that the phone wouldn't flip modes from Kies to the download mode but instead would hang in the Kies preparing firmware process. I deleted a couple of thumbnail picture files that had long file name extensions and did a factory reset and then kies was able to change the phone into download mode. However, at this point, perhaps because the laptop I was using is old and only has the old usb ports it would then report that it didn't recognise the usb device or crash device manager.
Anyway for now I have given up on the carrier rom option and opted for an Odin flash of JVQ and CF-Root 3.7.
Phone is now a lot faster than Froyo 2.2 and next on the agenda is to use the CF-Root addon for converting to ext4. The only downside I've found so far with JVQ is the usb tethering is flawed, either doesn't recognise that the usb is connected or seems to freeze net comms over the usb service after only a short time. Mobile AP seems to work so I have a pci wireless card coming to upgrade the desktop PC.
Hope the usb tethering gets fixed in the next Android release but hopefully for now I can manage.
Hi Guys! I have a Galaxy S1 (I-9000). I've used a custom ICS rom until yesterday, but it was slow, and drained my battery very quick. So I XXJW4 (as far as I know this is the latest official release with value pack), but there are wierd issues (very quick battery draining, wifi disconnecting, doesn't remember my mobile network settings, sluggish browser, etc).
I did the usual stuff like cleaning cache/dalvik/factory reset. Usually I like hacking around with theese things, but now I just want to use my phone, so I would like to restore it to a "very" official state. I'm not sure about the technical details, but afaik some of the update packages are not completely reinstall everything. So what is the correct way to clean my phone so it would look like a brand new one like it has never been modded?
I think I need to repartition. Even if I don't want to change the file systems I would prefer to have a fresh start so no previous data could remain. After that I would need a firmware that contains everything (kernel, bootloader (?), modem, dbdata, factory file system, etc etc) I've already found a lot of roms out there, but I'm not certain witch one will do the job. After I installed the value pack update I realized that dbdata was not part of that package, and I had to find one after googling for a while. So I'd really appreciate some pointers
So that's my story, to sum up the question is how to restore a galaxy s to an older version my making sure everything is completely wiped, overwriten, reinstalled, etc.
Thanks in advance.
go to sammobile dot com webpage and search what firmware you need and download. Flash this rom with odin.
Use Odin to flash the.rom that you like
why dun try ICS infinitum by bhu1...amazing,,...
It is not true. In the past i flashed with odin and it did not even remove all of the apps i had installed with 2.2 ...
DaveBG said:
It is not true. In the past i flashed with odin and it did not even remove all of the apps i had installed with 2.2 ...
Click to expand...
Click to collapse
Okay, let us be more specific:
- format /sdcard
- format /system
- wide data/factory reset
- flash with odin
Nothing and I mean nothing will be left on your phone. That process formats everything you need to in order to wipe your phone.
Good luck!
Read this https://www.fixmystuff.in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom.46/
Value pack made my phone weird to.
just download some original Rom and flash via odin that will work
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
ttibbetts83 said:
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks ttibbetts83, I will try that and see how i go
Thanks Arobase40.
I'll get a strong coffee and read your reply from top to bottom and then plan my next move.
The repair was done by people unrelated to Samsung.
I currently have GB v2.3.5, (SGN_XX_OXA_KJ1_FACTORYFS) which works well, it would seem.
I'd love to get ICS back on it but need to gather info (such as that from yourself) before I do anything.
A bit more info on the state of the emmc storage: Using 'adb shell' and executing the command DD did in fact find bad blocks in partitions 9-11 (can't recall right now exactly which ones), so there are issues there.
The partition that is in place now, __appears__ to have successfully skipped those bad blocks.
And on something slightly tangential to the current topic, I know that doing a 'WIPE DATA' from the recovery menu zaps emmc, but does that also happen when you do a factory reset from within Android? From memory, when doing so, it seems to go into recovery mode and do it, so I'd expect that it'd also damage emmc.
Cheers
arobase said:
As opposed to all alarmist and contradictory posts about eMMC bug on stock Samsung ROM : GB or ICS, I never got any issues with this so called eMMC bug and never got bricked G-Note as long as I kept at using the stock kernel, nevertheless I made various and numerous wipe whichever the ways (from recovery or the settings)...
For rooting, I always used the temporary Touch CWM to flash (which has been may be removed from XDA, I guess as it was supposed to cause bricked devices) anything : superuser, busybox, and other custom ROM... ^^
BUT when I flash a custom ROM, I always removed the custom kernel (so called "safe"), and replace it for a stock kernel and never got issues with it.
The first and last time I flashed a custom with custom kernel I got my G-Note bricked (just forgot the replace the custom kernel for a stock one... ^^) !!!
So, if you want to flash an ICS version, get one from Sammobile, and flash it with PC Odin !
You shouldn't have any problem with them !!!
Get all root and busybox files from dr Ketan, and if you can find it again use the temporary Touch CWM which has NO kernel inside : it WORKS quite fine !!!
Click to expand...
Click to collapse
Unfortunately there are no high trees on XDA beause you should look for one before typing this utter personal nonsense that could brick anybody's Gnote.
Taking your own convictions for thruth is one thing, sending innocent ppl into the jungle is another...
What you are saying is: If there is a lightning storm, just go into an open field en enjoy. I cannot say it is 100% safe, but I never got struck....I think they removed the tree i used to seek shelter from the rain, but if you search real hard you might find it anyway.
---------- Post added at 10:33 AM ---------- Previous post was at 10:17 AM ----------
amanmasgaman said:
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
Click to expand...
Click to collapse
Actually you should be happy that they revived your Note after brick even if it's only running GB for now.
However if you are a brave person you can do the same trick on ICS.
Just read and understand the thread that is a guide on doing so.
You can root your GB without a problem, but there is no obligation for it to install ICS with odin.
However what you do need is the following (besides a lot of patience and courage) :
1. get the ICS files you want to flash including the pit file.
2. get a program called PIT MAGIC to recreate a suitable pit file
3. determine where your bad blocks are located
4. Load the pit file into the magic program and alter the stock pit file
with the values needed to ommit your bad emmc area
5. save it and then flash your note in odin with your newly created pit file and repartition ticked.
@OP: could you please check your internal storage capacity? Is it aroung 8GB?
Arobase we are not going to rediscuss this matter for another 556643 pages.
Just ask yourself : if there was no problem then why did samsung patch their JB kernels for it. http://forum.xda-developers.com/showpost.php?p=34933643&postcount=683
Also nobody asks you to reconsider your own experience and beliefs, but the day someone follows your instructions and bricks his phone, are you going to pay for a new motherboard ?
I'll stop this discussion here, and just hope nobody will get struck under the tree.