So coming from dx we had no kernels to worry about. Now, my questions are.
Say I flash to a rom that now has a kernel that's flashed with the rom. And I make a backup before I flash. After being on that rom with a kernel, can I restore the backup and it restores the stock kernel that the backup was running on?
It seems I've read some people coming from cm10 trying to restore to a tw rom and it not booting, thoughts have been because of the cm10 kernel it was
the on?
If I need to flash kernels before restoring backups where do I get stock kernel and what's the proper way to get to a working backup once kernels are involved?
I hope I'm not to confusing here.
Sent from my Synergized vzw S3!
silver04v said:
So coming from dx we had no kernels to worry about. Now, my questions are.
Say I flash to a rom that now has a kernel that's flashed with the rom. And I make a backup before I flash. After being on that rom with a kernel, can I restore the backup and it restores the stock kernel that the backup was running on?
It seems I've read some people coming from cm10 trying to restore to a tw rom and it not booting, thoughts have been because of the cm10 kernel it was
the on?
If I need to flash kernels before restoring backups where do I get stock kernel and what's the proper way to get to a working backup once kernels are involved?
I hope I'm not to confusing here.
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
im not sure but I think things are a bit different now with the unlocked bootloader. there was a lot of problems between kexec and switching between TW and CM10.
I think that any restore will get you back just fine as it flashes everything back including kernel. just be REALLY careful what CWM you are on. its just safer overall to stick with 6.0.1.0 as it works with every rom.
i have no idea if its on XDA but you can find imoseyon and stock kernel on rootzwiki.com
xicewallx said:
im not sure but I think things are a bit different now with the unlocked bootloader. there was a lot of problems between kexec and switching between TW and CM10.
I think that any restore will get you back just fine as it flashes everything back including kernel. just be REALLY careful what CWM you are on. its just safer overall to stick with 6.0.1.0 as it works with every rom.
i have no idea if its on XDA but you can find imoseyon and stock kernel on rootzwiki.com
Click to expand...
Click to collapse
That helps a little. I know with being unlocked any recovery should work. Twrp has been good to me so far, I'm going to try and stick with it.
Sent from my Synergized vzw S3!
Nobody else is used to flashing with kernels and can give a little input?
Sent from my Synergized vzw S3!
Yes there were issues going from kexec to no kexec...I have tried almost all the ROMs out since the unlocked bootloader and not had any issues with this I have also been using a Sprint kernel and not having any issues...just make sure that you flash aosp kernels if you're using aosp and tw kernels if using a tw ROM...and personally I use TWRP and have never had any issues at all...if using TWRP just pay attention to what you're wiping because you have lots of options there
Delete
1. Unlock your bootloader first. Skip anything that says for k-exec.
2. Use latest CWM.
3. Make sure that any Kernel you use is designed for your type of ROM. JB-AOSP Kernels for JB-AOSP ROMs, ICS-TW for ICS-TW ROMs, etc. Again, make sure it is non-kexec.
4. Always wipe cache and dalvik cache when switching kernels to be sure your dalvik is rebuilt by the new kernel.
If these steps are followed you should be golden. Happy flashing!
Sent from my SCH-I535 using Tapatalk 2
Related
CWM Kexec
CWM
CWM touch
??????
that will work with stock roms and asop roms and anything else???
or will we have to change recovery for whatever rom we are using at the time??
Hate to be mean, but this isn't exactly development. Should've been posted in the Q&A forum probably. To answer your question though, you don't need to change recoveries with ROMs, they are universal (until you get to booting kernels in recovery and using Kexec). Which recovery you use though, is simply personal preference for the most part.
so you will have to change recoveries depending if you flashing a stock rom or a kexec kernel rom????
jdog94 said:
so you will have to change recoveries depending if you flashing a stock rom or a kexec kernel rom????
Click to expand...
Click to collapse
CWM Kexec is used to flash CyanogenMod, and any other ROMs that people may put out that utilize Kexec. It's basically a work-around for the locked bootloader. Otherwise, it doesn't really matter what recovery you have. CWM and TWRP both do the same things.
so can CWM Kexec be used to flash a stock rom ???
jdog94 said:
so can CWM Kexec be used to flash a stock rom ???
Click to expand...
Click to collapse
Yes.
Honestly I haven't tried to flash a stock TouchWiz ROM with CWM Kexec, but I assume it could be done.
ok cool..
i found EZ-Recovery so i can switch back and forth as needed
thanks
TWRP and CWM are for touchwiz roms generally, and CWM kexec is for aosp (aokp, cyanogenmod, etc).
update: after some testing, cwm kexec works oon touchwiz also so honestly i would use that until the bootloader unlock is complete.
I use CWM kexec with a Synergy (TouchWiz) and the iwo kernel. The kernel is why I use kexec but I'd say the kexec is worth it so you don't need to worry about switching to it if/when you decide to use an aftermarket kernel or rom that requires kexec
Sent from my SCH-I535 using xda app-developers app
Hi,
I have followed everything in this thread http://forum.xda-developers.com/showthread.php?t=1837863
I have backups nandroid ready and wasn't too sure, if I dont like this build then i could restore back to stock using CWM? or Odin.
I felt that I need to wait for reply to comfirm before flashing this cyanogenMOD 10.
Thanks!
LeonKnight12 said:
Hi,
I have followed everything in this thread http://forum.xda-developers.com/showthread.php?t=1837863
I have backups nandroid ready and wasn't too sure, if I dont like this build then i could restore back to stock using CWM? or Odin.
I felt that I need to wait for reply to comfirm before flashing this cyanogenMOD 10.
Thanks!
Click to expand...
Click to collapse
IF my memory serves me right, with an unlocked bootloader, you can recover to a TW rom but I think its needs to either have the kernel built into it OR you need to somehow flash to a TW kernel. I say this because I think that if your kernel is still an AOSP one, then the device will not boot up.
some roms already come with a kernel for their rom so I think in most cases, with CWM 6.0.1.x, you could restore a TW nandroid.
If you want to restore a backup of a TouchWiz rom you have then just use the EZ Recovery app to flash the hybrid (CWM/Kexec) recovery...reboot to recovery and restore your nandroid. Simple process!
Once the Dev's building TW roms start using the non-kexec flashing method then you will be able to restore using the normal CWM recovery. Just like you said, you can also use ODIN to restore to stock but it's a pain because you have to root all over again. Just know you have a few options.
Ok thanks everyone!
So good
Fwiw... I've been switching back and forth between Synergy and CM for a couple days now (flashing multiple times) and cwm touch works for synergy but u need new cwm for CM10.
Hope this helps.
Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.
Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium
nativesmiley said:
Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You come back to TW at your own risk. This where most bricks happen. Best practice is to Odin back to stock and then come back to TW. Luckily you survived CM so far but flashing back to TW could cause a problem. If you don't want to Odin first wipe all partitions till raw and give it a shot.
ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks
Rudy_Ruettiger said:
ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks
Click to expand...
Click to collapse
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:
goldsmitht said:
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:
Click to expand...
Click to collapse
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
Stay on TWRP 2.3.3. I've been using TWRP 2.3.3 just fine while flashing multiple Beans JB TW builds. Not sure what issues others had but it works fine for me. Also, if you intend to install 4.2 AOSP in the future then you'll have to update TWRP again anyway if you downgraded it.
nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
yes, you can use TWRP 2.3.3 to flash old backups made with any version TWRP. with no problems.
however, you can NOT flash old backups made with CWM. different system and will definitely NOT work.
:cyclops:
thank you very much guys! appreciate the input!
what is the proper way to flash between TW and CM (10.1) so I dont get stuck in roaming mode again?
Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app
Nopi45 said:
Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
know that if you go the ODIN route, you will have to re-root and re-unlock your bootloader.
if you have the MOST up to date recover (CWM OR TWRP - I prefer TWRP 2.3.3) and you have a backup made of a TW ROM, and are on 10.1 currently, then just clear dalvic, cache, and restore your TW ROM.
however, if you do not have one, then would suggest factory reset and then clean install of TW.
there are always "chances" of issues, mainly the 0 folder, but i've been flashing back and forth between MIUI bV, Synergy, and CM10.1 and only problem i had was when my mobile network got switched, and i had to go back in and change to RUIM/SIM. and that was the only thing.
just know what you are doing and know where to go to get answers to help fix things that may go wrong.
and, "insert legal comments here"... no one is responsible for what YOU do to YOUR phone, except YOU.
:cyclops:
The only bad experiences I've had going from 4.2 to TW is when I only briefly installed 4.2 but didn't get data working. That left me with no data in TW. So I had to odin back to stock then re-root, unlock bootloader and flash.
will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?
Rudy_Ruettiger said:
will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?
Click to expand...
Click to collapse
I haven't had a problem going from one 4.2 AOSP rom to another. YMMV tho. Just flash a nandroid before you do it just in case.
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.