Database Info

[APP]Simple Recovery Switcher

I made this app because I got sick of flashing stock recovery when a GPE OTA came, and then flashing back to a custom. I also wanted to cut my teeth on Android App Development so here it is. My first app..
Description
Must have ROOT and Busybox installed.
Instructions:
To use the one tap method:
1. place a custom recovery on your internal SD card and name it "custom.img"
2. place a stock recovery on your internal SD card and name it "stock.img" (without quotes, case matters)
3. Once they are on your internal card you can just tap "Custom" to flash to custom recovery or "Stock" to flash back to stock recovery.
To flash any recovery on your device:
1. Press the floating action button on the bottom right side of the screen.
2. Select a .img file from either internal or external SD card
3. Confirm yes or no if you want to flash
*Support for more devices added besides just devices using Snapdragon SOC's
-Should support most Terga devices
-Should support most Snapdragon devices
-Should support most Exynos devices
Play Store Link: https://play.google.com/store/apps/details?id=com.graffixnyc.m8recoveryswitcher
Donate version: https://play.google.com/store/apps/details?id=com.graffixnyc.simplerecoveryswitcherdonate

reserved

Awesome
Let me try on my Moto
regards

This looks really cool and handy. Great job! I wish that I could use it on my Note 3. Damn!

This'll be one to watch...

hi, great app, a really needed one! i just bought a donate version to spupport you.
still i have a few questions:
1. on my HTC One SV the path is slightly different as it should be: /dev/block/platform/msm_sdcc.1/by-num/recovery structure (by-num instead of by-name) is this a typo from your side or i have an unsupported device? if so, could you add support for my device's recovery path to your app?
2. i still have the original factory recovery on my device (which is rooted and with busybox). will your app work if i've never installed custom recovery on this device before?
3. does the bootloafer need to be unlocked?
thank you!

graffixnyc said:
You MUST place a stock recovery img and a custom recovery(of your choice) img onto your INTERNAL sd card(if you have both internal and external). Name them stock.img and custom.img (case matters)
Click to expand...
Click to collapse
The problem for me (I also have an HTC One M8) is that each OTA seems to come with a new recovery image (or it looks like a different version to me). I usually keep a copy of the OTA after download, but before applying it, then extract the new stock recovery from that so I can flash back the latest stock version after doing all my custom recovery stuff. I can't see how your app gets around the need to do that. Or am I missing something simple (and owe you an apology).

clarkg said:
The problem for me (I also have an HTC One M8) is that each OTA seems to come with a new recovery image (or it looks like a different version to me). I usually keep a copy of the OTA after download, but before applying it, then extract the new stock recovery from that so I can flash back the latest stock version after doing all my custom recovery stuff. I can't see how your app gets around the need to do that. Or am I missing something simple (and owe you an apology).
Click to expand...
Click to collapse
I guess that the whole purpose of this app is to bypass the adb PITA where you need PC access to flash stock recovery to get the OTA, then adb fastboot reflash custom recovery etc. You can then always replace the stock recovery on your internal SD card with the latest version from the OTA.
---------- Post added at 10:45 PM ---------- Previous post was at 10:24 PM ----------
@graffixnyc, I really like the idea behind this app and want to buy it, but just to be clear, and it's not mentioned anywhere, is it ok for HTC One M8 Sense version? I don't know much about the partition structures.

I'm sure this is a stupid question, but in what directory can i find the stock recovery.img so i can use your app? I am currently using Philz but i thought that KitKat 4.4.3 came with it's own recovery image so it must be stored somewhere?

I hope this works on Moto e as it uses the Same path as you mentioned above. @graffixnyc

Can we use this app for M7 devices?

hey guy!
how to know that our devices using "/dev/block/platform/msm_sdcc.1/by-name/recovery" structure.

Does this work on verizon lg g2

Thank you, this works great on my Nexus 4.

Hi, really great job !
Does it work with multirom ?
Thanks

Moto G
Working fine on the Moto G (Snapdragon 400) with TWRP 2.7.1.1.
One sugestion: Could you add 2 options to flash custom recoveries? In this way we could switch between STOCK X CWM X TWRP.
Great work!

danilocps87 said:
Working fine on the Moto G (Snapdragon 400) with TWRP 2.7.1.1.
One sugestion: Could you add 2 options to flash custom recoveries? In this way we could switch between STOCK X CWM X TWRP.
Great work!
Click to expand...
Click to collapse
I think that would be a pretty good idea actually. Be sure to support him with the donate version and drop the suggestion to him personally if you dont get a reply here

I must be missing something.... Does it matter where I place the stock.img and custom.img? I have both of them on my phone, ran the app without issue, selecting Stock. But when it reboots it still goes into CWM.

GoPadge said:
I must be missing something.... Does it matter where I place the stock.img and custom.img? I have both of them on my phone, ran the app without issue, selecting Stock. But when it reboots it still goes into CWM.
Click to expand...
Click to collapse
This was in the homepage article
The application should work as intended on every Qualcomm device that uses the*/dev/block/platform/msm_sdcc.1/by-name/recovery*structure and is rooted with Busybox installed. Recoveries must be named stock.img and custom.img and must be placed in the root folder of your internal SD Card.*Before using this tool, double check everything, since messing with recoveries may result in*a bricked device.
Click to expand...
Click to collapse

jbnorton0524 said:
This was in the homepage article
Click to expand...
Click to collapse
Sorry about that... I missed the one word "root" in root folder. Now I get the Dead Android with Red Triangle when I try the stock recovery.
(But I can switch back to the CWM one with no trouble.)

Team Win Recovery Project for the LG G Pad X 8.0 (V521, V522, V525)

[RECOVERY] TWRP 2.8.7.0 - TeamWin Recovery Project
TeamWin is proud to present TWRP v3.0.2.0 for the LG G Pad X 8.0 (V521, V522, V525)
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
b3 Device Config: https://github.com/Shabbypenguin/android_device_lge_b3
DOWNLOAD:
http://www.t2h-gh0st-is-garbage.xyz/TWRP-V521-3.0.2.0.img
Support:
Only ask for support in the chat for general twrp issues, not device specific problems.
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers[/QUOTE]

8/21/2016
updated the link, same file name fixed internal storage mount and a few other minor issues
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.

Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?

shabby is the man

emilyrugburn said:
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
Click to expand...
Click to collapse
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.

shabbypenguin said:
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
Click to expand...
Click to collapse
Xposed looks to work just fine. Thanks again

emilyrugburn said:
Xposed looks to work just fine. Thanks again
Click to expand...
Click to collapse
glad to hear it
i grabbed the tablet as it was a great deal and ive loaded it up with apps for my daughter who is the primary user for it so i wont be doing much with it but its good to see the community finally taking off .

Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them

avishah395 said:
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
Click to expand...
Click to collapse
there is a donate to me button under my name and those instructions dont apply to this device. i specify how to use this in the second post.

IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.

avishah395 said:
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
Click to expand...
Click to collapse
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number

shabbypenguin said:
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
Click to expand...
Click to collapse
I'm not entirely sure about clearing encryption to use TWRP. I know when I did it, TWRP functioned normally.
Ill ask XDA about the ET, maybe it has a second page that isn't showing.
UPDATE: To add our tag, look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443944}. Our ET/tag is "lg-g-padx"

If it could be made as flashable .dz or .tot, that would be excellent.

mingkee said:
If it could be made as flashable .dz or .tot, that would be excellent.
Click to expand...
Click to collapse
as previously mentioned, only people who have leaked lg tools can make flashable tots etc. i spent hours researching it, testing out different methods and reflashing stock kdz a bunch of times.
the only way i could streamline this is if i submitted this to be made official so once rooted you could use twrp manager, but the submission process isnt exactly one that is a lot of fun to do. especially considering with flashify you only have to do like 3 clicks anyways.

Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.

eriklion said:
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
Click to expand...
Click to collapse
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?

shabbypenguin said:
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
Click to expand...
Click to collapse
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0

Confused About Install Instructions
shabbypenguin said:
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Click to expand...
Click to collapse
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.

pressmoon said:
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
Click to expand...
Click to collapse
you need to go to wipe > format data. your devices data is by default encrypted and twrp cant decrypt it. once youve wiped data, reboot recovery and then do a factory reset. your device will boot and function as normal and youll have a fully working twrp

eriklion said:
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Click to expand...
Click to collapse
ive uplaoded a version taht fixed that, but im unable to mount external_sd or usb otg. sda1 doesnt show up for me in /dev/block and even manually trying to mount sdcard to mccblk1p1 fails due to an invalid arguement, how did you mount yours?

Data Partition Encryption

Hey all,
I unlocked bootloader, installed TWRP and installed Magisk just fine.
As far as I was aware, I had disabled encryption on the sdcard, and this makes sense as I flashed Magisk from its installation zip in my sdcard.
However, I just rebooted to recovery in order to make a backup
It prompts me to input password in order to decrypt data.
I don't need to input password, I can click cancel and get to TWRP, but then, using its file manager, I see that all file names are in gibberish. Obviously the personal data Partition is also read only
I don't know how it got encrypted, and it was after I installed Magisk from sdcard, showing it was not encrypted at some point.
Well I can't make a TWRP back in this state.
Anyone know how it got encrypted again and how to undo that so I can make backups?

for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.

Ajaykumar21066 said:
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Click to expand...
Click to collapse
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone. ?
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs

drakenabarion said:
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone.
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
only change was you didnt have any lockscreen pin setup on your phone, And now you have one i think. its the same pin twrp is asking for.

Ajaykumar21066 said:
only change was you didnt have any lockscreen pin setup on your phone, And you have one i think. its the same pin twrp is asking for.
Click to expand...
Click to collapse
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison! ??
Sent from my OnePlus 6 using XDA Labs

drakenabarion said:
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.

Ajaykumar21066 said:
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Click to expand...
Click to collapse
The important thing for me now is that I have a stable backup. It can take me days to setup a new phone to my comfortable default setting, so now I feel secure that I have a saved image of my idea of a good install. So thank you for helping with that!
But it will be interesting to see how custom roms not based on OOS will be.
Up until my last phone (Honor 6x - proprietary soc, therefore limited rom support), I would flash a custom rom ASAP (typically LineageOS or before that, CyanogenMod). But I already get that kind of experience (with good historical reasons I guess) from OOS. It would take a bit to tempt to flash something else. ?
Sent from my OnePlus 6 using XDA Labs
And might I just say that woohoo for large storage! My previous 32gb phone took 10 gb for firmware and left me struggling after installing a normal set of apps, typically leaving me about 10gb to put music etc into. My backup that I just made took 18gb, because I installed alot of games I couldn't before, is bigger in general than base free space before!

A buggy twrp for A60, but not sure for M40.

I have made and got a buggy twrp for A6060, which is the Chinese version of M40, based on android-11. It can startup but lacking mtp and usb. It can't decrypt the /data too so you should do some preparations before can use it. I am not sure whether it can be used on M40.
Usage in shorts:
① Magisk and root. You can find the guide in this forum so I will pass it.
② Using a file manager to access /system/vender/etc/fstab.qcom, in the part of /userdata delete the field of "fileencryption=ice" (usually sth. like this, not includes the quotation marks), same and quit.
③ Enter recovery and wipe data. Then use odin flash this recovery: Just zip it to .tar file then flash in the AP slot.
④ When startup, press VOLUMN UP ＆ POWER. If everything goes well, you will see the logo of twrp and enter it and can successfully access the files in /data. Then you can copy some gsi and have a try.
Click to expand...
Click to collapse
Hope it will be helpful and I really hope somebody can make it a ture and full device tree. That will definetely benefit both A60 and M40 users.
The twrp for A60: https://github.com/Jason-summer/Action-Recovery-builder
The source of the twrp: https://github.com/Jason-summer/device_samsung_a60q/tree/android-11
Sorry for my poor English if causing someone confused.

good job! Is it possible to flash a phone using this? (i have a60)

blankkk123 said:
good job! Is it possible to flash a phone using this? (i have a60)
Click to expand...
Click to collapse
It works for me. But you should decrypt your phone first before you try to flash sth. or you may found /data a pile of random code.

SummerElement said:
It works for me. But you should decrypt your phone first before you try to flash sth. or you may found /data a pile of random code.
Click to expand...
Click to collapse
If it's not difficult, can you please write instructions? I think this will help many who want to flash

How To Guide Installing a custom recovery, and disabling encryption in the system.

Hello everyone.
If you want to have a recovery with the ability to backup/restore, this instruction is for you.
Here are recovery, while they do not know how to encryption of data section (I hope we will have such ones sometime).Yes, recovery already patched by magisk 25.2
Download the patch, copy it to the SD card (if you have it) or to a USB flash drive, for firmware by otg.
We set the recovery in fastboot mode with the command:
fastboot flash boot (recovery name).img
We load into the recovery, flash the patch, and make FORMAT DATA.
Attention!!!This will delete all your settings and installed programs, including deleting everything from the internal memory.
After that, we boot into the system, configure and "rejoice", now the recovery will see data and, accordingly, internal memory.
And yes, if you have a security thing, this procedure disables the encryption of your data
COMPLETELY, THAT IS, COMPLETELY.
Oh, I forgot, although I think it's clear by the name of the recovery, they (recovery) are designed for firmware on Android 12.
Download files:
RECOVERY

Guys, one jamb got out here, my system has been transferred to RW, and I checked the script on such a system. As it turned out, the script does not work on the stock system. So, in order for it to work normally, you need to first transfer the system to RW

Any chance to explain step by step?

reosm said:
Any chance to explain step by step?
Click to expand...
Click to collapse
What exactly?
In the post everything is written as to put.

There are 2 img in the recovery file, which one will be loaded before or after

reosm said:
There are 2 img in the recovery file, which one will be loaded before or after
Click to expand...
Click to collapse
one is TWRP recovery and the other is Orange Fox recovery, choose which one you want to use, just flash one of them.

Hey does twrp/orangefox actually work on this phone. I've heard that those are currently under development. And does flashing these .img require wipe data or can they work with sd card or OTG?

Soma Das said:
Hey does twrp/orangefox actually work on this phone. I've heard that those are currently under development. And does flashing these .img require wipe data or can they work with sd card or OTG?
Click to expand...
Click to collapse
Recovery can work with both sd and otg. While they cannot decrypt the data, but if you transfer the system to RW, and flash the patch to disable encryption in the system, then everyone will see the recovery.

Who has a system in RO, you can use these, checked, it also works
[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"
Disable Force Encryption NEO Do you all know what DFE is? no? Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption: -...
forum.xda-developers.com

arraki said:
Recovery can work with both sd and otg. While they cannot decrypt the data, but if you transfer the system to RW, and flash the patch to disable encryption in the system, then everyone will see the recovery.
Click to expand...
Click to collapse
Can it backup anything such as boot.img, vendor etc?

Soma Das said:
Can it backup anything such as boot.img, vendor etc?
Click to expand...
Click to collapse
Probably you can, but why. A backup of the datа section is enough for normal recovery. Of course, you can also make a backup of the super section if you changed something in it.

arraki said:
Probably you can, but why. A backup of the datа section is enough for normal recovery. Of course, you can also make a backup of the super section if you changed something in it.
Click to expand...
Click to collapse
Do I need to flash disable dm Verity?

Soma Das said:
Do I need to flash disable dm Verity?
Click to expand...
Click to collapse
In the first post, everything is written.

does it work for Mediatek cpu install on the Note 11 pro plus 5g?

Christ_soyo said:
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Click to expand...
Click to collapse
MediaTek chip on is Redmi note 11 pro. It wilont work and you will get soft brick.

Christ_soyo said:
does it work for Mediatek cpu install on the Note 11 pro plus 5g?
Click to expand...
Click to collapse
What exactly works?

Do we need to unlock the bootloader firtst before we flash the recovery, right?

derjango said:
Do we need to unlock the bootloader firtst before we flash the recovery, right?
Click to expand...
Click to collapse
Of course

After using this patch my device doesn't know how to be case sensitive, which makes some apps have weird errors with read and write functions

nimade2333 said:
After using this patch my device doesn't know how to be case sensitive, which makes some apps have weird errors with read and write functions
Click to expand...
Click to collapse
This is clearly not because of the patch, I have put it on for a long time, and there are no problems. Yes, and he only disables encryption in the system, how can he influence this.