Database Develop

[DEV][BRAINSTORM] Fully-working CWM Recovery

While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Now, I have tried to fix these but recoveries are a new domain for me and at a first attempt I couldn't bring some of these to work. Compiling the latest version was easy and an important first step towards official; however, all others I couldn't do it and I don't think we should talk with koush before fixing all this.
Here are my short attempts:
- For USB mount I defined on the BoardConfig the path for UMS lun0 file. The path seems to be correct and there's no other file in /platform/ as I've found out by running a ls -R. I have no idea why it's not working.
- For ADB, I made sure the persist.adb.service is set to 1 and the init.rc is starting it. This being said, I don't know what's missing. Perhaps this is of interest?
- For EXT4 support I thought it was just a matter of adding alternative FS to recovery.fstab. Seems I was wrong though.
So, does anyone want to join in and help?
This is really new territory to me and I have a quite faint idea of what I'm doing.
A few guidelines:
- Read this to get an idea.
- You'll need CM sources (repo init... repo sync...)
- The CWM recovery source is in /bootable/recovery
- Here is my device source and a patch file for some changes on recovery src *
- Run build commands (. build/envsetup.sh, lunch full_p970-eng, make -j4 recoveryimage)
* If you don't change what I did on the recovery source you won't have a key to select.
Also, I have CWM 4.x at the moment on my OB but since it does the same as the already posted 3.x I don't deem necessary to share it; but if anyone wants, I'll upload it.
I'll join the party when I come from the mini-vacations, hope there'll be some progress meanwhile!

Great
i'll try to do some help,maybe little

If anyone wants you can request a pull from my source.
Also, here's a flashing CWM 4.x. I renamed it Nova recovery for the lulz.
http://www.multiupload.com/R7WGNYTL7G

Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
EXT4 Backup and Restore worked for me after editing the fstab file.
For the ADB and USB mount problem i have no Idea what is missing. Like you said, adb daemon should get started througt the initscript.
BTW. seems like the Progressbar isn´t working on the newer Versions of CWM

xantaro said:
EXT4 Backup and Restore worked for me after editing the fstab file.
Click to expand...
Click to collapse
Could you release a new version or tell us how to do it? Thanks

To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto

xantaro said:
Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
Click to expand...
Click to collapse
I thought the flag wasn't suffice. Thanks.
Rusty! said:
To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto
Click to expand...
Click to collapse
Nice tip, I'll try.

knzo said:
While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Click to expand...
Click to collapse
Hey,
I know this is an old thread but still if u have not resolved the problem with ADB and USB follow these instruction:
Before we start:
My mobile is Spice Mi-410 (Qualcomm made), also known as Cherrymobile magnum, Wellcomm, Motorola triumph in different countries. So may be these tweak will not work with your device. (But you can give it a try )
I hope you know how to unpack recovery.img of your device (or boot.img if your recovery ramdisk is stored in boot.img like Xperia Arc) if not then follow this guide to unpack recovery.img and extract recovery ramdisk into a folder.
Tweak
For ADB: Open init.rc file from recovery ramdisk/initram using any editor of your choice
Put this line at the end of "on init" section
Code:
write /sys/module/g_android/parameters/product_id ####
where #### should be replaced by your device's product id.
(if you dont know what it is then connect your mobile to PC and issue "lsusb" command in ubuntu terminal, you should see something like this
Bus 001 Device 027: ID 0489:c000 Foxconn / Hon Hai
Here c000 is my devices product id and Foxconn is my device's manufacturer)
Though /sys/module/g_android is not present in our device but this worked for me.
Please note that the device id is case sensitive, so write what you see on PC
For USB: For this add following line at the end of "on boot" section in init.rc file
Code:
echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
For your device first confirm the location of /sys/class/ ###### / ####/usb_mass_storage/enable
Since this location vary from device to device.
This should enable usb storage mounting from recovery.
Best of luck!!

One option for load rootfs image in native mode is necesary
enviado

[ROM] [4.3.1] CyanogenMod 10.2

Hi, if anyone would like to run a 4.3.1 Google OS on a Archos G9 80S device (and currently only this), download and extract this file:
19_01_2014-13_32_32
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
What's new ?
------------ since 19_01_2014-13_32_32 -------------
Last attempt to satisfy "H" model users. Wrong fstab definition file was used.
ArchosControlCenter: Alternate command for enabling disabling 3G service activation/deactivation.
------------ since 17_01_2014-20_17_32 -------------
KSM (Kernel samepage merging) support. (Enable it in CM performance options).
HDMI enable for 101 models too.
WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).
------------ since 22_12_2013-13_29_20 -------------
Deactivated PCB temperature sensor. It is not part of the devices, and (my) default setting gives the cpufreq
module a wrong view of the situation. Now it should reduce the reboot which is caused by critical temp, by reducing core speed.
------------ since 19_12_2013-23_43_36 -------------
Using CPUFreq from 3.0.31 omapzoom reference kernel
Included app from @mordesku (modified by me) -> 3G should work!
Note that if you only pushed the image as update, please make sure to delete the /data/data/com.android.providers.telephony/databases/telephony.db
(adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db) and reboot the device to rebuild.
I forgot to include the apns-conf.xml so there are no APN's available (as result no data connection can be established).
Removed my Widget to not affect the archos control center app
Some kernel changes.
Enabled zram and init.d
Initial support for H models (testing and patches are welcome).
Newest CM Updates: Changes since last release
------------ since 02_12_2013-22_56_07 -------------
Removed clicks when audio driver is closed
Reduced the volume a little bit to avoid scratches
Removed default dpi setting on build
Newest CM Updates: Changes since last release
------------ since 21_11_2013-21_45_53 -------------
Using new pvr library SGX-BIN: DDK binaries and KM source [email protected]
HWComposer 1.1 interface
No ICS audio blob anymore. Adapted omap upstream audio HAL.
Some internal audio extensions by TI (omap_enhancement)
Kernel audio sources updated to 3.0.31 omap upstream release.[/INDENT]
------------ since 08_11_2013-22_14_52 -------------
CM10.2
Upstream init.rc
TI Openlink WLAN driver R5.SP6.01
Temporary disabled ClockworkMod Recovery
A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
Initial A101s support.
Something I've not tried...
3G USB Stick is working.
Issues:
- GPS not reliable (as usual for every release....) -> After complete new system ("Reset Android & Storage") the GPS is working very good. Subsequent boots later it gets worse at my device(s):
My Workaround: Go into Settings->Apps->All->Google Service Framework and delete data and cache. Then reboot and GPS should e working. Also I get sufficient results with the GPS Toolbox App.
21_11_2013-21_45_53:
Microphone as degraded sound quality compared to the stock rom.
Some sound clicks here and there when system sounds are turned on.
Audio sound is a little bit quiet compared to the stock rom. (Needs to be adjusted by myself).
Can't test HDMI (both audio/video). (It's also not an use case for me). If someone would like to help....
HDMI scaling issues
"H" models doesn't seem to work.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Archive:
17_01_2014-20_17_32
22_12_2013-13_29_20
19_12_2013-23_43_36
02_12_2013-22_56_07
21_11_2013-21_45_53
08_11_2013-22_14_52
07_11_2013-22_53_33
Archos CM10.2 - 26_10_2013-23_26_11

Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?

mordesku said:
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
Click to expand...
Click to collapse
As usual for the custom Android releases for this archos device , they don't replace the original partitions. But it is not possible to run both in parallel. So practically yes, it replace the original system.

Quallenauge said:
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
{
"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"
}

mordesku said:
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
Click to expand...
Click to collapse
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]

Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
(Just for reference, when using the update mechanism the file has to placed here:
Code:
sudo cp archos.ext4.update <Mount_Path>/data/[B]media[/B]/archos.ext4.update
)

Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4

mordesku said:
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
Click to expand...
Click to collapse
Thanks for your reply. I corrected the paths in previous posts.

Is it stable for very day use???
Everithing working lie Cam and HW video?

Using it since yesterday. It's very smooth and fast. No freezes at all.
Sent from my ARCHOS 80G9 using Tapatalk 4

Installation on Mac OS X
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave

stealthdave said:
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
Click to expand...
Click to collapse
Damn to install it yesterday i installed debian on virtualbox on my macbook
Sent from my ARCHOS 80G9 using Tapatalk 4

My tablet is still showing the snazzy CyanogenMod bootloader image after an hour and refuses to load the Android GUI. I tried starting the process over again with the same results. I am able to get to an adb shell and play around there, but Android never finishes loading. I'm running a G9 80S with 1GHz OMAP 4430 and 512MB of RAM. Logcat attached.

Hi,
thank you for building this and all your other ROMs.
Quallenauge said:
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/archos.ext4
Click to expand...
Click to collapse
This is inconsistent.
Is it local/ or data/local/?
I tried to install the ROM following your instructions.
I renamed "archos.ext4.update" to "archos.ext4".
I reset Android and Storage, exported the USB storage, on my machine it was mounted on /media/username/data.
I then used the following commands:
Code:
sudo mkdir /media/username/data/local
sudo cp archos.ext4 /media/username/data/local/
Then I selected "OK" in the tablet and "Flash Kernel and Initramfs" followed by:
Code:
sudo cp zImage /media/username/A80S_REC/
sudo cp initramfs.cpio.lzo /media/username/A80S_REC/
Then I rebooted the tablet.
Now the tablet was flashing the Archos logo for a second and then rebooting, in a loop.
So I guessed the local/ directory was wrong and I might have to use data/local/.
I repeated the steps above, replacing "local/" with "data/local".
This time the tablet didn't reboot in a loop, but I only got the static Archos logo, not the animated Archos logo or the CyanogenMod logo.
I probably missed a step or misread some instruction.
Any idea where I made the mistake?

@esque: Sorry for the confusion... Your first attempt was right:
Code:
sudo mkdir /media/moronoxyd/data/local
sudo cp archos.ext4 /media/moronoxyd/data/local/
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Just to be sure, reboot the tab and mount the drive and perform a
Code:
md5sum <Mount_Path>/local/archos.ext4
and verify that value with the image on your host.
If there are the same values, we have to find another solution for the problem.
@stealthdave: Your logcat file looks very close to the problem above (file image broken).

Quallenauge said:
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Click to expand...
Click to collapse
Yes, that was the issue. umount for everyone!!!

Thanks.
Great job, like buying a new tablet.
The only thing I would add is to sudo sync before unmounting.

Quallenauge said:
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Click to expand...
Click to collapse
D'oh! I knew I made a rookie mistake.
Yes, that did the trick.
Thanks Again!

Hi,
Great job.
Is there a possibility to have the same ROM for the 101 version ?
Regards
Sent from my Galaxy Nexus using xda premium

Hi,
After two days of using this rom I must say it is very fast and smooth. But on idle after 6 hours I got -40% battery drain. Also I can feel heat from it. Got installed only 2 apps and one game. Is there any chance to implement deep sleep in this rom, to minimize batery drain?

Fire TV 2 - Ubuntu (Headless) Install Guide

This guide is intend to help you with "installing" Ubuntu 14.04 (12.04 also works) on the Amazon Fire TV 2 after @rbox recovery has been setup. Only headless mode is possible, similar to Ubuntu Server, but it still makes a nice little ARMv8 development box. Starting X.org or running systemd based Linux distributions will likely never be possible due to features missing from the Amazon kernel. Creative use of the framebuffer is possible if desired, maybe eventually a terminal emulator could be started. As long as you don't mount and modify mmcblk0pX there should be no possible way to mess up Android or brick the device. It's 100% reversible by just removing the SD card. You accept all responsibility for what you do with this work should something go wrong and the device becomes inoperable. With disclaimers and precursor knowledge out of the way let's get started.
To follow this guide you will need:
A micro SD card (2 GB+ recommended)
A Linux system
To login into Ubuntu you will need either:
A 1.8 V TTY USB serial device connected to the UART
A pair of USB serial devices and a null modem cable
I actually used a pair of Xbee's for testing the ttyUSB0 stuff, so hence a pair of FTDI chips would also work.
Preparing the SD Card
To get started you need to first partition the micro SD card:
Type = MBR
Part 1 = 100 MB, Fat32 (vfat)
Part 2 = Remainder, Ext4
Extract the attached zip file to the root of the first partition (extracted filename must be "ramdisk-recovery.cpio.lzma"). This is an alternative initramfs that simply uses busybox to clean up from the partial Android boot and prepare the filesystem for regular Linux. Extract an Ubuntu core root filesystem archive, ubuntu-core-14.04.4-core-arm64.tar.gz, to the root of the second partition as the root user (to preserve ownership/permissions). Make sure you sync or eject the device when done with this work so the data gets flushed to the SD card.
Now we need to make a few changes to the root filesystem to avoid usability issues and allow logins.
Replace /etc/fstab with the following contents to correct some mount options. This "disables" SELinux which fixes dpkg errors and some other login annoyances.
Code:
/dev/mmcblk1p2 / ext4 defaults,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs ro,relatime 0 0
Replace /etc/init/console.conf with the following contents to allow logins from the UART. Once the root password has been set (root is disabled by default) you can remove "-a root" if desired.
Code:
# console - getty
#
# This service maintains a getty on console from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -s -a root console
Create /etc/init/ttyUSB0.conf with the following contents to allow logins from an attached USB serial device. This should help people who don't want to take apart their device to solder wires onto the UART test points. SSH would of course be an alternative but it's not installed by default in Ubuntu core and this guide is about the building blocks not providing pre-made images (yet). Since udev doesn't work due to devtmpfs not being enabled in the kernel you will need to attach the USB serial device before booting for this to work. As before you can remove "-a root" later if desired once the root password is set. Also you should change the baud rate if needed.
Code:
start on (tty-device-added ttyUSB0)
stop on (runlevel [!2345] or tty-device-removed ttyUSB0)
respawn
exec /sbin/getty -L -a root 115200 ttyUSB0 vt102
Preparing the Fire TV
Until the search order for the initramfs file is changed by @rbox you will need to rename the initramfs on the system partition so it will continue to search for one on the SD card or USB stick. You need to connect to the device using adb either over USB or the network to execute the following commands.
Code:
adb$ su
adb# mount -o remount,rw /system
adb# mv /system/recovery/ramdisk-recovery.cpio.lzma /system/recovery/ramdisk-recovery.cpio.lzma.bak
adb# mount -o remount,ro /system
Right now this prevents "su" from working, which should be fixed by @rbox in due time. To get "su" working again you should extract the original recovery initramfs file to a USB stick and boot the device with that USB stick inserted instead of the previously created SD card. Then to restore "su" you can repeat the above steps just swapping the order of the files in the "mv" command.
Booting Ubuntu
After connecting your serial device of choice simply insert the SD card and power on the device. It's that easy! With luck you should get a shell prompt that is already logged in as root. It's a good idea to set the root password before going much further. The device isn't too useful without networking, so you can install more packages. To solve that connect an ethernet cable (since it's simpler) and type "dhclient eth0" to get online. At this point you can install openssh-server using apt-get or do anything else you'd normally do on an Ubuntu VM or headless Ubuntu system. I'm interested in hearing what people plan to do with a more-or-less high-end ARM development system.

Tips and Tricks
NOTE: These changes, unless otherwise noted, are performed while logged into the target Ubuntu system.
Setting the Hostname
You can change the hostname using the following command:
Code:
echo sloane > /etc/hostname
You should also create a simple /etc/hosts file that matches the chosen hostname.
Code:
127.0.0.1 localhost
127.0.1.1 sloane
Enable Ethernet at Boot
Create the file /etc/network/interfaces.d/eth0 with the following contents:
Code:
auto eth0
iface eth0 inet dhcp
Allow Users Network Access
Since we are stuck running an Android kernel you need to create the following group and add users who need network access (such as ping) to this special group.
Code:
groupadd -g 3003 aid_inet
usermod -G aid_inet -a root
usermod -G aid_inet -a <username>
Removing Failed Services
There are a few services that fail to start due to hardware limitations. We should just prevent them from starting in the first place. We have no VT support enabled in the kernel (boo) so we can just remove the ttyX login prompt services. Also the console setup doesn't work since our console is a serial device not a virtual terminal or other "graphical" type terminal emulator.
Code:
rm /etc/init/tty?.conf
echo manual > /etc/init/console-font.override
echo manual > /etc/init/console-setup.override
Fix /dev Hotplug
As stated before udev doesn't work due to missing kernel features. The busybox applet mdev is a simple replacement for most users. After installing the "busybox-static" package run the following command:
Code:
ln -s /bin/busybox /sbin/mdev
Now add the following line to /etc/rc.local before "exit 0".
Code:
echo /sbin/mdev > /proc/sys/kernel/hotplug
Pre-installing SSH
See: http://forum.xda-developers.com/showpost.php?p=65595013&postcount=13 (thanks @segfault1978)

Thanks a lot, that was exactly the thing I was searching for. Since before today the Raspi3 came out, this box is the cheapest ARMv8 development machine available. With your instruction I was able to login via SSH and install all required software for my development environment. No GUI needed for that, I'm doing all remotely via SSH. Again, thank you!

segfault1978 said:
Thanks a lot, that was exactly the thing I was searching for. Since before today the Raspi3 came out, this box is the cheapest ARMv8 development machine available. With your instruction I was able to login via SSH and install all required software for my development environment. No GUI needed for that, I'm doing all remotely via SSH. Again, thank you!
Click to expand...
Click to collapse
Awesome to hear that it worked for you. Just curious if you went the USB serial route or soldered to the UART pins.

There is also the Dragonboard 410c which is a quad core A53 but has a bit more than the raspberry pi. The price is higher though but it has been out probably a year or so. Just FYI. The raspberry pi 3 is a good deal.

zeroepoch said:
Awesome to hear that it worked for you. Just curious if you went the USB serial route or soldered to the UART pins.
Click to expand...
Click to collapse
None of these methods (since I was in my weekend and all cables and adapters reside in my office)
I placed all .deb-files for openssh-server including all requiremens onto the microSD card, and placed a call "dpkg -i /*.deb" with logging options in /etc/rc.local. I also configured network by mounting the sd card, editing /etc/network/interfaces, and last changed /etc/shadow to have a valid root account for login. It took my some try-and-error loops, but finally it worked as expected. Call me crazy, but I succeeded without any hardware.
---------- Post added at 09:09 PM ---------- Previous post was at 09:03 PM ----------
zeroepoch said:
There is also the Dragonboard 410c which is a quad core A53 but has a bit more than the raspberry pi. The price is higher though but it has been out probably a year or so. Just FYI. The raspberry pi 3 is a good deal.
Click to expand...
Click to collapse
Thank you for the hint, I'll have a look for the availability of this board in germany.

I'm facing a memory problem, resulting in a reboot of the device when all RAM is being used. My compile session takes more than 1.x GB of RAM for the quite complex compilation of all required packages. I can reproduce the situation where all memory is consumed and the device instantly reboots when hitting "no memory left" situation. Since "swapon" is not supported by the kernel (really?): is there any way to enable swap functionality, i.e. via a kernel module? How to overcome this situation where more memory is needed?

segfault1978 said:
None of these methods (since I was in my weekend and all cables and adapters reside in my office)
I placed all .deb-files for openssh-server including all requiremens onto the microSD card, and placed a call "dpkg -i /*.deb" with logging options in /etc/rc.local. I also configured network by mounting the sd card, editing /etc/network/interfaces, and last changed /etc/shadow to have a valid root account for login. It took my some try-and-error loops, but finally it worked as expected. Call me crazy, but I succeeded without any hardware.
Click to expand...
Click to collapse
That is pretty crazy, but since you knew the changes required it worked Not everyone I expected to have such experience. I figured someone might even try to do a qemu chroot or debbootstrap to preinstall openssh. Multiple ways to solve the same problem I guess.
segfault1978 said:
I'm facing a memory problem, resulting in a reboot of the device when all RAM is being used. My compile session takes more than 1.x GB of RAM for the quite complex compilation of all required packages. I can reproduce the situation where all memory is consumed and the device instantly reboots when hitting "no memory left" situation. Since "swapon" is not supported by the kernel (really?): is there any way to enable swap functionality, i.e. via a kernel module? How to overcome this situation where more memory is needed?
Click to expand...
Click to collapse
Looking at the default kernel config from the source code drop from Amazon I see:
Code:
# CONFIG_SWAP is not set
Swap can not be compiled as a module. Even if you chose to use a USB stick or something as the swap device It wouldn't work. Given that we can't change the kernel we can't try stuff like zram or zswap either. The only other suggestion I might have is if you're using "-j4" or something while compiling just remove that so it does a single threaded compile. I'm sure you already tried that. Beyond that you could look at using the Linaro AArch64 toolchain and cross compile. Since we're running Ubuntu you shouldn't need to worry about static binaries.

zeroepoch said:
Looking at the default kernel config from the source code drop from Amazon I see:
Code:
# CONFIG_SWAP is not set
Swap can not be compiled as a module. Even if you chose to use a USB stick or something as the swap device It wouldn't work. Given that we can't change the kernel we can't try stuff like zram or zswap either. The only other suggestion I might have is if you're using "-j4" or something while compiling just remove that so it does a single threaded compile. I'm sure you already tried that. Beyond that you could look at using the Linaro AArch64 toolchain and cross compile. Since we're running Ubuntu you shouldn't need to worry about static binaries.
Click to expand...
Click to collapse
Unfortunately, I'm not compiling with parallel processes (I'm compilig Icinga2 for arm64), I'm running
Code:
dpkg-buildpackage -us -uc
within the source package. One single cpp call consumes so much memory (which is crazy in my eyes, never seen such a big compiler process until today), so I'll investigate the option of cross compiling and afterwards creating the deb file outside of the machine.
Code:
cd /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base && /usr/bin/aarch64-linux-gnu-g++ -DI2_BASE_BUILD -Doverride="" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -pthread -std=c++11 -Wno-inconsistent-missing-override -fPIC -I/root/icinga2-2.4.3 -I/root/icinga2-2.4.3/lib -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib -I/root/icinga2-2.4.3/third-party/execvpe -I/root/icinga2-2.4.3/third-party/mmatch -I/root/icinga2-2.4.3/third-party/socketpair -o CMakeFiles/base.dir/base_unity.cpp.o -c /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base/base_unity.cpp
I'm a novice in android devices: What would be required to use a custom kernel? A hacked boot loader, which is not available for the AFTV2?

segfault1978 said:
I'm a novice in android devices: What would be required to use a custom kernel? A hacked boot loader, which is not available for the AFTV2?
Click to expand...
Click to collapse
Yep... we need to be able to use fastboot to boot an unsigned kernel and initramfs (boot.img). I tried at one point to overwrite the boot partition with own image and it failed to boot. Since I had the preloader stuff worked out already I was able to restore the original boot image and get it working again.
On a side note, if you don't mind could you post the list of packages needed to install SSH server from rc.local? Others might find that useful. To get around the unset password issue you could have also saved a public key in /root/.ssh/authorized_keys which would also avoid you needing to change /etc/ssh/sshd_config to allow password logins as root.

segfault1978 said:
within the source package. One single cpp call consumes so much memory (which is crazy in my eyes, never seen such a big compiler process until today), so I'll investigate the option of cross compiling and afterwards creating the deb file outside of the machine.
Code:
cd /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base && /usr/bin/aarch64-linux-gnu-g++ -DI2_BASE_BUILD -Doverride="" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -pthread -std=c++11 -Wno-inconsistent-missing-override -fPIC -I/root/icinga2-2.4.3 -I/root/icinga2-2.4.3/lib -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu -I/root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib -I/root/icinga2-2.4.3/third-party/execvpe -I/root/icinga2-2.4.3/third-party/mmatch -I/root/icinga2-2.4.3/third-party/socketpair -o CMakeFiles/base.dir/base_unity.cpp.o -c /root/icinga2-2.4.3/obj-aarch64-linux-gnu/lib/base/base_unity.cpp
Click to expand...
Click to collapse
I see you are not using -pipe which is good, but a quick search suggested something that might not be simple since this package has it's own build system but changing from -O2 to -O1 might help.

I noticed that Debian has the package available for the same version and already built for arm64.
https://packages.debian.org/sid/icinga2
Maybe you already tried that. You could try going back to jessie which is probably an older version but I think most jessie packages work with Ubuntu 14.04.

zeroepoch said:
Yep... we need to be able to use fastboot to boot an unsigned kernel and initramfs (boot.img). I tried at one point to overwrite the boot partition with own image and it failed to boot. Since I had the preloader stuff worked out already I was able to restore the original boot image and get it working again.
On a side note, if you don't mind could you post the list of packages needed to install SSH server from rc.local? Others might find that useful. To get around the unset password issue you could have also saved a public key in /root/.ssh/authorized_keys which would also avoid you needing to change /etc/ssh/sshd_config to allow password logins as root.
Click to expand...
Click to collapse
This is the list of packages I manually downloaded for ARM64 (unfortunately I used Debian packages which worked first, but leads to a hell situation afterwards when dealing with other dependencies; be sure to use Ubuntu packages in order to avoid problems afterwards):
Code:
busybox_1.22.0
libedit2_3.1
libgssapi-krb5
libk5crypto3
libkeyutils1
libkrb5
libkrb5support0
libwrap0
openssh-client
openssh-server
openssh-sftp-server
This is the piece of calls in /etc/rc.local, right before the exit:
Code:
dpkg --force-all -i /*.deb > /install.log 2>/install.err
echo $? >> /install.log
echo "installation finished" >> /install.log
It took about 1-2 minutes before SSH started to work automatically, you can mount the SD card afterwards in another system in order to check the written logfiles.

Here are some notes for getting wireless working. In addition to the normal OS steps (installing wpasupplicant or wireless-tools and editing /etc/network/interfaces or using wicd) you will need some firmware files from /system (/dev/mmcblk0p13).
Code:
mount -o ro /dev/mmcblk0p13 /mnt
cp -r /mnt/etc/firmware/ /lib/
cp -r /mnt/etc/Wireless /etc/
umount /mnt

segfault1978 said:
None of these methods (since I was in my weekend and all cables and adapters reside in my office)
I placed all .deb-files for openssh-server including all requiremens onto the microSD card, and placed a call "dpkg -i /*.deb" with logging options in /etc/rc.local. I also configured network by mounting the sd card, editing /etc/network/interfaces, and last changed /etc/shadow to have a valid root account for login. It took my some try-and-error loops, but finally it worked as expected. Call me crazy, but I succeeded without any hardware.
Thank you for the the fire tv guide.
Click to expand...
Click to collapse

So, what's the verdict on this? I want to use my firetv 2 as an emby server. Is it worth it trying to get Ubuntu to run?
Sent from my Mi A1 using Tapatalk

mrchrister said:
So, what's the verdict on this? I want to use my firetv 2 as an emby server. Is it worth it trying to get Ubuntu to run?
Click to expand...
Click to collapse
If it has arm64 packages and headless you can give it a try. If you don't like it you can just revert the ramdisk and go back to Android.

Ok sweet, thanks for the reply
Sent from my Mi A1 using Tapatalk

Just curious if anyone's tried running Plex server on this?
I've been looking for a better solution without shelling out $500+ for a dedicated NAS. AFTV is tiny so I could hardwire it and hide it away.
Thanks

I got the same idea. Right now the firetv is still being used as a media streamer but I'm thinking of doing this soon

[ROM][124602 - 2018-08-26] Unnamed Test

For anyone still using a rooted chromecast but having issues with Netflix and paid content from Google, I put together a rom that may help. It's -alpha quality for now, but works for me.
You'll need to flash it with flashcast, and there's no automatic updates or services.
https://github.com/KenMacD/Eureka-ROM/releases/download/v0.0.1-alpha/eureka_image.zip
It's based on upstream release 124602, but with an old kernel and normal modifications to make it not update.

KenMacD said:
For anyone still using a rooted chromecast but having issues with Netflix and paid content from Google, I put together a rom that may help. It's -alpha quality for now, but works for me.
You'll need to flash it with flashcast, and there's no automatic updates or services.
https://github.com/KenMacD/Eureka-ROM/releases/download/v0.0.1-alpha/eureka_image.zip
It's based on upstream release 124602, but with an old kernel and normal modifications to make it not update.
Click to expand...
Click to collapse
This is great. How can I install it into a flashcast rooted device? It's stuck in the chrome logo right now after an update which of course didn't fully get installed.

mobileman88 said:
This is great. How can I install it into a flashcast rooted device? It's stuck in the chrome logo right now after an update which of course didn't fully get installed.
Click to expand...
Click to collapse
Do you still have a flashcast-installed usb stick? If so then just copy eureka_image.zip to that, and then follow the same steps as you would have to install flashcast (boot with the button pressed).
If you have to make another flashcast usb stick then follow the instructions from: https://forum.xda-developers.com/showthread.php?t=2452838
It could probably be installed from the recovery you have now, but I haven't tested that so I don't have instructions yet.

ah cool!
i was chasing something like this as one of the many pet projects i never get to.
ie: getting back to the last viable autoroot version, and making a tweak to disable auto update, and then producing sidechannel updates for flash cast that had dmverity/crypotab stuff off. think i was pretty close, but ran into issues getting the kernel repack to work since couldn't leverage the kernel params to point to the init (IIRC) - all had to be baked in.

speakxj7 said:
ah cool!
i was chasing something like this as one of the many pet projects i never get to.
Click to expand...
Click to collapse
Same here. Autoroot would be nice, but first step first was seeing if things would actually work.
This is a kernel build from eureka_linux, which is based on oss release 1.16. The init.rc was just updated to remove the dmtable stuff and mount it directly.
From here it's probably pretty easy to do a EurekaROM-like release.

Awesome contribution, thank you. I turned on my Chromecast today just to find Netflix not working. I'd love to see this project evolve into something more advanced.

KenMacD said:
Same here. Autoroot would be nice, but first step first was seeing if things would actually work.
This is a kernel build from eureka_linux, which is based on oss release 1.16. The init.rc was just updated to remove the dmtable stuff and mount it directly.
From here it's probably pretty easy to do a EurekaROM-like release.
Click to expand...
Click to collapse
ah, i was trying to go through the repack steps on one of the latter Google OTA updates, didn't think of just going for the Eureka linux builds! i recall they were doing some stuff with the graphics system on some of the 'latest' branches, is that in here or elsewhere?
i definitely wasn't going for it to be auto-updating like autoroot, but i did want to put busybox back in and some of the other basic mods. Was shooting for 'updates' to always be a manual step via flashcast. Shy of running your own OTA system like Eureka did, doing live mods on Goog's OTA's is always going to be brittle, since they could 'break' the mod script at any point.
re: dmtable, exactly yes. once we control the init, can just setup/mount the system plain-ways.

Recovery Instructions
First up. Let me just say thanks to KenMacD!! My chromecast has been borked for a couple of years and now it works again!
KenMacD said:
It could probably be installed from the recovery you have now, but I haven't tested that so I don't have instructions yet.
Click to expand...
Click to collapse
Note: Per the release notes there is no ssh/telnet/web access after the flash
Here are steps to I used get it working via Recovery, output will follow...
Reboot into Recovery. Not sure the exact way to do this (holding the button didn't work), it seems like I just disconnected and reconnected power a couple of times until it showed the "Please wait while your ChomeCast is updated..." screen.
At this point the device should be connected to your wifi (assuming your AP is the same as when you set-up the chromecast back in the day)... so connect to it over SSH
Next up put the image onto a usb stick (fat formatted), plug it into your Y-wire and mount it. (it might be possible to just scp the image to the flashcast, if you don't have Y-wire handy)
Finally run flash-image on the zip file
After flashing and cleanup message appears, reboot - all done.
Output from my run
Code:
[email protected]:~$ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no [email protected] # password: letmein
[[email protected] ~]# mkdir /mnt/usb
[[email protected] ~]# mount /dev/sda1 /mnt/usb
[[email protected] ~]# nohup flash-image /mnt/usb/eureka_image.zip & tail -f nohup.out # Nohup isn't really needed because the process doesn't reboot automatically, but I'm a bit paranoid when it comes to firmware updating...
[1] 704
nohup: appending output to nohup.out
Extracting /mnt/usb/eureka_image.zip (zip) to /tmp/tmp.lfOvoz
Archive: /mnt/usb/eureka_image.zip
inflating: boot.img
inflating: imager.sh
inflating: recovery.img
inflating: system.img
Flashing mod at /tmp/tmp.lfOvoz
KennyROM-124602.001: Imager.sh now running
KennyROM-124602.001: Flashing Kernel...
Flashing ./boot.img to kernel (mtd2)
KennyROM-124602.001: Flashing System...
Flashing ./system.img to rootfs (mtd3)
KennyROM-124602.001: Script Finished!
Removing temporary mod directory /tmp/tmp.lfOvoz <--- Once you see this, flashing is done
^C
[[email protected] ~]# reboot

Is there any way to get a chromecast back to stock?

Android tv
Please help to install new ROM for my smart TV to install apps from google play because my device didnt alow me to install any app from google play....
Please help me

Mstst2008 said:
Please help to install new ROM for my smart TV to install apps from google play because my device didnt alow me to install any app from google play....
Please help me
Click to expand...
Click to collapse
You mean to say your tv is not allowing installation of apps found on google play running on your tv?

My smart tv running aptoide tv so i need install this app
play.google.com/store/apps/details?id=com.ispsgroups
So, please help me to modify the firmware to LG or Samsung firmware ...
---------- Post added at 04:30 PM ---------- Previous post was at 04:27 PM ----------
avvgopal said:
You mean to say your tv is not allowing installation of apps found on google play running on your tv?
Click to expand...
Click to collapse
My smart tv running aptoide tv so i need install this app
play.google.com/store/apps/details?id=com.ispsgroups
So, please help me to modify the firmware to LG or Samsung firmware ...

THANKYOU @KenMacD !!!
managed to upload it via ssh with tftp, ( idea from @ironstorm about svp. but seems theres no sftp-server installed etc, but found there is a tftp ... )
so no usb sticks, or y-cables etc needed will give other people a guide here ...
1. You need a tftp server running, so get tftpd64 running and setup on ya pc (from here http://tftpd32.jounin.net/tftpd32_download.html)
2. my chromecast worked as such, just wasnt able to actual cast anything, so use the proper google app to set it up on WiFi if it isnt already
3. get chromecast into recovery, power up/down/up/down seems to induce it ! not sure like ironstorm what the proper procedure is !
4. then connect to it via SSH, i used PuTTY (ip will be different than when you initially set it up on Wifi with app)
5. then in PuTTY once connected /user/bin/tftp -g -f eureka_image.zip 192.168.x.x
6. then flash-image eureka_image.zip
7. once its finished ! .. reboot (powercycle)
and wahoo ! working chromecast again !!!
just to note, as i was worried .. althou we have no SSH etc when its running as norm.
we DO have SSH while in recovery/flashcast as above, it doesn't remove that, so its all good for next update, which can be done via this procedure too

I was able to resurrect my old Chromecast using the flashcast method, but I wasn't able to configure it. The Chromecast dongle would start up okay, but it needed to be setup. When I launched the Google "Home" app, it couldn't find the Chromecast. I eventually flashed an older eureka_image.zip (44433) and then the "Home" app was able to find the Chromecast, and I was able to set it up. Then I flashed this latest version (124602) and it continued to work.

Does this build still enable telnetd and/or sshd?
Edit: Looks like the answer is no, but you can still ssh into recovery.

I checked this kernel with the latest OTA as well and it should still work theoretically by combining this kernel with new system (ota.159268) and libc from ota initrd. Maybe minor midifications on init.rc possibly to adjust some arguments on service calls.
But there is always that slight risk of unbootable system. The worse scenario possible is if the system image is not properly modified, allowing overwrite of recovery partition and loosing flashcast. But still doable by someone who still know what he is doing and still have that interest and time on this device.
I also posted another method recently of achieving the same, essentially by allowing whatever rootable kernel/system you have to boot completely and then mounting new modified system and initrd.libs over original mounts, and then restarting some services. But again the mod we do to system is important, so that unwillingly we don't let googles services to overwrite flashcast (cleanup those flash recovery executables update_engine and recovery.img on OTA system).
But beyond that since nothing is really flashed, there is less chance of a brick, but still allowing the old chromecast to use latest cast_engine and all related executables and binaries (just as an unrooted chromast on latest OTA).
KenMacD said:
Same here. Autoroot would be nice, but first step first was seeing if things would actually work.
This is a kernel build from eureka_linux, which is based on oss release 1.16. The init.rc was just updated to remove the dmtable stuff and mount it directly.
From here it's probably pretty easy to do a EurekaROM-like release.
Click to expand...
Click to collapse

morchu said:
I checked this kernel with the latest OTA as well and it should still work theoretically by combining this kernel with new system (ota.159268) and libc from ota initrd. Maybe minor midifications on init.rc possibly to adjust some arguments on service calls.
But there is always that slight risk of unbootable system. The worse scenario possible is if the system image is not properly modified, allowing overwrite of recovery partition and loosing flashcast. But still doable by someone who still know what he is doing and still have that interest and time on this device.
Click to expand...
Click to collapse
I have attempted to do this, but I don't really know what I'm doing. Every image I've generated in this attempt has been unbootable, necessitating recovery and reflash. Can you give more details of what modifications are needed? This will be the last upstream for this hardware, so it would permanently solve the OTA attempts and take the hassle out of rebooting. Thanks.

Thanks @KenMacD @ironstorm @miniminus
I finaly resurrect my CC. I've made it using ssh and scp.
Somehow it happend that I had issue with free space on CC (even that I cleared /tmp), so I tried to flash it from zip but saw next
Code:
[[email protected] fw]# unzip -d /tmp/fw/ /tmp/eureka_image.zip
Archive: /tmp/eureka_image.zip
inflating: boot.img
inflating: imager.sh
inflating: recovery.img
inflating: system.img
unzip: write: No space left on device
unzip: inflate error
so I had to unzip fw localy and scp files to cc. (because otherwize it show error and unziped not fully)
(I created folder /tmp/fw to keep fw files)
Code:
scp ./imager.sh [email protected]:/tmp/fw
scp ./boot.img [email protected]:/tmp/fw
scp ./recovery.img [email protected]:/tmp/fw
scp ./system.img [email protected]:/tmp/fw
scp ./flash-image.sh [email protected]:/tmp/fw
last one file is modified https://raw.githubusercontent.com/team-eureka/flashcast-flasher/newmode-alpha/src/flash-image
I've change few lines near 293 , it was made not to coping this files again to tmp folder
Code:
elif test -d "$_MOD_FILE" ; then
_EXTRACTED_PATH="/tmp/fw"
echo "Copying ${_MOD_FILE} to ${_EXTRACTED_PATH}"
# cp -r "$_MOD_FILE" "$_EXTRACTED_PATH"
chmod 755 "$_EXTRACTED_PATH"
else
echo "${_MOD_FILE} is not of a recognized mod format"
exit 2
fi
So after that I saw
Code:
[[email protected] fw]# ./flash-image.sh /tmp/fw/
Copying /tmp/fw to /tmp/fw
Flashing mod at /tmp/fw
KennyROM-124602.001: Imager.sh now running
KennyROM-124602.001: Flashing Kernel...
Flashing ./boot.img to kernel (mtd2)
KennyROM-124602.001: Flashing System...
Flashing ./system.img to rootfs (mtd3)
KennyROM-124602.001: Script Finished!
Removing temporary mod directory /tmp/fw

annoyingly i went to use my chromecast again after a while...
but i have since changed wifi settings (as stopped old WPA, and only on WPA2, so update pass etc)
so i needed to setup again... but like @SFDave google home just doesnt see it anymore...
tried finding 44433.001.zip like him, but its not available anywhere now so i failed on first hurdle
anyone still have a copy ?....
have now found it... the http://pdl.team-eureka.com/ota/final/44433.001.zip link, found in the main 44433 pinned thread does work !!!!
but as its not a "secure" link you have to copy link and past it in as separate address! (as in just clicking link within that post/thread doesn't actually work etc)
flashed 44433.001 by renaming to eureka_image.zip and placed in root of fat32 formatted usb stick, with he y powered USB cable.. when in the recovery flashcast screen (plugin, unplug, plugin quickly) (takes a few minutes be patient!
once it reboots you will know it worked ! also you get a log file on the USB stick too .
then i flashed the one at top of thread.....

Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)

Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! THIS ROM IS ONLY FOR THE EXYNOS VERSION !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
First I would like to thank NoKit, monich, elros34 and all the Sailfish OS porter guys who helped me to make this port.
Thank you very much guys!
News 05/03/2023: OTA to SFOS 4.5.0.18
26/10/2022: OTA to SFOS 4.4.0.72
14/07/2022: OTA to SFOS 4.4.0.68
08/06/2022: OTA to SFOS 4.4.0.64
30/05/2022: OTA to SFOS 4.3 & 4.4
22/02/2022: OTA to SFOS 4.2
16/10/2021: Waydroid on Galaxy Note4 (SFOS 4.1)
03/09/2021: OTA to SFOS 4.1
23/03/2021: OTA to SFOS 4.0
Requirements:
Before you start to download anything, please read all this through carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
Installation instructions:
1. Download all files, LOS14.1 zip, Sailfish OS zip and twrp2.8.7.img to the external SD card on the phone
2. Reboot into TWRP (Hold buttons: Power on + Home + Volume up)
At this point you should install TWRP 2.8.7 as the installation work the best with this recovery.​
Once you flashed TWRP 2.8.7, please reboot into recovery and continue the process.​
​3. Do a factory reset
4. Still in recovery, flash the LOS14.1 image
5. Still in recovery, flash Sailfish Os image
8. Reboot
9. Enjoy the latest (3.3.0.16) Sailfish OS on your Note 4 (treltexx).
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on LOS 14.1.
Downloads:
twrp2.8.7.img for Note 4 (treltexx)
LOS14.1 for Note 4 (treltexx)
Sailfish OS 4.5.0.18 for Note 4 (treltexx) - 05/03/2023
Sailfish OS 4.4.0.72 for Note 4 (treltexx) - 26/10/2022
Sailfish OS 4.4.0.68 for Note 4 (treltexx) - 13/07/2022
Sailfish OS 4.1.0.24 for Note 4 (treltexx) - 09/09/2021
Sailfish OS 3.3.0.16 for Note 4 (treltexx) - 09/10/2020
Boot logo updater for Note4 (treltexx)
kernel for lxc support (this kernel is only for sfos 3.3, the newer OTA updates all have this support!)
fix for 'Private number' calls
Problems/Solutions:
Problem: LXC container doesn't start on any of these two builds.
Solution: In TWRP install the kernel for lxc support. (This will be included into a later build.)
Problem: Incoming calls are not displaying the number only the 'Private call' text.
Solution: Install the fix for 'Private number' calls rpm. (This will be included into a later build.)
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
You can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Battery life
In my experience this build gives a very good battery life (I've tested with a new battery and it drops beteen 5% - 10% overnight with wifi on)
Changelog:
10.10.2020
=========
Custom (Sailfish OS) boot logo
09.10.2020
=========
Sound fix is included, it works out of the box
GPS fixed!
S-Pen works as a mouse! To make the cursor visible (thanks for elros34!) you need to install:
Patchmanager 3 from openrepos
mousetracker
amend '/var/lib/environment/compositor/droid-hal-device.conf' file, add the -plugin evdevmouse:abs:/dev/input/event3 to the end of LIPSTICK_OPTIONS. (That line should look like this:
Code:
LIPSTICK_OPTIONS=-plugin evdevtouch -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap -plugin evdevmouse:abs:/dev/input/event3
as final step apply the moustracker patch in Settings/Patchmanager, then restart the services (pulley menu in Patchmanager) or reboot, then pull out the S-Pen and use it as a stylus/mouse.
(Note: As patchmanager doesn't yet work when the default user is defaultuser, the instruction above works only on sfos 3.3.0.16 or the OTA updated 4.0.1.48. On fresh sfos 4.0.1.48 install you need to install mousetracker and manually apply the patch from it.)
28.09.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
GPS (The permanent solution will be included in a future build. Now, the workaround is (do it only once): as root delete the folder /data/system/gps and then reboot. GPS should start working)
Notification LEDs (white, green, blue, red)
Wifi
MTP
Bluetooth
Calls incoming/outgoing
Messages incoming/outgoing
Mobile data
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is the name of the sd card when it was formatted like 4B93-785B)
Home button and the Back soft button
Vibra
Pixel ratio and icons set to 2.00
Audio is routed to headphone if that presents
Camera front/rear
Video recording (only on the rear camera)
Jolla store (please skip the account creating/adding in the initial setup)
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
Sound - Please download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download, then give it executable permission and run as root or do the following:
Download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download
goto Settings/Developer tools, enter a Password and save it
start the Fingerterm app and within, issue the following commands
devel-su (press enter, then enter the password you set)
chmod +x /home/nemo/Download/soundfix-treltexx.sh
/home/nemo/Download/./soundfix-treltexx.sh
Do not work:
USB mode selection from Settings (workaround: as root run 'systemctl restart usb-moded' command)
Video recording on the front camera
Video playback in Gallery app (You can use Kodi for playing videos)
Internal SD card is not mounted to /android
S-Pen WIP
Extra 1: Change boot logo, Download warning image, Charring image and Download image for Sailfish OS like.
Simply download the Note4-Boot-Logo-Updater_by_edp17.zip from the download section and flash it with TWRP.
Important!: Once the zip is flashed, boot into recovery again, then you can boot into Sailfish OS.
To revert these images back to original:
Download the original param.bin and flash it with heimdal:
Code:
heimdall flash --PARAM param.bin
Inspired by this post
Extra 2: Desktop Linux distro install/run on the Note 4!
1. First flash the kernel from the Downloads section (in a later build this kernel will be included)
2. Install all the following packages:
lxc
lxc-templates
nemo-qml-plugin-dbus-qt5
sailfish-polkit-agent
python3-base
python3-gobject
dbus-python3
lxc-templates-desktop
qxdisplay
harbour-containers
mouse cursor support for SFOS and LXC
3. Once the packages are installed, fire up the LXC and install a distro into it (e.g. Debian SID)
On the Note 4 the harbour-containers GUI doesn't work properly. Fortunately the desktop distro installation can be done from a command line. Here are the steps:
sudo lxc-create -t sfos-download -n mycontainer
follow the instruction and set the distribution (e.g. debian) then the version (e.g. sid) then the architecture (armhf)
example command: sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid
sudo lxc-start -n mycontainer
sudo lxc-attach -n mycontainer
then within the container:
/mnt/guest/setup_desktop.sh
/mnt/guest/setups/debian.sh
4. Once the Desktop distro is installed you can start:
I recommend to use one of these scripts as they save a little time. (Note: You need sudo installed and configured for these scripts!)
Start LXC and desktop in landscape mode with mouse support: debian-mouse-landscape.sh
Start LXC and desktop in portrait mode with mouse support: debian-mouse-portrait.sh
Start LXC and desktop without mouse support: debian.sh
5. Enjoy.
6. More info about the Full linux distros on Sailfish OS.
Pictures:
{
"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"
}
Custom boot logo and other pictures:

Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant

tigerpro357 said:
Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant
Click to expand...
Click to collapse
Yes, all sources are available on github: here
Please let me know when the UT is available for this device! I'd like to try it.

calls not work

Oh, it's you again dude That is AWESOME

lee.wp14 said:
Oh, it's you again dude That is AWESOME
Click to expand...
Click to collapse
I am still chasing my n7000. Once I got that I will complete that port too. Will let you know.

usaman65 said:
calls not work
Click to expand...
Click to collapse
What variant of Note 4 is that? This port is for the European Exynos version (SM-N910C).

edp17 said:
What variant of Note 4 is that? This port is for the European Exynos version (SM-N910C).
Click to expand...
Click to collapse
test on n910c .sound also not work

usaman65 said:
test on n910c .sound also not work
Click to expand...
Click to collapse
Yeah, I installed the build again and tested these. I can confirm these do not work. Hmm, all those worked fine on all previous builds, so I am not sure why the stopped working. It seems permission issue to me. I double check and will come back with a solution. Thanks for reporting!

edp17 said:
Yeah, I installed the build again and tested these. I can confirm these do not work. Hmm, all those worked fine on all previous builds, so I am not sure why the stopped working. It seems permission issue to me. I double check and will come back with a solution. Thanks for reporting!
Click to expand...
Click to collapse
any patch possible for android apps ?

usaman65 said:
test on n910c .sound also not work
Click to expand...
Click to collapse
I have figured out a solution to the sound issue. It was me forgot to include this into this build. I will add it into a later one. Until then, please follow the instruction from the main post. (I added a script into the Download section and a comment how to apply it.)
For me, this fix solved the issues with calls and torch too.

edp17 said:
I have figured out a solution to the sound issue. It was me forgot to include this into this build. I will add it into a later one. Until then, please follow the instruction from the main post. (I added a script into the Download section and a comment how to apply it.)
For me, this fix solved the issues with calls and torch too.
Click to expand...
Click to collapse
thanks its fix now .tuch missing some time while tipping

who to install lxc for desktop linux .nothing find on google

usaman65 said:
who to install lxc for desktop linux .nothing find on google
Click to expand...
Click to collapse
How do you mean? There is instruction in the first post and there is a link to the main post of lxc (option 5).

edp17 said:
How do you mean? There is insttuction in the first post and there is a link to the main post of lxc (option 5).
Click to expand...
Click to collapse
there is a link but cannot find all required files .and how to fire lxc ...? cannot find harbour-containers .there is a link but cannot instaled it

usaman65 said:
any patch possible for android apps ?
Click to expand...
Click to collapse
No, none of the community ports have support for android apps. However you can install a desktop linux and can run desktop apps. (Although very few is touch control friendly.) Instruction for how to install a desktop distro on this device is available in the main post.

usaman65 said:
there is a link but cannot find all required files .and how to fire lxc ...? cannot find harbour-containers .there is a link but cannot instaled it
Click to expand...
Click to collapse
The link to the harbour-container is in the 'Extra: Desktop Linux distro install/run on the Note 4!' section (main post).
Although, here is how to install it, follow these steps:
download the 'harbour-containers-0.4-1.armv7hl.rpm' from this link.
open a terminal (Fingerterm)
type: devel-su (then press enter, then type your password and press enter again)
go to the library where you downloaded the rpm file
type: pkcon install-local harbour-containers-0.4-1.armv7hl.rpm (then press enter)
!Note: Before installing the harbour-container, you need to install ALL the other packages that are listed in the 'Extra: Desktop Linux distro install/run on the Note 4!' section (main post).
There is a full topic about all of this (also provided in the main post) here.

Does it work on note 4 n910v verizon?

Hola117 said:
Does it work on note 4 n910v verizon?
Click to expand...
Click to collapse
I think the N910V is not an Exynos but a Snapdragon device. This means, no, this port won't work on that. Sorry.

edp17 said:
I think the N910V is not an Exynos but a Snapdragon device. This means, no, this port won't work on that. Sorry.
Click to expand...
Click to collapse
you are correct, the 910V is a snapdragon device, its actually what I used to do my Ubuntu Touch port, BTW, I am still going to do a exynos note 4 UT port, just been busy