nyuuzyou/wikis huggingface dataset:
Motorola Moto Z2 Force (motorola-nash)

== Contributors ==
* Fengjiongmax
== Maintainer(s) ==
== Users owning this device ==
== Unlocking Bootloader ==
== How to enter flash mode ==
* Hold down and button.
== Installation ==
installing pmos on device system_a makes pmos unable to find boot partition,but install pmos on sdcard works.
* make sure the bootloader on your device is unlocked.
* pmbootstrap init and select motorola-nash
* pmbootstrap install --sdcard=[your sdcard device]
* boot your device into fastboot and plug in the usb cable(use a usb 2.0 port on your pc if possible).
* this device has two os slots,so you can use one of them to install pmos,the other one to run android.
let's say I'm going to install pmos on slot a:
pmbootstrap chroot -- fastboot --set-active=a #replace a with b if you want to boot pmos from slot b.
# now if you want to boot into pmos without a pc, run this:
pmbootstrap flasher flash_kernel --partition='boot_a' # replace boot_a with boot_b if you want to boot pmos from slot b.
pmbootstrap chroot -- fastboot continue
# or if you don't want to write anything to the device:
pmbootstrap flasher boot
== Note ==
* this device cannot install twrp directly into the device,but able to boot into it without installing,so if you want to see what's wrong with the kernel,you can boot the device into fastboot after a failed pmos boot,and then run
fastboot boot [you twrp.img location]
and then
adb pull /sys/fs/pstore/console-ramoops-0
and check what went wrong,some kernels may not generate such file.A vibration after issued a boot command is a good indication of whether a kernel works.
* I tried to install pmos into 'system_a',and then boot with a kernel flashed into 'boot_a',but initfs seems can not find boot partition.And if I specify boot partition in the cmdline (pmos_boot=/dev/block/sde17) , initfs-extra can't be found.
== See also ==
Motorola RAZR i (XT890) (motorola-smi)

== Contributors ==
* Julianwi
== Users owning this device ==
== How to enter flash mode ==
* Hold + buttons
* Release button as soon as device vibrates
== Installation ==
* Bootloader must be unlocked
* Bootloader from Android 4.0 firmware doesn't support standard bootimg format. Bootloader from Android 4.1 firmware or later should work
* Installation with pmbootstrap flasher should work.
== Notes ==
GPU acceleration with the PowerVR SGX540 is not available, but the software based pixman renderer works quite well on the device's x86 CPU.
What works:
* booting pmOS with phosh
* installing applications
* browsing the web
* display brightness adjustment
* charging over USB
What doesn't
* CPU-freq / CPU-idle / Powemanagement
** Device runs in full power mode and drains battery quickly
== Mainline ==
The internal peripherals of the Intel Medfield SoC can be discovered by PCI and mostly already work with the mainline kernel drivers.
Intel MID devices where designed to boot using Intel's "Simple Firmware Interface" (SFI). The mainline implementation of SFI was quite messy and has recently been dropped in newer releases. Therefore, the second stage bootloader Petitboot is used to boot newer kernels with kexec and devicetree.
Mainline fork
== See also ==
* Initial merge request (motorola-smi)
* 
* 
* Intel MID
Mrtest

mrtest helps with testing merge requests from both pmaports, as well as Alpine's aports. It automatizes downloading the packages that were built in CI and offers a convenient, interactive prompt to install them. 
It's meant to be run on your postmarketOS device (ie. your phone).
For usage details, please check the official documentation: https://docs.postmarketos.org/mrhlpr/usage.html#mrtest
== See also ==
* : initial merge request
* postmarketOS podcast #16 where the tool gets introduced and discussed
* Source code
Multilaser M7s Quad Core (multilaser-astar-ococci)

== Contributors ==
* Riomccloud
== Users owning this device ==
== How to enter flash mode ==
# With the tablet turned off, hold the button
# While holding it, connect the USB cable and press the button five times
# Release both buttons
== Installation ==
For this initial testing phase, follow the Installation guide and select a device with the same SoC, like INet Tek D70 A33. Install it to the SD card, since internal storage seems to be not recognized for now.
== Features ==
=== WiFi ===
Its wireless network capabilities aren't included in the SoC. It seems to use an Espressif ESP8089 chip - there is a driver being maintained here, but I haven't managed to build it yet.
== See also ==
NEC Terrain (nec-terrain)

== Contributors ==
* Maxnet
== Maintainer(s) ==
== Users owning this device ==
== How to enter flash mode ==
== Installation ==
== See also ==
* GSM Arena's NEC Terrain page - information about the device including hardware specs
* alex-kas's NEC Terrain repo - information about gaining the ability to flash the device, including utilities
* x29a's Android app - automates some of the steps described by alex-kas and includes some links with background information
* Spec Device's NEC Terrain page - based on data collected from the device, includes some WiFi and OpenGL details
NGM WeMove Action (ngn-wemove-action)

== Contributors ==
* drebrez
== What works ==
* Kernel compilation
* Flash Kernel (pmbootstrap flasher flash_kernel)
* Flash Rootfs (pmbootstrap flasher flash_rootfs)
* Framebuffer graphics (Splash screens)
* SSH Connectivity
* Weston on framebuffer
* Initramfs boot
== Device info ==
* Full phone specifications
== Additional info ==
=== Entering "Bootloader mode?" ===
Hold the Volume Down button, and then press the Power button
=== Entering "Recovery mode" ===
Hold the Volume Up button, and then press the Power button
=== Partition layout ===
dev: size erasesize name
mtd0: 00080000 00040000 "preloader"
mtd1: 00180000 00040000 "dsp_bl"
mtd2: 00300000 00040000 "nvram"
mtd3: 00040000 00040000 "seccnfg"
mtd4: 00080000 00040000 "uboot"
mtd5: 00a00000 00040000 "boot"
mtd6: 00600000 00040000 "recovery"
mtd7: 00140000 00040000 "secstatic"
mtd8: 00080000 00040000 "misc"
mtd9: 00300000 00040000 "logo"
mtd10: 000c0000 00040000 "expdb"
mtd11: 00400000 00040000 "gionee"
mtd12: 0eb00000 00040000 "system"
mtd13: 03c00000 00040000 "cache"
mtd14: 0a540000 00040000 "userdata"
=== Leds ===
/sys/devices/platform/leds-mt65xx/leds/green
/sys/devices/platform/leds-mt65xx/leds/red
/sys/devices/platform/leds-mt65xx/leds/blue
== Useful links ==
MT657x flashing tutorial
NVIDIA Tegra Note 7 (nvidia-tegratab)

== OEM Variants ==
* HP Slate 7 Extreme (hp-olive)
* ZOTAC Tegra Note 7
* EVGA Tegra Note 7　...and more info 
== Contributors ==
* coffeebeat
== Maintainer(s) ==
== Users owning this device ==
== How to enter flash mode ==
Hold + , enter to fastboot protocol
== Memo ==
Using GCC6, 
Mostly flashing method doesn't work, but pmbootstrap install --sdcard is OK,
boot topmbootstrap flasher boot
I'm not recommended flasher flash_kernel, because you can't charging battery!
tegranote7c is LTE version(Probably). Don't get confused.
== osk-sdl ==
# osk-sdl -d a -n a -c /etc/osk.conf -v
INFO: /home/buildozer/aports/community/sdl2/src/SDL2-2.0.12/src/video/directfb/SDL_DirectFB_video.c (239):A general initialization error occured
Segmentation fault
== wifi ==
fix to firmware path
$ sudo mkdir -p system/etc
$ cd system/etc
$ sudo ln -s /lib/firmware/ti-connectivity firmware
wl12xx: loaded
but it's not work
$ ip set wlan0 up
wl12xx: WARNING unsupported chip id: 0x0
SDIO Vendor ID:0097 and SDIO Device ID: 4076
wl12xx: WARNING unsupported chip id: 0x0
SDIO Vendor ID:0097 and SDIO Device ID: 4076
wl12xx: WARNING unsupported chip id: 0x0
wl12xx: ERROR firmware boot failed despite 3 retries
== Mainline (Grate) ==
Mainline kernel contains tegra114-tn7.dts.
It's partial worked linux-postmarketos-grate(5.11.0_rc4), but have some problems.
I'm not recommended to test this (Maybe killed sdcard slot).
=== Hardware status (mainline) ===
 	Status	info
Booting 	Y 	
Xwayland 	Y 	confirmed startup demos
USB Telnet 	N 	
Wifi, Bluetooth	 	wl1271, in mainline
Touchscreen 	 	maxim_sti, not in mainline
Battery gauge 	 	max17048, in mainline(max17040)
== See also ==
* Using Kernel
* Using Config
* If you want tested, use this
Navon iQ7 2018

== Contributors ==
* martonmiklos
* StandaSK
== Users owning this device ==
== How to enter recovery mode ==
* Hold and button
* When you see the Navon logo, release the button
* Keep holding until you get to recovery
== Installation ==
== Components ==
Component 	Model
Motherboard 	AL-A64-86VH-V1.0
SoC 	Allwinner A64
PMU 	X-Powers AXP803
Wi-Fi 	Realtek RTL8703BS
Bluetooth 	Realtek RTL8703BS
Rear camera 	GalaxyCore GC2145
Front camera 	GalaxyCore GC0312
Touchscreen controller	Silead GSL1680
Touchscreen digitizer 	DR7-M7S-XC XC-PG0700-108B-A1
== Partition layout ==
iQ7_2018:/ $ cat /proc/partitions
major minor #blocks name
 253 0 262144 zram0
 93 0 32768 nanda
 93 16 16384 nandb
 93 32 32768 nandc
 93 48 1572864 nandd
 93 64 196608 nande
 93 80 16384 nandf
 93 96 32768 nandg
 93 112 524288 nandh
 93 128 16384 nandi
 93 144 16384 nandj
 93 160 512 nandk
 93 176 15872 nandl
 93 192 81920 nandm
 93 208 16384 nandn
 93 224 5046272 nando
 254 0 1572864 dm-0
iQ7_2018:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 501948 468 501480 1% /dev
tmpfs 501948 0 501948 0% /mnt
tmpfs 501948 0 501948 0% /sensors_cache
/dev/block/dm-0 1523568 1133152 374032 76% /system
/dev/block/by-name/cache 507848 532 496832 1% /cache
/dev/block/by-name/alog 76528 44 74848 1% /logger
/dev/block/by-name/UDISK 4888112 2666192 2205536 55% /data
/dev/block/by-name/bootloader 130798 5956 124842 5% /bootloader
/dev/fuse 4888112 2666192 2205536 55% /storage/emulated
== Photos ==
File:Navon_iQ7_2018_recovery.jpg|thumb|left|Navon iQ7 2018 in recovery mode
== See Also ==
* Navon iQ7 2018 at linux-sunxi.org
Netgear PTV3000 (netgear-ptv300)

==Architecture==
It is unknown for the soc's architecture is whatever is armhf or armv6(unsupported by pmos). some soc that use ARM1176JZF has hard float support some dont.
== Contributors ==
* exkc
== Users owning this device ==
== How to enter flash mode ==
== Enable USB Debugging ==
== Installation ==
== Notes ==
== Related pages ==
DIAL
== See also ==
wikidevi
exploitee.rs(uart pinout)
NetworkManager/DHCP

Here's a list of the DHCP Clients integrated in NetworkManager and the problems that have been discovered with them.
Currently the default is dhcpcd.
== Internal ==
Devices not able to connect to WiFi (with old vendor kernels) ( and )
Change /etc/NetworkManager/NetworkManager.conf to contain dhcp=dhclient and sudo apk add dhclient
== dhcpcd ==
Device is flooded with IPv6-related messages ( - NetworkManager issue: NetworkManager#5)
== dhclient ==
-
== dnsmasq ==
Dnsmasq needs to be compiled with Dbus support in order to function. Comment the line dns=dnsmasq in /etc/NetworkManager/conf.d/dns.conf.
( - dnsmasq: add package with dbus support: dnsmasq)
= See also =
* Change default NetworkManager DHCP client to dhcpcd
NetworkManager/DNS

NetworkManager implements several dns clients.
== default ==
The default method adds the DNS servers from the network connections. It gives a warning that "the libc resolver may not support more than 3 nameservers".
This can have issues with some applications (such as aerc or senpai) as the top 3 DNS servers may be inaccessible over your WiFi network.
(for example T-Mobile adds 4 DNS Servers which are only accessible on their network: https://rudism.com/solving-openvpn-dns-issues-on-android-clients/)
== dnsmasq ==
Setting
dns=dnsmasq
in NetworkManager.conf by default will have issues, as NetworkManager will overwrite the /etc/resolv.conf which dnsmasq needs by default.
edit /etc/dnsmasq.conf
resolv-file=/var/run/NetworkManager/no-stub-resolv.conf
and add it to the default runlevel so openrc will autostart it.
issue: if dnsmasq crashes, network related things will totally fail to work.
With the above configuration, it's always crashing on boot... almost-certainly because /var/run/NetworkManager/no-stub-resolv.conf doesn't exist yet. To work around this, edit /etc/init.d/dnsmasq and add
supervisor=supervise-daemon
respawn_delay=2
# respawn_max defaults to 10, so this effectively gives NetworkManager 20 seconds to create the file
You may want to add
strict-order
to your dnsmasq config, so that it tries every server, rather than just whichever one it wants. (This can be helpful if your carrier's servers don't resolve on non-carrier servers.
== static ==
To prevent adding DNS servers by NetworkManager (for example, if you prefer do not use ISP's nameservers), add to /etc/NetworkManager/NetworkManager.conf
[main]
dns=none
and add preferred DNS servers to /etc/resolv.conf, for example
nameserver 127.0.0.1
== Manually set dns servers ==
First, list the connections:
$ nmcli con
In the NAME column, find the name of the connection for which you want to set the dns servers.
You can set the ipv4 and ipv6 dns servers with the following command:
$ nmcli con mod $conNAME ipv4.dns "8.8.8.8 8.8.4.4" # set ipv4 to google's dns servers
$ nmcli con mod $conNAME ipv4.ignore-auto-dns yes # ignore the ipv4 dns provided by the network
$ nmcli con mod $conNAME ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844" # set ipv6 to google's dns servers
$ nmcli con mod $conNAME ipv6.ignore-auto-dns yes # ignore the ipv6 dns provided by the network
# /etc/init.d/networkmanager restart # apply new dns settings
Next Thing Co. CHIP (ntc-chip)

== Contributors ==
* Symmetrist
== Maintainer(s) ==
* Symmetrist
== Status ==
At the moment it is possible to build a pmOS image using the commands explained below.
However to boot this image we need to change u-boot configuration, and unfortunately
the procedure explained below does not work on all the version of u-boot for CHIP around.
The next step is to package and compile u-boot to provide a uniform bootloader for pmOS.
== Users owning this device ==
== How to enter flash mode ==
The CHIP has two different flashing modes:
* FEL mode: used to flash bootloader and rootfs
* Fastboot mode: used to flash rootfs
To enter FEL mode:
* Connect the FEL and GND pins with a jumper cable
* Power on the CHIP
To enter Fastboot mode:
* Connect an serial (UART) USB adapter to UART1-TX, UART1-RX and GND
* Power on the CHIP
* Press enter during boot up to access the U-Boot console
* On the console type fastboot 0
== Configure U-Boot ==
PostmarketOS loads an initramfs together with the kernel, while original Debian installation only used the kernel.
To boot PostmarketOS we need to change the U-Boot configuration to support the initramfs.
From the U-boot serial console issue the following commands:
* Print the current value of the bootcmd, save it in case you want to restore it later.
> printenv bootcmd
* Change the bootcmd value
> printenv bootcmd
> setenv bootcmd "gpio set PB2; ${bootcmd_fel}; ${boot_initrd};"
> saveenv
== Create the UBIfs image ==
* Configure the installation and build the system
$ pmbootstrap init
$ pmbootstrap install
In workdir/chroot_rootfs_ntc-chip there is the rootfs for your ntc-chip
The following commands needs to be launched from your pmbootstrap workdir
* Copy dtb from linux-ntc-chip
$ sudo cp cache_git/pmaports/device/testing/linux-ntc-chip/sun5i-r8-chip.dtb chroot_rootfs_ntc-chip/boot/
Install mtd-utils from your distro repositories e.g. pacman -S mtd-utils
* Create the UBIfs image
$ mkdir ubi
$ sudo mkfs.ubifs -m 16384 -e 0x1f8000 -c 2000 -r chroot_rootfs_ntc-chip ubi/ubifs.img
$ sudo chown youruser:youruser ubi/ubifs.img
$ ubinize -o ubi/ubi.img -m 16384 -p 2MiB -s 16384 cache_git/pmaports/device/testing/device-ntc-chip/ubinize.cfg
$ img2simg ubi/ubi.img ubi/ubi.img.sparse 2097152
== Flash the UBIfs image ==
* Enter fastboot mode as described above
* On your computer
$ fastboot erase UBI
$ fastboot flash UBI ubi/ubi.img.sparse
$ fastboot reboot
== See also ==
* UBIFS
* Initial merge request
* Sunxi wiki page
* Wikipedia wiki page
* Tool for flashing the CHIP
* CHIP microSD slot mod
* Good U-Boot guide
Nextbit Robin (nextbit-ether)

== Contributors ==
* ashirviskas
== Maintainer(s) ==
* ashirviskas
==Note==
Due to a pipeline error, this device codename become nextbit-robin
== How to enter flash mode ==
Fastboot: Hold down POWER and VOL DOWN. Use volume buttons to navigate to Fastboot and press power.
== Installation ==
(Fastboot)
Fastboot is the only tested method
== See also ==
* Initial pull request
* Display working pull request
* Device package
* Kernel package
Nextbook 8 (nextbook-nxm865fd)

The Nextbook 8 NX785QC8G is an RK3188-based tablet from 2014. The tablet was marketed under the Nextbook USA brand (now defunct), distributed under the E FUN brand, and manufactured by Yifang Digital Technology Co., Ltd.
A few months after launch, Nextbook released an update to Android 4.4 Kit Kat for tablet owners. At the same time, Nextbook released new tablet models which came with this update pre-installed. These new tablet models also came in new color varieties and more importantly were based on the slightly slower RK3188-T chipset. These new models are labelled as NX785QC8G-R.
Further confusing matters, over the years Yifang released several tablets, including some x86 Atom-based hardware, under names very similar to "Nextbook 8": the Nextbook Ares 8, Nextboot Ares 8L, Nextbook Ares 8A, Nextbook Premium 8HD, Nextbook Premium 8SE, Nextbook Flexx 8, and Nextbook 8 Windows 8.1.
Yifang Digital is also known to have sold the same tablet hardware under various regional brands: Intenso in Western Europe, Prestigio in Russia and Eastern Europe, Master-G in South America, etc. If other brands of the same tablet are discovered please document those on this page.
== Contributors ==
== Users owning this device ==
== How to enter flash mode ==
== Installation ==
== Parameter File ==
== Kernel ==
Yifang and associated brands have not released kernel source. However the RK3188 SoC is supported in mainline. There are also various generic RK3188 tablet kernel trees (example).
== Battery Hardware Defect ==
Several hardware owners have reported strange issues with battery reporting on the Nextbook 8 running Android. These issues include sudden shut downs around 15% battery, battery dropping from 100% to around 75%, and delays in powering on the device from an empty battery. The root cause of these issues was identified by ShaunMT of the FreakTab community as a hardware defect in which the cable connecting the battery to the mainboard can very easily become loose or unplugged. In response some users have fit loose material under the battery cable to keep it snug, and at least one user has soldered on longer battery cables to work around the issue.
== See also ==
* Product Detail Page (archived)
* Android 4.4 Kit Kat Release Announcement (archived)
* Stock Android 4.4.2 Update RKFW Image (sha1sum: 31da26cd18be4fe867ceef201cb9eea5bd0f2dea)
Nftables

nftables is a newer replacement for iptables, ip6tables, arptables and ebtables. It has a serialisation format for defining rules and it supports using the same rulefile for IPv4 and IPv6.
The first kernel with nftables support is 3.13
== Installing ==
The kernel on the device needs to have the kconfig options enabled for nftables, the main options for this are CONFIG_NF_TABLES and CONFIG_NF_TABLES_INET.
The userspace part is in the Alpine package nftables which provides the nftables openrc service and the nft command to do runtime changes.
# apk add nftables
# rc-update add nftables
# service nftables list
table inet filter {
 chain input {
...
The default configuration when adding the nftables package and enabling the service will drop all incoming connections and blocks no outbound connections. It will also ratelimit incoming icmp packets. This config is stored in /etc/nftables.nft and will include any ruleset files that are put in
/etc/nftables.d/*.nft. This is a good place to put your own extra rules.
== Allowing SSH ==
Since the default ruleset drops all incoming connections you will no longer be able to SSH into the device after starting the nftables service. To allow connections again you can create an extra ruleset that allows connections over USB networking and over wifi:
table inet filter {
 chain input {
 type filter hook input priority 0; policy drop;
 iifname usb0 accept \
 comment "Accept all traffic from USB ethernet"
 iifname "wlan*" tcp dport {ssh} accept \
 comment "Accept SSH over wifi"
 }
}
These rules will be amended to the default ruleset and allow all connections from usb0, which is the network interface created by the usb networking in postmarketOS. The second added rule will allow incoming SSH connections on any interface starting with wlan.
After creating or changing the rules files you can make them active with the reload command on the nftables service:
# service nftables reload
== How to disable firewall ==
# nft flush ruleset
# rc-service nftables stop
# rc-update del nftables default
== Logs ==
* Install the postmarketos-config-nftables-log package
* Restart the nftables service with sudo rc-service nftables restart
* Logs should be available in the kernel through dmesg
== More information ==
the nftables wiki
Nightly

= Plasma Mobile =
postmarketOS has a nightly repository which contains (semi-) nightly builds of all KDE packages to make it easy to develop Plasma Mobile and it's applications on postmarketOS which are currently build against Qt6. No device images will be made for these for now and it's only available for aarch64 (armv8) devices.
== Upgrading an existing Plasma Mobile installation ==
Make sure your system runs postmarketOS edge.
This repository is not supported on any stable editions.
First, enable the apk key used to sign the packages.
$ wget https://nightly.postmarketos.org/plasma-mobile/pmos@local-66ca51cb.rsa.pub
# mv pmos@local-66ca51cb.rsa.pub /etc/apk/keys/
Then enable the repository and update the system.
# echo "https://nightly.postmarketos.org/plasma-mobile/packages/master/" >> /etc/apk/repositories
# apk update
# apk upgrade -a
== Build a new image ==
Make sure you have selected to install postmarketOS edge in pmbootstrap.
This repository is not supported on any stable editions. 
First, enable the apk key used to build the packages:
$ wget https://nightly.postmarketos.org/plasma-mobile/pmos@local-66ca51cb.rsa.pub
# mv pmos@local-66ca51cb.rsa.pub $(pmbootstrap config work)/config_apk_keys/
Every pmbootstrap command can be run as normal except for install. Add the -mp argument as follows:
$ pmbootstrap -mp "https://nightly.postmarketos.org/plasma-mobile/packages/" -mp "http://mirror.postmarketos.org/postmarketos/" install