Here is the easiest way to get it, make sure you factory reset, it will most likey reboot once so don't worry
-------Directions-------
Boot into TWRP and format data to transfer files
Unzip the zip file
Place extracted Dp3 folder into the TWRP folder
And restore the backup
Then factory reset and should boot fine
Magisk app is already installed and just not rooted in backup. Make sure you wait for it to boot after it installs for 19.4 update directly and automatically reboots
It'll take around 5mins to boot up after updating root from the magisk app
Don't install twrp
https://drive.google.com/file/d/1c1A9tTnPSAodYeoDn1la1H0eGX3uIwQr/view?usp=drivesdk
ayjays said:
Here is the easiest way to get it, make sure you factory reset, it will most likey reboot once so don't worry
Magisk app is already installed and rooted in backup. Make sure you wait for it to boot after it installs for 19.4 update directly and automatically reboots
It'll take around 5mins to boot up after updating root from the magisk app
Don't install twrp
https://drive.google.com/file/d/1c1A9tTnPSAodYeoDn1la1H0eGX3uIwQr/view?usp=drivesdk
Click to expand...
Click to collapse
So all I need to do is boot TWRP VIA FASTBOOT CORRECT but do not install?? And while in TWRP FLASH THIS ZIP?? AND EVERYTHING WILL BOOT UP FINE??
Jlsmith said:
So all I need to do is boot TWRP VIA FASTBOOT CORRECT but do not install?? And while in TWRP FLASH THIS ZIP?? AND EVERYTHING WILL BOOT UP FINE??
Click to expand...
Click to collapse
Boot into TWRP and wipe data to transfer files
Unzip the zip file
And then once done, place the DP3 folder you've extracted in your phone in the TWRP folder
And restore the backup
Then factory reset and should boot fine and yes don't install TWRP after just boot into it or it'll boot loop and you'll have to use msmtool and retry again
is there a specific version of twrp required for this?
king_david43 said:
is there a specific version of twrp required for this?
Click to expand...
Click to collapse
I don't think so I believe you can use any since
ayjays said:
Here is the easiest way to get it, make sure you factory reset, it will most likey reboot once so don't worry
-------Directions-------
Boot into TWRP and wipe data to transfer files
Unzip the zip file
And then once done, place the DP3 folder you've extracted in your phone in the TWRP folder
And restore the backup
Then factory reset and should boot fine
Magisk app is already installed and just not rooted in backup. Make sure you wait for it to boot after it installs for 19.4 update directly and automatically reboots
It'll take around 5mins to boot up after updating root from the magisk app
Don't install twrp
https://drive.google.com/file/d/1c1A9tTnPSAodYeoDn1la1H0eGX3uIwQr/view?usp=drivesdk
Click to expand...
Click to collapse
Wipe data or format data? A little confused what you're stating here.
the.emilio said:
Wipe data or format data? A little confused what you're stating here.
Click to expand...
Click to collapse
Format sorry!
ayjays said:
Format sorry!
Click to expand...
Click to collapse
Do we flash over beta or stable OOS?
the.emilio said:
Do we flash over beta or stable OOS?
Click to expand...
Click to collapse
This is a TWRP recovery backup so it doesn't really matter because the partitions will be formatted and rewritten when you restore
Related
Hi !
I've rooted N6 and installed M with factory image file. Today, i've an security update, size 4MB. When i try to install it; first, update downloaded and phone try to install. But when reboting, phone boot recovery menu. And when i reboot again on recovery, update notification reappear.
Anybody know why N6 diong this andhow can i solve this problem?
Cortex-A93 said:
Hi !
I've rooted N6 and installed M with factory image file. Today, i've an security update, size 4MB. When i try to install it; first, update downloaded and phone try to install. But when reboting, phone boot recovery menu. And when i reboot again on recovery, update notification reappear.
Anybody know why N6 diong this andhow can i solve this problem?
Click to expand...
Click to collapse
Because you modified the system, it therefore doesn't match the expectations of the update, so it is protecting itself from corruption by not installing.
You need to install your updates from here instead;
https://developers.google.com/android/nexus/images?hl=en
doitright said:
Because you modified the system, it therefore doesn't match the expectations of the update, so it is protecting itself from corruption by not installing.
You need to install your updates from here instead;
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
Will he be able to re-root with this, given that others have experienced endless boot-loop when trying to root the stock image?
aiiee said:
Will he be able to re-root with this, given that others have experienced endless boot-loop when trying to root the stock image?
Click to expand...
Click to collapse
Yes, he can re-root after installing the full image. I have done so many times and never ran into a boot-loop from doing so. Just make sure to not flash userdata if he wants to keep his programs and settings.
I just did the update on my phone. I had been running 6 with root and unencrypted with TWRP recovery. What I did was flash the new radio and the system img from fastboot. Rebooted to recovery and reflashed my no encrypt kernel and SU package, wiped delvik and cache. Rebooted and was back up and running. I had to redo my build prop edit for lcd density and reapply the host files for adaway, but other than that every thing is as it was.
alryder said:
Yes, he can re-root after installing the full image. I have done so many times and never ran into a boot-loop from doing so. Just make sure to not flash userdata if he wants to keep his programs and settings.
Click to expand...
Click to collapse
Great news. I wouldn't have thought that the case, given the root=bootloop situation with MM and the factory image.
eman5oh said:
.....root and unencrypted with TWRP recovery. What I did was
1. Flash the new radio and the system img.
2. Reboot to recovery.
3. (re)Flash no encrypt kernel and SU package.
4. Wiped dalvik and cache. Reboot.
I had to redo my build prop edit for lcd density and reapply the host files for adaway.....
Click to expand...
Click to collapse
Nice method. Allow me to add a suggestion for users using rro.layers.
Besides a backup in local storage of the no encrypt kernel and SuperSU, also make a copy of system/vendor/layers. This directory is wiped.
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root
I am upgrading my OP3T from 5.0.1 to 5.0.3. My device is rooted using magisk and I have TWRP installed.
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?
EDIT - I read about Dirty flashing the version I want but I can't find 5.0.3 image on Oneplus website.
shantam2 said:
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?.
Click to expand...
Click to collapse
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
przemcio510 said:
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
Click to expand...
Click to collapse
Re-flashing magisk via TWRP will keep my data ?
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Can you elaborate more on this ?
After I upgrade (and it becomes unrooted). I immediately flash magisk via TWRP ?
I didn't get the part "flash the whole rom and don't exit" ?
Also, Will I lose any data in the process ?
shantam2 said:
Re-flashing magisk via TWRP will keep my data ?
Click to expand...
Click to collapse
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
przemcio510 said:
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
Click to expand...
Click to collapse
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
b4bass said:
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
Click to expand...
Click to collapse
If you flash the update downloaded as zip from downloads.oneplus.com via TWRP, then no, there will be no need to flash it again via fastboot and no need to install TWRP Manager.
Boot to TWRP
Flash 5.0.3 zip
Flash Magisk
Reboot & enjoy
OK thanks! I thought the recovery would go back to stock after flashing the rom
And guys, if other members help you with their posts, don't forget to thank them.
Unleashed by my rooted OP3T on 8.0
b4bass said:
OK thanks! I thought the recovery would go back to stock after flashing the rom
Click to expand...
Click to collapse
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
So magisk is patching bootloader? I thought it was it point not to
Though this method is saving me some serious time!
b4bass said:
So magisk is patching boot, I thought I was it point not to
Though this method is saving me some serious time!
Click to expand...
Click to collapse
Magisk makes a point of not touching the system partition but a lot of its magic is done by changing the boot image.
Sent from my OnePlus3T using XDA Labs
OK thx ! First time I replaced supersu to pet magisk. Will have to find more details on this subject
b4bass said:
So magisk is patching bootloader? I thought it was it point not to
Click to expand...
Click to collapse
Boot image is kernel and ramdisk. Boot image is not the same as bootloader!
Hi guys and girls,
I used to have a S7 Edge and found that really easy to root as it had am sd card I've managed to unlock the bootloader and install TWRP But all the advice guides says to install supersu on the internal memory from the pc I did that but when I loaded TWRP up and searched for the zip file it wasn't in any folders or sub folder is someone able to. Explain where to put it or help with a step by step guide I am using CLT-L09 if that helps thanks so much.
If you have TWRP, just flash Magisk.
krs360 said:
If you have TWRP, just flash Magisk.
Click to expand...
Click to collapse
I have tried and followed the instructions but it won't let me install magisk either but bootloader is unlocked
It looks like twrp hasn't decrypted my internal storage I haven't got any security measures on my phone how would I decrypt it?
Scdean1985 said:
It looks like twrp hasn't decrypted my internal storage I haven't got any security measures on my phone how would I decrypt it?
Click to expand...
Click to collapse
Are you using the 'Official' or 'Unofficial' TWRP?
danifilth4king said:
Are you using the 'Official' or 'Unofficial' TWRP?
Click to expand...
Click to collapse
Don't know i found a thread online and it told to to download thr TWRP off that site I guess I should do the official one then could I just reload over the top off it
Scdean1985 said:
it is the official twrp should I have used an official one ill take a screen shot off all the files it shows
Click to expand...
Click to collapse
Install the unofficial TWRP. Remove fingerprint/password/pin etc then try again. TWRP doesn't decrypt when they're active.
colthekid said:
Install the unofficial TWRP. Remove fingerprint/password/pin etc then try again. TWRP doesn't decrypt when they're active.
Click to expand...
Click to collapse
How do I unistall TWRP as I've never needed to uninstall it before lol.
Scdean1985 said:
How do I unistall TWRP as I've never needed to uninstall it before lol.
Click to expand...
Click to collapse
Install the unofficial one from this thread https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
Just flash it over the one you currently have with the same method you used before via fastboot.
When you issue the 'fastboot reboot' command after installing unplug the usb cable straight away and hold volume up button until it boots to TWRP. This will stop TWRP being overwritten by stock recovery on first boot. Disable all fingerprint/pin/password/face unlock security first, to be able to see your files correctly.
Youre better off flashing Magisk than SuperSU
danifilth4king said:
Install the unofficial one from this thread https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
Just flash it over the one you currently have with the same method you used before via fastboot.
When you issue the 'fastboot reboot' command after installing unplug the usb cable straight away and hold volume up button until it boots to TWRP. This will stop TWRP being overwritten by stock recovery on first boot. Disable all fingerprint/pin/password/face unlock security first, to be able to see your files correctly.
Youre better off flashing Magisk than SuperSU
Click to expand...
Click to collapse
THANKS SO MUCH MATE. i appreciate all the help and finally my phone is rooted and i can do everything i wanted to do on it