Develop Bugs

[DISCONTINUED][MOD] Kali NetHunter for Honor 5x

What is Kali NetHunter?​If you don't know what NetHunter is read this: https://www.kali.org/kali-linux-nethunter/
Q: Why don't I flash the original nethunter version by keeping my current kernel?
A: To get Nethunter fully work you need a kernel that supports its features, such as put a wireless adapter in monitor mode or perform a HID Keyboard attack
Special Patches included in this kernel:
mac80211 injection patch, to put wireless adapters in monitor mode; note that built-in wireless chipset doesn't support monitor mode and you have to use external wireless adapter (see supported wireless cards here)
HID patch, to perform HID keyboard attacks
CD-ROM patch, to emulate CD-ROMs in DriveDroid
Warning!!!:
This version is not tested by me (since I don't have a hono 5x ) but it's tested by another user that told me it works, so, if it doesn't blame him not me
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK.
Required Downloads:
Download any CM based ROM
Download any custom recovery (like twrp)
Download my Nethunter "ROM" here: https://androidfilehost.com/?w=files&flid=118871 All future updates will be in that folder
How to Install (CM/RR):
Note: When you flash my zips, don't check "zip signature verification" box in TWRP recovery
1) Install TWRP
2) Enter in TWRP recovery
3) Flash any CM based (like cm, rr, aicp...) ROM
4) Optional: flash Google Apps after flashed a cm based recovery
5) Flash NetHunter zip
7) Reboot
8) Open Nethunter app and go to menu<chroot manager<install chroot and download the full chroot, for devices which have more storage available, or minimal chroot, for devices which have less space available
9) Close NetHunter app and reopen it to complete the installation
10) Enjoy
Important: I called NetHunter "ROM", but it isn't a ROM, so, you don't have to wipe system partition.
Note: report only bugs related to NetHunter and not to cm based roms
Kernel Source Code:
https://github.com/DeadSquirrel01/android_kernel_huawei_kiwi branch cm-13.0
Now you can build it by youself on official HetHunter source page
You Need this https://github.com/offensive-security/kali-NetHunter
and this https://github.com/offensive-security/nethunter-devices (branch experimental for now )
For Any questions contact me at: [email protected]
Credits: @jcadduono, binkybear and offensive security team for NetHunter source code
XDA:DevDB Information
[MOD] Kali NetHunter for Honor 5x, Kernel for the Honor 5X
Contributors
DeadSquirrel01
Kernel Special Features: mac80211 Packet Injection Patch, HID gadget USB/Mouse Patch, CD-ROM Patch for emulate CD-ROMS in DriveDroid
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-10-01
Created 2016-10-01
Last Updated 2016-10-01

already using it NYC work

Will someone explain what this does?? I tried the link but couldn't get much out of it.... Thnx
Sent from my KIW-L21 using Tapatalk

Faheemarif252 said:
Will someone explain what this does?? I tried the link but couldn't get much out of it.... Thnx
Click to expand...
Click to collapse
Well, Mate its actually used for pentesting or penetration testing of wifi or wireless networks... google it for detail information.

mumith3 said:
Well, Mate its actually used for pentesting or penetration testing of wifi or wireless networks... google it for detail information.
Click to expand...
Click to collapse
Yep, it's for pentesting

it is a amazing kernel, wow.

kaankulahli said:
it is a amazing kernel, wow.
Click to expand...
Click to collapse
I know

Gonna try it

Kali Linux on Honor 5X! This is amazing!

Downloaded and flashed on KIW-L22 - On Tipsy OS - AOSP and AOKP (CM Based) - Initial boot took a while longer than normal, got a boot loop first, but it came back up after cache/dalvik wipe
Kali chroot manager stuck in "Checking" even after 10 minutes though
Edit: Lost root on installing this and didn't notice it, and busybox too.....reinstalling SuperSU through TWRP is not bringing it back root access either, so cannot install busybox too......nethunter app returned an error for not getting root access and no busybox installation!
PS: In love with the boot animation!!

nandakalyan said:
Downloaded and flashed on KIW-L22 - Kali chroot manager stuck in "Checking" even after 10 minutes though
1. On Tipsy OS - AOSP - working fine! Initial boot took a while longer than normal, got a boot loop first, but it came back up after cache/dalvik wipe
2. On AOKP (CM based) - Flash and wipe cache/dlavik, took a while longer but booted up normally, but I guess it will settle
Still trying to figure out how and what to use it for but just wanted to report back that the flashing process went well!!
PS: In love with the boot animation!!
Click to expand...
Click to collapse
mmm, stucking in checking it's very strange. Maybe compile a full zip here https://github.com/offensive-security/kali-nethunter (you have to clone
https://github.com/offensive-security/nethunter-devices, too (branch experimental) then for build with full chroot, just type:
$ python build.py -d kiwi --marshmallow --release v1.0 --rootfs-full
Anyway i will upload the zip with full chroot once i finish my cm14 port for a5

DeadSquirrel01 said:
mmm, stucking in checking it's very strange. Maybe compile a full zip here https://github.com/offensive-security/kali-nethunter (you have to clone
https://github.com/offensive-security/nethunter-devices, too (branch experimental) then for build with full chroot, just type:
$ python build.py -d kiwi --marshmallow --release v1.0 --rootfs-full
Anyway i will upload the zip with full chroot once i finish my cm14 port for a5
Click to expand...
Click to collapse
Thanks man, I wish I knew enough to compile and run things on github just edited by previous post.....it seems it got stuck because of no root access and busybox missing. Lemme know if i can test things out for you, glad to be of any help that way!
---------- Post added at 07:52 PM ---------- Previous post was at 07:12 PM ----------
OK, just figured it was me being a bit duh on the whole thing! I just reinstalled the whole ROM, and flashed this again. Installed SuperSU from playstore (it went missing after installing this) and things are back to normal.....now downloading full chroot! Hurray!

[/COLOR]OK, just figured it was me being a bit duh on the whole thing! I just reinstalled the whole ROM, and flashed this again. Installed SuperSU from playstore (it went missing after installing this) and things are back to normal.....now downloading full chroot! Hurray![/QUOTE]
Strange, the zip should include SuperSU

Hi,
where can I find the full chroot file (~ 750Mo), I want to download it manually
+
Why "wifite" does not recognize my hama adapter with Ralink RT2500 chipset?!
It is identified but when I choose the interface, it still returns the menu of choice
thanks for your help

panther2005 said:
Hi,
where can I find the full chroot file (~ 750Mo), I want to download it manually
+
Why "wifite" does not recognize my hama adapter with Ralink RT2500 chipset?!
It is identified but when I choose the interface, it still returns the menu of choice
thanks for your help
Click to expand...
Click to collapse
You can download chroot here:
https://build.nethunter.com/kalifs/
Regarding your adapter, read this: https://github.com/offensive-security/kali-nethunter/wiki/Wireless-Cards
Unlucky, your adapter does not support nethunter

DeadSquirrel01 said:
You can download chroot here:
https://build.nethunter.com/kalifs/
Regarding your adapter, read this: https://github.com/offensive-security/kali-nethunter/wiki/Wireless-Cards
Unlucky, your adapter does not support nethunter
Click to expand...
Click to collapse
Thanks bro
I even tried the alfa rtl8187l chipset without any result,
The problem is the low current for the adapter from the phone,
The usb hub with an external power supply maybe solves the problem, but it is not practical for a displacement
thanks again DeadSquirrel01
Sent from my KIW-L21 using XDA-Developers mobile app

panther2005 said:
Thanks bro
I even tried the alfa rtl8187l chipset without any result,
The problem is the low current for the adapter from the phone,
The usb hub with an external power supply maybe solves the problem, but it is not practical for a displacement
thanks again DeadSquirrel01
Sent from my KIW-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
For this i dunno, i'm not an elctronic expert ^^

DeadSquirrel01 said:
For this i dunno, i'm not an elctronic expert ^^
Click to expand...
Click to collapse
I must choose
kalifs-armhf-full.log
kalifs-armhf-full.sha512sum
kalifs-armhf-full.tar.xz
for KIW-L21?

panther2005 said:
I must choose
kalifs-armhf-full.log
kalifs-armhf-full.sha512sum
kalifs-armhf-full.tar.xz
for KIW-L21?
Click to expand...
Click to collapse
The .tar.xz one

Hey all,
so i flashed the nethunter zip with no hiccups.
However, now my wifi wont connect.
Does anyone know what might be the problem?

[ROM][Unofficial][8.1.0][deprecated] Lineage OS 15.1 for Xperia Z1 compact 29.12.18

This Thread is deprecated!
Please use https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-lineageos-15-1-xperia-z1-compact-t3884247/
We'll provide Lineage 15.1 builds there as well. They come in two different flavours:
pure LineageOS
Security hardened microG LineageOS
Functionality is completely the same as provived by the builds from this thread - they are build from the same sources. Only difference: The new builds are signed to guarantee a maximum of security.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by AdrianDC
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: didn't test
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok, but installing updates only works with adb sideload!
- SEPolicies : Enforcing
Download
https://androidfilehost.com/?w=files&flid=269301
latest version: https://www.androidfilehost.com/?fid=11410963190603873784
Click to expand...
Click to collapse
FAQ
What about device encryption?
Device encryption is working. You only have to keep in mind that you need a PC with adb to install systemupdates.
Flashing via recovery isn't working until now, because there isn't a recovery capable of decrypting Oreo /data partitions at the moment. But an easy "adb sideload" should do the job. Or installing from the external SD card.
Click to expand...
Click to collapse
What about reboot to recovery?
Reboot to recovery is only working with magisk installed. Investigating this...
Reboot to recovery is working as it should now (and of course also without magisk).
Click to expand...
Click to collapse
What about GPS?
GPS apps like GPS Status&Toolbox or SatStat don't get location fixes. Nevertheless navigating with Osmand or googleMaps should work. Positionfinding is also slow. Got better
Click to expand...
Click to collapse
I found a bug. What should I do?
We need your feedback for optimization. But your feedback is only useful in connection with logs --> see section Bugreports
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 15.1 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/AICP/kernel_sony_msm8974
Manifest: https://github.com/115ek/manifest
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 15.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/115ek/manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-09-10
Created 2018-09-10
Last Updated 2019-03-18

Changelog
13.12.2018
fixed wrong bluetooth MAC address (00:00:00:00:5a:ad on all devices), now displaying correct device specific one
12.12.2018
synced LineageOS sources (security patch level December 05, 2018)
11.11.2018
fix problem with Lineage SU addon by using 64-bit binder API (thanks @NyQuilXT)
synced LineageOS sources (security patch level November 05, 2018)
14.10.2018
fixed GPS 3D fix
08.10.2018
fixed MHL (thanks @koron393)
added callrecording
synced LineageOS sources (security patch level October 05, 2018)
23.09.2018
fixed reboot to recovery without magisk
minor improvements from AICP devices trees (thanks @SpiritCroc)
synced LineageOS sources
10.09.2018
initial release

Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
Encryption : Ok but needs recovery capable of Oreo decryption for installing updates (AFAIK such a recovery doesn't exist until now for our device...)
Click to expand...
Click to collapse
I'm actually having some trouble finding a up-to-date recovery.

Jeroen1000 said:
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
I'm actually having some trouble finding a up-to-date recovery.
Click to expand...
Click to collapse
You can use this https://androidfilehost.com/?fid=5862345805528046823 or that https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450.
For Lineage 15.x flashing you need TWRP>=3.2.x If the version is older you'll end up in a error 7.
Concerning decryption: Google introduced some new encryption stuff and so the decryption of /data from inside TWRP is broken. Some guys are working on it (@nailyk).
Encrypting the device should work fine, but I don't know what happens if you want to update the encrypted device. (I'm going to test that ).
Basically you need to store the update package outside of encrypted partitions... Maybe adb sideload works - but it's circumstantial.
Edit:
That's only interesting if you plan to encrypt your device. Otherways you can relax.
Edit2:
adb sideload should do the job. But you need a PC for updating. Installing an image directly via recovery isn't possible until now.

With sources for both kernel and system unlike the other port! Thanks, I'll definitely be using this!

Xperia J1 Compact
could this work on an Xperia J1 Compact?
it's basically the same phone with the same specs right?

The rom looks very stable and balance, but I've some problems with root procedure. I tried the lineage addon, the root seems active, but opening apps (es. Ad away) results unrooted, any ideas?
Update: Now Works. Flashed lastest Magisk

Amazing to see this old device on Oreo, just installed and it feels smooth and nice. Just a pity that I have broken the sim card connectors inside so I cant use it as a phone but I will fins use of it at home just for fun. Thank you for your work 115ek :good:

Great to see this rom realy! This rom have stock camera?

munjeni said:
Great to see this rom realy! This rom have stock camera?
Click to expand...
Click to collapse
What do you mean with stock camera?
There was a thing with kernel versions 3.4 and 3.10, wasn't it? We're using 3.4.
Concerning the camera: I'm not that expert, but it looks okay I would say.
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.

115ek said:
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
Click to expand...
Click to collapse
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery

raschad said:
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
Click to expand...
Click to collapse
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome

115ek said:
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
Click to expand...
Click to collapse
I meant does this rom have stock camera blobs? Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?

munjeni said:
Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
Click to expand...
Click to collapse
Good news: an easy import of your init_board_device.h did the trick. Maybe a timing problem?
Anyway: reboot to recovery is now working correctly, even without magisk
Is that okay for you: http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/73688 ?

I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...

munjeni said:
I meant does this rom have stock camera blobs?
Click to expand...
Click to collapse
We're using them https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/rhine-common/proprietary/vendor, so I guess yes.
You're more into topic, aren't you? How to distinguish between AOSP and stock blobs? There were some mysteries around DRM, camera quality and so on. I remember a separate thread you also participated in...
But I'm not really into this topic.

munjeni said:
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
Click to expand...
Click to collapse
No, it's actually in here: https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/include/init_sony/init_board_device.h
But It's different from yours. Yours performs another keycheck.

Seems rom have stock blobs. To distinguish between AOSP and stock blobs... depends on kernel you have using, aosp kernel can't be used with stock blobs since aosp camera kernel module is diferent, but I'm out of development for long, have no free time and to be honest I still didn't forgot treatment & injustice for my status on xda, that made me more inactive here. Recognised members have bad treatment here, seems senior members have much more priority than recognised members, and thats reason why everybody here need to care how many hours per day to waste here. I decided to stop wasting my time on xda since xda leaders do not respect anybody's hard work here. I recommend the same to everyone here.

I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem ?

ULT][MO said:
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem
Click to expand...
Click to collapse
What recovery are you using? I recommend this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
With mine from here https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450 it still won't work. Maybe a timing thing.
But it's okay if we have at least one working TWRP.
And oreo /data decryption is still an issue we have to address.

[GUIDE][ROM][ROOT]SHAI'S MEDIOCRE ROM N ROOT HOW TO: FOR DUMMIES

x3r0.13urn said:
It's good one. You should move it into a new thread in Guides, News, & Discussion section, it's more appropriate there, and I'm sure it will be last longer rather than in here.
Click to expand...
Click to collapse
Well damn, here goes.
Also extra stuff like passing safetynet and some troubleshooting included but the tags were getting too much.
$Blue - specifics for POSP 11 #this whole guide was made cuz of it after all
#Green - comments
Red - warnings
and with that out of the way...
____________________________________________________________________________________________________________​SHAI'S MEDIOCRE ROM & ROOT HOW TOS: FOR DUMMIES​FROM DUMMIES​FOR DUMMIES​
____________________________________________________________________________________________________________​
Python:
import disclaimer
"""
This how-to is presented to you from my own experiences, AS IS.
By using it, you agree not to hold me responsible for any bricked devices,
melted icecream or lost cat pics. Don't blame me if you forgot to back up some things before proceeding.
Check that all your data has been backed up before proceeding with this guide and then check again, one can never be too safe.
If I missed something or you'd like to add your own experiences to this so it's all in 1 neat place let me know.
"""
____________________________________________________________________________________________________________​
[1. PREREQUISITES]​
0*. UNBRICK GUIDE:
# the mega-thread preloader is redundant since this became a thing imo
UNBRICK BEGONIA NO AUTH
Requirements: 1) PC 2) Internet 3) Patience Windows Method: • Download this file - Click-Here (Download from Telegram) (https://mega.nz/file/A4YSEZaA#0Jk3_jH8uVtMnATciVRtWw2r_SH0NPLq4P6SrGNuwJQ)
telegra.ph
1. TWRP:
⠀⠀⠀⠀- ANDROID 9: TWRP 3.3
⠀⠀⠀⠀- ANDROID 10: # no problems encountered with any of them for me, go crazy
⠀⠀⠀⠀- ANDROID 11: # trying to install an A11 rom from twrp 3.3 RESULTED IN A BRICK
⠀⠀⠀⠀⠀⠀⠀⠀# following ones confirmed to be working | | 3.4 may work on noncfw, if anyone tested it out lmk
⠀⠀⠀⠀⠀⠀⠀⠀CFW: https://sourceforge.net/projects/begonia-oss/files/CFW-TWRP/ #3.4 tested -> working
⠀⠀⠀⠀⠀⠀⠀⠀NONCFW: 3.5 or forks of it [BlackCatTWRP , unofficialTWRP unified tested] worked for me,
# MAKE SURE NOT TO MIX UP CFW & NONCFW RECOVERIES
# MAY CAUSE-> unable to boot in recovery, bootloop[from OTA update while first effect ] ! ! and in few cases BRICKS
2.CFW:
⠀⠀⠀⠀# check megathread for dowloads and the tags on the rom that you're installing to know what to get... except this
⠀⠀⠀⠀# guide wouldn't be a thing if those tags were accurate.... sigh.... check their site & telegram or other similar things before if you want to be 100% sure
3. Your ROM... duh
Now that that's over time to get on with the main course
____________________________________________________________________________________________________________​
[2. INSTALLATION]​
$ assuming you're coming from miui android 10, should work with other AOSP roms.
$ If you're on android 9 for some reason it'd be ideal to update beforehand, since you can't install recoveries needed by it on it
1. RECOVERY INSTALLATION: #3.4 official +ADBFTools included in my mediocre rom scripts & zip below,replace w/e
⠀⠀⠀⠀- INSTALL: ADB & fastboot tools
⠀⠀⠀⠀- enter fastboot⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀$use what I mentioned in the NONCFW A11 section
⠀⠀⠀⠀- after connecting phone to your PC, type in cmd " fastboot flash recovery <recov_name>.img
⠀⠀⠀⠀- type fastboot reboot recovery
2. ROM INSTALLATION:
⠀⠀⠀⠀-⠀on recovery -> WIPE: FORMAT DATA && ADVANCED WIPE [dalvik, system, cache, data] #somewhat overkill
⠀⠀⠀⠀-⠀on pc cmd -> adb push <drag n drop rom file> / #or /sdcard if you want | | repeat for w/e you wna add
⠀⠀⠀⠀-⠀on recovery -> INSTALL:
$ sourceforge version: VDNK30 / github ones && OTAs: noncfw
$ don't touch the sourceforge one since you'll have to move to the others either way
⠀⠀⠀⠀- # install cfw beforehand if needed by your rom select and flash ROM along with anything else you need like gapps/magisk
⠀⠀⠀⠀- reboot & proffit
____________________________________________________________________________________________________________​
[3. MAGISK AND SAFETYNET PASSING]​
1. INSTALLATION: rename LATEST MAGISK APK to .zip and flash it from recovery, or use your recovery's built in if it's up to date... that's it really
2. PASSING SAFETYNET:
⠀⠀⠀⠀- use magiskhide on google play store & services
⠀⠀⠀⠀- flash from magisk kdrag0n's universal safetynet fix
⠀⠀⠀⠀- if on android 10: use magiskhide props config to change fingerprint to begonia
$ only univ safetynet fix needed for me to pass, if you're having problems try props as well?
____________________________________________________________________________________________________________​
[4. TROUBLESHOOTING]​
1. Trying to recover from brick: Mediatek device shows up broken in device manager
-> REDO STEPS 2-4 ON THE UNBRICK TOOL​
2. Recovery crashes after a few seconds in it
->YOU FLASHED NONCFW RECOVERY ON CFW BUILD, INSTALL A PROPER ONE​
3. Device shows up with wrong/halved memory capacity
->FORMAT DATA FROM RECOVERY #obviously erases all data​
More to be added when people have troubles.
____________________________________________________________________________________________________________​
[X. MILASCENIOUS]​
# Things that don't really belong anywhere but yeah
-> POSP 11's lawnchair rewrite is still in alpha, I don't really recommend using it for the time being since a lot of features are still missing, get the one from the play store til it gets some polish. Most notably categories & hide app missing
-> On android 10 you can get ANXCamera for all the camera sensors + 64MP camera, haven't looked into a11's
-> For really big mistakes: this is how you remove magisk modules from recovery, in case you mess up big time
-> Extra used things: STOCK ROM [MIUI 12 a10] for those that bricked their phone | blackcat recovery working on posp 11 and it's good for newbies to rooting & that 1 batch recovery script
-> I really wish they're gonna add back the POSP swag (icon on top left statusbar w posp logo)
-> There is an empty character I found some while ago, it's not the same as space : it doesn't get auto deleted, use it to make your formatting neater on places where spaces >2 are being deleted [like here] or to confuse ppl? [⠀]<- that
-> Mug cakes are really great, you should make 1 sometime

github one is noncfw? confused

seb1g said:
github one is noncfw? confused
Click to expand...
Click to collapse
yeah soosoo they:
- switched from sourceforge to github ->https://t.me/SaucyPotatoNews/400
- switched from vdnk-30 to noncfw -> https://t.me/RedmiNote8ProUpdates/735
No I don't know why there are 2 diff patch notes for the same build from 2 diff ppl and at this point I gave up tryna make sense of this
And none of those are mentioned in the POSP11 thread, it's still listed as [vdnk30], causing a lot of confusion, bricks and generally a waste of time, ppl got bricks on OTAs cuz of that for god's sake, ain't that neat....

ShaiBlizzard said:
yeah soosoo they:
- switched from sourceforge to github ->https://t.me/SaucyPotatoNews/400
- switched from vdnk-30 to noncfw -> https://t.me/RedmiNote8ProUpdates/735
No I don't know why there are 2 diff patch notes for the same build from 2 diff ppl and at this point I gave up tryna make sense of this
And none of those are mentioned in the POSP11 thread, it's still listed as [vdnk30], causing a lot of confusion, bricks and generally a waste of time, ppl got bricks on OTAs cuz of that for god's sake, ain't that neat....
Click to expand...
Click to collapse
Ty bhai

[ROM][UNOFFICIAL|CUSTOM|LOCKEDBL][Q/A10][hotdog] /e/ OS for OnePlus 7T Pro - BYE Google, HELLO privacy and security (LOCK your BOOTLOADER)!

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is not just another ROM - it is a mobile ecosystem (ROM + online services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds are all signed with a custom private key for best trust. This also means you have to factory reset when coming from another ROM!
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
You can LOCK YOUR BOOTLOADER - if you like
Build variants (UNOFFICIAL, CUSTOM)
UNOFFICIAL builds:
full OTA support
no other differences to pure /e/. It is just an unofficial build (if you want to have it official test my builds and report also SUCCESS! this ROM is currently awaiting to get approved by /e/ for official builds)
CUSTOM builds:
2 variants: rooted (magisk) or unrooted
removed: the app "Apps" (see FAQ why)
added: F-Droid, F-Droid priv ext, F-Droid additional repos (disabled by default), AuroraStore, Lawnchair-latest (taken from their TG group), PhoneSky (google play store - patched for microG), Magisk app when choosen the rooted variant
patched with this safetynet patch (this will not bypass safetynet though)
fully patched for AVB / dm-verity support - means you can lock your bootloader! (all builds since 3rd of Sep 2021) - yes even the rooted variant can run on locked bootloader!
SHRP included (accepted by a locked bootloader) - means when you want to use a different recovery you have to flash / re-flash it after flashing / upgrading the ROM. Including this is needed to not brick devices running on locked bootloader.
.. read all the details about locking your bootloader in this post
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
none known (yet)
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build (while I am testing with SHRP only)
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything!
Planning to lock your bootloader? Read this first
Installation
Planning to lock your bootloader?
Read on here
Detailed guide:
follow MSe1969's guide here
Quick guide (assuming you have TWRP/SHRP already):
Full clean install as described here (FAQ #2). DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (planning to lock your bootloader? Read this first)
If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
Join my Telegram groups (see "Support" topic)
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
MSe1969, wth.. you did an AWESOME job
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot (let me know if that's the case ofc) ..
Sources
/e/ : https://gitlab.e.foundation/e
my build manifest
MSe1969's stuff

Frequently Asked Questions (FAQ)
Q #0: For CUSTOM builds only: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive
When " usb debugging root" is enabled in developer settings:
adb root
adb shell
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If your issue is not solved with selinux permissive click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.
Q #4: Is there a FAQ specific for /e/?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
App alternatives (to replace google variants): click
Q #5: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?
See OP
Q #8: Will my banking app (or other root detecting app) work with this ROM?
The answer is .. well .. simple. it depends.
First of all the following technique works regardless of what ROM you are using or what device. It worked with my LG G4, OnePlus 6T and now OP7tpro so its a generic "maybe-solution"
Read on here:
I am using a german banking app which works even when root gets detected. It will prompt and say thats bad but I am still able to use it. The same was the case for the TAN generator app of the same bank but it fully stopped working one day after a (forced) app upgrade.
So I started to play around and found a solution which works for me since several years but there is no guarantee it will work for you or for how long it will work. The process and steps must be followed briefly and nothing more, nothing less must be done.
The following references a banking app but it applies to any app which rejects starting when root or a custom ROM has been detected:
you need root, i.e. Magisk. This ROM has a custom build which includes Magisk already.
uninstall the currently not working banking app(s)
install & setup a work-profile manager like Insular, Shelter, (if you do not care about google trackers: Island), or [fill-in-another] ,.....
configure Magisk that it hides itself (i.e. re-package Magisk with a random name) & reboot just to be sure. and yes that works on signed and locked ROMs, too
newer Magisk versions will clone themself into the island profile during the repackage process so open island then switch to the island tab and remove the magisk app there (so not from the "mainland"!)
install the banking app(s) - BUT DO NOT start it!
clone that app into your work-profile (i.e. open Insular/Shelter/Island/.. find the app, clone it there), repeat that step for any app needed
configure Magisk hide for this app(s) and ensure you select all options (some apps can be expanded in magisk hide, select all options then)
remove any icons of your app(s) from your launcher but DO NOT UNINSTALL them!! (never)
in your work-profile manager (Insular/Shelter/Island/...) find your app and create a quick start launcher (repeat that for any app needed)
now start your banking app quick link (again it HAS to be the one created by your work-profile manager). usually you can identify that you are using the right one bc it has a mini icon of your work-profile manager on top of the regular app icon
enjoy. if it does still detect root or a custom ROM you either have not followed the above steps briefly or you are out of luck.
Background:
You cannot uninstall the app(s) from android (ever) because otherwise Magisk hide will not work. so you always need to keep that app(s) but never starting it.
It can make sense to try another work-profile manager if the above way fails for you as the app devs using different techniques
Q #9: Will DRM protected content work? | Will this ROM satisfy Safetynet?
Likely not. Yes this ROM is signed, selinux is enforcing and you can lock your bootloader but these days this is not enough anymore. While there are some workarounds available these might stop at any time. So do not expect that this will work or work for a long time.

LOCK your bootloader​Yes you read correctly: you can lock your bootloader again! Why is that so amazing? The most important thing: security. When your bootloader is locked no one can install or modify without you notice it. Let's say you loose your phone and your bootloader is unlocked. The person can boot into fastboot and flash a custom recovery of his choice and have full access to your data (if not having a pin set) but also can tamper e.g. your system partitions like installing malware. Yea for that the attacker needs physical access to your phone but there is malware around and this is REAL which uses bugs to install themselves even on your system partition. For this the attacker does NOT need physical access to your phone.
On a locked bootloader the device won't boot anymore as a modification like that will be detected.
Anyways.. yea one can say both attack variants are not THAT critical or affecting you as you are paying attention on what you do but .. there is a always a risk of undetectable malware like the good old drive-by downloads etc. so .. its all up to you if you want to have that extra barrier or not..
But before we begin
a HUUUUGE thanks to @WhitbyGreg !!!
All this here would not be possible without his great guide here ! Ofc I need to adapt it and integrate all this within my automation process but it would have been a LOT harder without his thread(s).
So if you love it having a locked bootloader now - give HIM some thanks clicks, donations, hugs.. as well
Checklist: is locking the bootloader something for me?​If you answer anyone - even just 1 - of the following with YES - then KEEP AWAY FROM LOCKING your bootloader!
I want to remove (not just disable) system apps (often called bloatware)
I want to add / convert apps into system apps (e.g. Titanium Backup offers such an option)
For rooted variant: I want to update Magisk to the latest version
For rooted variant: I want to change init scripts, XMLs or anything else within system/, product/ etc partitions
For rooted variant: I want to use an ad-blocker which modifies the "hosts" file (system partition)
I want to install another recovery then the one coming with the ROM (SHRP)
I want to flash GApps (LOL! this is /e/ !! even on unlocked bootloader this won't work!)
I want to flash anything else in recovery which modifies: boot, recovery, system or any other partition then userdata
Do you have answered at least 1 of the above with YES ? Then do NOT lock your bootloader. It WILL brick your device if you try.
if you can live with the above - GO GO GO
Lock your bootloader - process​Downloads
ROM without root: https://leech.binbash.rocks:8008/e-os/a10/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom_pkmd.bin
ROM with root: https://leech.binbash.rocks:8008/e-os/a10_rooted/hotdog/ (all CUSTOM(!) builds since 2021-09-03)
AVB key: https://github.com/sfX-android/update_verifier/blob/master/hotdog_eos-q_custom-rooted_pkmd.bin
backup all your data. I am serious EVERYTHING. we need to FORMAT the userdata partition during the lock process and there is no way around. so use TB or Swiftbackup, Migrate or any other. Always a good idea to also having a TWRP/SHRP backup just for the case..
boot your current recovery
flash the ROM of your choice (with or without root)
reboot to the bootloader / fastboot
if you flashed the ROM with root: fastboot flash avb_custom_key hotdog_eos-q_custom-rooted_pkmd.bin
if you flashed the ROM without root: fastboot flash avb_custom_key hotdog_eos-q_custom_pkmd.bin
type: fastboot oem lock
approve locking the bootloader on the phone's screen
< take a deeeeeeep breath >
recovery (SHRP) will load automatically
choose wipe -> format(!) data (there is no way around)
boot android -> you will notice a new bootloader message warning you that you have a custom ROM installed - but it will load
congrats! you now running on a locked bootloader + /e/ OS!
for the rooted variant: start the Magisk app (requires internet), accept the install request and open the magisk app afterwards and let it reboot when asked
enjoooooy
Locked - now what?​OEM unlock option
The above does not mention one additional step: disabling OEM unlock in developer options. For a reason. I mean you CAN uncheck that option now that all is running fine but you don't get any more security tbh.
The reason is if you keep it checked an attacker is able to unlock your device but it WILL format the encryption keys when done. that means no way to access your data anyways. If you want to avoid even that then feel free to uncheck OEM unlock in developer settings as well but then a brick will require low level recovery tools to bring your device back to life.
Magisk (rooted variant)
I recommend to disable automatic update checking within magisk settings - remember: when flashing a newer version of magisk it WILL brick your device. you have to wait for me updating it within the ROM.
Anything you do within Magisk can EASILY BRICK your device, installing a magisk module which tampers your system partition: BRICK. So really really check if a module touches anything mentioned in the above checklist topic. Using the magisk variant has HIGH potential of bricking your device.
You can use all standard root functions, magisk hide and even re-pack the magisk app though.
Bricked
Always keep an eye on the above "Checklist" topic! If you change/do something mentioned there you will brick your device with a snap of a finger.
Android does not boot anymore because you flashed a newer version of Magisk or changed something within the protected partitions:
boot recovery (power off, press power on and vol down the same time and keep it pressed until you see the shrp logo)
flash the current ROM version or a later release and reboot
recovery does not load bc you flashed another recovery:
wait for the next OTA and it get fixed automatically
or unlock the bootloader again (this will need to FORMAT the userdata partition)

Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?

L4WL13T said:
Sounds like a cool ROM, however I'm curious, what issues might I run into having no Google services? Are most apps going to work ok?
Click to expand...
Click to collapse
hard to say. there are some which might not work and/or apps you should avoid (as they contain trackers etc). There is a good list of alternatives in FAQ 4 above

steadfasterX said:
​
Do a full (i.e. not just TWRP/SHRP - as those do not backup your internal storage) backup before doing anything
Click to expand...
Click to collapse
Do TWRP backups even work on this device? Last I heard, it was broken.

Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)

ap81z said:
Hi! Why is there no gesture based navigation??? I'd love to see it!!!
at first glance the system is very surprising, like the very idea of a system without GAPPS. Looking forward to the development)
Click to expand...
Click to collapse
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..

steadfasterX said:
Yea they removed it bc their launcher does not support it yet. There is an open issue on their bug tracker. I don't know when they will fix it tbh but i need it so bad that i found a way to include it. It's a kind of dirty hack but ... it works and will find its way in my next CUSTOM build..
Click to expand...
Click to collapse
ok, I'll be waiting!!!

forgot to mention it here (another reason why users should join my automation channel):
Gestures are supported since the latest version.
breaking news:
I was working on using this device as my DD again but I have very strict requirements:
/e/ OS must work (reason: privacy focus, google-free) [ DONE ]
encryption must work (reason: security, e.g. loosing or selling the phone) [ DONE ]
selinux must run in enforcing [ DONE ]
/e/ OS must be signed with own private key (reason: allowing secure OTA and local/recovery upgrades) [ DONE ]
SHRP must work (reason: a password on startup can be set - allowing to have rich recovery feature set but secured - when the bootloader is locked!) [ DONE ]
and here the fun began:
/e/ OS must run on locked bootloader [ DONE ]
SHRP must run on locked bootloader [ DONE ]
OTA must work on locked bootloader [ WIP ]
so overall I am pretty much where I want to be and can provide a privacy focused, secure, google-free and locked bootloader experience soon...
stay tuned

Ever wanted to lock your bootloader - not on STOCK but on a custom ROM?​Most ppl don't know (or don't care) that almost all Oneplus devices offer such an option - if the ROM dev is willing to take the journey implementing it.
This is now possible when running my /e/ OS CUSTOM builds (read more in the OP about the diff between CUSTOM and UNOFFICIAL) and not just that my new CUSTOM builds coming either pre-rooted or not - whatever you wish more.
I have to say that this was something on my to-do list since I bought this device more then 1 year ago. After a lot of work in the past months I am finally where I am and can use it as my DD again. Something which makes me reeeeeeally happy lol
Dunno but maybe someone enjoys having a locked bootloader like I do
Read all the details and how it works: here

Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks

Also I doesn't find any option to change 60hz/90hz ?

Thetimelost said:
Hey just for info, I'v tried without relocking bootloader, to install aa auto as I do on lineage, and it give me the same result as locked bootloader, a black screen, I know that it's not your job to debug aaauto since it's a de-google rom. But the rom is unusable in my case, another question, why Play Store is installed by default ?
Thanks
Click to expand...
Click to collapse
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Thetimelost said:
Also I doesn't find any option to change 60hz/90hz ?
Click to expand...
Click to collapse
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh

steadfasterX said:
The CUSTOM builds containing the play store as i need it for some apps which do their license check over it. You csn simply deactivate it or use the UNOFFICIAL build instead (which do not allow locking the BL though).
Hmm good q. Is there an option for that in LOS? Maybe that's a limitation by /e/ but dunno tbh
Click to expand...
Click to collapse
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^

Thetimelost said:
Thanks for the answer ! Yes on LOS there is an option for it, and after use my op7t pro for 2 year with 90hz I directly spot the difference. ^^
Click to expand...
Click to collapse
Hm interesting mine is running at 90 hz all the time it seems. Weird bc /e/ is based on LOS so maybe its an option in a11 first?

When will we get Android 11?

andr052h said:
When will we get Android 11?
Click to expand...
Click to collapse
Why do you want to have it?

steadfasterX said:
Why do you want to have it?
Click to expand...
Click to collapse
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.

andr052h said:
I mean, I really like what you have done with your current build, and would love to see that applied to the new Android 11 version as-well.
Click to expand...
Click to collapse
Well first of all I thought no one uses my ROM anyways so there was no need for me upgrading to a11. This ROM is rock stable and does what i need as a daily driver and gets monthly security patches. Many ppl just want to have a newer android version just bc there is one and not bc for a specific reason. That's why I'm asking.
I personaly prefer a good working ROM over having always the newest android version just because there is one
Other then that i may upgrade to a11 but not anytime soon. Main reason is that I am using this as my daily driver so it would be hard alsi dev on it..

Lineage OS 19 (ANDROID 12) for Moto G7 Play [UNOFFICIAL]

After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )

Thank you all for this ROM, also there are LineageOS 20 builds (Android 13) on official LineageOS site, i want to ask if there is an way to fix ambient display on LineageOS 19, LineageOS 20 sadly gives me way too low RAM to use it, and SWAP memory is not working on Lineage 20
Edit: many apps do restart extremely often, but it's understandable since it's only an 2 GB RAM device running an ARM64 ROMs

@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?

kreksoverzum said:
@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?
Click to expand...
Click to collapse
Well, i didn't test that but sadly, Moto Camera doesn't even have enough permissions to save pictures to SD Card

please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"

newbierooter said:
please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"
Click to expand...
Click to collapse
Try to install Fastboot/ADB Driver

feder86co said:
After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )
Click to expand...
Click to collapse
when will we have new updates?

Androi100 said:
when will we have new updates?
Click to expand...
Click to collapse
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org

chuy19312 said:
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
more on the site there is only one lineage 20

Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
Well, sadly, LineageOS 19 zips were deleted, even LineageOS 18 zips some time ago, and i never understood why, there are only LineageOS 20 builds today

Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
I just remembered, i have the last official LineageOS 19 for Moto G7 Play, i uploaded it to my Google Drive, here you have an link
lineage-19.1-20221225-nightly-channel-signed.zip
drive.google.com
The only bug it have is that ambient display doesn't work, at least, is the only one i found
Note to official developer of this ROM. if there is an problem to share this old version ROM, please tell me , but please, don't report my link in case there is an problem, i can remove the link but not the ROM since i have it because LineageOS 20 restarts almost all of the apps, multitasking on that rom doesn't exist because when switching on apps, they get restarted, even system ones
Edit: if someone have an build of LineageOS 18 or 18.1, please, give me an link for it