Android-x86 6.0-rc2 (marshmallow-x86) 2016/08/15
The Android-x86 project is glad to announce 6.0-rc2 release to public. This is the second release candidate for Android-x86 6.0 (marshmallow-x86) stable release. The prebuilt images are available in the following site:
http://osdn.org/rel/android-x86/android-x86/Release 6.0
Key Features
The 6.0-rc2 release is based on the latest Android Marshmallow-MR2 release (6.0.1_r61) with all AOSP security patches applied. We fixed a lot of issues found in the 6.0-rc1 and added more features:
Launch the Android-x86 Analytics Program to collect anonymous data from users.
Update kernel to 4.4.17 with more upstream patches.
Update Mesa to 12.0.1. The unstable issues of i965/i915/Nvidia GPUs found in 6.0-rc1 are fixed.
Fix software rendering crashing issues on VM like QEMU and VirtualBox.
Fix modules auto loading method to improve hardware compatibility.
Improve audio hal sound card selection.
Auto-mount USB/sdcard with ext4/ntfs/exfat/vfat filesystems.
Add back SDCARD=xxx function to vold 3.0.
RTC time is set to local.
Released Files
We created universal images for most x86 platforms. This release contains two files. One is the 32-bit x86 ISO and the other is the 64-bit x86_64 ISO. Both can be boot from legacy BIOS and newer UEFI firmware. You can choose one of them depends on your devices. In doubt, try the 32-bit ISO for legacy BIOS devices and 64-bit ISO for UEFI devices.
32-bit: android-x86-6.0-rc2.iso
sha1sum: d05874e2591d18f45f4463f53b0bcb00b7731e15
64-bit: android-x86_64-6.0-rc2.iso
sha1sum: 8de2faf6c1cae7eee64dbc4d375bcfe359cbb777
For Linux users, just dump the iso into a usb drive to create a bootable usb stick like
$ dd if=android-x86-6.0-rc2.iso of=/dev/sdX
where /dev/sdX is the device name of your usb drive.
Windows's users can use the tool UNetbootin to create a bootable usb stick.
Please read this page for how to install it to the device.
Known issues
The display of built-in browser messes up sometimes on Skylake GPU.
Suspend and resume doesn't work on some devices.
Source code
The source code is available in the main git server,
$ repo init -u git://gitscm.sf.net/gitroot/android-x86/manifest -b marshmallow-x86
$ repo sync
It booted on my acer ES511, used rufus to make a bootable usb.
Its stock android, no desktop functions like remix or pheonix but it runs mucher faster.
Looks like it's rooted already.
Sent from my Aspire ES1-511 using XDA-Developers mobile app
flashallthetime said:
It booted on my acer ES511, used rufus to make a bootable usb.
Its stock android, no desktop functions like remix or pheonix but it runs mucher faster.
Looks like it's rooted already.
Sent from my Aspire ES1-511 using XDA-Developers mobile app
Click to expand...
Click to collapse
yeah its rooted, maybe faster too, but compared remixOS or phoenix its rediculous!
but works!
<<<New World Order (NWO)>>>
[email protected] said:
yeah its rooted, maybe faster too, but compared remixOS or phoenix its rediculous!
but works!
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
Agreed , already firing remix back up.
Sent from my du_lux using XDA-Developers mobile app
For me, It's much faster than either Remix or Phoenix (Core M - Broadwell) plus it's the first one with proper acceleration, including x264 videos.
With sane battery life on top, this with Phoenix/Remix would be amazing.
Tested it on my core m5 Lenovo miix 700, and finally a release with working audio!! (Realtek high definition audio).
It would be great to have this working on RemixOS!!
I keep on getting
"ioremap flush page- no chipset flushing"
any fixes for this? does anyone know how to get around
Remix OS will base on this? Please!
Almost everything in this version seems to work well on the Surface Pro 3. There is still a random touch point that pops up and stays activated on the screen after a while though. I sure wish they would fix that issue. Been reporting it for almost a year now...
Latest RemixOS (3.0.201) is already based on it!
LuckyNuke1310 said:
Latest RemixOS (3.0.201) is already based on it!
Click to expand...
Click to collapse
....yes everything BUT the kernel, so most of the hardware problem from 3.0.104 are carried along to this new version!
<<<New World Order (NWO)>>>
it stays black nothing happen here is what i get after install or live
{
"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"
}
HP elitebook 2740p
This seems to work very well on the HP Elitebook 2740p
the one thing I hoped for sadly does not work is the touch screen.
the touchscreen worked well in the latest Ubuntu desktop
is there anyone that could help me get the touch screen working?
even a push in the right direction would be helpful I know its a shot in the dark lol.
I was able to get the dmesg | lsmod | lsusb test files from a live Linux boot disk if that would help in any way.
here is the context of the lsusb
Bus 002 Device 003: ID 0b27:6998 Ritek Corp.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04f2:b183 Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader
Bus 001 Device 003: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Thanks in advance!
---------- Post added at 10:34 PM ---------- Previous post was at 10:31 PM ----------
rn0rdin said:
it stays black nothing happen here is what i get after install or live
View attachment 3959558
View attachment 3959559
View attachment 3959562
View attachment 3959563
Click to expand...
Click to collapse
I was able to find out from days of research that it is not formatting the partition properly so to fix that I just installed the latest Ubuntu and installed Ax86 right over the Linux system partition. select yes to the grub and uefi do not format!
Related
Code:
****Disclaimer: I'm not responsible if you destroy your device. Use at your own risk.****
Introduction:
Welcome to my builds of AOSP for the Raspberry Pi 3. You can get a very similar feel to that of a Nexus player when you combine this build with TV GAPPS. I welcome other developers to assist me in this project!
Bug Reporting:
Please only report bugs in the following format:
Device Firmware base:
Kernel &Version:
ROM date of release/nightly:
Governor:
Scheduler:
Any changes made within a kernel/ROM manager:
Any bootup scripts:
Brief description of bug:
Intended behavior:
Actual behavior:
Steps to reproduce bug:
Do this
Do that
See the bug
****Attach a logcat or you will be ignored****
Features:
AOSP for Raspberry Pi 3
More features to be added
Click to expand...
Click to collapse
Instructions:
Install Linux on your computer or a VM
Make sure you have adb installed
Download ROM and GAPPS
Insert your SD card into your computer or via adapter
Prepare SD card with the following partitions:
Code:
p1 512MB for BOOT : Do fdisk : W95 FAT32(LBA) & Bootable, mkfs.vfat
p2 1024MB for /system : Do fdisk, new primary partition, mkfs.ext4
p3 512MB for /cache : Do fdisk, mkfs.ext4
p4 remainings for /data : Do fdisk, mkfs.ex4
Set volume label for each partition - system, cache, userdata : use -L option of mkfs.ext4, e2label command, or -n option of mkfs.vfat
Un-tar/gz the downloaded ROM
Get your partition names with fdisk:
Code:
fdisk -l
Write the partitions: (In this example I will use mmcblk0 as my storage name)
Code:
$ sudo dd if=boot.img of=/dev/mmcblk0p1 bs=1M
Code:
$ sudo dd if=system.img of=/dev/mmcblk0p2 bs=1M
Un-tar your downloaded GAPPS
Boot up your Pi and connect it to your network (highly recommended to hardwire it or it will be a b*** to flash GAPPS)
Open up a terminal and cd into the directory you extracted the GAPPS in
Edit the gapps.sh script where it says IP to match the IP of your Pi
Flash GAPPS:
Code:
$ chmod +x gapps.sh && ./gapps.sh
Your Pi will reboot a few times and you'll be all set
Download:
Download Repository
Changelog:
06/28/2017
Merge tag 'android-7.1.2_r17' into all repos
Add prebuilt fugu (Nexus Player) launcher and other vendor apps
Use only SW video decoder
04/20/2017
Initial release
Click to expand...
Click to collapse
Bugs:
DRM content currently does not work as we do not have any certifications for this device. I could use help hacking this.
Screen flickers sometimes
Youtube app plays sound but no video (you can use a 3rd party app to get videos to play)
Let me know...
Sources:
Kernel
Device Tree
GAPPS script derived from: https://github.com/bjsiu/rpi3-gapps
ROM originally derived from: https://github.com/android-rpi
Android Security Patch Version: June 5, 2017
XDA:DevDB Information
AOSP/Android TV for Raspberry Pi 3 (Testing), ROM for the Raspberry Pi
Contributors
tabp0le
Source Code: https://github.com/tab-pi/platform_manifest
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2017-04-21
Last Updated 2018-10-15
Reserved
{
"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"
}
Reserved
Anyone want to explain this to an idiot like me? Struggling hard over here just trying to format the SD
matistight said:
Anyone want to explain this to an idiot like me? Struggling hard over here just trying to format the SD
Click to expand...
Click to collapse
You can use gparted to make it easier. Delete all partitions from the SD. Then make a 512MB partition with label boot and format as fat32. Change flags to boot and lba. Then make a 1024MB ext4 partition with label system. Then another be 512MB ext4 label cache. Then another with remaining space labeled data.
Does Chromecast'ing / Screen mirroring work?
would this also work on Raspberry Pi 2?
How do you control through the interface? Does hdmi-cec work(like in kodi) so you can use your remote control?
Sent from my SM-G935F using Tapatalk
tabp0le said:
Code:
****Disclaimer: I'm not responsible if you destroy your device. Use at your own risk.****
Bugs:
DRM content currently does not work as we do not have any certifications for this device. I could use help hacking this.
Click to expand...
Click to collapse
Once upon a time, I tried doing the same thing for the RK3288 android-on-a-stick. I think I was able to get *some* of the DRM stuff to work by stealing a bunch of the binary blobs from the Razer Forge ATV device and hacking the build.prop to look like a razer - but never fully got Netflix to work.
My suggestion for an approach to hacking DRM support in for this device would be to do the same thing for the 7.1.2 build for Nexus Player - diff your ROM against the extracted source for Nexus, find any missing binary blobs in /bin, /xbin, and /vendor, (probably /vendor more than anything), and then start modding the build.prop to make it look like a nexus player till it works or you break something.
Download-Link is broken.
Would be interested if it works with pi2 as well
ad_on_is said:
Download-Link is broken.
Click to expand...
Click to collapse
It returns me a 502 Bad Gateway too.
Download link is broken.
:crying:
Please correct Download link - i'm waiting hard for Android TV on my RPi3
This sounds like a fantastic project! I'm excited to see how well it works out
Link working now
Very interested to know if the casting ability works. Is the ability for a device to appear as a "chromecast" device hardware or software limited?
This could be interesting. I wish Google would actually populate their GIT that they started for it...
arusiasotto said:
This could be interesting. I wish Google would actually populate their GIT that they started for it...
Click to expand...
Click to collapse
Found this: android-rpi
Sounds like the beginning of a nice project. Interested to see how this pans out!
{
"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"
}
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, [URL="https://github.com/offensive-security/kali-nethunter/wiki/NetHunter-Mana-Wireless"]Evil AP MANA attacks[/URL], and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
FIRST THINGS FIRST, SERIOUSLY:
Your warranty was void as soon as you unlocked your bootloader.
Although Kali Nethunter should be safe to use, I am not responsible for whatever happens to your device, router, or whatever networking infrastructure because of YOU misusing the available facilities of Kali.
Remember that while Kali can be absolutely safe, if you handle root access improperly, no one will help you.
Make sure you read all of the info here and have some basic knowledge about networking, kernels and Linux/Unix.
Even if you're able to find a vulnerability on a different host (often called victim) , don't misuse the advantage you have.
Report the issue to the device's owner and the OEM. Do not complain if the attacks aren't working. Security has been ramping up ever since the wikileaks incident and the Edward Snowden thing.
FEATURES:
Kali NetHunter Application
Home Screen - General information panel, network interfaces and HID device status.
Kali Chroot Manager - For managing chroot metapackage installations.
Check App Update - For checking Kali NetHunter Android App updates.
Kali Services - Start / stop various chrooted services. Enable or disable them at boot time.
Custom Commands - Add your own custom commands and functions to the launcher.
MAC Changer - Change your Wi-Fi MAC address (only on certain devices)
VNC Manager - Set up an instant VNC session with your Kali chroot.
HID Attacks - Various HID attacks, Teensy style.
DuckHunter HID - Rubber Ducky style HID attacks
BadUSB MITM Attack - Nuff said.
MANA Wireless Toolkit - Setup a malicious Access Point at the click of a button.
MITM Framework - Inject binary backdoors into downloaded executables on the fly.
NMap Scan - Quick Nmap scanner interface.
Metasploit Payload Generator - Generating Metasploit payloads on the fly.
Searchsploit - Easy searching for exploits in the Exploit-DB.
3rd Party Android Applications (WIP)
NetHunter Terminal Application
DriveDroid
USB Keyboard
Shodan
Router Keygen
cSploit
Remember that there might be many other exploits and attack features available online, the ones mentioned above are officially documented by Kali. Secondly, not much support will be possible regarding the attacking since not everyone will have the same opportunities.
DOWNLOADS
1. For N Custom ROMs :
Android File Host Link
2. For stock N:
INSTALLATION
IMPORTANT NOTE: Kali NetHunter is NOT an Android ROM, but it is an overlay ( you have to flash it above android).
The builds currently provided are to be used on Nougat based custom ROMs ONLY. (which use the LineageOS kernel)
Installing it on a ROM which uses the LineageOS 14.1 kernel. (examples include all of our N custom ROMs like Lineage, AEX, AICP, AOKP, DU ) :
1. Make sure you are running the latest available build of the ROM you have installed.
2. Reboot to TWRP.
3. Make sure you backup Boot, System and Data partitions, just incase you want to remove Kali, you can restore it.
3. Wipe Cache and ART Cache (Formerly known as Dalvik Cache). Do NOT wipe your data partition.
4. Install the zip file.
5. Reboot to System.
POST INSTALLATION:
1. Open the NetHunter App and start the Kali Chroot Manager.
2. You might want to download the real packages which might be around 400-500 MB in size.
3. Set up Hacker Keyboard.
4. Configure Kali Services, such as SSH.
5. Set up custom commands.
6. Initialize the Exploit Database.
SCREENSHOTS:
https://vimeo.com/132329259
View attachment 4217645 View attachment 4217646 View attachment 4217647 View attachment 4217648
https://youtu.be/yV6AzqgdBo4
IMPORTANT LINKS:
1. TWRP : Santhosh M's thread
2. KaliLinux NetHunter Github Wiki
3. KaliLinux NetHunter Website
4. Source for potter: https://github.com/tywinlannister7/nethunter-devices
Contributors
tywinlannister7 @fAIyaZ
XDA:DevDB Information
KaliNethunter for potter, ROM for the Moto G5 Plus
Contributors
tywinlannister7
Source Code: https://github.com/offensive-security/kali-nethunter
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest stock Nougat firmware
Version Information
Status: Stable
Stable Release Date: 2017-07-20
Created 2017-07-20
Last Updated 2019-11-22
Reserved
Reserved
Thank you very much.
Thank You
I'm waiting for NetHunter since I've bought this device thank you very much.
@tywinlannister7 followed the steps. But after flashing it, it bootloops..... like I thought it must be normal for few times but it continues for more. Am I missing anything?
@punto said:
@tywinlannister7 followed the steps. But after flashing it, it bootloops..... like I thought it must be normal for few times but it continues for more. Am I missing anything?
Click to expand...
Click to collapse
Hmm, seems like a mistake form my side. Anyways, check the new build in the downloads folder. It should work fine as tested :good:
yayyy atleast it booted perfectly. but kali terminal fcs. when i try to install chroot or even if i open kali terminal app. i will attach a log later...... thnkss
Fixed NetHunter Terminal Force Close
@punto;73120051]yayyy atleast it booted perfectly. but kali terminal fcs. when i try to install chroot or even if i open kali terminal app. i will attach a log later...... thnkss
Click to expand...
Click to collapse
@punto I faced same problem but i solved it.
Just Open NetHunter app and Go to Kali Services and Start SSH Service.
That's it...Now open Terminal :good:
@utsavisnh88 i did still it fcs..... as i said i will post a log but currently dont have time..... so i am nit reporting without a proper log.
regarding log
since i am doing this on the fly i may have wrongly captured
https://hastebin.com/oqedefitun.pl
I m using a external wifi adapter (802.11n) to have fun with kali.. but the phone is not detecting the external wifi adapter.. usb pendrives are detected just fine.. no problems there.. i have tried wifite and airmon-ng in terminal.. but none of them detects it.. can someone help?
Wifi and Camera Issues
Downloaded but now Wifi and camera will not work. Any suggestions?
[QUOTE @punto;73129957]@utsavisnh88 i did still it fcs..... as i said i will post a log but currently dont have time..... so i am nit reporting without a proper log.[/QUOTE]
Sorry @punto i can't help you with that at the moment because I'm now Switched to Stock Rom. I'm can't remember how i have got it working.
Did anyone get any wireless adapter working ?? .. i have alpha and otg cable but does not detect it .. pen drives and wireless mouse works good though
Can we install it on oreo based rom
can't do DuckHunter HID attack
And it also says no HID interface detected...
Please help.
@punto said:
@utsavisnh88 i did still it fcs..... as i said i will post a log but currently dont have time..... so i am nit reporting without a proper log.
Click to expand...
Click to collapse
Just open inbuilt terminal of lineage os and type
"su" grant the su permission and type"bootkali" now you must get something like [email protected]#~ and now you can close this and open your nethunter terminal it should work perfectly
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
@punto said:
@utsavisnh88 i did still it fcs..... as i said i will post a log but currently dont have time..... so i am nit reporting without a proper log.
Click to expand...
Click to collapse
open builtin terminal of lineage os and type "su" grant the permission and type "bootkali" now it will say something like [email protected]:~# now you can close the terminal and open nethunter terminal or you can use this also
Bro could you provide the full source code... As there is only precompiled zimage.
HID attacks and wifi attacks working or not?
{
"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"
}
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, [URL="https://github.com/offensive-security/kali-nethunter/wiki/NetHunter-Mana-Wireless"]Evil AP MANA attacks[/URL], and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
FIRST THINGS FIRST, SERIOUSLY:
Your warranty was void as soon as you unlocked your bootloader.
Although Kali Nethunter should be safe to use, I am not responsible for whatever happens to your device, router, or whatever networking infrastructure because of YOU misusing the available facilities of Kali.
Remember that while Kali can be absolutely safe, if you handle root access improperly, no one will help you.
Make sure you read all of the info here and have some basic knowledge about networking, kernels and Linux/Unix.
Even if you're able to find a vulnerability on a different host (often called victim) , don't misuse the advantage you have.
Report the issue to the device's owner and the OEM. Do not complain if the attacks aren't working. Security has been ramping up ever since the wikileaks incident and the Edward Snowden thing.
FEATURES:
Kali NetHunter Application
Home Screen - General information panel, network interfaces and HID device status.
Kali Chroot Manager - For managing chroot metapackage installations.
Check App Update - For checking Kali NetHunter Android App updates.
Kali Services - Start / stop various chrooted services. Enable or disable them at boot time.
Custom Commands - Add your own custom commands and functions to the launcher.
MAC Changer - Change your Wi-Fi MAC address (only on certain devices)
VNC Manager - Set up an instant VNC session with your Kali chroot.
HID Attacks - Various HID attacks, Teensy style.
DuckHunter HID - Rubber Ducky style HID attacks
BadUSB MITM Attack - Nuff said.
MANA Wireless Toolkit - Setup a malicious Access Point at the click of a button.
MITM Framework - Inject binary backdoors into downloaded executables on the fly.
NMap Scan - Quick Nmap scanner interface.
Metasploit Payload Generator - Generating Metasploit payloads on the fly.
Searchsploit - Easy searching for exploits in the Exploit-DB.
3rd Party Android Applications (WIP)
NetHunter Terminal Application
DriveDroid
USB Keyboard
Shodan
Router Keygen
cSploit
Remember that there might be many other exploits and attack features available online, the ones mentioned above are officially documented by Kali. Secondly, not much support will be possible regarding the attacking since not everyone will have the same opportunities.
DOWNLOADS
1. For N Custom ROMs :
Android File Host
2. For stock N:
3. For MM Custom ROMs:
4. For Stock MM:
INSTALLATION
IMPORTANT NOTE: Kali NetHunter is NOT an Android ROM, but it is an overlay ( you have to flash it above android).
The builds currently provided are to be used on Nougat based custom ROMs ONLY. (which use the LineageOS kernel)
Installing it on a ROM which uses the LineageOS 14.1 kernel. (examples include all of our N custom ROMs like Lineage, AEX, AICP, AOKP, DU ) :
1. Make sure you are running the latest available build of the ROM you have installed.
2. Reboot to TWRP.
3. Make sure you backup Boot, System and Data partitions, just incase you want to remove Kali, you can restore it.
3. Wipe Cache and ART Cache (Formerly known as Dalvik Cache). Do NOT wipe your data partition.
4. Install the zip file.
5. Reboot to System.
POST INSTALLATION:
1. Open the NetHunter App and start the Kali Chroot Manager.
2. You might want to download the real packages which might be around 400-500 MB in size.
3. Set up Hacker Keyboard.
4. Configure Kali Services, such as SSH.
5. Set up custom commands.
6. Initialize the Exploit Database.
SCREENSHOTS:
https://vimeo.com/132329259
https://youtu.be/yV6AzqgdBo4
IMPORTANT LINKS:
1. TWRP
2. KaliLinux NetHunter Github Wiki
3. KaliLinux NetHunter Website
4. Source for harpia: https://github.com/tywinlannister7/nethunter-devices
XDA:DevDB Information
KaliNethunter for harpia, ROM for the Moto G4 Play
Contributors
tywinlannister7
Source Code: https://github.com/offensive-security/kali-nethunter
XDA:DevDB Information
KaliNethunter for harpia, ROM for the Moto G4 Play
Contributors
tywinlannister7
Source Code: https://github.com/offensive-security/kali-nethunter
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Stock Marshmallow Firmware
Version Information
Status: Beta
Stable Release Date: 2017-07-20
Created 2017-07-20
Last Updated 2017-07-20
Reserved
Reserved
I'm just wondering as I haven't seen this anywhere, xiaomi/huami didn't released kernel source for those watches, did they? Have there been any efforts to press them for it? As it has been confirmed those devices use android I'm assuming they must be useing linux kernel, is that right? If that's the case it's another GPL violation from xiaomi/huami.
I asked them if they intended to release the kernel source for the Pace. They said no.
There's currently attempts to use the kernel source for the board the watches are based on to see how far that gets but nothing of note yet
I will try to ask them the same question, I'm assuming the answer will be the same as you have received or no answer at all, but if that's the case I will contact gpl-violations for help in pressing them down about source code release. Are you able to provide a proof that those devices are running on Linux kernel? Something that is easily verifiable by looking at available binaries? I'm not really sure how to prove there is Linux inside but I guess there must be something within the binaries.
They run Android, that's proof enough
I already asked them twice, but no answer,
Asked on Facebook group, but no answer...
I think they'll never release it, but I hope I'm wrong
Surprisingly I've received the answer very quickly.
"Thank you for contacting Amazfit.
Oh somehow I was unable to include full message in the previous post. Editing it also didn't helped, anyway response from amazfit was exactly what I have expected. I'll try to press them harder.
shamus said:
Oh somehow I was unable to include full message in the previous post. Editing it also didn't helped, anyway response from amazfit was exactly what I have expected. I'll try to press them harder.
Click to expand...
Click to collapse
whats the reason for pressing them to publish the kernel source? For what do you need the source?
I understand the OSS aspect but is that all?
thaberkern said:
whats the reason for pressing them to publish the kernel source? For what do you need the source?
I understand the OSS aspect but is that all?
Click to expand...
Click to collapse
So we can build for it. Personally I'd like an Oreo build so WearOS might actually stand a chance of working
Quinny899 said:
So we can build for it. Personally I'd like an Oreo build so WearOS might actually stand a chance of working
Click to expand...
Click to collapse
just found this site
http://iwop.ingenic.com/static/iwds-releases/
from first look it seems like whe watch os is based on this verison and even look at this image, its like amazfit
{
"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"
}
I think Huami has taken over the failed OXY smartwatch: https://www.indiegogo.com/projects/oxy-smartwatch-your-daily-companion/
This seems to be the base of WatchOS. But it will be difficult to release an Oreo version of it. You will need all the drivers for the Linux kernel be Oreo compatible and then Oreo will still not run on the watch. The current Android is stripped down heavily. I think we have to wait until Ingenic releases a new version which probably only will come with a new CPU. What me worries is that the last release is from 2016. The new watches with Android 7 now have a Mediatek processor.
[EDIT]
I have just read that the processor is a MIPS processor which is not longer supported in Android. All new is using ARM. However it should not be too difficult for Huami to port their stuff over. But it will require a new watch with an ARM v7 processor. In Bip Huami is using an ARM processor as well.
SteffenBerlin said:
This seems to be the base of WatchOS. But it will be difficult to release an Oreo version of it. You will need all the drivers for the Linux kernel be Oreo compatible and then Oreo will still not run on the watch. The current Android is stripped down heavily. I think we have to wait until Ingenic releases a new version which probably only will come with a new CPU. What me worries is that the last release is from 2016. The new watches with Android 7 now have a Mediatek processor.
[EDIT]
I have just read that the processor is a MIPS processor which is not longer supported in Android. All new is using ARM. However it should not be too difficult for Huami to port their stuff over. But it will require a new watch with an ARM v7 processor. In Bip Huami is using an ARM processor as well.
Click to expand...
Click to collapse
MIPS is still supported, but will be dropped from support in the next NDK release. If Huami are sane, they'll switch to an ARM CPU, but I've been told they have some contract or connection with Ingenic to use the MIPS CPU, and there's nothing stopping them continuing to use Android 5.1 with an outdated NDK to build new watches, they just have to live with the legacy OS
This is great find hopefully this will allow to build a working kernel I'm still pushing for sources with Amazfit customer support, so far no major revelations I'm affraid.
There is interesting change of action from Huami. This is part of the email I've received today:
"Our technical team are collating the codes of our products. It would take certain time to come out with a workable way to deal with Linux Kernel. We are working our best now.
It is still of no much use. Even if you can patch a recent kernel to run on MIPS it will be far from being optimized. Same for Android. Anyway I don't understand why they are not just using their own OS on base of an ARM M4 like Garmin or Suunto but an old and deprecated Android.
SteffenBerlin said:
It is still of no much use. Even if you can patch a recent kernel to run on MIPS it will be far from being optimized. Same for Android. Anyway I don't understand why they are not just using their own OS on base of an ARM M4 like Garmin or Suunto but an old and deprecated Android.
Click to expand...
Click to collapse
In theory Android still supports MIPS, there's still generic MIPS sources being updated, just deprecated
The reason they're using an outdated Android build is that's what Ingenic provide, it's either 5.1 or 4.4/4.3
{
"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"
}
I present to you: Kali NetHunter for the Huawei Nexus 6P Android 8.1 Oreo
This is the recommended stable version for the Nexus 6P.
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
~ Prerequisites ~
- Android 8.1 - https://developers.google.com/android/images
- TWRP - https://twrp.me/
- Magisk – https://forum.xda-developers.com/apps/magisk
~~ Downloads ~~
- NetHunter: https://www.offensive-security.com/kali-linux-nethunter-download/
~~ How to Install ~~
- Update to / flash latest official Android release
- Install TWRP
- Copy Magisk and NetHunter image to USB drive
- Reboot into TWRP, insert USB drive.
- flash NetHunter image
- flash Magisk
- Reboot
- Run NetHunter app
- Reboot
~~~ Notes & Updates ~~~
Nexmon is included in the 2020.2 release.
Credits: The Offensive Security Team and the NetHunter community, huge thanks to yesimxev, & kimocoder.
Android Version: 8.1
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the Huawei Nexus 6P
Contributors
@Re4son, @kimocoder, @yesimxev
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/Re4son/android_kernel_huawei_angler
**RESERVED**
**RESERVED**
Little teaser of what more is to come
You are a man of your word.
Huge thanks to you and the entire Kali Nethunter team !
I don't how you did finally get rid of this pesky reboot bug by plugged in wlan adapter, but you delivered.
And don't disappoint.Like always.
I could go on complimenting, but as someone said to me once, back to the issue related subject on hand.
There are none.
--
Even my to an oblivion gebranded Asus NIC is working very good (with Realtek 8812au).The same goes for 8811 and the other AC ones I have.
I hadn't the time to test every single one, but I am curios if the Realtek 8811eu(s) has made it, as well.
For many people this chipset has somekind of importance, because it was the second revision of the TP-LINK TL-WN722N model.
Like you wrote, has Nexmon are couple of problems.
I could use nexutil, but solely without results.
---
I would like to thank you in the name of the Nexus community, who has held on to this device series, for one or another reason.
I will try and look, that my next device a OnePlus 7 or maybe a Xiaomi Mi 9T is going to be..
I wanted to ask if you could post a link to the most recent repository for this kernel.
I tried to build it of yours, about a week ago and couldn't pass the usb related bug.
I started to revisit the Oreo kernel for the Nvidia Shield K1 tablet, perhaps you saw the link to the posts on Twitter, over here at the shield sub-forum.
Unfortunately bricked the device a month after I finished compiling it while trying to port Linux Tegra (Ubuntu flavoured OS to the Shieldtablet..).
I kept the finished kernel.The best result did I link in the Nvidia forum at Xda and 5 other iterations are in my Afh-dev account.
I did a couple test runs yesterday, but had no luck so far.
Maybe you could take a look a the kernel and give me a hint when you have a bit free time, ..next summer?
Many heaps^
UsPdSr
edit.
The request for a link to the recent kernel source has answered itself..
Many thanks for this release. Nethunter works like a Charme
Just for those user, who like to use a other rom, than the resource hungry Google stock one, AOSiP 8.1 works just as well.
If someone rather prefers a stock environment, then SUPERXE or nrdw are a good alternative as well.
The nethunter page says the current download for 2020.2 is available. Does that mean nexmon is fully working ?
Re4son changed the Nexmon files in Nethunter's repo ~2 weeks ago again.
https://gitlab.com/kalilinux/nethun...3e47c0368acbf5878cce/oreo/angler/system/lib64
After some issues* with my 6P during testing various compatible roms for the new kernel, which reminded me painful at the last days of my previous one, which bite the dust end of last year after kimocoder's try to 'enhance' a kernel respectively released a build for android stock, which already existed to the time, based primarily on jcadduono work, revised by Re4son and then as latest working release to the official repository added.After I tried to build one by myself, supported the community(especially for this device at the time) and made pressure to the whole botched so-called "working" releases for Oreo 2 years prior.
He put some bells and whistles on it, but the massive reboots after trying to set external wlan adapter into Monitor mode, didn't let the kernel unfortunately run properly.
I am looking for a new device, but am unsure what to buy.
Beside that the Nexus nostalgic will always be a great and important factor.
Too bad that the foremost specs and the faulty hardware behave not so harmonic are over time.
I can gladly upload installer which I build a couple of days ago with the changes from Nethunter's repo.
If the Xiaomi Mi 9T wouldn't be so "full of MIUI", bootloader restrictions and Anti-Rollback protection, could it be a spectacular device.
But Xiaomi's business strategy to release every week 3 "new(sic!)" devices are a bit too generic for me, without sounding pretentious.
OnePlus is obviously the chosen candidate - Google's Pixel aren't any different from Samsung Galaxy horror show and the ridiculous expensive and at the same time sh*tty performance mastering iPhone by now. :E
The price of the OnePlus are getting affordable, some provider finally starting to pick them up here and even not everything is honkey doorey with them (firm politics have changed rapidly as well) , so are they the best-bad choice.
Sorry, I digressed.
I am happy to upload the kernel or the complete installer if prefered for you to test.
Cheers
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
@Re4son
I noticed the thread title 'rom' contained.
If possible, would I like to ask to change it into 'Overlay' or kernel.
Just for user, who are unsure about the application, function, usability of Kali Nethunter.
*
I wanted to make it clear that the device issues are to 99,9 % result of the age or his famous hardware default(s), not of this awesome work and the entire project behind.
Can't get the phone into monitor mode for the life of me.
Thanks for this very much. Im just starting to get my feet wet with this nethunter stuff. Any tips and tricks would be appreciated.
huge thanks for your work.
there is a problem: i have installed twrp,magsik,android oreo(angler-opm7.181205.001-factory-b75ce068.zip) and nethunter(nethunter-2020.2-angler-oreo-kalifs-full.zip). i could see a new HID KeyBoard Device in Win7 ,but the HID Attacks didn't work well . how can i fix this issue ?
upon flashing the file and booting , i tried opening the nethunter app , but it says "New app build detected: Doing app files update.(init.d and filesDir) and then force closes. the device is connected to the internet . what am i doing wrong ? .os is nrdw's stock optimized
crashnova said:
Can't get the phone into monitor mode for the life of me.
Thanks for this very much. Im just starting to get my feet wet with this nethunter stuff. Any tips and tricks would be appreciated.
Click to expand...
Click to collapse
The complete lack of information is overwhelming.
Which chipset?External adapter or internal chip?
;/
---------- Post added at 07:30 PM ---------- Previous post was at 07:24 PM ----------
Nightslade said:
upon flashing the file and booting , i tried opening the nethunter app , but it says "New app build detected: Doing app files update.(init.d and filesDir) and then force closes. the device is connected to the internet . what am i doing wrong ? .os is nrdw's stock optimized
Click to expand...
Click to collapse
Wipe everything and start over.
Do you build your own installer, or flashed the official release?
I had a couple of problems with Nrdw's rom, if I remember correct.It is likely to work if you fire the last stock on it, or try ABC, they are all very stable.
UsPdSr said:
The complete lack of information is overwhelming.
Which chipset?External adapter or internal chip?
;/
Click to expand...
Click to collapse
My bad. Internal, for now.
crashnova said:
My bad. Internal, for now.
Click to expand...
Click to collapse
Hm, Re4son changed the Nexmon files shortly after the pre-release and apparently fixed them.
I use it not that often and currently have I a seperate setup for work.
In any case, did I build a new installer with a freshly baked chroot, all the updates and upgrades, Apps and the currently recommended kernel for this device.
I uploaded it.
Wipe and format your device and flash afterwards the newest stock rom.
Flash Magisk and try it with the installer again.
If you encounter issues would I refer to the Kali Nethunter's gitlab presence and write a issue report.
The installer (full chroot, bootanimation, kernel..).
https://mega.nz/file/FJoAAI7A#CfAicSrguktZU8yH0X0u1BA-CH8AdWVrHlkbH13MaCk
UsPdSr said:
Wipe everything and start over.
Do you build your own installer, or flashed the official release?
I had a couple of problems with Nrdw's rom, if I remember correct.It is likely to work if you fire the last stock on it, or try ABC, they are all very stable.
Click to expand...
Click to collapse
I flashed the official release
Just after i posted this i tried with the latest stock clean install. even with no encryption and all i had the same error . Does the updating this happen for all devices ?
ill give the file you uploaded a try
Nightslade said:
I flashed the official release
Just after i posted this i tried with the latest stock clean install. even with no encryption and all i had the same error . Does the updating this happen for all devices ?
ill give the file you uploaded a try
Click to expand...
Click to collapse
Do you mean with 'update' the one recently introduced by the Nethunter team?
I assure you that is not in correlation with such bug.
Since release didn't I have a problem with one single external adapter.
As written before, do I not use nexutil often.
Re4son changed the patched firmware ~2 weeks after pre-release.
I cloned the repo, devices and build you the installer with python3.
If you have further issues would I recommend that you issue a bug report on gitlab, or write Re4son, yesimxev or kimo here..
it seems is not clear, is nexus 6p have a working monitor mode and injection working?