rooting inkpalm without ADB

[EleanorRagone]

Not sure if you're amenable to helping me track down my problem or not, but you seem to have the knowledge that might get me past where I'm at.

So I somehow managed to get myself into a bit of a pickle... After successfully setting things up, I wanted to start over as I had installed several launchers and just wanted to try everything from the beginning. I decided I would change the language to English as one of the first things I did. So I factory reset the device, then used ADB to change the language to English. Great! Until I got to the (I think) last screen of the setup process, where it says "Basic operating instructions", and has a right arrow and says "Enter Moaan" under it at the bottom, and doesn't do anything no matter where I press on the screen. I can't go back, I can't go forward. Even better, somehow ADB is no longer able to see the device.

Any thoughts on how to troubleshoot this?

[qwerty12]

I don't have my inkPad any more, so there's not really much I can check, but...

USB debugging being disabled after a factory reset is expected; you'll need to do something like this to re-enable it. The thing is, the recovery on the inkPad is the restricted, standard-fare environment. It's not impossible to do those steps, but you'll need to write your own recovery script (and do the stuff described in the guide to sign the ZIP file containing it) that does something like mount /data and writes to the files necessary to enable ADB. It's been a very long time since I've looked at any of this, but I think you can write a recovery script that extracts a shell script from the ZIP archive to /tmp and then executes that - it might be easier to write to the necessary files from a shell script instead of spending time working out what Edify commands the inkPad recovery accepts.

As to how to get to the recovery environment without ADB, I have no idea. I have memories of just letting the battery drain and then praying I hit the right buttons when plugging the USB cable back in while connected to my PC...

Any thoughts on how to troubleshoot this?

At risk of stating the obvious, ADB is necessary. My guess would be something was removed from the /system partition (think pm uninstall <package> vs pm uninstall --user 0 <package>) but that's something only a logcat could confirm.