Question [Kernel] [Help] Galaxy A32 [SM-A325F/DS] custom kernel is needed! For nethunter. - Samsung Galaxy A32 4G

Hello fellow developers,
I recently rooted my A32 without any prior knowledge. I did it so i could install Nethunter app on it to essentially turn it into a functional portable kali linux device. Foolishly, i did not check the compatibility for my device with full nethunter installatiion. Turn out my device has one of the most annoying kernel. Can any android guru help me in flashing my phone with right software to run nethunter fully (everything currently works except for HID and WIFI injection).
I have tried to connect my Ralink rt3070 external usb wifi adapter with otg but my phone is not currently recongnising it as a wifi adapter.
IMPOTANT TO NOTE:
When I write lsusb, it correctly lists the device. but in ifconfig, my adapter is not being listed. as far as my knowledge its a driver issue.
Thanks in Advance.
Burhan A.

You should say it was for nethunter, just flash this via magisk https://github.com/rithvikvibhu/nh-magisk-wifi-firmware

Thank you alot. I will try to flash it if i run into any problems, i will ask.

kilam9900 said:
You should say it was for nethunter, just flash this via magisk https://github.com/rithvikvibhu/nh-magisk-wifi-firmware
Click to expand...
Click to collapse
Hi,
I installed the drivers via magisk and rebooted. Look at all the attached screenshots. Unfortunately, my adapter is still not working with my phone I think my kernel doesn't support wifi adapters because on the GitHub page for wifi drivers, the person said that it might not work with such devices.
Anyways, one thing that is bugging me Is that when I type in lsusb, my adapter is showing properly with its default chipset. But after running ifconfig, I get no "wlan1". I only see the phone's adapter which is very weird.
Look at the screenshots
.

checksum.Burhan_Arif said:
Hi,
I installed the drivers via magisk and rebooted. Look at all the attached screenshots. Unfortunately, my adapter is still not working with my phone I think my kernel doesn't support wifi adapters because on the GitHub page for wifi drivers, the person said that it might not work with such devices.
Anyways, one thing that is bugging me Is that when I type in lsusb, my adapter is showing properly with its default chipset. But after running ifconfig, I get no "wlan1". I only see the phone's adapter which is very weird.
Look at the screenshots
.
Click to expand...
Click to collapse
I think i add to add support for external WiFi in the kernel

What? Sorry i did not quite understand the answer.

Related

USB Modem OTG Drivers for Stock ROM?

I recently purchased a Freedompop USB 4GB stick, but plugging it into the S4 (or any Samsung Android devices) doesn't work via OTG cable. The unit just isn't recognized at all, and I've figured out that Samsung has brilliantly left out drivers for USB modems/ethernet. Is there a driver out there that can be installed on the stock ROM without messing around with kernels? I'd really like to use the Wimax modem or ethernet, but I need a driver for it.
Any help would be much appreciated.
I'm facing the same problem with my S5 and wimax modem. The modem gets power and the light on the device shows it is connected, but there is no connectivity in the phone. It is a plug and play modem, which has android support. The phone doesn't recognize the modem. Is there any fix to this?
same issue on my SGH-M1919, running 4.4.4. tried the *30808# dialer, get the menu, and set it to MTP. Still no access to USB. my Win7 PC does not even see the phone when plugged in. Sucks. Kies and smart switch are equally oblivious to the phone.
Any ideas?
USB modems and OTG cables on stock roms.
I am sure that you are already aware of this brief module explanation, I am presenting it here for those that do not know how USB devices work.
Any time you plug an item into a usb port on your phone, that item returns a specific ID to the Linux kernel to inform it what the device you plugged in is. The kernel then uses a series of rules to determine what to do about that. Once it figures out what the device is and what is needed, the kernel then loads the appropriate kernel module ( a file that ends with .ko ) to handle that device. That module is the device driver.
In Linux, these modules can be compiled and/or added. However, for security reasons, the kernel may only accept "signed" modules, or it may not accept modules at all. Samsung usually signs their kernels, and due to manufacturer requests they generally require the kernel to not accept kernel modules at all. What this means is that IF your kernel would accept modules at all, it would need to be a signed module from the kernel makers. While there are tricks to get around this, it requires some pretty serious wizardry. Chances of finding said signed module: I think you would have better luck winning the lottery.
Back to the question at hand.
There are some *possible* ways around this:
You could first use Chainfire's app to see if your USB OTG cable setup is properly setup:
http://forum.xda-developers.com/showthread.php?t=1493325
(Be sure to slap his Chainfire's thanks button!)
and then you could download the PPP Widget:
https://play.google.com/store/apps/details?id=de.draisberghof.pppwidget3
There is a ppp widget 1, 2, and 3, and you may need to try them all. It will require root access and may not work, but it is the best option you have at this point, without buying new equipment, or changing the equipment you have.
If that does not work, then you would need to compile a new kernel for that specific purpose, with those modules or with the modules built in.
I hope that helps.

[Q] Anyone have ethernet access for N7 LTE working yet?

Hi
I am trying to get ethernet access on the N7 LTE using a USB OTG cable and USB-Ethernet adapter. Has anyone had success with patching the stock images, or is there a development ROM that has this available.
Thanks
Alex
Yes. Take a look here. http://code.google.com/p/android/issues/detail?id=58868
There's a lot to go through, but the condensed version is that a fellow made a new boot image that supports Ethernet connections via USB OTG. Your bootloader must be unlocked in order to flash the boot image.
Thanks, but it is still not working.
I have downloaded the N7 LTE patched boot image from the thread and flashed it. My N7 boots successfully but using the OTG cable + USB ethernet adapter the ethernet is not recognised (I am using a USB 2.0 ethernet adapter from the company 'Plugable')
I have also tried to extract, edit and repack an official rom, but I get an error during the repack stage. I am trying to use Android kitchen and cygwin.
So I am stuck. Help!
Update.
Using the patched boot image, then rooting, and then issuing the command 'dhcpcd eth0' in terminal I can browse the internet in Chrome. However GMail and Play store don't work connect correctly
Everything seems to work now except Youtube app.
Frustrating thing is that I have to connect to a wifi source, disconnect, and then ethernet works (I am not using a sim). If I dont connect first to wifi, the apps dont see the connection!
I went to use the Microsoft Remote Desktop app over ethernet and the device does not see a network! Would have thrown the device in the garbage disposal shute (if I had one).
Finally there is a solution to get ethernet working on the Nexus 7 2013 LTE with all apps without connecting to Wifi first and praying to the heavens. I found that installing the latest stable Cyanogen Rom works, so I can now use this needlessly hampered device for what I purchased it for.
Hope this saves someone some valuable time, unnecessarily wasted by ? at Goggle for reasons unfathomable.

[Q] Easycap via USB OTG not working

Hi,
I would like to use lg g3 as a screen for my reverse/backup camera in a car. Before buying the g3 I checked that it supports OTG and latest Android has easycap drivets built in so you do not have to root the phone.
I have got easycap with UTV007 chip which should be supported and I checked that it works on windows laptop. I have got USB OTG cable. If I connect mouse to g3 in otg mode it does work.
However if I connect easycap it does not. I am using one of the reverse camera apps. I ran usb host check program and got the following output:
Android.hardware.usb.host.xml OK
Handheld.core.hardware.xml : usb host not enabled
Tablet.core.hardware.xml : not found
When i tap "fix" i am getting "could not start su process".
To me it sounds like it needs root rights to update some configuration. G3 has factory android 5.0 installed. I have enabled usb debugging but it did not help.
Do you know what the problem is and how can I get easycap working?
I would prefer to not root the device neither to install custom roms because I have no experience (my first week on android)
Thanks in advance!
Forgot to mention: The phone is D855 v20i TWN XX Android 5.0 kernel 3.4.0 if it makes any difference
So I have installed busybox and terminal, no root yet.
I have found handheld.core.hardware.xml and it does not "include" anything to do with usb host- is this a problem?
Furthermore there are numerous files like video0, video1,...video31,video32 in /dev/ - can someone please help explain it?
What is the best thing to check next?
hello. Have you tried using an otg y-cable? It may make no difference, but perhaps a y-cable with power source may help.

[ROOT] How to enable OTG Support for Android

How to enable USB host API support
How to connect and debug Android device with ADB over TCP WiFi
How to enable USB host API support
Clone this wiki locally
https://github.com/452/USBHIDTerminal.wiki.git
How to enable USB host API support
Some Android devices have no support USB On The Go (OTG)
USB host mode is supported in Android 3.1 and higher
Also for this you need ROOT access.
To enable USB host API support you should add a file named android.hardware.usb.host.xml and containing the following lines:
<permissions>
<feature name="android.hardware.usb.host"/>
</permissions>
into folder
/system/etc/permissions
in that folder find file named
handheld_core_hardware.xml or tablet_core_hardware.xml
and add
<feature name="android.hardware.usb.host" />
into <permissions> section.
Reboot your device. USB host API should work.
Procedure:
adb pull /system/etc/permissions/tablet_core_hardware.xml
Update that file and create android.hardware.usb.host.xml as specified by Greg-q.
adb push android.hardware.usb.host.xml /system/etc/permissions
adb push tablet_core_hardware.xml /system/etc/permissions
Reboot.
Videos:
https://www.youtube.com/watch?v=oaXYMx8-SZ4
links:
http://stackoverflow.com/a/11992683/984156
http://stackoverflow.com/a/17036007/984156
Thank you I find this quite useful for my E5 (SM-S978L)
zenful said:
Thank you I find this quite useful for my E5 (SM-S978L)
Click to expand...
Click to collapse
Thanks for reply
I tried this all in my samsung e700h but not suceeded. If anybody suceeded in doing this way plse tell how???
You can try using NeOTG in grand 2/s3 neo forums. If you have a kernel support of OTG,then it'll work
How to check if my kernel supports native USB OTG support? Perhaps I have to check for it in "/dev/" or somewhere?
doesnt work on e500h with stock lollipop
Someone have the github files that were taken down?
Sent from my SM-A520W using XDA Labs
No OTG in E700H it seems...
The USB controller used in Galaxy E700H is Richtek RT-5033 which is apparent by examination of
PHP:
dmesg | grep 5033
This RT-5033 handles battery management and flash LED etc. but the driver for this in kernel given by Samsung doesn't have anything specific related to USB host/OTG.
There is a mention of a register for USB OTG/Host, but it's not documented.
So even if the chip RT-5033 supports OTG, without the support in kernel, OTG can't be enabled.
I want to enable OTG support on my Irulu X11 tablet, I can access a recovery menu and there's a lot of options in there. I can update from multiple source, I can reboot to bootloader... etc...
I don't have any knowledge in this 'domain' but I'm pretty good with that stuff usually.
If you can explain to me how I can edit those files to enable the USB OTG to work, I would bless you.
Basically, someone said that in the Recovery Menu your tablet is practically 'rooted', I'm not sure what that means and I hope someone can help me.
I got the file ' android.hardware.usb.host.xml ' and it's already got the permission in there but it's not in ' tablet_core_hardware.xml ' and when I try to edit it for File Explorer, I get an error when saving.
Actually, I think OTG support is already enabled.
If I can use a micro USB keyboard for my tablet, that means the OTG support is working right?
Then, my problem would be that all the apps I'm trying to use are not made my version of Android or something.
Let me explain.
I bought a USB microscope and I want to connect it to my tablet to I can inspect stuffs on the fly.
It's working perfectly fine on my computer, but I've tested 10 apps on my tablet and none are showing the camera view but they detect something in USB (USB Camera) and the leds on the lens are turning on.
What's the issue ?
Well, apparently my device doesn't have any built-in UVC support and that's why I cannot see the video of the camera.
Is it possible to add UVC support? I know at this point I should make my own thread but let's see..
Harshiv989 said:
No OTG in E700H it seems...
The USB controller used in Galaxy E700H is Richtek RT-5033 which is apparent by examination of
PHP:
dmesg | grep 5033
This RT-5033 handles battery management and flash LED etc. but the driver for this in kernel given by Samsung doesn't have anything specific related to USB host/OTG.
There is a mention of a register for USB OTG/Host, but it's not documented.
So even if the chip RT-5033 supports OTG, without the support in kernel, OTG can't be enabled.
Click to expand...
Click to collapse
I don't understand so much of this .. i tried too many videos to make the E7 compatible to otg and it worked but when i try to use the otg experimentally it doesn't work !!
Ok I've gotten to the end of the instructions, the last step, & I have an issue...
When I enter:
adb push android.hardwae.usb.host.xml/system/etc/permissions
I get:
adb.exe: push required an argument
I entered the command exactly as written so what is the problem & how can I fix it?
Thanks. .

Install TWRP or Magisk on a Samsung A5 2017 (SM-A520F) Android 8.0? - USB port broken

Im trying to get TWRP or Magisk installed on this phone so I can install Lineage, but the major stumbling block is that the USB port is broken.
It will only charge from the port. Ive tried looking for a replacement usb board from parts resellers, but have only been able to find ones for different A5 models, or the USB port itself which would require my buying a heatgun.
LSUSB / DMESG never reports anything when its plugged in and every now and then when I charge it the phone displays a "Moisture in USB port" message, despite it having been in a box for several years. I think it was stress on the USB cable that killed it initially.
Ive read that you can use ADB over TCP instead, but this requires root access to run the commands if you cant start off by connecting with a USB cable, so no joy there.
Is it possible to install Magisk via Magisk manager on a non rooted phone?
Looking at threads on the Magisk github page It seems like I need to build a custom ROM using a stock one + some modifications from a python script that Magisk manager can then try to install. Where can I get those ROM's, if this is even possible?
More info about the device / Android version below:
Android 8
Kernel 3.18.14-13712092-QB20832987
[email protected] #1
Thu Nov 29 08:29:34 KST 2018
R16NW.A520FXXU7CRK7
SM-A520F
So, Ive found and downloaded the stock firmware for my phone (SM-A520F_1_20200211163854_iyofhdwau9_fac.zip). I let the phone update to the latest official update as I couldn't find a decent mirror for the older version.
Im now trying to follow the instructions for payload_dumper so I can patch payload.bin, but the 2.4 GB file didnt have this inside, only these files that im unable to extract any further.
AP_A520FXXUDCTB1_CL13712092_QB29074577_REV00_user_low_ship_meta.tar.md5
BL_A520FXXUDCTB1_CL13712092_QB29074577_REV00_user_low_ship.tar.md5
CP_A520FXXUDCTB1_CP15068674_CL13712092_QB29074577_REV00_user_low_ship.tar.md5
CSC_OXA_A520FOXADCTB1_CL17962365_QB29105314_REV00_user_low_ship.tar.md5
HOME_CSC_OXA_A520FOXADCTB1_CL17962365_QB29105314_REV00_user_low_ship.tar.md5
Can I get the OTA Update zip file from somewhere on the phone?
find -name *.zip hasnt turned up anything obvious.
Mikebdict said:
Im trying to get TWRP or Magisk installed on this phone so I can install Lineage, but the major stumbling block is that the USB port is broken.
It will only charge from the port. Ive tried looking for a replacement usb board from parts resellers, but have only been able to find ones for different A5 models, or the USB port itself which would require my buying a heatgun.
LSUSB / DMESG never reports anything when its plugged in and every now and then when I charge it the phone displays a "Moisture in USB port" message, despite it having been in a box for several years. I think it was stress on the USB cable that killed it initially.
Ive read that you can use ADB over TCP instead, but this requires root access to run the commands if you cant start off by connecting with a USB cable, so no joy there.
Is it possible to install Magisk via Magisk manager on a non rooted phone?
Looking at threads on the Magisk github page It seems like I need to build a custom ROM using a stock one + some modifications from a python script that Magisk manager can then try to install. Where can I get those ROM's, if this is even possible?
More info about the device / Android version below:
Android 8
Kernel 3.18.14-13712092-QB20832987
[email protected] #1
Thu Nov 29 08:29:34 KST 2018
R16NW.A520FXXU7CRK7
SM-A520F
Click to expand...
Click to collapse
Try using non-PC root methods like the old KingRoot or something new/similar. :good:
MaDaLiNoSt said:
Try using non-PC root methods like the old KingRoot or something new/similar. :good:
Click to expand...
Click to collapse
Cheers. Its been an adventure in uninformed badly written web articles and spyware ridden apps installed via APK, but I dont think anything can actually do it to an Oreo device.
Kingo root claims it can, but just crashes when you try to root.
Im going to try and find a new usb board and tool from some where and pull it apart
edit - sadly the usb port is part of the mainboard, so they arent actually that cheap. I set up an ebay watcher for broken / old ones. :<

Categories

Resources