Database Info

[RELEASE][06/01/2011] ClockworkMod Recovery - current version - 3.0.0.5

Hi all, I thought to open this thread to keep all users updated to all the new release of the ClockworkMod Recovery for our Desire.
Current version: 3.0.0.5
FakeFlash zip for S-ON users
recovery-clockwork-3.0.0.5-bravo.zip
Flashable image for S-OFF users
recovery-clockwork-3.0.0.5-bravo.img
MD5: 0bd2a55504dd70641feb9c9b3ba5b1da
SHA-1: 0b6e77dedd8b954817d7210bf77c55f38da82278
Old versions:
2.5.1.8 (.zip - .img)
2.5.1.2 (.zip - .img)
2.5.0.7 (.zip - .img)
Changelog:
2011-01-06
fix /sd-ext wipe
fix android secure formatting
Add the volume command for seeing the current recovery.fstab. Support crazy HTC chargemode.
Refactor nandroid so the availability of boot backup is determined automatically. Boot backups are also no longer assumes to be on raw partitions, as they may be on a VFAT partition or someting different, such as in the case of Nook.
3.0.0.4. Provide an error message if an Amend zip is provided.
readd ext2/ext3 format support.
fix executable bit on e2fsck
Support for ext2 and ext3 update-binary.
2010-12-15
fix no select button
Added options for an internal SD card to be handled by recovery.
Exable uses in BoardConfig.mk:
BOARD_HAS_SDCARD_INTERNAL := true
BOARD_SDCARD_DEVICE_INTERNAL := /dev/block/mmcblk3p1
Setting BOARD_SDCARD_DEVICE_SECONDARY to the same value as
BOARD_SDCARD_DEVICE_INTERNAL will allow the device to
"fall back" to the internal SD card for other actions.
recovery: Remove condition around get_root_mtd_partition
Refactor recovery's block device handling to work across variant hardware in a cleaner fashion.
Fix write_raw_image on mtd devices.
Fix graphics corruption on some devices. BML restore needs to unlock first.
fix up bmlutils some more
2010-11-12
Supress "warning: comparison between signed and unsigned integer expressions" in minui/resources.c and mtdutils/mtdutils.c
2010-11-11
implement bmlutils
fix up implementation of int get_partition_device
Modify apply_patch to fail if trying to patch mtd on non-mtd devices.
Warning: Don't make a backup with Amon_Ra's recovery and restore it with ClockworkMod Recovery and vice-versa, you may USB brick your device.
{
"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"
}
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!

reserved for me.

I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers

unie said:
I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers
Click to expand...
Click to collapse
Fastboot.
Remember to S-Off.

2 newer version of recovery mod in one day
hard to choose between them
tnx for updating bro

wow thx pal for this, great staff =]

So, does it work with bravo-recovery-v1.5.3-CustomMTD.zip from http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1?

Narfx said:
So, does it work with bravo-recovery-v1.5.3-CustomMTD.zip from http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1?
Click to expand...
Click to collapse
Me also this interests.

as we all see, a clockwork is a one step ahead

does this have SLCD support?

Works fine here
Sent from my Desire with Oxygen, @XDA App

unie said:
I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers
Click to expand...
Click to collapse
both methods is working...

I have rom manager prem installed won't it auto update the recovery?

How do I setup?
Good day to you all ... How will everyone?
I wonder which of the 2 files I download to install and if I flash normally files?
How do I setup?
Thank you!

Pajorve said:
Good day to you all ... How will everyone?
I wonder which of the 2 files I download to install and if I flash normally files?
How do I setup?
Thank you!
Click to expand...
Click to collapse
as i see you are s-off so you can't use fake flash method,download the img file (the second one) so u just have to burn the recovery with unrevoked flasher tool, or the android flasher tool both are good and working.
soz i don't have time to search links, i think if u go a little down by pages u will find the android flasher.

Go to your "old" ClockworkRecovery and apply Update.zip
Worked fine for me!

goodmorning to you all.i've tried update through recovery but it didn't do it.it says 2.5.1.2 then the menu for reboot and after reboot still 2.5.0.7

konn4312 said:
goodmorning to you all.i've tried update through recovery but it didn't do it.it says 2.5.1.2 then the menu for reboot and after reboot still 2.5.0.7
Click to expand...
Click to collapse
I get this too. When I'm actually in recovery the version number is 2.5.1.2, but ROM Manager reports the version number as 2.5.0.7. ROM Manager also says the latest version is still 2.5.0.7. I guess it's ROM Manager that's wrong, rather than the actual recovery.

help
i did a backup using nandroid on this new recovery and now im in a bootloop...need assistance...

Why did you alter the source before you built it? You added your own name to the recovery screen, while I don't see that you changed or added any functionality of the recovery. Your changelog is identical to the github logs.

[RECOVERY][July25] TWRP 2.7.0.0 Touch Recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 2.7
Introduction:
Team Win Recovery Project 2.7, or twrp2 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.
Screenshots:
Phone look:
Tablet look:
​
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
Changelog for LG P500:
20140311
SELinux functions support
Android 4.4.2 support
20140406
USB Mass Storage mounting
Display brightness and timeout settings working
20140725
TLS support
Swap /system and /userdata
Installation:
Flash the ZIP file in your existing recovery to install TWRP.
Credits:
AndroidMeda
TeamWin
Source Code:
Github

Will i be able to backup/restore SD-ext2 (link2sd) partition?

ujilraj said:
Will i be able to backup/restore SD-ext2 (link2sd) partition?
Click to expand...
Click to collapse
I can use to backup/restore SD-ext4

will it work when i try to flash android 4.3 and prior Roms or just 4.4 only?

thanks bro for 2.7.0.0.

Downloading.
Thanks
Sent from my LG-P500

thanks bro.,

I got reboot when I restore backup.

delete

Version for Odin?
Can't install Goo manager on this old phone because the stock ROM is too old. Froyo! And there is no newer software available!

james.faction said:
Version for Odin?
Can't install Goo manager on this old phone because the stock ROM is too old. Froyo! And there is no newer software available!
Click to expand...
Click to collapse
I have never used Odin on an LG device. As I understand it's widely used by Samsung owners. But there are other methods that I am familiar with. If you are able to access fastboot mode on your rooted LG P500 device, you could extract the zip, and use AndroidFlashRecovery:
http://forum.xda-developers.com/showthread.php?t=1827723
to flash recovery.img. Also there is a simple installation script that I use in terminal emulator:
http://www.mediafire.com/download/7baf5u85iah4fa0/rec.zip
Download and extract the zip into the root of your sdcard so that the path is /sdcard/rec. Copy desired recovery.img to the rec directory, overwriting the one that is already there. DO NOT RENAME RECOVERY.IMG. Install a terminal emulator from play.and start it. Type "su" (without quotes) and enter. Superuser prompt should appear. select allow. now type "sh /sdcard/rec/rec.sh" (without quotes) and enter. Phone will reboot into your new recovery.

TWRP 2.7 July25
New version compatible with latest jenkins builds is out.
Changelog:
20140725
TLS support
Swap /system and /userdata

Error executing updater binary in zip '/data/OldBBBFix_signed.zip'
I'm getting "Error executing updater binary in zip '/data/OldBBBFix_signed.zip'"
The OldBBBFix_signed.zip file is a flashable file which allows to flash an old baseband.
As you can see I try to install it from /data/
It won't work in this way or with sideload.
If I remember correct it wen't pretty well on ClockworkMod when the zip was on sd-card.
But now I need TWRP since I don't have sd-card and CWM allows to flash only from sd-card...
Any suggestions?
Edit: never mind. I just found this:
Tasssadar said:
OLD UPDATE-BINARY (error executing updater binary in ZIP)
P500 is fairly old device, so it is quite possible that some ROMs use old update-binary in their ZIP files, which is not compatible with TWRP. This is not a bug, rather a design feature - TWRP simply does not use such old parts anymore.
You can fix the ZIP by yourself. Download correct update-binary and put it to folder META-INF/com/google/android/ in the ZIP file. You should see previous update-binary in there, just overwrite it.
The binary affects only the ZIP file, nothing else - it is used only to install the contents of the ZIP file.
Click to expand...
Click to collapse
Sorry for posting before doing a thorough research.
@HardLight, I really think you should edit the first post with this information.

[UPDATE-v3.3][PORT][RECOVERY] Carliv Touch Recovery For Iris458Q/XOLO-Q600/CROSS A88

This is the port of Carliv Touch Recovery v3.3 based on latest ClockWorkMod 6.0.5.1 for LAVA Iris458Q
{
"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"
}
This is kitkat based recovery and has full SELinux support .Since LAVA iris458Q , XOLO Q600 and CROSS A88 are similar (clone) devices . This recovery should work on these devices . Test at your own risk . And always have a backup before flashing anything .
NOTE: Don't use this recovery on any other device except above specified devices !!!
Changelog by Master Carliv
Version 2.7 update (11-dec-2014):
- rebuilt from base (cwm 6.0.3.7) and add improvements on top.
- reintegrated bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- better compressed backups integration - pigz support from cm-11
- new "nvram backup/restore" menu functionality: the nvram partition will be backed up in clockworkmod/backup/.nvram/nvram-xxxxx folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition defined in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- the recovery has now an increased stability, many issues are solved
- the content of the backup folder will contain only what an usual clockworkmod backup contain, and that will make it easy to restore backups made with older versions.
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
- some other changes.
Click to expand...
Click to collapse
Version 2.5 update (29.06.2014):
- cleaned up the source code
- removed "wipe all" option from wipe menu (too many users wiped their system and blamed me); if you need to wipe system, use "format system" from "mounts/storage"
- rearanged menu order in root menu to restore CWM order
- added a "nvram backup/restore" menu in "carliv" section: the nvram partition will be backed up in clockworkmod/backup folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition of size 0x500000 (check your scatter) and if you have the nvram defined as /dev/nvram path in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- some other small changes.
Click to expand...
Click to collapse
Version 3.3 last release (21-apr-2015):
- based on cwm (cwm 6.0.5.1) and added improvements on top.
- bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- many fixes in code;
- cleaned up the source code;
- reset battery stats option;
- wipe all - preflash option;
- removed nvram backup/restore because it can corrupt the bootloader;
- a new advanced backup/restore menu
- separate power and wipe menu
- aroma file manager integration (you can flash the attached AromaFM_installer.zip in recovery, and that will place the aromafm.zip at its place).
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
Click to expand...
Click to collapse
Some screenshots of Recovery
​
DOWNLOAD:Check the attachments-for older JB stock kernel based and for new-Drive​
Installation:
First rename the file to recovery.img then for
Mobile -> copy to sd card and flash using Mobile Uncle Tools.
or
PC -> Use SP Flash to flash it to phone.
or
For latest version directly flash the recovery zip in custom recovery or extract recovery.img and follow above methods.​
Kernel Source:GitHub​
Credits:
@Doha for his KK kernel
@carliv for his awesome recovery
@carliv for his user friendly guide
@Koush for his amazing CWM recovery
@Napstar for his full touch modules
@bgcngm for his unpack/repack utils
@sk8erwitskil for aromafm menu​If anybody missed PM me​
If you have Mediatek MTK android and your model is not listed anywhere in xda and if you want a custom recovery use MTK droid tools for windows or click on below links to port a custom recovery for your device.
http://forum.xda-developers.com/showthread.php?t=2648309
http://forum.xda-developers.com/showthread.php?p=46206519
http://forum.xda-developers.com/showthread.php?p=52851128
http://forum.xda-developers.com/showthread.php?t=2759981
http://forum.xda-developers.com/showthread.php?t=2201860

[OTA] ADB-Enabler - Flashable UPDATE.ZIP File

{
"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"
}
This tool is not meant to be used on Android devices with dm-verify or Android Verify Boot (AVB) enabled
Every Android device has a stock recovery installed. That default recovery typically at least offers you the 4 options
reboot system now
apply update from sd card
wipe data factory reset
wipe cache partition
thus you can place any valid update.zip in device's SD-card slot and update your Android from external SD-card.
Because being in recovery mode Android isn’t loaded, the Android system files are not placed in memory, which means they can be accessed, edited and replaced.
That fact allows Android users to enable ADB on their devices what natively support ADB, if they haven't done it yet, for whatever reason.
Download the signed ADB.Enabler.OTA.ZIP from here . IMPORTANT: Rename it to UPDATE.ZIP before you make use of it.
If you get error "Signature verification failed" means that OEM/Carrier blocked to flash a 3rd-party OTA. You would need to have a Custom Recovery like CWM/TWRP already installed and use that to flash the ADB.Enabler.OTA.
HTH

link not working

I am looking for zip that can enable usb-debugging and disable RSA keys without touching /data (encrypted/not mountable):
- boot.img
- system.img A-only SAR system-as-root device
I tried modifying build.prop and default.prop manually but it seems adbd is not running at all

got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK

aIecxs said:
got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK
Click to expand...
Click to collapse
is root required?

No root required. Magisk is recommended for easy avb/dm-verity disable, but of course one can also place the files manually by unpack/repack (simg2img/sdat2img) flash tool method.

optional:
- copy sqlite3 binary to SD Card
(get it from here credits: @DiamondJohn)
- copy Magisk-v23.0.apk to SD Card
(credits: topjohnwu you all know of course)
have added example code in userinit.sh that can authorize su permissions for adb shell. useful on broken screen in case one can't get scrcpy to work on boot-loop
(credits: @mirfatif for magisk.db injection)
rsa_copy works also from emulated storage if one edit the path in first line:
Code:
sdcard=/sdcard
on locked screen external MicroSD Card is only available location as MTP might not work. in that case place files from PC card reader and insert back
remember the whole purpose of that backdoor is inaccessible userdata partition, otherwise one could just add rsa_copy or 99userinit_daemon to /data/adb/service.d systemless-ly instead (or most straightforward inject /data/misc/adb/adb_keys directly).
once got su shell one can backup partitions, for example:
Code:
adb shell su -c "cat /dev/block/dm-0 2> /dev/null" > userdata.img
edit: visit main thread for more discussion
https://forum.xda-developers.com/showthread.php?t=2965462

FIX THE LINK

@AlinTecsan​So let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update fron SD card" and that will be all?

helen2 said:
@AlinTecsan​So let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update frn SD card" and taht will be all?
Click to expand...
Click to collapse
i didnt try yet i need this file this is gone as a cloud

AlinTecsan said:
i didnt try yet i need this file this is gone as a cloud
Click to expand...
Click to collapse
me to maybe I will sort ut all my troubles let we wait post is quite old :/

This won't work on stock recovery anyway, it's for custom recovery only

[TWRP][RECOVERY]TWRP 3.6.1_9-0 for LG G7(judyln)

TWRP 3.6.1_9-0 for LG G7 judyln
Build Date:2022-02-28
Tested on LM-G710N LGT,crossflashed to G710EM30f Open
Requirements:
1.Unlock your bootloader
2.Magisk or another version of twrp or ofox
Downloads:
TWRP installer: https://drive.google.com/file/d/1-PL9dJtEsQJiDVAqzKrMK_hT32ZKqf7h/view?usp=drivesdk (Recommend)
**I will not provide TWRP img file because it couldn't boot**
Device tree: https://github.com/LameMonster82/android_device_lge_judyln-twrp/tree/android-9.0
Installation:
Method 1:
1.Download TWRP installer
2.Install TWRP installer as a magisk module in magisk app and flash magisk again(or you will lost root)
3.Reboot to recovery and enjoy
Method 2:
1.Download TWRP installer
2.Reboot to recovery(such as twrp or ofox)
3.Install TWRP installer as a flashable zip and flash magisk again(or you will lost root)
4.Reboot to recovery and enjoy
Working:
Install ZIP
Install Image(and Flash to both slots)
Backup ＆ Restore (Expect for modem,will appear:Error opening:' '(No such file or directory)")
Mount:System,Vendor,Firmware,Micro SD card,Data(You should decrypt data first)
MTP
ADB (sideload)
etc......
Not Working:
Auto decrypt (May not work,I didn't test it because my data already decrypted)
Backup ＆ restore modem partition
USB OTG(May not work)
U tell me
If there is "E:Error getting bootctrl module" appeared over and over again,just ignore it or reboot TWRP
Spoiler: Screen shots
{
"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'm sorry because I've never used Google Drive before, so I set wrong permissions when sharing files, you need to send me a request to download files, and I didn't notice that Gmail and Google Drive’s notifications so that you have trouble downloading files, and the file sharing permissions have been modified. sorry again

Cheers mate I'll give this a try.

tried on europe android 10 30h, could not mount data.
i am trying to disable verity but this rom did not have fastboot. any help?

tolong_saye said:
tried on europe android 10 30h, could not mount data.
i am trying to disable verity but this rom did not have fastboot. any help?
Click to expand...
Click to collapse
(All of your data will be lost)You should prepare a SD card but not USB-OTG(because this twrp not supported),put disable dm verify and force encrypt flashable zip into your SD card,format data partition and flash that flashable zip and format data partition again,then reboot recovery.

HanCF1014 said:
(All of your data will be lost)You should prepare a SD card but not USB-OTG(because this twrp not supported),put disable dm verify and force encrypt flashable zip into your SD card,format data partition and flash that flashable zip and format data partition again,then reboot recovery.
Click to expand...
Click to collapse
i can mount after changing the data to ext2 then ext4. however, I will lose root.
when I try to flash the patched magisk boot image, even with the untick preserve encryption, I will get decrypt unsuccessful.
so I back to square one where I dont have access to oem/op folder. I really need it to paste the volte configuration.
any help?

tolong_saye said:
i can mount after changing the data to ext2 then ext4. however, I will lose root.
when I try to flash the patched magisk boot image, even with the untick preserve encryption, I will get decrypt unsuccessful.
so I back to square one where I dont have access to oem/op folder. I really need it to paste the volte configuration.
any help?
Click to expand...
Click to collapse
You can't mount data on stock rom unless you decrypt the phone.