Database Users

[Q] How to install new android on A1000L-F

Hi!
Can someone guide me little with rootting and installing new android on IdeaPad A1000L-F?
I've found a lot of guides, but none of those are for this wlan model only, I think? I would be so happy, if someone could tell me how and what can I do with this. Current android (4.1) is so outdated, that I cant stand this. And latest games don't even install on this version.
Thanks!
Edit: Got my tab rooted with one click root, but what now?

any help yet? i have same tablet and same question:silly:

Nothing yet, sorry. We'll see, maybe someone gives us a little advice soon. Hope so!

First, you'd have to port a recovery (cwm or twrp) to your device and fastboot flash it.
You'll have to use a repo for aosp, cm, miui, or other and make a rom.
The a1000l source code is available here: http://mobilesupport.lenovo.com/us/en/products/a1000_tablet?tabname=downloads
You will need that in your venture.
Unfortunately, this is just not a popular tablet. I bought one for my daughter and rooted it, but that's about as far as I will go with it.
Good luck!

It looks like recovery is already available for T, F, models. I'm not certain if this will translate over to G, L models or not:
CLICK HERE FOR REDIRECT
This is from page 3 of that translated russian thread:
Administrator
1004 posts
481
Honored forumchanin
Extras. Information [+]
Posted November 29, 2013 - 10:03
pitshocker написал (28 Nov 2013 - 11:12):
I think this recovery is not compatible for A1000L-F 8Gb model?
Version of the A1000-F can earn. Use at your own risk, no one has tested it.
Click to expand...
Click to collapse
The only "custom" ROM I have found is just a modified version of stock. This means no version upgrade:
CLICK HERE FOR REDIRECT

I am unable to get flashtool working from those threads and fastboot is not detecting the device in Windows or Linux. I was hoping to "fastboot boot recovery.img" in order to do some testing, but no luck right now. I'll mess around some other time...

I've got working CWM on my A1000L-F thanks to the links in this thread:
http://forum.xda-developers.com/showpost.php?p=50187460&postcount=2
Lenovo has only released broken source so compiling 4.2+ will be too much of a hassle for an $80 tab that my daughter uses...

[UPDATED]Firefox OS 1.4 for ZTE Open

Hello Guys, i am here to share FF OS 1.4 build for ZTE Open
Much more stable than previous build.
Code:
[b]fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash cache ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img[/b]
Link(updated)(22-09-14)

Thank you, I build fos myself and use your boot.img to flash my phone and now it boots well.
Could you explain which changes you have made to boot.img (and from which version)?

sekun said:
Thank you, I build fos myself and use your boot.img to flash my phone and now it boots well.
Could you explain which changes you have made to boot.img (and from which version)?
Click to expand...
Click to collapse
Which version you have compiled?
I didn't modified any boot.img
It was modified by someone else.
One More Question:
Did you ZTE Open hangs most of the times?

LinuxHolic said:
Which version you have compiled?
I didn't modified any boot.img
It was modified by someone else.
One More Question:
Did you ZTE Open hangs most of the times?
Click to expand...
Click to collapse
First I built from 1.1B02 to 1.3 and modified boot image according to this method [1] and made these modifications [2].
Next, built from 1.3 to 1.4 and used your boot img.
I've just tested 1.4 a little for now, and my zte open never hangs on 1.3.
[1] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[2] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9

sekun said:
First I built from 1.1B02 to 1.3 and modified boot image according to this method [1] and made these modifications [2].
Next, built from 1.3 to 1.4 and used your boot img.
I've just tested 1.4 a little for now, and my zte open never hangs on 1.3.
[1] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[2] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
Click to expand...
Click to collapse
How did you installed 1.3 on you phone?
An .img files?
I wasn't able to install it on my phone. Tried with 3 different boot.img files
Thanks

LinuxHolic said:
How did you installed 1.3 on you phone?
An .img files?
I wasn't able to install it on my phone. Tried with 3 different boot.img files
Thanks
Click to expand...
Click to collapse
I've followed this tutorial [1] (built from 1.1 to 1.3, set BRANCH=v1.3 instead of v1.2 in the script) and have modified boot.img according to the 2 links [2] and [3] mentioned before.
[1] rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open
[2] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[3] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9

sekun said:
I've followed this tutorial [1] (built from 1.1 to 1.3, set BRANCH=v1.3 instead of v1.2 in the script) and have modified boot.img according to the 2 links [2] and [3] mentioned before.
[1] rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open
[2] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[3] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
Click to expand...
Click to collapse
Can you give me the boot.img that you modified?
Thanks

LinuxHolic said:
Can you give me the boot.img that you modified?
Thanks
Click to expand...
Click to collapse
filebin.net/hfalt65z3o/boot-1.3.0.img

Works great!!!
LinuxHolic said:
Hello Guys, i am here to share FF OS 1.4 build for ZTE Open
This will work for all those who are having Bootloop issues while flashing Custom firmware
This build is compiled by someone so i take no credit for that. I'm just here to share that
Code:
[b]fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash cache ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img[/b]
Click to expand...
Click to collapse
This image works great. At least as far as I have tested. Much snappier than 1.1, 1.2.
Could I ask (beg) you to compile a japanese version?
I'm giving a talk in Japan on JavaScript in about a month and I was hoping to show off this device.
I'd really appreciate it if you could do this for me.
I believe the information contained here may be helpful: ... 8 / I cannot post links as a newbie...
The comments at this bugzilla page explain how to add japanese text @ bugzilla mozilla org show_bug.cgi ? id=933252#c16
thank you so much!

asdf2a3 said:
This image works great. At least as far as I have tested. Much snappier than 1.1, 1.2.
Could I ask (beg) you to compile a japanese version?
I'm giving a talk in Japan on JavaScript in about a month and I was hoping to show off this device.
I'd really appreciate it if you could do this for me.
I believe the information contained here may be helpful: ... 8 / I cannot post links as a newbie...
The comments at this bugzilla page explain how to add japanese text @ bugzilla mozilla org show_bug.cgi ? id=933252#c16
thank you so much!
Click to expand...
Click to collapse
As i've already mentioned earlier that this build has been compiled by someone(not me)

Whoops
LinuxHolic said:
As i've already mentioned earlier that this build has been compiled by someone(not me)
Click to expand...
Click to collapse
:crying: My bad. I didn't read before I installed..
Could you point me in the right direction?
My own builds of b2g have been less than successful. The closest I've gotten was to get a unstable versions installed.

you may want to have a look at neuralassembly . blogspot . com (can't post links....) its in japanese and he explains how to build a japanese enabled version for Samsung Galaxy S3, you'll have to adapt that but i guess at least you will be able to read it without google translate
hope this is helpful to you.

linr76 said:
you may want to have a look at neuralassembly . blogspot . com (can't post links....) its in japanese and he explains how to build a japanese enabled version for Samsung Galaxy S3, you'll have to adapt that but i guess at least you will be able to read it without google translate
hope this is helpful to you.
Click to expand...
Click to collapse
Thanks, I can and have compiled for this device. The tricky parts are finding a version that is stable enough to use. And getting all of the right proprietary drivers. And there may be some other unknown(s) that I'm messing up. The version you've posted tells me the git version so that's 1 of the 2 major foreseeable obstacles.
Call me a conspiracy nut, but what's the big deal with closed source drivers on cell phones? So what if the public finds out how to write to a screen or send communication over the radio. Technically we can already write to small lcd screens with adrino parts and communicate over the air with shortwave. And yet every single phone out there is closed, even the Maemo was partially closed. I don't see any legitimate reason for this other than some giant conspiracy by large corporations. Either the ma bells don't want us using the air-waves for free or the governments of the world don't want us not being tracked. And I suppose it's a lot of both.

well, it was just an example on how to get japanese working on the device, not really a cookbook.
for the building i guess you should follow the instructions on Mozilla developer network.
they have a page dedicated to the ZTE Open.
mine will arrive maybe next week, so i cant really build yet, since the phone has to be connected for the build to proceed.
and i am fine with it being in english, even though my native language is german, but i always change the language to english (must be an IT thing with me)

linr76 said:
well, it was just an example on how to get japanese working on the device, not really a cookbook.
for the building i guess you should follow the instructions on Mozilla developer network.
they have a page dedicated to the ZTE Open.
mine will arrive maybe next week, so i cant really build yet, since the phone has to be connected for the build to proceed.
and i am fine with it being in english, even though my native language is german, but i always change the language to english (must be an IT thing with me)
Click to expand...
Click to collapse
There are some official ZTE versions out there with fastboot disabled. B06 is safe. But be careful to read about other user experiences before you upgrade.

asdf2a3 said:
There are some official ZTE versions out there with fastboot disabled. B06 is safe. But be careful to read about other user experiences before you upgrade.
Click to expand...
Click to collapse
As far as I am aware when ZTE first released the 1.1 Firefox OS update through their website it was released without fastboot enabled. This however was a mistake, so they took those files down and re-uploaded newly compiled versions of the same Firefox OS 1.1 but with fastboot enabled. :good:

thanks for the warnings, i have read about that and i think it is even stated on the MDN.
i think because of this there is also a lot of misunderstandings, as i do not think you need a hacked boot.img if your phone has fastboot enabled already.
well i guess i will find out when it arrives, as i want to upgrade at least to 1.3
this wont be my daily use device, i just want to see where FXOS stands and is developing to.
if i like it i guess i would go for a more mid-level device (like a Alcatel Fire E/S or the new not yet announced higher spec ZTE)
my only gripe here is that sony doesnt seem to move on and release their FXOS phone, and the support with Alcatel was a bit patchy so far from what you read.
it would be nice if all of the FXOS phones had the possibility to be used as Dev-devices.

Deleted

Hi,
Thanks for this release. Is all the device working ? I mean GPS, WiFi etc...
I'm new to Firefox OS, and I would like to install the latest fully functional release
Anyway thanks for your great work !

Nitroman70 said:
Hi,
Thanks for this release. Is all the device working ? I mean GPS, WiFi etc...
I'm new to Firefox OS, and I would like to install the latest fully functional release
Anyway thanks for your great work !
Click to expand...
Click to collapse
I am not the creator/uploader of this post but I have installed it multiple times and know a little bit about this kind of thing It is a pre-release version so it is far from being complete or "stable"... I would not suggest using this build for daily use as there is no guarentee everything will work correctly even if it does for someone else, but for testing and/or restoring a bricked (broken phone) it is perfect.

Sailfish for Android devices release!

Hello guys,
I just got an awesome e-mail from Jolla. I think they don't mind posting it here for everyone interested to see, it even mentioned this forum. If anyone feels I'm sharing confidential stuff, please PM me
Here it is:
Dear early adopter of SailfishOS for Android devices.
We're kicking off today by publishing the first Early Adopter Release of SailfishOS (1.0.4.20) for Nexus 4 (mako) to early adopters. Please make sure to read this whole e-mail through.
Later we'll be publishing images for Samsung Galaxy S III LTE (i9305) and we'll be delivering updated images as we go along for each device as hardware support improves. This is just the beginning.
We are also working on the SailfishOS hardware adaptation development kit, which describes how to port SailfishOS to existing CyanogenMod 10.1 devices. Later versions of CM will be supported eventually. We'll publish the HADK in the next few weeks if everything goes well.
This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see release notes below. We think it's worth sharing already now to get all of you properly included in the early stages of the project.
We want to build a community around SailfishOS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is an under-development snapshot and not a final product release.
It is important for Jolla that the correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product.
WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.
NOTE: You will lose your on-device data, so make a proper backup.
To install this release of SailfishOS on a Nexus 4 device:
* 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
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/android/nexus/images#instructions
b. Download links can be found here: https://developers.google.com/android/nexus/images#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. The file you want to download is cm-10.1.3-mako.zip
b. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the SailfishOS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.4.20-EA1.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 SailfishOS .zip file in the same way ("on top of it")
* Reboot bootloader, SailfishOS should boot and be visible
We can recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
If you want to go back to normal CyanogenMod:
a. Boot into recovery mode
b. Choose "Wipe data / factory reset"
c. Flash cm-10.1.3-mako.zip
d. (to go back to SailfishOS, flash the SailfishOS .zip on top of it)
To SSH into your device via USB (Linux)
1. Enable remote connection in Settings->System->Developer mode
2. Set your USB interface on host machine to IP 192.168.2.2
3. ssh [email protected]
4. Use the password from developer mode to log in
5. Use the 'devel-su' command with the same password in order to gain root
6. To SSH over WLAN, use IP listed in developer mode under "WLAN IP address"
Release notes and Known issues for Early Adopter Release 1 for mako/Nexus 4:
* We have a subtle watermark underneath the UI at all times stating "SailfishOS development software" "This is not production quality". Developer mode is activated at all times.
* Modem and related functionality works, 3G data, SMS but no call audio (comes in next release). There has been no throughout testing of telephony related functionality (roaming, airplane mode, data counters, etc) and any use of this functionality is at your own risk.
* Sensors, Device clock/alarms, Reset device, Bluetooth, USB control + MTP, Bluetooth, WLAN hotspot, Camera (photography, video recording), and video playback is not supported in this release.
* Jolla account / Store is removed from the image due to problems with registering with Jolla infrastructure.
* The image SW is not currently upgradeable, nor is any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, or word prediction for virtual keyboard preinstalled.
* After returning from suspend, UI may be slow for a moment. It is not possible to double-tap to wake up the device. Power button may fail to wake device at times, check if you are covering the proximity sensor. Powering off device puts it into a state of deep slumber; possible to get out of by holding power button and volume down key with a bit of persistence.
* Fingerterm applications may fail to launch during first attempts.
* FPS drop while scrolling in homescreen due to non-batching when rendering of application icon grid
* Icons/graphics appear unproportionally small in browser toolbar, time select widget, and Settings favourite icons
* Multiboot / multirom is not supported currently
We will all meet in #sailfishos on irc.freenode.net and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at http://github.com/mer-hybris .
You are also welcome to participate in threads at http://forum.xda-developers.com/nexus-4/general about Nexus 4 and SailfishOS as well as for more general SailfishOS topics at http://forum.xda-developers.com/jolla-sailfish/general
Best regards,
Carsten Munk (Stskeeps) on behalf of the SailfishOS for Android devices team
Chief Research Engineer @ Jolla
Click to expand...
Click to collapse

Daycrawler said:
Hello guys,
I just got an awesome e-mail from Jolla. I think they don't mind posting it here for everyone interested to see, it even mentioned this forum. If anyone feels I'm sharing confidential stuff, please PM me
Here it is:
Click to expand...
Click to collapse
Great, I'll give it a try

Daycrawler said:
Hello guys,
I just got an awesome e-mail from Jolla. I think they don't mind posting it here for everyone interested to see, it even mentioned this forum. If anyone feels I'm sharing confidential stuff, please PM me
Here it is:
Click to expand...
Click to collapse
Can't we just flash CM 10.1 instead of flashing the 4.2.2 factory images?

Zehlek said:
Can't we just flash CM 10.1 instead of flashing the 4.2.2 factory images?
Click to expand...
Click to collapse
no you should't, because the images also contain radios and those are needed that sailfish works properly on the nexus 4

Oli28 said:
no you should't, because the images also contain radios and those are needed that sailfish works properly on the nexus 4
Click to expand...
Click to collapse
I just flashed
1. Older bootloader
2. Older Radio
3. CM 10.1.3
4. Sailfish

Just tweeted by Nemo mobile
You can now try Glacier UI even on #Nexus4 ! Via #sailfishforandroid project and http://t.co/mGaE1KqbAj
Sent from my HTC One using xda app-developers app

I'll try this asap

Tried it.
But somehow the mobile data isn't working for me.
(just flashed JDQ39 bootloader and radio instead oft the whole Firmware)

jedi2001 said:
Tried it.
But somehow the mobile data isn't working for me.
(just flashed JDQ39 bootloader and radio instead oft the whole Firmware)
Click to expand...
Click to collapse
Check the settings , its quite tricky

And where there?
If I enable mobile data in the settings I just geht an error popin on the top. "problems with data connection" vor something similar.

I had no problem with 4.2 radio with T-Mobile in the US. No settings changed.
Sent from my Nexus 4 using Tapatalk

Thats a great news, lets hope thay make it available for the S4 soon.

I finally had some time to look into the problem.
Sailfish had the wrong APN
Edit:
After two hours playing with Sailfish, I can say that the Sailfish feels nice and it seems quite stable.
No comparison to the very buggy Ubuntu.
Once camera and bluetooth works, and we get a chance to at least buy AlienDalvik on their app store, this could become my main OS.

are there mako drivers or config files in the sailfish zip ?
can this sailfish zip be installed on nexus 7 grouper?
or does it has to be build specific for grouper?

frullewulle said:
are there mako drivers or config files in the sailfish zip ?
can this sailfish zip be installed on nexus 7 grouper?
or does it has to be build specific for grouper?
Click to expand...
Click to collapse
I think you can try it safely, it shouldn't brick anything as it's loaded from the kernel. but I think it will not work. They mention some help in porting soon and I'm waiting for that.

Zehlek said:
Can't we just flash CM 10.1 instead of flashing the 4.2.2 factory images?
Click to expand...
Click to collapse
Just flashed cm10.1.3 and SailfishOS from another custom rom 4.4.2...Everythink should work, works. No problem with SMS, GSM data and OS is very smoothly... Perhaps WLAN?
EDIT: After some tests, radio from factory image 4.2.2 is necessary for WLAN and sound

are the updates for this rom going to be nightly or weekly??
and can anyone please pm me when theres an update??
thanks

Are there any update about other nexus device like galaxy nexus? That phone isn't too old for an official support (I think), and there are lots of people like me who want to try that OS on that device
Sent from my Galaxy Nexus using xda app-developers app

No N5 love makes me a sad bunny...
Sent from my Nexus 5 using Tapatalk

setspeed said:
No N5 love makes me a sad bunny...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same, I would try and force the nexus 4 version to work on the n5, as that is basically how the HADK is going to work, but haven't got time for it yet, I also intend to make an app that copies over SMS and WhatsApp messages between sailfish and android roms, but 1. Don't know if its possible, and 2. No time, due to exam revision.

[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] OmniROM 5.1.1 A500/A501 - V9 - Lollipop Rooting

Found Answer (below) disreguard this:
"Newbie", also I was also drop on my head when I was very young, so please explain as though I'm a 5 year old:
I installed rom and it works great. However I do not have root, near does any app or adb/fastbook code I have tried work to root this.
How or can this be rooted manual or with an app?
Remember, I am very slow learner.
A500 - 5.1.1 20150623 v9
CMM Recovery v5.5.5.0.x rev.7.3 (couldn't install newest version so I just picked an old one).
Skrilax CZ V8 (get an Second kernel image error: Invalid secondary (AKB) kernel image).
However I boot the primary, other than that and not being able to see a root ???
Answer: Found UPDATE-SuperSU-v2.46.zip and installed it in recovery.
Worked like a charm, I'm back in business.

wally wingnut said:
Found Answer (below) disreguard this:
"Newbie", also I was also drop on my head when I was very young, so please explain as though I'm a 5 year old:
I installed rom and it works great. However I do not have root, near does any app or adb/fastbook code I have tried work to root this.
How or can this be rooted manual or with an app?
Remember, I am very slow learner.
A500 - 5.1.1 20150623 v9
CMM Recovery v5.5.5.0.x rev.7.3 (couldn't install newest version so I just picked an old one).
Skrilax CZ V8 (get an Second kernel image error: Invalid secondary (AKB) kernel image).
However I boot the primary, other than that and not being able to see a root ???
Answer: Found UPDATE-SuperSU-v2.46.zip and installed it in recovery.
Worked like a charm, I'm back in business.
Click to expand...
Click to collapse
Could you pls share the source to get the "trusted & reliable" Omni 5.1.1 ROM?

jksmith0011 said:
Could you pls share the source to get the "trusted & reliable" Omni 5.1.1 ROM?
Click to expand...
Click to collapse
No, he wouldn't play nice with XDA rules, so no mention of his work allowed sadly.

can anyone post a download link?

ldeveraux said:
No, he wouldn't play nice with XDA rules, so no mention of his work allowed sadly.
Click to expand...
Click to collapse
Why not?
I try also to get the latest omnirom but cant even register at "Tegraowners" to get a download.