[One (M7) Q&A, Help & Troubleshooting] uuzi:
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:

Core problem:

After replacing my broken display assembly (before, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone went into bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.

So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).

Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)

What I tried already after reading a whole lot of threads:

1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)

2. Factory reset via hboot

3. bootloader relocked then unlocked then relocked again to flash ruus

4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"

5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)

6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.

7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results

EDIT1: 8. rewritten version-main from 4.19.xxxxxx to 1.00.000.0 (via HTC One All-In-One Toolkit by Hasoon2000) in an desperate attempt to fix ruu flashing, no luck as well (i think that even broke more things :( )

EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.

current state:

i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)

fastboot getvar all gives:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 3544************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s

If you need any additional info, i'd gladly supply.

anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.

thx in advance,

uuzi