Hi.
I have rooted med 2012 Nexus 7 and need to install Timur's Kernel to use otg during charging.
But how do i Install a Kernel?
mehrvarz.github.io/nexus-7-usbrom/
I dont see any guides at the website.
Evelen said:
Hi.
I have rooted med 2012 Nexus 7 and need to install Timur's Kernel to use otg during charging.
But how do i Install a Kernel?
mehrvarz.github.io/nexus-7-usbrom/
I dont see any guides at the website.
Click to expand...
Click to collapse
Flash it in recovery or use a program like Flashify
Juhful said:
Flash it in recovery or use a program like Flashify
Click to expand...
Click to collapse
Hello
Are there any guidelines for this?
Evelen said:
Hello
Are there any guidelines for this?
Click to expand...
Click to collapse
Save the zip file containing the Kernel to your SD card and remember where it is, download Flashify from the app store and open Flashify grant permission, under flash choose zip file, go to the location of the zip file containing the kernel, select it and choose normal way then flash it, it will reboot and the kernel should be installed
Juhful said:
Save the zip file containing the Kernel to your SD card and remember where it is, download Flashify from the app store and open Flashify grant permission, under flash choose zip file, go to the location of the zip file containing the kernel, select it and choose normal way then flash it, it will reboot and the kernel should be installed
Click to expand...
Click to collapse
Hi, done.
Flashify displayed that the kernel was installed, i rebooted, than i got a image of a androide logo with text "Error".
Rebooted device, started ok.
How can i see if it worked?
PS: Used internal memory, Nexus 7 don't support SDcard
I don't think it worked, cant se any of the Timur-Kernel functions
Go to settings, about device and you can see what kernel you are running.
Juhful said:
Go to settings, about device and you can see what kernel you are running.
Click to expand...
Click to collapse
Kernel v: 3.1.10-g4776c68
[email protected] # 1
Wed Nov 20 12:07:54 PST 2013
Build nr; KOT49H
Mhm, does not seem to have worked, tips to other solutions?
Tryed a app caled "ROM Manager", worked
Cool, glad you have it working !
Related
Hello XDA,
So I was following a youtube guide that shows how to root nexus s. (http://www.youtube.com/watch?v=GSD92Qjt5Og). This is one click verison. So after unlocking the bootloader, when its time to select flash CWM, the CMD window would just close. I guess the file i was using were bad. So then i switched over to another youtube video (http://www.youtube.com/watch?v=EA6DlAqYUeo). In this video, (using the files in video's description), I mananged to flash CWM (but i used the latest verison of CWM 5023-cyan.img). Then pretty much followed the video and got superuser installed on my nexus. Now when i tried to boot into recovery, it will not boot into CWM. it shows the android with exclamation mark and there when i press volume up and power, i am taken to the stock recovery i guess.. So now I am confused if my phone is rooted. I do have superuser installed on my phone right now (version that was included in the 2nd youtube video) but I don't have CWM. I am interested in flashing other ROMS. How and what should i do? Sorry for the long explanation. Thanks for your help
Use root explorer or similar program to rename the file "/system/etc/install-recovery.sh" to anything you like (e.g. install-recovery.sh.bak), as this script is run on boot and replaces a custom bootloader if it is installed. After this just flash CWM again and you can be free
You'll have to do this anytime you install a Google Stock ROM.
Harbb said:
Use root explorer or similar program to rename the file "/system/etc/install-recovery.sh" to anything you like (e.g. install-recovery.sh.bak), as this script is run on boot and replaces a custom bootloader if it is installed. After this just flash CWM again and you can be free
You'll have to do this anytime you install a Google Stock ROM.
Click to expand...
Click to collapse
I installed ES File Explorer and I cannot locate any folder called system.. the only 3 folders I see are "android", "clockworkmod", "Lost.DIR". root explorer is paid app. do you know any other free app. I don't know if this ES File explorer allows me to see system files. Its only showing whats on SD card...
NVM... i managed to get another app.. that allowed me to change the file name as you suggested.. then i installed ROM manager.. Flashed CWM from there.. and rebooted into recovery.. and GUESS WHAT.. I GOT CWM.. .. thanks buddy..
No worries mate. BTW, for ES, you need to go to options and tick the two options all the way at the bottom (enable root, mount /system).
So I have a Nexus 7 32GB wifi and I unlocked the bootloader and rooted it last night and had CWM touch installed. The problem is, when I boot the tablet back into recovery, it doesn't load CWM, it just displays the stock recovery screen with a weird android logo.
What I'd like to accomplish at this point is to install the latest version of CWM Touch 6.0.1.9, which I already downloaded from the official site, it seems to be an img file, and after all that is done, I'd like to install the latest version of CleanROM.
I have no access to a computer at this time, so would this still be possible?
Can anybody please walk me through it?
so I acutally managed to download cwm from the market, and it installed, its not the touch version, but it works. I also used es file explorer and went into the system folder, and renamed the recover-from-boot.p file.
Now, what I'd like to do is install cwm touch, but I only have an img file of it downloaded, any ideas on how i can install it without a pc?
have you tried the Rom Manager app, is that how you installed CWM from the market? Rom Manager might have the touch version, but i haven't looked myself.
otherwise, you could probably install the .img file using Terminal Emulator on the phone. sorry i can't give you the exact command, but it would be a dd command and you would need to know the name of the recovery partition to write the image file to.
yogi2010 said:
have you tried the Rom Manager app, is that how you installed CWM from the market? Rom Manager might have the touch version, but i haven't looked myself.
otherwise, you could probably install the .img file using Terminal Emulator on the phone. sorry i can't give you the exact command, but it would be a dd command and you would need to know the name of the recovery partition to write the image file to.
Click to expand...
Click to collapse
So yea...I got rom manager from the market, and installed cwm that way, its not the touch version, but it was enough for me to install CleanRom 3.0
Now, regarding Rom manager, it has an option to flash the latest recovery mod, and I used es file explorer and found the following directory:
/sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries/
inside was the following file:
recovery-clockwork-6.01.9-grouper.img
Now, I wonder if I can simply replace that img file with the following:
recovery-clockwork-touch-6.0.1.9-grouper.img
would I need to rename it and remove the touch part of the file name?
I was thinking of just replacing and flashing via rom manager, you think it'll work?
just tried my above theory, and rom manager is actually smart, it downloads a new copy when you want to flash cwm
I've done something like this (though I forget exactly what) using Android Root Toolkit app.
AcuraKidd said:
just tried my above theory, and rom manager is actually smart, it downloads a new copy when you want to flash cwm
Click to expand...
Click to collapse
Yeah, I'm sure it checks hashes before flashing anything, and since they didn't match, it downloaded a new copy.
I thought you could buy the pro version of rom manager and it would then flash the touch versions for you?
When I go into Rom Manager and choose flash CWM it gives me the option to flash the touch version or the normal version. Maybe you need to flash the normal version with Rom Manager first then it'll give you the option for touch?
if you have the .IMG file for w/e recovery you want to install, download Terminal Emulator app from gPlay and fire off the following commands:
Code:
su
dd if=/sdcard/shineynewrecovery.img of=/dev/block/mmcblk0p1 bs=4096
Alter the /sdcard/shineynewrecovery.img to wherever you saved the .IMG of the recovery.
I just created a zip. Testing now to make sure its all good and then I'll post the link
*edit*
Here's the link
http://db.tt/xEIWqXFe
I know that when I did this for 6.0.1.0 people had trouble flashing this from TWRP but if you have CWM non-touch already installed flash this and you're god to go. Feel free to mirror
Sent from my Galaxy Nexus using xda app-developers app
HellcatDroid said:
if you have the .IMG file for w/e recovery you want to install, download Terminal Emulator app from gPlay and fire off the following commands:
Code:
su
dd if=/sdcard/shineynewrecovery.img of=/dev/block/mmcblk0p1 bs=4096
Alter the /sdcard/shineynewrecovery.img to wherever you saved the .IMG of the recovery.
Click to expand...
Click to collapse
Thanks, this method worked perfectly.
mrich137 said:
I just created a zip. Testing now to make sure its all good and then I'll post the link
*edit*
Here's the link
http://db.tt/xEIWqXFe
I know that when I did this for 6.0.1.0 people had trouble flashing this from TWRP but if you have CWM non-touch already installed flash this and you're god to go. Feel free to mirror
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll hold onto the zip for the future.
can anyone advise? i want to install a custom rom and root my tf300t
i have unlocked it but now i need to install the mod twrp but apparently i need a pc. is there another way? via .apk file or something...
i then need to put my rom and gapps file on sd card, reboot to recovery and install the zip files right? and i am done????
wakkaday said:
can anyone advise? i want to install a custom rom and root my tf300t
i have unlocked it but now i need to install the mod twrp but apparently i need a pc. is there another way? via .apk file or something...
i then need to put my rom and gapps file on sd card, reboot to recovery and install the zip files right? and i am done????
Click to expand...
Click to collapse
Yes you can do that, all you need is a "terminal emulator" app, there are plenty available just search for them. Depending on the custom ROM some already provide updated gapps so be sure to use the right one and not just the one given in tools like goomanager.
I would recommend the following.
1. Backup your apps + data using Titanium Backup
2. Boot into recovery and create a backup of your system
3. Wipe cache/davlik/data + system
4. be aware of the right "flashing order" FIRST the ROM file, then add more zips and choose gapps
5. enjoy your custom ROM
frankgreimes said:
Yes you can do that, all you need is a "terminal emulator" app, there are plenty available just search for them. Depending on the custom ROM some already provide updated gapps so be sure to use the right one and not just the one given in tools like goomanager.
I would recommend the following.
1. Backup your apps + data using Titanium Backup
2. Boot into recovery and create a backup of your system
3. Wipe cache/davlik/data + system
4. be aware of the right "flashing order" FIRST the ROM file, then add more zips and choose gapps
5. enjoy your custom ROM
Click to expand...
Click to collapse
Something tells me he hasnt rooted yet. If im not mistaken, he can't use a terminal app with the dd command if he isnt rooted. I know you can root using adb though with debugging enabled but im not sure he can root without a pc.
Here is a good place for him to start :
http://forum.xda-developers.com/showthread.php?t=2228613
Sent from my SGH-T889 using xda app-developers app
pyraxiate said:
Something tells me he hasnt rooted yet. If im not mistaken, he can't use a terminal app with the dd command if he isnt rooted. I know you can root using adb though with debugging enabled but im not sure he can root without a pc.
Here is a good place for him to start :
http://forum.xda-developers.com/showthread.php?t=2228613
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the correction, assumed he's already rooted sorry.
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
I'm not a kernel person and that's the only thing that didn't work, was Kali dirty kernel changing.
I honestly can't answer that but seems plausible to me if someone can figure out the kernel thing.
Sent from my BLU R1 HD using XDA Labs
wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
this isnt a rom it's a linux system you flash ON TOP of the n5 stock rom, so no
This is incredible, thank you for sharing!
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
jasonmerc said:
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
Click to expand...
Click to collapse
There is a universal kernel option in setup. Like I said though it didn't flash the kernel to kalidirty kernel. Everything else worked though. With the views I'm sure someone else can verify they got it working as well.
blu kernel source, binaries available?
Are the blu kernel source, binaries available to try and create a custom ROM?
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
emc2cube said:
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
Click to expand...
Click to collapse
have you done anymore looking into the AOPP ?
wfandreas said:
have you done anymore looking into the AOPP ?
Click to expand...
Click to collapse
Yes, but no success so far.
HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
Which supersu did you install ?
HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
what command it that last pic?
wfandreas said:
Which supersu did you install ?
Click to expand...
Click to collapse
Originally I installed the one off the Google play store and then pro off the store as well.
Once installing nethunter I used the older supersu that comes in the zip.
wfandreas said:
what command it that last pic?
Click to expand...
Click to collapse
That's the bootup from vnc. You have to go set your passwords and boot into it.
HeeyMaan said:
That's the bootup from vnc. You have to go set your passwords and boot into it.
Click to expand...
Click to collapse
thank you, I did the same install, works well.
Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....
Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.
Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a
Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?
Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk
When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!