I don't know what you can do in the device. Just some common suggestion. 1. Build a ramdisk with busybox into kernel, and boot this ramdisk to shell 2. mount the android partition, and switch to android by switch_root command, I think you can get some info by this way.
On Aug 25, 5:17 am, Radu Iscu <linke...@gmail.com> wrote: > Hello guys, > > Here's the skinny: I'm trying to port the honeycomb to the ziio 7 and I have > to say that I can't even get the bare bones init.rc to boot. > I left the kernel partition intact as there's no point in messing with that > (there's no recovery partition so the kernel doubles as a rescue). It holds > a 2.6.29 kernel, which is the same as the default one in 3.0. > > I never managed to get to a point where I have the new init/ueventd working. > The device gets stuck in a boot loop, never getting passed the kernel logo. > > I've tried putting exec logcat -d -f here and there in the init process, > hoping for some clues, but that doesn't seem to be working. > Also there is nothing in /data/dontpanic/ > > Any ideas about what I should do to get a clue about what's going on? > > -- > Radu Iscu > Tel: 0742082607 -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
