Originally Posted by glenlee
We're using the LG Ally in a business as a GPS tracking device for our trucks, the phone is disabled. A few of the phones are stuck in a reboot loop. None of us are Android Geeks, so short of bringing the phone back to Verizon we don't know what to do.
We're using Load Trek as the tracking app. Some of the working phones crash immediately when we try to load Load Trek. I'm wondering if the rebooting loop phones are trying to start Load Trek on startup and crashing due to a bug in Load Trek.
In the phones I've be able to bring current on the software the problem has not surfaced. I've yet to find a way to interrupt the phones in the reboot loop so I can update Android, Froyo, and Load Trek.
1. Is there a way to interrupt the boot cycle in the rebooting phones and boot into some kind of a safe mode, and manually delete Load Trek? If so please give a step by step explanation how to do it. I'm a Debian end user, so I'm not a complete idiot, but I can't read between the lines, so please don't skip any steps.
2. Could there be another problem we should be looking for that could be triggering this?
If you have some time you can find out whats causing the loops by running a logcat while the phone boots up, to do this you will need to setup ADB (adnroid device bridge) so you can communicate with your phone via USB, with ADB running it is also possible to recover the phones.
Alternatively you can run my FroyoLiteWin batch to reflash the phone to stock 2.2.1 (the latest software version) If it fails it would be because the USB Debugging is turned off, you can get around this by starting the phone in recovery, pull the battery and turn the phone on with the MENU SEND and END buttons held, you may even be able to reset the phones thru stock recovery, when it pops up the Android ! you can press 5 on the hardware keyboard to bring up the recovery menu (timing is tricky)