Database Develop

Debian on the Vogue

I've been running Debian natively from my SD card for a while, so I decided I'd share the [relatively easy] instructions. First, though, here's the status of the hardware support...
* X11 is working quite nicely. 480x640 resolution is best for using E17.
* I'm trying to think up a solution for the 3D accelerator. LLVMpipe works but it's not much faster than classic Mesa. Maybe that's because I'm only testing performance with Mupen64Plus and SuperTux Ideally we would have an open-source OpenGL ES 1.0 driver with an OpenGL 1.3 wrapper/Gallium state tracker, but unfortunately Qualcomm closed it
* The hardware buttons don't generate input events (except the power button, which apparently makes SDL windows fullscreen).
* USB function ether works. This means you can SSH into it or update packages without a data connection (I don't think data even works).
* Sound doesn't work because Android doesn't use ALSA - or maybe because DZO hasn't written the proper driver...
* Camera(s) would need a Video4Linux driver; again, not my area
* Bluetooth is untested.
* GPS needs userspace work (gpsd?) - maybe the HTC Dream page at HTC-Linux.org has info...
* Calling - untested because: 1) I doesn't got the software, and 2) even if it worked, I have no one to call
If you're willing to wait indefinitely for those things to be fixed (or if you don't care), all you need is a Debian chroot on an EXT2-formatted SD card and my special NBH. The NAND should also work*, but Debian probably wouldn't fit on it. These instructions should also work for Ubuntu, Gentoo, FSO/OpenMoko, Angstrom, ARMedSlack, Fedora, or what have you - the only requirements are ARMv6 or lower and a semi-standard root filesystem layout (i.e. /sbin/init).
For those of you who don't trust binaries, I've uploaded my patches to the kernel and tinboot needed for Debian to boot. For everyone else, I have NBH files ready. Just flash the NBH, insert your SD card, and it should boot.
Links:
http://www.mediafire.com/?mnv2memddug (source)
http://www.mediafire.com/?immywzmmqjn (binaries)
*LogFS patch included and enabled in my NBH.

Interesting, i'm going to have to try it out, any chance of getting it bootable from within android, like haret is with windows?

what exactly is debian??
is it like ubuntu thats on my computer

jadenj5 said:
what exactly is debian??
is it like ubuntu thats on my computer
Click to expand...
Click to collapse
yes
10char

little confused though, where do I get the debian root files though

Debian Root
Instructions to build your own RootFS follow. If you're lazy, Google for a pre-built one.
If you're on Ubuntu:
Code:
sudo apt-get install debootstrap
sudo debootstrap --arch armel --foreign unstable root/ http://http.us.debian.org/debian
Substituting "unstable" for "stable" or "testing", "root/" with the the path to the directory you want the rootfs in (probably your SD card mountpoint), and your country code in ftp.??.debian.org (or another mirror). You might also need to do
Code:
sudo mount -o remount,rw,dev,exec $MOUNTPOINT
to your SD card (which, again, should be ext2-formatted) for debootstrap to work.
Then to complete the bootstrap:
Code:
sudo apt-get install qemu-kvm-extras-static
sudo cp /usr/bin/qemu-arm-static $ROOTFS/usr/bin/
sudo chroot $ROOTFS
From inside the chroot, do
Code:
/debootstrap/debootstrap --second-stage
Then, apt-get install whatever you want on the phone (after configuring /etc/apt/sources.list), exit the chroot, unmount the card, insert it in your phone, and boot!
You'll need - at the very least - xserver-xorg-video-fbdev and xserver-xorg-input-evdev *WITHOUT* installing the other video or input drivers. And a desktop/window manager. If you haven't used Debian before, try e17.

Thanks man, i'm going to go check it out

If you're lazy, Google for a pre-built one.
Click to expand...
Click to collapse
can't find one.?

If you're on Ubuntu:
Click to expand...
Click to collapse
ubuntu 10.04 debootstrap doesnt know about stable/testing/unstable names, but knows about lenny, squeeze, sid

okay, I maked Debian unstable rootfs - here it is (127MB tar.bz2). here is dpkg -l.
root password is "1", apt sources.list is configured to most close to me mirror. I also added /proc into fstab.
how to pack my rootfs into .img image now?

can you post a screenshots please ???

there is nothing to show now, really. we need to make working pack first.
google e17 screenshots, on device you will have same.

a note about the sound issue. You are correct in that the vogue kernel does not have alsa support at this time.

nice job on this

Code:
E: No such script: /usr/share/debootstrap/scripts/stable
debootstrap installed with no errors but that's what I get when I try to run
Code:
sudo debootstrap --arch armel --foreign stable /media/79e9dd5a-174b-4324-a704-6aa06807fe35 http://http.us.debian.org/debianc

Try "lenny" instead of stable.

gTan64 said:
Try "lenny" instead of stable.
Click to expand...
Click to collapse
progress but now i get
Code:
I: Retrieving Release
E: Failed getting release file http://http.us.debian.org/debianc/dists/lenny/Release

Look closely - the mirror URL doesn't contain "debianc", does it?

gTan64 said:
Look closely - the mirror URL doesn't contain "debianc", does it?
Click to expand...
Click to collapse
I'm F-ing retarded
/facepalm
-Edit- any packages you would advise to install?
New problem
Code:
[email protected]:/$ sudo chroot /media/79e9dd5a-174b-4324-a704-6aa06807fe35_
chroot: cannot run command `/bin/bash': Exec format error
Could it be because sudo apt-get install qemu-kvm-extras-static had no packages and I had to install sudo apt-get install qemu-kvm-extras

Code:
sudo cp /usr/bin/qemu-arm-static $ROOTFS/usr/bin/
This step is essential - without qemu-arm-static in your chroot, you won't be able to run/emulate any ARM binaries (in this case, Debian-armel's /bin/bash).
Yes, you do need the static version. Last I checked it was actually in the Ubuntu repositories, so look again...
As far as what packages to install, here you go.
Essential packages: xserver-xorg-{video-fbdev,input-{mouse,keyboard}}
Essential desktop packages (pick one): e17 fluxbox lxde xfce4
Recommended packages: cellwriter xfce4-goodies
Suggested packages: Whatever floats your boat.
Packages I installed even though having no sound makes them useless: zynaddsubfx supertux sopwith bomberclone

[TUTORIAL] The Step-By-Step guide to build Cyanogenmod7 for the LG Optimus 2X

aMpeX proudly presents:
The Step-By-Step guide for building CM7
for the Optimus 2X​
Disclaimer:
I'm taking no responsibility for any damage that might occur to your phone or your PC
This guide illustrates how to setup an UBUNTU 11.04 equipped PC to build CM7 from source
It does not provide any support beyond that operating system, so if you insist on using other
Linux distributions, either adapt the guide yourself or look elsewhere.
Moreover I'm not providing any support for any problems that might occur during the course
of this guide, if they are not introduced by faults within the guide itself. I will only
troubleshoot the activities that this guide is based upon and won't be able to help with your
general linux problems. Feedback however is greatly appreciated.
Reposting this on other forums:
Feel free to post this guide on other forums. I'd like to be given credit though. Thanks
I am new to this myself, but I thought I'd share my findings after successfully building my first kang.
News & changelog:
v0.92 2011/06/01 Fix:
Added "change directory" before init repository (thanks to peewster)
v0.91 2011/05/31 Fix:
Fixed PATH exports (thanks to bhanvadia)
v0.9 2011/05/31 Initial release:
Still much formatting to be done, typos possible. Leave me some feedback if you encounter them.
Alright, so you want to build your own CM7 KANG's ?
Step 0: The starting point + info
When you start this guide, I assume that you just installed your Ubuntu 11.04 copy to your PC and set up all the drivers to your hearts content.
All commands are supplied, as they would be typed in from a USER ACCOUNT, if you operate from the root account, you will
have to add /home/<yourusername> to the most commands. I suggest, after performing the actions required by root, that you log out by typing
Code:
exit
What you need:
A working copy of Cyanogenmod7 installed on your phone
A PC with Ubuntu 11.04 installed (NOTE: If you're about to install Ubuntu from scratch, use the 64Bit version.
I can build CM7 on a 32Bit OS just fine. But AOSP for example won't build beyond Froyo on 32Bit.
At least 20GB of free space (including space required for the operating system itself)
A considerably fast internet connection (syncing the repo takes everal Gbs)
At least 3 hours of time.
All done? Then let's get started:
Step 1: Install the Java JDK
Go to System → Administration → Synaptics Package Manager
Here, we have to enable the partner repositories.
Go to Settings → Repositories → Other Software → Tick Canonical Partners and hit Close
Now push the „Reload“ button, and use the Search button to find the sun-java6-jdk package
tick the box in front of it and choose „Mark for installation“ and accept the following dialogue.
Click the „Apply“ button. Accept the dialogues, you now have the Java JDK installed.
Step 2: Install the Android SDK
Go here and download this.
Extract the archive to a directory of your choice.
Open a Terminal, navigate to the „tools“ subfolder and run the AVD Manager using ./android
In the new Window hit „Available Packages“ tick the „Android Repository“ and select „Install selected“
Once thats done, close everything up, time for step 3.
Step 3: Set up udev
The description from the CyanogenMod wiki struck me as being a slightly bit overkill, and, while it might be necessary for other devices, for LG phones this works just fine:
Create a new file on your desktop named
Code:
99-android.rules
and fill them with the following content:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
This will enable the debugging for LG devices, if you have time, it won#t hurt to add the other vendors. Just add another line
like above and replace the „1004“ with the appropriate vendor ID from http://developer.android.com/guide/developing/device.html (scroll to the bottom)
Log in as root using
Code:
sudo su
and paste our file to
Code:
/etc/udev/rules.d
using the terminal (cp)
Set permissions for the file using
Code:
chmod a+r /etc/udev/rules.d/99-android.rules
Now would probably be a good time to check if adb is working correctly.
But first, lets update the PATH so we can type „adb“ anywhere on the file system.
Navigate to your user home directory, press CTRL+H to show hidden files and edit the
Code:
.bashrc
file by adding the following
Code:
export PATH="/home/<yourusername>/<path to the android SDK >/platform-tools/:${PATH}"
export PATH="/home/<yourusername>/bin/:${PATH}"
(The 2nd line is necessary for later)
NOTE:This only enable the use of adb everywhere when logged in with your username. When working as root, you'll have
to add a separate line with /home/<yourusername> in front of the path above.
You have to log out and in again for the changes to take effect.
Now check if you can see your phone with
Code:
adb devices
Alright, still awake? Good, because now it gets interesting
Step 4: Install build packages and create directories
Since we already installed the JDK this command differs a bit from the Cyanogen Wiki:
For 32 and 64 Bit
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool
For 64 Bit only
Code:
sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.4-multilib g++-4.4-multilib
Now we need 2 directories
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
Almost there ….
Step 5: Install the repository
Now we need our repo binary:
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
(credits to p.valenta for notifying me of the adress change)
NOTE: You may need to reboot now
Change to your previously created directory:
Code:
cd ~/android/system/
Initialize the repository:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Enter your Name, eMail adress and select if you want colors or not.
AND NOW THE FINALE
Code:
repo sync -j16
Get yourself a BIG coffee, because this is going to take MUCH MUCH time, because basically you are now checking out all there is to CyanogenMod.
But wait, we're not done yet. Hang on
Step 6: Getting proprietary files for the Optimus 2X
For this step, you need an O2X with a running Cyanogenmod build, so if you're still on stock, this is the time to flash Cyanogenmod for the first time.
Connect your phone to your PC via USB and
navigate to the device tree in your repo folder:
Code:
cd ~/android/system/device/lge/p990/
and run
Code:
./extract-files.sh
This will extract some libs from your device. But sadly, not all of them (build will still fail) but we will fix this now.
Go to
Code:
https://github.com/koush/proprietary_vendor_lge/tree/gingerbread/p990
and click the download button on the right.
Extract the „p990“ folder located in the subfolder
Code:
/koush-proprietary_vendor_lge-a43238f/
in the archive to
Code:
~/android/system/vendor/lge/
Step 7: Get latest ROMManager
I know I must be annoying the sh** out of you by now, but hang in there
Code:
~/android/system/vendor/cyanogen/get-rommanager
Step 8: BUILD F***ING EVERYTHING
Now this is what you've been waiting for huh?
Sync the repository again:
Code:
cd ~/android/system/
repo sync
Build the ROM
Code:
. build/envsetup.sh && brunch p990
Wait
When everything is finished, your KANG will be stored in
Code:
~/android/system/out/target/product/p990/
And THATS IT!
Congratulations, you have just built your own CM7 KANG, don't forget to share it to other nightly testers
Cheers aMpeX

Useful stuff and tools:
SH script by bhanvadia, tailored to the directories introduced by this tutorial:
Download here
Extract anywhere and make it executable by typing
Code:
chmod +x kang.sh
Create shortcut to the output directory of your KANGs
Type
Code:
ln -s ~/android/system/out/target/product/p990/ <your desired shortcut location>

nice guide, really liked it.
too bad there were none when I started making my kangs.
btw: I use mac it is bit different for mac. but nothing its missing.
Here is file you keep on you desktop to make it work without any typing of commands after you setup your computer working directory as per guide by aMpeX.
and check post #2 for making that file executable.....
kang.sh

bhanvadia said:
nice guide, really liked it.
too bad there were none when I started making my kangs.
btw: I use mac it is bit different for mac. but nothing its missing.
add "~/android/bin/" to path too so you can "repo sync" from anywhere.
just a suggestion... can upload build.sh file on here to make it easy.
something like
1. for clean and build
2. for repo sync
open file and press your options.
thats what I use...
Click to expand...
Click to collapse
That's why the guide states its for ubuntu. I found that even the Cyanogenmod Wiki entries don't work completely for the latest ubuntu (with g++ and gcc 4.3 not being available anymore, also hat huge problems with the java jdk at first)
I'll add the additional PATH variables as you suggested. Thank you.

aMpeX said:
That's why the guide states its for ubuntu. I found that even the Cyanogenmod Wiki entries don't work completely for the latest ubuntu (with g++ and gcc 4.3 not being available anymore, also hat huge problems with the java jdk at first)
I'll add the additional PATH variables as you suggested. Thank you.
Click to expand...
Click to collapse
Here is file you keep on you desktop to make it work without any typing of commands after you setup your computer working directory as per guide by aMpeX.
PS: aMpeX can you just test that file??? just repo sync or rom manager update options.

awesome guide !!! thanks aMpeX !

seems to be working, after you chmod+x the sh file that is. My Repo Sync is stuck at 1%, but I doubt its related to your file.
I'll add it to the 2nd post

aMpeX said:
seems to be working, after you chmod+x the sh file that is. My Repo Sync is stuck at 1%, but I doubt its related to your file.
I'll add it to the 2nd post
Click to expand...
Click to collapse
modified my mac file i use to fit to your setup of directories, just changed directories. ...
yeah then it would work, hope it make it more easy
GET the KANGs flowing...........

aMpeX said:
Useful stuff and tools:
SH script by bhanvadia, tailored to the directories introduced by this tutorial:
Download here
Extract anywhere and make it executable by typing
Code:
chmod +x kang.sh
Create shortcut to the output directory of your KANGs
Type
Code:
ln -s ~/android/system/out/target/product/p990/
Click to expand...
Click to collapse
Download link is sending to wrong post still....
now it should work like this....
http://forum.xda-developers.com/showpost.php?p=14310172&postcount=5
copy
http://forum.xda-developers.com/showpost.php?p=14310172&postcount=5

Can you please also state that it only works on 64bit builds of ubuntu and not 32bit...

Renegade_Rulez said:
Can you please also state that it only works on 64bit builds of ubuntu and not 32bit...
Click to expand...
Click to collapse
Aside from what you can read on the net, my KANGs build perfectly fine on Ubuntu 32Bit
No reason to not install 64Bit though. I'll add a remark in the first post.
Edit: After some asking and digging, read this:
http://twitter.com/#!/CM_arcee/status/75677847712309249
So while standard Gingerbread cannot be built by 32Bit, the CyanogenMod7 repository can.

is this meant to download a lot of stuff for different phones? mine is downloading a lot of stuff at step 5 and it's taking forever..

Imperticus said:
is this meant to download a lot of stuff for different phones? mine is downloading a lot of stuff at step 5 and it's taking forever..
Click to expand...
Click to collapse
It will download files for each and every phones supported by CyanogenMod, thats why its called cyanogen repo, not just P990 repo, but mostly you will use stuff thats required by your phone.
and its suggested to have 15 - 20 GB free, as it takes a lot....
3.5 GB is just "out" folder when it compiles for one device (P990)......

bit of a noob.. done everything..when I try to make the build using build/envsetup.sh i get permission denied
Any help please?

copy/paste the command from the tutorial
there is a leading dot and space before "build
Code:
. build/envsetup,sh && brunch p990

Thank's for the tutorial but i allways get no gsm function build
logcat -b radio
RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
Click to expand...
Click to collapse
or
Couldn't find 'rild' socket; retrying after timeout
Click to expand...
Click to collapse

What baseband are you using? Make sure that the lge-ril.so is in your proprietary files

aMpeX said:
What baseband are you using? Make sure that the lge-ril.so is in your proprietary files
Click to expand...
Click to collapse
Thank's for repy.
lge-ril.so is in and generally i flash my build coming from cyano #31 (405) and mcr18 (405)
So...405

Possibly (if you synced the proprietary repository by koush AFTER you ran extract-files.sh) your ROM still includes the lge-ril for 0218.
Try reflashing the ril with the methods provided in this forum.
Other than that, I have no idea what might be causing your problems.

old ril file from koush files do work on 405 baseband too, but you feel better performance with new ril. with old ril you may loose signals sometime.
delete your vendor/lge/p990 folder, and download again from koush's files and put it back there. make sure your directories are in order
example: for lib-ril.so in as below
like ~/android/system/vendor/lge/p990/proprietery/lib/

[Tutorial][ROM][5.1.1][Pure AOSP] Kali Nethunter with 5.1.1 AOSP

Hello all today I will be showing you how to flash Kali Nethunter 2.0 onto your Nexus 5 device running AOSP 5.1.1_r13.
Prerequisites:
Custom recovery, I recommend TWRP 2.8.7.1 (I used it for this tutorial)
Updated bootloader which can be found here: Bootloader & Radio update
Supersu v2.46 Download
First let's setup our build environment.
Java Development Kit 7:
Code:
sudo apt-get install openjdk-7-jdk
The build tools:
Code:
sudo apt-get install git gnupg flex bison gperf build-essential
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386
libgl1-mesa-dev g++-multilib mingw32 tofrodos
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
The repo command:
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Let's add bin to our path, the first step here is for Ubuntu 14.04 (Not sure if later distro's are the same) and the second step is for Linux Mint 17+
Step 1 (Ubuntu):
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Step 2 (Mint):
Code:
sudo gedit /etc/bash.bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify yourself to the repo:
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Sync the Repo (This may take awhile):
Code:
mkdir ~/Source
cd ~/Source
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r13
repo sync
After the repo has synced fully you must install the Nexus 5 binaries which are below into the root of the Source (or whatever you called it) folder.
Binaries:
NFC, Bluetooth & Wifi (Broadcom) for 5.1.1 - Download
Camera, Sensors & Audio (LG) for 5.1.1 - Download
Graphics, GSM, Camera, GPS, Sensors, Media, DSP & USB (Qualcom) for 5.1.1 - Download
Jump into ~/Source (Your folder) and run envsetup:
Code:
cd ~/Source && source build/envsetup.sh
Choose the device (It should be number 8)
Code:
lunch
Let's build our rom:
Code:
make -j4 otapackage
the -j flag can be specified depending on your CPU on mine I get a good rate at -j8 (HexaCore 3.5GHz)
GAPPS:
I used the PICO modular package due to wanting the smallest Google fingerprint from here http://forum.xda-developers.com/android/software/tk-gapps-t3116347
After copying everything to your sdcard you can now perform a full wipe (After a backup of course) and flash the newly built rom from ~/Source/out/target/product/hammerhead/ and then flash gapps (Not required) & SuperSU and then reboot into your pure AOSP rom.
Flash SuperSU before rebooting your phone as it's required for the next step
After a full reboot of the system update busybox to the latest release and the download Kali Nethunter from here and flash in recovery
I Take no responsibility if your device becomes bricked I made this tutorial for educational purposes as I had no problem flashing my device with the above steps.
EDIT Optional Step:
I Also flashed the ElementalX Kernel BEFORE flashing Kali Nethunter, this is not a requirement but this may help with battery drain ElementalX.org
CREDITS:
@osm0sis For the GAPPS (Awesome guy)
Offensive Security For Kali Nethunter (Thanks guys)
@scrosler For his tutorial on how to build AOSP from source (Taught me alot)
@Chainfire For the most excellent SuperSU
TeamWin For their awesome recovery
@flar2 for a wicked kernel
If i've forgotten anyone then let me know I'll add you

Or you can just download zip from their website and flash it.

Tazerick said:
Or you can just download zip from their website and flash it.
Click to expand...
Click to collapse
Well actually yes you can but thanks for your vibrant input, this is just to help people learn how to do it themselves completely from source.

How much about the source code takes?The source folders has taken up to 7GB and seems to grow endless, And what does mingw32 do in compiling?Sorry for the questions but I'm just a Linux beginner interested in this and it‘s a little bit hard for me to access Google for some reasons. Tks in advance

I want to thank the OP for sticking his neck out with this thread. I found it very helpful as I was having a lot of trouble getting Nethunter to install until I found this thread.
Things to know about Nethunter (that I didn't know when I started)
- it is not a complete rom, but if you flash it into a rom slot using multirom, it will get partway through booting and may confuse you.
- it does replace the boot.img file with its own
- it is very sensitive to the particular combination of ROM and NH release you're attempting to install.
So, things I tried that did not work:
- flash just NH 2.0. Whoops. Nope, not a complete ROM, as I could see after poking around in the zip file.
- flash the N5 KitKat nethunter 2.0 release over cm-11-20141008-SNAPSHOT-M11-hammerhead.zip
This just failed to boot, black screen.
- flash the N5 Lollipop Nethunter 2.0 release over cm-12.1-20150901-SNAPSHOT-YOG4PAO237-hammerhead.zip
Again, black screen. This one I did after doing a complete device wipe and fastboot flash of the 5.1 bootloader and boot.img, as well as one attempt in multirom as a secondary.
The key takehome for me in this post was that someone had successfully gotten NH 2.0 lollipop to install on an AOSP rom based on 5.1.1 R13.
So I grabbed the ROM from this thread:
http://forum.xda-developers.com/goo...nt/rom-aosp-userdebug-stagefright-ii-t3178947
reinstalled multirom after redoing my phone, and installed the flashable zip file aosp_hammerhead-ota-eng.soilandwater.zip
Rooted that, installed busybox, rebooted and used the multirom TWRP to flash Nethunter over the AOSP.
It lives! It boots!
If that had failed, I was looking at potentially installing the pwnkernel for 5.1.1 into the multirom secondary slot. My impression is that the Nethunter included kernel and boot.img are pretty sensitive about the exact lollipop build they can play nicely with, and that the pwnkernel project is less sensitive to that.
One other tip: when you start flashing nethunter, put your phone either in the fridge or on an icepack from the freezer, covered with a thin towel.
The nethunter flash process is very, very processor intensive and the CPU will heat well past the stock thermal throttling if you let it.
My end result is that I have Marshmallow in my default slot and Nethunter as my secondary. Both are booting happily.
Later today my USB antenna and OTG cables should arrive.

roustabout said:
One other tip: when you start flashing nethunter, put your phone either in the fridge or on an icepack from the freezer, covered with a thin towel.
The nethunter flash process is very, very processor intensive and the CPU will heat well past the stock thermal throttling if you let it..
Click to expand...
Click to collapse
This was amusing. Beware of condensation! Anyway, there's also this beta that needs some volunteers. I actually heard from Binkybear that there will be a new incarnation coming soon... but the idea is to make NetHunter basically an update.zip with a kernel+an app and the app does the actual installation of the Kali 2.0 chroot.

"beware of condensation" - yep, hence the towel to sop up most of it.
I like the idea of flashing a kernel and an APK and letting the rest of the process get handled more visibly.
I'm seeing some interesting stuff in the NH 2 release. If I ssh into my phone and invoke the menu, everything that requires wlan1mon works fine.
If I launch the console menu option from the Kali launcher, almost none of the things that require access to a monitoring interface work.
If I remember it correctly, that stuff was working before I enabled login via ssh. I may well have to redo the install, though, I've just tried to set tethering on my phone and am discovering that marshmallow takes a very dim view of fiddling with the N5 build.prop.

[ROM][10.0][Xiaomi Mi 9][UNOFFICIAL]LineageOS 17.1 CLEAN, STOCK [2020-07-10]

** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
**Download Link Updated to build 2020-07-10**
TL;DR:
This is a Clean, Stock LineageOS Build for Xiaomi Mi 9 (cepheus) that does NOT include any GApps, MicroG, or Signature Spoofing.
What you choose to add/modify after installing this ROM is entirely up to you.
All,
I wanted to distance myself from Google as much as possible, so I decided to build LineageOS from the source.
I used the LineageOS source they provide via GitHub, available here.
I also use the Proprietary Blobs for the Cepheus Device Tree from Demon000's GitHub, available here.
To get current version to build, I also needed to add the LineageOS/android_hardware_xiaomi source to my local manifest and use the repopicks Cozzymy13 includes in the OP of his ROM's thread. [Thanks k1l for and Cozzymy13 for pointing out these additions!]
The result is a stock build of LineageOS 17.1 for the Cepheus device. In the spirit of LineageOS, this does not include Signature Spoofing. You will need to use Xposed or some other method if you desire that functionality.
This also does not include MicroG or any other additional applications. This is pure LineageOS, built on 2020-07-10.
NanoDroid patcher works well for anyone who wants to add MicroG support. You will still need to use Xposed or similar if you want Signature Spoofing as NanoDroid does not offer a patch for Android 10 as of this build.
Feel free to provide download mirrors.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Flash lineage-17.1-20200710-UNOFFICIAL-cepheus.zip
3) Format Data (Wipe -> Format Data -> type "yes"
3b) - OPTIONAL - Flash Magisk Zip for Root
4) Reboot to system
Alternate Install Steps for Full MicroG with Signature Spoofing:
From TWRP:
1) Wipe Date (standard wipe)
2) Flash lineage-17.1-20200710-UNOFFICIAL-cepheus.zip
3) Format Data (Wipe -> Format Data -> type "yes"
3b) - OPTIONAL - Flash Magisk Zip for Root
4) Reboot to system (ignore any errors about missing Google Services)
5) Reboot to TWRP
6) Flash NanoDroid Patcher (either the Full package or you can customize per the instructions in the NanoIx link below)
7) Reboot
8) Install the Magisk Module for Xposed Framework and the EDXposed.ZIP as per the instructions in the Xposed link below)
9) Reboot to activate the new Module
10) Within the EDXposed App, Install the FakeGApps Module
11) Reboot to activate the new Module
As everything I really care about is working in this build, I do not plan to devote much, if any, time to "supporting" this release. I just thought I'd share my clean 17.1 LineageOS in case anyone else is interested.
Download:
LineageOS 17.1 Unofficial (Built: 2020-07-10) md5sum: 1c340fc16a6fbc7586d0a856acb9c600
NanoDroid Patcher (optional): NanoIx
Magisk Root (optional): Magisk
XPosed for Android 10 - Magisk Module (optional): Xposed

Just found a new bug:
Wireless Hotspot will not start.
Can anyone confirm if this is an issue with other LineageOS build for this device?

Messed around too much and had to re-flash. Afterwards, I could not get apps to register with MicroG Cloud Messaging, so some notifications were not working.
If anyone runs into this issue, just get a root shell and run this command:
Code:
adb shell
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546 --receiver-include-background
This will register the current user with Cloud Messaging. You can verify this works with the "Push Notification Tester" app in the Aurora Store.
This knowledge comes to you courtesy of lxp over on the MicroG Github

Using for 3 days now, and is working good, i don't use MicroG and no google apps. Nice work

Using it for second day, and everything seems fine, hotspot working too.
Only problem is with Revolut app which say it's incompatible app, are there any workaround?
Btw. Good job, thanks!

Simonell said:
Using it for second day, and everything seems fine, hotspot working too.
Only problem is with Revolut app which say it's incompatible app, are there any workaround?
Btw. Good job, thanks!
Click to expand...
Click to collapse
I'm not familiar with that App. Is it working on other AOSP-based ROMS?
It looks like Mobile Banking app. I don't have an account to really test; nor do I have the energy to try and troubleshoot individual apps.
Are you by chance running it on a rooted install? If you have rooted this ROM, that could be why you are having trouble with that Banking App. I know they tend to not like rooted phones.
I have been happy with this build since I compiled it on the 25th, but I may update and compile from current source. It I do, I can make it available for you to try.
Of course, if it is broken on other LineageOS builds, or if you are rooted, I would expect it to still complain on this build, too.
If you rooted with Magisk, there is a Magisk Hide option in the Magisk Manager app that may let you hide your root from that specific banking app.

photonmedia said:
I'm not familiar with that App. Is it working on other AOSP-based ROMS?
It looks like Mobile Banking app. I don't have an account to really test; nor do I have the energy to try and troubleshoot individual apps.
Are you by chance running it on a rooted install? If you have rooted this ROM, that could be why you are having trouble with that Banking App. I know they tend to not like rooted phones.
I have been happy with this build since I compiled it on the 25th, but I may update and compile from current source. It I do, I can make it available for you to try.
Of course, if it is broken on other LineageOS builds, or if you are rooted, I would expect it to still complain on this build, too.
If you rooted with Magisk, there is a Magisk Hide option in the Magisk Manager app that may let you hide your root from that specific banking app.
Click to expand...
Click to collapse
It's working after root and Hide in Magisk Manager. I was confused because it was showing up as "Incomaptible with device" in google play store, after rooting it's installed. Thanks!
Could you send commands which you used to compile ROM? I have some free space on my home server, maybe I could set up Jenkins with auto building. Is it possible to get auto update working?

Simonell said:
It's working after root and Hide in Magisk Manager. I was confused because it was showing up as "Incomaptible with device" in google play store, after rooting it's installed. Thanks!
Could you send commands which you used to compile ROM? I have some free space on my home server, maybe I could set up Jenkins with auto building. Is it possible to get auto update working?
Click to expand...
Click to collapse
ThePiGuy already has a great overview of building for unsupported/unofficial devices here
You'll need to install all the base requirements on your build distro before you proceed. This includes the adb and fastboot tools, the build packages, and the java versions as mentioned in this LineageOS build guide for one of their other Xiaomi "supported" devices.
What I post here is basically my method of pulling the relevant info from the two build guides above to get a successful build for the Xiaomi Mi 9 (cepheus).
I will say as for the Requirements, it really needs to be 16GB of RAM. I tried building in a VM with 8GB multiple times and it failed due to running out of memory. This could just be because I run on SSDs and do not use SWAP space/files...
When it comes to your Proprietary Blobs, I pulled mine from Demon000's Github Source
You will need these repos, and we will cover these steps further down:
vendor_xiaomi
kernel_xiaomi_sm8150
device_xiaomi_cepheus
device_xiaomi_sm8150_common
When performing the "ccache -M $G" command I used:
Code:
ccache -M 50G
Now let's create your base folder where you want to make all the magic happen. Be sure to have plenty of storage available. In my case, I needed about 200GB.
Code:
mkdir -p ~/android/lineage
cd ~/android/lineage
When performing your repo init commands, reference branch 17.1:
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
Sync the repo to your current working directory, in this case the lineage folder you created above (which should still be your working directory):
Code:
repo sync
This will pull down 100+GB of files, so this takes quite some time.
Following along, you should be in your folder called "lineage" where you ran your repo init and repo sync commands. In my case this is:
Code:
~/android/lineage/
Attached is my manifest file called "cepheus.xml" that references the Demon000 github source.
Place this cepheus.xml file here:
Code:
~/android/lineage/.repo/local_manifests/cepheus.xml
(creating the local_manifests folder if necessary)
Now you need to complete the build of your device tree.
You will clone each of the four repositories above into their respective locations in the device tree:
vendor_xiaomi -> ~/android/lineage/vendor/xiaomi/
kernel_xiaomi_sm8150 -> ~/android/lineage/kernel/xiaomi/sm8150
device_xiaomi_cepheus -> ~/android/lineage/device/xiaomi/cepheus
device_xiaomi_sm8150_common -> ~/android/lineage/device/sm8150_common
Note: Be sure to check each of those four locations and make sure the contents of the repository are in those folders, not, for example: ~/android/lineage/device/sm8150_common/device_xiaomi_sm8150_common. You don't want the repo contents within that extra subfolder...
In my case, I created the necessary directory structure and changed to that directory, then cloned the repo and moved the contents from the subfolder created by the clone operation into the correct location.
Code:
mkdir -p ~/android/lineage/vendor/xiaomi/
cd ~/android/lineage/vendor/xiaomi
git clone https://github.com/Demon000/vendor_xiaomi.git
mv vendor_xiaomi/* .
rm -r vendor_xiaomi
Code:
mkdir -p ~/android/lineage/kernel/xiaomi/sm8150
cd ~/android/lineage/kernel/xiaomi/sm8150
git clone https://github.com/Demon000/kernel_xiaomi_sm8150.git
mv kernel_xiaomi_sm8150/* .
rm -r kernel_xiaomi_sm8150
Code:
mkdir -p ~/android/lineage/device/xiaomi/cepheus
cd ~/android/lineage/device/xiaomi/cepheus
git clone https://github.com/Demon000/device_xiaomi_cepheus.git
mv device_xiaomi_cepheus/* .
rm -r device_xiaomi_cepheus
Code:
mkdir -p ~/android/lineage/device/xiaomi/sm8150_common
cd ~/android/lineage/device/xiaomi/sm8150_common
git clone https://github.com/Demon000/device_xiaomi_sm8150_common.git
mv device_xiaomi_sm8150_common/* .
rm -r device_xiaomi_sm8150_common
Now return to your base lineage folder:
Code:
cd ~/android/lineage
Now that you have init'd and synced your repo and pulled your proprietary blobs into their respective folders, you are ready to build with the brunch command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
For me, I have no idea how long this took to complete as I left it running overnight. I would imaging at least 4 hours on my i5 device. Once it's done, you should have a TWRP-flashable zip and an OTA zip in the ~/android/lineage/out folder.
Note: If after compiling for some time, the process fails with errors, it should provide you with information on how to track down the error. In my case, I ended up with it stopping with a failure a couple times, but I just re-ran the above brunch command and it picked up where it left off, eventually completing successfully. YMMV
I'm sure there are cleaner, simpler ways of going about this, but I'm just getting my feet wet with current Android source. I haven't really done any sort of Android "development" since the days of KitKat...

photonmedia said:
ThePiGuy already has a great overview of building for unsupported/unofficial devices here
You'll need to install all the base requirements on your build distro before you proceed. This includes the adb and fastboot tools, the build packages, and the java versions as mentioned in this LineageOS build guide for one of their other Xiaomi "supported" devices.
What I post here is basically my method of pulling the relevant info from the two build guides above to get a successful build for the Xiaomi Mi 9 (cepheus).
I will say as for the Requirements, it really needs to be 16GB of RAM. I tried building in a VM with 8GB multiple times and it failed due to running out of memory. This could just be because I run on SSDs and do not use SWAP space/files...
When it comes to your Proprietary Blobs, I pulled mine from Demon000's Github Source
You will need these repos, and we will cover these steps further down:
vendor_xiaomi
kernel_xiaomi_sm8150
device_xiaomi_cepheus
device_xiaomi_sm8150_common
When performing the "ccache -M $G" command I used:
Code:
ccache -M 50G
Now let's create your base folder where you want to make all the magic happen. Be sure to have plenty of storage available. In my case, I needed about 200GB.
Code:
mkdir -p ~/android/lineage
cd ~/android/lineage
When performing your repo init commands, reference branch 17.1:
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
Sync the repo to your current working directory, in this case the lineage folder you created above (which should still be your working directory):
Code:
repo sync
This will pull down 100+GB of files, so this takes quite some time.
Following along, you should be in your folder called "lineage" where you ran your repo init and repo sync commands. In my case this is:
Code:
~/android/lineage/
Attached is my manifest file called "cepheus.xml" that references the Demon000 github source.
Place this cepheus.xml file here:
Code:
~/android/lineage/.repo/local_manifests/cepheus.xml
(creating the local_manifests folder if necessary)
Now you need to complete the build of your device tree.
You will clone each of the four repositories above into their respective locations in the device tree:
vendor_xiaomi -> ~/android/lineage/vendor/xiaomi/
kernel_xiaomi_sm8150 -> ~/android/lineage/kernel/xiaomi/sm8150
device_xiaomi_cepheus -> ~/android/lineage/device/xiaomi/cepheus
device_xiaomi_sm8150_common -> ~/android/lineage/device/sm8150_common
Note: Be sure to check each of those four locations and make sure the contents of the repository are in those folders, not, for example: ~/android/lineage/device/sm8150_common/device_xiaomi_sm8150_common. You don't want the repo contents within that extra subfolder...
In my case, I created the necessary directory structure and changed to that directory, then cloned the repo and moved the contents from the subfolder created by the clone operation into the correct location.
Code:
mkdir -p ~/android/lineage/vendor/xiaomi/
cd ~/android/lineage/vendor/xiaomi
git clone https://github.com/Demon000/vendor_xiaomi.git
mv vendor_xiaomi/* .
rm -r vendor_xiaomi
Code:
mkdir -p ~/android/lineage/kernel/xiaomi/sm8150
cd ~/android/lineage/kernel/xiaomi/sm8150
git clone https://github.com/Demon000/kernel_xiaomi_sm8150.git
mv kernel_xiaomi_sm8150/* .
rm -r kernel_xiaomi_sm8150
Code:
mkdir -p ~/android/lineage/device/xiaomi/cepheus
cd ~/android/lineage/device/xiaomi/cepheus
git clone https://github.com/Demon000/device_xiaomi_cepheus.git
mv device_xiaomi_cepheus/* .
rm -r device_xiaomi_cepheus
Code:
mkdir -p ~/android/lineage/device/xiaomi/sm8150_common
cd ~/android/lineage/device/xiaomi/sm8150_common
git clone https://github.com/Demon000/device_xiaomi_sm8150_common.git
mv device_xiaomi_sm8150_common/* .
rm -r device_xiaomi_sm8150_common
Now return to your base lineage folder:
Code:
cd ~/android/lineage
Now that you have init'd and synced your repo and pulled your proprietary blobs into their respective folders, you are ready to build with the brunch command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
For me, I have no idea how long this took to complete as I left it running overnight. I would imaging at least 4 hours on my i5 device. Once it's done, you should have a TWRP-flashable zip and an OTA zip in the ~/android/lineage/out folder.
Note: If after compiling for some time, the process fails with errors, it should provide you with information on how to track down the error. In my case, I ended up with it stopping with a failure a couple times, but I just re-ran the above brunch command and it picked up where it left off, eventually completing successfully. YMMV
I'm sure there are cleaner, simpler ways of going about this, but I'm just getting my feet wet with current Android source. I haven't really done any sort of Android "development" since the days of KitKat...
Click to expand...
Click to collapse
Thanks! I will try this guide at the weekend, and post results

Simonell said:
Thanks! I will try this guide at the weekend, and post results
Click to expand...
Click to collapse
For what it's worth, I just successfully compiled an updated build today, but it fails to boot after flashing. Had to go back and flash my 2020-01-25 build from the OP.
YMMV

.

stock mi 9 camera works or not on this rom? because i don't raelly like gcam.

ahmadharith said:
stock mi 9 camera works or not on this rom? because i don't raelly like gcam.
Click to expand...
Click to collapse
I was able to install ANXCamera and their ANXCustLibsQ_160.DisloyalInnocentVelvetworm.zip Libraries and it works fine for me. Sometimes Portrait mode freezes, but I never use that anyway...
https://github.com/XEonAX/ANXCamera

us23heep said:
Hello friends!
Sorry my poor english. I am stuck 5 days with this error. Google cant answer. Please can you tell me if what I am doing wrong?
Error always say ... depends on undefined module
Try 1: pastebin.com/33nmpQLU
Try 2: pastebin.com/n3gxTXgY
Try 3: pastebin.com/7Lre4ZiF
Standard manifests:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
local_manifests:
pastebin.com/kt4ES0d4
Thank you :good:
Click to expand...
Click to collapse
It seems like maybe it is not seeing some or all of the device tree files it needs. You may try manually downloading those device files an putting them in the appropriate folders as I mentioned I did in the steps I posted.

I built this yesterday using the instructions above... thanks a lot for those photonmedia!
Some of the instructions were wrong, ie a _ instead of a - in a dir name, but easy fixed.
After that, the entire build completed with 0 errors.
I didnt end up with a ZIP file though, just a approx 400MB "build-lineage_cepheus.ninja" file?

MWPau said:
I built this yesterday using the instructions above... thanks a lot for those photonmedia!
Some of the instructions were wrong, ie a _ instead of a - in a dir name, but easy fixed.
After that, the entire build completed with 0 errors.
I didnt end up with a ZIP file though, just a approx 400MB "build-lineage_cepheus.ninja" file?
Click to expand...
Click to collapse
did you first
Code:
breakfast cepheus
and then
Code:
brunch cepheus
?
the .zip is actually in the
/out/target/product/cepheus/ folder.

I did *exactly* as was instructed above...
Code:
cd ~/android/lineage
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug

MWPau said:
I did *exactly* as was instructed above...
Code:
cd ~/android/lineage
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export USE_CCACHE=1
ccache -M 50G
source build/envsetup.sh
brunch lineage_cepheus-userdebug
Click to expand...
Click to collapse
My understanding is that the breakfast command is not necessary when you are building for unofficial devices and manually populating the necessary device tree files; you skip to the brunch step.
That is per the other guide I referenced in my instructions and how I was able to build this release.
I have not tried to pull and build an updated version as of this time.

k1l said:
the .zip is actually in the
/out/target/product/cepheus/ folder.
Click to expand...
Click to collapse
I missed this at the end of your reply :/
Yup, it's in there. Thanks
Code:
838M -rw-r--r-- 2 root root 838M Feb 25 01:31 lineage-17.1-20200224-UNOFFICIAL-cepheus.zip

photonmedia said:
For what it's worth, I just successfully compiled an updated build today, but it fails to boot after flashing. Had to go back and flash my 2020-01-25 build from the OP.
YMMV
Click to expand...
Click to collapse
Same for me. Have been trying to get it sorted the last few days, i dont know whats going on.
Original OP build works ok.

[OFFICIAL][NETHUNTER][SUZURAN][LOS-NOUGAT]

##I DO NOT ACCEPT FOR BRICKED DEVICES, AND ILLEGAL WORKS##
!!!USE WITH CAUTION!!!
Device: Sony Xperia Z5 Compact
OS: LineageOS 14.1 / Android 7.1.2
Thanks for helps to: @Joeisgood99
1.Take a full backup or only Boot partition
2.Flash Nethunter zip
3. Reboot
4. Open FDroid Nethunter, Upgrade Nethunter apps
5. Open Nethunter app, give permissions
6. Open Nethunter Terminal, give permissions and: apt-get update
7. Open Nethunter app,Navigate to Chroot (metapackages) manager, select Nethunter and press install/upgrade
Unofficial Download Link: https://drive.google.com/file/d/1iFDtMelkcDjOgiNnS90GsHdaWTmeap6l/view
EDIT: Dear @Re4son built OFFICIAL NETHUNTER for Suzuran . It includes; patched wlan0 firmware, HID support and many RTL wlan1 drivers
INSTRUCTIONS FOR BUILD YOURSELF OFFICIALLY (RECOMMENDED):
1- clone this https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project
Code:
git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project
2-
Code:
cd nethunter-installer
3-
Code:
./bootstrap.sh
4- press Y to download devices list.
5-
Code:
python build.py -d suzuran --nougat --rootfs full
(if you prefer lower storage usage, then change rootfs full to rootfs minimal.)
(press Y to download latest rootfs chroot.)
(This will create about 1,2GB of flashable ZIP file and after flash this, it will take 10 GB of internal storage)
6- connect your Z5 Compact to your PC and move zip to your internal storage.
(if you arent have PC, then flash my UNOFFICIAL zip and start KeX in Kali Nethunter menu (Desktop Enviroment) and run that commands in Nethunter)
(if your PC doesnt know your device, press this commands:
Code:
adb push CreatedNethunterFlashableZip /sdcard
7- after, go to TWRP and press backup your BOOT partition for any bootloop causes.
8- in TWRP, press install and choose created Nethunter Zip then press flash.
9- Reboot device and go to FDroid Nethunter version and upgrade Nethunter to latest apk.
10- go to Nethunter app and grant permissions.
11- press Kali chroot manager and then press Add metapackage. Select Kali-linux-nethunter
12- after install procces, go to KeX menu and press Setup local server and write custom password for Kex VNC login. after write, press n
13- In KeX menu, press start server and wait.
14- go to KeX app and write ip to your local ip ( in Nethunter app, go to Home menu and check wlan0 inet without /24 (example 192.168.1.101))
(if you arent connect wifi, press 127.0.0.1 in ip section.
15- write your preconfigured custom password
16- in front of ip section, press 5901 and hit connect.
INSTRUCTIONS FOR WLAN0 (INTERNAL WIFI) MONITOR MODE AND INJECTIONS TEST
INSTRUCTIONS FOR EASILY SET MONITOR MODE:
1. Download Prepatched Firmware:
nougat/suzuran/nexmon-fw/fw_bcmdhd.bin.nexmon · master · Kali Linux / NetHunter / build-scripts / kali-nethunter-devices · GitLab
Devices https://stats.nethunter.com/ https://nethunter.kali.org/
gitlab.com
(rename to fw_bcmdhd.bin)
2. Go to TWRP, select mount and system.
3. Go to main, file manager.
4. Navigate to /system/etc/firmware/wlan/bcmdhd/
5. Move fw_bcmdhd.bin file to your /sdcard/ (for backup)
6. Move into prepatched firmware
/system/etc/firmware/wlan/bcmdhd/
7. reboot system and done.
PATCH YOURSELF:
PART 1:
IN YOUR PC:
1. git clone https://github.com/seemoo-lab/nexmon.git
2. sudo apt-get install git gawk qpdf adb flex bison
3. sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
4. cd nexmon
5. source setup_env.sh
6. make (enter in terminal, like that up)
7. cd patches/bcm43455/7_45_59_16/nexmon
8. make
9. Generate a backup of your original firmware file: make backup-firmware
Install the patched firmware on your smartphone: make install-firmware (make sure your smartphone is connected to your machine beforehand)
https://github.com/seemoo-lab/nexmon...ster/README.md
PART 2 TEST WLAN0 MONITOR MODE:
IN YOUR PHONE:
1- open your wifi and go terminal app.
2-
Code:
. monstart-nh
3- and lets test monitor and injections:
Code:
airodump-ng wlan0
Code:
aireplay-ng -9 wlan0
4- if monitor mode shows any AP's, injection test says injections works, and some AP's reach %1 or upper, then monitor support works good, enjoy
thanks to @Re4son ..
Source Code: https://github.com/Re4son/android_kernel_sony_msm8994/tree/nethunter-14.1

NV modding
Are you able to modify Modem NV Registers with this kernel (assuming it's custom). Can you give it a try via vi or vim? I would prefer to do the modifications on device and simply update ramfs, if possible let me know.

nice
good job, do you know if encryption is working ?

No wlan 1
Thank you so much for making Nethunter for the Z5 compact.
Im on LOS 14.1 / Android 7.1.2 unoffical-suzuran.
I flash the zip from twrp, Restart and update Kali Chroot.
Everything works, Except kali can not find my wifi adapter.
I use the TP Link TL-WN722N-V1 have tried different otg cables,
But no Luck. "i also turn on usb otg"
I have tried many different wifi adapters, im not shore
what wifi drivers that this kernel suport.
im a newbie, So hope someone could help me make this work.
Thank you and regards from Michael.

@NetRoot bro. How to enable monitor mode?
Monstart-nh?

aggunawan said:
@NetRoot bro. How to enable monitor mode?
Monstart-nh?
Click to expand...
Click to collapse
yes bro
source monstart-nh

@NetRoot whats wrong bro with this?
And what is external wireless card support to the kernel? I use tp-link 722n v-1. Chipset atheros ath9k.

NetRoot said:
yes bro
source monstart-nh
Click to expand...
Click to collapse
What's wrong ?

@NetRoot and no module installed

@aggunawan Oops bro i forget.
You must patch wifi:https://github.com/seemoo-lab/nexmon
Our phone uses BCM43455 .

I added broadcom wifi and bluetooth modules but it isnt correctly installed.

NetRoot said:
@aggunawan Oops bro i forget.
You must patch wifi:https://github.com/seemoo-lab/nexmon
Our phone uses BCM43455 .
Click to expand...
Click to collapse
thanks bro @NetRoot. But I have tried compile nexmon https://github.com/seemoo-lab/nexmon many many time, but i always failure. Please help me to compile step by step? Please bro

aggunawan said:
@NetRoot bro. How to enable monitor mode?
Monstart-nh?
Click to expand...
Click to collapse
aggunawan said:
thanks bro @NetRoot. But I have tried compile nexmon https://github.com/seemoo-lab/nexmon many many time, but i always failure. Please help me to compile step by step? Please bro
Click to expand...
Click to collapse
1. git clone https://github.com/seemoo-lab/nexmon.git
2. sudo apt-get install git gawk qpdf adb flex bison
3. sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
4. cd nexmon
5. source setup_env.sh
6. make (enter in terminal, like that up)
7. cd patches/bcm43455/7_45_59_16/nexmon
8. make
9. Generate a backup of your original firmware file: make backup-firmware
Install the patched firmware on your smartphone: make install-firmware (make sure your smartphone is connected to your machine beforehand)
https://github.com/seemoo-lab/nexmon/blob/master/README.md
4.

NetRoot said:
1. git clone https://github.com/seemoo-lab/nexmon.git
2. sudo apt-get install git gawk qpdf adb flex bison
3. sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
4. cd nexmon
5. source setup_env.sh
6. make (enter in terminal, like that up)
7. cd patches/bcm43455/7_45_59_16/nexmon
8. make
9. Generate a backup of your original firmware file: make backup-firmware
Install the patched firmware on your smartphone: make install-firmware (make sure your smartphone is connected to your machine beforehand)
https://github.com/seemoo-lab/nexmon/blob/master/README.md
4.
Click to expand...
Click to collapse
Have you @NetRoot succesfully compiled it bro ?

@aggunawan yes bro.

NetRoot said:
@aggunawan yes bro.
Click to expand...
Click to collapse
@NetRoot. does it have to compile Android-NDK? How to compile it?

Failure to compile nexmon
Bro @NetRoot

@aggunawan bro use Kali amd (pc) not use compiling procces in nethunter.

NetRoot said:
@aggunawan bro use Kali amd (pc) not use compiling procces in nethunter.
Click to expand...
Click to collapse
Is there another way to compile it bro @NetRoot?
And please make kernel support external wireless adapter bro? Please

aggunawan said:
Is there another way to compile it bro @NetRoot?
And please make kernel support external wireless adapter bro? Please
Click to expand...
Click to collapse
No bro you must patch bcm43455 wifi.
Yeah that kernel already compiled for rtlwifi drivers.
You can see in: /system/etc/firmware/rtlwifi/