Installing Nethunter
1. Download and install magisk module called KaliNethunter
2. Go to offensive security website and download generic arm64 nethunter image
3. Extract and install following apps from downloaded archive: NetHunter.apk, NetHunterTerminal.apk.
4. Extract kalifs-arm64-full.tar.xz on your phone.
5. Open NetHunter app and grant permissions and root permission
6. Open hamburger menu, select Kali Chroot Manager, select location where you had extracted kalifs-arm64-full.tar.xz and start installing chroot
7. Wait some time (~10 minutes)
8. Start chroot. Now you can use nethunter app and nethunter terminal app.
Enabling monitor mode on built-in wifi module
0. I could not enable it on custom roms. On stock 082 it worked, but there are some problems. Contact me if you have any info about enabling monitor mode on roms except stock.
1. Open nethunter app, go to custom commands
2. Click run on "Start wlan0 in monitor mode"
3. Now wlan0 is in monitor mode. I've tried capturing handshakes using airodump-ng, it worked. However, when I tried deauth attack using aireplay-ng, wlan0 was stuck on channel 0.
4. Note that if you turn wifi on/off or try to disable monitor mode, your phone will turn off.
5. Alternative way: you can enable monitor mode using other apps, like penmon. However, your phone will still turn off if you do anything to wlan0 while it is in monitor mode.
Using external wifi adapter
0. Your wifi adapter must support monitor mode. External adapter won't work without a kernel that supports it. I've built one based on darkonah (many thaks to @travarilo ). Atheros HTC based adpaters are not supported!
1. Flash the attached kernel (the latest version is NH_kernel_v2.zip).
2. Now you can use your exernal adapter.
Enabling monitor mode on external adapter
0. I only tested it with Alfa AWUS036NH (chipset ralink3070), but the instruction may be similar for other adapters
1. First, let's install firmware for your wireless adapter
Code:
apt update
apt upgrade
apt install firmware-ralink
2. Execute command iwconfig and check if your adapter is present there. For me it was displayed as wlan1
3. Turn your adapter off and put it into monitor mode
Code:
ifconfig wlan1 down
airmon-ng start wlan1
4. Check airmon-ng output. It will say you that your adapter is now in monitor mode and will give you new adapter's name (for me it was wlan1mon)
5. Now you can use monitor mode on your adapter (for example, to run airodump-ng)
P.S.: Do it at your own risk and don't use this info in illegal purposes. Only you are responsible for your actions.
Thank you very much sir! Really appreciate your work time and efforts!
Just one small query about what rom and firmware are you using?
Heven11 said:
Thank you very much sir! Really appreciate your work time and efforts!
Just one small query about what rom and firmware are you using?
Click to expand...
Click to collapse
Right now I'm using stock rom 082 (and fw 082, respectively), but it would be great if you tested this guide on any custom rom (if you are not going to use built-in wifi module. If you are, I recommend you to use stock rom)
Ok thank you!
tutaf said:
Installing Nethunter
1. Download and install magisk module called KaliNethunter
2. Go to offensive security website and download generic arm64 nethunter image
3. Extract and install following apps from downloaded archive: NetHunter.apk, NetHunterTerminal.apk.
4. Extract kalifs-arm64-full.tar.xz on your phone.
5. Open NetHunter app and grant permissions and root permission
6. Open hamburger menu, select Kali Chroot Manager, select location where you had extracted kalifs-arm64-full.tar.xz and start installing chroot
7. Wait some time (~10 minutes)
8. Start chroot. Now you can use nethunter app and nethunter terminal app.
Enabling monitor mode on built-in wifi module
0. I could not enable it on custom roms. On stock 082 it worked, but there are some problems. Contact me if you have any info about enabling monitor mode on roms except stock.
1. Open nethunter app, go to custom commands
2. Click run on "Start wlan0 in monitor mode"
3. Now wlan0 is in monitor mode. I've tried capturing handshakes using airodump-ng, it worked. However, when I tried deauth attack using aireplay-ng, wlan0 was stuck on channel 0.
4. Note that if you turn wifi on/off or try to disable monitor mode, your phone will turn off.
5. Alternative way: you can enable monitor mode using other apps, like penmon. However, your phone will still turn off if you do anything to wlan0 while it is in monitor mode.
Using external wifi adapter
0. Your wifi adapter must support monitor mode. External adapter won't work without a kernel that supports it. I've built one based on darkonah (many thaks to @travarilo ). Later I'll update this post to list adapters that should be supported by tis kernel.
1. Flash the attached kernel.
2. Now you can use your exernal adapter.
Enabling monitor mode on external adapter
0. I only tested it with Alfa AWUS036NH (chipset ralink3070), but the instruction may be similar for other adapters
1. First, let's install firmware for your wireless adapter
Code:
apt update
apt upgrade
apt install firmware-ralink
2. Execute command iwconfig and check if your adapter is present there. For me it was displayed as wlan1
3. Turn your adapter off and put it into monitor mode
Code:
ifconfig wlan1 down
airmon-ng start wlan1
4. Check airmon-ng output. It will say you that your adapter is now in monitor mode and will give you new adapter's name (for me it was wlan1mon)
5. Now you can use monitor mode on your adapter (for example, to run airodump-ng)
P.S.: Do it at your own risk and don't use this info in illegal purposes. Only you are responsible for your actions.
Click to expand...
Click to collapse
I love it when you put 0 first instead of 1. A true caffeine blooded being. Btw im on .087 fw ver (X00TDB var.). Gonna try the image out and see if internal wifi module works. Im running BT5 on my xp era machine.
ImperialNuggets said:
I love it when you put 0 first instead of 1. A true caffeine blooded being. Btw im on .087 fw ver (X00TDB var.). Gonna try the image out and see if internal wifi module works. Im running BT5 on my xp era machine.
Click to expand...
Click to collapse
What is BT5? I got it
does the kernel support atheros chipset: TL-WN722N v1?
ive done everything i could but my device still dont detect my adapter
...
apt update
apt upgrade
apt install firmware-atheros
airmon-ng... nothing..
xda_u$er said:
does the kernel support atheros chipset: TL-WN722N v1?
ive done everything i could but my device still dont detect my adapter
...
apt update
apt upgrade
apt install firmware-atheros
airmon-ng... nothing..
Click to expand...
Click to collapse
I had some problems building kernel, so I had to disable support for Atheros HTC based cards. You can try to add it as a loadable kernel module.
0. Flash the attached kernel, download and extract module file (ath9k_htc.ko) from zip
1. Go to NetHunter Terminal app and start androidsu shell
2. Go to the folder where you had extracted ath9k_htc.ko. For example:
Code:
cd /storage/emulated/0/Download
3. Install the module
Code:
insmod ath9k_htc.ko
If it throws error like "no such file or directory", check dmesg
4. Check if the module is installed
Code:
lsmod
You should see the name of the module (ath9k_htc) and its size (check attached screenshot)
5. Now try executing airmon-ng in kali terminal.
Module doesn't persist between reboots. Let me know if it works for you, I'll try to automate module installation process.
Throws me error..
xda_u$er said:
Throws me error..
Click to expand...
Click to collapse
Could you please execute dmesg command right after getting this error and show me the output?
its huge, so I put it in notepad
xda_u$er said:
its huge, so I put it in notepad
Click to expand...
Click to collapse
Sorry, my bad, I gave you the module for the previous kernel build (it has different name, that is why insmod throws error). Please try installing the attached module. If anything goes wrong, send me dmesg again.
@xda_u$er did it work?
Well, the installation went ok, but the external adapter its not working, it is not recognized by the device.
xda_u$er said:
Well, the installation went ok, but the external adapter its not working, it is not recognized by the device.
Click to expand...
Click to collapse
Sorry, I don't know what to do with that. You may try to find an old version (~2019) of TRB kernel, I've heard that its developer tried to enable Atheros HTC based adapters support.
Hii again! Your kernel is working amazingly good!and thanks to your guidance nethunter is working fine for me!
But I am unable to perform hid attacks are you able to do them? Like using our phone as a bad usb ! Does this also need kernel modification?
Heven11 said:
Hii again! Your kernel is working amazingly good!and thanks to your guidance nethunter is working fine for me!
But I am unable to perform hid attacks are you able to do them? Like using our phone as a bad usb ! Does this also need kernel modification?
Click to expand...
Click to collapse
As far as I know, it does. I haven't tried any usb attacks, but I'm going to.
Heven11 said:
Hii again! Your kernel is working amazingly good!and thanks to your guidance nethunter is working fine for me!
But I am unable to perform hid attacks are you able to do them? Like using our phone as a bad usb ! Does this also need kernel modification?
Click to expand...
Click to collapse
I've enabled everything that should be enabled to make bluetooth attacks work, but they don't. The adapter is recognized by the system, but nethunter app doesn't see it. I would be very thankful if you tested bluetooth with new kernel. Btw, usb attacks work with new kernel too. I've tried launching firefox on my PC, it worked. This is a really cool thing
Firstly sorry for late reply! I had to reset my device since I was testing some android 11 rom and Thank you sooooo much for V2 of this kernel,usb/hid is working like a charm but I haven't tried bluetooth yet but will definitely try it soon since I don't know how to do it!
Please continue the development of this kerneland remember you are a legend!
Thank you again!
Hii! I want to try Kali nethunter on my device but there are many bugs that I am facing my internet is not working in Kali not monitor mode is working!
Can you please make a nethunter ROM!please
Or give me a backup of your ROM KERNEL AND FIRMWARE THAT I can flash through TWRP !
Please!
PS. Currently I am using Android 10 corvus os and nethunter is not working!
Related
This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread
dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?
hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them
thats amazing, will try it as soon as possible
SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx
Work work work, thank you bro .
uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.
I tried it, it's working. Thanks for the mod
I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.
Ouya SuperScript
By TehCrucible
v0.1
INTRODUCTION
So I originally wrote this batch script to simplify and combine some of the most frequently used tweaks on the forums for my own sake, to speed up my tinkering with the Ouya but I've decided to clean it up and upload it in case anyone else wants to use it.
This script is designed as a "one-click" modification tool for a stock Ouya on the latest firmware. Please read this guide carefully.
I ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSS. This script is built on the work of many others much smarter than myself and be sure to check the credits.
SO WHAT DOES IT DO?
In a nutshell:
- Install Clockworkmod Recovery
- Root Ouya
- Install Xposed Framework
- Install Google Play Store
WHAT DO I NEED?
- A Windows PC. I have included drivers for both x86 and x64.
- A Micro USB cable.
INSTALLATION OVERVIEW
1. Update your Ouya to latest stock firmware
2. Install ADB drivers
3. Run the script
4. Play some games!
There's a more detailed step-by-step in the included README.txt file.
KNOWN ISSUES
- None
CREDITS & THANKS
WonderEkin
mybook4
elmerohueso
fatesausage
DOWNLOAD
Here
Thanks a lot for this. A lo of people have been asking about an automated method to get the play store running on the OUYA...
Great works. I just think of root my ouya....
A quick update:
It's working. I'm on the latest firmaware which is JZO54L-OUYA, kernel version 3.1.10-g780994a. Completely stock, but I had already rooted my OUYA.
Anyway, I enabled the Wireless ADB which will instantly show you the ip and port, installed the drivers for 64bit. Then open CMD and type: adb connect "iport"
Then I ran the superscript and everything went fine.
Hope this helps. I didn't even have to connect with a wire.
But I guess if you wanna install the CWM recovery you should be connected with a wire...
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
Did you install the drivers right? If yes, then you should open the folder where you extracted your files and right click while holding shift then choose open CMD here. Then write: adb devices
If your device is there, it will give you an output of the IMEI and name of device
From there, you can then tell us what the error is and hopefully we can resolve it...
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
that happened to me yesterday, but I overcame it by have my computer plugged into the Ouya then reboot the ouya and as soon as the computer recognized it started the script and it worked.
but I have an issue too
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesnt recognize the ouya....
unkoil said:
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
Click to expand...
Click to collapse
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
TRMB said:
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesn't recognize the ouya....
Click to expand...
Click to collapse
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.[/QUOTE]
I have tried both from my windows 7 computer and 8.1 laptop. It showed up just as you said "missing driver", sent it to the drivers part of SS to get the driver, it said it installed but when i run the SS and hit option "1" it comes up blank...
ahmadshawki said:
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
I am having the same issue but not only with this method, I have also tried to install CWM with oneclicks auto and manual method to no avail.....
any suggestions?
Click to expand...
Click to collapse
always says it installed but will only boot into stock recovery
TRMB said:
always says it installed but will only boot into stock recovery
Click to expand...
Click to collapse
I can see from your posts that you tried everything and I'm so sorry that I'm just a user and not a developer or something. May be you can try sideloading terminal and try CWM manually (if you haven't already) or sideload ROM Toolbox and try the flash recovery option.
That's all I got. But if I were you, I won't bother about the CWM at all. It's useless.
As for the Play store, try the mod that I attached in my reply and let me know if this one works for you...
Unfortunately the link is not working. Is it possible to update it, please?
What I do if my micro usb is broken :/. I only have wireless adb
.. nice .. now my ouya will run again .. thanks
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
vinirockman said:
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
Click to expand...
Click to collapse
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
vinirockman said:
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
Click to expand...
Click to collapse
.. CWM need wired usb keyboard no navigate .. i don't remember if it can do it via bluetooth
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Johnny TDN said:
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Click to expand...
Click to collapse
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
You must do on the all files. Now only android.hardware.usb.host.xml
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
Do it for all of the files. Not only on android.hardware.usb.host.xml
doesn't work..
you must make changes to kernel also for otg to work
snapdesign said:
doesn't work..
you must make changes to kernel also for otg to work
Click to expand...
Click to collapse
Did you checked all the boxes on the permissions?
Johnny TDN said:
Did you checked all the boxes on the permissions?
Click to expand...
Click to collapse
what do you see in the photo? also otg needs support from kernel... it doesn't work without it
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
BadWolfYe said:
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
Click to expand...
Click to collapse
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
snapdesign said:
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
Click to expand...
Click to collapse
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
BadWolfYe said:
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
Click to expand...
Click to collapse
well, someone is working on a cm build... when that will boot we should have a kernel with multirom...
i tried on more way too for OTG already,,, added lines too vold.fstab etc etc but it wont support,,,
UPDATE
My phone is rooted and i am testing it. Hope it works on mine. If it doesn't, the post should be removed
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
The value changed... I forgot my USB adapter in the car... will update the in a few minutes... if it works you resolved a big thing in what..2 days from having the device? great dev... thanks!
EDIT: unfortunately it doesn't work on my device... also after reboot the value changed to OFF again... great find although
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
WORK !!! THANK YOU !
- install from Playstore Universal Init.d
- Open Universal Init.d and activate support
- Create a generic text file Ex. usbotg in /etc/init.d folder with the following content
#!/system/bin/sh
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
!!!! Replace "f4000000" with the value found in your smartphone (my: ff100000) !!!!
- give to the file 755 permission
- reboot
I used Root Explorer to do all.
Enjoy !
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
ThankS!!!! It worked but, there are some troubles:
after using that command doesn't work the usb cable phone - PC (need reboot or to write "hostoff" instead of "hoston");
after rebbot need again to rewrite the command.
With universal Init.d it can be a little easy cause you can make 2 file ( 1 for hoston and 1 for hostoff) and just run them from app, so with 2 touch you can enable and disable otg instead of wirting everytime the command using terminal.
Edit: universal init.d doesn't work properly so I used a script runner and just run from it (with root permissions) 1 of 2 script (enable, disable).
Edit2: Look these images to see what I've done(don't need to reboot phone after):
Image 1: http://prnt.sc/ckk9hs
Image 2: http://prnt.sc/ckka26 (used this app: https://play.google.com/store/apps/details?id=com.snclabs.scriptrunner&hl=it)
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Noel.89 said:
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
SevenSlevin said:
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
Click to expand...
Click to collapse
Really how did you get yours to work maybe I'm doing something wrong putting the file in wrong place
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
##I DO NOT ACCEPT FOR BRICKED DEVICES, AND ILLEGAL WORKS##
!!!USE WITH CAUTION!!!
Device: Sony Xperia Z5 Compact
OS: LineageOS 14.1 / Android 7.1.2
Thanks for helps to: @Joeisgood99
1.Take a full backup or only Boot partition
2.Flash Nethunter zip
3. Reboot
4. Open FDroid Nethunter, Upgrade Nethunter apps
5. Open Nethunter app, give permissions
6. Open Nethunter Terminal, give permissions and: apt-get update
7. Open Nethunter app,Navigate to Chroot (metapackages) manager, select Nethunter and press install/upgrade
Unofficial Download Link: https://drive.google.com/file/d/1iFDtMelkcDjOgiNnS90GsHdaWTmeap6l/view
EDIT: Dear @Re4son built OFFICIAL NETHUNTER for Suzuran . It includes; patched wlan0 firmware, HID support and many RTL wlan1 drivers
INSTRUCTIONS FOR BUILD YOURSELF OFFICIALLY (RECOMMENDED):
1- clone this https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project
Code:
git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project
2-
Code:
cd nethunter-installer
3-
Code:
./bootstrap.sh
4- press Y to download devices list.
5-
Code:
python build.py -d suzuran --nougat --rootfs full
(if you prefer lower storage usage, then change rootfs full to rootfs minimal.)
(press Y to download latest rootfs chroot.)
(This will create about 1,2GB of flashable ZIP file and after flash this, it will take 10 GB of internal storage)
6- connect your Z5 Compact to your PC and move zip to your internal storage.
(if you arent have PC, then flash my UNOFFICIAL zip and start KeX in Kali Nethunter menu (Desktop Enviroment) and run that commands in Nethunter)
(if your PC doesnt know your device, press this commands:
Code:
adb push CreatedNethunterFlashableZip /sdcard
7- after, go to TWRP and press backup your BOOT partition for any bootloop causes.
8- in TWRP, press install and choose created Nethunter Zip then press flash.
9- Reboot device and go to FDroid Nethunter version and upgrade Nethunter to latest apk.
10- go to Nethunter app and grant permissions.
11- press Kali chroot manager and then press Add metapackage. Select Kali-linux-nethunter
12- after install procces, go to KeX menu and press Setup local server and write custom password for Kex VNC login. after write, press n
13- In KeX menu, press start server and wait.
14- go to KeX app and write ip to your local ip ( in Nethunter app, go to Home menu and check wlan0 inet without /24 (example 192.168.1.101))
(if you arent connect wifi, press 127.0.0.1 in ip section.
15- write your preconfigured custom password
16- in front of ip section, press 5901 and hit connect.
INSTRUCTIONS FOR WLAN0 (INTERNAL WIFI) MONITOR MODE AND INJECTIONS TEST
INSTRUCTIONS FOR EASILY SET MONITOR MODE:
1. Download Prepatched Firmware:
nougat/suzuran/nexmon-fw/fw_bcmdhd.bin.nexmon · master · Kali Linux / NetHunter / build-scripts / kali-nethunter-devices · GitLab
Devices https://stats.nethunter.com/ https://nethunter.kali.org/
gitlab.com
(rename to fw_bcmdhd.bin)
2. Go to TWRP, select mount and system.
3. Go to main, file manager.
4. Navigate to /system/etc/firmware/wlan/bcmdhd/
5. Move fw_bcmdhd.bin file to your /sdcard/ (for backup)
6. Move into prepatched firmware
/system/etc/firmware/wlan/bcmdhd/
7. reboot system and done.
PATCH YOURSELF:
PART 1:
IN YOUR PC:
1. git clone https://github.com/seemoo-lab/nexmon.git
2. sudo apt-get install git gawk qpdf adb flex bison
3. sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
4. cd nexmon
5. source setup_env.sh
6. make (enter in terminal, like that up)
7. cd patches/bcm43455/7_45_59_16/nexmon
8. make
9. Generate a backup of your original firmware file: make backup-firmware
Install the patched firmware on your smartphone: make install-firmware (make sure your smartphone is connected to your machine beforehand)
https://github.com/seemoo-lab/nexmon...ster/README.md
PART 2 TEST WLAN0 MONITOR MODE:
IN YOUR PHONE:
1- open your wifi and go terminal app.
2-
Code:
. monstart-nh
3- and lets test monitor and injections:
Code:
airodump-ng wlan0
Code:
aireplay-ng -9 wlan0
4- if monitor mode shows any AP's, injection test says injections works, and some AP's reach %1 or upper, then monitor support works good, enjoy
thanks to @Re4son ..
Source Code: https://github.com/Re4son/android_kernel_sony_msm8994/tree/nethunter-14.1
NV modding
Are you able to modify Modem NV Registers with this kernel (assuming it's custom). Can you give it a try via vi or vim? I would prefer to do the modifications on device and simply update ramfs, if possible let me know.
nice
good job, do you know if encryption is working ?
No wlan 1
Thank you so much for making Nethunter for the Z5 compact.
Im on LOS 14.1 / Android 7.1.2 unoffical-suzuran.
I flash the zip from twrp, Restart and update Kali Chroot.
Everything works, Except kali can not find my wifi adapter.
I use the TP Link TL-WN722N-V1 have tried different otg cables,
But no Luck. "i also turn on usb otg"
I have tried many different wifi adapters, im not shore
what wifi drivers that this kernel suport.
im a newbie, So hope someone could help me make this work.
Thank you and regards from Michael.
@NetRoot bro. How to enable monitor mode?
Monstart-nh?
aggunawan said:
@NetRoot bro. How to enable monitor mode?
Monstart-nh?
Click to expand...
Click to collapse
yes bro
source monstart-nh
@NetRoot whats wrong bro with this?
And what is external wireless card support to the kernel? I use tp-link 722n v-1. Chipset atheros ath9k.
NetRoot said:
yes bro
source monstart-nh
Click to expand...
Click to collapse
What's wrong ?
@NetRoot and no module installed
@aggunawan Oops bro i forget.
You must patch wifi:https://github.com/seemoo-lab/nexmon
Our phone uses BCM43455 .
I added broadcom wifi and bluetooth modules but it isnt correctly installed.
NetRoot said:
@aggunawan Oops bro i forget.
You must patch wifi:https://github.com/seemoo-lab/nexmon
Our phone uses BCM43455 .
Click to expand...
Click to collapse
thanks bro @NetRoot. But I have tried compile nexmon https://github.com/seemoo-lab/nexmon many many time, but i always failure. Please help me to compile step by step? Please bro
aggunawan said:
@NetRoot bro. How to enable monitor mode?
Monstart-nh?
Click to expand...
Click to collapse
aggunawan said:
thanks bro @NetRoot. But I have tried compile nexmon https://github.com/seemoo-lab/nexmon many many time, but i always failure. Please help me to compile step by step? Please bro
Click to expand...
Click to collapse
1. git clone https://github.com/seemoo-lab/nexmon.git
2. sudo apt-get install git gawk qpdf adb flex bison
3. sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
4. cd nexmon
5. source setup_env.sh
6. make (enter in terminal, like that up)
7. cd patches/bcm43455/7_45_59_16/nexmon
8. make
9. Generate a backup of your original firmware file: make backup-firmware
Install the patched firmware on your smartphone: make install-firmware (make sure your smartphone is connected to your machine beforehand)
https://github.com/seemoo-lab/nexmon/blob/master/README.md
4.
NetRoot said:
1. git clone https://github.com/seemoo-lab/nexmon.git
2. sudo apt-get install git gawk qpdf adb flex bison
3. sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
4. cd nexmon
5. source setup_env.sh
6. make (enter in terminal, like that up)
7. cd patches/bcm43455/7_45_59_16/nexmon
8. make
9. Generate a backup of your original firmware file: make backup-firmware
Install the patched firmware on your smartphone: make install-firmware (make sure your smartphone is connected to your machine beforehand)
https://github.com/seemoo-lab/nexmon/blob/master/README.md
4.
Click to expand...
Click to collapse
Have you @NetRoot succesfully compiled it bro ?
@aggunawan yes bro.
NetRoot said:
@aggunawan yes bro.
Click to expand...
Click to collapse
@NetRoot. does it have to compile Android-NDK? How to compile it?
Failure to compile nexmon
Bro @NetRoot
@aggunawan bro use Kali amd (pc) not use compiling procces in nethunter.
NetRoot said:
@aggunawan bro use Kali amd (pc) not use compiling procces in nethunter.
Click to expand...
Click to collapse
Is there another way to compile it bro @NetRoot?
And please make kernel support external wireless adapter bro? Please
aggunawan said:
Is there another way to compile it bro @NetRoot?
And please make kernel support external wireless adapter bro? Please
Click to expand...
Click to collapse
No bro you must patch bcm43455 wifi.
Yeah that kernel already compiled for rtlwifi drivers.
You can see in: /system/etc/firmware/rtlwifi/
Finally
I can confirm it worked on my Oneplus 7 Pro both Volte and Vowifi calling it also can work on oneplus 6, and 6T since I don't have a device so I can't test it.
some people are unable to activated so this method require additional step for them.
Install QPST: https://mega.nz/file/zQt3ESDA#dd69iA2r9xZaYwWvYrCvVHl-OmjucIWI4ETFBTO5bM8 (This tool only work on Oneplus 6,6t, 7 series. Oneplus has blocked this tool on oneplus 5 series)
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
now right-click on overseas commerical ds and select Deactivated - Sub0
now right-click on Commerical-TMO and select SetSelectedConfig - Sub0
and now button Activate
Restart your phone than apply following step:
Oneplus Usb driver (Dont install it if you already installed this before)
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
After unzipping pixel3.zip you need to go to: Pixel3\mcfg_sw\generic\Pixel\NA\Freedom\VoLTE and copy mcfg_sw.mbn file to folder where you will have your EfsTools saved. It will ask you to overwrite one that is in that folder. Press yes.
Now follow these steps:
This method doesn't required root.
0. Make sure that you just enabled the VoWiFi and VoLTE in your carrier first !!!
1. Download and install the oneplus LogKit and Engineering mode apk:
3. Type *#800# --> oneplus Logkit --> Function Switch --> enable VoLTE and VoWifi switch
4. Open Settings --> WiFi & Intenet --> SIM & netwok --> enable VoLTE and VoWifi switch
5. Connect your phone to PC
6. Type *#801# in Phone app and enable Full-port switch (if your computer unable to recognize COM PORT try installing qualcomm driver: https://mega.nz/file/jV9ByarL#lbryKSC6uk9D-GTErtJ0SHyVOfWKA2TIl-psXmhj4YU)
7. Download and unzip the EfsTools with config files includes. (Make sure copy mcfg_sw.mbn file from pixel3.zip freedom folder replace the file if already exit.)
8. Open CMD as Administrator on the PC, navigate to the folder where you extract the files (eg. cd c:\EfsTools-0.10-modded-1.2-win32)
9. Now execute the following commands:
EfsTools.exe efsInfo
If your Freedom sim in Slot 1 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
If your Freedom sim in Slot 2 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
Thats it. Commands with "1" on at the end are for the second SIM card.
You must register here in order to wifi calling work: https://vowifi.authenticateme.ca/
Credit goes to @popos1 and @astracd. Original Post: https://forums.oneplus.com/threads/freedom-mobile-wifi-calling-working.1284987/
You need These file:
Pixel 3 mbn file:
https://forum.xda-developers.com/showpost.php?p=78563337&postcount=4 (Recommend for oneplus 6 series)
Pixel 4 mbn file:
https://forum.xda-developers.com/pixel-4/help/mbn-files-pixel-4-request-t4050247 (Recommend for Oneplus 7 series)
Thanks for @asasanc
Oneplus logkit:
https://mega.nz/file/rZlADYzD#Pg8vLZI4tZ16VXe-v-JfPLCiCab9fTTWwFcPBI04oho
Efstool:
https://mega.nz/file/fQcnQAZT#i0dRA6PvsuK4_PmLHPVXSwhOZroSsR6P1CuUDHwHW8g
Enigneering Mode apk:
https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/
Join Telegram group:
https://t.me/joinchat/QOPwqkqivRqnI4YIW2bojA
Edit:
Alot of people have confirm this method working on Oneplus 6,6t, 7,7 pro, 7t, and 8. For some people VoLTE works right away but for some it take few day to provision as per freedom it could take somewhere 72-120 HR to provision.
Edit 2:
Pixel 2 mbn for oneplus 5. This is recommended for Oneplus 5 only.
https://mega.nz/file/HUsHVYqS#n7pDP-mEMIY5MXffqViAVoqPgF_Au3hzzm6s5dgBZu0
Update: 3/25/2021
This new method requires Root on Android 11.Please note Engineering won't work on Android 11. you need to follow the following steps to open the ports.
you need Adb tool Platform-tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
1. Extract the Folder
2. Open the Platform Tool folder then hold the Shift key and right-click on empty space to open the Command Prompt in the same folder.
3. Then Type "ADB shell"
4. Then type "su" (This will ask root access on your phone)
5. Then type this command to open the port.
"setprop sys.usb.config diag,serial_cdev,rmnet,adb"
Then you have will access to EFStool and PDC tool to Flash mbn file using the above method
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
does this trick only work on stock roms, or would it work on a custom rom as well?
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
omvir said:
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
Click to expand...
Click to collapse
Yes it does connect to band 13.
CrazedBoredom said:
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
Click to expand...
Click to collapse
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
nabbasi said:
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
Click to expand...
Click to collapse
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
This is awesome news. Thanks for sharing brother!
CrazedBoredom said:
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
Click to expand...
Click to collapse
.
Did you run CMD as administrator if not try with that.
nabbasi said:
.
Did you run CMD as administrator if not try with that.
Click to expand...
Click to collapse
Yep, no dice.
astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
darkknight200 said:
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
Click to expand...
Click to collapse
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
astracd said:
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
Click to expand...
Click to collapse
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
darkknight200 said:
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
Click to expand...
Click to collapse
Full port is enough. You don't need serial. :good:
astracd said:
Full port is enough. You don't need serial. :good:
Click to expand...
Click to collapse
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
darkknight200 said:
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
Click to expand...
Click to collapse
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
astracd said:
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
Click to expand...
Click to collapse
Yes to both
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
astracd said:
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
Click to expand...
Click to collapse
stil no luck with renaming them and using different state from charging to file transfer mode