Question Viper not working - Google Pixel 6

Literally found this on another thread credit to @Forever Alone just install, open app, let it install the driver and reboot, then I selected legacy mode. Enjoy and thanks again too forever alone

After second reboot viper stoped working JamesDSP is working great tho

I followed instructions from 6p thread for viper.
Working fine here even after reboot

Stupid question here (yeah, I should know better...) JamesDSP and Viper4Android still require a rooted device, correct?

Yes they do

Related

[Q] xposed / folder mount and orbot combo - endless reboot?

phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues

[Q] Xposed Framework Not Updated After Reboot

Hey all,
I tried searching for this issue, but couldn't find anything--apologies if it's been answered already. I just got my first smartphone and rooted it yesterday, so I'm new to this stuff (but in general am good w/ tech). It's a Moto X non-dev verizon, and running 4.4.
Xposed Framework (installed 2.4.1) won't stay up to date after a hard reboot (app_process is a red dash) and thus my modules don't work at bootup. There actually was an issue when I first installed Xposed: after installing and then updating and rebooting, it wouldn't say it was up to date until I did a soft reboot. Now after a hard reboot, I have to reupdate xposed and then soft reboot for modules to work. Apparently there are at least a few others with the same issue. Is this a known bug?
Any ideas? I've tried reinstalling Xposed, no go. SuperSU seems to work fine with my other apps too. Any help would be appreciated!
Thanks!
P.S. Gravitybox is hella crazy what the wizardry?
I am having the exact same problem. When I click reboot or soft boot I get a blank dialog box and then click ok but nothing ever happens and when I reboot manually from the power menu it gives me the red dashes like you said. It worked fine on my nexus 5 a while back but I'm trying it now on my galaxy tab 2 and getting this issue
ricesteamer said:
Hey all,
I tried searching for this issue, but couldn't find anything--apologies if it's been answered already. I just got my first smartphone and rooted it yesterday, so I'm new to this stuff (but in general am good w/ tech). It's a Moto X non-dev verizon, and running 4.4.
Xposed Framework (installed 2.4.1) won't stay up to date after a hard reboot (app_process is a red dash) and thus my modules don't work at bootup. There actually was an issue when I first installed Xposed: after installing and then updating and rebooting, it wouldn't say it was up to date until I did a soft reboot. Now after a hard reboot, I have to reupdate xposed and then soft reboot for modules to work. Apparently there are at least a few others with the same issue. Is this a known bug?
Any ideas? I've tried reinstalling Xposed, no go. SuperSU seems to work fine with my other apps too. Any help would be appreciated!
Thanks!
P.S. Gravitybox is hella crazy what the wizardry?
Click to expand...
Click to collapse
The newest version of Xposed (2.5) solved this, but not directly:
Without TWRP or CWM or anything, I tried to install/update the framework via recovery (flash zip automatically) -- this was a new option in the update. It didn't exactly work, but then I tried install/update normally (writing to /system) and it finally worked. No idea why, but I'm happy. I googlefu'd the crap out of this too, sigh.

GApps error after installing custom ROM

So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2

Sparrow_7.1.1_Debloat ROM

This is a debloated/slightly modified ROM. There are NO ASUS apps, and only the bare minimum Google apps. I don't use any of the Fit apps, so they have been removed, but I believe they can be easily reinstalled through the PlayStore. Everything on the watch is significantly faster, except the Bluetooth call lag still exists on 4G, like it does on every device lately. I don't notice the bluetooth lag when the phone and watch are connected to WiFi. There is no watch face installed, so install one from the PlayStore after it boots. I pulled the boot animation from the developer preview, and the clock works during boot. It's pretty sexy.
Within the zip are the boot and recovery files as well, which include TWRP and a patched boot.img for Magisk. You'll need to sideload the latest Magisk Manager to have root access.
DIRECTIONS:
Download and extract Sparrow_7.1.1_Debloat
Boot into fastboot mode.
fastboot -w (This wipes the device, which is HIGHLY recommended.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.simg
I highly recommend starting with fastboot -w to wipe the device. If you run into any issues at all and didn't wipe before install, then wipe and try again before posting issues. Also, pay close attention to the SIMG in system.simg. Type it exactly as it's posted, or copy and paste it. The SIMG is important lol.
Anyone running this ROM should look into this mod by @LeeonLee. Everything is noticeably smoother and lightning fast. I haven't gotten any Bluetooth lag since I implemented it. https://forum.xda-developers.com/ze...parrowaw2-0-enabling-cores-gpu-boost-t3800427
Let me know what you guys think and if I should add/remove anything. I plan to add some more tricks if I update the ROM, including some speed tweaks. Happy Flashing!!!
Appears to work fine here.
CVertigo1 said:
This is a debloated/slightly modified ROM. There are NO ASUS apps, and only the bare minimum Google apps. I don't use any of the Fit apps, so they have been removed, but I believe they can be easily reinstalled through the PlayStore. Everything on the watch is significantly faster, except the Bluetooth call lag still exists on 4G, like it does on every device lately. I don't notice the bluetooth lag when the phone and watch are connected to WiFi. There is no watch face installed, so install one from the PlayStore after it boots. I pulled the boot animation from the developer preview, and the clock works during boot. It's pretty sexy.
Within the zip are the boot and recovery files as well, which include TWRP and a patched boot.img for Magisk. You'll need to sideload the latest Magisk Manager to have root access.
DIRECTIONS:
Download and extract Sparrow_7.1.1_Debloat
Boot into fastboot mode.
fastboot -w (This wipes the device, which is HIGHLY recommended.)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.simg
I highly recommend starting with fastboot -w to wipe the device. If you run into any issues at all and didn't wipe before install, then wipe and try again before posting issues. Also, pay close attention to the SIMG in system.simg. Type it exactly as it's posted, or copy and paste it. The SIMG is important lol.
Anyone running this ROM should look into this mod by @LeeonLee. Everything is noticeably smoother and lightning fast. I haven't gotten any Bluetooth lag since I implemented it. https://forum.xda-developers.com/ze...parrowaw2-0-enabling-cores-gpu-boost-t3800427
Let me know what you guys think and if I should add/remove anything. I plan to add some more tricks if I update the ROM, including some speed tweaks. Happy Flashing!!!
Click to expand...
Click to collapse
Hi...I install this rom and the mod leeonlee, my watch have high battery drain, I do not know what to do
Did the battery life get significantly worse compared to stock 2.0? There was no noticeable difference in battery life for me. It was always horrible on 2.0 for me.
I have been running this for almost 3 weeks with @LeeonLee mod, and I haven't gotten any significant Bluetooth lag for calls. Before his mod, it wasn't uncommon that my phone would ring for 5 seconds before the watch showed me someone was calling. I mainly use my watch for riding my motorcycle, so any call lag is a big deal when I can't see who is calling.
I also haven't gotten the "not available" message when using voice commands since the mod.
Hello, I'm using still the stock rom, just rooted + performance patch, watch last 2 days, even 3 days when not used so intensively.
LeeonLee said:
Hello, I'm using still the stock rom, just rooted + performance patch, watch last 2 days, even 3 days when not used so intensively.
Click to expand...
Click to collapse
Maybe I should look into the build.prop mods I added from another watch. Perhaps it's causing excessive battery usage. It could also be that my watch battery is degraded.
which version of magisk manager and how sideload it? i'm little bit noob with adb
Here is a much easier way if you don't know adb too well. Download the latest Magisk installer zip from the Magisk thread onto your PC. I personally am using the 16.4 beta at this time. The Magisk Manager is included in the Magisk zip. Assuming you have TWRP installed, boot into recovery using *adb reboot recovery* or swipe from the top right when booting. The watch is recognized as a storage drive when it's in recovery. Then you can copy the Magisk zip from you PC to your watch, and install it with TWRP. This will give you the latest Magisk and Magisk Manager.
CVertigo1 said:
Here is a much easier way if you don't know adb too well. Download the latest Magisk installer zip from the Magisk thread onto your PC. I personally am using the 16.4 beta at this time. The Magisk Manager is included in the Magisk zip. Assuming you have TWRP installed, boot into recovery using *adb reboot recovery* or swipe from the top right when booting. The watch is recognized as a storage drive when it's in recovery. Then you can copy the Magisk zip from you PC to your watch, and install it with TWRP. This will give you the latest Magisk and Magisk Manager.
Click to expand...
Click to collapse
Never thought about using TWRP to transfer the zip, I just simply pushed it via adb and then rebooted to TWRP to install magisk zip.
BTW, after installing recovery.zip, boot.zip, magisk.zip, I rooted and setup the OnDemand script. It now is much smoother and don't see any noticeable lags. I downloaded System Info Wear to check that the script is actually working. It shows all four cores running at 787Mhz. Kudos to @LeeonLee for the script setup!! Many thanks also to @CVertigo1 !! I also decided to do what @LeeonLee mentioned in regards to stock rom staying put. I wasnt too eager to wipe current system just yet
hi guys... the smartwatch finally is usable.. but i have a question, have the wrist gestures been removed?
Just want to say that I've been using this ROM for a few weeks now, along with the core unlock mod. And it is amazing. The watch is so much more fluid. And with my rather light usage (always on, no gestures) I still get a full day out of the battery. I'm also glad all the extra bloat is gone. No apps I'll never use and no watchfaces I never set.
If you are thinking about switching from stock, highly recommended.
Thanks @CVertigo1
mastermoon said:
hi guys... the smartwatch finally is usable.. but i have a question, have the wrist gestures been removed?
Click to expand...
Click to collapse
Wrist gestures are still there, you just have to turn on that setting under Gesture settings.
bleached45 said:
Just want to say that I've been using this ROM for a few weeks now, along with the core unlock mod. And it is amazing. The watch is so much more fluid. And with my rather light usage (always on, no gestures) I still get a full day out of the battery. I'm also glad all the extra bloat is gone. No apps I'll never use and no watchfaces I never set.
If you are thinking about switching from stock, highly recommended.
Thanks @CVertigo1
Click to expand...
Click to collapse
I really appreciate the kind words. That's exactly what I was going for. I'm not big into searching through a hundred apps to find the few I need, so I prefer my devices to be very militaristic. If I need Fit apps, or any other app, I'll install them separately. They don't need to live in the system. I stripped as much as I could without causing bootloops. I may be able to pull a few more out for the next ROM upload, and I'll also include @LeeonLee mods.
despite my limited modding skills I managed to do everything without doing any damage .. a big thank you to @CVertigo1 and @LeeonLee for the great work ..
Hope @CVertigo1 will be able to port a zenwatch3 rom on 2 one day...
Can I use this rom for wren?
I have just recently installed this on my watch, and it is very nice! The only thing that I noticed is that the pedometer (through Google Fit) does not seem to count the steps I am taking, is this related to some of the files be removed or is it just Google?
I'm not working at the moment but I want to send you a donation as soon as I can. I wanted to thank you because your debloated ROM managed to get my watch booting up once again for the first time in nearly a year. You deserve a donation because you saved me from spending money I don't wanna waste on an entirely new watch.
Is there any way to install some watchfaces stock after installing this Rom?
jnelsoninjax said:
I have just recently installed this on my watch, and it is very nice! The only thing that I noticed is that the pedometer (through Google Fit) does not seem to count the steps I am taking, is this related to some of the files be removed or is it just Google?
Click to expand...
Click to collapse
Is the pedometer really not working on this rom?
djleor said:
Is the pedometer really not working on this rom?
Click to expand...
Click to collapse
nope, but everything else works great.

Question Viper4Android not working

Does anyone know how to get Viper4Android working on this device, I tried everything and it still asks me to install the drivers after every reboot.
I also got the same issue
Use jamesdsp it works.
It's because of the OS, with AOSP it works.

Categories

Resources