Related
Hey guys. I had rooted my Nexus One without unlocking the bootloader using the 1-click root application. I have managed to successfully use Cyanogen roms in the past. I am currently running eViL's NXSense v1.26.
I want to now revert back to the stock Froyo Rom, install all the latest updates which have been done after Froyo 2.2 & be ready eventually for Gingerbread . My question is how I can safely revert back to the stock Froyo rom & still be rooted?
I have Rom Manager installed and I am currently using clockwork recovery. I believe that there is an option in Rom manager to flash the stock Froyo rom. Is this the best option to select? Also I have an ext 3 partition of 512 MB. Do I have to format my card to delete the partition ?
I would really appreciate if someone can post a step by step procedure regarding what needs to be done
http://forum.xda-developers.com/showthread.php?t=829577
Thanks for the link mate. I would still like to know since my Nexus is rooted, if I revert back to the stock rom will I lose the root? Also if I revert back to stock Froyo 2.2, will I get the OTA updates which have been released after that? Finally what about the ext 3 partition? Do I keep it or do I have to delete the partition and how I delete it if it is not required?
Hey guys. Can anyone please look into my questions? I want to switch back to the stock rom while still maintaining my root.
you will lose root on a completely stock (untouched) ROM, no matter the version. But you can always root back through various methods if needed. Rooting does not prevent you from getting OTA updates.
If you go to Froyo 2.2, you MIGHT have to manually update to 2.2.1 (FRG83) depending on if Google made the update available again (it was taken off for some reason...) but you WILL get future updates (such as the new FRG83D)
As for the ext partition, I do not think it's useful, unless you are planning to use apps2ext which requires root I believe. Don't take my word for granted, I don't know much about this.
Thank you replying mate. As mentioned earlier, rom manager does have an option of going back to the stock Froyo rom. I have a2sd enabled. So how do I go back to the stock Froyo rom. Do I have to format my sdcard to delete the ext 3 partition?
Hey guys. I managed to download & install Nexus One FRF91 stock rooted image using rom manager. I have also managed to restore my applications using Titanium backup. I can see all my root applications are working fine & I can also see the superuser app.
Now when I go to Settings--> About phone--> System updates, it gives me a message that my system is currently up to date. Is this because I am rooted? As mentioned earlier I rooted using the 1-click root & so my bootloader is still locked. How do I move on from FRF91 to the remaining Froyo updates while still maintaining my root?
Also when I connect my phone to my PC & use Minitool Partition Wizard, it shows me my ext 3 partition & the swap space. Since I am not using a2sd, how do I regain this space while still maintaining other files? Can I just delete these 2 things using Minitool Partition Wizard?
I would really appreciate some help here folks
Ok Mods I have finally updated to FRG83D without unlocking my bootloader Also I do not have to delete my a2sd partition now. So please delete this thread. Thank you to everyone who attempted to answer my queries.
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
Ok, so heres the deal. Was on stock rooted 886 w/o permaroot, and my dumbass did the OTA 893 update. Lost root, so I used R3l3AS3DRoot and did a Restore, Root, & For3v3r root. This brought my system back to 886, but from what I've gathered, my kernel and radio are still 893? My issue is, now I cant update at all, to 893 or 901 (basically what I want to do is run Eclipse V2.0 .901 Patched thats posted Here. I've tried this and the update still fails. I've also tried updating straight to 901 due to the fact that my kernel and radio are supposedly still 893 since I did that stupid ass OTA update. Am I screwed, or is there something else I can do?
BTW, I did get the Eclipse V2.0 901 Patched to install on my safe boot partition with bootstrap recovery, but I had absolutely NO DATA. I even tried moving the 901's system/lib files and still nata. I'm assuming this is due to the fact that the kernel and radio are still 893?
try the pathsaver method by p3droid. first go your sd-ext and remove any updates that are their or it will not push the ones you need. there is a vid out there somewhere on how to but it is pretty easy just read all instructions
New with this phone, messed around a bunch with my backflip several months ago
I have a Bell xt860 running 2.3.4 (bell stock)
unlocked and rooted (running on telus)
installed the latest safestrap from Hashcode (1.08)
grabbed the bell 2.3.6 rom that Willis111 link to (http://forum.xda-developers.com/showthread.php?t=1465153)
Followed the instructions on Hashcode's site (howto safestrap)
get stuck in boot loop
logfile says:
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x000
ro.hardware=mapphone_cdma
ro.revision=0
ro.kernal.memsize=512M
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:skipping execution of extendedcommand. file not found...
anyone know how to get this going forward?
Thanks
Hi
I have a Bell xt860 running 2.3.6 (bell stock)
unlocked and rooted (Ebay purchase)
i new in that business, there is way i could help?
I have 2.3.4. and I messed with some things so I can't do the O.T.A. update. Have you gone through the update process yourself?
I have an old /system partition from bell 2.3.4, can you dd that back in? I also have an old nandroid backup of the system partition that maybe you can use...
Let me know where to put things as I"m still at a loss!
Sorry, I don't understand what you mean my "dd that back in" I screwed my backup up in safestrap. Now I have wifi only. Don't really know what to do at the moment. My original problem that prevented my O.T.A. update was killing some required apps. (contacts is screwed as many people have done lol) I guess if I can get it back to a more "stock" version I could get the O.T.A. to work.
I am going to look for the stock system dump. I remember seeing it around.
Hey, I posted a guide on how to upgrade a rooted 2.3.4 to 2.3.6 below:
http://forum.xda-developers.com/showthread.php?t=1404608
Thanks for the link. I checked that before. The zip file link gives an F.B.I. takedown page though.
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