Database Info

[Recovery] TWRP 3.2.2.0 for redmi 6 pro ( sakura )

{
"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"
}
IM NOT THE CREATOR OF THIS TWRP, FOUND IT SPMEWHERE AND WANTED TO SHARE IT​
installation:
1. Setup ADB/Fastboot
2. Download the twrp from here : download
3. Power off your device.
4. Hold volume down + power button to boot into the bootloader.
5. Connect your device to your PC with a USB cable.
6. Open the command prompt on your PC.
7. Type cmmand : fastboot flash recovery "filename of recovery.img"
done
If u have anti rollback enabled :
first method:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
2nd method:
fastboot flash antirbpass "recovery.img"
changelog:
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
for further questions and discussion join telegram group here

nofx161 said:
IM NOT THE CREATOR OF THIS TWRP, FOUND IT SPMEWHERE AND WANTED TO SHARE IT​
installation:
1. Setup ADB/Fastboot
2. Download the twrp from here : download
3. Power off your device.
4. Hold volume down + power button to boot into the bootloader.
5. Connect your device to your PC with a USB cable.
6. Open the command prompt on your PC.
7. Type cmmand : fastboot flash recovery "filename of recovery.img"
done
changelog:
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
for further questions and discussion join telegram group here
Click to expand...
Click to collapse
C : \ adb> fastboot flash recovery sakura . img
sending 'recovery' (47604 KB)...
OKAY [ 1.562s]
writing 'recovery'...
FAILED (remote: rollback version downgrade)
finished. total time: 1.578s

evl01 said:
C : \ adb> fastboot flash recovery sakura . img
sending 'recovery' (47604 KB)...
OKAY [ 1.562s]
writing 'recovery'...
FAILED (remote: rollback version downgrade)
finished. total time: 1.578s
Click to expand...
Click to collapse
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"

nofx161 said:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"
Click to expand...
Click to collapse
Now is asking for a password to decrypt. What should I put there?
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
evl01 said:
Now is asking for a password to decrypt. What should I put there?
Click to expand...
Click to collapse
When I put cancel, I can enter to recovery but I can't use any storage. It's 0mb

If you factory reset through twrp and reboot recovery it should be OK. But keep in mind to do a backup of your stuff first.

Hello,
TWRP is released under GPLv3+. It means that if you submit a build of TWRP, you need to distribute its source code and instructions to build it.
Where did you find this build if you "found it somewhere and wanted to share it"? You are basically violating the license by just "sharing" it.
Read the pinned post for more information (applies to GPLv2 like GPLv3).

nofx161 said:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"
Click to expand...
Click to collapse
Thanks for the information, I lost connection with terminal after booting into TWRP, and didn't know what to do next as TWRP was o MB .
And terminal showed "FInished" with no error in your second command, but twrp was still not installed after holding down power + volumn down. :/
Is there anything i did wrong? Please reply Mr.Sakura

How to check if anti rollback is enabled?

Fastboot getvar anti

It just says anti: and no number. What does this means?

Mine shows the same so I think there is no anti rollback on our 2 devices.

mine also says "anti"..no number

Please be careful while flashing recovery that are found "somewhere".

Well, after flashing latest miuipro still anti with no count

Please delete this thread! False information!

any solution it is show 0mb internal

Do a factory reset in twrp or flash disable encryption.zip

forum.xda-developers.com/redmi-6-pro/development/recovery-twrp-v3-2-x-redmi-6-prosakura-t3851959
Check my post in above link

Doubt
coolek33 said:
If you factory reset through twrp and reboot recovery it should be OK. But keep in mind to do a backup of your stuff first.
Click to expand...
Click to collapse
How will i access the internal storage later if i format it totally ???

You will access it but it will be empty. So U can use sd card/usb otg for flashing

[R][PRAGUE][February] Descendant XI - android ver. 11r31

{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page.
Sources
Github
* you must have TWRP installed (The pretoriano80 one is more compatible with Q and R, so I recommend it.)
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) !
* format data
* reboot to bootloader
* extract Descendant archive
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
And your done. Reboot and wait for Descendant beauty to show up. ​
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Remember this is Unofficial rom so for support ask on our HI6250 Community group.
Don't spam on Descendant group!
Preloaded applications
Kiwi Browser and Metro.
ADB is not working.
The signal icon is buggy due to Huawei weird ril implementation.
*If you know more let us know.​
@phhusson - For GSI stuff. Your the Greatest!!
@Dil3mm4 - For Descendant creation! Thanks a lot man. Your ROM is so perfect. Your a legend.
@DarkJoker360 - For trees, support, everything related with hi6250/prague. You are the best.
@Hami_Do - For hi6250 fixes/debugging. And what comes in the future. You are always a great help to us. Keep it up man!
@haky 86 - For being Haky! Your knowledge/opinions helps us.​

NOTES
* For root method read this post.
* If you face corrupted storage issues you need to do factory reset and reinstall rom.
* I recommend using pico OpenGapps.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* If you want VoLTE/Wifi Calling working flash this zip.
* If you find empty Signal icon distrubing, you can flash this zip. Thanks to @Hami_Do
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.
~Thanks to @DarkJoker360

Reserved2

Flashed on Huawei Mate10 Lite RNE-L21. booted good at once.
but there is no navigation icon at bottom of device.
Bluetooth buggy.
also didn't find camera.
Rest working good , very snappy so far.

Hello .
I have to install the Rom and it works so far: But no root access.
I have installed the APK that works on AOSP 11.
But no root access.
Please help

Hi when i try to write system i had this error . can some one help me ?
PS D:\Download 2018\P8 Lite 2017\ROM\Android 11\descent> fastboot flash system ourmonalisa.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' (460799 KB)...
OKAY [ 12.629s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.668s

piterconlai said:
Hi when i try to write system i had this error . can some one help me ?
Click to expand...
Click to collapse
Maybe you're using a wrong firmware. Newer firmwares have reduced system partition size.
From note
Use 8.0.0.360 or maximum .400 firmware for booting the rom.

Thread closed by OP request!

Rooting on MIUI 13.0.3.0

Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!

ashirviskas said:
Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!
Click to expand...
Click to collapse
Did you try with Magisk manager?

That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A

ashirviskas said:
That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A
Click to expand...
Click to collapse
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20

NOSS8 said:
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20
Click to expand...
Click to collapse
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.

ashirviskas said:
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.
Click to expand...
Click to collapse
I had this phone but I don't remember if it has RAMDISK?
{
"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"
}

NOSS8 said:
I had this phone but I don't remember if it has RAMDISK?
Click to expand...
Click to collapse
It does.

And no vbmeta

ashirviskas said:
It does.
Click to expand...
Click to collapse
Surely you did everything correctly but just in case, check.(Possibly post a screenshot of the CMD with the result)
Copy the boot/recovery image to your device
Press the Install button on the Magisk card
If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
In most cases, it should already be automatically checked.
Choose “Select and Patch a File” in the method, and select the stock boot/recovery image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC with ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/recovery image to your device.
For most devices, reboot into fastboot mode and flash with the command:
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image
Reboot and voila!
Or use the twrp to flash the modified boot.img

Though I do see it when I run `adb shell ls -l /dev/block/by-name` I will try repatching and reflashing, maybe this is what has been missing.

Here's my latest attempt with vbmeta.img included:
sudo fastboot flash boot magisk_patched-25200_VvhFg.img
[sudo] password for mati:
Sending 'boot' (131072 KB) OKAY [ 3.275s]
Writing 'boot' OKAY [ 2.315s]
Finished. Total time: 5.600s
sudo fastboot flash vbmeta --disable-verity --disable-verification lmi_global_images_V13.0.3.0.SJKMIXM_20220620.0000.00_12.0_global/images
/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.024s
sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.201s
Opening magisk app it still says `Installed: N/A`

Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.

ashirviskas said:
Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.
Click to expand...
Click to collapse
Better than stock(more options, call recorder)and play store certified without root.
https://xiaomi.eu/community/threads/miui-13-stable-release.64441/

Huawei P20 data restore

Hello guys,
One of my clients asked me to restore data (photos, documents, messages...) from his Huawei P20 ANE-LX1.
It is stuck on the following screen:
{
"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"
}
Your device has failed verification and may not work properly.
To learn more, visit:
http://zh.ui.vmall.com/emotiondownload.php?mod=restore
It always shows this error screen after a reboot.
I can not enter in Recovery mode. When I try to, it stays for ever on the Huawei logo screen.
I tried to install a firmware from an Micro SD card but without success.
Here's the firmware version I found online: Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.278(C432E6R1P7T8)
To do so, I placed the "dload" folder in the Micro SD card's root folder. Then rebooted the phone and maintaining the volume+ and volume- buttons together while 30 sec.
The result is a green screen with a red and blue square while few seconds, then rebooting again and again:
I tried to enter in Fastboot & Rescue mode. It works:
The error message in the middle is not always the one appearing in the picture (FASTBOOT_LOADLPMCU_FAIL 169).
From there, I tried to use ADB to get the files (photos, docs...) from the internal memory. But I never managed to display my device with the adb devices command:
Tried from 3 differents computers, with different ADB drivers, found online.
The result is always the same; nothing.
Here's an example of the drivers I got:
Here's infos about the smartphone that I got from Fastboot commands:
fastboot oem get-build-number
(bootloader) :ANE-LX1 9.1.0.401(C432E13R1P7)
OKAY [ 0.013s]
finished. total time: 0.014s
fastboot oem get-product-model
(bootloader) ANE-LX1
OKAY [ 0.014s]
finished. total time: 0.015s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX1-CUST 9.1.0.13(C432)
OKAY [ 0.014s]
finished. total time: 0.014s
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
OKAY [ 0.014s]
finished. total time: 0.015s
fastboot oem battery_present_check
(bootloader) 3521mv
OKAY [ 0.015s]
finished. total time: 0.017s
I really need to recover the internal data of this phone.
Any ideas?

May be reading the article linked to below helps
Download Huawei USB Driver for Windows (Latest Driver)
Download the latest and original Huawei USB Driver to connect any Huawei Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
The ADB driver you use is meant to be used on Google devices onlly

Thanks xXx yYy but it doesn't work.
The drivers for Huawei P20 ANE-LX1 found on this website seams also meant to be used on Google devices...
I already tried this one.
I tried once again.
I followed the androidmtk.com's guidelines to install the driver (add legacy harware). And as you can see, it appears well in my devices manager.
The second one, without yellow warning sign, is the one appearing when I plug the phone on my computer.
But even after a computer and smartphone reboot, I am still not able to see any device with the adb devices command.

Have you ever USB Debugging enabled on Android device?

xXx yYy said:
Have you ever USB Debugging enabled on Android device?
Click to expand...
Click to collapse
How could I?
I can't start the phone correctly, never had a chance to go into the Android menus/apps.
A normal start leads to this screen:

A serious Android user does this when he first operates his Android device.

xXx yYy said:
A serious Android user does this when he first operates his Android device.
Click to expand...
Click to collapse
It doesn't help me

Question Unable to install TWRP after rooting Redmi Note 11 Pro 5Gv(veux)

Hello all
I have used the information on here to successfully root my phone (Redmi Note 11 Pro 5G - veux) via magisk but I would like to put TWRP on it however whenever I try to boot the recovery image it does not work. Below I will include the mod el and info of my phone and also the output message of powershell, if anyone can tell me what I am doing wrong that will be great.
{
"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"
}
I did my flashing with the official mi flash tool to root with magisk but this screenshot from a different author seems to show the information you may need to help me nicely.
Here is the output from powershell when I try to boot the unofficial version I found named "360 pissarro RN 11 Pro+ pjgowtham" which says its for veux but I'm not getting much success.
I have flashed successfully and the drivers seem to be ok and list the device in "fastboot devices" and it is in USB developer mode but other than that I can't figure out why it wont't boot the recovery img so I can install TWRP
I will be eternally grateful if someone can tell me what I am doing wrong or what the actual correct file is
PowerShell Output:
PS C:\Users\Steve\Desktop\platform-tools> fastboot boot C:\Users\Steve\Desktop\recovery.img
downloading 'boot.img'...
OKAY [ 1.086s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.101s
PS C:\Users\Steve\Desktop\platform-tools>

Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img

No Sir, but I will try it right now

friend.evil said:
Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!

tehnooks said:
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!
tehnooks said:
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!
Click to expand...
Click to collapse
EDIT: AGAIN
Click to expand...
Click to collapse
Didn't actually work now it's just stuck on the FASTBOOT screen
Heres what I got:
C:\Users\Steve\Desktop\platform-tools>fastboot flash boot recovery.img
Sending 'boot_a' (38418 KB) OKAY [ 1.031s]
Writing 'boot_a' OKAY [ 0.147s]
Finished. Total time: 1.454s
Am I using the wrong set of adb files to flash it with? Im using the platform tools from the android sdk

friend.evil said:
Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Tried flashing both boot_a and boot_b but still just ended up stuck on the fastboot screen

Had the same problems first, use command Prompt instead of powershell and make sure drivers are updated.
If you need twrp to install a new Rom follow these steps.
First type: fastboot getvar unlocked to check if it's unlocked.
Second Step is to download 2 Firmwares ( one updated and one slightly older ) from here
Flash up to date Firmware ( Slightly older is downloaded incase there are issues ) and boot to system, enable adb in developer options then use magisk to root phone, flash patched boot img with: fastboot flash boot patchboot.img
Edit: To flash a firmware follow this link and look at 2nd post if software isn't opening ( copy adb files to folder before using flash_all.bat )
After your phone is rooted and you made sure it was functional flash twrp: fastboot flash boot twrp12.img
Go to recovery mode, if the phone doesn't respond with touch display insert a usb c hub and add a mouse.
Download Encryption Disabler from Here and go to adb sideload and install it with adb sideload, next step is to install a Rom.
Mount Everything and wipe data then install Rom with ADB Sideload. ( ArrowOS is good ). Flash ROM then Gapps.

friend.evil said:
Had the same problems first, use command Prompt instead of powershell and make sure drivers are updated.
If you need twrp to install a new Rom follow these steps.
First type: fastboot getvar unlocked to check if it's unlocked.
Second Step is to download 2 Firmwares ( one updated and one slightly older ) from here
Flash up to date Firmware ( Slightly older is downloaded incase there are issues ) and boot to system, enable adb in developer options then use magisk to root phone, flash patched boot img with: fastboot flash boot patchboot.img
Edit: To flash a firmware follow this link and look at 2nd post if software isn't opening ( copy adb files to folder before using flash_all.bat )
After your phone is rooted and you made sure it was functional flash twrp: fastboot flash boot twrp12.img
Go to recovery mode, if the phone doesn't respond with touch display insert a usb c hub and add a mouse.
Download Encryption Disabler from Here and go to adb sideload and install it with adb sideload, next step is to install a Rom.
Mount Everything and wipe data then install Rom with ADB Sideload. ( ArrowOS is good ). Flash ROM then Gapps.
Click to expand...
Click to collapse
Which is the most suitable twrp image to use? I cant find one for veux or one named twrp12.img
Thanks!
EDIT: found it at https://drive.google.com/file/d/1-2_8YAfnWgvoRxIecDtN6JBRYWRKq8Ii/view
Thanks a lot it boots the twrp fine now