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
Related
I know what I'm doing but I'm not sure if I'll do it right so just checking.
So... do I flash back to stock ROM and use CWM from there.
Or... do I use the current CWM in my custom ROM.
th3controller said:
I know what I'm doing but I'm not sure if I'll do it right so just checking.
So... do I flash back to stock ROM and use CWM from there.
Or... do I use the current CWM in my custom ROM.
Click to expand...
Click to collapse
From your signature it looks like you are on SCOM so you can use cwm and flash any bml build directly from there.
If you are switching to MTD (CM9, MIUI, AOKP...) make sure to follow all of the steps as in the OP of each thread. There are directions on how to flash any rom in the OP for each rom. It may help if we know what rom you are wanting to flash to.
To whoever can help me -- I'm trying to use kexec to install CM10 on my SGS3, but i've been hearing that when you hard-reboot your phone, AKA battery pull/death, or using the power button, you go right back to the recovery. This isn't a problem, as long as I don't have to re-flash CM10 every time I boot, or I have no choice but to go to the stock ROM. I'd like to be able to either boot to the CM10 or go to my currently flashed version of CM10 from the recovery.
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Bumping... could really use help here.
Just reboot from recovery and it will bootloop a couple times then boot up.
DonSagiv said:
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Click to expand...
Click to collapse
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
lazarus2405 said:
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
Click to expand...
Click to collapse
In which cases would someone lose kexec and need to reinstall it?
Zalithian said:
In which cases would someone lose kexec and need to reinstall it?
Click to expand...
Click to collapse
When u flash back to stock.
droidstyle said:
When u flash back to stock.
Click to expand...
Click to collapse
Or any rom.
jaymattt said:
Or any rom.
Click to expand...
Click to collapse
not necessarily...if your flashing a custom rom/kernel like beans custom stock, cm10, paranoidandroid, aokp, or imosyeons Touchwiz leankernel, kexec is always there...kexec is built into the kernel, cwm 6.0.1 is compatible with kexec.
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
droidstyle said:
Just reboot from recovery and it will bootloop a couple times then boot up.
Click to expand...
Click to collapse
Thanks! CM10 works beautifully on here.
droidstyle said:
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
Click to expand...
Click to collapse
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link. There is also a kexec twrp 2.2 recovery but it didn't work for me.
piiman said:
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link.
Click to expand...
Click to collapse
yea i know, thats what I used in reference to my previous post.
droidstyle said:
yea i know, thats what I used in reference to my previous post.
Click to expand...
Click to collapse
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Triskite said:
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Click to expand...
Click to collapse
let this thread die....there is no need to use anything kexec. stick to cwm 6.0.1.0 or 6.0.1.2
I'm as happy as anyone else with this new method of unlocking the bootloader. I'm rooted the ODIN way and then have bean's stock rom with imosey's custom rom installed (via the k-exec). I've read that people are doing this with all different kinds of rom and recovery.
My question: what happens to the k-exec? All gets re-written? we don't need to go to stock to get this to work? It seems to me that it would be safer if we re stock, no?
I know there is a one click now but I prefer manual stuff.
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
vx2ko said:
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
loveubuntu said:
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
I'm on Synergy 1.7 (non-nightly) and it's running fine. Still using the stock kernel and not Imo's lean kernel but it apparently still worked for others.
PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
We need a list of non kexec and kexec recoveries and kernels. I've been in the Rom flashing and troubleshooting game for a while but never had to use a locked otloader so this kexec stuff is new. If someone could clarify what's kexec and what's not that would be great
Sent from my SCH-I535 using xda app-developers app
loveubuntu said:
I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
lazarus2405 said:
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
Click to expand...
Click to collapse
Thank you, great explanation. To clarify: If you have k-exec and rot before the bootloader unlock leak and now unlock your bootloader with the new leak, you have the best of both worlds. If you use a ROM that uses K-exec, the k-exec part kicks in and if you use the new CM10 alpha without k-exec, the k-exec is unused and the new unlock bootloader is utilized.
Is that right?
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
droidstyle said:
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
Click to expand...
Click to collapse
Quick noob question. I rooted and flashed synergy v1.7 using ROM Manager from the app store. When I open the app is says rom manage v5.0.1.5 at the top. Everything is running perfect and do not want to flash a new rom until synergy does a jellybean rom. Should I use the unlock app to unlock my phone now or is there no need? Also is rom manager ok to continue using or should I use something else? Thanks for the help
I got lazy and unlocked using the market app. Running Bean building 8 that is using kexec. I'm still getting three reboots. Is this right?
Sent from my SCH-I535 using xda premium
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?
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