[Android Q&A, Help & Troubleshooting] xdaforumusers:
Solved - I ended up buying a SanDisk 32 GB On-The-Go retractable flash drive (an OTG cable would work too, if you have the ROM saved on a flash drive that you can plug into it). I saved Revolution ROM to the OTG, and then installed it from TWRP, wiped Dalvik, and rebooted. That worked.

Original post:

Current situation: my M7 has no OS.

Initially intended: install Ubuntu Touch (incomplete OS).

Initial backup option: Cyanogenmod.

What I did: Save the 3 Ubuntu Touch .zip files and cm-****-ul.zip to /sdcard/Download.

Install TWRP and MultiRom to phone.

Boot from TWRP to attempt to install Ubuntu Touch, but when that didn't work, attempt to install Cyan instead.

My OS was wiped in the process of all this.

I saw online guides that said to wipe Dalvik after install, so I did that, but I suppose I wiped all data, because there are no more .zip ROMS stored in my phone's data, so I think my hopes rest on somehow flashing the stock ROM.

What I'm now attempting to do:

Either get the stock ROM back, or literally anything to get it working again.

Phone details:

Model: HTC One M7

S-On

OS version: 7.23.502.9

HBoot: 1.61.0000 (so I can't get S-Off without Sunshine)

Tools available to work with:

Ubuntu PC:

I have Android Studio installed.

fastboot devices

shows the device listed, when I've got fastboot up.

But when I use

fastboot flash recovery recovery.img

(having changed Terminal directory to /platform-tools, with recovery.img in this same folder, where fastboot is located), the Terminal just echoes back "waiting for device".

adb devices

does not show the device listed, when I bring up TWRP's ADB sideload feature

When I try to use

adb sideload rom.zip

, Terminal echoes back "error: device not found"

I've tried sideloading both a recovery.imp and RUU.zip (with RUU being the stock ROM for my device)

VirtualBox Windows 7:

I have Android Studio, Eclipse and Java installed.

I installed HTC Sync to get the HTC drivers (which doesn't actually recognize the device, probably because there's no OS), but online guides recommended uninstalling HTC Sync after getting the drivers, because it affects PATH, so I've uninstalled HTC Sync.

I've also downloaded the specific drivers for my HTC One M7 anyway, just to ensure it has the correct drivers installed.

fastboot devices

recognizes the device when fastboot is up.

adb devices

does not recognize the device when ADB sideload is up

Whether using the Ubuntu Terminal, or using Minimal ADB and Fastboot from CMD, both methods show the device from fastboot, and neither method shows ADB.

When trying to ADB Sideload, it just waits for a while and never accepts the file. It just says:

Updating partition details . . .

Error opening: '/data/ubuntu/dev/ram11' (Not a directory)

Error opening: '/data/ubuntu/dev/loop3' (Not a directory)

Error opening: '/data/ubuntu/dev/loop4' (Not a directory)

Error opening: '/data/ubuntu/dev/ram2' (Not a directory)

Error opening: '/data/ubuntu/dev/ram4' (Not a directory)

Error opening: '/data/ubuntu/dev/ram6' (Not a directory)

Error opening: '/data/ubuntu/dev/loop7' (Not a directory)

Error opening: '/data/ubuntu/dev/ram16' (Not a directory)

Error opening: '/data/ubuntu/dev/ram15' (Not a directory)

Error opening: '/data/ubuntu/dev/ram13' (Not a directory)

Error opening: '/data/ubuntu/dev/ram7' (Not a directory)

Error opening: '/data/ubuntu/dev/loop0' (Not a directory)

Error opening: '/data/ubuntu/dev/ram9' (Not a directory)

Error opening: '/data/ubuntu/dev/ram0' (Not a directory)

Error opening: '/data/ubuntu/dev/ram14' (Not a directory)

Error opening: '/data/ubuntu/dev/loop2' (Not a directory)

Error opening: '/data/ubuntu/dev/ram12' (Not a directory)

Error opening: '/data/ubuntu/dev/ram8' (Not a directory)

Error opening: '/data/ubuntu/dev/loop5' (Not a directory)

Error opening: '/data/ubuntu/dev/ram10' (Not a directory)

Error opening: '/data/ubuntu/dev/loop1' (Not a directory)

Error opening: '/data/ubuntu/dev/ram1' (Not a directory)

Error opening: '/data/ubuntu/dev/loop6' (Not a directory)

Error opening: '/data/ubuntu/dev/ram3' (Not a directory)

Error opening: '/data/ubuntu/dev/ram5' (Not a directory)

. . . done

Full SELinux support is present.

MTP Enabled

Starting ADB sideload feature . . .

Injecting boot.img with MultiROM . . .

ADB push:

If I bring up ADB Sideload and use Ubuntu Terminal to

./adb push '/home/user/Android/Sdk/platform-tools/ruu.zip' '/data/local/'

It returns: "adb: error: connect failed: no devices/emulators found"

If I use Terminal to:

adb push (the same)

(the difference there is without the "./")

It returns:

adb server is out of date. killing . . .

* daemon started successfully *

error: device not found

If I use Minimal ADB and Fastboot (Win 7) to try this, it returns a similar error:

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

adb: error: connect failed: no devices/emulators found

I've downloaded and installed the Hasoon2000's HTC One All_in_One Kit on Win7, which does not seem to do anything at all. It just returns the same exact error messages, that I get each time I do it manually.

Mmm... any help here would be hot.

Edit 1:

In the IRC, I was asked to run "fastboot getvar all", which returned the error: "getvar:all FAILED <command write failed<No error>> finished. total time: 0.003s"

On that note, "fastboot reboot-bootloader" doesn't work, either, with the exact same error message.

I assume that the only way to fix this is to install the RUU, which I have already downloaded to my computer and have it ready, but I can't figure out how to "adb push ruu.zip" to my phone's /sdcard storage. Each time I try "adb devices", it comes up empty (whereas "fastboot devices" lists the phone). I enter Recovery -> ADB Sideload, and then type "adb devices" (from both the command prompt and terminal), but it always shows up empty. Until I can push the RUU to my phone's storage, I can't try installing the stock ROM from Recovery, because it's only on my computer's storage.