[G1 Q&A, Help & Troubleshooting] jmhecker:
I got my G1 last December. Like a lot of other people, I rooted it right away, and started testing other ROMs that are out there before settling on one that I liked.

In Mid February I gave SuperD a shot, and loved it. I stuck with it for a while, and then yesterday I decided to give his latest version a go, v1.9.3.

I flashed it the same way that any ROM is done. Using RA Recovery (1.6.2), wiping all data, hell, I even repartitioned my SD Card. I then flashed the .zip, and started the boot process.

Once it was booted, the first thing to appear on the screen was an FC Message for the Setup Wizard. It appeared before the "Click The Android" to begin message showed up. After pressing the FC button, it reappeared in a few seconds. Below is the part of the log file that kept cycling every time I hit the FC Button:

I/ActivityManager( 72): Process com.android.setupwizard (pid 397) has died.
I/ActivityManager( 72): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.setupwiza
rd/.SetupWizardActivity }
I/ActivityManager( 72): Start proc com.android.setupwizard for activity com.an
droid.setupwizard/.SetupWizardActivity: pid=406 uid=10014 gids={3003}
W/UsageStats( 72): Something wrong here, didn't expect com.android.setupwizard
to be resumed
W/dalvikvm( 406): Unable to resolve superclass of Lcom/android/setupwizard/Netw
orkMonitor$Callback; (285)
W/dalvikvm( 406): Link of class 'Lcom/android/setupwizard/NetworkMonitor$Callba
ck;' failed
I/dalvikvm( 406): Failed resolving Lcom/android/setupwizard/BaseActivity; inter
face 204 'Lcom/android/setupwizard/NetworkMonitor$Callback;'
W/dalvikvm( 406): Link of class 'Lcom/android/setupwizard/BaseActivity;' failed

W/dalvikvm( 406): Unable to resolve superclass of Lcom/android/setupwizard/Setu
pWizardActivity; (165)
W/dalvikvm( 406): Link of class 'Lcom/android/setupwizard/SetupWizardActivity;'
failed
D/AndroidRuntime( 406): Shutting down VM
W/dalvikvm( 406): threadid=3: thread exiting with uncaught exception (group=0x4
001da28)
E/AndroidRuntime( 406): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 406): java.lang.RuntimeException: Unable to instantiate activ
ity ComponentInfo{com.android.setupwizard/com.android.setupwizard.SetupWizardAct
ivity}: java.lang.ClassNotFoundException: com.android.setupwizard.SetupWizardAct
ivity in loader dalvik.system.PathClassLoader@4320b568
E/AndroidRuntime( 406): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2324)
E/AndroidRuntime( 406): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2417)
E/AndroidRuntime( 406): at android.app.ActivityThread.access$2100(Activi
tyThread.java:116)
E/AndroidRuntime( 406): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1794)
E/AndroidRuntime( 406): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 406): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 406): at android.app.ActivityThread.main(ActivityThrea
d.java:4203)
E/AndroidRuntime( 406): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 406): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 406): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 406): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:549)
E/AndroidRuntime( 406): at dalvik.system.NativeStart.main(Native Method)

E/AndroidRuntime( 406): Caused by: java.lang.ClassNotFoundException: com.androi
d.setupwizard.SetupWizardActivity in loader dalvik.system.PathClassLoader@4320b5
68
E/AndroidRuntime( 406): at dalvik.system.PathClassLoader.findClass(PathC
lassLoader.java:243)
E/AndroidRuntime( 406): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:573)
E/AndroidRuntime( 406): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:532)
E/AndroidRuntime( 406): at android.app.Instrumentation.newActivity(Instr
umentation.java:1097)
E/AndroidRuntime( 406): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2316)
E/AndroidRuntime( 406): ... 11 more
I/Process ( 72): Sending signal. PID: 406 SIG: 3
I/dalvikvm( 406): threadid=7: reacting to signal 3
E/dalvikvm( 406): Unable to open stack trace file '/data/anr/traces.txt': Permi
ssion denied
I/DumpStateReceiver( 72): Added state dump to 1 crashes I/ActivityManager( 72): Process com.android.setupwizard (pid 397) has died.
I/ActivityManager( 72): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.setupwiza
rd/.SetupWizardActivity }
I/ActivityManager( 72): Start proc com.android.setupwizard for activity com.an
droid.setupwizard/.SetupWizardActivity: pid=406 uid=10014 gids={3003}
W/UsageStats( 72): Something wrong here, didn't expect com.android.setupwizard
to be resumed
W/dalvikvm( 406): Unable to resolve superclass of Lcom/android/setupwizard/Netw
orkMonitor$Callback; (285)
W/dalvikvm( 406): Link of class 'Lcom/android/setupwizard/NetworkMonitor$Callba
ck;' failed
I/dalvikvm( 406): Failed resolving Lcom/android/setupwizard/BaseActivity; inter
face 204 'Lcom/android/setupwizard/NetworkMonitor$Callback;'
W/dalvikvm( 406): Link of class 'Lcom/android/setupwizard/BaseActivity;' failed

W/dalvikvm( 406): Unable to resolve superclass of Lcom/android/setupwizard/Setu
pWizardActivity; (165)
W/dalvikvm( 406): Link of class 'Lcom/android/setupwizard/SetupWizardActivity;'
failed
D/AndroidRuntime( 406): Shutting down VM
W/dalvikvm( 406): threadid=3: thread exiting with uncaught exception (group=0x4
001da28)
E/AndroidRuntime( 406): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 406): java.lang.RuntimeException: Unable to instantiate activ
ity ComponentInfo{com.android.setupwizard/com.android.setupwizard.SetupWizardAct
ivity}: java.lang.ClassNotFoundException: com.android.setupwizard.SetupWizardAct
ivity in loader dalvik.system.PathClassLoader@4320b568
E/AndroidRuntime( 406): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2324)
E/AndroidRuntime( 406): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:2417)
E/AndroidRuntime( 406): at android.app.ActivityThread.access$2100(Activi
tyThread.java:116)
E/AndroidRuntime( 406): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1794)
E/AndroidRuntime( 406): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 406): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 406): at android.app.ActivityThread.main(ActivityThrea
d.java:4203)
E/AndroidRuntime( 406): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 406): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 406): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 406): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:549)
E/AndroidRuntime( 406): at dalvik.system.NativeStart.main(Native Method)

E/AndroidRuntime( 406): Caused by: java.lang.ClassNotFoundException: com.androi
d.setupwizard.SetupWizardActivity in loader dalvik.system.PathClassLoader@4320b5
68
E/AndroidRuntime( 406): at dalvik.system.PathClassLoader.findClass(PathC
lassLoader.java:243)
E/AndroidRuntime( 406): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:573)
E/AndroidRuntime( 406): at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:532)
E/AndroidRuntime( 406): at android.app.Instrumentation.newActivity(Instr
umentation.java:1097)
E/AndroidRuntime( 406): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:2316)
E/AndroidRuntime( 406): ... 11 more
I/Process ( 72): Sending signal. PID: 406 SIG: 3
I/dalvikvm( 406): threadid=7: reacting to signal 3
E/dalvikvm( 406): Unable to open stack trace file '/data/anr/traces.txt': Permi
ssion denied
I/DumpStateReceiver( 72): Added state dump to 1 crashes

I reflashed this ROM a few times, sometimes repartitioning, sometimes wiping, sometimes both...tried with ext[2,3,4], sometimes fixing the permissions, sometimes not.

No matter what I did, it would not let me get to the point where I could skip the setup wizard.

I tried numerous 1.6 based ROMs, including official releases from T-Mo, and Enoms 2.6.2 Base. Each and every ROM is giving me the same problems with the Setup Wizard being FCd.

I was working with Shadoch31 yesterday, and he recommended that I un-root, to bring the core of everything back to stock, which I did. The un-rooted device boots up fine, and I see the generic OS that came with the G1 when it was initially purchased.

I then re-rooted, upgraded the radio to 2.22.19.26i, upgraded the SPL to Hykuro's Death, and then tried to flash another custom ROM. I do not recall which one I tried to flash this time around, but I received the same exact problems.

One thing I noticed when the new ROM is booting, is the mountpoints seem a little bit odd...here is what I have:

In the past, I remember seeing that /system/[app,app-private,dalvik-cache] symlinked to system/sd/[app,app-private,dalvik-cache], but, that is not the case in any rom I try now. Also, /system/sd/app remains empty, with no applications in there. And there are times when I see a zero length file in there named 'placeholder'.

Below is the output of 'busybox ls -lL /system':

And here is ls -lL /data:

I am not seeing any symlinks anywhere...now, there may be a new process for using apps2sd, which does not require symlinks, which I am not aware of.

Logcat from HTC Clay 2.3: http://pastebin.com/KDjtA6YC

Logcat from HTC Clay 3.0.3: http://pastebin.com/DnYQYx2b

You can see in both of those log files that there is a lot of looping going on.

Does anyone have any ideas of what might be going wrong? I have tried different SD cards, different partitioning schemes, different ways of downloading and transferring the ROMs to the SD card, etc. I even verified MD5 sums when they were provided. Everything checks out just as it should, but it is still a no-go.

Both Shadoch31 and I are completely stumped, and have decided to see if anyone else can shed some light as to what might be causing this hicup in my flashing process.