Warning: This is an untested unoffical build for the Pixel 3 (blueline), so please take caution in flashing and make a backup.
{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
I am not a developer, I only build this ROM and it reflects the the current status of LineageOS / Resurrection Remix. If there are any device specific things missing or not working. I suggest to contact the LineageOS team, they are the real developers here and deserve all the credits.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process, so make sure you make a backup if needed.
In order to make the right startbase for the ROM you have to install the latest stock Pixel 3 image from Google found here.
Place the ROM and optionally the TWRP zip, a kernel and root on the phone and reboot to recovery by using the command line (fastboot boot twrp.img) or hold the VOL DOWN key while rebooting the phone.
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe or use the slider in TWRP for a factory reset. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip, kernel and root and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM on the phone and reboot or fastboot flash to the TWRP recovery
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when Resurrection Remix has also adapted to the latest monthly sources, you will have to do an extra step:
Download the latest Resurrection Remix ROM and place it on the internal storage
Download the latest image from the Google Factory Images site, extract the bootloader, radio and vendor images and flash them in the bootloader to both slots
From here go to TWRP recovery and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
ROM Download
GApps are already included in the ROM
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
- Active Edge
- Now playing
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
turbolukex5 said:
Warning..
Click to expand...
Click to collapse
Is this ROM featuring OpenGapps, like the unofficial LineageOS 16.0 build(s) does?
xFirefly93 said:
Is this ROM featuring OpenGapps, like the unofficial LineageOS 16.0 build(s) does?
Click to expand...
Click to collapse
It features the gapps that come with the Dirty Unicorns ROM.
So excited to finally see RR on my pixel 3. Been a long wait
Thank you ?
Hey, your instructions confused me a little. Do we need to flash our own kernel of choice, or can we stick to the kernel that comes with the ROM?
retr0gr4d3 said:
Hey, your instructions confused me a little. Do we need to flash our own kernel of choice, or can we stick to the kernel that comes with the ROM?
Click to expand...
Click to collapse
You can do both.
I flashed your rom yesterday but got stuck on the bootscreen logo. I let it sit for 15 minutes & nothing.
Spider_Pig27 said:
I flashed your rom yesterday but got stuck on the bootscreen logo. I let it sit for 15 minutes & nothing.
Click to expand...
Click to collapse
This is the exact issue I had, which is why I asked about the kernel situation. It seems like people have had success, however I don't know whether those people flashed this build or not.
The instructions aren't exactly crystal clear.
retr0gr4d3 said:
This is the exact issue I had, which is why I asked about the kernel situation. It seems like people have had success, however I don't know whether those people flashed this build or not.
The instructions aren't exactly crystal clear.
Click to expand...
Click to collapse
I flashed it with a custom kernel & still didn't boot for me. I flashed it like I've been flashing other rooms. Didn't really do anything different or special with this one.
All is running well for most trying it out and that's why it is so quiet ??
Doesn't work, installed latest factory image, installed the ROM, TWRP, and Magisk (no custom kernel). Image fails to boot, stuck at boot image for about 10 minutes and then it kicks me back out to TWRP.
I'm also stuck on the start screen with the loading icon. Just installed RR and TWRP, nothing too special. Everything went perfectly until I attempted to boot. Is there anything I'm missing?
Sad to report same issue here..
To everyone with boot issues: please keep in mind that this is still an experimental built, bugs are to be expected. If you are able to pull some adb logs from the bootloop and post it here, the dev might actually be able to fix those nasty bootloops. This way, you can actually participate in the development process to make this ROM acessible for other members.
Portgas D. Ace said:
To everyone with boot issues: please keep in mind that this is still an experimental built, bugs are to be expected. If you are able to pull some adb logs from the bootloop and post it here, the dev might actually be able to fix those nasty bootloops. This way, you can actually participate in the development process to make this ROM acessible for other members.
Click to expand...
Click to collapse
I haven't tried this one yet but had the same problem in LineageOS. Stuck in the bootscreen. Not sure what it is.
Did the updates and development for blueline just stop with this. I cannot for the life of me find an update version of this.
eezdva said:
I haven't tried this one yet but had the same problem in LineageOS. Stuck in the bootscreen. Not sure what it is.
Click to expand...
Click to collapse
tjcalhoun1221 1 said:
Did the updates and development for blueline just stop with this. I cannot for the life of me find an update version of this.
Click to expand...
Click to collapse
I know the dev, he doesn't know how to fix this.
However, you can flash the RR 7.x.x GSI if you want. I'll leave detailed steps.
Do not I am not some sort of Pixel dev. I did these steps myself with help from a friend in the Proton Kernel team.
1) Boot to your TWRP
2) Flash avbctdisable.zip. It acts like a dm-verity disable afaik, however I can't remember where I found it. I think it's on the internet, I'll edit when I find it, or if I post it myself.
3) Boot to fastboot
4) Flash the stock boot.img from the latest P OTA (fastboot flash boot boot.img)
5) Flash your GSI (fastboot flash system system.img)
6) Flash TWRP temporarily (fastboot boot twrp.img)
7) Wipe your /data (wipe > advanced wipe > data > type "yes") but do NOT reboot yet
8) Flash TWRP installer (blueline/crosshatch respectively, then reboot back to TWRP)
9) Flash your GApps, Magisk and/or kernel
9.1) If this doesn't work (/system isn't big enough) then put "resize2fs /dev/block/by-name/system$(getprop ro.boot.slot_suffix)" into adb shell. It will make /system bigger for GApps.
10) Reboot and you should have RR 7.x.x GSI working.
Related
Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"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:
/*
* 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.
*/
About Carbon ROM :
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.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
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.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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. Any bug not reported in the bug report format above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17
Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2
mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi
Excellent work. What would you say are the main differences between Carbon and Lineage?
sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------
New build is up.
Changelog in post 2.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.
I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.
One button navigation
Is one button navigation still not working on this rom?
superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: https://www.androidfilehost.com/?w=files&flid=274850
Official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
select ARM + Android Oreo 8.1 here: https://opengapps.org/
- SELinux is permissive
- The current builds are "incompatible" with some apps in the Play Store > You can download the last build without this issue here
You tell
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Sources:
Kernel source
Device tree
Vendor tree
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
@deadman96385
@Galaxy-MSM8916 team
@elginsk8r
ROM OS Version: 8.1.0 Oreo
Kernel: Linux 3.10.x
Version Information:
Status: NIGHTLY
Release Date: 25-6-2018
You want to see a "normal" night at the "DEV office", click here!!
Can it be installed on t555?
Mihai14 said:
Can it be installed on t555?
Click to expand...
Click to collapse
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.
virsys said:
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.
Click to expand...
Click to collapse
I don't really care about ril but it just doesn't boot. Like the other roms and i just can't find the problem. Lineage os 14.1 should boot on t555 too but without ril and it ij stuck in the boot logo refusing to boot into /system.
Mihai14 said:
it just doesn't boot.
Click to expand...
Click to collapse
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?
virsys said:
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?
Click to expand...
Click to collapse
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data
Mihai14 said:
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data
Click to expand...
Click to collapse
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.
virsys said:
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.
Click to expand...
Click to collapse
Of course i would want to help. I can PM you my telegram.
Hi all,
I tested the ROM on SM-T550 and it boots quiet well.
Initial google (nano opengapps) setup was broken for me, but the setup
via "Google app" and my phone worked.
Another thing is that when installing a browser it
crashes right after starting it.
Opera says that I have no space free
Chrome says something like an unexpected error.
Buildin browser just appears short and closes immediately.
The game little wars and Netflix app shows the same behaviour.
So right now I can't use the ROM but I am very Happy that this device is not abandoned!
Thank you for your work and if I can help testing, just drop me a line.
I have SM-T550
Its great ROM, but.. Problem, has error browser, for example: I can't open Google chrome, opera, ... Pls fix? You are the best! ??
Ok so apparently it boots but the screen is always black. I just found a screenshot i've taken accidentally after i flashed the rom and it seems to boot.
ramaxcalmax said:
Another thing is that when installing a browser it
crashes right after starting it.
Click to expand...
Click to collapse
Thanks for your report. The latest build should work.
My Model: SM-T550
I have one problem... The ROM is great working with all browser (Google Chrome, Opera, ...) Very Good.
But... Please you read.
- It's very laggy the security (for example: PIN, password and Sequence). I'm ready PIN, it's fine.
When my tablet is lock PIN (Off). I'm watching TV or other. My tablet lets off 1 hour. After, I go my tablet open "On" it's very laggy and PIN too, all..
I hope you understanding? I'm a deaf, sorry!
I'm fighting against selinux right now. I'll update the build soon, thanks for your hint.
I think I found why the screen is not working on t555: might be because of a problem in the kernel. More precise the dt. You can use the kernel from the stock firmware as base to fix this. Also for the ril take look at samsung galaxy j5 2015/2016 sources. They have the same chip as t555/t550. Especially the 2016 version as it have almost the same base firmware (7.1.1).
Mihai14 said:
You can use the kernel from the stock firmware as base to fix this.
Click to expand...
Click to collapse
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.
virsys said:
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.
Click to expand...
Click to collapse
I would but my laptop is quite s**t. I have tried to build roms before but ot was a fail.
Thanks for keeping this device relevant. Working great!
Could this be ported to the 8" variant SM- T350 ? We have no Oreo development
vin_001 said:
We have no Oreo development
Click to expand...
Click to collapse
That's not true.
There's oreo development.
{
"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:
/*
* 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.
*/
What is ProjectTitanium?"ProjectTitanium is an GZOSP-Based-Custom Aftermarket Firmware Distribution for Android Devices. Our Goal is to Deliver Performance with many Features, Security, Cleanliness, and good Battery Life, Trying to make Something Unique than any other Android ROM. We Hope That you'll Love our Work, and help us in Making it even Better in the Future.
Features:Work In Progress
Featured Stuffs:
- TiPapers
- About ProjectTitanium
-WIP
And many more being added regulary! *soon
Installation:Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest ProjectTitanium ROM & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ProjectTitanium ROM
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
Downloads:A/B: PTi-Beta-0.5-GSI-ARM64-AB-OFFICIAL(update 02/07/2019)
Only A: PTi-Beta-0.5-GSI-ARM64-A-OFFICIAL (update 02/07/2019)
GApps
Source Code:ProjectTitanium
Credits:
-@XTutorials(Founder/Lead Developer)
-@DarkJoker360(Co-Founder/Lead Developer)
-@Thespartann(Senior Developer)
-@K3RN3L_P4N1C(Web Developer)
- Phhusson for Treble trees
- LineageOS
- GZOSP
REPORTING BUGS/PROBLEMS!
As soon as the problem occurs, feel free to tell me or, if possible, send me a logcat and I'll see what I can do!
Have a feature request? Don't spam here. Visit our Telegram group!
ProjectTitanium Official Website:
ProjectTitanium
ProjectTitanium Official Telegram group:
Telegram
Support us!
Hello, Gracious human! if you like our work, you may support us by donating:
PayPal
Note
This ROM is in Beta state for now, I uploaded it here mainly for testing purposes(not that it can't be used as a daily ROM, it can actually, it just doesn't have all the things the final 1.0 will have.
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Mohammed779 said:
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Click to expand...
Click to collapse
Ah, damn. Let me see what I can do. Thanks for the report.
Could you give me any log?
Mohammed779 said:
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Click to expand...
Click to collapse
Same issue for same device.....
I will test it on s9+ and let u know if it boots or no
Update coming this night fixing hopefully all boot issues, even though on some devices it boots...
Regards,
ARM 64 A Only build boots fine on ZTE Axon 7. I had a quick browse through Settings, seems very barebones. I don't blame ya, you said yourself it's in beta. I'll keep an eye out for when you've had a chance to update it
Booted on s9+ but the rom is like stock aosp no features or anything, maybe because it is still on beta
Update 02/07/2019!
Good Evening! I'm back as I said, and here is the update for this ROM.
Changelog:
-Boot issues fixed!
-Vendor fixed!
-New stock wallpaper
-Fixed build number bug
-Other miscellaneous fixes
Download:Only A:
PTi-Beta-0.5-GSI-ARM64-A-OFFICIAL
A/B:
PTi-Beta-0.5-GSI-ARM64-AB-OFFICIAL
Best Regards!
A/B Build added to the update reply, now since the builds should work our team is going to start working on actually bringing features to this.
Hopefully sooner than you think.
Regards,
Akhayev said:
Booted on s9+ but the rom is like stock aosp no features or anything, maybe because it is still on beta
Click to expand...
Click to collapse
Would you please tell the Firmware and Vendor you are on . Thank you !
fares70 said:
Would you please tell the Firmware and Vendor you are on . Thank you !
Click to expand...
Click to collapse
Brk3 vendor , and firmware use the one u already using ,
XTutorials said:
A/B Build added to the update reply, now since the builds should work our team is going to start working on actually bringing features to this.
Hopefully sooner than you think.
Regards,
Click to expand...
Click to collapse
Do you mean this ROM is intended to be feature-rich like Havoc, Liquid, PixelDust...?
Boots on Blu Vivo XI.
Hello Goodnight.
I previously installed GSI roms.
but now I try to install with the usual procedure
for my G9600 S9
but I can not get into the system
it always stays in the logo and never passes from there.
I already wait more than 25 minutes and nothing.
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
Unpack it if it wasn't in .IMG format
Wipe DATA, and reboot in TWRP
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Install the kernel for GSI GSI Kernels
In TWRP mount System, then go to ADVANDED, File Manager, and delete this file: system/bin/rw_system.sh
Reboot system
What is wrong?
Technical said:
Do you mean this ROM is intended to be feature-rich like Havoc, Liquid, PixelDust...?
Click to expand...
Click to collapse
Well, we want to make something different from any other ROM, but yes, it will also have plenty of features enough to satisfy everyone, hopefully also reaching my intentions. We intent of bringing 1.0 this fall.
Regards,
hi Guys
I can not install a gapps twrp error 70 otherwise rome runs well and as always with my asus zenfone 5 ze620kl automatic brightness does not work ..
can you please build a rome with gapps.
Thank you
XTutorials said:
Well, we want to make something different from any other ROM
Click to expand...
Click to collapse
What do you mean?
Until May I was able to compile Bootleggers, Havoc and Liquid. Since then, sepolicy and other specific issues are blocking building or booting later. I like featured rich ROMs and I could help to compile Titanium, although my knowledge is not enough to help you, devs.
---------- Post added at 08:19 ---------- Previous post was at 08:14 ----------
barbaross said:
hi Guys
I can not install a gapps twrp error 70
Click to expand...
Click to collapse
In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again.
Technical said:
What do you mean?
Until May I was able to compile Bootleggers, Havoc and Liquid. Since then, sepolicy and other specific issues are blocking building or booting later. I like featured rich ROMs and I could help to compile Titanium, although my knowledge is not enough to help you, devs.
Click to expand...
Click to collapse
Well, this ROM can be build as any other ROM, so anyone with some Linux knowledge should be able to build this, as any other ROM.
And soon accepting official maintenance!
mezacorleehone said:
Hello Goodnight.
I previously installed GSI roms.
but now I try to install with the usual procedure
for my G9600 S9
but I can not get into the system
it always stays in the logo and never passes from there.
I already wait more than 25 minutes and nothing.
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
Unpack it if it wasn't in .IMG format
Wipe DATA, and reboot in TWRP
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Install the kernel for GSI GSI Kernels
In TWRP mount System, then go to ADVANDED, File Manager, and delete this file: system/bin/rw_system.sh
Reboot system
What is wrong?
Click to expand...
Click to collapse
First you need BRK3 vendor , and flash aosp kernel not gsi , the best kernel is Endurance-Kernel-AOSP-1.2.30.zip
First, wipe system data cache and then flash vendor then flash the rom then flash kernel the magisk then reboot ot will work fine , no need to delete rw_system or anything
{
"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"
}
Resurrection Remix Q
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.
*/
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Download Resurrection Remix AP tar & the latest GApps package
Boot into download mode
Flash the provided file as AP in Odin
Turn off the device
Boot to your recovery by pressing power key + volume up
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 5 minutes.
ROM Download (With OrangeFox Recovery built by me)
ROM Download (With TWRP built by Magendanz)
GApps
Resurrection Remix Source
GSI
Magendanz ~ Device tree for recovery & vendor image to make GSI useable for the machine
phhusson ~ Maintaining the treble repositories
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
you can create this rom for sm-t580 this rom is fluid And it is very customizable
Chris_0147 said:
you can create this rom for sm-t580 this rom is fluid And it is very customizable
Click to expand...
Click to collapse
I don't have that device, searched out multiple places and their is no publicly available specifications on it (not even GSI)
I was hoping this ROM would have support for exFat on the SD card, but no such luck. Still have to flash the Xfinity kernel to get exFat.
Very nice ROM build! No issues so far... root an custom kernel installed. This is the ROM i've wanted since day one of having this tablet. Tried many but none of them are nearly as good as this one. THANK YOU
Thank you so much! This is still one of my favorite ROMs.
Im new to rooting. Ive looked through tutorials and before I proceed. My android tab 10.1 has android version 10. All the root files ive seen none of them match the build number I have on the tablet. Is this a whole new OS of sorts? So no matter the build my android is showing, I can still install this.
watts320 said:
Im new to rooting. Ive looked through tutorials and before I proceed. My android tab 10.1 has android version 10. All the root files ive seen none of them match the build number I have on the tablet. Is this a whole new OS of sorts? So no matter the build my android is showing, I can still install this.
Click to expand...
Click to collapse
This is GSI, so this does not depend on any version specific kernels
You can backup important things first before flashing, then download stock ROMs in case things really went wrong
This build does not come with root, you can follow Magisk guides for flashing root
will this ROM get OTA updates for future builds ?
memleketim05 said:
will this ROM get OTA updates for future builds ?
Click to expand...
Click to collapse
I do have plans on making this official, but for OTA, since this is a GSI build, there might be difficulties, however updates will get posted here constantly, so subscrible to the thread if you want manual OTA for now
Allready subscribed
Also looking forward to Android 11 from you for this device
memleketim05 said:
Allready subscribed
Also looking forward to Android 11 from you for this device
Click to expand...
Click to collapse
The RR team has been working on Android 11 for what I heard of, I will build it as soon as a some what stable one comes out
RobotHanzo said:
The RR team has been working on Android 11 for what I heard of, I will build it as soon as a some what stable one comes out
Click to expand...
Click to collapse
Anybody working on exFat support?
lewmur said:
Anybody working on exFat support?
Click to expand...
Click to collapse
Not sure
Follow the instructions but the can't install gapps and the system will not boot.
Update: Got it to boot by manually flashing the img files in TWRP.
Hi, nice to see a RR ROM on the 510 but how do you install a tar file with twrp, it takes only zips ?
Imagitom said:
Hi, nice to see a RR ROM on the 510 but how do you install a tar file with twrp, it takes only zips ?
Click to expand...
Click to collapse
Flashed my device yesterday.
The Custom Recovery is included in the rom. The Orange Fox Recovery is great so far and based on TWRP 3.5.0. So can recommend the Rom woth Orange Fox.
You have to open the .tar file in Odin as AP.
@RobotHanzo
I found out that the automatic adjustment for the brightness doesn't work.
Also it would be great if you could write in your first post which version the ROM is based on so we can see if there are updates in future.
The header says 8.6.4 but the ROM is 8.6.5.
Imagitom said:
Hi, nice to see a RR ROM on the 510 but how do you install a tar file with twrp, it takes only zips ?
Click to expand...
Click to collapse
For this, since its a GSI, you don't have to install the zip if you have already patched the vendor images, if you haven't, go find Magendanz's builds like his Nexus rom and flash it
Next, download the rom and extract the files using software like 7zip or winrar
Send the system.img you get from the extraction process to your tablet and flash as system image, you should get a working system
memleketim05 said:
Flashed my device yesterday.
The Custom Recovery is included in the rom. The Orange Fox Recovery is great so far and based on TWRP 3.5.0. So can recommend the Rom woth Orange Fox.
You have to open the .tar file in Odin as AP.
@RobotHanzo
I found out that the automatic adjustment for the brightness doesn't work.
Also it would be great if you could write in your first post which version the ROM is based on so we can see if there are updates in future.
The header says 8.6.4 but the ROM is 8.6.5.
Click to expand...
Click to collapse
Actually the first build is on 8.6.5 but I mistyped lol
For the light adjustment part, it seems like another generic samsung problem thats caused by using camera as the light sensor, you can try to follow the issue here https://github.com/phhusson/treble_experimentations/issues/1468 and see if theres any future responses from that
Thanks for bringing this RR rom. Previously I was using a different RR GSI. Does it have smaller recent preview? Cuz the big recent apps looks awkward on a tab. Moreover there is this brightness bug where on very low brightness the screen looks like it is turned off! And please can you make the rom in compressed format like .xz, would be a great help to this wandering soul, as it eats less data.
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.
@Subinsmani
@rahul9999
@@ki
@Shreejoy Dash
@kvijaya
@AxelBlaz3
@Psycho-Mods
@aswin_a_s
@Gero
@melvingarcia
Support Us if you like our work
Got an issue or suggestion? Reach us at
Telegram: https://telegram.me/pixysos_chat
Phone calls & messaging
Wi-Fi & Mobile data
VoLTE (but no icon in statusbar)
Fast charging
Dark theme, night mode
Fingerprint sensor
Face unlock
NFC
FM Radio
Wireless Bluetooth audio with AptX codec
and much more...
Less customizations but more stability...
Pixys: PixysOS
Pixys Device Sources: PixysOSDevices
NOTE: It is recommended to update your stock ROM to Android 10 before flashing this custom ROM.
IMPORTANT: If you want to use GAPPS build, it is necessary to resize system and vendor partition on your phone before flashing rom! This step will perform format of system and vendor partition and even userdata partition so make a backup if you don't want to lose your data!
If you downloaded VANILLA build, you can skip this step and if you want then you can flash gapps of your choice.
Please download this nice and user friendly Nokia Repartition Tool brought to you by Raghu Varma and look at this instructional video:
Just use the first option "3.5G S - 1G V" - it is enough for this rom.
NOTE: After resize your phone will be automatically booted to TWRP, but because this tool is intended for Nokia 6.1 Plus, this TWRP will refuse to flash ROM zip on 6.1. In this case just reboot to bootloader and download this TWRP for our Nokia 6.1, boot it and everything will be fine. Now you can begin flashing.
After booting to TWRP:
1) If you just resized your system and vendor partitions using Nokia Repartition Tool then you have already formatted userdata so you can skip this step, otherwise if you want to do a clean flash then please Format Data by typing yes, then go to the Bootloader and reboot TWRP. (For dirty flash use adb sideload method because TWRP can not decrypt Android 12 userdata partition.)
2) Flash latest ROM zip via TWRP
3) Switch to alternative slot (if you are on slot a switch to b if you are on b switch to a)
4) Reboot system
Now you are done!
SafetyNet on latest PixysOS builds passes out of the box, so you won't need root/Magisk anymore. Flash Magisk only in case that you really need to root your device.
ROM: Sourceforge download linkAt the download page, you can choose GAPPS build (with Google play store and other apps included) or VANILLA build, which contains only basic apps without Google play store (in this case you can flash gapps of your choice).
Wi-Fi Hotspot works only without password. FIXED
Custom statusbar icon pack is reverted back to default after device reboot.
Credits:
- Google for AOSP
- Dirty Unicorns
- Pixel experience
- AOSP extended
- LineageOS
- Superior OS
- Statix OS
- YAAP
- Krypton AOSP
- Project-Kaleidoscope
- AICP & POSP Team for thread template idea
- Also many pro developers who all help us to bring this rom to you...
- Please let us know if we forgot to mention your name in credits...
Contributors:
Big thanks to LineageOS developers and maintainers for Nokia 6.1 device and vendor tree on which this build is based!
Since PixysOS v5.1.5 thanks to Raghu Varma Android developer for new Nokia 6.1 device tree + vendor and kernel sources!
Kernel source:
https://github.com/LineageOS/android_kernel_nokia_sdm660
Kernel source since PixysOS v5.1.5:
https://github.com/RaghuVarma331/android_kernel_nokia_sdm660/tree/android-12.0-gcc
ROM OS Version: 12.1
ROM Kernel: 4.4.x
Based On: AOSP
Version Information
Status: Stable
Current Version: v5.1.5
Hey, really appreciate your work!) Specific bug for your rom is inability to setup magisk, because stock rom recovery "Failed to clear BCB message" error, adb sideload method doesn't works in it too. If i flash boot TWRP, then I can't boot rom, it stucks on boot logo. General bugs for all roms, such as hanging vibration (12.1 bug), gcam, that after some time of use can't take photos are here. Again. thanks for your work!!
Hi, thanks for your reply! Magisk works on this ROM, I just tested the version 24.3.
You need to boot into TWRP (twrp-3.4.0-0-PL2_sprout-11.0-20200909.img), select adb sideload option and flash latest Magisk zip. Then reboot and check the magisk app. Now you are successfully rooted. ;-)
Note: If you are installing Magisk right after flashing rom, don't forget to switch slot first!
I tried to install magisk right after I installed rom. For example now I am on a slot B, rom is installed on slot A. Magisk would setup on current slot, not as rom, that would setup on inactive slot -> I need go to the A slot to setup magisk. If I try to do that through stock rom recovery on slot A, I get error, because ADB sideload isn't working. If I try to "fastboot flash "twrp"" on slot A, then I can install magisk, but I am stuck on the rom boot logo. If I try to use twrp install.zip file from TWRP on slot B, then I get would the same problem (boot logo) on slot A. ADB sideload is installing magisk in current slot, that's why I can't do it from slot B to setup magisk on slot A. It's a bit sadly. And the second question to you, why our community vendor has general GCam problem, that is on all roms? Maybe you can contact to developers of it to fix that problem? Because it's really shame bug)
Just tell me about the experience you had with the Rom. is it smooth or not
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Gcam not working fix it
Machi007 said:
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Click to expand...
Click to collapse
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Rbargujar said:
Gcam not working fix it
Click to expand...
Click to collapse
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
FarLine99 said:
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Click to expand...
Click to collapse
I don't understand why to use stock recovery when we have TWRP.
Machi007 said:
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
I don't understand why to use stock recovery when we have TWRP.
Click to expand...
Click to collapse
Because if we try to use flash boot twrp on rom slot, then rom can't boot, it stuck on boot logo)
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Machi007 said:
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Click to expand...
Click to collapse
Maybe) In my experience, if I flash TWRP after flashing rom the rom doesn't boot, at all. Maybe I have done something wrong, but any way, if you will fix the stock recovery, it would be better!)
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Machi007 said:
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Click to expand...
Click to collapse
I tried to use twrp installer first, it did not worked for me, then I tried to use fastboot flash boot method, that is recommended for this TWRP. Using both flash recovery and boot method is new for me, so maybe it will be ok. But flash boot method doesn't work. And yeah, I used recommended from you Raghu's TWRP.
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Machi007 said:
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Click to expand...
Click to collapse
Maybe would try later, thanks for your work!)
Is anyone able to check if Duo Mobile 2fa is working?
I did all the steps, installed the rom, It siad "Fhasing A/B Zip to ianctive slot: B" after I try to change the slot and reboot, it says no OS installed... Is anyone else having this issue?
I did the Nokia Partition Tool, rebooted to bootloader, booted into the 3.4 TWRP it suggested and did the steps, It still said the error and rebooted back into TWRP*
EDIT: I was redoing it for the 3rd time as I typed this message and it magically worked.
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too? Perhaps then the installation would fit on the device without repartitioning -- I have made a couple of observations that have made me arrive at this conclusion:
My experience with LineageOS 19 is that the build + MindTheGApps package fits on the stock system partition without the need for repartitioning.
On the official PixysOS downloads page, I see that the size difference between Android 12 vanilla and GApps builds for one of the devices is something like 600 MB.
I am downloading the build at this instant, and I'm going to try fiddling around with the system image to make it fit on my PL2 before resorting to repartitioning (because we all know how much of a pain that can be ). I intend to install it later in the day, so I don't yet have feedback on the build itself.
Cheers! And thanks for your effort and time!
EDIT: I must also add that for a) people who prefer to use only core Google apps like GMS and Play Store (e.g. myself), and b) people who do not want to use even core Google services, a vanilla build would be ideal.
Vedanth Padmaraman said:
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too?
Click to expand...
Click to collapse
I'll consider it, maybe from the next build I'll provide both versions.