The g1 is plagued by a bug that will end up with you locked out of the phone. If you call TMobile or search on the net, the responce is to factory reset the phone. The bug rears its ugly head when someone tries to get past the g1 pattern lock and ends up on the "too many pattern attempts" screen where you should be able to login with your gmail account information. Something strange happens where the g1 stops actually doesnt try to auth anymore, it just reports a bad UN/PW instantly. This state will survive reboots and even pulling the battery. The net has "fixes" ranging from making sure you are on the TMobile 3G network, to using different domains as part of the username. There is also one fix by haykuro that is almost right. This was done on a rooted phone. If you are not rooted, well i make no promises and say its not my fault if you break something. You will need the android-sdk. http://developer.android.com/sdk/ I did this in windows cause its what i was using at the time, should work the same in linux once you get the shell to the phone open. > adb -d shell su # sqlite3 /data/data/com.android.providers.settings/databases/settings.db sqlite> .tables android_metadata bookmarks secure bluetooth_devices gservices system sqlite> .header on sqlite> .mode column sqlite> select * from system; you will see something similar to the following(the number might be different) _id name value --------------------------------------------- 18334 lockscreen.lockedoutpermanen 1 Disable that, sqlite> update system set value=0 where _id=18334; check the change. sqlite> select * from system; you should have _id name value --------------------------------------------- 18334 lockscreen.lockedoutpermanen 0 Exit sqlite with ".exit" Reboot phone and the screen will be gone. #reboot Credit to haykuro, ForgeMo from andforge.net and Davanum Srinivas for making guides that helped get me down the path. init me while (1=1) me = mage2 domain=bleedingwound.com address =$me@$domain printf $address