Sailfish OS 2.0.5.6 (alpha) for Zuk Z1 (ham)

Search This thread

tradiz

Member
Jan 4, 2016
10
12
tradiz.org
Tried everything I could but still couldn't get it to boot.
Used Official TWRP this time, flashed as per instructions but simply can't get past boot logo.
Attaching TWRP log with the post, didn't notice anything unusual.
Any help would be much appreciated.
Or if someone who has successfully booted can share the ROM version they were initially using, TWRP versions etc.... I'd be very thankful
I had stock CM 12.1 YOG4P ROM on Zuk Z1 at first. After unlocking device I've just wiped everything and installed CM 12.1 YOG7D (same as used in OP-post) with TWRP (twrp-3.0.2-0-Z1.img) from dl.twrp.me/Z1/. That's all.
Since there is broken USB connection in this image, I need to figure out how we can fix it, even temporarily, for you to get some logs on boot process. I'll try to find solution, give me some time.
 

sahu.prashant

Senior Member
Oct 19, 2014
366
315
26
Chandigarh
I had stock CM 12.1 YOG4P ROM on Zuk Z1 at first. After unlocking device I've just wiped everything and installed CM 12.1 YOG7D (same as used in OP-post) with TWRP (twrp-3.0.2-0-Z1.img) from dl.twrp.me/Z1/. That's all.
Since there is broken USB connection in this image, I need to figure out how we can fix it, even temporarily, for you to get some logs on boot process. I'll try to find solution, give me some time.

Actually mate I was just going to update about my progress here.
I somehow ended up getting my device hard bricked in the most unusual manner (phone ran totally out of battery and wouldn't get charged and showed absolutely no signs of life)
So I had to send it to service center. I thought it was an issue with battery or motherboard had malfunctioned but they simply restored firmware (wiped internal storage in the process). Unfortunately I forgot to note what was the exact version of firmware or COS.
I simply flashed TWRP, wiped system, dalvik/cache and flashed Sailfish OS according to the instructions and it worked, flawlessly!
Now I'm on Resurrection Remix N 5.8.2 and will try flashing Sailfish OS.... Hopefully the results will be desirable.

Thanks for your response and many thanks to the developer for porting it to our device. It was a lovely experience using it.
 
  • Like
Reactions: tradiz

Udaya.kr

Senior Member
Dec 12, 2015
51
16
Bangalore
OnePlus 6
which is the rom in the screenshot ?

---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------

I believe I'm using the same baseband.... I was about to flash Stock COS and try again but like you just stated it's been tested with the same baseband version.

I should perhaps use official TWRP but I believe that would make little difference since flashing both zips was successful.

which is the rom in the screenshot ?
 

zangetsuzuk

Member
Jan 19, 2017
49
10
I had stock CM 12.1 YOG4P ROM on Zuk Z1 at first. After unlocking device I've just wiped everything and installed CM 12.1 YOG7D (same as used in OP-post) with TWRP (twrp-3.0.2-0-Z1.img) from dl.twrp.me/Z1/. That's all.
Since there is broken USB connection in this image, I need to figure out how we can fix it, even temporarily, for you to get some logs on boot process. I'll try to find solution, give me some time.


first of all love the rom :)
and yes usb charging is broken...i just ried charging option , will try mtp option anf c if it works
also when i recieve a call when screen is off i can't lift or reject it...just shows black screen

also when i call someone ,screen blanks out and i cant end call because all i c is black screen

thankyou for ur efforts for making such a awesome port to our zuk z1 , really amazing...
planning to use this as my daily driver but the chargibg problem won't let me ...
please do try to fix it :)

---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------

Sailfish OS 2.0.5.6 for Zuk Z1 (ham) - based on CM-12.1 base

Hi, zuk people.... This is my first build of any rom. It is an alpha build
So don't expect it to be your daily driver
Bugs to my knowledge :
Vibration
Charging % will not be right most the times
Sound bug : starts at 100% and fades away to 20%
No fingerprint middleware for it yet


Working:
RIL
Touch
Camera & Video
Call audio


(OTA coming soon)



If any bugs please do report.

Downloads
CM - https : / / drive.google.com/file/d/0ByIhcy48y4uON2VBeXNmelV3RlU/view?usp=sharing
SailfishOS - https : / / drive.google.com/file/d/0ByIhcy48y4uOeXM2MXRMSnhTZms/view?usp=sharing
(This is my first post. Please fix the links and use it. Sorry)

Installation Instrucions
Go to recovery(twrp)
Wipe partitions (data,system,dalvik/art cache) - (Clean Wipe)
Flash cm-12 image provided above
Flash Sailfish image over that(immediately without reboot)
reboot


FAQ
Does it support VoLTE?
Nope. Please don't make any requests. If zuk releases the VoLTE enabled modem firmware then there is possibility.
Does it run Android Apps?
Nope. There is a chance but still not available.
Playstore?
It has an inbuilt Jolla store which is pointless as they provide that for Licensed devices only (Jolla C, Intex...)
You can download Harbour-Warehouse from openrepos.net


If you are interested in contributing, ping me on telegram @aki237
and totally forgot to mention
Thank @tradiz for making this port possible.
He was of immense help for porting sailfish OS.

feedback :
usb charging is broken
calls over locked screen can't be accessed

awesome rom though....love the sailfish OS ui...
and ambience feature
please do provide the OTA for this...
was never even this excited for zui 2.5
 

karimskcs

Senior Member
May 26, 2016
186
119
Rom is good but dev had to work alot as it doesn't support android applications and buttons are not working finger print also not working.
It is not usable for day to day useage.
Thanks waiting for official launch
 

zangetsuzuk

Member
Jan 19, 2017
49
10
I had stock CM 12.1 YOG4P ROM on Zuk Z1 at first. After unlocking device I've just wiped everything and installed CM 12.1 YOG7D (same as used in OP-post) with TWRP (twrp-3.0.2-0-Z1.img) from dl.twrp.me/Z1/. That's all.
Since there is broken USB connection in this image, I need to figure out how we can fix it, even temporarily, for you to get some logs on boot process. I'll try to find solution, give me some time.


tried mtp mode to charge ....same problem...
tried switching it off and charging....didn't work either...

well only way to charge ur phone in sailfish OS alpha version is to boot to recovery and charge it...

and the problem where we can't accept calls over lock screen ... tried putting no device pin but still doesn't work
 

tradiz

Member
Jan 4, 2016
10
12
tradiz.org
tried mtp mode to charge ....same problem...
tried switching it off and charging....didn't work either...
well only way to charge ur phone in sailfish OS alpha version is to boot to recovery and charge it...
There is mess with power supplies drivers in current image which in result gives wrong data about battery and charger status read by statefs daemon. As temporary&dirty hack you can run "systemctl stop statefs" from terminal as root, plug-in charger for time enough for full charge (there is no indication for charging, but it works), unplug cable and run "systemctl start statefs" after.

and the problem where we can't accept calls over lock screen ... tried putting no device pin but still doesn't work
Interesting, I met this bug on other port with same SFOS version.
 

zangetsuzuk

Member
Jan 19, 2017
49
10
There is mess with power supplies drivers in current image which in result gives wrong data about battery and charger status read by statefs daemon. As temporary&dirty hack you can run "systemctl stop statefs" from terminal as root, plug-in charger for time enough for full charge (there is no indication for charging, but it works), unplug cable and run "systemctl start statefs" after.


Interesting, I met this bug on other port with same SFOS version.


thank you for the trick :)
im not sure how to root sailfish os as it is totally linux based and already has su binaries installed ..
what do i do to gain root access to run the above command in terminal?
 

tradiz

Member
Jan 4, 2016
10
12
tradiz.org
thank you for the trick :)
im not sure how to root sailfish os as it is totally linux based and already has su binaries installed ..
what do i do to gain root access to run the above command in terminal?
Go to "Settings" -> "Developer mode" page and get root password or set your own. Then open Terminal app, type in "devel-su" command, then enter password you set/got earlier. That's it.

is there no temporary fix for it because i saw some patch apps in warehouse app for it but nothing seems to work

apart from that rom is awesome...
will there be fix for battery and the call issue....
can i help ?
I didn't even try to get some logs for "calls" bug since i'm trying to fix this battery problem, it's most critical atm.
You can help - try to catch this calls bug and get logs in the moment of incoming call:

Connect your device to Internet, then run in Terminal with root rights:
zypper in mce-tools
mcetool --set-verbosity=debug

Now try to reproduce this bug when someone is calling you - when it's done, get back to Terminal and type:
journalctl -b -e > /home/nemo/mce.log
chown nemo:nemo /home/nemo/mce.log

Now you can connect to your device via any SCP-client (WinSCP for example) and get this file from /home/nemo directory, then pastebin it or just send to me. You can get phone's IP-address on the same Developer's page.
 

zangetsuzuk

Member
Jan 19, 2017
49
10
Go to "Settings" -> "Developer mode" page and get root password or set your own. Then open Terminal app, type in "devel-su" command, then enter password you set/got earlier. That's it.


I didn't even try to get some logs for "calls" bug since i'm trying to fix this battery problem, it's most critical atm.
You can help - try to catch this calls bug and get logs in the moment of incoming call:

Connect your device to Internet, then run in Terminal with root rights:
zypper in mce-tools
mcetool --set-verbosity=debug

Now try to reproduce this bug when someone is calling you - when it's done, get back to Terminal and type:
journalctl -b -e > /home/nemo/mce.log
chown nemo:nemo /home/nemo/mce.log

Now you can connect to your device via any SCP-client (WinSCP for example) and get this file from /home/nemo directory, then pastebin it or just send to me. You can get phone's IP-address on the same Developer's page.


after installing it for the 3rd time somehow it works
....
i guess the reason is because i didn't start the tutorial...so my first call that i received was over lock screen and it showed instructions to accept/reject the call ...there on everything works fine:)

---------- Post added at 12:21 AM ---------- Previous post was at 12:18 AM ----------

Go to "Settings" -> "Developer mode" page and get root password or set your own. Then open Terminal app, type in "devel-su" command, then enter password you set/got earlier. That's it.


I didn't even try to get some logs for "calls" bug since i'm trying to fix this battery problem, it's most critical atm.
You can help - try to catch this calls bug and get logs in the moment of incoming call:

Connect your device to Internet, then run in Terminal with root rights:
zypper in mce-tools
mcetool --set-verbosity=debug

Now try to reproduce this bug when someone is calling you - when it's done, get back to Terminal and type:
journalctl -b -e > /home/nemo/mce.log
chown nemo:nemo /home/nemo/mce.log

Now you can connect to your device via any SCP-client (WinSCP for example) and get this file from /home/nemo directory, then pastebin it or just send to me. You can get phone's IP-address on the same Developer's page.


next time i get this issue using sailfish with calls i'll surely provide you with the logs
 

zangetsuzuk

Member
Jan 19, 2017
49
10
the work around for calls to work is

as the tutorial starts press start tutorial and lock the screen , now upon unlocking the screen u can c that u skipped the tutorial part...

now try calling to ur phone if u still c black screen double press volume button....
u get options to decline and leave message , if u swipe down u can accept the call

---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------

media doesn't play from default media apps or any other music players from wearhouse app...

vibrations won't work and can't play songs via Bluetooth

if u guys can fix this...then its a great daily driver since lenovo keeps promising us updates but didn't even release a single ota to a android version ...
anything that v got was for cm12.1....incremental updates.....

now with this Sailfish Os port...
atleast there is something totally new we can try .



awesome job guys :good::laugh::)
 

zangetsuzuk

Member
Jan 19, 2017
49
10
can't play music...
found some methods,in one plus one forms but didn't workout :(
most of the zuk z1 specs r same as that of one plus one...
thought if i used some lib files from that to fix audio it would work but unfortunately it didn't ...
i even tried to change directory so sailfish can read my sd card by default ...
that too didn't go well coz i did something wrong i guess
 

zangetsuzuk

Member
Jan 19, 2017
49
10
c'mon guys
is no one excited about sailfish os?
i mean after reading one plus one forms...
i find few people r actually testing sailfish or few don't know that there is a page in xda...


i mean zuk z1 is advanced version of oneplus one...
it has all the desired qualities....good battery, fingerprint scanner, camera,metal frame
then y does one plus still receive all the fame and not zuk z1
 

zangetsuzuk

Member
Jan 19, 2017
49
10
Go to "Settings" -> "Developer mode" page and get root password or set your own. Then open Terminal app, type in "devel-su" command, then enter password you set/got earlier. That's it.


I didn't even try to get some logs for "calls" bug since i'm trying to fix this battery problem, it's most critical atm.
You can help - try to catch this calls bug and get logs in the moment of incoming call:

Connect your device to Internet, then run in Terminal with root rights:
zypper in mce-tools
mcetool --set-verbosity=debug

Now try to reproduce this bug when someone is calling you - when it's done, get back to Terminal and type:
journalctl -b -e > /home/nemo/mce.log
chown nemo:nemo /home/nemo/mce.log

Now you can connect to your device via any SCP-client (WinSCP for example) and get this file from /home/nemo directory, then pastebin it or just send to me. You can get phone's IP-address on the same Developer's page.



i found this
...will these work ?
 

Attachments

  • Screenshot_2017-04-17-21-02-09-1550719896.jpg
    Screenshot_2017-04-17-21-02-09-1550719896.jpg
    204.2 KB · Views: 273

mukesht

Member
Mar 24, 2015
38
94
Thank you.
Can you pls share the procedure to port sailfish os ? So I will try it for my Lenovo K6 Power.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    /* *** Disclaimer
    * I am not responsible for bricked devices, dead SD cards, thermonuclear war,
    * or you getting fired because the alarm app failed. Please do some research
    * if you have any concerns about features included in this ROM/KERNEL
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point your finger at me for messing up your device, I will laugh at you.
    * BOOM! goes the dynamite
    */

    Sailfish OS 2.0.5.6 for Zuk Z1 (ham) - based on CM-12.1 base

    Hi, zuk people.... This is my first build of any rom. It is an alpha build
    So don't expect it to be your daily driver
    Bugs to my knowledge :
    • Vibration
    • Charging % will not be right most the times
    • Sound bug : starts at 100% and fades away to 20%
    • No fingerprint middleware for it yet

    Working:
    • RIL
    • Touch
    • Camera & Video
    • Call audio

    (OTA coming soon)



    If any bugs please do report.

    Downloads
    CM - https : / / drive.google.com/file/d/0ByIhcy48y4uON2VBeXNmelV3RlU/view?usp=sharing
    SailfishOS - https : / / drive.google.com/file/d/0ByIhcy48y4uOeXM2MXRMSnhTZms/view?usp=sharing
    (This is my first post. Please fix the links and use it. Sorry)

    Installation Instrucions
    1. Go to recovery(twrp)
    2. Wipe partitions (data,system,dalvik/art cache) - (Clean Wipe)
    3. Flash cm-12 image provided above
    4. Flash Sailfish image over that(immediately without reboot)
    5. reboot

    FAQ
    Does it support VoLTE?
    Nope. Please don't make any requests. If zuk releases the VoLTE enabled modem firmware then there is possibility.
    Does it run Android Apps?
    Nope. There is a chance but still not available.
    Playstore?
    It has an inbuilt Jolla store which is pointless as they provide that for Licensed devices only (Jolla C, Intex...)
    You can download Harbour-Warehouse from openrepos.net


    If you are interested in contributing, ping me on telegram @aki237
    and totally forgot to mention
    Thank @tradiz for making this port possible.
    He was of immense help for porting sailfish OS.
    5
    5
    Done. Now there is page for ZUK Z1 port on merproject's wiki. And here is link to Sailfish OS 2.1.0.11 alpha1 installation zip-file and upcoming versions as well: http://images.devaamo.fi/sfe/ham/
    Make sure you have reflashed CM 12.1 YOG7D image from wikipage above before installing SFOS 2.1.0.11 alpha1 because it's new one.
    2
    Tried everything I could but still couldn't get it to boot.
    Used Official TWRP this time, flashed as per instructions but simply can't get past boot logo.
    Attaching TWRP log with the post, didn't notice anything unusual.
    Any help would be much appreciated.
    Or if someone who has successfully booted can share the ROM version they were initially using, TWRP versions etc.... I'd be very thankful
    I had stock CM 12.1 YOG4P ROM on Zuk Z1 at first. After unlocking device I've just wiped everything and installed CM 12.1 YOG7D (same as used in OP-post) with TWRP (twrp-3.0.2-0-Z1.img) from dl.twrp.me/Z1/. That's all.
    Since there is broken USB connection in this image, I need to figure out how we can fix it, even temporarily, for you to get some logs on boot process. I'll try to find solution, give me some time.
    2
    All major issues have been fixed (battery/charge status, audio volume, vibration, OTA-updates), I plan to release new ROM on next week, some preparation is still needed.