Help needed with TWRP 3.3.1-0 (up & running)

[[email protected]]

Hi, that's my first customisation:

1. Device unlocked:

2. TWRP flashed + *zip ready on /sdcard1

3. Install Zip fails

The checksums of all zips are ok, verified on my notebook.
I also can't wipe. And the standard Android 7.1 is recovering itself, if I boot-up.

Please advise, thanks!

 

[kabu83]

1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded

 

[[email protected]]

SECURE BOOT - enabled — Am I root?

1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded

Thanks, I did all that and much more, trying to install CM 13.1, crDroid, OrangeFox, SuperSu => nothing installs!

Now I wonder: Am I root at all? I thought so, since I installed TWRP on a naked device?!

The bootloader shows: DEVICE STATE - unlocked

 

[kabu83]

The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104

 

[[email protected]]

TWRP cannot mount /system

The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104

Now, that my holidays are over, I want this Crackling to crack!
Here my efforts to crack it via Fastboot:
Since the vintage Cyanogen fails as well as the state of the art Linage, I suspect that the payload might not be the cause for the failure?!

# fastboot flash system lineage-16.0-20190826-microG-crackling.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2794255 is not a multiple of the block size 4096
erasing 'system'...
OKAY [  0.841s]
sending sparse 'system' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
OKAY [  8.258s]
writing 'system' 1/3...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 16.173s
# fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [  1.042s]
finished. total time: 1.043s

# fastboot flash system SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 350727218 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 82295858 is not a multiple of the block size 4096
erasing 'system'...
OKAY [  0.831s]
sending sparse 'system' 1/4 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
OKAY [  8.290s]
writing 'system' 1/4...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 14.176s
# fastboot erase recovery
erasing 'recovery'...
OKAY [  0.205s]
finished. total time: 0.205s
# fastboot flash recovery twrp-3.3.1-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16984 KB)...
OKAY [  0.563s]
writing 'recovery'...
OKAY [  1.188s]
finished. total time: 1.751s
# fastboot boot twrp-3.3.1-0-crackling.img
downloading 'boot.img'...
OKAY [  0.535s]
booting...
OKAY [  0.672s]
finished. total time: 1.208s

 

[kabu83]

Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)

 

[[email protected]]

Bootloader vs BIOS

Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)

At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?

In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')

Thanks for all your assistance, most appreciated! :good:

 

[kabu83]

At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?

In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')

Thanks for all your assistance, most appreciated! :good:

I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currentyl installed?

 

[[email protected]]

/system is empty

I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currently installed?

As mentioned, I prefer a clean install. Thus formatted /system with ext4 via Fastboot (it's default). It should be possible to mount an empty /system -- isn't it?

 

[kabu83]

A clean install is needed anyway. It seems just easier to install the OS via TWRP and for future nightly updates anyway.

 

[[email protected]]

Heureka!

I would recommend installing TWRP, Version 3.2.1-0.

With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)

What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?

 

[kabu83]

With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)

What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?

Can you boot into CM 13 now?
Has it replaced TWRP as recovery?

 

[[email protected]]

Bingo!

Can you boot into CM 13 now?
Has it replaced TWRP as recovery?

I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.

Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.

 

[kabu83]

I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.

Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.

Happy to help. So you are all set now?