Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS! - Page 238

**makkonen** · #**2371** (**permalink**) 05-11-2010, 02:10 PM

And the latest AIO package (2010-05-11) has a rootfs from last night, so it should be past that point. I'm really baffled by all these boot loop issues. I think I've replaced all the things that would cause it, but maybe there's something I'm missing. If someone wants to hook up adb and get a logcat of it happening, that could help. (Install Droid Explorer. Connect to Activesync. Start Android. Start Droid Explorer and connect. Start logcat. Look to see what messages come up right before the X locks up and the boot process restarts.)

Edit: What the hell. OK... I'm going to re-up the AIO with the absolute latest rootfs. Maybe I just got unlucky last night.

Edit2: Uploaded. ~73mb. Hopefully not corrupt.

**arrrghhh** · #**2372** (**permalink**) 05-11-2010, 02:12 PM

Quote:

Originally Posted by oranges311

hey guys i downloaded the all in one and unzipped it and put the andboot onto the root of my sd card. but when i ran the Haret.exe the little laser x thing ran on my phone but thats all it would do was repeatedly make that start up image. i found the past like 2 pages back saying to try the latest Zimage or something but idk what that means. do any of you know what i should do? im just tryin out the Android on the touch pro so if someone could tell me some of the basics also id appreciate it alot

Sorry, your question got kinda buried. I don't mean to show you "attitude" here, but you really do need to read the first and maybe second post so you have *some* idea of what's going on. Posting in a thread saying "I don't know what X means" usually means "I didn't search, please hand-feed me the answer".

2 things - update to the newest AIO, Makk just posted a new one. 2nd, be patient. The first boot takes seemingly forever, I know.

**arrrghhh** · #**2373** (**permalink**) 05-11-2010, 02:13 PM

Quote:

Originally Posted by hotwired34

Hey now...settle down. I don't want you to think I don't appreciate your help.
Based on your suggestions, I noticed that the rootfs that I had on the card was still the one from the all in one package. On the first post, there is a link to dowload the latest rootfs. I got the latest and put it in the andboot folder and it is now working. I am not sure if this was supposed to be updated through the MJGDroid Util, but either way, it is working and I appreciate your help.

I'm settled. Glad you got it working. Seems we need to track down the developer of the MJGDroid Util, because it doesn't seem to be doing its job. Sigh, it was a good idea.

**arrrghhh** · #**2374** (**permalink**) 05-11-2010, 02:15 PM

Quote:

Originally Posted by makkonen

And the latest AIO package (2010-05-11) has a rootfs from last night, so it should be past that point. I'm really baffled by all these boot loop issues. I think I've replaced all the things that would cause it, but maybe there's something I'm missing. If someone wants to hook up adb and get a logcat of it happening, that could help. (Install Droid Explorer. Connect to Activesync. Start Android. Start Droid Explorer and connect. Start logcat. Look to see what messages come up right before the X locks up and the boot process restarts.)

Edit: What the hell. OK... I'm going to re-up the AIO with the absolute latest rootfs. Maybe I just got unlucky last night.

LOL thanks for putting up with our ridiculousness Makk. Not sure why they're all having the issue as well, but hopefully keeping that AIO package will cut down on the problems. I'd like to track down the guy who wrote MJGDroid to see what we can do about improving that app - checking to see if we already have the latest, making sure it's using the new non-debugging zImages, etc.