Curious, did you manage to get the device to boot using a magisk patched boot image? I’ve got this rom running now which has builtin su, but I can’t get anything to actually boot a magisk patched boot.img, it just drops me to fastboot, where if I flash the original boot.img it will boot fine into whatever OS.
Initially I played with TWRP and Magisk (sorry for omitted this detail).
After the full reset, it works well with Lineage 17.
Now I’m trying to install Linage 18 (with the correct fastboot mode):
./fastboot flash system lineage-18.1-20210317-UNOFFICIAL-treble_arm64_bvS.img
Resizing 'system' FAILED (remote: 'Not enough space to resize partition')
How can I resize the system partition (for newbie like me please) ?
Some other members were saying they just deleted the logical product partition. I haven’t tried it yet, but fastbootd (see link above to google’s docs on it) it seems to have a command like this for resize:
resize-logical-partition <partition> <size> Resizes the logical partition to the new size without changing its contents. Fails if not enough space is available to perform the resize.
I’m thinking if product can just be resized using this, then when you flash system it will just auto-resize to the appropriate size. You could also just delete product like suggested above though, I did it can it seems like things still run ok, not totally sure what data is stored there.
I was able to flash lineage 18 after:
fastboot delete-logical-partition product
“delete-logical-partition” is not documented in fastboot --help, but it works
Thanks @mastershake and @anonimal !
Anyone have trouble with speakerphone? Mine just is an immediate feedback loop. I just applied the headphone jack fix, no difference there (and was present prior) with regards to speakerphone, headphone jack works great though.
Note: To apply the headphone jack fix, I couldn’t get it to work just be editing prop.default, I had to use the following, I’m not sure where it stuck that prop config for persistence though.
:/data/data # getprop persist.sys.overlay.devinputjack
false
:/data/data # setprop persist.sys.overlay.devinputjack true
:/data/data # getprop persist.sys.overlay.devinputjack
true
1 Like
I was also able to flash lineage 18 after deleting product. I gather the product partition really doesn’t apply to GSIs? I am still trying to fully wrap my head around the concept of a GSI.
Two things to check:
- Try a different phone/dialer app like Simple Phone.
- Check phh gsi github issues (or google) to see if similar issue is being reported on latest builds.
Thanks for the suggestions! I did look on the phh github issues but didn’t see anything, but I might have the wrong search terms, there is a lot of activity over there. I just tried out Simple dialer and it seemed to have the same issues with speakerphone, when turned on it just becomes a feedback loop.
Could you try a different gsi maybe Android 10, 11.
Hello followed instructions from n download ran the update and so everything is working fine
No trouble with Jack or speaker. Thanks
1 Like
which gsi are you using? thanks
Looks like Phh has fixed the audio echo problem in the v305 release of their AOSP11 GSI. The pull request that managed the fix can be found here: https://github.com/phhusson/platform_frameworks_av/pull/8/commits/4613a24b3bc739b4fcc0d158b5ef8517107d526f. If you are building another GSI you can probably use the pull request to come up with a patch or point the project maintainer to this fix.
1 Like
Thanks, but … how to become root with Lineage OS ?
I can install TWRP + magisk to be root with the original Teracube 2e ROM.
I can install Linage OS 17 without magisk.
But each time I try to install Lineage + TWRP + magisk (in any order) it ends with a boot loop 
Please, help !
I could correctly install LineageOS 18 and TWRP, the order seems relevant: first install LineageOS 18
and then install TWRP. I cannot guarantee that this will not result in a boot-loop in the future though: LineageOS ships recovery updates within the system updates sometimes.
In order to change the sound property, you don’t necessarily need to have a rooted phone, but simply be able to send root commands through adb:
- Go in Settings > System > Developer options
- Activate “USB debugging” and “Rooted debugging”
- Connect the phone via USB to your pc
adb shell setprop persist.sys.overlay.devinputjack true
Hi @anonimal
I have a similar issue with lineage-18.1-20210411-UNOFFICIAL-treble_arm64_bvS.img
I can ear my own microphone in the speaker (with a short delay) during a call.
Same issue if I use a bluetooth headset.
With a jack headset, it’s worse (it seems that both microphones are used).
So the phone is not usable for phone calls
PS : No issue in jitsi meet
The patches used for the lineage-18 build done by AndyYan (which I suspect is the one you are using) are only up to date to v304 of PHH’s patches. The next release of that GSI will probably merge in the audio patch for the microphone in the speaker issue.
Hello Sir
can i flash Andy Yan`´S GSI Images (IMG File) via TWRP??? Flash with fastboot dont work…
Regards
Can you please elaborate on the issue with flashing via fastboot?
Please note, on the Teracube 2e, you will have to reboot to fastbootd in order to flash a GSI.
fastboot reboot fastboot to go into fastbootd.
Hello Mr.
after command: fastboot reboot fastboot…
fastboot:usage:unknown reboot target fastboot
try to flash roar…gsi…img
fastboot flash system roar.img
writing system 1/12…
Failed remote (this parition dosent exist…
what can i do???
Hello Matrix,
Check your fastboot version:
fastboot --version
You might need to download the latest version from android(dot)com (platform tools).
1 Like