Database Info

[RECOVERY] ClockworkMod Recovery 5.0.2.8 for vc088x tablets |v1.1b| 30-4-2012

ClockworkMod Recovery 5.0.2.8 unofficial port for Vimicro vc088x based tablets v1.1 beta by mikeNG a.k.a mikeioannina
Info:
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain 3e recovery and uses Edify scripting exclusively.
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
More info about creating your own update-scripts is here.
Disclaimer:
This is still experimental.
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR TABLET!
Some options might not work correctly and you might brick your tablet and/or lose your personal data!​
Features:
ADB root shell in recovery
Options:
Reboot system now
Apply update from sdcard
Wipe data / factory reset
Wipe cache partition
Install zip from sdcard
----Choose zip from sdcard
----Apply /sdcard/update.zip
----Toggle signature verification
----Toggle script asserts
----Choose zip from internal sdcard
Backup and restore
----Backup
----Restore
----Advanced restore
Mounts and storage
----Mount / unmount /sdcard
----Mount / unmount /emmc
----Mount / unmount /system
----Mount / unmount /data
----Mount / unmount /cache
----Format /sdcard
----Format /emmc
----Format /system
----Format /data
----Format /cache
----Mount USB storage
Advanced
----Reboot recovery
----Wipe Dalvik Cache
----Wipe Battery Stats
----Report Error
----Key Test
----Partition SD Card
--------Ext Size
--------Swap Size (Set this to 0)
--------Rest Size (vfat)
----Fix permissions
Power off
Requirements:
Basic skills in using adb or terminal emulator.
Installation:
It is recommended to do a clean install with this FlashTool first, then install the recovery image, so there is no problem with the sizes of the partitions of the internal sd.
1. Unzip the file you downloaded, you will get recovery.img
2. Copy recovery.img in your sdcard
3. Now type the following command in adb shell or in Terminal emulator:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p3
4. It will show a message after a while, it means it's completed
Usage:
1. Turn off the device
2. Turn on the device
3. When the boot logo appears, press immediately the menu button and hold it down for 3sec approximately.
Working:
Not everything is tested yet. You are the testers for the most of the things. I've tried a backup & restore, it worked. Also tried installing a modified kernel image, it worked too.
Known bugs:
Some errors about /cache are displayed when you boot, factory reset or wipe cache. They stop if you go every time under "mounts and storage" and you mount the cache partition.
Download links:
v1.1 beta for Haipad M8 1GB version
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"
}
Credits:
koush: for making this wonderful recovery
Cyanogen: for all the support for android
ilarrain & teamhacksung: the fixes for the 32bit framebuffer problems​

Changelog:
24-11-2011 / ClockworkMod Recovery 5.0.2.6 v1.0a
- Initial port for the M8
- Removed multiple "No" prompts in confirm dialogs
- Fixed screen update bug
25-4-2012 / ClockworkMod Recovery 5.0.2.8 v1.1b
- Ported latest CM7 Recovery
- Fixed 32bit framebuffer (multiple screens) problem. Now the image is perfect
- Capitalized first letter of all menus in the recovery
- Changed the color from default orange to default ICS blue on the menus
To Do:
- Add support for more vc088x based tablets

is this still working?

Terramoto said:
is this still working?
Click to expand...
Click to collapse
Yes but I lost the sources so I can't build anything new

how did you unpack that recovery img i am trying to make a CWM for my penta is703c tab same as haipad m8
but it dosnt work .....................i cam boot into CWM recovery but i cant read any of the options stated there.........

ss429842 said:
how did you unpack that recovery img i am trying to make a CWM for my penta is703c tab same as haipad m8
but it dosnt work .....................i cam boot into CWM recovery but i cant read any of the options stated there.........
Click to expand...
Click to collapse
I didn't unpack the image, I compiled from source. Unfortunately I lost the modified sources so I can't help you :/

[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.

[ROOT] Install Magisk on ZC551KL Guide "FINALLY"

This is a messy post, do as you please with it. I am not responisble for ang damage to your device. Additionally, I dont take any credits for any of this, I just put everything together here.
Tags zc551kl Asus Zenfone 3 Laser z01bdc
Tools Needed:
Asus Bootloacker Unlock Tool - http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZC551KL/UnlockTool_Android_M_0706_signed1.apk
You current boot.img version which can be downloaded from here [Its packaged in the update file]- https://www.asus.com/us/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_BIOS/
ADB and Fastboot from here [Credits to Snoop05] - https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Magisk Manager - https://tiny.cc/latestmanager
Prep:
Install the Asus Unlocker on your phone and unlock it.
Install Magisk Manager on your phone but dont run it yet.
Enable USB Degugging on your phone.
Install ABD and Fastboot on your PC. It will be installed to c:/adb/
Download the update that matches your phone version to your pc. [Mine was version "WW-32.40.106.41"]
Open the update file on your pc with your favorite zip manager and extract the boot.img .
Put the boot.img onto your phones internal storage.
Follow this guide [Credits to Dhananjay @ thecustomandroid.com]
» Non-rooted devices
Magisk 14.0 introduces a new and neat method to install on non-rooted Android devices. This new process doesn’t require your device to be rooted, nor does it require a custom recovery like TWRP. But for this method to work, your device must have the stock boot.
But for this method to work, your device must have the stock boot.img dump placed in the internal storage.
Make sure that you enable USB debugging and setup ADB access first, you will need it later in the guide.
Download Magisk Manager 5.3.0: Link
When the APK has been downloaded, use a file manager to install it. Now run the app from the app drawer.
Go to the app settings and tap on “Patched Boot Output Format”. You can select “.img.tar” if you will be using ODIN to flash the file or else simply select “.img” for the rest of the devices.
{
"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"
}
Go back to the app main screen and tap on the “Install” button. Go to INSTALL > PATCH BOOT IMAGE FILE.
Navigate through the storage and select the stock boot.img file. As soon as you select the stock boot.img file, the app will download the installer to patch the image.
Once the process is complete, you can tap on the “CLOSE” button.
Your new and patched boot image now include root and support for modules. So the last step is to grab this boot file and flash it your device via fastboot or ODIN (Depending on the output format you chose in step #4).
Connect your device to the PC via USB cable and navigate to the Magisk Manager folder inside the storage. Your “patched_boot.img” file will be present right there. So copy it to your PC.
Move the “patched_boot.img” file to C:/adb folder. And type in the following command to boot your phone into bootloader/fastboot mode:
adb reboot bootloader
Once your phone enters the bootloader/fastboot mode, enter the command to flash the file:
fastboot flash boot patched_boot.img
Finally, reboot your device:
fastboot reboot
That’s all, you have just installed one of the most trending mod out there and especially on your non-rooted device without any need of a custom recovery. Isn’t it great? Tinker around with the app and see what all things you could do.

I can confirm this is working! Thank you!

Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks

kamo84 said:
Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks
Click to expand...
Click to collapse
I know it's been some time since this was discussed, but I am trying to go through this process. Can you confirm that you unlocked the bootloader on 8.0 with the Asus tool? Or did you install magisk without unlocking the bootloader (if that's possible)?
thanks

I don't think the unlocker tool works anymore.

[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.

Android 10+ system file r/w access

Hi what is secret to using file manager on phone Android 10+ with su access to read and write in system - remove bloat apps? I have su access, but I read in 10+ file system not allow from file manager, only need use adb. How to use file manager with su to remove manually on Android 10+? I get error when deleting app from any file manager with su access "cannot delete". Danke.

Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
{
"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"
}

SirisRui said:
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
View attachment 5577955
Click to expand...
Click to collapse
Wow very complex but thank you for explain!