Related
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
WHAT IS THIS APP ALL ABOUT?
THIS IS A APP THAT CONTAINS
NEW PORTED ROMS
ROM GUIDES
NEW UPCOMING ROMS
MODS
UPDATES
AND A LOT MORE TO BE ADDED .........
WHY THIS APP ?
A LOT OF ROM FOR ALL MTK DEVICES
SORTED ROMS (DIFFERENT CHIPSETS ) FOR EASY PORTING
PORTING GUIDES
MANY TUTORIALS
LEAST NUMBER OF ADS
BETTER UI
A PLACE WHERE U LL GET EVERY ROM
U CAN ALSO ADD YOUR ROMS IN THE APP (PROPER CREDITS WILL BE GIVEN TO ALL)
FEATURES
MATERIAL UI
MATERIAL THEMES
(LIGHT RED , METRO BLUE , LIGHT,DARK)
REVIEWS OF DIFFERENT ROMS (WITH VIDEOS)
AND MUCH MORE .........
A NOTE
EVERY ROM YOU PORT GIVE PROPER CREDITS
SHARE THIS APP
AND MAKE THE COMMUNITY OF MTK BETTER
XDA:DevDB Information
MTK ROMS OFFICIAL APP , ROM for all devices (see above for details)
Contributors
manhar2108
Source Code:
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Beta
Stable Release Date: 2016-03-31
Beta Release Date: 2016-03-07
Created 2016-03-07
Last Updated 2016-03-07
DOWNLOAD LINK
HERE
or
the download tab
for lazy guys
here
last one
forgot this
Thanks
So this is for ANY device? I have the d2cri and there are no new roms being developed for it. I really want to be rid of KitKat and to get Lollipop but nothing I have tried has worked up to this point.
Sn0wflak352485 said:
So this is for ANY device? I have the d2cri and there are no new roms being developed for it. I really want to be rid of KitKat and to get Lollipop but nothing I have tried has worked up to this point.
Click to expand...
Click to collapse
Yes its for any device
We have porting guides
Custom ROMs and .any more things
U can choose them
We will also help u if u find any problems
Stay connected
Just downloaded and installed this on to my MediaTek China phone. Unfortunately this app has not been active for the last 3-4 years. Shame as it would make a nice little community for all of the MTK users out there
Chris
MTK ROMs? Wowzers!
Unfortunately this app has not been active for the last 3-4 years. Shame as it would make a nice little community for all of the MTK users out there Chris
Click to expand...
Click to collapse
I probably wouldn't have found this if you didn't make a comment. Would you please point out what link you used to get a ROM, all the ones I see here are broken or non-functiomal. I've been looking for some firmware to put into my RCA Tablets that haven't made it past Android 5 Lollipop. I wish I could find something more up to date like Android 8.1
I didn't get a ROM. I merely downloaded this app to my phone, installed it and noticed that all of the posts were from 3-4 years ago.
are we going to see any updates soon?
Here's a usable link
tarongee said:
are we going to see any updates soon?
Click to expand...
Click to collapse
I doubt it. I've been waiting for years searching for an update to my RCA tablets. I can Root them but then I have nothing to flash into it. So I, like everyone else is stalled.
Here's a workable link to the MTK app
https://forum.xda-developers.com/devdb/project/dl/?id=17231
Any possibilities of ANDROID O for htc one m8
http://www.lineageosrom.com/2017/03/los-15-list-of-devices-getting-lineage.html
"This is all About the List i know though many more smartphones can get android 8.0 Oreo Because this list is not yet officially published by the google and This is not the official list its only based on the hardware and software of the devices that can support This type of android."
nolt said:
http://www.lineageosrom.com/2017/03/los-15-list-of-devices-getting-lineage.html
"This is all About the List i know though many more smartphones can get android 8.0 Oreo Because this list is not yet officially published by the google and This is not the official list its only based on the hardware and software of the devices that can support This type of android."
Click to expand...
Click to collapse
Lineages OS support the devices which have no official support from Google seems Lineages OS just have this project, wait and see for ONE M8
Someone need to build it when the source code drops. Until then you won't get any "Oreo"!
Thanks a lot @nolt, @Harrison Le & @mihran_thalhath
Has anyone tried this?
http://www.cyanogenmods.org/forums/topic/lineageos-15-htc-one-m8-android-oreo-8-0-rom/
anyone ?
I've tried but it didn't pass the bootanimation screen. I don't know what's the problem. I waited more than 30min but unfortunately no success.
grh35 said:
I've tried but it didn't pass the bootanimation screen. I don't know what's the problem. I waited more than 30min but unfortunately no success.
Click to expand...
Click to collapse
Same
David_UK said:
Has anyone tried this?
http://www.cyanogenmods.org/forums/topic/lineageos-15-htc-one-m8-android-oreo-8-0-rom/
Click to expand...
Click to collapse
I tried but stuck in bootloop and waited for a hour.
Don't you guys see a weird thing when the page says
LineageOS 15 GApps download link for HTC One M8 LineageOS 15 Oreo 8.0 ROM (Download the stock ARM64 GApps)
Since when M8 become 64 bit arch ?
I'll never trust a site with wrong info and put my device on risk of bricking.
ckpv5 said:
Don't you guys see a weird thing when the page says
LineageOS 15 GApps download link for HTC One M8 LineageOS 15 Oreo 8.0 ROM (Download the stock ARM64 GApps)
Since when M8 become 64 bit arch ?
I'll never trust a site with wrong info and put my device on risk of bricking.
Click to expand...
Click to collapse
I just flashed the rom and rebooted still it stucks at bootloop.
Seriously Guys??? Bruno is the only one right now who is trying to build O for m8. That build on that site was compiled by me, using Bruno's changes. It was not for public testing and someone shared it regardless. Just wait for Bruno to bringup O. Show some patience guys!
A reminder to all users who are willing to try Oreo at this moment:
Since the Oreo source just released, it would be possible custom ROM builds are highly experimental at this early stage. Please do take precautions on these builds and always have a full backup if you would like to try them out.
Stay safe and enjoy flashing!
jerryhou85 said:
A reminder to all users who are willing to try Oreo at this moment:
Since the Oreo source just released, it would be possible custom ROM builds are highly experimental at this early stage. Please do take precautions on these builds and always have a full backup if you would like to try them out.
Stay safe and enjoy flashing!
Click to expand...
Click to collapse
Yeah that's good thing b4 doing anything just take a full backup and play with any rom, in btw link for Oreo
mihran_thalhath said:
Seriously Guys??? Bruno is the only one right now who is trying to build O for m8. That build on that site was compiled by me, using Bruno's changes. It was not for public testing and someone shared it regardless. Just wait for Bruno to bringup O. Show some patience guys!
Click to expand...
Click to collapse
Thanks for your info. Will wait for official link from your side. I'm here to help you.
Patience is a virtue.
I remember when first versions of N roms dropped - they were mostly working, but not really usable
I'm just going to wait until stable los builds drop, then hopefully we'll get RR and others based on it.
Saleen28 said:
Patience is a virtue.
I remember when first versions of N roms dropped - they were mostly working, but not really usable
I'm just going to wait until stable los builds drop, then hopefully we'll get RR and others based on it.
Click to expand...
Click to collapse
Yeah patience needed for Android O for this old-age pretty smartphone.
I will say yes. https://forum.xda-developers.com/showpost.php?p=73545811&postcount=330
nunclud said:
I will say yes. https://forum.xda-developers.com/showpost.php?p=73545811&postcount=330
Click to expand...
Click to collapse
Yeah I too noticed that, waiting for official release.
FYI
https://forum.xda-developers.com/pr.../paranoid-android-pie-beta-qssi-8998-t3886750
Seems interesting. Not ready yet for prime time.
No need to comment here. Use above dedicated thread.
I wait new build from dev. I use my device as primary phone but this build Calling not work. That why I decided not flash this
Sony released remote play for all Android phones this week with compatibility from Android 5.0 onward but it's recommend to have Android 10 to use a DS4 due to better compatibility drivers. Is there any chance you could rip the drivers from the OnePlus 7 or 7 pro on OOS 10 put them in a zip and flash them through TWRP or magisk?
I think you just need to wait since the official update is coming this month of October.
Graffiti Exploit said:
I think you just need to wait since the official update is coming this month of October.
Click to expand...
Click to collapse
Not to argue specifics but the beta comes out this month and the full release is next month. But I understand your point. I still want to know if it's possible to do it though.
Drivers are in the kernel in Linux based systems. You can't just 'rip' the drivers. You have to find a kernel Dev willing to work this with a soon deprecated Android version... with yet unpublished oos kernel sources, only AOSP ones. Not easy
That's why it will be more easy to wait beta / official OOS. Or perhaps be ready to try one of the Android 10 ROMs floating around there
Striatum_bdr said:
Drivers are in the kernel in Linux based systems. You can't just 'rip' the drivers. You have to find a kernel Dev willing to work this with a soon deprecated Android version... with yet unpublished oos kernel sources, only AOSP ones. Not easy
That's why it will be more easy to wait beta / official OOS. Or perhaps be ready to try one of the Android 10 ROMs floating around there
Click to expand...
Click to collapse
Understandable thanks for the answer, I thought it was more like the adreno drivers that you could update through TWRP or magisk I forget which one I just remember doing it on my V20.