Develop Bugs

[modules] cifs.ko, md4.ko, nls_utf8.ko, stock [4.2 / 4.2.2] 3.4.5-g4e6298b / gaf9c307

I have managed to get CIFS working on stock Nexus 10.
It's quite a bit more problematic on the Nexus 10 than normal.
There are 2 main issues to deal with. Newer versions of the Linux kernel require a UNC variable to be passed to them and the current version of busybox doesn't do this. There is a patch out. I have extracted the patched busybox binary from craigacomez's AOSP Nexus 10 rom.
(Check it out here: http://forum.xda-developers.com/showthread.php?t=1998585 ). Otherwise it should work on the stock mount command if you specify the unc= mount option with the share.
The other issue is the multiuser stuff. If you execute the mount command from inside Terminal Emulator (or a script program) it looks like it mounts ok and you can 'ls' in the directory but it doesn't work for Android apps, they just see an empty directory but if you do it via a 'adb shell' it works fine in Android apps. My theory is ADB is outside of the multiuser stuff. adb actually ships on the device.
1) Unlock bootloader (fastboot oem unlock)
2) Flash recovery adb flash recovery whatever.img
3) Root device (flash CWM-SuperSU-0.98.zip)
4) Install BusyBox (from the market)
5) Copy md4.ko and cifs.ko to device. The files can go anywhere you like. In this example I will just use the root of the sdcard. Some people like them in /system/modules or /system/lib/modules
6) busybox mount -o rw,remount /
7) adb shell
8) Override /system/bin/busybox with the patched version (maybe move it first so it's backed up).
9) insmod /sdcard/md4.ko
10) insmod /sdcard/cifs.ko
11) busybox mount -t cifs -o username=MYUSER,password=MYPASS,unc=\\\\192.168.1.1\\storage //192.168.1.1/storage /data/media/0/cifs/Storage
You will need to manually preform the last 3 commands each time you reboot the device from a adb shell.
NOTE: You can probably get rid of the -o flags completely. In theory the patched version of busybox makes the UNC bit redundant. Possibly you can use the stock busybox with the UNC flag and avoid using the patched one totally. I have just included it to be sure.
Make sure you type 'busybox mount' not 'mount', by default they are different binaries. Otherwise you can remove the /system/bin/mount command and make a new one linking /system/bin/mount to /system/bin/busybox.
Possibly there is some way to get the mount working in the multiuser environment without requiring busybox. If you figure it out please tell ☺
Some threads on the issue:
http://forum.xda-developers.com/showthread.php?p=34397868#post34397868
http://forum.xda-developers.com/showthread.php?t=733490&page=6
http://www.mail-archive.com/[email protected]/msg17650.html
The modules are for 3.4.5-g4e6298b.
EDIT: I added nls_utf8.ko by request
EDIT2: Since adb comes on the device, it is possible to use it to connect to local host:
1) Install cifs modules to /system/lib/modules
2) Install Script Manager from the play store
3) Copy script to device
4) Start SManager
5) Find your script and open it.
6) Tick the su box
7) Hit save
8) Goto home sccreen
9) Add a 'SMShortcuts' widget to your home screen
10) "Add one script shortcut"
11) Choose your script
12) Optionally use this pretty icon ☺
13) Give it a nice name like "Mount Shares"
Here is a shell script...
Code:
#!/system/bin/sh
# Your settings here
USERNAME="USERNAME"
PASSWORD="PASSWORD"
IPADDRESS="192.168.1.1"
SHARE="storage"
MOUNT_POINT="/data/media/0/cifs/Storage"
# If you need to change the mount command edit this
MOUNT_CMD="\
mount -t cifs \
\
-o \
user=$USERNAME,\
password=$PASSWORD,\
unc=\\\\\\\\\\\\\\\\$IPADDRESS\\\\\\\\$SHARE \
\
//$IPADDRESS/$SHARE \
$MOUNT_POINT"
COMMANDS="\
insmod /system/lib/modules/md4.ko; \
insmod /system/lib/modules/nls_utf8.ko; \
insmod /system/lib/modules/cifs.ko; \
$MOUNT_CMD
"
# Starting ADB...
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb kill-server
adb start-server
stop adbd
start adbd
adb connect localhost
# Make sure we only use the first device (sometimes there is more than one)
SERIAL=`adb devices | head -n2 | tail -n1 | cut -f1`
if [ "$SERIAL" = "" ] ; then
echo "ERROR: Could not find ADB device.";
fi
echo Mounting share via adb...
adb -s $SERIAL shell su root -c "$COMMANDS"
# If you started adb, then stop it here for security:
adb disconnect localhost
stop adbd
setprop service.adb.tcp.port $PORT
start adbd
RESULT=`mount | grep $MOUNT_POINT`
if [ "$RESULT" = "" ] ; then
echo "Mounting failed..."
else
echo "Mounting sucess!"
fi
echo Done... You may close this script window.
EDIT3: Added usbserial.ko, option.ko and usb_wwan.ko
EDIT4: Some users have reported that the need to modify the script to get it working with their version of SU.
EDIT5: I have uploaded modules for 4.2.2, kernel 3.4.5-gaf9c307 but I haven't actually tested them myself (still on 4.2.1). Apparently the adb loophole has also been patched but it is possible to reenable it by putting a RSA key onto the device. Check out this set of instructions here.
EDIT6: I have updated to 4.2.2 on my Nexus 10 and can confirm the new modules work.
You must setup the adbkey or you will get a "device: offline" message. By default adb when adb first runs it tries to create the keys in the $HOME dir which is /data/.android, but the data directory isn't accessible by the 'shell' user.
I got it working simply by setting the HOME variable to /sdcard and restarting the adb server in the script then Android popped up a query (I have update the script above).
IMPORTANT: The Android Media scanner recursively scans folders for media to add the the database so it shows up in programs like Google Music. On large shares this can be a long process and use heaps of battery life. To prevent this add a blank file with the name ".nomedia" to the root of your mount points (or each individual share if you aren't used 1 folder for all your mounts). This will stop music showing up in programs though.
If you find that the device stops responding (the launcher might work but apps fail to load) or you get reboots (often after the previous bug) this is probably due to a bad wifi connection.

Is it posible to make a CWM flash file?

Great
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?

alias_neo said:
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
Click to expand...
Click to collapse
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg

craigacgomez said:
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
Click to expand...
Click to collapse
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.

Although I don't have nexus 10, I am having the similar mounting issue on my nexus 7 until I saw this post.
Advise about "adb shell" really helps me resolve the multiuser issue.
Thanks for sharing.

Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!

H3g3m0n said:
1) Unlock bootloader (adb oem unlock)
Click to expand...
Click to collapse
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)

momulah said:
Is it posible to make a CWM flash file?
Click to expand...
Click to collapse
Not a high priority right now as currently you need to do the manual adb shell stuff by hand to get things mounted, a little extra setup work isn't a huge difference.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
Are you mounting in a 'adb shell' or locally in something like terminal emulator? My OTG cable won't be here for a while so I can't really test myself.
weasal said:
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
Click to expand...
Click to collapse
Posted, haven't tested it but it seemed to insmod fine.
espionage724 said:
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
Click to expand...
Click to collapse
Yeh typoed, i'll fix that now.
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.

alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
I've been working on getting OTG support natively in my AOSP based custom ROM and I have had some success... check out my ROM for details

H3g3m0n said:
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
Click to expand...
Click to collapse
Just wanted to thank H3g3m0n as I was able to successfully mount over adb. Also came up with a workaround to bypass connecting to a PC, grabbed the arm fastboot binary from this thread and installed it on my nexus 7. Used it to connect wireless adb on the 10 and ran the mount commands on the 7.

H3g3m0n said:
Posted, haven't tested it but it seemed to insmod fine.
Click to expand...
Click to collapse
Thanks, I'll give it a try!

You might find my posts #156 and #162 at http://forum.xda-developers.com/showthread.php?t=1781411&page=17 helpful.

Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium

spdwiz18 said:
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Loadable_kernel_module

craigacgomez said:
http://en.wikipedia.org/wiki/Loadable_kernel_module
Click to expand...
Click to collapse
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium

spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
These modules are needed to enable support for CIFS (Windows share) mounts...

spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
Basically you can setup a shared folder from a remote computer. It allows you to have files on another system accessible as if it was part of the internal storage in the device.

Just found out that Android ships with the adb binary on the device itself (after crosscompiling it myself :/, oh well the experience was useful).
It should be possible to setup a script to start the adb server, connect to the localhost and execute the mount without too much difficulty.

Ok, added a script and instructions to the front page for simple on tablet mounting.

[Q] Mounting network folder as a local directory

Hello all.
I'm running my FireTV as an entertainment system. It's rooted with Kodi, Mobdro, RetroArch, ePSXe w/ Sixaxis PS3 as controller etc.
Since the FTV only has 8GB of local storage, I was wondering if there's a way to mount a samba share into a local directory so I can load emulator games without transferring them. Majority of the emulators only scan ROMs / ISOs etc on local directories.
Unfortunately, apps like cifsmanager and mount manager are broken since android 4.3 I think.
Thanks in advance.

Maybe this might be helpful:
http://forum.xda-developers.com/fire-tv/general/run-script-firetv-boot-t2986158

This works for me:
Code:
busybox mount -t cifs //my.ip.address/my.share /sdcard/somedir -o username=guest

jocala said:
This works for me:
Code:
busybox mount -t cifs //my.ip.address/my.share /sdcard/somedir -o username=guest
Click to expand...
Click to collapse
Hello there.
Thanks for the help. But do you mind answering a couple of Qs because I'm a filthy nub when it comes to this.
1. Where do I run this command? Do I connect to my FTV using adb and just type this in?
2. How would this work if my Samba share has spaces on it?
3. Do I run this everytime I reboot my FTV?
Thanks again

Squalll13 said:
Hello there.
Thanks for the help. But do you mind answering a couple of Qs because I'm a filthy nub when it comes to this.
1. Where do I run this command? Do I connect to my FTV using adb and just type this in?
2. How would this work if my Samba share has spaces on it?
3. Do I run this everytime I reboot my FTV?
Thanks again
Click to expand...
Click to collapse
1. As posted, it would be run from the command line, from a root prompt. I use busybox, so you need that as well for my method.
2. I stay away from directories with spaces, but it may work with quotes, idk, haven't tested. It works with embedded spaces if they are inclosed in quotes: e.g:
Code:
busybox mount -t cifs "//192.168.1.200/media/my folder" /sdcard/cifs -o username=guest
3. Easiest thing to do would be to put it into a script that runs at boot. That's the approach I'm taking with my program adbFire. I'm testing this functionality now.

oops.... guess that was already answered. Anyhow, can't leave text field blank so; Yeah this works great. I got mine all set up with Advanced Launcher kodi addon. Tested with a few emulators and ISOs load near instantly

Thanks for the replies. Though I noticed something peculiar and I would like some insight.
I noticed that after I haven't used the FireTV for a while. Maybe 24 hours. The mounted folder kinda "disappears" for a bit but come back. For example, I use ES File Explorer and go to /mnt/obb/ and it will just keep "Loading" until I just press back. Same thing when I used adb shell, cd to /mnt/obb/ and use ls. It just stays there until I force exit. But after a waiting around a bit like 10 mins or so, the mounted folder shows up no problem.
It kinda feels like you need to ping /access it or something, fail, wait a bit then it shows up.
I hope what I said isn't too confusing. If it was I apologize.

[Q] Problem sideloading kodi.tv

I am having issues. The first time I tried this I thought it was a success as I went through the steps and got the loading screen on the fire tv to come up. I waited for about 10 minutes and then the firetv reset but Kodi did not install.
Now I am trying to do it and when I hit enter after the string to sideload the .apk nothing happens. I get no response in the terminal and it just goes to the next line. I cannot figure this out for the life of me.
I am using terminal on a mac. This method http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/
please help.

Try the additional "-r" option during install ('-r' means reinstall the app, keeping its data).
For e.g.:
Code:
adb install -r kodi.apk

Calibaan said:
Try the additional "-r" option during install ('-r' means reinstall the app, keeping its data).
For e.g.:
Code:
adb install -r kodi.apk
Click to expand...
Click to collapse
Thanks - I am brand new to mac so this is new to me. So basically my string would be
./adb install /Users/YourUserName/Desktop/-r filename.apk
?

seagood3 said:
Thanks - I am brand new to mac so this is new to me. So basically my string would be
./adb install /Users/YourUserName/Desktop/-r filename.apk
?
Click to expand...
Click to collapse
No. The option "-r" must be used before the complete path to the APK file. Have a look:
Code:
./adb install -r /Users/YourUserName/Desktop/filename.apk

Calibaan said:
No. The option "-r" must be used before the complete path to the APK file. Have a look:
Code:
./adb install -r /Users/YourUserName/Desktop/filename.apk
Click to expand...
Click to collapse
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.

seagood3 said:
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
Click to expand...
Click to collapse
Couldn't you use adbfire on your mac..... it's available from this link http://forum.xda-developers.com/showthread.php?t=2786505 it might make things a little easier...

slackbladder said:
Couldn't you use adbfire on your mac..... it's available from this link http://forum.xda-developers.com/showthread.php?t=2786505 it might make things a little easier...
Click to expand...
Click to collapse
I haven't used that because I am running into all kinds of issues. First I got the "Can't create log file" error. I googled that and see that I need to drag the app onto the desktop or into the applications folder. The problem is when I try to move it I get another error message "The operation can’t be completed because you don’t have permission to access some of the items". I feel like such a newb with this Mac. I have no clue how to troubleshoot.
any help?

Any chance you have a Windows PC connected to your network that you can try? I did this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-windows/) and had no issues.
If you can get ES File Explorer onto the FireTV, then you can go to Network/Cloud and add an account, connected it to a Dropbox account, then just download apks and open them from ES File Explorer, you won't need the PC or adb any more.

seagood3 said:
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
Click to expand...
Click to collapse
Can you even connect to the aTV?
Try some ADB commands to see if ADB does really work:
Code:
adb devices
This should list all via ADB connected devices. If the list is empty you´re not connected.
When your device is connected try some basic shell commands:
Code:
adb shell
This opens a bash shell. Within this shell type
Code:
ls
and the directory content of the actual folder should be listed.
ADB shell can be left with:
Code:
exit
If this isn´t working, check your ADB version you have installed and try to install a newer/other one. I had such an issue once on Windows with an Android tablet which couldn´t be connected with the ADB version I had already installed on my PC so I took another ADB version and it worked. Of course this shouldn´t be but it seems that this can happen.
Another hint might be your problems regarding adbfire. Perhaps your user restrictions prevent ADB from proper working. I´m not firm on MAC´s but I think they support the "sudo" command (explanation: http://en.wikipedia.org/wiki/Sudo). So try your ADB commands again with an additional sudo before similiar like this:
Code:
sudo adb install kodi.apk

I can't figure this out - I am following this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/) perfectly and I got it to work the first time but it just didn't complete it for some reason and now every time when I hit enter on the last step nothing happens.
I can't use the adbfire app because of the other issue.
WTF? why isn't the method through terminal working?

seagood3 said:
I can't figure this out - I am following this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/) perfectly and I got it to work the first time but it just didn't complete it for some reason and now every time when I hit enter on the last step nothing happens.
I can't use the adbfire app because of the other issue.
WTF? why isn't the method through terminal working?
Click to expand...
Click to collapse
I don't know...on mac you need to use ./ unless you configure it otherwise so to connect I'd type ./adb connect myipaddress
If you are connecting then you have adb working. I use adbfire but here's what I'd do...
I like keeping my adb folder with platform tools on my desktop. Put the apk you want to install in that folder
type "cd" <space> then drag the whole folder into the terminal--hit enter
now type ./adb connect youripaddress--hit enter
if it says connected type ./adb install<space>then drag the apk from inside your adb folder right into the terminal--hit enter
If you did it right nothing will happen instantly. It depends on how fast your connection is. Wait up to 5 minutes I'd say and you'll either get a success message of an error. If it's the latter, post it here.

Did you read my previous topic and tried what I´ve written?
Forget this Howto since it is just a general guideline and it can´t help you with your actual problem since it is more or less a first time installation guideline but you have already had a previous installation which makes the difference. It can also not deal with restrictions on your system side for e.g. if ADB wouldnt´be allowed to access USB.
If you´re sure that your system is not restricted anyway and ADB should work and if you still prefer to work only with this guideline do a factory reset within your FireTV. This should set the box in a state back again where this guideline should work how it is intended.
Or try SPMC from Amazon App Store which would be the easiest way:
http://www.amazon.com/Semperpax-SPMC/dp/B00MK49LL8

Playstation Vue on Fire TV and Fire TV Stick

I'm a cord cutter, so this option appeals to me. I downloaded the app on my Fire TV, but as soon as I run it, it says, "Playstation vue not available for your device."
Anyone else try it yet? I signed up for a trial, but I can't even get the damn thing to work yet. I'm hoping it's not because my Fire TV is rooted.

I haven't tried it yet... But.. You may not be able to use it if your not in one of the few cities it is currently limited to. Look on sonys site.. There is a map. Try using a VPN to appear to be in a supported city like Chicago.. Cause I live in Wisconsin and Sony can suck my nuts. Lol
Sent from my A0001 using Tapatalk

LittleBear1981 said:
I haven't tried it yet... But.. You may not be able to use it if your not in one of the few cities it is currently limited to. Look on sonys site.. There is a map. Try using a VPN to appear to be in a supported city like Chicago.. Cause I live in Wisconsin and Sony can suck my nuts. Lol
Click to expand...
Click to collapse
I already signed up for the free trial. The app just tells me it's can't be used on my device (not location). There's nothing to verify zip codes.

I'm having the same problem with a rooted FTV1. It works fine on my non-rooted FTV Stick.

Can someone extract the APK and post it.

esny23 said:
Can someone extract the APK and post it.
Click to expand...
Click to collapse
Here you go:
https://onedrive.live.com/redir?res...4316&authkey=!AF6D-sAh6Y_HAJI&ithint=file,apk
BTW, I installed the latest RootCloak and add this app to the configuration. I enabled it in XPosed and rebooted. Still won't run correctly.

I tried Hide My Root and that didn't work either. I started looking through the apk and it seems it is looking for any of the following files:
/system/app/Superuser.apk
/sbin/su
/system/bin/su
/system/xbin/su
/data/local/xbin/su
/data/local/bin/su
/system/sd/xbin/su
/system/bin/failsafe/su
/data/local/su
Then it also runs "/system/xbin/which su" and checks the output. I'm not home now to try renaming these files but I'll try tonight and report back.

RootCloak allegedly blocks apps' access based on keywords that include "su" and "Superuser" but it doesn't allow the app to work.

Renaming /system/xbin/su and /system/app/Superuser.apk worked. I can now run PS Vue on my rooted FTV, confirming it's just looking for those files.
---------- Post added at 12:47 AM ---------- Previous post was at 12:03 AM ----------
I think rootcloak should do the trick, but it's failing to load on my Fire TV, check your Xposed log file and see if you get this too:
Code:
Nov 17, 2015 12:29:39 AM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'bueller-user 4.2.2 JDQ39 51.1.6.3_user_516012020 test-keys' with fingerprint 'qcom/bueller/bueller:4.2.2/JDQ39/51.1.6.3_user_516012020:user/release-keys'
Loading modules from /data/app/com.devadvance.rootcloak2-1.apk
Loading class com.devadvance.rootcloak2.RootCloak
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at dalvik.system.DexFile.defineClass(Native Method)
at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:211)
at dalvik.system.DexPathList.findClass(DexPathList.java:305)
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:62)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:421)
at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:386)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:120)
at dalvik.system.NativeStart.main(Native Method)

esny23 said:
Can someone extract the APK and post it.
Click to expand...
Click to collapse
rveety said:
Renaming /system/xbin/su and /system/app/Superuser.apk worked. I can now run PS Vue on my rooted FTV, confirming it's just looking for those files.
---------- Post added at 12:47 AM ---------- Previous post was at 12:03 AM ----------
I think rootcloak should do the trick, but it's failing to load on my Fire TV, check your Xposed log file and see if you get this too:
Code:
Nov 17, 2015 12:29:39 AM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'bueller-user 4.2.2 JDQ39 51.1.6.3_user_516012020 test-keys' with fingerprint 'qcom/bueller/bueller:4.2.2/JDQ39/51.1.6.3_user_516012020:user/release-keys'
Loading modules from /data/app/com.devadvance.rootcloak2-1.apk
Loading class com.devadvance.rootcloak2.RootCloak
java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation
at dalvik.system.DexFile.defineClass(Native Method)
at dalvik.system.DexFile.loadClassBinaryName(DexFile.java:211)
at dalvik.system.DexPathList.findClass(DexPathList.java:305)
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:62)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:421)
at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:386)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:120)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
How do I get the log? BTW, I'm using 2.7 experimental1

Sizzlechest said:
How do I get the log? BTW, I'm using 2.7 experimental1
Click to expand...
Click to collapse
Open the Xposed installer app and open Logs. I'm using the same version.

rveety said:
Open the Xposed installer app and open Logs. I'm using the same version.
Click to expand...
Click to collapse
Yes. Same error here. I uninstalled 1.5 and installed the older RootCloak 1.4. I don't get an error in the log, but PlayStation Vue crashes as soon as it's launched.

Would anyone be able to provide the newest version of the APK? Has anyone tried using this on a Nexus device?

rveety said:
Renaming /system/xbin/su and /system/app/Superuser.apk worked. I can now run PS Vue on my rooted FTV, confirming it's just looking for those files.
Click to expand...
Click to collapse
Hi,
How did you change /system/xbin/su from read-only? I've been trying to set permissions or just rename using mv but it's not working.
EDIT:
got it working now with the following
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/Superuser.apk /system/app/XSuperuser.apk

Tweek- said:
Hi,
How did you change /system/xbin/su from read-only? I've been trying to set permissions or just rename using mv but it's not working.
EDIT:
got it working now with the following
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/Superuser.apk /system/app/XSuperuser.apk
Click to expand...
Click to collapse
Thanks for posting the instructions, this worked on my setup. Any downsides to leaving these changes permanent on the system?

dailo_wai said:
Thanks for posting the instructions, this worked on my setup. Any downsides to leaving these changes permanent on the system?
Click to expand...
Click to collapse
I'm far from an expert so i don't know for sure but from what I can tell you just need to call su xsu in the future when ssh'd into your box if you want to access that command

Does this cause issues for apps calling for superuser permission? I got it working but now es file explorer can't get root permissions.

Worked for me except im using SuperSu.apk
My commands:
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/SuperSU.apk /system/app/XSuperSU.apk

nineismine said:
Worked for me except im using SuperSu.apk
My commands:
Code:
adb shell
su
mount -o remount,rw /system /system
chmod 761 /system/xbin/su
mv /system/xbin/su /system/xbin/xsu
mv /system/app/SuperSU.apk /system/app/XSuperSU.apk
Click to expand...
Click to collapse
Any ideas how to get this to work on a rooted firestick? I got it to work on both of my boxes and just rooted my stick and this doesnt work. I assume its a minor change, but not sure where to go from here.

So, I have been connecting to Vue behind a DD-wrt router so that I could access Chicago local networks. I don't live in an area where I can receive local channels OTA.
I have no trouble with the connection through Fire Sticks, but the PS4 and Fire TV box will not allow for authentication. I imagine this is because the hardware in those devices allows for a more complex authentication process and Sony is turning back folks from accessing their servers through VPN's.
Here's what happens:
Fire Sticks when connecting via VPN router - works like a charm.
PS4 and Fire TV box when connecting through VPN router - "There was an error during authentication. Please try again later. Press EXIT to close application."
Here's the part that may tell us something: ALL of the above devices, when connecting through my regular, non-VPN router, all return the message stating that I am currently not connecting in my home area, if I click "yes" a new home area will be established and I will no longer be able to use the old area. Again, all of the devices do that, including the Fire TV box and the PS4.
The question I have for the hive mind is: assuming it's an authentication issue, can I defeat or trick the authentication process? Is there a way to fool Sony's servers into thinking I am not, in fact, behind a VPN?
Thanks for the thoughts, folks.

Is it possible to block AFV stick from updating ?

I've seen that Amazon firesticks have updated their software which has effected Firestarter. I just wanted to know three things:
Is it possible to block amazon updates? I've got a virgin superhub router.
Is there a way to backup the entire firestick and not just Kodi?
Can you previous firmwares versions be restored/downgraded on firesticks?
The last thing I think anyone wants is for an update that wipes of Kodi altogether :crying:

Yes, you can block updates. See my guide here: http://www.aftvnews.com/block
If the device is rooted and running TWRP custom recovery, you can backup and restore the entire device at once. There is no TWRP for the Fire TV Stick currently, but rbox is working on it. For now, all you can do is backup individual files and folders, like app data, but depending on where the data is stored, you may still need to be rooted. App data in /sdcard can be backed up without root, but app data in /data requires root to access.
You can only downgrade if the device is rooted and running TWRP custom recovery. There is an old downgrading method that requires root and uses the default recovery, but I have not tested it on Fire OS 5 devices.

Hey thanks for that, I think I managed to prevent the firestick from any updates using adb + terminal from you pointing me on the right track.

hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'

scofield27 said:
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
Click to expand...
Click to collapse
I'm on a firestick with 5.0.5 and ran the command no problem, and disconnected properly. I had issues though after a few fire stick reboots where my firestick was connected to my router and had an ip, but had no internet connection. Basically it seemed like the command blocked the firestick from doing anything. I used the unhide command and rebooted a few more times and then ran the command to hide it once more and rebooted a few more times. Now it appears it is blocking updates and i can still use kodi.
I also have been having router issues, so it could be my router.

AFTVnews.com said:
Yes, you can block updates. See my guide here: http://www.aftvnews.com/block
If the device is rooted and running TWRP custom recovery, you can backup and restore the entire device at once. There is no TWRP for the Fire TV Stick currently, but rbox is working on it. For now, all you can do is backup individual files and folders, like app data, but depending on where the data is stored, you may still need to be rooted. App data in /sdcard can be backed up without root, but app data in /data requires root to access.
You can only downgrade if the device is rooted and running TWRP custom recovery. There is an old downgrading method that requires root and uses the default recovery, but I have not tested it on Fire OS 5 devices.
Click to expand...
Click to collapse
Hi Aftvnews, how do you delete the update cache on the firestick? I got a new firestick but it was downloading update before I could stop it. It's there but if I can get into the folder to delete it that would be great. I saw mention how to do it but didn't show the command lines. Thanks!

scofield27 said:
hi AFTVnews.
is the adb shell pm hide com.amazon.device.software.ota command still works ? i have tried yesterday and it worked fine, and today i try again the same commend on second device (fire stick) and i get : unknown command 'hide'
Click to expand...
Click to collapse
The command only works on software version 5.0 and up. If that Stick is on 54.1.2.3 or older, then the only way to block updates is externally through a router or OpenDNS (method 3 and 4 in my guide).
eore227 said:
Hi Aftvnews, how do you delete the update cache on the firestick? I got a new firestick but it was downloading update before I could stop it. It's there but if I can get into the folder to delete it that would be great. I saw mention how to do it but didn't show the command lines. Thanks!
Click to expand...
Click to collapse
Your Stick must be rooted to delete the update file from /cache. Here's how to do it:
Code:
adb shell
su
rm -f /cache/*.bin

AFTVnews.com said:
The command only works on software version 5.0 and up. If that Stick is on 54.1.2.3 or older, then the only way to block updates is externally through a router or OpenDNS (method 3 and 4 in my guide).
Your Stick must be rooted to delete the update file from /cache. Here's how to do it:
Code:
adb shell
su
rm -f /cache/*.bin
Click to expand...
Click to collapse
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
---------- Post added at 02:09 AM ---------- Previous post was at 01:50 AM ----------
eore227 said:
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
Click to expand...
Click to collapse
Ok I have root access I typed adb shell then I did su to get root access. Now it shows [email protected] montoya: #
After the # i typed rm -f/cache/*.bin
Is this correct? I don't see anything happened

eore227 said:
Hi aftvnews can you show me how this command works for a mac? I just rooted a fire stick right now using king root. It says root was sucessful but I don't want to reboot as the update is on there. If I could delete this update before the update that would be good but I'm using mac terminal and typed in your command but it's not working. Thanks
---------- Post added at 02:09 AM ---------- Previous post was at 01:50 AM ----------
Ok I have root access I typed adb shell then I did su to get root access. Now it shows [email protected] montoya: #
After the # i typed rm -f/cache/*.bin
Is this correct? I don't see anything happened
Click to expand...
Click to collapse
First, be sure there is a space after the "f"
You won't see anything come up on the screen. I also just learned a few hours ago that there is an alternate location for the update file. So do the following to clear out both locations:
Code:
adb shell
su
rm -f /cache/*.bin
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin

Perfect that did the trick the update was deleted. I rebooted and still have root and uodate is gone. Thanks!