Database Info

[APP]Ubuntu Install Guide - Galaxy Note Testers wanted - 12.04 in testing

I have working on a project in the form of an app, which guides you through the installation of Ubuntu within android via chroot. It includes a ubuntu 10.10 image I have been working on which includes lots of program to allow users to develop program/scripts etc within Ubuntu on there phone/tablet.
However I have I have yet to get much testing on this device and would like more feedback from users!
Please post your device/kernel/rom along with what did and didn't work, so I can draw up what I need to change in the next release of the app/ubuntu build.
Website
http://linuxonandroid.blogspot.com/
Video
http://www.youtube.com/watch?v=UCqzs8yQTM8
App Download
Free App
Paid App
Boot Script
ubuntu.sh(V5)
Full Image
This image is 1.5GB to download, once extracted 3.5GB, and include alot of programs like openoffice, thunderbird, firefox and over programs for 'developing' - Also allows you to switch between the LXDE and Gnome desktops, and you can define screen size on boot!
ubuntuV5-image.zip
Lightweight Image - This is yet to be included in an app, will be included in the next release (aka 2.0 ), so get it now before anyone else!
This image is just under 500MB to download, once extracted 2.5GB, and include only programs needed (LXDE desktop, web browser, + other basic programs) also allows you to define screen size on boot
ubuntuV5-sm-image.zip
12.04 images
I have now started work on building new 12.04 images these come in core (just the bear-bones ubuntu) and full (ubuntu with GUI and other programs) and will be updated as 12.04 moves through its milestones (and when I make new updates to the mods I make from the main stream arm port).
These are for testing ONLY until 12.04 reaches stable release.
You can view the images here:
http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/12.04/
I also want to build up a small group of testers who I can email with new images and scripts, these will include all future distros that I do. If you are interested in joining this test group please PM me or send a email to [email protected]
The only requirement is that your willing to test and send feedback along with screen shoots etc where required, it would also be good if your willing to try different roms and kernels for your device!
Sig Banner
Show your love of ubuntu on android with my sig banner:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
image url is "http://dl.dropbox.com/u/11206993/ubuntuuser.png"
Other Guides
Like this guide? want to try something different? then check out my other guides for different distro's
Backtrack - This is a distro that is based around security testing, it also includes the Gnome desktop environment and a range of other programs.
Updates
18/02/12
*New 12.04 images started building, for now not included in the app but once a bit more stable will be included
29/01/12
*New V5 small image, featuring fixed Java, even more lightweight (now around 1.2GB free) and user can set screen size on boot
*PAID New Build guide which shows you how to build your own Ubuntu images
*Brand new UI To make the whole thing more useable
*PAID new 'one click boot' feature to allow quick booting from either the widget or inside the app
*PAID new widget to activate the one click boot
*PAID app install guide changed in light of 'one click boot'
*Fixed keyboard mapping of random letters in Gnome
18/01/12
*Large ubuntu image now allows user to set screen size on boot!
*Large Ubuntu image now lets you select between LXDE and Gnome desktops
*Large Ubuntu image has been recompiled to fix the likes of Java (note some of the above changes will be included in the small image in the future)
*FAQ section updated with more answers to questions I have been getting
*Install guide updated in light of the new large image
06/01/12
*PAID app file downloads now use new fast FTP server and support direct downloading (click the button to download a image and it starts to download right away)
*New boot script which has fixed problems with it not booting on alot of devices, and fixed problem which some people getting a grey screen when loading UI
*Boot script now downloaded in zip file to fix problems with downloading script
*Both apps fixed to support low resolutions
*Both apps cleaned up
28/12/11
*PAID app now supports 960x540 'qHD' resolution
*ALL Ubuntu lightweight images cleaned up even more saved another 300MB of space
*ALL Ubuntu images updated with all new updates
*ALL Ubuntu images now in .zip format to fix problems with some peoples devices failing to extract the .rar files
*Boot script updated, once booted now terminal acts like a command line interface for Ubuntu, and some boot problems now fixed
*Image and boot script now downloadable separately to allow easier updating
19/12/11
New 'lighter' ubuntu image options for all resolutions already supported
15/12/11
New ubuntu images with all updates up to 15/11/11
FREE app ubuntu image resized to fit 800x480 resolution
PAID app ubuntu images now includes 4 images for 800x480, 854x480, 1024x600 and 1280x800 resolutions

http://forum.xda-developers.com/showpost.php?p=20598548&postcount=83
Samsung Galaxy Note G7000
FM 1.5 Kernel
RocketRom V10 (14Toggle, smoothnessupdate, addperformance, stock theme)
Note freezes after executing ubuntu.sh, only restarting by holding powerbutton helps...
It's a pity, I thought booting ubuntu is only possible on a Rom with loop devices capabilities and now I read that only the stock rom is working
tried ubuntuv3.sh see picture:
http://imageshack.us/f/808/sc20111223042953.png/

Allamann said:
http://forum.xda-developers.com/showpost.php?p=20598548&postcount=83
Samsung Galaxy Note G7000
FM 1.5 Kernel
RocketRom V10 (14Toggle, smoothnessupdate, addperformance, stock theme)
Note freezes after executing ubuntu.sh, only restarting by holding powerbutton helps...
It's a pity, I thought booting ubuntu is only possible on a Rom with loop devices capabilities and now I read that only the stock rom is working
tried ubuntuv3.sh see picture:
http://imageshack.us/f/808/sc20111223042953.png/
Click to expand...
Click to collapse
Indeed its VERY odd that stock works but custom roms do not work...should really be the other way round, perhaps something to do with how the device file system in custom roms is different or something?
I don't know, this is the problem trying to support as many devices as possible, I don't have the device to test and work out what's wrong, just got to keep basically stabbing into the dark until I hit something

Change log for new release (release will be in the next few days for paid end of next week for free) - all new images etc will be added to the first post as they are finished and uploaded!
*PAID app now supports 960x540 'qHD' resolution
*ALL Ubuntu lightweight images cleaned up even more saved another 300MB of space
*ALL Ubuntu images updated with all new updates
*ALL Ubuntu images now in .zip format to fix problems with some peoples devices failing to extract the .rar files
*Boot script updated, once booted now terminal acts like a command line interface for Ubuntu, and some boot problems now fixed
*Image and boot script now downloadable separately to allow easy updating of the script
*+more likely before release

Allamann said:
http://forum.xda-developers.com/showpost.php?p=20598548&postcount=83
Samsung Galaxy Note G7000
FM 1.5 Kernel
RocketRom V10 (14Toggle, smoothnessupdate, addperformance, stock theme)
Note freezes after executing ubuntu.sh, only restarting by holding powerbutton helps...
It's a pity, I thought booting ubuntu is only possible on a Rom with loop devices capabilities and now I read that only the stock rom is working
tried ubuntuv3.sh see picture:
http://imageshack.us/f/808/sc20111223042953.png/
Click to expand...
Click to collapse
+1 I got it to boot with cf kernel but not with fm or abyss kernel.
Sent from my GT-N7000 using xda premium

timstanley1985 said:
+1 I got it to boot with cf kernel but not with fm or abyss kernel.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Odd so I'm guessing the two kernels that don't work don't have loop support...best talk with the kernel developer
Sent from my HTC Desire S using XDA App

timstanley1985 said:
+1 I got it to boot with cf kernel but not with fm or abyss kernel.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yep, I was really enjoying - had PHP and mysql installed and working as a wee test environment, then flashed FM and no more Ubuntu.
Thanks for the work - appreciated

If I manually downloaded the script and the image, where do I put
the extracted content of the zip, and the script ? on the root of external SD or phone storage ?

lucid said:
If I manually downloaded the script and the image, where do I put
the extracted content of the zip, and the script ? on the root of external SD or phone storage ?
Click to expand...
Click to collapse
Place them in a folder called ubuntu on either your sdcard or internal memory as you have both either should work
Sent from my HTC Desire S using XDA App

Thanks, by pressing ahead without knowing I put the files there, however, in terminal emulator, after aquiring superuser persmissions, changing to the ubuntu folder wont work. I must be doing something wrong. I came as far as cd /sdcard but /sdcard/ubuntu fails. Asking ls -a says dir is empty ? Linux noob

lucid said:
Thanks, by pressing ahead without knowing I put the files there, however, in terminal emulator, after aquiring superuser persmissions, changing to the ubuntu folder wont work. I must be doing something wrong. I came as far as cd /sdcard but /sdcard/ubuntu fails. Asking ls -a says dir is empty ? Linux noob
Click to expand...
Click to collapse
check in a file explorer where the sdcard is mounted, sometimes the internal memory is mounted as the sdcard directory and then the sdcard itself is mounted in another directory within that.
Once you work out where its mounted then just cd to that location

Got it to work. Copied the ubuntu folder to /
Pretty responsive in 24bit colour. Working with cassies ultralight v4.

lucid said:
Got it to work. Copied the ubuntu folder to /
Pretty responsive in 24bit colour. Working with cassies ultralight v4.
Click to expand...
Click to collapse
which Kernel/Rom?

Hi
Before run ubuntu.sh check if loop inst bussy with other kind of programs who use it.
try losetup will show you how many loop you have used and edit ubuntu.sh to get 1 free
like last 1 user will be 10 then line with busybox mknod /dev/loop11 b 7 11
and wher you see loop0 change to loop11 or any free number.
Hope will works for you.
---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------
Hi,
Nice work but you forgot something.
Your image wont work on many device since the /sdcard partition if VFAT who limit the file to 2G.
converting /sdcard to ext2 or ext4 is the way to work with files larger than 2G.
B.

dahas said:
Hi
Before run ubuntu.sh check if loop inst bussy with other kind of programs who use it.
try losetup will show you how many loop you have used and edit ubuntu.sh to get 1 free
like last 1 user will be 10 then line with busybox mknod /dev/loop11 b 7 11
and wher you see loop0 change to loop11 or any free number.
Hope will works for you.
---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------
Hi,
Nice work but you forgot something.
Your image wont work on many device since the /sdcard partition if VFAT who limit the file to 2G.
converting /sdcard to ext2 or ext4 is the way to work with files larger than 2G.
B.
Click to expand...
Click to collapse
Thank you very much I will integrate these changes in the next version of the script

you can also change de fstab line where root partition is mount by uuid and replace by name

losetup returns nothing...
I also asked the dev of FM kernel and he told me that it has loop capabilities

if losetup show nothing then or you dont have loop set or you not root.
for see if you r root type id and the have to show your id. If is not root type su -
For the no loop set then the original ubuntu.sh have to work.

Runs perfectly on my Note
Had rooted it yesterday with CFRootFlasher
Kernel is "KK9" (Android 2.3.6)
Tested the V3 800 first, and now running with the V4 1280 image
Btw I´m an Android noob, came from Ios 2 weeks ago, so i dont really know what is important for you to know. But if you want to know something, just ask

kevinturbo said:
Runs perfectly on my Note
Had rooted it yesterday with CFRootFlasher
Kernel is "KK9" (Android 2.3.6)
Tested the V3 800 first, and now running with the V4 1280 image
Btw I´m an Android noob, came from Ios 2 weeks ago, so i dont really know what is important for you to know. But if you want to know something, just ask
Click to expand...
Click to collapse
Thank you very much, glad to hear you have it working!
And welcome to the dark side

Dual booting Windows RT and RT 8.1

Dual booting Windows RT and RT 8.1 (almost)
I was original working on dual booting RT from internal flash and from SD card
by adding extra entries in the bcd store and a ‘copy’ of windows on the SD card
Note it actually still boots from the system partition on the internal flash but tries to boot an alternate Windows installation from \windows on the SD card
http://forum.xda-developers.com/showthread.php?t=2343101
But now moved on to dual booting Windows RT and RT 8.1 (both from internal flash)
and almost have it working
Installing the RT 8.1 Preview saves the old OS in \windows.old\windows
Or rather saves most of it, but not all
So you need to pre-save much of the original \windows elsewhere, using the recovery environment, BEFORE installing 8.1
as certain important bits seem to get stripped out of windows.old
Then use the same technique of adding entries to the bcd store to allow the system to boot from \windows.old\windows
It wont be perfect as it will pick up certain hard coded \windows stuff and also will pick up the wrong \Program Files
but should be just about usable, especially in desktop mode which is the reason for keeping the original OS
It does boot, but doesn’t pick up the Start screen properly, so need further work on that
Could do it properly if we shrank the C: volume and set up a new dedicated volume for the alternate OS
Original RT
Use recovery environment to make a copy of
\windows\system32\*
\windows\system32\config\*
\windows\system32\drivers\*
Would be easier to copy \windows /s but then get a bloated mess due to the WinSxS hardlinks
Install 8.1 Preview
copy the copied data over the top of \windows.old\windows
will be lots of access denied for files already there
but will copy the important missing files
including the registry hives, ntoskrnl.exe, winload.efi [need the old winload.efi as the new one wont accept the signature of the old ntoskrnl etc]
Suspend bitlocker (if in use)
manage-bde -protectors -disable c:
bcdedit /copy {current} /d "Windows RT 8.0 hack”
note the new guid
bcdedit /set {guid} recoveryenabled no
bcdedit /set {guid} path \windows.old\windows\system32\winload.exe
bcdedit /set {guid} systemroot \windows.old\windows
Restart (or shift restart)
Select the Windows RT 8.0 hack
The original RT OS boots but no Start screen
but is running and a dot will follow your finger
Need to modify the windows.old registry and fix up something
To be investigated
Can also test and develop this with Windows 8.1 Intel on a PC
That also doesn’t get the full Start screen on the hacked (barstardised) alternate boot back to 8.0
Also best to rename \windows.old to something else, as \windows.old gets removed after a few days

Note, this is a hack
The correct method would be to set up seperate OS partition on the internal flash drive
(but a bit small to do that)
Or to get the alternate OS to boot from SD card

Also as mentioned in the 8.1 jailbreak thread, RT 8.1 wont run RT 8.0 OS binaries or office binaries
(due to the new and more restrictive signatures needed by RT 8.1)

You can create a VHD and extract recovery WIM there to get a complete copy of OS. Earlier I've played with that with success.
One note: you can't use the recovery to restore the original "main" windows while BCD has an VHD entry - it fails with an undescriptive error.

My windows8.1 recovery file is .esd not .wim.So I must install windows8.1 first then make a windows8.0 vhd?And microsoft says windows rt cant boot from VHD.

windowsrtc said:
My windows8.1 recovery file is .esd not .wim.So I must install windows8.1 first then make a windows8.0 vhd?And microsoft says windows rt cant boot from VHD.
Click to expand...
Click to collapse
Yes, just take WIM from the recovery partition of 8.0, extract it to VHD, then upgrade to 8.1
I was playing with the windows PE - it could boot from VHD. So I assume that "big" RT would boot too, but had no mood to finish tests.

Enjoy this while you can, because I suspect that the Windows 8.1 final release will include a firmware update that locks out booting 8.0 forever on your device.
Also, disable Windows Update or change it to manual mode, on both 8.0 and 8.1!! I think Microsoft will release RT 8.1 as a free upgrade that is forced upon 8.0 by being labeled an important Windows update.

I think I am strong enough to return my surface to microsoft and get my money back if microsoft block my windows 8.0.And then I will say goodbye to any windows rt device.

Myriachan said:
.. I suspect that the Windows 8.1 final release will include a firmware update that locks out booting 8.0 forever on your device.
Click to expand...
Click to collapse
Definitely not, at least not immediately after the 8.1 official release. As this would cause lots of complains and support calls from people not being able to use the recovery USB disks in the case if the upgrade process goes wrong or if they'd like to return to backup.

mamaich said:
Definitely not, at least not immediately after the 8.1 official release. As this would cause lots of complains and support calls from people not being able to use the recovery USB disks in the case if the upgrade process goes wrong or if they'd like to return to backup.
Click to expand...
Click to collapse
Microsoft is copying Apple--that is the whole reason Windows 8 exists--and Apple is even worse than this, giving Microsoft plenty of precedent. On iPads, not only can you not downgrade after you upgrade, you can't even do a restore to your current version. If your iOS device is corrupted, you have to upgrade to the newest version.
Apple's enforcement of this mechanism is that during the reflash operation, the boot ROM generates a random challenge that needs to be answered by Apple's servers with public-key cryptography. Therefore, you can never flash a version of the OS to your device unless Apple is authorizing that version at that particular moment.
I don't think that Microsoft will add a phone-home requirement to restores like Apple does, but I think that they will lock out the old version.

Apple does not officially allow you to make a backup copy of your OS including all your data to a bootable USB. So they don't need to care about user-made backups. While MS recommends doing this before upgrade - so they'd need to support a downgrade path.
Anyway we see one improvement in Win8 development infrastructure. MS have published the whole Windows 8.1 RT WDK (a driver-maker kit), including all import libraries for usermode apps. So you can create a driver for WinRT or a normal desktop app without old hacks with manual import-library creation (of cause you'll need a working "jailbreak" or a development device). Have they done this as a mistake or intentionally - I don't know, but anyway go and grab your copy

windowsrtc said:
My windows8.1 recovery file is .esd not .wim.So I must install windows8.1 first then make a windows8.0 vhd?And microsoft says windows rt cant boot from VHD.
Click to expand...
Click to collapse
ESD file is an encrypted WIM file. The 8.1 upgrade process has trashed the recovery partition upgrading it to 8.1
Today I'll try to revert to 8.0 (fortunately I've made a recovery USB before upgrade), then try to make an 8.1 VHD to use it in parallel with 8.0.
I'll publish instructions when (or if) I'll succeed.
And yes, seems that 8.1 stopped to support booting from VHD. At least I was unable to do this from the first attempt. But I had success with VHD in 8.0, so I'll start from reverting to it.

Here is a simple method of having both 8.0 and 8.1 on the same device. You'll need a 64Gb device.
I've decided not to play with VHD any more and just added the another partition.
So here is what to do (do everything in a running Windows 8.0, not in a command line mode):
1. manage-bde -protectors -disable c:
2. Shrink your OS partition from disk manager GUI leaving about 20 Gb free space.
3. Create new partition over the free space, format it to NTFS, add a drive letter, say, F:
4. Obtain image.wim from your recovery USB or from a recovery partition and do:
Dism /apply-image /imagefile:full-path-to-your-backup-install.wim /index:1 /ApplyDir:F:\
5. Add the needed entries to boot-menu:
bcdedit /copy {current} /d "Windows RT 8.0 copy”
bcdedit /set {guid} device partition=F:
bcdedit /set {guid} osdevice partition=F:
bcdedit /timeout 5
6. Reboot
Select the second OS - you'll see that it boots, but you'll get an error. This is due to the wrong drive letter assignments. Your backup image "knows" that the first partition has drive letter C:, while now this letter should be assigned to the second one. It is easy to fix this, read this article: http://support.microsoft.com/kb/223188. Just boot to a command line environment, run regedit, select HKEY_USERS, use "load hive" menu to load "\Windows\System32\config\SYSTEM" from the second partition (when asked how to name the key - type any name you like), then rename "\DosDevices\C:" to "\DosDevices\Z:" and "\DosDevices\D:" to "\DosDevices\C:" (they are located in HKEY_USERS\your-loaded-key\MountedDevices). Unload hive, reboot - and everything would be fine.
You'll have two OSes, I'd recommend to upgrade the one located on the first partition to 8.1 and leave the newly created one as 8.0, so later, when you'd decide to stay on 8.1 you'd just would need to delete a second partition and expand the 8.1 over the remaining space.
Usual note: be careful when playing with the partitions and registry. As you can't kill the device even by deleting all the partitions (you can always boot from usb and recover them manually) - the recovery process is rather complex for the ordinary user.

mamaich said:
Here is a simple method of having both 8.0 and 8.1 on the same device. You'll need a 64Gb device.
I've decided not to play with VHD any more and just added the another partition.
...
Click to expand...
Click to collapse
Thanks! That worked perfectly, even on my 32Gb Surface RT. :laugh:
I only had to tweak the 5th step a bit; on the second and the third line I had to change "{guid}" to "{current}" if I remember correctly.
But afterwards I didn't even get the error you spoke about, the dual boot worked directly.
I also enabled the classic boot menu with "bcdedit /set {default} bootmenupolicy legacy", as the new one first boots and then lets you choose, which can be time consuming.
The problem with this legacy bootloader on the surface rt is that the touchcover doesn't work, you can select a OS with the volume buttons of the tablet, but you can't press enter.
It works with an usb keyboard, but It would be nice if the touchcover would work.

Hey mates!
I wanted to try out 8.1 final with dual boot on my 64GB surface RT. Are there any updates on this topic?
I would take the instructions from @mamaich and wanted to know if we can use the touch cover to select the OS by now?
If not, we could create 2 scripts for changing the default OS.
1) Placed on 8.0 Desktop: Switch default OS to 8.1 and reboot
2) Placed on 8.1 Desktop: Switch default OS to 8.0 and reboot
Cheers
Blade

So far so good. I got dual-boot 8.0 and 8.1.
mamaich said:
... then rename "\DosDevices\C:" to "\DosDevices\Z:" and "\DosDevices\D:" to "\DosDevices\C:"...
Click to expand...
Click to collapse
I did not have to do this step. Doesnt matter which Windows i load, it sets the active Windows Partition to C and the non active one to F or D
Here I am on my main sytem (Jailbroken RT 8)
Click to enlarge
Here I am on the newly created untouched System 8.1
Click to enlarge
And for {guid} in step 5 line 2 and 3 i inserted the ID given me in the Output of line 1...
For those who got Problems with shrinking the partition: deactivate Pagefile
How to deactivate Pagefile:
press search
type in "advanced"
press on "Settings"
click on "View advanced System Settings"
click on the tab called "Advanced"
click on "Settings" in "Performance"-section
click on "Advanced"-tab
click on "Change" in "Virtual Memory" section
untick "Automactically manage ..."
set bullet-point to "No paging file"
click on "Set"
3 times OK and then reboot
Don't Forget to set it back after resizing!!

A quick warning: you'll probably want to re-enable paging after resizing the partitions. Most RT devices only have 2GB of RAM. Even with just web browsing, email, etc. you could end up hitting that if you're a heavy browser tab like me. Gaming, really big Excel spreadsheets, running desktop apps via jailbreak (why else keep 8.0 around?) and so on are much more likely to hit that limit. When apps hit the limit, and the OS can't increase the commitable memory because there's no paging file to back data swapped out of RAM, stuff will start crashing.

Yes, ofc. I write a warning in my list (I thought it would be self-explaining). Thank you master.
btw I did it. Got dual-booting JB8.0 and RT8.1. everything works very nice. (Even though i used 2nd Partition for win8.1 with only 14,6GB, because I wanted to Keep my highly modified and customized winRT8.0)
For those who want a shortcut on the Desktop to get to advanced boot Options: download shortcut
Works in both 8.0 and 8.1, if C:\ is root path for each (see my last post)
This way you can set the timeout of your boot-menu to 0 and set the OS you are using mainly as Default. To Switch OS simply use the shortcut, OR: open Charms-bar - Settings - Power - hold SHIFT while clicking on restart
After that: [Could not take a screenshot]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello, everyone.
Tomorrow I will get a surface RT with windows 8.1 already. Is it possible to make the dual boot like this too?

If it's a gen1 RT, yes (use the 8.0 recovery image to install it). If it's a gen2 ("Surface 2") then no.

Looking for a complete/real Linux on my Nexus 5

Hello everybody,
I've been trying to get a complete Linux (for example Debian or Ubuntu) on my old Nexus 5 (NOT Ubuntu-Touch). All the Linux commands ("sudo" etc.) should work and I need to install Python.
Since I would like to use the Nexus 5 only for network stuff and bots at home, I don't really need Android anymore on the device.
I have no additional equipment (for exemple Bluetooth keyboard / mouse or USB to HDMI adapter) and I would prefere not buy any equipment.
Windows 10 would be enough as well on the Nexus 5 (I read it should work with some Android devices).
I got TWRP recovery on the phone.
What I've tried so far:
1.
The Maru ROM (Android + Linux parallel running). However, for the first configuration on the Linux-Desktop it seems like I need an adapter + Bluetooth keyboard & mouse, since the first configuration has to be done on the desktop
But have no corresponding periphery.
After the initial configuration of the Linux Desktop/Interface, via USB to HDMI adapter, you can access the Linux system on the Nexus 5 via SSH or VNC.
Apparently it's also possible to do the first configuration of the Linux interface via VNC. But I have not succeeded. I've followed various instructions and tried from Android by using terminal emulator to acces the parallel running Linux. VNC Viewer Apps were also used. Everything did not work out. Either there were error messages that the system is not "listening" on the port or that the access was denied. Is there an idiot-safe step by step guide for this?
2.
Next I flashed "[NEXUS 5][N7.1.2] - Pure Nexus"
I tried to to configur the terminal emulator and Termux with BusyBox and the "sudo installer app" to behave as if the terminal would be a real Linux. I also failed (couldn't get sudo command and other commands to work).
3.
Finally, I've used the "Complete Linux Installer" app. However, it turned out that my kernel does not support "loop device" (which is a prerequisite). So I tested the Franco Kernel and another custom kernel (name forgotten), which also did not work. I haven't found a custom kernel which is explicit "loop device" supported.
What ROM / Kerel Combo is required to use "Complete Linux Installer"?
Since I need no Android it would be the simplest thing to flash Linux (or Win10) with TWRP on to the Nexus 5. Is there some pure Linux ROM for the N5?
Otherwise an idiot-safe step by step guide for the N5 for the method 1 (Maru ROM via VNC without HDMI adapter), or for the method 3 ("Complete Linux Installer") would be great!
If someone has a full functional Linux or Win10 on the Nexus 5 (without additional peripherals) please report! Thanks in advance!

really no one an idea?
A ROM/Kernel Combination for the Nexus 5 with "Loop Device" support would be enough! (see 3. "Complete Linux Installer")

playerkirk1 said:
The only way I could imagine installing Ubuntu or any form of Linux based OS other than android would involve using EFIDroid, which isn't hard to install at all.
Here's the link to that.
I'd imagine you'd have to find a way to efi boot a version of Ubuntu arm or Debian arm, because the Nexus 5 is an arm device. As for Windows 10, IIRC Microsoft still hasn't released Windows 10 arm out yet, so we can't find out if we can port it back to arm32 or lower end Snapdragon devices like the Nexus 5.
Click to expand...
Click to collapse
Ok nice thx! I'll try it with EFIDroid.
Unfortunately I have not much time most recently... So it will have to wait.
I'll report if I manage to run any Linux version on the N5.
One more Question:
Is it easy to find an arm version of Debian or Ubuntu? Haven't searched yet.

Why use EFIDroid?
I built Gentoo linux on my htc hd2 a yaer ago (and lost the image a few weeks ago). It's not really hard to install a full native linux system on your phone and boot to it DIRECTLY (without android).
All you need is
a custom kernel with support for loop devices (may need some changes later for the display, or some dirty hacks)
a base system for gentoo and some linux knowledge
creating a loopback device and using it for the system storage
working from within android in the beginning on the loopback device, until the base system is installed, configured, bootable and has SSH ENABLED via ethernet, with custom ip address (this is tricky, as it's the only way to use the phone before a gui is installed)
working from the pc using ssh, installing all needed packages
failing too many times until everything works
Edit: while installing the system, you must maintain an ssh connection via usb, as i said earlier, and to reach the internet, you must use iptables from the host pc to share the connection and configure your phone to get to the internet using the host.
As i said, i had done it in the past for the HTC HD2, but never posted it (due to ****ty internet connection). I had done all the system compiling directly on the HD2. On such a slow device (1ghz single core, 512mb ram, class 4 sd card) it took about 2 weeks for the GUI to be working.
What i did later was take the same base system and run it on the HTC M8. while it works, display never worked correctly. I had to use a program i compiled to refresh the screen all the time, which consumed cpu quickly.
Anyway, it can be done on any phone. There's no such thing as impossible.
A shot of the end result gui on hd2 (i know, horrible gui and wtf is that resolution )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tl;dr: Install Gentoo linux

@ playerkirk1
Ok thanks. Maybe this way leads to a solution for me.
@ gilbert32
Impressive! That seems to me like pretty advanced work! I'm afraid my Linux knowledge is fare under yours...
But like I thought, it's possible! Thanks for sharing!
gilbert32 said:
a custom kernel with support for loop devices (may need some changes later for the display, or some dirty hacks)
Click to expand...
Click to collapse
So again it depends on the custom Kernel with loop device suport. I couldn't find one explicitly supporting "loop device" for the N5.
If I had, I would have used the "complete Linux installer" app.
(Check out 3. on my first post)

shomu said:
So again it depends on the custom Kernel with loop device suport. I couldn't find one explicitly supporting "loop device" for the N5.
If I had, I would have used the "complete Linux installer" app.
(Check out 3. on my first post)
Click to expand...
Click to collapse
It's not that hard to get it working
Should be about downloading the source code of any kernel you want to use, make menuconfig, adding loop device support and compiling the kernel. it's about 5-6 commands.
I honestly didn't know this was even possible, but this is amazing. I just thought you'd need EFIDroid and an ISO to boot off of, but that seems way too complicated to do reliably. I'll definitely try this myself because it sounds awesome. Thank you, you rock!
Click to expand...
Click to collapse
Yes, it is very possible. In the old days before android (where developers used to port linux to windows mobile devices, using HaRet), it was about compiling a working kernel, adding a ramdisk that prepares the loop device and mounts it, then changing the root to the loop device. In another way, to achieve it on a new phone:
Build the os for your phone, or install it. You must have a working loop device in the end, containing the root filesystem
Create the init file to use with the ramdisk later
compile a kernel that supports all features required by the OS
package the ramdisk and kernel into a bootable image, that you can fastboot boot or flash
On The M8, This is what happens:
Bootloader boots boot.img. I use fastboot boot boot.img since i don't want to override my boot image
kernel boots and runs my init. Which is a series of shell commands.
The commands mount the required partitions, then mount the loopback device to somelocation
init calls for switch_root, which turns somelocation into the new root filesystem, and launches the appropriate init script (IIRC /sbin/init in gentoo)
the new init starts its work, calls for OpenRC, etc etc etc
As i said before, i got it booting on the HTC M8 by grabbing a working boot image for the device, and modifying the ramdisk to use scripts for the HD2. I had modified those scripts to match the M8 requirements, then repackaged the image and voila. If i still had my working image, i would've uploaded it for you and tried modifying the needed files.
If you get the needed kernel working, i will help you with the next steps

and just another pic i found.

gilbert32 said:
It's not that hard to get it working
Should be about downloading the source code of any kernel you want to use, make menuconfig, adding loop device support and compiling the kernel. it's about 5-6 commands.
Yes, it is very possible. In the old days before android (where developers used to port linux to windows mobile devices, using HaRet), it was about compiling a working kernel, adding a ramdisk that prepares the loop device and mounts it, then changing the root to the loop device. In another way, to achieve it on a new phone:
Build the os for your phone, or install it. You must have a working loop device in the end, containing the root filesystem
Create the init file to use with the ramdisk later
compile a kernel that supports all features required by the OS
package the ramdisk and kernel into a bootable image, that you can fastboot boot or flash
Click to expand...
Click to collapse
hm..ok, but I must say, I never compiled a kernel...
I got kind of "advanced" knowledge about android compared to normal "Smartphone users", but I'm definitely no developer!
So unfortunately compiling things is beyond my skills. I think I could do it with a step-by-step-tutorial, but I guess my request is too specific to find a fitting tutorial.
When it comes to Linux, I know some basics about the system and some basic commands. But usually when I'm doing stuff with Linux I use tutorials as well.
I have much more experience with Windows, html, css and some java...
So again, for everything that has to be done with Linux, I need an easy tutorial...
I appreciate your trying to help me, but unfortunately i must say it's way too advanced for me. without a detailed how-to, I will not be able to do this...

gilbert32 said:
and just another pic i found.
Click to expand...
Click to collapse
I'm feeling a bit ambitious and wanted to try something, just want to know if it's been done before.
So I want to use my other phone - Samsung Galaxy Nexus - as a home server (FTP, p2p for start and maybe some light home automation later if everything works well).
So there is a patch for the GNex kernel that allows for phone charging and OTG at the same time. Also, I would need to patch in the loop back into the kernel so I wanted to know if Gento would be able to access my HDD hooked on OTG and how the drivers work in general on Gento and if it is worth the hassle getting it from Android to Gento. Also, I plan to VNC into the phone so display drivers aren't needed to work 100%.
Opinions?

Just install Sailfish OS. It's Linux with just a modified GUI for phones.
Here you can get the latest images, instructions, help (if you need) and info about all the various things https://talk.maemo.org/showthread.php?t=99377
Then take a look at this thread https://talk.maemo.org/showthread.php?t=98882
this is a link to working arch linux chroot https://github.com/Preflex/easy-chroot/releases/tag/0.0.2
here is a pic from my setup
Now someone made a patch for wayland to open in landscape mode. here it is https://openrepos.net/content/elros34/qxcompositor
And here is also ubuntu chroot, which works with that patch https://github.com/elros34/sailfish_ubu_chroot
I moved away from android long ago. Because i want my privacy back from google. Now i do not use anything from google except youtube (without google account)

ILA said:
I'm feeling a bit ambitious and wanted to try something, just want to know if it's been done before.
So I want to use my other phone - Samsung Galaxy Nexus - as a home server (FTP, p2p for start and maybe some light home automation later if everything works well).
So there is a patch for the GNex kernel that allows for phone charging and OTG at the same time. Also, I would need to patch in the loop back into the kernel so I wanted to know if Gento would be able to access my HDD hooked on OTG and how the drivers work in general on Gento and if it is worth the hassle getting it from Android to Gento. Also, I plan to VNC into the phone so display drivers aren't needed to work 100%.
Opinions?
Click to expand...
Click to collapse
If you can get the HDD to work inside android, it will work inside Gentoo. As long as you can mount the HDD inside android it should be possible. And you really don't need android to mount it, just look for the dmesg and see if it's detected, or look for it in /dev/sdxx. If it works, then don't forget to install the specific HDD filesystem support in Gentoo.

The easiest way is Linux deploy in the Google play store, u have the option to install Ubuntu, Debian, Kali, etc. Also with the option of selecting your GUI such as KDE, lxde, etc. U can also chose to build it as an image or use an sdcard partition if you're advanced which is the best option. Most Android devices can easily support running Linux IMO, there hasn't been a device I haven't got it not running on, with the exception of the ones u can't root lol. Give it a try, you'll see what in talking about, as for the vnc use juice SSH on the play store, that's my favorite, also helps to install the hackers keyboard from the play store too. Depending on the internet it should take u less than 30 minutes to get Linux up and running

Sailfish OS (pretty darn good), Plasma-Mobile (not very efficient), and PostmarketOS (least efficient) are good alternatives

there is shortly to be some work done by wicket in my home community of Maemo ...
to get Maemo Leste OS running on the nexus 5 ...
I suggest patience.
it will happen...there are just the n9 and n900 to come first...(which are coming along nicely thus far ..)
I myself am looking forward to having Leste on both my n900's and Nexus 5's...
Leste for the nexus 5 should progress quite rapidly once work begins, considering the nexus 5 is the perfect candidate in compare with other devices.
So you may wish to keep an eyeball on the Maemo Leste OS project

shomu said:
really no one an idea?
A ROM/Kernel Combination for the Nexus 5 with "Loop Device" support would be enough! (see 3. "Complete Linux Installer")
Click to expand...
Click to collapse
KDE Plasma
Sailfish OS if you can figure out how to install manjaro
Ubuntu Touch with dock
Come on just use Google.

[GUIDE]How to setup Dual Boot on legacy PC? (BlissOS and Windows 7/8.1/10)

NOTE: This guide is for MBR disks and legacy bios. If you want install on UEFI, this method can not help you.
1- Preparing the installation
a. Download BlissOS Official Roms ISO image.
b. Extract .ISO files into the *\BlissOS\ folder and create a custom size data.img (4gb for fat32 disk - Recomended 16 GB or 32 GB for NTFS disk)
* = Must be disk part. (you can select C:\ , D:\ or another diskparts)
Tips: You can create data.img file with Android PC Toolbox . Create and copy data.img into the BlissOS folder.
2- Setup grup for dual boot
a. Download EasyBCD and install it.
b. Run EasyBCD.exe > Add new entry > NeoGrub > İnstall
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Click Configure and delete all text. (editing menu.lst)
-Copy and paste that text there..
default 0
timeout 1
title BlissOS
root (hd0,1)
find --set-root ls /BlissOS/kernel
kernel /BlissOS/kernel quiet root=/dev/ram0 androidboot.selinux=permissive SRC=/BlissOS vga=788
initrd /BlissOS/initrd.img
boot
Click to expand...
Click to collapse
Important Note for root settings: You will change these numbers according to where you installed it.
root (hd0,1)
hd0 is your hdd number..
1 is your hdd disk volume number..
-Download Bootice for see disk numbers..
-Run Bootice.exe > Physical disk > Parts Manage - You will see disk parts.. No = hdd disk Volume number
-Rename your boot entry
-Select Count down (you can change timing "10")
-For Windows 10 / windows 8.1 os, check the "use metro bootloader" option.
-Click Save settings.
3-Setup completed. Restart your pc and have fun.

Error 15 file not found

Edit : Changed menu.lst entries. Now,It is set to be the root kernel.

WoltreX said:
Edit : Changed menu.lst entries. Now,It is set to be the root kernel.
Click to expand...
Click to collapse
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.

jhetrosky said:
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
Click to expand...
Click to collapse
the installer provided by bliss is only compatible with UEFI systems. Is not compatible with legacy. And it will tell you in the output window(top right corner of the installer) which conditions are not met. Just have to look:good:

ElfinJNoty said:
the installer provided by bliss is only compatible with UEFI systems. Is not compatible with legacy. And it will tell you in the output window(top right corner of the installer) which conditions are not met. Just have to look:good:
Click to expand...
Click to collapse
Does it creates a swap partition or use ramdisk. If ramdisk, then compatibility will also depend on the RAM.

TeamPrimeOS said:
Does it creates a swap partition or use ramdisk. If ramdisk, then compatibility will also depend on the RAM.
Click to expand...
Click to collapse
There is no swap created by Bliss
There is a ramdisk

ElfinJNoty said:
There is no swap created by Bliss
There is a ramdisk
Click to expand...
Click to collapse
Thanks for the info, what is the minimum ram required then?

TeamPrimeOS said:
Thanks for the info, what is the minimum ram required then?
Click to expand...
Click to collapse
We've not had an issue with a minimum requirement.
This is an OS booting directly. Compare it to an older phone that can run Android: 1gb? 2gb?safe to assume more ram the better...
Most modern systems have at least 2gb which should be sufficient for any Blisss OS build.
As usual, why not test and find out?
#StasyBlissful

ElfinJNoty said:
We've not had an issue with a minimum requirement.
This is an OS booting directly. Compare it to an older phone that can run Android: 1gb? 2gb?safe to assume more ram the better...
Most modern systems have at least 2gb which should be sufficient for any Blisss OS build.
As usual, why not test and find out?
#StasyBlissful
Click to expand...
Click to collapse
Thanks for the info.
---------- Post added at 07:25 AM ---------- Previous post was at 07:23 AM ----------
jhetrosky said:
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
Click to expand...
Click to collapse
Can you list the mentioned incompatibilities.

TeamPrimeOS said:
Thanks for the info.
---------- Post added at 07:25 AM ---------- Previous post was at 07:23 AM ----------
Can you list the mentioned incompatibilities.
Click to expand...
Click to collapse
His issue was not due to incompatibility
The installer has some basic minimum requirements which is explained in the OP and Post 2. It also produces a log which would have explained his exact problem. There is also a YouTube video demonstrating the process successfully from start to finish.
*I didn't want their to be any confusion of there being something incompatible or broken about the UEFI Windows installer.exe*

Why the link for BlissOS/Android PC Toolbox has been deleted? I need it for installing Bliss OS on my not uefi pc
EDIT: Anyway I created an USB Bliss image (BlissOS 7.2 stable) and installed successfully on my hd (on a new partition formatted as ext4), I created then the entry with EasyBCD as suggested, changing the hd number, but when I choose the Bliss entry in the boot menu i got the "Error 13, invalid or unsupported executable format” message. Can anybody help me?

nerub config file for a android 9 Pie Bliss
when you click on easy BCD and install a neogrub and open neogrub install file
you i have seen someone has made a code like this >
defaul 0
timeout 10
root (hd0,X)
title 1. Normal Mode - Start Android OS in normal mode.
find --set-root /Android/kernel
kernel /Android/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=Android/ DATA= CREATE_DATA_IMG=1
initrd /Android/initrd.img
boot
root (hd0,X)
title 2. Recovery Mode - Start Android OS in recovery mode.
find --set-root /Android/kernel
kernel /Android/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=Android/ DATA= CREATE_DATA_IMG=1 SAVE_LO
initrd /Android/initrd.img root=/dev/ram0 androidboot.selinux=permissive vmalloc=192M buildvariant=eng nomodeset RECOVERY=1 RAMDISK=recovery.img SRC
boot
--------------------------------------------------------------------------------------
then instead of X you find your partition and like everything but
my ask for help is a code is incomplete as you see a second part a recovery more
start android in recovery mode is incomplete ? does anyone knows the ending of a code ? thank you ....its for making a better boot android neogrub menu and dual boot with windows 10 .......

@WoltreX hey, i just followed your guide for my laptop but after booting it just keeps showing a yellow animation forever any idea what's wrong ?

works on windows 10 surface tablet? without touch or bluetooth bugs?

Any suggestions on what to use if EasyBCD doesn't work states cannot run on (U)EFI.

Detecting android x86 found at Dev/sda6
Stuck at this screen plz help plz.....

Stuck at (blinkin) _
After I press the BlissOS boot option
The last phrase on the text is Android-x86. . . found at /dev/sda4
then around 20 seconds
black screen appear with blinking _ at the top corner

wtf is up with the shady as hell link for the toolbox? Russian website says I have to install Multy App to download it.
This is some bull**** right here, not touching that with goddam 10 foot pole

Do you know if this is possible in Linux Ubuntu?

[GUIDE] Rooting the Moann inkPalm 5

Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.

qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !

I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...

So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada

Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !

squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language

ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.

This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.

Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button

qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.

reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).

qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.

squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada