I've tried that but I couldn't access adb. Is there any other way to debug a device that doesn't have adbd running (in the context of a bare bones boot)?
On 26 August 2011 09:49, Amit Pundir <pundira...@gmail.com> wrote: > On Thu, Aug 25, 2011 at 2:47 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? >> >> > Hi, I have been to this stage before where my system got stuck in boot loop > because my Android services was crashing. Try following modifications in > your init.rc > > 1) Set your "loglevel to 8". That way you will get more logs. > > 2) Disable all the service except "ueventd" and "console". See if you are > able to get up to Android prompt (Console). If you manage to get Console, > then start the services manually (e.g. start debuggred) and find out the > service which failed first. > > Regards, > Amit Pundir > http://arowboat.org > > >> -- >> Radu Iscu >> Tel: 0742082607 >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-porting >> > > -- Radu Iscu Tel: 0742082607 -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
