I backed myself into a brick corner and need some guidance

[Ivalicenyan]

It seems the daemon ist not running when first giving the command. As it should have started after the first command, what happens if you just repeat the "adb devices" for a second time?

Gesendet von meinem SM-G935F mit Tapatalk

I get

list of devices attached

without the daemon stuff.
This is in fastboot BTW.

In recovery > adb sideload I get:

list of devices attached
3f743bc1        sideload

I went a step ahead and dried adb sideload ota.zip again, and I got the same "error protocol fault no status" in the 1st picture on page 2 without matt daemon stuff this time

 

[s3axel]

I went a step ahead and dried adb sideload ota.zip again, and I got the same "error protocol fault no status" in the 1st picture on page 2 without matt daemon stuff this time

Well, it looks as if in adb sideload mode at least your devices is detected correctly. So, given the ZIP-file is OK, you should be able to finally flash the OTA.

To get rid of this error, please Open task manager and search for adb.exe and right click > end process. Then retry with the adb sideload command, if the daemon error comes up again just retry with the same command.

 

[Ivalicenyan]

Well, it looks as if in adb sideload mode at least your devices is detected correctly. So, given the ZIP-file is OK, you should be able to finally flash the OTA.

To get rid of this error, please Open task manager and search for adb.exe and right click > end process. Then retry with the adb sideload command, if the daemon error comes up again just retry with the same command.

And ive re-downloaded this zip multiple times

 

[Ivalicenyan]

Live support team bailed me out.

 

[Ivalicenyan]

NEW ISSUE!

With everything fixed, I went on about my business as usual, and then I get a notification of an update. So I accept.

Update froze in recovery, now its bootlooped again. What do?

 

[s3axel]

Just as an update to track solutions in order

In the meantime I was in the same boat in getting my new OP3T to working order. The above mentioned adb-error for me was solved by using/installing a later adb-version, which is e.g. available here.

WRT to your recent error - let me check, presently updating my OP3T to 3.5.3 via adb....