Database Users

[09-06]SailfishOS & Multirom. How to set up guide

Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.

I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.

anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did

Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.

anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android

Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish

anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...

v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.

mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).

Works nicely on my n4. Looking for getting gapps to run....

mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic

iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.

iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.

mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.

iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).

Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you

Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...

Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?

Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...

Works perfectly on my oneplus one

{Q} Custom ROMS (AOSP/CM) for Galaxy A8 (SM-A800F)? Any possibility in Future??

Hello all
I was wondering if there will be AOSP/CM ROM for this device, not a single ROM is available and no dev is interested to work on such a great device.
Such a totally crap device, still stucked on 5.1.1 since launch, no dev is interested in the development either, where android n announced already, we are still waiting for Android M update, i wasted my money on such a **** device, will never buy a sammy mid range in future, m totally fed up with this

I think because there are few developer with that phone and they can't test their work. You can port ROMs such as CM to you phone by your self. There are tons of guides and forums. All u need is a linux OS (such as ubuntu, debian and others) and sources.

DeadSquirrel01 said:
I think because there are few developer with that phone and they can't test their work. You can port ROMs such as CM to you phone by your self. There are tons of guides and forums. All u need is a linux OS (such as ubuntu, debian and others) and sources.
Click to expand...
Click to collapse
Ok i want to port Resurrection Remix on my A8, i need a simplest guide for android build environment startup, using windows 10, with no knowledge about programming languages such as C++ etc etc which is required to be used on Linux OS, can you plz help me, i will install ubuntu OS on my laptop, but i am worried can i install two different os in one machine, i.e. Windows 10 & Ubuntu

shubham540 said:
Ok i want to port Resurrection Remix on my A8, i need a simplest guide for android build environment startup, using windows 10, with no knowledge about programming languages such as C++ etc etc which is required to be used on Linux OS, can you plz help me, i will install ubuntu OS on my laptop, but i am worried can i install two different os in one machine, i.e. Windows 10 & Ubuntu
Click to expand...
Click to collapse
yep, I'm on kali and I use windows 10 to play games, so the only thing is: take care when partitioning. After you installed ubuntu there is a bootloader called "GRUB" and there you can choose if you want to boot windows or linux

Android 7.0

Since google released the source,did anyone try building aosp 7.0 yet?Even xperia m managed to boot it XD
Since we have snapdragon 410 and with our kernel,Im pretty sure its compatible,1gb ram does the job too.

MaRtYy01 said:
Since google released the source,did anyone try building aosp 7.0 yet?Even xperia m managed to boot it XD
Since we have snapdragon 410 and with our kernel,Im pretty sure its compatible,1gb ram does the job too.
Click to expand...
Click to collapse
Moreover, there is another device Wileyfox Swift with almost the same specs as our phone has (the only difference is that in Wileyfox users have 2 gb of RAM). Still, enthusiasts managed to compile almost fully working ROM on AOSP 7.0 for that device. I think, that what is needed for our device is kernel. Once we have a kernel that supports Android 7, I guess it'll be easy to port that ROM for our device. I wish I were a dev to do all of that by myself

georgearn said:
Moreover, there is another device Wileyfox Swift with almost the same specs as our phone has (the only difference is that in Wileyfox users have 2 gb of RAM). Still, enthusiasts managed to compile almost fully working ROM on AOSP 7.0 for that device. I think, that what is needed for our device is kernel. Once we have a kernel that supports Android 7, I guess it'll be easy to port that ROM for our device. I wish I were a dev to do all of that by myself
Click to expand...
Click to collapse
The dragonite kernel of har**** jain is android n ready which he included in his rom

Junaid Shafi said:
The dragonite kernel of har**** jain is android n ready which he included in his rom
Click to expand...
Click to collapse
That ROM is ARM64 and kernel is compiled accordingly for x64. And the AOSP 7.0 ROM for Wileyfox is ARM.

georgearn said:
That ROM is ARM64 and kernel is compiled accordingly for x64. And the AOSP 7.0 ROM for Wileyfox is ARM.
Click to expand...
Click to collapse
Maybe har**** has 32bit android n kernel contact him on telegram
Dev_harsh1998

[Discussion] SM T819 - Lineage OS - A possible starting point!

I have been waiting quite some time for a custom rom for SM T819 but I haven't see much progress in this. I looked for a device with similar specs for our device and came across this device which already has a Lineage OS build available. Its practically the same device but with a different screen size.
LeEco Le 2 Specs: http://www.gsmarena.com/leeco_le_2-8053.php
LeEco Le 2 Lineage OS Github Repo: https://github.com/LineageOS/android_device_leeco_s2
It will be a good starting point as I think for getting a custom rom for this device with a great potential. I have read that having spec devices is a great start to porting a ROM from one device to another without specifically building it from the source. However it includes a few build prop tweaks and changing few lines on kernel which I have no technical expertise.
Looking forward for your thoughts.

It's true, personally I don't have this tab but I had experience with a Tab I used which was similar in specs with S4 Mini ..
You'll get bugs though and you can base device tree from the Leeco Phone to build ROMs

Anything new here?
Seems like @tuxing built a modified T813 LOS build for himself, but of course no LTE in there. https://forum.xda-developers.com/showpost.php?p=73992901&postcount=552

i really hate the lack of support for LTE Tablets :/

Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?

kinglolloman said:
Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?
Click to expand...
Click to collapse
Not that easy, but I had a nice chat session with @LuK1337 and he explained me how to get things built and boot on T819: https://forum.xda-developers.com/tab-s2/general/guide-build-lineageos-15-1-t819-t3721477
It's not that difficult as I thought. @LuK1337 told me it's simple and even I managed to get it working.

[SM-T510] (2019) Search for Nethunter/ Kali Linux rom and guide

Hello guys,
this is my first post. Since today I´m a proud owner of a Galaxy Tab A (SM-T510 with 64 GB ROM and 3GB RAM, newest stock android build T510XXU2ASK5, never connected to internet yet).
I want to install Nethunter OS or Kali Linux (if possible) on this and read many hours in the internet but there are some questions:
Has anyone flashed the SM-T510 with Nethunter OS? (if this isn´t possible, a way to just use the kali apps is fine too but not my first choice)
Is it possible to flash directly to the ROM instead to a SD Card?
Which type of processor has the tablet? I think it is amd64 not arm, right? Maybe I could try to flash a Nethunter Image for Galaxy Tab S4 but I´m sure this doesn´t work cause the processor is not exact the same... (https://www.offensive-security.com/kali-linux-nethunter-download/)
I found this thread about Kali Linux installation but I would find a direct installation better https://forum.xda-developers.com/hardware-hacking/hardware/devices-kali-linux-installation-t3414523 (If I can´t install directly, can I use this guide for my device after I rooted it?)
A few years ago I flashed Android on a SD-Card for my HTC Kaiser 130 (still working fine), so I have a little experience about flashing and so on but flashing this tablet looks a little bit more difficult to me, so I want as much information as possible cause I have only one try (in the baddest scenario)
I hope you can help me.
Thanks for reading! (I´m from germany, so I´m sorry for my bad english)
Edit: I have found UserLAnd and will try it now, if someone has a better suggestion, feel free to post it

Where'd you get the idea that this was an AMD64 tablet? All Samsung Galaxy Tab As are ARM, The T510 has an Exynos 7904 or 7885 SoC. And I've never heard of anyone porting a Linux distro to one.

lewmur said:
Where'd you get the idea that this was an AMD64 tablet? All Samsung Galaxy Tab As are ARM, The T510 has an Exynos 7904 or 7885 SoC. And I've never heard of anyone porting a Linux distro to one.
Click to expand...
Click to collapse
Thanks for your answer lewmur, I just read it is a 64bit proc and thought it is amd64, my last tablet is some years old and I just thinked the technical development is quicker... ^^
Hmm... sounds like bad news, I just googled yesterday and it is a Exynos 7904, yes you´re right. That means it is closed source, damn.
In this thread (https://forum.xda-developers.com/galaxy-m30/help/hope-custom-rom-development-m30-exynos-t3910256) I found someone who maybe has kernel source, I will write him. Maybe where is a way to build a Nethunter image by myself. I have tested UserLAnd on the tab and I don´t really like it, it´s not smooth.
On monday I will go to the shop where I buyed the tab and try to give it back, maybe they have goodwill, then I will buy online a nexus tablet, looks much more easier.
Thank you anyway, maybe someone has some more good tipps for me.

I have downloaded this
nethunter-2021.3-generic-armhf-kalifs-full.zip
and flashed it with TWRP on my Rooted Device and it works on SM-T510 Android 11 StockROM