{
"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 v7.0.2
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]
About Resurrection Remix:
Resurrection Remix is a custom ROM based on LineageOS, SlimRoms, Omni and the original Remix ROM builds. This creates an awesome combination of customization & performance optimizations while bringing the latest features directly to your device.
Introduction:
This is an unofficial build of Resurrection Remix for the Motorola G7, codename ocean.
It should support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable. Sadly, we can not support the Verizon or AT&T variants, as their bootloaders are permanently locked.
ROM:
RR-P-v7.0.2-20191103-ocean-Unofficial-signed.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy A to B: (prevents bricks)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org
Preparation for A/B Roms:
1. Download TWRP and the Firmware for your variant from the links above.
2. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
3. Unlock your bootloader Instructions HERE.
4. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
5. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
6. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
7. While in TWRP choose Reboot > bootloader
8. Now you're ready for ROM Steps below
ROM - Installation:
1. Download the ROM, TWRP and GApps from the links above.
2. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
3. Flash signed ROM.zip
4. TWRP_installer/boot.img ramdisk method
5. Tap Reboot > Select opposite slot > Back > Recovery
6. Install Gapps + Magisk (if you choose)
7. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_Installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
It is imperative that you flash copypartitions.zip before flashing any OTA zips via TWRP. If you fail to do so you may require a blank flash to recover your device from QCOM DL when it switches slot suffix from A to B.
Any time your internal storage aka "Userdata" is directly from a stock install you must use 'fastboot -w' to erase it before using ROMS
XDA:DevDB Information
Unofficial Resurrection Remix for G7 Power , ROM for the Moto G7 Power
Contributors
Geofferey, SyberHexen, erfanoabdi
Source Code:
kernel_motorola_msm8953
android_device_motorola_ocean
proprietary_vendor_motorola-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock vendor.img
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 2019-11-03
Stable Release Date: 2019-10-31
Created 2019-10-31
Last Updated 2019-11-07
Changes:
- 10-31-19
Initial signed release
- 11-03-19
Improve notification led
Add picture adjust to livedisplay
This would get released an hour after my phone bricks. This is so f'ing frustrating. I'm sure the rom will be awesome.
Thanks a lot for this Rom!
With RR arrival for the G7 Power, the G7 power is becoming a viable solution for a main phone now!
disobey said:
This would get released an hour after my phone bricks. This is so f'ing frustrating. I'm sure the rom will be awesome.
Click to expand...
Click to collapse
How bricked? Lol. QCOM_BULK? Phone can prolly be unbricked with blank flash. Check out this group on telegram with some valuable resources & info http://t.me/G7Power.
the recovery .img you provided doesnt boot
---------- Post added at 06:07 AM ---------- Previous post was at 05:37 AM ----------
i just did an install following your instructions but using the recovery zip/img from here: https://forum.xda-developers.com/g7-power/development/rom-lineage-os-16-0-t3969341 and it seems to have worked fine
Everything seems to work fine but I just cannot get the twrp to permanent flash to the recovery... This ramdisk method is it literally just flashing the installer zip?
Geofferey said:
Resurrection Remix P v7.0.2
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]
About Resurrection Remix:
Resurrection Remix is a custom ROM based on LineageOS, SlimRoms, Omni and the original Remix ROM builds. This creates an awesome combination of customization & performance optimizations while bringing the latest features directly to your device.
Introduction:
This is an unofficial build of Resurrection Remix for the Motorola G7, codename ocean.
It should support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable. Sadly, we can not support the Verizon or AT&T variants, as their bootloaders are permanently locked.
ROM:
RR-P-v7.0.2-20191031-ocean-Unofficial-signed.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy A to B: (prevents bricks)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org
Preparation for A/B Roms:
1. Download TWRP and the Firmware for your variant from the links above.
2. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
3. Unlock your bootloader Instructions HERE.
4. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
5. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
6. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
7. While in TWRP choose Reboot > bootloader
8. Now you're ready for ROM Steps below
ROM - Installation:
1. Download the ROM, TWRP and GApps from the links above.
2. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
3. Flash signed ROM.zip
4. TWRP_installer/boot.img ramdisk method
5. Tap Reboot > Select opposite slot > Back > Recovery
6. Install Gapps + Magisk (if you choose)
7. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_Installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
IIt is imperative that you flash copypartitions.zip before performing any ROM flashing via OTA zips in TWRP. If you fail to do so you may require a blank flash to recover your device from QCOM DL when it switches slot suffix from A to B.
Any time your internal storage aka "Userdata" is directly from a stock install you must use 'fastboot -w' to erase it before using ROMS
XDA:DevDB Information
Unofficial Resurrection Remix for G7 Power , ROM for the Moto G7 Power
Contributors
Geofferey, SyberHexen, erfanoabdi
Source Code:
android_device_motorola_ocean
kernel_motorola_msm8953
proprietary_vendor_motorola-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock vendor.img
Based On: Lineage OS
Version Information
Status: Beta
Current Beta Version: 2019-10-31
Beta Release Date: 2019-10-31
Created 2019-10-31
Last Update
d 2019-10-31
XT1955-4 work?
Click to expand...
Click to collapse
Fully working now for 6 hours I can't see any bugs also fully bypassing the safety metrics and compatible with smali patcher spoofing Pokémon and able to use Google pay etc....
Match love man
sithuphyo said:
XT1955-4 work?
Click to expand...
Click to collapse
I don't see why it wouldn't.
By the way sorry I had posted the wrong link to TWRP, I've updated the link now.
I'm using Verizon, but plan to buy the variant with CDMA support that's unlocked. Do you know if this ROM will have any problems with it? Also, does VoLTE work with this rom?
@rocktone As I have no CDMA variant to test with I'm not sure. You might have problems with APNs but I wouldn't doubt that it would boot. VoLTE, wifi calling and messaging all work in my test but that's with a GSM carrier.
Nice ROM. Geofferey, thank you for your contribution!
I was only running Lineage OS for a few days when I decided to give this ROM a try. I performed the steps in 'dirty flash'. The ROM booted OK. Wow, there are a ton of options in this ROM!
For some reason, many Google apps did not show up. I flashed open_gapps-arm64-9.0-stock-20191025. I did not get Chrome, Drive, Duo, Maps, News, YouTube and others. I was able to install these via the Play Store. I think I figured out why this happened, but I will not attempt to replicate the problem; I'd rather stay with what I have.
Two notes for users: 1) stay away from the option which allows you to bypass PIN entry after reboot (w/fingerprint), 2) music visualizer on the lock screen does not work for me. It's difficult to find faults with this ROM.
PS: @sithuphyo or anyone else, please do not repost or quote the original post in its entirety. It makes comments difficult to follow.
I'm looking forward to trying this rom. I just got my phone yesterday and plan on trying this at some point. Probably not right now. I haven't even unlocked the bootloader or anything yet. I want to use it for a bit before doing that. I just got it all setup and don't want to wipe out my data yet. After coming from a phone I dropped in a sink full of water, I'm happy to have a 100% working phone. I look forward to seeing where this build goes.
Does it work on the 1955-2 ocean model, South American version?
danny8 said:
Nice ROM. Geofferey, thank you for your contribution!
I was only running Lineage OS for a few days when I decided to ....
Click to expand...
Click to collapse
How is battery life compared to stock ?
Sent from my moto g(7) power using Tapatalk
Battery life seems to be as good as stock.
KUSANAGUI said:
Does it work on the 1955-2 ocean model, South American version?
Click to expand...
Click to collapse
I have 1955-2 RETLA (I'm in USA) and it seems fine, as does Lineage OS.
A small feature in the stock ROM that's not in LOS / RR is the ability to turn off BOTH sims. You must have at least one sim active. If I were to do it over, I might've bought the USA version, even though it has less RAM, storage, and only one SIM slot. None of the previous is germane to your question, however.
Resurrection Remix ROM should work fine on your phone model.
MrCamby said:
How is battery life compared to stock ?
Click to expand...
Click to collapse
It is about the same or greater. See screenshot.
Unknown IMEI & No Sim Dectected
After install I have no sim dectected and unknown imei., everything else works just fine. Has anyone else had this issue and if so is there an easy fix?
I installed the update. I then put my phone down. When I came back the notification led scared me lol
Stock doesn't support the notification LED @Metalheadx you should have flashed the copypartitions.zip file. I think it's in the instructions.
Working great but is there an option to disable the fingerprint scanner acting as a home button? Only issue so far..
Edit: Replaced /system/usr/keylayout/uinput.fpc.kl with the one from Lineage to get rid of the fingerprint home gesture.
24hrs in it's very stable, no crashes or visual glitches :good:
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.
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.
{
"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"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
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.
*/
PROJECT STATUS:
- Everything seems to work fine at this point.
HOW TO INSTALL LINEAGEOS:
- Check your current firmware version: required version is V3.150 (March 2021 update, Android 11).
- If you're not on this version or unsure:
1 Reboot to recovery
Code:
adb reboot recovery
2 Download https://android.googleapis.com/packages/ota-api/package/37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip3 Sideload the file
Code:
adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip
4 Reboot to recovery again5 Sideload the file again to have it in both slots, A & B
Code:
adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip
- Flash Lineage recovery/bootimage to active slot via fastboot:
- Find out active slot:
Code:
fastboot getvar current-slot
- Flash boot.img to active slot:
Code:
fastboot flash boot_X boot.img
- Reboot to Lineage recovery via the fastboot UI
- Sideload LineageOS via Lineage recovery
Code:
adb sideload lineage-18.1-20210718-UNOFFICIAL-panther.zip
- Optional: flash GAPPS before rebooting to system
GOING BACK TO STOCK:
- Sideload https://android.googleapis.com/packages/ota-api/package/37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip in Lineage recovery
DOWNLOADS:
- LineageOS 18.1
- Lineage recovery
- Google Apps: MindTheGapps
DEVELOPER RESOURCES
- LineageOS source code: https://github.com/LineageOS @ lineage-18.1
- Device tree: https://github.com/trautamaki/android_device_nokia_panther @ lineage-18.1
- Kernel: current: https://www.nokia.com/phones/en_int/opensource (prebuilt)
(for reference: https://github.com/trautamaki/android_kernel_nokia_sdm439)
Android version: Android 11
Kernel version: Linux 4.9.y
Required firmware: March update, Android 11, V3.150 (Nokia/Panther_00WW/PAN_sprout:11/RKQ1.200928.002)
THIS IS ONLY TESTED BY ME ON MODEL TA-1157.
Indian variant may or may not work with this.
Telegram: https://t.me/los_panther
Info for curious:
This uses prebuilt stock vendor, hence the need to have 2 proper slots (as well as correct firmware version)
UPDATE:
* Sync LineageOS sources
* Audio is fixed
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
All the basic functionality appears to be working now. It is still built with selinux permissive and eng-variant, which reduces security.
* Download
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* Built the userdebug variant
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
All the basic functionality appears to be working now.
Todo:
* Light HAL for notification indication LED
* Firmware version checks for checking vendor & firmware version
* Download
I was surprised when I saw lineage for my nokia 4.2 that sits in box since I got it for free from operator when renewing contract.
I am not a novice for lineage, but first time working with nokia. I unlocked bootloader, although I still have message every time when I turn it on, that bootloader is unlocked and device is not secure. I hope that is fine.
I checked slots and slot B is in use, so, as a novice and because of securing my existing OS (i hope that counts) decided to set slot A as active.
I didnt touched anything else except tried to sideload suggested image and install it. But, everytime I encouter a error at 47% - pc saying "adb: failed to read command: No error" while device saying that it is wrong image and it is for PAN_sprout?
Then I tried to sideload Nokia-4.2-V3.150_B01.zip with same error, wiping data between retries. And on slot B I have latest update - march 2021 and andr 11.
Also, I presume that my device is locked to operator and it is dual sim. I returned to slot B and device is in working condition.
Any idea what can be done so I can install lineage?
vladabgd said:
I was surprised when I saw lineage for my nokia 4.2 that sits in box since I got it for free from operator when renewing contract.
I am not a novice for lineage, but first time working with nokia. I unlocked bootloader, although I still have message every time when I turn it on, that bootloader is unlocked and device is not secure. I hope that is fine.
I checked slots and slot B is in use, so, as a novice and because of securing my existing OS (i hope that counts) decided to set slot A as active.
I didnt touched anything else except tried to sideload suggested image and install it. But, everytime I encouter a error at 47% - pc saying "adb: failed to read command: No error" while device saying that it is wrong image and it is for PAN_sprout?
Then I tried to sideload Nokia-4.2-V3.150_B01.zip with same error, wiping data between retries. And on slot B I have latest update - march 2021 and andr 11.
Also, I presume that my device is locked to operator and it is dual sim. I returned to slot B and device is in working condition.
Any idea what can be done so I can install lineage?
Click to expand...
Click to collapse
The instructions were purposefully a bit obsecure when the project status was hardly WIP. I should update the instructions soon.
Basically you need to flash LineageOS with the provided recocery image (see downloads).
Going back to stock, use boot-no-assert.img (it doesn't check device before install).
This is needed because I named the device panther instead of PAN_sprout. I will fix this some day.
T1mb3, thanks on all efforts. And thank you on reply! It is easy to follow your procedure once I figured out how these devices working - well I figured out enought to work with installing lineage. I am little bit more rusty. Ive heard for a slots for the first time now. lol. I have 2 sony compact devices - with lineage, only because windows 8.1 died. and I had 8.1 only because 6 died. hah...
So, after your explanation I successfully installed lineage on Nokia 4.2!!!
T H A N K YOU!!!
for those who will give a try I can add this:
- I had problems with unlocking bootloader - device was visible in adb mode, but once restarted fastoot didnt worked - check device manager in windows and if you see nokia 4.2 as other device just manually update driver with android adb device from list.
- once that worked well, everytime I start phone I see screen with warning that bootloader is unlocked. just wait for some seconds and it will disappear.
- once booted back to operating system check for enabled developer options and check does adb working. if it works reboot to fastboot with "adb reboot fastboot"
- with fastboot choose right slot for experiment: "fastboot getvar current-slot" shows current. mine was b so I changed to a with "fastboot set_active a"
- once set slot, flash boot with "fastboot flash boot_a boot-no-assert.img" where _a is slot you choose.
- reboot with "fastboot reboot"
- enter new boot and choose adb. with adb sideload zip "adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip". maybe there will be warnings but continue anyway. after some time and with step 2/2 check on computer did adb command finished. after finish restart nokia.
- i went directly to os, expecting that this is android from zip flile, on slot a. but then I checked and saw that active slot was again b and that android was mine.
- i went to fastboot again and set active slot to a again, tried to restart device and got message that operating system is corrupt. holding power button turns off device and i entered again bootloader with power button and vol down.
- then I decided to sideload lineage on same slot - a, who cares, hah, and sideloaded it after I wiped all data.
- restarted device and voila - lineage works!!!
maybe this will help someone who have nokia 4.2 and want to install lineage. time consumed is about one hour.
thanks T1mb3
vladabgd said:
T1mb3, thanks on all efforts. And thank you on reply! It is easy to follow your procedure once I figured out how these devices working - well I figured out enought to work with installing lineage. I am little bit more rusty. Ive heard for a slots for the first time now. lol. I have 2 sony compact devices - with lineage, only because windows 8.1 died. and I had 8.1 only because 6 died. hah...
So, after your explanation I successfully installed lineage on Nokia 4.2!!!
T H A N K YOU!!!
for those who will give a try I can add this:
- I had problems with unlocking bootloader - device was visible in adb mode, but once restarted fastoot didnt worked - check device manager in windows and if you see nokia 4.2 as other device just manually update driver with android adb device from list.
- once that worked well, everytime I start phone I see screen with warning that bootloader is unlocked. just wait for some seconds and it will disappear.
- once booted back to operating system check for enabled developer options and check does adb working. if it works reboot to fastboot with "adb reboot fastboot"
- with fastboot choose right slot for experiment: "fastboot getvar current-slot" shows current. mine was b so I changed to a with "fastboot set_active a"
- once set slot, flash boot with "fastboot flash boot_a boot-no-assert.img" where _a is slot you choose.
- reboot with "fastboot reboot"
- enter new boot and choose adb. with adb sideload zip "adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip". maybe there will be warnings but continue anyway. after some time and with step 2/2 check on computer did adb command finished. after finish restart nokia.
- i went directly to os, expecting that this is android from zip flile, on slot a. but then I checked and saw that active slot was again b and that android was mine.
- i went to fastboot again and set active slot to a again, tried to restart device and got message that operating system is corrupt. holding power button turns off device and i entered again bootloader with power button and vol down.
- then I decided to sideload lineage on same slot - a, who cares, hah, and sideloaded it after I wiped all data.
- restarted device and voila - lineage works!!!
maybe this will help someone who have nokia 4.2 and want to install lineage. time consumed is about one hour.
thanks T1mb3
Click to expand...
Click to collapse
Nice!
The issue you had in the end was that you only flashed the 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip once to slot a. Now when you go install Lineage, it installs to slot b -> there's a mismatch. Therefore you should install the stock rom twice.
UPDATE:
* Sync LineageOS sources
* Light HAL works now, features include battery light and static notification light (no breath effect)
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
Todo:
* Firmware version checks for checking vendor & firmware version
* Fix tethering
* Download
Thanks on new update!!!
1 yes, you are right. I noticed that lineage is on slot b. I didnt understood when you wrote mismatch - do you mean that I needed to flash zip twice on slot a, or once on slot a and once on slot b?
2 also, I do not know how to flash updated version of lineage: if I just sideload it on existing and working lineage on slot b should I wipe data on slot b before install or I can just install over existing version?
3 finally: I never used opengapps - I meant mindthegapps so I wanted to try - I was late: already installed lineage and booted into it. do you have idea what to do now.
thanks on great efforts T1mb3!!!
vladabgd said:
Thanks on new update!!!
1 yes, you are right. I noticed that lineage is on slot b. I didnt understood when you wrote mismatch - do you mean that I needed to flash zip twice on slot a, or once on slot a and once on slot b?
2 also, I do not know how to flash updated version of lineage: if I just sideload it on existing and working lineage on slot b should I wipe data on slot b before install or I can just install over existing version?
3 finally: I never used opengapps - I meant mindthegapps so I wanted to try - I was late: already installed lineage and booted into it. do you have idea what to do now.
thanks on great efforts T1mb3!!!
Click to expand...
Click to collapse
1. Yes, you need to have the correct stock rom (vendor partition and firmware) version on both slots. Flashing it twice with a reboot back to recovery will do the job.
2. Download the zip, reboot to recovery and sideload normally. Data-partition does not have a/b slots, it's shared across both slots so no need to wipe it.
In your specific case, you will likely need to flash the stock rom once again to populate the vendor and firmware partitions, then Lineage update (both on the same slot).
3. Wipe data, flash Gapps, reboot. This makes you to start from the setup wizard.
UPDATE:
* Previous update I accidentally built eng variant instead of userdebug, this is same but userdebug.
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
Todo:
* Firmware version checks for checking vendor & firmware version
* Fix tethering
* Download
I just tried it yesterday. Am I the only one whose nokia 4.2 constantly reboots after a minute or sth? Bc it seems like there are stability issues with the current build
el-chuerro said:
I just tried it yesterday. Am I the only one whose nokia 4.2 constantly reboots after a minute or sth? Bc it seems like there are stability issues with the current build
Click to expand...
Click to collapse
I have experienced no issues.
2 days with lineage on nokia 4.2 and no single issue. all is working even notification led.
i had issues with gapps - even i tried to wipe data and reinstall clean lineage google kept returning and crashing system. so I ended with what I didnt do at first place - complete wipe and starting from step one - stock rom on both slots with whole procedure one by one. it was exhausting but all worked fine after.
even I have branded phone I tested it with sim card from another operator and device is sim free now.
at the end, thanks to Timb3 we have very nice debloated and degoogled device. and I thought that I will never take it in hands... brilliant work...
UPDATE:
* Wifi causing whole system to crash (only affected a few) is fixed
* Wifi tethering is fixed
* Updated CarrierConfig
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
Todo:
* Firmware version checks for checking vendor & firmware version
* Download
I tried installing MindTheGApps from the start a handful of times. I don't know why, but it's never worked. I then tried to install OpenGApps too, but that also didn't seem to work? I'm very confused.
I don't get any errors, so I don't know what's happening. They seem to install fine, but when I get into LineageOS, there's no google apps installed.
UPDATE: I figured it out. I didn't realize I had to reboot back into recovery after the lineage install.
Wifi wont even turn on at all, I tap the quick button for it and it just turns itself off, I go into the settings themselves and switch it on, it turns itself off again.. so I guess wifi isn't causing system to crash now, but that's only because you cant even turn WiFi on at all
UPDATE:
* Headphone jack fixed
NOTE:
You may need to update recovery (= fastboot flash boot_X boot.img) to install this update.
Download updated recovery: https://sourceforge.net/projects/lineageos-panther/files/recovery/boot-2021-08-01.img/download
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
* Download
UPDATE:
* Security patch from August
Old news (only needed if upgrading from older build than 2021-08-01): Download and flash updated recovery if installing fails: https://sourceforge.net/projects/lineageos-panther/files/recovery/boot-2021-08-01.img/download
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
* Download
Note: The source code is no longer maintained. Hence the ROM ends its life here.
{
"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"
}
Rich (BB 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.
Read the whole OP! Be respectful to each other and don't ask for ETAs, it's considered as being rude!
AOSP Extended is an AOSP based ROM which provides stock UI/UX experience with useful customizations. Being based on AOSP it provides a smooth experience. We have added useful customizations from various other open-source projects and have tried to keep our things simple. A ROM by a user, for a user. #BeExtended
Download AEX for OnePlus 7
Want to try this awesomeness? (Clean Flash May Build)
Rich (BB code):
-Make sure that you have backed up your data and are familiar with your device
-Also make sure that you have unlocked your bootloader
-You will need to have OxygenOS 11.0.7.1 or above flashed to both the slots before flashing this ROM. If not, you might have broken Widevine L1, HDR, High quality streaming on OTTs like Amazon Prime and Netflix.
-If you are unsure of having OOS 11.0.7.1 on both slots, Do the following:
1. When you are on OOS 11, get into fastboot mode and flash the given boot image by using the command: fastboot flash boot <boot_file_name>.img
2. After that's done, press volume down button twice and you will see "Recovery Mode" at the top of screen. Press power button to enter recovery.
3. From menu select "Apply update" and then "Apply from ADB".
4. Sideload the file mentioned below by using: adb sideload copy-partitions-20200903_1329.zip
copy-partitions-20200903_1329.zip- After this you can follow directly from step 3 below.
- Note that this copy partition is required only during first flash.
ADB Sideload Method+Clean Flash:
1. Get into fastboot mode and flash the given boot image by using the command: fastboot flash boot <boot_file_name>.img
2. After that's done, press volume down button twice and you will see "Recovery Mode" at the top of screen. Press power button to enter recovery.
3. When in recovery, select "Factory reset" and then "Format data/Factory reset".
4. Go back to main, menu and select "Apply update" and then "Apply from ADB".
5. Next, sideload the ROM by using the command: adb sideload <ROM_file_name>.zip
-Flashing will take some time (progress will be only upto 47%). Later reboot to system.
Note: After first flash, OTA will be applicable for further builds.
ADB Sideload Dirty Flash.
-Reboot to recovery and select "Apply update" and then "Apply from ADB".
-Next, sideload the ROM by using the command: adb sideload <ROM_file_name>.zip
-Reboot to system.
For Rooting
-Patch the boot image using magisk and flash it via fastboot by the command: fastboot flash boot <boot_file_name>.img
-No need for format data while switching the kernel or rooting. Note that the ROM is non-sdcards and FBEv2
First boot will take a few minutes! Have patience
Clean Flash is always recommended!
Visit our Website. Subscribe to our Telegram Channel. Also join our Telegram Group Chat!
Want to translate to your language? Visit our Crowdin
Want to contribute to the development of this ROM?
Checkout our Github and Gerrit
People behind this amazing ROM!
@ishubhamsingh (Owner/Dev/Designer), JDC Team, DirtyUnicorns, LineageOS/Cyanogenmod, TeamSubstratum, Nitrogen Project, Pure Nexus, OmniROM, AOSPA, ABC ROM, GZOSP Community, YAAP ROM and YAAP developers, AOSP-Krypton ROM and AOSP-Krypton developers, Johan Söderholm for DuckDuckGo Browser, Enrico D'Ortenzio for Music Player Go, @AlienCreature7, @Wizper99, @Allstargaurav, @Edozullo and @harsh sharma (For designing the ROM Logo, Fling etc)
XDA:DevDB Information
AospExtended, ROM for OnePlus 7
Contributors
ROM Maintainer: Shantanu Sarkar
Source Code: https://www.github.com/AospExtended
Kernel Source: https://github.com/AOSP-Krypton/kernel_oneplus_sm8150
Kernel Developers: AnnoyingZlatan & nvp12
Device Sources: https://github.com/AospExtended-Devices
ROM OS Version: 12.1.x
ROM Kernel: Dora 3.1
ROM Firmware Required: OOS 11.0.7.1
Based On: AOSP
Version Information
Status: Stable
Security Patch: 5 May 2022
Stable Release Date: 12-05-2022
Donation links:
PayPal
UPI: [email protected]
Thread designed by AmolAmrit and ishubhamsingh
Screenshots [Update: 12th May 2022]
Really smooth and customizable rom, but drains a lot of battery while being idle, is there any fix for battery backup or the rom is itself battery consuming?
Good Going Guacamoleb!!
Great Work Dev
Working Flawlessly
Awesome rom. Switched from KOSP rom. Loving it more. Definitely feeling better.
Stable, fast and features packed
Sachet7 said:
Awesome rom. Switched from KOSP rom. Loving it more. Definitely feeling better.
Stable, fast and features packed
Click to expand...
Click to collapse
Few downsides -
Wide wine L1 certification is not there. It has LE certification.
HDR support is also not there.
Max playback - SD on Netflix and Amazon Prime
@shantanusarkar please fix these.
Sachet7 said:
Few downsides -
Wide wine L1 certification is not there. It has LE certification.
HDR support is also not there.
Max playback - SD on Netflix and Amazon Prime
@shantanusarkar please fix these.
Click to expand...
Click to collapse
This is not true. In flashing instructions it is clearly mentioned that you need to have OOS 11.0.5.1 on both the slots before flashing the ROM. Not doing so will result in breaking widevine. It is working fine in my device. Look at the attached screenshots
I has rolled back to oxygen OS and updated to OOS 11.0.5.1 using MSM tool but I don't know how to verify whether it was installed on both slots or not. How to check that?
Is there any way to fix this without rolling back to OOS. It takes a lot of time
Sachet7 said:
I has rolled back to oxygen OS and updated to OOS 11.0.5.1 using MSM tool but I don't know how to verify whether it was installed on both slots or not. How to check that?
Is there any way to fix this without rolling back to OOS. It takes a lot of time
Click to expand...
Click to collapse
sideload this zip using aex recovery or twrp and see if it is fixed. If not, you will have to flash OOS manually on both slots.
copy-partitions-20200903_1329.zip
drive.google.com
shantanusarkar said:
sideload this zip using aex recovery or twrp and see if it is fixed. If not, you will have to flash OOS manually on both slots.
copy-partitions-20200903_1329.zip
drive.google.com
Click to expand...
Click to collapse
Didn't work. Thanks though.
I tried the whole process again. I rolled back to android 10 using mam tool. It had L3 certification. Then I downloaded the latest firmware 11.0.6.. using oxygen updater and confirmed that widevine level had changed to L1 and stayed at L1 even after unlocking bootloader. Then I installed this rom. Again the certification broke and changed to L3 in AOSP.
What do I do
Sachet7 said:
I tried the whole process again. I rolled back to android 10 using mam tool. It had L3 certification. Then I downloaded the latest firmware 11.0.6.. using oxygen updater and confirmed that widevine level had changed to L1 and stayed at L1 even after unlocking bootloader. Then I installed this rom. Again the certification broke and changed to L3 in AOSP.
What do I do
Click to expand...
Click to collapse
When you're on oxygen 11.0.6.1, fastboot flash boot boot.img. Then reboot to recovery. Before you flash the ROM, flash the copy-partitions-20200903_1329.zip using adb sideload. After that, flash the ROM. You'll be good to go.
It worked finally. Thanks for the support
Standby battery discharge is quite high, especially in comparison with Kosp 2.4. I also feel, auto brightness is quite aggressive. However, the rom is smooth and fantastic. Looking forward to improvement in battery and auto brightness in future updates.
Nice work ... Thanks for supporting this device guys
Has this rom been abandoned?
giannib.90 said:
Has this rom been abandoned?
Click to expand...
Click to collapse
No. Officially released in feb and you are thinking it is abandoned already?
shantanusarkar said:
No. Officially released in feb and you are thinking it is abandoned already?
Click to expand...
Click to collapse
usually early versions are full of bugs and the fix update arrives within the first 2 weeks. A month has passed and everything is silent
giannib.90 said:
usually early versions are full of bugs and the fix update arrives within the first 2 weeks. A month has passed and everything is silent
Click to expand...
Click to collapse
It has two reasons. The initial build is almost bug free. Secondly, google has surprised us by officially releasing 12.1 aka 12L. The source needs to be rebased. Also, google themselves haven't released a march update for Pixel 6/6 Pro
{
"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.