[OnePlus 3 Questions & Answers] TheSwede86:
Info from FASTBOOT;

Product Name: msm8996

Variant: MTP UFS

Bootloader version: -

Baseband version: -

Serial Number: <omitted from here>

Secure Boot: Enabled

Device State: unlocked

Hi,

I have ALWAYS had a lot of problems flashing both custom (Lineage 14.1) and official ROMs (Oxygen OS).

If I calculate the md5-checksum of lineage-14.1-20171102-nightly-oneplus3-signed.zip after its been downloaded I get this:

a42a838309e0b75f54a032d1e1722c74 which matches the official checksum here:

https://www.lineageoslog.com/14.1/oneplus3

The same goes for OnePlus3Oxygen_16_OTA_036_all_1710262329_97651662219b4e6b.zip downloaded from here:

oxygenos.oneplus.net.s3.amazonaws.com/OnePlus3Oxygen_16_OTA_036_all_1710262329_97651662219b4e6b.zip

which matches this checksum: 1cd78fd180ead7908b0c1127c7e385b3

But after I've transfered either Lineage or Oxygen to my phone I get different checksums each time I transfer them using "adb push".

This makes it really hard to update / install custom ROMs and I've tried two different USB-cables and different USB-ports on my computer.

The checksum should match even if I transfer the file to my phone, thats the whole idea of a (file)checksum = to validate file integrity.

My example:

Using TWRP 3.1.1-2

Using lineage-14.1-20171102-nightly-oneplus3-signed.zip

Host: Ubuntu 17.04 (Had 16.04 earlier, same problem, even tried with Windows, same problem)

Android Debug Bridge version 1.0.36

Revision 1:7.0.0+r33-2

* Reboot into recovery

* Allow for modifications for partition "system"

* Wipe (data, cache, dalvik; also tried wiping all partitions, no change)

* "adb push" to "/sdcard/"

* adb shell > cd /sdcard/ > md5sum lineage-14.1-20171102-nightly-oneplus3-signed.zip = 44851d667c8b13f18f054e6e4ce41ecb = NOT the correct checksum

* Tried installing lineage together with OpenGApps & AddOnSU and I always get different results. Normally it just stops at a "random" point in the process, this time it went all the way but it does notc continue installing the other zips. I can't however find any errors in the "/tmp/recovery.log", see paste here:

https://pastebin.com/JX13qUNc

Ok lets redo it:

Now its unable to mount system

https://pastebin.com/JtiEzZMc

Ok so the "system" partition is:

/system | /dev/block/sde20 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB

which explains why it won't mount it...

* Wipe > Advanced Wipe > Selected all > Success except for OTG-USB

* Transfer the files using adb-push

* This time we get this checksum (on the phone): 10207fc1cbb1dc2c6b29c63dcff6d3c2

* Stalls around 20% with this error:

minzip: zlib inflate call failed (zerr=-3)

full log here:

https://pastebin.com/zgSXnq1d

So the times I've got it working has simply been a roll of the dice by doing multiple transfers and hoping one completes the installation.

Would really love some feedback and help, am I missing something really basic or is it actually behaving weird?

Best Regards and thanks for reading so long / TheSwede86

Update:

Tried the official android platform tools from Google here:

https://developer.android.com/studio/releases/platform-tools.html

Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

Behaves the same...