Development [RECOVERY] [UNOFFICIAL] TeamWin Recovery Project [3.7.0][A12-13]

[mahbod.es.1996]

which version of android are you using?

xiaomi.eu 13.0.4 based on Android 12
Sorry for delay.

 

[beachdirge]

any news on android 12 decryption?

 

[Camerado]

any news on android 12 decryption?

https://sourceforge.net/projects/twrp-releases/files/Courbet/recovery.img

 

[Lollauser]

https://sourceforge.net/projects/twrp-releases/files/Courbet/recovery.img

3.6.2 has just been removed

 

[Camerado]

3.6.2 has just been removed

 

[Sunnykha]

Do we know any reason why ?

 

[Sunnykha]

https://sourceforge.net/projects/twrp-releases/files/Courbet/TWRP-3.6.2_12.1-courbet-20220701.img

Has anyone tried this one.
I haven't it is posted on telegram

 

[anu1]

Will it work with indian version i mean COURBETIN?

 

[Sunnykha]

Will it work with indian version i mean COURBETIN?

I cant say for sure, but I would think it should. Maybe you can go to the telegram group where posted to check. I cant post the link since not allowed.

 

[anu1]

I cant say for sure, but I would think it should. Maybe you can go to the telegram group where posted to check. I cant post the link since not allowed.

Thank you so much

 

[HerH2]

New update to 3.7.0

Support A12, A13 Decryption.
Improve minor stuff

Download

 

[asakurato]

Can't seem to make magisk work on 3.7.0. I used to flash patched boot.img with previous twrp, but now it just won't boot after flashing.
Edit: nvm, I was using wrong boot.img file...

 

[mzcl-mn]

New update to 3.7.0

Support A12, A13 Decryption.
Improve minor stuff

Download

Hello, I am wondering what might I have done wrong in regard to an event that was happening with my courbet and that I don't understand why it was 'acting like that'...

Is there any difference between the two suggested TWRP recovery flashing commands provided?

fastboot boot <recovery.img file>

and:

fastboot flash recovery <recovery.img file> ?

The 'otherwise unexplainable' events that I've noticed were, TWRP being booted every so often (in a random pattern) while trying to boot the system from ('go figure') other recoveries (like OrangeFox).

I had flashed TWRP before trying out OrangeFox. (And, I had tried to use both of those provided fastboot commands. Could that be the source of my issues with that TWRP 'persistence'?

I've sought (googled) for this issue for a while, so I apologize for the inconvenience if this is addressed somewhere else.

Summing up:

Why was there a TWRP persistence, and why did it 'come up' / boot 'at its own will'?

Thank you very much for any information!

Besides, thank you very much for your work!

Cheers!

 

[Lollauser]

Hello, I am wondering what might I have done wrong in regard to an event that was happening with my courbet and that I don't understand why it was 'acting like that'...

Is there any difference between the two suggested TWRP recovery flashing commands provided?

fastboot boot <recovery.img file>

and:

fastboot flash recovery <recovery.img file> ?

The 'otherwise unexplainable' events that I've noticed were, TWRP being booted every so often (in a random pattern) while trying to boot the system from ('go figure') other recoveries (like OrangeFox).

I had flashed TWRP before trying out OrangeFox. (And, I had tried to use both of those provided fastboot commands. Could that be the source of my issues with that TWRP 'persistence'?

I've sought (googled) for this issue for a while, so I apologize for the inconvenience if this is addressed somewhere else.

Summing up:

Why was there a TWRP persistence, and why did it 'come up' / boot 'at its own will'?

Thank you very much for any information!

Besides, thank you very much for your work!

Cheers!

Sorry I don't completely understand the issue, but the fastboot commands you listed do two different things:

fastboot boot <recovery.img file>
This load and boot a recovery image from your pc, without flashing (and thus changing) anything on the phone

fastboot flash recovery <recovery.img file>
This one install (flash) the recovery in the recovery partition on your phone, replacing the stock one ore the one you already had
This is generally speaking, then if you reboot your phone to stock system, the custom recovery may still be overwritten by the default one (our Courbet works that way), but this is not your problem i guess

 

[mzcl-mn]

Sorry I don't completely understand the issue, but the fastboot commands you listed do two different things:

fastboot boot <recovery.img file>
This load and boot a recovery image from your pc, without flashing (and thus changing) anything on the phone

fastboot flash recovery <recovery.img file>
This one install (flash) the recovery in the recovery partition on your phone, replacing the stock one ore the one you already had
This is generally speaking, then if you reboot your phone to stock system, the custom recovery may still be overwritten by the default one (our Courbet works that way), but this is not your problem i guess

Hello @Lollauser , thank you for your answer. I'm sorry if I wasn't clear.

Basically, my issue is that I am greeted with TWRP recovery whenever I try to boot the system. This happens, usually, but unexpectedly, whenever I flash xiaomi.eu ROM. Which makes me wonder why. Could it be that xiaomi.eu ROM flashes some particular TWRP version whenever that ROM gets flashed? I came here so that I could see if my issue with xiaomi.eu ROM is particular of mine or not. I figured, for instance, that, since the TWRP version that I get whenever I flash xiaomi.eu ROM is the one from this thread I am posting on right now and that you are reading, this might be the right place to ask for advice.

I hope this time I made myself a little bit clearer...

Cheers.

'See you later', hopefully.

 

[Lollauser]

Hello @Lollauser , thank you for your answer. I'm sorry if I wasn't clear.

Basically, my issue is that I am greeted with TWRP recovery whenever I try to boot the system. This happens, usually, but unexpectedly, whenever I flash xiaomi.eu ROM. Which makes me wonder why. Could it be that xiaomi.eu ROM flashes some particular TWRP version whenever that ROM gets flashed? I came here so that I could see if my issue with xiaomi.eu ROM is particular of mine or not. I figured, for instance, that, since the TWRP version that I get whenever I flash xiaomi.eu ROM is the one from this thread I am posting on right now and that you are reading, this might be the right place to ask for advice.

I hope this time I made myself a little bit clearer...

Cheers.

'See you later', hopefully.

I'm sorry but i never used xiaomi.eu and i don't know well how it's working, maybe by flashing it (fastboot version?) it flashes also twrp, in a way that is not compatible with a later flashing of different recovery?
Or maybe you made something wrong in flashing recovery (orange or twrp) and it ended in a wrong partition, other than recovery one.
I'm sorry but i'm no developer

One thing you can do to get rid of the issue, is flashing a stock fastboot rom with official miflash. That will erase everything and bring your phone to factory state, then you can do your flashing again by scratch.

 

[HerH2]

Hello @Lollauser , thank you for your answer. I'm sorry if I wasn't clear.

Basically, my issue is that I am greeted with TWRP recovery whenever I try to boot the system. This happens, usually, but unexpectedly, whenever I flash xiaomi.eu ROM. Which makes me wonder why. Could it be that xiaomi.eu ROM flashes some particular TWRP version whenever that ROM gets flashed? I came here so that I could see if my issue with xiaomi.eu ROM is particular of mine or not. I figured, for instance, that, since the TWRP version that I get whenever I flash xiaomi.eu ROM is the one from this thread I am posting on right now and that you are reading, this might be the right place to ask for advice.

I hope this time I made myself a little bit clearer...

Cheers.

'See you later', hopefully.

Hi, I think what you're talking about. if you flashed EU 13.0.9.0 and/or later than that it will start twrp again. I understand that it is solved using the boot.img from EU 13.0.8.0.

 

[Lollauser]

Trying to flash nikgapps for android 13 on top of latest crDroid rom
Installation fails because of a not enough storage error, so I need to resize System partition.
But I don't have that partition in the list of wipable ones, and i can't find the way to mount it.
Is it not possible with this 3.0.7 on Android 13?

 

[p1lo]

So... I'm on my Courbet, with old TWRP 3.6.0 and xiaomi.eu 12.5.
Could I'll update to TWRP-3.7.0-courbet-ygherna.img quietly?

Try to update to 3.7.0, but can't unlock phone with pattern.
Flash the 3.6.1, it is back, unlock pattern work

 

[HerH2]

Trying to flash nikgapps for android 13 on top of latest crDroid rom
Installation fails because of a not enough storage error, so I need to resize System partition.
But I don't have that partition in the list of wipable ones, and i can't find the way to mount it.
Is it not possible with this 3.0.7 on Android 13?

Rom issues, Dev should modify partitions table