Database Info

[ROM][NZH54D][2023/04/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP

This thread is about installing and using AOSP 7.x (Nougat) ROM for the ASUS Nexus 7 Grouper / Tilapia devices.
Asus - Model names
Grouper = Asus Nexus 7 2012 WiFi
Tilapia = Asus Nexus 7 2012 3G
Initial Setup Installation
Update Recovery to TWRP 3.6.2-9 for Grouper resp. TWRP 3.6.2-9 for Tilapia
Boot into Recovery
Factory Reset (only needed if you are not already on Android 7.x AOSP)
Install 7.1.2 Grouper OTA-Package (Build 20230418) (MD5: 3abdfef56c75cc171fce1c4ffd7a17a8)
or
Install 7.1.2 Tilapia OTA-Package (Build 20230418) (MD5: fc7a5bc81587dba848b37bd62e6166b9)
Reboot into recovery
Install Open GApps (arm/7.1/pico)
(if you have issues regarding the size of the GApps please refer to the next post)
[*]To get root access, I suggest to use either Magisk (V21.4) and Magsik Manager (V8.0.7) the "old" version of Magisk, or the new unified Magisk (V26.1) which can be flashed by TWRP, too. Probably you'll need to rename Magisk-v26.1.apk to Magisk-v26.1.zip
I was not able to flash Magisk 24.x by TWRP / direct install, nevertheless the patching boot.img method worked. For that you need to extract the boot.img from the OTA and transfer it to your devies. Then you need to patch the boot.img and transfer it back to your PC. Finally you can flash the patched boot.img using fastboot.
For detailed instructions please consult the Magisk threads here in XDA.
Do not install Magisk on initial setup as it might lead to issues. Start the ROM without having root access the first time and install Magisk in a second step.
If you are already on Android 7.x AOSP, it's sufficient to do the follwowing steps:
Update Installation
Boot into Recovery
Install 7.1.2 Grouper OTA-Package (Build 20230418) (MD5: 3abdfef56c75cc171fce1c4ffd7a17a8)
or
Install 7.1.2 Tilapia OTA-Package (Build 20230418) (MD5: fc7a5bc81587dba848b37bd62e6166b9)
Reboot into recovery
Install Open GApps (arm/7.1/pico)
(if you have issues regarding the size of the GApps please refer to the next post)
Wipe cache/dalvik-cache (optional, but suggested)
reboot
Important: For more detailed installation instructions please refer to the next post
Important: First boot after upgrading will take a bit longer (stays on ANDROID) because of art optimizations
flash and use on your own risk!
CREDITS,
AOSP/Google, LineageOS, Ziyann for setting up the Grouper-AOSP repository and his Unlegacy Android project, daniel_hk for some hints how to get the 3.1 kernel running with N, timduru for his work on the Asus Transformer, Timur Mehrvarz for his work on the tegra kernel, Francisco Franco for his kernel work in general
Bugs:
please report
Latest Changes
20230418(AOSP 7.1.2)
security fixes for January / February / March and April
Latest version with MicroG-patch applied to them:
aosp_grouper-7.1.2-mg-ota-20230418.eng.ds.zip (MD5: ccfd0b77ca5d2bc8bf98a530737158ba)
aosp_tilapia-7.1.2-mg-ota-20230418.eng.ds.zip (MD5: f91a7ac97aae3b724612980848fed342)
Changelog
Please refer to the changes found in the github repos
All ota packages can be found here:
AndDiSa ROM files repository
Sources
https://github.com/AndDiSa
If you would like to build from the sources, you can do so by cloning and build from repositories:
repo init -u https://github.com/AndDiSa/platform_manifest-Grouper-AOSP.git -b ads-7.1.0
repo sync (... and go out for lunch ...)
. build/envsetup.sh
lunch 7 / 8 / 9
make / make otapackage
but please take in mind that you need to have some free space (>= 100 GB) and some time ...
XDA:DevDB Information
Android 7.x AOSP, ROM for the Nexus 7
Contributors
AndDiSa
Source Code: https://github.com/AndDiSa?tab=repositories
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-09-23
Last Updated 2021-12-09

Please note:
the system partition is already quite full which leads to the problem that gapps probably will not install correctly and that may lead to weired problems (apps closing / not showing up correctly / ...). I suggest to use the dynamic gapps package linked above. In addition I suggest you to erase the system partition completely before applying the OTA package
If you get "Error 7" when trying to flash the ROM directly after upgrading to TWRP 3.5.2-9, wipe the Boot, System and Cache partition and clean dalvik-cache, then re-boot to Recovery and try again (you will not loose any data as long as you do not wipe the Data partition).
If you get "Error 70" when installing GApps copy the attached gapps-config files into the same directory where the gapps installation packages is copiedI.e. something like
/sdcard/open_gapps-arm-7.1-pico-20210922.zip
/sdcard/gapps-config-tilapia.txt
/sdcard/gapps-config-grouper.txt
and then try to start the installation again. Error 70 should be fixed.
Some additional hints
If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
Code:
adb reboot bootloader
After a few seconds the device should show up the bootloader screen

Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?

Nintonito said:
Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?
Click to expand...
Click to collapse
Why not figure it out by yourself?
If you flash this ROM you can create a list of what's working and what's not [emoji6]
Anyway, when I'm home, I gonna flash this ROM on my brother's Nexus 7 and give feedback. [emoji4]
Sent from my Nexus 5 using XDA-Developers mobile app

Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
View attachment 3884176
View attachment 3884177
View attachment 3884178

Thanks, I'll correct the link
Nevertheless your problems I cannot reproduce ... probably because I've done an update installation. I'll have a look at it.
What was the ROM you have had installed before? Did you wipe?

When i get a chance this weekend I'm going to try this with Phh Superuser and Magisk. That combo is/was working great on your MM rom.

I flashed your ROM with TWRP 3.0.2-0 and after 'Patching system image uncondinionally' i get
Code:
Patching system image uncondinionally...
E:unknown command [log]
E:unknown command [log]
script succeeded: result was [1.000000]
Updating partition detail...
...done
I doublechecked the md5 of the file and reflashed but still no luck.
[Edit]
I rebooted and it seems to run....
[Edit2]
Flashing the plain ROM without the gapps seems to work - but after these gapps it doesnt start.

I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx

tpuserhp said:
I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx
Click to expand...
Click to collapse
I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
DSTear said:
Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
View attachment 3884176
View attachment 3884177
View attachment 3884178
Click to expand...
Click to collapse
Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx
I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.

As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.
Sent from my Nexus 7 using XDA-Developers mobile app

AndDiSa said:
As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm not using f2fs. I issued a mount command and did not find any f2fs hits. Not sure why I am getting those msgs. Odd.

I've updated the installation instructions in the OP / second post
I've added some hints, too, how to get out of bootloops, if you encounter such situations.

tpuserhp said:
I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx
I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.
Click to expand...
Click to collapse
Hi. It's quite simple to fix that. Just connect your device to computer, then start bootloop. You will able to fix it using ADB:
Code:
adb reboot bootloader
And after that format your cache partition:
Code:
fastboot format cache
And reinstall TWRP just in case:
Code:
fastboot flash recovery [twrp img for your device]

Bluetooth is not working.
Could Restart be added to the shut down menu please?

Bluetooth will be fixed with the next release.
Sent from my Nexus 7 using XDA-Developers mobile app

difference to
http://forum.xda-developers.com/nexus-7/development/rom-naosprom-nexus-7-2012-t3467335

hanschke said:
difference to
http://forum.xda-developers.com/nexus-7/development/rom-naosprom-nexus-7-2012-t3467335
Click to expand...
Click to collapse
Bluetooth isn't working.
*SCNR*

I want Restart menu.
Next time
Please Support Restart menu.

AndDiSa said:
Some additional hints
If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
Code:
adb reboot bootloader
After a few seconds the device should show up the bootloader screen
Click to expand...
Click to collapse
I'm having the same bootloop issues when trying to go to recovery after my rom is installed. After adb reboot bootloader I have to flash twrp to fix that.
Do you maybe know what can cause this issue?
For the bluetooth I saw you already applied the fix to your source

[GUIDE][PORT] How to install the Android Pie sGSI on your Xiaomi Mi A1

Code:
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this GSI and/or kernels. You do so at your own risk and take the responsibility upon yourself.
MOD EDIT: Remember to be prepared for an experimental or unstable ROM. If do you not know what you are doing or not experienced with flashing and recovering your data then it's not recommended.
REMEMBER TO BACKUP EVERYTHING AS THIS WILL REPARTITION YOUR USERDATA AND WILL WIPE YOUR INTERNAL STORAGE. ALSO, REMEMBER TO READ EVERYTHING AS ALL FIXES ARE POSTED BELOW. DON'T JUST FLASH THEN JOIN TELEGRAM TO ASK WHY THIS DOESN'T WORK FOR YOU.
READ THE IMPORTANT NOTES POSTED HERE​
TO REVERT TO NON-TREBLE/STOCK ROM, WATCH THIS VIDEO BY @GizmoFreak OR FOLLOW THIS POST
Here's everything I can provide to the normal user willing to try this out on their Mi A1.
PLEASE VISIT THIS NOTE TO SEE ALL THE REMAINING BUGS
OR JUST READ THEM HERE
SELinux is permissive
Hw key lights don't light up
Everything else works fine. Just need to update your Google Play services app and you can restore apps via Google Backup (if you didn't already do it with Titanium Backup). Yes, rooting with Magisk works and some modules work as well such as Blobmojis among others.
Here are the steps to install it in your Mi A1 if you're coming from stock ROM
Or watch a video made by @GizmoFreak
Enable Developer options in Settings app
Check Enable OEM Unlocking
Reboot to fastboot mode
Unlock your bootloader
Install TWRP-fastboot only through fastboot boot command (Extract the .img file from the zip)
Flash CosmicDan's TWRP Installer through your current TWRP. Credits to @CosmicDan for his TWRP and @mohancm for official TWRP sources.
Reboot to TWRP recovery
Go to WIPE then ADVANCED then click FORMAT data. This will remove Encryption on your device and allows you to set new passwords when installing the GSI. Note that this will format your internal storage.
Treblelize through TWRP Tissot Manager (Go to advanced, click Tissot Manager and choose the repartition userdata option. Select singleboot option then click repartition)
Flash latest Vendor.img as VENDOR IMAGE
Flash A/B system Pie PR2 img as SYSTEM IMAGE (Extract the .img file from the zip) (special thanks to @dgadelha for the sGSI)
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Flash a treble-compatible kernel (Moun, ProjectK,Velocity)(credits to @mountaser halak, @khusika, @kdragon)
Reboot to system.
Once booted, install the latest Play services linked above either via the Files app or via adb. This will fix the Pixel Setup and Google Backup issues as well as allows you access to the Play Store without problems.
You can now flash Magisk 17.3. This is the version that works properly with treble. Credits to @topjohnwu for Magisk.
Install the Data transfer tool APK update as well.
Special thanks to @erfanoabdi for porting the Pie A/B GSI.
Some features may seem to be broken but can actually be fixed with a few tweaks
USB MTP FIX
To enable USB MTP, enable Developer options in the About phone section of the Settings app by tapping the Build Number 4 times. Then look for the File Transfer option in the Dev options.
ENABLE NAV BAR GESTURES
To enable Nav Bar, I installed this nav bar enabler by @Hugwalk via Magisk.
After rebooting, go to Settings > System > Gesture and enable Swipe Up on Home Button to enable the Nav Bar Gestures.
SUBSTRATUM
Substratum is now much better for Pie.
Install the latest APK from this telegram channel and now all themes with Pie support can be installed.. Just reboot after building the themes and go into managers to enable the overlays you built.
Ethereal - https://play.google.com/store/apps/d...ethereal&hl=en
Outline - https://play.google.com/store/apps/d....outline&hl=en
Compound - https://play.google.com/store/apps/d...compound&hl=en
Sai's theme - https://t.me/tissotpsemigsi/33526
Click to expand...
Click to collapse
You should have the Android Pie booting on your Mi A1 now with less issues.
To update from PR1 to PR2, you can do so without wiping data
Wipe system ONLY
Flash PIE PR2 AB GSI
Reboot to system
Click to expand...
Click to collapse
To update your post post GSI zips, follow this
Wipe vendor ONLY
Flash vendor
Flash POST-sGSI 1 tissot zip.
Flash POST-sGSI 2 tissot zip.
Reboot to system
Click to expand...
Click to collapse

Awesome work @joeyhuab bro ?

Edit:- Chrome sucks! Posted same thing twice.

Youtube not working for me(

Great job!!!i will wait to change to beta

Tornado95 said:
Youtube not working for me(
Click to expand...
Click to collapse
I also encounter YouTube issues. :/

Don't work the camera and black for me

ErickCartman17 said:
Don't work the camera and black for me
Click to expand...
Click to collapse
Try Footej Camera from Play Store please, it can be usefull if Footej or Open Camera works

waiting camera fix

cant mount system(invalid argument)
Failed to mount system after i try to flash GSI

I will wait for the stable...but is a good work... Thanks for try this.

andrexp31 said:
I will wait for the stable...but is a good work... Thanks for try this.
Click to expand...
Click to collapse
lol, then just wait for the official release. This is as close as we can get, for now since google hasn't uploaded the source code for P yet

I'm already looking into a fix for Camera. I'll post it once it's available.

What if I want to come back from Android Phone to another Custom ROM? Do I have to "un-treble" the device?

When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?

danilguy said:
When I Flash A/B system GSI img i have a 255 error: Updater process ended with ERROR: 255 Error installing xip file `tissot_manager/flash_proxy.zip`. How i can fix it? What is the problem?
Click to expand...
Click to collapse
Remove the spaces from the folder name and try... Works for me...

Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.

joeyhuab said:
Camera has been fixed. Just adding some more fixes and we'll probably get fingerprint working too. I'll update the links later when done.
Click to expand...
Click to collapse
U have don great work
Really well done
Waiting for camera, fingerprint and flash bugs fixed and i will surely test the rom

What about Bluetooth?

Chris_Cheekyz said:
What about Bluetooth?
Click to expand...
Click to collapse
Fixed as well together with Camera fix. Credits to Rupansh and @kdragon for using Whyred's blobs. Credits also to @ghpranav for BT fix.
Download

[GUIDE] Havoc P and other P GSI with anykernel2 8.1 to P boot patch [temp]

First things first
1. Remove all pattern, fp, face data and BACKUP all Partition in TWRP ( I lost baseband trying GSI images, those backup saved me).
2. TWRP should be installed and also Force disabled Encryption should be flashed.
Now follow the steps
1. Go to TWRP, wipe dalvik/cache, cache, system, data
2. Go back and Flash HavocP system image as System or you can try other P GSIs..
HavocP-arm64_aonly_vanilla_nosu-0830.zip
( You can check the source here for updates).
Optionally you can flash arm64 Gapps 9.0 (nano or micro is recommended) opengapps.org
3. Next without exiting TWRP flash this zip, this one patches boot for Android P GSI image compatibility..
POST-sGSI_3_v0.5.zip
4. Now go to wipe menu and wipe Dalvik/cache, cache, data and reboot.
For audio distortion fix:
[Temp] How-To Fix Audio distorted on P GSIs
For Volte: not found any fix yet, but may be fixed by tweaking build.prop like some other devices.. Will add if found.
May this line be added in Vendor/bin/init.qcom.sh like One plus 3.
Code:
# Hack to get IMS up and running on GSI
if [ -f /data/system/users/0/settings_global.xml ]; then
sed -i 's/"multi_sim_data_call" value="1"/"multi_sim_data_call" value="-1"/g' /data/system/users/0/settings_global.xml
restorecon /data/system/users/0/settings_global.xml
fi
This thread is temporary.. Will close it if stable Havoc is released by the Devs
Credits- skulshady, zenixxx, erfanoabdi, EnesSastim, phhusson, SH1M4BD

Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!
EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized
Regards.

Please test multitouch issue, if it exists in this rom.

NexusPenguin said:
Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!
EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized
Regards.
Click to expand...
Click to collapse
1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.
In short, these GSIs are not stable.
shailendra1993 said:
Please test multitouch issue, if it exists in this rom.
Click to expand...
Click to collapse
Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..

palbadi said:
1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.
In short, these GSIs are not stable.
Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..
Click to expand...
Click to collapse
No, the multitouch bug, ghost touch is different.
Check this out: en.miui.com/forum.php?mod=viewthread&tid=3746297

palbadi said:
1.
In short, these GSIs are not stable.
Click to expand...
Click to collapse
Hi,
Same impression here : Treble needs a lot more work to deliver what Google is aiming at !
I now understand why some ROM devs do not want to release GSI ROM images
Regards.

If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.

Technical said:
If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.
Click to expand...
Click to collapse
It is due to mismatch of ro.vendor.build.fingerprint value in build.prop in System and Vendor..
FIX:
1. Connect data cable to PC and boot into twrp
2. Go to Advanced/file manager
3. Copy build.prop from both Vendor and System to Sdcard, so that you copy them to your PC and edit.
4. In PC, Copy those build.prop files from sdcard and change the value of ro.vendor.build.fingerprint from build.prop (system) to build.prop (vendor).
5. Now overwrite the edited build.prop (vendor) to Vendor in the same process and you may give permission 644 (rw-r--r--) that vendor/build.prop
6. Reboot and check

What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.
I don't see the point.

SmallTarzan said:
What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.
I don't see the point.
Click to expand...
Click to collapse
Havoc did not boot without that zip

[ROM][A530W/A530F/A730F] SaboorROM

[A530x][A730F]
SaboorROM
PLEASE READ ALL THIS BEFORE DOING ANYTHING
________________________________________________
NOTICE:
I am not responsible for any happy endings, a nuclear war with your device, your alarm clock electrically shocking you, or your device literally freezing, so dont blame me for my mistakes or yours, or else i will laugh at you
Please backup your device (System, Data, EFS, and Cache, Especially EFS) because you might regret flashing this
________________________________________________
CREDITS:
@prashantp01 for Quantum Kernel
SuperR kitchen to build rom
________________________________________________
FEATURES:
Canada A530WVLU4CSCA base
Debloated
Deknoxed
Rooted
S10 Sounds and ringtones
Screen Recording (check section 2 on post #3 for more details)
build.prop tweaks
Status bar size options (check section 1 on post #3 for more details)
G975F/G975W ODM
ODM mods that add mobile data quick settings tiles etc
Applock
Call recording
Mobile data toggle in power menu
________________________________________________
BUGS:
Freezes on bootanimation and when playing video (sometimes) (i dont think there is with 4/23 build, someone test and tell me ASAP)
Digital wellbeing not showing stats (check section 3 on post #3 for workaround) (DIGITAL WELLBEING NOT AVAILABLE ON 4/23 BUILD I WILL ADD IT ON FUTURE BUILDS LOL I JUST FORGOT ABOUT DIGITAL WELLBEING)
Everything else works
________________________________________________
INSTRUCTIONS:
1. Download the ROM zip, and zip #2 for your model under this section
2. Boot into TWRP
3. Wipe system, cache, and data
4. Flash ROM zip
5. Flash zip #2
6. Boot and setup
7. done! (PLEASE READ THE BUGS BEFORE YOU GO TO THE COMMENTS AND SAY "sar why my phone freeze so much ur rom is stupid")
________________________________________________
DOWNLOAD
DOWNLOAD ROM AND ZIP #2
DOWNLOAD UNTESTED NEWER 4/23 BUILD AND ZIP #2
________________________________________________
How to update from existing version of rom
1. Dont forget to download the zip #2 update too, that zip updates too!
2. Flash ROM zip
3. Flash zip #2
4. Wipe cache/dalvik
5. Wait for device to finish optimizing and updating before reporting any bugs
________________________________________________​
XDA:DevDB Information
SaboorROM, ROM for the Samsung Galaxy A8+ (2018)
Contributors
587.saboor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 420-11:11AM
Stable Release Date: 2019-04-20
Current Beta Version: 4-23-6:50PM
Beta Release Date: 2019-04-23
Created 2019-04-13
Last Updated 2019-04-23

/////////////////////////////////////////////////////////////////
Click here to join us in the one and only A8/A8+ Telegram group
/////////////////////////////////////////////////////////////////​

_____________________________________________
STATUS BAR SIZE
If you see the screenshot below, you'll see the status bar is a bit big (pls don't mind the blank settings page lol)
https://photos.app.goo.gl/wiYKVbJed52t9SiN6
DON'T PANIC BIG STATUS BAR HATERS! THIS IS ONLY OPTIONAL AND THIS EVEN HAS OPTION FOR SMALLER STATUS BAR
How do you get it, you ask?
just follow these steps after installing the rom
1. go to settings
2. developer options (u already know how to turn dev options on)
3. scroll down to "Simulate display with a cutout" and tap it
4. select a size of status bar (this wont add any notch on your phone, this only makes the status bar a bit bigger like on the screenshot)
5. done!
_____________________________________________
SCREEN RECORDER
You can record your screen with sound too
How do you get it, you ask?
just add it to the quick settings menu
_____________________________________________
DIGITAL WELLBEING FIX
Digital wellbeing doesn't show stats but you can make it show
How?
just follow these steps:
1. go to settings
2. search "Special Access"
3. press Special Access
4. scroll down to Usage data access and press it
5. press the 3 dot menu on the top right
6. press Show system apps
7. press Digital wellbeing and enable allow usage tracking
8. done!
_____________________________________________
SCREENSHOTS
https://photos.app.goo.gl/4USaY78w3cm8DG5p9
_____________________________________________​

yeet

587.saboor said:
yeet
Click to expand...
Click to collapse
Why do you think Samsung released a updated that has bugs?

mchlbenner said:
Why do you think Samsung released a updated that has bugs?
Click to expand...
Click to collapse
idk cuz they're high? ????

A8 2018 - SM-A530F
Upgrade from Nougat (Android 7.x):
-installed newest TWRP via TWRP
-backed up the old Nougat via TWRP
-wiped and installed DOWNLOAD ROM AND ZIP #2 (non-beta) via TWRP
-reboot
-it took about 15 minutes and several reboots --> be patient
-message "KERNEL IS NOT SEANDROID ENFORCING" at every boot now (top left of screen, small red font)
Root problem:
if you grant apps root, magisk manager is constantly crashing (if an app uses root) (e.g Titanium Backup, Total Commander)
-reduce to core functions in magisk manager did not help
-upgrading magisk manager to 7.1.1 did not help
-downgrading magisk to 18.1 helped (I removed magisk 19.0 with Magisk-uninstaller-20190328.zip in TWRP first)
EdXposed is working (I had to flash it _twice_ via TWRP)
-flash magisk-riru-core-v18.zip
-flash magisk-EdXposed-v0.3.1.7_beta-release.zip
-install EdXposedInstaller_v2.2.4-release.apk
Important apps that work: AFWall+ 2.99, XPrivacyLua 1.24, Titanium Backup, FM-radio
Looks like, I can't go back to Nougat (just want to do this because I missed to save settings in XPrivacy and wifi passwords before the upgrade).
Downgrading to Nougat (Restore in TWRP) didn't work:
-backed up the new Pie and wiped data, system, cache
-restoring Nougat went well but gave one error at the end:
-Failed to mount '/system' (Invalid argument)
-I got bootloops.
So I restored Pie in TWRP:
-wiped data, system, cache
-wiping went well but gave one error at the end:
Failed to mount '/system' (Invalid argument)
-restore went well, no bootloops

phocriab said:
A8 2018 - SM-A530F
Upgrade from Nougat (Android 7.x):
-installed newest TWRP via TWRP
-backed up the old Nougat via TWRP
-wiped and installed DOWNLOAD ROM AND ZIP #2 (non-beta) via TWRP
-reboot
-it took about 15 minutes and several reboots --> be patient
-message "KERNEL IS NOT SEANDROID ENFORCING" at every boot now (top left of screen, small red font)
Root problem:
if you grant apps root, magisk manager is constantly crashing (if an app uses root) (e.g Titanium Backup, Total Commander)
-reduce to core functions in magisk manager did not help
-upgrading magisk manager to 7.1.1 did not help
-downgrading magisk to 18.1 helped (I removed magisk 19.0 with Magisk-uninstaller-20190328.zip in TWRP first)
EdXposed is working (I had to flash it _twice_ via TWRP)
-flash magisk-riru-core-v18.zip
-flash magisk-EdXposed-v0.3.1.7_beta-release.zip
-install EdXposedInstaller_v2.2.4-release.apk
Important apps that work: AFWall+ 2.99, XPrivacyLua 1.24, Titanium Backup, FM-radio
Looks like, I can't go back to Nougat (just want to do this because I missed to save settings in XPrivacy and wifi passwords before the upgrade).
Downgrading to Nougat (Restore in TWRP) didn't work:
-backed up the new Pie and wiped data, system, cache
-restoring Nougat went well but gave one error at the end:
-Failed to mount '/system' (Invalid argument)
-I got bootloops.
So I restored Pie in TWRP:
-wiped data, system, cache
-wiping went well but gave one error at the end:
Failed to mount '/system' (Invalid argument)
-restore went well, no bootloops
Click to expand...
Click to collapse
lol
first of all, why are you downloading this rom from nougat? it's gonna obviously cause problems if you're coming from nougat so i recommend going to pie first from odin, then flash this rom, or oreo if you really dont want pie.
second of all, you shouldnt use xposed with samsung firmware, or else you would encounter issues but it's fine if you want to use stuff like greenify or something
third of all, the KERNEL IS NOT SEANDROID ENFORCING is normal but shouldn't show up anyways, it's showing up because you have old nougat bootloader so thats another reason to flash official pie from odin before flashing this rom

587.saboor said:
first of all, why are you downloading this rom from nougat? it's gonna obviously cause problems if you're coming from nougat so i recommend going to pie first from odin, then flash this rom, or oreo if you really dont want pie.
Click to expand...
Click to collapse
that's the lazy man's approach, just give it a try
587.saboor said:
second of all, you shouldnt use xposed with samsung firmware, or else you would encounter issues but it's fine if you want to use stuff like greenify or something
Click to expand...
Click to collapse
okay, i switchted from XPrivacyLua to AppOps
587.saboor said:
third of all, the KERNEL IS NOT SEANDROID ENFORCING is normal but shouldn't show up anyways, it's showing up because you have old nougat bootloader so thats another reason to flash official pie from odin before flashing this rom
Click to expand...
Click to collapse
imho it is not obvious: you can still boot windows 10 with a windows 7 bootloader, same for linux
probably you should add that hint to you first post

phocriab said:
imho it is not obvious: you can still boot windows 10 with a windows 7 bootloader, same for linux
probably you should add that hint to you first post
Click to expand...
Click to collapse
nah i dont really need to add the hint cuz ur literally the only one here who's flashing on nougat bootloader lol

587.saboor said:
nah i dont really need to add the hint cuz ur literally the only one here who's flashing on nougat bootloader lol
Click to expand...
Click to collapse
I recently upgraded to the latest bootloader to see if it would help pie boot better.
Which it did not these roms issues freezing on boot up and video freezing is Samsung fault.
I have contacted them and I ask why they would released a buggy update their been giving me excuses instead of answers.
Back to Oreo for a couple months until I sell this phone no more Samsung!

mchlbenner said:
I recently upgraded to the latest bootloader to see if it would help pie boot better.
Which it did not these roms issues freezing on boot up and video freezing is Samsung fault.
I have contacted them and I ask why they would released a buggy update their been giving me excuses instead of answers.
Back to Oreo for a couple months until I sell this phone no more Samsung!
Click to expand...
Click to collapse
ye its complete bs that they give excuses and s*** like that smh

new 4/20 build is out
Changelog:
Call recording
Mobile data toggle in power menu

My phone broke, so development will be temporarily suspended till I get a replacement.
For now, as an "update" flash quantum kernel v2 and then magisk after flashing the latest version
For now, I'll see y'all later when I get a new replacement a8

Pls donate to me
paypal.me/youhavebeenyoted
This is just so I can fully pay for my replacement A8 which is $229 or make it more affordable for me
I'd be very thankful if you donate

lol i did say development was suspended till i get a replacement a8 but i just dont know what to do in my free time other than this
anyways new build 4/23 blah blah blah heres the changelog:
separated zip 2 for people with limited internet data i guess
updated base to a530w base
someone pls try this build and tell me if there are any freezes or not ASAP thanks
enjoy

587.saboor said:
lol i did say development was suspended till i get a replacement a8 but i just dont know what to do in my free time other than this
anyways new build 4/23 blah blah blah heres the changelog:
separated zip 2 for people with limited internet data i guess
updated base to a530w base
someone pls try this build and tell me if there are any freezes or not ASAP thanks
enjoy
Click to expand...
Click to collapse
What are the two zips

mchlbenner said:
What are the two zips
Click to expand...
Click to collapse
What two zips?
Theres 2 zips to flash for the rom
First one is the rom zip
Then the zip 2, ignore the ones that arent your model number

587.saboor said:
What two zips?
Theres 2 zips to flash for the rom
First one is the rom zip
Then the zip 2, ignore the ones that arent your model number
Click to expand...
Click to collapse
I have discovered that on the latest pie you have use custom kernel or you will get locked but reflashed stock then I was able to flash twrp.

mchlbenner said:
I have discovered that on the latest pie you have use custom kernel or you will get locked but reflashed stock then I was able to flash twrp.
Click to expand...
Click to collapse
Lol the zip 2 contains the custom kernel

[UNOFFICIAL][wrappedkey] LineageOS 16 with CAF encryption support

Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet

Thanks ?

Thank you for the ROM!

There's a Typo in the ROM os version description.

cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.

jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.

jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?

Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.

jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first

Download link not working
Edit: UC browser was the culprit

dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue

gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer

rom keeps rebooting into twrp , i did every step

gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too

Device not charging above 86%. Anyone else facing this bug ?

PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!

lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build

PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.

lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint

Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.