oZoP Development Projects are on the way!!!
ONE ZIP ONE PLACE
System Transition Animations mod
By flashing this zip you will be given a bunch of choices for different system animation style for screen/window transitions, keyboard/toast views and many others. You will get an additional option to tweak a little for unique styles!!
So I give you this, UNIVERSAL for MOST devices Aroma installer to give users the option for different choices!
This zip will work for MOST device running ANY Rom with ANY version Android 5.0+!
How to use the ozop-restore.zip to revert/recovery quickly without the need to restore or reinstall the whole Rom:
And just to be safe, I have included in my scripts and files a method that will create a flashable restore zip of your files before the mods does its thing!
The restore zip will be inside the new "ozop" folder that has been created and the zip is named "ozop-restore.zip"
If something doesn't play nice, just flash the zip and you'll be back to the way it was before you flashed the mod
NOTE: the script will delete any existing restore zips EVERY TIME you flash a new option, meaning that if you flash the mod again, your original system files will be replace with the file you flash previously!
If you want to have a permanent back up of the original file, you will need to rename the zip inside the ozop folder to whatever, just can't have the same name or it gets replaces everything you flash the mod
BUG REPORT:
Code:
MIUI choice causing boot issues for some users (works fine for me), so be prepared to you the restore.zip if needed. Will look into a fix for future releases
Report bug properly to get my support
Of course there are many way to properly report bugs and ALL of these ways have one thing in common, THEY ALL REQUIRE VERY DETAILED NOTES of the issue!
I'm not going to go deep into how detailed you could get because lets face it, most people that report improperly are the ones who don't read and probably are going to read this! HaHaHa...
To get support from me I only ask for some simple things
1. What device, and rom you are running
2. What is the issue (no boot, fc everywhere, fc only certain app etc...)
3. Which option did you select
4. Did you get the install log
5. Did you use the restore.zip option to get back running
6. Do other choices share the same effect
That looks like a lot, but it really is the minimum amount of info need to troubleshoot!
Provide me that and I'll do my best to fix things and make this fun for everyone.
If you post things like
"Doesn't work", "bootloop" or anyone other similar post that have no value and help development is no way, actually these kinds of post only put development behind and slow progress die the fact that anyone who cam help has to waste their time reading it!
If these kind of post ever come up, its best to ignore the lazy person and not clog the thread with flaming replies as that too slows development!
Anyway, I don't expect there to be many if any bugs! Been tested by myself and confirmed with users of this device!
Now grab the download and enjoy!
DOWNLOAD v1.1 HERE
SYSTEM ANIMATIONS PREVIEW PAGE:
Note: the animation have unique motions and some may look better with some minor adjustments to animations speeds. Some are better set to quick speed, others set slow. You will have to decide as per your needs.
You can access these adjustments via developer options in settings (activate if not shown by clicking about device/software version/build number 7 times)
List of the current animation:
COMPLETE SYSTEM ANIMATIONS
"oZoP Custom Missing Link Animations",
"Nexus 7 Ported Animations",
"Blur Animations"
"iOS Animations",
"Flyne OS Animations",
"Stock Animations",
"Google Pixel Animations",
"MIUI Animations"
ANIMATION ADJUSTMENT ADD-ON FOR POP-U AND DIALOG ANIMATIONS
"Bounce Style Dialog Animations",
"Drop In Style Dialog Animations",
"Flip in Flip mix Style Dialog Animations",
"Fold Style Dialog Animations",
"Slide Style Dialog Animations",
DEVICE COMPATIBILITY
Confirmed compatible devices for this version:
LG
OnePlus
Confirmed NOT compatible with the version:
?Samsung
PREVIEWS:
Credits:
spanna for the original vrtheme script
changelog:
v1.1
*added support for OnePlus and possibly more devices..
*cleaned up Aroma code
*added ext sdcard calculation to device info and mount info
v1a
*removed incompatible Samsung styles
*changed text style in Aroma UI
*fixed mounting
*fixed install log recording
v1
*initial release
XDA:DevDB Information
oZoP Development - System Animations, Theme for the OnePlus 3T
Contributors
stangdriver44
Version Information
Status: Stable
Stable Release Date: 2017-07-30
Created 2017-07-30
Last Updated 2017-08-06
Cool mod
Great... All in one place... Missing link is my favourite... Many thanks dev
Missing link animation is great.... Will try more animation on oos 4.1.6
Welcome
@stangdriver44, great to see you here! your amazing work for the Galaxy S6 was the only reason I kept it for as long as I did. Ultimately touchwiz killed me and I switched to the 1+3T.
Miui animation giving bootloop...
Does it provide Miui recent apps horizontal thumbnails style?
Sent from my LG-H870DS using XDA-Developers Legacy app
Does it require root and trwp?
PashaF said:
Does it require root and trwp?
Click to expand...
Click to collapse
Yes
---------- Post added at 08:41 PM ---------- Previous post was at 08:41 PM ----------
EMJI79 said:
Does it provide Miui recent apps horizontal thumbnails style?
Click to expand...
Click to collapse
No
Whoever wish to use this theme first pls make sure that u took a original backup of system animation as said by OP otherwise you can stuck on bootloop. However most of the animation is working on my oos 4.1.6
It broke most of my apps running 7.1.2 resurrection remix CAF version with stock kernel (whatsapp, contacts, playstore, GMS) , i had to revert back using the restore zip and waiting for it to boot up. thanks anyway.
OP updated with the Preview page
SYSTEM ANIMATIONS PREVIEW PAGE:
I am also looking at the MIUI animations that some users are having trouble with.
Hopefully a fix and possibly more animation options coming soon...
stangdriver44 said:
OP updated with the Preview page
SYSTEM ANIMATIONS PREVIEW PAGE:
I am also looking at the MIUI animations that some users are having trouble with.
Hopefully a fix and possibly more animation options coming soon...
Click to expand...
Click to collapse
hope you can make this more modular, i like missing link keyboard animation, and like ios transition
so for now i use missing link + drop down transition
hope more option coming on next release
Missing link and iOS animations worked fine for me on RR . Using missing link right now. Missing link working on my son's nexus 6 running RR as well
Now my smartphone looks much better.
I use the Nexus 7 Style.
Thank you for your work .
Can you add the OxygenOS animations? The fading etc that they add is very nice.
I can't flash the zip through TWRP, when i try it says that it cannont be installed and it gives me error 255.
Model: Asus Zenfone 2 Z00A
ROM: LineageOS 14.1
I tried mutiple times and also tried moving the zip from the SD to internal storage but it gave me the same error again.
I really hope you can help me because i really want those iOS animations since LOS ones suck.
OBS: This is the only info i can give to you since i can't even see the Aroma GUI, the error happens as soon as i try to flash the zip.
Edit: Through a little research i now think is because me phone is x86 and not arm, would you kindly make it x86 compatible? Please?
Edit 2: Here's the recovery log i copied right after the error appeared: https://pastebin.com/6q1cwdeA (the flashing process starts at line 1022)
Edit 3: Managed to fix the 255 error by replacing the "update binary" file with one compatible with x86 (from lineageOS). But now i get another error, this time error 6, which apparently has something to do with the "updater script" file i think.
lucassilvas1 said:
I can't flash the zip through TWRP, when i try it says that it cannont be installed and it gives me error 255.
Model: Asus Zenfone 2 Z00A
ROM: LineageOS 14.1
I tried mutiple times and also tried moving the zip from the SD to internal storage but it gave me the same error again.
I really hope you can help me because i really want those iOS animations since LOS ones suck.
OBS: This is the only info i can give to you since i can't even see the Aroma GUI, the error happens as soon as i try to flash the zip.
Edit: Through a little research i now think is because me phone is x86 and not arm, would you kindly make it x86 compatible? Please?
Edit 2: Here's the recovery log i copied right after the error appeared: https://pastebin.com/6q1cwdeA (the flashing process starts at line 1022)
Edit 3: Managed to fix the 255 error by replacing the "update binary" file with one compatible with x86 (from lineageOS). But now i get another error, this time error 6, which apparently has something to do with the "updater script" file i think.
Click to expand...
Click to collapse
This mod is made keeping the OnePlus 3T in mind, buddy. You should have expected it to not work on the ASUS Zenfone. Moreover, ARM - x64 v/s Intel - x86 (32 bit). It was bound to fail.
No updates??
Will it work on one plus 3t 5.1 oxygen os
Related
As a fan of Deus Ex Human Revolution game I was trying to theme my Nexus 10 for some time. Using combination of UCCW, live wallpaper (by Makomako) and android theme by Ramazor I’ve almost reached my goal – last thing that wasn’t themed was recovery. Lucky for me TWRP comes with fantastic theming system.
I’ve made theme based on Deus Ex HR game interface for TWPR 2.6.3.0.
It probably won’t work with older versions! I do not recommend using it with any older version than 2.6.3.0!
Features of landscape version (2560x1600):
Menu:
This theme has live main menu on left, which means it is slightly different from stock “page by page” display. In my theme it is possible to jump between different active pages – it will cancel all selected actions and reset variables, though. So, basically it is equal to pressing “Home” and “page” button in stock theme.
Keyboard layout:
Added numeric keyboard
Terminal Command – keyboard shortcuts:
e2fsck - As I’ve had few times problems with restoring backups and my tablet basically froze in recovery mode, I thought it will save me connecting to PC and doing it via ADB. After performing e2fsck on all partitions (usually DATA was most affected) I could restore backups or flash new roms.
It is important to unmount partitions first, otherwise e2fsck will report mounted partition and exit. It could be done either from \Mount menu or another “shortcut” in \Advanced\Terminal command\e2fsck. These “shortcuts” require pressing “ENTER” button on keyboard.
This theme was designed to use on Google Nexus 10 and as such I’ve added only mmcblk0p7, mmcblk0p8, mmcblk0p9 to umount and e2fsck “shortcuts”.
If any one will ever use this theme on any other device, those commands might not work!
CLS button:
If anyone do not like “swipe left to clean” feature, I’ve added CLS button, which cleans typed characters in command line. (CLS is available only in Terminal command window!)
Remove theme:
If one will have any problems with this theme or will get bored with it, it could be removed and recovery will reload stock theme without rebooting recovery. (File will be renamed to “ui_DeusEx.zip” but TWRP won’t load it anyway – to restore it simply rename it back to “ui.zip” and reload theme).
Portrait version (768x1280, 720x1280, 1200x1920):
Remove theme option (as above).
It was tested by me on Google Nexus 4 phone and Google Nexus 10 tablet. It should work on any device with the same screen resolution.
Theme comes in 2 color variants: orange (Deus Ex) and holo (I rather should say: “holo-ish”).
As files are quite big, please verify checksum after download.
Installation:
Download selected version, verify checksum, rename file to ui.zip, copy via file manager or adb push to /sdcard/TWRP/theme/
Disclaimer
Theme was tested only by me as far as I could and I didn't have any problems with it but I do not take any responsibility for any data loss or other damage. Use it on your own risk!
I will appreciate feedback. I can respond to questions\queries on evenings as I’m working and do not have too much spare time.
UPDATE 1:
Theme now supports TWRP 2.6.0.0.
UPDATE 2:
Removed confirmation windows from Power Menu actions (restored stock function: "No OS installed!" warning message in case of no data on /system partition) - thanks to Nezorflame for pointing it out
Added "(sort of) Holo colors" variant - thanks to halrulez for suggestion
Holo colors: basically only orange color has been replaced with light blue plus new background image to match it.
UPDATE 3:
It's actually a small correction on both themes. I left mount USB storage with disabled condition and it was shown even on devices without that function (i.e. Nexus 10), I'm sorry!
UPDATE 4:
Another detail that I missed previously was corrected (one of consoles windows was slightly adjusted) , added "Inject TWRP" and "Re-inject TWRP" options (it will be visible on supported devices, I can't see it on my both Nexuses). Added phone (portrait) versions.
UPDATE 5:
- Added 1200x1980 pix version (portrait), file has upscaled bitmaps and that bloated it up to 10MB. I do not want to re-make any of the images because it would take a lot of time (which I do not have right now), sorry.
- 1200x1980 version has different keyboard (removed keyboard background, highlighted buttons)
- All portrait themes were updated to TWRP 2.6.3.0. Landscape is still for TWRP 2.6.0.0, I was too focused on fixing portrait versions and completely forgot to update it, sorry! I'll do it ASAP.
- All portrait files can be found on my dropbox folder, link below.
UPDATE 6:
- All themes (lanscape and portrait) are now compatible with TWRP 2.3.6.0.
- In landscape theme Settings menu items were slightly rearranged.
UPDATE 7:
- Fixed "Copy" button position in 768x1280 themes (both variants)
- Fixed "File" icon not showing up in 768x1280 themes (both variants)
UPDATE 8:
- Added MultiROM support for 768p themes (Nexus 4)
- Added "restoreDeusEx.zip" file for restoring theme after use /ADVANCED/Theme tools/Rename theme file option: file can be flashed from stock theme (or any other) but will overwrite any existing ui.zip in Theme folder.
- Added batch "ADB_DE_push.bat" file for simpler theme install: just copy whole selected folder on your PC and run ADB_DE_push.bat file. Along with "ui.zip", "restoreDeusEx.zip" will be copied to /sdcard/TWRP/theme (folder will be created if there isn't one already).
UPDATE 9:
Themes for 768p, 720p, 1080p (portrait) devices as well as Nexus 10 (landscape) are now updated to TWRP 2.7.0.0 (that includes small changes to Settings page). MultiROM version will follow soon.
(I do not have Nexus 7 (flo) on me at the moment, so I wasn't able to test it properly)
Important!
Sorry guys, look's like it will gonna take some more time to fix phone themes - I'm removing them for time being.
I hope I'll be able to make it work.
Please stop use it for your devices safety!
Files were fixed as far as I could - no one reported any problems, neither I had any, so I can assume, that everything is fine.
If anyone will have any problems with theme, please post details and I'll try to fix it.
There are some issues with TWRP 2.6.3.1 on Nexus 10 at least with ROMs based on CM (partition problems, freezes).
These are not theme related and I can't fix it. I recommend not to upgrade TWRP now, please wait for at least 2.3.6.2 version.
I do not intend to produce any other versions for different devices.
But feel free to do it yourself, just keep my nick in xml.file
Information:
There is no chance I'll be able to make updates to MultiROM version or any other version of theme. I simply do not have time and I need to focus on other things right now Sorry!
I'd like to thank all of you for support and all help that you've given me!
If anyone wants to take over please let me know - I can share source files in PSD format.
Below you can find link to all the PSD files, feel free to use them. Please read info.txt. Good luck!
https://www.dropbox.com/sh/1b3kqiijornl95o/AAClEBfnw2Ky8gTvGsmScgsha
I do not take responsibility for any moded/updated theme!
Download:
All files could be found on my dropbox folder:
https://www.dropbox.com/sh/hemfcd28oz1qtaq/0Xe8ZQUxwb
Checksums for all files can be found in checksums.txt file.
Please always verify checksums after downloading theme files!
Wow.
Beautiful theme.
Will give it a try. Thx!
Even though I don't follow the Deus Ex franchise, I can say that this looks absolutely cracking!
Will try this on the first thing when I get some free time with my N10 tomorrow.
Thanks! I forgot to mention that there are two sliders - one you can see on lockscreen preview in first post, other is bigger and thing that should be touched/swiped is that light blue cube on the left. It sounds a bit cryptic but you'll get it when you'll see it.
I removed a prior theme I had from the TWRP theme folder and replaced with this theme. Upon reboot recovery all I get is reboots to the TWRP loading screen. The loading screen is the prior theme though so it seems like its still trying to load the older theme that I removed and replaced with this theme.Any help or do I need to reflash. Not a big deal since I want to try the new 4.3 Factory anyway. Since I cant get into TWRP Recovery it seems I'll have to go back to stock and start over.
Dude I totally love this theme. Took TWRP to a whole new level. Wish the was a good theme for smart launcher to match it.
Sent from my Nexus 10 using Tapatalk 2
Great Theme, e2fsck shortcuts are really handy too :thumbup:
Sent from my Nexus 10 using Tapatalk HD
NICE! I love the Deus Ex HR interface style. Makes me dream of a world where you are just as technological as your computer...
You did a marvellous job there, the theme makes perfect use of the screen!
Could you give me a hint on how I can also get an android framework with solid xhdpi theming?
momulah said:
I removed a prior theme I had from the TWRP theme folder and replaced with this theme. Upon reboot recovery all I get is reboots to the TWRP loading screen. The loading screen is the prior theme though so it seems like its still trying to load the older theme that I removed and replaced with this theme.Any help or do I need to reflash. Not a big deal since I want to try the new 4.3 Factory anyway. Since I cant get into TWRP Recovery it seems I'll have to go back to stock and start over.
Click to expand...
Click to collapse
Sorry to hear that but I'm afraid I can't really help you - it didn't happen to me. You can try to push ui.zip via adb again as adb should be working even with TWRP curtain image stuck on screen. Maybe file was corrupted or something...
halrulez said:
Dude I totally love this theme. Took TWRP to a whole new level. Wish the was a good theme for smart launcher to match it.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks
I'm using these:
theme - https://play.google.com/store/apps/details?id=com.ramazor.theme.freedeax
icons - https://play.google.com/store/apps/details?id=com.badwolf.grey.deus.ex
live wallpaper - https://play.google.com/store/apps/details?id=com.mako.goldlite
plus few widgets that I've made for UCCW and it's almost perfect :laugh:
Still, I'd like to see a proper skin for android that would use similar interface...
pingguo said:
NICE! I love the Deus Ex HR interface style. Makes me dream of a world where you are just as technological as your computer...
You did a marvellous job there, the theme makes perfect use of the screen!
Could you give me a hint on how I can also get an android framework with solid xhdpi theming?
Click to expand...
Click to collapse
Not really I was able to make TWRP theme as it was quite easy (xml there is simple and hardest thing was creating images). Things you're looking for are way out of my league.
Awesome theme. Now you should make a CM 10 theme using the same theme
Sent from my Nexus 10 using Tapatalk 4 Beta
Im using TWRP latest and I cant get it to boot with the theme. ui.zip placed in themes folder but it just boots to the TWRP load screen and stays there.
Sorry to hear that, I can't really help you with that. I do not have any problems with it and nobody else reported any problems.
Does it boot normally without it? Does it work with any other theme for 2.5.0.0? Can you run e2fsck on your sdcard via adb (make backup of your data on other storage before that!)? I've added shortcuts for e2fsck because I had problems with restoring backups but other people reported similar problems with their data or partitions on TWRP 2.5.0.0 (some of them went back to older versions). Can you repack ui.zip and try with it? Last one is a long shot... Otherwise, I do not know what else could be done, sorry.
Hatman41 said:
Awesome theme. Now you should make a CM 10 theme using the same theme
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Have you seen this one: http://forum.xda-developers.com/showthread.php?t=1673652
Making proper CM theme is beyond my skill, I'm afraid.
Kraliz said:
Sorry to hear that, I can't really help you with that. I do not have any problems with it and nobody else reported any problems.
Does it boot normally without it? Does it work with any other theme for 2.5.0.0? Can you run e2fsck on your sdcard via adb (make backup of your data on other storage before that!)? I've added shortcuts for e2fsck because I had problems with restoring backups but other people reported similar problems with their data or partitions on TWRP 2.5.0.0 (some of them went back to older versions). Can you repack ui.zip and try with it? Last one is a long shot... Otherwise, I do not know what else could be done, sorry.
Click to expand...
Click to collapse
Neva mind for some reason it didn't download the whole theme. I re downloaded and it worked. Looks really nice but seems slower...best theme i'm seen so far though. Thanks.
momulah said:
Neva mind for some reason it didn't download the whole theme. I re downloaded and it worked. Looks really nice but seems slower...best theme i'm seen so far though. Thanks.
Click to expand...
Click to collapse
Great! :good:
Kraliz said:
Great! :good:
Click to expand...
Click to collapse
It even works fine with 2.6 guys
Sent from my Nexus 10 using Tapatalk 2
halrulez said:
It even works fine with 2.6 guys
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, good to know. I've updated TWRP on my tablet and I'll check for any changes in stock theme later.
Kraliz said:
Thanks, good to know. I've updated TWRP on my tablet and I'll check for any changes in stock theme later.
Click to expand...
Click to collapse
Would this be awesome if it had the holo colors instead on the orange. I love it the way it is don't get me wrong. Any chance for different colors?
Sent from my Nexus 10 using Tapatalk 2
Beware of googleys
FRANK
Layers
Day/Night theme switcher from first M preview
Init.d support
Advanced reboot
SuperSu 2.52 flashed with the rom
Volume rocker wake
Volume rocker cursor control
Long press quick settings control
Stock Like feel, please don't ask for features
Installation
Roms can change from update to update that sometimes you can dirty flash but if you have errors that other users don't then you will have to clean flash
First Time Installation:
Download the ROM and Other Optional files below.
Connect your Nexus 5 to the PC and transfer all the zips to the root of your device’s storage.
Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
Wipe the following partitions: System, Data and Cache
Install the ROM zip file
Let it boot. Setup now and wait for the ROM to settle.
Reboot into Recovery again and Install the remaining zip files.
Updating from previous version:
1.Download the ROM and Other Optional files below.
2.Connect your Nexus 5 to the PC and transfer all the zips to the root of your device’s storage.
3.Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
4.Wipe the following partitions: Dalvik-cache and Cache
5.Install the ROM zip file
6.Reboot now
7.Let it boot. Setup now and wait for the ROM to settle.
8.Reboot into Recovery again and Install the remaining zip files.
9.If have issues with dirty flash, reboot and redo steps wiping DATA also
Sources
Hammerhead GPL Kernel Source: prebuilt aosp marshmallow n5 kernel in aosp source
Rom Source: Click here
Changelog
Code:
10-19
Minor update
enable systemui tuner by default
add scanning menu into location
speed up recent app back
sprint fix included
Copy pasta from mako changelog
10-15-15
Minor update
added aldy's kernel in and turned back on usb-otg in fstab (n4)
added minkin text layout engine in thanks to @ckret for pointing it out (hammerhead had this already)
10-14-15
bug fixes!!!
some changes on the device tree so anyone using it should update
can build with clang now thanks to @ckret for pointing out the fixes (we are still gcc compiled)
Fixed downloads dark theme thanks to Branden M
Fixed supersu and layers icons being off on the dark theme, thanks Branden again
ambient display color layers inversion fix up ported from lollipop
Fix annoying usb mounting to computer (Thanks to snak3ater pointing this out to zephik)
10-13-15 update-1
added volume rocker wake (in settings/display to turn on)
add volume rocker cursor control
added animation transition animations of .25 and .75
set default animation speeds to .75
added long press recent button switches to the last app
removed the spinner from optimizing apps dialogue so it is quicker at dexopting
added long press on quick settings tile takes you to their settings menu
minor sepolicy fixes
disabled the after flash image verification (was breaking multirom flashing)
10-13 build
Fixed mac address bug thanks to this pull request
https://github.com/marshmako/device_lge_mako/commit/49b11281e25e434d7f56c4677e663e8dff87ccad
Fix a bad copy pasta of the init usb midi support
12-12
Added ambient display and full rotation
removed some debugging code
sped up a few things
Frank 10-12-15 with theme switcher, update 1
added google exchange services included in the build, it replaces exchange2
should be able to remove the layers manager icon from the launcher now
removed cell broadcast receiver
added the locked update receiver commit
beanstown found a line to set doze power saving mode that was set to off in aosp so turn it on
https://www.androidfilehost.com/?fid=24052804347836304
10-12 theme switcher update
added day/night theme switcher back to dev settings like what was in M dev preview 1 (only does settings, bluetooth and package installer so we will have to expand on this for layers), will prob move the switch out to the dashboard below layers or some place later.
added https://github.com/BenzoRom/framewor...54a3aa73367bde which should give core google apps default permissions out the box (you might still have setup wizard bug though)
Your current layers themes will only work properly in light mode
new in 10-11-2015
Removed art optimize everything till we have fully deodexed gapps
advanced reboot
init.d support
supersu and layer manager embedded in setting (you need layers manager of course) (forgot to add the hide icon part )
too tired for the rest so just read the commit history if you wanna know more https://github.com/marshmako/platfor...b5b1c3bc4419da https://github.com/marshmako/platfor...6896b4d256a871 pretty much just kanged a bunch of commits from zephik there.
new in update 1.
fixed init.d, removed aosp clock and aosp mms apps. Use updated and better google versions
added missing files for miracast
Downloads
Current Build = https://www.androidfilehost.com/?fid=24052804347841653 10-19-15
Gapps = https://www.androidfilehost.com/?fid=24052804347841244 Txuki
or
Gapps = https://www.androidfilehost.com/?fid=24052804347841070 banks
Backup Gapps down below if those don't work
gapps without setup wizard if you get wizard fc upon boot thanks to barome (modifed version without setup wizard of above)
just access play store to be able to log in with your google account
http://renderserver.net/?dl=6455ad109b871809d8f34b25a92f6904
For those interested in the commits for the theme switcher
https://github.com/marshmako/platfo...mmit/da669b1ebda7ee8ac7a39d181eb944290ce9ea72
https://github.com/marshmako/platfo...mmit/00b529c60d31e554b9c090c03f02ce06a652135a
https://github.com/marshmako/platfo...mmit/3c683a0124129bda309615a281fc3feb3ec58fde
https://github.com/marshmako/platfo...mmit/22c13d6bfd5dee4843a6fdca953350d7f56b7066
https://github.com/marshmako/platfo...mmit/4f298e8f8ab2c08f0e8c4ae92da72b01e0db6b5d
https://github.com/marshmako/platfo...mmit/4136e2ff29a84be80f8bf7f83a357fb0342e6718
Click to expand...
Click to collapse
Current layers themes will only work on light themes until adapted
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
XDA:DevDB Information
[L][5.0] Frank N5 - Aosp builds in testing [1-11-2015], ROM for the Google Nexus 5
Contributors
sykopompos, bgill55
Source Code: https://github.com/marshmako
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Stable
Created 2015-02-27
Last Updated 2015-10-19
Reserved
[/HIDE]
nexus devices threads
Mako
http://forum.xda-developers.com/nexus-4/development/lpv-79-mako-port-beta-t2807446
deb
http://forum.xda-developers.com/nex...e/l-android-lpv-dev-deb-t2856915#post55016443+
flo
http://forum.xda-developers.com/nex...id-lpv-dev-flo-enhanced-t2856920#post55016534
hammerhead
http://forum.xda-developers.com/google-nexus-5/development/l-android-lpv-dev-n5-enhanced-t2856934
Look @vomer 's op for a general FAQ for L preview as those apply here along with other downloads for radio, bootloader, etc (maybe looking for my permissive boot.img or art tweaks, they are there)
http://forum.xda-developers.com/google-nexus-5/development/rom-n5-l-developer-preview-t2796003
good morning.. i will try in multirom.. thx a lot!
Best regards
Craxx
Send from my Nexus 5 with Tapatalk
Woot woot! Glad it is stable now. Kudos and great job!
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
Question. Can we now straight flash L kernels without you modifying the ramdisk? Like code blue, arkenstone etc etc?
eluspo said:
Woot woot! Glad it is stable now. Kudos and great job!
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
Question. Can we now straight flash L kernels without you modifying the ramdisk? Like code blue, arkenstone etc etc?
Click to expand...
Click to collapse
Nope. Still need the any kernel version because of how heavy of ramdisk edits that there is.
The whole ramdisk is aosp and modified for permissive selinux so flashing a boot image will crash out the whole system.
@ramjet73 is working on a ramdisk injector to replace the ramdisk in kernels that do a complete boot.IMG
WOw.... downloading .... :laugh:
sykopompos said:
Nope. Still need the any kernel version because of how heavy of ramdisk edits that there is.
The whole ramdisk is aosp and modified for permissive selinux so flashing a boot image will crash out the whole system.
@ramjet73 is working on a ramdisk injector to replace the ramdisk in kernels that do a complete boot.IMG
Click to expand...
Click to collapse
I think im going to use your modified code blue kernel for now. Thanks a lot for bringing this smoothness to n5 L.
I forgot to add in the op and will. If you are coming from the official L preview, you might experience a bunch of force closes on first boot. Just reboot about twice and it will settle down.
This is some funkiness involving selinux getting switched over to permissive.
eluspo said:
I think im going to use your modified code blue kernel for now. Thanks a lot for bringing this smoothness to n5 L.
Click to expand...
Click to collapse
shhhhh there isn't supposed to be any modified versions of his kernel distributed outside his thread, u saw how grumpy he got that we even did a test one
Will I loose my SD card by flashing this
Sent from my Nexus 5 using xda premium
sykopompos said:
shhhhh there isn't supposed to be any modified versions of his kernel distributed outside his thread, u saw how grumpy he got that we even did a test one
Click to expand...
Click to collapse
Okay haha i will be discreet about it. We dont him attacking this thread ??
stewartk said:
Will I loose my SD card by flashing this
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
It will behave exactly like the preview would when it comes to the sdcard so no you shouldn't. I don't have a n5 so o don't know if that behavior is in the preview or not.
I haven't heard anyone say anything about it on mako coming from kit kat
eluspo said:
Okay haha i will be discreet about it. We dont him attacking this thread ??
Click to expand...
Click to collapse
Yes please. He made his wishes clear. Ramjet is working in the injector which will do a reverse anykernel basically and replace the ramdisk like I did in the test.
This could be solved if the L kernel guys made a anykernel version instead of a full boot image so it wouldn't touch my ramdisk.
A lot of the magic that makes it so smooth is in the ramdisk.
sykopompos said:
Yes please. He made his wishes clear. Ramjet is working in the injector which will do a reverse anykernel basically and replace the ramdisk like I did in the test.
This could be solved if the L kernel guys made a anykernel version instead of a full boot image so it wouldn't touch my ramdisk.
A lot of the magic that makes it so smooth is in the ramdisk.
Click to expand...
Click to collapse
Okay okay haha. I can definitely feel that magic in this rom.
eluspo said:
Okay okay haha. I can definitely feel that magic in this rom.
Click to expand...
Click to collapse
Well I believe you were on the left over bunny stew so you could see the difference between the ramdisk difference and the the rest so you should be able to tell how much just the ramdisk does and then the evolution to what it is now and what makes it the complete picture.
Bet you love those 20 second boot times though
Anyways, time to get some sleep. It has been a long night and I'm hitting the caf stuff at every turn in the 1+1 L port and it is giving me a headache just thinking about it.
I'm gonna hang out with my son all day tomorrow so I won't really be on
sykopompos said:
Well I believe you were on the left over bunny stew so you could see the difference between the ramdisk difference and the the rest so you should be able to tell how much just the ramdisk does and then the evolution to what it is now and what makes it the complete picture.
Bet you love those 20 second boot times though
Anyways, time to get some sleep. It has been a long night and I'm hitting the caf stuff at every turn in the 1+1 L port and it is giving me a headache just thinking about it.
I'm gonna hang out with my son all day tomorrow so I won't really be on
Click to expand...
Click to collapse
Thanks man! Get some sleep. Have fun with your son.
Just flashed, works flawlessly, thanks for this great build!
BTW guys, you can use SuperSU, I just haven't gotten around to merging it in to replace koush's before SuperSU worked properly when fully permissive. Just make sure you use 2.02 or higher
Just an FYI, permissive just logs and doesn't actually deny anything so you will see the avc denied in logcats but it does go through.
I gotta tune the policy for hammerhead as I just did a basic aosp one for it
How would I get the home button to work. Its there just doesn't work
Sent from my Nexus 5 using xda premium
First, let's give credit where credit is due. @ZeNiXxX and @SKULSHADY are the developers of this ROM. Additional credit goes to @phhusson and @Dil3mm4 as well as:
LineageOS Team (https://www.lineageos.org)
AICP (https://www.aicp-rom.com)
MSM-Xtended Team (https://forum.xda-developers.com/one...0-pre-t3693585)
Crdroid (https://crdroid.net)
Omnirom (https://omnirom.org)
And all the other Developers, Testers, Donators and Users.
The source code which can be reviewed and continued too can be located here https://github.com/Havoc-OS and https://github.com/Havoc-Devices You can request features https://goo.gl/forms/b8rY79XtUZnd5ji42 Announcement are made here https://t.me/Havoc_OS and additional support can be requested here https://t.me/havocofficial. Finally, the official Havoc-OS page can be located here https://sourceforge.net/projects/havoc-os/files The original official thread is actually located here and was originally posted by @EnesSastim and an updated thread can be found here originally posted by @mountaser halak I, myself, @MotoX4 did full testing in verifying the support of MotoX4 having tested on several XT1900-1 (both Andriod One, Amazon Moto Retail, and * Project FI).
However, the purpose of this thread is only to bring awareness that MotoX4 users (such as yourself) do have another ROM to choose from and to include full instructions on how to install this on your MotoX4 device.
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.
*/
Not working:
Tethering
- You tell me
FEATURES:
Code:
[SIZE="4"][B][U][SIZE="5"]General:[/SIZE][/U][/B]
System-wide Rounded UI
Full OMS support
System-wide burn-in protection
Spectrum support
Compiled using SDCLANG
Razer Phone lock/unlock sounds
OTA support
Signature spoofing
Micro-G support
[SIZE="5"][B][U]Included Apps:[/U][/B][/SIZE]
AdAway
Google Calculator
Google Markup
Lean Launcher
[SIZE="5"][B][U]Settings:[/U][/B][/SIZE]
[B][U]Battery:[/U][/B]
Battery performance profiles
Sensor block per-package
Wakelock blocker
Alarm blocker
Optimal charge level alert
[B][U]Display:[/U][/B]
Live display (Day/Night/Outside)
Colour profiles (sRGB, DCI-P3)
Font manager
Ambient display
Always on display
Expanded desktop
[B][U][SIZE="5"]Havoc Settings:[/SIZE][/U][/B]
[B][U]Status Bar:[/U][/B]
Quick pulldown
Smart pulldown
Tap to sleep
Brightness control
Battery icon styles
Bluetooth battery status
Battery bar
Battery saver color
Clock & date options
Statusbar logo
No sim network hide
Disable no sim icon
Volte icon
Network icon customization
Net activity
Custom carrier label
System icons
[B][U]Panels:[/U][/B]
Power menu tweaks
Volume dialog tweaks
[B][U]Quick Settings:[/U][/B]
Brightness slider customization
QS panel footer customization
QS layout editor
Custom header images
[B][U]Notifications:[/U][/B]
Disable fc notifications
Force expanded notifications
Disable immersive mode messages
Kill app button in notification
Screen-on notifications
Toast icon
Toast animation
Toast icon color
Toast text color
Heads up toggle
Heads up timeout
Heads up blacklist
Heads up stoplist
Snooze timer
Statusbar ticker
Ticker animation
In-Call vibration options
Less annoying in-call notifications
[B][U]Recents:[/U][/B]
Stock recents customization
Clear all button customization
Memory bar
Recent styles
Hide apps from recents
Icon pack
Immersive recents
Recents layout (Stock/Grid/Android Go)
OmniSwitch
Slim recents
[B][U]Interface:[/U][/B]
Berry styles (Light/Dark/Black/Auto)
Blur personalization
Dashboard suggestions
Dashboard conditions
Screen stabilization
[B][U]Lockscreen:[/U][/B]
Charging info
Hide statusbar
Lockscreen elements visibility
Notification count
Lockscreen colors
Clock and date options
Lockscreen alpha
Double tap to sleep
Wake and unlock
Ambient display music ticker
Ambient display bottom view (Weather/Battery/None)
Music cover art
Music visualizer
Disable power menu
Disable qs panel
Fingerprint vibration
FP unlock on boot
Face auto unlock
Custom bottom shortcuts
[B][U]Navigation:[/U][/B]
Navigation mode(Stock/Smartbar/Fling)
Dynamic navbar color
Pulse
[B][U]Buttons:[/U][/B]
Swap back and recents
Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer)
Accidental touch
Power menu customization
Long press power button torch
Disable buttons
Button backlight customization
Hardware keys customization
Swap volume buttons with rotation
Volume keys for media volume
Playback control
[B][U]Gestures:[/U][/B]
Three finger screenshot
Pie control
App circle bar
Gesture anywhere
Screen-on gestures
Touchscreen gestures
[B][U]Animations:[/U][/B]
System Animations
Android P animations
Disable animations
QS tile animations
Listview animations
Custom Bootanimation
Screen off animation
[B][U]System:[/U][/B]
SELinux mode Toggle
Smart Pixels
Suspend actions
System app remover
Allow untrusted overlays toggle (for Substratum Support)
CPU info overlay
[B][U]IME Settings:[/U][/B]
Selector notification
Auto keyboard rotation
Disable fullscreen keyboard
[B][U]Weather:[/U][/B]
Weather service settings
Statusbar weather
Lockscreen weather
[B][U]Miscellaneous:[/U][/B]
Screenshot editor
Wake on plug
Pocket detection
Camera shutter sound
Disable safe headset volume
Launch music App on headset Connection
Scrolling cache
Events[/SIZE]
How to install Havoc-OS on Moto X4
!! Please read before proceeding !!
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
!! You will be wiping everything because regardless if you are coming from stock or a different ROM as this ROM works best with a full wipe !!
Note: If upgrading this ROM a full wipe is not necessary. See upgrade instructions below.
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), select "advanced wipe" to wipe your device (select all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
If coming from stock:
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Continue:
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest Amr64 A/B ROM located here: https://sourceforge.net/projects/havoc-os/files/arm64-ab/ - NOTE: You want the ROM that comes without Gapps. You can install Gapps after (see instructions below).
Extract the zip (XZ file) onto your computer. -- I suggest the free and open source program 7zip https://www.7-zip.org/
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img /sdcard/
In TWRP select Install *
Select Install image
Locate your .IMG file and flash it to "SYSTEM"
* TWRP troubleshooting:
A small group of individuals has reported that TWRP will not correctly install IMG files directly. If you're one of those few people a manual install may work for you.
First wipe your phone again
Reboot back to bootloader. - Stay at bootloader
As an administrator on windows or as root on Linux run this command
Code:
fastboot -u flash system Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
Credit to @*.jpg for this solution.
NOTE: Do NOT yet install Gapps. See instructions below.
After a successful install, REBOOT your phone.
Congratulations, you're done!
If adding Gapps: -- Read me
Your phone will work perfectly fine without Gapps. But if you do want to install Apps and use Google products and services; I recommend the minimal Gapps install known as Pico. You can learn about the many different Gapps flavors by visiting the Open Gapps Wiki found here https://github.com/opengapps/opengapps/wiki/Package-Comparison
Let your phone boot the ROM for the 1st time. - !! IMPORTANT !! You want to fully boot your phone and let the ROM load for the 1st time before installing Gapps.
After your phone as successfully booted up and loaded the ROM, reboot back into recovery
Download the latest Gapps - https://opengapps.org
Upload the zip to your phone
Install Gapps
Wipe cache/dalvik
Additionally, if you're one of those paranoid people who want to keep your distance away from Google (to each their own, but I love me some Google ) you do have the following alternatives.
https://apkpure.com/
https://en.uptodown.com/android
https://f-droid.org
Just remember that these are unofficial sources and you take the risk that can potentially come with them.
UPGRADING - How to upgrade this ROM.
Also known as a dirty upgrade, you do not need to wipe everything and start over. However, if this dirty upgrade fails a fresh install is recommended.
Download the latest ROM
Reboot into recovery
Install your new .img file
Wipe cache/dalvik
Reboot
If all has gone well you're done! If not, a full wipe and install are recommended.
* Project Fi
If you do not have Google Project Fi as your cellular provider, you can ignore this.
The Google Project Fi app will inform you that you cannot activate using this GSI/Rom. Assuming, you have already previously activated your phone before trying out new GSI/ROM's, you can technically, safely ignore this warning as you will still be able to send and receive calls, text, data, etc... and continue to use the Project Fi app to manage your account. However, if this is your first time activating or you simply wish to be sure you get the latest carrier and tower updates (recommended), this fix is for you.
First let's give credit where credit is due. @Sass86oh for originally coming up with this fix here and a personal thanks to @johnjingle for pointing this out to me here.
Google Project Fi Fix
You will need to make a minor and yet important edit to your system before installing the Project Fi app. If you have already installed the Project Fi app before making this edit, you should close the app, clear both the app's cache and clear the app's storage, then proceed to uninstall the Project Fi app.
Using your preferred root text editor navigate to /system/
Locate the file build.prop
Carefully make the following changing, listed below, to the file build.prop
!! Important !! Double check you have correctly made the correct changes.
Save your changes
REBOOT your phone
Go to: Setting > System > About
Verify that your device model is a Moto x4
Install Project Fi
Open Project FI and proceed with the activation
Congratulations, you're done!
!! IMPORTANT !! These values are CASE SENSITIVE which means if you type "Payton" rather than "payton" it will NOT work !! Be sure you double-check what you type before saving !!
Locate and edit to match. -- Do NOT rush (Do NOT be in a hurry). This is something you want to carefully take your time with.
Code:
ro.product.model=Moto x4
ro.product.brand=Motorola
ro.product.name=payton
ro.product.device=payton
ro.product.manufacturer=Motorola
ro.build.product=payton
ro.opa.eligible_device=true
Headphone jack fix found here. credit: @abrfilho
????
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
abrfilho said:
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
Click to expand...
Click to collapse
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
SchmilK said:
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
Click to expand...
Click to collapse
Yeah, when I was using phh's Pie AOSP I was able to use the wide lens, even on modded GCam, but here I'm not able. ?
I already installed Moto Camera here.
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
*.jpg said:
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
Click to expand...
Click to collapse
How can you do that? I think I can't just fastboot flash havoc.....img right?
I installed via TWRP, but I am stuck at the android loading screen. I will try to re-flash I guess.
khanhlinh said:
How can you do that? I think I can't just fastboot flash havoc.....img right?
Click to expand...
Click to collapse
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
Code:
fastboot -u flash system [*your GSI here*].img
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
Click to expand...
Click to collapse
You can flash Magisk without a problem.
khanhlinh said:
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
Click to expand...
Click to collapse
I am having the same issue, except I get to the android text sometimes. I have tried installing the rom with gapps and w/out.
Not sure what I am doing wrong I came from Lineage trebelized and I did wipe everything even internal storage. Should be simple.
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
Click to expand...
Click to collapse
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
I only managed to enter system with GApps version by disabling all networks (removing SIM and not connecting to wifi), but everytime prompted some login, I could configure without a problem using the normal version with GApps flashed.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Nice work bro... Please keep it live and update it time to time
johnjingle said:
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Click to expand...
Click to collapse
can you skip if you turn the phone off and on again?
xdacinq said:
can you skip if you turn the phone off and on again?
Click to expand...
Click to collapse
unfortunately no. at the same position i got the loop. But the Version without gapps worked.
Well, I'm puzzled why some of you are having so many issues. I had 3 MotoX4's to play with and all of them worked without issue. Granted, all 3 are XT1900-1 devices and I wouldn't imagine a big different between XT1900-1 through 7. Did this with the original Amazon Moto Retail (the one which says Moto and not Andriod One), plus the Andriod One I got from Motorola and finally the Project Fi phone too (also an Andriod One edition), but none of them had the issues some of you are reporting. -- Which is why I felt confident sharing this in this forum.
I will add that I always used the ROM without Gapps included (and later installed Gapps after adding the ROM). Gapps tends to update often and I wanted to start fresh with the latest edition, so I installed the Rom without Gapps, confirmed that all was working, and then rebooted back into recovery and installed Gapps (as instructed in post 1).
For the few of you reporting issues... Perhaps start from scratch (as if coming from stock) and see if that resolves things.
I included this in the instructions and someone who sent me a PM made it clear where they were making mistakes. -- DO NOT install Gapps right away. Load the ROM 1st (let your phone boot up the ROM as if you're done and then reboot and install Gapps). I made this clear in my instructions and I think some folks are ignoring that little bit (those of you getting the "checking info" message).
Pleaseb see all Posts Below for context and Important information!
This is a little bigger project of mine
I started a poll over at t.me/motoxproject and t.me/montanalabtesters
without going into detail, MIUI won with the most amount of votes
So here it is!
MIUI 11 Based on Android P From berilium (Poco F1)
Bugs:
-Themes only partially work by default, for a fix, see second post!
-Possibly Bluetooth
-Doesnt work on XT1799-2
Download:
https://t.me/MotoXProject/84
(I uploaded it to Telegram, just press on the link and it should bring you to the message)
Any questions?
PM me on Telegram or on Xda!
Status: Stable?
Android Version: 9
Supported Kernels: Radium (preinstalled) / in a later update EVA as well
Have fun trying this and stay inside!
To fix MIUI themes:
1. Download both files from here:
https://drive.google.com/open?id=1Lz8a9mypwTQ67-JWnTTbtKjo5a8Qx731
2. Flash the first zip within TWRP, reboot, and open the themes app once
3. Reboot to TWRP and flash the second zip file
4. Reboot into MIUI and open the themes app, if it doesn't crash, try downloading a theme, if it works
Congratulations you fixed MIUI Themes
You most probably won't be able to login to Google Play Services when booting,
MAKE SURE TO DOWNLOAD A GMS APK FILE FROM APKMIRROR AND INSTALLING IT FIRST AFTER BOOTING!
A fix has been discovered for the blur issues!
For a one time fix head into developer options and scroll to
"Disable HW Overlays" and instantly you see no more buggy Blur.
This resets on reboot tho
So I'll put some links down below!
Extract this and put it into init.d (emulated?) or use any application to run this at startup!
https://forum.xda-developers.com/attachment.php?attachmentid=2741603&d=1399997136
I'm sorry for being stubborn btw, the file above
1. Can't be easily downloaded
2. Doesn't even work due to a renaming error caused by me
:\
I will be fixing this though
I can't install, on twrp error 7 appears in red
error 7 al instalar
pipedd09 said:
error 7 al instalar
Click to expand...
Click to collapse
1.
Speak English, other languages aren't allowed on Xda.
2.
You got a corrupted zip file, please redownload
Hi,
screenshots?
Just Standard MIUI, nothing Special, this is outdated anyways
GravityBox - all-in-one tweak box - Xposed module for devices running Android 11
Version 11.0.5 [R]
Version for JellyBean is available in this thread: https://forum.xda-developers.com/showthread.php?t=2316070
Version for KitKat is available in this thread: https://forum.xda-developers.com/showthread.php?t=2554049
Version for Lollipop is available in this thread: https://forum.xda-developers.com/showthread.php?t=3037566
Version for Marshmallow is available in this thread: https://forum.xda-developers.com/showthread.php?t=3251148
Version for Nougat is available in this thread: https://forum.xda-developers.com/showthread.php?t=3653953
Version for Oreo is available in this thread: https://forum.xda-developers.com/showthread.php?t=3739929
Version for Pie is available in this thread: http://forum.xda-developers.com/showthread.php?t=3908768
Version for Q is available in this thread: http://forum.xda-developers.com/showthread.php?t=3974497
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Introduction
The app utilizes Riru-EdXposed Magisk module which uses original Xposed Framework API created by rovo89.
!!!!!! WARNING !!!!!!
This module utilizes EdXposed Framework which is still in early development stage and may contain bugs or might not be fully compatible with the system of your Android device. I take no responsibility for any issues arising from using GravityBox with EdXposed and strongly recommend creating a full backup of your device before activating the module.
Requirements
- Magisk v21 or later
- Riru v23 or later (Magisk module)
- EdXposed Manager (Application)
- Avoid using Resource hooking support if possible (Can be disabled in EdXposed Manager settings)
Installation
This procedure assumes you have working Magisk installation.
1) Install Riru module in Magisk Manager
2) Install and run EdXposed Manager app and download Riru-EdXposed module v5.1.3.x or later (currently Alpha/Canary)
3) Install downloaded Riru-EdXposed module in Magisk Manager
5) Reboot and open EdXposed Manager app to check if EdXposed works and is active
6) Install GravityBox and enable it in EdXposed Manager
7) Reboot and profit
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Feature highlight
--- Lockscreen tweaks
--- QuickSettings tile management with additional tiles
--- Statusbar tweaks
--- Navigation bar tweaks
--- Pie controls
--- Power tweaks
--- Display tweaks
--- Phone tweaks
--- Media tweaks
--- Hardware/navigation key actions
--- GravityBox Actions - interface for 3rd party apps
--- Notification control (per-app notification LED/sounds/vibrations)
--- Fingerprint launcher
--- Advanced tuning of Framework and System UI parameters
... and many more
Compatibility
GB's main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM.
It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device - it won't work.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win. They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 11 (AOSP)
- officially supports devices/systems it was developed and tested on
- Samsung, HTC, MIUI, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS MODULE WAS NOT EXPLICITLY DESIGNED FOR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
GravityBox [R] has been designed for and tested on
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Reporting bugs
If possible, please use Github issue reporting interface for reporting bugs.
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach logs that can be exported from EdXposed Manager app.
Real-time logging can be performed by using ADB: adb logcat -s EdXposed-Bridge
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that it will work flawlessly on yours.
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Preferred way is to use GitHub interface to fork your own copy of GravityBox, make changes and then send pull request against original repository.
Anoter way is to simply download this file: https://github.com/GravityBox/GravityBox/raw/r/GravityBox/src/main/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/r
If you're a dev and have some ideas for additional features, feel free to fork it, work on it and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/r/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there are three premium features:
- Backup/restore of GB settings.
- Ultimate notification control
- Advanced Tuning
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- RikkaW for creating and maintainng Riru Magisk module
- solohsu & MlgmXyysd for creating and maintaining EdExposed Magisk module
- @frank93 for donating Pixel 3a for development
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @simmac for app icon
- @romracer for Motorola specific code contributions
- @firefds for Samsung specific code contributions
- CyanogenMod project
- ParanoidAndroid project
- Slim, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- ArthurHub for Image cropping library
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, Fatih Firinci, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/r/CHANGELOG.txt
Changelog 11.0.5 - 08/08/2021
- Lockscreen: added option to blur media artwork on lockscreen (thanks to robbins)
- Navbar: allow cursor control keys in gestural navbar
- Dialer: adjusted for compatibility with the latest Google Dialer
- Properly identify OnePlus 8T as device running OxygenOS ROM (thanks to F-i-f)
--- should improve compatibility significantly
Developed and tested on:
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Current issues
- Display: Expanded Desktop - immersive modes not working
- Key actions: Home double-tap not working
- Lockscreen: Changed custom carrier text won't appear immediately
- Custom Battery indicator: stock battery may appear for a while after the reboot
- ... + potentially others mainly device/system variation specific
Removed features
- GPS and SlimKat tiles - location modes (battery saving/high accuracy/device) no longer exist in Android 11
- Audio Recording tile - background recording of audio not possible in Android 11
Download
https://github.com/GravityBox/GravityBox/releases/tag/v11.0.5_r
Settings
It is possible to restore settings that were backed up in GravityBox [Q]
Simply transfer "GravityBox" folder from internal storage of one device to internal storage of another device.
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Credits
@frank93 for donating Pixel 3a for developemnt
Commit history
Commit history for transition from 11.0.4 to 11.0.5
@C3C076
Mate, you did it. Congratulations.
Can't wait to try it out.
Really appreciate your efforts in bringing this to us 11ers.
Cheers
2021 is looking good! Thank you so much. Working flawlessly on my pixel 3a
@C3C076
THIS is the first gift I've received of the new year. Thank you, sir!!!
Now, that's pretty awesome!
And the January update from Google should drop soon as well.
Thanks a lot @C3C076!
Got my Github notification this morning about the [R] pre-release! Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems. Everything working perfectly fine! All I had to do was first disable GravityBox [R] in EdXposed Manager, and disabled Kirisakura AK3 (kernel) module helper in Magisk Manager. Upgraded to Android 11 with no issues at all, and everything system and root-wise seems to work perfectly fine. My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
Though I'm gonna play it safe and OTA each month, instead of factory image (sans "-w" flag) jumping. Gonna work my way up to the current firmware, then test out GravityBox [R] - thanks so much @C3C076! The fact that so many people like me have held off on upgrading to the latest Android version just based on your work should speak volumes! I'll report back once I'm able to actually play around with GB[R] some. The baby's starting to wake... :O
edit: my son rolled over, coo'ed, and faceplanted back to sleep <3
- Also should note, I was on Kirisakura 5.2.6 kernel before. Now on 6.6.0, all is well!
- Also wanted to note, SafetyNet was passing (with my current configuration) on 09-2020 build with no further modifications necessary. I just finished updating up to 12-2020, and SafetyNet is still passing . Activating GravityBox module now, and will further report back!
edit 2: Seems verrrry stable so far! The only thing I found that didn't work properly (or rather, worked 80% correctly) was for an option that I don't even normally use, and accidentally toggled, haha. Under QuickSettings management -> Tiles per header, each option works fine, but when selecting 8, it still only shows 7.
Other than that, at least as far as the options that I personally use, everything seems fine! I didn't get a chance to test out every function affected by my set of GB options in such a short time, of course, but I will certainly report if there are any issues. And of course I won't list every single option I ticked off, but attached is my backup file / preferences of my current config for anyone who may be curious. Again, keep in mind that compared to the vast functions GB offers in totality, I only use what I use so of course I can't account for the entirety of GB. But from what I've tested so far, it seems damn stable and this has made my transition to Android 11 pretty much seamless!
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
i5lee8bit said:
Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems.
[...]
My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
[...]
Activating GravityBox module now, and will further report back!
Click to expand...
Click to collapse
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Ghisy said:
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Click to expand...
Click to collapse
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
i5lee8bit said:
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
Click to expand...
Click to collapse
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
i5lee8bit said:
see my edit above =)
Click to expand...
Click to collapse
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
If I can share my experience. I applied standard system update procedure from settings being on Pie (had it on your pixel to bring update for GB for Pie). This went without uninstalling magisk etc. I simple went incrementally from Pie through Q up to R and then several security update. Only after I was in the latest update I grabbed boot.img from corresponding system image, patched it using magisk and then flashed using fastboot. All apps and settings were preserved from Pie.
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
frank93 said:
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
Click to expand...
Click to collapse
Yeah, note that I never flashed full rom image. I went using standard system update from settings. In the end it was only patched boot.img I flashed.
okay, apparently not even a "real" firmware update (using the original stock boot image) works for me. loops back to bootloader 2-3 seconds after the google-logo. so i guess there’s something else wrong with my device/system.
i’ve "updated" back to the latest/last android 10 for now (there the firmware upgrade/downgrade works!?), and i’ll scratch my head another time i think. thanks for your input though!
i5lee8bit said:
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
Click to expand...
Click to collapse
Thanks, I appreciate it! You took one for the team and shared interesting info too! *(air) high five*
C3C076 said:
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
Click to expand...
Click to collapse
I use App List mode, but not White List mode, as I use the Pass SafetyNet option (so basically on Blacklist mode). Because I also have GPay working and all (I've linked to that thread before, it's the one I linked with my list of active modules). Hahaha, I didn't even realize you put in the 2nd post about it not working - weird! Definitely working for me though, using these current configurations.
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
Since I'm sure others may find it useful, I'll post it here. Also, @C3C076 may find it useful to follow this concept, assuming things are similar for Pixel 3a (I've been a long time HTC user, up til U12+ and only then switched to Pixel phones, 4 for wife and 4 XL for me to be exact).
My firmware update procedure is basically predicated on restoring the stock boot and dtbo (dtbo in case custom kernel flashed) images for your current build, which restores the stock firmware (and therefore recovery) and "unroots" / stock-ifies the phone without removing any of your Magisk or EdXposed configs, which allows you to simply boot into recovery and apply (sideload) OTA zip from stock recovery. Before booting back into system after OTA flash, reboot back into bootloader and flash the new build's Magisk-patched boot image, and when you boot up into system, voila, seamless, intuitive, and relatively safe update to new firmware version. Worst case scenario, if you bootloop you just flash the stock boot image (or even better, a modified Magisk Core Only boot image) and fix whatever is causing the problem.
Here is a link to my guide for September 2020 build, which was the first Android 11 build. There's a bunch of additional notes due to the major update at the time, though some of the info is a bit outdated. I assumed everyone at the time was on a very specific versions of firmware, Magisk, EdXposed, and even modules, etc. But if you read, especially the 2nd post, you can certainly understand how it all works and how we could apply the process from any firmware version. Here's the thread: https://forum.xda-developers.com/t/...0-009-coral-magisk-stock-boot-images.4160787/
- I recommend giving the procedure a read, as you should be able to understand the intuition behind the process I use.
As we're already (assuming) on latest Magisk, Magisk Manager, EdXposed, Riru, etc. etc, we don't need to worry as much about compatibility of our installed modules before OTA'ing. So basically, I condensed down what needs to be disabled, in my case, to the old GravityBox module (obviously), and the old Kirisakura (my kernel on Q) kernel helper Magisk module. You would also want to disable any modules, Magisk and EdXposed, that may not be compatible with [R] yet.
So here was my update procedure, from here on, coming from August 2020 build already on Magisk 21.2 and up to date EdXposed / Riru / etc. modules - SPECIFICALLY FOR PIXEL 4 XL "CORAL"
(OPEN THE "SPOILER" TO VIEW!):
Spoiler: Pixel 4 XL (and by extension and intuition, hopefully other Pixel series) keep-root / updating guide-procedures
NOTE: The files I provide are specifically only for Pixel 4 XL!! You will need to obtain the correct files for your own device to follow this procedure, but the same idea should be able to be applied!
First, I downloaded the boot and dtbo file(s) for Aug. 2020 thru Dec. 2020 builds. Here's a link to my AFH uploads for these files: P4XL Boot / DTBO files
Then, I patched each month's boot image with Magisk 21.2, and put them to the side.
There's only stock dtbo.img for 08-2020 because dtbo will remain stock throughout the updating procedure, fyi.
Actually, hell, for Pixel 4 XL "Coral" users, to make your life extremely easy, I've uploaded all the files you'll need to follow this here!! - LINK HERE
And OTA files from Google servers: LINK#2 HERE
Disabled GravityBox [Q] module in EdXposed Manager / Uninstall GravityBox [Q]
(Don't bother installing GravityBox [R] yet)
Disabled Kirisakura AK3 Kernel Helper module in Magisk Manager
(you'll also want to disable any modules that potentially may not work with [R])
-- Reboot once to finalize disabling the modules --
(Don't boot back into system until this section is done, to ensure all root, settings, mods, etc. are retained - this is basically the 2nd post of the September guide I linked earlier)
- Reboot into Bootloader mode -
fastboot flash boot 08-boot.img
fastboot flash dtbo 08-dtbo.img
(these steps revert recovery to stock)
- Reboot into Recovery mode-
(when No Command / Android icon shows up, hold power button and tap volume up to get to recovery menu)
Choose option: Apply update from ADB
adb sideload (09-2020 OTA zip).zip
after OTA zip flash completes, REBOOT BACK TO BOOTLOADER
fastboot flash boot 09-patched.img
- NOW REBOOT INTO SYSTEM! -
When your phone boots back into Android (11), you will be rooted, with all mods and settings retained. And if you passed SafetyNet before with the right combination of mods and settings, it should still pass now. While you can, I wouldn't yet bother installing GravityBox [R] quite yet. Let's first continue to incrementally upgrade until we're at 12-2020 (or 01-2021 depending on when you're reading this). Basically, just make sure the Android System Update notification (sorry, I don't remember exactly the notification label, but you'll know when you see it) indicates the update completed before proceding.
Now we just repeat my OTA update procedure again, except no need to flash stock dtbo images, as we're not doing anything (like flashing custom kernel) in this short amount of time that modifies the dtbo partition.
Reboot into bootloader mode
fastboot flash boot 09-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (10-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 10-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 10-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (11-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 11-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 11-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (12-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 12-patched.img
Boot to system
EDIT: Google released January 2021 firmware update, literally minutes after (or maybe while??) I was posting this! Here is my January 2021 easy update guide for Pixel 4 XL: https://forum.xda-developers.com/t/...5-003-coral-magisk-stock-boot-images.4213263/
Allow time for the system update notification to indicate update was completed.
Install GravityBox [R], activate module, reboot one more time, have fun!!
Also install custom kernel or whatever else you might need to do as well.
To be honest, I kinda rushed this post, so I'll re-read it later and make sure I didn't make any little mistakes. But hopefully if you read my guides threads and stuff (like, actually read it), the entire concept should be very clear and intuitive to you! Assuming other Pixel phones (at least AB Pixel devices) have similar partitioning schemes, this should be very useful knowledge to have, as it makes updating to new firmware versions incredibly easy and low risk. Good luck, I hope this huge post helps some people / makes a better day for someone! =)
EDIT: @frank93, seeing your linked post, I see you have a Pixel 4a. Unfortunately you obviously can't use the exact files I provided / linked, but you should still be able to follow the same procedure. Just grab the OTA's, plus the full factory images, pull the necessary boot and dtbo files from the factory images, and Magisk patch the boot images for each month, and name / organize all the files and put them aside on your computer. You should still be able to follow my procedure, but with your files. I hope it works for you with no problems if you decide to try it!
Has anyone tried one plus 8t?
...aaaand Pixel January 2021 update just dropped
Awesome! 2021 is looking good! Donation sent! Keep up the awesome work bro! Working flawlessly on my Pixel 3xl