NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[natemcnutty]

Originally Posted by [ACL]

i dunno if i would consider this progress :-\

all of the sudden i cant boot into android. It seems that the data.img and system.img no longer mount.

grrr this is hard to figure out since i cant adb anymore. Have to just constantly butcher the init to find out where its dying. I guess we can begin to mod the initrd to make this more friendly.. im sure nate is ahead of me and prob has that all written already :-p

update: ok looks like android itself (not rootfs) is trying to mount the system and data from nand. since i havent been successful in writing to nand yet, it craps out..

Well, I had been in the process of testing moving to the Vogue's bootenv/tinboot setup when my USB died on me. Still haven't gotten USB functions back, and I've seriously tried everything I can think of.

Vogue's tinboot has some really awesome changes since wozzer ported it over for us. They now have working data during boot, ADB enabled by initramfs, and lots of other great changes.

They use bootenv git for building their initrd which they've changed to lzma instead of gzip: SourceForge - androidhtc/bootenv.git/summary

And their tinboot is here: SourceForge - androidhtc/bootenv.git/summary

[[ACL]]

Originally Posted by natemcnutty

Well, I had been in the process of testing moving to the Vogue's bootenv/tinboot setup when my USB died on me. Still haven't gotten USB functions back, and I've seriously tried everything I can think of.

Vogue's tinboot has some really awesome changes since wozzer ported it over for us. They now have working data during boot, ADB enabled by initramfs, and lots of other great changes.

They use bootenv git for building their initrd which they've changed to lzma instead of gzip: SourceForge - androidhtc/bootenv.git/summary

And their tinboot is here: SourceForge - androidhtc/bootenv.git/summary

so what you are trying to tell me is that its time to pillage code.. :-p.. you wanna champion this? im busy so if you can prep a patch ill commit.

[natemcnutty]

Originally Posted by [ACL]

so what you are trying to tell me is that its time to pillage code.. :-p.. you wanna champion this? im busy so if you can prep a patch ill commit.

yup, pillaging code is what I'm good at. I'll look at finishing up what I was working on and test it on my phone. At this point, I could really care less if I bricked the thing. Since my USB is stuck on all the time, I lose battery in about 8 hours

[[ACL]]

Originally Posted by natemcnutty

yup, pillaging code is what I'm good at. I'll look at finishing up what I was working on and test it on my phone. At this point, I could really care less if I bricked the thing. Since my USB is stuck on all the time, I lose battery in about 8 hours

ahh man .. did you try to mtty to bootloader yet and do the task 2* from there ? thats what fixed my issue last time. task29 itself did nothing.

[natemcnutty]

Originally Posted by [ACL]

ahh man .. did you try to mtty to bootloader yet and do the task 2* from there ? thats what fixed my issue last time. task29 itself did nothing.

I can't mtty because it won't switch over to USB in bootloader (unless there is another way). It just stays on Serial and never changes, and I have tried everything I know how. I've been looking into JTAG options, but all I can find are retail kits

Edit: The USB connection is never seen by the computer, in Android or in WinMo. The phone just thinks it is hooked up to a charger.

[arrrghhh]

Originally Posted by natemcnutty

I can't mtty because it won't switch over to USB in bootloader (unless there is another way). It just stays on Serial and never changes, and I have tried everything I know how. I've been looking into JTAG options, but all I can find are retail kits

Edit: The USB connection is never seen by the computer, in Android or in WinMo. The phone just thinks it is hooked up to a charger.

I'm SURE this has been mentioned before, but maybe you haven't used enough horsepower...

I've heard of things getting stuck in there and mucking up USB in this manner. Maybe you've tried blowing in there - have you tried anything like canned air, an air compressor, or even a shop vac in 'blow' mode? Maybe you'll get lucky...

[natemcnutty]

Originally Posted by Lmiller1708

Wirelessly posted (Vogue: Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; MSM Build/FRX03) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)



Nate have you tried another cable? I had this problem until I switched to a new one.

I've got about 12 different USB cables that I've tried, including the special ones with 2x USB to 1x mini-USB connector (for powering laptop drives that exceed 500ma). I have three original HTC cables that came with the phone (and two others at work that are the same). Sadly, none of them work.

Originally Posted by arrrghhh

I'm SURE this has been mentioned before, but maybe you haven't used enough horsepower...

I've heard of things getting stuck in there and mucking up USB in this manner. Maybe you've tried blowing in there - have you tried anything like canned air, an air compressor, or even a shop vac in 'blow' mode? Maybe you'll get lucky...

Wish it were that simple. I've used canned air as well as a plastic brush we commonly use to clean the fans on servers. It looks perfectly clean in there, so my thought is it must be the connector to the board or something wrong with the bootloader itself. Sadly, I can't re-flash HSPL since I have no USB...