Database Info

[ROM][GT-P511X][4.2.1]AOSP - Experimental 12/22/2012

Disclaimer: I have no idea if this will run properly, therefore it is considered experimental.
I do not have a p511x and haven't got the balls yet to flash my p311x build on my tablet.​
If you don't have experience recovering from stuff messing up due to badness happening, please don't flash this. I will not be able to help you recover if something goes wrong.
What this is: Straight up AOSP 4.2.1 from source with the Gtab2 p51XX device code from CM10.1. This is as vanilla Android as you'll get if it boots. The zip was made using the regular otapackage method with some modifications to the makefile to allow for extra device asserts and removal of the install-recovery.sh script. I couldn't get the CM zip stuff (squisher) working with the vanilla AOSP build structure.
The su executable is included in /xbin, but I have no idea if root actually works. I do know that busybox is nowhere in the zip. You'll have to install ChainFires' SuperSu from the Play Store to see if you can do all the cool stuff that root lets you.
Downloads:
p5100: Don't have a build yet, my build system sucks and takes 4.5 hours to do a clean build. Please don't ask for an ETA, I'll be out of town for a while without access to the build system.
p5110: http://www.mediafire.com/?48w04zlx3xa9ukr md5: a12208f385abcd3ac0d24faee77d76bf
p5113: use p5110
Issues:
I have no idea
Google Apps can be found here, I would assume you'd need to pick the latest one for CM10.1.
Installation:
Ensure you're running the latest ClockworkMod Recovery
Copy zip of ROM and GAPPs to your SD Card
Reboot to Recovery
Flash ROM
Flash GAPPs
Perform a Factory Reset
Reboot
Cross your fingers and hope it boots...
Follow CM10.1's install procedure after the reboot here
Recommendations:
None at this time
Credits:
codeworkx and teamhacksung for their work on CM10.1
frankdrey for his initial testing of not totally working ota zip packages
Screenshot:
Don't have any...

Stealing this one just in case.

Thank for your effort itest it and i see you later if work or not work
Envoyé depuis mon GT-P5110 avec Tapatalk
---------- Post added at 12:35 PM ---------- Previous post was at 12:11 PM ----------
ok i test it and i stay on startup logo dont boot

coelho_ said:
Thank for your effort itest it and i see you later if work or not work
Envoyé depuis mon GT-P5110 avec Tapatalk
---------- Post added at 12:35 PM ---------- Previous post was at 12:11 PM ----------
ok i test it and i stay on startup logo dont boot
Click to expand...
Click to collapse
Thanks for the info, did you by chance have it hooked up to adb when it was attempting to boot?

Not booting
Same problem here as well, It hangs at the boot logo. I've also noticed something intresting when I flashed it in CWM, When I flash it, it says "Warning: No file_context" weird huh?

I think I shall give this a shot again
Sent from my GT-P5110 using xda app-developers app

[ROM][EXT4][F2FS-All] CM11 Snapshot M12 AIO [Gapps][M-Kernel][Adblock][No Bloatware]

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

[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

[ROM][discovery][PIE] Resurrection Remix [DISCONTINUED]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To God be the glory, I finally finished a XA2 Ultra build of Resurrection Remix! It's Resurrection Remix, Pie flavored!
WARNING: This is for phones that are now using the 50.2 firmware base! There is still an old build for the 50.1 firmware base, but I recommend you upgrade to 50.2 firmware.
"We work to make your android experience elegant. Handpicked features beautifully packed into one ROM."
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
A huge thanks to the Resurrection Remix team!​
Another huge thanks goes out to @LuK1337 for all of the great development that he does on the Sony Xperia XA2 Ultra! He did most of the heavy lifting by making a great LineageOS build, upon which this RR is based. Please note, this is an UNOFFICIAL ROM.
Disclaimer: Resurrection Remix is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make Resurrection Remix, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
This Unofficial Resurrection Remix Pie ROM was built for H3223 (discovery), but may work on some of the other variants, please try at your own risk. However, if you do try it on another variant, please be sure to let me know in the comments how it worked.
Downloads:
Rom Download link:
WARNING: This is only for those on firmware versions 50.2.xxxxxx, not for those who are on firmware versions 50.1.xxxx. I recommend everyone update to 50.2 firmware!
http://www.mediafire.com/folder/el24nm0l3m38y/50.2_based
WARNING: This is only for those on firmware versions 50.1.xxxxxx, not for those who are on firmware versions 50.2.xxxx and up. This old version is not updated, but works fine.
http://www.mediafire.com/folder/15nb0swbcqcxi/50.1_based
If there is an ENG and USERDEBUG build, the ENG build is marked "ENG" for testing purposes only. You can install anything you want, but I recommend not installing the ENG build.
Gapps link:
http://opengapps.org/
If desired. Personally, I've gone Gapp-less.
Installation instructions:
-Download ROM and gapps, and put them on your removable sdcard storage. (Or leave on your computer and flash with adb sideload.)
-Reboot into the bootloader.
-Fastboot boot your TWRP.
-Backup what you had. (Just to be safe.)
-Wipe everything and format data.
-Install Rom. (Either from adb sideload or from your removable sdcard storage.)
!!!IF YOU GET AN ERROR, MAKE SURE YOU ARE USING THE LATEST TWRP!!!
-Reboot to system and enjoy!
If you also want Gapps:
-Reboot again into the bootloader.
-Fastboot boot your TWRP.
-Install Gapps. - Optional
If you plan to install magisk (good idea), then let the rom boot the first time, then go back to TWRP and flash magisk. This is optional, of course.
What works:
Code:
So far everything that I have tried works, such as
- Camera for pictures and video!
- Phone calls
- Data 3g/LTE
- Bluetooth
- WiFi
- MTP
- FM Radio
etc....
What doesn't:
Code:
- Nothing else that I know of, but if you find something, please let me know so we can try to fix it!
Source Code:
https://github.com/ResurrectionRemix
Official website:
http://www.resurrectionremix.com/
My device trees, vendor blobs, and kernel source:
https://gitlab.com/alaskalinuxuser/android_device_sony_discovery
ROM OS Version: 9.0 Pie
RR version: 7.0.2
ROM Kernel: Linux 4.4.153
Based On: The best of every ROM, but particularly based on LineageOS.
Created 2019-08-16
Last Updated 2019-11-04

Change log:
2019-08-17
RR accepted my commit:
https://github.com/ResurrectionRemi...mmit/db98cc9253b8680005b90122c48b40f633dc04e5
2019-08-16
-7.0.2 stable ENG and USERDEBUG build.
Had to edit a lot of whitelist permissions issues in RR itself to make this work. I created pull requests with RR, but if they don't add them, it makes repo sync difficult as I will have to make my edits all over again.

Rom notes:
As @Ultramanoid pointed out in LineageOS https://forum.xda-developers.com/showpost.php?p=80053444&postcount=219 You can use Open Camera to allow you to switch between all three cameras (one rear, two front).
Want to build your own custom kernels, custom roms, or learn the ins and outs of development? You can check out my video tutorials with over 24 hours of video and explanations here:
https://forum.xda-developers.com/android/general/guide-how-to-build-custom-roms-kernel-t3814251

Thanks given! Thank you so much man! Don't get me wrong I love Lineage but I was ready for some more rom love ?

Question though, I'm on the latest nightly of lineage, can I wipe and drop this gem on it with success?

appleknight said:
Thanks given! Thank you so much man! Don't get me wrong I love Lineage but I was ready for some more rom love ?
Click to expand...
Click to collapse
Yeah, I think @LuK1337 and the LineageOS team does a great job. I just like having a little variety, myself.
appleknight said:
Question though, I'm on the latest nightly of lineage, can I wipe and drop this gem on it with success?
Click to expand...
Click to collapse
You sure can, because that's what I just did. However, you may have to wipe and format data. :good:

Loving the rom keep up the good work? everything works but SD cards which was the same on lineage. Other than that this rom has the rr customization and is smooth like butter!

No issues here!

Yodasgodfather said:
Loving the rom keep up the good work everything works but SD cards which was the same on lineage. Other than that this rom has the rr customization and is smooth like butter!
Click to expand...
Click to collapse
appleknight said:
No issues here!
Click to expand...
Click to collapse
Great! Thanks guys! I used to build roms all the time, back before Oreo, but I took a break for a while and I'm trying to get back into the swing of things. I'll try to chase down that sdcard issue, I didn't have one in the phone to test it.
My usual MO is to build Lineage (already done by LuK1337), RR, AOKP, and SlimRoms (I don't think Slim has a working Pie at the moment), then move on to custom kernel work. We'll see what we can get done here. I also have two of these phones, so I'm hoping to finish building these roms, then update the phone to 50.2 firmware and update the device trees, kernel, and blobs to match and see if we can update the roms for the latest firmware. I can only image that @LuK1337 already tried this, so there must be some hangup in doing so, but we'll see what we can do. No promises, since I'm not the most skilled dev, but that's the overall plan.

Yodasgodfather said:
Loving the rom keep up the good work everything works but SD cards which was the same on lineage. Other than that this rom has the rr customization and is smooth like butter!
Click to expand...
Click to collapse
I just tested my sdcard, and it came right up. I could access the files and I started watching a video from there. What specifically doesn't work for you when you use an sdcard so I can troubleshoot that?

Oh? Well then what am I doing wrong cause for some reason the phone will freeze on setup unless I remove it? I dirty flash and follow the steps mentioned above? Perhaps is their a certain format aosp or certain Roms prefer like exfat or fat32... Etc

Yodasgodfather said:
Oh? Well then what am I doing wrong cause for some reason the phone will freeze on setup unless I remove it? I dirty flash and follow the steps mentioned above? Perhaps is their a certain format aosp or certain Roms prefer like exfat or fat32... Etc
Click to expand...
Click to collapse
Thanks for the info. So a few thoughts and questions, so we can get to the bottom of the issue:
Thought - I highly discourage dirty flashing. You never know what is left over from the last ROM. It makes trouble shooting very difficult.
Question - does it work without flashing gapps or magisk, just when you flash only the ROM? (This works for me here, just a clean install with only the ROM. I don't use gapps anymore, so that may matter.)
Question - if you do flash gapps or not, does it work if you boot the phone without it for the first boot, then power down and put it in for future use? E.g., does it work on subsequent boots, after setup is complete?
Question - what firmware are you running? And what phone variant?
Thanks, these things will help. Also, a huge help is pulling logs with logcat, so I can see the errors about the sdcard.
Question for the group: is anyone else successful in using the sdcard?

Just as a side note, I tried using the lineage addonsu zip(since this is lineage based). It definitely adds root to the developer options menu, but does nothing when an app tries to gain root( no dialog, toast etc..) just in case anyone wanted to know. So I went with magisk ?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
AlaskaLinuxUser said:
Thanks for the info. So a few thoughts and questions, so we can get to the bottom of the issue:
Thought - I highly discourage dirty flashing. You never know what is left over from the last ROM. It makes trouble shooting very difficult.
Question - does it work without flashing gapps or magisk, just when you flash only the ROM? (This works for me here, just a clean install with only the ROM. I don't use gapps anymore, so that may matter.)
Question - if you do flash gapps or not, does it work if you boot the phone without it for the first boot, then power down and put it in for future use? E.g., does it work on subsequent boots, after setup is complete?
Question - what firmware are you running? And what phone variant?
Thanks, these things will help. Also, a huge help is pulling logs with logcat, so I can see the errors about the sdcard.
Question for the group: is anyone else successful in using the sdcard?
Click to expand...
Click to collapse
No issues with sdcard here! H3223
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
Question: is there a hide navbar setting? If so I missed it so I'm using an app called custom navigation bar, which I've had to use in the past, tho for some reason on this rom it's sometimes difficult to get to appear when you swipe up from the bottom, any ideas?
---------- Post added at 06:37 PM ---------- Previous post was at 06:26 PM ----------
AlaskaLinuxUser said:
Great! Thanks guys! I used to build roms all the time, back before Oreo, but I took a break for a while and I'm trying to get back into the swing of things. I'll try to chase down that sdcard issue, I didn't have one in the phone to test it.
My usual MO is to build Lineage (already done by LuK1337), RR, AOKP, and SlimRoms (I don't think Slim has a working Pie at the moment), then move on to custom kernel work. We'll see what we can get done here. I also have two of these phones, so I'm hoping to finish building these roms, then update the phone to 50.2 firmware and update the device trees, kernel, and blobs to match and see if we can update the roms for the latest firmware. I can only image that @LuK1337 already tried this, so there must be some hangup in doing so, but we'll see what we can do. No promises, since I'm not the most skilled dev, but that's the overall plan.
Click to expand...
Click to collapse
Would definitely love to see some slim love ? I developed for the z ultra back in the day. I never have the spare time anymore, full time parent n all

appleknight said:
Just as a side note, I tried using the lineage addonsu zip(since this is lineage based). It definitely adds root to the developer options menu, but does nothing when an app tries to gain root( no dialog, toast etc..) just in case anyone wanted to know. So I went with magisk
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
No issues with sdcard here! H3223
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
Question: is there a hide navbar setting? If so I missed it so I'm using an app called custom navigation bar, which I've had to use in the past, tho for some reason on this rom it's sometimes difficult to get to appear when you swipe up from the bottom, any ideas?
---------- Post added at 06:37 PM ---------- Previous post was at 06:26 PM ----------
Would definitely love to see some slim love ? I developed for the z ultra back in the day. I never have the spare time anymore, full time parent n all
Click to expand...
Click to collapse
Hear you there, I've got three and one in the oven! Kids are great, but they'll keep you busy!
As for the Nav bar, go to settings, RR tools, navigation, navigation, enable nav bar. :good:
There are several options as well, fling, standard, edited, etc. You'd have to play with them to get it all sorted out how you like it.

Congrats man! I meant to autohide the navbar, I don't see an option for it.

It doesn't I'm not able to access it. Doesn't matter if I flash gapps or not the phone will not boot properly with the SD card in and it works fine on stock. It was the same issue on lineage os. The setup will be stuck in a loop say its searching for networks and eventually crash the system. When I inserted it just now it kept saying "phone is starting" and just crashed. Should I try formatting the SD card? I have xa2 ultra h3223 just in case your wondering...

appleknight said:
Congrats man! I meant to autohide the navbar, I don't see an option for it.
Click to expand...
Click to collapse
Thanks! Sorry I didn't understand your request. Yes, the "expanded desktop" option will auto hide the status bar and/or the navbar per your preferences. Settings, display, advanced, expanded desktop. A swipe up brings the bar back. :good:
Yodasgodfather said:
It doesn't I'm not able to access it. Doesn't matter if I flash gapps or not the phone will not boot properly with the SD card in and it works fine on stock. It was the same issue on lineage os. The setup will be stuck in a loop say its searching for networks and eventually crash the system. When I inserted it just now it kept saying "phone is starting" and just crashed. Should I try formatting the SD card? I have xa2 ultra h3223 just in case your wondering...
Click to expand...
Click to collapse
I think formatting the card would be wise. If you used it as "built in" storage before, instead of for transferring files (the initial question it asks when you first put one in) you can run into trouble with it on other ROMs or phones. I have the same phone, and it is working for me and for appleknight, so it must be something with your phone or card. Let me know if formatting helps. :good:

Ah that works, still for some reason though I have to swipe a few times to get it to appear, almost seems like the sensitivity is off or something it's weird
---------- Post added at 12:26 AM ---------- Previous post was at 12:08 AM ----------
So do you think the RR team will make this an official build? ?

appleknight said:
[/COLOR]So do you think the RR team will make this an official build?
Click to expand...
Click to collapse
Not likely.... They'd need a device maintainer. You know, some skilled dev to keep things working and running smooth. As far as I know, LuK is too busy. :silly:

So far I really like this as my daily driver

[ROM][UNOFFICIAL][matisse][millet] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Installation instructions :
Be sure to have installed latest TWRP recovery (you can find it in downloads) and latest Android Lollipop (5.0.2 for matisse, 5.1.1 for millet) firmware
Download the latest build and GApps (ARM, 9.0, I advice pico package) - if you'll go to wipe even internal storage, put them on a microSD or an USB OTG, or copy them after wiping it
Boot to recovery mode
Wipe > Advanced wipe > Select system, data, cache and dalvik/art cache (and, if you want to clean more, select even internal storage, which deletes all the content in /sdcard) and do swipe to wipe. When it finishes, go to home page
Install > select ROM zip file > swipe to flash and, when it finished, go to home page
Do the same thing to flash GApps
Reboot > System
Update instructions :
Be sure to have installed latest TWRP build
Download the latest build
Boot to recovery mode
Install > select ROM zip file > swipe to flash and, when it finished, go to home page
Reboot > System
Known issues :
Magnetic cover doesn't trigger magnetic sensor (it works, but it's too little sensible).
Some randomic minor issues with YouTube app (sometimes, after skipping ads in a video, you'll get just a grey screen - close and reopen video to fix the issue)
Some randomic issues with bluetooth MAC address (bluetooth app crashes always). To fix this, you need to get (take note!) the address by going to stock ROM and getting that from Settings > About tablet menu. Then, come back to LineageOS 16 and rewrite the file /efs/bluetooth/bt_addr by using root permissions and a root file explorer, or by using adb push/pull, better in TWRP.
In all millet, camera crashes when trying to take pictures and can't zoom
5 GHz WiFi networks between channels 149 and 161 are invisible to the Tab
In matisse3g and millet3g SIM isn't working
Downloads :
All models (from 2022-12 build): https://github.com/matteo0026/OTA/releases
Mirror for all models: https://t.me/tab4los
matisse (10.1) devices (until 2022-09 build): https://androidfilehost.com/?w=files&flid=304073
millet (8.0) devices (until 2022-09 build): https://androidfilehost.com/?w=files&flid=304074
TWRP recovery: https://forum.xda-developers.com/tab-4/development/recovery-twrp-recovery-matisse-millet-t4019831
GApps: https://opengapps.org/ (ARM, 9.0, I advice pico package)
Contributors
matteo0026, DJABHipHop, Alastor89, All the S3NEO devs that provided the base for developing Pie on Tab 4
Source Code:
https://github.com/lineageos for samsung msm8226 common device and kernel source, with some patches coming from Gerrit for device source
https://github.com/s3neo for matisse and millet and specific variants device and vendor source

Failed to flash
Hi I am running into an issue flashing your rom in recovery. I have TWRP 3.0 flashed and when I flash your rom I get the following error:
E: unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file /sdcard/lineage-16.0.20200108-UNOFFICIAL-milletwifi.zip
I have redownloaded the rom multiple times to verify that the zip isn't broken. I am flashing it on a SM-T230NU that is rooted as well.

Flash latest TWRP
---------- Post added at 08:14 AM ---------- Previous post was at 07:38 AM ----------
judgemstr said:
Hi I am running into an issue flashing your rom in recovery. I have TWRP 3.0 flashed and when I flash your rom I get the following error:
E: unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file /sdcard/lineage-16.0.20200108-UNOFFICIAL-milletwifi.zip
I have redownloaded the rom multiple times to verify that the zip isn't broken. I am flashing it on a SM-T230NU that is rooted as well.
Click to expand...
Click to collapse
But your device is neither millet (t33* series) or matisse (t53* series) so it is not compatible

SM-T335 / Tab4 8.0 LTE / milletlte
Thanks a lot for the ROM! 1st was trying to get the LightningFastRom running but ended up in a bootloop to recovery with the Lineage 16 versions.
Then got to the Telegram channels and saw there that you opened that thread @xda here and gave it a shot.
After a clean install I am really happy especially because the phone part works!
Not tested Skype yet and Camera is not really the burner anyways
Even so, any idea if there is a working Google Camera Mod available?
One thing I figured out: the tablet does not go to sleep/shuts down the display anymore if I close my cover (magnetic one). Any idea how to solve that?
Again thank you very much!!!

Everytime I try to install it with gapps I get a booloop in T530. I'm flashing ARM 9.0 Nano, is this correct?
Edit: NVM, just took longer to boot. Working flawlessly.

Nice dude!
Wow even though the tablet is old you actually made it happen! My tablet is now pretty useless so i can test this for you Good job dude

Great work first off...
I have reflashed a number of times:
1. os, 2. reboot to recovery, 3. flash gapps, 4a. flash su enabler for lineageOS (was not compiled with ‘export WITH_SU=true’) or 4b. even magisk.
Reboot, setup - enable root for apps/adb via developers tools. Works : but something stops it from going forward and 'sticking' then the app reverts to non-SU state and says Root not available.
I have searched, I have found little on this... any help would be appreciated. If there is an 'easy' way then great but many things are not ever so easy.
Thanks in advance...
*Edit*
It has something to do with more than just the ROM or flashing, on any 7.1.1 it is the same... not sure where to go from here.
SU can be installed and openly visible, even works for seconds and then KNOX? or Some other protection brings it back to unavailable.
**Final Edit**
Sorry everybody, I have not rooted since Gingerbread... I was getting rusty.
All is good, I only needed to mount /system as RW to copy my hosts file into place. I feel a bit silly.
@matteo0026:
Really great work, this tablet is doing GREAT with your ROM and TWRP. Thank you for taking the initiative!
Keep up the Community Love!

Thank you very much for supporting 6 years old devices... Please keep your work.

Has anyone had a problem with the milletlte/tmoT337T or T335 going directly into safemode after installation. It happened to me on LOS 14, 16 and the latest 20200110 build.
Thanks.

how do media apps work on the rom.any issues.also do plan on using the rom on the device as i have no longer bought tablets in a while.most of these devices have been phone as they have better performance then the mid ranged priced tablets.

donj001 said:
Has anyone had a problem with the milletlte/tmoT337T or T335 going directly into safemode after installation. It happened to me on LOS 14, 16 and the latest 20200110 build.
Thanks.
Click to expand...
Click to collapse
Are you sure that you installed latest firmware before installing this ROM?
mrk2815 said:
how do media apps work on the rom.any issues.also do plan on using the rom on the device as i have no longer bought tablets in a while.most of these devices have been phone as they have better performance then the mid ranged priced tablets.
Click to expand...
Click to collapse
What do you mean by media apps? Make practical examples, please.
Anyway, I'm going to build and upload new builds with security patches updated to February 2020. So, new builds start from today, 21st February. I can't build and upload all the builds fast because I'm using a medium-range laptop and an ADSL connection at 1 Mbps in upload.

matteo0026 said:
Are you sure that you installed latest firmware before installing this ROM?[/QUOTE
I'm on the last 5.1.1 that TMobile released for that Tab 4. But I'm glad for the response and I'll give the new builds a try. Thank you.
Click to expand...
Click to collapse

donj001 said:
matteo0026 said:
Are you sure that you installed latest firmware before installing this ROM?
Click to expand...
Click to collapse
I'm on the last 5.1.1 that TMobile released for that Tab 4. But I'm glad for the response and I'll give the new builds a try. Thank you.
Click to expand...
Click to collapse
Oh now I saw that I forgot to build and upload the version for milletltetmo! Sorry! When it'll be uploaded, I'll tell you.

* Last firmware update 12/2016
* TWRP milletltetmo image
* Magisk v20
* Full wipe
* No errors on install
Flashed the latest 16 build.
Bootloops every time.
Could not get logcat
I am very happy to test the ltetmo builds. I'm not sure anyone but me is using it.
Thanks

matteo0026, thanks for build these roms for tab4 tablet.i have another tablet which devs don't even want to develop for which is stuck on android 7.1.2.at least the tab 4 has multi development love even though both tablets are from the same time frame of 2014. a tab 4 which i got from a family member and plan on using it asa good tablet .wwill you anounce hwen you have new builds here.thanks again. the media apps that i was talking about playing wer netflix, youtube and apps like that . i know that apps like tune in , and i heart radio fm usa will probably work for streaming audio i was jsut asking about video playback. .

any plans to keep teh project going with monthly security updates or maybe think about a lineage 17.1 build to android 10 for the devices.just wondering. i have flashed and kept alot of devices alive through either official or unofficial builds of cm 12-14, to lineage 14.1 to 16.0 from all the way from samsung galaxy s2 to all the way up to nexus 6p and pixel XL. so i dont mind doing the work and learning. .

mrk2815 said:
matteo0026, thanks for build these roms for tab4 tablet.i have another tablet which devs don't even want to develop for which is stuck on android 7.1.2.at least the tab 4 has multi development love even though both tablets are from the same time frame of 2014. a tab 4 which i got from a family member and plan on using it asa good tablet .wwill you anounce hwen you have new builds here.thanks again. the media apps that i was talking about playing wer netflix, youtube and apps like that . i know that apps like tune in , and i heart radio fm usa will probably work for streaming audio i was jsut asking about video playback. .
Click to expand...
Click to collapse
Don't do 2 messages. We are in a forum, so you have all the time to edit the old post.
Anyway, I don't think Netflix works, as other feedbacks told me (app can't be found on play store because of problems with safetynet I guess), but YouTube yes, of course.
mrk2815 said:
any plans to keep teh project going with monthly security updates or maybe think about a lineage 17.1 build to android 10 for the devices.just wondering. i have flashed and kept alot of devices alive through either official or unofficial builds of cm 12-14, to lineage 14.1 to 16.0 from all the way from samsung galaxy s2 to all the way up to nexus 6p and pixel XL. so i dont mind doing the work and learning. .
Click to expand...
Click to collapse
I'll keep this build with security patches. Unfortunately, I haven't a good computer to build them and a good Internet connection to upload them, but I'll try to do all I can do.
Lineage 17.1 is already on the way (look at the LightningFastRom 17.1 by DJabHipHop), but it isn't as stable as lineage 16.0. Another thing is that I have a matissewifi, but I can't use it because the mobo is broken and probably requires a work of microsoldering. So, I can't test personally the builds...

Hi,
I´ve installed this rom on my Tab 4 10.1 wifi a few days ago and I´m really impressed. Thank you for your great work!
The rom is working smooth and stable in general. But there´s a problem with the Xiaomi Home app. I'm using this app to control my Roborock S5. Starting the app works fine. It´s even possible to log in or create a Xiaomi Account etc. But when I try to open the control panel of the Roborock S5, the whole system crashes while the app is downloading the map from the Roborock S5. The system reboots completely without any warning. This happens every time at the same moment. On other devices (Tablets, Phones) the app works without any problems. I had the same issue with another app that´s installed on the Tab 4 but it only happened once. I think, there´s some kind of a bug in the system. Is it possible to find and fix it?
As far as I can tell, everything else (accept the dark rear camera) is working fine.
EDIT: My Roborock S5 got an firmware update yesterday and now the app/Tab 4 doesn´t crash anymore.

heres my question with this one.do you have to format internal storage to decrypt as i dont know if theis device is encrypted. Before wiping and installing rom and gaps.just wondering as i had to do that to another device in order to install the rom an dnot to have twrp pass word screen come up an for the lineage rom to boot to lineage set up screen. jus want the exact steps so tha icna havea correct installation. as i am only going to do this once to this device.
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
here's my question.with the installation of the rom. do you have to format internal storage an then wipe and install rom and gapps . what is the exact correct process that i need toperform to have a correct installation of the rom.i cant provide development but i can provide testing of your builds.

mrk2815 said:
heres my question with this one.do you have to format internal storage to decrypt as i dont know if theis device is encrypted. Before wiping and installing rom and gaps.just wondering as i had to do that to another device in order to install the rom an dnot to have twrp pass word screen come up an for the lineage rom to boot to lineage set up screen. jus want the exact steps so tha icna havea correct installation. as i am only going to do this once to this device.
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
here's my question.with the installation of the rom. do you have to format internal storage an then wipe and install rom and gapps . what is the exact correct process that i need toperform to have a correct installation of the rom.i cant provide development but i can provide testing of your builds.
Click to expand...
Click to collapse
Encryption isn't supported in my build of TWRP, so don't try to do that with LineageOS.