Database Info

[PC-APP] SGN3 Mod Tool

DOES IT WORK? I am yet to receive my SGN3, so I haven't been able to test.
I made this tool originally for SonyEricsson Xperia X10, but have now modified it to work for our Samsung Galaxy Note 3. I hope it will make life a little easier when modifying files on the device. It uses ADB to pull and push files, change file permissions and much more - so users don't need to remember long command prompt/terminal emulator commands! It also has a nifty little application manager, which allows for quick installation, backup, and removal of both pre and self -installed software. It has a LogCat function to read and save logs on the go when investigating errors, as well as functionality to decompile/recompile APK, JAR and ODEX files, sign and zipalign APKs, and decompile System images. Finally, straight ADB shell access is integrated.
{
"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"
}
Instructions:
1. Download.
2. Extract archive.
3. * Install LinuxReader to GalaxyS3ModTool\tools\LinuxReader.
4. Run SGN3ModTool.jar!
*This step is only needed for the Decompile System function in the ROM Manager.
Note: Make sure your phone is connected in debug mode, you have root privileges, and unsecured your device's shell. The application will try to unsecure your shell if you haven't already, but worst case scenario you might have to do this manually.
Also, the manage ROMs functionality is still experimental, and the Recompile System function is disabled. If you know how these processes can be automated, let me know and I will incorporate the functionality.
If you have problems, let me know and I will try to sort them out with you. Keep in mind that often when a modification goes wrong, you can simply push back the original files and reboot. So keep backups handy!

Reserved in case of future expansion.

Very interesting, will test when i get back home. Thanks!

Sound good mate. I'll give it a go I reckon

Wow sounds awesome thank you very much

Does it backup app data as well? This looks very promising. As it is java based, would it work on other platforms?
Sent from my Nexus 4 using Tapatalk

Post Removed

Breach said:
1. Download.
2. Extract archive to C:\cellphone\SGN3ModTool
3. * Install LinuxReader to C:\cellphone\SGN3ModTool\tools\LinuxReader.
4. ** Install the Java Runtime Enviroment from.. http://www.java.com/en/download/windows_xpi.jsp?locale=en
5. Make sure your Note 3 is plugged in and the screen is unlocked.
6. Run SGN3ModTool.jar
* This step is only needed for the Decompile System function in the ROM Manager.
** This step is only needed if you do not already have the JRE installed.
------------
It is telling me the device is offline. For example.. Roboot, Refresh Content, etc.. do not nothing.
Make Dir says "Directory Created" but does this...
adb shell mount -o remount,rw /system
adb shell mkdir "/test"
error: device offline
Click to expand...
Click to collapse
you have to allow ADB to acces your device..
when you try to do anything with ADB, look at your phone screen, it will give you a popup that will enable you to 'allow ADB connections'

karoolus said:
you have to allow ADB to acces your device..
when you try to do anything with ADB, look at your phone screen, it will give you a popup that will enable you to 'allow ADB connections'
Click to expand...
Click to collapse
I watched my screen. I got no popups other than the original "usb connected" popup when I plugged in the usb cable.
Edit: Deleted the app. No Support from Dev.

Breach said:
I watched my screen. I got no popups other than the original "usb connected" popup when I plugged in the usb cable.
Edit: Deleted the app. No Support from Dev.
Click to expand...
Click to collapse
this actually does work!
if somone still wants to use it for whatever reason you can:
get a kernel that is not SElinux enforcing (permissive).*
get adb insecure by chainfire and switch to insecure mode.
be sure that in the app it says:
Binary: Insecure
USB debugging: Enabled
should work, at least for me it did.
not sure if every custom kernel(permissive) works.
*lastest wanam exposed module has an experimental feature to set the selinux to permissive.
i havent tried it but maybe you can do the above with stock kernel and just setting permissive mode in wanam.
edit: does not work with stock kernel, at least for me.
i have not tested every function of this tool but connecting, pushing, pulling and so on work.
there are other tools that can do that, i wrote this just for information.

works well here! well done

cant get it to work on mac

thanks MrRusch for your great work!
I am a newbie about these stuff so forgive me if these are questions are stupid~
I was trying to use it to deodex the SamsungChineseIME apk and I got 2 questions want to ask.
1. when it asks for "Install Framework?", I choose the framework-res.apk extracted from my rom. But I also notice there is a twframeworkres.apk in the rom, do I need to include that also?
2. I came to a prompt asking me for "Select framework directory to reference" (as attached screen), I was hold back since I don't know what to choose for this.
Thank you again for your effort and this great tool!

[GUIDE] Enable Multi-Window Mode on Android 6.0 Marshmallow

There's a hidden feature in Android 6.0, multi window. It has its warnings:
{
"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"
}
So decide if this is actually for you before following these steps
It's not shown in user builds, so we have to do some messing. You'll either need root or a custom recovery to do this, but as not everyone wants root, here's how you do it with TWRP, a USB cable, and a PC with ADB:
1. Boot your device into recovery
2. Mount your system by going to Mounts > Tick System
3. On your PC open a command line, somewhere like your desktop is useful
4. Type the following command:
HTML:
adb pull /system/build.prop
5. Open the build.prop file with your favourite (decent) editor, I recommend using Notepad++ on Windows
6. Find the "ro.build.type" line
7. Change the text after = to "userdebug" from "user"
BONUS: If you want a nicer DPI here, change the line "ro.sf.lcd_density" to your preferred DPI
8. Save the file
9. Go back to the command line and enter the following command:
HTML:
adb push build.prop /system/
10. Now open a shell doing:
HTML:
adb shell
11. Now a adb shell will open, enter these commands:
HTML:
cd system
chmod 644 build.prop
12. Reboot the device as normal
13. When the device has booted, go to the developer options
14. Scroll down to the bottom of the "Drawing" category
15. Enable multi-window and have some fun!
If you're rooted...
1. Download "Build.prop editor"
2. Find "ro.build.type"
3. Edit it to have the value "userdebug" from "user"
4. Reboot when prompted
5. When the device has booted, go to the developer options
6. Scroll down to the bottom of the "Drawing" category
7. Enable multi-window and have some fun!

Worked ! Thanks
Such a shame the Keynote didn't introduce such feature, it's stable enough. Just think of the use of the feature on a 10" tablet.

works perfect thank you !

How do you use it after enabling?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
Go recent menu, on the apps beside the x there's a button to choose the top half or second half.
Multirom users can go /data/media/multirom/roms/ and edit the build prop directly there, no need to use adb. I did it without using a PC

I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
I get how to use it, but how do you consistently pick the two apps that you want to appear?
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
elreydenj said:
I get how to use it, but how do you consistently pick the two apps that you want to appear?
Click to expand...
Click to collapse
It seems to be all over the place. I cant figure out how to always get the two apps that i want in multiwindow to show....

prwnd said:
I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?
Click to expand...
Click to collapse
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards

is it possible to do that with Wugfresh Nexus Root Toolkit?

jonathanxx1 said:
is it possible to do that with Wugfresh Nexus Root Toolkit?
Click to expand...
Click to collapse
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.

drgonzo712 said:
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.
Click to expand...
Click to collapse
I tried also ,,and it doesn't work.

Adr990 said:
I got this message from ADB:
Anything?
Click to expand...
Click to collapse
Open terminal, type
su
cd system
chmod 644 build.prop
exit
and do stages again

Adr990 said:
When I do that, in adb shell:
Click to expand...
Click to collapse
Ow, i forgot ,my mistake sorry can you try this ?
cd system
chmod 777 build.prop
exit

damn.. is there a way to do it if it is a secondary rom on multiboot?

Adr990 said:
Oh and I also tried this:
Kinda wierd how it is not working for some, while we all flashed according to Google's adb flashing method.
Click to expand...
Click to collapse
Can you send your build.prop to me via pm. I can make a flashable zip for you

Hello people, I have multirom installed on my nexus 5, the primary rom is 5.1.1 (LMY48B), and my secondary rom is the developer preview MPZ44Q. I want to know if it's possible to enable multi-window mode since the M preview is installed as secondary rom.

I did it. Reboot into recovery. Swap the Roms. Don't reboot . reboot into recovery again from the reboot tab. Select multiboot tab just to ensure you are OK and the M ROM is the internal.. Mount system and do what the op says. Reboot into recovery again swap Roms again . reboot system and you should be OK. Takes like a half an hour to do though
PS. NEVER FIX SU. ALWAYS SKIP

I understood that if i try to install su on the M rom, it will result in bootloop. And my internal rom is stock ROOTED. So do you think it will work ?
When i will swap the roms, the fact that my primary rom is rooted, will it cause any problem ? Thanks in advance.

Nope my primary is still rooted. And I an typing this from my secondary M ROM with multi window enabled. All you have to do is never fix su for either ROM and never boot the system with M as your primary ROM and you are ok

Help me too
hsay said:
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards
Click to expand...
Click to collapse
This is the worst thing to do here but could u please guide me too to the recovery as i searched all i could but still got no answer. Even the Guys in the Discussion group had no answer. Please Help ME,.

[X553] recowvery, unlock, root Infinix HOT 3 LTE potential - with TWRP

Team Win Recovery Project 3.0.2-0
How it looks :
{
"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"
}
Notice : I don't own the device my self, so i need some one to test this method.
This will allow you to install TWRP and flash SuperSU!
Step 1 : Unlocking your bootloader
You need unlock bootloader first before installing twrp.
You will also need adb and fastboot. You can download them in a portable small form factor here :
[ADB FASTBOOT][LINUX&WINDOWS]
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
Enable usb debugging on developer option, and extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
Step 2 : Running recowvery
You can find the recowvery binaries (you need to download all of these) at :
Here
You're now ready to follow the recowvery installation instructions.
See here (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3 : Flashing TWRP & Rooting
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, or you can also just use adb push. (mentioned here)
Download TWRP build here.
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from here to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU : here
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4 : Have fun!

Thanks for this great work brother
But sorry i can't try any thing right now because I have exams nowadays
I want to tell you also that I just rooted successfully my hot 3 lte now using kingoroot apk with out using pc 😄😄😄

ModaAli said:
Thanks for this great work brother
But sorry i can't try any thing right now because I have exams nowadays
I want to tell you also that I just rooted successfully my hot 3 lte now using kingoroot apk with out using pc 😄😄😄
Click to expand...
Click to collapse
so root is done, then time to try twrp just if u not busy

And then for custom rom ??
But later, I'm so busy sorry ? ?

ModaAli said:
And then for custom rom ??
But later, I'm so busy sorry ? ?
Click to expand...
Click to collapse
Don't hope too much this is still for testing but probably soon will have a custom rom, well good luck for your exam bro :good:

It will be sure
Thanks bro ?

Thread closed per OP request.

Root with magisk, airplane mode toggling on and off, need to boot on charge.

Hi,
My company bought four Samsung Galaxy A30s (SM-A307FN) phones to be used in a project, where we need remote control and access to the phone and it's camera. So far, everything is looking dandy, however we're missing a critical feature. If the phones runs out of battery, we want it to boot when power has come back again. It's a critical feature, because the phones will be installed in places not easy to reach.
I therefore started looking into getting root access. I used this approach https:// www .recovery-mode. com/ root/ root-samsung-galaxy-a30s-magisk-root-without-twrp. html rooting without twrp and rooting seems succesful. However - the phone periodically toggles airplane-mode - and connection to the carrier cannot be reached. Does anyone have similar issues - or solutions or ideas as to how I can fix it?
If I boot with no root (disable recovery mode) the connectivity comes back, and the phone behaves normally.
I regards to the boot on charge, I've tried different things with the lpm file. I always end up being stuck with the charge symbol in a circle, and I have to reboot with power+vol-up+vol-down.
I tried this:
Google search: Root Samsung Galaxy A30s ( Magisk Root ) without TWRP recovery mode
(i cannot post link since I'm a new user)
and this:
Google search: Auto-starting Samsung Android phone when charger is plugged in. (mediumdotcom)
Lastly I looked into this thread:
Google search: lpm-reboot-samsung-galaxy-s7
but when I try to remount /system with read-write, I get an error message saying " '/system' not in /proc/mounts" .
Also if I try to get root access through adb it tells me "adbd cannot run as root in production builds".
Any help would be appreciated.
/Lasse

Allright, I got this far:
Managed to get the LPM file changed and get the phone to boot on charge.
After rooting successfully (although airplane-mode / Flight-mode keep toggling) I got access to the lpm file.
first, I entered shell
Code:
adb shell
then I gained superuser access:
Code:
su
I had to change read/write mode for the system-directory. I couldn't use "remount -o rw,remount /system" - as it told me that it wasn't part of /proc/mounts/.
I found a thread saying to remount the root directory " / " instead - that worked:
Code:
mount -o rw,remount /
Great - now all I had to do, was to change the contents of the lpm file. Making a new lpm file didn't work - apparently the lpm file has a unique inode value - that the system uses to identify the file, and making a new file, creates a new inode number. So I had to use the original file. I was sceptical about this, because I didn't want to brick the phone, so I made a copy of the lpm contents in order to go back to normal - if it didn't work. I copied the contents to a new file called lpm.orig using cat:
Code:
cat system/bin/lpm > system/bin/lpm.orig
So now i had to insert new text in the original lpm file. I made a script with the following contents:
Code:
#!/system/bin/sh
sleep 30
/system/bin/reboot
and called it lpm-script - the 30 sec sleep period is because I want to make sure the power is back, before booting the phone.
Now all I had to do is to cat the contents of lpm-script into lpm:
Code:
cat system/bin/lpm-script > system/bin/lpm
I rebooted in system mode (not recovery), so I once again had cellular connection, powered the phone off, plugged the usb in, and waited - and success... it worked. Originally I had a 5 second sleep period, but it stille took around 20 sec for the phone to boot - so be a little patient before turning the phone on manually.
So my next issue is the flight-mode toggl. If I managed to get this solved, I hope I'll be able to use the phone with root access all the time, but for now, my initial goal is completed: Boot samsung galaxy a30s on charge.
Let me now if anyone else gets it to work.
/Lasse
Labild said:
Hi,
My company bought four Samsung Galaxy A30s (SM-A307FN) phones to be used in a project, where we need remote control and access to the phone and it's camera. So far, everything is looking dandy, however we're missing a critical feature. If the phones runs out of battery, we want it to boot when power has come back again. It's a critical feature, because the phones will be installed in places not easy to reach.
I therefore started looking into getting root access. I used this approach https:// www .recovery-mode. com/ root/ root-samsung-galaxy-a30s-magisk-root-without-twrp. html rooting without twrp and rooting seems succesful. However - the phone periodically toggles airplane-mode - and connection to the carrier cannot be reached. Does anyone have similar issues - or solutions or ideas as to how I can fix it?
If I boot with no root (disable recovery mode) the connectivity comes back, and the phone behaves normally.
I regards to the boot on charge, I've tried different things with the lpm file. I always end up being stuck with the charge symbol in a circle, and I have to reboot with power+vol-up+vol-down.
I tried this:
Google search: Root Samsung Galaxy A30s ( Magisk Root ) without TWRP recovery mode
(i cannot post link since I'm a new user)
and this:
Google search: Auto-starting Samsung Android phone when charger is plugged in. (mediumdotcom)
Lastly I looked into this thread:
Google search: lpm-reboot-samsung-galaxy-s7
but when I try to remount /system with read-write, I get an error message saying " '/system' not in /proc/mounts" .
Also if I try to get root access through adb it tells me "adbd cannot run as root in production builds".
Any help would be appreciated.
/Lasse
Click to expand...
Click to collapse

airplane mode
Hi,
I'm stuck with the airplane mode toggling on and off after rooting with magisk. I've tried to re-flash the phone, but it seems to be the same issue, although the root procedure had no errors or no warnings. Root access works.
Is there anyway to permanently disable airplane mode? Other than pushing the on/off switch.
{
"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"
}
Any help or suggestions would be appreciated.
/Lasse

Hey, did you find how to solve this problem? i also have it

[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