[Galaxy Note II Q&A, Help & Troubleshooting] Robobob1221:
Ok I found you can install busybox in the xbin directory of the system through adb, however the full set of applets cannot be symlinked when using an installer like jrummy's or sericssons, this is what seems to be causing the hot restart. We need to find out what is causing this

This is the output from a logcat when I ran the busybox installer, well the part that I thought was of issue.

E/su (11351): sudb - Opening database

E/su (11351): sudb - Database opened

E/su (11351): sudb - Database closed

I/SurfaceFlinger( 1978): id=54(6) createSurf 0x42a32244 (1x1),1 flag=0, unnamed

D/KeyguardViewMediator( 2403): setHidden false

D/KeyguardViewMediator( 2403): setHidden false

D/KeyguardViewMediator( 2403): setHidden false

D/AndroidRuntime(11353):

D/AndroidRuntime(11353): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<

D/AndroidRuntime(11353): CheckJNI is OFF

D/AndroidRuntime(11353): setted country_code = JP

D/AndroidRuntime(11353): setted countryiso_code = JP

D/AndroidRuntime(11353): setted sales_code = DCM

D/AndroidRuntime(11353): readGMSProperty: start

D/AndroidRuntime(11353): readGMSProperty: already setted!!

D/AndroidRuntime(11353): readGMSProperty: end

D/dalvikvm(11353): Trying to load lib libjavacore.so 0x0

D/dalvikvm(11353): Added shared lib libjavacore.so 0x0

D/dalvikvm(11353): Trying to load lib libnativehelper.so 0x0

D/dalvikvm(11353): Added shared lib libnativehelper.so 0x0

D/KeyguardViewMediator( 2403): setHidden false

D/KeyguardViewMediator( 2403): setHidden false

D/dalvikvm(11353): Note: class Landroid/app/ActivityManagerNative; has 153 unimplemented (abstract) methods

D/AndroidRuntime(11353): Calling main entry com.android.commands.am.Am

D/STATUSBAR-SignalClusterView( 3489): mSeparateMobileGroup=8

D/STATUSBAR-SignalClusterView( 3489): mSeparateMobileGroup=8

D/STATUSBAR-SignalClusterView( 3489): mSeparateMobileGroup=8

D/AndroidRuntime(11353): Shutting down VM

D/dalvikvm(11353): GC_CONCURRENT freed 102K, 86% free 594K/4096K, paused 1ms+0ms, total 5ms

D/STATUSBAR-NotificationService( 2403): enqueueToast()

I/SurfaceFlinger( 1978): id=55(4) createSurf 0x40f3e27c (1x1),1 flag=0, Uoast

D/KeyguardViewMediator( 2403): setHidden false

D/PowerManagerService( 2403): acquireWakeLock flags=0x2000000a tag=KEEP_SCREEN_ON_FLAG uid=1000 pid=2403 myUID=1000 myPID=2403 myTID=2403

D/KeyguardViewMediator( 2403): setHidden false

D/su (11351): 10259 com.jrummy.busybox.installer executing 0 /system/bin/sh using shell /system/bin/sh : sh

D/KeyguardViewMediator( 2403): setHidden false

D/KeyguardViewMediator( 2403): setHidden false

D/STATUSBAR-SignalClusterView( 3489): mSeparateMobileGroup=8

D/STATUSBAR-SignalClusterView( 3489): mSeparateMobileGroup=8

D/STATUSBAR-SignalClusterView( 3489): mSeparateMobileGroup=8

I/EventHub( 2403): Removing device '/dev/input/event9' due to inotify event

D/KeyguardViewMediator( 2403): setHidden false

I/EventHub( 2403): Removing device '/dev/input/event4' due to inotify event

I/EventHub( 2403): Removing device '/dev/input/event5' due to inotify event

I/EventHub( 2403): Removing device '/dev/input/event6' due to inotify event

I/EventHub( 2403): Removing device '/dev/input/event7' due to inotify event

I/EventHub( 2403): Removing device '/dev/input/event8' due to inotify event

I'm wondering if we need to edit ramdisk, init.rc or something or other, to initiate busybox symlinks before boot, on init or on early-init??

If its not ramdisk then it is probable that the zimage (kernel image) has been modified.

I guess we can't rule out that there is something in the system that is being activated that could be removed to prevent this even if its in the kernel image