Develop Bugs

[cofface]Oneplus 3T Twrp recovery,update20161208

Recovery base on TWRP 6.0:
support auto disable boot verify;
support setting restore offical recovery;
Screenshot:
{
"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"
}
Flash Method:
1. First must be unlock bootloader:
HTML:
fastboot oem unlock
2. Flash command:
HTML:
fastboot flash recovery cofface_recovery_oneplus3t.img
fastboot boot cofface_recovery_oneplus3t.img
3. Twrp recovery.img download Links:
https://www.androidfilehost.com/?fid=385035244224404291
4、if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc ，PAYPAL DONATION LINK
https://www.paypal.me/cofface

Fantastic work but how to get it in English dude?
Scratch that very easy....now in English...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

cofface said:
Recovery base on TWRP 6.0:
support auto disable boot verify;
Click to expand...
Click to collapse
What is boot verify? Is that screen that apear every time saying that your phone is rooted or something like that?
Sent from my Galaxy S6 using XDA Labs

If I install this I still can get ota update from OnePlus ?
Sent from my ONEPLUS A3003 using Tapatalk

If you select "disable auto verify": Is that merely "cosmetic" so that it doesn't ask you any longer for your encryption pwd or PIN? If it doesn't ask for it, does it still somehow allow you to operate an encrypted phone, backup & restore, etc?
Thanks.

There already is an official TWRP thread. Please use this thread:
http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308

Question OnePlus 9 Pro EDL/Qualcomm Crashdump

I tried to flash a modified magisk boot image, got the boot image from the payload.bin (stock OOS 12 newest update) booted the modified file then tried to flash the boot image via magisk manager, didnt worked 2 times with 2 different boot images, always ending up in Qualcomm Crashdump/Bootloader, I dont know how to fix this problem at this point.

Don't flash patchrd boot.img
Use fastboot boot, after booting you can use direct install from magisk

AboAnas25 said:
Don't flash patchrd boot.img
Use fastboot boot, after booting you can use direct install from magisk
Click to expand...
Click to collapse
I did exactly this and bricked my phone twice with it

Leon2504 said:
I did exactly this and bricked my phone twice with it
Click to expand...
Click to collapse
Did you use this option?
{
"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"
}

AboAnas25 said:
Did you use this option?View attachment 5498261
Click to expand...
Click to collapse
I booted the patched boot.img, phone booted just fine. Went to magisk, it asked for something needs to be install in other for magisk to work (cancel because otherwise it would reboot and I lose my root). I direct installed, reboot and qualcomm crashdump mode. @@ anyhelp?

Nhatlienhoan said:
I booted the patched boot.img, phone booted just fine. Went to magisk, it asked for something needs to be install in other for magisk to work (cancel because otherwise it would reboot and I lose my root). I direct installed, reboot and qualcomm crashdump mode. @@ anyhelp?
Click to expand...
Click to collapse
what version of magisk are you using?

ChrisFeiveel84 said:
what version of magisk are you using?
Click to expand...
Click to collapse
25.2

Custom ROM for Huawei y6 (2018)

I unlocked the bootloader of my Huawei y6 (atu-l21) 2 days ago. Now the problem is that I can't get working custom roms for twrp.
I had downloaded many .ZIP files but the zip file always contained only one image. When I wanted to download the ZIP file via twrp bottles, I always got a red message "invalid zip file format!
Does anyone have working custom ROMs for the Huawei y6 (atu-l21)
{
"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"
}

By you meaning by one file contains img file, you are trying to flash compressed gsi/treble image.
The installation procedure is different for treble devices. Instead do:
First you must uncompress it & do "adb reboot bootloader" & "fastboot flash system [UNCOMPRESSED_IMG_FILE]", wipe data by "fastboot -w", final reboot ur device "fastboot reboot"

do you think I should e.g. extract the customrom.zip to customrom.img and then the image with the commands Flash

Yes, Only if zip archive contains one *.img file like aonly, ab... etc

can I also flash the .IMG file via twrp. because when i try dan i don't know which partition to select.

System-Image

I just tried it and the message "Image is too large for the device" appears

You may read THIS POST about your device custom rom.
And if ab image doesn't work for you try aonly

Jannikoks06 said:
I just tried it and the message "Image is too large for the device" appears
Click to expand...
Click to collapse
Try with fastboot method

I'll do it later I'll report if it worked

Danielisko said:
Try with fastboot method
Click to expand...
Click to collapse
I did it but the phone doesn't boot, only the screen appears where it says that the bootloader on the phone has been unlocked

Question my mi 11x is not flash twrp , when i was flash my phone my cmd is stop

{
"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"
}

Wrong CMD.
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/

i am not able to download from your link.. please give me another link of twrp for mi 11x
please

manish1012 said:
i am not able to download from your link.. please give me another link of twrp for mi 11x
please
Click to expand...
Click to collapse
the link tells you how to flash the twrp
twrp
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/alioth/

manish1012 said:
View attachment 5823123
Click to expand...
Click to collapse
Look at the path - "platform-tools_r33.0.3___SPACE____ (1)\platformtools"
Cmd should work regardless I think...
But still remove that " (1)" from the platform tools folder name , it might cause you issues down the road.
( Mi flash doesn't work if you place it in a path that has spaces like this )
Now , check again - open cmd and type
Code:
fastboot devices
Does your device show up? Did you press enter after typing fastboot devices?
If it shows up , to flash twrp :
Command is
Code:
fastboot boot "twrp.img"
Open twrp website to learn how to do a permanent flash.
Xiaomi Poco F3
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Next time you wanna flash something do some research first... Flashing it with the command you found on YouTube for a different device than what you're using is an easy way to break the device...
To recover you'd have to extract boot.img / vendor_boot from your rom and flash it ( Unless you're using miui you'll have a pretty bad time ... )

Root Realme 9 4G (RMX3521) Without Custom Recovery

Hello,
As we all know there is no Custom Recovery available yet for our device. I decided to root the device with patched_boot.img.
I am able to root my Realme 9 4G successfully. I am sharing the procedure if someone like me, who cannot use a android mobile without root can follow the steps to root his Realme 9.
Before starting Make sure you are on RMX3521_11_A.31.
As the attached boot.img files are only for RMX3521_11_A.31.
To check your OS version Go to Settings > About device > Version and Match your Build Version. It should be RMX3521_11_A.31
First of all you have to unlock the bootloader.
Follow this Guide to unlock your bootloader.
Once your Bootloader is Unlocked. Follow the steps below
1. Download the magisk_Patched_boot.img from attachment and move it your PC.
2. Reboot your device into bootloader.
3. Open cmd in adb & fastboot directory and type the command
Code:
fastboot flash boot <drag magisk_patched_boot.img here>
And press enter.
4. Now restart your device by entering the command
Code:
fastboot reboot
5. Download the Magisk Manager and install it.
Your Device is Rooted Now. Make sure to disable the auto software update to avoid getting bootloop.
{
"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"
}

Btw there is an unofficial custom recovery for this device. It works and is tested. Here's the github link; https://github.com/cd-Crypton/custom_recovery_tree_realme_messi