TouchPad Bootloop After Memboot

[Vistaus]

So I tried to doctor my Touchpad with the 3.0.5 Doctor. Went well, until the reboot. After the reboot, it got stuck in a bootloop. Everything I tried didn't work, so I ended up recreating the file system following a guide on here and run the doctor after that. That did work, but it still got stuck in a bootloop afterwards. I am able to boot into bootie, but novaterm just hangs. I am able to use novacom though and it lets me run some specific commands, but I'm not sure what to do.

How can I fix this now? I want webOS back and need it also for work

[jaltman]

Try membooting and downloading a new kernel. See Memboot - WebOS Internals

[Vistaus]

Thanks, tried that, but still in the boot loop

[sledge007]

<thread moved>
<title clarified>

I just moved this over to webOS Internals forum so that it might get noticed by them a little sooner, as opposed to getting lost in general TouchPad forum.

[Vistaus]

Thanks! But the title is still not accurate as the bootloop was there before I tried memboot. But thanks for moving it!

[sledge007]

I'm sure they'll understand. The only reason (I would think) you would do a memboot, is because you're bootlooped. Hope you get it resolved soon, frustrating I'm sure.

[Vistaus]

Noone?

[jaltman]

Perhaps extract a 3.0.4 kernel file and try membooting that? Or, just doctor back to 3.0.4 and see what happens? If that works you could might do a total system wipe before retrying 3.0.5.

[Vistaus]

I tried membooting 3.0.4 file. But why would it work to doctor 3.0.4?

[Vistaus]

Is this really such an impossible problem?

[Vistaus]

Come on people, I need my Touchpad for some work things. Can seriously noone help me?

[Vistaus]

So I can basically throw my Touchpad away it seems. Thanks for the great help!

[John Steffes]

Originally Posted by Vistaus

So I can basically throw my Touchpad away it seems. Thanks for the great help!

Without seeing the command line output it is hard to help?

[Vistaus]

Originally Posted by John Steffes

Without seeing the command line output it is hard to help?

Someone could've asked for the Terminal-output, but it doesn't really matter anyway since Novaterm can't reach the Touchpad anymore (though Novacom itself can).

[John Steffes]

Originally Posted by Vistaus

Someone could've asked for the Terminal-output, but it doesn't really matter anyway since Novaterm can't reach the Touchpad anymore (though Novacom itself can).

Well if one uses novacom and uses the uimage to boot it would produce a command line output...

[Vistaus]

Originally Posted by John Steffes

Well if one uses novacom and uses the uimage to boot it would produce a command line output...

Such as "Waiting for device..." in my case? I have the TP booted to USB Recovery Mode so it should be recognized, but it isn't (and it was before).

[jaltman]

Well, i suggested Doctoring an older version, but you rejected that idea. I might have some other ideas, but you'll probably reject them too.

[Vistaus]

Originally Posted by jaltman

Well, i suggested Doctoring an older version, but you rejected that idea. I might have some other ideas, but you'll probably reject them too.

If my Touchpad is barely recognized by Novacom, then how is it supposed to Doctor? Please explain to me that first.

[sirocyl]

I'm having this, or a similar issue, and I'm in the process of troubleshooting it.
Any help is appreciated. I will document the steps used to troubleshoot this.

Situation:
- Touchpad 32GB WiFi
- Used with highly experimental software - Android builds, desktop GNU/Linux distros
(I am fully aware that I take full responsibility for my actions as a result of that)
- Have default Cyanogen/ACME-created partitions in the lvm space
- Have a 4GB ext3fs partition for experiments

Issue:
- Doctored to 3.0.5, using java -jar <doctor name>.jar from commandline
- Doctor showed no issues through UI, cursory glance over console log shows no issues either
- Touchpad reboots, and then Kernel panics and reboots repeatedly.

Clarification:
- Output from novacom get file://klog follows:

<6>pm8058-rtc pm8058-rtc: setting system clock to 2012-02-21 17:51:06 UTC (13298
46666)
<6>msm_v4l2: msm_v4l2_init
<6>EXT3-fs: barriers not enabled
<6>kjournald starting. Commit interval 5 seconds
<6>EXT3-fs (mmcblk0p13): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) readonly on device 179:13.
<0>Kernel panic - not syncing: No init found. Try passing init= option to kerne
l. See Linux Documentation/init.txt for guidance.
[<80045afc>] (unwind_backtrace+0x0/0x160) from [<80490818>] (panic+0x6c/0xe8)
[<80490818>] (panic+0x6c/0xe8) from [<8003e7a8>] (init_post+0xac/0xd4)
[<8003e7a8>] (init_post+0xac/0xd4) from [<8000880c>] (kernel_init+0x208/0x260)
[<8000880c>] (kernel_init+0x208/0x260) from [<80040344>] (kernel_thread_exit+0x0
/0x8)
evlog: beg
evlog: end
<2>CPU0: stopping
<0>Rebooting in 5 seconds..[<80045afc>] (unwind_backtrace+0x0/0x160) from [<8003
e310>] (do_IPI+0xc8/0x13c)
[<8003e310>] (do_IPI+0xc8/0x13c) from [<8003ec4c>] (__irq_svc+0x4c/0xe4)
Exception stack(0x80655f40 to 0x80655f88)
5f40: 00000000 00000000 00000001 00000000 00000000 000000f2 00000000 84340160
5f60: 8433ea30 510f02d2 84340170 00000000 00000000 80655f88 800c995c 8008acc8
5f80: 60000013 ffffffff
[<8003ec4c>] (__irq_svc+0x4c/0xe4) from [<8008acc8>] (msm_cpuidle_enter+0x108/0x
128)
[<8008acc8>] (msm_cpuidle_enter+0x108/0x128) from [<80378a0c>] (cpuidle_idle_cal
l+0xd0/0x134)
[<80378a0c>] (cpuidle_idle_call+0xd0/0x134) from [<80040c60>] (cpu_idle+0x7c/0xd
8)
[<80040c60>] (cpu_idle+0x7c/0xd8) from [<80008d6c>] (start_kernel+0x2bc/0x324)
[<80008d6c>] (start_kernel+0x2bc/0x324) from [<40208084>] (0x40208084)

[jaltman]

Originally Posted by Vistaus

If my Touchpad is barely recognized by Novacom, then how is it supposed to Doctor? Please explain to me that first.

I would prefer to know what you have to lose by trying it, other than a few minutes of your life. When I first suggested it you were merely bootlooping and doctor had run fine, albeit without solving the problem.