Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- TWRP boots;
- Fastboot boot is working;
- Decryption is working (except for Oxygen OS);
- System, Vendor and Product partitions mount is not working but it's not a big problem;
- You can flash ROMs;
- Format Data is broken;
- You can flash magisk
Install guide (Reccomended):
Acutally seems oneplus (or directly android 10) re-introduced the recovery partition so you should only flash it in recovery partition or you can try to boot it from fastboot. For now only boot it.
To flash:
Code:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Tips:
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.4.0-2 Test by mauronofrio
TWRP 3.4.0-0 Test by mauronofrio
TWRP 3.3.1-43 Test by mauronofrio
TWRP 3.3.1-25 Test by mauronofrio
TWRP 3.3.1-5 Test by mauronofrio
TWRP 3.3.1-0 Test by mauronofrio
Stock Recovery
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_hotdog_unified_TWRP
Kernel source: precompiled stock one
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
I want to say a big thanks to the testers @houmles and @ChrisFeiveel84
Created 2019-10-02
This is a first test TWRP, i have not tested it because i have not the device, if someone want to help me in testing it, contact me or leave a comment.
Actually i don't know if fastboot boot command will work or not. Fastboot boot is working
I'm sure the twrp will not be able to decrypt the internal storage TWRP is not decrypting
If someone test it, please give me a feedback, it's a first build and i have to make some others fixes Still need of more testers
I am willing to test.
But if it can't decrypt storage, how can I test it ?
Just boot it ?
Another if something goes wrong, is there any chance I need to format data ?
Cause I don't want to loose my 180gb+ data.
.
I tried to root stock boot.img with Magisk patcher beta and canary, but it's not booting at all.
.
Also, this is A/B device.
So for installing trwp, we need patch stock boot.img ramdisk as recovery is in it.
Please check Oneplus 7 Pro threads.
RohanAJoshi said:
I am willing to test.
But if it can't decrypt storage, how can I test it ?
Just boot it ?
Another if something goes wrong, is there any chance I need to format data ?
Cause I don't want to loose my 180gb+ data.
.
I tried to root stock boot.img with Magisk patcher beta and canary, but it's not booting at all.
.
Also, this is A/B device.
So for installing trwp, we need patch stock boot.img ramdisk as recovery is in it.
Please check Oneplus 7 Pro threads.
Click to expand...
Click to collapse
Try to boot it first...
If its working you can just flash magisk to root
You dont need the patched img
I also don't have the device
OP6T
OB17
mauronofrio said:
This is a first test TWRP, i have not tested it because i have not the device, if someone want to help me in testing it, contact me or leave a comment.
Actually i don't know if fastboot boot command will work or not.
I'm sure the twrp will not be able to decrypt the internal storage
Click to expand...
Click to collapse
Hi, did you build this stock kernel sources for Oneplus 7T ?
RohanAJoshi said:
Hi, did you build this stock kernel sources for Oneplus 7T ?
Click to expand...
Click to collapse
I used the one from the stock rom, i got some problems to build the kernel from the sources.
mauronofrio said:
I used the one from the stock rom, i got some problems to build the kernel from the sources.
Click to expand...
Click to collapse
Will you please share rooted boot.img which you build from sources ?
I am not able get root even after patching current boot.img with Magisk stable beta and canary.
RohanAJoshi said:
Will you please share rooted boot.img which you build from sources ?
I am not able get root even after patching current boot.img with Magisk stable beta and canary.
Click to expand...
Click to collapse
I have not used a rooted boot.img for the twrp, in all cases i don't think it's a kernel problem, maybe it's a magisk problem.
So the twrp is partially working, decryption is the biggest problem.
mauronofrio said:
I used the one from the stock rom, i got some problems to build the kernel from the sources.
Click to expand...
Click to collapse
What problems?
Should still be able to push to /temp to be able to flash. But may need the stock recovery in order to wipe properly.
Same issue on the p20 Pro, it's never been fixed.
ADB push /temp
Reboot to download mode
Flash stock recovery
Wipe data
Boot.
But I've not worked with 10 yet so not sure.
Hard bricked OnePlus 7t
Hi, I’ve hardbricked my Oneplus 7t. It’s stuck on the fastboot screen. Please let me know how to fix it. I’m terribly scared. I can’t even boot to twrp. Pressing the power button keeps bringing me back to the fastboot screen. Please help!
How2Kritin said:
Hi, I’ve hardbricked my Oneplus 7t. It’s stuck on the fastboot screen. Please let me know how to fix it. I’m terribly scared. I can’t even boot to twrp. Pressing the power button keeps bringing me back to the fastboot screen. Please help!
Click to expand...
Click to collapse
Check fastboot images in general thread.
RohanAJoshi said:
Check fastboot images in general thread.
Click to expand...
Click to collapse
Hi, I don’t understand what you mean by this, could you please explain it to me? Sorry for being dumb.
How2Kritin said:
Hi, I don’t understand what you mean by this, could you please explain it to me? Sorry for being dumb.
Click to expand...
Click to collapse
Check this thread
https://forum.xda-developers.com/oneplus-7t/how-to/stock-fastboot-flashable-images-oneplus-t3977623
RohanAJoshi said:
Check fastboot images in general thread.
Click to expand...
Click to collapse
nikhilsnigam said:
Check this thread
https://forum.xda-developers.com/oneplus-7t/how-to/stock-fastboot-flashable-images-oneplus-t3977623
Click to expand...
Click to collapse
Hi, I’ve tried this but it said that logo_a, logo_b, system_a, system_b, vendor_a, vendor_b partitions not found. Everything else worked. The phone is still stuck in the same screen with no change.
Actually for root there are some magisk problems, the device has a a/b structure but the boot partition is like a-only device, so magisk should be modified to make it works properly on this device. The better way is to report the problem to topjohnwu with logs and more.
mauronofrio said:
Actually for root there are some magisk problems, the device has a a/b structure but the boot partition is like a-only device, so magisk should be modified to make it works properly on this device. The better way is to report the problem to topjohnwu with logs and more.
Click to expand...
Click to collapse
The problem is I didn’t really attempt to root, it just got stuck in this mode.
---------- Post added at 06:26 AM ---------- Previous post was at 06:22 AM ----------
How2Kritin said:
Hi, I’ve tried this but it said that logo_a, logo_b, system_a, system_b, vendor_a, vendor_b partitions not found. Everything else worked. The phone is still stuck in the same screen with no change.
Click to expand...
Click to collapse
EDIT: The phone is now stuck in a “Qualcomm crash dump mode” saying “dm-verity device corrupted force dump
kernel-restart”
What do I do now?
How2Kritin said:
The problem is I didn’t really attempt to root, it just got stuck in this mode.
---------- Post added at 06:26 AM ---------- Previous post was at 06:22 AM ----------
EDIT: The phone is now stuck in a “Qualcomm crash dump mode” saying “dm-verity device corrupted force dump
kernel-restart”
What do I do now?
Click to expand...
Click to collapse
To quit from crash dump mode you should keep pressed both volumes buttons and power button for 30 seconds
mauronofrio said:
To quit from crash dump mode you should keep pressed both volumes buttons and power button for 30 seconds
Click to expand...
Click to collapse
I’ve done this and it just rebooted into fastboot mode like before, what do I do now to fix it?
Please guide me
How2Kritin said:
I’ve done this and it just rebooted into fastboot mode like before, what do I do now to fix it?
Please guide me
Click to expand...
Click to collapse
The bootloader is unlocked?
Related
I have do a port of TWRP from Vernee Mars Pro (Jemmini build) to MAZE Alpha (MT6757D) it works well if booting it directly by fastboot, but when flashing it and reboot into recovery the touch screen not works!
This is working
Code:
fastboot boot twrp-recovery.img
This is not working : issue with touch screen
Code:
fastboot flash recovery twrp-recovery.img
Curiously, if I flash it into boot partition (insead of recovery partition) and reboot, it works!
Code:
fastboot flash boot twrp-recovery.img
Can any one help please ?
Sir please make a twrp for lenovo k5 note
No one never have an issue like this ?
how it can be possible that a recovery image works well when booted and not when flashed ?
Can at least someone please explain to me how the process of boot from the recovery partition is different from the boot from the boot partition ?
Just for test, I have flashed the boot.img in the recovery partition and reboot to recovery (it will do a normal boot, because the recovery is a simple boot now) and I loss the touch screen in the booted Android !!
Why one can loss some drivers just when we change the boot partition (from boot to recovery) ?
Please help.
dreambo said:
No one never have an issue like this ?
how it can be possible that a recovery image works well when booted and not when flashed ?
Can at least someone please explain to me how the process of boot from the recovery partition is different from the boot from the boot partition ?
Just for test, I have flashed the boot.img in the recovery partition and reboot to recovery (it will do a normal boot, because the recovery is a simple boot now) and I loss the touch screen in the booted Android !!
Why one can loss some drivers just when we change the boot partition (from boot to recovery) ?
Please help.
Click to expand...
Click to collapse
I'm no expert on the subject, but my mildly educated guess is that the recovery partition is overwriting something.
Booting into recovery from fastboot forces a total restart before going into recovery. Booting from fastboot forces you into recovery without the shutdown, so there's no wipe.
@[email protected]
Any idea?
ninjasinabag said:
I'm no expert on the subject, but my mildly educated guess is that the recovery partition is overwriting something.
Booting into recovery from fastboot forces a total restart before going into recovery. Booting from fastboot forces you into recovery without the shutdown, so there's no wipe.
@[email protected]
Any idea?
Click to expand...
Click to collapse
To be honest. I didn't have that problem. I flashed through messi2050's twrp but it should be able to flash. Did you have that problem?
---------- Post added at 09:14 PM ---------- Previous post was at 08:59 PM ----------
Bootloader has to be unlocked and to flash it the code is
Fastboot flash recovery twrp.3.1.1-0_lv3.img
I just ran it myself and it works. Make sure your recovery image is on the same path as adb and fastboot. Example if it is on the Desktop than you cd Desktop than fastboot flash ,etc.
---------- Post added at 09:24 PM ---------- Previous post was at 09:14 PM ----------
https://youtu.be/INAMo9RNAXs
Proof of flash
[email protected] said:
To be honest. I didn't have that problem. I flashed through messi2050's twrp but it should be able to flash. Did you have that problem?
---------- Post added at 09:14 PM ---------- Previous post was at 08:59 PM ----------
Bootloader has to be unlocked and to flash it the code is
Fastboot flash recovery twrp.3.1.1-0_lv3.img
I just ran it myself and it works. Make sure your recovery image is on the same path as adb and fastboot. Example if it is on the Desktop than you cd Desktop than fastboot flash ,etc.
---------- Post added at 09:24 PM ---------- Previous post was at 09:14 PM ----------
https://youtu.be/INAMo9RNAXs
Proof of flash
Click to expand...
Click to collapse
Thank you for your interest to my problem
The flash itself to the recovery partition works well (fastboot flash recovery twrp.img), and when we reboot to recovery, we have a working TWRP recovery except the fact that the touch screen not works.
the same flash to the boot partition (yes we will loss the Android OS, just for test purpose) with this : fastboot flash boot twrp.img works well, and when we reboot (normal reboot in this case) we have a 100% TWRP.
dreambo said:
The flash itself to the recovery partition works well (fastboot flash recovery twrp.img), and when we reboot to recovery, we have a working TWRP recovery except the fact that the touch screen not works.
Click to expand...
Click to collapse
Some kernels are known to disable the touch device when boot mode is recovery. Check your kernel sources.
dreambo said:
Thank you for your interest to my problem
The flash itself to the recovery partition works well (fastboot flash recovery twrp.img), and when we reboot to recovery, we have a working TWRP recovery except the fact that the touch screen not works.
the same flash to the boot partition (yes we will loss the Android OS, just for test purpose) with this : fastboot flash boot twrp.img works well, and when we reboot (normal reboot in this case) we have a 100% TWRP.
Click to expand...
Click to collapse
I apologized to you I misunderstood your statement and questions as related to the LG Aristo twrp recovery and didn't read that you have a Maze Alpha. Have you tried compiling it from sources instead of porting it? Just a question. If you need help I'm sure someone can help you.
_that said:
Some kernels are known to disable the touch device when boot mode is recovery. Check your kernel sources.
Click to expand...
Click to collapse
Thank you very match :good:
It may be the case for my kernel.
That explain why if I boot any thing from recovery (normal boot.img or recovery.img) I loss the screen touch.
I do not have the kernel sources, only binaries, can I patch it ?
Or even do an hex search to be sure that my kernel is in this case ?
[email protected] said:
I apologized to you I misunderstood your statement and questions as related to the LG Aristo twrp recovery and didn't read that you have a Maze Alpha. Have you tried compiling it from sources instead of porting it? Just a question. If you need help I'm sure someone can help you.
Click to expand...
Click to collapse
Thank you, I will do a compilation if I cannot resolve this issue.
I have some knowledge on compiling, but the tutorials I find for compiling TWRP are not user friendly at all
I expect things like :
1- download the sources (wget, svn, git ...)
2- configure
3- make
Do you know a tutorial more usable ?
Thank you again
No the tutorials are hard for someone that had never complied a recovery but the XDA thread for it has some decent peoples that will respond. Send me the boot image build prop and what android version it's on and I'll try to compile one for you. My email is my name. [email protected]
No promises but I'll see what can be done
[email protected] said:
No the tutorials are hard for someone that had never complied a recovery but the XDA thread for it has some decent peoples that will respond. Send me the boot image build prop and what android version it's on and I'll try to compile one for you. My email is my name. [email protected]
No promises but I'll see what can be done
Click to expand...
Click to collapse
Very nice
I will do that this night at home.
Many thanks
_that said:
Some kernels are known to disable the touch device when boot mode is recovery. Check your kernel sources.
Click to expand...
Click to collapse
Please just an other question :
Do you know an Android Kernel sources that do that check (if we are in recovery mode or not) ?
If I can have an example of source code that do that check, I can, create a binary patch :
Just compile a sample code source that do the same check, locate it in the result ASM code and I can create a patch later for my binary kernel, with some ASM code, with the same length, that can tell that we are never in recovery mode.
What do you think to that procedure ?
dreambo said:
Please just an other question :
Do you know an Android Kernel sources that do that check (if we are in recovery mode or not) ?
If I can have an example of source code that do that check, I can, create a binary patch :
Just compile a sample code source that do the same check, locate it in the result ASM code and I can create a patch later for my binary kernel, with some ASM code, with the same length, that can tell that we are never in recovery mode.
What do you think to that procedure ?
Click to expand...
Click to collapse
I think you should just get the kernel sources. If that's not possible, someone sold you a device with an illegal copy (aka "warez") of the kernel, and discussing warez is forbidden by the forum rules.
_that said:
I think you should just get the kernel sources. If that's not possible, someone sold you a device with an illegal copy (aka "warez") of the kernel, and discussing warez is forbidden by the forum rules.
Click to expand...
Click to collapse
Thank you but we are 100% discussing development here
I am trying to bypass completely the need of the sources, by patching the kernel binary (as some root apps do)
I have compared the 2 boots of the recovery :
1- When I boot with fastboot boot recovery. img I have noticed (by connecting with adb) the presence of this 2 folders
Code:
/sys/devices/virtual/input/input8
/sys/devices/virtual/input/input9
2- When I boot the same recovery.img already flashed by fastboot flash recovery recovery.img this 2 folders are missing!
I have do a simple tar of this 2 folders from the working recovery and when I try to restore them : Operation not allowed (or something like that)
How can I restore this 2 folders ?
dreambo said:
How can I restore this 2 folders ?
Click to expand...
Click to collapse
You can't. They are created by the device drivers for those input devices.
This will give you the list of input devices with their name:
Code:
grep . /sys/class/input/event*/device/name
Maybe you find the string "recovery" near these names somewhere in your kernel.
_that said:
You can't. They are created by the device drivers for those input devices.
This will give you the list of input devices with their name:
Code:
grep . /sys/class/input/event*/device/name
Maybe you find the string "recovery" near these names somewhere in your kernel.
Click to expand...
Click to collapse
Thank you
I found only one string "recovery" (kpd-hw-recovery, a sheatcode for the kernel I suppose) I replace it with an other string with the same length: the same issue
dreambo said:
Thank you
I found only one string "recovery" (kpd-hw-recovery, a sheatcode for the kernel I suppose) I replace it with an other string with the same length: the same issue
Click to expand...
Click to collapse
I didn't forget about you I am currently working on a project then I will tackle it.
[email protected] said:
I didn't forget about you I am currently working on a project then I will tackle it.
Click to expand...
Click to collapse
Don't worry, take your time
As @_that said, the problem is the kernel that disable touch when it detect the recovery mode, I am not sure at 100% that a compilation (without the kernel sources) can resole our issue.
Thank you for your help.
[!]NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.[!]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Installation
-Reboot into fastboot
-use the command: fastboot flash recovery_ramdisk twrp-X-X-X
CHANGELOG for 3.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
Dil3mm4's Changelog
-Added splash2 partition as mountable to obtain failure logs.
-/cust as TWRP settings holder
Download
TWRP 3.2.1-0 April 6th build
TWRP 3.2.1-0 April 8th build
TWRP 3.2.1-0 April 8th build Round 2
NOTE:
This recovery was built for PRA-LX1.
But after some P20 lite users report, I've added it over here since it's working on this device too.
Still, I don't have the device in my hands.
So every bug report about eventual bugs, should be really detailed.
XDA:DevDB Information
TWRP , Tool/Utility for the Huawei P20 Lite
Contributors
dil3mm4.dev, TeamWin Recovery Project
Version Information
Status: Stable
Created 2018-04-27
Last Updated 2018-04-26
HI,dil3mm4.dev
can you open twrp device code push to github?
@dil3mm4.dev
poppy22 said:
HI,dil3mm4.dev
can you open twrp device code push to github?
@dil3mm4.dev
Click to expand...
Click to collapse
The device tree needs a cleanup.
As soon as I'll do that it will be publicly pushed over a github repo.
Thanks for your interest.
Thanks for your efforts, are you working on a way to enable data decryption ?
I saw that the P20 Pro and P20 have now decrypting enabled twrp, maybe we'll have it soon so we can start to work on custom roms, cause without backup/restore it's a pain to try a build and revert back to stock
@dil3mm4.dev
sorry, this twrp nothing for Huawei P20 Lite WITH delivered OREO
you can flash this twrp, it start, touch work - but without decryption NO backup/recovery
on Honor 9 Lite work this trick : flash twrp, format data, reboot from twrp to twrp
on Huawei P20 Lite this trick NOT work
phone need factory-reset, format data lowlevel AND after this : data again encrypted
i am test if twrp install work : install SuperSU, write it doing, reboot, NO SuperSU
I am so sorry for your good work ! :good:
This twrp work on Huawei P20 Lite (OREO) NOT
twrp with de/encrypting is very tricky programming
look on the work from Pretoriano80 & Co (example : https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400)
we need now for OREO twrp with de/encrypting
the disaster is : it's give 1 and the same phone with delivered "N" and now with delivered "O" - this leads to misunderstandings
these are 2 completely different phones (with the same name, hardware, look)
JamesBott said:
@dil3mm4.dev
sorry, this twrp nothing for Huawei P20 Lite WITH delivered OREO
you can flash this twrp, it start, touch work - but without decryption NO backup/recovery
on Honor 9 Lite work this trick : flash twrp, format data, reboot from twrp to twrp
on Huawei P20 Lite this trick NOT work
phone need factory-reset, format data lowlevel AND after this : data again encrypted
i am test if twrp install work : install SuperSU, write it doing, reboot, NO SuperSU
I am so sorry for your good work ! :good:
This twrp work on Huawei P20 Lite (OREO) NOT
twrp with de/encrypting is very tricky programming
look on the work from Pretoriano80 & Co (example : https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400)
we need now for OREO twrp with de/encrypting
the disaster is : it's give 1 and the same phone with delivered "N" and now with delivered "O" - this leads to misunderstandings
these are 2 completely different phones (with the same name, hardware, look)
Click to expand...
Click to collapse
I don't get what actually you're saying.
As stated in the OP, there's no decryption and no MTP.
So you're not bringing up that much of a news over here.
As soon as I'll have something new to popup with, I will.
Next time you post, do use your "mother" language (if I did miss something), because with that english, I'm not able to understand everything you said.
Have a nice day.
This recovery was built for PRA-LX1.
But after some P20 lite users report, I've added it over here since it's working on this device too.
Still, I don't have the device in my hands.
@dil3mm4.dev
I respect your work ! I test many other twrp on HuP20L and this twrp start, touch work !
I have this phone in my hand. Can i help you ? Write, what you need and i do for you.
I need twrp for this phone !
This is english Forum, my mother-speak is german, my english is learning by writing and google-translation.
I hope you understand this text.
How can i help you ?
Hey guys, I´d like to know if I can install this on my ANE-LX1.... ???
Thank you
EDIT: Okay, I tried its not working..
Ty btw..
Greetings
Hey i am trying to
Code:
fastboot boot recovery.img
in order to pull the stock recovery in case anything goes wrong but it seems to give me the following error
Code:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.260s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.264s
I know this has nothing to do with the recovery itself but i might as well ask here for solutions to this.
Barrel Titor said:
Hey i am trying to
in order to pull the stock recovery in case anything goes wrong but it seems to give me the following error
I know this has nothing to do with the recovery itself but i might as well ask here for solutions to this.
Click to expand...
Click to collapse
You can't boot TWRP on huawei devices and many others afaik. You have to flash it
Sent from my HUAWEI BLA-L29 using XDA Labs
Hi there,
Been doing some digging, I'm currently on the p20 pro and looking for a treble compatible twrp, do you think this may work on the p20 pro?
If not then thanks all the same.
dladz said:
Hi there,
Been doing some digging, I'm currently on the p20 pro and looking for a treble compatible twrp, do you think this may work on the p20 pro?
If not then thanks all the same.
Click to expand...
Click to collapse
if you can get access to the update zip for your current firmware, then flash this recovery and give it a go, worst that will happen is it wont boot into recovery and you flash back the standard recovery. you need to extract it from the update.zip for your firmware. most of them seem interchangeable to some degree. it will be the recovery_ramdis in the update.zip although you flash using recovery_ramdisk.
i did something similar on my mate 10 pro and it worked okay.
I have another TWRP here could but doesn't decrypt, so have to remove pin / password can i just flash that if this one doesn't work??
Or would it have to be stock?
You could flash either of them to see if they work. If they all fail, just flash back the stock recovery ramdisk. Are you trying to flash a treble ROM. ???
DANIELWHITT said:
You could flash either of them to see if they work. If they all fail, just flash back the stock recovery ramdisk. Are you trying to flash a treble ROM. ???
Click to expand...
Click to collapse
Yes I was but I'm feeling quite disheartened now. None of them have worked
Flashed via flash system in fastboot but was having none of it
That phone runs the same internals pretty much as the mate 10 pro. I flashed phhussons treble ROM via the system.img in fastboot and all I had to do was do a factory reset, or low level format as Huawei calls it and the phone booted fine. What issues are you having because flashing via system.img is really easy. ?? Alot less hassle than twrp. ??
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
If I remember right. I went into bootloader, did a fastboot -w to wipe, then flashed the new system image and then a low level format via erecovery to get it to boot. ??
DANIELWHITT said:
That phone runs the same internals pretty much as the mate 10 pro. I flashed phhussons treble ROM via the system.img in fastboot and all I had to do was do a factory reset, or low level format as Huawei calls it and the phone booted fine. What issues are you having because flashing via system.img is really easy. ?? Alot less hassle than twrp. ??
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
If I remember right. I went into bootloader, did a fastboot -w to wipe, then flashed the new system image and then a low level format via erecovery to get it to boot. ??
Click to expand...
Click to collapse
So in order...
Wipe
Flash ROM / IMG
Factory rest via twrp?
We're you referring to me by the way?
dladz said:
So in order...
Wipe
Flash ROM / IMG
Factory rest via twrp?
We're you referring to me by the way?
Click to expand...
Click to collapse
Yes, lol
the way i did it was with a stock recovery and system image
boot into erecovery and do a factory reset or a fastboot -w
boot back into the bootloader
flash the system image for the treble rom
then go into erecovery and do a factory reset
and then it should boot no problem at all
twrp cant wipe properly on treble roms
ive done the same on my p20 lite today, all stock and no issues booting at all
let me know how you get on
:good:
DANIELWHITT said:
Yes, lol
the way i did it was with a stock recovery and system image
boot into erecovery and do a factory reset or a fastboot -w
boot back into the bootloader
flash the system image for the treble rom
then go into erecovery and do a factory reset
and then it should boot no problem at all
twrp cant wipe properly on treble roms
ive done the same on my p20 lite today, all stock and no issues booting at all
let me know how you get on
:good:
Click to expand...
Click to collapse
Aye I'll give it a whirl pal, so unfamiliar though.
Never would have thought that twrp would be the fault. But it makes perfect sense.
dladz said:
Aye I'll give it a whirl pal, so unfamiliar though.
Never would have thought that twrp would be the fault. But it makes perfect sense.
Click to expand...
Click to collapse
Huawei phones are a wierd bunch to work on, but once you get the hang of it, it will be all good.
id be suprised if you have any issues.
let me know how you get on
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP For Jasmine
Source Device Tree: Device Tree For Building TWRP
Temporary using guide:
Download this TWRP,
fastboot boot TWRP.img
Flash installer zip
(NEED TWRP 1020 or later)
If you have better way,tell meThanks.
Reserved
is it work >?
TingyiChen said:
Temporary using guide:
Download this TWRP,
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
then reboot and hold Volume Up to boot,you will enter TWRP
Go Back to System:
Activate Slot A at TWRP Reboot Menu and reboot
If you have better way,tell meThanks.
Click to expand...
Click to collapse
WILL THIS COMMAND ( fastboot boot twrp.img) work on this device for only boot into twrp >??
tnmsrkr said:
WILL THIS COMMAND ( fastboot boot twrp.img) work on this device for only boot into twrp >??
Click to expand...
Click to collapse
No,due to some AB special thing,directly fastboot boot twrp.img will cause a reboot on splash screen and brick ur data,only wipe data can enter system again
How can I install Magisk from the TWRP of Slot B in Slot A? When trying to install it detects Slot B and installs it in it.
TheXenons said:
How can I install Magisk from the TWRP of Slot B in Slot A? When trying to install it detects Slot B and installs it in it.
Click to expand...
Click to collapse
There should be a change slots option
I think you need bootctrl package to install TWRP to both slots. Also need to tell which slots are a & b. check any other device with ab slots, like Moto X4.
https://github.com/TeamWin/android_device_motorola_payton
TingyiChen said:
No,due to some AB special thing,directly fastboot boot twrp.img will cause a reboot on splash screen and brick ur data,only wipe data can enter system again
Click to expand...
Click to collapse
Really, I'm assuming A2 A/B is different to OnePlus 6 but what we do is fastboot boot twrp and then flash the official twrp and all is working. A bit weird it's different on A2.
munchy_cool said:
I think you need bootctrl package to install TWRP to both slots. Also need to tell which slots are a & b. check any other device with ab slots, like Moto X4.
https://github.com/TeamWin/android_device_motorola_payton
Click to expand...
Click to collapse
hmm maybe?Cuz I am not familiar with AB now..Still reading documentations...
Anybody has any idea on how to install supersu or magisk?
secosan said:
Anybody has any idea on how to install supersu or magisk?
Click to expand...
Click to collapse
For magisk or supersu you can use patched boot flashable trough fastboot command, with twrp i have really no idea if there are some flashable zip or similar
This recovery done nothing as it was installed on _b rather than _a, so it's not modifying _a partition. and if we flashed it on _a, it will get bootloop/asking to reset data, even we flashed lazypatcher. And our device get bootloop to on _b partition.
You can use this to root, just flash it on boot_a. It was made by magisk manager with patch boot image method. You still need to install magisk manager to get root.
Don't install magisk xposed or you will facing bootloop/asking to reset data. If that happen and you don't want to lose your data, flash twrp from this thread to boot_a, use magisk recovery manager to uninstall xposed module, and then flash magisk boot from me again to boot_a. reboot afterwards.
Magisk boot image on 9.6.9.0.ODIMIFE : https://drive.google.com/file/d/1sMFjQVLvj_cX_tht7-woSQQ4YlCF_i4i/view?usp=sharing
grzpra said:
This recovery done nothing as it was installed on _b rather than _a, so it's not modifying _a partition. and if we flashed it on _a, it will get bootloop/asking to reset data, even we flashed lazypatcher. And our device get bootloop to on _b partition.
You can use this to root, just flash it on boot_a. It was made by magisk manager with patch boot image method. You still need to install magisk manager to get root.
Don't install magisk xposed or you will facing bootloop/asking to reset data. If that happen and you don't want to lose your data, flash twrp from this thread to boot_a, use magisk recovery manager to uninstall xposed module, and then flash magisk boot from me again to boot_a. reboot afterwards.
Magisk boot image : https://drive.google.com/file/d/1sMFjQVLvj_cX_tht7-woSQQ4YlCF_i4i/view?usp=sharing
Click to expand...
Click to collapse
Which version of ROM do I need to have to flash the patched boot.img? Also, are the modules working?
emperor8696 said:
Which version of ROM do I need to have to flash the patched boot.img? Also, are the modules working?
Click to expand...
Click to collapse
my rom ver is 9.6.9.0.ODIMIFE, and the modules is working.
When should we expect official?
grzpra said:
Magisk boot image on 9.6.9.0.ODIMIFE : https://drive.google.com/file/d/1sMFjQVLvj_cX_tht7-woSQQ4YlCF_i4i/view?usp=sharing
Click to expand...
Click to collapse
Thank you, you saved my day. My Mi A2 (Global) finally has Root.
I tried with the howtos from the internet and installing different Magisk zip files through TWRP, nothing worked.
Is it possible to get a Magisk 16.7 boot image?
Roi Danton said:
Is it possible to get a Magisk 16.7 boot image?
Click to expand...
Click to collapse
I got it myself. With your image (from a older stock ROM) wifi did not work anymore.
If someone is interested, I got a patched boot.img from stock ROM V9.6.10.0.ODIMIFE and Magisk 16.7.
Roi Danton said:
Thank you, you saved my day. My Mi A2 (Global) finally has Root.
I tried with the howtos from the internet and installing different Magisk zip files through TWRP, nothing worked.
Is it possible to get a Magisk 16.7 boot image?
Click to expand...
Click to collapse
If your rom is updated, i can't. As mine were Mi6x not A2, but it work with cross flashing with a little modification (don't know if it from A2 to Mi6x).
You can patch it yourself with magisk manager, copy the boot image from fastboot rom to your phone, in magisk manager you need to choose install and then select patch boot image. You need to be on "unroot" condition, just flash the original boot.img rom first with fastboot.
grzpra said:
If your rom is updated, i can't. As mine were Mi6x not A2, but it work with cross flashing with a little modification (don't know if it from A2 to Mi6x).
You can patch it yourself with magisk manager, copy the boot image from fastboot rom to your phone, in magisk manager you need to choose install and then select patch boot image. You need to be on "unroot" condition, just flash the original boot.img rom first with fastboot.
Click to expand...
Click to collapse
Thank you. As I wrote here I have a patched boot.img for stock ROM V9.6.10.0.ODIMIFE and Magisk 16.7 - which works pretty good. With your boot.img I had the problem that wifi did not work anymore.
If someone needs the patched boot.img, get in contact with me.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
DOWNLOAD: https://twrp.me/sony/sonyxperiaxa2ultra.html
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][discovery] TWRP Touch Recovery [OFFICIAL], ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/TeamWin
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-10-30
Last Updated 2020-06-25
Thank you for this. I was able to boot the recovery and install magisk on my device. Is there any way to make the recovery permanent or do we have to fastboot the recovery every time?
Aklenz07 said:
Thank you for this. I was able to boot the recovery and install magisk on my device. Is there any way to make the recovery permanent or do we have to fastboot the recovery every time?
Click to expand...
Click to collapse
Not yet. Thought I don't think it's worth to /install/ it anyway.
Error flash
Hi,
I installed LineageOS but when I want to flash the "recovery", I am in error...
"target reported max download size of 536870912 bytes
sending 'recovery' (57720 KB)...
OKAY [ 1.281s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.284s"
Why ?
GunnarZX said:
Hi,
I installed LineageOS but when I want to flash the "recovery", I am in error...
"target reported max download size of 536870912 bytes
sending 'recovery' (57720 KB)...
OKAY [ 1.281s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.284s"
Why ?
Click to expand...
Click to collapse
You don't flash it.
LuK1337 said:
You don't flash it.
Click to expand...
Click to collapse
Just boot only ?
GunnarZX said:
Just boot only ?
Click to expand...
Click to collapse
That's all you need.
Done
It messed up (bootloop) at first, but second time worked fine.
Messed up my Xperia XA2 ultra
Hi i tried to use twrp 3 to install lineage OS.
Unlocked bootloader.
Fastboot boot the twrp.img
Backed up the device
Installed lineage os 15.1 and got an error
So decided to roll back to stock os
Restored the backup files.
It failed to restore it: device in bootloop.
I tried to use sony flashtool got an error; usb debug off
Can anybody help me?
bsbrfb said:
Hi i tried to use twrp 3 to install lineage OS.
Unlocked bootloader.
Fastboot boot the twrp.img
Backed up the device
Installed lineage os 15.1 and got an error
So decided to roll back to stock os
Restored the backup files.
It failed to restore it: device in bootloop.
I tried to use sony flashtool got an error; usb debug off
Can anybody help me?
Click to expand...
Click to collapse
Restore phone with Sony flash tool
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Install Lineage properly
https://wiki.lineageos.org/devices/discovery/install
Hi
Will this work on H3223 ?
Can this h3223 be rooted
mchlbenner said:
Hi
Will this work on H3223 ?
Can this h3223 be rooted
Click to expand...
Click to collapse
Unsure about root... Yet... But if you are bootloader unlocked you should at least be able to boot to twrp...
mchlbenner said:
Hi
Will this work on H3223 ?
Can this h3223 be rooted
Click to expand...
Click to collapse
Yes it roots
appleknight said:
Yes it roots
Click to expand...
Click to collapse
Magisk, and patch n flash boot.img?
Sorry mate, i'm coming from a device where kernel and ramdisk were separate partitions...
EDIT: Yes. Exactly
Aklenz07 said:
Restore phone with Sony flash tool
How Do I unlock the device?
I get an error saying my device is locked
Click to expand...
Click to collapse
tournelhenry said:
Aklenz07 said:
Restore phone with Sony flash tool
How Do I unlock the device?
I get an error saying my device is locked
Click to expand...
Click to collapse
https://wiki.lineageos.org/devices/discovery/install it tells you how to unlock
Click to expand...
Click to collapse
bootloader enter your imei it will give a key following all instructions precisely. it tells you the rxact command to use for unlocking the bootloader. after its unlocked, open your command prompt in your adb /fastboot folder. then adb reboot bootloader. after reboot phone will be blank screen. you have to download twrp 3.3.0.0 .img its the most updated. do that before the adb thing. then after adb thing, when you are booted into bootloader.....fastboot boot twrpxxxxx.img
this will boot into recovery. make sure you have magisk 19.zip doenloaded to your phone. then just flash magisk from the recovery, after reboot install magisk apk. there you go. sorry all of this is not in order. ive done it so many times im skipping ahead. i can give a better detailed and precise instructions if needed, litterally walk you thru it, if you need it. but the instructions provided by all the download sites are great. its easy peasy. if you need bettrr instructions youre more than welcome to get in contact with me. [email protected]
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
sorry about that ****ty message, this goddamn site is retarded on mobile. im not going thru all that **** again but yes it can be rooted and its easy, if you need some clear instructions you can hit me up at the email i provided in that ****ty short bus post i left.
---------- Post added at 09:49 PM ---------- Previous post was at 09:37 PM ----------
you can keep the stock rom fyi. and theres an updated android 9.0 pie stock rom floating around too. im using it, no problems. you have to use xperifirm and flashtool to flash it tho. its simple unless its your first time doing, after you do it once youll ask yourself why it seemed so hard to get to that point. also, fyi, this particular is almost brick proof not saying it cant be bricked because, i did, several times boot looped it, everything, **** right now i dont even have a stock recovery because of some errors i made learning how to do all of this, but its up and running, its not buggy, magisk works great, stock android 9.0 firmware, just no recovery, but good ole twrp works just fine when you boot it for recovery. great phone to learn how to do all of this on. like i said its almost brick proof.
Sony Xperia XA2 Ultra - ROOT and Stock Rom 9.0
enter 192_161_227_73 in ip address format with the ftp header ftp://
should make rooting a little easier, need unlocked bootloader
simple interactive root process
also contains android 9.0 stock for Sony Xperia XA2 Ultra H3223
thanks Luk1337 for your work.
A) I get a stuck boot on SONY white screen when trying to reboot after a boot to twrp using fastboot (swipe to allow modifications and nothing else). Fastboot boot to TWRP was after a clean installation of Android Pie.
B) I even made a TWRP backup of the Android Pie rom but restoring backup runs into same issue of stuck on SONY logo). (well if just a twrp boot to resulted in a stuck boot (as in A) rebooting after a twrp backup restore would not have a chance either but just mentioning)
I am guessing we need a disable verity to avoid this?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://forum.xda-developers.com/showpost.php?p=77177197&postcount=3
Do we have a vbmeta.img for the XA2 Ultra? (from stock kernel) sorry if a noob question. Thanks.
mac231us said:
thanks Luk1337 for your work.
A) I get a stuck boot on SONY white screen when trying to reboot after a boot to twrp using fastboot (swipe to allow modifications and nothing else). Fastboot boot to TWRP was after a clean installation of Android Pie.
B) I even made a TWRP backup of the Android Pie rom but restoring backup runs into same issue of stuck on SONY logo). (well if just a twrp boot to resulted in a stuck boot (as in A) rebooting after a twrp backup restore would not have a chance either but just mentioning)
I am guessing we need a disable verity to avoid this?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://forum.xda-developers.com/showpost.php?p=77177197&postcount=3
Do we have a vbmeta.img for the XA2 Ultra? (from stock kernel) sorry if a noob question. Thanks.
Click to expand...
Click to collapse
Flash magisk or something, it'll disable verity.
Also we don't have vbmeta partition.
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer
rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute
Won't let me simend the link
rob420p,
Please provide links.
rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!
lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now