Database Info

Accidentally deleted backup and os installed on my opo!

Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.

dxlevel81 said:
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
Click to expand...
Click to collapse
Can you boot into fastboot or recovery?

Mr.Ak said:
Can you boot into fastboot or recovery?
Click to expand...
Click to collapse
yes I can boot into TWRP, but can't connect to pc.

dxlevel81 said:
yes I can boot into TWRP, but can't connect to pc.
Click to expand...
Click to collapse
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.

Mr.Ak said:
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Click to expand...
Click to collapse
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.

dxlevel81 said:
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
Click to expand...
Click to collapse
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.

Mr.Ak said:
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Click to expand...
Click to collapse
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus

dxlevel81 said:
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
Click to expand...
Click to collapse
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979

Mr.Ak said:
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
It does'nt show in the device manager.

[TOOL] Unlock bootloader in ASUS ZenPad 3S 10 Z500M (P027)

Tool to Unlock Bootloader in ASUS ZenPad 3S 10 Z500M (P027)​
This software essentially unlocks the bootloader in your tablet. I've developed a way to switch a Mediatek bootloader into an unlocked state using root privileges. Luckily, the Z500M does give us temporary root access to run this tool. The result is an "Orange State" boot mode, which disables boot partition verification. As a bonus, this procedure does not erase your data like a typical unlock routine does. It also does not require a PC except to start the temporary rooted image. Note that your tablet will still lack fastboot flashing functionality. But flashing by other means is still possible.
WARNING: Running this tool should be pretty safe. But I don't encourage anyone to try this. Before trying this out, consider the risks and drawbacks involved. By unlocking, you are essentially giving up the security of your device. It's also possible that a future firmware update will relock the bootloader or become incompatible with this tool.
This software is only for ASUS model Z500M/P027. Do not try it on any other device. It will not work. Support for other Mediatek devices may be added in the future. (That's why this is posted in the general forum rather than the ZenPad 10 one.)
And by the way, I don't own this tablet.
DISCLAIMER
This software is for educational purposes only. Anything you do that is described in this post is at your own risk. No one else is responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
REQUIREMENTS
A ZenPad Z500M tablet upgraded to Android N
A rooted/patched boot image such as one made by Magisk Manager (method 1)
Temporary root with Magisk or other superuser manager installed (method 1)
TWRP image (method 2)
Knowledge of adb/fastboot and of basic Linux command shell
INSTRUCTIONS
Method 1
Read all of these instructions and make sure you understand them before starting
If you don't have an offline patched boot image, use Magisk Manager to make one from the stock boot.img of your current firmware. Transfer it to your PC.
Reboot your tablet into fastboot mode--either hold vol. down + power to power up, and select Fastboot. Or run 'adb reboot bootloader' while in Android.
Connect your tablet to a PC and run fastboot boot patched_boot.img to start the rooted image in tethered mode
Download the tool zip file to your tablet.
Extract the zip to your /data/local/tmp folder.
Open a root shell with adb shell, then run 'su'
Change your shell current directory to that folder (cd /data/local/tmp)
Run this command to unlock or lock the bootloader
Code:
sh unlockbl.sh
Follow the instructions on the screen and type the requested confirmation into the prompt.
Check for completion or any error messages. Report them here.
If no errors, you are unlocked and may modify your boot partition (e.g. install root).
Method 2
Read all of these instructions and make sure you understand them before starting
If you don't have TWRP for your tablet, download the latest image to your PC from this thread.
Download the tool zip file to your tablet.
Extract the zip to your /data/local/tmp folder. (For this method, most other folders should work as well due to permissive selinux mode)
Reboot your tablet into fastboot mode--either hold vol. down + power to start up and select Fastboot, or run 'adb reboot bootloader' from Android
Connect your tablet to a PC and run fastboot boot twrp-*.img to start TWRP in tethered mode
At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
Mount system in TWRP in read-only mode. Mounting in read/write mode will render your tablet unbootable.
Open a shell with adb shell on your PC or open TWRP's built-in terminal
Change your shell current directory to the folder that you extracted the tool zip into (cd /data/local/tmp)
Run this command to unlock or lock the bootloader
Code:
sh unlockbl.sh
Follow the instructions on the screen and type the requested confirmation into the prompt.
Check for completion or any error messages. Report them here.
If no errors, you are unlocked and may modify your boot partition (e.g. install root).
DOWNLOAD
Current Version
Unlock Tool v0.6a
Changelog
v0.6a
Actually improve compatibility with TWRP
v0.6
Handle units with blank bootloader configs
Improve compatibility with TWRP
Improve text wrapping for TWRP's terminal
v0.5
Major overhaul to remove the need for kernel module
v0.2
Made compatible with other FW versions
v0.1
First release
CREDITS
@amartolos for being a kick-ass tester
If anyone wants to develop a full Android app around this script, be my guest.
Also, that Thanks button will not click itself...

reversed :silly:

I got this after typing "Yes, I want to unlock"
Extracting binaries
Inserting kernel module
Testing kernel module
Oops! Something went wrong. Aborting
Your system has not been modified
Exit code 126
Click to expand...
Click to collapse
When running script with terminal on tablet I got exit code 1 on the same stage.

Joh14vers6 said:
I got this after typing "Yes, I want to unlock"
When running script with terminal on tablet I got exit code 1 on the same stage.
Click to expand...
Click to collapse
Were you running a basic boot image or did you boot the patched boot image?

amartolos said:
Were you running a basic boot image or did you boot the patched boot image?
Click to expand...
Click to collapse
I booted from the patched boot image. Latest FW. Script will not run without (temp)root.

I haven't been able to get magisk to make a patched boot.img
Any help appreciated.

Can we use the patched boot image you posted from the other thread? "Z500M_signed_patched_boot.tar"? https://forum.xda-developers.com/showpost.php?p=74303280&postcount=72

2. Install Magisk Manager and create an offline patched boot image from the stock boot.img if you don't have one.
Apologies. I have Magisk installed on my Nexus 6 but I would not consider myself an expert. With that device I installed the Magisk zip file in TWRP recovery and then installed Magisk Manager. After installation of Magisk Manager on the Z500M and launching the app it asks if I want to install the Magisk 15.2 zip. Should that be done?
At this time I haven't done this and I don't see any method for creating the patched boot image. Can someone direct me via a link or explanation on how to do this?

There's another thread that contains this info: Click Here

ExtremeRyno said:
Can we use the patched boot image you posted from the other thread? "Z500M_signed_patched_boot.tar"? https://forum.xda-developers.com/showpost.php?p=74303280&postcount=72
Click to expand...
Click to collapse
Yes
Sent from my P01MA using Tapatalk

Joh14vers6 said:
I got this after typing "Yes, I want to unlock"
Extracting binaries
Inserting kernel module
Testing kernel module
Oops! Something went wrong. Aborting
Your system has not been modified
Exit code 126
Click to expand...
Click to collapse
When running script with terminal on tablet I got exit code 1 on the same stage.
Click to expand...
Click to collapse
Hmm, that sounds like a permissions problem. Before running the script, can you turn off Selinux enforcement somehow? Try running 'setenforce 0' or maybe there's a setting in Magisk that controls this. Bear with me, I'm trying to get to the bottom of this...
Has anyone besides amartolos gotten this to work yet?

I ran the tool successfully and it said to reboot and Root. While rebooting it says:
Orange State
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
Then I can't get a root to take.
Edit: I found the problem. After you run the script, run magisk to root before you reboot, while you are still in temp root status.
Sent from my P01MA using Tapatalk

loner. said:
I ran the tool successfully and it said to reboot and Root. While rebooting it says:
Orange State
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
Then I can't get a root to take.
Click to expand...
Click to collapse
Yep, you got it! In order to have persistent root, you actually have to install it to your boot partition while booted up with temporary root.

loner. said:
Edit: I found the problem. After you run the script, run magisk to root before you reboot, while you are still in temp root status.
Click to expand...
Click to collapse
Word

diplomatic said:
I got this after typing "Yes, I want to unlock"
Hmm, that sounds like a permissions problem. Before running the script, can you turn off Selinux enforcement somehow? Try running 'setenforce 0' or maybe there's a setting in Magisk that controls this. Bear with me, I'm trying to get to the bottom of this...
Has anyone besides amartolos gotten this to work yet?
Click to expand...
Click to collapse
I tried SELinuxModeChanger to set Selinux to permisive and tried setenforce 0 and both give same exit code 1 from the terminal.

Joh14vers6 said:
I tried SELinuxModeChanger to set Selinux to permisive and tried setenforce 0 and both give same exit code 1 from the terminal.
Click to expand...
Click to collapse
What firmware version do you have installed? And are you running this from the /data/local/tmp directory?

diplomatic said:
What firmware version do you have installed?
Click to expand...
Click to collapse
FW WW_14.0210.1709.30 from 04 jan 2018 and yes, I ran from that folder.

Joh14vers6 said:
FW WW_14.0210.1709.30 from 04 jan 2018 and yes, I ran from that folder.
Click to expand...
Click to collapse
Last two numbers should be .27
I checked and yes there is a update, but I don't think I can install it. Since I and already rooted. The size of the update seems to be a security update.
---------- Post added at 05:16 PM ---------- Previous post was at 05:11 PM ----------
Has anyone who successfully rooted this device able to do the update after?

I'm glad to see that Asus is releasing security updates even if it does break the unlock. My biggest fear buying this tablet was that it would not be updated. I opted for the update and will hope for an updated patch from @diplomatic.
As an aside. I would encourage anyone in this thread to give hit the "Thanks" button for diplomatic!
EDIT: I just checked and see my last update brought me to WW_14.0210.1711.30_20171206. That's different than the 1/4/2018 update showing on the website which is WW_14.0210.1709.30 and what @Joh14vers6 shows.

Joh14vers6 said:
FW WW_14.0210.1709.30 from 04 jan 2018 and yes, I ran from that folder.
Click to expand...
Click to collapse
OK everyone, this is important... I found an incompatibility between the new FW's kernel and the tool. You have to use the patched boot image from FW 1709.27 for temporary root... In the meantime, I have to fix it to be able to run under the new FW. But it won't be compatible with the old. And I hope it still unlocks...

minimal adb and fasboot vs. platform tools

I want to know for flashing peter's twrp, which one should i use platform tools or minimal adb and fastboot?

hackermssharma said:
I want to know for flashing peter's twrp, which one should i use platform tools or minimal adb and fastboot?
Click to expand...
Click to collapse
Both ss are attached below
Sent from my Redmi Note 7 Pro using XDA Labs

hackermssharma said:
Both ss are attached below
Click to expand...
Click to collapse
They are both essentially the same thing i.e they offer the same functionality for the standard user.
Both of them install ADB on your PC, but Platform tools has more advanced options and is more suitable for devs while Minimal ADB can be considered to be a scaled down version of Platform Tools.
I suggest you use Minimal ADB as it's both lightweight and simple.

General [Root] Magisk Patched Boot image

Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.

M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Thanks dear I'm on 18.0830.2101.75 can you provide patched image boot for my version because i want to change fingerprint to WW then install newer version through my phone.

İs there stock boot.img

How to relock the bootloader and remove root?

M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Hey i got update version 18.0810.2101.95
Can i use this img to root or i have to update first?

Eeveeone said:
Hey i got update version 18.0810.2101.95
Can i use this img to root or i have to update first?
Click to expand...
Click to collapse
First update, then flash this img, this img caused bootloop my phone so take care.

sorankira said:
First update, then flash this img, this img caused bootloop my phone so take care.
Click to expand...
Click to collapse
If like that better not update to 18.0830. but how i want to get stock img for 18.0810

Eeveeone said:
If like that better not update to 18.0830. but how i want to get stock img for 18.0810
Click to expand...
Click to collapse
Download 18.0810 firmware on your PC and download dumper tool it will extract payload.bin you can find stock images there.

sorankira said:
Download 18.0810 firmware on your PC and download dumper tool it will extract payload.bin you can find stock images there.
Click to expand...
Click to collapse
Can you help me by doing it. coz i couldnt do the proper way. it say syntax error

Eeveeone said:
Can you help me by doing it. coz i couldnt do the proper way. it say syntax error
Click to expand...
Click to collapse
My internet is very slow indeed like 100KB/s but i will try to download it and send you the stock img.

sorankira said:
My internet is very slow indeed like 100KB/s but i will try to download it and send you the stock img.
Click to expand...
Click to collapse
Thx a lot.. currently i managed to do it. Now i have the stock img

Does anyone tried applying an OTA update while rooted? Is it sufficient to restore stock boot image, apply update zip file and flash new patched boot image? I have not tried it yet, because there is no TWRP available and I want to backup my data before trying.

MarekPietrzak said:
Does anyone tried applying an OTA update while rooted? Is it sufficient to restore stock boot image, apply update zip file and flash new patched boot image? I have not tried it yet, because there is no TWRP available and I want to backup my data before trying.
Click to expand...
Click to collapse
Yes you can apply ota update.
When the OTA Update finishes don't reboot click later, then go to magisk install OTA to inactive slot.

THANK YOU! This file saved my phone. I installed some other boot image that wouldn't let me boot the phone, this file brought it back to life.
Thank you again!

M.Qassem said:
Firmware 18.0830.2101.81 Magisk patched boot image.
I have dumped the boot image from Asus payload BIN using Python. Tested and works flawlessly.
Try on your own RISK!
How to install:
- Unlock your bootloader using ASUS unlock app.
- Enable debugging in developers options.
- Install ADB & Fastboot Drivers.
- Extract then copy the attached boot.img to ADB tools folder.
- Open a prompt command in ADB folder, enter command "adb reboot bootloader"
- Select Recovery using the volume keys and power key , then select fastboot.
- Enter command "adb flash boot boot.img"
if the above doesn't make sense, then probably you shouldn't be trying to root using this method.
Thanks.
Click to expand...
Click to collapse
Hallo
Any boot.img for latest version WW ASUS-18.0840.2103.26-1.1.81?
Can`t get my payload working, because not installing in correct folder.

ltth said:
Hallo
Any boot.img for latest version WW ASUS-18.0840.2103.26-1.1.81?
Can`t get my payload working, because not installing in correct folder.
Click to expand...
Click to collapse
Try extracting from your phone for payload.bin file. Or there is a "rooting my notes" discussion video in one of the post. You can see there

I have the payload bin file, but can`t extract in payload_dumper-master (not working correctly so I get the boot.img

ltth said:
I have the payload bin file, but can`t extract in payload_dumper-master (not working correctly so I get the boot.im
Click to expand...
Click to collapse
[Tutorial] Android OTA payload dumper on Android
Introduction This tutorial will teach you how to specifically extract the boot.img from your OTA/ROM's payload.bin on your Android device, rather than a computer. In addition to this, you will also have the ability to access all other img files...
forum.xda-developers.com
Use this link to extract the boot.img from payload.bin using your phone. Give a try. I also had issues extracting from pc. So did in my phone and worked.

jhosharath said:
Try extracting from your phone for payload.bin file. Or there is a "rooting my notes" discussion video in one of the post. You can see the
Click to expand...
Click to collapse

I found a Payload_Dumper wich worked very well, just have execute the scipt, then I got my boot.img
Thanks for your help!!

Can't side load apps after updating to Android 11 - HELP!

Xiaomi Mi 10T stock global stable. Updated to Android 11 and can no longer side load anything – not just Google apps, ANYTHING. Not even via ADB installation commands.
Then I learned that Google introduced something called "app integrity" with Android 11 that hinders side loading. It's a function of Google Play Services, which stores its rules in an inaccessible directory (so I can't delete them). I tried uninstalling Google Play Services altogether and cutting all access to the Internet, but that didn't work either.
There must be a workaround that doesn't involve me having to root my phone (too much hassle and risk for my liking), or reverting to Android 10 (is that even possible?).
Any help would be appreciated.

adb sideload is TWRP specific feature so if you updated your Android Version you need to update TWRP too so it support adb sideload once again ... or you just using adb sideload command directly ??

ineedroot69 said:
adb sideload is TWRP specific feature so if you updated your Android Version you need to update TWRP too so it support adb sideload once again ... or you just using adb sideload command directly ??
Click to expand...
Click to collapse
adb sideload is NOT TWRP specific.
ADB Sideload is a mode the bootloader loads device into if requested to do so.

jwoegerbauer said:
adb sideload is NOT TWRP specific.
Click to expand...
Click to collapse
read my post

ineedroot69 said:
adb sideload is TWRP specific feature so if you updated your Android Version you need to update TWRP too so it support adb sideload once again ... or you just using adb sideload command directly ??
Click to expand...
Click to collapse
Directly, I guess. Am I using it wrong? Tbh, I'm not a dev and don't know what TWRP is.
Before Android 11, I was always able to install APKs directly via the phone. Only after updating did I try it via ADB to see if it solves my problem and it didn't – despite ADB being properly installed and my use of the appropriate commands.

Don't confuse "Sideload an APK" and "ADB Sideload" as others here do.
ADB Sideload isn't the correct method to install ( sideload ) APKs.
Read here
How to Use ADB Sideload in Android [Stock and TWRP Recovery]
In this guide, we will show you how to install ZIP files using the adb sideload command in both the stock and custom TWRP Recovery.
www.droidwin.com
To sideload an APK you run adb install [Options] APK what of course requires USB-debugging got enabled on phone before.

i dunno about Android 11 but have you tried installing it casually then just enable "allow Install unknown apps" ??

jwoegerbauer said:
To sideload an APK you run adb install [Options] APK what of course requires USB-debugging got enabled on phone before.
Click to expand...
Click to collapse
Yes, this is what I tried but it didn't work unfortunately. I keep getting "Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user]".

ineedroot69 said:
i dunno about Android 11 but have you tried installing it casually then just enable "allow Install unknown apps" ??
Click to expand...
Click to collapse
C'mon bro, I'm not that much of a noob. It's allowed for all the apps from which I install APKs.
I can no longer install casually after updating to Android 11.

Dagabix said:
Yes, this is what I tried but it didn't work unfortunately. I keep getting "Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user]
Click to expand...
Click to collapse
On some devices "Install Via USB" must also get enabled.

jwoegerbauer said:
On some devices "Install Via USB" must also get enabled.
Click to expand...
Click to collapse
I always keep it enabled.

jwoegerbauer said:
On some devices "Install Via USB" must also get enabled.
Click to expand...
Click to collapse
^ ohh yeahi forgot that there's this setting on Developer Options it's called Verify app over USB you provably need to disable that since your apk is from unknown source

ineedroot69 said:
^ ohh yeahi forgot that there's this setting on Developer Options it's called Verify app over USB you provably need to disable that since your apk is from unknown source
Click to expand...
Click to collapse
It's always been disabled, except for the one time I enabled it to see if it would make a difference – it didn't.

Problem solved. Turns out uninstalling 'MIUI security components' (com.miui.guardprovider) when debloating is what caused me to lose the ability to side load!