Develop Bugs

[RECOVERY] [OnePlus 5] OrangeFox Recovery Project [19 FEB 2020]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OrangeFox Recovery
Installation:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to fastboot screen, connect USB and send fastboot commands "fastboot flash recovery <recovery image file name including extension>"
OR
1. Reboot to existing TWRP recovery and flash image file to recovery partition
2. Reboot to recovery
3. Enjoy!
Features:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Flashlight
* Password, torch, led
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Source Code:
https://gitlab.com/OrangeFox
https://github.com/neobuddy89/android_device_oneplus_cheeseburger-twrp
Screenshots:
https://files.orangefox.tech/Screenshots/R10/
IMG Download:
19 Feb 2020: https://sourceforge.net/projects/cr.../OrangeFox-20200219-cheeseburger.img/download
Frequently Asked Questions:
* See https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
XDA:DevDB Information
OrangeFox Recovery Project, ROM for the OnePlus 5
Contributors
neobuddy89
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-02-18
Last Updated 2020-02-18

Added to the OnePlus 5 Index Thread here.

Added to Telegram Channel here: http://t.me/op5_files/1559

The recovery is very beautiful !
could you add the support to F2FS ? it can't read my data partition，Thx.

Also, seems it is unable to restore backups within same ROM for Q. I can try unless you are aware of it.

Thanks Mr neo. Backs up great looks great. Haven't tried to restore yet

Can it be used to flash custom pie roms?

str8str said:
Thanks Mr neo. Backs up great looks great. Haven't tried to restore yet
Click to expand...
Click to collapse
Did you use it to flash a rom? If so, has the procedure been performed without any issues?

Sc4r3Crow said:
Did you use it to flash a rom? If so, has the procedure been performed without any issues?
Click to expand...
Click to collapse
So far just did backup. Can't see why it wouldn't work

Sc4r3Crow said:
Did you use it to flash a rom? If so, has the procedure been performed without any issues?
Click to expand...
Click to collapse
Yes works. I tried install, backup, restore, moving files, etc. I am Encrypted BTW.

Can anyone tell me if wiping vendor is necessary when changing roms or clean/dirty flashing

str8str said:
Can anyone tell me if wiping vendor is necessary when changing roms or clean/dirty flashing
Click to expand...
Click to collapse
yes,recommended.

tried to flash twrp recovery
It's so pretty.
Restoring from a backup is working.
When trying to flash twrp-3.3.1-0-cheeseburger.img using this recovery it gets stuck in the bootloader and wont start anything.
not sure if this is an issue with twrp recovery. or even a corrupted file.
using firmware_9.0.10

@spo0nless What ROM was the image made of and which parts are backing up/restoring?

Is it possible to make it OP 5T compatible ?

mnurolcay said:
Is it possible to make it OP 5T compatible ?
Click to expand...
Click to collapse
It works fine on the 5t, I've been using it for a few weeks and the only "issue" is that it says cheeseburger instead of dumpling.
I've had no issues restoring nandroid backups (both ones made with twrp and OrangeFox).

Isn't there a port specifially for the 5t?

Pokemetti2 said:
Isn't there a port specifially for the 5t?
Click to expand...
Click to collapse
There's one but a bit outdated. This one is more up to date esp about Android 10.

spo0nless said:
It's so pretty.
Restoring from a backup is working.
When trying to flash twrp-3.3.1-0-cheeseburger.img using this recovery it gets stuck in the bootloader and wont start anything.
not sure if this is an issue with twrp recovery. or even a corrupted file.
using firmware_9.0.10
Click to expand...
Click to collapse
It's surely a corrupt file. I've flashed other twrp versions using OrangeFox and it worked everytime. Just to be sure you could flash 9.0.11 in advance and have a try to flash another twrp after that...

If I select internal memory, along with the usual, to wipe, is that the equivalent of TWRP's format data?
edit: just noticed the note saying it got moved to manage partitions, so nvm

[Recovery][v3.0.0][Curtana] Unofficial PBRP Recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp

Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path

kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp

Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!

@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?

You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.

Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?

mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it

end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks

Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well

Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?

Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.

end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!

Thank you
Sent from my Redmi Note 9 Pro using Tapatalk

is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!

keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk

how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted

trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...

Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222

Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 (Snapdragon)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S10 G9730, G973U, G973U1 and G973W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10: beyond1qlte.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
10.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
16.02.2021 - Initial R build for Android 11
31.12.2020 - Update TWRP to 3.5.0
14.11.2020 - Initial Release

Seems to be working properly! Thank you!

wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!

robocopvn said:
wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!
Click to expand...
Click to collapse
It isn't free, but yes. Mine is and rooted. Verizon variant here.

abranson said:
It isn't free, but yes. Mine is and rooted. Verizon variant here.
Click to expand...
Click to collapse
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.

superturtlr19 said:
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.
Click to expand...
Click to collapse
I had to pay and had it done remotely. Sampwnd. . Google it

abranson said:
I had to pay and had it done remotely. Sampwnd. . Google it
Click to expand...
Click to collapse
Oh wow, these are pricey. Well thank you for your time.

Deleted

afaneh92 said:
Note: download link is down, will make new build tomorrow then will fix the link. Please do not share older builds.
Edit: new builds are up, US devices are not supported anymore, only devices already unlocked before 9 November are.
Click to expand...
Click to collapse
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it

illspiritX said:
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it
Click to expand...
Click to collapse
Read notes on OP

afaneh92 said:
Read notes on OP
Click to expand...
Click to collapse
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?

abranson said:
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?
Click to expand...
Click to collapse
Will contact you on telegram

Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?

fabiokino said:
Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?
Click to expand...
Click to collapse
To encrypted the the data partition again need to do factory reset from stock recovery.

afaneh92 said:
To encrypted the the data partition again need to do factory reset from stock recovery.
Click to expand...
Click to collapse
Thank you for the answer. My idea was to make a TWRP image once I completely personalized the system and then encrypt the device, but I understand that it's not possible...
So the alternative solution is to find a way yo make an image of the encrypted device after the personalization...
Is there a way to make an image of the encrypted data partition apart from using dd? Since it is encrypted with fbe I was wondering if there's a method which doesn't require to save the whole partition but only the actual (encrypted) files.

Changelog:
16.02.2021 - Initial R build for Android 11

Does anyone with a SM-G9730 wanna try a US rom I made for it?

how to disable AVB in s10 9730?

jrkruse said:
Does anyone with a SM-G9730 wanna try a US rom I made for it?
Click to expand...
Click to collapse
9730 module can flash us version? I wanna try

[RECOVERY][UNOFFICIAL][3.5.2_10-0][dipper] TWRP Recovery for Xiaomi Mi 8

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel
Prerequisites:
Unlocked bootloader
What's working?
- ADB
- MTP
- DECRYPT
- And more
Download:
twrp3.5.2_10-0
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Source code:
GitHub - LowTension/android_device_xiaomi_dipper: Device tree for build TWRP for Xiaomi MI 8(dipper) only.
Device tree for build TWRP for Xiaomi MI 8(dipper) only. - GitHub - LowTension/android_device_xiaomi_dipper: Device tree for build TWRP for Xiaomi MI 8(dipper) only.
github.com
GitHub - TeamWin/android_bootable_recovery
Contribute to TeamWin/android_bootable_recovery development by creating an account on GitHub.
github.com
Credits:
althafvly​

reserved

Anything different than the official one?

Installed without problems.
Works well on A-11
Thank you

250652 said:
Installed without problems.
Works well on A-11
Thank you
Click to expand...
Click to collapse
Thank you for your feedback.

Thankyou ZonaRMR
Does it work with LineageOS? Previous Official did not

vulongmos said:
Does it work with LineageOS? Previous Official did not
Click to expand...
Click to collapse
Official TWRP 3.5.0_9 works fine with official LOS.
I didn't get the point on this release yet, TWRP says their _10 versions are for devices released with Android 10, so _9 is correct for the good old Mi 8...

vulongmos said:
Thankyou ZonaRMR
Does it work with LineageOS? Previous Official did not
Click to expand...
Click to collapse
Do you mean that?
Moldeb said:
Official TWRP 3.5.0_9 works fine with official LOS.
I didn't get the point on this release yet, TWRP says their _10 versions are for devices released with Android 10, so _9 is correct for the good old Mi 8...
Click to expand...
Click to collapse
it makes sense to me since the Xiaomi Mi 8 received android 10 officially.

Moldeb said:
TWRP says their _10 versions are for devices released with Android 10
Click to expand...
Click to collapse
ZonaRMR said:
Mi 8 received android 10
Click to expand...
Click to collapse
Spot the difference. I'm on Android 10 as well of course, soon on Android 11 and the official TWRP _09 branch supports this. Could you please explain the benefits of your unofficial version? I'd like to understand the facts before considering a test.

Tried to compile it on my own with your device Tree.
Got Error
FAILED: ninja: '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfsfde_intermediates/import_includes', missing and no known rule to make it
21:58:28 ninja failed with: exit status 1
Did something change on TWRP?
Greets and thanks

Updated to 3.5.2_10-0 (Based on Android 10)
Download: https://www.mediafire.com/file/fe9ttmec4vjc5nb/twrp3.5.2_10.0.img/file

How do i decrypt my Mi8 Dipper? i just formatted data and clean flashed and now have encrypted phone.

Arthur P. Dent said:
Tried to compile it on my own with your device Tree.
Got Error
FAILED: ninja: '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/[...]/out/target/product/dipper/obj/SHARED_LIBRARIES/libcryptfsfde_intermediates/import_includes', missing and no known rule to make it
21:58:28 ninja failed with: exit status 1
Did something change on TWRP?
Greets and thanks
Click to expand...
Click to collapse
Did you ever figure this out? I'm getting the same error trying to build official TWRP for the mi 8 Pro.
EDIT: Turns out you can get around the error by removing the line: "TARGET_HW_DISK_ENCRYPTION := true" from your BoardConfig.mk but I'm not sure if it will be able to decrypt.

Hi, all day trying to flash TRWP. I want to switch from miui.eu to lineageos, so I wipe data and then try to flash LOS. Nothing work and I decided to upgrade TWRP from FASTBOOT. Nothing work, the phone got stuck on fastboot. Then with MIflash I was able to install miui global, but now I simple cant install TWRP over the MI-Recovery 3.0
I'm using diferent TWRP versions and the following commands
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
After that black screen for a few seconds and the it boot normally to MIUI and MI Recovery 3.0 still there. Dont know what to do or combination to use
Please help!!

nortuzar said:
Hi, all day trying to flash TRWP. I want to switch from miui.eu to lineageos, so I wipe data and then try to flash LOS. Nothing work and I decided to upgrade TWRP from FASTBOOT. Nothing work, the phone got stuck on fastboot. Then with MIflash I was able to install miui global, but now I simple cant install TWRP over the MI-Recovery 3.0
I'm using diferent TWRP versions and the following commands
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
After that black screen for a few seconds and the it boot normally to MIUI and MI Recovery 3.0 still there. Dont know what to do or combination to use
Please help!!
Click to expand...
Click to collapse
Make sure all is working(adb, fastboot, USB port...)
Code:
fastboot flash recovery recoveryname.img
fastboot reboot recovery

Please @LowTension Could start Creation Of TWRP 3.6 Working on Android 12

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 (Snapdragon)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S22 S901E/S901N/S9010.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22: AFH: r0q twrp and kernel / Drive: r0q twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree

Changelog:
GitHub History

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section

Is there a kernel for 901E?
Can only seem to find one for 901b
EDIT: found what I needed in the telegram group snapdragon models use the same kernel

i flashed twrp in fw ave4 , after flash kernel, wipe data, and get bootloop, how fix?

skinza said:
Is there a kernel for 901E?
Can only seem to find one for 901b
EDIT: found what I needed in the telegram group snapdragon models use the same kernel
Click to expand...
Click to collapse
send me kernel bro please...

Tonystarki said:
i flashed twrp in fw ave4 , after flash kernel, wipe data, and get bootloop, how fix?
Click to expand...
Click to collapse
you ran multidisabler?

Tonystarki said:
send me kernel bro please...
Click to expand...
Click to collapse
Dont flash wrong kernel, if you have snap use the link from this thread

afaneh92 said:
Dont flash wrong kernel, if you have snap use the link from this thread
Click to expand...
Click to collapse
calm down, I will not install the wrong kernel

running the multidisabler is essential to install the custom kernel, the device does not start but runs multidisabler, all right now, what customizations does the kernel have? @afaneh92

Tonystarki said:
running the multidisabler is essential to install the custom kernel, the device does not start but runs multidisabler, all right now, what customizations does the kernel have? @afaneh92
Click to expand...
Click to collapse
permissive and disabled security

Please lmk if you get it working
I flashed on s22 veh and lost WiFi
Then when phone screen went to sleep I couldbt wake it up
Followed the instructions

skinza said:
Please lmk if you get it working
I flashed on s22 veh and lost WiFi
Then when phone screen went to sleep I couldbt wake it up
Followed the instructions
Click to expand...
Click to collapse
Will look into it

afaneh92 said:
Flash custom kernel and magisk apk in twrp
Click to expand...
Click to collapse
Is this step to root the Phone？

sinaamos said:
Is this step to root the Phone？
Click to expand...
Click to collapse
You can skip magisk if you don't want root

Just got my S901E on FW U1AVCJ. Is it safe to update to U2AVF1 before installing TWRP? Just making sure I will be able to unlock BL and install TWRP. Thanks in advance!

Daemonite said:
Just got my S901E on FW U1AVCJ. Is it safe to update to U2AVF1 before installing TWRP? Just making sure I will be able to unlock BL and install TWRP. Thanks in advance!
Click to expand...
Click to collapse
Its ok

hi there!
i would love to follow this tutorial, however, i have some noob doubts before doing it that i would like to address:
1) what does it mean r0q? "Downloads for S22: r0q twrp and kernel"
2) how should i decide which files download in twrp? what does it mean afaneh92-r0q? its for S22 non-ultra
3) why can i download the custom kernel in point 7 if there is no custom kernel for s22 non-ultra?
4) the custom kernel of point 7 must be flashed through twrp?

r0q is regular s22
The s22, s22+ and ultra all use the exact same kernel

skinza said:
r0q is regular s22
The s22, s22+ and ultra all use the exact same kernel
Click to expand...
Click to collapse
thank you! i have managed to make it work! i dont think it's related but i cant wipe system partition since its not present in the twrp wipe section... perhaps i am missing something?