Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
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
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.
XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21
Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...
Reserved
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Woks awesome, thank you dev
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!
LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please
asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat
Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help
BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.
I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to Pie Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7885 Vendors and modified to support our devices, i have also added few patches and fixes to this vendor to get the best possible experience
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the vendor and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Bevice By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Dumpster.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
Bluetooth calls are broken
Credits:
- @ananjaser1211 for his contribution
- @TaifAljaloo for testing
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Treble, Vendor for the Samsung Galaxy A8 (2018)
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Current Stable Version: v1
Created 2019-05-17
Last Updated 2019-05-17
{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Treble Pie Vendor Dumpster V1.0 [LATEST]
Treble folder : Gdrive
Recommended GSI : Gdrive
Generic System Image (list) : Github
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
V1.0
-initial release
F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above
reserved
I just flashed the Lineage OS v16 GSI with this vendor and found no problems other than no network bars (as mentioned above) and there were no problems with the camera and fingerprint. I will notify you later if there is a bugs
Thanks for your hard work ?
Sweet! I'm gonna be up all night!
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
mindlery said:
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
Click to expand...
Click to collapse
Where you able to get gapps installed it always failed for me.
This has happened on most of these roms
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
mindlery said:
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
Click to expand...
Click to collapse
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
mchlbenner said:
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
Click to expand...
Click to collapse
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
mindlery said:
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
Click to expand...
Click to collapse
I had not heard of it also but it seems to work without issue.
Only thing on screenshot you have edit where photo is being stored.
Does this allow me to use system-as-root gsis? Since android 9 treble implementation is supposed to be system as root even on aonly, I would guess so, but I couldn't get my device to boot with one yet.
Weird, I can't even get aospextended to work... It just bootloops without bootanimation.
Edit: nvm, I got it to work, but I had to flash the oreo vendor first, and then the pie vendor.
Edit2: fingerprint doesn't seem to work even with fp patch (it's weird, it registers the fingerprint, and even validates it, but it does nothing on the lockscreen)
Edit3: restart fixed it
I have a few questions
I used to flash the usual custom roms so is this is the same thing i mean that if i can use it to flash custom roms
And which roms exactly working perfectly on this device without any issues
Also should i root my phone before installing it or what exactly should i do
Is it stable and doesn't have any problems or will i face some problems while im using it
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
CoinKiller said:
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
Click to expand...
Click to collapse
Did you install GSI_Fix_boot.zip?
So I want to install Google phone but I cannot get it to work. Can you give me an alternative ?
If I want to install a different GSI I follow the steps again (install vendor, flash GSI, flash boot fix and fixes if needed) or just wipe system, data, cache and flash the new image+ boot fix
slawdos said:
Did you install GSI_Fix_boot.zip?
Click to expand...
Click to collapse
Yes but i had to format /vendor after installing that zip (it wasnt the zip fault!), Didn't that get installed in /system?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
(A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)
Latest Downloads:
Official Server | SourceForge Mirror
NOTE:
- Download the Fastboot images zip of the variant you want
- There are two variants, "Official" does not contain Gapps while "Gapps" does.
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on
XDA:DevDB Information
Android Open Source Illusion Project, ROM for the OnePlus 7T
Contributors
anirudhgupta109
Source Code: [url]https://www.github.com/AOSiP[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.2 or above
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-14
Last Updated 2020-05-06
Reserved
INSTALLATION PROCEDURE:
MAKE SURE YOU'RE ON THE LATEST OOS FROM HERE
DO NOT EVER WIPE SYSTEM OR VENDOR ON THE OP7T!!!!!
Considering how the 7T doesn't have TWRP and has dynamic partitions, I'll try to explain everything in detail:
1. If you're coming from another ROM (including OOS) or need to perform a clean flash:
Boot into the bootloader (if you don't know how to do this, you should probably not flash)
Connect your phone to your PC and in an ADB/Fastboot shell, wipe device using
Code:
fastboot -w
Connect your phone to your PC and in an ADB/Fastboot shell, type
Code:
fastboot reboot fastboot
NOTE: If command prompt/line complains about fastboot not being a valid target you need to update fastboot from HERE
Your phone should now be in fastbootd (the UI is exactly like recovery mode so don't get confused)
Read about fastbootd HERE
Type the following to make sure your phone is in fastbootd while also making sure your phone is in the recovery-like UI
Code:
fastboot getvar is-userspace
If the above does returns the value true you can now flash the ROMs, if it doesn't try figuring out what went wrong (I don't want to hear about the failed attempts, please don't spam the thread with them)
Type this command to flash the ROM:
Code:
fastboot update <ROM.zip>
NOTE: IF COMMAND LINE IS SAYING:
Code:
archive does not contain 'xyz.sig'
This is normal, ignore it.
After the above is done, your device will automatically reboot to AOSiP, have fun!
OPTIONAL:
If you want magisk, patch the boot image from the AOSiP site which ends in the name -boot.img, in Magisk manager
Boot to bootloader
Boot into that image (DO NOT FLASH!!!)
Code:
fastboot boot magisk_patched.img
Install Magisk manager and from it select Install > Direct install
Reboot and enjoy AOSiP with Magisk!
Enjoy
OPTIONAL:
If you'd like to convert to F2FS:
Open settings>system>reset options and select Erase all data (factory reset)
This'll wipe all data and convert your device to f2fs automatically!
2. If you're updating the ROM:
a. Via the inbuilt Updater
When you get a notification of new build available, tap it
Tap Download
Wait for Download
Tap install
Wait for install
If you use Magisk, open Magisk Manager, select install, select Install to Inactive Slot (After OTA)
Tap reboot
Enjoy!!
b. Manually via bootloader
Disable all substratum overlays if you have a theme applied
Boot into fastbootd
If you're booted into the system
Code:
adb reboot fastboot
If you're booted into bootloader
Code:
fastboot reboot fastboot
Flash the ROM using
Code:
fastboot update <ROM.zip>
NOTE: YOU DO NOT NEED TO WIPE DATA WHEN UPDATING
Reboot to system and enjoy
NOTE: If you have issues with Settings or Play Services force-closes you need to clean flash (Method 1).
KNOWN ISSUES:
Auto brightness is wonky in dark enviroments Fixed in 20200625
Reserved
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your OOS base versions in reports. (Eg: 10.0.1, 10.0.2, 10.0.6 etc.)
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
FREQUENTLY ASKED QUESTIONS:
Q: Fastboot isn't allowing me to flash system image, what am I doing wrong?
A: You haven't booted to fastbootd (the UI looks like recovery and fastboot devices command shows the device in fastboot mode)
Q: What GApps do I flash?
A: You cannot flash Gapps on the device, use the Gapps variant build instead if you need Gapps.
Q: When booting to the Magisk patched image, it leads to crashdump mode.
A: You didn't select the first two options in Magisk Manager before patching the boot image under Advanced settings (i.e. Preserve force encryption and Preserve AVB 2.0/dm-verity).
Q: Do I have to wipe data if coming from another ROM?
A: Yes, I will not be providing help/support to users that haven't wiped data when coming from another ROM.
Q: How often will I be getting updates?
A: The plan is for weeklies, if unavoidable circumstances come up, please don't spam the thread. I will release a build as soon as one is ready.
Q: Does VoLTE/VoWiFi work?
A: VoLTE works, I have tested on Airtel in India and a couple of my US based testers have too.
VoWiFi (WiFi Calling) works based on my testers in the US and for me on Airtel (India), let me know about other carriers.
Q: Does Android Auto work?
A: I don't have accessibility to an Android Auto vehicle nor the hardware but my testers have confirmed that it works! Let me know if it does for you too so that others have concrete proof about it.
Q: I ended up on CrashDump mode, how do I get back to my system?
A: Theres a valuable thread HERE which can help restoring your system, you WILL LOSE ALL DATA and I will not be blamed under any circumstances.
Q: Is the ROM official?
A: The ROM is Official.
Q: I use Telegram, where can I find help on that platform?
A: There is a common AOSiP Group Chat for all devices, the link is HERE
Q: Does SafteyNet pass and is the SELinux Enforcing?
A: Yes, SafteyNet does pass out-of-the-box and SELinux is Enforcing.
Q: What OOS Base firmware do I use?
A: OOS 10.0.6 is the recommended base firmware right now.
Q: I'm having high idle drain, please fix.
A: I'll need more data from you to figure it out, Install BetterBatteryStats and let me know about what it tells you after 3-4 charge cycles. Please do not report issues when having apps like Greenify, Naptime, Wakelock blocker etc.
Q: My phone is stuck on the "Bootloader is unlocked" warning page, why isn't my system booting?
A: Since there are a bunch of scripts being executed when the device is sent a power on signal, it might take some time to boot. Don't panic, your system will boot fine after some time. All builds are personally tested by me and a few testers.
Reserved
Littyyyyy???
Yay, aosip is here. You are the man @anirudhgupta109 glad you got Verizon going. Kudos to the Verizon tester and whatnot.
Thank you for the perfect Rom.
This has all the customizable features like android 9
so when you say a clean flash, does it mean wiping the internal storage as well cause it'll be a little vexing to transfer all the data again and again
anirudhgupta109 said:
Reserved
Click to expand...
Click to collapse
Very well written op and following couple posts. OP's like this is why I still use XDA everything right where you need it instead of having to go through thousands of lines of Chat.
This is the most detailed instructions I've ever seen on xda. Very well written. Thanks for your patience teaching a newb everything he should know. And congrats for your nice work!
I installed it. Great work. Thanks.
All looks fine so far. Didn't setup fingerprint yet so no comments on that.
The only thing that I did not like much is the camera app. Can we have camera of Oneplus or GCam please? I know, I can install gcam separately but would be better if it is included instead of the one available right now in the rom.
So far the experience has been great. Fingerprint is pretty good, about 9/10 success times.
I noticed that the FP icon when pressed is only a white circle, while on OOS it's white with red in middle, that wouldn't factor in accuracy?
Additionally, on AOD, does the screen stay running at 90Hz? As that would make it drain battery quite fast.
Either way, great ROM, thank you.
aer0zer0 said:
Yay, aosip is here. You are the man @anirudhgupta109 glad you got Verizon going. Kudos to the Verizon tester and whatnot.
Click to expand...
Click to collapse
Thanks a lot for testing that annoying carrier ???
umair shaikh said:
so when you say a clean flash, does it mean wiping the internal storage as well cause it'll be a little vexing to transfer all the data again and again
Click to expand...
Click to collapse
Yes, clean flashing includes internal storage.
The only time you need to clean flash is when coming from another ROM.
When updating AOSiP you don't need to so it's basically a one time process.
david72262 said:
Very well written op and following couple posts. OP's like this is why I still use XDA everything right where you need it instead of having to go through thousands of lines of Chat.
Click to expand...
Click to collapse
yqx1110 said:
This is the most detailed instructions I've ever seen on xda. Very well written. Thanks for your patience teaching a newb everything he should know. And congrats for your nice work!
Click to expand...
Click to collapse
Thanks for the kind words the two of you, it took awhile to type it out for everyone, glad it's appreciated ??
elanandkumar said:
I installed it. Great work. Thanks.
All looks fine so far. Didn't setup fingerprint yet so no comments on that.
The only thing that I did not like much is the camera app. Can we have camera of Oneplus or GCam please? I know, I can install gcam separately but would be better if it is included instead of the one available right now in the rom.
Click to expand...
Click to collapse
We are an open source project so including any form of closed source apps we can do away with irks me. The idea of having GApps inside the ROM itself feels wrong but it's a necessity.
Anyway, the latest Urnyx GCam works perfectly with AOSiP without any magisk modules nor setting permissive selinux. It's literally install and use so you can do so if you need to.
The OnePlus Camera also works, just that it needs to be launched from the long press menu on your launcher.
Mohammed779 said:
So far the experience has been great. Fingerprint is pretty good, about 9/10 success times.
I noticed that the FP icon when pressed is only a white circle, while on OOS it's white with red in middle, that wouldn't factor in accuracy?
Additionally, on AOD, does the screen stay running at 90Hz? As that would make it drain battery quite fast.
Either way, great ROM, thank you.
Click to expand...
Click to collapse
That's an interesting observation, I'll look into the red center.
No, there is nothing to refresh on AOD so it doesn't run on 90Hz.
You can also choose the type of 90Hz you want to run with in OnePlus Settings (forced or auto)
Hey the google bar seems to be permanently affixed to the home screen, I cant drag it away like a normal widget, is there anything I can do about that short of installing a launcher?
10.0.7
What are my chances if I start from 10.0.7?
I've got problems with an updated rooted 1903. Tried to keep root but didn't work. Now I've got no wifi and no sound.
Will this get me rolling again?
Many thanks
mikefnz said:
What are my chances if I start from 10.0.7?
I've got problems with an updated rooted 1903. Tried to keep root but didn't work. Now I've got no wifi and no sound.
Will this get me rolling again?
Many thanks
Click to expand...
Click to collapse
I'm running this ROM on 10.0.7. everything is fine.
help !!!
anirudhgupta109 said:
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
(A massive thanks to @0ctobot and @RenderBroken for the help with the kernel)
Latest Downloads:
Official Server | SourceForge Mirror
NOTE:
- Since the ROM is big in size due to gapps, try downloading from SourceForge to make sure you get the complete file and also compare md5sum.
- GApps is already pre-included in the ROM.
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on
XDA:DevDB Information
Android Open Source Illusion Project, ROM for the OnePlus 7T
Contributors
anirudhgupta109
Source Code: https://www.github.com/AOSiP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.6
Based On: AOSP
Version Information
Status: Alpha
Created 2019-12-14
Last Updated 2019-12-14
Click to expand...
Click to collapse
writing 'system' ...
FAILED (partition not found)
hru200 said:
writing 'system' ...
FAILED (partition not found)
Click to expand...
Click to collapse
Follow the instructions maybe?
Type "fastboot reboot fastboot" then do the images flashing commands.
---------- Post added at 10:45 AM ---------- Previous post was at 10:39 AM ----------
Anyone having weaker WiFi signal compared to OOS? On a 5GHz WiFi that is. Same testing position, yet much weaker. Additionally, frequent disconnections.
[10.0][OFFICIAL]Resurrection Remix v8.x [device_code]
{
"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:
[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. For 7T: Be sure to be on latest oos, beta or stable is fine (flash both slots prior to installing the rom)
Download the latest Resurrection Remix Rom (currently on V8.6)
(7T builds gave gapps included) so disregard flashing gapps.)
You can use either twrp (mauronfrios latest or Chinese) to flash the rom.
Additionally - you can unpack the bin that is in the zip and fastboot flash as many other roms. SEE POST#4!! Importantly, after flashing, no matter the method, once you see the RR boot logo, force reboot to bootloader mode, and use the buttons to cycle to recovery. Select this as it will now reboot to the roms recovery. Go to wipe data. Wipe data and now reboot. This is mandatory if you flash via twrp or want to run f2fs vs ext4; bc the rom will run very well on f2fs as it is much faster file system than ext4.( Once you format after the first flash.) If using twrp, the first boot sets it as this but unless a format is done, it will not boot. So, do not skip this step. After the data wipe and rebooting, the rom boots up in a few Mins. If it doesn't boot in 5mins. You may have made a mistake and in that case reflash stock to both slots and try again.
Yes, Ota updates work fine, be sure to go to updater and prioritize update process. I usually send a build every couple days.
You can retain root by after the download and install occurs but before reboot, launching magisk manager and installing to opposite slot and then rebooting.
**Ota will not work unless RR is on both slots before taking ota. To fix that, after you get it booted, boot to bootloader and fastboot set_active other, and reflash via fastboot. OR if you used twrp, flash the ota again and it puts it on the opposite slot.
Neutrino Kernel is built in-line, latest Hoth 1.95
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
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.
Current download and details:https://forum.xda-developers.com/showpost.php?p=83469869&postcount=465
7T TG Chat https://t.me/rr_op7t
Payload Dumper
https://drive.google.com/open?id=1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut
Thanks for this! Glad to see you here as well
Here are some more detailed instructions by my long time constituent @aer0zer0 thank youuuu!!!
how to extract a payload and flash a rom for noobs, windows only
pre-requisites:
1. In general, you want to have the SAME version of OOS on both sides. Im not going to go into detail on how to MSM, and flash a full OTA locally, reboot, then flash the same OTA locally again and reboot.
2. payload dumper for windows: https://drive.google.com/file/d/1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut/view?usp=sharing its windows 64 bit only
3. Latest ADB/Fastboot binaries: when flashing using using a script, and you see errors such as system partition cannot be found, etc... your binaries are old, most likely cause by some ghetto version minimal adb/fastboot thats jank. To verify where your adb/fastboot is running from, in a shell, type fastboot --version this will tell you where you resident adb/fastboot binaries are running from. The link to updates binaries is here https://developer.android.com/studio/releases/platform-tools select the windows SDK version. Once downloaded, copy and paste them over top of the ones being used from the fastboot --version output.
4. a bat file to flash all the images you are dumping. https://drive.google.com/file/d/1HW1Q82wpsnBPUcPkAnXO-tQjVIWSZ_oQ/view?usp=sharing this wipes, goes to fastbootd, will flash all the images from the payload.bin dump to both sides, wipes, and sets it to boot from slot A.
5. lots of common sense
Instuctions
1. extract the payload dumper somewhere on your PC, you will see an "IN" folder, "OUT" folder, and an executable.
2. extract the payload.bin file from the rom.zip you wish to install, and place it in the "IN" folder.
3. run the payload dumper exectuable, a shell will pop up, showing the images being extracted.
4. once the shell closes, the images are all succesfully unpacked. Copy those images in the "OUT" folder to whereevr you would like to store your rom.
5. copy/paste the bat file wherever you placed your images.
6. reboot your phone to fastboot, plug it into the PC, and run the bat.
7. process takes 4-5 minutes, sit back, it will then reboot back to fastboot.
8. start the phone from fastboot, and wait for your new rom to boot.
9. finish and enjoy!
Also, there is no real bugs. On occasion one may think there is a bug, and if there is in fact one, we work promptly to resolve it as a team. Typically, one thinks a bug is a bug, but the rom has so many features, it is just a conflicting setting most likely, I implore you all to exercise trial and error. If something was fine and you fiddled with settings, go unfiddle and see what could make something not work. We could not foolproof all features to not conflict on the occasion if we get kinda crazy with what we expect our device and it's software to be able to do. All works flawlessly. Enjoy the rom and thanks to my colleagues and my friends who have always been there in this wonderful android world, never quick to judge, always quicker to help and teach. Never from the class of elitist android dev who is "too cool" to just be nice. Thanks guys.
The names below have helped me in numerous ways over the years, thanks for the help, support, and overall non-douchebaggery activities:
KangaroosterMeadows-Where the magic happens
@wrongway213
@aer0zer0
@xstefen
@NoSpamDan
@varund7726
@Freak07
@return.of.octobot
@abalam
@hondajohn
@Neo
@unixandria
@fKm
@lil_kujo
@kdp162
@omariscal1019
@DeathStroke
@risasuke
JackEagle-his guides and advice in chat, Anthony P, DPryor, Cody S, and everyone else I haven't named. Thanks also go to AOSiP- for solid trees that most of us all use.
Congrats @FullOfHell what a great rom
Just installed it and I'm liking every bit of it thank you @FullOfHell!
I am touched! I was losing hope for this device. thank you!
Thanks! Will try it soon.
Enviado de meu HD1903 usando o Tapatalk
Face unlock included? How about Fp? Works great, even with low brightness?
Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
yes faceunlock is included and fingerprint works flawlessly, low light, no light, any situation
Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
lil_kujo said:
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
Click to expand...
Click to collapse
Thanks man appreciate it. Hope you enjoy it
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
AnkeshReborn said:
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
Click to expand...
Click to collapse
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
FullOfHell said:
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
Click to expand...
Click to collapse
Great to know the safety net passes.
Would just leave a message here asking if any forum member based from India installing RR can confirm if the payment apps like PayTM, PhonePe and the likes of it work? It's the just last thing that's stopping me from getting this beauty on 7T.
Along with info of banking apps, i would also like to know if this has auto call recording feature ? 90hz display support ?
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
shetty_chadda said:
Along with info of banking apps, i would also like to know if this has auto call recording feature ?
Click to expand...
Click to collapse
No call recording feature as the lineage dialer is overridden for gapps, ie google dialer. Find a 3rd party app/mod. Sorry, I tried adding the option to allow the user to pick los dialer or google dialer, it but broke other things the majority of users need over call recording. Yes, 90hz support. 60/90 or auto
AnkeshReborn said:
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
Click to expand...
Click to collapse
It's easy. Use twrp, or unpack the bin file in the rom and flash with fastboot. same as other roms, just must format after install and reboot.
{
"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 a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
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. LineageOS does still include various proprietary hardware-specific code.
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. You can also view the Changelog for a full list of changes & features.
Information
This ROM uses source built kernel, kernel modules, and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware.
To use the eSIM you need to have GApps
Instructions
Follow https://wiki.lineageos.org/devices/lynx/install for how to install
Downloads
Official Builds
Optional GApps: MindTheGapps
Reporting Bugs
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/*
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Known Issues
Face Unlock, because Google doesn't provide an AOSP option.
Contributors
mikeioannina
nicknitewolf
The LineageOS team
Source Code: https://github.com/LineageOS
Great
Great. Thanks. Just got my Pixel 7a today.
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
Does the Play Store icon exist?
The GApps package may just install Play Services and the Play Store, from which you can install all optional Google apps.
Such packages avoid installing these apps as system apps, since you wouldn't be able to uninstall them without root.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
You have to reboot to recovery again for it to install on the correct slot
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
You can install Aurora Store and login there with your Google account.
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
sumdewd01 said:
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Click to expand...
Click to collapse
Wishmasterflo said:
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
Click to expand...
Click to collapse
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
mxz55 said:
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
Click to expand...
Click to collapse
No promises but we are waiting for June ASB
nicknitewolf said:
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Click to expand...
Click to collapse
This fixed it, thanks. I would like to mention that there are sone UI inconsistencies when it comes to the status bar, there's padding on one side and not the other, and when you go into the notification drawer (I think that's what it's called, swiping down from the status bar) the time and the date are not aligned by a little bit vertically. It's a small problem but still somewhat noticeable.
nicknitewolf said:
No promises but we are waiting for June ASB
Click to expand...
Click to collapse
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
mxz55 said:
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
Click to expand...
Click to collapse
Yes and yes. I am already part of the LineageOS team... Current builds are signed with test keys but official builds are signed with separate keys, hence a full wipe is required. You could try the zip attached but I doubt it works (since I don't really wanna test it).
nicknitewolf said:
Reboot into fastboot (With the device powered off, hold Volume Down + Power)
Flash
Click to expand...
Click to collapse
Just wanna say it should be "Reboot into bootloader", as the bootloader type of fastboot is required to flash some of the images: the dtbo, vendor_boot and vendor_kernel_boot partitions can't be read by pure fastboot (what's usually called fastbootD) mode and will throw this sort of error:
Warning: skip copying .. name .. image avb footer (.. name .. partition size: 0, .. name .. image size: .. ).
Sending '.. name ..' (... KB) OKAY [ 0.404s]
Writing '.. name ..' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
So anyone that got confused should just use `adb reboot bootloader` instead of reboot fastboot
I've flashed the ROM and so far it looks & feels really smooth, thanks!
Currently using GrapheneOS. Will flash LOS once they release a user build with release keys.