so now the phone boots up !!
the problem was the recovery.img I downloaded from http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArT
now I installed trwp an all went fine...
thx for help - have a nice day
so now the phone boots up !!
the problem was the recovery.img I downloaded from http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArT
now I installed trwp an all went fine...
thx for help - have a nice day
@ianus
now I have tested ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img
and after success I had:
adb shell
root@OnePlus5:/ # cd data
root@OnePlus5:/data # ls
android-rootfs.img rootfs.img
and then I reboot phone
check again and /data is emty ??
@ianus thx for reply
my /data is empty ?
michi@Core5M:~/Downloads$ adb shell
root@OnePlus5:/ # ls /data
root@OnePlus5:/ #
regards
@ianus can I also use Helium-recovery instead of twrp ?
thx for reply
@arubislander
yes, right - no problems during installprocess. but phone does not boot to ubuntu touch.
@arubislander no phone does´t boots in Touch hangs on android boot logo
@arubislander thx for reply
right - the bootlogo is probably from android 11 - other question to run "./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img"
I have the recovery.img from "http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArT"
installed is that correct ? - because without recovery adb will not run.
thx
so next problem, after successful installation - my phone is in the 1+ logo powered by android ??
I had originally installed a custom rom with trwp - maybe that's the problem ?
yes thats it - my phone was allways in fastboot-mode - new in recovery-mode all was fine
- THX
yes, fastboot devices is ok, but adb devices doesnot show any device when phone is in fastboot mode
usb debugging is on
phone is unlocked
Hi, I have installed ubuntu touch like in https://pad.ubports.com/p/HaliumHowToTestInstall.
when I Issue ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img - I get:
Chosen rootfs is ubuntu-touch-android9-arm64.tar.gz
Chosen android image is system.img
Chosen release is ut
Compress images before pushing: false
I: Writing rootfs into mountable image
I: Writing android image into mountable image
I: Running post installation tasks
enabling SSH ... [done]
Please enter a new password for the user 'phablet':
Geben Sie ein neues UNIX-Passwort ein:
Geben Sie das neue UNIX-Passwort erneut ein:
passwd: password updated successfully
I: Copying ssh key to the user 'phablet'
I: Shrinking images
e2fsck 1.45.6 (20-Mar-2020)
resize2fs 1.45.6 (20-Mar-2020)
Die Größe des Dateisystems auf .halium-install-imgs.ymhtd/system.img wird auf 118902 (4k) Blöcke geändert.
Start von Durchgang 3 (max = 24)
Die Inode-Tabelle wird gelesenXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Das Dateisystem auf .halium-install-imgs.ymhtd/system.img is nun 118902 (4k) Blöcke lang.
I: Unmounting images
I: Pushing rootfs and android image to /data via ADB
I: Pushing rootfs to /data via ADB
adb: error: failed to get feature set: no devices/emulators found
I: Pushing android image to /data via ADB
adb: error: failed to get feature set: no devices/emulators found
I: Renaming to system-as-root compatible system image
adb: no devices/emulators found
real 0m0,012s
user 0m0,010s
sys 0m0,000s
Error: Couldn't copy the files to the device, is it connected?
I: Cleaning up
umount: .halium-install-rootfs.UI62L: nicht eingehängt.
adb: no devices/emulators found
any hints ?
Michael