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.
Im new to the whole SGS2 so needed a little help ive rooted my Galaxy and its on UK 2.3.5 stock rom my question is can i flash any rom i choose or is it like when rooting it when i had to get a kernel that matched.
The other thing is, is it worth buying Odin Mobile.
Cheers
Once you root your phone and have CWM recovery and not the stock one you can flash any ROM you choose.It has nothing to do with kernels but each ROM is based on a firmware so you should match your firmware to a ROM based on the same to start with and if you choose to stay with the same ROM then there are non-wipe ROMs that can be flashed over top without worries.Just be sure you read properly the install/flash instructions.Some ROMs need Odin to be flashed but most just need to be pasted to your internal-SD and then flashed in recovery mode.Ill leave a link below to my ROM where there is an instruction guide so you can read it to see what I mean.
http://forum.xda-developers.com/showthread.php?t=1290468
polly69 said:
Im new to the whole SGS2 so needed a little help ive rooted my Galaxy and its on UK 2.3.5 stock rom my question is can i flash any rom i choose or is it like when rooting it when i had to get a kernel that matched.
The other thing is, is it worth buying Odin Mobile.
Cheers
Click to expand...
Click to collapse
It depends on how you have rooted ...... if as mentioned above you have CWM (means you have flashed a custom/insecure stock kernel) just flash a ROM with CWM Recovery like any ZIP but i'd advise you to reset the phone before that .... since you are on Stock ROM which is Odexed and all custom ROMs are deodexed you might end up in a bootloop also may i suggest CheckROM as it is simple to install and highly customizable thus i recommend this as your first flash......
checkrom thread:
http://goo.gl/eRCJt
else i use this site it's pretty awesome to keep track of things
http://goo.gl/ihgse
Cheers to both of you, i think i will give checkrom ago as theres that many to choose from and im new to the rooted SGS2.
Hi S2 user, :angel:
I will buy a new S2 phone soon. I need a little help from you guys. I need to know something about S2 :laugh:
My old phone is Xperia Arc S. This phone need following step to flash kernel and rom.
Kernel:
For flash a new kernel, I need to unlocked the bootloader first. Then this phone can flash any kernel anytime. But unlocking the bootloader will void the warranty.
Rom:
For flash a new rom, as long as the rom does not need to have specific kernel, in other word, stock based rom, no unlocked bootloader required. Just install the CWM and flash the rom.
How about S2 guys? Do I need to unlock something before flash kernel and rom? Can someone explain clearly or likes how I explain my old phone.
p/s- i read in some thread, doing a factory reset in cwm will make S2 brick? hard brick? can't even power on the phone. OMG is it true?
its very scary because in Xperia Arc S, i always flash a new rom. flasholic
I don't want my new S2 brick
I hope you guys can help me. Thanks
faiz5200 said:
Hi S2 user, :angel:
I will buy a new S2 phone soon. I need a little help from you guys. I need to know something about S2 :laugh:
My old phone is Xperia Arc S. This phone need following step to flash kernel and rom.
Kernel:
For flash a new kernel, I need to unlocked the bootloader first. Then this phone can flash any kernel anytime. But unlocking the bootloader will void the warranty.
Rom:
For flash a new rom, as long as the rom does not need to have specific kernel, in other word, stock based rom, no unlocked bootloader required. Just install the CWM and flash the rom.
How about S2 guys? Do I need to unlock something before flash kernel and rom? Can someone explain clearly or likes how I explain my old phone.
p/s- i read in some thread, doing a factory reset in cwm will make S2 brick? hard brick? can't even power on the phone. OMG is it true?
its very scary because in Xperia Arc S, i always flash a new rom. flasholic
I don't want my new S2 brick
I hope you guys can help me. Thanks
Click to expand...
Click to collapse
You don't have to unlock. Just download Odin and flash all the ROMs/kernels you want. As for the cwm brick bug, your phone will only brick if you factory reset through CWM in 4.0.4. In other versions you should be fine.
Sent from my GT-I9100 using xda app-developers app
S2 is the best phone to flash No problem with bootloader lock, you download Odin und happy flashing
Gesendet von meinem GT-I9100 mit Tapatalk 2
preseodymium said:
You don't have to unlock. Just download Odin and flash all the ROMs/kernels you want. As for the cwm brick bug, your phone will only brick if you factory reset through CWM in 4.0.4. In other versions you should be fine.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. For the brick bug, how come I want to factory reset when flashing new rom? And I think latest firmware for S2 is 4.0.4. Correct me if im wrong.
faiz5200 said:
Thanks for your reply. For the brick bug, how come I want to factory reset when flashing new rom? And I think latest firmware for S2 is 4.0.4. Correct me if im wrong.
Click to expand...
Click to collapse
I am currently installing 4.1.2, unofficial of course
The brick Bug problem by 4.0.4 only with Stock Kernel ! when you have 4.0.4 on your phone you flash a save Kernel (Siyah, Dorimanax .....) with Odin (only Odin not Cwm )
and it was save .After you can flash wath you want
smooth 123 said:
The brick Bug problem by 4.0.4 only with Stock Kernel ! when you have 4.0.4 on your phone you flash a save Kernel (Siyah, Dorimanax .....) with Odin (only Odin not Cwm )
and it was save .After you can flash wath you want
Click to expand...
Click to collapse
I see. So the brick bug actually come from the kernel inside firmware 4.0.4. Not the entire 4.0.4 firmware. Is other custom kernel likes you mention (Siyah, ..) is 100% safe?
faiz5200 said:
I see. So the brick bug actually come from the kernel inside firmware 4.0.4. Not the entire 4.0.4 firmware. Is other custom kernel likes you mention (Siyah, ..) is 100% safe?
Click to expand...
Click to collapse
enjoy ur s2, i just got the s2 and flash over 20 roms like crazy!! jajaja is very good phone
faiz5200 said:
I see. So the brick bug actually come from the kernel inside firmware 4.0.4. Not the entire 4.0.4 firmware. Is other custom kernel likes you mention (Siyah, ..) is 100% safe?
Click to expand...
Click to collapse
100% safe! Her is ohter 100% safe Kernel http://forum.xda-developers.com/showthread.php?t=1877270
for 4.0.4 Stock In this thread you found more to the theme brick bug.
I flash my S2 i don t know:victory: 100× no Problem S2 likes flashing
faiz5200 said:
Thanks for your reply. For the brick bug, how come I want to factory reset when flashing new rom? And I think latest firmware for S2 is 4.0.4. Correct me if im wrong.
Click to expand...
Click to collapse
You factory reset when installing ROMs to make sure there are no errors. Plus with siyah kernels, you can't be 100% sure your phone won't brick when factory reset in CWM. Best is to flash 4.0.3 before doing anything else.
Sent from my GT-I9100 using xda app-developers app
Rooting
Guys.. 1 more question.
When I get my S2, I plan to flash custom rom like aosp or aokp but not stock rom.
Do I need to root my S2 first before flash any rom? Because my Xperia Arc S, I do not need to root because root come inside with the custom rom zip. So when I flash a new rom, my Xperia automatically root. No need to do other step.
I'm curious about this because I see in some thread, talking about cf root or something like that. The thread is very updated. Looks like it very necessary to do it at least once to have root before flash any custom rom.
Please explain for me about this root. Thanks guys.
faiz5200 said:
Guys.. 1 more question.
When I get my S2, I plan to flash custom rom like aosp or aokp but not stock rom.
Do I need to root my S2 first before flash any rom? Because my Xperia Arc S, I do not need to root because root come inside with the custom rom zip. So when I flash a new rom, my Xperia automatically root. No need to do other step.
I'm curious about this because I see in some thread, talking about cf root or something like that. The thread is very updated. Looks like it very necessary to do it at least once to have root before flash any custom rom.
Please explain for me about this root. Thanks guys.
Click to expand...
Click to collapse
I'm not sure about CF root though. Although the ROM I am in now has built in kernels, I still think its best to root first as some ROMs may not have the built in kernel (never searched other ROMs not entirely sure). I might recomment siyah kernel though
Sent from my GT-I9100 using xda app-developers app
preseodymium said:
I'm not sure about CF root though. Although the ROM I am in now has built in kernels, I still think its best to root first as some ROMs may not have the built in kernel (never searched other ROMs not entirely sure). I might recomment siyah kernel though
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
uhh.. So root is come from kernel? Ermm.. so it different than xperia. So if I flash siyah kernel, I do not need to root?
faiz5200 said:
Guys.. 1 more question.
When I get my S2, I plan to flash custom rom like aosp or aokp but not stock rom.
Do I need to root my S2 first before flash any rom? Because my Xperia Arc S, I do not need to root because root come inside with the custom rom zip. So when I flash a new rom, my Xperia automatically root. No need to do other step.
I'm curious about this because I see in some thread, talking about cf root or something like that. The thread is very updated. Looks like it very necessary to do it at least once to have root before flash any custom rom.
Please explain for me about this root. Thanks guys.
Click to expand...
Click to collapse
Some people want to simple root their phone and don't care too much for custom roms and stuff. So for such people, they can simply root their phone using one of the many rooting methods mentioned.
However, if your primary aim is to install a custom rom/ kernel, you can use Odin to flash a custom kernel on your phone. (like siyah, dorimanx, Philz, the list goes on..) and you'll have root. Thereafter you can install a custom rom compatible with the kernel. Earlier on it was simple. Flash siyah or dorimanx and any custom rom will work on it. Kinda like a 'one size fits all' deal. However, right now with new mali drivers etc, some versions of a kernel are reqd based on which rom you plan to install. (JB with new mali drivers or JB without those new mali drivers/ICS)
CF-Root is the method I'd used..but right now it's not recommended, since if you're on certain 4.0.4 firmware, that is susceptible to the emmc brickbug I'm sure you've read about. Siyah, dori, etc kernels are safe.
HAXTREME said:
Some people want to simple root their phone and don't care too much for custom roms and stuff. So for such people, they can simply root their phone using one of the many rooting methods mentioned.
However, if your primary aim is to install a custom rom/ kernel, you can use Odin to flash a custom kernel on your phone. (like siyah, dorimanx, Philz, the list goes on..) and you'll have root. Thereafter you can install a custom rom compatible with the kernel. Earlier on it was simple. Flash siyah or dorimanx and any custom rom will work on it. Kinda like a 'one size fits all' deal. However, right now with new mali drivers etc, some versions of a kernel are reqd based on which rom you plan to install. (JB with new mali drivers or JB without those new mali drivers/ICS)
CF-Root is the method I'd used..but right now it's not recommended, since if you're on certain 4.0.4 firmware, that is susceptible to the emmc brickbug I'm sure you've read about. Siyah, dori, etc kernels are safe.
Click to expand...
Click to collapse
I see. Thanks. Flash kernel using odin. I see in this thread http://forum.xda-developers.com/showthread.php?t=1125282 , he said flashing a kernel is same like flashing a custom rom which is in CWM. Flash kernel in CWM? I thought the only way is using odin.
faiz5200 said:
I see. Thanks. Flash kernel using odin. I see in this thread http://forum.xda-developers.com/showthread.php?t=1125282 , he said flashing a kernel is same like flashing a custom rom which is in CWM. Flash kernel in CWM? I thought the only way is using odin.
Click to expand...
Click to collapse
For S2 we can. Because it won't increase your flash counter. But I never tried flashing through CWM.
Sent from my GT-I9100 using xda app-developers app
faiz5200 said:
I see. Thanks. Flash kernel using odin. I see in this thread http://forum.xda-developers.com/showthread.php?t=1125282 , he said flashing a kernel is same like flashing a custom rom which is in CWM. Flash kernel in CWM? I thought the only way is using odin.
Click to expand...
Click to collapse
There are two ways of flashing a kernel.
1. Use the .tar version of the kernel and flash via Odin
(the same way you'd flash the cf-root kernel you'd mentioned in a post above. I'll assume you know the steps as they're mentioned in chainfire's post. Or there are many posts on that topic)
Advantages: tried and tested route, simple one step method. You're rooted and have a custom kernel in about 30 secs.
Disadvantage: You rely on Odin and the connection to your computer which some don't trust. Increases flash counter.
2. Use the .zip version of the kernel and flash via CWM.
Since in this case you need CWM to start off with, you can use Rachmat3's method described HERE to get temporary CWM first.
Advantages: No computer needed. Everything happens through your phone. Flash counter isnt increased.
Disadvantages: Can be a little finicky at times..but you'll get there eventually. Involves 2 steps. First get temporary CWM, then install custom kernel via cwm.
You can start off with a very popular kernel. Gokhanmoral's siyah kernel.Both the zip and tar versions are available downloadable from HERE
HAXTREME said:
There are two ways of flashing a kernel.
1. Use the .tar version of the kernel and flash via Odin
(the same way you'd flash the cf-root kernel you'd mentioned in a post above. I'll assume you know the steps as they're mentioned in chainfire's post. Or there are many posts on that topic)
Advantages: tried and tested route, simple one step method. You're rooted and have a custom kernel in about 30 secs.
Disadvantage: You rely on Odin and the connection to your computer which some don't trust. Increases flash counter.
2. Use the .zip version of the kernel and flash via CWM.
Since in this case you need CWM to start off with, you can use Rachmat3's method described HERE to get temporary CWM first.
Advantages: No computer needed. Everything happens through your phone. Flash counter isnt increased.
Disadvantages: Can be a little finicky at times..but you'll get there eventually. Involves 2 steps. First get temporary CWM, then install custom kernel via cwm.
You can start off with a very popular kernel. Gokhanmoral's siyah kernel.Both the zip and tar versions are available downloadable from HERE
Click to expand...
Click to collapse
Another disadvantage of "not using" odin is when you cant enter cwm.
I use cwm and mobile odin.I flashed a kernel and couldnt access cwm nor phone would boot.
So I had to fix it using my pc via odin.
guys im new here on galaxy s2 thread so kindly do not judge me if i ask noob things
i want to flash AOKP for galaxy s2 and i found 2 of them Revolt and thunder roms
download both + dorimanx kernel placed on SD going into CWM trying to flash kernel and rom but im getting this message :
E:signature verification failed !!
Like just about everything else on here, 'E:signature verification failed !!' has been covered many many times on here (Including a couple of times over the past few weeks). Search for those threads, your answer will be in one of them.
i think i have the stock recovery !!
flashing this Cf-root throw odin will give me the CWM ??
Having stock recovery would explain your problem. If you flash the correct CFRoot kernel via Odin, yes, you will have a rooted phone + CWM. However, many people prefer to simply flash the Odin version of a custom kernel (like Siyah) to achieve this aim these days (Given the issues with 4.0.4 stock kernels, which CFRoot is, and the brickbug). Find the relevant Odin flashable version of Siyah for the Android version you're running; check the Siyah threads for which build is compatible with which version of Android (should be on the first page).
all the Cf-root is ICS and im running JB what i can do in that case ??
all i want to access cwm to flash rom and kernel
This recovery I have
Sent from my LT26i using Tapatalk 2
Which as you said is stock recovery. You can flash temporary versions of CWM from stock recovery, but these only persists until the next reboot/aren't permanent. Make life easy for yourself & flash the Odin version of a rooted kernel as advised in my PP (Use CFRoot if you really want to, just don't do a wipe from CWM while you're running it, wait till you're running a custom kernel before doing any wipes).
Edit - You're welcome, BTW.
MistahBungle said:
Which as you said is stock recovery. You can flash temporary versions of CWM from stock recovery, but these only persists until the next reboot/aren't permanent. Make life easy for yourself & flash the Odin version of a rooted kernel as advised in my PP (Use CFRoot if you really want to, just don't do a wipe from CWM while you're running it, wait till you're running a custom kernel before doing any wipes).
Edit - You're welcome, BTW.
Click to expand...
Click to collapse
ye but the problem cf-root only for ICS and im on JB so if i flash it and then flash JB kernel will do the job or i will stuck !?
sorry if i sound noob but frist time im dealing with Samsung its completly diffrent from Sony
thanks for your help
OK. This is my final post to this thread. I tire very quickly of having to repeat myself.
For the last time...Go to the Siyah threads. Work out which Siyah build you need for the Android version you're running. Get the Odin flashable version of that kernel. Reboot into download mode & flash it with Odin.
Done.
Rooted phone + CWM.
dude sorry but i'v found this
flashing this Siyah-s2-v6.0b4
and now i have cwm and flashed thunder rom
thanks for help and sorry for beeing noob here
Make a nand and efs backup now for future reference.
theunderling said:
Make a nand and efs backup now for future reference.
Click to expand...
Click to collapse
yep this part i know from my Xperia S
Hey guys.
I just bought a samsung tab 2 10.1 and want to flash it to cyanogen to get the multiple users that comes with android 4.2.x
I havent flashed in a while since i updated my i9100 to 4.1.2, so i thought best to flash my i9100 to cyanogen first to try it out as my phone is already rooted. I found a few guides for installing cyanogen to my phone using cwm recovery to install from the SD card.
I remember rooting my device back when i updated it to 4.1.2 but when i tried to boot into cwm is would boot into the stock android recovery.
so i figured i needed to flash cwm recovery.
after checking all kies processes were stopped i flashed the kernel "GT-I9100_ClockworkMod-Recovery_4.0.1.4" , but the phone would not boot and hang at start screen.. as a plus side i now had access to cwm recovery from boot... ironic.
so i booted into cwm recovery thinking to install cyanogen mod as i thought maybe the rom wasn't compatible with the kernel?
but noticed that the cyanogen rom was not present on the menu in cwm recovery, must of put it in the wrong place. I was now thinking to get my phone to boot into 4.1.2 that should still be on the phone, since the current kernel wasn't working i flashed "Siyah-v5-MCM-i9100-vsync_sysfs-20130217" in hopes it would be compatible.. still no luck with it booting. but i still have access to CWM recovery.
Any thoughts on how i should proceed? if i can get cyanogen onto the SD card should i install it via CWM?
little lost at the moment. been a while since i done all this.
here is the information i noted down before i started today.
4.1.2
i9100xxls8
3.0.31-863787 [email protected] #3 smp preempt thu jan 31 12:20:07 kst 2013
JZO54K.I9100xxms1
Thanks for reading.
Serathian
Philz kernel lss flash that through odin. Reboot to recovery, do the wipes and and reboot. 4.1.2 should boot up then. Then move custom rom to int sd and flash away. Philz installs custom cwm. Once you have flash custom rom philz will be replaced with stock custom kernel with cwm built in to it.
andrewwright said:
Philz kernel lss flash that through odin. Reboot to recovery, do the wipes and and reboot. 4.1.2 should boot up then. Then move custom rom to int sd and flash away. Philz installs custom cwm. Once you have flash custom rom philz will be replaced with stock custom kernel with cwm built in to it.
Click to expand...
Click to collapse
I'll give it a shot, is the Philz kernel you mentioned this one?;
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
I'm not to sure what kernel version i need.
how would i find out this information ?
Many thanks.
Edit:
I noticed in my previous notes i made when first flashing my phone a year or so ago. The kernel i used was this;
3.0.15-I9100BGLP8-CL317471 [email protected]#3
It is now kernel version;
3.0.31-863787 [email protected] #3 smp preempt thu jan 31 12:20:07 kst 2013
which has no reference to previous kernels. but my current baseband version is: i9100xxls8
LS8 stands out in both... so would using PhilZ-cwm6-XWLSY-ORA-5.10.0.tar.md5 work on my phone?
Lss will work as it for 4.1.2 it just has newer cwm installed.tar is for odin. You could get the zip one and put on an sd card put bk in your phone and flash it like that. Make sure its zip not tar for flashing in cwm.
Thanks
andrewwright said:
Lss will work as it for 4.1.2 it just has newer cwm installed.tar is for odin. You could get the zip one and put on an sd card put bk in your phone and flash it like that. Make sure its zip not tar for flashing in cwm.
Click to expand...
Click to collapse
Thanks, that worked. opted for no installing the nightly version of cyanogenmod as i would like something more stable on my phone.
I've been looking at Resurrection Remix 3.1.2 or CM1UI Jelly Bean.
Is the Philz kernel i installed a widely compatible kernel or should i install Siyah ? my last attempt to install Siyah kernel lead me to write this post.. how would i go about installing a more widely compatible kernal with out ending up in a hang screen again ?
Kind regards and many thanks.
Serathian
Serathian said:
Is the Philz kernel i installed a widely compatible kernel or should i install Siyah ? my last attempt to install Siyah kernel lead me to write this post..
Click to expand...
Click to collapse
By 'compatible', you mean the kernel works with many ROMs?
Philz is a stock based kernel. So it only works on stock based ROMs, and depends on the android version and the build versions (like LSS, LSJ, LSD etc). Siyah is more compatible, because it only depends on the android version (like JB, ICS or GB).
You had a bootloop before after flashing Siyah mcm kernel, because the mcm kernel supports AOSP 4.2.2 ROMs, not stock JB.
Serathian said:
how would i go about installing a more widely compatible kernal with out ending up in a hang screen again ?
Click to expand...
Click to collapse
To avoid bootloops after flashing a kernel, use these tips:
1. Flash only kernels supported by your current firmware. Suppose you are running stock JB and you want to flash AOSP 4.2.2 ROM. You might be tempted to flash Siyah mcm kernel (because it supports AOSP 4.2.2). But that would end up in a bootloop as Siyah mcm doesn't support stock JB! :good:
2. Use a kernel cleaning script before flashing any kernels. :good:
immortalneo said:
By 'compatible', you mean the kernel works with many ROMs?
Philz is a stock based kernel. So it only works on stock based ROMs, and depends on the android version and the build versions (like LSS, LSJ, LSD etc). Siyah is more compatible, because it only depends on the android version (like JB, ICS or GB).
You had a bootloop before after flashing Siyah mcm kernel, because the mcm kernel supports AOSP 4.2.2 ROMs, not stock JB.
To avoid bootloops after flashing a kernel, use these tips:
1. Flash only kernels supported by your current firmware. Suppose you are running stock JB and you want to flash AOSP 4.2.2 ROM. You might be tempted to flash Siyah mcm kernel (because it supports AOSP 4.2.2). But that would end up in a bootloop as Siyah mcm doesn't support stock JB! :good:
2. Use a kernel cleaning script before flashing any kernels. :good:
Click to expand...
Click to collapse
Thanks for your reply, i have a few questions to try and understand.
Would i be right in saying;
When im looking to install a new kernel and/or Rom. My check list should be;
1. Kernel to phone compatability. I.e my phone is LS8 so i look for LSS/LSY/LSD soforth and so-on.
2. Kernel to Romcompatability. I.e Philz is a stock kernal hence why it works with 4.1.2 stock Rom.
So if i want to install Resurection Remixed i believe its a modified stock Rom so it should work with Philz?
As would cyanogenmod as it is modified stock?
Or is even that modified to much?
If i want to change both kernel and Rom, would it work if i installed for example siyah kernel then boot into CWM recovery and installed from there a new Rom?
Im looking to try out a few roms on my i9100, mainly Reserection remix, and other cyanogenmod clones with light modification as i enjoy the stock android experiance.
Also looking to install cyanogenmod to my p5100 tab. Flashing Philz p5100 kernal and then installing superuser through recovery and then installing cyanogenmod 10 stable version?
thanks for reading and taking the time to anwser my previous questions.
Many thanks
Serathian.
Serathian said:
Would i be right in saying;
When im looking to install a new kernel and/or Rom. My check list should be;
1. Kernel to phone compatability. I.e my phone is LS8 so i look for LSS/LSY/LSD soforth and so-on.
2. Kernel to Romcompatability. I.e Philz is a stock kernal hence why it works with 4.1.2 stock Rom.
So if i want to install Resurection Remixed i believe its a modified stock Rom so it should work with Philz?
As would cyanogenmod as it is modified stock?
Click to expand...
Click to collapse
Don't worry, things can be a bit hard to digest at first.
Let me make it easier:
1. U are currently using a stock or custom ROM, but you want to change the kernel (without any plans to flash a new ROM). In this case, you need to select a kernel that is compatible with your current ROM.
2. U are on a stock ROM, and you need to flash a custom ROM. You want to flash a kernel to root it and install CWM (to enable u to flash a new ROM). In this case also, u should flash a kernel that supports your current stock ROM.
3. U are on a custom ROM, and you want to try another custom ROM (which may require another kernel to support it). In this case, you DON'T need to flash a new kernel that will support ur new ROM. You can flash the new ROM directly. All custom ROMs come with their own supported kernels bundled in the ROM. So, after flashing the new ROM, your current kernel will be REPLACED by a supported one from the new ROM.
Better?
"To err is human, to forgive is divine. "
Sent from my SGS II
I dont believe that rr is stock based. Sorry I didnt reply xda app was down. Immortalneo is top man and will guide you down the right path.:thumbup:
immortalneo said:
Don't worry, things can be a bit hard to digest at first.
Let me make it easier:
1. U are currently using a stock or custom ROM, but you want to change the kernel (without any plans to flash a new ROM). In this case, you need to select a kernel that is compatible with your current ROM.
2. U are on a stock ROM, and you need to flash a custom ROM. You want to flash a kernel to root it and install CWM (to enable u to flash a new ROM). In this case also, u should flash a kernel that supports your current stock ROM.
3. U are on a custom ROM, and you want to try another custom ROM (which may require another kernel to support it). In this case, you DON'T need to flash a new kernel that will support ur new ROM. You can flash the new ROM directly. All custom ROMs come with their own supported kernels bundled in the ROM. So, after flashing the new ROM, your current kernel will be REPLACED by a supported one from the new ROM.
Better?
Click to expand...
Click to collapse
So my breakdown would be I'm using a Stock ROM with Philz kernel rooted and CWM. I want to Install Resurrection Remix which is a 4.2.x ROM, Philz is a 4.1.x Kernel so i need to install a new kernel to support Resurrection Remix? or would that come with its own Kernel?
And for my tablet. I flash Philz kernel and install superuser to root the device. so now its stock Rom with Philz kernel. So when i install Cyanogenmod Rom it will install its own Kernel or do i also need to install a Kernel that supports 4.2.x?
Or is it Firmware version based Kernel updates that happen when you install and new custom ROM?
i.e Running 4.1.x kernel and installing a 4.1.x Custom ROM will update the kernel, but installing a 4.2.x ROM will not?
vice versa Running a 4.2.x kernel and installing a 4.2.x ROM will update the kernel, but installing a 4.1.x ROM will not?
Kind Regards, I appreciate your time for reading my mind numbing questions.
Serathian
For you i9100 just flash the rom using philz cmw recovery and once its done you will have a custom rom with custom cm kernel which is rooted and has cwm with it. I would say to format system ,data, cache and preload before you flash it using philz recovery and make sure the rom and gapps is on int sd card were you can find it.
As for the tablet make sure philz is compatible with that tablet first!! Dont just flash it on that thinking because its 4.1.2 it will work.
Btw with philz also come with root access too.
Serathian said:
So my breakdown would be I'm using a Stock ROM with Philz kernel rooted and CWM. I want to Install Resurrection Remix which is a 4.2.x ROM, Philz is a 4.1.x Kernel so i need to install a new kernel to support Resurrection Remix? or would that come with its own Kernel?
Click to expand...
Click to collapse
No, you don't need to install a new kernel, because flashing RR will flash a compatible kernel (included in the ROM) by itself. :good:
Serathian said:
And for my tablet. I flash Philz kernel and install superuser to root the device. so now its stock Rom with Philz kernel. So when i install Cyanogenmod Rom it will install its own Kernel or do i also need to install a Kernel that supports 4.2.x?
Click to expand...
Click to collapse
CM ROM will install its own kernel, so you don't need to do that. :good:
Serathian said:
Or is it Firmware version based Kernel updates that happen when you install and new custom ROM?
i.e Running 4.1.x kernel and installing a 4.1.x Custom ROM will update the kernel, but installing a 4.2.x ROM will not?
vice versa Running a 4.2.x kernel and installing a 4.2.x ROM will update the kernel, but installing a 4.1.x ROM will not?
Click to expand...
Click to collapse
Don't overcomplicate stuff mate. When you flash a ROM, the kernel contained in the ROM will be replace your current kernel. Simple.
Thanks a lot!!!
I installed RR to my i9100 and cm10.1 to my p5100.
I'm having a little trouble with i9100 device though, I keep getting random sim locks on the device.. Not sure what could be causing it. It didn't happen on stock 4.1.2.
The devices will be locked and when I wake it I get prompted for the sim lock code. I now have the sim lock on my phone deactivated but I'm fearful that even thought I am not getting prompted for the sim code, the sim could be de-activated while the phone is in sleep thus not connect to the network?
Could be a loss of signal activate a security feature of the sim. Or a problem with the kernel?
Kind regards.
Many many thanks for all your advice into helping me understand a little better.
Serathian.
Sent from my GT-P5100 using xda app-developers app
If you're sim locked, then you want the app 'Galaxsim unlock'. Search for the xda thread, the OP is spocky12 if that helps you find it. It won't be kernel related. And, test it for yourself. See if you get messages /calls / push notifications while your screen is off & phone is sleeping.
Sent from a galaxy far, far away
The i9100 was originally sim locked, but I paid someone to unlock it, once I got the phone back from him "unlocking" it. It was apparent that he has flashed the device with a new kernel and ROM in order to unlock it... Not to sure of the process. A couple months later I flashed 4.1.2 as it wasn't available as a update on the ROM he installed. The phone re-sim locked and I downloaded the app you mentioned and unlocked the phone successfully, been happily using it up until I installed RR. Now I'm suffering from random pin locks. The phone connects to the network and functions perfectly, apart from said sim locks.
My only fear is missing important calls if this lock is causing network disconnections. Can I log network functions and connectivity to see what's causing it?
Regards
Sent from my GT-P5100 using xda app-developers app