Saw this posted in the Nexus S Development forum and wasn't sure if people are checking both so I thought this post was appropriate.
CWM has been update to v3.2.0.0
I just flashed it and all seems to be working OK. Head over to the link below and just make sure you grab the NS4G one.
http://forum.xda-developers.com/showthread.php?t=988686
Its layout is different than the normal Clockwork, but I find it more useful.
Thanks for bringing this to the frontline
Sent from my Nexus S 4G using XDA Premium App
No problem, figured it would be more noticed here from the 4G users. I did notice the layout difference as well. I like that its less cluttered and more organized... just my .02 anyway
Is there a zip that I can flash thru recovery? Or what's the easiest way to flash this. When I had an evo and amon ra I could upgrade the recovery thru a zip, is that possible?
Sent from my Nexus S 4G using XDA Premium App
use fastboot like you did when you rooted.
NYYFan325 said:
Saw this posted in the Nexus S Development forum and wasn't sure if people are checking both so I thought this post was appropriate.
CWM has been update to v3.2.0.0
I just flashed it and all seems to be working OK. Head over to the link below and just make sure you grab the NS4G one.
http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
This link takes you to the mod'd version. Do you have the link to the official version? If you are running this mod'd version, Rom Manager will not accept it as official and will want to install the official version. Rom Manager does not show 3.2.0.0 in its interface as of yet.
EDIT: Here is the link to the official Koush site. For our phone, 3.1.0.1 is the only release.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I've never used ROM manager so I really can't comment on it "seeing" the recovery. Pretty sure the only thing modified is the colors, nothing more.
NYYFan325 said:
I've never used ROM manager so I really can't comment on it "seeing" the recovery. Pretty sure the only thing modified is the colors, nothing more.
Click to expand...
Click to collapse
Colors and layout are different. Rom Manager is developed by Koush and works together with the recovery. So, if you do use rom manager, it does not recognise the mod'd version as official and you will not be able to do things like download roms and extras through Rom manager. .
No Biggie, just thought people should know before they download this and find out there rom manager does not function fully until they install the official clockwork recovery again.
ROM Manager seems to be working just fine for me
mbh87 said:
ROM Manager seems to be working just fine for me
Click to expand...
Click to collapse
So, with this mod version installed, Rom Manager (by Clockwork) is not telling you that you have to install Clockwork Recovery to be able to perform that function?
Interesting, did that to me on the last version of the mod (3.1.0.1) Maybe they changed the mod to function with the Clockwork Rom Manager.
I will install and see.
EDIT: OK, seems to work fine with Rom Manager. The last Mod did not. I had to reinstall the official clockwork Recovery. Well That Just Shows Me, Hu. Sorry for the alarm. (the sky is falling, the sky is falling)
anyone try flashing anything? if a rom/kernel uses edify to define what phones it can be flashed on i know using the crespo recovery will block all but crespo flashes..
again thats only if teh rom dev uses that feature
shabbypenguin said:
anyone try flashing anything? if a rom/kernel uses edify to define what phones it can be flashed on i know using the crespo recovery will block all but crespo flashes..
again thats only if teh rom dev uses that feature
Click to expand...
Click to collapse
All 3.X recoveries are edify. Koush and most other devs have completely moved away from amend scripts for updates/flashable zips. amend was around since cupcake if I recall correctly.
Sent from my SCH-I500 using XDA Premium App
shabbypenguin said:
anyone try flashing anything? if a rom/kernel uses edify to define what phones it can be flashed on i know using the crespo recovery will block all but crespo flashes..
again thats only if teh rom dev uses that feature
Click to expand...
Click to collapse
Installed one of Net's kernels just to be sure before posting this... no problems at all
sunder74 said:
All 3.X recoveries are edify. Koush and most other devs have completely moved away from amend scripts for updates/flashable zips. amend was around since cupcake if I recall correctly.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
perhaps i wasnt making myself clear enough.
assert(getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo4g" || getprop("ro.product.board") == "crespo4g");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
Click to expand...
Click to collapse
thats from the updater script that cm7 uses, if when it does getprop it finds anything but the crespo4g, it will fail. flashing the crespo recovery could have undesired effects.
like i stated tho, only if the dev chose to use that feature
Is this strictly a crespo recovery? I was under the impression from the post that there were 2 different recoveries uploaded, one for the ns and one for the 4g. If you find out that this doesnt work I can edit the post title to state not to flash...
my apologies didnt know there was a 4g version, just thought everyone was going willy nilly with the nexus s version
shabbypenguin said:
my apologies didnt know there was a 4g version, just thought everyone was going willy nilly with the nexus s version
Click to expand...
Click to collapse
Silly penguin, gotta click links first!
So are the different colors for just style or do they signify something?
sent from my sexy nexy 4 gizzle!
chewbz said:
So are the different colors for just style or do they signify something?
sent from my sexy nexy 4 gizzle!
Click to expand...
Click to collapse
Just personal preference... no difference otherwise
Related
Has anybody TRY flashing Modaco's "Paul's Rom" after ClockworkMod Recovery ? Do we have a green light to do so, or should we wait for further instructions ?
Thank you all.
I am not sure if this is safe yet since it is a different region. Wait until someone confirms though.
yvyv said:
Has anybody TRY flashing Modaco's "Paul's Rom" after ClockworkMod Recovery ? Do we have a green light to do so, or should we wait for further instructions ?
Thank you all.
Click to expand...
Click to collapse
he posted the download in the vibrant forum they have over there.. i'll test it
I'm actually a Modaco add-free member from my nexus one days but I don't see a " U.S Vibrant " section, he does how ever has a GalaxyS, I wonder if we good, I think paul is out for the weekend but I have a feeling we good to go..
Where is there a Vibrant forum? I only see a Galaxy S one on his site.
BigWorldJust said:
Where is there a Vibrant forum? I only see a Galaxy S one on his site.
Click to expand...
Click to collapse
i don't really remember where he posted it,
but i downloaded it and am gonna try it..
i'll look and see if i can figure out where it was
This is a holding topic for discussion of ROM compatability with the Samsung Vibrant / Captivate devices (Galaxy S variants).
I don't see any major reason why ROMs wouldn't be compatible, but I guess we'll find out soon enough. I may look into picking up a Vibrant so I can test future ROM releases on it.
Anyone have anything to add?
Click to expand...
Click to collapse
http://android.modaco.com/content/s...m/314109/vibrant-captivate-rom-compatibility/
Posted on Jul 21 2010, 20:04
alright flashing one of his deodexed versions that he posted in a thread for the vibrant
wish me luck..
if it works i'll find the link for you guys
link to modaco roms for vibrant
for those of you who wanna test it out.. booted up for me but i'm looking into functionality right now
How is it working?
Sent from my SGH-T959 using XDA App
rizzxx7 said:
How is it working?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Seems kinda like the one from MS_guru.. except a little more stable
i haven't been getting all the random reboots that are on ms_gurus, it still is buggy when you plug it into the computer (goes to the MTP Application.. ugh), wifi is working well (except rom manager still won't let me flash recovery through there because it says the wifi isn't stable enough or something), its pretty fast but i'd rather a stock rom than this
i noticed on that page i linked you guys to that they had a link for a download to a stockrom2.1.zip.. i'm going to test that one out as well
I am at work waiting for the word that its a go cause this stock build is killing me! Keep us posted!
Sent from my SGH-T959 using XDA App
one of the links provided has a thread where someone flashed this on a Vibrant and it stuck on boot.
Looks like Ryanolson7 has already gotten past that issue.. should work but I too will wait to hear
Made a backup in the mean while using nandroid and bought the premium version of Rom Manager to support Koush.
ryanolson7 said:
Seems kinda like the one from MS_guru.. except a little more stable
i haven't been getting all the random reboots that are on ms_gurus, it still is buggy when you plug it into the computer (goes to the MTP Application.. ugh), wifi is working well (except rom manager still won't let me flash recovery through there because it says the wifi isn't stable enough or something), its pretty fast but i'd rather a stock rom than this
i noticed on that page i linked you guys to that they had a link for a download to a stockrom2.1.zip.. i'm going to test that one out as well
Click to expand...
Click to collapse
If you have Recovery installed "update.zip" you don't have keep going back to rom manager and worry about "wi-fi" issues any more because is already installed in your system, just download quick boot from the market, allow su permision, reboot in recovery click reinstall packages and in 1 second you there...
The stock rom on that site is MS_gurus, not the real tmobile stock
yvyv said:
If you have Recovery installed "update.zip" you don't have keep going back to rom manager and worry about "wi-fi" issues any more because is already installed in your system, just download quick boot from the market, allow su permision, reboot in recovery click reinstall packages and in 1 second you there...
Click to expand...
Click to collapse
well i have recovery working by just going into stock recovery and flashing update.zip (clockwork recovery) but i was just testing out some ROMs that had potential to work on vibrants
rsfaze said:
one of the links provided has a thread where someone flashed this on a Vibrant and it stuck on boot.
Looks like Ryanolson7 has already gotten past that issue.. should work but I too will wait to hear
Made a backup in the mean while using nandroid and bought the premium version of Rom Manager to support Koush.
Click to expand...
Click to collapse
well that was a .zip of pauls rom that was themed as stock android.. i got the other one to boot called 'GalaxysDeodexed'.. still isn't stock quality though
do you guys know if we can flash his nandroid to our phones so we can have stock? if so, rsface, you should upload your nandroid somewhere and link us to it.. if you're willing to.. because the 'stock' roms out there are crap.. not even close to stock.
daweedk1991 said:
The stock rom on that site is MS_gurus, not the real tmobile stock
Click to expand...
Click to collapse
hopefully its not... they had it in a zip so it MIGHT not be his.. but i did see a link that links to MS_guru
oh and if you guys wanna get back to stock
check out this thread
http://forum.xda-developers.com/showthread.php?t=734475
Ryan, where did you put the .zip file ? SD card internally in the phone or external/removable card where movie and other stuff came..
Please be specific.
Thank you..
-------------------------------------
Sent via the XDA Tapatalk App
ClockworkMod 5 is available through ROM Manager.
Sent from my PG06100 using XDA App
I suggest asking a mod to move this to general asap..
Sent from my PG06100
I don't want to be "that guy" but every single device's Development forum (including this one) has a sticky thread about not posting questions in this forum. There is a sticky thread titled:
Thread DELETED/Locked??? >>>> This is DEVELOPMENT section not Q&A/General!!!! <<<<
This isnt a question, its a statement
Learn to read punctuation.
Sent from my PG06100 using XDA App
Anywho, is it good to flash?
Evo SHIFT
Enraged21 said:
Anywho, is it good to flash?
Evo SHIFT
Click to expand...
Click to collapse
I've flashed it. No issues thus far. It's blue!
HTCotta said:
I've flashed it. No issues thus far. It's blue!
Click to expand...
Click to collapse
Hate blue but seems to work fine.
gigermunit said:
Hate blue but seems to work fine.
Click to expand...
Click to collapse
Well once twrp is released publicly you can choose your color
Sweet thanks
crump84 said:
Well once twrp is released publicly you can choose your color
Click to expand...
Click to collapse
Looking foward to it .
iatedeadpeople said:
This isnt a question, its a statement
Learn to read punctuation.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
You're right, I absent-mindedly misworded my post. However the point about posts that aren't development to be posted on other subforums still stands.
Since you seem to be getting technical on my post, I will point out that the OP didn't have any form of punctuation in the post
Anyway, here is the official changelog from Koush's Google+ page:
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Click to expand...
Click to collapse
Also post bug reports here
Flashed this on wifey's shift last night, tried to run a backup from recovery. Was going good, then failed on /system. Tried running it again and it failed on /boot. Rebooted and phone is fine, however, I didn't have time to try anything else.
Has anyone else experienced back up issues with the new recovery?
Edit in: Resolved, her SD card was full...
jefbal99 said:
Flashed this on wifey's shift last night, tried to run a backup from recovery. Was going good, then failed on /system. Tried running it again and it failed on /boot. Rebooted and phone is fine, however, I didn't have time to try anything else.
Has anyone else experienced back up issues with the new recovery?
Click to expand...
Click to collapse
I back up through rom manager, not recovery. And its pretty solid.
Evo SHIFT
Enraged21 said:
I back up through rom manager, not recovery. And its pretty solid.
Evo SHIFT
Click to expand...
Click to collapse
You will retract that statement after it fails... lol
Sent from my PG06100 using Tapatalk
Enraged21 said:
I back up through rom manager, not recovery. And its pretty solid.
Evo SHIFT
Click to expand...
Click to collapse
Rom Manager is just a front end for the recovery. When you back up thru Rom Manager, it just scripts a reboot into recovery and run the nandroid backup...
jefbal99 said:
Rom Manager is just a front end for the recovery. When you back up thru Rom Manager, it just scripts a reboot into recovery and run the nandroid backup...
Click to expand...
Click to collapse
Correct so skip all the app non-sense and just boot into recovery and do your nandroid... One sure fire way to have **** go bad is taking too many unnecessary steps, i.e. using an app to start a nandroid... I have had so many issues with cwm borking nandroids that I barely trust it, if at all... and adding an app to that equation, you are setting yourself up for an epic fail... I trust my fingers and brain to hit the right buttons... Not an app...
Sent from my PG06100 using Tapatalk
I use Rom Manager to do backups only when I need to name them. I've had good luck with it on my phone. But that being said. I've also had real bad experiences on other devices, really bad . Like every backup made thru RM being bad, and failing. But if I went thru recovery all was good. So it's not a failsafe method IMO.
MikShifted on XDA Premium APP
TEAM MiK
Mik ROMs Since 3/13/11
Yeah well that's what I meant.
Evo SHIFT
Prboy,fyi don't really need RM to name backups just ooen root explorere or any file manager go to cwm > backup > and rename
Sent from my PG06100 using xda premium
FdxRider said:
Prboy,fyi don't really need RM to name backups just ooen root explorere or any file manager go to cwm > backup > and rename
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
+ 1... I usually add an abbreviation at the end and have had no probs...
Sent from my PG06100 using Tapatalk
Alright, who has some spare time and wants to test a "ROM" (read: hacked together") zip?
That doesn't sound completely sketchy at all...you'll have to provide more details.
teh roxxorz said:
That doesn't sound completely sketchy at all...you'll have to provide more details.
Click to expand...
Click to collapse
Haha, I've been getting that for the past few days on a thread about a script that pulls messages. I've "built" a kang of a kang and I wanted to see if anyone wanted to test it.
pspunderground said:
Haha, I've been getting that for the past few days on a thread about a script that pulls messages. I've "built" a kang of a kang and I wanted to see if anyone wanted to test it.
Click to expand...
Click to collapse
So you're kang squared then...So then what's the original rom it was built off of, and aosp/sense? People are gona wana know these things.
teh roxxorz said:
So you're kang squared then...So then what's the original rom it was built off of, and aosp/sense? People are gona wana know these things.
Click to expand...
Click to collapse
I'll list some of the basics.
AOSP based
Base ROM: Ultimate Droid 3.3.1 Gingerbread
^Removed all extras and non-allowed apps
^like Fancy Widget
Added some init.d scripts for faster boot
no bootanimation
The purpose: To use all of the add-ons and customizations
^that I have found over the months
^like two tone SMS app
^CPU Settings
^Modified Launcher2
^etc, etc.
EDIT: not "kang squared"
EDIT2: kang²
pspunderground said:
I'll list some of the basics.
AOSP based
Base ROM: Ultimate Droid 3.3.1 Gingerbread
^Removed all extras and non-allowed apps
^like Fancy Widget
Added some init.d scripts for faster boot
no bootanimation
The purpose: To use all of the add-ons and customizations
^that I have found over the months
^like two tone SMS app
^CPU Settings
^Modified Launcher2
^etc, etc.
EDIT: not "kang squared"
EDIT2: kang²
Click to expand...
Click to collapse
There ya go...I can't do super scripts. By the way, a lot of people here don't like ultimate droid and practically forbidden to speak of it, so you may be based... forewarned.
teh roxxorz said:
There ya go...I can't do super scripts. By the way, a lot of people here don't like ultimate droid and practically forbidden to speak of it, so you may be based... forewarned.
Click to expand...
Click to collapse
Yeah. I may lie, and say it CyanogenMod 7.9
I'm always game for testing new ROMS, pm me if you're still looking
http://min.us/m3CijQyEF
Here is a link if anyone wants to test. Please post results on this thread.
pspunderground said:
http://min.us/m3CijQyEF
Here is a link if anyone wants to test. Please post results on this thread.
Click to expand...
Click to collapse
I'll bite and try it out. I'll examine the zip and flash it, give downloading now
Sent from my PC36100 using xda premium
tropicalbrit said:
I'll bite and try it out. I'll examine the zip and flash it, give downloading now
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Ok. I'll post what I have done on the ROM.
Sent from my PC36100 using XDA App
tried flashing, got this error:
E:Board does not support mtd utils.E:Failure atline 77:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
In case im not the only one (i think its due to my recovery menu) i found a fix here:
http://forum.xda-developers.com/showpost.php?p=10963396&postcount=3117
Also found a fix in my dev menu in recovery so nvm haha
Sent from my PC36100 using XDA App
dsuffern said:
tried flashing, got this error:
E:Board does not support mtd utils.E:Failure atline 77:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
In case im not the only one (i think its due to my recovery menu) i found a fix here:
http://forum.xda-developers.com/showpost.php?p=10963396&postcount=3117
Click to expand...
Click to collapse
What recovery are you using?
EDIT: You found a fix!
Sent from my PC36100 using XDA App
I need a few more testers, so if you have some spare time, please try out the ZIP on the first page.
pspunderground said:
What recovery are you using?
EDIT: You found a fix!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm using Ra 3.07 recovery but yes, found a fix for it
dsuffern said:
I'm using Ra 3.07 recovery but yes, found a fix for it
Click to expand...
Click to collapse
Ah, Ok. I'm using the Ra-Style Recovery, so I was wondering why it wasn't "working".
Hey folks,
I am sharing the latest CWM recovery images; CWM 6.0.1.9, while the one available in ROM Manager is 6.0.1.0
To be straight, I used Koush's Recovery Builder to build these latest recovery images in both, touch & non-touch variants. And so I do not take any credit, all of it to Koush. Also, I didn't publish a thread for this in development section since I didn't perform any development on this. :angel:
Downloads
ClockworkMod 6.0.1.9 Touch Recovery
ClockworkMod 6.0.1.9 Non-Touch Recovery
Click to expand...
Click to collapse
How to build on your own?
Visit the Recovery Builder
Click on the "Existing Devices" tab.
Now under the Existing Devices dropdown, select "crespo".
Tick "Touch Recovery" option if you desire for the touch variant, otherwise do not touch it.
Now click on the blue colored "Build" tab.
The page will then prompt you with a reference build ID, take note of it.
Now continue to build server.
Look for the corresponding build ID.
Once its done, click on it.
You can now download your "recovery.img" build.
How to flash?
For those who know already know how to flash recovery via fastboot, type this for flashing touch recovery:
Code:
fastboot flash recovery cwm-crespo-6.0.1.9-touch.img
and for non-touch, type:
Code:
fastboot flash recovery cwm-crespo-6.0.1.9-touch.img
If you are new to flashing via fastboot then, you shall visit my guide for simplified and step-to-step instructions.
Flashable zip please?
USB mount working?
I built it myself, but USB Mount didn't worked.
Can you please provide a changelog?
I'm using the touch one for the ns4g. Maybe I'm just missing it but there's no way to do a battery wipe in cwm? Unless they took that out?
Sent from my Nexus S 4G using xda premium
903tex said:
I'm using the touch one for the ns4g. Maybe I'm just missing it but there's no way to do a battery wipe in cwm? Unless they took that out?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
You dont need to wipe battery stats, thats myth bull****.
Sent from SpeedMachine i9023
sidnoit22 said:
Flashable zip please?
Click to expand...
Click to collapse
I doubt its stability yet,
Articudos said:
USB mount working?
I built it myself, but USB Mount didn't worked.
Click to expand...
Click to collapse
Yes, its not functional.
903tex said:
I'm using the touch one for the ns4g. Maybe I'm just missing it but there's no way to do a battery wipe in cwm? Unless they took that out?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I don't think that they took it out since its present in N4. Must be a building error.
To sum up, I will ask a mod to close this thread.
alen1901 said:
You dont need to wipe battery stats, thats myth bull****.
Sent from SpeedMachine i9023
Click to expand...
Click to collapse
I agree to that
DJBhardwaj said:
I agree to that
Click to expand...
Click to collapse
Well guess it times for a new battery....
Sent from my Nexus S 4G using xda premium
Disclaimer
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
What is It
This is the latest version of CWM Touch Recovery (6.0.2.8) that I've built for the Touchpad.
It is a flashable zip so simply download the file and flash in your installed recovery.
It is also should be compatible to use with ACMEInstaller3.
I've uploaded the Touch version of CWM but touch doesn't work. However this version of CWM still has the enlarged icons like CWM Touch Recovery. It's really a CWM Touch Recovery but touch just isn't working yet. Touch should be working sometime this weekend. You can still navigate in this recovery with the hardware keys.
Changelog
CWM Touch 6.0.2.8 has the ability to "Install zip from sideload" while jcsullin's doesn't.
This allows you to use adb to install packages from your computer. Essentially you choose that option than run adb sideload flashable_zip_name (where flashable_zip_name is the path to the zip you want to flash). This prevents you from having to go into USB mode to copy over files to flash. Instead you just activate this and get it directly installed.
This was an intentional thing on jcsullin's recovery but has been fixed/enabled in this version (so basically not a problem with CWM itself).
This is probably not going to really sway very many of you but just keep in mind there are probably plenty of under the hood changes and ones I simply don't know.
Obviously, now this is the touch version of CWM but touch isn't working yet. Just use the hardware keys for now.
If I get any further changes I will post them here.
Downloads
Download No Touch Version Here
Download Touch Version Here
Bugs/Issues
If you have any issues please feel free to post them in this thread.
If someone thinks I should add more information to the OP just ask.
Hi, can you tell us what the difference is between your version and jcsullins version 6.0.1.9 please..
Thanks
these version numbers always confuse me. b/c if i look at cwm on google play store they list:
Updated:
February 16, 2013
Current Version:
5.5.2.3
is cwm 6x a beta or something? i can't find any info on the cwm website, or a changelog
x000x said:
these version numbers always confuse me. b/c if i look at cwm on google play store they list:
Updated:
February 16, 2013
Current Version:
5.5.2.3
is cwm 6x a beta or something? i can't find any info on the cwm website, or a changelog
Click to expand...
Click to collapse
I think what you are referring to is Rom Manager which is specifically designed to work with CMW much like Goo Manager is designed to work with TWRP an alternative to CMW.
The version I was referring to was written by jcsullins to overcome earlier versions corrupting the system along with moboot and the latest cm10 which most other versions for our TouchPad appear to be based on.
Works great so far! Thanks! :highfive:
-SGA- said:
Works great so far! Thanks! :highfive:
Click to expand...
Click to collapse
SGA can you tell us how this differs from jcsullins version. Thanks.
haha you're absolutely right sstar. when trying to find changelogs etc, i clicked on it through the clockwork website, and thought it was the same thing
sstar said:
Hi, can you tell us what the difference is between your version and jcsullins version 6.0.1.9 please..
Thanks
Click to expand...
Click to collapse
There is no official changelog for CWM so the answer is no I don't know the changes right now.
-SGA- said:
Works great so far! Thanks! :highfive:
Click to expand...
Click to collapse
Thanks for the feedback!
x000x said:
haha you're absolutely right sstar. when trying to find changelogs etc, i clicked on it through the clockwork website, and thought it was the same thing
Click to expand...
Click to collapse
It appears koush doesn't really say what every version has in it.
Remolten said:
There is no official changelog for CWM so the answer is no I don't know the changes right now.
Thanks for the feedback!
It appears koush doesn't really say what every version has in it.
Click to expand...
Click to collapse
Thanks for your reply but in the op you've said that you built this, so what changes have you made?
Re: [RECOVERY] [Remolten's CWM 6.0.2.8] [02-28-13]
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Anyone know Koush? If so, ask him for some details and post them here.
-SGA- said:
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for your reply . My understanding was that jcscullins developed one that did not corrupt the system as posted by nevertells.
Maybe I'm wrong, just don't like the idea of flashing something the poster/ developer can't give any details about.
-SGA- said:
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
SGA explains it perfectly.
sstar said:
Thanks for your reply . My understanding was that jcscullins developed one that did not corrupt the system as posted by nevertells.
Maybe I'm wrong, just don't like the idea of flashing something the poster/ developer can't give any details about.
Click to expand...
Click to collapse
I can't give any information as I don't know what koush edits and such in CWM I just built it for the Touchpad.
Only change that I can vouch for is the version has been bumped.
You can see the commits do dot really go into any kind of detail as to what the changes are: https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
Many of the moves to a higher version are only committed with a version number update.
-SGA- said:
You can see the commits do dot really go into any kind of detail as to what the changes are: https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
Many of the moves to a higher version are only committed with a version number update.
Click to expand...
Click to collapse
Noticed that too.
Also I noticed that the latest version of CWM for the Nexus devices is 6.0.2.3 so I'm not sure how the version incrementals work since CWM is available on loads of different devices. I've successfully built a CWM Touch for the Touchpad with no touch (however it has the enlarged icons but no touch yet). Will post soon if you just want a recovery with enlarged look.
Added changes (changelog) from jcsullin's CWM6 release.
Remolten said:
Added changes (changelog) from jcsullin's CWM6 release.
Click to expand...
Click to collapse
Thanks, where are they?
sstar said:
Thanks, where are they?
Click to expand...
Click to collapse
Sorry took time to write look for section called changelog.
Re: [RECOVERY] [CWM 6.0.2.8] [No Touch] [02-28-13]
Is there a way to configure Rom Manager to recognize this version of CWM Recovery?
Sent from my cm_tenderloin using xda app-developers app
masterosok said:
Is there a way to configure Rom Manager to recognize this version of CWM Recovery?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I would have to become the CWM Recovery Device Maintainer which isn't going to happen anytime soon as I'm not a prominent developer yet
Short answer is not yet.
Why do you need to use Rom Manager? Just download the file and flash in your current version of CWM Recovery.