[ROM][6.0.1] Android 6 - Marshmallow (August 5, 2016) [P605] - Galaxy Note 10.1 (2014 Edition) Android Developmen

[ROM][6.0.1] Android 6 - Marshmallow (August 5, 2016) [P605]
{
"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"
}
Android 6.0 Marshmallow coming to a Note 10.1 LTE (2014)!
This ROM is for P605.
It is directly based on vanilla Google Android sources. Real AOSP.
This ROM is stable and can be used as a daily driver.
Download
Note 10.1 LTE (2014) (P-605) - aosp-6.0.0-latest-lt03lte.zip (md5sum)
Download GApps
OpenGApps (Tested with open_gapps-arm-6.0-nano-20160723)
Do not use Stock or higher. Nano is recommended.
Download SuperSU
SuperSu 2.76 (Tested with UPDATE-SuperSU-v2.76-20160630161323)
Prerequisites
TWRP 2.8.6.2 or higher
Applied bootloader update, e.g. by
flashing the stock 4.2(or higher) samsung rom or
by applying bootloader directly with odin
Instructions
Flash TWRP 2.7.1.1 or higher (Note: 2.8.7.0 does not work).
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Go into install.
Flash aosp-XXX.zip
Reboot to Recovery. Else flashing GAPPS will FAIL!
Flash GAPPS.zip
Flash SuperSU.zip
Reboot to System
Check Settings->System Updates (Creates /sdcard/OpenDelta/FlashAfterUpdate)
Copy SuperSu and Gapps zip to /sdcard/OpenDelta/FlashAfterUpdate so that they are automatically applied after OTA update. Else your system will be unusable after an OTA!
Issues
No major issues
Camera takes 30sec to start
Bad GPS performance
Tips'N'Tricks
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
Probably just a developer tip, but if you dirty flash without cleaning /cache it could be that flashing fails. This is probably due to the /cache partition being full. Delete /cache/backup and reflash. Dunno why android fills this partition so much.
Screenshots
Source
Kernel
Android
Code:
/*
* Your warranty is now void.
*
* I will not accept responsibility for any adverse effects to your device,
* including, but not limited to: bricking, dead SD card, bootloops etc.
*
* You mod your device at your own risk.
*/
Please Donate
If you like my ROMs please donate by pressing the "Donate to Me" button below my name on the left side. It takes a lot of my spare time developing these ROMs for the community and every penny is greatly appreciated .
XDA:DevDB Information
AOSP Marshmallow, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
Schischu
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: >= 20151222.201844
Stable Release Date: 2015-12-22
Created 2015-11-22
Last Updated 2016-08-02

Reserved

There is still a lot todo. For example we should move to the newer vendor blobs.
But I think this version is a good base and I am excited to get your feedback.
Note: I recommend doing a backup of your old ROM before testing.

Hi,
at first thanks a lot for your hard work.
Can you please give me the link to the threads, from which you've got the Gapps,
because i'd like to know, which parts of gapps are inside those packages.
Thank you
Edit:
I just installed it, really excited Works great so far, no lags, very smooth.
Open Gapps Pico (http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071 marshmallow is not mentioned in the thread, but you can download the packages from their download website)
The only issue so far - besides camera - is a force close of Exchange services after booting, but i freeze this service anyway, so no problem for me
This is probably a noob question, but why aren't we using SuperSu 2.52 Beta?

Great work, I followed your excellent work on Lollipop, Now with Marshmallow, I have no reason to swap my P605. A big Thank You from Prague!.

Does this support exfat sdcards please?

Issue found: Rotation doesn't work, only in horizontal mode, because Sensors don't work for me (In other roms this often was modem related, I'm on stock LP modem, which one do you use?).
XPosed v78 works in this Rom.
Edit: I've done some research, maybe it's related to the new "Sensor Hub" implemented with 6.0
Edit2:
Issue 2, already present in 5.1.1: After reboot clock is set back to a date in 2014.
Issue3: After switching to flight mode (I do not use Data), the clock is not synced with the network. So i have to set the clock manually. Though the clock in clock settings shows the right time, the clock in the upper corner and in the pull down menu remains on that time which has been set. Only when i set the clock again, it is synced with the clock in the upper corner, after that it remains on this time again. This seems a bit weird, and might be a bug in GravityBoxMM. Update: Now clock is working correctly, strange....

I had some insurmountable problems with updating twrp, so I performed clean flash following the instructions with obsolete 2.8.1.0.
It seems to have worked, exchange services stopped on boot as reported above.
Edit: Google play crashed once during initial setup, but account configuration and play store works. Maybe caused by the ****ty wifi I am currently using.
Observed issues:
* backlight control is not fuctional
* screen rotation is not fuctional (as poster above)
* exchange service crash (as poster above)

Great rom..been using your first one since day one. Only thing I can see is the Screen rotation like some have mentioned. Great start and looking forward to the changes.

Encryption failing
So, I was trying out encryption and would like to share my experiences:
First try
flash TWRP 2.8.6.1 with Odin (2.8.6.2 was not available on twrp.me)
boot into recovery
flash Schischu's ROM (incl md5sum check)
reboot into recovery (w/o installing TWRP's SuperSU)
flash SuperSU 2.52 (it seems I forgot to flash gapps here; no google "welcome" later on)
reboot into ROM
set password
start encryption
Results: After initiating the encryption, the Android encryption screen is shown for just a few seconds and the tablet reboots. When now starting Android, it asks for a password. But every password (incl. the correct one) is accepted as valid but the data is claimed to be corrupted on a Decryption unsuccessful screen. I can reset the tablet from here (it boots into TWRP for a data wipe) and that's it. A wipe seems to fail, though, as the tablet continues to boot into the decryption dialog.
Second try
wipe everything from TWRP 2.8.6.1
flash Schischu's ROM (incl md5sum check)
reboot into recovery (w/o installing TWRP's SuperSU)
flash gapps and supersu 2.52
reboot into ROM
set password
start encryption
Results: the same as above...
Third try
wipe everything from TWRP 2.8.6.1
flash TWRP 2.7.1.1 as recovery using the currently installed TWRP 2.8.6.1
reboot into recovery
flash Schischu's ROM (incl md5sum check)
reboot into Schischu's ROM directly
start encryption (without setting a password first)
Results: the same as above... (including asking for the password, even though none was set during setup)
Fourth try
format everything from TWRP 2.7.1.1 (creating new filesystems where possible)
reboot into recovery
flash Schischu's ROM (incl md5sum check)
reboot into recovery (w/o installing TWRP's SuperSU)
flash gapps
flash SuperSU 2.50 (not combined with gapps but in a second step)
reboot into ROM
skip any Google or internet setup
set password
start encryption
Results: the same as above...
Until now I wasn't able to get encryption to work with Schischu's ROM on the P605. Any hints what I should try? Did anybody else successfully activate tablet encryption with this ROM? Thanks.

My menu key works only as a "recents" key. Does anyone have an idea how to remap it?
Edit:
Changing the following line in /system/use/keylayout/sec_touchscreen.kl:
key 139 APP_SWITCH VIRTUAL
Click to expand...
Click to collapse
to:
key 139 MENU VIRTUAL
Click to expand...
Click to collapse
fixed the behavior.

mcfisch said:
My menu key works only as a "recents" key. Does anyone have an idea how to remap it?
Click to expand...
Click to collapse
Use GravityBoxMM for XPosed

mcfisch said:
My menu key works only as a "recents" key. Does anyone have an idea how to remap it?
Edit:
Changing the following line in /system/use/keylayout/sec_touchscreen.kl:
to:
fixed the behavior.
Click to expand...
Click to collapse
The Recent key had to be moved, as long pressing the Home key now calls Now On Tap.
The Menu key isn't really needed anyway.

Anyone having problems with sd card access? I have it running in external storage mode and I don't seem to have write permissions. Reading contents is fine though.

Kybic said:
Anyone having problems with sd card access? I have it running in external storage mode and I don't seem to have write permissions. Reading contents is fine though.
Click to expand...
Click to collapse
I get a message of unsupported sd card.
My sd card is falsely recognised as samsung and i should format it if i want to use it with this rom.
My card is transcend 64gb fat32 though.
With previous rom(5.1.1) it is recognised ok
In twrp it is recognised ok
I dont know if it is a marshmallow thing and not roms fault.
I will try to reformat it

Marshmallow changed several things, I recommend reading the following
SD-Card
System UI Tuner
Doze
Now On Tap
Permissions

Schischu said:
The Recent key had to be moved, as long pressing the Home key now calls Now On Tap.
The Menu key isn't really needed anyway.
Click to expand...
Click to collapse
That's only true for apps already adjusted to handle the new behavior properly. Titanium backup for instance doesn't seem to correctly detect the absence of a working menu key and therefore keeps hiding the menu button. So I have no chance to setup the data folder and can't restore anything from it. And that's just one example, there are plenty of apps who get same issues.
Besides that I just don't need "now on tap" at all.
However, I think the best compromise - at least for me - would be having "recent" bound to menu-long-press.

subbing to follow progress. sounds like in a few versions i'll be updating to this.

Rom works fine. After flashing opengapps 6.0 stock, I get Neverending force closes on Google play services, setup wizard and a few others... No means to fix it except reflash without gapps

jacauc said:
Rom works fine. After flashing opengapps 6.0 stock, I get Neverending force closes on Google play services, setup wizard and a few others... No means to fix it except reflash without gapps
Click to expand...
Click to collapse
pico opengapps work just fine, maybe try a smaller package.

Related

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][tblte][trlteduos]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: Whenever I try flashing any lineage-15.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 4 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Odin
- Odin3 v3.13.1
Heimdall
- Glass Echidna
Bootloaders and modems
- ripee
TWRP for Samsung Galaxy Note 4 (Qualcomm)
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
Open GApps
OFFICIAL !!
I am not building for oreo anymore, devs have moved to pie,
thanks everyone !!
tripLr
Code:
LAST ROM Downloads for Oreo
triplr
Source Code http://www.github.com/tripLr
@kevintm78 kernel development
https://forum.xda-developers.com/note-4/snapdragon-dev/kernel-flashpoint-v3-1-stock-n7-ports-t-t3727407
(LineageOS su root included.)
ROMs Note 4
SM-N910F/G/P/R4/T/T3/V/W8:
click to open trlte drive folder
https://drive.google.com/drive/folders/1XWrdmxHeC0A7zGK-TGOH3XG2VfKYP-IA?usp=sharing
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 Edge
Note 4 Edge Thanks to @micky387 and @ripee
Which device is supported ??
I'm do the best for support multi note edge device so tell me if you see an issue and write it here with you variant
Support SM-N915F SM-N915FY SM-N915G SM-N915T SM-N915P SM-N915V
Click to expand...
Click to collapse
Google Drive Download Folder Click to open and browse to latest
https://drive.google.com/drive/folders/1lD5vLRFYr8XyGIgL2oT9VXFmdcLOWe3F?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 DUOS
- SM-N9100ZC/ZH/6W/9W:
click to open trlte duos folder
https://drive.google.com/drive/folders/1uibdRnVs9-klbJhtvB5__5B9XFYel1jK?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
Code:
# Depreciated
[B]ripee[/B] [I]([COLOR="Teal"]LineageOS[/COLOR] su root included.)[/I]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31259"][B]
lineage-15.1-20190218-UNOFFICIAL-trlte.zip[/B][/URL]
- SM-N9100ZC/ZH/6W/9W: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31260"][B]
lineage-15.1-20190218-UNOFFICIAL-trlteduos.zip[/B][/URL]
[B]_mone[/B]
- [URL="https://androidfilehost.com/?w=files&flid=140308&sort_by=date&sort_dir=DESC"][B]LineageOS[/B][/URL]
[B]micky387[/B]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://androidfilehost.com/?w=files&flid=257279&sort_by=date&sort_dir=DESC"][B]Note 4[/B][/URL]
[/CODE]LineageOS Extras
- addonsu-15.1-arm-signed.zip
- addonsu-remove-15.1-arm-signed.zip
Magisk
The SELinux Switch
- Ibuprophen
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 15.1 variant, which corresponds to the model of your phone!​
How to flash a bootloader and/or modem and TWRP​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import the bootloader.tar file with the "BL" button and the modem.tar file with the "CP" button, or a combined BL_CP.tar file with the "AP" button, for your variant,
3. Download the .tar file of the latest version of TWRP from the link above,
4. Reboot into Download mode again and import the TWRP .tar file with the "AP" button.
How to flash LineageOS and Open GApps​FULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Important information about stock S Pen functionality!​The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
How to install SPenCommand​1. Install The SELinux Switch and Select SELinux mode as PERMISSIVE,
2. Reboot into System,
3. Install SPenCommand.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Temporary fix for random SIM death on all trlte variants, courtesy of _mone: boot-1223-trlte.img
- The fingerprint scanner has not yet been integrated into either trlte or trlteduos.
- The front camera force closes, requiring a reboot to work again.
- Bluetooth does not see some wearable devices.
- The built-in camera app is slow and crashes randomly, especially when the flash fires, requiring a reboot to function again.
- Video recording in 4K resolution is not possible with either the built-in camera app or any 3rd party camera/camcorder apps.
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not (yet) supported.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- fattire and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the trlte and trlteduos.
Sources
- LineageOS
- triplr-dev
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy Note 4
Contributors
micky387, ripee, tripLr, _mone, cvxda
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Snapshot
Current Stable Version: 8.1.0
Created 2018-03-09
Last Updated 2019-07-13
Reserved
Reserved
known bugs?
Rom for note 4 duos N9100???
I am gonna test it now on N910T and will report back.
Thank you.
.
By the way i got some cool amoled wallpapers of lineage os below.
Thx ,keep the note 4 alive ,I will try this weekend
aafranki said:
known bugs?
Click to expand...
Click to collapse
Some camera issue (minor) and ??
merc200k said:
Rom for note 4 duos N9100???
Click to expand...
Click to collapse
Not support
Trex888 said:
I am gonna test it now on N910T and will report back.
Thank you.
Click to expand...
Click to collapse
Perfect ,report after
Becareful read closely OP.
When @ripee or @_mone are ready , they will continue this project
not support N9100??? so I cant test it..
maybe in the future?
Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.
Fingerprint dosnt work.No sound too.
Sound is not in this package
nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
bt don't work, call sound don't work, speaker sound don't work= phone inusable
petzku said:
Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.
Click to expand...
Click to collapse
scpeter1 said:
Fingerprint dosnt work.No sound too.
Click to expand...
Click to collapse
nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
Yes ,error in script.
Upload in progress with new build.
Sorry for this mistake
aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
That's right but I am jockeying a little the dev well fix this in the next update
nisi3nt said:
That's right but I am jockeying a little the dev well fix this in the next update
Click to expand...
Click to collapse
Yes, Done. New build available in Op
Sorry again
micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
download link?
hmm link dosen work error 404
micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
Rom dl Link not working.
Fingerprint dosntworking again.Sound is back.

[ROM][DISCONTINUED][9] LineageOS 16.0 [tblte][trlte][trlteduos]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant under the links in the TWRP thread. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 5 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Open GApps
ROMs
triplr
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
- SM-N915F/G/P/R4/T/W8: tblte
_mone
- LineageOS
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 16.0 variant, which corresponds to the model of your phone!
How to flash LineageOS and Open GApps​FULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Important information about stock S Pen functionality!​The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not supported, and will not be supported for the foreseeable future.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Our resident Developer Emeritus fattire and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the tblte, trlte, and trlteduos.
Sources
- LineageOS
- apq8084
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy Note 4
Contributors
ripee, _mone, mobspyguy, khalvat, cvxda, tripLr
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-02-16
Created 2019-02-16
Last Updated 2020-04-04
Reserved
Join us on Telegram!
LineageOS is part of the triplr_dev_users group, courtesy of tripLr.
Reserved
Please create this RAM for Exynos SM-N910c phones. We are waiting for your goodness.
hamid6831 said:
Please create this RAM for Exynos SM-N910c phones. We are waiting for your goodness.
Click to expand...
Click to collapse
As has been explained in every Qualcomm thread, what you are asking for is like trying to grow oranges using tomato seeds. Please contact the appropriate dev in the appropriate forum about Exynos support.
It's not really important at all, but is there a way to change the boot logo on this ROM (the Galaxy Note 4 logo displayed when starting the phone)? I tried to extract param.bin, it didn't work
Rom , after a total clean flash with Open Pico Gapps and Magisk 18.1, has booted up in just 2 minutes.
Android setup finished in less than a minute.
No hick ups, no errors.
Everything has run smooth and fast.
This is a job very well done.
Thank you all for taking us to the next level of Android.
Thank you @ripee, thank you @_mone , thank you @mobspyguy
Unofficial lineageos pie superuser add on
https://androidfilehost.com/?fid=11410963190603875495
Works on my tab s2
Credit
https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-16-0-t3833953/page1
Lets have a look inside it
holy crap, will be trying this asap
piemanny said:
holy crap, will be trying this asap
Click to expand...
Click to collapse
Love your username
---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------
First time I have ever seen ALL MY WIFI
Without having to edit nvram_net.txt
Had a issue installing from a otg.
WiFi is extremely fast on 5gz.
Downloading my gapps.
Sofar what I need works with ROM only.
Awesome
---------- Post added at 11:00 PM ---------- Previous post was at 10:21 PM ----------
FYI, when installing without su or any gapps, root may be enabled for adb in developer mode. Don't know what it does but the selection is there.
Stock ROM no gapps
Everything works
Except ... Fingerprint
And low mic volume
Still wow.
Gapps pico and supersu
Typing in this app doesn't show each letter
As you go. Weird. Oh, battery was low. Put on charger, back to normal.
Bluetooth works
tripLr said:
Stock ROM no gapps
Gapps pico and supersu
Typing in this app doesn't show each letter
As you go. Weird. Oh, battery was low. Put on charger, back to normal.
Bluetooth works
Click to expand...
Click to collapse
Here same strange thing.
Typing message in XDA App and cannt really see what you type.
after a while, or when hit ender, letters show up..
Pico Gapps with magisk, battery foul.
So, its not battery related, or root.
logosA said:
Lets have a look inside it
Click to expand...
Click to collapse
Can I add these to the OP?
ripee said:
Can I add these to the OP?
Click to expand...
Click to collapse
of cource you can.
Its your work after all
logosA said:
of cource you can.
Its your work after all
Click to expand...
Click to collapse
Thanks but it's _mone's and mobspyguy's work
Sim Death....or No Service
For what its worth, even with an earlier modem (and i even rolled back the 1st 6.0.1 modem available for my region N910GDTU1DPF4), i still get the occasional sim death..not quite as bad as on Oero though
Usually i would manually reset the Ril Daemon via RIl Control from F-Droid
Today i finally got tired of doing this manually and set out to automate ril restarting with tasker
Please note i have never used Tasker before, so my shared profile may be less than ideal, im open for suggestions from more seasoned users, but for me it works well enough, or it seems to....
Tasker profile removed - it just wasnt as effective as Automate, harder to use, and unreliable in its State function....
Meanwhile i have been using Automate and testing this Automate flow i cobbled together - Updated 19/02/19 (similar to Tasker, but waaay easier to work with, flowchart based...) It currently checks for mobile connectivity every 5 minutes, and restarts ril-daemon if needed
The Automate way seems to be working better than Tasker....like u said I've not used Tasker before, and its horribly complicated compared to Automate...
Update: As of using my last Automate flowchart (updated above this morning), i have had zero sim death, dunno why, maybe polling connectivity every 5 minutes is enough to stop sim death, it hasnt gotten as far as the ril-daemon restart so far...will update if it does....
Of course, i spoke too soon, and jinxed myself
An hour after my last update i finally had my first sim death/ril-daemon reset...still, it was automatically recovered
I've tried this and mobspyguy's rom. the problem I have is that in my area I have good lte and data signal with these roms. But for some reason I have to drive 3 miles out of town before I can make a call. I'm on N910v straight talk on verizon network. P. S. The data works great while I'm at home just can't make calls.
Anyone run into SDCard showing as corrupted
ninja_unmatched said:
Anyone run into SDCard showing as corrupted
Click to expand...
Click to collapse
Although this shouldn't be the case, going from one version to another, your sd card can usually be expected to work best when you format it with the new version.

[ROM][9.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510]

{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510/T515], here's one I just created based on the September 2019 Update and @AndyYan's LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process may require you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the November 2019 Update (T510XXS3ATB4) for the SM-T510.
The system is based on @AndyYan's LineageOS 16.0 GSI with the latest Stock variant from OpenGApps.
Boot logo and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
I've dialed back most of scary bootloader warnings and Knox Security branding from the boot sequence.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
SM-T510:
Nexus_Stock_LP_T510XXS3ATB4-20200422.tar.md5 (Odin tarball)
Nexus_Stock_LP_T510XXS3ATB4-20200422.zip (TWRP update)
SM-T515:
No longer supported (since I don't have hardware for testing), but archives are posted here.
Change Log:
20200422:
New private build of LineageOS GSI with April 2020 security patch.
Updated to T510XXS3ATB4 kernel and vendor partition (February 2020 Update)
Updated to latest OpenGApps (20200422), with private fix for Chrome issue.
20200405:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
New private build of LineageOS GSI with the above fixes (#663 & #1228).
Updated to latest OpenGApps (20200404), with private fix for Chrome issue.
20200325:
Switched back to Pixel Launcher updated with Nexus tablet device profiles.
New LineageOS GSI build of treble_a64_bvN target with March 2020 Security Update.
Switched to ext2simg for sparse image conversion to improve Odin compatibility and reduce download size.
Updated to OpenGApps 20200311. (Subsequent builds have issues.)
20200308:
Charging after full shutdown will no longer hang during level-of-charge animation.
MTP file transfers no longer require USB Debugging to be enabled.
Updated to T510XXU2ASK5 kernel (November 2019 Update)
Updated to latest OpenGApps (20200307)
20200103:
Updated to T510XXS2ASK1 kernel (November 2019 Update)
Updated to latest OpenGApps (20200103)
20191109:
USB Debugging is enabled by default (MTP workaround)
SurfaceFlinger optimization to improve scrolling performance
Updated to latest OpenGApps (20191109)
Now building TWRP update (.zip file)
20190922:
Switched from AOSP base to LineageOS.
Updated to latest OpenGApps (20191022)
20190921:
Updated to T510XXU2ASI4 kernel and TWRP v3.3.1-5..
20190909:
Scoped MTP fix more tightly, preventing charging cap at 79%.
20190906:
Fixed MTP support, so you can now transfer files easily via USB.
20190828:
Google Play Protect now plays nice. You no longer have to register your GSF ID. (Thanks, @phhusson!)
Removed DeviceID app, since it's now unneeded.
20190825:
AOSP 9.0 v119
Updated to TWRP 3.3.1-2
Restored some security features to custom kernel
20190810:
AOSP 9.0 v117
August security patch
Nexus default wallpaper
20190629:
Initial release based on AOSP 9.0 v114
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Phh-Treble
treble_build_los
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Oo our first custom rom!! Thanks alot!! Cant wair to try it soon
Important Note: The Night Mode setting in Developer Options is set to "Always off" by default. Don't change it! When I set it to "Automatic (based on time of day)", the screen went black and I couldn't recover without a factory reset. (I'm assuming that this was a bug in SystemUI.apk.)
Thanks for the effort and time you've put into this.
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.
NightHawkUndead said:
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.
Click to expand...
Click to collapse
Well, I just verified the MD5s and they match. However, to be a little more squared away, I replaced the original .tar file that I uploaded with a .tar.md5 (a.k.a. "tarball) which has the MD5 footer that Odin can use to verify the file integrity. I've also compressed the contents with LZ4, which cut the size down by a third.
Installing the new tarball with Odin3 v3.13.3 on my tablet went smoothly, so I hope this works for you.
Finally got it to work. Had to flash back to stock. Wipe. Then immediately reboot bootloader again and flash Rom.
How do I go about rooting now?
Edit: nevermind, got it rooted. Everything is working fine now!
Sent you a donation for your work. ? ?
I have a new SM-T510 on T510XXU1ASEF
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Tried to flash 3 times, same result.
Is there something to going back to stock, wiping, bootloader, flash again? Or is that just doing things until it works?
garyemiller said:
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Click to expand...
Click to collapse
It's important that you wipe the data partition before TWRP boots, since it currently hangs when it encounters an encrypted file system. (Yes, this really shouldn't happen, but I haven't found a fix for that TWRP bug yet.)
Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM?
"Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM? "
Yes.
I got it to work. reinstalled stock rom (link above). Booted it stock. Enabled Developer Mode, Enabled USB debugging. confirmed OEM still unlocked. Boot to recovery, wipe, boot to bootloader. Flash this ROM with Odin3. reboot. All is well.
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Along the way I also wasted a lot of time trying to flash with heimdall 1.4.2. But that was very flakey. Odin3 just worked.
---------- Post added at 08:46 PM ---------- Previous post was at 08:23 PM ----------
I guess I should mention my biggest issue was unlocking the bootloader. Not like before.
Power off. Hold Vol UP and Vol Down. Plug in USB. Long press Vol UP to unlock.
garyemiller said:
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Click to expand...
Click to collapse
If you install Magisk, you might not have to do the device certification dance. It tries to fake out Play Protect.
The device certification was painless. I've doe that before on other devices.
Rooting with Magisk was also painless:
Grab boot.img from your tarball.
adb push boot.img /storeage/emulated/0/Download
patch using Magisk Manager
adb pull /storage/emulated/0/Download/magisk_patched.img .
heimdall flash --BOOT magisk_patched.img
I can't get SafetyNet to pass, even with Magisk SafetyPatch module. But not a big deal to me.
Is there a way to turn off the google page on the launcher?
Thanks for the nice ROM! So much better than stock.
I'm still looking for a good ad blocker for Pie. Up tile now I have used a Raspberry Pi as a dnsmasq server for ad blocking.
garyemiller said:
Is there a way to turn off the google page on the launcher?
Click to expand...
Click to collapse
If you open up the Android One Launcher settings, there's a "Display Google app" option that you can disable.
garyemiller said:
I can't get SafetyNet to pass, even with Magisk SafetyPatch module..
Click to expand...
Click to collapse
Yeah, I've tried the usual tricks like spoofing the fingerprint, but that didn't work either. This kind of hard Play Protect device rejection seems to happen for me whenever the vendor partition is using release keys and the system partition is using test keys.
I haven't found an XDA thread yet that really provided deep insight into the algorithm that Google uses for Play Protect and SafetyNet. And given the proprietary nature of what it's doing, we may never get it. I think our best long-term solution is to get LineageOS 16 builds that pass CTS testing, but we may have to scrounge for 64-bit drivers.
I just went with Nova Launcher. It has been good to me.
I can wait for Lineage to catch up. I'm happy to be rid of bloatware. And with root I can block ads and my firewall works.
Thanks for the ROM! I'm happy!
ankh_hikes said:
Which stock files do I need to replace the nexus boot splash screens? I would like have the Samsung ones.
Click to expand...
Click to collapse
Just restore the original param image. (But seriously, why would you? The stock boot splash is ugly! )
Just ordered my T510, can't wait to try this out when it arrives
d4dave said:
Just ordered my T510, can't wait to try this out when it arrives
Click to expand...
Click to collapse
The 3G/128G config was selling for just $250 USD through Costco until a few days ago. That's a pretty insane value....as long as you aren't stuck with Samsung's One UI, that is.
will there be a new release coming?
DarthGW said:
will there be a new release coming?
Click to expand...
Click to collapse
Yes, I'm trying to build an unofficial LineageOS 16.0 release, but am struggling with some build issues. The primary goal is to deal with the Play Protect device certification (but I definitely won't pass SafetyNet). Eventually, I'll also get to fixing MTP.
wow dude, thanks a lot for you work
Is it possible to install this on the 510 with Product code NEE
PDA T510XXU1ASF2
CSC T510OXM1ASF3
It's the stock may Nordic firmware

[ROM][UNOFFICIAL]LineageOS-14.1 for deb/flo | Android 7.1.2 Nougat [MAY 2023]

{
"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 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.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working :
Everything that worked in last OFFICIAL build.
There are NO MODIFICATIONS at all. If something didn't work in the last official LineageOS release, it wont work in this build.
Instructions :
Download build and copy it to Internal Memory
Reboot to TWRP recovery
Create TWRP Backup (Recommended)
Flash the latest build (Clean Flash if coming from any other build)
Flash Magisk/LineageSU zip (Optional)
Flash GApps/MicroG (Optional)
Reboot
Downloads :
deb
Build: lineage-14.1-20230514-UNOFFICIAL-deb.zip
MD5: 534dff964ca9c44a8ab00e6a6d3883f9
flo
Build: lineage-14.1-20230514-UNOFFICIAL-flo.zip
MD5: 66a094b14a1f1531af1d195bf787a03b
TWRP
deb: twrp-3.4.0-0-deb.img
flo: twrp-3.4.0-0-flo.img
followmsi builds: TWRP-followmsi
Root Method:
Magisk: here
LineageOS su: here
Addon (GApps/MicroG):
GApps: BiTGApps (arm 7.1.2)
MicroG (Built via FriendlyNeighborhoodShane repo): MinMicroG.zip
Source Code: https://github.com/LineageOS
Proprietary Files: TheMuppets
Kernel Source: Here
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.0
Security Patch: May 2023
Created 2021-01-12
Last Updated 2023-05-14
Older Builds
Downloads:
AFH Google Nexus 7 (2013) Root Folder (Builds older than July 2022)
SourceForge - deb
SourceForge - flo
Thank you.
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
aurocha said:
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Click to expand...
Click to collapse
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
aurocha said:
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
Click to expand...
Click to collapse
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
Os_A said:
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
Click to expand...
Click to collapse
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
M4Master96 said:
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
Click to expand...
Click to collapse
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
aurocha said:
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Click to expand...
Click to collapse
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
M4Master96 said:
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
Yep, that's the kernel I'm running. Mainly because of DT2W. Loads of options when flashing because of the Aroma installer and easily manageable with exkm, which I bought some years ago.
M4Master96 said:
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
plusminus_ said:
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
Click to expand...
Click to collapse
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
this looks great - thank you - does it work with any of the Custom Kernels?
February 2021 Security Patches
deb
Build: lineage-14.1-20210208-UNOFFICIAL-deb.zip
MD5: 7ed9473d325d20b863d1516d902602d7
flo
Build: lineage-14.1-20210208-UNOFFICIAL-flo.zip
MD5: 9a6617aa7111b4c91daf310e7bf09183
Added links in first post
M4Master96 said:
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
Click to expand...
Click to collapse
Ah I suspected this, hmm
thanks
Thanks all you guys, was looking for a decent rom for this tablet, can't live without doubletap2wake and newer roms are just too heavy for this gadget, was looking for a decent rom for it, and I have finally find it
March 2021 Security Patches
deb
Build: lineage-14.1-20210309-UNOFFICIAL-deb.zip
MD5: 6d23b5115b073a6d9a85981cb6abac11
flo
Build: lineage-14.1-20210309-UNOFFICIAL-flo.zip
MD5: 39f1a8945af9870369ffdd1deefb5e4c
Updated links in first post
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
sundog1 said:
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
Click to expand...
Click to collapse
I create flashable microg zip via https://github.com/WeAreFairphone/flashable-zip_microG and then flash it along with ROM, magisk and kernel. Afterwards, I use SmaliPatcher Module to patch and enable SignatureSpoofing so that MicroG works.
I had also raised Merge Request in lineageos4microg so that We can build ROM with microg without syncing repository but my MR is still open and so, Not able to build that.
April 2021 Security Patches
deb
Build: lineage-14.1-20210409-UNOFFICIAL-deb.zip
MD5: 627ce7454888bc71aec2fea10e6023ce
flo
Build: lineage-14.1-20210409-UNOFFICIAL-flo.zip
MD5: 54ac5466ae8df749a6650ee1c7b28e82
Updated links in first post
aurocha said:
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
Click to expand...
Click to collapse
Hi,
May i know which 'official image' you restored and which version of twrp was used?
I flashed LOS 18.1 before and it work but seems lag. Then I tried to flash this ROM but faced the same problem, endless looping is the screen of upwards arc w/ circle (LOS logo?) running from right to left again and again.
Thank you!
Update: Well, i just follow the link provided by @JT1510365 in https://forum.xda-developers.com/t/...oted-unmodified-6-0-mra58v-flashable.3694735/ and download the stock rom, restore to 6.0, it boot normal. Then flash twrp & this rom and it work now.
Thank you for your share of the reinstallation of 'official image'.

[ROM][12.1][OFFICIAL][LMI] crDroid v8.14 [23.03.2023]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
gapps : Nikgapps and Flamegapps are both tested
Magisk 23.0 for root (after first boot) - (Download from here)
First time installation:
make use of 3.6.0_11-RedmiK30Pro_v3.0.3_A12-lmi-skkk_0b4ac24c.img or your preferred one
boot recovery
format & reboot recovery
flash Firmware (minimum requirement 12.5.3) (skip if you are on 12.5.3 or later)
flash crDroid
reboot recovery
(optional) flash Gapps
(optional) flash Magisk
boot system
Update installation: (if on cr8 already)
boot recovery
flash crDroid
boot system
Sources:
ROM: https://github.com/crdroidandroid
Device Trees: lmi + common
Kernel: Quantic kernel thx @GtrCraft
Download:
ROM: LMI
Changelog: LMI
LATEST BUILD AND INSTRUCTIONS
Known issues:
...
ROM OS Version: 12.0
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, min. miu v12.5.x
Status: stable
Sec. Patches : 2023.03.05
Created : 2022.01.18
Last Updated : 2023.03.23
Thnx to :
@Schnedi
@Ayrton990
Visit official website @ crDroid.net
crDroid LMI Telegram
crDroid Community Telegram
crDroid Updates Channel
Donations are appreciated to continue development
Changelog: LMI
Thx boss !!!!!
This is one of the ROMs that I've been anticipating to have an A12 update. Thank you for keeping lmi alive!
Does VOLTE work here?
Can someone please confirm if the low microphone volume recording bug for WhatsApp voice notes etc is present on this rom, like it is for the A11 crdroid?
Hi to all of you!
Great ROM with all the great looks and feel but as in 7.13 version I am not able to get the mobile data to work...
Anyway, big thanks to the developers for all the effort!
lafa011 said:
Hi to all of you!
Great ROM with all the great looks and feel but as in 7.13 version I am not able to get the mobile data to work...
Anyway, big thanks to the developers for all the effort!
Click to expand...
Click to collapse
Have you tried manually setting up the APN in Settings?
I was looking forward to this update, Thanks for your hard work!
I'm facing a bootloop problem for some reasons...
I once successfully installed it, but realized NikkGapp didn't use my config, so I went back into TWRP to run it again and use my config.
I didn't realized it at this time (now I know), but TWRP didn't ask for any pattern unlock. The sd-card wasn't detected, so I tried a couple of things to solve it, and this is where it starts to get problematic. I did the sd-card switch from ext2 to ext4.
From that point, I got into a boot loop. I tried to flash the CrDroid rom again, but it won't work.
I then flashed the global original image to start fresh, but TWRP still won't ask for pattern to unlock, thus doing the flashing again didn't work...
Do you have any idea how I can fix it? I'm back on MIUI and I already miss CrDroid
woodencase01 said:
I was looking forward to this update, Thanks for your hard work!
I'm facing a bootloop problem for some reasons...
I once successfully installed it, but realized NikkGapp didn't use my config, so I went back into TWRP to run it again and use my config.
I didn't realized it at this time (now I know), but TWRP didn't ask for any pattern unlock. The sd-card wasn't detected, so I tried a couple of things to solve it, and this is where it starts to get problematic. I did the sd-card switch from ext2 to ext4.
From that point, I got into a boot loop. I tried to flash the CrDroid rom again, but it won't work.
I then flashed the global original image to start fresh, but TWRP still won't ask for pattern to unlock, thus doing the flashing again didn't work...
Do you have any idea how I can fix it? I'm back on MIUI and I already miss CrDroid
Click to expand...
Click to collapse
After getting bootloops from installing different roms I learned this: disable the screen lock (Settings->Security->Screen lock->None) before flashing anything. This way TWRP should be able to mount the partitions
thetta-reddast said:
After getting bootloops from installing different roms I learned this: disable the screen lock (Settings->Security->Screen lock->None) before flashing anything. This way TWRP should be able to mount the partitions
Click to expand...
Click to collapse
Thanks for your help.
I disabled the screen lock, but sadly it didn't work.
I get errors messages such as:
I:File Based Encryption is present
fscrypt_init_user0 returned fail
fscrypt_init_user0 returned fail
fscrypt_init_user0 returned fail
Unable to decrypt FBE device.
If your device is not encrypted, decrypting the FEB device will fail.
E:fde::get_crypt_ftr_and_key::Unexpected value for crypto key location:
E:Error getting crypt footer and keyE:Could not get footerDecrypt process ended with signal: 11
Failed to decrypt data.
Unable to decrypt with default password. You may need to perform a Format Data.
and
Android Rescue Party trigger! Possible solutions? Either:
1. Wipe caches, and/or
2. Format data, and/or
3. Clean-flash your ROM.
The reported problem is:
'set_policy_failed:/data/system'
Not sure what to do...
I tried changing the data format to ext4, then format it through ADB, didn't work.
My current error message is "init_user0_failed". I also still have the "Rescue Party trigger!" message.
EDIT:
I managed to boot by formatting DATA after flashing, but the OS seems to be missing a lot of stuff.
EDIT 2:
Ok, started the clean flashing process again, still got in bootloop. Tried formatting data again, and it worked!
batuken said:
Have you tried manually setting up the APN in Settings?
Click to expand...
Click to collapse
Thank you for your reply. I did not try changing the APN settings but tried MIUI stable 12.2.6.0 needed for flashing the 7.13 crDroid and it works there out of the box. Maybe changing the APN would work but I gave up and get back to EU version instead, which is ok for me except for custom launcher like Nova since I cannot get around the home buttons appearing/dissapearing when I use gestures with Nova launcher... That was the first thing that led me to trying crDroid
Спасибо за ROM!!!
----------
MOD EDIT: English Translation Below
Thanks for the ROM!!!
tell me from which version of MIUI you need to flash crdroid 8
Can anyone confirm wether crdroid has issues with high security apps requiring "official" builds?
For example the Danish verification service MitID (https://play.google.com/store/apps/details?id=dk.mitid.app.android)
App would open to only display that "device is rooted" on Spark A12 rom...
Lyngze said:
Can anyone confirm wether crdroid has issues with high security apps requiring "official" builds?
For example the Danish verification service MitID (https://play.google.com/store/apps/details?id=dk.mitid.app.android)
App would open to only display that "device is rooted" on Spark A12 rom...
Click to expand...
Click to collapse
I have the same problem with our COVID app, I simply flashed Magisk, then once I'm in the OS, you can install MagiskHide, it also works for Google Pay on rooted phones. Make sure to clear the app cache when activating MagiskHide, otherwise the message about the rooting will stay.
woodencase01 said:
I have the same problem with our COVID app, I simply flashed Magisk, then once I'm in the OS, you can install MagiskHide, it also works for Google Pay on rooted phones. Make sure to clear the app cache when activating MagiskHide, otherwise the message about the rooting will stay.
Click to expand...
Click to collapse
This was without root. Google Pay and other banking apps and such worked. But a few had some extra checks apart from SafetyNet and such.
I would rather not root and mess with magisk if it could be avoided.
I don't have any need for root and would rather not install too much third party stuff with potential security risks.
Did Google Pay not work for you without root and magisk hide either?
I'm currently using "NikGapps-full-arm64-12-20211227-signed" as GAPP, but sadly, chrome keeps freezing. I'm currently using a different browser. Has anyone a fix for this?
Lyngze said:
This was without root. Google Pay and other banking apps and such worked. But a few had some extra checks apart from SafetyNet and such.
I would rather not root and mess with magisk if it could be avoided.
I don't have any need for root and would rather not install too much third party stuff with potential security risks.
Did Google Pay not work for you without root and magisk hide either?
Click to expand...
Click to collapse
My device is rooted since day one. I don't know how to flash a custom ROM without first rooting.
But yes, without MagiskHide, I couldn't use Google Pay. Haven't found another way to make it work.

Categories

Resources