[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-92709":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":8,"language":10,"languages":8,"totalLinesOfCode":8,"stars":11,"forks":12,"watchers":13,"openIssues":12,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":14,"stars7d":14,"stars30d":12,"stars90d":14,"forks30d":14,"starsTrendScore":14,"compositeScore":15,"rankGlobal":8,"rankLanguage":8,"license":8,"archived":16,"fork":16,"defaultBranch":17,"hasWiki":16,"hasPages":16,"topics":18,"createdAt":8,"pushedAt":8,"updatedAt":19,"readmeContent":20,"aiSummary":21,"trendingCount":14,"starSnapshotCount":14,"syncStatus":22,"lastSyncTime":23,"discoverSource":24},92709,"pxeboot","vvb2060\u002Fpxeboot","vvb2060",null,"","Java",52,1,51,0,35,false,"master",[],"2026-07-22 04:02:06","# Android PXE Boot Server\n\nAndroid PXE Boot Server is an Android application that integrates ProxyDHCP, TFTP, and HTTP services to provide a temporary PXE environment on a home network.\nIt is intended for recovery and maintenance scenarios, such as booting Windows PE or other rescue environments.\n\n## Overview\n\nThe application is designed for short-lived PXE deployments in a local network where a dedicated boot server is not available.\nA rooted Android device can temporarily act as the network boot endpoint and serve iPXE scripts, bootloaders, and ISO-backed resources required for rescue workflows.\n\nThe app is **not** a full DHCP server. It listens for DHCP traffic and responds with ProxyDHCP information so PXE-capable clients can discover the boot resources exposed by the device.\n\n## Usage\n\n1. Connect the computer to the home gateway by **wired Ethernet**.\n2. Connect the Android device to the **same gateway over Wi-Fi**.\n3. Ensure the computer and the Android device can reach each other directly.\n4. Verify that the gateway does **not** enable AP isolation or DHCP anti-spoofing \u002F DHCP protection features that would block DHCP listening behavior.\n5. Verify that the gateway or firewall does not block the ports used by the app:\n\n| Protocol | Port | Purpose                |\n|----------|------|------------------------|\n| UDP      | 67   | DHCP request listening |\n| UDP      | 69   | TFTP                   |\n| TCP      | 80   | HTTP                   |\n| UDP      | 4011 | ProxyDHCP              |\n\nThe HTTP port is configurable. UDP ports `67` and `69` require [privileged access](https:\u002F\u002Fissuetracker.google.com\u002Fissues\u002F218578943), so the Android device must be rooted.\n\nTo start a boot environment:\n\n1. Prepare a Windows PE ISO in the device storage, or use an ISO hosted on a NAS or on the internet.\n2. Open the app.\n3. Edit the bundled iPXE script as needed.\n4. Start the service.\n\n## Supported Platforms\n\nThe app supports the following PXE client platforms:\n\n- x86_64 BIOS\n- x86_64 UEFI\n- arm64 UEFI\n\nUEFI HTTP Boot does not use ProxyDHCP, so UEFI HTTP Boot provisioning is only available through DHCP.\nIf your firmware provides a manual UEFI HTTP Boot configuration screen, you can still enter the URL of this app's HTTP service manually.\n\n## Secure Boot\n\nThe bundled UEFI boot chain supports Secure Boot with both Microsoft 2011 and Microsoft 2023 certificates.\nHowever, the operating system image or ISO you boot must also be compatible with Secure Boot.\n\nMany custom Windows PE and Linux images do **not** yet support the Microsoft 2023 certificate chain.\nEven if the application-side bootloader works correctly, the final boot image may still fail Secure Boot validation.\n\n## iPXE Script\n\nThe built-in `autoexec.ipxe` script contains three example entries:\n\n1. A Windows PE example intended for ISO booting over HTTP\n2. A more advanced example that chains to another network boot workflow\n3. A Debian installer example enabled by default so the app is usable out of the box\n\nFor Windows PE booting, use the first example, replace the URL with your own ISO location, and remove the comment marker.\nFor more advanced scenarios, use the second example as a starting point and customize the script according to your environment.\n\n## Local Development\n\nThe server implementation is written in plain Java and does not depend on Android APIs.\nThis makes it possible to run the server component on any system with a supported JDK.\n\nExample:\n\n```sh\ngradlew :app:localRun --args=\"--server-ip=192.168.1.2 --http-root=D: --http-port=8080\"\n```\n\nTo stop the local server, type: `stop`\n\n\nLicense\n-------\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n    http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n","这是一款运行在 rooted Android 设备上的轻量级 PXE 启动服务应用，通过集成 ProxyDHCP、TFTP 和 HTTP 服务，在家庭或临时网络中快速搭建网络启动环境。核心功能包括响应 DHCP 请求并提供 ProxyDHCP 引导信息（不替代主 DHCP 服务器）、托管 iPXE 脚本、分发 UEFI\u002FBIOS 兼容的引导镜像（如 Windows PE 或 Debian 安装镜像），并支持 Secure Boot（含 Microsoft 2011\u002F2023 证书）。适用于无专用服务器的救援场景，例如离线系统修复、裸机重装或应急维护，依赖有线以太网+Wi-Fi 混合组网及 Android root 权限。",2,"2026-07-10 02:30:12","CREATED_QUERY"]