Aura ONE Forcing Connect to PC without using screen

[ReaLx3m]

Thanks to kwiatek69 i became a owner of an Aura One. It is a broken one, but no matter was pretty happy to get it and im very grateful to the guy.
I managed to bring it in more or less working order, but still have some issue that i cant figure how to work around, so maybe some of you can give me an idea.

The flex cable for the digitizer(touch) has been damaged(stabbed with a sharp object) during initial opening, so a part of the screen doesnt respond to touch.
Right where the "connect" to PC button is.

Tried loading from calibre/opds server, but keyboard number area was also covered by the issue so i couldnt input the ip address of the server. I managed to work around this by running a hotspot from the pc using a wireless adapter, and edited PC hosts file to point to that address by using a name that can be typed by the usable part of the keyboard. Tip might come in handy to someone in similar situation.
But for the irony to be greater, unresponsive touch also covers the space where the confirm download button is when trying to load from calibre/opds server using the browser.
Going from top to bottom, approximately 50-75% area of the touch doesnt respond.

So at the moment im stuck. Does anyone have any suggestion how to work around this and force it connecting to pc without pressing the button? Or some alternative method of loading files to it that i havent thought of?

Managing to load Koreader would be great as connect to pc is in part of screen that works and doesnt need any confirmation. Maybe someone has an idea/tips how to trick it loading as an official firmware update by running local apache server?

Atm im still wary of trying to remove the screen alltogether and check if the flex cable is soldered to the digitizer or can be replaced, as it doesnt look kobo made Aura One with easy fixability in mind. Havent removed a screen on Aura One previously, so wouldnt like to break it in the process as long as there is still some hope to make it useable.

Any input appreciated.

[geek1011]

If you can enable developer mode, do that. Otherwise, I think you'll need to factory reset it to get the usb to autoconnect.

After you get a connection, you can use remote access and/or NickelMenu for future connections.

[ReaLx3m]

Originally Posted by geek1011

If you can enable developer mode, do that. Otherwise, I think you'll need to factory reset it to get the usb to autoconnect.

After you get a connection, you can use remote access and/or NickelMenu for future connections.

I managed to enable devmode, but cant see anything relevant there like enabling autoconnect. Am i missing something?

Havent done a factory reset for very long time, and cant recall is there any confirmation dialogs on the reader in the affected touch area in the process that might leave me stranded on that screen?

[davidfor]

There isn't anything on the screen. But, you can telnet into the device and edit the config to add the hidden option. The config file is "/mnt/onboard/.kobo/Kobo/Kobo eReader.conf". Find the line with "[DeveloperSettings]". After this, add a line with "AutoUsbGadget=true". There should be several similar lines. The order isn't important as long as the new line is before the next section heading (Lines like "[SomethingOrOther]").

With that in place, the device should connect automatically.

[ReaLx3m]

Originally Posted by davidfor

There isn't anything on the screen. But, you can telnet into the device and edit the config to add the hidden option. The config file is "/mnt/onboard/.kobo/Kobo/Kobo eReader.conf". Find the line with "[DeveloperSettings]". After this, add a line with "AutoUsbGadget=true". There should be several similar lines. The order isn't important as long as the new line is before the next section heading (Lines like "[SomethingOrOther]").

With that in place, the device should connect automatically.

Oh nice, youll have to hold my hand for a bit as i havent used telnet for very long time and have basic understanding of it. The device got detected and i logged in with user root and no password. Cd to the folder where the config is , but dont know the command to open the file for editing. Can you point me in the right direction?

Edit: Im using PuTTY, in case that makes any difference

[davidfor]

Originally Posted by ReaLx3m

Oh nice, youll have to hold my hand for a bit as i havent used telnet for very long time and have basic understanding of it. The device got detected and i logged in with user root and no password. Cd to the folder where the config is , but dont know the command to open the file for editing. Can you point me in the right direction?

Edit: Im using PuTTY, in case that makes any difference

You can use vi to edit the file. Find the line I mentioned, type "o" (without the quotes) to add a line after it and type in the new line. Press the escape key and then ":wq" to save the changes an exit.

[ReaLx3m]

Originally Posted by davidfor

You can use vi to edit the file. Find the line I mentioned, type "o" (without the quotes) to add a line after it and type in the new line. Press the escape key and then ":wq" to save the changes an exit.

We have a liftoff . It was the space in Kobo eReader.conf filename that was giving me grief with vi, was opening an empty file. Finaly figured that filenames with space need to be in quotation marks to be opened correctly.

Thank you for your help, couldnt have done it without you.

[ReaLx3m]

Btw, can touch events be sent to reader via telnet using xy coordinates?

[NiLuJe]

Yup. The protocol is a little wonky, but it's more-or-less Linux evdev as usual (c.f., this for a standalone dumb example, and Plato/KOReader for a full input framework).

[Quoth]

Originally Posted by davidfor

There isn't anything on the screen. But, you can telnet into the device and edit the config to add the hidden option. The config file is "/mnt/onboard/.kobo/Kobo/Kobo eReader.conf". Find the line with "[DeveloperSettings]". After this, add a line with "AutoUsbGadget=true". There should be several similar lines. The order isn't important as long as the new line is before the next section heading (Lines like "[SomethingOrOther]").

With that in place, the device should connect automatically.

And cut the data wires if there is problem with a charger getting recognised as a PC. Usually red and black is power.

[ReaLx3m]

Originally Posted by NiLuJe

Yup. The protocol is a little wonky, but it's more-or-less Linux evdev as usual (c.f., this for a standalone dumb example, and Plato/KOReader for a full input framework).

Thanks, much appreciated.