Related
OK I have a problem. Till now:
1. Installed drivers
2. Bootloader unlocked
3. ADB enabled. PC authorised.
4. OEM unlocking permitted confirmed.
5. Command fastboot devices shows phone connected in fastboot mode.
EDIT: Solved. Experimented with different drivers on different laptop.
Now trying to send official twrp with command fastboot flash recovery recovery.img and I get error:
sending 'recovery' (18680 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
Can't seem to get a solution to this
Any help?
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
Hi,
i want to install twrp-3.2.3-0-whyred.img recovery on my Xiaomi and later xiaomi.eu_multi_HMNote5Pro_V10.0.1.0.OEICNFH_v10-8.1.
But I always get some errors. I never had this with my mi max 2.
I am afraid to brick this Redmi Note 5. Please help me
Redmi Note 5 Global Version RED (dual camera)
Miui version: miui global 9.6 stable 9.6.4.0 (OEIMIFD)
model name: M1803E7SG
Bootloader Unlocked by http://en.miui.com/unlock/
USB Debugging Enabled
Using latest platform-tools
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\Users\Marija\Desktop\platform-tools> adb kill-server
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
*Numbers* fastboot
PS C:\Users\Marija\Desktop\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
Sending 'recovery' (36324 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: Anti-rollback check failed)
Finished. Total time: 0.906s
cassinni said:
Hi,
i want to install twrp-3.2.3-0-whyred.img recovery on my Xiaomi and later xiaomi.eu_multi_HMNote5Pro_V10.0.1.0.OEICNFH_v10-8.1.
But I always get some errors. I never had this with my mi max 2.
I am afraid to brick this Redmi Note 5. Please help me
Redmi Note 5 Global Version RED (dual camera)
Miui version: miui global 9.6 stable 9.6.4.0 (OEIMIFD)
model name: M1803E7SG
Bootloader Unlocked by http://en.miui.com/unlock/
USB Debugging Enabled
Using latest platform-tools
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\Users\Marija\Desktop\platform-tools> adb kill-server
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
*Numbers* fastboot
PS C:\Users\Marija\Desktop\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
Sending 'recovery' (36324 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: Anti-rollback check failed)
Finished. Total time: 0.906s
Click to expand...
Click to collapse
First, copy the twrp image onto internal storage. After you connect it in the fastboot mode, boot into twrp (fastboot boot twrp-3.2.3-0-whyred.img), then after you booted into twrp, flash the twrp image within twrp.
attitude12 said:
First, copy the twrp image onto internal storage. After you connect it in the fastboot mode, boot into twrp (fastboot boot twrp-3.2.3-0-whyred.img), then after you booted into twrp, flash the twrp image within twrp.
Click to expand...
Click to collapse
I copied the same twrp.img into internal storage that is in platforms-tools folder and fastboot devices is showing the phone number and i get this:
...\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
< waiting for any device >
Different attept: platform-tools> fastboot boot twrp.img
Downloading 'boot.img' FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.024s
cassinni said:
I copied the same twrp.img into internal storage that is in platforms-tools folder and fastboot devices is showing the phone number and i get this:
...\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
< waiting for any device >
Different attept: platform-tools> fastboot boot twrp.img
Downloading 'boot.img' FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.024s
Click to expand...
Click to collapse
Are you sure ur doing everything right?
Is usb debugging on?
Stock twrp is a hustle to install you need to unlock the fastboot using dummy.img and use lazy flasher...
Just use redwolf recovery find it and
Fastboot boot redwolf.img
Install redwolf.img as recovery
Reboot to recovery
Enable USB Debugging (security settings) and then try
fastboot boot twrp.img
Then once again flash twrp.img within twrp recovery
t0per666 said:
Stock twrp is a hustle to install you need to unlock the fastboot using dummy.img and use lazy flasher...
Just use redwolf recovery find it and
Fastboot boot redwolf.img
Install redwolf.img as recovery
Reboot to recovery
Click to expand...
Click to collapse
There is no redwolf for this modell
SunilSuni said:
Enable USB Debugging (security settings) and then try
fastboot boot twrp.img
Then once again flash twrp.img within twrp recovery
Click to expand...
Click to collapse
USB Debugging is enabled under developer mode
\platform-tools> fastboot flash recovery twrp.img
< waiting for any device >
cassinni said:
There is no redwolf for this modell
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...t/recovery-red-wolf-recovery-project-t3766997
Next time use search function sir
Doesn't work even with redwolf. Adb is installed, twrp.img is in root storage of phone and in adb folder. usb debugging enabled, phone unlocked by xiaomi (during booting and in settings it says unlocked). tried usb 2 and 3.0 ports on pc. windows 10 x64.
PS C:\Users\marija\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\marija\Desktop\platform-tools> fastboot flash recovery twrp.img
sending 'recovery' (37592 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: -0.000s
cassinni said:
Doesn't work even with redwolf. Adb is installed, twrp.img is in root storage of phone and in adb folder. usb debugging enabled, phone unlocked by xiaomi (during booting and in settings it says unlocked). tried usb 2 and 3.0 ports on pc. windows 10 x64.
PS C:\Users\marija\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\marija\Desktop\platform-tools> fastboot flash recovery twrp.img
sending 'recovery' (37592 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Waiting for device means you haven't installed required Xiaomi drivers in your PC, install drivers and then try
There are two types of USB DEBUGGING in Xiaomi phones
USB DEBUGGING
USB DEBUGGING (Security settings)
You have to enable these two options
If you still face problem maybe you can try different PC/Laptop
SunilSuni said:
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Waiting for device means you haven't installed required Xiaomi drivers in your PC, install drivers and then try
There are two types of USB DEBUGGING in Xiaomi phones
USB DEBUGGING
USB DEBUGGING (Security settings)
You have to enable these two options
If you still face problem maybe you can try different PC/Laptop
Click to expand...
Click to collapse
Both USB Debugging are enabled. Also the right drivers are installed. I have done this several times for other Xiaomi
devices, but this Redmi Note 5 Global Version (Dual Cameras) Red is crazy.
Maybe this cannot work because this is not Global Rom. It is Global Version and there is no twrp that supports Version.
I want to install twrp so i can flash xiaomi.eu 10 on it. Everything is stock on the phone and it does not work.
Sometimes it finds the phone and says file size too large and wont flash, or it gets stuck while flashing for 30mins and nothing happens or i get this error i just posted. I dont want to downgrade firmware, i want to update from 9 to 10.
I tried now on the laptop and it shows the device but it will not work.
PS C:\adb> adb kill-server
PS C:\adb> adb start-server
* daemon not running; starting now at tcp:5027
* daemon started successfully
PS C:\adb> adb devices
List of devices attached
60dbr4g2 device
PS C:\adb> fastboot boot twrp.img
< waiting for any device >
SunilSuni said:
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Click to expand...
Click to collapse
The antirollback was the issue. Now I am in TWRP. Do i have to wipe something? Please give exact command lines and where I enter them.
I flash twrp successfully. Then i went to wipe Dalvik, Cache, Data, System, Vendor.
Then Installed xiaomi.eu_multi_HMNote5Pro_8.8.30_v10-8.1.zip. At the end of install it had an error
for Vendor. E2001 Failed to update vendor image. Updater process ended with error 7.
I rebooted and now everytime i reboot it takes me to Fastboot screen?
Please help
cassinni said:
I flash twrp successfully. Then i went to wipe Dalvik, Cache, Data, System, Vendor.
Then Installed xiaomi.eu_multi_HMNote5Pro_8.8.30_v10-8.1.zip. At the end of install it had an error
for Vendor. E2001 Failed to update vendor image. Updater process ended with error 7.
I rebooted and now everytime i reboot it takes me to Fastboot screen?
Please help
Click to expand...
Click to collapse
Once again fastboot boot twrp.img and flash twrp
You have to avoid erasing vendor partition just system data cache dalvik cache is enough
I was in fastboot and used in adb fastboot boot twrp.img, then i got to twrp.
Now I should reflash twrp-3.2.3-0-whyred.img as recovery or vendor image?
I did already as recovery and then wiped data, cache, delvik and system as you said
then installed xiaomi.eu rom but i got the same vendor error.
Hello.
The problem is arb4 in this version of miui
follow the order of operations marked here:
https://androidfilebox.com/tips/root-redmi-note-5/
just add between step 10 and step 11 the unlocking of the arb4 ; this is possible with "toolkit flasher" that you find there:
http://en.miui.com/forum.php?mod=viewthread&tid=3282063&extra=page=3&mobile=2 (4 flash unlock anti roll back)
everyone tells me something different
the phone is not on miui 10. it was on stock stable miui 9. the flashing of 10 failed. The bootloader is already unlocked by xiaomi.
I believe my problems come from wiping vendor before i tried to flash miui 10 in twrp. I wasnt trying to downgrade (roll back), so arb4 should be irrelevant.
cassinni said:
everyone tells me something different
Click to expand...
Click to collapse
do as you like.
I rooted yesterday my note 5 (same model) which also turns on 9.6.4.0.
I did everything on https://wiki.lineageos.org/devices/ginkgo/install , I flashed the recovery, on the Prompt I get "okay" to both Sending and Writing, and on "Now reboot into recovery to verify the installation" my phone is still on fastboot, so I press for a long time the power button to (force?) shut down it, use volume_up+power and what I see is the "Redmi-Recovery 3.0" (stock recovery).
Is it possible to have 2 recovery and I simply don't know how to access the LOS one? Maybe I could have more luck installing TWRP and overwriting it with LOS recovery (how to?)?
From fastboot if I write "fastboot reboot recovery" right after "fastboot flash recovery ..." prompt says "Rebooting into recovery...okay" but then the normal OS is loaded.
If I use
Code:
adb reboot bootloader
I access to the stock fastboot, and from there
Code:
fastboot boot recoveryimagename.img
says
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
. If I use it from MIUI-OS:
Code:
< waiting for any device >
and Prompt is waiting there.
I have fastboot and recovery image in the same folder but with
Code:
fastboot flash recovery *recovery*
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
, infact I used full path (full of the img file, not the adb/fastboot which I properly installed) instead of relative, giving the "okay", and after that with
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
!
Only now I've seen I was writing from root Prompt and therefore from "C:\WINDOWS\system32>", I used "cd platform-tools_path" and (after
Code:
fastboot flash recovery lineage-17.1-20201228-recovery-ginkgo.img
)
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
worked, but now the phone is stuck here!! From prompt everything seems ok. The phone is stuck on the normal loading boot after that "fastboot boot..."! Before I even tried installing TWRP...maybe that was too much? Now?
I used again "fastboot boot lineage-17.1-20201228-recovery-ginkgo.img" and it seems to working...maybe in a couple of minutes(hours probably) I'll mark this as solved!
Ok, I think everything is good now, but I have a question: is it possible to have more than one recovery installed?
BEDBOI2 said:
is it possible to have more than one recovery installed?
Click to expand...
Click to collapse
it is possible on other devices, but until now not possible on ginkgo
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.