Ok i did manage to root lollipop but now im having issues installing viper4android. How do i install viper4android? Never had issues with that untill now.
http://forum.xda-developers.com/showthread.php?p=64715727
This worked fine for me
Related
So Xposed has been doing me pretty well. Never had a problem until today.
Unfortunately, my most recent backup is right before I installed Xposed, and I've installed lots of apps and things since then, so I really dont wanna restore.
I installed the Xposed module, "Xposed Wallpaper" and it has rendered my phone useless. I was finally able to get into recovery and now I would like to remove the module. Is there a way to do this?
LG G2 - Sprint
CM11 Snapshot
TWRP recovery
Thanks!
Hello all!
I had root on Android 4.4.2 with VRUFNK4 build... It was all working fine but I wanted to get back to the NK1 kernel to see if that would fix some battery usage issues I was running into.
The root apps/modules I'm using are:
nomaptips
XPrivacy
Wanam Xposed (and Xposed framework)
Greenify
So I popped open Odin 3.09+, flashed the NK1 kernel and lost root. SO I flashed the NC1 kernel. Towelroot says it's successful, root checker is taking a bit of time to validate though. I think TR didn't actually work. So I flashed the NK1 kernel and my wanam mods are still working (I'm not going to try to change them).
What could I be doing wrong?
Does Root Checker PURELY verify when SU is properly updated...?
Thanks!
-Matt
So I
1. Unlocked the bootloader
2. Installed firmware 32.0.A.6.152 / R11B via Flashtool (using the built-in xperifirm, and CDA: 1298-5497)
3. rooted using the TWRP method,
4. installed xposed framework using XposedInstaller_3.0_alpha4.apk & framework xposed-v75-sdk22-arm64.zip
I've discovered my camera doesn't work properly - it launches, then crashes with "Unfortunately Camera has stopped". Strangely, the "AR Effect" app, which uses the camera, it works fine.
Could it have something to do with having xposed framework installed?
Is there way to reinstall just that camera app?
Any tips for the best way to diagnose?
Thanks
OK, I've tried factory reset (didn't work so I had to wipe from within TWRP), reflashed .152, re-rooted, and the camera is still working. Going to install all the same apps over the weekend, and test again before assuming something in xposed didn't play nicely
Same problem here but I use Google camera from Google play, and it's working very well
Same here. May we should wait for a modded camera.
I have found this bug is because of flashing the Xposed framework zip file via recovery. Uninstalling the zip via recovery using xposed-uninstaller-20151217-arm64.zip fixes the problem and you get the camera back but at the cost of losing Xposed and vice versa. Anyone got a working zip?
I was using E5823 Android 5.1.1 32.0.A.6.200 with xposed-v79-sdk22-arm64.zip (sdk23 said Android 6.0 only when flashing?) and Xposedinstaller_3.0_alpha4.apk
I've got this problem on the latest Marshmallow firmware for the Z5C. The camera FCs every few minutes when I have it open and even when I'm not moving the phone around. So far it continues even without installing xposed but I'm going to try running the phone completely stock with no root to see if rooting is the issue now. I wonder if there is any solution to this on Marshmallow.
i am also facing the same issue, pls help!!!
Hello everyone!
I share my experience installing and configuring VIPER4ANDROID in my BLU VIVO 5.
Before starting the phone must be rooted to this point use the following guide published on the Internet:
http://reviewroots.com/root-BLU-Vivo-5-with-or-without-pc
1) Install VIPER4ANDROID FX
http://forum.xda-developers.com/showthread.php?t=2191223
2) Download and install SELINUXMODECHANGER
http://forum.xda-developers.com/showthread.php?t=2524485
3) Open VIPER4ANDROID and install the driver
4) Open SELINUXMODECHANGER and change mode to Permissive
After these steps VIPER4ANDROID is ready to use
Screenshots please
Framaroot worked for you??? I had to return my first Blu Vivo 5 because it bootlooped after trying to install SuperSU over Kingroot with Framaroot. Besides, don't you need to flash Viper4android on a custom recovery? Which none are available for our phone that I know of.
al_bert7 said:
Framaroot worked for you??? I had to return my first Blu Vivo 5 because it bootlooped after trying to install SuperSU over Kingroot with Framaroot. Besides, don't you need to flash Viper4android on a custom recovery? Which none are available for our phone that I know of.
Click to expand...
Click to collapse
Really man? Oh, thanks. I was going to root this device with kingroot.
Chiclez said:
Really man? Oh, thanks. I was going to root this device with kingroot.
Click to expand...
Click to collapse
Alright, figured out what I did wrong. You can root using king root but do not check oem unlock in developer settings, that's what causes the bootloop. As for V4A I was able to get it to work with the instructions in the OP. But I didn't switch out king root for supersu out of fear of it bricking again haha.
Also, for those of you who got V4A working (Rooted, BusyBox Installed, SELinux Set to Permissive) and noticed V4A stop working after a few seconds after leaving the app, go to the V4A settings and check "Show Notification". That's it!
al_bert7 said:
Alright, figured out what I did wrong. You can root using king root but do not check oem unlock in developer settings, that's what causes the bootloop. As for V4A I was able to get it to work with the instructions in the OP. But I didn't switch out king root for supersu out of fear of it bricking again haha.
Also, for those of you who got V4A working (Rooted, BusyBox Installed, SELinux Set to Permissive) and noticed V4A stop working after a few seconds after leaving the app, go to the V4A settings and check "Show Notification". That's it!
Click to expand...
Click to collapse
I think it's related to swapping kingroot for supersu. I got that bootloop on a different device, had to reinstall the ROM. Didn't even try on my VIVO, just accepted I'll have to deal with KingRoot. It's not terrible, though. I just hope it's not sending my info elsewhere.
I used SuperSu Me pro to get rid of kingroot and it worked like a charm.
victorvscn said:
I think it's related to swapping kingroot for supersu. I got that bootloop on a different device, had to reinstall the ROM. Didn't even try on my VIVO, just accepted I'll have to deal with KingRoot. It's not terrible, though. I just hope it's not sending my info elsewhere.
Click to expand...
Click to collapse
padevoto said:
Hello everyone!
I share my experience installing and configuring VIPER4ANDROID in my BLU VIVO 5.
Before starting the phone must be rooted to this point use the following guide published on the Internet:
http://reviewroots.com/root-BLU-Vivo-5-with-or-without-pc
1) Install VIPER4ANDROID FX
http://forum.xda-developers.com/showthread.php?t=2191223
2) Download and install SELINUXMODECHANGER
http://forum.xda-developers.com/showthread.php?t=2524485
3) Open VIPER4ANDROID and install the driver
4) Open SELINUXMODECHANGER and change mode to Permissive
After these steps VIPER4ANDROID is ready to use
Click to expand...
Click to collapse
Thanks!!!
Link does not work
This link to "root-BLU-Vivo-5-with-or-without-pc" does not work anymore.
Hi guys,
I'm looking for a ROM that will pass the Safetynet checks but it seems these days everything is comes pre rooted. I've tried unrooting it (SuperSU app > uninstall root) but no luck.
Can anyone recommend a ROM or an unroot method that might work?
Just wondering what you're trying to achieve with the Safetynet check? Once I'd done "full unroot" on a few ROMs, I could quite comfortably play Pokemon Go on them, which allegedly uses a SafetyNet check.
For instance, I'm using Exodus now (with full unroot) but this has worked with many other ROMs too, such as SLIMrom.
Krexus-CAF is not rooted from memory, but it also is a little behind in security patches at the moment.
If you explain your end goal, someone might be able to help a little more!
Cheers
Thanks, it is to play pokemon go. I was using the magsik but since that stopped working and I don't use root for anything I thought I would just loose root. I've tried 4-5 ROMs including CM13, CM14 and exodus over the last few days bit no luck.
Would you share your full unroot method? what ever I'm doing I'm not doing right
have same question.
waiting for the best solution
Use Magist to bypass Safetynet
Try Magisk or System-less root.
If you really wish to fully unroot, go to SuperSU -> Settings and tap on unroot. It will unroot.
As you said you have already tried it the try this method :-
- Go to TWRP.
- Go to advanced page.
- Tap on File Manager.
- Browse to /system/bin/
- Delete su file.
That's all, you will be fully unrooted (no sure whether a word called unrooted is there! )
Good Luck :good:
Thank You!
Use magisk/suhide
FletchNZ said:
Hi guys,
I'm looking for a ROM that will pass the Safetynet checks but it seems these days everything is comes pre rooted. I've tried unrooting it (SuperSU app > uninstall root) but no luck.
Can anyone recommend a ROM or an unroot method that might work?
Click to expand...
Click to collapse
Magisk has system less root,xposed,v4a,busybox
Works gr8 with miui 8 6.9.29
Finally a temporary working method to use Systemless Xposed and bypass SafetyNet
Get Pokemon back to work in latest safetynet upgrade.
The below procedure along with the above "Root Switch" apk will allow you to play Pokemon again.
Alternatively there is a new file/patch for suhide that passes the latest SafetyNet Update.
Finally a temporary working method to use Systemless Xposed and bypass SafetyNet
Above works on Xiaomi.eu 6.10.13 (MIUI), marked temporary because if SafetyNet gets update again, it will probably fail again.
Use Suhide v0.55 and systemless supersu v2.78 SR1.
corkiejp said:
Finally a temporary working method to use Systemless Xposed and bypass SafetyNet
Above works on Xiaomi.eu 6.9.29 (MIUI), marked temporary because if SafetyNet gets update again, it will probably fail again.
Use Suhide v0.55 and systemless supersu v2.78 SR1.
Click to expand...
Click to collapse
nice one. :victory:
Thanks for your help.
The answers I needed.