Well I got on a bumpy road with this stuff, it seems on one of my 'formattings' things went wrong, and my phone got bricked... the phone always turning back to fastboot menu without any possibility to run recover

So I ended up on my linux box and found a guide to flash TWRP via the computer.
Having set the phone on fastboot menu I followed this guide
https://gist.github.com/edouard-lopez/44d14602e9c30490513b9f5aa12300fb

From the part "Install Recovery"
step 1 to 7
then rebootet into recovery and got this screen.

Then from TWRP I did a wipe and after a format on the 'data'.
I did not realy find a place where I could define the format to be etx4..

I then started the Ubports installer with the phone in fastboot menu and this went OK, even if this "sick android" figure still appeared in a few splash screens...

Thanks to all for the helping with this

Now my phone is running ubuntu touch so the next step is now to figure out how this thing works

Well I got on a bumpy road with this stuff, it seems on one of my 'formattings' things went wrong, and my phone got bricked... the phone always turning back to fastboot menu without any possibility to run recover

So I ended up on my linux box and found a guide to flash TWRP via the computer.
Having set the phone on fastboot menu I followed this guide
https://gist.github.com/edouard-lopez/44d14602e9c30490513b9f5aa12300fb

From the part "Install Recovery"
step 1 to 7
then rebootet into recovery and got this screen.

Then from TWRP I did a wipe and after a format on the 'data'.
I did not realy find a place where I could define the format to be etx4..

I then started the Ubports installer with the phone in fastboot menu and this went OK, even if this "sick android" figure still appeared in a few splash screens...

Thanks to all for the helping with this

Now my phone is running ubuntu touch so the next step is now to figure out how this thing works

I did try formatting to ext2 without succes it is as if the partition does not exist? I am now certain that this is a partition error of some kind though I am able to reinstall the android operating system OK and all is running fine. If I wish to do a system upgrade then installation fails on the reboot part.
Besides I cannot install the system update from a zip file passed to the phone from a computer, also installation error.
I will keep searching for how to get in control of the partitions.

I tried a fastboot getvar all to show all the partitions

C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3955000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x19f00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd68877000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xbc000000
(bootloader) serialno:7d6b67e9
(bootloader) kernel:lk
(bootloader) product:msm8996
(bootloader) oem_project_name:15801
all:
finished. total time: 0.219s

I then see the partition userdata but not "data" which I believe should be there or?

after that I did a "fastboot format:ext4 userdata" it format OK, then afterwards trying with UBPorts installer gets at least some reaction with an error message like this below. I believe it is a partition problem.
Anybody can read something from this?

@Lakotaubp This is also my understanding that there is a partition issue, without beeing and expert

@ernest
Not encrypted and yes did install TWRP but installation from that also fails....

@Lakotaubp
I tried this part with format ext4, see below, but no changes.
Still get the "android warning triangle"

And I believe this error is the root for my troubles

Asger

C:\WINDOWS\system32>fastboot devices
7d6b67e9 fastboot

C:\WINDOWS\system32>fastboot format:ext4 cache && fastboot format:ext4 data
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 435159040 bytes
erasing 'cache'...
OKAY [ 0.000s]
sending 'cache' (6248 KB)...
OKAY [ 0.250s]
writing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.328s
Warning: data type is , but ext4 was requested for formating.
Need size of filesystem
target reported max download size of 435159040 bytes
sending 'data' (0 KB)...
FAILED ()
finished. total time: 0.000s

C:\WINDOWS\system32>

Thanks for the replies, I am not really able to succeed with any of the guides.
The device is though unlocked and when trying to follow the twrp I get stuck in the process also.
I believe the error message from the image in my first post is the key to my problems.
I will try to find a way to completely reset the phone and start from scratch.... If too troubled I will try to find a supported device , ubtouch seems very nice in many apsects.

Hi

I have been trying to install UB tocuh on oneplus 3 phone, with windows 10 model says this:
ONEPLUS A3003_16_181206

Starting the program it finds the device fine and downloading and all that.
Then when the phone is rebooting comes to FASTBOOT menu and starts and..it shows a splash screen very quickly with a android figure with stomac open and a red warning triangle (had to film to find the sequence with the figure)

Then this menu comes
Android Recovery
Use Volume up/down and power

Reboot system Now
Ubuntu Actions
Adroid actions

PC program says sending files and after a while it says connection to device
lost

I have tried different options at the recovery options with out any results, always ending up with the same.
I guess the reason is to be found in the "android error" and why this?

Any help apreciated.

Thank you.

Asger

Note: I am also running linux but have never succeded to connect to the device (Linux Mint 18)