Develop Bugs

[beta] [SFOS] SailfishOS 2.1.3.7 for cancro

Introduction
Sailfish OS is a mobile operating system combining the Linux kernel for a particular hardware platform use, the open-source Mer core middleware, a proprietary UI contributed by Jolla, and other third-party components.
Click to expand...
Click to collapse
This is a port of Sailfish OS to cancro (Xiaomi Mi3/Mi4), based on CyanogenMod 12.1.
What Works: https://wiki.merproject.org/wiki/Adaptations/libhybris#Smartphones (Check Xiaomi Mi3)
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Whats new:
Updated to Sailfish 2.1.3.7
Click to expand...
Click to collapse
Known issues:
1) Wifi mac address not detected properly
Click to expand...
Click to collapse
Current TODOs: Sailfish OS on cancro's Trello Board
Download links:
Cyanogenmod 12.1 base: https://www.androidfilehost.com/?fid=529152257862691291 (Mirroring this, as CM servers are shutting down)
Sailfish OS rootfs: https://www.androidfilehost.com/?fid=817906626617953262
Click to expand...
Click to collapse
Installation Instructions:
NOTE: This release is also available as an OTA to existing users.
1) Make sure your device has the new partition layout needed for Android M and a custom recovery. Boot to Recovery, wipe cache, dalvik-cache, system and data. ( https://jrizzoli.github.io/dotfiles/ )
2) First install cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-cancro.zip As your base ROM, and make sure it works well.
3) Then Install sailfishos-cancro-release-2.1.3.7-beta.zip on top of it. This will replace your boot image with sailfish boot image, and installs sailfish os to /data/.stowaways/sailfishos . The installation can take a little while, so be patient.
If you are already running, CM12.1 YOG7D/already have SailfishOS installed, you can simply flash the Sailfish OS without wiping flash/partition.
Click to expand...
Click to collapse
Big kudos to @mixmoto and Nokius, for patiently testing this release over and over.
P.S Thank you all for your support. I really really appreciate it - and it's what motivated me to make some time in my busy days to create this release. Wish you all Happy Holidays!
XDA:DevDB Information
Sailfish OS for cancro, ROM for the Xiaomi Mi 3
Contributors
saidinesh5, Ar4er, Folks at #sailfishos-porters, especially @mal-
Source Code: https://github.com/CancroSailors
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Must have CM12.1-YOG7D
Based On: CyanogenMod 12.1-YOG7D
Version Information
Status: Alpha
Created 2016-09-15
Last Updated 2018-01-07

Hey Dinesh,
Thanks for your work,
does this have sfdroid support?

Ekril said:
Hey Dinesh,
Thanks for your work,
does this have sfdroid support?
Click to expand...
Click to collapse
Hey, Nope. SFDroid support is on my TODO list for now.
It may take a while though. I need a Multirom working with CM13.0(which is my primary ROM), so I can safely port all the needed changes for SFDroid to my CM12.1 base without losing all my data. Any help welcome here!
Cheers

saidinesh5 said:
Hey, Nope. SFDroid support is on my TODO list for now.
It may take a while though. I need a Multirom working with CM13.0(which is my primary ROM), so I can safely port all the needed changes for SFDroid to my CM12.1 base without losing all my data. Any help welcome here!
Cheers
Click to expand...
Click to collapse
Thank you!!! this is awesome!!
Almost everything it seems to be working :good:
Is it stable for daily use?

Rocketval said:
Thank you!!! this is awesome!!
Almost everything it seems to be working :good:
Is it stable for daily use?
Click to expand...
Click to collapse
Great!
Right now i don't think it's ready for daily use yet, as sometimes my device's sensors and audio stop working randomly. Not sure if it is just my device though (because of some weird hacks I've been using).
I suspect this maybe because the CM 12.1 zip i was using to boot differs from the sources I've used to compile this rom. Once that issue is fixed, i think this will be usable for daily use. Camera works, Browser works, basic apps work.. And compiling that cm 12.1 means even sfdroid will work ...

saidinesh5 said:
Great!
Right now i don't think it's ready for daily use yet, as sometimes my device's sensors and audio stop working randomly. Not sure if it is just my device though (because of some weird hacks I've been using).
I suspect this maybe because the CM 12.1 zip i was using to boot differs from the sources I've used to compile this rom. Once that issue is fixed, i think this will be usable for daily use. Camera works, Browser works, basic apps work.. And compiling that cm 12.1 means even sfdroid will work ...
Click to expand...
Click to collapse
For what I know only few cm12 builds worked fine when flashed before sfos..
Maybe you need another build.. I don't know..

Rocketval said:
For what I know only few cm12 builds worked fine when flashed before sfos..
Maybe you need another build.. I don't know..
Click to expand...
Click to collapse
Could be. Most bugs i had to fix last week were because of differing versions too. That's why I'm trying to compile a cm12.1 right now.
Also right now as I'm on CM13.0, i was just using a system.img from the CM12.1.zip.. And making sailfish loop Mount that as the actual /system/ . not sure if that's causing any issues.
Right now my options are port multirom to CM13.0 (having some weird errors there) or wipe my device clean and downgrade to CM12.1 (have been trying to avoid this for months now!).

saidinesh5 said:
Could be. Most bugs i had to fix last week were because of differing versions too. That's why I'm trying to compile a cm12.1 right now.
Also right now as I'm on CM13.0, i was just using a system.img from the CM12.1.zip.. And making sailfish loop Mount that as the actual /system/ . not sure if that's causing any issues.
Right now my options are port multirom to CM13.0 (having some weird errors there) or wipe my device clean and downgrade to CM12.1 (have been trying to avoid this for months now!).
Click to expand...
Click to collapse
Yeah, we definetely need multirom, with 64gb mi4w I have more than 32+ free and a lot of will to try

Thank bro

Thank you!!!

As a temporary fix for radio, pulseaudio could be restarted, NOT as root.
Code:
systemctl restart pulseaudio --user

adeen-s said:
As a temporary fix for radio, pulseaudio could be restarted, NOT as root.
Code:
systemctl restart pulseaudio --user
Click to expand...
Click to collapse
I currently use this command everytime i wanted the FM radio to work. I will have to look into why this is failing by default though
Code:
$pactl set-source-port source.primary input-fm_rx

i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?

Dr. Ramm said:
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Click to expand...
Click to collapse
this isn't android, you cannt flash gapp

Dr. Ramm said:
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Click to expand...
Click to collapse
Due to legal reasons, Sailfish OS doesn't bundle the proprietary blobs(device drivers, system libraries etc..) provided by the phone vendors in it's zip.
As I have compiled Sailfish OS using sources from CM-12.1, it tries to access these proprietary files on your device via. CM-12.1 libraries. That's why you have to flash a CM-12.1 zip first, before flashing Sailfish OS. (i.e just clean flashing sailfish.zip won't work)
As of now, you don't have to flash gapps, as there is no way to use them from Sailfish OS. Once we get sfdroid running, we can run Android apps from within Sailfish OS, then you can flash gapps if you want.
Sailfish OS already comes with an su binary (accessed via. devel-su command) and full root access. So, you won't need Super SU.

saidinesh5 said:
As I have compiled Sailfish OS using sources from CM-12.1, it tries to access these proprietary files on your device via. CM-12.1 libraries. That's why you have to flash a CM-12.1 zip first, before flashing Sailfish OS. (i.e just clean flashing sailfish.zip won't work)
Click to expand...
Click to collapse
got it
saidinesh5 said:
As of now, you don't have to flash gapps, as there is no way to use them from Sailfish OS. Once we get sfdroid running, we can run Android apps from within Sailfish OS, then you can flash gapps if you want.
Click to expand...
Click to collapse
Stock market not working (as u say in 1st post) but how i can install some apps?
saidinesh5 said:
Sailfish OS already comes with an su binary (accessed via. devel-su command) and full root access. So, you won't need Super SU.
Click to expand...
Click to collapse
nice

run very smooth on my mi3

Dr. Ramm said:
got it
Stock market not working (as u say in 1st post) but how i can install some apps?
nice
Click to expand...
Click to collapse
You can use https://openrepos.net/content/basil/warehouse-sailfishos app to install apps.. I will include this in the zip for the next build (Which will soon be available).
First enable installation of untrusted software in Settings, then download the latest rpm of that from your browser and install it.

saidinesh5 said:
You can use https://openrepos.net/content/basil/warehouse-sailfishos app to install apps.. I will include this in the zip for the next build (Which will soon be available).
First enable installation of untrusted software in Settings, then download the latest rpm of that from your browser and install it.
Click to expand...
Click to collapse
can u tll me where located screenshots and how i can upload it on pc
some screens is here

after turn off mi3 10s, i dont turn on device

[ABANDONED][RECOVERY][UNOFFICIAL][SOURCE-BUILT][WIP] TWRP for Huawei Honor 3C

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is an unofficial TWRP 3.x build for the Huawei Honor 3C (h30u10/H30-U10)
This project is abandoned! I'll reopen the thread if I have any progress in the future... If you want anything from me you can contact me in my email address, in Telegram (@iamnotstanley) or in private message.
Only use this binary with your own responsibility, and please read the "known issues" list.
Working:
Everything, except the things in the "known issues" list.
TWRP functional checklist, but in this list not everything applies for our device
Known issues:
flash/restore image (boot&recovery) (installing with a zip [if you're using codelover's fixed update-binary] and backup working correctly) **need help **
Download:
Latest and older versions: See the DevDB Downloads page or click here. (Mirror)
Install:
You can install this recovery in 4 way:
Using an another version of TWRP: install the downloaded zip
Using an another version of TWRP: extract the zip and flash the image
Using SP Flash Tools: extract the zip and flash the image
Using Flashify or other flashing app: extract the zip and flash the image
Revert easily to codelover's TWRP:
Download from here the UPDATE-TWRP-2.8.6.0_H30-U10.zip or the UPDATE-TWRP-2.8.6.0_V2_H30-U10_EU.zip and install it inside the TWRP, after that if you reboot to recovery, you will see the old version.
Changelog:
TWRP changelog: here
Device changelog:
3.1.1-0:
Updated to the latest version.
We still have the the "image flash" problem!
3.1.0-0:
First release for Huawei Honor 3C (h30u10)
Built with omnirom android-5.1 tree
Prebuilt kernel: EU B306 (3.4.67)
Screenshots: See the DevDB Screenshots page or click here.
Credits:
iamnotstanley
codelover
carliv for his bootimg module
MSF-Jarvis for his initial device tree
TeamWin team
omnirom team
XDA:DevDB Information
TWRP for Huawei Honor 3C, Device Specific App for the Honor 3C
Contributors
iamnotstanley, codelover, carliv, MSF-Jarvis, TeamWin team & omnirom team
Source Code: https://github.com/iamnotstanley/android_device_huawei_h30u10/tree/android-5.1
Version Information
Status: Abandoned
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-05-13
Created 2017-04-01
Last Updated 2018-01-29

Reserved

Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources

hassanjavaid8181 said:
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
Click to expand...
Click to collapse
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10

iamnotstanley said:
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
Click to expand...
Click to collapse
really appreciate your efforts:good:
good luck

Bro can we flash magisk by this version.

mnumaher said:
Bro can we flash magisk by this version.
Click to expand...
Click to collapse
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)

Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless

iamnotstanley said:
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Click to expand...
Click to collapse
Thanks.
Is touch working correctly in this version?

mnumaher said:
Thanks.
Is touch working correctly in this version?
Click to expand...
Click to collapse
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Rayquaza said:
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
Click to expand...
Click to collapse
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.

iamnotstanley said:
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
Click to expand...
Click to collapse
Ty bro it's working absolutely fine.
When we will be able to flash img.

mnumaher said:
Ty bro it's working absolutely fine.
When we will be able to flash img.
Click to expand...
Click to collapse
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.

working fine cheers!

iamnotstanley said:
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
Click to expand...
Click to collapse
hi and great work, thanks for that
codelover maybe have a patch for that, past time he say i forget it, but can help you to know how solve that

Hi @iamnotstanley, to answer your question:
If i recall correctly i did explained about the problem in my thread earlier - the problem lies on 3C KK kernels. (MTK variant only)
H30-U10 stock KK kernels do not permit writing to the boot partition (/dev/bootimg) directly, the partition is mounted as read only.
Interestingly, there are some ported recoveries out there that doesn't work, and user doesn't even know about it. (eg: ROM appeared to be flashed successfuly but failed to boot because boot.img didn't get through, missing assert() to stop)
If you find a working H30-U10 recovery that can write to boot for 3C, it's likely using JB kernel or KK kernel from other 6582 compatible KK kernel, not sure if someone has compiled a fully working 3C kernel.
With JB kernel, you will be missing SELinux & some other features, while KK kernel from other device is dangerous IMHO, unless you are 100% sure it's compatible, sometimes i wonder whether those permanently bricked 3C with partition error were using these 'patched' recoveries...
My TWRP 2.8.6.0 has been customized to deal with this, i wrote a few C custom functions for twrp, it works like this;
1) read the partition table while flashing, loop through until you find the details for target partition that you need to write.
2) calculate the size and offset to write (you will need to convert the hex to int, then some math again to get the bs, skip, etc value for dd)
3) use 'dd' to write directly to mmcblock0, instead of C fwrite to the specific built-in partition mount point, eg: /dev/bootimg
Wish i could help more, unfortunately i don't have 3C data with me anymore (hdd crashed), and my work is killing me.
Good luck with that!

codelover said:
Hi @iamnotstanley, to answer your question:
...
Click to expand...
Click to collapse
Hi!
Thanks for your answer, I really appreciate your help.
So the problem is mainly in the kernel. I don't think I can fix this, but I'll try after my exams.

TWRP updated to 3.1.1-0
Hello guys!
I updated the TWRP to 3.1.1-0 yesterday. Unfortunately it still have the image flash issue. If you're interested you can download from the DevDB Downloads page or the Github mirror.

Huawei Honor 3C H30-U10
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance

SHBhatti said:
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
Click to expand...
Click to collapse
Try rooting with root applications such as Baidu root and etc.

TamaziAce said:
Try rooting with root applications such as Baidu root and etc.
Click to expand...
Click to collapse
I was Try to root with king root, king root said that your device is rooted successfully but root checker said no root???? what should i do now..?

[ROM][P905][UNOFFICIAL] Resurrection Remix 5.8.5 Android 7.1.2 20180118

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte

Thanks again a lot for your work.
I wish you a happy new year!

@Valera1978
What such amazing gift for New Year!!!
Thanks for such awesome work my friend!

What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?

Mad07 said:
What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?
Click to expand...
Click to collapse
Hardware and config the same.
The idea is create another thread for custom firmwares, based on lineage\aosp.
Right now it's RR only, i'm working on OMNI rom, and later i'll build more firmwares.

please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion

Dagoncore93 said:
please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion
Click to expand...
Click to collapse
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.

Loakidog said:
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.
Click to expand...
Click to collapse
I received myself the error system ui crashed, and it got stuck on it.

Thanks Valera 1978, what a great new year gift!

I'm actually running Android 5.0.2, so is that Lollipop
Sent from my SM-G935F using XDA-Developers Legacy app

Albinoni said:
I'm actually running Android 5.0.2, so is that Lollipop
Click to expand...
Click to collapse
Yes

ralph_kl said:
I received myself the error system ui crashed, and it got stuck on it.
Click to expand...
Click to collapse
Send Valera1978 a bug report via Private Message. It is the only way developers can isolate the problem and fix it. In most Roms you can take a bug report via developer options.

help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally

theogalaxy said:
help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally
Click to expand...
Click to collapse
Try a full wipe magisk was removed with the latest version and super su added

A little help, please
Hello,
Sorry, but I need an help for understand.
How I can install this system?
I mean, can you explain to me what steps I need to do to install and which files to download?
sorry for my english, which is why I did not understand how to do it
Rosario
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Click to expand...
Click to collapse

Compability
It is can flash for SM-P091 ?

i want the S Pen features and UI of Galaxy Tab S3 on my Galaxy Note 12.1 Pro Wifi. Am I right here and if yes how to do it please?
In terms of the little RAM I have I will use on microSD card as a RAM alternativ. is this a good idea in combination with a custom Rom?
Thx!

[ALPHA] Lineage 15.1 Builds [T00F/T00J] by nguyenhung9x

As we all know the Oreo is something that is quite distant for our device.
We need testers for Oreo Builds who can report bugs with accuracy, provide the logs required and have basic experience in software testing.
Be aware that the current & later releases are unstable & cannot be used as daily drivers.​
BUG:
I don't have device test
Installation Instructions:
- Download the ROM
- Put the downloaded zip files on your SDCard
- Reboot in Recovery
- Wipe System, Cache, Dalvik Cache, Internal and Data Partition
- Flash rom
- Reboot system
Download from google drive: https://drive.google.com/drive/folders/1ktJvwxpb6aFHIr36gOZmv9I32e6gZd2M
XDAevDB Information
[WIP] Oreo Testing & Bug Fixing (T00F/T00J), ROM for the Asus ZenFone 5
Contributors
@nutcasev1.5, @tank0412, @flex1911, @nguyenhung9x
Source Code: github.com/Zentalk-VN
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Alpha
Current Stable Version: None
Current Beta Version: None
Created 2018-08-17

New build flash to fastboot : lineage 15.1

good work

I have updater eror 7 when flash rom

aman3378 said:
I have updater eror 7 when flash rom
Click to expand...
Click to collapse
I will update again file zip , please wait

aman3378 said:
I have updater eror 7 when flash rom
Click to expand...
Click to collapse
https://drive.google.com/file/d/1jouImtwKCEjnKdrWLQ7lig8AdRvxtOtD/view?usp=sharing
Flash again , i have try fix it

nguyenhung9x said:
Flash again , i have try fix it
Click to expand...
Click to collapse
at the end flashing updater eror 11 and bootloop with reboot

Plz fix camera
as the title says, can you please fix the camera? I had no issues with the camera when unlocking the bootloader but when i flash this rom, it says cannot connect to the camera. thx

aman3378 said:
at the end flashing updater eror 11 and bootloop with reboot
Click to expand...
Click to collapse
I have update file zip new , please downloads and flash again

nguyenhung9x said:
I have update file zip new , please downloads and flash again
Click to expand...
Click to collapse
where can i download this ZIP , the link under the post has an old version

nguyenhung9x said:
I will update again file zip , please wait
Click to expand...
Click to collapse
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.

nutcasev1.5 said:
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
Click to expand...
Click to collapse
kkkk I have build lineage 15.0 and it boot last years , https://github.com/VTEK-TEAM , omg
https://forum.xda-developers.com/zenfone-5/development/rom-lineageos-15-0-nguyenhung9x-t3673940

nutcasev1.5 said:
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
Click to expand...
Click to collapse
I use device base fugu oreo and + hardware/intel branch 8.1 of you , i have thanks you in post

is there any point to test on the zenfone 6?

nguyenhung9x said:
kkkk I have build lineage 15.0 and it boot last years , https://github.com/VTEK-TEAM , omg
https://forum.xda-developers.com/zenfone-5/development/rom-lineageos-15-0-nguyenhung9x-t3673940
Click to expand...
Click to collapse
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
nguyenhung9x said:
I use device base fugu oreo and + hardware/intel branch 8.1 of you , i have thanks you in post
Click to expand...
Click to collapse
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.

nutcasev1.5 said:
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
Click to expand...
Click to collapse
I'm sorry, I'm lazy so I'm copying your post, but I'll milk it in the future

nutcasev1.5 said:
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
Click to expand...
Click to collapse
If you and I help each other build the android device, I think maybe Ril will work on Zenfone 2

nguyenhung9x said:
If you and I help each other build the android device, I think maybe Ril will work on Zenfone 2
Click to expand...
Click to collapse
Most of my development happens on telegram.
Let's get in touch there.
t.me/nutcasev1_5
There are 5 or 6 things to fix in the data structures & then some shimming to do.

@nguyenhung9x Based on 8.1? I'm gonna try it once I get my screen repaired.

error 11 and bootloop
just at the end in twrp it shows error 11 and when tried to reboot to system, it sends me to recovery

Development [TWRP Recovery] TWRP recovery for SM-F926B based on CVCA

Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)

So just push it as the recovery to the active slot via adb?

Breaks dex? If Not its kompatible with latest one ui?

It doesn't break dex, you can backup your recovery partition, it should be compatible with latest Android, since recovery is contained

Mikowitsch said:
So just push it as the recovery to the active slot via adb?
Click to expand...
Click to collapse
Yes, the usual way works fine

is the link down.. i cant download it

miman04 said:
is the link down.. i cant download it
Click to expand...
Click to collapse
Fixed !

Azkali said:
Fixed !
Click to expand...
Click to collapse
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?

miman04 said:
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
Click to expand...
Click to collapse
Yes in Odin putting recovery.tar in AP will work fine ^^

i cant download recovery and vbmeta

Azkali said:
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
Click to expand...
Click to collapse
404 page on TWRP and VBMETA

Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon

ROM-PacMe said:
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
Click to expand...
Click to collapse
I have a newer TWRP, maybe instead of a new build we could figure something out together
Join the discord and ping me there, I'll be available later

Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!

ROM-PacMe said:
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
Click to expand...
Click to collapse
is it compatible with SM-926B?
q2q is SM-926B?
google didnt know anything about "q2q samsung"

Can you try, If not working, only re install the recovery stock and vbmeta too

The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?

thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
the revision is a random number gived from Github Actions, nothing more my friend

thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
only use the vbmeta and recovery tar of my own github releases, let me any update, ok?
i see soon any bug to help to fix