write it in a nicer way and give it a undderstandable structure
- User
write it in a nicer way and give it a undderstandable structure
- Assistant
Absolutely! Here's a clearer and more polished version of your GitHub issue, structured for better readability and understanding:
Title:
🛠️ postmarketOS installation on a3y17lte via TWRP:/systemmount error, fstab creation failed, device stuck on boot
Device: Samsung Galaxy A3 (2017) (
a3y17lte)
Channel:edge
User Interface:plasma-desktop
Installation Method: Recovery installer via TWRP (pmbootstrap install --android-recovery-zip)
🐛 Issues Encountered
After following the standard installation process for postmarketOS on the
a3y17ltedevice using TWRP as the recovery environment, I ran into several issues:1. 🧱 Installation Errors
-
At the end of installation, TWRP shows:
failed to mount /system (device or resource busy) error creating fstabThis happens whether I install to
/systemor/data. -
Files appear to be installed to the partition, but...
2. 🔁 Boot Loop / Stuck Boot
-
On first boot, the following messages appear:
initializing starting postmarketOS...and it hangs on this screen indefinitely.
-
No shell or UI appears afterward.
-
The kernel seems to load properly, as the device is detected in
dmesg.
🧪 Additional Notes & Attempts
Installation Steps Tried:
- ✅
pmbootstrap install --android-recovery-zip - ✅
pmbootstrap flasher --method=adb sideload→ Device restarts after sideload, but no behavioral change. - ✅ Tried installing onto both
systemanddatapartitions
Chroot Error from pmbootstrap:
When using
--android-recovery-zip --recovery-install-partition=data, got this warning:(buildroot_aarch64) chroot not initialized! This is a bug! Please report it.It then proceeds with:
(buildroot_aarch64) initializing the chroot for you... (buildroot_aarch64) create recovery zipTWRP Issues:
- ADB does not work at all in TWRP for this device, making debugging more difficult.
📦 Kernel Question
I found this package:
🔗 linux-samsung-a3y17lte (testing)Question:
Is this kernel package already included in the currentedgebuilds for this device, or should it be manually integrated?—
❓ Questions
- What’s causing the
/systemmount failure and fstab creation error? - Is the boot hang related to the kernel or fstab issue?
- Is the chroot error during recovery zip creation known, and can it be safely ignored?
- Is the kernel linked above part of the current edge image (or should I build it manually)?
- Any known workarounds or fixes for ADB not working in TWRP on this device?
📎 Logs Available Upon Request
I'm happy to provide:
- TWRP logs
pmbootstrapoutputdmesgfrom host when phone is connected
Thank you in advance for your time and work on this amazing project 🙏
Let me know how I can help debug this further!
Let me know if you'd like help submitting this issue on GitLab/GitHub, or generating logs to include.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.