Develop Bugs

Any thoughts?

So I rooted my DInc and installed Virtuous 3.1.0 and switches to the Virtuous custom kernel.
Problem is, I tried to install chars kernel and just kept getting a reboot loop, no matter what version I tried. So then I restored and tried to instell SkyRaider from ROM Manager... but when I went rebooted and tried to setup my phone, it would just reboot the phone back to the setup. I did do a wipe before installing SkyRaider and chars kernel. Any thoughts on what's wrong?
Sent from my ADR6300 using XDA App

Did you also wipe dalvik cache too? It's under advanced in recovery... I do that before each kernel install without issue.

Common mistake I do believe don't "wipe" when installing a kernel just wide cache partition and advanced/ dalvik I hope that helps. I know a few people were doing full wipes when installing kernels
Sent from my Incredible using XDA App

Thank you for the help! =D
Got chads kernel installed with out any trouble this time. Gonna give SkyRaider ROM a try now.
Update - Got SkyRaider 3.5 installed, but I don't like the default lock screen, and no matter what I do, I can't change it. I've tried installing both lock screens in ROM Manager (didn't work), tried deleting the HtcLockScreen.apk in root explorer (didn't work), and tried to change the lock screen in both the terminal emulator and through adb shell - lockscreen in the sdk. Any one have any ideas on how to get rid of the default lock screen?

[Q] Why do I keep getting cache errors and bootloops??

I have been running CM7 RC1 for a few weeks now with no issues. I have no special apps or anything besides the basics (titanium backup, setcpu, and CWM).
I ran into this issue about a week ago when I tried to flash my stock rom when I was running Gingervillian 1.5. I was getting:
E: Can't open cache/recovery/command
when I tried to flash back from stock Froyo ROM to Gingervillian and I figured it was because I used CWM 3.x.x and not CWM 2.x.x to flash from a Gingerbread ROM to a Froyo ROM...
However, since then, I installed a clean CM 7 RC1 ROM and have been fine. Then all of a sudden today, the phone locked up and I had to pull the battery and then it ran fine for a few hours and did it again. So, when I got home, I flashed a recovery from 2 days ago that was running fine and I got the cache error and then bootloops again.
WTF is going on?
The ONLY thing that changed between my recovery image from Mar 11 to now was my wife downloaded Soduko from the market, and I made a SetCPU profile for when the phone is charging. Other than that, nothing changed.

I was able to get it working...I am not sure what I did that made it work but this is what I did.
Format /cache (originally gave me the cache error)
Format /data (originally gave me the cache error as well)
Format /davlik cache
Reboot recovery
Downloaded another CWM 3.0.0.5 .img file and copied it to sd card (was going to try to flash new CWM to see if it would help).
Then I tried to Format /data again and it worked, so I tried format /cache and it worked.
Then I tried my recovery and it worked as well. So, it is working, but I think I may flash CMW 2.x.x and go back to CM 6.1 since it is stable. I know everyone says CM 7 RC1 is pretty stable as well, and I reallllly don't want to go back to Froyo...I don't want to keep having problems like this.

happened again tonight. Phone froze after running completely fine. I pull battery and try to reboot and get stuck at HTC screen. Go into recovery and get the same cache errors.
I tried formating data, cache and davlik cache and nothing is working. Is there something I am doing wrong, or something I can do to keep this from happening?

You need Clockwork mod recovery app from market. 3.0.0.5 is official and goes between froyo n cm7 without problems. Try that
meXdroid Ghost Chilli

I have the latest CWM and I wasn't trying to flash a new ROM tonight, or last time either. The phone just froze and then started with the cache errors.

...anyone?

[Q] can't run any new rom, hangs at white htc incredible screen on boot

I rooted the incredible using unrevoked, no problem.
Installed and ran root apps, no problem, backed up everything using titanium backup and rom manager (nandroid) and so forth, installed cw recovery 3.0.0.8.
When I install the skyraider 4 rom from rom manager, it reboots and installs, but then when it reboots again it hangs at the white htc incredible screen (and I've let it wait as long as a half an hour). I have to take out the battery to be able to reboot it.
I can boot back to recovery and then re-install and boot back to the stock rooted rom just fine. But I can't get a new rom installed and working.
I've looked at previous threads about this problem:
http://forum.xda-developers.com/showthread.php?t=1038402
http://forum.xda-developers.com/showthread.php?t=1023358
http://forum.xda-developers.com/showthread.php?t=991953
http://forum.xda-developers.com/showthread.php?t=739646
http://forum.xda-developers.com/showthread.php?t=620621
and several other threads on other sites.
The only suggestions to come out of those, other that starting over from scratch (which I've done multiple times now), were to reformat the sd card, which I've also done, and to downgrade to cm recovery 2.5.1.2. Rom manager only shows versions as old as 3.0.0.5. I have put the PB31IMG.zip file on the sd card and loaded that before to help recover but I don't see how that helps with installing a new rom.
Any other suggestions? The main reason I even need a new rom is because bluetooth doesn't work in the stock rom (known issue: http://community.htc.com/na/htc-forums/android/f/91/p/2336/8570.aspx )

It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe

patsfan1130 said:
It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe
Click to expand...
Click to collapse
appreciate your help, yeah I've been doing that everytime in rom manager. I tried it several times manually in cm recovery, too, and still the white screen.
I'll just see if verizon can exchange it, or else I'll sell it for another phone with working bluetooth.

Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App

when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.

when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.

k_nivesout said:
Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
.
There is a flash of CWM 2.5 that temporarily lets you use that to flash the rom then when you reboot it will revert back. Try that.

three major problems

ok so heres the deal...
i downloaded htcclay supercm7 (latest version) from ROM manager premuim... flashed it and rebooted my phone... after 3 seconds i noticed three major problems:
1- where is the status bar? oh wait... "status bar not responding" oh... force close issue :S
2- i'll try fixing the status bar issue by rebooting... WHAT?? i can't turn off my phone... it reboots direcly into "google" splash screen!!
3- lockscreen gone!!
any ideas on how to fix these??
thank you!

PROBLEMS UPDATE:
just got to cyanogenmod settings, system, update nofication... when i click it... the settings force closes
its frustrating!!

Wipe. In either hboot or recovery. Whichever one you can get into. Flash something more reliable. A stable cm build. I'd say the latest nightly, but I don't want to sound like a broken record.
Never again load something from rom manager's list
Sent from my HTC Vision using XDA Premium App

LOL... ok
i reflashed the latest ILWT CM7 and everything went back to normal...
just one last question: i usually wipe dalvik cache and flash a ROM...
should i wipe data if i flash a new ROM?
and should i wipe data if i update a ROM?

Riro Zizo said:
LOL... ok
i reflashed the latest ILWT CM7 and everything went back to normal...
just one last question: i usually wipe dalvik cache and flash a ROM...
should i wipe data if i flash a new ROM?
and should i wipe data if i update a ROM?
Click to expand...
Click to collapse
General rule of thumb:
- when switching to an entirely different rom (or if you switch to a rom by a different developer, e.g. bulletproof miui to osimod miui) it's best (in many cases necessary) to do a full data/cache wipe
- when updating a rom one can generally assume to get by fine if only cache and dalvik are wiped, in this case extensive wiping should only be necessary if you encounter problems or the OP specifically tells you to do so.

[Q] ROM issues

A huge problem seems to have arisen on my Desire Z.
After using Andromadus 8 for a while I decided to try some other ROMS.
They were:
- Andromadus V10 and 11
- Virtuous Quattro RC3
- Ice Cream JIBwich 1.1
- BlissDroid
- Android Revolution HD 7.0
All of these ROMS flashed after using Superwipe G2 however were stuck on the initial boot screen.
I left some of these ROMS on for more than an hour on the boot screen to no avail.
The only ROMS that still seem to function are Andromadus V8 and MIUI ICS (however with no Wi-FI)
Please can anyone give an indication of what is wrong?

Some roms don't want you to wipe anything because the flashing will do it for you. Although it could've been that the roms have problems?
Sent from my CM7 G2!

i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.

Cleared dalvik and checked all the MD5. Everything seems fine except it doesn't work

Tried a ordinary factory reset/data wipe?
-Nipqer

starop013 said:
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Click to expand...
Click to collapse
Superwipe does clear dalvik cache.

I am at my wits end
ONLY Andromadus 8 works for some reason
I cleared it and cleared it, and reflashed every combination of roms
BUT only 8 works and I'm tired of not having my camera anymore
I've even tried bare Sense 2 ROMS to no avail. Every ROM is stuck on bootloops
Does anyone have a solution?

Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer

Have you tried flashing from recovery directly? RM is great for convenience, but I just don't trust it to do things properly. I've had this happen to me sometimes where a ROM looks like it's flashed, but hasn't. Weird, I know. Try the following, it worked for me before:
1. Flash SuperwipeG2+ext4 (if you want the ext4 filesystem)
2. Flash your ROM
3. Check to see if it worked
4. If it didn't work, flash your ROM again without wiping
Usually that fixes it for me. In 4EXT recovery, you can check the partition sizes to see if the ROM installed properly. Not sure if CWM does that as well.

Nipqer said:
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Click to expand...
Click to collapse
Nipqer
You sir are a legend
An obvious solution that makes me wonder why I didn't think of it
Thank you, thank you

flashing through recovery is just easier for some, and if your not near a computer. but for best results always fastboot -w and flash rom via fastboot, just makes life easy the first time. and im ocd a little so i also flash superwipe and manually wipe data/cache. so if you dont wont any issues, fastboot wipe, fastboot flash... your golden!