Apps that work on phone but not Android box - Android Q&A, Help & Troubleshooting

I came across this issue 3 or 4 years ago. I searched internet and there were some discussions saying that there is a file (or profile) in Android that contains info on the type of device it is running on. The reason for the Apps not running was because the software (OS or Apps) detected that it is not on the right device. One circumvention is to modify the file (or profile) on the Android box to fool the software that it is running on the right device (e.g. a phone). This kind of modification require root access. At that time, I did not have any spare device to risk with. I did not write down the details. Now I have a spare android box and like to revisit the problem. But I am not able to find the info anymore. I hope my memory is correct. I am not sure if this is still true with the current Android version. If anyone has seen this before, can you kindly point me to the right direction.

There are some protections in app like RootBeer or PiracyChecker that check few things that crash certain apps on rooted phones and android emulators.
Check examples: is there superuser.apk, is there /system/bin access, is there SU binary or magisksu, is there Android_x86/Android_x64/MoboGenie/Droid4X in signature in build.prop, or hacking apps like AC Market, Black market, Lucky patcher etc.

Related

[Q] Azpen A701 Tablet

Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
drivers
I found the correct address for the drivers for this tablet, and 2 others from Azpen.
www.mediafire.com/azpensupport
The links on their webpage incorrectly spell mediafire and also include .com in the last part of the link.
Note: I recently got an email from Azpen telling me the exact same url that I had already figured out. Their email is about week to a week and a half after I sent them a request for the proper address. Also, as of the time I am posting this update, they have not corrected the address on their website.
Tried methods
I have tried SuperOneClick which reports that the system is rooted, but ADB Wireless says it is not.
I have tried Bin4ry's Root Many Android! (options 1, 3, and G) and briefly got temp root on option 3 but I lose wireless functionality (I get one or the other message from ADB Wireless (no root or no wireless), verified that Wireless connection has been turned off and won't turn back on until reboot which loses me the root again).
Retries
Ok, finally rooted the Azpen A701.
What I did:
First, I went back to SuperOneClick, and choose Unroot to reverse anything it did.
Retried Bin4ry's Root Many Android! v31, option 1 (new standard method), test, failed, unroot, 3 (old method), test, failed, unroot, then G (Google Glass method), test, WORKED this time.
Verified by using a root browser (can see files/folders(subdirectories) in /data after giving permission), a root checker (note: do not turn on SuperUser's Autoanswer, gives false information from some checkers), and ADB Wireless works while in range of a wireless router/source.
I am guessing that somehow the leftovers from SuperOneClick were affecting my results with Bin4ry's collected scripts.
Props to all that developed each of those programs and scripts.
I don't know if anyone will be seeing this but I hope it helps anyone needing the info.
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
no idea
BizarreMan said:
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
Click to expand...
Click to collapse
I have absolutely no idea. The only additional rom I have seen ANYWHERE is the Jellybean update for it (see driver link above). This seems to not be a very popular tablet to work with, going by the fact I received no help from anyone here. All research on this so far has been done by me. I stumbled on to Bin4ry's rooting method by accident. I'm not a ROMer, I don't know how to build one. Also I don't know which ROM backup method to use on it/will work with it.
Alright
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
trying again...
BizarreMan said:
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
Click to expand...
Click to collapse
It may have been the sequence I used. Tried SuperOneClick several times (as above it said tablet was rooted but several apps said it wasn't) which installed su, busybox, and superuser. Then found Bin4ry's method, got temp root (tryied 1, 3, and Glass). Then went back to SuperOneClick and unrooted, returned to Bin4ry's and finally got it with Glass method.
Don't know if that helps
Well
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Good to see that your were able to root.
BizarreMan said:
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Click to expand...
Click to collapse
So I think we can safely say that using both methods together + patience will root this tablet (don't know why one or the other wouldn't do it).
Not having any luck
CyberSpiderPrime said:
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
Click to expand...
Click to collapse
I have been trying to root AZPEN A701 for the past week, I have tried everything written on this forum. Any help PLEASE!
clean slate
Are you willing to do a full restart on the tablet (factory reset)? I had to do that before my root took, as I found on other systems that I have rooted some programs you load can interfer with rooting. Save any personal data before you do this, programs can be reinstalled from Google Play or (hopefully you saved them if you downloaded them) your computer
Factory reset:
Press and hold up volume button then press and hold power button. The screen will remain black (no backlight)
Wait 4 seconds then release both buttons (backlight will come on). Shortly the android on it's back with the open torso (the sick android) will be displayed.
Press the down volume button. You should see 5 options available- You are now in the System Recovery program.
Using the up or down volume button to highlight an option then press power to select the option.
1) select Wipe Cache Partition
let the unit reboot, then turn it completely off
reenter System Recovery again.
2) select Wipe data/factory reset
let the unit reboot, then turn it completely off
The system is as clean as it is going to get now.
On your pc (don't know for MAC's) download the drivers, Android programs needed (Android Debug Bridge -ADB- is part of the Android Development kit and some Java Development Kits), and both SuperOneClick and Bin4ry's root software. Install all software and drivers as per their instructions. Run SuperOneClick and Bin4ry's root programs. Busybox and SuperUser will be added automatically by these root programs.
While having wifi and internet access (McDonalds anyone?), re-sign up for Google Play (sorry, but the settings got wiped earler). Go to Google Play and let all the programs update. Update Busybox and SuperUser if needed/possible.
Download any root enabled file system browser (FSB) (permission will have to be granted in program to use root functions) - I used Ghost Commander for mine. It may take a bit to find it in the directory structure for the FSB you downloaded but you need to get to the root system folder.
Ghost Commander has a Local Storage option press it and an new list of folders/files will be displayed, move to the previous folder level (double dots at the top) and give permission to move to a system folder, move to the previous folder again to get to root directory, "/mnt" is the directory you just came out of and is highlighted but you will be at the root of the file system.
Enter the "/data" directory. If you can see files listed there, you have root; if not rooting attempt failed.
Once rooted, doing a system cleaning and Factory reset will not remove root but will remove SuperUser and Busybox (re-run one of the root programs to re-install then update the next time you are on the internet/web). Updating/upgrading the rom will remove root if the rom does not have root activated - I don't know of any custom roms for this tablet (there is a Jellybean upgrade in the Azpen website, if they haven't updated to the correct web address then use the one I listed on the front page, mediafire is spelled wrong in the address). Nandroid level system backup is not available yet for this tablet to my knowledge.
For several reasons, do not turn on SuperUser's automatically give permission option (the one that affects all programs), except on a one for one basis: 1) some root testing programs will fail if this option is turned on, 2) security: turning this on will allow ALL programs - including some malicious ones - to have super-user rights, 3) you will get to know which programs are asking for root permissions beforehand not after, you may want some to have automatic access (like DroidWall in my case, a firewall) and not others.
Also other information that can be useful:
/sdcard does not refer to the removeable SDCard but to the internal user data area. All programs that can be moved to a SDCard (like by Apps2SD) will be moved to this directory by default (some may allow re-assignment of the destination location) instead of the removeable SDCard (blame Azpen, it was their decision to use the directory and name that way). On most other systems /sdcard is the removeable SDCard.
/extsd is the removeable SDCard, when installed, maximum size is 32Gb.
/usbhost1 is for any usb flashdrive connected by a USB-OTG cable (OTG means On-The-Go, special usb cable that puts the tablet into host mode, similar to connecting a flashdrive to a computer, the cable is not a standard Data Connect/transfer cable, one USB-OTG comes with this tablet). Note about USB-OTG cables: if one is connected you can connect either a flashdrive, usb keyboard, usb mouse, combo keyboard/mouse unit, or a powered usb 2.0 hub. Only one flashdrive can be connected at a time (anyone know of downloadable software that would allow 2 or more? I know some modified kernels can allow more than one) so with a hub you can connect a flashdrive + keyboard + mouse (I use the RII wireless combo keyboard and mouse with mine). Maximum size appears to be 8GB, format must be FAT32; will be testing with a 16GB key shortly.
Azpen A701 and Jelly Bean
Shortly after I wrote the above I had to re-flash my tablet, but Azpen had deleted the ICS image (after a request it was restored to the site, get it while you can) and had to flash Jelly Bean. I found there were troubles with this image.
First: I could not write to either the external SDCard (called extsd) nor an attached USB flash key; reading was unaffected. I found this out when I attempted to reassign my backup location to the external sdcard and it was unable to create the directories.
Second: I couldn't find a rooting program.
After a little research, I found that the external media had not been given R/W permission in the platform.xml file - I could actually navigate the FS and read the file even without root.
Also I finally found after 2 days of searching a root program, VROOT, http://forum.xda-developers.com/showthread.php?t=2434453, that would work. Be prepared to deal with Chinese for a little bit and follow the instructions on that page (press the buttons to see screenshots). The superuser app needed to fix/replace the Chinese app is SuperSU (Google Play) which supposedly fixes problems found with other superuser apps. Once you have downloaded SuperSU, had it download/update its binaries and have rebooted, you will have to disable the Chinese Superuser app as you are unable to uninstall it using the app manager: I located it by its icon (shield with cog) in /system/app and appened '.old' to the name: "Superuser.apk" => "Superuser.apk.old'. I didn't use Titanium Backup as suggested because I am not a fan of the program .
platform.xml is located in /system/ext/permissions. After you have root, open platform.xml in what ever text processor you want locally or transfer it to your computer and work with it. You will have to add '<group gid="media_rw">' to the 'WRITE_EXTERNAL_STORAGE' group, on the line after '<group gid="sdcard_rw">' (don't type the single quotes but the double quotes are needed) and write the file back to its location (need root for that, adb pull/push may be possible to fix this). Remember on this tablet, sdcard refers to the internal user storage, media_rw will give permissions to the extsd (external sdcard) and USBHost1 (using included USB-OTG cable and a flash drive). I rebooted the tablet and tested the RW state of extsd, and voila, it now is write capable.
I wish there was more aid on this tablet but since it is not mainstream (not made by a big manufacturer like LG, Motorola, Samsung, etc.) I doubt that it is coming (I am not a ROMmer but have been using computers since the 80's, so I know a few tricks and am always learning). I will keep adding info as I find or fix it.
I will probably go back to ICS as some of my programs are not working right, and JB is sluggish.
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
johncro13 said:
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
Click to expand...
Click to collapse
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
comstar said:
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
Click to expand...
Click to collapse
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
cheeb said:
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
Click to expand...
Click to collapse
Glad it worked for you! I started this thread for the A700 http://forum.xda-developers.com/showthread.php?t=2532464 - No activity in it yet. But if you come across anything good post it over there.
Sent from my Transformer TF101 using XDA Premium HD app
Update
I am glad to see that others are taking an interest in this tablet.
I found 2 methods that worked and am glad that others are finding more.
Now if I can get the boot loader cracked I could finally make a nandroid copy and save myself 4+ hours restoring everything when it goes wonky. This has happened twice- OS partition fills up (and don't know why) and the device resets to near factory reset level (even some of the factory apps are missing) and won't install anything but the smallest of apps which are deleted on the next reboot; the only solution is to re-flash the tablet. Note that I have gone back to using ICS as JB has other problems (external media including its own sdcard partition is not rw enabled for one).

[Q] Issue with installing an app

Hi everyone,
I'm new on xda and I come here because I struggle to install this app on my rooted Galaxy S4 with CyanogenMod 11: "Paiement mobile (pour Orange)" (sorry, I'm new, so I cannot post urls).
In fact, this app has not been declared by the devs (on the Google Play) to be compatible with my phone, despite the fact that I have the specs to run it (NFC payment).
I asked a friend who was able to download the app to upload it on Aptoide, giving me the opportunity to download the apk on my phone (this apk is available in this thread). I tried to install it, but I get the following the error: "app not installed".
I would like to force the installation of the app. I tried many ways, like using apps that use root access on the phone, without success (for example, I tried with "System Apps Installer" on the Google Play, but I get a problem with mounting /system). I also tried to install it with the command line tool, but I get the error "[install_failed_invalid_uri]". I tried to change the permission of the /data/local directory and /data/local/tmp with ES file explorer, but it did not change anything.
In addition to this, I'm not able to enable usb debugging in the developper options (to install the apk with adb), because every time I activate the option, it becomes disabled in the following seconds.
It seems to be a little bit complicated, because I seem to have different problems, but I hope that someone here will be able to help me !
Thanks for your help,
Aquignis.
The issue is most likely Cm. They alter things so some that normally work no longer work
I suceeded to solve the "[install_failed_invalid_uri]" error in the command line tool by also changing the permissions of /data.
After that, I got another error (yes, one more, but the last) that made me discovering what's the real problem in this situation: "install_failed_missing_shared_library". By doing some researches on the web and exploring the apk, I understood that the app use a library called "org.simalliance.openmobileapi" that corresponds to the work of SIMalliance, who developped an API called "Open Mobile API", which notably enables communication with NFC sim cards and must be integrated to the build of the ROM. This system is used by many banks in Europe and has been integrated in the stock ROM of many NFC devices by the important manufacturers, but not by Cyanogenmod devs in the last stable release of CM 11 for the Galaxy S4.
Like you said it, the problem was CM
I asked them if it has been integrated in CM 12, because that is why the app is said to be incompatible with my device by Google Play which automatically checks which libraries are installed on your device (I'm waiting for their answer). The other solution would be to add the library to the CM build by myself, because it seems not to be very complicated, but I'm not qualified enough to do this !
If it is not part of aosp I wouldn't count on it being added to be honest. Not to mention most banking apps refuse to work if the Rom has root as it can cause security issues.
Yes, the root seems to be a problem with some apps according to the work of this man.
On the other hand, I think that this API is important enough to make CM devs pay attention to it, because it is used in many countries (except the USA which use only HCE, I believe). If only I was able to build it myself !

[Q] SD CARD fix (KitKat or higher)

I have a question, and if possible the answer should be as wide as possible to work on as many systems as possible. While I am not fully conversed in Android functions, syntax, and interfaces, I have been programing various computers since the mid 80's and have applied rooting/jailbreaking methods to several systems (if it functions like a computer, I want my Admin rights, much thanks to each and all authors of these). I know that someone somewhere out there may have asked and already found a solution to this very annoying problem.
Thanks to the Google's decision to increase security in the Android OSes (KitKat and higher) by removing write access to the SD Card (as I call it a very 'bonehead' and brute force decision), most of the older apps do not work properly anymore with the user added SD Cards and most are not being updated with some form of support (create a folder on SD Card). The solution for most persons is to root the system then either run an app that corrects the problem or install a new LRAM image (Lockable RAM: 'unlock' the RAM and overwrite its data with a new image then re-lock it. I don't like the term 'ROM' for this as it has been incorrectly used since the late 80's). I have found at least 2 file managers that say they have a (in-app) solution, but these solutions don't extend to all of your other apps (ie "Root Explorer" or "B1" solution doesn't help your File server/uTorrent/Photo Gallery app).
But what of the owners that for one reason or another can't root their system (unable to root, not authorized or allowed to root, etc.) but want/need to have write access to the user added cards (mainly because their internal storage is just too small)? Example, in my case my personal phone has several apps that require it to remain in an unrooted state for certain work related programs (security issues).
So here is my question:
Is it possible, on an unrooted and stock LRAM android device, using ADB to PULL the "platform.xml" file, add the line '<group gid=”media_rw” />' to it, then PUSH the edited file back to the android device?
I realize this may require entering (various name versions) Recovery or Update mode which is specific to each device (I think Samsung calls their ODIN). But I think the ADB commands and computer side instructions should be the same. So if it is possible, please list all ADB instructions (I know the text editor used will depend on the PC/MAC OS used).
Thank you one and all that give any advice or assistance.
Well it looks like there have been a lot of lookers since I first posted this but still no reply by anyone that knows Android OS inside and out. Most of you are probably thinking "tl:dr" to all of it.
I know there has to be a way to update/upgrade system files that doesn't require rooting or a way to find the manufacturer's or cellular vender's access path or password.

cifs.ko module / Busybox / mounting CIFS shares

Hello all. In the last 24 hours I've racked my head against a wall and I can't seem to get past this. So some pointers would be very welcome.
Backstory - Been doing backups of Titanium Backup onto my Nexus 9 (16GB internal storage) and I'm running into problems with running out of storage space. So I thought I'd look into doing a CIFS share mountpoint to my tablet and backup directly to the CIFS shares on my FreeNAS box. I figure a couple TB of storage is enough to store my Titanium Backups.
So first I read about CIFS Manager. Seems it may be discontinued or not functional on Lollipop.
Then I read about Busybox. Very cool, I think I'd marry Busybox if it was a woman. It seems so amazing I bought the Busybox Pro version.
So I tried to mount the CIFS/SMB share but I keep getting the dreaded "no device found" which means the cifs.ko isn't loaded. Apparently it's not in OS by default, so I need to compile it. (I'm not against someone giving me the .ko file, but I'd rather learn how to fish for myself than expect someone to give me a fish when I'm hungry) I have no clue how to compile it or even where to start to get a resemblance of the necessary steps. My experience is mostly Windows and FreeBSD, with only enough knowledge of linux to be very dangerous. I've tried searching all over for some kind of guide, pointers on what files I need to get, where to go to compile, etc but there seems to be nobody out there with any kind of good guide, even an outdated one I could use to fill in the blanks. I was hoping to put together a fairly detailed guide that includes steps on how to compile the cifs.ko yourself from source as well as mount your share on the device for whatever purposes you desire. But I'm finding that there is basically no info online on how to do this, where the source is, how to compile it, etc. If you know how to do this and are willing to help me write the guide (I've written quite a few articles on FreeNAS and ZFS) I'd be more than happy to give you some credit. I have no doubt lots of people will use the document once it is created.
Alternatively I considered doing the same with NFS but again I'd need to compile the nfs.ko module, so I'm stuck at the same point there.
Anyone have any pointers on how to do this? Or, anyone have any other options that will work just as well that allow me to not have to store the actual titanium backup files locally?
About the only thing I can find is someone saying that you need a Linux VM, the kernel sources, sdk, some knowledge in unix, and patience. But hell, I don't know if by saying "kernel sources" they are talking about the kernel source for the Linux VM or the Android OS I'm running (or both), if the SDK is referring to the Android SDK or not, etc.
Thanks in advance!
Joshy8 said:
Or, anyone have any other options that will work just as well that allow me to not have to store the actual titanium backup files locally?
Click to expand...
Click to collapse
I was in the same boat as you a few years back. Basically I would root, find a kernel that had the CIFS module, then use CIFS Manager to mount the shares. I would also use rsync & busybox. This stuff is tricky. The command to get Android to mount the shares, the CIFS module and kernel always has to be up to date, changes in busybox, etc.. I dreaded Android system updates. It starts to feel like a Rube Goldberg machine.
I started using an app called FolderSync (there's a paid version, too) and never looked back. It works quietly in the background and have never had any problem with it. It's one of the best apps on Android.
I do thank you for the advice, but that's how I've been doing backups for several years. I bought it back when the original Droid phone came out.
However in this case, since my tablet has only 16GB of internal memory and you can't easily have permanently attached external storage I'm forced to come up with an alternative of some kind.
I have had some problems lately with FolderSync. Not sure exactly what the problem is, but FolderSync seems to have issues from time to time and it gets stuck on random files and never finishes, even if left to complete for several days. I've had this issue randomly on 3 different devices, and one of my friends that also uses FolderSync has had the same issue on his. So I'm pretty sure there's a bug of some kind in FolderSync that sometimes breaks it.
Anyway, since my tablet has only 16GB of internal memory and you can't easily have permanently attached external storage I'm forced to come up with an alternative where the data is never actually stored on the device itself. :/
I know this isn't the answer you were looking for, but have you seen these:
http://www.meenova.com/st/p/mrg2.html
It's the closest thing I've found to convenient usable external storage.
Sent from my Nexus 9
The Fire-Ice kernel (http://forum.xda-developers.com/nexus-9/orig-development/kernel-fire-ice-t2930451) supports CIFS. I use it to connect to my SAMBA linux server. I also did the following, not sure if both of these are necessary: set SELinux to permissive with SELinux Mode Changer, and use the "patched" version of CIFS Manager (found on this forum).
I'm still hoping somebody will just write or cross-compile a FUSE module (like SMBnetFS) that works on all rooted devices, so we don't have to rely on custom kernels/modules anymore...
Since you asked for alternatives, you can also just get an OTG cable and hook up a USB stick or external HD to your phone (needs root and an app like StickMount).
Thanks for the reply. Been a bit busy with life stuff and just finally got to sit back down and look at this again.
I agree that a FUSE module would be useful for something like this. I don't have a need for high performance with regards to this problem, so a FUSE module would seem very appropriate.
I do have an OTG cable and I do have a 64GB thumbdrive I can use. I was just hoping for something that was a little non-obtrusive and passive so that I'm not actively having to be involved in the backup process itself. As soon as someone in the meat-world has to take active steps to make a backup every time, that's when backups typically stop happening, and then the next thing that happens is data loss. So I'm trying to remove myself from the equation as much as possible.

Mediapad 10 (T1-A21L) usb webcam/rooting

Hello,
I have an external USB camera(endoscope) that I'd like to use with my Huawei Mediapad tablet. I've been googling and its possible, there is no hardware restrictions since USB OTG is working(tested with thumb drive). I'm not sure about UVC drivers but there are a few other problems that might be causing the problem.
Reading a blog i discovered that since KitKat(this tablet has 4.4.4) the SELinux policy is set to "enforced" and therefore apps can't access external USB camera feeds like they used to straight out of the box. There are 3 workarounds which all require rooting.
1. Start the app with superuser rights
2. Configure SELinux to allow USB cam feed
3. Custrom rom
Blog link: htt ps://droidperception.wordpress. com/2013/12/01/webcams-on-android-4-4/
So it all comes down to this - I need to have this device rooted but I haven't even found a single thread about this model in this forum.
NB! I don't have room for experimentation(read: bricking the device) since the device is not mine.
Thanks for you attention,
Pask
You ask quite a while ago and I see no answer. So, just in case, I did root mine in a way I not necessary would recommend, but ... KingRoot latest version can do a trick, but it definitely not kind of software I would keep on my tablet. So after that I install SuperSU, Link2SD ( using it to get rid of applications I do not like) and RootExplorer + Terminal. Give all of them root access using KingRoot manager and with help of Super-Sume App (will cost you some money) start a process of getting read of all related to KingRoot and Co. It is more tricky that one may think but by freezing and killing some processes in "write" time I manage to install SupeSU binaries and remove left overs. I still have problems to get su requests, so just copy config files from my phone with access rights already given to specific applications and deny access to anything else. So far do not see anything I cannot identify running, so my hope KingRoot is completly gone.
So far I did not fine any other tools/methods to get root

Categories

Resources