Hi,
I successfully installed XDAndroid 2.2 OS on my Diamond (DIAM100), but I have 1 problem so far. I need to use terminal/console emulator, but virtual keyboard doesn't work!
It works in every part of system (SMS, configuration, etc.), but when I run terminal emulator VK doesn't react. Hardware buttons works - I can go to new line (enter) by pressing circle. I try also ConnectBot and other version of terminal emulator and it's the same - I'm not able to write in command line.
Plz help!
defik665 said:
Hi,
I successfully installed XDAndroid 2.2 OS on my Diamond (DIAM100), but I have 1 problem so far. I need to use terminal/console emulator, but virtual keyboard doesn't work!
It works in every part of system (SMS, configuration, etc.), but when I run terminal emulator VK doesn't react. Hardware buttons works - I can go to new line (enter) by pressing circle. I try also ConnectBot and other version of terminal emulator and it's the same - I'm not able to write in command line.
Plz help!
Click to expand...
Click to collapse
I have the same problem, also got a D100. I have not tried other versions of Termina Emulator but installed the latest ROM (also reinstalled android 2.2 multiple times).
Any more have this problem?
I have the same problem with my Diamond Touch 2 (TOPAZ)
I tried everything but I can't type in the terminal emulator. Did you found a solution ?
Or anybody else an idea ?
Thanks
Hi,
Just plugged my XBox 360 joypad into keyboard dock to play some GTA. The light shows up on the controller indicating it's drawing power but the pad itself is not being detected by the tablet. No button presses or analogue stick movements are being registered. This worked fine previously on Honeycomb.
Is there an option I'm missing or is this not supported in ICS?
I am surprised you even got it to work with honeycomb, i yried everything on my tf 101 b80 with 8.6.5.21 and to no avail was unsucessful, if you could give details on how you got yours to work i would GREATLY APPRECIATE IT, as for your problem on ics, i wil keep scouring the forums for an answer and keep you posted if i find anything, i decided to wait a little bit before upgrading to ics---reason being i feel there are too many little bugs in the first release- how would you compare ics to hc? tia for your reply and answers
In honeycomb, I just plugged in my USB XBox 360 joypad and it worked, simple plug and play. Had used an unofficial one previously (replaced it due to an unrelated failure in the pad) which had everything working except the bottom two triggers and then bought an official Microsoft black USB 360 pad where every button worked. Was using it for GTA, Shadowgun, Riptide, Cordy and a bunch of emulators flawlessly.
Kinda gutted that it's not working on ICS now. Especially as my USB hard drive still detects fine (thankfully as I have a LOT of movies on there, lol).
As for ICS, loving it, much faster than previous, web browser works much better, being able to use Chrome is another big plus (works great, just a shame that it'll never support flash ). Glad to finally have inbuilt folder functionality as I prefer to keep all my apps sorted by category.
Love the Asus task manager widget and being able to swipe away running apps and notifications.
App drawer is much better organised and smoother, putting widgets in there was a great idea. Being able to force 2D GPU rendering is awesome as older apps now run smoother also due to now using hardware acceleration.
Videos still work fine using various video players such as Dice & MX. Oddly enough I noticed that the stock video player now plays standard def avi files (such as xvid and divx), pretty sure it didn't play those before.
Would have been nice to have face unlock but luckily I have Visiodon AppLocker installed. As a default lock screen it's useless as pressing home skips it, but it is much more convenient (and unskippable) than Asus App Locker for protecting apps, now protected apps can only be opened via a face unlock.
Anyway, back on topic now, has anyone had any success with a USB pad after ICS update?
I too have been unable to get my controller working post update to ICS
I will keep an eye on this forum so if anyone finds an answer please post or if I do I will post as well.
I did try a PS3 controller plugged in via USB and it worked fine but like the OP said the light comes on but nothing happens.
Download this follow instructions, map the dock keys on the app so it can recognize them on the controller (xbox and sixasis compatible)
Works on HC and ICS
surtrafl said:
Download this follow instructions, map the dock keys on the app so it can recognize them on the controller (xbox and sixasis compatible)
Works on HC and ICS
Click to expand...
Click to collapse
sucks to pay 4 bucks for something that was plug and play in HC
Problem is I also used the 360 joypad for Onlive and I'm pretty sure it won't work with that app.
In the meantime, I found a spare PS3 pad and using that now via bluetooth (see: http://forum.xda-developers.com/showthread.php?t=1514777), works very well. Just doesn't register button presses in Onlive, works flawlessly with everything else though (GTA, Shadowgun, etc).
i tried it for me, pluggin in the xbox 360 into the key dock. but the xbox button only blinks.
/dev/input list
EDIT 2: Fixed below.
To preface this: I'm not an Android developer, just a CS grad. I noticed on my ICS upgrade, the /dev/input directory only has event0 to event3, but I saw talk on other ROMs about a js0 device. If anyone still has HC or installs an HC-based ROM, could you do an 'ls -al /dev/input' and post the results here?
I can't imagine that Asus would intentionally break something that was present in previous firmwares.
EDIT: Can an HC user also post an 'ls -al /system/lib/modules' listing? Mine on ICS is:
android:/system/lib/modules $ ls
battery_rvsd.ko
bcm4329.ko
bcmdhd.ko
scsi_wait_scan.ko
Fixed.
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Didn't work with my USB Controller, still doing nothing.
RobertZFord said:
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Click to expand...
Click to collapse
Worked like a charm except for the script at the end. Dont know if I am doing something wrong but does not seem to run at boot. I just created a install-recovery.sh file with the script and copied to /system/etc is that not right?
Also any idea as to why these would have been removed since they were working in HC just prior to the update?
Perfect Solution tyvm
RobertZFord said:
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Click to expand...
Click to collapse
This is also worked for me, I thank you very much.
I was happily using a wired 360 controller with OnLive on my TF101 when it was running HC.
Then ICS broke it
This is not the perfect solution for OnLive mind. There is a mismapping of buttons compared to the HC implementation it seems.
I sense that the Back button on the controller is acting as a back button as opposed to how it used to act within OnLive and the ever blinking 360 button just takes me back 'Home to my launcher instead of bringing up the OnLive dashboard.
Other than that this is perfect until ASUS fix it fix it fix it.
More than likely one of the incredibly talented XDA devs will arrive at a solution prior to ASUS though.
Cheers
djasmithxda said:
This is also worked for me, I thank you very much.
I was happily using a wired 360 controller with OnLive on my TF101 when it was running HC.
Then ICS broke it
This is not the perfect solution for OnLive mind. There is a mismapping of buttons compared to the HC implementation it seems.
I sense that the Back button on the controller is acting as a back button as opposed to how it used to act within OnLive and the ever blinking 360 button just takes me back 'Home to my launcher instead of bringing up the OnLive dashboard.
Other than that this is perfect until ASUS fix it fix it fix it.
More than likely one of the incredibly talented XDA devs will arrive at a solution prior to ASUS though.
Cheers
Click to expand...
Click to collapse
You may want to try this for the onlive controller I ran across it trying to fix shadowgun
http://forum.xda-developers.com/showthread.php?p=23151895#post23151895
My question concerns the script it is working however I wanted to add to it so that a file would be pushed on each boot as well.
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
echo "cp /data/flash/libflashplayer.so /data/data/com.adobe.flashplayer/lib/" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
Does this look correct for pushing libflashplayer.so at each boot?
I'm unsure about the pushing of files at startup using install-recovery.sh
Beyond my scope of knowledge that one.
In theory I would say that it should work? Much like a batch script at the startup of windows?
I had reverted back to Revolver 3.1 but given your post had a crack with Revolver 4 again.
I insmod'd the xpad files and then copied the keyboard layout as per your post.
I still found the controller within OnLive to act as if the Back and XBox buttons were mismatched to how they acted previously under HC.
So I have reverted back to HC and Revolver 3.1
Other than a few bugs and a smoother launcher with folders I see no reason yet to upgrade to ICS? All works well for me on HC.
Cheers
The script is working like a charm for me.
Stock ICS rooted rom with xbox 360 gamepad
RobertZFord said:
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Click to expand...
Click to collapse
Any chance this could also work on the Team EOS nightlies? I tried this and it doesn't seem to fix my wired Xbox360 pad
EDIT: Well, I flashed over to Revolver 4.0.0 to test this using a stock-based ROM and it seems to be working fine now. I do I could get it working with one of the AOSP ROMs too though. In any event, thank you RobertZFord!
robert your script worked for me thanks. one glitch i found is when you hit any triggers while playing GTA3 you get stuck in look around mode and have to unplug and reconnect for it to work again
ics ARHD
ok so i am not good at adding script
can the script be made in to a zip and flashed i am clueless on even getting to this to work or just some serious help is needed i just flash android reveloution ics 3.01.1 and love it no probs but i just want my xbox controller to work
I really, really hate to bump this thread, but the script that guy posted isn't working for me. I tried it 2 times but it just won't work. Is it because I'm not on stock ICS but a custom ROM?
Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx
Fr4nz84 said:
Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx
Click to expand...
Click to collapse
Why the quotes around "official"?
Cifs and nfs support is built-in, there's no need for additional loadable kernel modules (you can check https://github.com/CyanogenMod/andr.../arch/arm/configs/msm8960_mmi_defconfig#L3091 )
If mount fails for you, try busybox mount.
Btw., after CM11 M2, Motorola msm8960 2012 devices were unified under moto_msm8960 moniker in CM11.
Later, after the release of the official KitKat update for only a subset of the devices being part of the moto 2012 family, xt897 builds went under moto_msm8960_jbbl (jellybean bootloader) unified builds.
So the latest CM11 builds for xt897 can be found here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
For CM12, the builds were separated again, so CM12 builds for xt897 can be found again under http://download.cyanogenmod.org/?device=xt897
A other problem?
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.
I've always accessed CIFS shares thru an app like ES File Explorer. Works fine.
Fr4nz84 said:
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.
Click to expand...
Click to collapse
CM11 M2 is quite old, so I can't be 100% sure it worked there, but I'm convinced that it worked fine even on such old build.
I mount cifs shares quite regularly on my xt897, so I guess I would have noticed if it was not working anymore in any milestone build.
Regarding SuperSU and BusyBox Free - there's no need to install anything like that, CM has built-in su and also busybox.
I'm on CM12 and I don't plan to restore CM11 any time soon (and certainly not M2, if anything it would be moto_msm8960_jbbl M12 or a recent moto_msm8960_jbbl nightly), but something like this has always worked for me:
Code:
su
mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I've just tested it (indeed with my own server path and user credentials) and it works fine.
To use busybox for mount, just replace "mount -o..." with "busybox mount -o..."
The stock CM busybox resides in /system/xbin , btw.
@arrrghhh good tip! Compared to AndSMB I can at least look at pictures without downloading with hand.
@kabaldan
You are totally right with cat /proc/filesystems I can see the Kernel supports cifs.
I had to install SuperSu because there was no su in terminal available.
After playing around, I was able to mount with:
mount -o username=franz,password=XXX,rw,nodev,relatime,default_permissions,allow_other -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
But it’s only available to the terminal where I executed the command. Do I have multiple root users?
I don’t know something in my system feels wrong.
Could there some other security policy I am not aware of?
It works now. It seems it was a update problem.
I wipe/clean the system with Open Recovery
removed all Files and Folders in /system (To remove old apps especially SuperSu)
And installed cm-11-20140104-SNAPSHOT-M2-xt897.zip again with Open Recovery
Now su is there on start and root is managed by the System. And I can mount cifs normally.
Whatever, now the shell seams not proper configured so I get this ^[[A^[[D^[[C for arrow keys, in su.
Also I can't get Link2Sd to work because mount give me constantly "invalid argument"( not more) even when I try it on console. Fells like it don’t want me to mount my second partition.
OK is a problem with the SD Card mount works normally. I tested it with another sd card.
Hello,
I am looking to watch my PS Vue subscription on my rooted Galaxy S7. I've tried to use RootCloak to no avail. Added com.snei.vue.android to the application list to cloak but PS Vue comes back with "Not available for your device" after launching. Obviously it's still seeing the device is rooted.
Any thoughts on getting this to work? The Amazon Fire TV forum says to rename xbin/su and superuser.apk but adb is giving me a "device or resource busy" when running the first mv command.
For reference, here is what Fire TV users are doing to get theirs working on rooted FTV's:
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
Thank you for your help in advance.
MrBaltazar said:
Hello,
I am looking to watch my PS Vue subscription on my rooted Galaxy S7. I've tried to use RootCloak to no avail. Added com.snei.vue.android to the application list to cloak but PS Vue comes back with "Not available for your device" after launching. Obviously it's still seeing the device is rooted.
Any thoughts on getting this to work? The Amazon Fire TV forum says to rename xbin/su and superuser.apk but adb is giving me a "device or resource busy" when running the first mv command.
For reference, here is what Fire TV users are doing to get theirs working on rooted FTV's:
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
Thank you for your help in advance.
Click to expand...
Click to collapse
Hi
Try with Magisk , it works for android pay.....
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I want to use mine also. It worked on 2 roms I tried. I'm using a oneplus 3.then I switched to a other rom (one which I want to keep) and it's giving me that error.
Fix for Playstation Vue Mobile on Galaxy Note 10
I came across this page in my search and thought I'd come back to share the fix I found using RootCloak. I can't share links yet, but you can find the video on Youtube by searching "How to Hide Root on Android with RootCloak" by AppReviewBros.
1. Install Xposed-Modules from the Play Store
2. Open it and select "Download"
3. Enter: RootCloak
4. Swipe the RootCloak page to the left and select the latest download.
5. Once it finishes, click "Install"
6. Activate the module (you should see that your device has a new notification; just open it and check the box)
7. Go back to the home screen and reboot the device
8. After it restarts, open RootCloak
9. Select "Add/Remove Apps"
10. Press the "+" in the upper right corner
11. Find and select "PS Vue Mobile"
12. Go to your device's Settings>Application Manager>PS Vue Mobile>Force Stop
13. Run the Vue app again, and it should work!
jshea001 said:
I came across this page in my search and thought I'd come back to share the fix I found using RootCloak. I can't share links yet, but you can find the video on Youtube by searching "How to Hide Root on Android with RootCloak" by AppReviewBros.
1. Install Xposed-Modules from the Play Store
2. Open it and select "Download"
3. Enter: RootCloak
4. Swipe the RootCloak page to the left and select the latest download.
5. Once it finishes, click "Install"
6. Activate the module (you should see that your device has a new notification; just open it and check the box)
7. Go back to the home screen and reboot the device
8. After it restarts, open RootCloak
9. Select "Add/Remove Apps"
10. Press the "+" in the upper right corner
11. Find and select "PS Vue Mobile"
12. Go to your device's Settings>Application Manager>PS Vue Mobile>Force Stop
13. Run the Vue app again, and it should work!
Click to expand...
Click to collapse
Great mate
Yes latest RootCloak is working for me too. Just signed up for this thing, and would have been a dealbreaker if this didn't work.
What I'm hoping to find out is, if I could set up some kind of proxy here to make the app think i'm ALWAYS home...
VPN on home router
Phreaker47 said:
Yes latest RootCloak is working for me too. Just signed up for this thing, and would have been a dealbreaker if this didn't work.
What I'm hoping to find out is, if I could set up some kind of proxy here to make the app think i'm ALWAYS home...
Click to expand...
Click to collapse
As far as i know, you would have to setup a vpn service on your home router and then tunnel to it whenever you were not at home. Then all traffic would look like it was coming from your home router. Of course your download speed while tunneling would be limited to your maximum upload speed for your service connected to the router providing the vpn. I have successfully tried this with my own hardware and it works. Just be aware of the download/upload caveat i mentioned.
oneleft.ak said:
As far as i know, you would have to setup a vpn service on your home router and then tunnel to it whenever you were not at home. Then all traffic would look like it was coming from your home router. Of course your download speed while tunneling would be limited to your maximum upload speed for your service connected to the router providing the vpn. I have successfully tried this with my own hardware and it works. Just be aware of the download/upload caveat i mentioned.
Click to expand...
Click to collapse
I do have 24Mb upstream, but between the remote streaming they do allow and also getting access to the various networks' apps (Fox Sports GO etc), I'm not sure it's worth bothering. I also still have my trusty Plex server as well.
MrBaltazar said:
Hello,
I am looking to watch my PS Vue subscription on my rooted Galaxy S7. I've tried to use RootCloak to no avail. Added com.snei.vue.android to the application list to cloak but PS Vue comes back with "Not available for your device" after launching. Obviously it's still seeing the device is rooted.
Any thoughts on getting this to work? The Amazon Fire TV forum says to rename xbin/su and superuser.apk but adb is giving me a "device or resource busy" when running the first mv command.
For reference, here is what Fire TV users are doing to get theirs working on rooted FTV's:
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
Thank you for your help in advance.
Click to expand...
Click to collapse
Well I found a quick fix for that everyone is over analyzing it if you have SuperSU watch my video
https: // youtu.be/4uG8YcNMNhI
It appears I can't post links yet so you'll half to just backspace the empty spaces
I got it working by flashing Magisk instead of SuperSU in twrp. Then just download the Magisk Manager in the play store then select PSVue under magisk hide in the app.