Root HTC One deleted OS, totally lost

[ChrisOB]

Hi, i tried to totally reset/clean my phone because i wanted to update (Was rooted) and now i've stupidly deleted my entire OS somehow. After looking for the last 2 days for the correct RUU, i can't find a single one that works because it looks like my OS (6.16.61.8 is higher than anything i can find.
I'm on EE, Relocked and all the ruu files i try fail, both exe and zip...

version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.16.61.8
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0

Any help would be massively appreciated, thanks!

 

[Hadron]

Your problem is that you have an EE-branded phone (actually Orange branded), and they rarely leak RUUs out. As you are S-On the phone will only let you use RUUs which match your CIDnum, and with no OS you won't be able to switch to S-Off and use a different RUU.

Simplest is probably to unlock your bootloader again, then assuming you have a custom recovery still you can just use that to flash a custom ROM. Either use "adb sideload" while in recovery to copy the ROM .zip, or buy a USB OTG cable (a small adapter that lets you connect a USB flash drive to your phone), copy a ROM .zip onto a flash drive, boot into recovery and then install the ROM from "USB storage".

If you somehow wiped the custom recovery then unlock the bootloader again and reinstall. But my guess is that you did your "total reset" using the recovery, in which case it will still be there itself; I reckon you probably deleted all partitions, including "system" which is, as the name implies, where the operating system lives.

 

[ChrisOB]

Thanks for the reply.
By total reset i mean i dived in like a plank and wiped everything, my bad. My problem now is i can't seem to find my device using 'adb devices' in cmd, I've tried uninstalling drivers, changing usb ports, and downloaded all sorts of different adbs, but it's just saying 'List of devices attached' and then it's blank. So trying to use a new unlock token just leaves me with 'Waiting for device'.
Fastboot detects it fine but adb doesn't.
Am i screwed?

 

[Hadron]

Have you still got a custom recovery? If you have, ADB will find it when you are in recovery mode (tech break: you need an adb daemon running on the phone for ADB to find it. This normally only happens if you have USB debugging enabled while running Android, but most custom recoveries also run an ADB daemon).

If you haven't, you'll need to install a custom recovery using fastboot. It's very hard to stop fastboot working, as you've discovered . You will however have to unlock the bootloader in order to fastboot flash a new recovery.

Or, as said, if you still have a custom recovery then with a flash drive and a USB OTG cable you can flash a ROM anyway.

Bottom line: as long as you can still get into the bootloader it's not hopeless. I am of course assuming that you have the bootloader unlock code from previously unlocking the bootloader, but I don't see how you could be in this position without that (either you used a custom recovery to wipe the partitions or you used fastboot, and either way the bootloader needed to be unlocked at some point).

 

[ChrisOB]

Aha! Managed to unlock it again and got TWRP back up so thanks for that. So now I've grabbed a custom rom (Android 5.0.2 (Lollipop) - latest official HTC One 7.19.401.30 (WWE) firmware (92.x series) [No Sprint Support])
I'm assuming that it's basically a modded OS? I tried to root by pushing the SuperSU.zip onto it and flashing, then installing the custom rom, but i keep looping and going back to recovery...
I'm deffo getting somewhere though!

 

[Hadron]

You don't need to root a custom ROM - they invariably come pre-rooted.

Yes, it's basically a modied/tweaked version of the official OS. Question: which ROM exactly (link to XDA thread would be unambiguous). If you are new to ROMs it's advisable to check whether it has any particular requirements. In particular, from the baseband version I suspect your firmware is quite old, in which case it's possible you might have problems with a Lollipop ROM - I take it you'd not had an official Lollipop update? If so you might have to try again with a KitKat ROM.

 

[ChrisOB]

All sorted now mate, i tried a few that led to bootloops but after trying ViperOne_6.2.0, it works a charm. Thanks for the help AJ, Smoke me a kipper!