Heres the Latest CM11 Snapshot M12 that CyanogenMod released
This is Android 4.4.4
This ROM includes:
- F2FS-ALL (System,Cache and Data)
- PA Micro GAPPS (Feb 15, 2015)
- M-Kernel a69 (credits to Metallice for this Awesome kernel)
- All CM11 unnecessary apps (bloatware) Removed.
- AdBlock (02102015) thanks to BSDgeek_Jake
Installation:
Theres tons of guides here on how to do this:silly:
- If you have already F2FS-ALL your System,Cache and Data using TWRP 2.8.5 or later
Just do a Factory Wipe in TWRP and manually Wipe System for a Clean install.
Doing so Would Not Format your Internal Storage.
- Install CM11 SNAPSHOT M12 F2FS-ALL-grouper.zip
- Then Flash the latest SuperSU
- Wipe Cache and Davlik
- Reboot
- Enable ART(optional)
- Install Nova Launcher for More Speed(Highly Recommended)
Download Links:
NEW: F2FS-ALL
ROM:CM11 SNAPSHOT M12 F2FS-ALL-grouper
MD5: 5DEDCDB4435549CE93811A25E6128C63
NEW: EXT4
ROM: CM11 SNAPSHOT M12 EXT4-grouper
MD5: E2CC59B4C59094BD20706EC16F0B2E59
OLD:
Rom: CM11 M9 F2FS-ALL Grouper
MD5: ced60d458ba060da7c3edc696d47bc5f
Get latest SuperSU here: SuperSU 2.46
I've got pristine CM11 M8 with clockwork mod 6.0.4.3
There are *lots* of posts... but can anyone direct me to a clear safe path from this to M9 with F2FS system and data?
There are many posts that involve fiddling with custom kernels on each update, and so on, but I want to avoid that and just have rolling CM 11 updates with support for F2FS on system and data.
thanks
samjam said:
I've got pristine CM11 M8 with clockwork mod 6.0.4.3
There are *lots* of posts... but can anyone direct me to a clear safe path from this to M9 with F2FS system and data?
There are many posts that involve fiddling with custom kernels on each update, and so on, but I want to avoid that and just have rolling CM 11 updates with support for F2FS on system and data.
thanks
Click to expand...
Click to collapse
Use [ROOT] Rashr - Flash Tool to install the latest TWRP recovery.
Then follow this guide [Guide][WIP] To ALL-F2FS
animatrix999 said:
Use [ROOT] Rashr - Flash Tool to install the latest TWRP recovery.
Then follow this guide [Guide][WIP] To ALL-F2FS
Click to expand...
Click to collapse
Darn, that guide didn't work, failed flashing;
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/usb-otg/CM11 M9 F2FS-ALL Grouper.zip'
On reboot it is stuck at "Google" screen with unlocked padlock
I have TWRP 2.7.1.1 (flashed using RASHR)
[EDIT] I repeat f2fs and try again and this time it works
Ack! now I restore data the restore will first format as ext4;
so to backup the ext4 data ina way I can restore it, I get a command window in /data and do:
tar -c . > /usb-otg/data.tar
then reboot back into recover and make data as f2fs again, and then:
tar -xv < /usb-otg/data.tar
Although data restored I had to so a wipe for the new system to work properly.
Thanks animatrix999 this is much slicker than CM11 M8 standard.
Only fault is also with CM11 standard is that Google play videos won't play, even when downloaded, although music will
Sent from my Nexus 7 using Tapatalk
Hi,
Can this ROM be installed in Tilapia? Nexus 7 3g 2012?
sudipt123 said:
Hi,
Can this ROM be installed in Tilapia? Nexus 7 3g 2012?
Click to expand...
Click to collapse
Only on Nexus 7 WiFi 2012 model.
I went back to stock 4.4.4 (with hacks to get boot to load), loaded twrp 2.7.1.0 with fastboot, rooted, left bootloader unlocked, and movies play OK.
I found that a twrp backup consists of tar files; e.g. data.ext4.win000 and data.ext4.win001 so I migrated bacl to f2fs and restored data manually by getting a shell in the backuo dir and running:
tar -C / -x < data.ext4.win000
tar -C / -x < data.ext4.win001
and that restored fine but most apps still failed unless I re-installed. google play movies and tv had an update and it didn't crash after the update but still could not play any movies so i think maybe there is a drm library missing or something.
So I am back to 4.4.4 stock image with trim but no f2fs.
I may do a diff on the files to see what might be missing from this all-f2fs image
- intersting the official 2048 force closes in stock but not in this m9 image.
This ROM is missing
/vendor/lib/mediadrm
/vendor/lib/mediadrm/libwvdrmengine.so
which sound related
Also missing: /vendor/lib/libfrsdk.so
but i don't know what that is
also: /lib/libchromeview.so
Later I will try transfer the libwvdrmengine.so to see if google play movies & tv starts working
Not just google play movies & tv, but also bluetooth is not working on M9 as well.
I don't know if it was working on M5 (did not try that).
How long does the first boot take. Think i have s bootloop. It's almost 15 minutes on the cm logo
r-l said:
How long does the first boot take. Think i have s bootloop. It's almost 15 minutes on the cm logo
Click to expand...
Click to collapse
Did you convert all the file systems to f2fs?
samjam said:
Did you convert all the file systems to f2fs?
Click to expand...
Click to collapse
All ready fixed it. I flashed it after coverting to f2fs and got a bootloop. Then i sideloaded it with the Nexus toolkit and flashed it again and now it works.
Let's see if f2fs really works (first time using it)
---------- Post added at 12:44 PM ---------- Previous post was at 11:56 AM ----------
Next problem i can't cast (bubbleupnp or any other app) to my chromecast anymore.
Edit: also fixed
r-l said:
All ready fixed it. I flashed it after coverting to f2fs and got a bootloop. Then i sideloaded it with the Nexus toolkit and flashed it again and now it works.
Let's see if f2fs really works (first time using it)
---------- Post added at 12:44 PM ---------- Previous post was at 11:56 AM ----------
Next problem i can't cast (bubbleupnp or any other app) to my chromecast anymore.
Edit: also fixed
Click to expand...
Click to collapse
How did you fix them?
Fix what? Chromecast?
Did a hard reset and rebooted my tablet a few times
jazzespresso said:
Not just google play movies & tv, but also bluetooth is not working on M9 as well.
I don't know if it was working on M5 (did not try that).
Click to expand...
Click to collapse
Bluetooth works fine
r-l said:
Bluetooth works fine
Click to expand...
Click to collapse
mine not....it was clean install by the way...no idea...could be one of xposed or CM11 themes causing?
jazzespresso said:
mine not....it was clean install by the way...no idea...could be one of xposed or CM11 themes causing?
Click to expand...
Click to collapse
Was a clean install too. Flashed it as my first rom on f2fs. Using xposed an android L cm theme
Works for me. I don't use xposed
animatrix999 said:
Only on Nexus 7 WiFi 2012 model.
Click to expand...
Click to collapse
Hi, animatrix999 , can you build the ROM for tilapia with M-Kernel a69 or point me in the right directon? I have the ROM- to F2fs convert app
Related
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 7"
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
CHECK KNOWN ISSUES BEFORE FLASHING. MAY NOT BE GOOD ENOUGH FOR DAILY USE.
Official nightly builds can be found here:
http://download.cyanogenmod.org/?device=tate
Download Google Apps for Android 5.1:
https://www.androidfilehost.com/?w=files&flid=25361
(Choose newest *-5.1-* file)
NOTES:
Older versions of TWRP will show a "mount failed error". This is safe to ignore.
First boot after a clean wipe will take a LONG time. Be patient.
KNOWN ISSUES:
Use XDA Bug Reporter
SCREEN SHOTS:
Use XDA Screenshots
XDA:DevDB Information
CM12.1 KFire HD 7 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2015-06-24
Created 2014-12-27
Last Updated 2015-06-24
Reserved
KERNEL UPDATES for Lollipop Android 5.0 / 5.1
Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
Combined defconfig setup to better support all HD models
Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
Picked IPV6 routing changes from Google's common 3.4 kernel
Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
Reserved
Android 5.1 / CM-12.1 changes:
SElinux Enforcing as default enabled
Woke up from my nap and saw this! Amazing!!! Downloading now
Edit: I would like to point out that there will be a mount failed error in TWRP when flashing the build. Ignore the error and be patient. It'll flash! It took about 2-3 minutes.
Edit2: And it has booted! Approx time is 8 minutes. Be patient on your first boot guys!
Very very thanks Hashcode you are awesome!
Always knew we could rely on the master. Flashing asap once downloaded.
Hashcode, I flash it and 5Ghz Wifi works for me
davigar said:
Hashcode, I flash it and 5Ghz Wifi works for me
Click to expand...
Click to collapse
Mines not. It's not detecting my 5Ghz network.
Can confirm the 7/8 minute 1st boot. Must be to do with initialising ART?!
Anyway, now for a play and a few customisations.
Once again, Thank you and hope you managed to find some time to enjoy Christmas!!
I just got 5Ghz to work. At least on mine. So since a lot of my android devices don't detect my 5Ghz I had to do some researching. Changing the 5Ghz channel from Automatic/Auto to 44 or 48 will make it work. Can confirm on my Nexus 4 and the Kindle. Works superbly!
Source
Glad to see you sorted out all of the issues quicker than any of the other developers could. We're not horrible, but there's no matching the talent that you have when it comes to this type of thing.
And we thought we were close ?. At least we learned a lot and more to come! Thanks Hash for putting your time and effort into this.
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Everything seems to be working very nicely so far. Just flashed about an hour ago. Seems much smoother than kit kat did. Thank you very much. Looking forward to the updates.
Sent from my Amazon Tate
cell2011 said:
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Click to expand...
Click to collapse
As the title of thread says, its in Alpha. But may I ask what FC's your'e getting? I'm running the build on my Kindle at the moment and the only FC I get is Bluetooth Sharing. Bluetooth was activated on the main user and when I switch to another user it FC's.
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
cell2011 said:
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
Click to expand...
Click to collapse
There's no need to flash SuperSU . SuperUser is built in already and working. Wipe System, Data, Cache, and Dalvik. Then flash the ROM and gAPPS.
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
Is anyone else getting a bootloop when clicking on reboot? I have to fully power down to be able to make it boot. Also, I'm unable to tick unknown sources when on another user (using Multi-Acc). Don't worry, I'm not downloading pirated apps xD. I download the APK's over at the Android Apps and Games forum.
Awesome work man! Flashing now...
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
Random Username said:
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
My other problem is that I can't log in with my Google account? Is this maybe related?
Click to expand...
Click to collapse
I get the same error and google account works fine for me
F2FS for ACE
AOSP only!
S-ON USERS SEE ADDITIONAL INSTRUCTIONS BELOW
Should work on all current CM12 or most any of our LP-based AOSP ROMs around here that use a current CM based kernel/trees
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery This is the same link the current 2.8.1.1 TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Fstab conversion zip Fstab is the file used by the kernel to determine how to mount all partitions. CM default is all EXT4. To utilize F2FS we need to modify your fstab. This installer is for use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab according to your current partitions and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Ace
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new TWRP recovery img if you are not already on it.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit "Repair or change filesystem". Convert to F2FS. Repeat for cache.
6. Flash the fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly ( manually, do not let OTA update flash on its own, you will not be given the chance to flash fstab zip and you WILL BOOTLOOP. Should this happen return to recovery and perform step 2)
2. Flash fstab conversion zip.
3. Reboot and profit.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
S-ON USERS
Code:
If someone has S-ON device, you still can use it like this:
After flashing ROM, reboot to bootloader and fastboot flash boot.IMG provided in ROM.zip as normal. This is required to get any new kernel updates. Return to recovery and make your desired f2fs changes and flash the f2fs script.
After you flashed this f2fs script, the modified boot image will be located at: /tmp/newboot.img
Now we need to download it by using adb in recovery: adb pull /tmp/newboot.img boot.img
After that, you can flash boot.img via fastboot and reboot as usual. (fastboot flash boot boot.img)
Code:
CHANGELOG
V1.0 - Initial release
V2 - switch to by-name fstab entries to go with cm12 nightlies after 1/9/15
V2.1 - typo fix
V3 - corrects fstab name after file name change introduced in 1/14 nightlies and beyond
Source:
Kernel: https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/tree/cm-12.0
Device tree: https://github.com/OpenDesireProject/android_device_htc_ace
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
Contributors
jrior001 @Mustaavalkosta, @paulb-nl and any others that have helped keep msm7x30 alive
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-01-06
Created 2015-01-06
Last Updated 2015-01-06
Important to note, all issues related to f2fs need to stay here and out of the cm12 thread. This is a experimental tweak and mustaa has enough to deal with, without unsupported drama. Please be respectful of this. Thanks and enjoy!
Cant find Convert to F2FS in recovery
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
xdagee said:
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
Click to expand...
Click to collapse
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Mustaavalkosta said:
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Click to expand...
Click to collapse
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
xdagee said:
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
Click to expand...
Click to collapse
Very good, interested what your experience is. I ran a bunch of tests when I got this working on my One XL(Evita) and found f2fs to be slightly better for heavy read/write action things like installing apps(especially that initial Google restore of apps on first boot) and more less the same or slightly better in daily use.
First of all- every next restart is rom more responsive. (it has it's own limitations, of course ) I'm not testing very much, but using as usually. Second- Gallery app doesn't show pictures until i enabled root access.. this is new problem, ringtone was unknown too, 0103 release was fine with this. So..don't know where is problem, but i see that this is good step. Thank you!!!
edit: @Mustaavalkosta , @jrior001 : this is not very good that your threads are separated. Because I see new problems that i never seen before, so I think this is problem of F2FS. In my previous installed nightly (it was one of those "smaller", so no 0103 as I wrote before, but maybe 0101?) was calculator OK, media player too, gallery too and ringtones too. Now I have problem with all - direct after restart i see pictures in gallery but after (what?) again i can't see it. Ringtone - i set ringtone and it was ok, but later it changes to "unknown" - so no ringtone. Audio player has similar problem.
...on other side - it is really good. (Musta's ROMS and this too). Thanks for your work!
Updated OP with S-ON flashing instructions courtesy of @kib0rg
..bad evening... after trying to install app- it ends in reset, system no more started..
I've just uploaded a new v2 script to go with tomorrow's nightly. There are significant changes to the fstab that warranted this new version.
can i use this only in clean new installation? I have installed 0111 version.Can i use it with dirty flash of new nightly?
I don't know what i'm doing wrong. After flashing F2FS v2 phone stuck on black screen - no cm bootscreen appears..
Edit:
after flashing v1 phone normally booting. So there is problem with v2 or after (dirty) flashing new rom I use v2 instead of v1?
Phone stacked after flashing nightly.
As much testing hasn't be done on this; which we know the reason. being that if we are able to get a much more daily driver like ROM then more people will try testing f2fs. But for yesterday as I try to update my recovery, i found out that ace_f2fs_fstab_script_cm12_v2.zip has been uploaded. I downloaded flashed alongside 20150110's nightly. After flashing, phone get stacked just after boot screen appears.
@xdagee - what CM12 nightly do you use? I think last two has problem with dialer/phone. Do you use F2FS script v1?
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
jrior001 said:
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
Click to expand...
Click to collapse
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
danvo01 said:
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
Click to expand...
Click to collapse
Hmm...I tested before I uploaded but I'll check it out tonight.
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
working fine, thanks
jrior001 said:
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
Click to expand...
Click to collapse
thats okay, we've got your back
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
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.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
- video record
Links
5. 20210419: april security patch: https://drive.google.com/file/d/1aXGrtLrmqAQEYMxcvzck9hJOd-f4OVke/view?usp=sharing
4. 20201220: december security patch: https://drive.google.com/file/d/1KMqFHfDORMCsNXGSrpWkh5IIZp1ZN5oJ/view?usp=sharing
3. 20200815: august security patch: https://drive.google.com/file/d/1oVmXeSfa7p9d4L2nSmiigCjNCo60So7n/view?usp=sharing
2. 20200724: july security patch: https://drive.google.com/file/d/15_4QTR5vKMRvIwXevu1QYb3WHMZsCW72/view?usp=sharing
1. 20200616: initial build, june security patch: https://drive.google.com/file/d/1is2tRwqsd7Nm9dhpkPrGbpgg7AjnOkZh/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Recovery
this is my build, the error with the screen off is still present, but I added an option for twrp with unlimited screen timeout, as a result, the screen does not automatically turn off.
for recovery: https://drive.google.com/file/d/1UeC4LwVEA6d46y0UPpuuipHbcjAtAo0Q/view?usp=sharing
for odin: https://drive.google.com/file/d/1WmAzhWkq9l_3d4m3Ft1xmihZaYfccUym/view?usp=sharing
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_picassolte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_picassolte
Thank you for this build.
Does anybody else have the problem that picture-in-picture mode is not working?
I'm watching a video with the German sky go app. Pressing the home button takes me to home screen and does not show the video in the small window.
This was working with the Android 9 build.
The permissions are set for the app.
Thank you for this version.
Warning: I initially tried with GApps Stock (like I did with 16.0) and it totally messed up the system (Pixel Launcher crashed constantly, attempting to log in to Google account resulted in a black screen). Now, with Pico, it seems to work alright.
deleted
Can i use a t525 rom to my t520 tablet? I mean, its the same tablet but without lte? If not, pls make a android 10 rom for the t520 tablet
Tabletbungie said:
Can i use a t525 rom to my t520 tablet? I mean, its the same tablet but without lte? If not, pls make a android 10 rom for the t520 tablet
Click to expand...
Click to collapse
T520 is not just T525 without LTE. T320, T325 and T525 have Qualcomm Snapdragon SoC's inside, so most of the codebase can be shared between them. T520 has Exynos which is quite different.
help
i had an error
it says
unknown command [retry_update]
Updater process ended with ERROR: 7
What i should do?
please help me
Just updated to 20200724 with GApps Pico, Magisk and Viper4Android. Nothing out-of-the-ordinary stands out, so in all regards this appears to be a safe upgrade.
в прошивке - LineageOS 17.1 | Android 10.0 Q 202007 24 (Samsung Galaxy Tab Pro 10.1)
не работает (функция не доступна) - поверх других приложений
Valera1978 - обратите внимание на проблему! исправьте пожалуйста!
....
in the firmware - the Lineages of 17.1 | Android 10.0 Q 2007 24 (Samsung Galaxy Tab Pro 10.1)
does not work (function is not available) - on top of other apps
Valera1978-pay attention to the problem! please fix it!
I tried to flash lineageOS 17.1 & 16 but got this error in attachment
What's wrong
Witzker said:
I tried to flash lineageOS 17.1 & 16 but got this error in attachment
Click to expand...
Click to collapse
Maybe try this?
M0lle said:
Maybe try this?
Click to expand...
Click to collapse
THX for taking care but it was my fault
I have not red carefully the instruction for recovery
I had an old version
Now installed the recommended one
for recovery: https://drive.google.com/file/d/1UeC...ew?usp=sharing
Here I have another question
when I go to TWRP -Install Choose the TWRP zip I only installed image not the Option Boot.
Was This OK?
TWRP is starting correctly and I have successfully flashed the image of June (1) & PICO.
BUT I have NO sound!!
How do I install the updates?
Links
3. 20200815: august security patch: https://drive.google.com/file/d/1oVm...ew?usp=sharing
2. 20200724: july security patch: https://drive.google.com/file/d/15_4...ew?usp=sharing
1. 20200616: initial build, june security patch: https://drive.google.com/file/d/1is2...ew?usp=sharing
Just flashing the latest (3) over the old
or flashing the next update (2) then the latest (3)
OR wipe and flash the Latest (3) ?
PLS Help again
THX
Witzker said:
How do I install the updates?
Click to expand...
Click to collapse
Wipe Art/Dalvik Cache, Cache and System
Flash the ROM image (the latest one only)
Flash the GApps
(Flash Magisk if you want root)
Reboot to System
Wait...
M0lle said:
Wipe Art/Dalvik Cache, Cache and System
Flash the ROM image (the latest one only)
Flash the GApps
(Flash Magisk if you want root)
Reboot to System
Wait...
Click to expand...
Click to collapse
SO I will lose all my settings?
Witzker said:
SO I will lose all my settings?
Click to expand...
Click to collapse
No, you won't. Data and Internal Storage will stay intact. This is the procedure I follow when I update from one version of e.g. 17.1 to newer one. Only when upgrading to a new major version do I fully wipe the device.
If you're unsure, backup your stuff with "ROM Settings Backup" and "Titanium Backup" before wiping anything.
THX Great worked ok.
BUT still no sound!
How to check if there is maybe a hardware problem?
I'm going to install this Rom (thanks to developer) , is the sound problem real?
alonzimanuel said:
is the sound problem real?
Click to expand...
Click to collapse
I haven't had any sound problems with either 16.0 or 17.1.
Witzker said:
THX Great worked ok.
BUT still no sound!
How to check if there is maybe a hardware problem?
Click to expand...
Click to collapse
My tab also freezes during browsing websites or open other apps!
What can be the reason ?
Are there some settings to change??
PS: I use Microsoft launcher
Witzker said:
My tab also freezes during browsing websites or open other apps!
What can be the reason ?
Are there some settings to change??
PS: I use Microsoft launcher
Click to expand...
Click to collapse
Don't know that launcher (mine Nova Prime) but did you test turning of animations in dev settings?