[OnePlus X Q&A, Help & Troubleshooting] semaph0re:
Hello there!

Long story short:

I'm was successfully running on twrp-3.0.2-0-onyx-20161020-085152.img and cm-13 on my beloved OPX for serveral months now. Got it running, following this guides:

http://xdaforums.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

https://wiki.cyanogenmod.org/w/Install_CM_for_onyx

Also, happily updating the nightly builds since then.

But last update went wrong. I OTA updated my device on the go, not paying to much attention that the update will be cm13->cm14. After TWRP installed the update i got stuck on reboot with the OnePlus logo.

I restarted the phone (Powerbutton off/on), 'cause my guts told me that something went wrong. I hoped to reboot to recovery an rollback the update to previous CM version.

But, it won't boot.

This is what happens:

Powerbutton down (Trun on): -> Vibrates -> flashes OP Logo + powerd by Android -> Vibrates -> flashes OP Logo + powerd by Android ->...

I can reach fastboot mode by VolumeUp (w/o pressing powerbutton) but i cannot reach TWRP recovery.

So normally i could totally live with fastboot, flashing reflashing unlocking etc. BUT here my first WTF experience took place:

I can not

fastboot oem unlock

because oem unlock is locked! I know how to unlock it via DevMode -> unlock oem unlock yadda yadda (who had this "great" idea anyway?!). But since i cannot boot the OS, i cannot enter devmode....

So before going through all the (Mega)unbrick guides, I'm curious:

Is there some way around this dilemma?

What we've got: No OS, no recovery, only fastboot

$: fastboot devices
...
25bf1e07	fastboot

$ fastboot oem device-info
...
(bootloader)	Device tampered: true
(bootloader)	Device unlocked: false
(bootloader)	Charger screen enabled: false
(bootloader)	Display panel:
(bootloader)	console_enabled: 0
(bootloader)	exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s

$: fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.003s

$: fastboot format userdata
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote:	Device not unlocked cannot flash or erase)
finished. total time: 0.000s

fastboot continue

ends up in same loop.

I cannot adb.

Device is encrypted.

I've no problem to completely wipe or factory reset or stock reset my device, hence i love tinkering with it and have backups of important data.

I sincerely ask for some pointers, links, opinions on how to go on from here? Is there a chance to get my phone back running? Should I stop searching and just follow the unbrick guides?

Are there unbrick guides for Linux users? (Just nice to have! :) )

Is there some exploit, backdoor, trick, magic to circumvent a disabled 'oem unlock'? (again: who had this 'great' idea anyways? :) )

Unbrick guide(s):

https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/

Thank you very much in advance! Have your (virtual) coffee on me!

sem