I am trying to set up a PPP connection from a Zte MF820b 4G LTE USB modem/router to a WiFi only Android tablet with a 4.2.2 os that has a custom ROM installed which technically shouldnt of been jailbroken. The tablet is running a Linux version 2.4.3 and KERNEL:3.0.36. The problem here is me. I am a complete newbie, but do know a little about command prompts and how this should work in theory. The tablet is fully rooted and has all the necessary applets installed via busy box(chat, nc, pppd, ect) and terminal emulator, or at least I think that's what's necessary. I installed PPPwidget 2 and 3 but as apk's and since they are not from the Play Store will not function. I have Google play store installed but its all but useless since I can not log into my account, for reasons I suspect as being that the system is too old and says something about the connection not being secure or private and as such...can not actually get the app with license verification from Google play store. I tried to lucky patch the apk and remove license verification but that did nothing as well. However the apk will read the modem and ask permission to allow pppwidget to be used but shortly fail after for the aforementioned lack of correct license. There must be a way to manually call the modem and connect via terminal emulator using adb ppp or nc? Without any understanding on how to actually write a script I'm hoping someone can help me get this functioning. Situation beyond current controll will not allow me to work with anything other than what's at hand, and I'm willing to pay for someones time if I can actually get this working. I also have a tablet with a different os (8.1 Oreo) should that be easier. With the 4.2.2 the device pops up as "storage" in my file manager. With the 8.1 it pops up as a device Id number when I type in lsusb in my terminal emulator. The 8.1 has Termux installed should that open up a different venue. The carrier I'm using is T-Mobile and the nameserver and ISP info is NS1-AUTH.SPRINTLINK.NET; IP 206.228.179.10. The device is functional as when the opportunity arose I was able to plug up to a computer and try it out. That's no longer viable. Again, I'm willing to pay for the help as I'm sure I'll need to correspond back and forth a few times and will probably need help writing the correct script if needed. Please email me @ [email protected]. Thank you.
Spoiler
milanv5 said:
I am trying to set up a PPP connection from a Zte MF820b 4G LTE USB modem/router to a WiFi only Android tablet with a 4.2.2 os that has a custom ROM installed which technically shouldnt of been jailbroken. The tablet is running a Linux version 2.4.3 and KERNEL:3.0.36. The problem here is me. I am a complete newbie, but do know a little about command prompts and how this should work in theory. The tablet is fully rooted and has all the necessary applets installed via busy box(chat, nc, pppd, ect) and terminal emulator, or at least I think that's what's necessary. I installed PPPwidget 2 and 3 but as apk's and since they are not from the Play Store will not function. I have Google play store installed but its all but useless since I can not log into my account, for reasons I suspect as being that the system is too old and says something about the connection not being secure or private and as such...can not actually get the app with license verification from Google play store. I tried to lucky patch the apk and remove license verification but that did nothing as well. However the apk will read the modem and ask permission to allow pppwidget to be used but shortly fail after for the aforementioned lack of correct license. There must be a way to manually call the modem and connect via terminal emulator using adb ppp or nc? Without any understanding on how to actually write a script I'm hoping someone can help me get this functioning. Situation beyond current controll will not allow me to work with anything other than what's at hand, and I'm willing to pay for someones time if I can actually get this working. I also have a tablet with a different os (8.1 Oreo) should that be easier. With the 4.2.2 the device pops up as "storage" in my file manager. With the 8.1 it pops up as a device Id number when I type in lsusb in my terminal emulator. The 8.1 has Termux installed should that open up a different venue. The carrier I'm using is T-Mobile and the nameserver and ISP info is NS1-AUTH.SPRINTLINK.NET; IP 206.228.179.10. The device is functional as when the opportunity arose I was able to plug up to a computer and try it out. That's no longer viable. Again, I'm willing to pay for the help as I'm sure I'll need to correspond back and forth a few times and will probably need help writing the correct script if needed. Please email me @ [email protected]. Thank you.
Click to expand...
Click to collapse
@milanv5
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Android Q&A but I also closed it as duplicate of
PPP connection with android
I am trying to set up a PPP connection from a Zte MF820b 4G LTE USB modem/router to a WiFi only Android tablet with a 4.2.2 os that has a custom ROM installed which technically shouldnt of been jailbroken. The tablet is running a Linux version...
forum.xda-developers.com
Allow me to suggest to review the XDA Forum Rules, to which you agreed to adhere when you registered on XDA two years ago, and to focus especially on rule no. 5!
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
Related
I've been working on this for days and I'm on the verge of giving up and send my android tablet back to the retailer but, on the off chance that someone can help, I thought I'd post a plea for help.
I have been playing with my mother's birthday gift, an android tablet, in an attempt to put a bird watching app on it. I'm not used to this OS, so it took me a few days to get the hang of it, and then the wifi stopped working.
From a user perspective, you turn on the wifi and, after 20 seconds, it turns itself off and the tick disappears.
I decided to look a little further into the problem, as I didn't believe it was the hardware so soon, and used LauncherPro and SuperOneClick to root the tablet and ddms to see what was going on.
Anyway, I think I have tracked the issue to the wpa_supplicant file. I can load up the wifi interface from the command line:
insmod /system/lib/modules/8192cu.ko
busybox ifconfig wlan0 up
But when I ran the original wpa_supplicant in /system/bin/ it simply said "not found"
The file was there - I could copy it onto a usb stick and open it in a hex editor on my PC, but whatever I did, it would say "not found" if I tried to use it (chmod 777 as well).
When I got no joy from that, I started to look for alternative wpa_supplicants (there was no sign of a direct replacement for my disgo8100 2.3.3 version) and found the ad-hoc enabled ones.
I have tried a selection, but the one that comes closest to working (I mounted the system rw and replaced the original before mounting it ro again) insists on running as "wifi" (or 1010) when the original ran as "system" (or 1000).
This seems to mean that, although the supplicant runs happily, it doesn't create the /data/system/wpa_supplicant/wlan0 file in a form that other programs can access (wrong group/permissions, I think).
So, this has become very frustrating (but I've learned a lot about android, and how it differs from linux).
Can anyone provide an explanation for why the original file says "not found"? Could it be corrupt? If so, could someone provide a replacement from the disgo 8100? Could it be relying on a library that's not there?
What about the ad-hoc version I have? Can I force it to run as system.system instead of wifi? Am I wasting my time and should try to get disgo to provide a whole replacement rom (they have an update apk, but I believe you need to connect to the Internet to do an OTA update, which I can't).
As I said, I'm ready to send this tablet back, but I hate to admit defeat!! Any help would be gratefully received.
Cheers.
Never mind. Made some progress with the ad-hoc supplicant in this thread:
http://www.freaktab.com/showthread....pa_supplicant-file&p=3600&viewfull=1#post3600
Disgo 8100 Rooting
On the basis that there doesn't seem to be much information about the Disgo 8100, I thought I would post my findings.
I initially tried z4root, universalandroot and gingerbreak, but none of these worked. However, I didn't understand that I needed (or how) to enable USB debugging.
Once I did, I installed LauncherPro-0.8.6.apk and configured a shortcut to the development tab, which let me enable the USB debugging option.
I then downloaded android-sdk_r18-windows and modified the android_winusb.inf file by inserting the following at the end of the [Google.NTx86] and [Google.NTamd64] sections:
;Disgo8100
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_1F00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_1F00&MI_00
When I plugged in the Disgo 8100, windows XP asked for drivers and I pointed it to the edited .inf file so that they could be installed and the disgo was recognised.
I then used SuperOneClickv2.3.3-ShortFuse on the PC to root the tablet - it all worked perfectly and reported success.
Installing term.apk got me a terminal emulator and I could su into root. Hopefully you can get yours rooted, too.
Disgo 8100 Android Market/Vending/Google Play
Whilst I managed to root the tablet, I couldn't get any form of the vending system to work.
I got the play dot google dot com site to recognise my tablet as a T-Mobile Samsung Nexus S using the information in this thread:
http://www.techknow.t0xic.nl/forum/index.php?topic=770.0
But market 2.3.6, 3.4.4 and the latest Google Play all fail with various errors (although I noticed that play only [email protected] out when the wireless is enabled - the others may do the same).
I have taken a log capture of google play failing using ddms and will look through it.
By the way, grabbing the hwver for this tablet gives:
console=ttySAC3,115200 androidboot.mode=normal mem=512M hwver=81.1.0.0 mtdparts=imapx200:[email protected](ramdisk),[email protected](kernel),[email protected](resv),[email protected](system),[email protected](userdata),[email protected](cache),[email protected](Local-disk),[email protected](panic) androidboot.mode=normal
Google Play working on Disgo 8100
Drawing this one to a close, in case anyone is interested:
I have Google Play installed and working. I downloaded com.android.vending-3.5.15.apk from the link in this thread:
http://www.theandroidsoul.com/download-google-play-store-apk-3-5-15/
I renamed it "Vending.apk" (the capitalisation may be important, not sure), mounted /system as rw (mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system) and copied it into /system/app. I changed permissions to "666".
I cleared the data/cache from the YouTube application and deleted YouTube.apk from /system/app (because it kept locking up) and replaced it with signedy244.apk (renamed as YouTube.apk) from http://forum.xda-developers.com/showthread.php?t=1529715 (the WifiHD version).
Rebooting the tablet, I connected to the WiFi and ran YouTube (in order to confirm my gmail account), which worked fine, and then Google Play, which (to my amazement) worked fine too.
Hope yours does too
Excellent thread! Wish I could thank you but I don't seem to have a Thanks button. Anyway, do you mind if I ask a couple of questions re. rooting the 8100:
1) Was your tablet running Android 2.3.3, kernel 2.6.35.7, build number GRI40?
2) Could you explain in a bit more detail what you did when you "configured a shortcut to the development tab"?
a3d35232 said:
Excellent thread! Wish I could thank you but I don't seem to have a Thanks button. Anyway, do you mind if I ask a couple of questions re. rooting the 8100:
Click to expand...
Click to collapse
Glad you like it.
a3d35232 said:
1) Was your tablet running Android 2.3.3, kernel 2.6.35.7, build number GRI40?
Click to expand...
Click to collapse
Yes.
a3d35232 said:
2) Could you explain in a bit more detail what you did when you "configured a shortcut to the development tab"?
Click to expand...
Click to collapse
a. Install launcherpro
b. Press home in the top left corner
c. Choose launcherpro
d. Press and hold a blank part of the screen
e. Choose shortcuts
f. Choose activities
g. Choose settings (scroll down to it)
h. Choose development (scroll down - not in alphabetical order)
i. Press ok
You should now have a desktop icon that lets you turn on USB debugging.
Enjoy
Thanks. Everything worked as you describe except the signedy244 version of YouTube. Whenever I launch it I get an error message "There was a problem with the network [400]". Searching on the net, it seems a lot of people are seeing this error and there may have been an update to the app which isn't in the signedy version. Are you still able to run it?
a3d35232 said:
Thanks.
Click to expand...
Click to collapse
No problem.
a3d35232 said:
Everything worked as you describe except the signedy244 version of YouTube. Are you still able to run it?
Click to expand...
Click to collapse
Yep, didn't have an issue - dropped it into the app folder, chmod and rebooted; worked first time and tested it a few times. The file I downloaded was 2,554,313 bytes, in case you want to check.
FYI, the issue I was having with the YouTube app was that it was making requests to the server with "restriction=ZH" in the uri. The server was replying with a HTML 400 error (bad request) because ZH is a language code, not a country code. Anyway, I've patched the app further to remove the restriction parameter from the request. I've posted details in the YouTubeHD thread (about half-way down page 36) if you're interested.
Any chance of telling a idiot how to get google play on the Disgo 8100?
My dad got given one at work but the app store sucks and I'm a little confused by the above
Many thanks
Salam,
I came here, because well, I literally have no where else to ask, even my university professor replied with " I don't have time for such nonsense" . Basically what I'm asking isn't if it's possible because almost everything is possible, so I want to know how to run a rom patched with a pDroid core on a PC.
If in the answer you'll use the x86 Android please add to it how I can run normal Android apps on it, I'm not that knowledged on the subject but I think it has to do with an ARM emulator.
Anyways, I want as a result to run Android apps on my PC, then use a pDroid manager to feed it info like phone ID, Phone number, GPS coordinates ... Thanks for your time
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Well said buddy.
I consider myself a fairly advanced android and linux user and I've customised the heck out of my n4 but I'm leaving my hdx as it is for now.
Good advise there.
Now if only mayday had a pro feature to help with rooting... haha
Can we set jcase up with a webcam? Lol
Sent from my Nexus 4 using Tapatalk
GSLEON3 said:
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
Click to expand...
Click to collapse
Safestrap! Safestrap!
http://forum.xda-developers.com/showthread.php?t=2556677
Firstly, this was posted before SafeStrap. Plus, I highly doubt even Hashcode would recommend new users mess with SafeStrap right now. I'm by no means a master developer, but I've been around a long time & I've participated in some pretty cool low level hacking with some of the old timers & I'll be the first to say that there is some funky stuff going on in the HDX. Amazon has not exactly gone out of their way to make modding safe or easy. Plus there's not a whole lot out there yet that requires an custom recovery. It may be fine for you or I, but it can open a whole other host of issues if used improperly.
Sent from my KFJWA using XDA Premium HD app
Hey there I am new to this forums! Got a kindle yesterday (as a gift) and moved straight to xda to see what's cooking unfortunately I was a bit disappointed because there is no "cooking" at all. I hope this has to do with the fact that it's a new device and nobody has tried to make some roms for it yet... Nevertheless I am quite happy with it, although this fire os is a pretty pain in the eyes. Thank God I have managed to get the YouTube app sync with my Google account, plus some other gapps like drive. Well that's it for the moment, I just didn't want to make a new thread so I posted in here. So what do you think, will there be some good roms for this device? And/or maybe we could use those for the kindle fire hd?
Sent from beneath my cloak of magic
Thanks for the info I'm super new at this but was thinking buying one of these. But now that I am acquainted with Flashing ROMs and stuff it's sort of a deal breaker if it's not being done. If I can't modify it, whats the point?
HDX rooting?
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
Patience good people. Each day a few qualified devs get a little closer ... all on their own free time. A crack might be right around the corner.
Well, it's almost June and development for the Kindle tablets seem to still be very slow, what's the story?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
You can get root and the Google Play Store on an older firmware, just not any of the newest couple. Yet (I hope).
Good to go: I was able to use hdx-toolkit with my router blocking
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
sabasc said:
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
Click to expand...
Click to collapse
I'm sorry I missed this. Great advise though.
A default Microsoft driver was blocking the Amazon ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install. --Win8/Win8.1
Click to expand...
Click to collapse
The toolkit needs to be run locally because well the adb connection won't go through your share to your computer.
GSLEON3 said:
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Click to expand...
Click to collapse
Is this still the case? Just wondering if this thread needs to be updated because some of what's written here seem to contradict what I've read people are doing with their hdx.
my 8.9HD ver. 8.5.1
Is my kindle an HDX?
ant17 said:
Is my kindle an HDX?
Click to expand...
Click to collapse
No, you can find anything related to your kindle here
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
hfpop said:
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
Click to expand...
Click to collapse
to an extent yes,most custom roms cannot be installed but if you rolled back you can still root and instal the hdx nexus 2.0.2 rom which is pretty much most of what the device needs
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
hfpop said:
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
Click to expand...
Click to collapse
i have it on 3.2.7 on my device and this here lists what you can do with a 3.2.8
http://forum.xda-developers.com/kin...o-13-3-2-7-t2993089/post58150015#post58150015
@Davengerr: Thank you. All worked out greatly.
Hello friends!
I have a Chinese BML One mini phone (I know it's crappy, but I had no choice), and I'm trying to start an android development with it.
I was aware that it might be hard to find any drivers for that phone, so I decided to use linux (opensuse 13.1) as a development machine (hopefully it requires no extra drivers).
The problem is that device seems to be invisible for the eclipse.
When I do in eclipse "run as - android application" - it says that there is no suitable device found and suggests to create a virtual one.
Usb debugging is on. Phone keyboard is unlocked.
The project is created to run on android 2.2. (The phone says that it is 4, but while digging here on the forum I found that it is really 2.3.5)
Is there any special way of connecting that phone to the PC? Hold secret combination of buttons maybe?
(As far as I know galaxy nexus for example is also invisible for eclipse when you connect it as a flash drive, so you have to connect it as camera.)
The problem is even worse as my laptop is too weak for the development on emulator, so that mobile was the only chance to start android development.
I would be grateful for any answers and links.
Thank you.
Hej hej! Please share any thoughts why it could be? Any suggestion of what to try? Does anyone experienced any device recognition problems with Chinese mobiles on any OS? Is there something special with connection MocorDroid to PC?
What would you try?
Please give me at least a direction to dig.
Thanks
The main issue is that it's not an official Android version and the fact that they modded it to read the wrong Android version there is almost nothing you can do. Mix in the fact that there IS no kernel source code there will not be much you can do at all with development for that device.
Hello, thank you for the answer. You inspired me to search in Chinese internet using google translate, and that is what I've found:
One need to find the vendor and device id using lsusb command
Bus 001 Device 002: ID 1782:5d04 Spreadtrum Communications Inc
These 1782:5d04 is actually a device and vendor id.
Then we need to write it to /etc/udev/rules.d/51-android.rules file in that way:
SUBSYSTEM=="usb",ATTRS{idVendor}=="1782",ATTRS{idProduct}=="5d04",MODE="0666"
And also add "0x1782" without quotes to /home/XXX/.android/adb_usb.ini file.
If you don't have any of these files, create it. Note that 51-android.rules should have 644 permissions.
Than I googled for "0x1782" and found these two links, so I think that problem is not only chinese-fake-android-specific:
stackoverflow. com/questions/9210152/set-up-device-for-development-no-permissions
sudotask. wordpress.com/2013/10/30/how-to-adb-on-open-suse
It could be also problem with permissions like described here:
stackoverflow. com/questions/6484279/detecting-device-for-debugging-adb-does-not-work
So, now I able to use my mobile for Android development! Wait for more garbage in play market!
Thank you!
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.