the title pretty well describes it. I've also disabled knox and have set SELinux to permissive.
symptom: plug in otg cable, put on thumb drive....nothing. search in file manager - nothing.
I've messed with, er, personalized the tablet and honestly can't recall all I've done, but USB OTG once worked and now doesn't. I've played with many of the 'troubleshooter' apps from the store [all useless, IMO, because all they say is yes or no].
Kernel support is there but no devices are recognized. The .xml file is present in system/etc/permissions or whatever the correct path is.
I've tried 2 different OTG cables and two different thumbdrives.
I've tried with selinux permissive and enforcing
I've rebooted both with and without the otg usb drive attached.
where can i look? are there any troubleshooting tools that give actual information?
i'm reasonably intelligent (PhD in physics) but not all that savvy with android (which, btw, i hate ) but i was once a unix sysadmin, so i fear no cli.
device is rooted, twrp installed if i recall correctly. completely unwilling to change kernels (unless there's a stock 7.1 or 8 )
thoughts? suggestions?
<rant>
[why do i hate android? why take a Ferrari and fix it so it will only go 50 mph? this is powerful hardware and software, but we're all treated like little children with no root control, hoops to jump through to change selinux, Samsung's god-awful knox, etc. etc. And android networking needs to get out of the 80s. DOS/Novell was better. i want to share drives from my tablet, and i want to mount drives from my PC so the contents are as available as the internal memory.]
</rant>
Using N4N 1.3 kernel with stock I6, TWRP, rooted using Magisk and OTG working flawless in my T810.
Read the changes: https://forum.xda-developers.com/tab-s2/development/kernels-n4n-i6-i5-710-715-810-815-t3700601
Related
Hello XDA,
Im back again with another personal project I'm having some issues with. First, a bit of explanation as to why I've chosen to attempt this.
I was running a heavily modified stock rom with nethunter 5.1.0 that was incredibly unstable, and eventually crashed right out on me (modified using root based apps so the crash was my fault) .
So I grabbed the CM13 snapshot for hammerhead, and layered on nethunter 3.0 (big fan since BT3), only to find out my wifi card isn't supported. On 5.1.0 I also had this issue
(see here http://forum.xda-developers.com)/showpost.php?p=64400679
which I managed to fix with a simple source build with a few extra options checked in menuconfig.
Sadly it doesn't seem to be quite that easy with CM13 and marshmellow.
I'm using the DWA160-b2 wifi adapter, which from my research, uses the rt2800usb chipset, which supposedly points to the rt5572 driver. So, I enabled the corresponding options in menuconfig , although I cant remember the exact wording at this moment (using winblows to write this, and not my linux) and I still have no life in my wifi card.
So, after even more research, I found out I should be able to cross-compile the required drivers using the arm-eabi tools. However, after trying I've come to the conclusion that there is no arm based config for this driver. So then I tried backports, and recieved an error about incomplete linux headers (I assume because of the chroot, because my headers are all installed).
Now finally my question:
How do I go about compiling this driver for arm? Or is there a know working arm driver for this particular card? As I have not come across one in my searching. Also please dont say get a new wifi card lol I have a few different usb wifi cards, all with the same issue (albeit different chipsets).
Are u trying to port kali kexec to cm13 kernel?
Sent from my fx-82MS with CM-CAF
Hi all,
my Huawei P9 is running Android 7.0 (EMUI 5.0.1) rooted.
As "Build" is shown "NRD90M test-keys", but as this doesn't correspond to any of what I have seen as valid build numbers so far, I guess this is wrong and somehow related to the Nandroid backup restore I did after upgrading this phone from Android 6 to 7... Anyway, my question is this:
What's the best option for me now to make this phone mass storage mode compatible?
The USB Mass Storage Enabler app claims that the current kernel does not support Mass Storage Gadget & FUSE and thus the app won't function.
So it seems that I need a new kernel.
- Is there a kernel available that I can use to simply substitute my current kernel?
- Can / should I easily compile my own one? (I have done that 15 years ago with Linux kernels, since then no kernel compilation experience anymore). If so, where do I start?
- Do I have to use a custom ROM? Which one do you recommend for that feature to work and for a lightweight system with high performance, flashable without muhc hassles from my current status?
Thanks a lot!
i think you updated to a beta firmware,
this thread may help,
good luck
Du you mean, a non-beta will contain the necessary kernel options?
daniel908 said:
Du you mean, a non-beta will contain the necessary kernel options?
Click to expand...
Click to collapse
not sure, but some had similar issues with the nougat beta.
[Post deleted] - sorry, didn't find a delete button, so just deleted the content.
On another P9 with Android 7.0 / EMUI 5.0.1 (Build-Nr EVA-L09C432B394) the USB Mass Storage Enabler app also doesn't work for the same reason.
So I think that beta (if it really is one - the Nandroid backup title of the system with build number shown above has the same string in its directory name - maybe when restoring the Nandroid backup, that string is written into the "Build" field?) is NOT the reason for the mode not working.
Anyone here who uses that app and has USB storage mode support on a (rooted) stock Android 7.0 / EMUI 5.0.1 on a P9?
The app says (Google Play) that it works only on "selected" Samsung and Sony devices (btw, it"s rated only 3.5)
I just tried (Magic zRainbow v3 which is based on v394 and rooted Magisk), it says it doesn't find the lun file and not compatible with the kernel. IMO, it can't work here (I don"t know would it work with AOSP firmwares instead of stock).
Btw if you really restored TWRP backup from MM (EMUI 4.1) to N (EMUI 5), you are lucky that you didn't (soft) brick the phone
The app worked very well on my older P9... so it's not really limited to "selected Samsung and Sony devices".
I didn't get a notice about missing LUN file, but kernel incompatibility message was shown here, too. However, as far as I know the kernel can be replaced easily by flashing a new kernel? Question is then only, how to get my hands on a compatible kernel. Compile my own one? I have never done this with Android.
Or is there any other method to enable mass storage mode for the microSD card, so I can sync my stuff easily with the Mac on a daily schedule without having to remove the card from the phone everytime?
I tried other (e.g. MTP-based) sync solutions, but they all fail badly (either crash or take ages) when keeping those about 2.000.000 small JPEG files in sync that I need on the phone's microSD card. Those files are virtual tours / gigapixel image tiles, that I host on the phone to be able to present those virtual tours to clients without carrying a computer with me).
Unreal.... can a group of professionals get together and spend a day cracking the bootloader and root the Verizon version note 5 not even one custom rom for this device all other models have gotten there attention we need to crack this note 5 please
so far no one can hack n920v bootloader. Me also waiting for this info. Until now my n920v still not root yet. huhuu
It does not bypass bootloader
It's funny, in the UART logs running an engineering s-boot, it will say that an invalid image was detected, and it will reboot to avoid tripping Knox. A t-mobile phone I got, I accidentally flashed a Verizon image, and there went Knox, before I had intended to. Verizon has probably drastically reduced the unexplained returns, with the lies suggested on here to use by doing that. That might be a main motivation to consider.
But back to the subject, before I ever tried attempted to understand Magisk (which I used on my XT1575), which sort of does the same thing I did, but still allows selinux, was to use the engineering kernel, and did the following:
& Mount /system as loopback in /data/systemmirror
& Mount a loop back image over /system, which effectively hides it
& Link to each file in the loopback to the mirror, except for what I didn't want, and add what I did want. I even got xposed, microg/unifiednlp working like that. I didn't want to use supersu, but I imagine it can be done too. Some files had to be on the loopback system because uh I think it didn't like dynamic linking some library files that were links, that was fun to debug again and again and again until it worked.
& Set selinux permissive, because links aren't normally allowed, and I couldn't figure out how to make that work in the policy, and I could have reloaded it with the tools in the supersu apk if I knew what I was doing.
Thus, a tethered root is made. Tethered. Every boot up, you have to log in with adb to run the shell script that mounts everything, changes selinux, and kills system_server, effectively rebooting it. I could not figure out another way. It worked, minus samsung pay.
While that doesn't sound so bad, I went into the subway, was playing my hacked up version of shattered pixel dungeon, and the kernel crashed. Man, I that was a bummer. Still haven't rooted it properly.
If there's a fwbl1 or something that breaks the chain of trust from a developers SDK, sboot could be modified to load any binary without tripping Knox into an existing sboot probably.
I've removed so much stuff from this post so many times while preparing the draft to submit to my comment editor, I wonder how many times before I'm forced to decide whether a sign post visible in 1/9th of a picture is part of a street sign or not.
The Bug:
Connecting Phone to PC using USB, no Notification appears for switching USB modes.
The Fix:
Go into Developer Settings and under 'USB Configuration' change option to 'MTP'. This doesn't survive reboots though and has to be repeated.
What we know:
There have been many reports of MTP issues with Oreo:
https://www.theandroidsoul.com/unable-to-connect-pixel-nexus-to-pc-android-o-fix/
https://forums.oneplus.com/threads/...on-menu-missing-mtp-after-oreo-update.688153/
https://productforums.google.com/forum/#!msg/phone-by-google/DfpqXN1UfWY/IloXRZB3CAAJ
https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU
The early reports of this bug date back to late 2017 when the only devices on Oreo were using Official Manufacturer ROMs. Particularly Nexus and Pixel devices. It looks like reports of the bug declined as the manufacturers got to grip with Oreo and fixed the issues. It seems to me that the bug exists in AOSP and so custom ROMs built upon it are now the only ones facing this issue.
FIXED:
Workaround fix:
Build prop edits applied by flashable .zip, from this thread:
https://forum.xda-developers.com/re...er-development/zip-mtp-fixer-devices-t3606872
Permanent Fix..
LOS 15.1 maintainer has fixed this in LOS Kernel:
https://review.lineageos.org/#/c/LineageOS/android_kernel_oneplus_msm8996/+/215091/
Caesium Kernel has also been updated with the patch.
Thanks to dianlujitao for finding the fix and to MSF Jarvis for getting it out there to test.
I never had such an issue on OxygenOS, LineageOS and Resurrection Remix (usually with custom kernel, Magisk's root and Xposed). Connecting to Windows 10 x64 PC with original Dash cable. USB debugging disabled. I didn't tinker with USB mode in developer settings at all, because I didn't have to. My current config in signature.
Other phones with Oreo onboard in my house are Nexus 5X with LOS 15.1 + ElementalX + Magisk + Xposed and Xiaomi Redmi Note 4X with similar to N5X's config, both of them are also ok.
przemcio510 said:
I never had such an issue on OxygenOS, LineageOS and Resurrection Remix (usually with custom kernel, Magisk's root and Xposed). Connecting to Windows 10 x64 PC with original Dash cable. USB debugging disabled. I didn't tinker with USB mode in developer settings at all, because I didn't have to. My current config in signature.
Other phones with Oreo onboard in my house are Nexus 5X with LOS 15.1 + ElementalX + Magisk + Xposed and Xiaomi Redmi Note 4X with similar to N5X's config, both of them are also ok.
Click to expand...
Click to collapse
I wonder if having Magisk installed does something to remedy the issue. It might explain why it doesn't affect everyone.
Hello guys
I have a rather "funny" issue with my MTP/USB connection on PC; All files (apk, zip etc) except media (mp3, mp4, jpeg etc) show up as Folders in windows file explorer when i connect the phone via MTP/USB. I have the Oneplus USB Drivers installed. Due to this I cant transfer any file (except media) from the phone (they are all folders).
I have tried connecting it to another computer but the issue is still there; which makes it rather an issue on the phone itself. Any help?
masaichris said:
Hello guys
I have a rather "funny" issue with my MTP/USB connection on PC; All files (apk, zip etc) except media (mp3, mp4, jpeg etc) show up as Folders in windows file explorer when i connect the phone via MTP/USB. I have the Oneplus USB Drivers installed. Due to this I cant transfer any file (except media) from the phone (they are all folders).
I have tried connecting it to another computer but the issue is still there; which makes it rather an issue on the phone itself. Any help?
Click to expand...
Click to collapse
Which ROM/Mods are you using? Any file System changes from default?
You could try clearing Cache/Data from Media Storage.
DirkGently said:
Which ROM/Mods are you using? Any file System changes from default?
You could try clearing Cache/Data from Media Storage.
Click to expand...
Click to collapse
I'm on stock OOS 5.0.1 Android 8.0.0 (Rooted), Magisk 16.0 with VIPER4Android FX for Magisk 15 installed.
I already tried cleaning Cache/Data but the issue still exists.
Additional Info: on the PC (This Computer), the phone displays as either a Keyboard or CD drive (different from the one with USB drivers) when installed
masaichris said:
I'm on stock OOS 5.0.1 Android 8.0.0 (Rooted), Magisk 16.0 with VIPER4Android FX for Magisk 15 installed.
I already tried cleaning Cache/Data but the issue still exists.
Additional Info: on the PC (This Computer), the phone displays as either a Keyboard or CD drive (different from the one with USB drivers) when installed
Click to expand...
Click to collapse
Did it always do this or has something changed? You have the phone in MTP mode when you plug it in? Does Device Manager in Windows flag any issues? See if this helps:
In Device Manager, (with the phone connected), look for your phone in the list. Right click on Phone, Update Drivers, Driver from Computer (Local Search), Select "MTP USB Device".
masaichris said:
Additional Info: on the PC (This Computer), the phone displays as either a Keyboard or CD drive (different from the one with USB drivers) when installed
Click to expand...
Click to collapse
I also have the keyboard instead of phone, but no problem with files here
Fixed. OP updated.
Thanks to @helmiau for being a superstar.
Mind sharing?
paul_damian said:
Mind sharing?
Click to expand...
Click to collapse
Already have. Read the OP.
Can't guarantee this works for every USB connection problem that people might have, but it fixes the one outlined in the OP. At least for me. YMMV.
As always, Nandroid before flashing. Nobody should need telling that though.
DirkGently said:
The Bug:
Connecting Phone to PC using USB, no Notification appears for switching USB modes.
The Fix:
Go into Developer Settings and under 'USB Configuration' change option to 'MTP'. This doesn't survive reboots though and has to be repeated.
FIXED: Build prop edits applied by flashable .zip, from this thread:
https://forum.xda-developers.com/re...er-development/zip-mtp-fixer-devices-t3606872
I don't understand how it works, only that it does work!
Click to expand...
Click to collapse
With this zip you are enforcing USB modes and enabling USB debugging on each boot
przemcio510 said:
With this zip you are enforcing USB modes and enabling USB debugging on each boot
Click to expand...
Click to collapse
That's great! Enabling USB modes at Boot is exactly what is needed. It's what is supposed to happen but for some reason hasn't been. It doesn't override what you have set in Dev options though. I run with USB Debugging disabled in Settings, and it remains that way.
It's MTP that i'm most concerned with and so far everything is working normally!
Hi mates
I am new to rooting n stuff.
But i am impressed by the MAGISK SYSTEMLESS CONCEPT.
I would like to suggest some development pathways.
1. Can drivers and firmwares be added systemlessly?
Eg. Add support to AWUS036H/ALFA wifi adapter and enable monitor mode
2. Samsung pay : Systemless support to fake Knox Status
And so on
My device is note 9 exynos. Any suggestions? Am i thinking right or wrong?
Not really my area of knowledge, but I believe neither is possible with Magisk.
Magisk does it's thing on the /system and /vendor partitions and I think that neither of your mod examples have anything to do with those partitions. #1 likely has to be added to the kernel (or something like that) and #2 has its own protected partition (or something like that, if I remember correctly) and cannot be altered.
Hopefully someone that actually knows what they're talking about will chime in and let us know if I'm just spouting nonsense...
Delete
There is actually a set of wireless adapter firmwares available through a Magisk module but your kernel also needs support for external USB network adaptors. In order for that to be accomplished your kernel needs to be compiled with that support. Magisk works on too high of a level to add that support through a module afaik.