Hello,
I upgraded from 2.3.3 to KI4 and the screen calibration became BAD.
(compare image is attached, look at the icons, the black became too black and the color is way too strong).
I also tried KI3, and there is the same problem.
(all the changes made via CWM .zip updated (not Odin))
Thanks a lot
sagi.m said:
Hello,
I also tried KI3, and there is the same problem.
(all the changes made via CWM .zip updated (not Odin))
Thanks a lot
Click to expand...
Click to collapse
Changes made via CWM what version of stock KI3/KI4 is that or do you mean a custom rom ??
jje
All of them were stock roms (also tried 2.3.4 KH4) that include a kernel with CF ROOT and RTL fix.
the last rom i tried was madmack's KI3 (the picture i added is the KF2 (KE2 Kernel with root) with the good picture and the Madmack's KI3)
Confusion is stock rom via CWM i am not aware that is possible .
But you say Kernel ???
Madmacks custom rom ??? .
jje
I am sorry, not stock rom, custom rom with minor changes.
this one:
http://forum.xda-developers.com/showthread.php?t=1083187
the KH4, KI4 and another KI3 that i tried is roms that the only changes that were done are the following:
1. RTL support.
2. CF ROOT.
the rom that i am using right now (2.3.3) is:
rom XXKF2
kernel XWKE2 rooted.
and that rom has a GREAT image quality.
anyone, help?
I got the same problem, I updated from stock to KE7, I 'm thinking that it might be due to a failed attempt on the first attempt to update the firmware using Kies, it got to 75% and did't budge after 4 hours so I was forced to disconnected, thought It bricked but luckily was able to access download mode and use Odin to upgrade to KE7, whoop, a solution to this great though??
Related
I have a SGS2 with the default ROM the phone came with, and CF-Root installed with CWM v3.0.0.5. Specifically, this is what’s installed:
Baseband version: I9100XXKDJ
Kernel: version 2.6.35.7-I9100XWKE8-CL214845, [email protected]#2
I just launched Kies to check for a firmware update, and was told this:
Current firmware: PDA:KE2 / PHONE:KDJ / CSC:KE2 (NEE)
Latest firmware: PDA:KF3 / PHONE:KE7 / CSC:KF1 (NEE)
I don’t quite understand what constitutes the Android firmware as I’ve recently migrated from iOS where baseband (modem) and OS are the two versions one needs to keep in mind (or just OS, if you had an unlocked iPhone like I did) for a jailbreak/unlock. Thus a few questions:
1. What are the PDA, PHONE and CSC parts of the firmware?
2. Why are there so many types of firmware; if you look at Chainfire’s CF-Root post there’s a host of patched kernels. Are SGS2s sold in regions with varying hardware? With the iPhone there was one hardware version, one OS (Verizon excluded). Simple.
3. I want to flash a custom ROM (Batista70 based on 2.3.4) - what is the best way to make sure everything is up to date before I do this? I was thinking of letting Kies update (which I guess will remove my root access), then installing the latest version of CF-Root with CWM 4, and finally flashing the ROM from CWM. I have the relevant app data backed up with Titanium Backup.
Many thanks!
Nitsson said:
I have a SGS2 with the default ROM the phone came with, and CF-Root installed with CWM v3.0.0.5. Specifically, this is what’s installed:
Baseband version: I9100XXKDJ
Kernel: version 2.6.35.7-I9100XWKE8-CL214845, [email protected]#2
I just launched Kies to check for a firmware update, and was told this:
Current firmware: PDA:KE2 / PHONE:KDJ / CSC:KE2 (NEE)
Latest firmware: PDA:KF3 / PHONE:KE7 / CSC:KF1 (NEE)
I don’t quite understand what constitutes the Android firmware as I’ve recently migrated from iOS where baseband (modem) and OS are the two versions one needs to keep in mind (or just OS, if you had an unlocked iPhone like I did) for a jailbreak/unlock. Thus a few questions:
1. What are the PDA, PHONE and CSC parts of the firmware?
2. Why are there so many types of firmware; if you look at Chainfire’s CF-Root post there’s a host of patched kernels. Are SGS2s sold in regions with varying hardware? With the iPhone there was one hardware version, one OS (Verizon excluded). Simple.
3. I want to flash a custom ROM (Batista70 based on 2.3.4) - what is the best way to make sure everything is up to date before I do this? I was thinking of letting Kies update (which I guess will remove my root access), then installing the latest version of CF-Root with CWM 4, and finally flashing the ROM from CWM. I have the relevant app data backed up with Titanium Backup.
Many thanks!
Click to expand...
Click to collapse
1. Pda is the basic firmware, Phone is the modem responsible for wifi/2g/3g, csc is the country specific code - language files/apps etc. You shouldn't consider these as separate, they all combine to make a single firmware (which will have the pda code)
2. There are multiple firmwares because they keep getting updated, the cf-root has multiple versions to accomodate those who haven't update to the latest. Usually the highest alphabetical and number code is the latest, currently kg3 i believe
3. Whatever kies updates, flashing a rom over it will overwrite anyway so there's no point using kies
Make a nandroid backup from cwm before you start flashing ROM in case something goes wrong
Ok, so neither pda, phone or scs constitute the kernel? I appreciate that custom ROMs incorporate the official (and sometimes the unofficial) Samsung releases meaning I don't need to faff around with Kies, but CF-Root handles only the kernel if understand it correctly.
In Chainfire's guide on rooting, specifically the but on getting rid of the warning triangle, he says "Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)" which I don't understand. How can I find a kernel, all I have are ROMs which as I understand it do not include the kernel.
Nitsson said:
Ok, so neither pda, phone or scs constitute the kernel? I appreciate that custom ROMs incorporate the official (and sometimes the unofficial) Samsung releases meaning I don't need to faff around with Kies, but CF-Root handles only the kernel if understand it correctly.
In Chainfire's guide on rooting, specifically the but on getting rid of the warning triangle, he says "Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)" which I don't understand. How can I find a kernel, all I have are ROMs which as I understand it do not include the kernel.
Click to expand...
Click to collapse
here is all the roms and kernels
if you read closely under each rom their is also a link for kernels.
http://forum.xda-developers.com/showthread.php?t=1075278
Nitsson said:
Ok, so neither pda, phone or scs constitute the kernel? I appreciate that custom ROMs incorporate the official (and sometimes the unofficial) Samsung releases meaning I don't need to faff around with Kies, but CF-Root handles only the kernel if understand it correctly.
In Chainfire's guide on rooting, specifically the but on getting rid of the warning triangle, he says "Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)" which I don't understand. How can I find a kernel, all I have are ROMs which as I understand it do not include the kernel.
Click to expand...
Click to collapse
Kernel is a (small) part of PDA. So flash PDA replaces the kernel. But you can flash kernel separately without changing the other parts of PDA.
Sent from my GT-I9100 using Tapatalk
zabihjan said:
here is all the roms and kernels
if you read closely under each rom their is also a link for kernels.
http://forum.xda-developers.com/showthread.php?t=1075278
Click to expand...
Click to collapse
tjtj4444 said:
Kernel is a (small) part of PDA. So flash PDA replaces the kernel. But you can flash kernel separately without changing the other parts of PDA.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Great, thanks. So if I flash a custom ROM based on KG2, do I need to flash the ROM first followed by CF-Root? I imagine that if I flash CF-Root first and then the customer ROM via CWM, this will overwrite portions of CF-Root which is needed for CWM etc.
Nitsson said:
Great, thanks. So if I flash a custom ROM based on KG2, do I need to flash the ROM first followed by CF-Root? I imagine that if I flash CF-Root first and then the customer ROM via CWM, this will overwrite portions of CF-Root which is needed for CWM etc.
Click to expand...
Click to collapse
CF-Root (flashed through Odin) is the 1st step in running a custom rom. The kernel will replace the stock samsung recovery with the clockworkmod recovery which is then used to flash custom ROMs
Custom ROMs may replace the CF-Root kernel but no responsible dev would include a kernel that removes the CWM recovery so you do not need to worry about overwriting it.
On a side note, in an original full stock rom (in tar format) the zImage file within the tar is the kernel, if you wanted to flash the original kernel back then you would remove all the other files from the tar (and leave zImage) and flash the tar in Odin as PDA.. although this wouldn't be a great idea as it would remove the custom CWM recovery
About point 3 - flashing a rom is the 'update'. Forget about KIES when you start flashing your roms, because all of the software is in there, the rom itself.
viva.fidel said:
CF-Root (flashed through Odin) is the 1st step in running a custom rom. The kernel will replace the stock samsung recovery with the clockworkmod recovery which is then used to flash custom ROMs
Custom ROMs may replace the CF-Root kernel but no responsible dev would include a kernel that removes the CWM recovery so you do not need to worry about overwriting it.
Click to expand...
Click to collapse
viva.fidel said:
On a side note, in an original full stock rom (in tar format) the zImage file within the tar is the kernel, if you wanted to flash the original kernel back then you would remove all the other files from the tar (and leave zImage) and flash the tar in Odin as PDA.. although this wouldn't be a great idea as it would remove the custom CWM recovery
Click to expand...
Click to collapse
Excellent, I get that part. Good explanation.
How about the order of flashing; the custom ROM I want to try is based on KG3, and I also want to flash the updated CF-Root v.4.1 KG3 kernel followed by the stock Samsung kernel to rid myself of that warning triangle (any future flashing I will do through CWM and not Odin). Should I install the custom ROM via my current version of recovery, then, upgrade CF-Root via the patched KG3 kernel, and finally flash the stock Samsung KG3 kernel?
Since I'm using KE2 at the moment, I'm thinking that flashing just a KG3 kernel to get CF-Root 4.1 isn't a best idea, as the KE2 firmware overall might not be compatible with a KG3 kernel.
Custom rom has to be installed as per each developers instructions for each individual rom .Not all are CWM flashable .
Personnel i would upgrade the CF root to the later verion before rthe custom rom but i would also read the details of the rom has it may have the latest CWM installed .
jje
Nitsson said:
Excellent, I get that part. Good explanation.
How about the order of flashing; the custom ROM I want to try is based on KG3, and I also want to flash the updated CF-Root v.4.1 KG3 kernel followed by the stock Samsung kernel to rid myself of that warning triangle (any future flashing I will do through CWM and not Odin). Should I install the custom ROM via my current version of recovery, then, upgrade CF-Root via the patched KG3 kernel, and finally flash the stock Samsung KG3 kernel?
Since I'm using KE2 at the moment, I'm thinking that flashing just a KG3 kernel to get CF-Root 4.1 isn't a best idea, as the KE2 firmware overall might not be compatible with a KG3 kernel.
Click to expand...
Click to collapse
which rom are you trying to flash? If it needs to be flashed through cwm then you'll have to flash a custom kernel through odin first to give you cwm recovery (custom rom can't be flashed with the stock samsung recovery), then flash the rom in cwm. Does the rom include cf-root? If it doesn't then flash the cf-root kernel and then the stock kernel to get rid of the triangle
If the rom can be flashed through odin then you can skip flashing the initial cwm-enabling ke2 kernel
Sent from my GT-I9100 using XDA App
JJEgan said:
Custom rom has to be installed as per each developers instructions for each individual rom .Not all are CWM flashable .
Personnel i would upgrade the CF root to the later verion before rthe custom rom but i would also read the details of the rom has it may have the latest CWM installed .
Click to expand...
Click to collapse
Ok thanks. I also think that I should install the latest version of CF-Root first.
viva.fidel said:
which rom are you trying to flash? If it needs to be flashed through cwm then you'll have to flash a custom kernel through odin first to give you cwm recovery (custom rom can't be flashed with the stock samsung recovery), then flash the rom in cwm. Does the rom include cf-root? If it doesn't then flash the cf-root kernel and then the stock kernel to get rid of the triangle
If the rom can be flashed through odin then you can skip flashing the initial cwm-enabling ke2 kernel
Click to expand...
Click to collapse
It's the Batista 3.2 ROM that I intend to flash. I already have CF-Root / recovery installed, and this ROM also installs recovery v4.0.1.4, but what I don't know if this is the same as the recovery included in CF-Root - most likely not.
I'll probably go ahead and will flash the custom CF-Root KG3 kernel and the stock KG3 kernel via Odin to get rid of the triangle, and finally the ROM via recovery. That should do it.
Should be pinned. This was exactly was I wanted to know and maybe many others too.
Nitsson said:
It's the Batista 3.2 ROM that I intend to flash. I already have CF-Root / recovery installed, and this ROM also installs recovery v4.0.1.4, but what I don't know if this is the same as the recovery included in CF-Root - most likely not.
I'll probably go ahead and will flash the custom CF-Root KG3 kernel and the stock KG3 kernel via Odin to get rid of the triangle, and finally the ROM via recovery. That should do it.
Click to expand...
Click to collapse
Think CF-Root comes with CWM 4.0.0.2
Looks like Batista's ROM includes a kernel.. you should therefore flash the ROM first, then CF-Root (so it overwrites the ROM kernel) and then the stock samsung-signed KG3 kernel
viva.fidel said:
Think CF-Root comes with CWM 4.0.0.2
Looks like Batista's ROM includes a kernel.. you should therefore flash the ROM first, then CF-Root (so it overwrites the ROM kernel) and then the stock samsung-signed KG3 kernel
Click to expand...
Click to collapse
I did exactly that Just flashed the CF-Root kernel via the CWM app at the end to have all the goodies. Works a treat so far but I'll see over the coming weeks.
Hello,
I am currently running GINGERBREAD.BVKL1, 2.6.35.7-I9100BVKL1-CL774645 and want to reflash kernel using CF-ROOT.
I am reading Chainfire's thread, and at this post I can find the closest match to my kernel being CF-Root-SGS2_XW_INU_KL1-v5.0-CWM5.zip.
Chainfire also mentions: KL1 (GB): Untested
I'm wondering if this is still the case, considering that this was posted on the 30th of May 2011.
So anyone out there running CF-ROOT KL1?
Yup, I was asking myself the same question because I used Kies to update to 2.6.35.7 BVKL1 and lost root. Obviously zergrush failed and i checked for insecure or rooted kernels. However I don't think the KL1 (GB) has anything to do with this version.
Any help would be apreciated.
w00tz said:
Hello,
I am currently running GINGERBREAD.BVKL1, 2.6.35.7-I9100BVKL1-CL774645 and want to reflash kernel using CF-ROOT.
I am reading Chainfire's thread, and at this post I can find the closest match to my kernel being CF-Root-SGS2_XW_INU_KL1-v5.0-CWM5.zip.
Chainfire also mentions: KL1 (GB): Untested
I'm wondering if this is still the case, considering that this was posted on the 30th of May 2011.
So anyone out there running CF-ROOT KL1?
Click to expand...
Click to collapse
cerberus1405 said:
Yup, I was asking myself the same question because I used Kies to update to 2.6.35.7 BVKL1 and lost root. Obviously zergrush failed and i checked for insecure or rooted kernels. However I don't think the KL1 (GB) has anything to do with this version.
Any help would be apreciated.
Click to expand...
Click to collapse
Ive been using the XW_INU_KL1 kernel in my phone for a while now with no problems at all.The kernel is now well and trully tested and is even included in my ROM.If it wasnt fully tested the dev wouldnt have put it in there so its perfectly safe to flash.As far as if its the correct kernel or not you only have to read the thread by Chainfire.As with any kernel the most important part are the last 3 digits.If your kernel ends in KL1 then its the correct one to use.
EDIT:Just thought Id let you know that my root kernel (XWKL1) is also 2.6.35.7 so the fact that you have "BV" doesnt matter.
cooza said:
Ive been using the XW_INU_KL1 kernel in my phone for a while now with no problems at all.The kernel is now well and trully tested and is even included in my ROM.If it wasnt fully tested the dev wouldnt have put it in there so its perfectly safe to flash.As far as if its the correct kernel or not you only have to read the thread by Chainfire.As with any kernel the most important part are the last 3 digits.If your kernel ends in KL1 then its the correct one to use.
EDIT:Just thought Id let you know that my root kernel (XWKL1) is also 2.6.35.7 so the fact that you have "BV" doesnt matter.
Click to expand...
Click to collapse
Great, thanks for the info! Will be reflashing today.
First, Thanks again cooza.
w00tz, for your info,
I have flashed XW_INU_KL1 kernel via Odin (because I didn't have CWM Manager) and installed superuser and busybox thus gaining root.
Then reflashed "original" 2.6.35.7-I9100BVKL1-CL774645 from intratech:
http://forum.xda-developers.com/showthread.php?t=1113928&highlight=bvkl1
Now running "official" kernel with root.
cerberus1405 said:
First, Thanks again cooza.
w00tz, for your info,
I have flashed XW_INU_KL1 kernel via Odin (because I didn't have CWM Manager) and installed superuser and busybox thus gaining root.
Then reflashed "original" 2.6.35.7-I9100BVKL1-CL774645 from intratech:
http://forum.xda-developers.com/showthread.php?t=1113928&highlight=bvkl1
Now running "official" kernel with root.
Click to expand...
Click to collapse
Thanks for sharing! Just reflashed minutes ago using XW_INU_KL1 also via Odin, gained root without problems and then unlocked my carrier block via Helroz's Galaxy S Unlock. Everything went smoothly.
I'm downloading now the 'original' stuff, it's good to have.
Is there any certain reason to reflash the 'original'? Besides getting rid of the yellow triangle. I'm guessing that KIES upgrades will also work with XW_INU_KL1. And I'm under the impression that my phone is a little bit faster with this kernel.
Good to see everything went well.Downloading the original stuff is just personal choice.You can flash any firmware you want,test it,change it,flash carrier branded and non carrier branded firmwares until you find what you like as each different firmware has a different modem.Good idea to get rid of the triangle if you dont have a usb jig just in case you want to send it away.Your new original F/W will have the modem being used in your area for best speed and conectivity so if you can be rooted on that F/W then better still.Kies will still work but the updates will only work on your BV rooted version.
Roger that. Thank you again, much appreciate it.
cerberus1405 said:
First, Thanks again cooza.
w00tz, for your info,
I have flashed XW_INU_KL1 kernel via Odin (because I didn't have CWM Manager) and installed superuser and busybox thus gaining root.
Then reflashed "original" 2.6.35.7-I9100BVKL1-CL774645 from intratech:
http://forum.xda-developers.com/showthread.php?t=1113928&highlight=bvkl1
Now running "official" kernel with root.
Click to expand...
Click to collapse
Just a little revive.
Because it has been reported to me that sometimes I cannot be heard by the other person while talking, I have decided to also flash the original kernel from intratech. From what I understand, Firmware and Kernel should have matching versions.
I wanted to ask you if:
1. you reflashed from CWM or via Download mode?
2. do you still have CWM after reflashing this stock kernel?
Thanks.
Friendly bump. I tried to contact cerberus1405 but haven't had success.
So if anybody else can answer my questions. It doesn't matter if it's about KL1 kernel or another one.
I guess you didn't manage to search in the past week then? Kernel is unlikely to have any impact on call quality, only modem.
1). If you want to flash a stock kernel, you can do it several ways and there's no difference in outcome.
2). No, if you flash a stock kernel, you will lose CWM recovery.
If those are not the questions you wanted asking then you'll have to be more specific.
w00tz said:
Friendly bump. I tried to contact cerberus1405 but haven't had success.
So if anybody else can answer my questions. It doesn't matter if it's about KL1 kernel or another one.
Click to expand...
Click to collapse
What's your question, more specified?
w00tz said:
Just a little revive.
Because it has been reported to me that sometimes I cannot be heard by the other person while talking, I have decided to also flash the original kernel from intratech. From what I understand, Firmware and Kernel should have matching versions.
I wanted to ask you if:
1. you reflashed from CWM or via Download mode?
2. do you still have CWM after reflashing this stock kernel?
Thanks.
Click to expand...
Click to collapse
sorry, didn't log in lately. I flashed via Download mode.
usualy CWM works with CF-Root kernels. In my case CWM detected that I was running a different kernel and warned me about some features disabled. The app appears functional but haven't tried it yet.
Hy there, i have BVKL1 on my s2 and if i understand what is written here i can use
XWKL1 insecure to flash ?
Is that correct, sry if i bother u i'm kinda noob on this ...
Thx.
R3d_Wolf said:
Hy there, i have BVKL1 on my s2 and if i understand what is written here i can use
XWKL1 insecure to flash ?
Is that correct, sry if i bother u i'm kinda noob on this ...
Thx.
Click to expand...
Click to collapse
KL1 yes
Best root method is .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
I was thinking to use odin + ClockworkMod-Recovery. This method it's not ok ?
Thank you for your answer.
Hi,
I used Odin and CF-Root XW_KL1 kernel.
I have kept these links http://forum.xda-developers.com/showthread.php?t=788108 and http://forum.xda-developers.com/showthread.php?t=1103399, try to find a matching kernel there.
This method incremented the flash counter to 1 (and when I boot the phone I get the warning triangle), but I don't quite really care anymore about it.
It's been a while since I flashed and I can say that it is stable.
I have a usb jig so hopefully no triangle and counter 0.
Thx
Hey everyone
A little while ago I jumped on the ICS bandwagon and flashed my villainrom 2.5-toting Optus i9100 to WanamLite 8.9, via CWM Recovery.
its been buggy as hell and the phone has turned to garbage ever since, with random freezing, touch input not responding, et cetera.
my question is - should i have flashed to one of the leaked samsung ICS ROMs via ODIN before updating to wanamlite via CWM Recovery?
i remember back in the SGS days, when moving from 2.1/2.2 to 2.3, you had to flash a generic 2.3 ROM via ODIN before you could flash a custom one. flashing a gingerbread darky's ROM over a froyo custom ROM directly using CWM caused all kinds of problems.
now that the official Samsung XXLPQ ICS is out, i want to flash to a pre-rooted version of it with CF-Root kernel (the ones that wanam himself has uploaded). but should i flash via ODIN to an official ICS first, and then root + flash the wanam custom version, just like i had to do when going from 2.2 to 2.3 on my original SGS?
sschrapel said:
Hey everyone
A little while ago I jumped on the ICS bandwagon and flashed my villainrom 2.5-toting Optus i9100 to WanamLite 8.9, via CWM Recovery.
its been buggy as hell and the phone has turned to garbage ever since, with random freezing, touch input not responding, et cetera.
my question is - should i have flashed to one of the leaked samsung ICS ROMs via ODIN before updating to wanamlite via CWM Recovery?
i remember back in the SGS days, when moving from 2.1/2.2 to 2.3, you had to flash a generic 2.3 ROM via ODIN before you could flash a custom one. flashing a gingerbread darky's ROM over a froyo custom ROM directly using CWM caused all kinds of problems.
now that the official Samsung XXLPQ ICS is out, i want to flash to a pre-rooted version of it with CF-Root kernel (the ones that wanam himself has uploaded). but should i flash via ODIN to an official ICS first, and then root + flash the wanam custom version, just like i had to do when going from 2.2 to 2.3 on my original SGS?
Click to expand...
Click to collapse
I flashed stock jpq then moved on. My phone is fine
Sent from my GT-I9100 using Tapatalk
If i helped please consider clicking yes,thats what my dog always wanted ! Sent from under my bed
Sorry for the previous post i clicked it while it ways empty by wrong
Just get ur phone into download mode and flash the stock jpq
After that do wipe cache and factory and ull be good to go
isn't the problem with doing that the fact that the bootloader will be upgraded as well, meaning i can't reset the flash counter with my USB jig anymore?
my question is - should i have flashed to one of the leaked samsung ICS ROMs via ODIN before updating to wanamlite via CWM Recovery?
Not really needed .
But this is what i always do with any major upgrade or new custom rom .
titanium backup and nandroid backup
Wipe.format system data cache .
Install stock rom of same version
Root with CWM and Root kernel.
Flash new rom .
result no problems .
jje
Restore backed up apps .
I have the following Galaxy s2:
PDA: XXKH3| Modem/phone: XXKH3| CSC: OXAKH3
Rooted and Siyah Kernel.
I was wondering if there is a way to get ICS update through Samsung Kies (when I plug the phone in it keeps telling me it's up to date)?
I want to keep all my setting and data.
I know it's possible to do it through Odin but all my apps and data will be erased
If there is no way to update using Kies what is the best/latest stock ICS firmware available now? Which one will get the latest updates first?
you can backup your apps and data using Titanium backup and flash a Custom ICS rom from CWM
latest stock is XWLP9 and reported very stable...you can get it from here Rooted and CWM flashable : http://forum.xda-developers.com/showthread.php?t=1292825
don't really want to keep backing up the app every time there is an update. I just want to go back to stock...
ZACQ8 said:
you can backup your apps and data using Titanium backup and flash a Custom ICS rom from CWM
latest stock is XWLP9 and reported very stable...you can get it from here Rooted and CWM flashable : http://forum.xda-developers.com/showthread.php?t=1292825
Click to expand...
Click to collapse
Make it dxlp9
Xwlp9 (xen) is buggy, sleep of death and other issues...
atifsh said:
Make it dxlp9
Xwlp9 (xen) is buggy, sleep of death and other issues...
Click to expand...
Click to collapse
I have been using XWLP9 (problem might be fixed by dev of my cureent Custom ROM) for one week without a single issue of ROM except some signal issues with the Modem lp6, i changed my old modem KE7 and problem fixed...
only language pack change in XWLP9 and DXLP9...
http://forum.xda-developers.com/showpost.php?p=26016162&postcount=2010
ZACQ8 said:
I have been using XWLP9 (problem might be fixed by dev of my cureent Custom ROM) for one week without a single issue of ROM except some signal issues with the Modem lp6, i changed my old modem KE7 and problem fixed...
http://forum.xda-developers.com/showpost.php?p=26016162&postcount=2010
Click to expand...
Click to collapse
You answered it your self, custom ROM......
Stock is buggy. Dxlp9 is good
I kind of want to go completely stock as I mentioned so when new version of Android comes out I can just update using Kies. Don't really want to deal with all backup and restores.
FYI, there is no guarantee a Kies update won't screw up either though. Always a good idea to back up before an upgrade, be it a Kies update, or an Odin flash. And if you're going from stock to stock with an Odin flash, that won't wipe your phone anyways. (still a good idea to wipe anyways, though...)
Hi,
I recently bought Samsung Galaxy S II I9100 on ebay. After receiving it I realized that it has a custom ROM installed on it. Now I cannot update my Galaxy SII using Kies. So, I decided why not flash it to stock ICS firmware.
as fas as I understand I need to flash my phone using ODIN with a stock ICS firmware (I choose the first one from Nordic countries from http://forum.xda-developers.com/showthread.php?t=1544487 ).
Now what if I think of rooting it ? I mean I want to unlock super user privileges. As far as I understand I choose SiyahKernel v3.2.7.2 (from http://www.gokhanmoral.com/gm/). Just like the way I flashed using ODIN. I repeat it with this .tar file from SiyahKernel v3.2.7.2. Is that it ?
Can anyone verify it ?
Yes, but you should flash CF-Root kernel first (after flashing stock ROM).
If not satisfied with this, then you can try Siyah...
thanks for your reply. What is the difference between Chain Fire and Siyah ? I tried to look for differences ... couldn't find any .. CyanogenMod has a lot of documentation... in fact it is kinda scary (with some of its security problems)..
satish1986 said:
thanks for your reply. What is the difference between Chain Fire and Siyah ? I tried to look for differences ... couldn't find any .. CyanogenMod has a lot of documentation... in fact it is kinda scary (with some of its security problems)..
Click to expand...
Click to collapse
hey ma8 first try to understand everything about root and recovery then try to implement the same
ps- also for rooting ur phone after flashing stock ics rom please check the link below
http://forum.xda-developers.com/showthread.php?p=20075898#post20075898
There is almost no visible diffrences between kernels. at least in normal mode.(siyah has its own CWM, way better than other CWM versions).
Siyah Kernel eliminates some of logging processes and unusefull procedures of android, so it gives you better battery life. specially in idle mode.(about 1 percent for 7-8 hour) and I feel CF-kernels are more battery consuming than stock kernels.
Also Siyah gives you advanced control over hardware, and has a dual boot option.(two different ROM of same version. both ICS or both GB). for best results you should download EX Tweaks from market.
satish1986 said:
thanks for your reply. What is the difference between Chain Fire and Siyah ? I tried to look for differences ... couldn't find any .. CyanogenMod has a lot of documentation... in fact it is kinda scary (with some of its security problems)..
Click to expand...
Click to collapse
CF-Root kernel from Chainfire is only a rooted stock kernel with a few extras (such as SuperSU, BusyBox, CWM recovery, CWM Manager app, etc.).
Have a look at CF-Root thread for detailed information => http://forum.xda-developers.com/showthread.php?t=1103399&highlight=CF+Root
SiyahKernel from gokhanmoral is completely different, as it is a custom kernel with a lot of patched, parts from other kernels/linux sources/other phones/individually developed code/etc.
See corresponding thread for further information => http://forum.xda-developers.com/showthread.php?t=1555259
If you want to stay "stock" but rooted, then flash the corresponding CF-Root kernel for your stock ROM.
Happy flashing !
P.S.: Use TriangleAway app from Chainfire to remove the yellow triangle and reset the counter after flashing an insecure kernel, such as CF-Root or Siyah.
And as soon as your phone is rooted, you can use Mobile Odin app from Chainfire to flash stock ROMs, kernels and other part of the firmware with an on-device app - without the yellow triangle and without increasing the counter.
CF kernels are STOCK kernels, only with root access.
Syiah, Speedmod and others are developed as new kernels with special properties - adjustable voltage and over- under- clocking... also there is a greater risk of them being unstable
all of this makes me scared .. but, I want to take that leap ... sounds geeky to me..
As long as you understand the process of whatever you're going to do to your phone & follow instructions to the letter you should be fine.
If you don't understand exactly what it is you're going to do to your phone, don't do anything until you do.