Database Info

[TIP] - Make *ViPER4Android* Work on *ANY* Marshmallow Device EASILY !!

FIRST OF ALL :
For rooted devices, busybox properly installed , etc. etc.!
Works on MM, should work on Nougat to...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Make ViPER4Android work on any marshmallow device : SELinux Permissive Fix
This is the easiest method I found so far, to make Viper4Android work on my V10 H960A running MM
Thanks to Sidharth Pk Here’s how you can install ViPER4Android on your Android phone running on Marshmallow or above. Change the SELinux policy from Enforcing to Permissive and enable ViPER4Android on your device. Also, fix the common errors while installing V4A like abnormal driver status, no processing etc.
I will copy/paste here his short instructions and for further details I will post a link to his page at the end of this post
Change SELinux to Permissive & Make ViPER4Android Work on any Marshmallow Device (By Sidharth Pk) :
ViPER4Android itself needs root access. So there’s no point of saying that your device must have root privileges.
.
Get ViPER4Android’s latest APK from here and install it on your Marshmallow device.
.
Now open it and let it install the driver for your device.
.
Once you get the install complete message, simply reboot the phone.
.
After bootup, Install Terminal Emulator App from here and install it on your phone.
.
Open it and perform the following commands one after one
Click to expand...
Click to collapse
Code:
[COLOR="Navy"][SIZE="4"][SIZE="5"]su
setenforce[/SIZE][/SIZE][/COLOR]
Close the terminal and check the driver status on ViPER4Android app, it should display like this:
{
"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"
}
The Enable & Processing status will automatically change to Yes once you activate the master power option and start playing music on your headphone/speaker. If this method doesn’t work for you, you can flash the ViPER4Android Marshmallow ZIP file. It changes the SELinux from Enforcing to Permissive.
For more info have a look at the original thread/page:
http://www.techbii.com/install-viper4android-marshmallow/
Cheers

Didn't work for me.

didn't worked for me either !!

PHH GSI surfaceflinger or full screen immersive issue

I just installed android 11 GSI based on PHH treble. It gets installed successfully, but there is a weired bug. The whole screen keeps moving up and down. Some times the navigation bar appears and disappears. I can't even get past the lock screen due to this bug. Forget enabling adb debugging. Is there another way to take logs? Such issue never existed on Android 10 gsi. I'm sending this message from andorid 10 gsi. I tried all GSI based on PHH 11 but same bug persistes. I had opened an issue on the phh gsi page but didn't get a conclusive response.
I had installed system-roar-arm64-aonly-vanilla.img.xz
My device - Micromax Infinity N12
Vendor version - android 8.1
Chipset - mt6762 helio P 22
Device architecture - arm 64, a only system partition.
Link to issue opened on github page
https://github.com/phhusson/treble_experimentations/issues/1674
{
"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"
}
Note - I'm not stuck in a bootloop, I know how to get out of one. I need help is solving this issue

Is there any way I can enable usb debugging without unlocking the phone?

Tab E said:
Is there any way I can enable usb debugging without unlocking the phone?
Click to expand...
Click to collapse
yes just enable developer options and enable usb debugging there

ineedroot69 said:
yes just enable developer options and enable usb debugging there
Click to expand...
Click to collapse
I cant even unlock the phone due the above bug. The screen keeps moving up and down. I've tried for a long time but just doesn't unlock

Magisk hide "Settings" app force closing

A few weeks ago, my hidden Magisk Manager (hidden as "Settings") stopped working. When I try and launch the generic Settings app it sets up, I get the normal FC menu ("Settings keeps stopping") error. I also get it when I open up any app that I previously allowed root access to, but obviously I cannot add new apps superuser access. I also get the FC every time I reboot the phone.
I haven't updated my OnePlus 9 Pro since the ColorOS 12 update came out, as 1) was not a fan, and 2) everything I read said I'd need to wipe the phone to get root back. Needless to say, it's been a while. My phone is currently on the 11.2.10.10.LE15AA version.
This just started happening one day, but I have no idea why. I am not sure what version of Magisk I am on, because I can't open the app. I also tried downloading the latest and installing the APK, but when I launch it, it's says things need to be "fixed" and to reboot. I then get the choice the normal Magisk installer brings up. I tried doing a direct install, but it failed. I also tried to restore the boot image, but it said the backup wasn't found (never seen that either, as I restore images every time I do an OTA).
Not sure what to do at this point. I'm at a complete loss. I would appreciate any help you guys can provide!

Do a LOGCAT to get the very reason why Magisk is not working.

I tried to get it as quickly as possible to minimize clutter, but it's still pretty long. I believe I've found where in the log the FC I captured (by looking for "zygote", but not sure what to make of it. It sounds like a file or something is missing.
{
"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"
}

Doesn't seem like the logcat file got attached.
Oh well, here's a link:
FilePost
filepost.io

[ROM][10][J600X][ARM64] HAVOC OS

{
"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"
}
HAVOC OS 3.12​Android 10
Before you get started,
i am not responsible for bricking device, dead SD cards,
muted alarm, or even thermonuclear war.
YOU have chosen to do this modification,
IF you point your finger to me for bricking your device,
I will laugh at you.​DEVICE:
All J6 variants, so don't ask if it work on a especific j6​
INSTALLATION:
Wipe cache, dalvik, system, vendor and format data
Flash ROM zip
Reboot to system
Enjoy
(if you want magisk and/or gapps, only flash them after the first boot)
FEATURES:
Archtecture ARM64
Simple Kernel Enforcing from Astrako (you can flash any other kernel at your choice, like ares or H-Kernel)
Optimazed
Clear Interface
Good Perfomace
All Havoc customizations
Gapps not included
DOWNLOAD:
Telegram | Attached file
SCREENSHOTS:
In the 2nd comment
WORKING:
Wifi
Bluetooth
Audio (Speaker and Microfone)
Camera (Video and Picture)
Flashlight
SMS
SIM Calls
Mobile Data
NOT WORKING:
None?
CREDITS:
@BrunoLiraTM
@Astrako
@GonicTEAM
HavocTEAM
Source Code:
HavocOS: GitHub
Kernel: GitHub

SCREENSHOTS:

Pro

Revoke USB authorizations is missing

UPDATE: now it shows up (dunno why), but I still get no actual authorization dialog when I try connecting with ADB, leaving the computer unaurhorized

DerivativeOfLog7 said:
UPDATE: now it shows up (dunno why), but I still get no actual authorization dialog when I try connecting with ADB, leaving the computer unaurhorized
Click to expand...
Click to collapse
You can use ADB over network wirelesslly

Hi, its a nice rom. I love native adoptable storage, i think its the only rom with this function. Thank you for the hard work. But it present 2 important bugs.
1st Wifi in j600G sometimes stop to work, or says its out of range, i try to restore wifi config but no luck... still bugged.
2nd flash. Camera Flash is broken or fail. Frontal Flash is totally broken. Third party camera apps works with flash, but not frontal flash.
There is a possibility that you can fix those bugs please? or can you spare me a solution? At least the Wifi one please
3rd Volte isn't working, is an aosp based rom, so Volte will not work.
Thanks for your time and Im sorry for my bad english.

Med0x said:
You can use ADB over network wirelesslly
Click to expand...
Click to collapse
No, I still can't authorize

Question Stuck in Download Mode: Error verifying vbmeta image

Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"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"
}

Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/

Thank you and please excuse my stupidity.

@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?

fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.

deleted

Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.

fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.