Related
When I'm trying to boot the recovery image in fastboot it gives me error:
C:\sdk\platform-tools>fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img
cannot load '/path/to/OuyaCWMrecovery6.0.3.2.img': No error
Fastboot devices sees my device
I have 3 copies of OuyaCWMrecovery6.0.3.2.img around just incase it needed a special place;
1 in the tools with adb and flashboot, 1 in the root of the c drive, and 1 on the desktop.
So can anyone help?
deathknight842 said:
When I'm trying to boot the recovery image in fastboot it gives me error:
C:\sdk\platform-tools>fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img
cannot load '/path/to/OuyaCWMrecovery6.0.3.2.img': No error
Fastboot devices sees my device
I have 3 copies of OuyaCWMrecovery6.0.3.2.img around just incase it needed a special place;
1 in the tools with adb and flashboot, 1 in the root of the c drive, and 1 on the desktop.
So can anyone help?
Click to expand...
Click to collapse
if adb fastboot does list your device, and you have a ouya cwm recovery in your adb/fastboot folder (make sure it's not a bad download)
and run fastboot boot OuyaCWMrecovery6.0.3.2.img
no need for path since it's in the same folder.
GizmoTheGreen said:
if adb fastboot does list your device, and you have a ouya cwm recovery in your adb/fastboot folder (make sure it's not a bad download)
and run fastboot boot OuyaCWMrecovery6.0.3.2.img
no need for path since it's in the same folder.
Click to expand...
Click to collapse
Thanks. that did it.
I did the same but i got an purple screen and I can not read the text because if aligned to the left :S
A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!
I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Any other suggestions..?
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?
that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..
tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7
i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow
LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7
Hi folks.
I'm trying to root my phone (ZE551ML - 2.83Ghz and 4Gb Ram) with method 3 in this thread (Using Ubuntu 14.04.1 with installed ADB 1.0.32 and android-tools-fastboot) but the script Root.sh gives me this error:
./adb.mac: 1: ./adb.mac: Syntax error: ")" unexpected
And the script is not rooting the phone.
Then i tryed to do things manually and observed that after i hit the 'adb reboot bootloader' (so i can flash the files like the script would do) the phone reboots into fastboot mode but the 'adb devices' or 'fastboot devices' didnt show my phone anymore - or anything.
Tried to do the same with phone in recovery mode and got the same result.
Can anyone help me?
Did I miss anything?
Ps. My Bootloader is locked and i have no intention of unlocking it yet.
C-Ph87 said:
Hi folks.
I'm trying to root my phone (ZE551ML - 2.83Ghz and 4Gb Ram) with method 3 in this thread (Using Ubuntu 14.04.1 with installed ADB 1.0.32 and android-tools-fastboot) but the script Root.sh gives me this error:
./adb.mac: 1: ./adb.mac: Syntax error: ")" unexpected
And the script is not rooting the phone.
Then i tryed to do things manually and observed that after i hit the 'adb reboot bootloader' (so i can flash the files like the script would do) the phone reboots into fastboot mode but the 'adb devices' or 'fastboot devices' didnt show my phone anymore - or anything.
Tried to do the same with phone in recovery mode and got the same result.
Can anyone help me?
Did I miss anything?
Ps. My Bootloader is locked and i have no intention of unlocking it yet.
Click to expand...
Click to collapse
Are you using root command prompt on your pc? You need admin privileges on pc.
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Are you using root command prompt on your pc? You need admin privileges on pc.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Yes. Using 'sudo fastboot devices' nothing happens.
C-Ph87 said:
Yes. Using 'sudo fastboot devices' nothing happens.
Click to expand...
Click to collapse
http://www.asus.com/zentalk/thread-76656-1-1.html
geopit said:
http://www.asus.com/zentalk/thread-76656-1-1.html
Click to expand...
Click to collapse
The comands in the Python Script are:
adb reboot bootloader
fastboot flash /system/bin/resize2fs magic
fastboot flash /system/bin/tune2fs busybox
fastboot flash /system/bin/partlink supersu.tgz
fastboot oem start_partitioning
fastboot flash /system/bin/logcat installer
fastboot oem stop_partitioning
The thing is that fastboot doesnt recognize my device after the 'adb reboot bootloader' and the message 'waiting for the device' gets stuck.
If you look into the thread you'll see that the 7th answer (user orlapalm) has the same unsolved issue.
Guess the solution is used somebody elses PC with Windows since there's no way to use Ubuntu on This phone.
Try this:
Code:
#!/bin/bash
adb reboot bootloader
fastboot flash /system/bin/resize2fs magic
fastboot flash /system/bin/tune2fs busybox
fastboot flash /system/bin/partlink supersu.tgz
fastboot oem start_partitioning
fastboot flash /system/bin/logcat installer
fastboot oem stop_partitioning
Save as root.sh and try again.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Try this:
Code:
#!/bin/bash
adb reboot bootloader
fastboot flash /system/bin/resize2fs magic
fastboot flash /system/bin/tune2fs busybox
fastboot flash /system/bin/partlink supersu.tgz
fastboot oem start_partitioning
fastboot flash /system/bin/logcat installer
fastboot oem stop_partitioning
Save as root.sh and try again.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Thanks but will not work.
I know how a script works but seems that Zf2 needs the Fasboot v1.0.32 - Witch i dont find anywhere.
Fastboot v1.0.31 (installed with apt-get install android-tools-fastboot) doesnt recognize the Zenfone 2 on Ubuntu.
Maybe because the USB device is not recognized, what does lsusb say before and after the reboot in bootloader?
Magister54 said:
Maybe because the USB device is not recognized, what does lsusb say before and after the reboot in bootloader?
Click to expand...
Click to collapse
lsusb (before reboot)
Bus 001 Device 004: ID 0b05:5601 ASUSTek Computer, Inc.
lsusb (after reboot)
Bus 001 Device 006: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
Fastboot cmds:
~$ fastboot continue
< waiting for device >
~$ fastboot reboot
< waiting for device >
Ps. After this I saw that device code is different after (0b05:4daf) and before (0b05:5601) reboot so i added the permission for this 'new dvice' in /etc/udev/rules.d/51-android.rules and now fastboot seems to recognize my phone.
Magister54 said:
Maybe because the USB device is not recognized, what does lsusb say before and after the reboot in bootloader?
Click to expand...
Click to collapse
Thank you very much for the tip, man!
Without it i would never solved this situation!
C-Ph87 said:
Thank you very much for the tip, man!
Without it i would never solved this situation!
Click to expand...
Click to collapse
No problem :highfive:
Having a weird issue I've never run into. Used to be on Invitrix rom, returned to stock via latest oreo flashall and wanted to get onto Lineage 15.1. While flashall works, I cannot boot from TWRP. I've attempted on both Windows 10, Ubuntu 18.04 LTS and Ubuntu 18.10 and ensured all drivers are installed. I've tried with and without sudo privilege just in case. I've tried renaming the .img to recovery.img, boot.img, etc.. Yet, I keep getting a simple failed message. Bootloader is still unlocked and I've tried multiple cables including the stock one, USB 2.0 and 3.0 ports on both my desktop and and laptop. Is my phone simply corrupted or am I missing something?
sudo fastboot boot twrp-3.2.3-0-nash.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
41rw4lk said:
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
Click to expand...
Click to collapse
I did. Device shows up like normal. I verified by typing
fastboot devices
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.