Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

139 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. aaand that was one of the parts I was missing. Thank you. @claude0001 ah. To be fair I didn't see the adb push thing. But the first way doesn't work [quote]Connect the UBports device and the PC with a USB cable. Then copy the file using your file-manager.[/quote] because the device isn't recognized - I think I described that before.
  2. @mibry I don't understand how to apply that fix. I can't edit those files from a terminal on the device, I can't ssh into Ubuntu Touch when it is running because no ssh service is running, I can't just copy files via USB because the device isn't recognized correctly and when I boot into recovery and connect via adb shell after mounting the filesystem, I can see all the files in /system_root but I can't execute vim.tiny to change anything. Oh and I can't set up a SSH server in Ubuntu Touch because I would have to copy my public key over aaand as I said I can't copy any files.
  3. uhm, could you post that fix? Because I couldn't find anything (useful) when I searched for that error.
  4. @mibry I can install a Ubuntu Xenial Xerus container, however I can't install any packages. During the installation the log spits out a bunch of mknod: fb0-: Permission denied makedev fb0 c29 0 root video 0660: failed messages and then ends with rm: cannot remove /dev/sde16: Permission denied and a general error that the installation process failed. Also see my previous post as I found two more issues.
  5. Surprisingly, this worked. Thank you! I first flashed the original image as described here -> And then I installed uboot-installer 0.54-beta by cloning the repository and checking out this branch here and then running npm install npm start The first attempt failed as the Pro1 wouldn't boot into recovery mode, but after restarting the phone, exiting the installer, going back to the boot menu and restarting the installer it worked. It just took a long time before I got into the start menu. @Raksura pinging you here as you had a detailed list of what worked and what d
  6. I tried flashing stable at first and now edge, both with the same result of the phone not booting. If anyone has any experience with Ubuntu Touch and is able and willing to help, this is what I can see in the /cache/ubuntu_updater.log file after waiting for 10 minutes for the device to start and then rebooting it into recovery mode: A/B slot system detected! Slot suffix is _b Formating: system system partition: /dev/block/bootdevice/by-name/system-b umount /system_root: Invalid argument mke2fs 1.43.3 /04-Sep-2016) Discarding device blocks: 4096/786432????????????????????????????
  7. I noticed something on the screenshot I took - from which I posted the small snippet above - which is the small selection box at the bottom of the installer screen. In there it lists all available images, including the FxTec Pro / Pro-X image (as feared they seem to have consolidated the two, which could mean that going forward only the Pro-X will be supported). After selecting the entry from that list I was able to install Ubuntu Touch on the Pro1. *edit* It doesn't boot. I can still get into the recovery mode and the boot manager but I can't start Ubuntu Touch.
  8. How though? FxTec's effort is focused on the Pro1-X. Not the Pro1. Also this guy says that the port was done by FxTec, not by the Ubuntu Touch community.
  9. @claude0001 let's talk about this here in the appropirate thread. The screenshot/snippet I posted was from the ubports-installer and it clearly shows that installation is not possible/supported. The installation method detailed in this thread is sketchy at best. It requires TWRP when TWRP isn't available for the Pro1 as detailed by this thread ->
  10. Let's talk about that in the Ubuntu Touch thread. I pinged you there.
  11. *edit* this post was previously posted over here -> What does this mean for Ubuntu Touch on the original Pro1? As of now it isn't possible to install it and the Pro1 shows up as not supported. I've seen some people having managed to install it, I'm guessing those were Ubuntu Touch developers.
  12. Hey that's fine πŸ™‚ I didn't know you were (again πŸ˜‰ ) the only one to work on it. As for /e/ - I find it unfair of you to call it a 'rip-off'. For one you can't "rip-off" an open-source project [unless you talk about violating the license covering it]. You fork it. Which is what /e/ is. A fork. With a lot of stuff that, a few years ago, were in LineageOS/CyanogenMod. All of which was removed from LineageOS over time. Default, built-in root? Removed. Ability to fake or obfuscate geolocation? Removed. On top of all of that, /e/ is an actual no-google-spy stuff distribution.
  13. Hey, hope you had a couple nice days and a happy new year πŸ˜‰ I need it to be able to flash /e/ as it seems. When I try to flash from a LineageOS recovery iso I get a weird error. Apparently that doesn't happen with TWRP.
  14. Is there any update on TWRP? What is needed for it to work on the pro1? I kinda need it apparently.
  15. huh, my last information was that TWRP didn't work with the Pro1 due to A/B stuff and encryption? I'll look into this, thank you! @Jeremiah Cornelius I wasn't using TWRP initially. I was using the LineageOS ROM.
  • Create New...

Important Information