Database Develop

OTA update for GPE 5.1 LMY47O.H9 to H10 -- TWRP

Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available. It only works for clean H9 installs that are NOT rooted.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
{
"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"
}

http://forum.xda-developers.com/showthread.php?t=2708589
Sent from my HTC6535LVW using Tapatalk

Getting an Error Executing updater binary in zip, error.
/system/bin/app_process32 has unexpected contents

/system/app/BasicDreams/BasicDreams.apk has unexpected contents
Please advise!
UPD1 Sorry, it was Philz recovery. Now I got TWRP and getting the same issue with app_process32
UPD2. It seems I have to unxpose and unroot first - but my M8 keeps rooting itself, cannot get into unrooted mode.

radeon_x said:
Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
Click to expand...
Click to collapse
Thanks for the update, but it didn't work and causes an error like the post before this.
Unexpected error .... etc.

I got the same errors trying to sideload the original OTA zip through stock recovery, so it must be something in the zip itself.
Maybe a security measure to prevent installing on modded phones.

Would it be possible to post the entire H10 ROM .zip? I usually have problems updating just the OTA file. graffixnyc usually posted it but for some reason that thread got closed.
Thanks!

The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...

sudaltsov said:
The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...
Click to expand...
Click to collapse
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.

If you received the OTA notification for H10
Well, I have tried it twice (from H6 I believe to H9 and now from H9 to H10) and it worked and I did not loose any data files! I got the OTA notification and followed the following protocol (I am rooted and running TWRP):
1. Revert any app that had root access (i.e. Adblock... just revert and disable). If you have XPOSED framework you have to revert everything to stock!
2. Withing the SuperUser app (SU), fully "un-root" the phone.
3. Restart (probably not necessary)
4. Install H9 Recovery (I downloaded it from graffixnyc: http://forum.xda-developers.com/showthread.php?t=2708589) Do not forget to at least thank him!
5. Erase cache (Fastboot erase cache) just in case and Restart.
6. Install OTA :good:
7. Done! Now you have to install again TWRP via fastboot (erase cache once again, just in case...) for root access and re-install whatever you had before with root access. :laugh:
Long process but saves me a lot of headaches with data and any other errors may occur...

I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.

sudaltsov said:
I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.
Click to expand...
Click to collapse
Well the initial boot after clearing the cache takes a really long time of course.... But if it really and truly doesn't boot after several minutes just install the full H10 from that other thread.

Seems I have no choice but to sideload (thanks to TWRP) the full OTA H10..

radeon_x said:
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.
Click to expand...
Click to collapse
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!

m_atze said:
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!
Click to expand...
Click to collapse
Thanks, it's work for me.
btw the original thread is here http://forum.xda-developers.com/showthread.php?t=2706441

After multiple issues I just installed the H9 RUU unrooted from @graffxnyc, then installed the ota which popped up as soon as it rebooted.
For now I'm leaving it unrooted etc until marshmallow drops later this month.

Don't know whats the update for tho. But anyways installed. Maybe to prepare our system for Marshmallow update? Like what cyanogen did?

i'm not sure what's going on, but the update is a POS. Like sure it's a stagefright fix, but they've broken more than fixed it. Im having massive lag issues, the text windows are stuttering at times, unlocking the phone freezes it for a while and there are times where the notification sounds don't even sound off.

Sorry guys. I've had no problems at all.
This Version is woking like charm.

H10 update recovery
Could someone provide the recovery image from the H10 update?!

[Magisk ON S7 EDGE]Magisk Safatynet Pass on Samsung Galaxy S7 edge

Hi guys! now i show to work magisk safatynet pass
Thanks @xJovs for your tutorial!
Link for your post Click Here!
Let's go
All rights reserved @xJovs for this tutorial
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
__________________________________​
*UPDATED*
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
- Samsung Galaxy S7
- SamSung Galaxy S7 EDGE
__________________________________​
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0+/7.0+
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Magisk V11.1 & Magisk Manager 4.1
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(If you cannot bypass with Xposed, use Root Switch!)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Step 1:
Clean Install
The first step install your custo rom, i installed SuperRom 1.2 MM and custom Karnel SuperStock 1.6 on installation.
Step 2: (For no MagiskSU users!)
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"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"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 4.2.6, SafetyNet Helper Sample, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV11.1
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V11.1, or reinstalling your rom.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "policy", change the permissions of the file from "444" to "440". If MagiskSU pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V11.1. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
If you're still not passing, try disabling USB Debugging in Developer Options!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________​
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.[/QUOTE]

Thanks man!
This actually worked on my S6 Edge SM-G925I.
I was just hoping if you could also figure out a way to use Samsung Pay despite having the Knox triggered.
TIA.

Shrey14 said:
Thanks man!
This actually worked on my S6 Edge SM-G925I.
I was just hoping if you could also figure out a way to use Samsung Pay despite having the Knox triggered.
TIA.
Click to expand...
Click to collapse
You are welcome!
On Android N you have update your Karnel for SuperStock 2.3 for work safetynet.

ClaudioJuniorBR said:
You are welcome!
On Android N you have update your Karnel for SuperStock 2.3 for work safetynet.
Click to expand...
Click to collapse
Currently I'm on Android M and safetynet is working. Please see the attachment.

Close this topic please!

I am stuck on stage 5 because I cannot see the check boxes on magisk manager 4.2.7. How to proceed?

Wow can't belive this actually worked!I spended so many times trying to make it work thanks OP.
However i can't make it work with xposed, the Safetynet check fails, it was strange because the first time it worked but as soon as i rebooted it was not working anymore.
There is a way to make Xposed work?I used Root Switch but it says is not fully supported for Magisk because it says that Magisk have it's own switch, i don't think it's referring to Magisk Hide because i have already enabled it so maybe i'm missing something here?

Help needed with Step 4
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.

Sandiramogan said:
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.
Click to expand...
Click to collapse
Error 1 can mean several things, post a recovery log from the installation.
And this guide is a bit outdated... Magisk performs step 6 and 7 automatically since v11.5.
Edit: answer my post in the support thread instead.

With magisk v12.. Any idea?

Didgeridoohan said:
Error 1 can mean several things, post a recovery log from the installation.
And this guide is a bit outdated... Magisk performs step 6 and 7 automatically since v11.5.
Edit: answer my post in the support thread instead.
Click to expand...
Click to collapse
Thank you for your reply. I managed to install Magisk v12 after performing a completely clean wipe and flashing the stock ROM from ODIN. I immediately attempted to install Magisk after flashing the latest version of TWRP and everything works like a charm, even passing Safety Net. However on the other hand, I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.

Sandiramogan said:
Thank you for your reply. I managed to install Magisk v12 after performing a completely clean wipe and flashing the stock ROM from ODIN. I immediately attempted to install Magisk after flashing the latest version of TWRP and everything works like a charm, even passing Safety Net. However on the other hand, I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.
Click to expand...
Click to collapse
Since you're passing SafetyNet it's a pretty sure bet that you have Magisk Hide enabled. That's all you need to do since the KNOX counter is masked by Magisk Hide. It doesn't work?

Do you know if Google changed something? Today I noticed that I can't see Fire Emblem and Mario Run in the Playstore. Days ago it was working fine but now it seems they are not compatible again.

I don't know why but I can't add new scripts in Kernel Adiutor.
Everything else worked. Any idea?

things i do to play super mario run

Works well when disable xposed in module section in magisk manager then reboot.
Any fix for work safetynet pass with enable xposed ?

koko115 said:
Any fix for work safetynet pass with enable xposed ?
Click to expand...
Click to collapse
Nope...

935V user here: I get "Custom Binary Blocked by Secure Boot". I flashed using Flashfire instead of TWRP. I used the root method described here: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
Should I have rooted a different way as to utilize TWRP?

some one can help me?
imgur.com/a/4cufj

Does anyone know if this works on any of the US models?

[ViPER4AndroidFX][AudioMod] Install Latest ViPER4AndroidFX_v2.5.0.5 on Any ROMs

{
"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"
}
*** I'M NOT RESPONSIBLE IF YOUR DEVICE IS NOT BOOTING UP, DEVICE IS BRICKED, GOT BOOTLOOPED OR WHATEVER ***​*** DO AT YOUR OWN RISK ***​*** READ AND UNDERSTAND EACH AND EVERY STEPS CAREFULLY BEFORE PROCEEDING ***​
The most commonly used Audio modification tool among the Android users is ViPER4Android. It has been making audio clearer and more perceptible on millions of Android devices out there. Today here, I will be guiding you on how to Install ViPER4Android on any ROM in your devices.
After months and months of no activity, the Viper4Android developer zhuhang has finally announced the official 2.5.0.5 update. While primarily, the update aims at enabling users to install ViPER4Android on Nougat 7.x.x, it also incorporates some new features.
Code:
CHANGELOG:
New App icon, package name, and UI
Added cross-channel (“quad channel”) convolver support.
This allows faithful reproduction of sound-field effects requiring such cross-channel convolution, such as simulation of speaker soundfield on headphones, or crosstalk cancellation (stereo widening) on stereo speakers.
Added FET compressor (new compressor / limiter simulating operation of FET circuits)
Support for custom settings storage path (no more looking everywhere in the phone for the settings directory!)
Miscellaneous bug fixes.
Code:
BUILD INFORMATION:
Version: FX version 2.5.0.5 (active)
Codename: (FX version) Beautiful
Compiled date: September 1,2016 / September 4,2013 – Official Release
Operating environment: Android 2.3 / 4.0 / 4.1 / 4.2 / 4.3 / 4.4 / 5.0 / 6.0 / 7.0/7.1/7.1.2
CPU platforms: ARM (ARM CortexA8 or higher), x86(Atom/i3/i5/i7)
Language: English (US) / Simplified Chinese / Traditional Chinese / more
​
Warning -
Installing incorrect/incompatible mods on your Android device could be harmful. Please make sure that you are aware of the outcome and don’t forget to take a Nandroid backup of your current ROM before proceeding. DroidOrigin or any of its members shall not be held liable for any damage to your device. However, if you’re stuck, we will still try to pull you out of any troubles.[/CENTER]
Installing Viper4Android is pretty simple, given that you meet the requirements pre-hand. If you have found yourself in a sticky situation, then the steps below could be of help too.
Requirement -
Rooted Device.
TWRP recovery.
BusyBox 1.26.2
ES File Explorer or Any Root File Browser.
NOTE :​There are two files provided in the download section below. One is for manually installing and another one is for directly flashing through twrp. Please download any one file whichever you want and then follow the correct steps for that file only. Before proceeding, please check whether you have downloaded the manual installation file or flashable file. If you have downloaded the manual installation file then follow the procedures for manually installing the app & drivers and if you have downloaded the flashable zip file then follow the procedures for flashing the zip file through TWRP and then installing the driver.​
Steps For Manually Installing ViPER4Android in your device-
1. Now that you have everything setup correctly, download the official ViPER4Android for Nougat (FX 2.5.0.5) from below.
2. Extract the downloaded zip and it will contain two apks –
ViPER4Android_FX_v2505_A4.x-A7.x.apk
ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk
3. Since we are going to install Viper4Android on Nougat, we will just need the “ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk” file.
4. If you have downloaded it to your PC instead, just transfer the apk to your phone’s storage.
5. Before we head to the installation, open the ES File Explorer and grant it root permissions when prompted.
6. Open ES File Explorer and browse to the location where the apk is present. Copy the “ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk” file and move it to “/system/priv-app“.
7. We are not done yet. Long-press the file, tap on the 3-dot overflow button, and select Properties. And set its permission to -rw-r–r–, and select APPLY.
8. Reboot your device now.
9. Now go to the app drawer and run the ViPER4Android FX app. When you are asked for storage permissions, make sure to grant them.
10. A prompt will display for driver installation. Select Yes to confirm the driver installation process. You will also need to allow Superuser (root) permissions to the app.
11. Your phone’s screen may freeze, don’t worry just wait and do not exit the app. Your android system will popup that app is not responding, just press wait button. Let the app finish it's driver installation, so don't exit the app now. When the installation is successful, you will get a message. Tap OK and reboot your device.
When your device reboots, you will have completely functional ViPER4Android on Nougat and other Android versions.
If you have trouble in driver installation, read the troubleshooting section below or comment right away.
Steps For Installing ViPER4Android through TWRP in your devices
1. Download the flashable zip file from below (Filename - ViPER4Android_2.5.0.5 (Flashable))
2. Reboot to recovery.
3. Flash the ViPER4Android_2.5.0.5 (Flashable).zip file.
4. Reboot system.
5. When device is booted up properly, then open the ViPER4Android app.
6. If it will ask root permission then grant the root permission.
7. It will popup a message for installing the driver. Just tap ok and wait for installing the driver.
8. Your phone’s screen may freeze, don’t worry just wait and do not exit the app. Your android system will popup that app is not responding, just press wait button. Let the app finish it's driver installation, so don't exit the app now. When the installation is successful, you will get a message. Tap OK and reboot your device.
When your device reboots, you will have completely functional ViPER4Android on Nougat and other Android versions.
NOTE : PLEASE DISABLE YOUR DEFAULT MUSICFX OR AUDIOFX IN ORDER TO USE ViPER4AndroidFX​
Credits -
zhuhang for developing the ViPER4Android
ViPER4Android Team
and many more.
(If I have missed anyone's name then please PM me for that)
You can download the ViPER4Android FX_version2.5.0.5 from below. Please follow the steps properly otherwise you will end up with problems.

Troubleshooting -​
If your driver installation has failed, then there could be few reasons behind it. Follow the simple steps below and check if anything helps.
Getting “Driver instal failed: I/O error, please reboot and try again”? Then read step again.
Uninstall the current busybox and switch to a different app to install busybox on your Android.
The most reliable and widely used method to root and manage permissions is SuperSU. If you’re using any other root method, uninstall that and opt for SuperSU.
Driver installation was successful, but V4A is still not working? The most common reason behind this is that your device may have other sound mods or tweaks installed. Disable them and completely remove them if possible.
On some devices, you may require to change your SELinux status from “Enforcing” to “Permissive”. You can do that by using the SELinuxToggler.
If nothing above has worked for you, then you may try switching to a different ROM as your last resort.
If you still have problems, comment below and don’t forget to mention your device model, ROM, and Android version.

reserved

reserved 2

do we still need busybox?

emirfahimi said:
do we still need busybox?
Click to expand...
Click to collapse
Without busybox you can't install viper4android. You have to install the latest busybox.

Hey bro , i use lineage os rom and i get driver install failed eventhough i change different busybox ..

not working it says cannot detect root and failed to install driver

emirfahimi said:
not working it says cannot detect root and failed to install driver
Click to expand...
Click to collapse
First root your device, then install the busybox. After that install the viper4android.

raven001 said:
Hey bro , i use lineage os rom and i get driver install failed eventhough i change different busybox ..
Click to expand...
Click to collapse
Please check the troubleshooting post.
Otherwise try this busybox which is shown in the screenshot below -

juyel92 said:
First root your device, then install the busybox. After that install the viper4android.
Click to expand...
Click to collapse
i did exactly as the step my phone is already rooted

emirfahimi said:
i did exactly as the step my phone is already rooted
Click to expand...
Click to collapse
Please check in devloper menu whether the root access is enabled for both adb & apps.

juyel92 said:
Please check the troubleshooting post.
Otherwise try this busybox which is shown in the screenshot below -
Click to expand...
Click to collapse
Still not work bro ,,

juyel92 said:
Please check in devloper menu whether the root access is enabled for both adb & apps.
Click to expand...
Click to collapse
yes it is adb and apps but its working other app such as free dom or lucky patcher can be used and i'm pretty sure root is working on my zenfone 5

raven001 said:
Still not work bro ,,
Click to expand...
Click to collapse
What error you are getting?

emirfahimi said:
yes it is adb and apps but its working other app such as free dom or lucky patcher can be used and i'm pretty sure root is working on my zenfone 5
Click to expand...
Click to collapse
Can you please share the screenshot of that error ?

juyel92 said:
What error you are getting?
Click to expand...
Click to collapse
This

juyel92 said:
Can you please share the screenshot of that error ?
Click to expand...
Click to collapse
View attachment 4131491

raven001 said:
This
Click to expand...
Click to collapse
I will check this issues.
Please give me some time. I will soon update/fix this issues.

I will soon fix these issues. Till then please wait and be patient.

Impossible to remove the root + flash stock rom for nem-l51 android N

Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!

Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.

sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root

Stay with magisk, it is better than SuperSU

PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !

Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob

Tata Sky App detecting root

I have renamed the Magisk package but it's still detecting root. My Jio app running successfully after renaming package but not Tata Sky. Pleas help me.

chaitut715 said:
I have renamed the Magisk package but it's still detecting root. My Jio app running successfully after renaming package but not Tata Sky. Pleas help me.
Click to expand...
Click to collapse
Enable Magisk hide for that app like the pictures below. And check your props to verify if you are passing CTS profile check.
{
"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"
}
Enviado de meu POCOPHONE F1 usando o Tapatalk

Same problem
Hey I'm having the same problem, somehow the tatasky app detects root.
I have magisk, hide, repacked name, passed safetynet and can use banking apps with ease meh.

Please link for this app in Google Play store.
This app ?

It's still not hiding.. My device had passed safetynet check and hidden Tata Sky but still it's detecting Root.
Other banking apps even Yono Mobile, Gpay, PayTm all are working fine!

Yes that is the app sorry for the late reply
Spartacus500 said:
Please link for this app in Google Play store.
This app ?
Click to expand...
Click to collapse

When trying to play Watch trailer videos error: 4104 pops up, even without root Magisk get the same error ... Can someone confirm ?

Re flash the recovery
You need to flash the recovery image file again to unroot it. I had same issue. I flash the recovery image and after that everything's working fine

This is how i got it to work
1. Install latest magisk and manager
2. Hide magisk manager using a random name. I used some random numbers
3. Verify Safety net
4. Install tatasky app. If already installed, clear storage for the app
5. Hide tatasky in magisk manager
6. Use any file manager and rename the TWRP folder to something else
7. Profit
chaitut715 said:
I have renamed the Magisk package but it's still detecting root. My Jio app running successfully after renaming package but not Tata Sky. Pleas help me.
Click to expand...
Click to collapse
Isaac John said:
Hey I'm having the same problem, somehow the tatasky app detects root.
I have magisk, hide, repacked name, passed safetynet and can use banking apps with ease meh.
Click to expand...
Click to collapse
YK RAJ said:
It's still not hiding.. My device had passed safetynet check and hidden Tata Sky but still it's detecting Root.
Other banking apps even Yono Mobile, Gpay, PayTm all are working fine!
Click to expand...
Click to collapse
Step 6 is key here. Tatasky has additional check for TWRP

Just rename the TWRP folder
juliusedward said:
Those is how i got it to work
1. Install latest magisk and manager
2. Hide magisk manager using a random name. I used some random numbers
3. Verify Safety net
4. Install tatasky app. If already installed, clear storage for the app
5. Hide tatasky in magisk manager
6. Use any file manager and rename the TWRP folder to something else
7. Profit
Step 6 is key here. Tatasky has an
additional check for TWRP
Click to expand...
Click to collapse
Yeah, I didn't mention but that day I'd found the solution from somewhere Just to rename the TWRP folder, and then it was working.
So, thanks anyway, and Yes the only 6th steps are required to do if your banking apps are already working fine.

chaitut715 said:
I have renamed the Magisk package but it's still detecting root. My Jio app running successfully after renaming package but not Tata Sky. Pleas help me.
Click to expand...
Click to collapse
how do I rename Magisk package ? Should I do it after the firestick is booted or in recovery mode.

sjude68 said:
how do I rename Magisk package ? Should I do it after the firestick is booted or in recovery mode.
Click to expand...
Click to collapse
In the app settings.

Didgeridoohan said:
In the app settings.
Click to expand...
Click to collapse
Thanks. I renamed the Magisk app to a number.
I am stuck in an state where I cannot use the firestick for anything. I did the following.
adb reboot recovery
In recovery console I did the following.
adb shell
twrp wipe data
twrp wipe cache
twrp wipe dalvik
twrp wipe /system
twrp install /sdcard/ftvs2k-5.2.7.7.zip
twrp install /sdcard/Amazon_Launcher_Replacement.zip
twrp install /sdcard/TWRPtestDelALandOOBE.zip
twrp install /sdcard/Magisk-v20.1.zip
twrp reboot
The firestick got booted as normal and I could open the Magisk Manager and rename it.
But now I cannot install anything on to it. The apps that are showing on the screen are PrimeVideo, Amazonmusic,AmazonPhotos, appstore, etc. but none of them are opening. I cannot see Youtube, Netflix etc. The launcher has been replaced so no Tatasky app to be seen.
Adb cconnection from Mobile App is working and I can accept the adb from the firestick.
I installed Hotstar using EasyFireTools. But when I Launch it, it asked me to sign to Amazon account. I cannot signin to Amazon. No errors popups.

@sjude68 Sounds like you need to find a Firestick thread/forum to ask for help...

....

juliusedward said:
Those is how i got it to work
1. Install latest magisk and manager
2. Hide magisk manager using a random name. I used some random numbers
3. Verify Safety net
4. Install tatasky app. If already installed, clear storage for the app
5. Hide tatasky in magisk manager
6. Use any file manager and rename the TWRP folder to something else
7. Profit
Step 6 is key here. Tatasky has additional check for TWRP
Click to expand...
Click to collapse
Man... Thank you!
Saved my day.
I wanted to watch the MotoGP live, but my family are watching a movie rn on the T.V.
So decided to stream via TataSky app on phone but it was detecting magisk root. And only this method allowed me to access the application.

juliusedward said:
This is how i got it to work
1. Install latest magisk and manager
2. Hide magisk manager using a random name. I used some random numbers
3. Verify Safety net
4. Install tatasky app. If already installed, clear storage for the app
5. Hide tatasky in magisk manager
6. Use any file manager and rename the TWRP folder to something else
7. Profit
Step 6 is key here. Tatasky has additional check for TWRP
Click to expand...
Click to collapse
How to rename TWRP folder? Follow up question, I am unable to find the TWRP folder in my device!. Is it because i had switched my recovery to Orange Fox from TWRP?
Please help as I too facing the same issue with only TataSky app but rest of the apps including banking apps are working fine and not detecting the root.

Manjunath T said:
How to rename TWRP folder? Follow up question, I am unable to find the TWRP folder in my device!. Is it because i had switched my recovery to Orange Fox from TWRP?
Please help as I too facing the same issue with only TataSky app but rest of the apps including banking apps are working fine and not detecting the root.
Click to expand...
Click to collapse
Use any file explorer. I use solid explorer. Look for a folder TWRP in /sdcard. If it's there, just delete it

juliusedward said:
Use any file explorer. I use solid explorer. Look for a folder TWRP in /sdcard. If it's there, just delete it
Click to expand...
Click to collapse
Actually I didn't find any folder of TWRP when I searched for it using MT File Explorer but I did find TWRP image file in my sd card which I had used to flash recovery long back, I deleted that as I had no use now, I checked the app after deleting that and voila it didn't detect Thanks

YK RAJ said:
Just rename the TWRP folder
Yeah, I didn't mention but that day I'd found the solution from somewhere Just to rename the TWRP folder, and then it was working.
So, thanks anyway, and Yes the only 6th steps are required to do if your banking apps are already working fine.
Click to expand...
Click to collapse
It worked now