Viper4Arise
This is a universal flashable zip for viper4arise / viper4andoird and will require your device to be running Magisk for this to work.
This is the latest build of the viper4arise.apk + the 2.5.0.4 Drivers (packed by topjohnwu )
What this flashable zip includes:
Code:
*Viper4Arise.Apk
*Viper4Android Drivers ( Requires a Magisk Rom) V 2.5.0.4 but topjohnwu mislabeled as 2.5.0.5
*Viper4Arise - Profiles
*Viper4Arise - DDC
*Viper4Arise - Kernel
Just go ahead and flash this via TWRP and re-boot, you should now have a Viper-app The Magisk module and all the profiles ready to go and no additional setup needed.
Credits go to @topjohnwu and the Arise team that made all this happen, just a easy zip of the stuff for anyone who has had trouble doing the work manually.
Download Link :
https://www.androidfilehost.com/?fid=529152257862713236
sources:
Viper4Arise:
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Magisk:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
No mirrors found on download.. Gonna keep trying
---------- Post added at 02:47 AM ---------- Previous post was at 02:40 AM ----------
storm68 said:
No mirrors found on download.. Gonna keep trying
Click to expand...
Click to collapse
Tried it. File downloaded as corrupt
storm68 said:
No mirrors found on download.. Gonna keep trying
---------- Post added at 02:47 AM ---------- Previous post was at 02:40 AM ----------
Tried it. File downloaded as corrupt
Click to expand...
Click to collapse
If you feel like it, you can extract the zip and then re-zip it. The contents are fine, but the zip itself isn't working.
uploaded the wrong zip. sorry guys
correct link is updated in OP, The zip should be ViperAllinONE.zip
again my fault, i uploaded the drivers only zip that was faulty lol
No mirrors found again.... Very weird.
storm68 said:
No mirrors found again.... Very weird.
Click to expand...
Click to collapse
androidfilehost is having problems i just kept trying till they showed up
jerrycoffman45 said:
androidfilehost is having problems i just kept trying till they showed up
Click to expand...
Click to collapse
Got it!
---------- Post added at 11:46 PM ---------- Previous post was at 11:04 PM ----------
You said magisk module? I don't see any in magisk. Am I doing something wrong... Everything else is fine.
storm68 said:
Got it!
---------- Post added at 11:46 PM ---------- Previous post was at 11:04 PM ----------
You said magisk module? I don't see any in magisk. Am I doing something wrong... Everything else is fine.
Click to expand...
Click to collapse
you have to be on a Magisk rom, or flash Magisk version 11.6 from its thread to use this, as i relys on Magisk for the drivers to be installed.
Viper4Arise's packages are flash-able as is without Magisk, but for myself and LS997 handset they caused issues, required selinux set to permissive, and it would seem like it would get randomly disabled after a song change and being very un-reliable. The app, the profiles the kernel and ddc all come from my zip the magisk part is not included with this mod.
storm68 said:
Got it!
---------- Post added at 11:46 PM ---------- Previous post was at 11:04 PM ----------
You said magisk module? I don't see any in magisk. Am I doing something wrong... Everything else is fine.
Click to expand...
Click to collapse
you have to be on a Magisk rom, or flash Magisk version 11.6 from its thread to use this, as i relys on Magisk for the drivers to be installed.
Viper4Arise's packages are flash-able as is without Magisk, but for myself and LS997 handset they caused issues, required selinux set to permissive, and it would seem like it would get randomly disabled after a song change and being very un-reliable. The app, the profiles the kernel and ddc all come from my zip the magisk part is not included with this mod.
Magisk can be found here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
should be able to flash it overtop of any rom and it work fine, if you have superuser it will use it as the root method, if you have nothing it will root your phone and provide magisksu for root management. Magisksu is considered fully system-less root, where supersu is a system modification, Supersu changed ownership late last year and is now owned by a Company and not a XDA dev and seems to be becoming a OLD root method. Magisk has been named the new root method by many as it can pass safety-net checks, provide root and work with almost all the current root stuff, but done a slighly diffrent way. Some old root apps may have issues with system-less and thats on the app devs to get their apps updated to support 2017 root methods.
Team DevDigitel said:
you have to be on a Magisk rom, or flash Magisk version 11.6 from its thread to use this, as i relys on Magisk for the drivers to be installed.
Viper4Arise's packages are flash-able as is without Magisk, but for myself and LS997 handset they caused issues, required selinux set to permissive, and it would seem like it would get randomly disabled after a song change and being very un-reliable. The app, the profiles the kernel and ddc all come from my zip the magisk part is not included with this mod.
Magisk can be found here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
should be able to flash it overtop of any rom and it work fine, if you have superuser it will use it as the root method, if you have nothing it will root your phone and provide magisksu for root management. Magisksu is considered fully system-less root, where supersu is a system modification, Supersu changed ownership late last year and is now owned by a Company and not a XDA dev and seems to be becoming a OLD root method. Magisk has been named the new root method by many as it can pass safety-net checks, provide root and work with almost all the current root stuff, but done a slighly diffrent way. Some old root apps may have issues with system-less and thats on the app devs to get their apps updated to support 2017 root methods.
Click to expand...
Click to collapse
Great info. Thanks
I flashed this, but Viper isn't processing
aaronfrickinaustin said:
I flashed this, but Viper isn't processing
Click to expand...
Click to collapse
Yep, same issue as the original magisk port. I have to use a combination of the old system install zip and this module to get viper to process audio. Probably because there are a bunch of audio conf files missing from the ported version.
Florian:
I have a LG G7 and have flashed the last version of viper4arise. Now I have the problem that the drivers are indeed active, but it comes only disturbing noises. as if you connect a plug incorrectly in a system.
the magisk modules do not sound good to me. That sounds like you're constantly switching between loud and quiet. So like constant fluctuations
Related
My phone was working fine until this morning when I tried to start wifitether and got the message "no SU binary installed" Does this mean I lost root somehow and have to root it again?
ilogik said:
My phone was working fine until this morning when I tried to start wifitether and got the message "no SU binary installed" Does this mean I lost root somehow and have to root it again?
Click to expand...
Click to collapse
Its possible that you removed root permissions solely for wifitether by accident. Uninstall and reinstall then when it fires up make sure you select allow when superuser popup comes on. If you know your way around you can avoid the uninstall by simply going into superuser app and fixing permissions for wifi tether. If not then you'll need to boot into recovery and reflash supersu as you did during the original root process.
hope this helps!
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
ilogik said:
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
Click to expand...
Click to collapse
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
jonesin said:
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
Click to expand...
Click to collapse
Also if you have difficulties removing it then you may have to use tibu to freeze then uninstall SuperSU. If that doesnt work your only option will be ADB, it may just uninstall fine it may not it depends. But you need to get rid of it.
ilogik said:
When I open superSU it tells me there is no SU binary and SuperSU cannot install it.
Click to expand...
Click to collapse
I was having issues like this. I had to swap between supersu and superuser. But it just never worked right. Once I flashed a new Rom it worked just fine.
sent from my rooted DNA
jonesin said:
Ok thats your first problem. you should NOT be using SuperSU app, its not compatible with the SU binaries we have installed on this phone. Until further notice this app is NOT compatible and wont be supported. Do to the binaries we used during the root process you must use the "superuser" app from the market. Some people have hacked in different binaries but unless it is specified that SuperSU is compatible then always is superuser.:angel:
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
Also if you have difficulties removing it then you may have to use tibu to freeze then uninstall SuperSU. If that doesnt work your only option will be ADB, it may just uninstall fine it may not it depends. But you need to get rid of it.
Click to expand...
Click to collapse
Given the phone is S-On the only real way to ensure a permanent, functional root on stock would be to first remove the SuperSU binary and app. It has been confirmed that SuperSU does not work.
This can be done directly from TWRP's file manager or ADB with the unsecured kernel:
The binary can be found at: /system/xbin/su
And the app can be found at: /system/app/superuser.apk
BOTH FILES must be removed. Freezing SuperSU will not work
Next download and then flash the following zip in TWRP or CWM:
Superuser Binary+App
At this point you should have fully functional root on stock
S121Guy said:
I was having issues like this. I had to swap between supersu and superuser. But it just never worked right. Once I flashed a new Rom it worked just fine.
sent from my rooted DNA
Click to expand...
Click to collapse
Again, simply flashing Superuser over SuperSU will not work, the app and binary must be removed before flashing.
Jarocks said:
Given the phone is S-On the only real way to ensure a permanent, functional root on stock would be to first remove the SuperSU binary and app.
This can be done directly from TWRP's file manager or ADB with the unsecured kernel:
The binary can be found at: /system/xbin/su
And the app can be found at: /system/app/superuser.apk
BOTH MUST be removed to avoid any issues
Next download and flash the following zip in TWRP or CWM:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
At this point you should have fully functional root on stock
Click to expand...
Click to collapse
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
jonesin said:
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
You need the binaries and the app to get root perm on anything from within the rom. I don't recommend this.
Sent from my HTC6435LVW using Tapatalk 2
jonesin said:
Your methods will remove the ability to provide root permissions to any apps...?
Sent from my HTC6435LVW using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------
You need the binaries and the app to get root perm on anything from within the rom. I don't recommend this.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The zip contains both the superuser app and corresponding su binary.
Jarocks said:
The zip contains both the superuser app and corresponding su binary.
Click to expand...
Click to collapse
I overlooked the zip portion of your comment. I thought that you were saying to simply remove the app and the binary and reboot. However the binaries wont load from SuperSU in the first place so you should eb good to just get rid of SuperSU and install superuser. If everyone has been following the recommended rooting steps that is. But if that were the case noone would be installing SuperSU
My system folder only contains /bin and nothing else. is there another system folder I should be in?
ilogik said:
My system folder only contains /bin and nothing else. is there another system folder I should be in?
Click to expand...
Click to collapse
are you in adb or are you using a file explorer?
TWRP file explorer
I'm having the same issue-- in TWRP file manager I see only system/bin. If I try to delete the files with adb it complains about a read-only filesystem.
droidmark said:
I'm having the same issue-- in TWRP file manager I see only system/bin. If I try to delete the files with adb it complains about a read-only filesystem.
Click to expand...
Click to collapse
I know this is an old thread but if it helps others, I had the same issue with TWRP, there is an option in SuperSu to unistall and switch to a another superuser app. Put the superuser zip above on the phones memory card, then just install regular superuser from the market. Now go into SuperSu and pick the option to switch to another app, once done go into file explorer and delete the files stated above if they are there. Now reboot into recovery & flash the new superuser zip..
That's very helpful information. Somehow I solved it back in December but I don' know how!
Samsung Galaxy Tab A 7.0 LTE/WIFI 2016 TINKER EDITION ROM (DEOXED/ROOT/XPOSED)
============================================
Update 01/04/2017
-----------------------
Tinker Edition V5.1 is now out.
* Re-added Samsung stock camera and gallery
* revert back to stock vold to fix issues people are having with micro sdcards
Now available for the SM-T285, SM-T280 to follow
Update 10/29/2016
------------------------
TWRP for the SM-T285 here
Early Build of TWRP for the T285 (see post by @ashyx will update this if an official version is released. The T280 version should be available not far behind I believe
Update 09/21/2016
-----------------------
V5 now out (root, deodexed, xposed) for the SM-T280/T285, still working on the SM-T280
Update 09/20/2016
------------------------
Turns out this device is not as locked as we all thought it too be. See thread below for my ordeal and more details:
http://forum.xda-developers.com/galaxy-tab-a/help/resources-samsung-galaxy-tab-7-0-2016-t3431022
Modifications:
===========
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Busybox
* Hijacked Vold (using CM 12.1 sources) to run shell scripts stored in /data/scripts/vold.init
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
* Dolby Atmos mod (09/11/2016) (thanks to @Nando14sunny)
* Deodexed/Xposed (09/13/2016) (thanks to @wanam and @rovo89)
* soft linked /etc/hosts to /data/scripts/hosts and can be edited using adb shell (09/13/2016) (thanks to @venomrat)
* V5: root chainfire's SuperSu 2.78 (09/21/2016) (thanks to @Chainfire)
* stock boot animation
Special thanks also to @ashyx for initially taking a look at this device , I haven't given up on rooting this device yet.
Special thanks to @klemen241 for helping me try out the SM-T280 build
Haven't done extensive testing on Xposed modules, but the pokemon go iv mod/hacked worked and that was good enough for me (Before pokemon Go was patched). If you use this ROM feedback is highly appreciated
NOTES: To be safe, perform a cache wipe using recovery. I didn't need to do this personally but I haven't tested all use cases
NOTES: Since this rom is deodexed, the first boot will take quite a while, so please be patient .
NOTES: if you are coming from V2 and are using the mount_ext4 apps2sd scripts please update it for additional support for the V3 ROM HERE:
https://github.com/jedld/smt285_data_scripts
NOTES: (09/13/2016) Unfortunately, the V3 build fails the Google SafetyNet check, will be a problem if you play Pokemon Go
Other Notes: Removed support for zygote.init scripts in V3 as I am now using the app_process32_xposed binary, will work to get this back soon. I haven't had a need for zygote scripts though. The vold.init scripts shoud still work as before if you are using the apps2sd script
Installation Instructions:
Odin or Heimdall Required. I you are coming from the Stock Rom please wipe/factory reset to be sure. If you are upgrading from V1 or V2 you are not required to wipe unless there are problems. If you are upgrading to V3 cache wipe is recommended using recovery.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Choose the appropriate download for the model (wifi only T280/ lte T285) that you have:
WIFI ONLY Download (SM-T280)
==========================
Link (V5 Deodexed, Rooted and Xposed):
https://mega.nz/#!0Jdg0a4D!XWLES1BwCPrkBlUzqNhRfRi_91LOdawYHydQ_scV2dI
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
LTE Version Downloads (SM-T285)
===========================
Link (V5.1 Deodexed, Rooted and Xposed):
https://mega.nz/#!ZFFTFKYZ!NAeajNUjIgYI7zOslpWoJ2AeJ-NCKG0Ut8Buz_6eCgU
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
Link (Original V2 odexed version):
Download from Mega (V2 09/11/2016)
If you have suggestions, send me a PM.
Other Notes (So people don't have to ask):
* I've tried to run superuser daemonsu, but unfortunately the sepolicy scopes for vold and zygote are too narrow in this device for supersu to use despite being root. In theory a version of daemonsu can be made specifically to run on this device with a somewhat castrated functionality though I don't have access to the source code to figure it out. Navigating the sepolicy landmine is hard.
WIFI ISSUES
=========
There are reports of wifi problems with the latest build due to wrong permissions with dhcp hooks, if so you can do the following (big thanks to @_mone):
Using adb shell:
Code:
su
mount -o rw,remount,rw /system
chmod 755 /system/etc/dhcpcd/dhcpcd-run-hooks
mount -o ro,remount,ro /system
/system is readonly by default, which is why you need the remount commands. Reboot your device after just to make sure.
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
venomrat said:
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
Click to expand...
Click to collapse
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
jedld said:
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
Click to expand...
Click to collapse
Thanks for your hard work. It's a pity this device is not as popular as their other models or more people would have already signed the petition.
I regret not doing more research before buying this tablet.
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Nando14sunny said:
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Click to expand...
Click to collapse
we could try, could you point me to a rom that has the specified libraries for Dolby?
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Nando14sunny said:
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Click to expand...
Click to collapse
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
jedld said:
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
Click to expand...
Click to collapse
Wow thank you! I'll test it right now
Edit:
It works like a charm! You really improved my devie with it!
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
venomrat said:
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
Click to expand...
Click to collapse
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
jedld said:
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
Click to expand...
Click to collapse
No hurry. I can wait. What you are doing now is more important. :good:
venomrat said:
No hurry. I can wait. What you are doing now is more important. :good:
Click to expand...
Click to collapse
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
corzradio said:
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
Click to expand...
Click to collapse
May need to modify build.prop, you may do this yourself here:
http://forum.xda-developers.com/galaxy-tab-a/how-to/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
Also there may be an Xposed framework modules that do that. Not sure though since I'm ok with the stock DPI
jedld said:
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
Click to expand...
Click to collapse
Thanks. Will need to find time to re-flash this weekend.
Regarding xposed have you actually tested any other modules that need root?
I already built a rom with xposed but it was all but useless because pretty much all the modules I use need root.
most of those I tried don't need root so far (youtube adaway, pokemon go iv). Haven't tried those that need root but I suppose those wouldn't work.
I use app settings and it works for dpi change, and you are welcome. I am glad to test stuff, its fun haha. If anyone has questions about t280 you can ask me
how can i boost the volume? since its not rooted i cant find the mixer.xml
Hi,
I am Using LAVA A97 device recently launched. I need to root this mobile to apply some tweaks. I tried various methods like flashing the zip from the SD card and sideload. The error I got always is "Signature Verification Failed". I tried finding custom recoveries and even tried porting custom recoveries but all stopped at the boot image.
Please help me to root this device or port me a custom recovery. I will provide you the files you needed.
Have you tried enabling OEM bootloader setting in developer options?
vshlkmr said:
Have you tried enabling OEM bootloader setting in developer options?
Click to expand...
Click to collapse
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Please tell me the procedure to add su files in marshmallow system.img and flash it
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
karljsamuel said:
Please tell me the procedure to add su files in marshmallow system.img and flash it
Click to expand...
Click to collapse
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
I tried the above mentioned steps in my Ubuntu 16.04 with Android Kitchen and Superr's Kitchen. With Android kitchen, I unpacked the system.img and the kitchen made the boot image and made the ro.secure=0. Then I added the necessory files from @Chainfire SuperSU.zip as per the update-binary script mentioned and repacked system.img with Superr's Kitchen. When I flashed modified system.img and boot.img with flash tool.
The superSU app said that su binaries are not installed and it cant install them also it asked me to reroot the mobile phone.
I also tried with Dirtycow exploit also but not worked.
Mobile is running Marshmallow API 23
Can you make me a custom recovery. I followed the steps mentioned in this forum to port a custom recovery but it struck in the boot logo.
The Stock Firmware file Now I have in my mobile can be downloded from Google Drive.
Boot.img Recovery.img and build.prop file is uploaded as Zip to Google Drive
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
vshlkmr said:
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
Click to expand...
Click to collapse
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
karljsamuel said:
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
Click to expand...
Click to collapse
Is USB debugging enabled?? Also switch the phone to cd rom and install the drivers
While installing the modified system.img it give me error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Even there is no such file in the stock rom. only a file named sh0 was present
I reflashed the rom and adb shell is working properly without the /system/bin/sh file
How to root lava a97
Hey bro I read your thread and also I myself tried many ways to root my lava a97
Did u got any method to root it??
Please tell
karljsamuel said:
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Click to expand...
Click to collapse
Lava A97 is CortexA7 device
use fastboot tools to flash TWRP and then flash SuperSU.zip
I'm gonna port TWRP for Lava A97 soon
And will test it.
pm me and I'll give you TWRP after success in testing
OK?
---------- Post added at 09:40 AM ---------- Previous post was at 09:35 AM ----------
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
Thanks alot bro???
TWRP port test failed
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Can anyone Provide me the recovery & Su files Please?
---------- Post added at 04:42 AM ---------- Previous post was at 04:40 AM ----------
Mrutunjaya said:
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Click to expand...
Click to collapse
I Also Want 2 Root My Device Please Can U Help Me?
I recently bought this new chinese phone ( out from 3 months, android 7.0 ) but after many hours i still was not able to root this, tried all 1click junk and nothing worked, tried PC apps.. followed many guides, nothing worked.
I would like at least to install TWRP, but of course, device is not supported, and i dont know where to get proper IMG file for my phone.
any help would be appreciated.. thanks
Edit: Tried Mtk tools, since its a mt6580, it does detect phone but there are errors,
TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64
Uknown rom structure, backup not possible
innersphere1 said:
I recently bought this new chinese phone ( out from 3 months, android 7.0 ) but after many hours i still was not able to root this, tried all 1click junk and nothing worked, tried PC apps.. followed many guides, nothing worked.
I would like at least to install TWRP, but of course, device is not supported, and i dont know where to get proper IMG file for my phone.
any help would be appreciated.. thanks
Edit: Tried Mtk tools, since its a mt6580, it does detect phone but there are errors,
TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64
Uknown rom structure, backup not possible
Click to expand...
Click to collapse
no way to root this??
Hi, I also just aquired the allcall rio.
Can you help me out with a few things,
1. does the back come off in order to reach the battery?
2. on a normal phone pressing the middle button normally gains you access into the app menu, for some reason i can only access the home screen with the apps being accessed by sliding the home screen to multi home screens, is this normal?
3. have you rooted your phone and if so can you leadme to where you done this?
I like the phone, just wondering whether what iv stated are normal features or a fault with mine
Thanks in advance for any help / info
Cheers
Rooted / ish
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
Hey,
I have not found a root method but iv found a way to access all sysytem files and folders.
Go to app store and download ROOT BROWSER by JRummy Apps.
Open the app once installed and it will ask you to download files to make it work, it downloads quickly from inside the app.
When its finished you can then access the phones root files as tho your phone was rooted.
Its better than nothing for now and im sure there would be a way to insert the nesscerry files for rooting into the correct folders.
Hope it works for you
ronyon78 said:
Hey,
I have not found a root method but iv found a way to access all sysytem files and folders.
Go to app store and download ROOT BROWSER by JRummy Apps.
Open the app once installed and it will ask you to download files to make it work, it downloads quickly from inside the app.
When its finished you can then access the phones root files as tho your phone was rooted.
Its better than nothing for now and im sure there would be a way to insert the nesscerry files for rooting into the correct folders.
Hope it works for you
Click to expand...
Click to collapse
So can you modify files in /system with ROOT BROWSER?
---------- Post added at 07:51 AM ---------- Previous post was at 07:26 AM ----------
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
SP flash to flash a custom TWRP recovery .
I have ported one recovery image from TWRP 3.0.0-0 for Tecno W4 using carliv image kitchen. And it works like charm.
I would put the link up If I could, but right now I still need to make a few more posts to gain the privilege .
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
Hi again, I've found the better way to get root using Magisk, available here in XDA.
first download the 0808 firmware from allcall's official website and flash it with SP flash.
wireless upgrade to 20170819, unlike 0728 and 0808, this version has remove all bloatware and malware
take boot.img from the firmware folder and put it to phone storage
install Magisk Manager v5.3, hit install, patch the boot image.
copy the patched boot.img to PC and SP flash it. (no need to unlock bootloader)
done!
everything for allcall rio
ALLCALL RIO- SOFTWARE+TWRP+PHILZ+SUPER SU+FLASH TOOL+SN WRITE TOOL needrom download success:good:
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
AllCall-RIOWCDMA-1GB+16GB-7.0-20171207 by radu13
ciroradu said:
ALLCALL RIO- SOFTWARE+TWRP+PHILZ+SUPER SU+FLASH TOOL+SN WRITE TOOL needrom download success:good:
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
AllCall-RIOWCDMA-1GB+16GB-7.0-20171207 by radu13
Click to expand...
Click to collapse
Can you help me rooting my allcall rio I just can't tryied every root apk and pc softwares
Hello everyone, I have a problem on which audio enhancement to use? I tried to install Viper4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk, but it does not install the necessary drivers, my problem is that I use Spotify and the sound is very simple, I would need to strengthen the bass a little bit, I have the B&O headphones.
Thanks
the best audio package by far is A.R.I.S.E.
I use magisk, but it should work with SuperSU too.
You need to have busybox installed to /system/xbin for Viper4Arise to work properly.
When you flash the ARISE package the first time, it will drop a file "arise_customize.conf" into /sdcard
This is what you use to customize which ARISE modules you want to be installed when you flash the ARISE installer the second time.
I have attached the arise_customize.conf file that I use, and know works very well on LG-V20.
For many reasons, though, I recommend looking into switching to magisk over supersu.
After you have busybox installed properly, and after you have Viper4ARISE flashed properly with the customize file used, there is a module in the magisk app repository "universal_deep_buffer_remover".. this is the ONLY thing I have found that correctly removes the deep buffer without breaking the HIFI dac on the V20.
(you can also easily install busybox from the magisk manager app too, although I recommend flashing that module from recovery first. You may need to play with that its triicky. Install from recovery and/or from within the magisk manager app.)
it should go without saying that before you start installing this you will need to remove any other audio mods that you have installed previously, or the best bet being reflash your ROM to get a fresh start.
syndre said:
the best audio package by far is A.R.I.S.E.
I use magisk, but it should work with SuperSU too.
You need to have busybox installed to /system/xbin for Viper4Arise to work properly.
When you flash the ARISE package the first time, it will drop a file "arise_customize.conf" into /sdcard
This is what you use to customize which ARISE modules you want to be installed when you flash the ARISE installer the second time.
I have attached the arise_customize.conf file that I use, and know works very well on LG-V20.
For many reasons, though, I recommend looking into switching to magisk over supersu.
After you have busybox installed properly, and after you have Viper4ARISE flashed properly with the customize file used, there is a module in the magisk app repository "universal_deep_buffer_remover".. this is the ONLY thing I have found that correctly removes the deep buffer without breaking the HIFI dac on the V20.
(you can also easily install busybox from the magisk manager app too, although I recommend flashing that module from recovery first. You may need to play with that its triicky. Install from recovery and/or from within the magisk manager app.)
it should go without saying that before you start installing this you will need to remove any other audio mods that you have installed previously, or the best bet being reflash your ROM to get a fresh start.
Click to expand...
Click to collapse
You forgot to attach the file
Looking forward to it, I've always used Viper and never heard of this one, I'm eager to try it.
UL7RA said:
You forgot to attach the file
Looking forward to it, I've always used Viper and never heard of this one, I'm eager to try it.
Click to expand...
Click to collapse
so sorry, my fault
I did attach the file but I didn't see that it rejected the .prop extension, I edited that first post with it uploaded as a text file, same file is attached here too. Remove the .txt and put it on /sdcard
If you open the file and change the install core to =true, you will only have to flash the arise zip once (instead of letting it place that customize.prop file on SD card the first time around).
syndre said:
so sorry, my fault
I did attach the file but I didn't see that it rejected the .prop extension, I edited that first post with it uploaded as a text file, same file is attached here too. Remove the .txt and put it on /sdcard
If you open the file and change the install core to =true, you will only have to flash the arise zip once (instead of letting it place that customize.prop file on SD card the first time around).
Click to expand...
Click to collapse
Unfortunately, I believe not much of ARISE works on my H990DS, as the first time I flashed using your prop file, I got arkamys audio to continuously force close. Uninstalled it by editing the prop file, reboot. Tried opening Dolby Atmos, force close. I guess I'm left with Viper, which I've had before anyway. I'm on magisk, if that matters, but I saw that the magisk compatibility was set to true.
UL7RA said:
Unfortunately, I believe not much of ARISE works on my H990DS, as the first time I flashed using your prop file, I got arkamys audio to continuously force close. Uninstalled it by editing the prop file, reboot. Tried opening Dolby Atmos, force close. I guess I'm left with Viper, which I've had before anyway. I'm on magisk, if that matters, but I saw that the magisk compatibility was set to true.
Click to expand...
Click to collapse
If you're using SuperSU the only other thing that I could think of would be making sure BusyBox is installed
In the future if something like that is force closing you can either just freeze the application or delete the app folder in system partition using recovery.
If you haven't yet tried flashing your ROM again, letting boot up and sit for a few minutes, then flash busybox and arise again on a fresh ROM installation, that is definitely something to try.
I'm just curious, is there a reason why you prefer SuperSU over magisk?
I use the BusyBox flashable installer made by as from here. He's got lots of other neat things on that thread to!
https://forum.xda-developers.com/showthread.php?t=2239421
Sent from my LG V20 using XDA Labs
syndre said:
If you're using SuperSU the only other thing that I could think of would be making sure BusyBox is installed
In the future if something like that is force closing you can either just freeze the application or delete the app folder in system partition using recovery.
If you haven't yet tried flashing your ROM again, letting boot up and sit for a few minutes, then flash busybox and arise again on a fresh ROM installation, that is definitely something to try.
I'm just curious, is there a reason why you prefer SuperSU over magisk?
I use the BusyBox flashable installer made by as from here. He's got lots of other neat things on that thread to!
https://forum.xda-developers.com/showthread.php?t=2239421
Sent from my LG V20 using XDA Labs
Click to expand...
Click to collapse
No, I'm not using SuperSU, I'm on Magisk (14.0). You might have missed when I said that. BusyBox is installed and running fine, and I managed to fix everything by flashing the ARISE zip, but with a modified prop file.
UL7RA said:
No, I'm not using SuperSU, I'm on Magisk (14.0). You might have missed when I said that. BusyBox is installed and running fine, and I managed to fix everything by flashing the ARISE zip, but with a modified prop file.
Click to expand...
Click to collapse
ahh ok, yeah misunderstood that you got it going
great
Sent from my LG V20 using XDA Labs
Hello, thanks for replying ... I installed my system again with MagiskSU, but when I installed ARISE, I could not understand how to install it ... I downloaded the MAGNUS OPUS package and tried to flash with the TWP, and there was ERROR 1, I put both your "arise_customize.prop" in my sdcard (/sdcard/arise_customize.prop) and what is in the ARISE forum, but without success ...
let's go to the beginning ... first I install MagiskSU, then BusyBox, then I put the file on sdcard? and then try to install? that's what i did
what am I doing wrong?
Thanks for the cooperation
pkrename said:
Hello, thanks for replying ... I installed my system again with MagiskSU, but when I installed ARISE, I could not understand how to install it ... I downloaded the MAGNUS OPUS package and tried to flash with the TWP, and there was ERROR 1, I put both your "arise_customize.prop" in my sdcard (/sdcard/arise_customize.prop) and what is in the ARISE forum, but without success ...
let's go to the beginning ... first I install MagiskSU, then BusyBox, then I put the file on sdcard? and then try to install? that's what i did
what am I doing wrong?
Thanks for the cooperation
Click to expand...
Click to collapse
The order I flash those things is first the ROM (if your ROM has any audio mods included as separate zips in the main rom zip, most modded stock roms do this, remove that. Either delete any viper or dolby zips from the main rom zip, or comment out the libes that install them in the update-script FIRST).
Second I flash busybox, it should say "installng to /system/xbin".
Third I flash Magisk. The current latest version is v14.5 and I can confirm it works n my V20.
After that, I boot into the rom and let it up the stock audio configuration to and confirm that you have sound working initially. After it settles down for a few minutes, I go back into recovery and then flash the arise zip.
The first time you flash ARISE, it checks to see if the customize prop file is present on/ sdcard and if it is it will use those options. If the customize file is not present the only thing it will do is install the core part of ARISE, and it will place that customize.prop file onto /sdcard for you. If that happens you'll get a message saying so, instructing you to edit it to select which modules you want. The customize.prop file I attached is what I use, you don't necessarily have to use those exact settings, you can choose what you want and play around with it and see what works. Trial and error is a way of life doing these mods.
Flashing the same ARISE zip a second time once you edited the prop file to your liking will install what you choose instead of just the core files.
Reboot back into your ROM and open the magisk manager app. You'll notice there is a module there for ARISE compatibility. At this point your equalizer apps should be functioning, but only for local media files. To get the sound to process through the Viper equalizer using streaming music you need to remove the deep audio buffer. Magisk manager allows you to do this very easily by just downloading the universal deep audio remover module from the repository in magisk manager.
While you're at this point, it's a good idea to also download and install the BusyBox module from the magisk manager app too. You can install the magisk BusyBox module on top of what you already flashed in recovery, thats how I do it. If there's any conflicting files the magisk module takes priority. If anything, doing this gives me the peace of mind that BusyBox is for sure installed correctly.
After installing the BusyBox and deep buffer remover modules from the magisk manager app, reboot and that should be it! The only thing you need to do now to take your already amazing DAC to the next level is adjust the equalizer settings to what you like. This is a never ending quest to make whatever youre listening to sound perfect. Frustrating but fun at the same time.
Of course there are a ton of things that could go wrong, each case seems to be different, so there's no way to let you know what to do before a problem shows up.
Try that and let me know how it goes. Good Luck!
syndre said:
The order I flash those things is first the ROM (if your ROM has any audio mods included as separate zips in the main rom zip, most modded stock roms do this, remove that. Either delete any viper or dolby zips from the main rom zip, or comment out the libes that install them in the update-script FIRST).
Second I flash busybox, it should say "installng to /system/xbin".
Third I flash Magisk. The current latest version is v14.5 and I can confirm it works n my V20.
After that, I boot into the rom and let it up the stock audio configuration to and confirm that you have sound working initially. After it settles down for a few minutes, I go back into recovery and then flash the arise zip.
The first time you flash ARISE, it checks to see if the customize prop file is present on/ sdcard and if it is it will use those options. If the customize file is not present the only thing it will do is install the core part of ARISE, and it will place that customize.prop file onto /sdcard for you. If that happens you'll get a message saying so, instructing you to edit it to select which modules you want. The customize.prop file I attached is what I use, you don't necessarily have to use those exact settings, you can choose what you want and play around with it and see what works. Trial and error is a way of life doing these mods.
Flashing the same ARISE zip a second time once you edited the prop file to your liking will install what you choose instead of just the core files.
Reboot back into your ROM and open the magisk manager app. You'll notice there is a module there for ARISE compatibility. At this point your equalizer apps should be functioning, but only for local media files. To get the sound to process through the Viper equalizer using streaming music you need to remove the deep audio buffer. Magisk manager allows you to do this very easily by just downloading the universal deep audio remover module from the repository in magisk manager.
While you're at this point, it's a good idea to also download and install the BusyBox module from the magisk manager app too. You can install the magisk BusyBox module on top of what you already flashed in recovery, thats how I do it. If there's any conflicting files the magisk module takes priority. If anything, doing this gives me the peace of mind that BusyBox is for sure installed correctly.
After installing the BusyBox and deep buffer remover modules from the magisk manager app, reboot and that should be it! The only thing you need to do now to take your already amazing DAC to the next level is adjust the equalizer settings to what you like. This is a never ending quest to make whatever youre listening to sound perfect. Frustrating but fun at the same time.
Of course there are a ton of things that could go wrong, each case seems to be different, so there's no way to let you know what to do before a problem shows up.
Try that and let me know how it goes. Good Luck!
Click to expand...
Click to collapse
Great Tutorial... but... in my phone... (H990DS) with custom root by DirtySanta, the Magisk v14.5 make this device no boot... does it work with version 14.0?
I have a LS997 and also see dirty santa. I run Schwifty's kernel, if that is of any interest to you.
Yes, v14 will be fine to use.
This is for anyone doing audio mods, check out sauron ainur audio, it's a Russian team that figured out a new/better way to mod devices,, (any variant) I've tried bout everything, and it is way better than arise, guitarded hero even chimed in on the forum and credited them as the real deal and not a poser basically, the bass is much tighter and puncher and tunable, must have magisk and u can have other mods along with it e.g.--v4a, James dsp, Arkamys, Dirac, etc. Read the thread!!! And it's easier to install. It will/is change android modding imo.
I was able to do it, but I only managed to release it on my device after upgrading to version 14.5... in version 14 it did not run... I did all the steps as it happened in my tutorial and now it is running the perfect V4A !! Thank you syndre was a great help!
I used to think arise was best, all magisk users should try sauron ainur audio mod, the only one I got to activate is the mk II beta 8. Easy to install if you follow directions and can use viper and other mods with it, they found a new way to do audio mods that's changing the game for audio it just ain't well known yet, read the thread, guitarded hero chimes in and validates them as the real deal and I can say it is awesome, tighter bass, clearer w/less congestion from non working/compatible ports. Message me if you need help or have general questions. Can be tricky to learn, (me anyway since I just started using magisk). Russian team I believe, try it out, good luck.
---------- Post added at 01:40 AM ---------- Previous post was at 01:34 AM ----------
Beta 8 was only one i could get to activate quad dac, wanted to correct that, but the versions without dac activated still sound better than other mods with dac working, it's that good. Imo the bass is way more tunable and precise, and punchier which is important to me.