[ROM][LineageOS][Android 8.1.0r52][OMS] TugaPower™ 30.0 - OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel

Build 16/12/2018 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower Oreo 8.1.0_r52 30.0 LineageOS #laos #OnePlus #OMS #SubstratumRootLess
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
Please be sure you are using one TWRP that can handle firmware flash and can decrypt sucessfull.
Your TWRP also need to be hable to mount and flash vendor partition.
Starting on O 25.0 the required firmware its 5.1.5 and is treblish, you need to have the vendor partition created, if you dont have you need to follow this steps:
Flash firmware 5.1.4 on TWRP
https://sourceforge.net/projects/ch...firmware/firmware_5.1.5_oneplus5.zip/download
Reboot TWRP
Flash firmware 5.1.5 on TWRP
https://sourceforge.net/projects/ch...firmware/firmware_5.1.5_oneplus5.zip/download
Reboot TWRP
Flash TugaPower O 26.0
Reboot phone
Relative to gapps, the advised ones is nano package ( ARM64):
http://opengapps.org/?api=8.1&variant=nano
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Full support to Substratum OMS RootLess without Andromeda
Powered by Magisk root v16.x
Direct unlock with face like OP5/OP5T OOS, credits to PixelExperience team
Safety Net checks patched to pass ( thanks to @Sultanxda )
Three fingers screenshot
WireGuard Support added
What does not works:
Let me know to add here
Changelog: TugaPower O 30.0
Magisk updated to latest canary version
Project name: proprietary_vendor_oneplus
msm8998: upgrade blobs from 5.1.7
Project name: android_device_oneplus_msm8998-common
msm8998: upgrade to 5.1.7
Project name: android_device_oneplus_cheeseburger
cheeseburger: update fingerprint
cheeseburger: require 5.1.7 firmware
Project name: android
manifest: android-8.1.0_r50 -> android-8.1.0_r52
Project name: android_frameworks_base
GlobalScreenshot: Fix screenshot not saved with some languages
ClipboardService: Restore different method calls to AppOps to fix PG
SystemUI: Clean duplicated CONFIGURE_WIFI_DISPLAY permission
Make adb use a custom prop for adb root
Rotation related corrections
Project name: android_packages_apps_Trebuchet
Trebuchet: move to default screen on home intent
Project name: android_packages_apps_SetupWizard
SetupWizard: fix SpannableString (Privacy Policy)
Project name: android_packages_apps_Settings
Make adb use a custom prop for adb root
Project name: android_packages_apps_LineageParts
PartsActivity: Prevent actionbar NPE
Project name: android_packages_apps_Messaging
Messaging: Add "Mark as read" quick action for message notifications
Allow intent shared subject or title to be mms subject
Project name: android_packages_apps_Bluetooth
Bluetooth: Clean duplicated READ_CONTACTS permission
Project name: android_packages_apps_LockClock
Release the wakelock before worker thread termination
Project name: android_packages_apps_Contacts
Project name: android_packages_apps_TvSettings
Make adb use a custom prop for adb root
Show Trust in security settings
Add button to shut down device
Project name: android_packages_apps_Exchange
Rename translations for new language code mapping
Project name: android_bootable_recovery
Fix making adb use a custom prop for adb root
Make adb use a custom prop for adb root
Project name: android_device_qcom_sepolicy
legacy: Resolve hal_gnss_default denial
Project name: android_device_lineage_sepolicy
common: Allow adbd to set a system_prop
Label lineage.service.adb.root as system prop
Project name: android_vendor_lineage
common: Allow custom vendor to override properties
Project name: android_hardware_qcom_power
power: Drop default POWER_HINT_INTERACTION routine
Project name: android_system_core
Make adb use a custom prop for adb root
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/OREO/TugaPowerO30_OP5.zip
MD5: cde6e88ef9d0bd947215e5b4f998288a
Please dont mirror for now the roms zips, thanks
Sources :
Rom:- https://github.com/LineageOS
Device:- https://github.com/LineageOS/android_device_oneplus_cheeseburger
Kernel:- https://github.com/LineageOS/android_kernel_oneplus_msm8998

Reserved for bug reports

Two thread! :/

Volte working?

ShiShTuBaBu said:
Two thread! :/
Click to expand...
Click to collapse
Where ?
Edit: See now, probably some bug on XDA creating the thread, asking to delete the other one
Cheers

G0dofWar said:
Volte working?
Click to expand...
Click to collapse
Dont have way to test because on my country ( France ) there is no network provider that uses VoLTE, try and let me know if is working.
If not working have few stuff to you guys to test if make it working.

danieldmm said:
Dont have way to test because on my country ( France ) there is no network provider that uses VoLTE, try and let me know if is working.
If not working have few stuff to you guys to test if make it working.
Click to expand...
Click to collapse
Downloading will report back!

This ROM is only for decripted device?

AleAndroid96 said:
This ROM is only for decripted device?
Click to expand...
Click to collapse
No, this rom works on encryption, assuming you current base is compatible, factory reset, flash rom, flash gapps, try to boot, if dont boot, remove the encryption and repeat the steps, after setting up phone it will be encrypted by default.

danieldmm said:
No, this rom works on encryption, assuming you current base is compatible, factory reset, flash rom, flash gapps, try to boot, if dont boot, remove the encryption and repeat the steps, after setting up phone it will be encrypted by default.
Click to expand...
Click to collapse
Thanks for the ROM, I will try on my decrypted device using noverity zip and report.

I'm on the encrypted RR 6.0, I did a factory reset, clean system, date and cache and flashed this rom with the gapps.
When the phone was restarted after the boot logo, the recovery started.

AleAndroid96 said:
I'm on the encrypted RR 6.0, I did a factory reset, clean system, date and cache and flashed this rom with the gapps.
When the phone was restarted after the boot logo, the recovery started.
Click to expand...
Click to collapse
And did you removed the encryption you have ?
Also prior to remove the encryption try again this, factory reset, flash rom, flash Gapps, factory reset again, then try to reboot the phone. If still a no go probably is the encryption you have the issue, remove encryption and repeat steps, then after setting up phone it will be encrypted by default.

To remove encryption I must format the sd from twrp, right?

To remove encryption I must format the sd from twrp, right?
Click to expand...
Click to collapse
Yes

OOSCAM with Portrait?

How I promise just flashed on my decrypted device with MicroG package with the unofficial installer (tried opengapps unofficial but setup crash), all seem working fine.
Thakyou very much for this great Rom

idelnon said:
OOSCAM with Portrait?
Click to expand...
Click to collapse
No portrait on OOS Cam except on one and only one custom rom as of now.

VampireHeart said:
How I promise just flashed on my decrypted device with MicroG package with the unofficial installer (tried opengapps unofficial but setup crash), all seem working fine.
Thakyou very much for this great Rom
Click to expand...
Click to collapse
Wich Gapps did you flashed? The Setup FC is probably issue with gapps package. But if you like MicroG just stick with it

danieldmm said:
Wich Gapps did you flashed? The Setup FC is probably issue with gapps package. But if you like MicroG just stick with it
Click to expand...
Click to collapse
I tried the nano gapps from the link in the op, rebooted but not solved so flashed microG.

VampireHeart said:
I tried the nano gapps from the link in the op, rebooted but not solved so flashed microG.
Click to expand...
Click to collapse
Like said before, if for you MicroG is good and you do not need of Gapps stick with that, if you need Gapps check the thread of gapps in OP and read last pages, they talk about setup fc and a fix is on the way.
Cheers

Related

[ROM][MASTER][6.0.1] AOSP Master Branch Built by Khaon

AOSP MASTER BRANCH FOR MANTA DEVICE
Hello everyone, you can download on XDA many good ROMS but each of them are based on "stable" android releases. That's why I chose to share something else.
I am offering a master branch build
Why use master branch ?
clang 3.8 | daily updates | java 1.8
instructions :
reboot to twrp recovery ( you can use mine if you want to use f2fs or having issues flashing my packages)
flasy my package
reset factory and IF YOU COME FROM ANOTHER DISTRIBUTION delete /sdcard/Android/data folder
flash gapps package ( I recommend opengapps)
reboot
I recommend people to factory reset time o time because of the master branch, it can be required to remove some bugs
What is not working/bugging for now
ROOT: latest supersu are patching the boot image and this doesn't work currently with my master branch releases. You need to use SuperSU v2.56
MXPlayer: for some reasons mxplayer doesn't find libcutils.so while it does exists. So for now, you gotta to use some alternatives: vlc, or what ever
Download link​
Sources
How to use AdwAway
In oder to get AdAway working you need to do the following:
1/ Set a file at
Code:
su/su.d
with the following content
Code:
mount -o bind /su/etc/hosts /system/etc/hosts;
2/ Make an empty host file at
Code:
/su/etc/hosts
I think you can find a working flashable package doing this on the unoffical adaway thred
XDA:DevDB Information
AOSP Master Branch for Manta, ROM for the Google Nexus 10
Contributors
Khaon
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2016-04-22
Created 2016-01-27
Last Updated 2016-04-21
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
PainToad said:
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
Click to expand...
Click to collapse
This is not 100% PURE aosp.
The base is aosp master branch. I have included some several extra such :
bootanimation
long press recent switches to latest app
led
...
Well nothing much.
The only critical thing I have touched is android permission : I override user's permission for google play service for the location permission access: otherwise it crashes.
I have uploaded a new build.
Too much changes to display here the changelog.
If you want extra tracking you should head here
To me, the main change, is clang prebult updated!
OP updated, root is now working.
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
ace9988 said:
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
Click to expand...
Click to collapse
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Khaon said:
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Click to expand...
Click to collapse
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
HmHm it is kinda late for me ( european timezone) but I have no issues using app requesting SU rights. I will take a look however at it tmr.
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
what opengapps version did you isntall ?
I am using pico, and I have no issue flashing it.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
How is your supersu status ?
I have no issue with su.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
I was reported an issue when formating to f2fs rebooting to the rom would format the userdata partition.
I investigated the AOSP code source and some commit format the partition if it fails mounting. Ofc trying to mount a f2fs partition with ext4 is considered as a fail...
Flashing my standalone kernel permit to pass that issue : my stand alone kernel will transform ext4 entries to f2fs(and vice versa) depending on the actual underlying fs.
The current release I am using features fixes for this, however, something broke the libsensors, so I need to find out what.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
Ewww, it should work ! Any other informations ? such logs ?
-----------------------------------------------------------------------------------------------------------------------------------------------------------
I am uploading a new build, I had issues for days with the builds.
Please tell me if you got bootloop on reboot. From what I saw bootloops do not longer exist.
I uploaded a new build.
It features master branch 02/21 with my latest kernel.
You just need latest opengapps for marshamallow and supersu 2.56.
Have fun.
All I see is one dated 2/5?
Sent from my Nexus 10 using XDA Free mobile app
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Der_Graf said:
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Click to expand...
Click to collapse
Grant play service the location permission and it will be fixed.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
I had this issue sometimes when installing the Rom and gapps in the same queue.. Installing the gapps seperatly afterwards worked then.. Try this out
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Der_Graf said:
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Click to expand...
Click to collapse
@Der_Graf
Hehe sorry for you this issue happens, the real culprit is Google. Since MM, the dev got to ask permission if not given. Google Play Frameworks/Service doesn't ask for this. So that's why you got FC. You should try after a Factory Rest- you need to that anyway when coming from another ROM- not installing Gapps in order to not have the first setup screen where you will get stuck because of the fc's spam.
Then Install gapps, and, since you will boot on the Home Screen, you should be able, with some pain, to get access to the app menu to get Location permission for Google Play Services.
Then, for any upgrade install, you won't have issues as the permission is already granted.
I know this sucks, but I tried to force give the permisison and it doesnt work :angry:
Ewwwww.
I wanted to share my latest build, as of the 25th feb, but NFC is broken and makes continuous FC'S, this appears also on my friend nexus 6's device, which is still supported by Google. So this is the bad news I've got to understand why this happens, well until Google fixes it or I find the culprit.
However, the good news is, that this friend, maintains more extra features then I do, so the next releases will feature more extra features

| ROM | LineageOS 14.1 | unofficial | 27/02/2017 | Signature Spoofing integrated |

Hello
I am going to release unofficial builds of LineageOS 14.1 for Wileyfox Crackling. The builds will be updated every month after a new security patch level is reached.
The build I made can be flashed on top of Cyanogenmod 13 build (with wiping dalvik and cache). It should work without any problems; I do not experience any.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
If it makes problems, wipe data/dalvik/cache and install again.
Besides that the ROM has two extra features:
I patched signature spoofing support into the ROM. Now it is possible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and will not affect the ROM in any way. It has to be enabled in the according settings.
Also, there's an option available to record calls now. Please respect the privacy of others.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-02-01.html"]February[/URL] | 2017-02-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170227-UNOFFICIAL-crackling.zip
Download:
Code:
[B][SIZE="2"]Openload.co:[/SIZE][/B]
https://openload.co/f/DBKYItUGllA/lineage-14.1-20170227-UNOFFICIAL-crackling.zip
https://openload.co/f/grRwId0HJJE/lineage-14.1-20170227-UNOFFICIAL-crackling.zip.md5sum
Alternativ:
[B][SIZE="2"]Free.fr:[/SIZE][/B]
http://dl.free.fr/uqIBAf8dM
The kernel and device sources I used to build the ROM can be found here:
Code:
https://github.com/lineageos
thomson.aa said:
Hello
This is my first build of LineageOS for Wileyfox Crackling.
I flashed it on top of my Cyanogenmod 13 build (with only wiping dalvik and cache) and it so far works without any problems.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
This release has the root access option disabled because LineageOS disables root for apps by default. It has to be enabled before building the rom - I didn't know that so I will provide an updated rom with root access for apps available.
Besides that the rom has one extra feature:
I patched signature spoofing support into the rom. Now it is possbible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and has to be enabled in the according settings.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-01-01.html"]January[/URL] | 2017-01-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Download:
Code:
https://openload.co/f/WCt_JxGZ-UE/lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Click to expand...
Click to collapse
Sorry thomson.aa sorry i do not have english my google translation. Work is very nice thanks one has a mistake sim card people do not see a way to solve it? I wish you continued success.
Where is the source ? You can't post this without kernel source
I dirty flashed this over crDroid and it seems to be working pretty well. Thanks.
All my app's (not many at the moment) were working fine.
Playstore thinks it's 'no carrier Wileyfox Wileyfox Swift'... but I guess that's better than 'Wileyfox Pixel XL' (crDroid).
On initial booting the status bar wouldn't pull down but works ok after a reboot.
Buttons were a bit messed up which only gave me a back button even though the usual defaults were all set. After deleting them and re-adding them they worked fine. I'm guessing this may be due to dirty flashing. Shame the button customisation is just as basic as cm13 especially after using crDroid.
Using Kernal Auditor Mod I see that the cpu only scales down to 800mhz and the gpu scales up to 400mhz. I don't know much about this but won't this make it a little power hungry?
Going through the settings, I'm thinking that LOS14 isn't quite as complete as the cm13 I was using a few weeks ago. Although I guess this is to be expected at this stage. And I'm used to the more versatile crDroid now so I'll be restoring that in a mo.
This MicroG project sounds great. It seems a bit complex to get it working as I'd like but I definitely be having a go when I get my head around it.
All in all, Great job. Keep up the good work... please. I'm already waiting for the next release.
Oh, and er... Surely you could find a better file host???
I tried to build the Image myself by using your other Thread's How-To and after flashing i had no WIFI.
Now i flashed this build and WIFI is also not working.
[Edit]
I've collected some Logs - perhaps they'll help.
[Edit2]
Now i tried another '14.1-ROM' and i've the same problem....
During all my Tests the shown MAC-Address during the 'inital install' was weird: 02:00:00:00:00:00.
Before the 14.1 Lineage i had the latest CMmod 13 running without any Problems :/
Ok - solved it....
I encrypted my Device during CM13 and always entered my Key during Boot/TWRP and Formatting/Installation of 14.1.
Now i *really* formated all the Data (and the former encryption), rebooted to Recovery and sideloaded the Image+Gapps.
Now WIFI is working.
How do I enable signature spoofing ? I can't find any relevant setting.
M.A.K said:
How do I enable signature spoofing ? I can't find any relevant setting.
Click to expand...
Click to collapse
Settings -> Apps -> Gear symbol -> App permissions -> Spoof package signature
No... it's not there for me.
M.A.K said:
No... it's not there for me.
Click to expand...
Click to collapse
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
fred0r said:
Now i *really* formated all the Data (and the former encryption)
Click to expand...
Click to collapse
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
thomson.aa said:
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
Click to expand...
Click to collapse
Ah, yes... got it now, thanks.
jobedius said:
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
Click to expand...
Click to collapse
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
update to official build?
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Nope, its not
Mithodin said:
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Click to expand...
Click to collapse
Twrp shows error 7(the data is incompatible). You need to wipe data, cache partitions and the system partition. Then install the zip with arm64 android 7.1 g-apps.
Cheers:good:
fred0r said:
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
Click to expand...
Click to collapse
Aahhh, that makes sense if you know it! Thanks!

[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!

[ROM] JAGUAR PIE OFFICIAL NON-TREBLE V6, updated August 7

Here is Jaguar Pie. In addition to familiar Pie features (all of them), you have:
Official Telegram Link: https://t.me/jaguar_Rom_Official
The main thing: Non-treble! So, your vendor is located in system partition, which is NOT available to the entire world, like in treble roms.
1. Hardened/fortified bionic (over 150 commits) to prevent bad behavior by system and third party apps
2. Most runtime processes are read only, which means they can't be exploited to take over the device. I am trying to attack the cause, rather than the symptoms (a specific exploit)
3. Many kernel security features activated, such as 'configuration_integrity', randomization; hardened user copy, etc. Impulse governor added
4. Yama security in kernel
5. Working msm hotplug, which actually plugs/unplugs CPU based on load
6. Wakelock blocker, Alarm blocker etc
7. Gestures, Omni Theming
8. Smart pixels
9. Offline charging
10. Utouch
11. AOD
12. No response to 'type zero' SMS
13. Boot time on a fully settled rom is about 4-5 seconds after Zuk logo
14. Qualcomm's boost framework
Many more features, which I am tired to list.
This is beta, because I don't have the device - relied on @Dr.07 @The.Night.King and @benedict97 - thanks for testing
INSTRUCTIONS:
1. Format System/Vendor (if you have it)/Data/Dalvik/Cache. If you are encrypted in Oreo or encrypted with FBE, you also need a format with factory reset to get rid of encryption. ALSO: FORMAT FACTORY partition, otherwise, you will have 2 sets of vendor blobs, which would create a mess on boot
2. Flash the rom, flash Gapps, reboot and let the rom run, then
3. Back to TWRP to flash Magisk (18.1 is working)
Rom download V1: https://forum.xda-developers.com/devdb/project/dl/?id=31427
This is the initial release. All future updates will be in post #3, as usual.
Credit: MrHacker (I used his device tree as a base) and many others who work on device tree and kernel and obviously AOSP, OMNI, DU, CopperheadOS, Carbon Rom, Xtended and Benzo
Also, credit for a Jaguar bootanimation to @Ashish9 and @The.Night.King who made a logo and header icon
If anyone is interested in Afwall with administrative option restored (app can't be uninstalled, unless confirmed by you): https://forum.xda-developers.com/attachment.php?attachmentid=4739733&d=1554836212
XDA:DevDB Information
[ROM] JAGUAR PIE NON-TREBLE 3.18 KERNEL OFFICIAL, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/optimumpr/kernel_zuk_msm8996
Sources for new (May 29) kernel: https://github.com/optimumpr/android_kernel_zuk_msm8996-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.1.x
Based On: AOSP, DU, Lineage
Version Information
Status: Beta
Current Beta Version: V1
Beta Release Date: 2019-04-05
Created 2019-04-05
Last Updated 2019-08-07
Screenshots
Some screenshots:
Updates in this post
Those who are coming from treble roms: you need to format Factory partition too, otherwise, you will have 2 sets of vendor blobs, in other words, MESS
August 7. New release.
1. August security patches
2. Google r46
3. Camera should have level 3 now + more
Dirty flashing is fine, if on the previous release. Otherwise, clean flash - wipe Vendor/Factory/System/Data/Cache/Dalvik
Download rom V6: https://forum.xda-developers.com/devdb/project/dl/?id=31753
July 30: New release V5.2 with fixed installation problems:
You could try dirty flash, but I installed clean, then flashed Opengapps, and Firefox installed without any problems, while it didn't on V5.1.
Download rom V5.2: https://forum.xda-developers.com/devdb/project/dl/?id=31733
July 27. New release, v5.1.
This will fix encryption.
The reason it didn't work was the official TWRP. The maintainer (a known pro) put in the wrong size of userdata partition. So, if you ever formatted data on official TWRP, especially with factory reset, your data partition is screwed for the purposes of encryption (no place for crypto footer). I had to install another version of TWRP, and after I did format there, encryption worked. So, I am attaching both the rom and unofficial TWRP by handibuddy. This is also a signed version (as well as the rom itself), so you can re-lock bootloader on this rom: I have been doing this for ages and long before Lineage came up with the idea (you can check my signing guide in Oneplus 5 thread).
Download Rom V5.1: https://forum.xda-developers.com/devdb/project/dl/?id=31727
Download signed TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=31728
Instructions: Rom could be flashed dirty over V5. TWRP could be flashed as image (to recovery) in your existing TWRP or via fastboot.
Just remember, if you want to relock bootloader, encrypt after locking.
July 25. New release, v5
1. July security patches
2. New Night Screen with configurable tint and brightness
3. Support for level 6-6.2 for AVC codecs
4. Option to disable proximity sensor during calls
5. In-CallUi is now themeable
6. Aggressive battery saving mode
7. Latest Lawnchair
Clean flash is required over V4 or if coming from a different rom, in which case you will also need to format vendor or factory partition.
DO NOT ENCRYPT YET!
Instructions:
1. Dirty flash, if already on Jaguar Pie
2. Clean flash, If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Download rom V5: https://forum.xda-developers.com/devdb/project/dl/?id=31725
________________________________________________________________________________________________________
June 6. New release, V4:
1. June security patches
2. Pie r41
Dirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
ps, reboot, then back to TWRP to flash Magisk
Download rom V4: https://forum.xda-developers.com/devdb/project/dl/?id=31621
______________________________________________________________________________________________________________________
June 2. Lawnchair update to the latest. Flash in TWRP.
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4770317&d=1559500522
May 31. Rom updated, V3:
1. Major kernel improvements - there is no reason to use my Oreo kernel or any other kernel
2. Flashlight works regardless of 'always on' or 'ambient display' (that required a clean flash)
Instructions:
1. Clean flash recommended - wipe system/data/cache/dalvik
2. If coming from a different rom, also format vendor/factory
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
Download rom V3: https://forum.xda-developers.com/devdb/project/dl/?id=31612
_____________________________________________________________________________________________________________________
May 30. This is an updated version of the new kernel I posted earlier. This one contains my commits + reversed 'power saving' commits. Sometimes, you get things better by reversing.
Unzip, put on internal SD and flash either with TWRP (as image onto boot partition) or via fastboot.
Download new kernel: https://forum.xda-developers.com/attachment.php?attachmentid=4768179&d=1559177914
May 28. Lawnchair update. Flash in recovery:
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4767269&d=1559060237
May 27. Updated release:
1. Fixed toggling flashlight in ambient display
2. Improvements in Qualcomm's boostframework
3. Contactsprovider updated (disappearing contacts)
Could be dirty flashed over V2. Otherwise, clean flash.
Download rom V2.1: https://forum.xda-developers.com/devdb/project/dl/?id=31602
May 25. New release, V2:
1. May security patches
2. Android Pie r37
3. Big changes in frameworks: exec spawning function is severely restricted to all apps, i.e., only one instance is allowed
4. Most resources preloading for exec spawning is disabled. As a result, boot time is shorter, fewer background resources are loaded in ram, which translates into an overall smoother experience.
5. Aggressive battery saving
6. Status bar burn protection
7. Media cover art filter (on lockscreen)
8. Switched to Bromite system webview V74
9. Redone auto-brightness and ambient display: ZukDoze removed, as Customdoze and Amibientdisplay are now builtin (Settings/Display)
10. Lawnchair upgraded: many fixes including Pie recents
11. MusicFX/Equalizer is now themeable
12. Zukparts removed, as spectrum profiles simply don't work, and KCAL could be done via Kernel Adiutor
13. Battery icon Q style
14. Wifi randomization working (Developer Settings)
15. Captive portal detection toggle (Settings/Wifi/Advanced - disable network connectivity check). You can now uninstall Captiveportal and have no 'x' in Wifi and Mobile icons
Instructions:
1. Clean flash required
2. Format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps or Nano Gaps, reboot. Then back to TWRP and flash Magisk
If your provider's APN is not on the list, set it up and enable. If data doesn't work, then change CDMA subscription in Mobile network to the alternative.
Download rom V2: https://forum.xda-developers.com/devdb/project/dl/?id=31591
__________________________________________________________________________________________________________________
April 9. New release. Lots of changes, mostly in kernel:
1. Inteli-thermal
2. Thermal-engine ported from Jaguar Oreo, so the rom runs about 3 degrees cooler
3. Substantially improved fluidity: according to testers, virtually no lag
Instructions:
1 If on a previous release, flash dirty and wipe dalvik/cache
2. if new, format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps, reboot. Then back to TWRP and flash Magisk
Download rom V1.1: https://forum.xda-developers.com/devdb/project/dl/?id=31467
_____________________________________________________________________________________________________________________
April 5. Here is the first update, kernel only. Speed improvement.
Just flash boot.img on top of the first release.
Download kernel: https://androidfilehost.com/?fid=1395089523397933955
Finally ?
@optimumpro Thank you. Respect?
Thanks for the work! ?
Woh!!!!...... Waiting for a detailed review by someone.....
Wow finally
vinay069 said:
Woh!!!!...... Waiting for a detailed review by someone.....
Click to expand...
Click to collapse
your prediction turned out pretty accurate about the release date lol
All right, boys and girls. First update: kernel only - speed improvement . Download (in post #3) and flash on top of the first release
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
GopalKaul said:
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
Click to expand...
Click to collapse
Screenshots posted. Stereo sound - not yet.
optimumpro said:
Screenshots posted. Stereo sound - not yet.
Click to expand...
Click to collapse
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Shubhi singhal said:
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Click to expand...
Click to collapse
Just flash rom
The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Kernel only.
venom0207 said:
Just flash rom
Click to expand...
Click to collapse
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
@optimumpro animations r fekked
Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
It is non treble, factory or vendor have nothing to do with it, you can straight away flash the rom
Flashed the ROM.
It took a lot of time to boot.
Swipe up home screen is not showing any options
Recents is not pie recents
Very fast ROM
In some themes, the notifications are invisible

GSIs fixed builds for hi6250 (emui8)

Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01
6 hrs SoT
Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.
thanks.. any build for havoc 2.9 ?
How can I remove the bottom pad that appears when I want to use the keyboard?
itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture
Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Achieve is currupt :-/
i get Error while flashing image, here is the log
Erro 255
I get error while flashing image here is the log
I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX

Categories

Resources