TWRP on Cosmo w/ V22

[360North]

Sorry...if this has been asked before...researched it, but didn’t find a conclusion.

Do we know yet, with regards to TWRP & TWRP partition on Cosmo...does the TWRP image from PC work, if installed in TWRP partition...or if PC image of TWRP is corrupted & have to use a different TWRP image??

In other words, does anybody have the TWRP image from PC working at all??

I’ve installed PC image of TWRP, but seems to be faulty (doesn’t work). All else works (Non-root, rooted, and Debian) AFAIK.

If I have to install a different image of TWRP in TWRP partition, will it cause any issues with Cosmo?

Also, how do we access TWRP on Cosmo to flash zip’s?? Only recovery I can access is PC’s recovery at boot, am I missing something or just getting confused? Used to working with Galaxy Notes in past.

Kind of a newbie here, trying to learn...if anyone can provide a tutorial or a link, that would help.

TIA

[Vistaus]

I have the same issue. I never got Planet's TWRP to work, but root (except for updating Magisk, which is broken), non-root and Debian work fine.

[cam1965]

I have the same issue. I never got Planet's TWRP to work, but root (except for updating Magisk, which is broken), non-root and Debian work fine.

Ninji TWRP worked for me with v19 . Planet TWRP never worked for me. Now with v22 because of the encrypted file it asks for a password. Please see https://www.oesf.org/forum/index.php?showtopic=35988. It only access the  external sd card.
Note : Please read everything in that post.

[360North]

So...I’m guessing that PC’s image for TWRP is totally bogus & corrupted??

I reached out to PC Support a while ago and this was their response...

“On a standard mobile device, if you were to root them or install another OS, you'd loose the warranty due to how experimental those OS's typically are. In our case, we don't void your warranty, but it is still important to note that the productivity software on our devices is the one that comes preinstalled after you unbox your device. Additional OS images are more or less experimental and they are developed by the community such as TWRP and Linux.”

...so I’m assuming they are NOT supporting TWRP...yet they put out a TWRP image, talk about confusing & conflicting info!  

How do we access TWRP, even if we got it working?

Oh...and what did you mean by Magisk is broken??

[Vistaus]

Linux, as in the Debian KDE image, is developed by someone from Planet. Not sure about TWRP.But I agree that the way they've written it is a bit vague.

I didn't say Magisk is broken, I said *updating* Magisk is broken. So rooted boot works fine, but you cannot update Magisk. Although I have to admit that I haven't tried it with V22 yet, maybe Planet fixed the issue. Will give it another try in the next couple of days.

[ehem]

I've had the exact same experience.  I tried Planet's TWRP image and got nowhere.  Selected TWRP boot option, then got dark screen and momentary vibration, wait for a bit and it is clear it went crunch.  I hope to rebuild TWRP myself as @Ninji's build doesn't meet my standards, then I can get onto further phases...

I didn't say Magisk is broken, I said *updating* Magisk is broken. So rooted boot works fine, but you cannot update Magisk. Although I have to admit that I haven't tried it with V22 yet, maybe Planet fixed the issue. Will give it another try in the next couple of days.

I'd been wondering about this.  I'd seen no complaints and was wondering if I was the only person who had run into this.

One big tidbit though:  Did you observe the messages during the attempt at upgrading Magisk?
Crucial one I noticed was "Installing in EMPTY_NORMAL_BOOT_4".

I'm pretty sure the problem is simply Magisk update is attempting to install to the wrong area.  Likely it is searching the MMC block devices in reverse order and so finds EMPTY_NORMAL_BOOT_4 before it finds ROOTED_ANDROID.  It might even be possible to boot using the extra entry...

Originally I was going to go and suggest copying boot to EMPTY_NORMAL_BOOT_4, installing and then copying back.  Unfortunately I kept reading the directions too many times and found what I had been looking for under "Boot Image Patching".  At which point I had the crucial bit of information I had been looking for.


Start a root shell and then run the command: `dd bs=2048 if=/dev/block/by-name/boot of=/storage/emulated/0/Download/magisk.img`
Go into Magisk Manager, select the "Update" option to the right of "Magisk".  Choose "Select Method", then "Select and Patch a File".  At this point you'll be in the file manager recent items list, go to "Downloads" and select "magisk.img".
Go back to the root shell (or start a new one) and run the command: `dd bs=2048 if=/storage/emulated/0/Download/magisk_patched.img of=/dev/block/by-name/boot`


You can change filenames/directories if you want, but that is the process.