[Q] Chrooting in kitkat - Nexus 7 (2013) Q&A

My issue started after updating to kitkat(stock), i have the wifi only model
Im trying to (re)install this https://github.com/borh/nexus-7-2013-arch-scripts
But im getting stuck on the first step of the install script - "chroot cannot execute /su/su-mksh no such file or directory"
eventho su-mksh IS there (i tried rerooting, prerooted stock, busybox in different locations and finally even using the root toolbox.. with wipes in between ofc).. root acess seems to be fine with every other app (clearly stuff like linux deploy dont work either.. yes i even tried the hurtful way )
Soo whats new in kitkat? it starts to feel like i need another kernel?

Related

[Q] Did I lose Root?

Hello all,
I have recently, finally got to root my Evo4G after making the mistake and taking the 2.3 update a few months back. I am some experience but not a lot with rooting phones. (I'm better at "rooting" if you will w/ computers and game systems. lol) Anyways here is what I did:
1. I used Revolutionary to S-Off my phone and use that as my Recovery System
2. Installed ICS-deck-4.0.3 PA8
3. Installed the gapps that it came with and booted up.
Everything is working very well, I ran into no issues at all. However some things I noticed are:
1. I cant mount my SD Card
2. Cant seem to get the calendar fix to work
3. Also it seems that I dont have root??? I thought that revolutionary rooted the phone. If not how do i actually "root" and not just S-Off so that I can install custom ROMS.
Thanks
Jessy
jessy5765 said:
Hello all,
I have recently, finally got to root my Evo4G after making the mistake and taking the 2.3 update a few months back. I am some experience but not a lot with rooting phones. (I'm better at "rooting" if you will w/ computers and game systems. lol) Anyways here is what I did:
1. I used Revolutionary to S-Off my phone and use that as my Recovery System
2. Installed ICS-deck-4.0.3 PA8
3. Installed the gapps that it came with and booted up.
Everything is working very well, I ran into no issues at all. However some things I noticed are:
1. I cant mount my SD Card
2. Cant seem to get the calendar fix to work
3. Also it seems that I dont have root??? I thought that revolutionary rooted the phone. If not how do i actually "root" and not just S-Off so that I can install custom ROMS.
Thanks
Jessy
Click to expand...
Click to collapse
To mount SD card you have to download a third party app.
the calender fix works (i think) but it depends on if it flashed correctly, if it was a bad download, etc.
Revolutionary removes the NAND protection, it doesn't root it. You have to flash a zip for the root binaries or you can install Superuser from the market. The su wasn't working for a little bit before because it wasn't updated for ICS. Make sure you have the latest Superuser app installed to install the latest su binaries.
my evo is aggressively runny
Couldn't update from market. Had to download the zip from su website then install from recovery. I got it to my phone from Bluetooth transfer from my notebook. Damn its like trying to get something done at a DMV. Haha. All works now. Mounting, hw acceleration, root access, now..... where's those beta cam drivers haha
Sent from my PC36100 using XDA App
Also, the calendar fix, I was only able to install 2 of the apk's but I did it while i was in the OS not in recovery mode. I wasnt able just install them via the .zip file in recovery either.
Does someone have some better instructions on this?

[Q] Problem after trying to root Arc S

Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
Click to expand...
Click to collapse
I had the same problem. First of all if you have bootloader unlocked it is still unlocked even if you had flashed another rom.
What rom did you exactly flashed? What OS do you use on your computer? When I started to flash different stock roms and then to root them then I unlocked my bootloader then the same problem appeared on Windows 8 (I could find no way to make my phone recognisable - don't know why). I tried to flash rom again on another one running on Winows 7 and after instaling drivers from flashtools and instaling sony companion phone started to be recognized.
So try to connect your phone to another Pc (if possible) and then flash any stock rom (for example ICS 4.04 build 4.1.B.0.587) and then (if you have unlocked you bootloader) flash any pre-rooted kernel (http://forum.xda-developers.com/showthread.php?t=2159411).
ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
Click to expand...
Click to collapse
1. Why did you use XParts? Unlocked bootloader means you can flash a stock kernel with CWM in it.
2. CM ROMs use different kernel, that's why you get status 7. Maybe you can Google a bit on CWM status 7 error? To install Cyanogen ROM, use the included kernel or look for a list of recommended kernels.
3. Flashtool should still work. Can you enter flashboot? Connect your cable to the PC, hold down the back button and connect your cable to it. A blue light means it's successfully connected in flash mode.
僕のLT18iから送られてきた
Thanks both for the different bits of advice. I dunno how, but it finally works now! In the end I installed sony's pc companion, switched off antivirus and then all of a sudden i could flash things again. Then i just followed the steps to rooting the phone for the second time, and it finally worked. Got my root back and also managed to install a ROM from CWM.
Again, not sure how, maybe i should have just turned off my antivirus from the start, or maybe in retrying all the steps I somehow stumbled across the sollution, but at least it works now
popthosegaskets said:
1. Why did you use XParts? Unlocked bootloader means you can flash a stock kernel with CWM in it.
2. CM ROMs use different kernel, that's why you get status 7. Maybe you can Google a bit on CWM status 7 error? To install Cyanogen ROM, use the included kernel or look for a list of recommended kernels.
3. Flashtool should still work. Can you enter flashboot? Connect your cable to the PC, hold down the back button and connect your cable to it. A blue light means it's successfully connected in flash mode.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
What is XParts? I don't think i used that program. The steps i previously followed might have been redundant in part, but I wanted to be on the safe side and just try all options i could find.
I tried googling for the CWM status 7 error, but couldn't really find any sollution i could work with. And anyway, it's fixed now (i hope, didn't try CM again though)
Flashtool didn't work yesterday. Or at least, it did work but i just couldn't flash anything cause it didn't recognise my phone.
Anyway, thanks again. This is fixed now
ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something.
Click to expand...
Click to collapse
Which is why senior members in all sections create guides like - [GUIDE] All Things XPERIA - Debranding - Rooting - BL Unlocking - Theming to make it easier for People like yourself, and in those guides you'll find things like...
XperienceD said:
Rooting:
UPDATE: One click root [4.1.B.0.587 /.431 /.562 ] All 2011 Xperias
- What is rooting and why should I do it? The pros & cons of Android rooting
Rooting methods for the XPERIA line of Phones has constantly changed from apps to Pre-Rooted ROMs and Kernels. A Google search of "root -insert device name-" should help to find the specific method for your Phone but the following link is well worth reading - [How-To] Rooting guide for 2011 xperia devices
References:
[Arc/S] [PRO] Root for 4.0.4 ICS Update [4.1.B.0.431+4.1.B.0.587]
Root MANY ANDROID! [Upd: 18.12.2012]
[ROOT+BB+CWM] ICS and non rootable GB build
[ROOT][NOOB GUIDE][for unlock BL] For Official ICS 4.0.4
[HOW-TO][FTF] Root and CWM with the latest 9.0.1.D.0.10 firmware
[ROOT&MORE]Xperia 2012 line Flashtool + prerooted system.img + Sony fw FTF + addons
[Tutorial]Root.Xperia 4.0.4 ROM [all h/m(dpi)] | 4.1.B.0.431
Click to expand...
Click to collapse
...so when a new members start new threads about something that's been covered a gazillion times, it can be quite frustrating.
XperienceD said:
Which is why senior members in all sections create guides like - [GUIDE] All Things XPERIA - Debranding - Rooting - BL Unlocking - Theming to make it easier for People like yourself, and in those guides you'll find things like...
...so when a new members start new threads about something that's been covered a gazillion times, it can be quite frustrating.
Click to expand...
Click to collapse
Well, I did follow the steps in at least one of those guides. And that worked. So the problem wasn't in working out how to root the phone, but in fixing what went wrong afterwards. The first attempt at rooting worked, but then flashing a ROM failed, the phone stopped working and after fixing that i lost the root and couldn't find a way to reroot it (even ater following all the steps in the guides i previously used, it just didn't work)
So, with all do respect to those guides and their usefullness, as far as I can tell my problem/question wasn't answered in them.

[Q] Lost root, won't come back

So I'm not a complete and utter n00b here, as I've been rooting and installing CM for at least three years now on several different phones. But this problem vexes me...
Patient: SIII, formerly rooted and running CM10.1 just fine. A few weeks ago, I tried to install a 10.2 stable build, and it somehow took my root away. I tried every trick I knew how - installing the root files via Odin (many versions), via ADB, via Kingo Root...nothing. Absolutely nothing I try will get this thing to give me my root back, and the ads are starting to really get on my nerves.
My ticker says 15 attempted installs, but I don't think it's blocking me from rooting...is it? All the phones I've rooted I've never had a problem like this, where absolutely nothing will allow root to "take", such as it is.
Any thoughts or suggestions?
Thanks!
Wow, nothing? I figured someone would at least sigh heavily, berate me for not reading the forums completely, then point me to a thread where this has been discussed ad nauseum
Last night, I tried rooting with TWRP, CWM, every variant and trick I could find to get this thing to root for me, and while these things all seem to load fine, none of them give me my root access back. No one has any ideas?
Thanks!
help
im using rooted 4.3 stock rom in t999..
everytime i boot into recovery it says "fixed root"
any solve for this?????
Did you dirty flash CM10.2 over CM10.1? if so, it might have failed to write the partition completely/correctly. I would suggest to backup everything that you can (adb backup or similar) and then wipe everything then reflash fresh CM10.2.0 + GApps + SuperSU or Koush's Superuser flashable zip.

Unable to Install ANY custom roms onto my m919

I am a frequent experience Android user and have been flashing Roms since like forever.
Owning gs4 been nice installing Roms all the time however recently when I went to install new gpe ROM (new kernel seemed prime to have) coming from HDrom rls20 I downloaded currupt zip. When I tried installing currupt zip (not knowing yet it was currupt) it gave me red errors not allowing me to proceed.. Then, I turned off device got fresh dload and made sure md5 sum was legit and it was tried again of course first factory data reset with advanced system wipe the ROM proceeded to aroma installer this time.. Attempting to install I chose all my settings and it went to progress bar to install and skipped any system extraction and went straight to Apks.. Batch completed and I hadn't a ROM installed for it took it 5seconds.. I have had this problem in the past before and I sold it they returned it (didn't like condition) and bingo I was able to install Roms again (this was way back in the day with this same gs4) I'm assuming system partition not mounting because also when I tried installing that currupt file it was saying in red unable to mount system and stuff. Luckily I downloaded NK2 firmware (took 8hs) and am fine on stock but I'm hoping someone has a clue to point me in right direction.. I saw forum of somebody with similar issue their fix was pushing zip via computer adb commands then installing. I'll have to give it a try but sticking to stock for a bit. BTW this happens with every ROM just skips system files in fact cyanogenmod just hhung at installation wouldn't fail or complete. I used TWRP LATEST. Please help developers I'm sure this ones a no brainer for y'all. Except seems like issue only I've encountered for this isn't a popular thing at all on google.
SOLVED
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Stoowyguy said:
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Click to expand...
Click to collapse
What does it mean to "push adb" a phone's rom? Doesn't Odin automatically flash the selected rom?

Cant seem to get viper4android to work

I learned about viper4android and that is what made me start this crusade. I literally spend all of yesterday researching and learning how to root and troubleshooting viper4android and I still can't seem to get it to work.
I rooted my phone and flashed the latest version of TWRP, and installed superSU as well. I initially had a lot of trouble getting the busybox drivers to install but I finally managed to get the latest version installed. The app busybox on rails verifies that the current version of the busybox drivers are installed.
I tried different methods of installing viper4android and I don't have any luck with any. I get the app installed but once I launch the app it asks me which drives I to install, I try to install the super quality drivers but the drivers will not install. I've done a lot of googling of what the problems could be but the "fixes" people suggest dont work. The latest thing I tried was installing SELinux and changing the mode to permissive before trying to install the the drivers but the drivers will still not install.
Any ideas on what to try next? I've granted all these apps permanent permission through superSU. The other thing I've been wanting to do is to remove all the ATT bloatware, but even the app I got for that called "uninstall" will not uninstall all the bloatware which makes me wonder if something is incorrect. However in the bootloader it says my phone is "modified" and "unlocked".
Any help would be appriciated, and I should also mention I have lolipop 5.0.2.
Your problem is the stock kernel. It has write protection enabled.
You need a custom kernel where the write protection is disabled.
Try ElementalX for a start : http://forum.xda-developers.com/showthread.php?t=2705613
or any Sense based kernel.
ckpv5 said:
Your problem is the stock kernel. It has write protection enabled.
You need a custom kernel where the write protection is disabled.
Try ElementalX for a start : http://forum.xda-developers.com/showthread.php?t=2705613
or any Sense based kernel.
Click to expand...
Click to collapse
Do I need to install skydragon before installing elementx? Or will installing elementX sense 5.0.2 version be ok?
Edit: I read on a blog that you need to install skydragon first, but I saw no mention of it in the official elemtnx thread so I ended up installing elementx and it worked by I kept getting hung on the HTC logo on boot, I did a reset and it fixed it with the eleX kernel running. viper works no but it looks like I've lost data. lol. Always something. Now it's time to figure this out.
Sep1911 said:
Do I need to install skydragon before installing elementx? Or will installing elementX sense 5.0.2 version be ok?
Edit: I read on a blog that you need to install skydragon first, but I saw no mention of it in the official elemtnx thread so I ended up installing elementx and it worked by I kept getting hung on the HTC logo on boot, I did a reset and it fixed it with the eleX kernel running. viper works no but it looks like I've lost data. lol. Always something. Now it's time to figure this out.
Click to expand...
Click to collapse
Did I mentioned any ROM ? I said and talked about ElementalX kernel only and your problem has nothing to do with ROM. I didn't ask what ROM that you have, right ? Because you already mentioned it has lollipop 5.0.2
ckpv5 said:
Did I mentioned any ROM ? I said and talked about ElementalX kernel only and your problem has nothing to do with ROM. I didn't ask what ROM that you have, right ? Because you already mentioned it has lollipop 5.0.2
Click to expand...
Click to collapse
Like I said in my edit it's something I read online. I am new to this stuff and at the time I thought you would need a new ROM in order to install a kernel. I was trying to research what I need to do so I dont go in screwing something up and there was a how to blog that specifically mentioned you need a new ROM inorder to install the element X kernel. But that turned out do be flawed information. Anyways I've since read a lot about ROMs, kernels and what not and now have a better understanding of what each piece of the puzzle does.
Anyways, the phone has been kind of unreliable. I had previously used the phone since it's launch before rooting it. I figured it might not be a bad idea to clean everything out hoping that would solve some of the problems. I relocked the phone and did an RUU. I then rooted the phone again and installed elementX. I cant send or receive multimedia texts, GPS does not work at all, and data works on and off. If I reboot the phone chrome will load any page but then after a few mins it stops and sometimes it will load certain websites and at other times it wont load anything at all. I am having good reception of course. Could elementX be the culprit here?
Sep1911 said:
Anyways, the phone has been kind of unreliable. I had previously used the phone since it's launch before rooting it. I figured it might not be a bad idea to clean everything out hoping that would solve some of the problems. I relocked the phone and did an RUU. I then rooted the phone again and installed elementX. I cant send or receive multimedia texts, GPS does not work at all, and data works on and off. If I reboot the phone chrome will load any page but then after a few mins it stops and sometimes it will load certain websites and at other times it wont load anything at all. I am having good reception of course. Could elementX be the culprit here?
Click to expand...
Click to collapse
I searched info on AT&T with ElementalX .. what I've found they worked.
So not sure why it didn't work for you. You tried ElementalX-m8-4.05-Sense, right ?
Your first post was asking about Viper4Android, you need a custom kernel with write protection disabled for it to work.
You can RUU it back and try different kernel and see how it goes.
BTW ... what's the RUU version no. ? 4.28.502.2 ?
ckpv5 said:
I searched info on AT&T with ElementalX .. what I've found they worked.
So not sure why it didn't work for you. You tried ElementalX-m8-4.05-Sense, right ?
Your first post was asking about Viper4Android, you need a custom kernel with write protection disabled for it to work.
You can RUU it back and try different kernel and see how it goes.
BTW ... what's the RUU version no. ? 4.28.502.2 ?
Click to expand...
Click to collapse
Yeah I was initially trying to get V4A to work, and flashing elemental X allowed me to resolve my problems with that, but now I'm having phone functionality problems. And yes, that is the RUU number that I used on my phone. Any kernels you recommend ? Also, as far as reliability and avoiding problems goes do I need to revert back to stock kernel everytime before flashing a new kernel or would clearing the caches and flashing a new kernel over another custom kernel suffice?
Can't help much on Kernel as I don't use custom Kernel.
You need to try some of them and find out which work best for your device.
Maybe asking in AT&T sub-forum will get you better respond.
The main point here is you need write protection disabled kernel to have that viper4android running and also to remove some bloatware that you want to get rid off.
ckpv5 said:
Can't help much on Kernel as I don't use custom Kernel.
You need to try some of them and find out which work best for your device.
Maybe asking in AT&T sub-forum will get you better respond.
The main point here is you need write protection disabled kernel to have that viper4android running and also to remove some bloatware that you want to get rid off.
Click to expand...
Click to collapse
Sorry for digging old thread but i have face the same situation like in the OP . My m8 has root access and ElementEX kernel installed but when i try to install viper4android it was asking to reinstall drivers again again . can you help me to figure this out ??????
I have finally found a method to get the Viper4Android working on HTC M8 (6.0)
1. Download viper4android apk from this Link - http://vipersaudio.com/blog/?page_id=48 (credit - zhuhang ) and install
2.Flash this zip in recovery Link - http://forum.xda-developers.com/showpost.php?p=64855827&postcount=5675 ( credit - Flar2)
3.Install drivers and reboot
4.Go to the system/etc and find the .conf file called "htc_audio_effects.conf" rename it to the "htc_audio_effects.bak" (this made file inactive but keep a backup in case something went wrong ) (Use Solid explorer or Root explorer for this )
4.Restart your device
5.Voila !! Now you have working Viper4Android
My Device Info
ROM - stock sense ( marshmallow)
Kernel - ElementX 7.0.0.11
Bootloader status - Unlocked (btw S-ON)

Categories

Resources