Database Develop

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 5G (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 5G G9770, G977U, G977U1 and G977W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10 5G: beyondxq.
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:
Code:
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
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
@jesec for unlock guide
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
27.04.2021 - Update to G977PVPU6FUBH kernel source
31.12.2020 - Update TWRP to 3.5.0
20.11.2020 - Initial Release

You can add the G977P/T to the list as working, confirmed working on my G977T.

Is this still good for android 11?

If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)

G977B supported? Android 11?

Yoonwoo said:
If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)
Click to expand...
Click to collapse
This is the wrong one, this is for exynos, we are dealing with snapdragon here.

razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Just got my G977P, getting info on how to root Android 11 G977PVPS5EUA4, trying not to brick my device. Any tips on how to do it the safe way? First time trying to root Snapdragon device.

Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!

razercortex said:
Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!
Click to expand...
Click to collapse
Thanks! Is it safe to update to latest official software update before installing TWRP?

Yes, it shouldn't matter.

razercortex said:
Yes, it shouldn't matter.
Click to expand...
Click to collapse
Confirmed working on G977P, so fast and easy, thanks for the support!

razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked

Nexu F said:
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked
Click to expand...
Click to collapse
Did you flash vbmeta? Also, starting android for the first time takes a really long time.

razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
I did yes. I'll try this doing this guide once more later tonight. Could be quite possible I'm missing a step or didn't pay close attention to one since the others with the same Device on this thread reported a success

razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
Any rough idea to how long the starting Android could take before i stop it?

Is the SM-G977N korean model supported
Android 11
Do you know how to access OEM Unlock in development. There is no sign of it on this phone.
Thanks

Any updates for Android 12 G977PVPS8HVE1 for SM-G977P (Sprint)? I can see the official firmware already out, but waiting for working version of TWRP.

Yo, idiot. This guide is for Beyondx not Snapdragon. Misleader.....

[ROM][RAV][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"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"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
08-04-21 Build - GAPPS/VANILLA
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

Hi, I need help. I did the exact process correctly but when it rebooted it went to fast boot and every time I reboot into system it just goes back to fast boot and if I boot in the recovery I get this error. What did I do wrong?

xam nam said:
Hi, I need help. I did the exact process correctly but when it rebooted it went to fast boot and every time I reboot into system it just goes back to fast boot and if I boot in the recovery I get this error. What did I do wrong?
Click to expand...
Click to collapse
reinstall stock, and try again. Only thing i can think of, is that you might not be rebooting to recovery after flashing

Still boots to fastboot rom won't boot

xam nam said:
Still boots to fastboot rom won't boot
Click to expand...
Click to collapse
When you use moto flash tool, are you leaving it connected long enough? The tool flashes the stock rom, then reboots to fastbootd and flashes system/vendor to slot b, then asks you if you want to format data, and then you exit.
Another user was disconnecting as soon as the firmware flashed, and was missing the slot b prep, i think you might have the same issue

I don't even know how to use the flash tool

Just tried this out and works fine. Still prefer stock motorola tho but android 11 looking to be very cool

ArrowOS June update available from the download link on the first post.
June Security patch
Added Moto Camera 2
Adjusted the status bar alignment (centered with the hole punch cam now)

Help me, I bought a motorola g fast on ebay, I'm from Venezuela, and it's blocked by boost mobile and I've contacted them and they can't help me to release it. I ask you, installing a custom rom could I free my moto g fast?

I did have to flash back to Android 10 to do this. I grabbed the earliest ROM from Motorola and used the flashfile.bat that is included in that download. No need to download the Moto Flash Tool.
Once I flashed back to Android 10, I was able to install TWRP via fastboot, boot into TWRP, format data, use TWRP to reboot into fastbootd within TWRP, and flash the files in OPs post. Thanks @Beetle84 !

[ROM][SOFIAR][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"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"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679

Agh, plain AOSP. I miss Havoc already.

Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.

Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?

jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)

Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here

This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.

Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.

RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d

Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.

RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?

Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.

Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.

Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?

jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.

ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?

Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.

jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.

actually it is rescuing me to android 11 no matter what i do

General [TWRP] [venus] Fixed TWRP Chinese Recovery for Mi 11

There is afwul closed source twrp made by xinkid520. It has very dangerous bug, if you switch slot your device will be bricked, and the only way to repair is paid authorized account (btw do not pay more than 15$ whatsoever, it's a ripoff).
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
I made a small mod to fix this.
Now it has default language by default (English) and that button was removed.
That jerk did not upload the sources, the changes were made only in the xml files, so there should not be any new bugs
Installation is the same as in original thread
Archive is .7z, but xda didn't allow this extension so i renamed it to .rar
Before and after
{
"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"
}

megapro17 said:
There is afwul closed source twrp made by xinkid520. It has very dangerous bug, if you switch slot your device will be bricked, and the only way to repair is paid authorized account (btw do not pay more than 15$ whatsoever, it's a ripoff).
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
I made a small mod to fix this.
Now it has default language by default (English) and that button was removed.
That jerk did not upload the sources, the changes were made only in the xml files, so there should not be any new bugs
Installation is the same as in original thread
Archive is .7z, but xda didn't allow this extension so i renamed it to .rar
Before and after
View attachment 5401889View attachment 5401891
Click to expand...
Click to collapse
Just a suggestion, why you don't share this file or put the link of this thread in the other thread, it will be useful for more people.

SubwayChamp said:
Just a suggestion, why you don't share this file or put the link of this thread in the other thread, it will be useful for more people.
Click to expand...
Click to collapse
Hmm, okay

megapro17 said:
Hmm, okay
Click to expand...
Click to collapse
Usefull, i'm here because of the link on the other thread
Thanks for your version !

megapro17 said:
There is afwul closed source twrp made by xinkid520. It has very dangerous bug, if you switch slot your device will be bricked, and the only way to repair is paid authorized account (btw do not pay more than 15$ whatsoever, it's a ripoff).
Click to expand...
Click to collapse
False ! the first time i try twrp, i switch the slot and yes my device was bricked. I just flash the engenering rom and reflash a global rom. my phone is working without paid .

Pikaone41 said:
False ! the first time i try twrp, i switch the slot and yes my device was bricked. I just flash the engenering rom and reflash a global rom. my phone is working without paid .
Click to expand...
Click to collapse
However you will agree it's a good fix for prevent mistake/issue

Can this twrp flash China dev rom pro? rom file larger than 4Gb

Pikaone41 said:
False ! the first time i try twrp, i switch the slot and yes my device was bricked. I just flash the engenering rom and reflash a global rom. my phone is working without paid .
Click to expand...
Click to collapse
How did you flashed engenering rom? I tried it, it required authorization anyway. Maybe your device wasn't completely bricked, not in 9008 mode?

Hi, I can't seem to copy any roms to my Mi 11 with TWRP, windows refuses to even start to try and copy and when i try to copy from my note 20 it gets to 99% and then fails?

skyler13 said:
Hi, I can't seem to copy any roms to my Mi 11 with TWRP, windows refuses to even start to try and copy and when i try to copy from my note 20 it gets to 99% and then fails?
Click to expand...
Click to collapse
flash from usb otg. this twrp is bad

Hi, how can I change to this fixed recovery from the original? Any mini tutorial?
Thanks in advance

neo9596 said:
Hi, how can I change to this fixed recovery from the original? Any mini tutorial?
Thanks in advance
Click to expand...
Click to collapse
From your actual TWRP > Install > (on bottom right) install image > choose new twrp > Reboot > Recovery
or from adb like the first time :
Code:
fastboot boot twrp-venus-fixed.img

Oh, so easy! Thanks. And I need to select inject again or no?
Thanks for your time

megapro17 said:
flash from usb otg. this twrp is bad
Click to expand...
Click to collapse
yeah i've already tried that but twrp doesn't see the usb otg for some reason, managed to fix it after an hour of searching. the method adb push rom.zip /sdcard didn't work but someone suggested adb push rom.zip /data and this has allowed me to copy the rom to my phone and flash it now.

Has anyone tried out this person's twrp
GitHub - LittleTurtle2333/android_device_xiaomi_venus-twrp: TWRP device tree for Xiaomi Mi 11
TWRP device tree for Xiaomi Mi 11. Contribute to LittleTurtle2333/android_device_xiaomi_venus-twrp development by creating an account on GitHub.
github.com

Pho3nX said:
From your actual TWRP > Install > (on bottom right) install image > choose new twrp > Reboot > Recovery
or from adb like the first time :
Code:
fastboot boot twrp-venus-fixed.img
Click to expand...
Click to collapse
What image to flash should i choose then 'Boot' ?

Development [RECOVERY] TWRP for ZenFone 8

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot boot twrp.img
Now you are booted into TWRP, but it is NOT permanently installed. To install it permanently, use the "Flash current TWRP" option in the Advanced menu. This will install the currently booted TWRP permanently to both slots. NOTE: If you were previously rooted, you will need to re-install the root apk/zip as the TWRP install will overwrite it!
Alternate Installation Method (requires prior TWRP installation, or if fastboot booted into TWRP already, start at step 3):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select "Install Recovery Ramdisk" from the partition list and swipe to flash
(Optional) If previously rooted, re-install root apk/zip, as the TWRP install will overwrite root.
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
3.5.2_11-2:
Add vendor_boot to partition list
3.5.2_11-1:
Update super and qti_dynamic partitions size
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
USB-OTG not working
Battery Status not working
TWRP Upstream
Android 12 decryption only works if no password/PIN/pattern is set (i.e. only default password)
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse

mine

I'll take 2

Maybe 3 to be safe

Thank you for this! Great to see a twrp thread

Pinch me, I must be dreaming!
Edit: it works, but how to enter it again?

Captain_Throwback said:
USB-OTG not working
Click to expand...
Click to collapse
Is it temporary? Or at the moment it can not be fixed?
P.S. Thank you for your release!

dron39 said:
Is it temporary? Or at the moment it can not be fixed?
P.S. Thank you for your release!
Click to expand...
Click to collapse
It seems you asked the same question twice, but the answer is that the OP has the current status. If there are any changes in the future, it will be updated.

Undead_Son said:
Pinch me, I must be dreaming!
Edit: it works, but how to enter it again?
Click to expand...
Click to collapse
Once you're booted into TWRP, you can use the "Flash current TWRP" option under Advanced to install it permanently. If you were rooted, you'll then have to re-flash the root apk/zip.

Captain_Throwback said:
If you were rooted, you'll then have to re-flash the root apk/zip
Click to expand...
Click to collapse
What is partition to where it should be flashed?
You wrote that we will need to reflash root (.apk or .zip). But what if I have also custom kernel installed (Kirasakura) ?
Shuld I "permanently" install recovery on stock kernel or it doesn't matter ? I just want to clarify, because as far as I understand magisk patches boot.img ?
And each time after firmware update we will need to reflash twrp, correct?
And I haven't found information about our device on twrp.me (Devices->Asus). Will you add it there later?

dron39 said:
What is partition to where it should be flashed?
Click to expand...
Click to collapse
I don't understand your question. When you flash the root apk/zip, it'll take care of flashing where it's supposed to go. You don't have to worry about any partitions.
dron39 said:
You wrote that we will need to reflash root (.apk or .zip). But what if I have also custom kernel installed (Kirasakura) ?
Click to expand...
Click to collapse
I don't know about custom kernel, but you can always flash it again after you re-flash the root zip to make sure it persists if you're unsure. Flashing it again won't hurt anything.
dron39 said:
Shuld I "permanently" install recovery on stock kernel or it doesn't matter ? I just want to clarify, because as far as I understand magisk patches boot.img ?
Click to expand...
Click to collapse
It's up to you whether you want to install TWRP permanently, but the instructions focus on fastboot booting. I'm not sure how Magisk is relevant here, as that has no effect on TWRP.
dron39 said:
And each time after firmware update we will need to reflash twrp, correct?
Click to expand...
Click to collapse
Yes, but if you install the update in TWRP, you can choose the option to "Automatically install TWRP after zip" to keep TWRP if you have it permanently flashed.
dron39 said:
And I haven't found information about our device on twrp.me (Devices->Asus). Will you add it there later?
Click to expand...
Click to collapse
This is a prerelease version. The Android 11 TWRP tree hasn't been officially released. The ZF8 page will be there once the release is official. There's already a markdown patch ready for that time.

What does "unable to locate storage device" mean?

Hi,
I unlocked my device with the asus unlocker and rooted succesfully.
But when I try flash TWRP with fastboot I get:
Sending 'boot.img' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Has anybody an idea whats the issue here?
Regards,
Hyper

HyperCriSiS said:
Hi,
I unlocked my device with the asus unlocker and rooted succesfully.
But when I try flash TWRP with fastboot I get:
Sending 'boot.img' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Has anybody an idea whats the issue here?
Regards,
Hyper
Click to expand...
Click to collapse
Are you sure you're in bootloader, and not fastbootd? Also please confirm that you're attempting to fastboot boot as per the OP instructions.

Captain_Throwback said:
Are you sure you're in bootloader, and not fastbootd? Also please confirm that you're attempting to fastboot boot as per the OP instructions.
Click to expand...
Click to collapse
Yes, I was in fastbootd
Thank you so much, it is working very well

New test version uploaded. Thanks to @micky387 for his help with the TWRP tree!

With newest version MTP does not work anymore.
I deleted the device and the new detected device name is different. It was "Zenfone 8" before and now "Asus_I006D"

HyperCriSiS said:
With newest version MTP does not work anymore.
I deleted the device and the new detected device name is different. It was "Zenfone 8" before and now "Asus_I006D"
Click to expand...
Click to collapse
I changed absolutely nothing related to MTP, and it continues to work fine here.
The device name in TWRP was always ASUS_I006D. If you happened to connect the device to your PC in Android first, then that's probably why it showed up as "ZenFone 8". But when you deleted it the TWRP default got set as the name.
Can anyone else confirm whether MTP is working for them on the latest version? If you're using Windows, it's possible some update broke something on your end.

Yes, Microsoft often messed with the MTP drivers. In the device manager I deinstalled everything related to the Zenfone and reinstalled, but still does not work.
TWRP throws some errors. Maybe this is the issue? I also reinstalled it again.

HyperCriSiS said:
Yes, Microsoft often messed with the MTP drivers. In the device manager I deinstalled everything related to the Zenfone and reinstalled, but still does not work.
TWRP throws some errors. Maybe this is the issue? I also reinstalled it again.
Click to expand...
Click to collapse
That looks very broken. But a screenshot is very unhelpful to determine root cause. The OP makes it clear that logs are required to get assistance. So please provide a recovery log and logcat so that I can review the problem.
Is Android working okay? Seems like something else is going on there. Did you install anything? I'm going to need more details of how exactly you got to this point.