Disclaimer: I'm pretty new to Android rooting, and just found this awesome site! So I tried to root my Incredible using unrevoked3 while using 2.1update1. I did this before having come to this site and hadn't seen the thread on here describing all the steps necessary to do after running it. I didn't think it was working, so I manually installed 2.2, and then reran unrevoked3. Just mentioning all this in case it could have messed up unrevoked3 once it was ran the 2nd time. Right now (I think?) I can get su access when running the terminal emulator on my phone; the # comes up when I execute "su", and I can then execute commands. However, when I run adb (Windows 7 command prompt, run as admin) I can't type anything once I try to get su access, though it does show a #: C:\>adb shell su # It just sits there and I can't type anything... Once I ctrl+c out it will then execute anything I tried typing while it was sitting there in the normal command prompt shell. I've read that this may be because "if my boot.img has ro.secure set to 1, it drops permissions after it loads". This doesn't mean much to me just sounded like it could be right? Thanks for your help!!!