Database Develop

Encryption with root

Are you not supposed to be able to encrypt the device when it is rooted? I tried but it just reboots, never doing anything.

You can encrypt a rooted phone, but I think you need the stock recovery for it to work (or it did with my Nexus phones, I haven't tried it on my Moto X 2014 yet). You could try flashing the stock recovery, encrypting then flashing TWRP/CWM back again.

Azarin said:
You can encrypt a rooted phone, but I think you need the stock recovery for it to work (or it did with my Nexus phones, I haven't tried it on my Moto X 2014 yet). You could try flashing the stock recovery, encrypting then flashing TWRP/CWM back again.
Click to expand...
Click to collapse
I'm on stock recovery

km8j said:
I'm on stock recovery
Click to expand...
Click to collapse
Sometimes Android can get confused and not encrypt your device - lots about it on googles issue tracker, but ensure your phone is fully charged, and plugged in at the time. Sometimes it takes people quite a few times, along with connecting/disconnecting the charger.
As a P.S. My moto x encrypted without issues, but it isn't rooted.

Azarin said:
Sometimes Android can get confused and not encrypt your device - lots about it on googles issue tracker, but ensure your phone is fully charged, and plugged in at the time. Sometimes it takes people quite a few times, along with connecting/disconnecting the charger.
As a P.S. My moto x encrypted without issues, but it isn't rooted.
Click to expand...
Click to collapse
I had a similar experience with my old phone - had to attempt encrypt multiple times, then it finally worked. Haven't encrypted this one yet, but I may have no choice for work.

What I did for my original Moto X was:
1) Unlock bootloader
2) Flash TWRP
3) Root the phone
4) Restore the phone to factory default but leaving the /data and /sdcard partitions in place
5) Encrypt the phone (you have no root at this point)
6) Flash TWRP
7) mount /sdcard and /data as tmpfs filesystems
8) Push the root.zip to one of the tmpfs using adb
9) TWRP can read the tmpfs /sdcard so I used root.
Step 9 fails to write files to the encrypted partition as /data is a tmpfs and the real /data is encrypted, but the files required are still there from the original rooting in Step 3. Now you have a rooted and encrypted phone. I forget the commands to do the tmpfs stuff and adb push, and I don't have an android phone at this time, but Google will help with those I'm sure.
This is a convoluted and annoying process, but it was the only way I could get root and encryption. I hope this helps.

I tried everything and still am not able to encrypt the phone with unlocked boot loader and root. I disabled supersu, rebooted into safe mode and turned on airplane mode.

edwardgtxy said:
I tried everything and still am not able to encrypt the phone with unlocked boot loader and root. I disabled supersu, rebooted into safe mode and turned on airplane mode.
Click to expand...
Click to collapse
Has anyone got some resolution on this? Rooted on the latest Lollipop build here. I've tried safe mode, fully charged, on the charger and every time it gets to the green android screen and then goes black on me.

I just did it yesterday. It didn't seem to be doing anything, but I left it alone and then suddenly it woke up to the encryption PIN entry screen. I'd say leave it alone longer than you think you should, and see what happens. I have stock recovery, BTW.

cbasse said:
I just did it yesterday. It didn't seem to be doing anything, but I left it alone and then suddenly it woke up to the encryption PIN entry screen. I'd say leave it alone longer than you think you should, and see what happens. I have stock recovery, BTW.
Click to expand...
Click to collapse
Any idea how long you left it alone (couple of minutes, 15-30 minutes, 1+ hours)? My device came with Lollipop; I unlocked the bootloader for my device using Motorola's instructions, then installed root according to this thread: http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154. I didn't install any custom recovery. I tried encrypting the phone multiple times, but each time it seems to get stuck at the black screen after shortly showing the android logo.
Edit: I finally got encryption to work; it looks like the device can't be encrypted with the rooting method that I used. In order to encrypt my phone, I flashed the stock ROM, did a factory reset, then encrypted it and installed root after that.

[Q] TWRP asks for password

I tried default_password and my lock screen password but neither works. Anyone know why I'm getting this prompt? Also, sometimes when I restart my phone it goes into a bootloop just showing the Google logo. However, if I turn my phone off and let it sit for several minutes and then turn it back on, it seems to boot up normally. Has anyone seen this before?
When i unlock my phone through fastboot a few days ago, I don't recall if I rebooted or not as required. If I didn't reboot, would that cause these weird kind of issues? I wonder what's causing the boot loop and why turning the phone off and letting it sit fixes the loop. I've used the toolkit now several times to restore and unroot. At this point, I'm thinking of relocking the phone and going through the entire process again except this time ensuring that I reboot after the unlock.
I wish Google had made the encryption optional. It's a real pain.

So, not sure what's causing the boot loops or why turn the phone off seems to work around it. But the reason I get a password prompt in recovery is because of android security setting for pattern (with prompt on boot) is activate. However, it doesn't ask me for a character based password so that when TWRP prompts for a password I don't know what to put because it doesn't accept a pattern obviously.
Should I not use pattern with prompt on boot since twrp won't work? Or am I a big dummy that's just missing something obvious??

soundneedle said:
So, not sure what's causing the boot loops or why turn the phone off seems to work around it. But the reason I get a password prompt in recovery is because of android security setting for pattern (with prompt on boot) is activate. However, it doesn't ask me for a character based password so that when TWRP prompts for a password I don't know what to put because it doesn't accept a pattern obviously.
Should I not use pattern with prompt on boot since twrp won't work? Or am I a big dummy that's just missing something obvious??
Click to expand...
Click to collapse
Read the twrp OP
Sent from my Nexus 6 using XDA Free mobile app

Ah...read this in the twrp op and makes sense now...
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
Click to expand...
Click to collapse
That explains one issue. Will have to keep my eye on the other issue where sometimes a reboot results in google-logo boot loop...which is resolved by turning the phone off for a few minutes. Lollipop is giving me a tummy ache, but I'm gonna keep lickin!

I had to unecrpyt my phone for it to stop looping even though the password was correct. It would say curvy l correct password but corrupted system. It's an easy fix vv

thanks for the info same happens to me.

[Q] Nexus 6 Won't Boot Into Recovery

Hello. Sorry if this issue already exists and I'm being negligent, but I have an interesting issue with TWRP. Whenever I try to boot to recovery, the screen stays at the teamwin splashscreen for a short time as it should, but then the device reboots normally and never allows me into the recovery. I've tried reflashing numerous older versions of TWRP via "fastboot flash recovery..." but the reboot still occurs. Just before this started happening I tried doing an "adb push..'" and that resulted in a permission denied. So I remounted using "mount -o rw,remount,rw /system" and the push succeeded. I'm pretty sure that this is at fault because I was able to get into recovery one time after playing with the writable and read only forms of the aforementioned command and wiping the cache via fastboot. Any ideas?

try deleting it first, via fastboot, then reflash it.

simms22 said:
try deleting it first, via fastboot, then reflash it.
Click to expand...
Click to collapse
I ran "fastboot erase recovery", reflashed TWRP, and the reboot still occured at the splashscreen.

It might be a long shot. Try and flash within Android using an app called Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Very simple app to use. :good:

Maverick-DBZ- said:
It might be a long shot. Try and flash within Android using an app called Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Very simply app to use. :good:
Click to expand...
Click to collapse
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?

Astrophysicist789 said:
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Click to expand...
Click to collapse
Yeah, enter your password.

Astrophysicist789 said:
Good news. That actually worked. I am able to use TWRP now. There's just one problem though. It asks for a password to decrypt the data partition. I've never seen this before. Any way to work around it?
Click to expand...
Click to collapse
Glad to hear it.
Sure, it's really simple, use your lock screen password. If you have a pattern lock you need to envision your pattern lock into numbers. The below example should help you out.
1 2 3
4 5 6
7 8 9
If you're still having problems, then just turn off pattern lock or use a regular numbered password. On the off chance what I said doesn't solve your problems, you can try one last thing.
Backup anything important on your phone before doing any of these steps below. Make sure lockscreen password is off. You can turn it back on once you've confirmed this worked.
1) Flash a modded stock boot image via Flashify, this will disable forced encryption.
2) Boot into bootloader and use fastboot format userdata
The command will wipe your phone to factory setting, so make sure you backed up! Flash a custom kernel after if you want.

Maverick-DBZ- said:
Glad to hear it.
Sure, it's really simple, use your lock screen password. If you have a pattern lock you need to envision your pattern lock into numbers. The below example should help you out.
1 2 3
4 5 6
7 8 9
Click to expand...
Click to collapse
I thought they got rid of this method and replaced it with something more pattern-lock like, in latest 2 versions?

danarama said:
I thought they got rid of this method and replaced it with something more pattern-lock like, in latest 2 versions?
Click to expand...
Click to collapse
It has been awhile since I've checked, so I had a look at the change logs and you're right, pattern lock was added in build 2.8.6.0. This should make it easier for @Astrophysicist789

Maverick-DBZ- said:
It has been awhile since I've checked, so I had a look at the change logs and you're right, pattern lock was added in build 2.8.6.0. This should make it easier for @Astrophysicist789
Click to expand...
Click to collapse
Further, if he hasn't set a lock, there should be a default TWRP one somewhere in the thread.

TWRP and Encryption password problem (or at least a question)

I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.

hachamacha said:
I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
Click to expand...
Click to collapse
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped

cameljockey1 said:
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
Click to expand...
Click to collapse
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.

hachamacha said:
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
Click to expand...
Click to collapse
Are you sure you had 3.5.3 the first time you did it?

c_86 said:
Are you sure you had 3.5.3 the first time you did it?
Click to expand...
Click to collapse
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.

hachamacha said:
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
Click to expand...
Click to collapse
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )

ghettopops said:
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
Click to expand...
Click to collapse
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )

hachamacha said:
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
Click to expand...
Click to collapse
Yes page 9 or 10 OP gives me a link

The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.

This seems to happen when you've got the fingerprint method enabled with PIN or password for that matter.

My experience:
I update from Oxygen 4.1.6 to 4.1.7 with TWRP and something went wrong because the phone stuck in bootload for more then half hour.
I've reboot and it appeared 'Encryption Unsuccessful' and it locked my phone. I tried to go to TWRP and it required the password that was 'default_password' but after it not allowed me to mount data and it seemed that there weren't any data in my phone.
I couldn't wipe, format or install other rom because I received error like 'unable to mount X'.
I've solved downloading the Oxygen Recovery and with a USB OTG, flashing it on my phone (with 'mount image' in TWRP).
I rebooted in Oxygen Recovery and it also asked me the password. I've just pushed 'Forgot password' and it formatted my phone.
The phone rebooted without problems (and without any data :\)
Hope to be useful for someone else in my same situation

You can get back in, without loosing any Data.
Go to TWRP
Choose Advanced
Select Terminal
Type this commands:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
reboot
Use Android again

I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.

astralbee said:
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
Click to expand...
Click to collapse
Same problem on one of my 3Ts, the other is working with the Oreo based TWRP.
Oreo based Red Wolf Recovery is working: https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/recovery-red-wolf-recovery-project-t3805416
These things are weird:
1. Why does one 3T work, but not the other 3T ?
2. Why does (Oreo based) Red Wolf Recovery work?
3. Why is OOS Beta 29 able to decrypt Data perfectly?
I assume it's a decryption related bug in Oreo based TWRP.

im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.

SourPower said:
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
What exactly is it you're trying to do? What TWRP are you using? What ROM?
You sound surprised that you can't see your Storage when you haven't entered a Password to Decrypt? That is, after all, what it's supposed to do. What security have you set up on your phone? Did you have Boot time security?
With so little useful information to go on it's hard to help. I'd recommend trying Red Wolf Recovery in any case. It's magic at solving many issues.

Sorry lol what happen was I was updating to latest stable oos, and had standard encryption set up. I wipes caches, and flashed latest rom, then magisk and again twrp (which I should not have) and then my phone had a quick reset. From there it was locked with twrp, neither my pin or default_pw worked so I just formated my phone, after copying data and important things to PC. Everything is good now just had to waste my own time.

For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.

raeee1 said:
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
Click to expand...
Click to collapse
Not so. I removed the password and TWRP still asks for a password.

hachamacha said:
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
Click to expand...
Click to collapse
This did not work for me.

Password doesn't always work.

My 4-digit password works just fine during normal use. But after upgrading to oxygenOS 5.0.1 (OTA) , I decided I wanted to revert back to nougat. So I load my backup in twrp and reboot, and it asks for my password rather than fingerprint to unlock screen because of reboot. And that's when my password is not recognized.
This is the only password Ive ever used for my phone so its definitely the right one. I can also see notifications and accept calls, it just won't unlock the screen. I also tried the default code for my simcard but even removing it doesnt make a difference.
Next, I restore my backup for 5.0.1. that I made prior to restoring nougat, and the same thing happens, password doesn't work. I had to do a factory reset to get my phone working again.
Still determined to get good old android 7 back, I install the original recovery as to upgrade from the oneplus website. And upon booting to recovery my password is once again not recognized.
I'm now back on twrp and have no problems with my passcode. But I think this is strange so maybe someone here has an idea about what's going on.

If you're restoring a backup, you have to remove gatekeeper.pattern (or password).key and locksettings.db, once removed it will work

I moved those files from data/system to data and it worked. Thank you very much!
I noticed this also removes the lock if you set it from another computer using the 'my devices' section of your google account. But it does not remove the lock notification, to do that you simply have to set a new password from your phone.

And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.

ast00 said:
And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.
Click to expand...
Click to collapse
AFAIK stock recovery allows only sideloading via adb

przemcio510 said:
AFAIK stock recovery allows only sideloading via adb
Click to expand...
Click to collapse
Not sure about Oneplus, but we have a Prestigio tablet here and I managed to delete an entire partition from the stock recovery. Wipe data didn't help a bootloop so I actually wiped it for good.
I hope other manufacturers aren't that foolish, but I'm not sure they know better.