[ATTN] ROM Manager 4 + ClockWorkMod 2.X causes Touchscreen Brick - Desire HD General

Hello All,
I would like to report that the newest version of ROM Manager which I have installed on my device caused a touch-screen problem.
I transferred the ROM to my SD card and used the newest version of ROM Manager to flash it.
After it was done, I turned on my device and found out the touchscreen completely broke. I could see the visuals on my screen, but I could not click on any buttons and the touchscreen is rendered useless.
I tried to manually enter the bootloader (switching off the phone, click once on the power button and hold on the vol down key until you see a white screen than click to recovery) to flash another ROM, but no matter which ROMs I flashed, the touchscreen did not work at all.
So I decided to RUU my phone back to it's original condition and send back to HTC (RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed)
and after it complete the flash, the touchscreen works again.
So I would just like to conclude that the newest version of ROM Manager caused problems with ClockworkMod 2.X
Thanks.

Many ROM's HAVE to be flashed using version 3+ of Clockwork recovery.
Based on the fact that there are still a LOT of people that are using the same combination I would say this is a rare occurrence.
Thank you for your post but I urge people not to take this as a definite. May I ask why you chose to use 2X not 3x of recovery?

Mr_JMM said:
Many ROM's HAVE to be flashed using version 3+ of Clockwork recovery.
Based on the fact that there are still a LOT of people that are using the same combination I would say this is a rare occurrence.
Thank you for your post but I urge people not to take this as a definite. May I ask why you chose to use 2X not 3x of recovery?
Click to expand...
Click to collapse
For me ANY of newer recoveries higher than OLD ONE 2.5.1.3 doesnt work proeprly :/ Thay don`t restore my roms properly. I wish i could have newer one but all ot them causes bootlopps or tones of FCs after restore.
Thats why IM USING 2.5.1.3

Krzysiec said:
For me ANY of newer recoveries higher than OLD ONE 2.5.1.3 doesnt work proeprly :/ Thay don`t restore my roms properly. I wish i could have newer one but all ot them causes bootlopps or tones of FCs after restore.
Thats why IM USING 2.5.1.3
Click to expand...
Click to collapse
I used to get that, there's a certain way of doing it that I found works.
Restore a backup using the older CWM recovery
Boot into the ROM and flash CWM 3.x using ROM Manager
Backup the ROM using ROM Manager
ROM should now restore properly.
I've got the 405.3 version of Sense rooted as a backup that didn't work on CWM 3.x but after doing it this way it works fine.
If you have more than one backup then flash the older CWM and repeat the above steps. The way the older versions backup seems to cause problems if you try to restore using a 3.x CWM.
Sent from my Desire HD using XDA App

Cwm 3.x works fine with me, when the backup isn't from à 2.x one...
Sent from my Desire HD using XDA App

Me too, cwm 3.x works fine for me
Sent from my Desire HD using XDA Premium App

Related

[q] omg need help. Mytouch 4g stuck on mytouch 4g screen.

Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only
Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?
If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App
3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.
i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.
hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?
OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.
I used the .zip file to restore my mytouch, but now it wont go into Hboot.
I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you
Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas

cwm failure

I have CWM 3.0.0.5 and I am unable to load any new roms now. I do not know if this is a common occurrence but everytime I try to boot into recovery, I get a quick flash of the htc logo and it just keeps going to the bootloader. Is this happening to anyone else?
Not sure what is causing it but when I had that problem I first booted to the ROM I had and went copied the *.img file for clockworkmod 3.0.0.5 to /clockworkmod/download/mirror1.kanged.net/recoveries/ by mounting my Desire Z as a disk.
I found a copy here of that *.img file in these forums
There is no reason to flash cw3 like that anymore. You can simply do it on rom manager now. You can only flash roms that support clockwork mod 3.
Sent from my HTC Vision using XDA App
Yep. I am guessing he formatted his SD card which happened to me once. Nice to know though that you can use this as an alternate method if anyone arrives at the same situation
Sent from my HTC Vision using XDA App
I didnt format my sd. also, it was installed via rom manager. I loaded virtuous and everything works great, but when I went to load up cm7, it wouldn't load into cwm.
the.goodhumorman said:
I didnt format my sd. also, it was installed via rom manager. I loaded virtuous and everything works great, but when I went to load up cm7, it wouldn't load into cwm.
Click to expand...
Click to collapse
Someone may need to correct me on this but at the top of my head there are certain ROMs that will not work properly with 3.0.0.5. You may need to downgrade it to 2.5.1.3.
Better clarify this first before going ahead.
iamthechickengod said:
Someone may need to correct me on this but at the top of my head there are certain ROMs that will not work properly with 3.0.0.5. You may need to downgrade it to 2.5.1.3.
Better clarify this first before going ahead.
Click to expand...
Click to collapse
The new 3.0.0.5 CWM recovery thru Rom Manager now supports all 2.2 and 2.3 roms. No need to use 2.5.1.3 anymore.
Sent from my HTC Vision using XDA App

[Help] Did I Brick My Mytouch4g?

MODS: I am unsure of where to post this so sorry for the trouble.
So I work for Tmobile and love showing off my rooted mytouch 4g in all its glory.
So I requested a warranty exchange and got a TAIWAN VERSION w/ GOOD SCREEN in return. Like Day and Night.
Upon Receiving my warranty exchange phone it was 2.2.1. I attempted the same Visionary Root Process, (however was there some extra file i needed to DL? i forget)
After rooting my new phone, S-Off, I had flashed FAUX stock kernel 0.4.0b.
THEN THIS HAPPENS:
I cant get past the mytouch 4g splash screen. The first logo that appears. It gets stuck or bootloops. I can HBOOT and get into recovery 3.0.0.5
This is all i can do...i already asked for another warranty exchange...but in the meanwhile..how can i fix this problem or what did i do wrong?
ALSO can you backup one mytouch 4g and load it back up on another mytouch 4g with the same sd card? Thanks!
I had this problem with my MT4G when I flashed his kernal. It seems that his kernals are not designed to work with every 4g device. I hope you did a nandroid backup on the device. I was never able to get past the mytouch splash screen with his kernals
Sent from my HTC Glacier using XDA App
Well, at since you can get into recovery there should be a number of things you can do to get your phone to boot.
Download a new ROM to flash, if you are on clockwork 3 then you need CM7.
Clockwork has usb drive ability, turn it on, transfer the ROM then flash.
If you can get into HBoot or Recovery on ANY phone, you're safe. Hell, if you can't get into HBoot, your phone wouldn't even start up since HBoot is basically the equivalent to BIOS.
THE VERSION OF CLOCKWORKMOD RECOVERY YOU USE IS CRITICAL!!!
The version you are using is for Android 2.3 only.
Flash a v2 Recovery with adb or fastboot and reinstall your kernel, or install CM7.
HTC Glacier CM7 41
I am trying to do this. How would I get my comp.to.recognize the devise. Sometimes it says mass storage device detected sometimes not. So I need cm7 rom to b able.to boot?
Sent from my HTC Glacier using XDA App
Tiltpoet said:
I am trying to do this. How would I get my comp.to.recognize the devise. Sometimes it says mass storage device detected sometimes not. So I need cm7 rom to b able.to boot?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
If you've ever connected it via USB, it should have installed the drivers automatically (at least on Windows). I think the ADB driver only installs if you had "USB Debugging" checked. Mass Storage usually only refers to mounting the SD card; the driver for ADB is different. Look for something like Android Phone or Android ADB Interface in your device manager (again assuming Windows).
If you have ADB set up, try running the adb devices command. If it spits back the serial number of your phone, you should be okay to proceed.
Don't exchange the phone, fix it...
Just use another phone to copy the latest CM7 to the root of your sdcard and flash, if that doesn't work do the same thing with a PD15IMG.zip file to the root of your sdcard, hboot and restore to stock.
I have no problem with someone doing a warranty exchange for a hardware issue, but if you break your phone, don't make someone else pay for it...
i ended up solving the problem by doing what some of you had suggested. I flashed CM7 and WAH-LaH! when the phone got past the splash screen into CM7 i was on cloud 9.
Now What are the benefits of running CM7? as opposed to going back to Sense w/ Faux kernel again?
PLUS
how would i go back to a sense type rom again? would i go back into rom manager and flash a different recovery?
XDA you have been so helpful!
___bonus__also the haptic feedback on this phone was not as strong as my original..though idk if its just me or not..should i call tmobile and stop shipment of the OTHER phone? how is it i have a taiwan version plum W/ good screen?
There are no Sense-based Gingerbread (Android 2.3) ROMs available now ... Best practice its to make a Nandroid backup of CM7 with your installed CWM Recovery, then flash a version 2.x of CWM Recovery to install any Froyo (Android 2.2) based ROM.
HTC Glacier CM7 41
Tiltpoet said:
i ended up solving the problem by doing what some of you had suggested. I flashed CM7 and WAH-LaH! when the phone got past the splash screen into CM7 i was on cloud 9.
Now What are the benefits of running CM7? as opposed to going back to Sense w/ Faux kernel again?
PLUS
how would i go back to a sense type rom again? would i go back into rom manager and flash a different recovery?
Click to expand...
Click to collapse
Good to see it is working.
Its mostly personal preference at this point. Sense on the MT4G is pretty responsive and has some nice features. CM7 has its own tweaks and features. You loose the sense widgets but many can be replaced with alternatives in the market. You gain and loose relative in both ROMs So try out both and decide.
Use ROM Manager app to flash a new recovery. One of the 2. versions, then flash a froyo based ROM.
what about flashing kernels..are those "roms"
is cm7 itself pretty battery efficient? i still downloaded setcpu and set it to 11---.
2.XXX ..u mean like 2.5.1.4 for example..sorry not lookin at the phone atm.
++bonus
i also dl the cynogyn updater or wut not..wut url do i add for themes?
Tiltpoet said:
what about flashing kernels..are those "roms"
is cm7 itself pretty battery efficient? i still downloaded setcpu and set it to 11---.
2.XXX ..u mean like 2.5.1.4 for example..sorry not lookin at the phone atm.
++bonus
i also dl the cynogyn updater or wut not..wut url do i add for themes?
Click to expand...
Click to collapse
Kernels are not ROMs, the kernel is the underlying software of an OS. The kernel talks to the hardware and lets different parts of the OS communicate. Kernels are ROM specific, or Framework specific. A sense ROM can not use a AOSP kernel and vice versa.
CM ROMs can be good on battery, or not. It all depends on personal use and how you set it up.
That is a good recovery to use when flashing sense ROMs.
Not sure about the updater. If it is the one I am thinking, it hasn't been updated in a while. I think it has been abandoned in favor of ROM Manager. CM updater did come in some of his older ROMs, before ROM manager became the norm.
So I can or cannot flash fauxs kernel. I really liked the smartass profile. Also..I'm on cm 7 now...y do I get force closes on my market.
Sent from my HTC Glacier using XDA App
As people have already said, you used the wrong version of clockwork, also, use clockwork to flash a new rom. And make sure you use the right version.
Tiltpoet said:
So I can or cannot flash fauxs kernel. I really liked the smartass profile. Also..I'm on cm 7 now...y do I get force closes on my market.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Try fix permissions. If that does not work, do a full wipe (factory reset). If that still does not work, try re-flashing the ROM.
If you flashed a new kernel before you started having issues, this may fix it, or you may need to wipe caches and re-flash the kernel.

GB ROMs from leak, help please

I tried to flash Xboarder 1.1.1 and RNK pure GB ROMs today. Both give me a barrage of FC messages after I flash with ROM manager. I've been able to restore to a good backup of my original rooted stock ROM so if they don't work no biggie, but I was hoping to try these out.
I had successfully flashed xboarder 1.0.1 last week, but had GPS issues so I restored to stock. I updated ROM manager recently and I'm curious if that's related. When I flash I check the new option to wipe dalvik cashe, clear data, and don't check the backup current rom because I have many redundant backups of that already.
Ideas anybody?
trjcasper said:
I tried to flash Xboarder 1.1.1 and RNK pure GB ROMs today. Both give me a barrage of FC messages after I flash with ROM manager. I've been able to restore to a good backup of my original rooted stock ROM so if they don't work no biggie, but I was hoping to try these out.
I had successfully flashed xboarder 1.0.1 last week, but had GPS issues so I restored to stock. I updated ROM manager recently and I'm curious if that's related. When I flash I check the new option to wipe dalvik cashe, clear data, and don't check the backup current rom because I have many redundant backups of that already.
Ideas anybody?
Click to expand...
Click to collapse
You have to fully wipe and reflash the rom. If you keep getting the force close msg try to redownload the rom, might be bad download
Sent from my HTC Vision using XDA Premium App
I would also recommend flashing directly from CWM and not from rom manager it has been known to cause issues for some people. And give the superwipe a try you can find in the dev forum.
Edit: was going to post a link to the super wipe thread but couldn't find it, but you can download from the first post in xboarders stock gingerbread thread http://forum.xda-developers.com/showthread.php?t=1054574
Sent from my HTC Vision using XDA Premium App
cjward23 said:
I would also recommend flashing directly from CWM and not from rom manager it has been known to cause issues for some people. And give the superwipe a try you can find in the dev forum.
Edit: was going to post a link to the super wipe thread but couldn't find it, but you can download from the first post in xboarders stock gingerbread thread http://forum.xda-developers.com/showthread.php?t=1054574
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
SuperWipeG2
http://forum.xda-developers.com/showthread.php?t=1044992
Yea, try using the SuperWipe and flashing through recovery. Don't use that rom manager crap..
Sent from my HTC Vision
-PoXx- said:
SuperWipeG2
http://forum.xda-developers.com/showthread.php?t=1044992
Click to expand...
Click to collapse
What's the difference between rom manager and clockwork directly? Clockwork made rom manager, no? The two names are not interchangeable? how does one directly flash from clockwork then? Is that done from the recovery menu I get when I volume down + power the phone?
trjcasper said:
What's the difference between rom manager and clockwork directly? Clockwork made rom manager, no? The two names are not interchangeable? how does one directly flash from clockwork then? Is that done from the recovery menu I get when I volume down + power the phone?
Click to expand...
Click to collapse
In theory, there should be no difference between flashing through rom manager and cwm and 90% of the time rom manager probably works. But on occasion it does cause issues for some people.
And yeah to get in to cwm hold power and volume down which put you in the boot loader menu. Then using the volume keys to highlight recovery then use the power button to select. Your phone will the boot in to cwm recovery.
Sent from my HTC Vision using XDA Premium App
super wipe worked! thanks for the support!

Question about CWM vs TWRP

I am real new to the KindleFire community but so far loving my Kfire. I see in slot of posts they say to use TWRP to install or update a ROM. Since I have CWM installed can I use it instead are they interchangeable for installing files?
Hope that make sense.
Thanks
Rod
most people are taking about twrp because it was the first recovery for the kf
cwm is quite new for the kf
you can use both to install roms ...
Cwm is able to be updated by current developers. Twrp looks cool, but just needs to be updated. If someone updates the reboot wrappers it'd be a winner. But I do like and prefer cwm
Sent from my Kindle Fire using xda premium
yeah twrp is dead for our device. cwm is still alive though
paranoid android85 said:
yeah twrp is dead for our device. cwm is still alive though
Click to expand...
Click to collapse
Is there or link or how-to to swtich from TWRP to CWM? Does CWM have all the features as TWRP? I have been using TWRP since I rooted the KF, have used it to back up, flash new roms to try out, flash back to my backup. CWM does all this, just dosn't have the nice CWM interface?
ontwowheels said:
Is there or link or how-to to swtich from TWRP to CWM? Does CWM have all the features as TWRP? I have been using TWRP since I rooted the KF, have used it to back up, flash new roms to try out, flash back to my backup. CWM does all this, just dosn't have the nice CWM interface?
Click to expand...
Click to collapse
The easiest way is to use THIS method, just be sure to unzip the file on your Kindle rather than on a computer or it may not work correctly. The only difference I've noticed between CWM and TWRP is that CWM does not compress the backup so the file is a lot bigger, my backups used to be in the low 500mb range and now they are in the low 800's.
Any particular reason to migrate to CWM? I have TWRP from the first day ant it doing a job very well. So, did CWM have any new features?
gett said:
Any particular reason to migrate to CWM? I have TWRP from the first day ant it doing a job very well. So, did CWM have any new features?
Click to expand...
Click to collapse
Development should be the main reason imo I think the interface looks way better. I got annoyed by the flickering backlight with twrp. It does all the same things, but cwm looks better. Plus before I switched, twrp wouldn't flash roms or gapps all the time, it would get stuck and I would have to reboot
Sent from my SPH-D710 using Tapatalk
gett said:
Any particular reason to migrate to CWM? I have TWRP from the first day ant it doing a job very well. So, did CWM have any new features?
Click to expand...
Click to collapse
For me there was not a reason to use TWRP as I have been using CWM for the last several years on smartphones and was more comfortable with it. I also read several articles where people had issues with TWRP so with as much problems as I was having trying to root my kindle because of USB driver I wanted to stick with something I know. So I thought it best to stick with and old friend I was used too. Not saying one is better than the other I just like CWM better for me and think it gives me more options to perform operations on my phone and kindle.
Rod
How have the pros and cons changed with the intro of TWRP 2.1? I am currently using CWM touch but prefer the TWRP interface, but don't want to sacrifice any features.
phantom9x said:
How have the pros and cons changed with the intro of TWRP 2.1? I am currently using CWM touch but prefer the TWRP interface, but don't want to sacrifice any features.
Click to expand...
Click to collapse
all the reboot option in twrp are still broken so Cwm is still the way to go and mabe im ocd but i like haveing Cwm on my phone and tablet plus you dont have to worry about accidenty hiting reboot to recovery and being in a boot loop
different versions of CWM touch?
I just switched from CWM touch (DooMLorD) v1.0 Final to v5.0.2.7-kf1.5 I was wondering what the differences are? I tried the Change UI color feature, but it doesn't seem to work, just stays red. is there something I'm missing? and what else was changed?
its just cleaned up. not sure why it wont change colors, works fine on my device I tested all the colors when I posted the screen shots.
Sent from my HTC Glacier using xda premium
smirkis said:
its just cleaned up. not sure why it wont change colors, works fine on my device I tested all the colors when I posted the screen shots.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I installed it and changed it to cyan with no problem! Thanks!
PS, not to resurrect a dead issue, make sure you use Root Browser (if you used Root Explorer it may not have updated check the version).
smirkis said:
its just cleaned up. not sure why it wont change colors, works fine on my device I tested all the colors when I posted the screen shots.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Hmmm....I followed the instructions to the letter, even retried it, then rebooted, no luck, installed TWRP, rebooted, reinstalled CWMT 1.5 still no luck with colors. It's not really a big deal, I'm just Being kinda OCD! Everything else about it work perfect though....
P.S. I realize this probably belongs in the DEV thread, but I can't post there yet YAY For Noobs!!

Categories

Resources