Related
Hello everyone,
I left my old galaxy spica few weeks ago for an Arc S, especially for the USB Host ability, and I was looking forward to get a phone for interfacing many devices I'm using at work.
Most of these devices use a FTDI chip enabling virtual serial COM port on USB, and now FTDI gives support to applications on Android OS :
[see FTDI website]
So I've been able to go through adding drivers to the kernel and start communication on a ZigBee network with Terminal Emulator.
Only a rooted phone is needed, no bootloader unlocked (you don't have to flash anything to add the drivers)
For anyone interested in using virtual COM port on their Arc / Arc S, these are the few steps to add support for FTDI chip (I did this with Ubuntu 11.10 on VMware Player, with almost no issue compared to building kernels for Galaxy Spica) :
1. Download Android NDK rev. 5c (newer give some issues when compiling kernel) to have a prebuilt toolchain, unzip in Home directory and add path to your environement var :
Code:
export PATH={HOME}/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/:$PATH
2. Clone kernel repository depending on your ROM (4.0.2.A.0.42 for me) :
http://forum.xda-developers.com/showthread.php?t=1312692
Many thx to DooMLoRD for this repo !
Code:
git clone -b 4.0.2.A.0.42 https://github.com/DooMLoRD/Xperia-2011-Official-Kernel-Sources.git
3. In kernel folder, add the default config file for your phone (Arc = anzu, Arc S = ayame)
Code:
cp arch/arm/configs/semc_ayame_defconfig .config
4. Edit config file to add USB serial drivers compilation as modules
Code:
ARCH=arm CROSS_COMPILE=arm-eabi- make menuconfig
Go to -> Device Drivers -> USB Support, highlight 'USB serial converter support' and press 'M' to include it as kernel module.
Go into the new submenu, highlight 'USB FTDI Single Port Serial Driver' and press 'M' to include it as kernel module too.
You can also choose any other USB serial converter depending on the manufacturer of your device
Leave menuconfig and save your config file
5. Build modules :
Code:
ARCH=arm CROSS_COMPILE=arm-eabi- make modules
6. Copy the drivers 'usbserial.ko' and 'ftdi_sio.ko' located in kernel/drive/usb/serial on your SD Card (don't forget usbserial.ko, this file is omitted in FTDI technical note)
7. On your phone, in Terminal Emulator, install the two drivers in this order :
Code:
$ su
# insmod usbserial.ko
# insmod ftdi_sio.ko
8. add this line to the file /ueventd.rc to give permissions :
Code:
/dev/ttyUSB* 0666 root root
9. plug your device, and even if it's not recognized by the phone, you should see 'ttyUSB0' in /dev !!!
Now you can play with Terminal Emulator using 'stty' to configure serial port and 'echo blablabla > ttyUSB0' to send some text
I've attached to this post a .zip file containing the two kernel modules for my config : Arc S (rooted, not unlocked) - 4.0.2.A.0.42
So you just have to follow this tutorial from step 6 (steps 1-5 can take some time)
Acknowledgement : DooMLoRD for the very useful repo, FTDI for the technical note and SE for the config files, avoiding hours of kernel config
Regards
PS : It's my first post so I've not been able to add this in dev section, especially in this thread : http://forum.xda-developers.com/showthread.php?t=1224676&highlight=usb and to give external links to DooMLoRD github repo and FTDI technical note, sorry for that (moderators can feel free to move this thread in the right section)
PPS : I'm not a very skilled developper, but I will try to do my best to give some support for this
PPPS : Well, sorry for my poor english
Bylos said:
Hello everyone,
I left my old galaxy spica few weeks ago for an Arc S, especially for the USB Host ability, and I was looking forward to get a phone for interfacing many devices I'm using at work.
Most of these devices use a FTDI chip enabling virtual serial COM port on USB, and now FTDI gives support to applications on Android OS :
[see FTDI website]
So I've been able to go through adding drivers to the kernel and start communication on a ZigBee network with Terminal Emulator.
Only a rooted phone is needed, no bootloader unlocked (you don't have to flash anything to add the drivers)
For anyone interested in using virtual COM port on their Arc / Arc S, these are the few steps to add support for FTDI chip (I did this with Ubuntu 11.10 on VMware Player, with almost no issue compared to building kernels for Galaxy Spica) :
1. Download Android NDK rev. 5c (newer give some issues when compiling kernel) to have a prebuilt toolchain, unzip in Home directory and add path to your environement var :
Code:
export PATH={HOME}/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/:$PATH
2. Clone kernel repository depending on your ROM (4.0.2.A.0.42 for me) :
http://forum.xda-developers.com/showthread.php?t=1312692
Many thx to DooMLoRD for this repo !
Code:
git clone -b 4.0.2.A.0.42 https://github.com/DooMLoRD/Xperia-2011-Official-Kernel-Sources.git
3. In kernel folder, add the default config file for your phone (Arc = anzu, Arc S = ayame)
Code:
cp arch/arm/configs/semc_ayame_defconfig .config
4. Edit config file to add USB serial drivers compilation as modules
Code:
ARCH=arm CROSS_COMPILE=arm-eabi- make menuconfig
Go to -> Device Drivers -> USB Support, highlight 'USB serial converter support' and press 'M' to include it as kernel module.
Go into the new submenu, highlight 'USB FTDI Single Port Serial Driver' and press 'M' to include it as kernel module too.
You can also choose any other USB serial converter depending on the manufacturer of your device
Leave menuconfig and save your config file
5. Build modules :
Code:
ARCH=arm CROSS_COMPILE=arm-eabi- make modules
6. Copy the drivers 'usbserial.ko' and 'ftdi_sio.ko' located in kernel/drive/usb/serial on your SD Card (don't forget usbserial.ko, this file is omitted in FTDI technical note)
7. On your phone, in Terminal Emulator, install the two drivers in this order :
Code:
$ su
# insmod usbserial.ko
# insmod ftdi_sio.ko
8. add this line to the file /ueventd.rc to give permissions :
Code:
/dev/ttyUSB* 0666 root root
9. plug your device, and even if it's not recognized by the phone, you should see 'ttyUSB0' in /dev !!!
Now you can play with Terminal Emulator using 'stty' to configure serial port and 'echo blablabla > ttyUSB0' to send some text
I've attached to this post a .zip file containing the two kernel modules for my config : Arc S (rooted, not unlocked) - 4.0.2.A.0.42
So you just have to follow this tutorial from step 6 (steps 1-5 can take some time)
Acknowledgement : DooMLoRD for the very useful repo, FTDI for the technical note and SE for the config files, avoiding hours of kernel config
Regards
PS : It's my first post so I've not been able to add this in dev section, especially in this thread : http://forum.xda-developers.com/showthread.php?t=1224676&highlight=usb and to give external links to DooMLoRD github repo and FTDI technical note, sorry for that (moderators can feel free to move this thread in the right section)
PPS : I'm not a very skilled developper, but I will try to do my best to give some support for this
PPPS : Well, sorry for my poor english
Click to expand...
Click to collapse
good read but will this work on windows? is there windows version? cheers
Sorry I didn't see the question before, thought this thread was buried
Do you mean by "working with windows" : will you be able to compile the kernel modules on windows ?
I think it's quite difficult to find the good cross compilation tools on windows, so I think the best way is to run a Ubuntu on virtual machine, as the cross compilation tools come with android sdk. Just download vmware player (free) and install a Ubuntu (open source) on it and you will be able to follow this guide
Regards
Hi there,
based on the work of bcmon.blogspot.com i compiled a working kernel + monitor mode module for the Nexus S running CyanogenMod 9.1
The Zipfile contains a kernel + monitor mode module + monitor mode firmware + aircrack-ng suite
Instructions:
Download & install CM9.1
Download & install zipfile via cwm recovery
To start monitor mode open a Terminal and type:
Code:
bcmon_start
The monitor interface is called eth0
Now you can run besside-ng airodump etc.
To stop monitor mode
Code:
bcmon_stop
Zip Download:
webschreinerei.com/nexuss/monitor-cm9-crespo.zip
rehost file?
[QQUOTE=solarwasser;50297254]Hi there,
based on the work of bcmon.blogspot.com i compiled a working kernel + monitor mode module for the Nexus S running CyanogenMod 9.1
The Zipfile contains a kernel + monitor mode module + monitor mode firmware + aircrack-ng suite
Instructions:
Download & install CM9.1
Download & install zipfile via cwm recovery
To start monitor mode open a Terminal and type:
Code:
bcmon_start
The monitor interface is called eth0
Now you can run besside-ng airodump etc.
To stop monitor mode
Code:
bcmon_stop
Zip Download:
webschreinerei.com/nexuss/monitor-cm9-crespo.zip[/QUOTE]
could you repost the file thanks. And did you have to change any of the source code for cm9 support? Any code you could also share? Thanks
Monkofthefunk said:
[QQUOTE=solarwasser;50297254]Hi there,
based on the work of bcmon.blogspot.com i compiled a working kernel + monitor mode module for the Nexus S running CyanogenMod 9.1
The Zipfile contains a kernel + monitor mode module + monitor mode firmware + aircrack-ng suite
Instructions:
Download & install CM9.1
Download & install zipfile via cwm recovery
To start monitor mode open a Terminal and type:
Code:
bcmon_start
The monitor interface is called eth0
Now you can run besside-ng airodump etc.
To stop monitor mode
Code:
bcmon_stop
Zip Download:
webschreinerei.com/nexuss/monitor-cm9-crespo.zip
Click to expand...
Click to collapse
could you repost the file thanks. And did you have to change any of the source code for cm9 support? Any code you could also share? Thanks[/QUOTE]
Right now i don't have a nexus s to to nor a real linux box to compile it again.
But here is the github ->
As far as i remember i compiled the kernel twice to with different source for the chipset one time clean source the other time with the source from the bemoan team
Anyway the cm 9.1 rom works with the bcmon app out of the box but i got much more handshakes using the module.
Sorry i just realized that Iam not allowed to post Links. For the github source search for sushiomsky/android_kernel_samsung_crespo at github
Bump...
Does anyone still have this zip anywhere? Since bcmon seems to fail on CM10.1+ and newer versions of Busybox even on BCM4329/4330.
Or anyone have a fresh compile from the repo? THanks
If you install a linux with SSH on Your Nexus S and give me a shell for a couple of hours i could compile it again. And take care that it doesn't get lost again...
PaulieP said:
Bump...
Does anyone still have this zip anywhere? Since bcmon seems to fail on CM10.1+ and newer versions of Busybox even on BCM4329/4330.
Or anyone have a fresh compile from the repo? THanks
Click to expand...
Click to collapse
Sounds great. Should have another Nexus S in my hands by Tuesday or so. will update.
Sorry I had forgotten about this thread.. I have the Nexus S, is there any particular distro of Linux I should install?
solarwasser said:
If you install a linux with SSH on Your Nexus S and give me a shell for a couple of hours i could compile it again. And take care that it doesn't get lost again...
Click to expand...
Click to collapse
PaulieP said:
Sorry I had forgotten about this thread.. I have the Nexus S, is there any particular distro of Linux I should install?
Click to expand...
Click to collapse
Hi,
perhaps I can guide you to compile the module if not we do it via ssh. First install cm 9.1 Gapps and debian or kali linux via Linux deploy
than do an "apt-get -y install build-essential" now clone the git repo with "git clone -b ics --single-branch https://github.com/sushiomsky/android_kernel_samsung_crespo/"
and now I am a little unsure but try to run a simple "make crespo_defconfig" followed by a "make" from within the source dir. copy the dhd4329.ko or similar (can't remember the exact name and folder) to your scared or somewhere else. now rename the /drivers/net/wireles/bcmon4329 to bcm4329 and do the make again now you have the monitor mode module. flash the boot image and load either the original (first) module or the monitor mode module with insmod.
Good luck
Cheers
Sol
●BRIEF INTRODUCTION :-
•Hello All, You May Be Well Known About Famous Gov-Tuner Project For Better Battery Management To Increase SOT More Effectively
•Here I Am Providing Tutorial About How To Setup Famous Gov-Tuner Mod On Samsung Galaxy Note 5 Running Custom TouchWiz S8+/Note5/Note FE Based Rooted Roms
•This Mod Will Work Effectively After Setting Up Properly To Increase SOT For Daily Usage To Avoid Frequent Charging Of Device Which Is Highly Annoying
●PRE-REQUIREMENTS :-
•Custom TouchWiz S8+/Note5/Note FE Based Rom
•Stock Pre-Rooted Rom
•Rooted Properly With Either SuperSU Root OR Magisk Root
•TWRP-Custom Recovery Installed
•Terminal Emulator Installed From PlayStore Granted Root Permissions
•Some Knowledge Of Applying Commands Through Terminal Emulator
*Note :-
You Just Have To Use Some Simple Commands Through Terminal Emulator
Like For Eg.
'su'
'govtuner'
'1/2/3 Profile Numbers'
•Gov-Tuner Project Zip You Can Download From Following Official Thread
*Note :-
Link To Official Gov-Tuner Project And Downloads
https://forum.xda-developers.com/an...mod-gov-tuner-project-29th-june-2016-t3407828
*Note :-
Download Either 4.1.1B Version Or 4.0.2 Version As 4.1 Version Have Some Reported Errors
•Above Posted Official Thread Is Reserved For F.A.Q. So Before Flashing Mod You Should Refer Those To Avoid Malfunctioning
●THANKS AND CREDITS GOES TO :-
•Gov-Tuner Project Team
•Developers And Contributors
1) @Senthil360
2) @Debuffer
3) @Paget96
4) @F4uzan
5) @veez21
6) @N1m0Y
●CAUTION :-
•Before Flashing Any Mods Its Always Recommended To Full Nandroid Backup Of Current Stable Rom
•Use This Mod At Your Own Risk, No One Here From XDA Including ME Will Be Responsible For Bricked Devices
•Mod Is Tested And Working Flawlessly On Samsung Galaxy Note 5 SM-N920G Running Infinity Note FE2.1 Port/With Khongloi Kernel V11
•Other Roms Needs To Be Tested, You Can Test It By Yourself And Report Here About Working Status
•If Your Device Loops After Setting Up Gov-Tuner Project Through Terminal Emulator Then Don't Worry Just Use 'x' Command At The Top Of Terminal Emulator To Exit And Everything Will Be Fine
•If Your Facing Issues Like Gov-Tuner Gets Disabled After Every Reboot, Kindly Refer The Following Post To Know More About Functionality Of Gov-Tuner
https://forum.xda-developers.com/an...-project-29th-june-2016-t3407828/post73188290
●INSTALLATION INSTRUCTIONS :-
•Download And Save Required Files Such As Gov-Tuner4.1.1 or 4.0.2.Zip From Official Gov-Tuner Thread
•Download And Install Terminal Emulator App From PlayStore
Note :-
*If Your Going To Try It On Stock Unrooted Rom Then First Install TWRP-Custom Recovery On Your Device And Root Your Device By One Of Following Method
*By Flashing CF-Autoroot Through Odin/Flashing Latest SuperSU V2.82 SR2 Through TWRP-Custom Recovery
OR
*By Flashing Magisk V13.3 Through TWRP-Custom Recovery
•Power Off Your Device
•Boot Your Device Into TWRP-Custom Recovery By Pressing Volume Up+ Home + Power Buttons Simultaneously Untill You See Samsung Galaxy Logo
•Select And Flash Gov-Tuner 4.1.1.Zip/Gov-Tuner 4.0.2.Zip Saved On Your Device Internal Storage
•Reboot Device From TWRP-Custom Recovery
•Wait For Atleast 3 Minutes To Integrate Gov-Tuner Profiles Completely With Current System/Custom Kernel
•Open Terminal Emulator App After 3 Minutes
•Type Following Commands Through Terminal Emulator
* First Type 'su'
Note :-
*Just Type Word su Only. Don't Type Comma Symbol Before After
*SuperSU Or Magisk Will Ask To Grant Root Access To Terminal Emulator
*Grant The Root Access
*Then Type 'govtuner'
Note :-
*Now Terminal Emulator Will Open Gov-Tuner Window
•You Will Now See Gov-Tuner Window With Profiles With Respective Numbers
Note:-
*Please Choose Profile Number To Activate It
For Eg.
1.Battery
2.Balanced
3.Performance
*Terminal Emulator Options For Advanced Utilization
g. Change Governer
i. Increase Performance (1)
u. Disable Govtuner
c. Changelog
p. Power Efficient
t. Tuned Parameters
w. Tweaked Parameters
v. Change Execution Interval (180 Secs)
e. Exit
•Select And Type Number In Terminal Emulator Of Profile Which Suits You The Best Like 1/2/3
Note :-
*Only Type Number Of Profile Like 1/2/3 In Terminal Emulator
*In Attached ScreenShots You Can See I Have Selected Number 1 Profile Which Is Battery Profile
*Terminal Emulator Will Run Commands To Set Gov-Tuner Profile
*It Will Take Some Time So Keep Patience
Sticky :-
*You Can See In Attached ScreenShots That Gov-Tuner Mod Is Active And Working
Profile:- Battery (Yellow Colour)
Gov-Tuner:- Active (Green Colour)
Init.d:- Working (Green Colour)
•Now Simply Type 'e' To Exit From Terminal Emulator OR In Quick Settings Panel Notifications Exit Terminal Emulator Window
Note :-
*In Attached ScreenShots I Have Shown How To Exit Terminal Emulator Both Through App And Quick Settings Panel
•Congratulations You Have Successfully Setup Gov-Tuner Mods On Your Device To Increase Battery Life Significantly
•You Can Do Following Actions Again By Following Same Terminal Emulator Method In Gov-Tuner
Note :-
*You Can Change Profiles
*See The Working Status Of Gov-Tuner
*Disable Gov-Tuner
*Change Governors
*Tweak Parameters
*Tune Parameters
●UNINSTALL GOV-TUNER MOD :-
•If You Want To Unistall Gov-Tuner Mod On Your Device Simply Open Terminal Emulator> Type su >Type govtuner > Type u To Disable Gov-Tuner
•Download Gov-Tuner Uninstaller.Zip From Official Thread Or You Can Find It Within Gov-Tuner.Zip In Path
Note :-
Path To Find Gov-Tuner Uninstaller Zip
Gov-Tuner_4.0.2.zip/common/system/etc/GovTuner/Unistall_Gov-Tuner.Zip
•Boot Your Device Into TWRP-Custom Recovery And Flash Gov-Tuner Uninstaller.Zip
•Done. Gov-Tuner Has Been Removed From Your Device
●ATTACHMENTS :-
•Below Are Some Attached ScreenShots Of Terminal Emulator Which Will Give Some Idea About Commands And Gov-Tuner Window/Profiles Etc.
This doesn't seem to work for Pixel Rom V6 - Fuel Kernel. (Samsung Touchwiz Based). Fails to set props.
Turbine1991 said:
This doesn't seem to work for Pixel Rom V6 - Fuel Kernel. (Samsung Touchwiz Based). Fails to set props.
Click to expand...
Click to collapse
1)Which version you tried? Try with lower version like 4.0.2 In Case if you tried with latest 4.1.1
2)Also If your using any third party Kernel Tuner Apps Then Unistall them first and Try the clean install of Govtuner again
Exynox86 said:
1)Which version you tried? Try with lower version like 4.0.2 In Case if you tried with latest 4.1.1
2)Also If your using any third party Kernel Tuner Apps Then Unistall them first and Try the clean install of Govtuner again
Click to expand...
Click to collapse
Cheers, I'll give them a go in order.
Do you know if disabling cpu cores can be done entirely with your method of tweaking? I used to run my Note 5 with 2 small cores & 1 big. On the MM Skyhigh kernel.
Do I have to re-apply the profile everytime the phone rebooted?
Sent from my SM-G955F using Tapatalk
bern4d1 said:
Do I have to re-apply the profile everytime the phone rebooted?
Click to expand...
Click to collapse
Sadly Yes But Read Below Post To Get More Information About Actual Working Phenomenon Of Gov-Tuner Mod
HERE
Turbine1991 said:
Cheers, I'll give them a go in order.
Do you know if disabling cpu cores can be done entirely with your method of tweaking? I used to run my Note 5 with 2 small cores & 1 big. On the MM Skyhigh kernel.
Click to expand...
Click to collapse
Gov-Tuner Apply some essential tweaks automatically by running profile scripts via terminal emulator And yes there is option within Terminal emulator to tune some parameters but i will suggest to use any kernel tuner app like Kernel Auditor to manually resize the core values for both big and small CPU's
Edit :- For F.A.Q's You Can Kindly Refer Main Govtuner Mod Thread Once For A While
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Latest Stable Magisk Version: v15.3
Latest Magisk Manager Version: v5.5.5Installing Magisk will give you ROOT, a super powerful Systemless Interface,
Magisk Modules support, and hide from tons of integrity tests like SafetyNet!Magisk only modifies the boot image and install files to /data and /cache
Your /system partition will only be modified if root is installed in /system, or using custom rom with addon.d support!
This Guide has been deprecated,Try Post#7
Before Proceeding , Beware that after this modification ,you will loose ALT+F1 TTY shell completely and you will only get back that after restoring original ramdisk.img.Mirroring System Image is still not working .So Limited Function
Requirements:
1.Linux OS or Windows OS (optional)
2.Phoenix_OS or any Android-x86 based Distro
3.Magisk Manager App
Installation Instructions
1.In Linux OS
Download android-tools-mkbootimg ,abootimg packages
For Debian Based Distros:
Code:
sudo apt install android-tools-mkbootimg abootimg
Copy ramdisk.img and kernel from Phoenix os iso and put in Home Directory
Now put these commands in terminal
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
Copy generated boot.img somewhere you can access in Phoenix OS
2. Now boot into Phoenix OS and Download Latest Magisk Manager from Official Github Repo
3. Now open Magisk Manager and Tap Install
Choose Patch boot.img
Select boot.img generated earlier
Now ,it will save patched img in /sdcard/MagiskManager/patched_boot.img
Save it somewhere again where you can access it in Linux OS
Go to ALT+F1 (ALT+Fn+F1) TTY and run these codes
Code:
cd /system/xbin && mv su su.bak
4. Go into Linux OS :
Open Nautilus and copy patched_boot.img in Home Directory
Now open terminal and enter these :
Code:
abootimg -x patched_boot.img
It will generate kernel and initrd.img file in Home directory
Rename initrd.img to ramdisk.img and replace with original ramdisk.img in Phoenix OS Installation Directory
5.Cool! Its Done ,Check Magisk Manager to confirm Root Access and Enjoy Magisk Latest features.
6.For Windows OS users ,check Sir [email protected] Android Kitchen thread for extracting and recompiling boot.img .
Further for sole Androidx86 users check CNexus thread .
Downloads:
I have done one for Phoenix OS 2.5.7 .see attachment ,backup original one and replace it.
This method will work for Any Android-x86 Distros like Bliss-x86 , LOS-x86 etc.
Credits:
topjohnwu
osm0sis
Ifom
Android-x86 Developers
PhoenixOS Team
Hello,
WONDERFUL GUIDE ! Thanks !
I've just manage to get PheonixOS onto Tesco connect 7" - which was hard, since no guide in the web for that cheap tablet.
few question for you:
1. have you done that on pheonixOS based on nougat or MM ?
( i've installed nougat - hope it is compatible )
2. have you mange to use magisk Xposed ( as a module ) onto this type of installation of magisk ?
( hope you can... since that's why I want to use magisk ).
did you manage
gps3dx said:
Hello,
WONDERFUL GUIDE ! Thanks !
I've just manage to get PheonixOS onto Tesco connect 7" - which was hard, since no guide in the web for that cheap tablet.
few question for you:
1. have you done that on pheonixOS based on nougat or MM ?
( i've installed nougat - hope it is compatible )
2. have you mange to use magisk Xposed ( as a module ) onto this type of installation of magisk ?
( hope you can... since that's why I want to use magisk ).
did you manage
Click to expand...
Click to collapse
1.There is no mm release of phoenixOS ,btw for Lollipop ,you can try .it should work
2.Nope lomount is still not working ,limited system tweaks @topjohnwu still silent
Camlin3 said:
Download android-tools-mkbootimg ,abootimg packages
Click to expand...
Click to collapse
Where can I find those two files? I'm using Windows 10, but working through cygwin64, I can do it following Linux steps, but couldn't find yet abootimg and I think that I have a wrong mkbootimg file if it needs to be named android-tools-mkbootimg and not just mkbootimg.
DaniDeVega said:
Where can I find those two files? I'm using Windows 10, but working through cygwin64, I can do it following Linux steps, but couldn't find yet abootimg and I think that I have a wrong mkbootimg file if it needs to be named android-tools-mkbootimg and not just mkbootimg.
Click to expand...
Click to collapse
Sorry to say but ,i dont use Windows btw you can try linux subsystem in Windows 10 or just try this guide ,it seems solved system mirroring issue . http://bbs.phoenixstudio.org/cn/index.php?m=3g&c=read&tid=14288&fid=12&page=1
2.5.9
Does this also work for 2.5.9?
Works perfect for Windows users. This would help more people with same issues.
Camlin3 said:
Sorry to say but ,i dont use Windows btw you can try linux subsystem in Windows 10 or just try this guide ,it seems solved system mirroring issue . http://bbs.phoenixstudio.org/cn/index.php?m=3g&c=read&tid=14288&fid=12&page=1
Click to expand...
Click to collapse
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
@DaniDeVega ,
I can only link works of others,but you posted the same ,so i don't think ,i have to do any thing else .
Jpalmer82 said:
Does this also work for 2.5.9?
Click to expand...
Click to collapse
Yess
Camlin3 said:
@DaniDeVega ,
I can only link works of others,but you posted the same ,so i don't think ,i have to do any thing else .
Click to expand...
Click to collapse
Yes, so I just did a little traduction of the chinese link you gave me, so I don't know yet if post this here (with or without mentioning the owner of the work) is forbidden or not on XDA.
If so, then, I would like to talk with a high rank member to explain and find any kind of way to let this be on xda too. :fingers-crossed:
This translation could help here so many people who would be with the same kind of issues to install Magisk on Phoenix OS that I found until finally you told me to review the link that gets me the solution, and I translate, just like a very helpful suggestion. :good:
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
This method works on 2.6.2 but How can I update Magisk?
And None of the modules that I have tried get enabled after rebooting
Update: Any module that has an app it requires you to install the app separately all other modules work fine
Hello, how to update pls :silly:
after the installation the internet was working, but after reboot, the internet stopped working, even configuring an static ip.
I'm using a desktop with wired cable and I don't have wireless network card
1.5.0 x86 Phoenix OS
Sorry for my bad english and sorry for posting here.
Hi ,the tools you mentioned I didn't find on CentOS, could you please give a repo address or direct RPM address? Thanks.
Does this method work in other android-x86? cm-14 r1, bliss etc?,
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
I couldn't have it work on x86 5.0.1
It boots back to BIOS
There's anyway for use phoenix os 3.0.5 or 3.0.6
I'am using windows,want use magisk
It works but after using it for a few minutes it reboots. Any fix?
Ytim08 said:
It works but after using it for a few minutes it reboots. Any fix?
Click to expand...
Click to collapse
I didn't get that ,if you can upload log ,I may help
Camlin3 said:
I didn't get that ,if you can upload log ,I may help
Click to expand...
Click to collapse
If I could get a logcat I could've maybe fixed it myself already, the problem is it reboots and logs are reset
Edit: out of curiosity, were you able to successfully install magisk 18 on latest Phoenix is version? It works for a couple minutes and then crashes and I have to hard reset
I believe someone will build a nethunter kernel for 8 and 8 pro.
Actually I found one on github and I tried to build a kernel to flash , I can't boot my phone. MY system is H2OS 10.5.12, oos and h2os can use same kernel. Oh, if anyone try to make a kernel, dont for android 11, the system has so many limits and bad experients.
Wanted to ask the same. I want to buy a new phone that works with Kali nethunter and I can't decide to buy the OnePlus 7 or the 8. Since there is an official rom for the OnePlus 7, and for the 8 there is only a kernel on GitHub that no one is able to make it work. I'm afraid to buy the OnePlus 7 and when I buy it then they make a nethunter rom for OnePlus 8 :laugh:
Figured i would chime in on this as i was able to get it up and running on my OP8P
i downgraded to 10.5.12 by flashing via fastboot from here...
Guide: Restore OnePlus 8/8 Pro Back to Stock OxygenOS Software
Guide to restore OnePlus 8/8 Pro back to the stock OxygenOS software after rooting, installing custom ROMs, etc by flashing the factory image (fastboot ROM).
www.thecustomdroid.com
Then go through the setup and root the device with magisk
once it was back to a "stock" rooted android 10 OS i installed the generic arm kalifs image via TWRP
booted back up and installed the nethunter store app apk, then nethunter apk.
NetHunter | Kali NetHunter App Store - Android App Repository for Penetraton Testing and Forensics
© 2010-2019 Kali Linux, F-Droid, and Contributors
store.nethunter.com
go to nethunter store first and install the nethunter terminal. once installed go back to the store and check for updates.
after the check open nethunter and it should do some more updates and you should be able to start the chroot
I have hid (rucky) and monitor mode working for internal wireless
BUT!
i did the OTA update to android 11 and rucky disappeared and sudo apt-get update no longer worked
but i found this post here
Temporary failure resolving 'http.kali.org' · Issue #913 · offensive-security/kali-nethunter
Device: OnePlus+ OS version Lollipop Output of cat /proc/version in adb shell or NetHunter Terminal: [email protected]:~# cat /proc/version Linux version 3.4.67-cyanogenmod-g399b32b ([email protected]) (gcc versio...
github.com
and that fixed the apt-get update.
rucky is still non operational unfortunately
markmn123 said:
Figured i would chime in on this as i was able to get it up and running on my OP8P
i downgraded to 10.5.12 by flashing via fastboot from here...
Guide: Restore OnePlus 8/8 Pro Back to Stock OxygenOS Software
Guide to restore OnePlus 8/8 Pro back to the stock OxygenOS software after rooting, installing custom ROMs, etc by flashing the factory image (fastboot ROM).
www.thecustomdroid.com
Then go through the setup and root the device with magisk
once it was back to a "stock" rooted android 10 OS i installed the generic arm kalifs image via TWRP
booted back up and installed the nethunter store app apk, then nethunter apk.
NetHunter | Kali NetHunter App Store - Android App Repository for Penetraton Testing and Forensics
© 2010-2019 Kali Linux, F-Droid, and Contributors
store.nethunter.com
go to nethunter store first and install the nethunter terminal. once installed go back to the store and check for updates.
after the check open nethunter and it should do some more updates and you should be able to start the chroot
I have hid (rucky) and monitor mode working for internal wireless
BUT!
i did the OTA update to android 11 and rucky disappeared and sudo apt-get update no longer worked
but i found this post here
Temporary failure resolving 'http.kali.org' · Issue #913 · offensive-security/kali-nethunter
Device: OnePlus+ OS version Lollipop Output of cat /proc/version in adb shell or NetHunter Terminal: [email protected]:~# cat /proc/version Linux version 3.4.67-cyanogenmod-g399b32b ([email protected]) (gcc versio...
github.com
and that fixed the apt-get update.
rucky is still non operational unfortunately
Click to expand...
Click to collapse
Thank you for documenting your experience. I attempted to install the generic Kali kalifs but the HID interface was not detected. I assume due to lack of kernel
Are there any developments in kernels for oneplus 8 pro? The following link provides a kernel builder but it is unsuccessful:
GitHub - kimocoder/nethunter_kernel_oneplus8: NetHunter kernel for OnePlus 8 / 8 Pro
NetHunter kernel for OnePlus 8 / 8 Pro. Contribute to kimocoder/nethunter_kernel_oneplus8 development by creating an account on GitHub.
github.com
Go to the nethunter app in your phone
then click USB arsenal in the hamburger menu
Click the USB function drop down and select HID
Click ADB dropdown and select disable
Finally click the "set usb function" button down below
If it works you will get a "USB function set successfully" notification
now open rucky and type away
markmn123 said:
Figured i would chime in on this as i was able to get it up and running on my OP8P
i downgraded to 10.5.12 by flashing via fastboot from here...
Guide: Restore OnePlus 8/8 Pro Back to Stock OxygenOS Software
Guide to restore OnePlus 8/8 Pro back to the stock OxygenOS software after rooting, installing custom ROMs, etc by flashing the factory image (fastboot ROM).
www.thecustomdroid.com
Then go through the setup and root the device with magisk
once it was back to a "stock" rooted android 10 OS i installed the generic arm kalifs image via TWRP
booted back up and installed the nethunter store app apk, then nethunter apk.
NetHunter | Kali NetHunter App Store - Android App Repository for Penetraton Testing and Forensics
© 2010-2019 Kali Linux, F-Droid, and Contributors
store.nethunter.com
go to nethunter store first and install the nethunter terminal. once installed go back to the store and check for updates.
after the check open nethunter and it should do some more updates and you should be able to start the chroot
I have hid (rucky) and monitor mode working for internal wireless
BUT!
i did the OTA update to android 11 and rucky disappeared and sudo apt-get update no longer worked
but i found this post here
Temporary failure resolving 'http.kali.org' · Issue #913 · offensive-security/kali-nethunter
Device: OnePlus+ OS version Lollipop Output of cat /proc/version in adb shell or NetHunter Terminal: [email protected]:~# cat /proc/version Linux version 3.4.67-cyanogenmod-g399b32b ([email protected]) (gcc versio...
github.com
and that fixed the apt-get update.
rucky is still non operational unfortunately
Click to expand...
Click to collapse
going back to the top, have you tried to run your internal WIFI card on monitor mode and perform packets injection at the same time, did you get any results back as your wifi card supports injection mode..? do u have a custom kernel works for Nethunter embedded by enabling external Wifi cards, monitor mode support, packet injection tested).?
let me pls know if u go successfully thru this before, and what is ur best android OS you always prefer to use with Nethunter..?
Invincible-Man said:
going back to the top, have you tried to run your internal WIFI card on monitor mode and perform packets injection at the same time, did you get any results back as your wifi card supports injection mode..? do u have a custom kernel works for Nethunter embedded by enabling external Wifi cards, monitor mode support, packet injection tested).?
let me pls know if u go successfully thru this before, and what is ur best android OS you always prefer to use with
Click to expand...
Click to collapse
So i have monitor mode working. I have set it up as a custom command using the following
echo "4" > /sys/module/wlan/parameters/con_mode
the above is all that needs to be typed. i also have exec mode to run in background
now to stop monitor mode you need another custom command
ip link set wlan0 down && echo "0" > /sys/module/wlan/parameters/con_mode
wifi operations will return to normal however packet injection does not work. then again i have only tested on wifite. I have not tried aireplay-ng
also im reading that installing nexmon from the nethunter store may add injection but i am weary of flashing wifi firmware since i dont know how to back up the existing in case it does not work
markmn123 said:
So i have monitor mode working. I have set it up as a custom command using the following
echo "4" > /sys/module/wlan/parameters/con_mode
the above is all that needs to be typed. i also have exec mode to run in background
now to stop monitor mode you need another custom command
ip link set wlan0 down && echo "0" > /sys/module/wlan/parameters/con_mode
wifi operations will return to normal however packet injection does not work. then again i have only tested on wifite. I have not tried aireplay-ng
also im reading that installing nexmon from the nethunter store may add injection but i am weary of flashing wifi firmware since i dont know how to back up the existing in case it does not work
Click to expand...
Click to collapse
Thing like that needs some patches over the kernel build, unfortunately none of them available now to match with kernel vers 4.19, so the biggest wanted part still missing "injection packets" even the monitor mode is working by default or not.
However I did one for my OP8pro and I only was able to enable some external usb wireless which is I have"rt2800, mt7601uu" at least I can do airmon-ng and activate monitor mode to do wifi attacks successfully, but still probably we need something to be specially build for this marvelous device!!
How did you get the drivers for the rt2800 on there? ive been looking for a way to get rtl8812 & rtl8814 on mine but dont know how
markmn123 said:
How did you get the drivers for the rt2800 on there? ive been looking for a way to get rtl8812 & rtl8814 on mine but dont know how
Click to expand...
Click to collapse
They're all there by default, no big deal only you need to enable them one by one from menuconfig settings, then you ready to go with compiling kernel after!
Here's my NetHunter kernel for OnePlus 8 Pro OOS v.10 based on blu_spark kernel. You can compile it by yourself or just flash prepared archive from Releases.
GitHub - flypatriot/blu-spark_kernel_oneplus_sm8250: blu_spark NetHunter kernel for OnePlus 8/Pro
blu_spark NetHunter kernel for OnePlus 8/Pro. Contribute to flypatriot/blu-spark_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
It is highly recommended to flash SystemRW_Script to have an ability to write to system_root.
After flashing the kernel you need to:
1. Copy 4.19.81-NetHunter folder from kernel archive (in modules/system_root/lib/modules) to android's /lib/modules.
2. Install NetHunter app and NetHunter Terminal from NetHunter Store.
3. Launch applications and give all needed permissions.
4. Install and start chroot.
5. Launch Android SU Terminal and enter commands:
mount -o remount,rw /
cp -sfr /data/data/com.offsec.nethunter/files/scripts/* /bin/
6. Copy folders from configs.zip to android's sdcard/nh_files.
7. Copy firmware files from firmware.zip to android's /etc/firmware/ and /vendor/firmware/
Hope you'll enjoy it.
flypatriot said:
Here's my NetHunter kernel for OnePlus 8 Pro OOS v.10 based on blu_spark kernel. You can compile it by yourself or just flash prepared archive from Releases.
https://github.com/flypatriot/blu-spark_kernel_oneplus_sm8250.
It is highly recommended to flash SystemRW_Script to have an ability to write to system_root.
After flashing the kernel you need to:
1. Copy 4.19.81-NetHunter folder from kernel archive (in modules/system_root/lib/modules) to android's /lib/modules.
2. Install NetHunter app and NetHunter Terminal from NetHunter Store.
3. Launch applications and give all needed permissions.
4. Install and start chroot.
5. Launch Android SU Terminal and enter commands:
mount -o remount,rw /
cp -sfr /data/data/com.offsec.nethunter/files/scripts/* /bin/
6. Copy folders from configs.zip to android's sdcard/nh_files.
7. Copy firmware files from firmware.zip to android's /etc/firmware/ and /vendor/firmware/
Hope you'll enjoy it.
Click to expand...
Click to collapse
it's better to include what features was added/enabled on this kernel..?
flypatriot said:
Here's my NetHunter kernel for OnePlus 8 Pro OOS v.10 based on blu_spark kernel. You can compile it by yourself or just flash prepared archive from Releases.
https://github.com/flypatriot/blu-spark_kernel_oneplus_sm8250.
It is highly recommended to flash SystemRW_Script to have an ability to write to system_root.
After flashing the kernel you need to:
1. Copy 4.19.81-NetHunter folder from kernel archive (in modules/system_root/lib/modules) to android's /lib/modules.
2. Install NetHunter app and NetHunter Terminal from NetHunter Store.
3. Launch applications and give all needed permissions.
4. Install and start chroot.
5. Launch Android SU Terminal and enter commands:
mount -o remount,rw /
cp -sfr /data/data/com.offsec.nethunter/files/scripts/* /bin/
6. Copy folders from configs.zip to android's sdcard/nh_files.
7. Copy firmware files from firmware.zip to android's /etc/firmware/ and /vendor/firmware/
Hope you'll enjoy it.
Click to expand...
Click to collapse
*EDIT*
Jumped ahead of myself before I found your repo. Excellent work! Cant wait to see what this thing is really capable of. Would love to mess around wit hbluetooth when it starts working
What features do you have working on the kernel?
The only thing i need to get working is Bluetooth (RFCOMM) and support for rtl8812au, rtl8188eus which work on this phone according to @kimocoder
I also have monitor mode on the internal wifi SoC but no injection. Is that possible?
flypatriot said:
Here's my NetHunter kernel for OnePlus 8 Pro OOS v.10 based on blu_spark kernel. You can compile it by yourself or just flash prepared archive from Releases.
https://github.com/flypatriot/blu-spark_kernel_oneplus_sm8250.
It is highly recommended to flash SystemRW_Script to have an ability to write to system_root.
After flashing the kernel you need to:
1. Copy 4.19.81-NetHunter folder from kernel archive (in modules/system_root/lib/modules) to android's /lib/modules.
2. Install NetHunter app and NetHunter Terminal from NetHunter Store.
3. Launch applications and give all needed permissions.
4. Install and start chroot.
5. Launch Android SU Terminal and enter commands:
mount -o remount,rw /
cp -sfr /data/data/com.offsec.nethunter/files/scripts/* /bin/
6. Copy folders from configs.zip to android's sdcard/nh_files.
7. Copy firmware files from firmware.zip to android's /etc/firmware/ and /vendor/firmware/
Hope you'll enjoy it.
Click to expand...
Click to collapse
Also source link isn't available
markmn123 said:
What features do you have working on the kernel?
The only thing i need to get working is Bluetooth (RFCOMM) and support for rtl8812au, rtl8188eus which work on this phone according to @kimocoder
I also have monitor mode on the internal wifi SoC but no injection. Is that possible?
Click to expand...
Click to collapse
Negative injection mode could not be presented on wlan0 since it's required some patches and I don't believe they're available for 4.19.81 kernel versions, however mon is already enabled by default and other features you add are enough to go ahead with nethunter.. Good job.. BTW the link for source you shared isn't available can you repost it again or you can drop the flashable.zip kernel itself let me test it on my phone first
Invincible-Man said:
it's better to include what features was added/enabled on this kernel..?
Click to expand...
Click to collapse
All features are listed in repo Readme.md
Invincible-Man said:
Also source link isn't available
Negative injection mode could not be presented on wlan0 since it's required some patches and I don't believe they're available for 4.19.81 kernel versions, however mon is already enabled by default and other features you add are enough to go ahead with nethunter.. Good job.. BTW the link for source you shared isn't available can you repost it again or you can drop the flashable.zip kernel itself let me test it on my phone first
Click to expand...
Click to collapse
Sorry for source links. It's really unavailable.
Plese try this one
GitHub - flypatriot/blu-spark_kernel_oneplus_sm8250: blu_spark NetHunter kernel for OnePlus 8/Pro
blu_spark NetHunter kernel for OnePlus 8/Pro. Contribute to flypatriot/blu-spark_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
And you're quite right about internal wifi injection mode.
markmn123 said:
*EDIT*
Jumped ahead of myself before I found your repo. Excellent work! Cant wait to see what this thing is really capable of. Would love to mess around wit hbluetooth when it starts working
What features do you have working on the kernel?
The only thing i need to get working is Bluetooth (RFCOMM) and support for rtl8812au, rtl8188eus which work on this phone according to @kimocoder
I also have monitor mode on the internal wifi SoC but no injection. Is that possible?
Click to expand...
Click to collapse
Most of features were presented by @kimocoder. But unfortunately kernel from his repo didn't work for me. So I spent time to compile a new one.
flypatriot said:
Sorry for source links. It's really unavailable.
Plese try this one
GitHub - flypatriot/blu-spark_kernel_oneplus_sm8250: blu_spark NetHunter kernel for OnePlus 8/Pro
blu_spark NetHunter kernel for OnePlus 8/Pro. Contribute to flypatriot/blu-spark_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
And you're quite right about internal wifi
Click to expand...
Click to collapse
flypatriot said:
btw I've done build my own nehunter kernel since last year almost based on elementalx kernel since this one has alot of good stuff in it ex. battery safer, gpu and cpu optimizations tho.. Can you also send me a flashable img or zip file to try this one as well..?
Click to expand...
Click to collapse
Check this one.
And can you share your kernel version just for testing.
flypatriot said:
Check this one.
And can you share your kernel version just for testing.
Click to expand...
Click to collapse
Currently im on OS10 kernel version 4.19.81
Invincible-Man said:
Currently im on OS10 kernel version 4.19.81
Click to expand...
Click to collapse
Mine is the same cause we don't have a normal working twrp for OOS 11.