yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] itenos:
Regarding the RSA key permission request that happens when I connect the phone to a computer with your app it doesn't appear at all.

I just tried to connect over wifi using Wifi ADB Pro from the play store and the devices actually Connect but no other operation is possible. Launching the file browser it stays

on /mnt and says that root access is false.

Will try now to connect the other way around, Nexus 4 accessing Nexus 7 and report back

EDIT: Forgot that the Nexus 4 doesn't have OTG support, so that second test is impossible ;)
[Android Apps and Games] evo.dev.m1nd:
Hm.. bad to hear.

Connect your Nexus 7 (Host) again to your Nexus 4 (Victim) via the USB OTG cable and try to manually figure out if the Nexus 7 detects the Nexus 4. Do this via the terminal or over a WiFi adb shell from your PC to your Nexus 7.

When you have a shell on your Nexus 7 - type "adb devices" and take a look if your Nexus 4 appears - if not, there is a problem with your OTG cable.
[Android Apps and Games] evo.dev.m1nd:
Guys, I told you that I'm working on another app at the moment - it's done. I ported an iOS app from a friend of mine to android.

Take a look if you want to: Multiplayer Stats - Halo Reach

..and if you like it - please give me some feedback in form of a rating and/or a review in the Play Store.

Cheers.
[Android Apps and Games] itenos:
Connecting it via cable gives no result because your app doesn't see my nexus 4 at all. The cable works well with USB sticks though. Connecting via ADB WI-FI instead shows ROOT ACCESS: FALSE in your app and UNAUTHORIZED in terminal emulator. All that without that the victim ever asks for the RSA authorization.

EDIT: I tried connecting again via cable and this time the result is the same as via wi-fi. Terminal emulator shows my device ID following an UNAUTHORIZED.
[Android Apps and Games] evo.dev.m1nd:
I meant:

1.) Connect your devices together (Nexus 7 = HOST)

2.) Install and open the app "Terminal Emulator" on the Nexus 7 and type in "adb devices". A list with a connected devices should appear now (including your Nexus 4). Does your Nexus 4 appear or not?

It should look something like that:

Is Busybox up-to-date on the Nexus 4? Because never version of the adb binary (with the whitelist feature) don't work with older versions.
[Android Apps and Games] itenos:
Yes, I understood and this is exactly what I have done.

The result is that next to my nexus 4 appears UNAUTHORIZED

I hadn't installed BusyBox at all though as a standalone app on it (apart from the BusyBox that comes with titanium backup), so I downloaded it from the play store but the result is the same. :(
[Android Apps and Games] evo.dev.m1nd:
I figured out that there are still a few minor bugs in the app - I'm working on it.

What you can try to do:

Install busybox (standalone app) from the playstore - it will remove your old binaries and update them to the newest versions. Maybe one of your "adb binaries" is really outdated.

Install rootexplorer (or any other explorer) and go to "/data/misc/adb", there should be a key file where the adb whitelist RSA keys are saved to (with the correspondig device) - delete this file and reboot.
[Android Apps and Games] itenos:
Ok, I did delete the old Whitelist keys and rebooted but the result stays the same. No authorization request on the slave and host shows UNAUTHORIZED in terminal window
[Android Apps and Games] evo.dev.m1nd:
Hm.. have you tried to update your binaries with the busybox standalone app yet?

What happens if you connect your nexus 4 to a pc? And what happens if you connect your Nexus 7 to a pc?

To you get a RSA key verification prompt in both cases?

greets
[Android Apps and Games] itenos:
As I said before I didn't have BusyBox installed at all before so I guess the fresh installation did update the binaries.

Connecting the two devices to a PC I do get the RSA key verification prompt in both cases
[Android Apps and Games] evo.dev.m1nd:
Well, then I don't know what to do.

Play around - maybe you find a solution by yourself. I can't figure out the problem atm.
[Android Apps and Games] itenos:
I did some more testing. As the nexus 4 doesn't support USB OTG it does support ADB over WiFi though, so I connected the devices the other way around, Nexus 4 host and Nexus 7 victim.

The result is the same as before so I guess it is really a problem with 4.3

Here in detail what I get:

1. After clicking on CONNECT and enter the correct IP address of the victim it connects successfully

2. It shows though Brand : Unknown and Model Unknown (Unknown)

3. when selecting the device a short pop-up from SuperSU states that root access has been granted

4. In the following screen though (the main working screen) your app shows a small android and besides that is written Unknown and Root Access: false

5. Selecting Browse files the file browser opens at /mnt and shows an empty window

As it appears your app is receiving root access but it's not recognizing it. I remember that there were quite some problems with root when 4.3 got released. Chainfire had to work very hard before the issues have been fixed.

Hope this helps
[Android Apps and Games] evo.dev.m1nd:
Thanks for that report!

I got some feedback that there is also a problem with WiFi ADB on Android 2.3.3 with (Unkown, Unkown, Unknown - the same problem you described). I'll check and try to fix this bug.

Cheers
[Android Apps and Games] evo.dev.m1nd:
Uni started 3 weeks ago and I've got lots of work to do.

It will take some time, but the next update will come ;)

Cheers
[Android Apps and Games] getiem:
Nice work on this app. I am able to connect my N7000 to my car with buildin Android device :) (android 2.3.7) with ADB over Wifi enabled.

Does the toolkit support added scripting/remote calls? We may need it to make a easy way available to root the car buildin android device. You can read about it in our topic SCT: http://xdaforums.com/showthread.php?p=47182309#post47182309

We are already able to root it using ADB over Wifi, but it needs a lot of scripting from a pc now, an app from phone would make it easier :)
[Android Apps and Games] evo.dev.m1nd:
That sounds freakin' amazing. I've just visited your site and that seems like an awesome idea. ;)

Does Craze work properly when you connect it to your board computer? Any issues?

Actually the app doesn't support any scripting/remote calls - but if you like to, we can do some team work and add the features you need. Write me a PM.

Cheers
[Android Apps and Games] getiem:
The connection between my Samsung Galaxy Note N7000 and the incar Volvo SCT system is perfect and suitable for communication. Filebrowser works, Package browser works. Install/Pull/Push works.

As you can see in our SCT topic, we need to put some specific commands into ADB to perform our rooting action. As it is not very handy to take a laptop into a car, it would make very helpfull to use an android phone.

I asked [MENTION=2984707]gekkekoe123[/MENTION], our developer of the rooting option, to get into contact with you to specify our wishes.
[Android Apps and Games] evo.dev.m1nd:
Perfect.

Cheers
[Android Apps and Games] spiderio:
this apps sound awesome...

I will try to download it and try it today
[Android Apps and Games] itenos:
Any news on the update?
[Android Apps and Games] evo.dev.m1nd:
I have lots of stuff to do, but I'll try to publish it as soon as possible.
[Android Apps and Games] Kebb42:
Can you post an apk, the play store days it's incompatible with my Nexus 7
[Android Apps and Games] itenos:
That's probably because your Nexus 7 in fact IS INCOMPATIBLE with this app, at least if you are running 4.3.

Just scroll up and read my former discussion with the developer here.
[Android Apps and Games] evo.dev.m1nd:
Are you running Android 4.3 ?

I can release a quick 4.3 support update if you like to.
[Android Apps and Games] evo.dev.m1nd:
I have released v2.2 to the Play Store.

Changes:

+ Removed all ad banner (!)

+ Added support for Android 4.4

That were just minor fixes - I discovered a few bugs, but I've very little time at the moment.

But please report any bugs to me - that'd be much help.

Cheers
[Android Apps and Games] evo.dev.m1nd:
v2.2 is up and can now be downloaded!
[Android Apps and Games] itenos:
Bad timing, since yesterday my test configuration has been changed. On my Nexus 7 I'm running 4.4 now...

I ran a quick test trying to connect Nexus 7 to Nexus 4 and viceversa both times by ADB over WiFi and the result is the same as before.

Device is recognized and connected but shows up as Unknown Unkown and the file browser states Root access: False

:(

Let me know if I can help you further debugging.
[Android Apps and Games] evo.dev.m1nd:
I'm going to work a few hours on Craze this weekend. I'll let you know any news.

PS: I added support for Android 4.4, not Android 4.3 (!) - 4.3 was already included!
[Android Apps and Games] itenos:
Just had the chance of doing some testing with a Samsung Galaxy Young. Connected through cable with my Nexus 7 the device is not recognized either, so I guess it's safe to state that Craze is not working with stock Android neither 4.3 nor 4.4 :(
[Android Apps and Games] jaiswalnilesh:
nice one

thank you
[Android Apps and Games] evo.dev.m1nd:
I'll give that a check as soon as possible.
[Android Apps and Games] Versatile1:
Getting a set Global Proxy error when I connect a flash drive after running this.
[Android Apps and Games] evo.dev.m1nd:
That's not possible. I don't change any system configuration.

Try uninstalling the app - does the error still occur?
[Android Apps and Games] Versatile1:
When I tried connecting to another device S3 from my device S4 it. FC'd systemui and showed that error. After that it does it whenever it is in host mode. Not saying your code did it but something happend. I have performed a factory data and installed a fresh rom and it is still there so its not a OS or kernel issue.
[Android Apps and Games] evo.dev.m1nd:
Hm, strange. I don't know what android version you're on, but on 4.2.2 and higher are several problems with adb. No connection can be established. But unfortunately that's an error of the adb binary, not of the app - so I can't fix that.

But I'll check that - thanks!

Cheers
[Android Apps and Games] StringMon:
Any progress ever made on attaching Craze to Kitkat clients? I've got the host running fine on a 4.3 GNex, and it connects flawlessly to older phones, but won't to my 4.4 devices. With the exception of Glass - go figure.

Basically, my symptoms are the same as what have been described on this thread last year: there's no reaction from either phone when I plug the USB OTG cable in. The client doesn't recognize that it has ADB connected, and Craze doesn't see it as an attached device. Just nothing.
[Android Apps and Games] MemoryController:
Deleted
[Android Apps and Games] evo.dev.m1nd:
Yeah, that's the annoying problem.. I can't figure out how to resolve it.
[Android Apps and Games] evo.dev.m1nd:
The development of this app is stopped due unresolveable problems (adb) with newer android version.
[Android Apps and Games] Asad85:
too bad, went through your thread, it was a great tool , with a huge potential, i wish development didn't stop, i hope it will be revived, because this kind of apps are really helpful.
[Android Apps and Games] evo.dev.m1nd:
Thanks mate.

We'll see, maybe I figure out any work around or stuff like that. But at the moment it looks really bad.
[Android Apps and Games] Asad85:
Ok. Sounds great. By the way, is your app based on KoS P2P project? Looks like its more advanced/polished version with several added features?
[Android Apps and Games] evo.dev.m1nd:
Yeah I got the basic idea from KoS's P2P ADB project.

Cheers
[Android Apps and Games] isgat:
what I need, excellent!
[Galaxy S 4 Q&A, Help & Troubleshooting] JonesWTF:
My GS4 has downloaded a citrate update but I don't want to update. It's just in case it blocks some way of rooting, which I plan to do over the weekend.

Does anyone know; 1) Where the download is stored; 2) If it's possible to delete it without root; 3) If I can't delete it, is there a way to remove the notification?

Thanks guys.
[Galaxy S 4 Q&A, Help & Troubleshooting] Delvorak:
I've read, but haven't verified, that wiping the cache will delete an OTA. Since I don't think we have a functional custom recovery, this may not yet be possible.

Also, there is an APK called FOTAKILL.APK, that if placed in the system/app, is supposed to prevent future OTA from being applied. Not certain that this works either, although I did apply it to my s4 in an attempt to bypass sprints latest OTA. You'll have to search for the APK, I don't have a link handy.
[MDA II, XDA II, 2060 General] IrishLad:
Does the XDAII support HSCSD. (High Speed GSM Calls)

If so does anyone know the AT commands to get it working, I use the HSCSD modem on my Nokia3650 using Blyetooth on my laptop and its works perfect. I DO NOT want to use GPRS which works fine on the XDAII.

So does anyone know how to get HSCSD to work on the XDAII if it is supported...?

Hopeing to get this done asap!

Thanks.
[T-Mobile Samsung Galaxy Note II] Luthien1:
This Is no good guys, it looks like snapdragon 800 is our future chip. The note 3 will use an outdated gpu, not capable of open gl 3.0. This is huge news and a huge disappointment. My note 2 will be my last note if this is true.
[T-Mobile Samsung Galaxy Note II] musclehead84:
The note 3 will use the octa core exynos not snapdragon 800. I agree on tje Mali 450. They should use something else since it isn't 3.0
[T-Mobile Samsung Galaxy Note II] Deleted member 2747343:
buy a tegra 4 device :good:
[T-Mobile Samsung Galaxy Note II] KennyG123:
Post in other device sticky
[Xperia Z Android Development] modsRule:
Here are NFS and CIFS modules compiled for use against the STOCK KERNEL ONLY.

Works for me on my Xperia Z. :)

Notes:

---------

NFS: supports NFSv3 only.

CIFS: Has the known kernel bug that affected all versions after 3.3.8 until ~3.5, which requires you to manually specify the unc parameter in the mount options.

I have included lockd.ko, sunrpc.ko for use with NFS, and nls_utf8.ko (only needed for .350, .432 has it compiled in to the kernel) for use with either.

I have only tested from the command line, so I won't offer any support for use from MountManager/CIFSManager. You are welcome to try to use them from there if you prefer.

4.2 introduced a more complicated multi-user storage system. (Details here). This may make it more difficult for you to use the mounted storage in your other apps (simply appearing as an empty folder). The only known workaround (please correct me if you know a better way) is to perform the mount via adb (yes, this you can do this from a script on your local device) so that all open apps get permissions to 'see' the mount.

Usage:

----------

insmod nfs.ko/cifs.ko/whatever
mount -t nfs -o vers=3,nolock,hard,intr 1.2.3.4:/yourmount /path/to/mount/to
mount -t cifs -o username=youruser,password=yourpassword,unc=\\\\1.2.3.4\\yourshare //1.2.3.4/yourshare /path/to/mountpoint/

Current Versions:

-------------------------

10.1.A.1.350 tar zip

10.3.A.0.423 tar zip

SHA512 sums:

---------------------

10.3.A.0.423

2b6109a329ed825b358607cd0f6218e064bd368c45bbecde38fd103f30c8cb323bfa4374ee4d85a77e70f52bf81109044f9f6a2e01ea4d521cb27a274a941d1b cifs.ko
20af544d34cc83b4955503d7232e8ea575c1d35abfd5e6c5c9726990ef9f945eaea9d22c91c95f6c03e366e9837fd30e60e3a09995c4d96bb7d4d93ca96edb6c config_nfscifs
6900aa64ce563f1d1c03e91aec2cbf89a69c902bbfdc78f3dca4bba2045e7106633d920da5ca285ebab7c26097e8ecc0b29c967fa14d28f057ada39dc8c8a294 lockd.ko
4760decf2cf3828af937ed844f436133c429a6db33bbdcd7563f8e6613414850fa13245e102115811196c1714522ec1c932ee7ea99ae9d4c4041425e63cf3a91 nfs.ko
4e0cdd708973ee1a90de490b9f2d0fc345447668d05539ebb97514997733be7421efbede2c0235414a3ad6be730bc1dfe20359ac285ccb9ff4038a7d34e2d4dd sunrpc.ko

10.1.A.1.350

5d6c29f519b3b85a08b0380271a64e52d23d641f030639ff560c7966811f2ec4b782a32f52b615d57463324169e7b410f51639513c038ddcf79895bcd7ca070a cifs.ko
34b767fce2c55fe5c3eb711df2ac7e450903901cecd21c165d5a1471da91f3a27c37c1d4c0530647064c1b92eac1b11751c2a829a1dbd0efec881a60be07477f config_nfs
eff854c9b28ae50d2b305ca4e230abbe8305d609783cc1ceb6b01a6d36ea55131cca29ab64cb3acf584fefb7c7bb6292e66f441333691da113f2c81d894ddbf9 config_nfscifs
6632ffd08354ee9b5e36615e19754696e8c497a8ce3639846b929b3d7085008f0c225bece20c6c96351c4e8612fc59084db975d71f44bd76b2c96b71d4ecef23 lockd.ko
278886d1a3684e1274477617b501b75d1a0d8caafc15d195564a3ef17dedbab90aa9e22eda7ec2d50e0e23206346d60b0f7b71a241e46252fb32ab2ad9ff088f nfs.ko
42c0bd96555a6396e24ea20e35305980a13cbf08bdc02fe660da5b23a641e70a38361c769f7d722bf116a8bc586ab20d278e3e8210b008524e5566fb46b740bb nls_utf8.ko
4a4b3bf6289904a0dedd889aacbb22a1a562fbaa7b78e714f9e1739ff7809187210b1cfac5632f740f81f4bb8213589707dc298319d7affb9910a33af1cd5d8a sunrpc.ko
[Xperia Z Android Development] johan8:
Cool !

I always use CIFS previously on my old samsung.

Tks a Lot !

:good:

Using script is fine for me, so that I don't need to install anything.
[Xperia Z Android Development] rregn:
[KERNEL] NFS & CIFS modules

For which kernel version are these modules?

I'm looking nfs (version 2), maybe cifs for 3.0.21
[Xperia Z Android Development] deligoz:
thank you for making this. Can you make one for the 10.3.A.0.423 kernel? and does it work for both 6602 and 6603?

thanks
[Xperia Z Android Development] xNAPx:
Sorry for my ignorance, but what this things are needed for?
[Xperia Z Android Development] modsRule:
These are for the kernel included with 10.1.A.1.350 which is 3.4.0-g298631f-01992-g95474bc.

I will add it to my list of tasks to do... If I don't do it within a few days, feel free to bump me to do it.

I think it should work with both C6602 and C6603, but I only have a C6603 so can't test...

These modules are used to access NFS/CIFS mounts from your phone, since Sony didn't compile them in by default. (If you don't know what NFS/CIFS is, you don't need this. :P )
[Xperia Z Android Development] Dr_SUSE:
Bump?

I'm looking for these very modules for 10.3.A.0.423 kernel.
[Xperia Z Android Development] modsRule:
Thanks for the bump. This task did get lost under everything else I do.

I am downloading the source package now so that I can do this.
[Xperia Z Android Development] modsRule:
Done. Check the first post for downloads.
[Xperia Z Android Development] Dr_SUSE:
Thanks for that!

Good news is that the module's loaded:

root@android:/ # lsmod
cifs 243687 0 - Live 0x00000000
wlan 2559132 0 - Live 0x00000000 (O)
texfat 121149 0 - Live 0x00000000 (PO)
cfg80211 128293 1 wlan, Live 0x00000000
hid_sony 1984 0 - Live 0x00000000 (O)

root@android:/ # modinfo /system/lib/modules/cifs.ko
filename: /system/lib/modules/cifs.ko
license: GPL
author: Steve French <sfrench@us.ibm.com>
description: VFS to access servers complying with the SNIA CIFS Specification e.g. Samba and Windows
version: 1.78
version: %s
srcversion: 3F86E0A9406EADE34D14793
depends:
vermagic: 3.4.0-gba62870 SMP preempt mod_unload modversions ARMv7
parm: enable_oplocks:Enable or disable oplocks (bool). Default:y/Y/1
parm: cifs_max_pending:Simultaneous requests to server. Default: 32767 Range: 2 to 32767.
parm: cifs_min_small:Small network buffers in pool. Default: 30 Range: 2 to 256
parm: cifs_min_rcv:Network buffers in pool. Default: 4 Range: 1 to 64
parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048

The bad news is I still can't get the share to mount.

mount -t cifs -o username=un,password=pw,unc=\\\\10.0.0.7\\Music \\10.0.0.7\Music /sdcard/Music
mount: Invalid argument
255|root@android:/ #

mount -t cifs -o username=un,password=pw \\10.0.0.7\Music /sdcard/Music
mount: Invalid argument

mount -t cifs -o username=un,password=pw,unc=\\\\10.0.0.7\\Music /sdcard/Music
Usage: mount [-r] [-w] [-o options] [-t type] device directory

mount -t cifs -o username=un,password=pw unc=\\\\10.0.0.7\\Music /sdcard/Music
mount: Invalid argument

mount -t cifs -o username=un,password=pw, \\10.0.0.7\Music /sdcard/Music
mount: Invalid argument

mount -t cifs -o username=un,password=pw,\\10.0.0.7\Music /sdcard/Music
Usage: mount [-r] [-w] [-o options] [-t type] device directory

dmesg

<3>[ 1619.729064] CIFS VFS: Connecting to DFS root not implemented yet
<3>[ 1720.159484] CIFS VFS: Connecting to DFS root not implemented yet
<3>[ 1880.073638] CIFS VFS: Connecting to DFS root not implemented yet
<3>[ 1931.261993] CIFS VFS: Connecting to DFS root not implemented yet
<3>[ 1963.688110] CIFS VFS: Connecting to DFS root not implemented yet

I've tried every reasonable variation I can think of in the syntax. Can you help me figure out what I'm doing wrong here?

Of interest?

Busybox /CIFS Bug/Patch
[Xperia Z Android Development] modsRule:
When you run 'mount', is that the busybox version or the android version?

Try again using 'busybox mount [parameters]'.
[Xperia Z Android Development] Dr_SUSE:
Same result. Slightly different error message:

mount: mounting \10.0.0.7Music on /mnt/Music failed: Invalid argument

but same return from dmesg.

Notice the missing "\" between 7 and Music. I'm copying your syntax letter for letter.
[Xperia Z Android Development] modsRule:
Sounds like the syntax may have changed slightly, grr... [I will check when I am next at my dev machine].

In the meantime, you may find it easiest to use the script here, which also handles the multi-user problems I explained in the OP, for you.
[Xperia Z Android Development] Dr_SUSE:
I checked out the script as is, with my information in the header, and I got an invalid argument error. I got the same when I changed the script to use busybox mount. Nothing even logged in dmesg after running the script.

I did notice that I do not have these two modules indicated in the script. Do I need them? Nothing (CIFS Manager, Mount Manager) seems to have installed them.

insmod /system/lib/modules/md4.ko;

insmod /system/lib/modules/nls_utf8.ko;

edit: I used the nexus modules provided with the script (md4, nls-utf8), but it wasn't useful: (Exec format error)
[Xperia Z Android Development] modsRule:
That is strange. What version of busybox do you have?

These are not included because they are compiled into this kernel version by Sony.

Surprise!</sarcasm>
[Xperia Z Android Development] Dr_SUSE:
Busybox v1.20.2-jb static 2012-11-25

edit: Updated to 1.21, no difference.

busybox mount -t cifs -o username=xxxxx,password=xxxxxx,unc=\\\\10.0.0.7\\Music \\\\10.0.0.7\\Music /storage/emulated/legacy/Music
mount: mounting \\10.0.0.7\Music on /storage/emulated/legacy/Music/ failed: Invalid argument

Sometimes it tells me it can't read fstab. I don't know if that means I'm getting warmer or colder.
[Xperia Z Android Development] modsRule:
I am using this version too.

I can confirm CIFS is working here with these modules using this syntax: (Updated first post to this too)

As superuser:

busybox mount -t cifs //x.x.x.x/share /path/to/mount -o unc=\\\\x.x.x.x\\share,username=myuser,password=mypass
[Xperia Z Android Development] Dr_SUSE:
That seems right, because now I'm getting a failure to mount on "Operation now in progress". That usually means the syntax is right, now I just have to see what I can figure out.

Does this module work with custom recoveries, such as CWM or TWRP? I'm asking because I saw another thread on XDA (OP was NUT) about how mounting and remounting /system as RO or RW was causing some devices to reboot, and one of the fixes, changing permissions on /sbin/ric, caused devices to send out dmesg's every 5 seconds complaining about denied permissions to /sbin/ric.

Well, second time I tried your new syntax to mount, my device rebooted, then I started seeing the dmesg's about /sbin/ric. Fixed that by resetting permissions.

Any relationship there?

I've been looking at a power consumption issue since.
[Xperia Z Android Development] modsRule:
I am running TWRP on a locked BL here. My dmesg is also full with messages about /sbin/ric (mine has mode 0644). Yet this mounting works.

I am not sure why you would get "Operation now in progress" when trying to mount.