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.
Is it ok to flash a custom kernel on top of another custom kernel?
Sent from my GT-I9100 using xda premium
You dont need to revert on the original one before flash another custom. But you need to format dalvik cache and cache in recovery before flashing or you probably have a bootloop.
I suggest to make a backup of the rom in recovery, so If something goes wrong you can enter recovery and have the latest known working rom back in 2 minutes.
Please note flashing kernels always have a very small chance to corrupt your efs partition, its suggested to backup your efs folder before start play with roms and kernels. How to backup the efs, use the search tool of the forum
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
You dont need to revert on the original one before flash another custom. But you need to format dalvik cache and cache in recovery before flashing or you probably have a bootloop.
I suggest to make a backup of the rom in recovery, so If something goes wrong you can enter recovery and have the latest known working rom back in 2 minutes.
Please note flashing kernels always have a very small chance to corrupt your efs partition, its suggested to backup your efs folder before start play with roms and kernels. How to backup the efs, use the search tool of the forum
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks for that. I know how to backup efs. Can i just use nitrality instead of ADB? To flash ROMs does it need to be in a specific firmware like sgsl or is it ok to have different firmware from the base of a custom rom?
Sent from my GT-I9100 using xda premium
I know my english sux sry:
Depends on the kernel but usually it is listed in the kernel thread the how to (odin or clockworkmod), clockworkmode is already on your phone if you rooted it with cf-root.
Now, to enter clockworkmod recovery, just push volume up + home + power button until the S2 bootlogo appears, then wait few seconds.
About the kernel type, i always flashed any kernel despite of my baseband, the difference is not so big.
if something is not working, you can always youse the nandroid backup (the backup done with the recovery cwm (up+home+power) and get back to the previous rom with previous kernel.
Im not really in the kernel "how to" someone else can prolly give you more detailed info, but as for me, i flashed ninphetamine 2.05 and 2.1.3 in cwm and it worked.
But.. as always, the kernel developers got a how to install in their kernel thread, so just read those and be sure about if you need odin or clockworkmod, if you are not sure, DONT flash anything until you are sure on how to proceed or wich system to use for flashing, better keep an old kernel with a working phone than have a brick to hold the papers
PS: also almost all the roms on the S2 forum are flashable with the clockworkmod, only few (like the lite'ning) are flashable with odin.
Again, i know im boring, dont proceed if you are not sure, better ask 10 times instead brick your phone
ephraim033 said:
Is it ok to flash a custom kernel on top of another custom kernel?
Yes not a problem flash as per the custom kernel instructions .
Kernel can be changed within an individual firmware or custom rom .
jje
Click to expand...
Click to collapse
Thanks for the reply guys. Coming back to my second question. What if i have KF1 and the rom i want to flash has a base of KI3, should i flash to stock KI3 first before flashing the custom rom or is it ok to flash a KI3 custom rom without flashing first to stock KI3?
Sent from my GT-I9100 using xda premium
The custom rom first, the kernel after.
I got the habbit to boot succesfully at least once the custom rom. If everything is ok i then flash the kernel. Better do 1 task at time.
You can decide to try the rom without change the kernel..and try a different one if you experience battery drain or other problems.
Sent from my GT-I9100 using Tapatalk
If i am on KH3 and want to flash a custom rom based on KI4 then i would flash stock KI4 and KI4 root first .
Custom rom flashed i will often try a different kernel later .
jje
from my experience
I have found that when i upgraded rom from gingerbread to ics that most custom kernals work with these roms ie now running with xxlpw ics (from gingerbread) with xwlp7 kernal. from what i have read on other posts and threads i could swap kernal to siya or any other as the mega good developers have made them (hotswappable) interchangeable as previous reply said swapping kernal might give you better battery or solve overheat probs.
Eg iwas running darkys rom with siya kernal v?something my phone rocketed temp in short time so i swapped kernal for an up to date one (could have used older one) it solved problem.
Anyone feel free to correct explination im still learning too lol
linuxnubee said:
I have found that when i upgraded rom from gingerbread to ics that most custom kernals work with these roms ie now running with xxlpw ics (from gingerbread) with xwlp7 kernal. from what i have read on other posts and threads i could swap kernal to siya or any other as the mega good developers have made them (hotswappable) interchangeable as previous reply said swapping kernal might give you better battery or solve overheat probs.
Eg iwas running darkys rom with siya kernal v?something my phone rocketed temp in short time so i swapped kernal for an up to date one (could have used older one) it solved problem.
Anyone feel free to correct explination im still learning too lol
Click to expand...
Click to collapse
I'll just point out this thread was dead since Sept 30 before you posted...
Hey Guys,
I bricked actually my phone.
I want to know now, wich is actually the best Android 4.0.3 ROM.
I know how to flash via zip and via odin.
I dont know how to flash kernel
I wanna use a Android 4.0.3 ROM with DarkKnights or Siyah Kernel, tell me what you think about it.
First flash the ROM then Kernel?
Best Regards!
Noxxo
There is no answer to "best rom/kernel?". Many are good - and it largely comes down to personal preference. Try out a few and see what you think for yourself.
In general, you flash a kernel just like you flash a rom from a .zip. Flash the rom first, then the kernel - otherwise the kernel would be overwritten with the stock one from the rom.
So the Kernel from the ROM is a stockkernel? i give a try
Well not necessarily a pure-vanilla-stock kernel, but the ROM will come with a kernel already baked in that will be a good baseline to start from.
Uhm.. at first I need CWM and a ROM with it.. I cant open now CWM. I have to flash via Odin right now, after that i can use from SD card, but i need a ROM and CWM for now, can u give me a link for a ROM via Odin ?
Flash to clear 4.0.3 it will wipe your phone (3 files - Modem file is for phone, CSC for CSC and CODE for PDA*check repartition*) + PIT file.
CFRoot it with ODIN(karnel file = PDA)it will give you root and CWM, flash old bootloader(BL file = Bootloader but dont check BL update), clear flash counter with JIG. Now you can flash zip files from CWM.
But i dont recommend 4.0.3 it is unstable and has many bugs. I am using HyperDroid 6.1.17(XILA2 based) and RedPill 1.3 karnel
I will try it now. thanks 4 ur config.
I've always used custom roms on my galaxy. I was even using in dual-boot, a Jelly Bean Revolt and other stock. I was testing a new stock, and flashed it with Odin Mobile. I ended up losing custom. Since then, I can no longer flashing custom roms, even having problems flashing a new kernel. I use the CWM, do the wipes and flash the* rom, but after the reboot, it starts a boot loop with the galaxy s2 logo. The phone is inoperable. At least the download mode works, and I ended up going back to stock a few times. I even tried and flash another custom roms, but the same problem happens.
Anyone know how to help??
gu_cad said:
I've always used custom roms on my galaxy. I was even using in dual-boot, a Jelly Bean Revolt and other stock. I was testing a new stock, and flashed it with Odin Mobile. I ended up losing custom. Since then, I can no longer flashing custom roms, even having problems flashing a new kernel. I use the CWM, do the wipes and flash the* rom, but after the reboot, it starts a boot loop with the galaxy s2 logo. The phone is inoperable. At least the download mode works, and I ended up going back to stock a few times. I even tried and flash another custom roms, but the same problem happens.
Anyone know how to help??
Click to expand...
Click to collapse
Flash a 3-parted stock firmware and activae "re-partition" in Odin.
After this flash a rooted kernel .tar (cf-root, speedmod, etc.) via Odin.
Now start flashing again.
Hope this works.
CHEERS
Hannibal226 said:
Flash a 3-parted stock firmware and activae "re-partition" in Odin.
After this flash a rooted kernel .tar (cf-root, speedmod, etc.) via Odin.
Now start flashing again.
Hope this works.
CHEERS
Click to expand...
Click to collapse
I've read about emmc brick. And this problem started after using a LQ6 4.0.4 stock rom.
I even used the "emmc brick check", and it shows "YES. Insane chip".
I flashed now a 2.3.6 stock rom. But i haven't tried to flash another custom rom yet.
Should i proceed as you say???
And sorry for my noobness, but what is a 3 parted stock rom?
gu_cad said:
I've read about emmc brick. And this problem started after using a LQ6 4.0.4 stock rom.
I even used the "emmc brick check", and it shows "YES. Insane chip".
I flashed now a 2.3.6 stock rom. But i haven't tried to flash another custom rom yet.
Should i proceed as you say???
And sorry for my noobness, but what is a 3 parted stock rom?
Click to expand...
Click to collapse
it contains a .pit file for re-partition and 2 other files,but u should be carefull in using the .pit file though, since it could potentially hardbrick ur device ma8
instead try updating ur device from GB 2.3.6 to a stock v4.0.3(do not flash any 4.0.4 ICS firmware) ICS firmware either thro 'KIES' or 'ODIN', then root ur phone and try installing a custom ICS rom of ur choice and see
Sun90 said:
it contains a .pit file for re-partition and 2 other files,but u should be carefull in using the .pit file though, since it could potentially hardbrick ur device ma8
instead try updating ur device from GB 2.3.6 to a stock v4.0.3(do not flash any 4.0.4 ICS firmware) ICS firmware either thro 'KIES' or 'ODIN', then root ur phone and try installing a custom ICS rom of ur choice and see
Click to expand...
Click to collapse
I'll try what you're saying.
I'm updating to a 4.0.3 through odin. After root, can i install directly a Jelly bean rom?
gu_cad said:
I'll try what you're saying.
I'm updating to a 4.0.3 through odin. After root, can i install directly a Jelly bean rom?
Click to expand...
Click to collapse
after root first install a custom kernel either siyah or dorimanx latest and then try installing a JB rom compatible with them and see
Sun90 said:
after root first install a custom kernel either siyah or dorimanx latest and then try installing a JB rom compatible with them and see
Click to expand...
Click to collapse
I've already updated to 4.0.3
If i'm flashing Jelly Bam Rom for an example, do i need to install these kernel before, since the rom already has it in the AROMA installer???
And should do the wipes before it/??
Thanks!
gu_cad said:
I've already updated to 4.0.3
If i'm flashing Jelly Bam Rom for an example, do i need to install these kernel before, since the rom already has it in the AROMA installer???
Thanks!
Click to expand...
Click to collapse
yes it will be there in Aroma but for a perfect trouble free install i suggested the same, rest is ur call ma8, fell free todo so the way it looks good for u
Sun90 said:
yes it will be there in Aroma but for a perfect trouble free install i suggested the same, rest is ur call ma8, fell free todo so the way it looks good for u
Click to expand...
Click to collapse
Thanks.
It only worked with with previous instalation of dorinmax kernel. So i had to use Revolt Jelly Bean Rom.
When i tried to flash Jelly Bam Rom, got into galaxy s2 loop, after reboot.
At least, i've got one custom rom.
Now it's so much more difficult to install a rom on my phone. Only because i used that 4.0.4.
There's no way back, right?
My warranty ends in November 30th.
:/
gu_cad said:
Thanks.
It only worked with with previous instalation of dorinmax kernel. So i had to use Revolt Jelly Bean Rom.
When i tried to flash Jelly Bam Rom, got into galaxy s2 loop, after reboot.
At least, i've got one custom rom.
Now it's so much more difficult to install a rom on my phone. Only because i used that 4.0.4.
There's no way back, right?
My warranty ends in November 30th.
:/
Click to expand...
Click to collapse
That's why I said to completely go back on a stock firmware with Odin.
But 3 parted (and for sure with .pit-file then, forgot to say this) and check repartition.
But u have to choose... A phone which turns screen on an just looping or a chance from 80% to 20% for getting phone working again or bricking it.
I personally hadn't any prob til now, but only went back 4-5 times ins 2-3 years (also did the same with SGS before SGSII)
So u got my answer u have to choose.
Anyway u can send it back because warranty and if they fix it, it's fine... If not u can try it by urself anyway
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
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