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
This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.
This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.
Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.
Some Notes:
It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.
Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)
Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.
Download
http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk
md5: f0a03b50e08faa09e8d49e7224b0cd0f
After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.
As I release new versions, I'll updated this OP.
EDIT: A number of users have been confused by the red outlined banner at the bottom. This banner replaced the links to my other apps a few versions back (2.7 something). The presence of that banner does not mean you've lost your premium license. The next beta will probably display a thank you banner instead of the one shown now if the premium features have already been purchased.
EDIT: V2.99beta3 is available at the link above. Much of the underlying code was changed and needed much testing. I believe it is pretty stable now. It supports TWRP 2.1.1!
For me (future changelog)
Euclid's Brother said:
This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.
This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.
Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.
Some Notes:
It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.
Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)
Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.
Download
http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk
md5: eb8302db485aa47df6f342698db6b820
After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.
As I release new versions, I'll updated this OP.
Click to expand...
Click to collapse
Looks Awesome I purchased this as as soon as walked out of bestbuy 8month ago this app has come a long way I just want to thank you for all you work its really a great app!
Sent from my Inspire 4G using Tapatalk
I will make custom rom for A100 , give me some time.
Just been very busy.
EDIT
Full A100 custom rom is in A100 section
Euclid's Brother said:
This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.
This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.
Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.
Some Notes:
It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.
Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)
Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.
Download
http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk
md5: eb8302db485aa47df6f342698db6b820
After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.
As I release new versions, I'll updated this OP.
Click to expand...
Click to collapse
Can I install it on top of the market version or Should I uninstall that first?
I think you probably can, but have not tried it. Give it a shot and let us know. Worst case is that it will say you have to uninstall the previous version.
Sent from my SPH-D710 using Tapatalk
anikiup said:
Can I install it on top of the market version
Click to expand...
Click to collapse
Yes.
---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------
Any idea if TWRP 2.1.0 supports the extendedcommand file?
elborak said:
Yes.
---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------
Any idea if TWRP 2.1.0 supports the extendedcommand file?
Click to expand...
Click to collapse
Unfortunately, it does not. I will add recognition to my app for TWRP, but it will not work with the premium features unless the dev add support for extendedcommand.
elborak said:
Yes.
---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------
Any idea if TWRP 2.1.0 supports the extendedcommand file?
Click to expand...
Click to collapse
Extended command actions are locked down to clockwork mod based recoveries. There is a key need to use that function. But there are other apps that work with twrp that basically do the extended command goodies.
Sent from my Iconia A500 using Tapatalk 2
^ In what way are they "locked down" to CWM?
@pimpmaneaton
In which version of CWM did they lock it down? It works fine in thor's 1.7, and in hbwelches version that was built for the A200 (can't remember which version he based it on).
It also works on fine on my Sprint Epic Touch 4G using a custom built CWM (not from ROM Manager). I created a test script myself and it ran fine. That was based on 5.0.2.4 I believe. I have 5.0.2.8 installed now, i'll try it again with that one and see.
extendedcommand support really isn't much more than looking for the file and executing it like any edify script. package_extract type commands shouldn't be allowed, since it's not part of a package, but things like ui_print, format, run_program, install_zip, set_permission, symlink, etc.. shouldn't be too hard to do.
I've been trying to find more info on how Open Recovery Script works. To see if i can use that.
installed fine on top of v2.74 -paid version - couple root beers on their way 0158-3554-2226-2151-1639
Euclid's Brother said:
I've been trying to find more info on how Open Recovery Script works. To see if i can use that.
Click to expand...
Click to collapse
If you find some interesting documentation/websites, would you mind sharing them here?
Although i would prefer normal extendedcommand support in twrp because seen the comments on review.cyanogenmod there is no change open recovery script will get merger to cwm. Besides that, if I understood it correctly, extendedcommand is not limited at all to rommanager. Kouch just changed his licence statement in the code to stipulate that.
Taptalked u see
If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.
Euclid's Brother said:
If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.
Click to expand...
Click to collapse
I just tried it, works fine although i had to read the op here again to realize i needed to put the recovery image in the correct directory. A small embedded browser would be nice. Or at least a help function/about under the overflow menu.
I used it to flash thor 1.7 cwm over twrp, without auto reboot to recovery. I have used the free market function only once before so i can't really tell you the differences/improvements.
Acer A500 btw.
Taptalked u see
Euclid's Brother said:
If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.
Click to expand...
Click to collapse
I'm use bêta 2.99 . I've tested 3 time full backup . 2 on 3 are working without problème. 1 time,reboot to recovery and reboot système without backup.
I've thor 1.7 cwm with flexreaper R11.
Your app are perfect.
Thanks
Sent from my A500 using Tapatalk 2
just installed and upgraded from thor 1.3.4 to 1.7...updating and flashed fine, rebooted into recovery and everything went perfect...thanks so much!
Zatta said:
I just tried it, works fine although i had to read the op here again to realize i needed to put the recovery image in the correct directory. A small embedded browser would be nice. Or at least a help function/about under the overflow menu.
I used it to flash thor 1.7 cwm over twrp, without auto reboot to recovery. I have used the free market function only once before so i can't really tell you the differences/improvements.
Acer A500 btw.
Taptalked u see
Click to expand...
Click to collapse
I forgot to this mention in the OP. To install a recovery that's not automatically downloaded by the app, you place it in the root of your external sdcard and name it "recovery.img" (just like the old version). HOWEVER, if you don't have an external sdcard, then it looks in /sdcard/.AcerRecoveryInstaller instead.
I'm going to work on this more for beta2 and have it able to use multiple custom images. So you can have one or more additional recovery images instead of just "recovery.img"
micky387 said:
I'm use bêta 2.99 . I've tested 3 time full backup . 2 on 3 are working without problème. 1 time,reboot to recovery and reboot système without backup.
I've thor 1.7 cwm with flexreaper R11.
Your app are perfect.
Thanks
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I guess it's possible, for whatever reason, the sdcard didn't mount that one time. If that happens again, please PM me the file located at /cache/recovery/last_log after it boots back into android.
Thanks!
ok.
Your app is fantastic so i've purchas the premium version .
Thanks
Best regards
Envoyé depuis mon A500 avec Tapatalk
Hi,
I have CWM 5.0.0.6 on my pad, which works ok. However, I'd like to have the latest version and I've even donated for the touch version. Now, I've tried installing the recovery through terminal and through Rom Manager. Both says everything's fine, but the recovery still 5.5.0.4. Rom Manager, however, tells me it's 5.8.2.1 . I'd be inclined to think the recovery console just states the wrong version, but the lack of touch support is a dead giveaway.
An other indication is that "reboot into recovery" just reboots my tablet, but does not start the recovery.
Anyone seen this before? Know a way around it?
I think I used RecoveryInstaller to install the recovery when I first installed it. This was before it had official TF101 support. The recovery console, when entered manually, seems to work fine, though, as my ICS was installed and then upgraded through it.
tiwas said:
Hi,
I have CWM 5.0.0.6 on my pad, which works ok. However, I'd like to have the latest version and I've even donated for the touch version. Now, I've tried installing the recovery through terminal and through Rom Manager. Both says everything's fine, but the recovery still 5.5.0.4. Rom Manager, however, tells me it's 5.8.2.1 . I'd be inclined to think the recovery console just states the wrong version, but the lack of touch support is a dead giveaway.
An other indication is that "reboot into recovery" just reboots my tablet, but does not start the recovery.
Anyone seen this before? Know a way around it?
I think I used RecoveryInstaller to install the recovery when I first installed it. This was before it had official TF101 support. The recovery console, when entered manually, seems to work fine, though, as my ICS was installed and then upgraded through it.
Click to expand...
Click to collapse
What is so difficult about posting in the right section?
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
What is so difficult about posting in the right section?
Click to expand...
Click to collapse
How difficult would it be to try to be nice in the post? I was conflicted on whether to post in the QA section of the development section as it very well could be a bug more than a user question.
But...since I ended up with this section, it'd be great if a mod could move the post if it is in fact in the wrong one.
tiwas said:
How difficult would it be to try to be nice in the post? I was conflicted on whether to post in the QA section of the development section as it very well could be a bug more than a user question.
But...since I ended up with this section, it'd be great if a mod could move the post if it is in fact in the wrong one.
Click to expand...
Click to collapse
It's difficult to be nice about it because it's incredibly frustrating. If you're starting a thread in development to ask a question, it's in the wrong place. Period. The only place you should be discussing bugs in the development section is a thread for a specific ROM, kernel, etc.
As far as your problem goes, if you looked around any of the ROM of recovery threads you would see that ROM Manager is nothing but trouble for the TF. That's probably what screwed you up in the first place. If you want the latest recovery for your Transformer you need to use one of these:
http://forum.xda-developers.com/showthread.php?t=1213723
http://forum.xda-developers.com/showthread.php?t=1577929
I've been using the JvS CoRp one, and have been very happy with it.
philburkhardt said:
It's difficult to be nice about it because it's incredibly frustrating.
Click to expand...
Click to collapse
Thanks for the links - I'll look into that. Regarding the frustration, I hear you. I'm a mod at some forums, and I know the feeling when someone's posting all the wrong things in all the wrong places. Didn't do it on purpose Actually, I knew it would probably be answered quicker in the QA section, but as I thought it might have a pinch of bug in it I opted for the slower way
Cheers, and have a good day
As I posted in the dev thread let's bring the chit chat into the general forum and keep the dev thread on topic and clear for people to help the devs move this rom forward.
So this thread is for all the GENERAL CM9 discussion.
Everybody suck
Sent from my GT-I9300 using xda premium
Informative.
Sent from my GT-I9300 using Tapatalk 2
Despite this, people will still go to the development thread to ask questions, request features, banal talks... etc.
Maybe use this thread to summarise FAQ's found in the other thread (and subsequently this thread)
Edit the first post to stay on top of things?
In summary, no exfat on CM9, use ext4 format if you must have files over 4Gb (that's all I know so far, I don't have CM9 installed yet)
*subbed*
Get xplod to put a link to this thread in the development OP? A link to that thread from here wouldnt hurt either
is there a way to block calls in cm9? (without having to install an apk from the market)
I don't have phone yet; however, was wondering if on cm9, do you still have the same camera function as with touchwiz, like fast burst, best shot, taking pic while recording? I don't really care about losing s voice.
jblazea50 said:
I don't have phone yet; however, was wondering if on cm9, do you still have the same camera function as with touchwiz, like fast burst, best shot, taking pic while recording? I don't really care about losing s voice.
Click to expand...
Click to collapse
Bot yet i think but soon u will have them al
Just wondering if anyone knew of a video player with live previews (in thumbnails) like the original one.
By the way great rom, I moved from Galaxy S II and was surprised to find it on the S III so fast.
own4d said:
Maybe use this thread to summarise FAQ's found in the other thread (and subsequently this thread)
Edit the first post to stay on top of things?
In summary, no exfat on CM9, use ext4 format if you must have files over 4Gb (that's all I know so far, I don't have CM9 installed yet)
Click to expand...
Click to collapse
Nice idea. Once I'm back from holiday on the weekend I'll get to work bringing all the known fixes, work arounds ,tweaks and tips into this thread. Would take an age doing it on the phone.
Still flashing nightly builds whilst away
Sent from my GT-I9300 using Tapatalk 2
P1n3apqlExpr3ss said:
*subbed*
Get xplod to put a link to this thread in the development OP? A link to that thread from here wouldnt hurt either
Click to expand...
Click to collapse
Will do.
Sent from my GT-I9300 using Tapatalk 2
Hey can any one extract the crt animation ( screen of &on) frm this rom & make a flashable zip file ?? Plzz Plzz
I want 2 use in my stock rom...
Plzz
Sent from my GT-S5570 using XDA
Ph3rOn!xX said:
Hey can any one extract the crt animation ( screen of &on) frm this rom & make a flashable zip file ?? Plzz Plzz
I want 2 use in my stock rom...
Plzz
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
Next time try using Google..cuz thats what i did and it was the first link
http://forum.xda-developers.com/showthread.php?p=27549498
k786 said:
Next time try using Google..cuz thats what i did and it was the first link
http://forum.xda-developers.com/showthread.php?p=27549498
Click to expand...
Click to collapse
I don't think that's what he was looking for. And I'm not sure if you can just apply the crt animations from CM9 to stock ROM.
Has anyone managed to get MTP to work in OS X? Android file Transfer doen't detect device. Xplodwild said it works but not for me here!
sinkingfish said:
Has anyone managed to get MTP to work in OS X? Android file Transfer doen't detect device. Xplodwild said it works but not for me here!
Click to expand...
Click to collapse
If it's like on linux i guess you need to install an mtp library to get it working (i.e. mtpfs).
Tectas said:
If it's like on linux i guess you need to install an mtp library to get it working (i.e. mtpfs).
Click to expand...
Click to collapse
Android File Transfer worked fine on stock using PTP and works great with my friends Gnex. Googled mtpfs for OS X but nobody seems to have had any success.
Hope codeworkx & XpLoDWilD are able to get mass storage working.
Sent from my GT-I9300 using XDA
Would Android beam on CM9 work with S-beam? Ie someone on stock samsung rom uses s-beam to communicate with me on android bean, no issues?
Could we use NTFS on the 64Gb SD card on the GSIII using CM9?
If not.. could I somehow parition the microSD card into x2 32Gb partitions, one ext4 the other ExFAT that way I can run with this until one of the other prevails? I only like copying data once....
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.