Database Users

why stuck on modaco??

hello all, i recently installed clockwork3.0 to try out the cm7 rom and did so. afer that i wanted to go back to cm6 but decided to try out a custom baked modaco in between. I went no problems to the modaco vision rom and then tried to go back to the cm6 and thats where i ran into the problem. It seems as if though all i can flash and boot now is the modaco vision and desire roms. i try enomther and cm and after the flash and reboot im always stuck at the HTC boot screen which i know shouldnt be there and cant format boot in cwork3.0 without failure error. Even a nandroid back to cm6 wont work. Im assuming this has something to do with the modaco rom writing some apps to /system during install. If anyone can point out my error or explain why this could happen it would be greatly appreciated. Thanke, veritasaequita

You need to flash back to the old ClockworkMod Recovery using fastboot? You have done that haven't you? CWM Recovery 3 is only for 2.3 roms atm afaik.

Cool, thanks for the input bro. Yes I sure have. I did see in the dev forum a thread titled install cw3.0 easily from phone. Is it possible to go back to the old cw by way of using the phone also? Once again thanks for your help
Sent from my HTC Vision using XDA App

oh yeah, indeed you have hit upon something. Try installing ROM manager via the Market,... then use that to re-install the old recovery.
But if that fails,... then yes, you SHOULD be able to use a Terminal Emulator to flash without using fastboot commands.

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

Savaged-zen(mod) reboots

Anyone else having random reboots in the savaged-zen roms? I've tryed flashing it a couple times used a few different versions of their kernels and I still get random reboots. It also reboots whenever trying to install any apps. If anyone else is experiencing these problems or has a fix. Feel free to comment
Sent from my CyanoEVO 7 using XDA App

you fix permissions?

NewZJ said:
you fix permissions?
Click to expand...
Click to collapse
yeah it didn't help at all.

someone posted this fix in another thread but i have no clue how to do it myself...
"I did a full wipe with Calk's Format All script and installed the RC3 with the SZ gapps from the first post (after a reboot, per an earlier post).
Couldn't install anything from the market or via File Manager. It would download, then hot restart the phone. Found out that the permissions/owner of /data/app (and/or data/app-private) were incorrect. Changed perms to 771 and owner to system.system and now all is well with the world again."

Had the same issue on my buddy's evo, after fixing permissions/owner I then used every option in ra recovery (2.3) in the wipe menu except " wipe sdcard" and " wipe boot", include android.secure and all other wipes. Flash rom then reboot phone, let the phone start up, then reboot back to recovery and flash gapps
Sent from my Evo using the XDA app

detcup4evr said:
Had the same issue on my buddy's evo, after fixing permissions/owner I then used every option in ra recovery (2.3) in the wipe menu except " wipe sdcard" and " wipe boot", include android.secure and all other wipes. Flash rom then reboot phone, let the phone start up, then reboot back to recovery and flash gapps
Sent from my Evo using the XDA app
Click to expand...
Click to collapse
The problem with that is that it wont boot with out the gapps being flashed. Ill try again doing what you said when I get home tho. Do you think its leftover files from other roms messing it up? Because when I first rooted I was what you would call a flashaholic haha and there is a few folders from other roms on my SD "miui, etc"
Sent from my PC36100 using XDA App

That is what I thought also, but it was a last ditch attempt before giving up and going back to his old nandroid, but the phone booted fine, and I was even able to make calls without gapps.
Sent from my Evo using the XDA app

ive had this issue with cm7...if i flash rom...then flash gapps...and then flast titanium backup
if i dont flash titanium back up it works fine.

[ATTN] ROM Manager 4 + ClockWorkMod 2.X causes Touchscreen Brick

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

Hello everyone! Noob here, a couple Q's

Hey guys, I just bought a used Mytouch 4G today, this phone is seriously awesome!! I used to have an Xperia X10, but I sold it to get this one!. Now flashing stuff on the X10 is super simple, everything is mostly one click! Here though, theres s-off, flashing radios and whatnot, recovery, etc.
Anyways, the phone I bought came with the crappy tmobile sense froyo, so I used visionary to permaroot and one of these tutorials to do s-off and get clockworkmod with rom manager! Now I have a question, about the radio do I have to flash it before I flash a new rom or after? Also do I just flash the new rom with recovery and i'm done, or are there any extra steps needed? Also is the kernel the same way?
Thanks!

abdurahman said:
Hey guys, I just bought a used Mytouch 4G today, this phone is seriously awesome!! I used to have an Xperia X10, but I sold it to get this one!. Now flashing stuff on the X10 is super simple, everything is mostly one click! Here though, theres s-off, flashing radios and whatnot, recovery, etc.
Anyways, the phone I bought came with the crappy tmobile sense froyo, so I used visionary to permaroot and one of these tutorials to do s-off and get clockworkmod with rom manager! Now I have a question, about the radio do I have to flash it before I flash a new rom or after? Also do I just flash the new rom with recovery and i'm done, or are there any extra steps needed? Also is the kernel the same way?
Thanks!
Click to expand...
Click to collapse
radio is flashed through the bootloader, renamed as PD151IMG.zip. i would suggest the panache radio, but all phones are different, and each have different results with different radios. doesn't matter when you flash the radio. all radios for the MT4G are found here: http://forum.xda-developers.com/showthread.php?t=1059347
flashing roms: before you flash a rom, BE SURE TO CHECK THE MD5SUM!!
this can be done using the free mand5 app from market. next, move the ROM.zip to your SDcard, reboot into clockworkmod recovery, DO A NANDROID BACKUP and DO A FULL WIPE.
full wipe is:
-wipe data
-wipe cache
-wipe dalvik cache (under advanced menu)
at least twice
after doing the full wipe, just select the ROM.zip and flash it.
first boot usually takes longer than usual.
flashing kernels is similar, but easier:
-DO NANDROID BACKUP
-wipe cache
-wipe dalvik
-flash kernel.zip
enjoy pure awesomenesss!!!
also, i would suggest you check out Virtuous Unity, a VERY nice rom created by the Virtuous team. link is here: http://www.virtuousrom.com/

oh yes I've had my eye on the virtuous rom, it looks very nice indeed! Thanks!

just one question, how do I boot into bootloader without using adb? Is it volume down+power??

abdurahman said:
oh yes I've had my eye on the virtuous rom, it looks very nice indeed! Thanks!
Click to expand...
Click to collapse
sure no problem

abdurahman said:
just one question, how do I boot into bootloader without using adb? Is it volume down+power??
Click to expand...
Click to collapse
Either adb reboot bootloader or volume down+power Button. Make sure fastboot is OFF
Sent from my HTC Glacier using xda premium

if you have rom manager (you said you did), in rom manager there's an option to reboot into recovery. from there if you flashed one of the custom roms, most of them when you choose to power off have an option to reboot into recovery as well.

aznanimedude said:
if you have rom manager (you said you did), in rom manager there's an option to reboot into recovery. from there if you flashed one of the custom roms, most of them when you choose to power off have an option to reboot into recovery as well.
Click to expand...
Click to collapse
Check out my YouTube channel. Same name as my XDA name. I have pretty much every thing you'll need to know about how to flash, radios, ROM's etc. Good luck buddy.
Sent from my HTC Glacier using xda premium

Thanks for the help everyone! I've gotten a new radio, the unity rom, and the demonspeed kernel running at 1.6 ghz!!
One more thing, is it normal to have a laggy homescreen in the sense rom? Like the drawer is super laggy too!

abdurahman said:
Thanks for the help everyone! I've gotten a new radio, the unity rom, and the demonspeed kernel running at 1.6 ghz!!
One more thing, is it normal to have a laggy homescreen in the sense rom? Like the drawer is super laggy too!
Click to expand...
Click to collapse
sometimes it might lag a little. but most of the time, it shouldn't lag one bit.

comparing the speed of sense to AOSP, it's gonna be a bit slower pretty much most of the time, but it's still pretty smooth and not that laggy all things considered
gratz on having fun with your phone