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.

[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

[RECOVERY][K920] TWRP 2.8.7.X for Lenovo VIBE Z2 Pro [2015-07-27]

No longer maintained, use TWRP 3 instead!
{
"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"
}
New, completely rebuilt
Team Win Recovery Project
for Lenovo VIBE Z2 Pro (K920) ROW.
Features
OTA Updates support
Full SELinux support
Mounting phone storage to PC via MTP
USB-OTG (exFAT & FAT32)
Fully functional ADB
Battery charging
Materialised theme by z31s1g
Additional partitions info
Modem - /modem
Efs - /fsg, /modemst1, /modemst2
Mrd - /mrd
Persist - /persist
Preload - /preload
Aboot (bootloader) - /aboot
Firmware-update - /sbl1, /rpm, /tz, /dbi
Splash - /splash
How to enter recovery
Hold the POWER button and BOTH VOLUME buttons simuntaneusly until you see the logo.
Disclaimer
I am not responsible for anything that happens to your phone or computer. You have to understand what you are doing.
One-Time Boot
Enable ADB debugging (in Developer Options)
Reboot into bootloader / fastboot mode (adb reboot-bootloader)
Boot into recovery.img (fastboot boot recovery.img)
Done!
How To Flash
Install ADB+Fastboot with drivers (I recommend this installer)
Enable ADB debugging on your phone (in Settings->Developer Options)
After connecting the phone to the PC, pop up may appear, tick Always allow from this computer and click OK
Extract downloaded recovery zip and copy .img file to C:/adb
Now open cmd line (press Start+R, type "cmd", press OK) and go to C:/adb (type "cd C:/adb" and hit Enter)
Reboot into bootloader (fastboot mode) (type "adb reboot-bootloader")
Your phone should now reboot into the bootloader (Little green android logo in the middle of the screen)
Flash the recovery.img (type "fastboot flash recovery recovery.img")
(*) Now boot into the recovery (type "fastboot boot recovery.img")
(*) Mount /system partition (In TWRP go to Mounts and tick System)
(*) In TWRP open File Manager, go to /system and rename recovery-from-boot.p to recovery-from-boot.p.bak
Finally, reboot!
Done!
* You should do these steps only if you have Lollipop firmware (to prevent from TWRP being overwritten by stock recovery on each boot)​
Download
(mega.nz)
TWRP 2.8.7.1 (18.0 MB)
TWRP 2.8.7.0 (19.5 MB)
CN Devices
There is limited support for CN devices although most features (backup/restore, etc...) should work fine.
I don't own CN device, therefore I can't "add" full support for them.
Check out my script for switching between UIs under TWRP!
Screenshots below​
Source: https://github.com/ElectryDev/twrp_kingdom_rowhttps://github.com/ElectryDev/twrp_kingdom_row
XDA:DevDB Information
TWRP for Lenovo VIBE Z2 Pro, Tool/Utility for the Android General
Contributors
Electry
Source Code: https://github.com/ElectryDev/twrp_kingdom_row
Version Information
Status: Stable
Current Stable Version: 2.8.7.1
Stable Release Date: 2015-12-19
Created 2015-08-01
Last Updated 2017-01-24

i guess this is only for kitkat and would not work with lollipop

jacktackle said:
i guess this is only for kitkat and would not work with lollipop
Click to expand...
Click to collapse
Yes, for now. There is still no way of unlocking the bootloader.

to unlock the bootloader take a look here
On K920 CN version I can't backup some addtional partitions
ROM: ROM VibeUI_2.5_1526_5.574.1_ST_K920
TWRP: K920_TWRP_2.8.6.1_LP
I can mount: System, Persist, Cache, Data, Modem & OTG
but NO NvRam! The Preload is available, but not checkable
I can backup: Aboot, Boot, Recovery, System, Persist,
No modem neither nvram

Uploaded 2.8.7.0

Lolipop 5.0.2 here. Rooted Z2 Pro, unlocked boot loader but still do not understand how to install twrp. No clear procedure ......

Have you read the first post incl the instruction "How to flash"?

I know it's not that straightforward. You have to have adb and fastboot installed somewhere, then copy the .img file there and execute those commands in cmd line from that location.
One thing I forgot to mention is that you have to delete recovery-from-boot.p file (i think it's in /system) before booting into android, otherwise your custom recovery will get replaced with the stock one.
I'll try to rewrite the guide tomorrow.

Electry said:
I know it's not that straightforward. You have to have adb and fastboot installed somewhere, then copy the .img file there and execute those commands in cmd line from that location.
One thing I forgot to mention is that you have to delete recovery-from-boot.p file (i think it's in /system) before booting into android, otherwise your custom recovery will get replaced with the stock one.
I'll try to rewrite the guide tomorrow.
Click to expand...
Click to collapse
THNX Electry for your answer
Tommes24 said:
Have you read the first post incl the instruction "How to flash"?
Click to expand...
Click to collapse
Try to be polite and not just the "smart" guy. Electry was so kind to give some explanations ......

Confirm problem
I have the Chinese version of K920.
Everything was ok until confirming the system/recovery.from.boot.p file rename.
I can not confirm. I should swipe to confirm, but it do not work. And when I unfortunately touched the power button, the whole operation was locked. Now I have a kind of an Icon in the lower left part of the screen parly hidden. It is a padlock and a text saying "...t to Unlock".
How to solve this?

Hi Electry,
Thanks for twrp and all your works.
I need to upgrade my phone but with twrp i can't, do you have stock recovery image?

The tutorial is ok, everything is working fine, but i don't now how to enter the google ui style (in developer options switching between Lenovo UI style and Google UI style, is not possible now, as recovery option). After switching, nothing happends, just rebooting recovery TWRP mode. After that, what to do?
---------- Post added at 05:09 PM ---------- Previous post was at 05:00 PM ----------
@ppllpp
http://lenovo-forums.ru/topic/14303-lenovo-vibe-z2-pro-k920-прошивка-k920-s271-150907-ota/
https://yadi.sk/d/hcZCg2SbbzSd8 (rom, sdupdate-qsb).

drpainster said:
The tutorial is ok, everything is working fine, but i don't now how to enter the google ui style (in developer options switching between Lenovo UI style and Google UI style, is not possible now, as recovery option). After switching, nothing happends, just rebooting recovery TWRP mode. After that, what to do?
Click to expand...
Click to collapse
Unfortunately, switching between UIs is feature of stock recovery so clicking on that button in Settings won't do anything. I made a simple script for this -HERE-, just flash it in TWRP (and tell me if it works for you).

It's working! Thanks

Installed script. After reboot device turns to pure Android. In order to change to Lenovo UI, you have to run script again !!!

Well, that's the purpose of the script. I can't really make that button in Settings work with custom recovery.
If you want to switch UI, you'll have to flash that .zip each time. It is not that hard.

Something's wrong with "3. Boot into recovery.img (fastboot boot recovery.img)" (One-Time boot).
Nothing happends, message: wating for device...

hi,
i am using "lenovo k920pro, cn version, android lollipop s271 and stock recovery".
cn version. dont eu version.
for this device "twrp recovery" is required.
is there that can help?
thank you.

i have a problem with 271 upgrade. Now after wiping cache when android boot and appear "starting app x of y" it takes little times and numbers runs quickly. When finishes booting appear an error "storage space is running out" or somthing like that. With 246 never appened. I have to format again to solve this problem. Why is this happening now?

i was having difficulties with command line on my pc,so i flash recovery easily with Flashify apk.works like a charm!ofcourse i have unlock bootloader first!

[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