TWRP Coral [Official]

[GROOVYJOSHCLARK]

I accidentally overrode the initial version instead of making a -1 release. However the fixed build for fastbooted twrp on lineage-19.1 will be up on twrp.me shortly.

Worked like a charm!

 

[xdadottts]

Thanks bigbiff! ax562- your steps does work; &YES, no more font-colors
Question? After fastboot/twrp, the "Mount" screen is asking for a password. I put my PIN/Screen lock password, but get "failed to decrypt user". When I remove the PIN /reboot/renter fastboot twrp, its fine. I put the PIN back on and its a no-go.

Any suggestions?

 

[ax562]

@bigbiff Yoooooo! You're the real MVP. Works great on lineage 19.1!

 

[ax562]

Thanks bigbiff! ax562- your steps does work; &YES, no more font-colors
Question? After fastboot/twrp, the "Mount" screen is asking for a password. I put my PIN/Screen lock password, but get "failed to decrypt user". When I remove the PIN /reboot/renter fastboot twrp, its fine. I put the PIN back on and its a no-go.

Any suggestions?

The Pin decrypt does work if you go into twrp without being restored from a backup. From my understanding decrypt isn't working if you flash a back up with a pin. I originally posted about this on my original post to you. I have backed up and restored multiple times without a pin set on backup's and they worked. TWRP was asking me "Are you sure you want to back up with a pin code?" which was a first and odd so I didn't backup with pin. I'm sure bigbiff can clarify.

 

[legend876]

An how you guys go about downloading this build

 

[legend876]

@bigbiff Yoooooo! You're the real MVP. Works great on lineage 19.1!

For lineage os 19.1

 

[bigbiff]

The Pin decrypt does work if you go into twrp without being restored from a backup. From my understanding decrypt isn't working if you flash a back up with a pin. I originally posted about this on my original post to you. I have backed up and restored multiple times without a pin set on backup's and they worked. TWRP was asking me "Are you sure you want to back up with a pin code?" which was a first and odd so I didn't backup with pin. I'm sure bigbiff can clarify.

The problem isn't when you backup, but when you restore with pin enabled. Since new inodes have to be created when new files are created on a newly formatted or clean filesystem, it will break zygote, because zygote will be expecting the inodes to not change. There is no way around this, and why we want you to remove pin before restoring backups.

 

[ax562]

For lineage os 19.1

It's the latest releases for our google coral device. Bigbiff said he named it the same as the previous release, so it's going to be the latest and greatest.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.

 

[legend876]

It's the latest releases for our google coral device. Bigbiff said he named it the same as the previous release, so it's going to be the latest and greatest.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.

I can confirm it works thanks man plus tried it on Android 13 latest works and everything touch included thanks developer for your hard work respect my man big up fam

 

[legend876]

Guys I got it to work on Android 13 with access to internal storage if you want to know just say although I bet most of you know how to already but still can try help

 

[legend876]

1.go to twrp page an download both .img and .zip

2.fastboot boot twrp.img in platform tools

3.go to twrp advance settings and go on adb sideload,after now adb sideload twrp installer.zip

4.reboot to recovery an there bammm you got internal storage access...

Your welcome hope you guys understand what I'm saying still kinda new to this but try something an it works haha now twrp my stock recovery an everything's working fine thanks again to the awesome developer......hope it works

 

[legend876]

1.go to twrp page an download both .img and .zip

2.fastboot boot twrp.img in platform tools

3.go to twrp advance settings and go on adb sideload,after now adb sideload twrp installer.zip

4.reboot to recovery an there bammm you got internal storage access...

Your welcome hope you guys understand what I'm saying still kinda new to this but try something an it works haha now twrp my stock recovery an everything's working fine thanks again to the awesome developer......hope it works

An for those with android 13

 

[legend876]

 

[legend876]

View attachment 5741873View attachment 5741875

That's the proof if you're guys not sure

 

[GROOVYJOSHCLARK]

That's the proof if you're guys not sure

Just a heads up, I fastboot boot the TWRP image, I do not install TWRP, I decrypt my /SDCard without an issue, I can (and do) mount my internal SD without any of those needed. I use LOS 19.1 official, with no kernels but also test A13 for others, I had no issues with the latest version on 13 official. Maybe I misunderstood your post.

 

[legend876]

Just a heads up, I fastboot boot the TWRP image, I do not install TWRP, I decrypt my /SDCard without an issue, I can (and do) mount my internal SD without any of those needed. I use LOS 19.1 official, with no kernels but also test A13 for others, I had no issues with the latest version on 13 official. Maybe I misunderstood your post.

I did not Install either but wasn't getting the access to my internal storage so I just adb sideload twrp.zip to patch both boot image caz I don't have an otg ATM but I will soon

 

[legend876]

Just a heads up, I fastboot boot the TWRP image, I do not install TWRP, I decrypt my /SDCard without an issue, I can (and do) mount my internal SD without any of those needed. I use LOS 19.1 official, with no kernels but also test A13 for others, I had no issues with the latest version on 13 official. Maybe I misunderstood your post.

It also wasn't show my code at the beginning step of twrp either after I finished with the adb sideload it show after I rebooted into recovery back......

 

[GROOVYJOSHCLARK]

It also wasn't show my code at the beginning step of twrp either after I finished with the adb sideload it show after I rebooted into recovery back......

All good, I just wanted to point out my testing results landed the same end results without the extra steps/work. I like to do it the easiest/safest way for consistency so that's the only place its coming from but not an attack on the methods used.

 

[legend876]

All good, I just wanted to point out my testing results landed the same end results without the extra steps/work. I like to do it the easiest/safest way for consistency so that's the only place its coming from but not an attack on the methods used.

Thanks man well appreciated

 

[digitalcircuit]

Heads up: if you have trouble decrypting FBE on an Android 12 ROM, removing your pattern/pin code/etc might work.

I've decided to make the jump from stock 12.1.0 (SQ3A.220705.003.A1, Jul 2022) to LineageOS 19.1 this evening, and I couldn't get twrp-3.7.0_12-0-coral.img to decrypt my user data despite confirming I had the correct pattern. Flashing the installer .zip and booting 3.6.2 didn't work, either.

However, booting into Android 12, removing my pattern in Settings, then booting into TWRP 3.7.0 worked.