I went through a couple threads and couldn't really find an answer for this. iif something says "edify only" does that mean i can NOT flash it through CWMR? Or can i? and if i cant use clockworkmod, how do i get "edify". sorry if this is a stupid Noob question
If it says edify only, it basically means that you can use it CWMR3 as well as the 3-31-11 version of CWMR. Basically, before, themers, kernelers, and devs were using the 'amend' script in their .zip flashing code for CWMR. But now, as a way to move on, devs etc and now using the new and improved 'edify' script. Hope that answers it.
Thanks
TheSonicEmerald said:
If it says edify only, it basically means that you can use it CWMR3 as well as the 3-31-11 version of CWMR. Basically, before, themers, kernelers, and devs were using the 'amend' script in their .zip flashing code for CWMR. But now, as a way to move on, devs etc and now using the new and improved 'edify' script. Hope that answers it.
Click to expand...
Click to collapse
so i can falsh edify only scripts with CWMR 2.5.x?
jkat797 said:
so i can falsh edify only scripts with CWMR 2.5.x?
Click to expand...
Click to collapse
You can flash both edify and amend in the newest cwm2.5.x and edify only in cwm3.
Sent from my SCH-I500 using XDA App
Related
It seemed to pop up out of nowhere when Super Clean switched to it. Now I'm seeing themes and such having to be updated to support it. Googling it just brings me to threads here discussing it, but I can't find anything introducing what it is.
It's the new update format introduced and required by CWM 3.
Does that mean a rom using edify must be flashed from CWM 3? Or is it backwards compatible?
Also, do themes with edify work on non-edify roms?
Pretty sure edify only works with 3, and 3 only works with edify.
jvincent08 said:
Does that mean a rom using edify must be flashed from CWM 3? Or is it backwards compatible?
Also, do themes with edify work on non-edify roms?
Click to expand...
Click to collapse
Edify isnt a rom type. All it is is the type of scripting language that the updater script inside the flashable zips use. So if you still have cwm 2.x you'd still be able to flash stuff that uses the amend scripts. But cwm 3 is edify and edify only. But to really answer your question, as long as the flashable zip's script is written in edify it'll flash as any other would, but only with CWM 3.x
Sent from my SCH-I500 using XDA App
times_infinity said:
Edify isnt a rom type. All it is is the type of scripting language that the updater script inside the flashable zips use. So if you still have cwm 2.x you'd still be able to flash stuff that uses the amend scripts. But cwm 3 is edify and edify only. But to really answer your question, as long as the flashable zip's script is written in edify it'll flash as any other would, but only with CWM 3.x
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
The red cwm from Jt seems to work with amend & edify as well. I upgraded to superclean 2.71 using the red cwm with no problems.
Ya from what I understand from the devs cwm 3.x is only edify while previous versions supported both.
Personally I'm still running 2.x red cwm.
Orange cwm doesn't work either. I don't trust it to do the necessary flashing that the red one can do.
Edify can work with older recoveries, but won't necessarily work, but amend will not work with CWM 3.x.
Also, why do people say that nothing works in the new cwm 3.0? I've flashed a few roms in it with no problems. Sure, stuff may be broken in it, but how is that different from green cwm?
garywojdan81 said:
The red cwm from Jt seems to work with amend & edify as well. I upgraded to superclean 2.71 using the red cwm with no problems.
Click to expand...
Click to collapse
As did I. Interestingly enough I had just flashed that new one a few days before adding 2.7.1, so maybe that's how I skipped whatever problems others are having.
When I want to flash I have to use Odin to flash a cwm.tar file. I wish the orange would work on everything!!!
Sent from my SCH-I500 using XDA App
This from Eugene:
All Scripting will be based on edify from here on ( No amend support )
When you update the zImage, and load Eugene's latest recovery, it will no longer flash other ROMs that are not built the way Eugene has done with his.
This is not a complaint, amend support has been deprecated by Google and the world is moving on. But right now I can't flash anything by EDT or TW without using ODIN to reset everything.
For dev level folks getting around this might be easy, but for a guy like me, it creates a barrier.
So my question for the devs would be, is everyone else planning on moving into edify scripts as well? Will I soon be able to flash GCR3 U7, then Bi-Winning, then Bionix without having to completely re-stock and re-root every time?
When we all move on to gingerbread ,everyone will use amend. It's dependent on the recovery. 2.2 kernels all use amend based recovery.
Sent from my SGH-T959 using Tapatalk
One way you can get around this is to flash another kernel. I think the stock voodoo kernels in supercurio's voodoo lagfix thread flash using edify but when loaded they support ammed scripts.
Also, bigertime, there is a word mistake in your first sentence. Gingerbread required edify, and you put ammed, just pointing that out so that people don't get confused.
Sent from my SGH-T959 using XDA App
geoffcorey said:
One way you can get around this is to flash another kernel. I think the stock voodoo kernels in supercurio's voodoo lagfix thread flash using edify but when loaded they support ammed scripts.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
good info...thanks
Androidawg said:
This from Eugene:
All Scripting will be based on edify from here on ( No amend support )
When you update the zImage, and load Eugene's latest recovery, it will no longer flash other ROMs that are not built the way Eugene has done with his.
This is not a complaint, amend support has been deprecated by Google and the world is moving on. But right now I can't flash anything by EDT or TW without using ODIN to reset everything.
For dev level folks getting around this might be easy, but for a guy like me, it creates a barrier.
So my question for the devs would be, is everyone else planning on moving into edify scripts as well? Will I soon be able to flash GCR3 U7, then Bi-Winning, then Bionix without having to completely re-stock and re-root every time?
Click to expand...
Click to collapse
Since Eugene has moved on to greener pastures, I removed his last kernel from my personal gc remix. I replaced the kernel with a version of cwk, replaced the edify scripts with the amend script from gc3.5, and removed the wipe file from the root of the zip, replacing it with the busybox file from gc3.5 in the root of the zip. It makes flashing back and forth to different roms less labor intensive.
Ginger Clones of the World Unite!!! via the XDA App
Br1cK'd said:
Since Eugene has moved on to greener pastures, I removed his last kernel from my personal gc remix. I replaced the kernel with a version of cwk, replaced the edify scripts with the amend script from gc3.5, and removed the wipe file from the root of the zip, replacing it with the busybox file from gc3.5 in the root of the zip. It makes flashing back and forth to different roms less labor intensive.
Ginger Clones of the World Unite!!! via the XDA App
Click to expand...
Click to collapse
Here's the part where I ask you to post that. You knew it was coming.
Androidawg said:
Here's the part where I ask you to post that. You knew it was coming.
Click to expand...
Click to collapse
Had an idea it was coming, but I'm not going to rehost his rom. The changes are simple enough, plus the specific kernel I am using was never meant to see the light of day, and I swore to its creator it never would through my hands. If you're looking for more specific directions, I can post more later when I get home. The simplest way is to open gc3.7 and gc3.5 in two different 7zip windows, and drag the scripts and busybox files as I described earlier from 3.5 to 3.7, and also the kernel of your choice into the update folder inside the zip. Lmk if you need any more help on that.
Ginger Clones of the World Unite!!! via the XDA App
so when sg2 comes out? will the devs be using edify or ammend?? curious noob here?
great question androidawg
well, since the SGS II is using GB, and GB REQUIRES edify (no legacy ammend support) then the devs will HAVE to use edify, there isn't any other choice.
geoffcorey said:
well, since the SGS II is using GB, and GB REQUIRES edify (no legacy ammend support) then the devs will HAVE to use edify, there isn't any other choice.
Click to expand...
Click to collapse
That was my understanding.
Br1cK'd said:
Had an idea it was coming, but I'm not going to rehost his rom. The changes are simple enough, plus the specific kernel I am using was never meant to see the light of day, and I swore to its creator it never would through my hands. If you're looking for more specific directions, I can post more later when I get home. The simplest way is to open gc3.7 and gc3.5 in two different 7zip windows, and drag the scripts and busybox files as I described earlier from 3.5 to 3.7, and also the kernel of your choice into the update folder inside the zip. Lmk if you need any more help on that.
Ginger Clones of the World Unite!!! via the XDA App
Click to expand...
Click to collapse
Sounds simple enough. But doesn't opening a .zip mean that it needs to be re-signed? I never understood how that works. Moving the files is easy enough.
If you're using cwm, then no resigning is required. That's part of the reason to get cwm.
Sent from my SGH-T959 using XDA App
Androidawg said:
Sounds simple enough. But doesn't opening a .zip mean that it needs to be re-signed? I never understood how that works. Moving the files is easy enough.
Click to expand...
Click to collapse
Youre actually not going to unzip the archive at all. Using 7zip, open the archive (right click-7zip menu-open archive), add and remove the files at your leisure, then close the 7zip window. You can even rename the zip and it will flash without needing to sign it. The latest versions (since january to my knowledge) of cwm dont even check the signature verification. Making it just that easy.
Ginger Clones of the World Unite!!! via the XDA App
I'm trying to install the community ROM and I've seen in Adrenalyne's guide that we shouldn't use CWR 3, which is the only one I've used. I downloaded a 2.5 version and there's no TAR file. How do I install this version? I've looked several places but not having any luck.
This should help you out.
http://forum.xda-developers.com/showthread.php?t=942021
therawuncut said:
I'm trying to install the community ROM and I've seen in Adrenalyne's guide that we shouldn't use CWR 3, which is the only one I've used. I downloaded a 2.5 version and there's no TAR file. How do I install this version? I've looked several places but not having any luck.
Click to expand...
Click to collapse
We are using Edify from now on. Every Roms/Kernels/Themes are edify compatible nowadays.
xHoLyx said:
We are using Edify from now on. Every Roms/Kernels/Themes are edify compatible nowadays.
Click to expand...
Click to collapse
And if they aren't compatible, they haven't been updated in probably a month and are outdated.
I have cyanogenmod 7, but it's way to buggy. I need a clean install, but I recently dropped my phone in the pool and it won't connect via USB.... Is there a way to revert to stock JFD on my device? Maybe a flashable .zip? or a full restore? I dunno, i'm pretty desperate and my device is fully backed up on my PC.
Based on my understanding (which could be completely wrong), the answer is a long yes. CM7 uses clockwork 3.X, which uses edify scripting. All of our 2.2 & 2.1 flashable zips use amend scripting, which is not compatible with clockwork 3.X. So based on this you would have to change the scripting on a flashable zip with 2.2 or 2.1 on it to be able to apply it with clockwork 3.x (which I have no idea how you would do or where to start) or get clockwork 2.x on your CM7 rom (which I'm not sure is possible).
new charger port bro. we went over this last night
hahaha i know, right? but i'm not gonna pay fifty bucks to have someone fix it, and i can't do it myself..... I'm a software developer, not a hardware engineer.
bfranklin1986 said:
Based on my understanding (which could be completely wrong), the answer is a long yes. CM7 uses clockwork 3.X, which uses edify scripting. All of our 2.2 & 2.1 flashable zips use amend scripting, which is not compatible with clockwork 3.X. So based on this you would have to change the scripting on a flashable zip with 2.2 or 2.1 on it to be able to apply it with clockwork 3.x (which I have no idea how you would do or where to start) or get clockwork 2.x on your CM7 rom (which I'm not sure is possible).
Click to expand...
Click to collapse
K, i got clockworkmod 2.x on my phone. You know where I can get a 2.1 rom?
Bible sticky in dev section
Sent from my SGH-T959 using XDA App
oh yeah. thanks.
How did it work out im in same situation mines completely broken so no Odin an I can't get replacement 4 a while an I got school so I need 10hr+ need battery life
Sent from my SGH-T959 using XDA Premium App
what is this and what does it do?
ensures you have no issues flashing different kernels.
Clears init.d scripts associated with Kernels, removes bln associated files, clears dalvik-cache, cache, and any logcat on/off
Click to expand...
Click to collapse
how to use
download zip to your sdcard and reboot into cwm
flash kernel cleaning zip
flash new kernel
....that's it
Click to expand...
Click to collapse
when to use
When flashing from one kernel to another. Right now the only two primary kernels are Entropy's DD and Siyah. Siyah adds etc/init.d/ scripts so this ensures they are removed prior to flashing a different Kernel.
Click to expand...
Click to collapse
download
Download Kernel Cleaning Script
Click to expand...
Click to collapse
Your work is great. Much appreciation!
Sent from my SGH-I777 using Tapatalk
So "when" should this be used? Between flashing new roms? Or can it be used to clean a rom you are using?
Btw the link is not working
Sent from my SGH-I777 using xda premium
After flashing Rom.
Sent from my GT-I9100 using xda premium
highaltitude said:
So "when" should this be used? Between flashing new rooms? Or can it be used to clean a rom you are using?
Btw the link is not working
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Not to sound like a prick, but can't you read?
It says right under the first part of the OP titled "what is this and what does it do?"
in the OP it also the title says Kernel Cleaning Script.
@ sgs You mean before flashing a ROM, right? Or before flashing a new kernel.
NJGSII said:
Not to sound like a prick, but can't you read?
It says right under the first part of the OP titled "what is this and what does it do?"
in the OP it also the title says Kernel Cleaning Script.
Click to expand...
Click to collapse
Chill brotha. He's asking for when it should be flashed for proper usage. Not what it is..
I believe it should be used prior to flashing a new kernel. Also when changing ROM's which also contain a different kernel.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Well you do sound like one, I did read it and didn't say when exactly you were to use it. SO then, use it ONLY when changing kernels. So if you flash a new rom, then you do or dont use it? Only if youre running a rom, but decide to go to another kernel?
Sent from my SGH-I777 using xda premium
highaltitude said:
Well you do sound like one, I did read it and didn't say when exactly you were to use it. SO then, use it ONLY when changing kernels. So if you flash a new rom, then you do or dont use it? Only if youre running a rom, but decide to go to another kernel?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I think you're on the right track:
1) use prior to flashing a new kernel
or
2) use prior to flashing a new ROM if that ROM uses a different kernel than what you are currently using
Jank4AU said:
I think you're on the right track:
1) use prior to flashing a new kernel
or
2) use prior to flashing a new ROM if that ROM uses a different kernel than what you are currently using
Click to expand...
Click to collapse
Exactly how this should be used...
Sent from my Galaxy S II (I777) - 1.4Ghz
Thanks that is what i thought, or at least figured out with your guys help. Just didnt know if it was useful in the middle of running a rom. i.e I just flashed the Siyah kernel to Miui yesterday, would this help me today, that kind of deal. So with that thinking, if I wanted to use this tool right now, I would run it, then flash the Siyah kernel again afterwards. Now, what about, when you restore a rom? I am about to put Shostock back, do I run this tool before restoring?
well, I restored, rebooted, then boot back into cwm, flashed the cleaner, then flashed the kernel I wanted, then rebooted.
After flashing SiyahKernel.
I make a point of not putting persistent cruft anywhere - not even rooting any more.
Entropy512 said:
After flashing SiyahKernel.
I make a point of not putting persistent cruft anywhere - not even rooting any more.
Click to expand...
Click to collapse
Is this something that would need to be done if flashing a different iteration of the same kernel? Siyah 2.6.1 to 2.6.3 for example?
I know you just said we don't need to run these kernel cleaning scripts for your kernels...thanks in advance. Also, is Pika's Bolt script compatible with your kernels or is it unnecessary? Just curious.
NJGSII said:
Not to sound like a prick, but can't you read?
It says right under the first part of the OP titled "what is this and what does it do?"
in the OP it also the title says Kernel Cleaning Script.
Click to expand...
Click to collapse
So quick to jump on someone! Not to sound like a prick, but can't YOU read?!
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Jank4AU said:
Is this something that would need to be done if flashing a different iteration of the same kernel? Siyah 2.6.1 to 2.6.3 for example?
I know you just said we don't need to run these kernel cleaning scripts for your kernels...thanks in advance. Also, is Pika's Bolt script compatible with your kernels or is it unnecessary? Just curious.
Click to expand...
Click to collapse
Depends on the kernel... If it puts crap in init.d or elsewhere on the system, then yes.
Note that it may also clobber stuff your firmware dev intentionally put into init.d - I believe gtg has a zipalign script along with a script to set the CPU governor to ondemand in Unnamed.
Awesome dude thank you for this! I had it on my captivate it worked wonders
Sent from my SAMSUNG-SGH-I777 using xda premium
I gather you just edited the script form the I9100 forums this thread samsung ultimate kernel cleaning script posted by buster041284... yes?
The scripts are very similar. Yours recursively deletes everything in the init.d folder and script posted by buster041284's version deletes specific files in the init.d folder.
I believe cleaning up scripts from Siyah's kernel prior to (re)installing Entropy's kernel is the only reason for us I777 folks to use the scripts.. . right?
Wouldn't you want to only kill those files vice every script in the entire folder?
Peaster111 said:
I gather you just edited the script form the I9100 forums this thread samsung ultimate kernel cleaning script posted by buster041284... yes?
The scripts are very similar. Yours recursively deletes everything in the init.d folder and script posted by buster041284's version deletes specific files in the init.d folder.
I believe cleaning up scripts from Siyah's kernel prior to (re)installing Entropy's kernel is the only reason for us I777 folks to use the scripts.. . right?
Wouldn't you want to only kill those files vice every script in the entire folder?
Click to expand...
Click to collapse
Most cleaning scripts are about the same. I actually got the idea from the captivate forums back when it was my primary phone. Also updated the script to just remove siyah init's since that is the only kernel we have right now that installs them.
jivy26 said:
Most cleaning scripts are about the same. I actually got the idea from the captivate forums back when it was my primary phone. Also updated the script to just remove siyah init's since that is the only kernel we have right now that installs them.
Click to expand...
Click to collapse
Gotcha... no surprise that the scripts would be similar. Good call on adjusting the updaterscript... folks might get a little concerned if you wiped their other init.d scripts too.