{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the Latin word for peace and Pax, the roman goddess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
Other than previously provided ROMs, this is using the "normal" method of providing a flashable zip.
You should start off with the latest OxygenOS on both slots and then proceed to flash Carbon.
You must at least use TWRP 3.4.0-1 by @mauronofrio to flash this.
Download the ROM and optionally GApps, reboot to TWRP.
Flash the ROM
Reboot recovery (to switch between slots)
Flash GApps (optional)
Format /data*
Done
*As TWRP is currently unable to format /data you can use fastboot to format
Code:
fastboot -w
It appears that fastboot on Windows has issues with the wipe command. In that case use both of the following commands
Code:
fastboot erase userdata
fastboot erase metadata
Download
Download Mirror
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the OnePlus 8 Pro
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2020-06-26
Last Updated 2020-10-13
Perks of flashing ROMs at 5AM, FIRST!!
Wow! Another rom awesome job!
let the ROMs start yeahhh
More roms!!! Yaaas
If coming by from another rom, do I just format data first and then flash Carbon or should I reflash OOS on both slots again?
@Myself5, you say to reboot twrp in between for flashing gapps to another partition. Do I read it right? Or do we need to flash the rom again to another partition after rebooting twrp
zanderzone said:
@Myself5, you say to reboot twrp in between for flashing gapps to another partition. Do I read it right? Or do we need to flash the rom again to another partition after rebooting twrp
Click to expand...
Click to collapse
Only reboot in recovery to change slot, and then flash gapps
---------- Post added at 07:57 AM ---------- Previous post was at 07:56 AM ----------
Gordietm said:
If coming by from another rom, do I just format data first and then flash Carbon or should I reflash OOS on both slots again?
Click to expand...
Click to collapse
I am always doing both ..just to be sure and to eliminate bugs
great work!
We dont need to format user data if you are on OOS do you?
Please do look into adding more space for GAPPs as I prefer to use mini
does oneplus 8 work?
so for me this doesnt work and i dunno what i am doing wrong.
flashed oos to both slots, flashed your twrp, flashed rom, reboot to recovery and device doesnt decrypt so no gapps to install. booting up ends in sticking at carbon boot logo.
Hey ! Do you add face unlock ??
I updated the flashing instruction in OP to reflect on various ways to format /data as TWRP is currently not able to do so.
You can either use fastboot to format
fastboot -w
Click to expand...
Click to collapse
or if that fails (which has been reported of being an issue with fastboot on Windows) flash THIS userdata.img using
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
EDIT: As of TWRP 3.4.0-1 by @mauronofrio you can flash Carbon with that just fine.
I discovered Bluetooth is broken in yesterdays build. This has been fixed in CARBON-CR-8.0-PAX-UNOFFICIAL-instantnoodlep-20200627-1418 which has just been uploaded.
Note: During the tests today I noticed that GApps seems to be finniky when updating. When I flashed Gapps I sometimes ended up in a bootloop because some parts of GApps were missing despite them flashing successfully in TWRP. Force rebooting and flashing them again fixed that. It is yet to be determined if this is a ROM or a TWRP issue but I am working with @mauronofrio on fixing the issue.
Myself5 said:
I discovered Bluetooth is broken in yesterdays build. This has been fixed in CARBON-CR-8.0-PAX-UNOFFICIAL-instantnoodlep-20200627-1418 which has just been uploaded.
Note: During the tests today I noticed that GApps seems to be finniky when updating. When I flashed Gapps I sometimes ended up in a bootloop because some parts of GApps were missing despite them flashing successfully in TWRP. Force rebooting and flashing them again fixed that. It is yet to be determined if this is a ROM or a TWRP issue but I am working with @mauronofrio on fixing the issue.
Click to expand...
Click to collapse
I noticed on yesterday's build gapps never installed I didn't retry them and wifi would not stay on but I'll try again today if I don't end up in crash dump again lol
---------- Post added at 12:15 AM ---------- Previous post was at 12:12 AM ----------
musicman5844 said:
I noticed on yesterday's build gapps never installed I didn't retry them and wifi would not stay on but I'll try again today if I don't end up in crash dump again lol
Click to expand...
Click to collapse
Do we need the installer one more question after flashing the build do we flash the installer and reboot to recovery and flash gapps on other slot
musicman5844 said:
I noticed on yesterday's build gapps never installed I didn't retry them and wifi would not stay on but I'll try again today if I don't end up in crash dump again lol
---------- Post added at 12:15 AM ---------- Previous post was at 12:12 AM ----------
Do we need the installer one more question after flashing the build do we flash the installer and reboot to recovery and flash gapps on other slot
Click to expand...
Click to collapse
About gapps issues, dev is working on it.. hopefully ,new build with fix will be out soon
marko94 said:
About gapps issues, dev is working on it.. hopefully ,new build with fix will be out soon
Click to expand...
Click to collapse
Well I'm on latest build and latest gapps nano from opengapps.org and everything is good
musicman5844 said:
Well I'm on latest build and latest gapps nano from opengapps.org and everything is good
Click to expand...
Click to collapse
I know..problem is when you doing update
marko94 said:
I know..problem is when you doing update
Click to expand...
Click to collapse
Ohhh I see . That's my next question when updating ( the process )? Is it flash build , flash installer ,reboot to recovery, flash gapps magisk reboot system ,,,,, are is it different
musicman5844 said:
Ohhh I see . That's my next question when updating ( the process )? Is it flash build , flash installer ,reboot to recovery, flash gapps magisk reboot system ,,,,, are is it different
Click to expand...
Click to collapse
reboot to twrp, flash carbon, reboot recovery, flash gapps etc
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM for Essential PH-1 8.1, ROM for the Essential Phone
Contributors
Somcom3X, f100cleveland, frap129
Source Code: http://github.com/carbonrom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Running stock firmware from 8.0 minimum
Based On: AOSP
Version Information
Status: Nightly
Created 2018-04-11
Last Updated 2018-04-13
Reserved
Steps to flash carbon:
Flash twrp to your current boot partition via fastboot in the bootloader.
Boot into recovery
Flash Carbon
Reboot back into bootloader, then go into recovery
Flash gapps
Reboot
This is great. Thank you
screenshot
here is a screeny
@Somcom3X thanks for this! ?
Does this ROM include an updater?
yep
Obamaloominaty said:
Does this ROM include an updater?
Click to expand...
Click to collapse
yep
drherdman said:
yep
Click to expand...
Click to collapse
You'll still have to manually flash the update, it reboots to recovery
Which gapps are you guys using? I flashed nano opengapps to the opposite slot, but they don't show up when I reboot.
I used this version
fossiltkm said:
Which gapps are you guys using? I flashed nano opengapps to the opposite slot, but they don't show up when I reboot.
Click to expand...
Click to collapse
https://mirror.myself5.de/taimen/GApps/
drherdman said:
https://mirror.myself5.de/taimen/GApps/
Click to expand...
Click to collapse
Took your advice with the carbon gapps, but I'm getting could not mount system error even though system is mounted through twrp. Anyone else run into this issue?
Got this from R3belle
i would go to stock then follow the directions below
1. Flash TWRP
2. In TWRP flash Carbon
3. Boot Carbon
4. Chek the Slot you are on
5. Flash TWRP too the Other slot
6. In TWRP flash Gapps then boot.img
7. Reboot
8. I did an Factory reset then from the rom
i don't know if you need that? but after that you get the setup.
drherdman said:
i would go to stock then follow the directions below
1. Flash TWRP
2. In TWRP flash Carbon
3. Boot Carbon
4. Chek the Slot you are on
5. Flash TWRP too the Other slot
6. In TWRP flash Gapps then boot.img
7. Reboot
8. I did an Factory reset then from the rom
i don't know if you need that? but after that you get the setup.
Click to expand...
Click to collapse
how do i change slots?
techfreak243 said:
how do i change slots?
Click to expand...
Click to collapse
fastboot set_active other
or
IH8TouchWiz said:
fastboot set_active other
Click to expand...
Click to collapse
or in twrp home click reboot, and you can see which one you are on and change there.
drherdman said:
or in twrp home click reboot, and you can see which one you are on and change there.
Click to expand...
Click to collapse
Do you recommend flashing stock to both slots as stated in the OP?
If you run the flashall.bat it will flash both slots
Amazing! Thank you. I'll flash it now and report back.
Edit-Camera seems to crash.
rydyd said:
Amazing! Thank you. I'll flash it now and report back.
Edit-Camera seems to crash.
Click to expand...
Click to collapse
Yep, still working on getting this fixed. Seems to be a selinux denial but I have not had a chance to make sure.
drherdman said:
i would go to stock then follow the directions below
1. Flash TWRP
2. In TWRP flash Carbon
3. Boot Carbon
4. Chek the Slot you are on
5. Flash TWRP too the Other slot
6. In TWRP flash Gapps then boot.img
7. Reboot
8. I did an Factory reset then from the rom
i don't know if you need that? but after that you get the setup.
Click to expand...
Click to collapse
Do you flash the April boot.img?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Also does any build from now on require a vendor partition, by doing this you will lose the ability to flash official builds provided by ZTE. Any failure in this process of flashing or repartitioning could lead to an unrecoverable bricked device.
What's not working:
SELinux is permissive
Instructions:
Attention! The bootloader needs to be unlocked!
Attention! You'll need a vendor partition!
1. Install the Universal bootloader and your model specific modem. Download
2. Flash vendor creation tool. Download (unnecessary, if done already)
* On first flash the device will reboot, just reboot to recovery and reflash the zip.
3. Update your version of TWRP. Download
4. Perform a backup of your current ROM. (optional)
5. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
6. Install the ROM. Download
7. Install GApps. (optional) [Recommended -> Open GApps (arm64) (9.0)]
8. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev
Source Code: https://github.com/OrdenKrieger/android_kernel_zte_msm8996
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Testing
Created 2018-08-19
Last Updated 2019-07-28
Some features of LineageOS are missing, but they will be merged in future builds.
Some features may or may not work, sometimes also differently. Feel free to ask
any question.
UwU neat p finally
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Predatorhaze said:
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Click to expand...
Click to collapse
Read the instructions, they are there for a reason.
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
Los 15 is abandoned I assume?
And 16 besides nfc and volte is functional?
Thanks for contributing.
wow. It is all happening very fast.
Thanks
OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important.You also say its optional to wipe system data cache if come from other rom,but in fact its REQUIRED to wipe system data if you come from other rom
Click to expand...
Click to collapse
GApps is always optional because some people want them and some don't. If you read carefully, on LOS 15.1 is the same.
I have heard Android Pie got GAPPS inbuild and i believe that because google dont want microg users.So its not true...
Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Click to expand...
Click to collapse
Why should I mention other stuff if I already provide a working bootstack. Why would I give a download link for Gapps and add the the optionally tag, if they would be build in.
thnx @OrdenKrieger and all others involved :good:
Nice build - working smooth, no lag
DT2W ok
Used bitgapps as a starter
At last NO echo and incall volume adjustable
FP working
Hotspot OK
camera pics ok, recording crashes when saving - on both pics and video lag on movement
usb preferences work
afaik there is no way in settings to reverse softkeys so i used mine : https://androidfilehost.com/?fid=3700668719832237510 (be sure to be rooted and mount system/vendor)
Notifications work - on lockscreen and leds ok
EDIT : after testing a bit, definitely more heating and i mean a lot, more cpu load (f.e. as on the PPR1 img )..... could not stabilize temp on cpu 92C ! Only after applying powersave in EXKM...definitely something to look into (only Wifi on, no BT, no specific apps running....only the basic stuff to test your build )
EDIT2 : fast charging way more heat on battery - also battery drain too fast even with no cpu load
Will test further
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
2000impreza said:
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
Click to expand...
Click to collapse
yep, tried recording now and crashes when saving. Also lag on movement.
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Hellsbend said:
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Click to expand...
Click to collapse
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
ttkian said:
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
Click to expand...
Click to collapse
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Hellsbend said:
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Click to expand...
Click to collapse
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Edit
Of course, it's easier to flash because Post 1,2 and 3 are "included" now.
So it's quicker to flash.
Hellsbend said:
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Click to expand...
Click to collapse
Not quite. Mine was derived from Redmi Note 4. It looks the same for sure but devs have done some adjustments as to ECHO, dt2w working, notifications, ....
BUT my LOS16 build had no heating, nice CPU load and no battery drain and no heating when charging at all but had the annoying echo as we know it on other gsi builds and no dt2w, no notifications working on lockscreen, no led...
So there are definitely pros from this build and pros from mine.
Hope they can manage heating.
Also back on AEX as the heating (in my case) was too heavy. Dont want to ruin anything now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Liquid Remix! Liquid Remix is a new ROM of today, and I'm bringing it to everyone! I hope everyone in the ZTE Axon 7 community can enjoy this ROM to it's max!
Liquid Remix is a New age mix of all the best ROMs of today with added essence from the older days. Android 9.0 project based from the old lead dev of Liquid smooth, Liquid0624, along with VenkatVV, and community contributors! All features are open source and will stay that way as the community is the most important thing to our project!
Our Android Development Team is very end user oriented; we care about what you want and bringing it to you. We do as much as we can to keep our users happy while primarily focusing the aims on stability, speed, optimizations, other additions and features that complement the ROMs as well as some frequently requested user add-ons.
Code:
/*
* 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.
*/
[/CENTER]
Even though the ROM is tested beforehand, I cannot guarantee anything that may happen to your device. I am not responsible for anything that happens to your device.
ROM - DownloadOpen Gapps - Download
Clean flash is recommended:
Unlock the Bootloader first , and flash universial bootstack and modem before anything
1. Go to TWRP
2. Wipe System, Vendor, Data, Cache, and Dalvik Cache. Internal Storage wipe is not needed
3. Flash Kranoner's vendor or Nfound vendor (Recommended vendor) or flash another vendor of your choice. LineageOS vendor and anything based on LineageOS, like DotOS vendor will not work.
4. Extract the ROM .zip file to get system.img , flash it in system partition. , Boot and check the ROM
5. Reboot to recovery after flashing ROM and then Factory reset then flash Opengapps. Nano or below is recommended
6. Reboot to system
7. After first boot, you will need to flash NFC/Hotspot fix by @raystef66 and @kountry83 .
8. DONE! Enjoy!
ROM - LiquidRemix
Device Tree - Phh Device
Google (for AOSP)
Lineage OS (Rom Base)
@phhusson for his great work in treble development.
@yshalsager for his treble build guide.
@Unjustified Dev
@DrakenFX
@Kranoner & @NFound
special thanks for all testers in Axon7 TG group
XDAevDB Information
Unofficial LiquidRemix, GSI for ZTE Axon 7
ROM OS Version
ROM : 10.0.5
Security Patch : 5 FEB.
Status:Unofficial
Created 2018-12-11
Last Updated 2019-2-15
ComboFix that will flash NFC/Button Swap/overlay fix/magisk in one go
Aroma Combo Fix
Thanks to @raystef66
What doesn't work/bugs:
Navigation Gesture
Network Traffic will reboot system UI / crash settings but the chosen option will be applied
VOLTE , WFC
maybe other custom settings ?
What works:
- Pretty much everything else
changelog:
14-2-2019
12-1-2019
22-12-2018
FAQ
Why GSI not a normal ROM ?
- The sources are still not available/stable so the only way to get new Pie ROMs for our device is by using GSI.
TWRP says no OS after flashing system.img ?
-Thats normal , just reboot and it should boot
Phone shows the following message after every reboot "Internal problem detected..."
-That's a vendor issue, it does not do anything just press OK.
Screen freeze or unresponsive ?
-Flash the NFC/Hotspot fix.
Which vendor is recommended ?
- NFound v1.1 has less amount of issues.
Some customization options does not work ?
-Restart system UI and/or Reboot system.
Themes are broken (Dark/Black) ?
- wipe clean everything (including vendor) and use NFound vendor , follow the instructions.
Substratum does not work ?
- use this apk key and install it as normal apk
Option XYZ does not work ?
- Post your setup with detailed description and of course a LOG.
I want XYZ feature ?
- I'm only a builder not a dev, so no promises.
How stable is this ROM ?
- the ROM is very stable and can be used as daily driver.
Very interested in this ROM, will try it out
Thanks for your great efforts, buddy.
I am going to try it out.
Which universial bootstack do you recommend?
Can you kindly make a link to it?
Thanks in advance.
samichiban said:
Thanks for your great efforts, buddy.
I am going to try it out.
Which universial bootstack do you recommend?
Can you kindly make a link to it?
Thanks in advance.
Click to expand...
Click to collapse
use this one here https://androidfilehost.com/?fid=11410932744536985259
anyway if you are in official LOS15.1and its working fine you don't need to flash bootstack/modem , just follow the instructions and it should boot fine
NOTE : WIPE THE VENDOR & FLASH ANOTHER ONE OTHER WISE IT WONT BOOT.
Nice!
Glad that my guide helped
king1990 said:
use this one here https://androidfilehost.com/?fid=11410932744536985259
anyway if you are in official LOS15.1and its working fine you don't need to flash bootstack/modem , just follow the instructions and it should boot fine
NOTE : WIPE THE VENDOR & FLASH ANOTHER ONE OTHER WISE IT WONT BOOT.
Click to expand...
Click to collapse
Thanks for quick reply, king1990. Much appreciated.
My mobile is Axon7G model, and ATM Nfound's AospExtended ROM v5.8 (Rom 8.1) running.
Your ROM zip title indicates A-only but will it work fine with my Axon7G?
yshalsager said:
Nice!
Glad that my guide helped
Click to expand...
Click to collapse
Your guide was huge help , without it this ROM would never happen
samichiban said:
Thanks for quick reply, king1990. Much appreciated.
My mobile is Axon7G model, and atm Nfound's AospExtended ROM v5.8 (Rom 8.1) installed.
Your ROM zip title indicates A-only but will it work fine with my Axon7G?
Click to expand...
Click to collapse
Flash LOS15.1 and it should create vendor partition to allow you to install this ROM
it will work in both G & U models
You post a GSI in axon 7 forums,why if i may ask? This is a GSI for treble A phones,i think this should be in the treble forums only?
Predatorhaze said:
You post a GSI in axon 7 forums,why if i may ask? This is a GSI for treble A phones,i think this should be in the treble forums only
I was happy when i saw LiquidRemix,the happynes didnt last long when ive read GSI
Click to expand...
Click to collapse
Those of us who initially tested this GSI did not think it was ready for other devices outside of the Axon 7 community, as it will not boot on LOS based vendors. @king1990 built this for our community, and it was just way too good of a ROM to keep from sharing on XDA.
Once again, thanks for your opinion. /S
EBeatFLA said:
Those of us who initially tested this GSI did not think it was ready for other devices, as it will not boot on LOS based vendors. @king1990 built this for our Axon 7 community, and it was just way too good of a ROM to keep from sharing on XDA.
Once again, thanks for sharing your opinion. /S
Click to expand...
Click to collapse
My opinion is that this is a GSI for a treble devices,so thats why i thought this should be in the treble forum.
And yes im avoiding treble system for my axon 7 because its a mess.
My opinion is this ROM is hands down, THE best GSI I've used in all of my testing, and by a long shot. Seeing as how this is only the first build, I'm excited to see how future builds will improve.
The difference between using this ROM with it's suggested installation, and other ROMs of the past is like night and day, including pre-treble ROMs. This is definitely the whole package when it comes to custom ROMs. Full of options, that work, and a UI that flies with no lag, without compromising battery life.
See screenshots of estimated 6 hours SOT, almost 2 hours of which I was on a Viber phone call through Bluetooth headphones while at the same time using my phone to message on Telegram.
Where others came up short, Liquid Remix just works. I'm sure there will be many other posts like mine, giving praises to this ROM. @king1990 Thank you again, so much for building this for us. It was a much needed relief from many headaches of searching and testing and fixes and testing... Lol
XDA only rendering 1 of 2 screenshots. Here is the second one.
Followed the installation guide:
Clean flash is recommended:
Unlock the Bootloader first , and flash universial bootstack and modem before anything
1. Go to TWRP
2. Wipe System, Vendor, Data, Cache, and Dalvik Cache. Internal Storage wipe is not needed
3. Flash Kranoner's vendor (Recommended vendor) or Nfound vendor or flash another vendor of your choice. LineageOS vendor and anything based on LineageOS, like DotOS vendor will not work.
4. Extract the ROM .zip file to get system.img , flash it in system partition. , Boot and check the ROM
5. Reboot to recovery after flashing ROM and then Factory reset then flash Opengapps. Nano or below is recommended
6. Reboot to system
7. After first boot, you will need to flash NFC/Hotspot fix by @raystef66 and @kountry83 .
8. Install Magisk 18.0
However, every time boots into system, it shows error:
Android System
There's internal problem with your device. Contact your manufacturer for details.
Does it mean Vendor Partition is not right?
ccfly888 said:
However, every time boots into system, it shows error:
Android System
There's internal problem with your device. Contact your manufacturer for details.
Does it mean Vendor Partition is not right?
Click to expand...
Click to collapse
This is a false error, and is very common when using a GSI. There is nothing wrong and it affects nothing. It is a minor annoyance to click OK, only on boot.
Sometimes this will go away depending on what vendor or kernel you are using. Hopefully it may go away in the future with a better vendor or if a future Liquid build works with other vendors.
ccfly888 said:
Followed the installation guide:
Clean flash is recommended:
Unlock the Bootloader first , and flash universial bootstack and modem before anything
1. Go to TWRP
2. Wipe System, Vendor, Data, Cache, and Dalvik Cache. Internal Storage wipe is not needed
3. Flash Kranoner's vendor (Recommended vendor) or Nfound vendor or flash another vendor of your choice. LineageOS vendor and anything based on LineageOS, like DotOS vendor will not work.
4. Extract the ROM .zip file to get system.img , flash it in system partition. , Boot and check the ROM
5. Reboot to recovery after flashing ROM and then Factory reset then flash Opengapps. Nano or below is recommended
6. Reboot to system
7. After first boot, you will need to flash NFC/Hotspot fix by @raystef66 and @kountry83 .
8. Install Magisk 18.0
However, every time boots into system, it shows error:
Android System
There's internal problem with your device. Contact your manufacturer for details.
Does it mean Vendor Partition is not right?
Click to expand...
Click to collapse
Ignore it! It's nothing serious. And yes it's the vendors fault. Our vendor is a mess!
EBeatFLA said:
This is a false error, and is very common when using a GSI. There is nothing wrong and it affects nothing. It is a minor annoyance to click OK, only on first boot.
Sometimes this will go away depending on what vendor or kernel you are using. Hopefully it may go away in the future with a better vendor or future GSI build.
Click to expand...
Click to collapse
Thanks for the quick reply.
Indeed, I clicked OK and it just moves on. But it shows up on every reboot. Kind of annoying.
ccfly888 said:
Thanks for the quick reply.
Indeed, I clicked OK and it just moves on. But it shows up on every reboot. Kind of annoying.
Click to expand...
Click to collapse
Sorry, bad wording, i should have said "on boot", not "on first boot". You get used to it.
EBeatFLA said:
Sorry, bad wording, i should have said "on boot", not "on first boot". You get used to it.
Click to expand...
Click to collapse
It is minor issue. I certainly can live with that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We’re really excited to announce the release of Paranoid Android Pie betas.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. For those who are unfamiliar, Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhances the overall user experience.
The beta builds include adjustments and improvements on top of the stock Android CAF base. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features.
Device-specific issues
- "Fingerprint Hardware Not Available" can occur
Note: Custom kernels are NOT supported!
Download
Get the latest Essential PH-1 build HERE.
Changelogs
Keep an eye on our Twitter account, @paranoidaospa , as we will be posting about new features getting included in the beta builds.
Paranoid Android Pie beta released
Instructions & requirements
- TWRP recovery image released by dees_troy doesn’t have touch support. To get around this, do
`adb shell twrp decrypt "YOUR PASSCODE"` if applicable
`adb push ROMNAME.zip /sdcard/Download`
`adb shell twrp install /sdcard/Download/ROMNAME.zip`
- After TWRP indicates its done flashing (using the TWRP installer):
`adb reboot`
Important / Useful links
OpenGapps
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Help us improve PA by submitting good bug reports possibly with a log attached. Learn how to take logs here.
Our device maintainers for Essential PH-1 @Newtsrock, having @ggpew2 as a device contributor. Mention (@) them if you need some assistance and/or when reporting bugs.
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android, ROM for the Essential Phone
Contributors
herna, newtsrock, ggpew2
Source Code: https://github.com/StatiXOS/android_kernel_essential_msm8998
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-01-09
Last Updated 2019-02-22
Reserved
Reserved!
Reserved!
Reserved!
This is awesome! I first used PA back when it's biggest feature was navbar and status bar colors. Super excited to be downloading it now.
Is twrp not working due to the official release that hasn't been updated?
Anyone have screenshots?
Is there a reason for fastboot w? Is this rom currently decrypted?
Awesome. I do have one correction, though: most recent TWRP builds DO have touch support, mainly if it's installed via the flashable zip OR with the patched boot img for stock. Just figured I'd mention that.
dragynbane222 said:
Awesome. I do have one correction, though: most recent TWRP builds DO have touch support, mainly if it's installed via the flashable zip OR with the patched boot img for stock. Just figured I'd mention that.
Click to expand...
Click to collapse
Could you provide an link to the patched boot image? I never brought the twrp touchscreen to life when I tried using it from pie
the_Pan said:
Could you provide an link to the patched boot image? I never brought the twrp touchscreen to life when I tried using it from pie
Click to expand...
Click to collapse
Here is a link to the latest patched boot image: https://drive.google.com/file/d/1wMiQ1M_2ib9kMVpC1X7j7HdbR4MXhOJ9/view
Source: https://www.reddit.com/r/essential/...date_root_and_twrp/?utm_source=reddit-android
Looks like there's a bootloop issue installing magisk and flashing twrp from the installer zip to both partitions, anyone else have this issue?
Edit: Looks like after installing the ROM - it overwrites the recovery flash from the above-patched twrp (Jan-Patch from Reddit source), it then just forces the boot to hang.
Edit 2:Looks like I got it to work, after installing the ROM, reboot back into recovery mode, flash the jan-patch twrp img again using fastboot.
Edit 3: Nope looks like a persistent bootloop. Gonna leave this ROM alone until it gets magisk and a proper TWRP fixed
prozo said:
Looks like there's a bootloop issue installing magisk and flashing twrp from the installer zip to both partitions, anyone else have this issue?
Edit: Looks like after installing the ROM - it overwrites the recovery flash from the above-patched twrp (Jan-Patch from Reddit source), it then just forces the boot to hang.
Edit 2:Looks like I got it to work, after installing the ROM, reboot back into recovery mode, flash the jan-patch twrp img again using fastboot.
Edit 3: Nope looks like a persistent bootloop. Gonna leave this ROM alone until it gets magisk and a proper TWRP fixed
Click to expand...
Click to collapse
Looks like the boot loop issue is occurring on both this ROM and the AOSIP ROM, leads me to believe this might be an issue with the patched TWRP possibly?
Anybody able to get this working with gapps? If I flash the rom it boots fine. If I flash twrp with it, it boots fine. But once I try to flash gapps it just hangs on the aospa boot animation
I tried with opengapps pico and nano as well as simplegapps
prozo said:
Looks like the boot loop issue is occurring on both this ROM and the AOSIP ROM, leads me to believe this might be an issue with the patched TWRP possibly?
Click to expand...
Click to collapse
I'm running aosip rom at the moment. I use the twrp installer each and every time I flash something. In the same session
uodii said:
Anybody able to get this working with gapps? If I flash the rom it boots fine. If I flash twrp with it, it boots fine. But once I try to flash gapps it just hangs on the aospa boot animation
I tried with opengapps pico and nano as well as simplegapps
Click to expand...
Click to collapse
Same issue here, can't install it without getting the hang
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
Bobbaloo said:
I'm running aosip rom at the moment. I use the twrp installer each and every time I flash something. In the same session
Click to expand...
Click to collapse
Are we talking about the same thing? The patch image in this thread or the original TWRP img from the original TWRP website?
After installing I can no longer access adb or fastboot commands, tried multiple devices, they all still detect my V40 in ADB but not the PH-1, any idea why?
Thanks for the ROM all wok good
This is how I install it
Flash ROM from twrp
Flash twrp installer
Reboot to twrp
Flash magisk
Reboot to system
Reboot to twrp
Flash gapps (micro)
Done
English not my first language
the_Pan said:
Could you provide an link to the patched boot image? I never brought the twrp touchscreen to life when I tried using it from pie
Click to expand...
Click to collapse
Here you go: https://drive.google.com/file/d/1wMiQ1M_2ib9kMVpC1X7j7HdbR4MXhOJ9/view?usp=sharing
The folks on Reddit usually make a patched stock boot image front the stock not image for each month within a week of release
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom rom based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel source
What's working:
Boots
RIL (Call, msg)
Wi-Fi
Bluetooth
Camera
Camcorder
Fingerprint
Video Playback
Audio
Sensors
Flash
LED
GPS
Encryption
Volte
Known Issues:
You tell me
Latest Downloads:
Aosip Server
Credit/Thanks:
Mike Williams(founder and creator of AOSiP)
Google
Dirty Unicorns
Ground Zero ROMs
AICP
ABC Rom
Screwd
Omni
Krexus
Cyanogenmod
LineageOS
SlimRoms
ChainFire (SuperSU)
Beanstown106
mTresk
nathanchance
Cory Collins
Sultanxda
flar2
francisofranco
---------
Any others i may have forgotten(sorry, please pm me)
All our testers
XDA:DevDB Information
[ROM][10][Official]Android Open Source Illusion Project[Fajita], ROM for the OnePlus 6T
Contributors
edi194, anirudhgupta109
ROM OS Version: Android 10
Version Information
Status: Testing
Created 2020-01-17
Last Updated 2020-05-06
Reserved
INSTALLATION PROCEDURE:
MAKE SURE YOU'RE ON THE LATEST STABLE FIRMWARE FROM HERE (10.3.0)
DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP6T!!!!!
1. If you're coming from another ROM or need to perform a clean flash:
Boot into TWRP
MAKE SURE YOU'RE USING ONLY TWRP
Flash 10.3.0 in TWRP
Flash TWRP Installer
Reboot to recovery
Flash 10.3.0 in TWRP again to make sure its on both slots
Flash TWRP Installer
Reboot to recovery
Flash ROM (link in first post)
Wipe Data and Cache
Flash TWRP Installer
Reboot to Recovery
Flash OpenGApps (link in OP)
Flash ONLY the latest Magisk
Any mods you want to flash (I won't be supporting Custom Kernels or Xposed)
Enjoy
2. If you're updating the ROM:
a. Via the inbuilt Updater
When you get a notification of new build available, tap it
Tap Download
Wait for Download
Tap the three dots>preferences>enable "Install updates faster"
Tap install
Wait for install
Tap reboot
Enjoy!!
b. via TWRP
Flash Substratum rescue zip if you have a theme applied
Flash ROM
Flash TWRP Installer
Reboot to recovery
Flash OpenGApps
Flash Magisk
Reboot
Enjoy
NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).
Reserved
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your OOS base versions in reports. (Eg: 9.0.8, OB17 etc.)
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
FREQUENTLY ASKED QUESTIONS:
Q: Which TWRP do I use?
A: Use only latest TWRP from HERE
Q: Which GApps do I use?
A: I recommened OpenGApps. Any Android 10 compatible GApps should work but I will only be answering to issues where OpenGApps is used.
Q: Do I have to wipe data if coming from another ROM?
A: Yes, I will not be providing help/support to users that haven't wiped data when coming from another ROM.
Q: How often will I be getting updates?
A: The plan is for weeklies, if unavoidable circumstances come up, please don't spam the thread. I will release a build as soon as one is ready.
Q: Does VoLTE/VoWiFi work?
A: Yes, I have tested on Jio in India and it does work. VoWiFi seems to be broken based on the 2 reports I've had, I can't test this personally since India doesn't have this feature.
Q: I ended up on CrashDump mode, how do I get back to my system?
A: Theres a valuable thread HERE which can help restoring your system, you WILL LOSE ALL DATA and I will not be blamed under any circumstances.
Q: Is the ROM official?
A: The ROM is an early Alpha build, I am the Official maintainer for OP6T AOSiP but the ROM is too early in the cycle right now for it to be tagged as Official.
Q: I use Telegram, where can I find help on that platform?
A: There is a common AOSiP Group Chat for all devices, the link is HERE
Q: Does SafteyNet pass and is the SELinux Enforcing?
A: Yes, SafteyNet does pass with Magisk and SELinux is Enforcing.
Q: What OOS Base firmware do I use?
A: OOS 10.3.0 is the recommended base firmware right now.
Q: I'm having high idle drain, please fix.
A: I'll need more data from you to figure it out, Install BetterBatteryStats and let me know about what it tells you after 3-4 charge cycles. Please do not report issues when having apps like Greenify, Naptime, Wakelock blocker etc.
Q: My phone is stuck on the "Bootloader is unlocked" warning page, why isn't my system booting?
A: Since there are a bunch of scripts being executed when the device is sent a power on signal, it might take some time to boot. Don't panic, your system will boot fine after some time. All builds are personally tested by me and a few testers.
Q: When I'm updating via OTA in the Updater, do I have to reflash GApps and Magisk? Will TWRP stay after I update?
A: When updating via OTA, GApps and Magisk will remain intact. Have a look in /system/addon.d/. Anything that is present inside that folder will stay after the update.
TWRP will not stay since A/B devices don't have a recovery partition for it to actually stay. You will be reverted to the stock recovery.[/QUOTE]
Installation steps please...??
Downloading now I will report any issues that I experience.. Thank you for all your hard work.
---------- Post added at 05:16 PM ---------- Previous post was at 05:16 PM ----------
nikz106 said:
Installation steps please...??
Click to expand...
Click to collapse
Steps are in op
cdnsnOw said:
Downloading now I will report any issues that I experience.. Thank you for all your hard work.
---------- Post added at 05:16 PM ---------- Previous post was at 05:16 PM ----------
Steps are in op
Click to expand...
Click to collapse
I commented within few seconds the developers opened the thread.. he was updating the posts that time.. guess I was too early.. :silly:
nikz106 said:
I commented within few seconds the developers opened the thread.. he was updating the posts that time.. guess I was too early.. :silly:
Click to expand...
Click to collapse
Lol. Let me know if you need any help. Enjoy the rom
Heyyyll Yeah, best friggin Rom on the 6T now comes with Android 10! You Sir or Sirs' or Ma'ams' are da sheet
Downloaded installed booted up first time. Everything seems to working great so far. no issues no random reboots running smooth. will let you know if something comes up.
Anyone kind enough to pop up some screenshots please? ?
Sent from my OnePlus6T using XDA Labs
There you go..
Since this is based on ob17 then maybe Verizon should work?
Heres a couple
Magisk ?
Latest stable or canary?
cultofluna said:
Magisk ?
Latest stable or canary?
Click to expand...
Click to collapse
I am running the latest stable version seems to be working great so far..
cdnsnOw said:
Heres a couple
Click to expand...
Click to collapse
Fresh install? Or did you upgrade from AOSiP 9.0?
nikz106 said:
There you go..
Click to expand...
Click to collapse
If I'm already on open beta 17 do I still need to factory reset on TWRP and follow method 1? Our can I flash directly over beta 17? And what is the difference between twro.img and the twrp installer.zip? Why needed to flash installer zip if TWRP is already my custom recovery? Not too clear on that..I know I lose root when I do flash that zip. Thx in advance! ?
itsdan313 said:
Since this is based on ob17 then maybe Verizon should work?
Click to expand...
Click to collapse
Verizon works great. Think you will enjoy it
SubwayJrd said:
Fresh install? Or did you upgrade from AOSiP 9.0?
Click to expand...
Click to collapse
I did a fresh install
Known issues says you tell me, does that mean the FOD works? Considering the nature of these ROMs and the FOD, I figured I'd ask