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

[ChaosTheory]

Quick question, I just updated both my zImage, module, and rootfs, and now my headphones/headphone jack doesn't work. Any idea which one is the most likely culprit, so I don't have to roll back all of them if I don't have to?

[mj41374]

Originally Posted by arrrghhh

I did read something over on XDA that made no sense... but can you post your startup.txt so I can compare it with mine?


So I just saw your new post. Glad you got it working, but that is an old build. You'll be running 2.0.1, which I guess isn't all that different. That makes me wonder... Can you download this SQSH file, backup your current sqsh file (rename it to system.sqsh.bak, and name this one system.sqsh) Please let me know how this works for you.

Yeah, I've posted the startup.txt file - it should be whatever is in the 2010-05-11 AIO package now that I've gotten it working (and according to the droid 'About' settings I'm now running Kernel 2.6.27.46-01081-gf2c4dc0 GlemSom@autobuild-service_20100506_120405 as well as 2.1-update1 firmware AOSP on XDANDROID MSM: xdndroid_msm_us-eng 2.1-update1).

SQSH file you linked works fine too (albeit with a different boot animation that the AIO package).

Edit: Here's the startup file:

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2039
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3"
boot

Edit: SQSH works just as well as the one in the AIO. I'm going to give the 2010-05-11 AIO clean(format)-install a try again and try to find out what makes the difference between a clean-install working and not working when copied/overwritten by an older AIO.

[mj41374]

OK, I did a clean-format on the sdcard and re-copied the 2010-05-11 AIO package that Makk posts in the first posting. It still does an endless reboot at the X logo.

Then I shutdown and copied/replaced the system.sqsh file that arrrghhh posted - same result - but now endless rebooting at the android logo.

During the initial (first-time) set up of the AIO package I noticed a dependency error message that I haven't seen before. The problem is, it flies by so fast I can't record it all (typing). Hareet debug doesn't seem to give me any useful info and I can't run an adb log using DroidExplorer as it doesn't seem to get far enough for my machine to connect to it. Ugh. Here's what little I copied down:

...
Welcome to Vogue Linux
Running an fsck on the SD card
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
.....
cleaning up...
switching to rootfs
rootfs loaded
gsm phone found
checking for partition...
creating a new Data store
...
depmod chdir(2.6.27.46-01081-gf2c4dc0) no such file or directory
dependency no such file <<<--Here's where I'm concerned... it looked like one of the modules was corrupt??>>
....
[touchscreen calibration stuff]
....
unknown option -- scmp: invalid option -s
touchscreen calibration successful; saving...
Bad mode
....

[hamagc]

mj41374, try updating with these files:

kernal: http://balsat.hopto.org/download.php...inuxMSM.tar.gz

rootfs: http://xdandroid.southcape.org/rootf...12-92b6e96.zip

these are a little more up to date than what you have. delete your current zimage and modules and rootfs. make sure you rename the new rootfs to rootfs.img.

use the startup.txt you posted above. shouldn't have an issue booting then.

[Ebiz]

I seem to be having the same problem with the AIOs. I tried the 5-7 and the 5-11 just now and also tried adding the files that hamagc just posted and no dice. This is after a complete reformat of the card and a fresh install. I can't remember what the last version I was using was... probably something from march, but it installed fine.

So yeah, I guess I'll try and do my homework and install this the hard way, but a heads up for the AIO people.

Thanks for everyone's hard work!

[Jopcastillo]

Originally Posted by mj41374

After going back, re-formatting, and getting the 2010-03-31 AOI working on my device (no boot-loop, and got all the way to the home screen), I then attempted to simply *overwrite* the sdcard with the latest AOI from 2010-05-11 and guess what - it works!!! I'm guessing that people who've been updating instead of clean-installs are working and those that do clean-installs don't work.

Hey! did u delete the DATA.img before?

[mj41374]

Originally Posted by Ebiz

I seem to be having the same problem with the AIOs. I tried the 5-7 and the 5-11 just now and also tried adding the files that hamagc just posted and no dice. This is after a complete reformat of the card and a fresh install. I can't remember what the last version I was using was... probably something from march, but it installed fine.

So yeah, I guess I'll try and do my homework and install this the hard way, but a heads up for the AIO people.

Thanks for everyone's hard work!

If you're doing a clean-formatted install of the AIO package... try using the AIO-2010-03-31.7z file first. Boot up the phone using that version and go through the screen calibration and get through the Google initizliaztion (or skip it) so you get all the way to the android desktop.

Then shutdown and download the 2010-05-11.7z AIO package (first post). Without removing or renaming *anything* on the sdcard, extract the 2010-05-11 files/folders and replace any duplicate files (merging all folders) on the sdcard in the same andboot folder w/o removing anything from the existing.

Boot back into droid and you should end up with a working 2010-05-11 package.

[mj41374]

Originally Posted by Jopcastillo

Hey! did u delete the DATA.img before?

No, I didn't remove/delete anything from the sdcard - just overwrote what was in 2010-05-11 with any duplicates found on the sdcard (and merged folders).

[mj41374]

Originally Posted by hamagc

mj41374, try updating with these files:

kernal: http://balsat.hopto.org/download.php...inuxMSM.tar.gz

rootfs: http://xdandroid.southcape.org/rootf...12-92b6e96.zip

these are a little more up to date than what you have. delete your current zimage and modules and rootfs. make sure you rename the new rootfs to rootfs.img.

use the startup.txt you posted above. shouldn't have an issue booting then.

Formatted sdcard - Clean install of 2010-05-11 then copied the zimage, modules, and rootfs.img you specified and same result as the others: endless X logo.

[mj41374]

My guess is something gets initialized in the older kernel that isn't being initialized in these later kernels. Then once the new kernel comes in, it doesn't have to init anything and continues to boot just fine. So people who have just been upgrading kernels and everything else all along are just fine. But anytime you do a format on your sdcard and do a clean install of the AIO package in the first post - you'll hit the endless logo problem.