Oneplus has released the PIE Oxygen OS for Oneplus 3T and 3.
This thread is only for OOS PIE. For disabling Dm-Verity and force Encryption in NOUGAT OOS ROMs refer to my thread here:https://forum.xda-developers.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232 and for OREO OOS refer to my thread here:https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Disclaimer: I am not responsible for any damage or data loss that happens to your device on embarking this procedure. This is a just released version of OOS and so expect the unexpected. Back up all your data and valuables before you go on and don't blame me if you or your device commits suicide..
THE DETAILS....
After a thororugh initial analysis of the PIE installation zip file for Oneplus 3/3T, I found that there has not been much hell of a difference in the protection schema related to Dm-verity and force encryption. Hence most of the procedure remains the same...As mentioned this is relatively new build and probably existing Twrp may need upstream fixes or other changes to accommodate PIE related commits before encrypting, decrypting and flashing...I have no intention of flashing the PIE build unless it gets stable and have a lot of time to spare so that if things get rough i can dive into it..So its untested from my side but its ought to work same as before. ..
So in a nut shell, to disable DM-Verity you will need to flash the patched Boot Images and to disable force encryption you will have to flash the force encryption disabler zip - The links of which are provided below. Do refer to the correct procedure explained in detail before attempting to do anything...
For all those who need an in-depth reading of the nature of patching the fstab in dtb file and my work you can refer here:
https://forum.xda-developers.com/showpost.php?p=74326761&postcount=3
THIS METHOD WILL WORK FOR BOTH ONEPLUS 3 T AND ONEPLUS 3...
FOR THOSE WHO HAVE ALREADY TRIGGERED DM-VERITY ON OOS PIE FOLLOW THE STEPS IN POST 2 IN THIS THREAD TO GET RID OF DM-VERITY BEFORE PROCEEDING...
Nothing has been changed....
It is 100% stock boot image except that the DM-Verity Flag has been patched...
Links:
For ONEPLUS 3T
STABLE OOS Boot Images
Patched Boot Image Stable OOS 9.0.6
https://www.mediafire.com/file/mgdc7fga7ypemon/boot-patched-9.0.6-OP3T.img/file
Patched Boot Image Stable OOS 9.0.5
http://www.mediafire.com/file/xuea2pjk7iebo7y/boot-patched-9.0.5-OP3T.img/file
Patched Boot Image Stable OOS 9.0.4
http://www.mediafire.com/file/dzbe1djwlc24h0q/boot-patched-9.0.4-OP3T.img/file
Patched Boot Image Stable OOS 9.0.3
http://www.mediafire.com/file/432r3vew6786pga/boot-patched-9.0.3-OP3T.img/file
Patched Boot Image Stable OOS 9.0.2
https://www.mediafire.com/file/fj2offc35sa0zo7/boot-patched-9.0.2-OP3T.img/file
BETA OOS Boot Images
Patched Boot Image Beta OOS 9.0.1
http://www.mediafire.com/file/bf32s2mf2c7y66o/boot-patched-9.0.1-OP3T.img/file
Patched Boot Image Beta OOS 9.0
http://www.mediafire.com/file/kesaqq2q8dgi43p/boot-patched-9.0.0-OP3T.img/file
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 9.0.6
http://www.mediafire.com/file/huxj64syp8l1o58/boot-patched-9.0.6-OP3.img/file
Patched Boot Image Stable OOS 9.0.5
http://www.mediafire.com/file/mkv6swi72pruafy/boot-patched-9.0.5-OP3.img/file
Patched Boot Image Stable OOS 9.0.4
http://www.mediafire.com/file/7d9k4nytqa7nqjv/boot-patched-9.0.4-OP3.img/file
Patched Boot Image Stable OOS 9.0.3
http://www.mediafire.com/file/z7dckvcztskes53/boot-patched-9.0.3-OP3.img/file
Patched Boot Image Stable OOS 9.0.2
http://www.mediafire.com/file/3rzae15wf25l72w/boot-patched-9.0.2-OP3.img/file
BETA OOS Boot Images
Patched Boot Image Beta OOS 9.0.1
http://www.mediafire.com/file/v36cxtcnao23bc3/boot-patched-9.0.1-OP3.img/file
Patched Boot Image Beta OOS 9.0
http://www.mediafire.com/file/a9gq8koevpra9bh/boot-patched-9.0.0-OP3.img/file
STEPS: This is applicable only to people who have their data currently ENCRYPTED and needs the procedure only for NOT TRIGGERING DM-VERITY
USAGE FOR STOCK OOS:
1. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)
2. Restart back to TWRP Recovery.
3. Done.
4. Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual
5. You dont have to worry about triggering DM-Verity again and any changes made to system via TWRP will not be reverted back..
The 2 Prodeures given below: This is applicable only to those people who needs the procedure for getting rid of FORCE ENCRYPTION AND PREVENT TRIGGERING DM-VERITY
PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED
First of all Backup your data preferably to and usb otg or a PC for later restore. You may lose your data from your phone following this procedure...
1. Format SYSTEM, DALVIK, CACHE and then only Flash the Full Rom Pie OOS zip file in TWRP.
2. DON'T REBOOT
3. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.
4. DON'T REBOOT TO SYSTEM
5. REBOOT TO TWRP.
6. In TWRP, MOUNT SYSTEM, GO TO ADVANCED > TERMINAL and Type "df system"(without quotes) and enter. The details of the system partition will be shown. Look at the Use% and Free Space. Make sure you have atleast 100MB free space in System before you go to the next step. If you don't have enough free space then mount system in TWRP, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps)...If there is low space on your system partition that fstab file flashing fails resulting in blank fstab file and you will end up in bootloop.
7. Once you have confirmed that you have atleast 100MB of free space left in system partition. REBOOT BACK TO TWRP.
8. Flash "Force Encryption Disabler For OOS Pie v1.zip" in TWRP.
9. Flash SuperSuSR5 / Magisk 18+
10. Done.
11. Reboot to System.
NB:f you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file. But if you followed Steps 6 and 7 carefully you wont end up here.
PROCEDURE 2: This is applicable only to people who have their data currently ENCRYPTED AND NEEDS TO GET IT DECRYPTED and PREVENT TRIGGERING DM-VERITY
First of all Backup your data preferably to and usb otg or a PC for later restore. You will lose your data from your phone following this procedure...
1. Go to Bootloader...
2. Connect to your PC..Type "fastboot format userdata" without quotes and press enter. (You will lose your data, do back up if you need something.)
3. Don't reboot to system...Using volume buttons select boot to recovery and Reboot to TWRP.....(Very Important)
4. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.
5. DON'T REBOOT TO SYSTEM
6. REBOOT TO TWRP
7. In TWRP, MOUNT SYSTEM, GO TO ADVANCED > TERMINAL and Type "df system"(without quotes) and enter. The details of the system partition will be shown. Look at the Use% and Free Space. Make sure you have atleast 100MB free space in System before you go to the next step. If you don't have enough free space then mount system in TWRP, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps)...If there is low space on your system partition that fstab file flashing fails resulting in blank fstab file and you will end up in bootloop.
8. Once you have confirmed that you have atleast 100MB of free space left in system partition. REBOOT BACK TO TWRP.
9. Flash "Force Encryption Disabler For OOS Pie v1.zip" in TWRP.
10. Flash SuperSuSR5 / Magisk 18+
11. Done.
12. Reboot to System.
NB: If you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file. But if you followed Steps 7 and 8 carefully you won't end up here.
Rooting:
For Rooting use only SuperSu 2.82 SR5 or Magisk 18 or above seems to work for root...
FAQs:
Q: Is the boot.img file altered in anyway?
A: As mentioned above its 100% stock boot image except that the DM-Verity Flag has been patched in the device tree blobs (dtb)...
Q: My phone is already encrypted, will I lose encryption on flashing the zip?
A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..
Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose changes made to system via TWRP or lose data/apps accidentally while updating OOS...Can this be corrected by using this method?
A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..
Q: I am Rooting my phone using Magisk/Supersu then why do i need this?
A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..
Q: How to flash the patched boot.img in TWRP?
A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.
Q: What is "-Xn" seen after the OOS Version in the settings menu?
A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity...
Q: Where to find downloads and queries regarding the Stock OOS ROM and Beta OOS?
A: @Siddk007 has been maintaining Stock and Beta OOS threads were you can find relevant information.
Hope you find it useful...
Will update this OP as newer OOS versions come....
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
AND IF YOU DO APPRECIATE MY WORK DONATIONS ARE ALWAYS WELCOME...
THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS PIE ROMs. ...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
READ ALL THE STEPS AND DOWNLOAD ALL REQUIRED FILES BEFORE PROCEEDING. FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for PIE OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for PIE OOS corresponding to your current OOS (current OOS is the version of OREO OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
12) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
13) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT:
1. If you need to keep your phone un-encrypted flash Force Encryption Disabler For OOS PIE.zip immediately after step 12 and then only reboot.
2.If you are attempting this method on a a CUSTOM ROM then after Step 12 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
Reserved..
Reserved...
Thanks for your work!
I have a question. Is there anyway to prevent OOS Pie Community Build from corrupting the /data partition on Unlocked Bootloaders with Encrypted /data partition? They specifically designed the builds to do so. It doesn't cause it if the device is locked. Can the boot image be patched for that too?
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
Thanks for your work!
I have a question. Is there anyway to prevent OOS Pie Community Build from corrupting the /data partition on Unlocked Bootloaders with Encrypted /data partition? They specifically designed the builds to do so. It doesn't cause it if the device is locked. Can the boot image be patched for that too?
Click to expand...
Click to collapse
That is the duty of twrp (recovery) I suppose because with stock recovery it doesn't seem to happen and it probably doesn't have anything to do with boot image as such...but u can very well try with the patched boot image..either u can flash the patched boot image immediately after flashing the zip file and try rebooting back to twrp and see
Or replace the boot image in the OOS zip file with mine and try flashing...but no guarantees buddy...
ALWAYS BACKUP BEFORE DOING ANYTHING...THIS IS A NEW OS ANS WE ARE STILL LEARNING...
Xennet said:
That is the duty of twrp (recovery) I suppose because with stock recovery it doesn't seem to happen and it probably doesn't have anything to do with boot image as such...but u can very well try with the patched boot image..either u can flash the patched boot image immediately after flashing the zip file and try rebooting back to twrp and see
Or replace the boot image in the OOS zip file with mine and try flashing...but no guarantees buddy...
ALWAYS BACKUP BEFORE DOING ANYTHING...THIS IS A NEW OS ANS WE ARE STILL LEARNING...
Click to expand...
Click to collapse
Alright thanks!
Let's see if anyone tries it out [emoji14]
I'm not in the urge of risking getting my /data wiped as of now
Sent from my #FlagshipKiller3T using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks @Xennet ...:good:
I followed all the steps from procedure 1 ( PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED ) and for everyone out there who are confused or fear of loosing data , I successfully booted OOS Pie beta/community build without loosing any of my data/internal storage (everything regarding data is intact).
DarkSJ1998 said:
Alright thanks!
Let's see if anyone tries it out [emoji14]
I'm not in the urge of risking getting my /data wiped as of now
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Don't try because if your data is encrypted and you follow the old steps with pie files for just not triggering dm-verity
Twrp cannot decrypt the data if you reboot after flashing oos community beta and then immediately patched boot image for pie
Luckily i saved myself (from loosing data) by not booting into system and again dirty flashing stable oreo rom using the guide for oreo and patched oreo boot image.
I had to dirty flash OREO Rom patched boot image and magisk all using OTG since i couldn't access data partition.
a0879 said:
thanks @Xennet ...:good:
I followed all the steps from procedure 1 ( PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED ) and for everyone out there who are confused or fear of loosing data , I successfully booted OOS Pie beta/community build without loosing any of my data/internal storage (everything regarding data is intact).
Click to expand...
Click to collapse
Did u have your bootloader unlocked and on what OOS were u on, before u upgraded...
Yudh said:
Don't try because if your data is encrypted and you follow the old steps with pie files for just not triggering dm-verity
Twrp cannot decrypt the data if you reboot after flashing oos community beta and then immediately patched boot image for pie
Luckily i saved myself (from loosing data) by not booting into system and again dirty flashing stable oreo rom using the guide for oreo and patched oreo boot image.
I had to dirty flash OREO Rom patched boot image and magisk all using OTG since i couldn't access data partition.
Click to expand...
Click to collapse
That's in line....
Hmmmmmm it's a Twrp problem...the problem is with decryption of pie data by twrp...as stated earlier by @a0879, the patched boot image works perfectly with already decrypted data partitions without losing data...
But @Yudh, the patched boot image did it's work by not letting twrp being overwritten by the stock recovery or else you would have been in trouble...
Xennet said:
Did u have your bootloader unlocked and on what OOS were u on, before u upgraded...
Click to expand...
Click to collapse
Yes, my bootloader is unlocked from time immemorial and i was on havoc 2.4, twrp 3.2.3-10, magisk v18.1 just before flashing oos pie beta today.
Earlier i tried the leaked version and the one3tos also a few days back which ultimately wiped whole of my data/internal (though i backed it on pc) and replaced it with the stock recovery, i was unable to do anything other than just using it as it was but then also my bootloader was unlocked.
So i was searching for how to use pie by remaining non encrypted and not formatting internal storage and saving then Finally after going through your post i decided to follow each and every step as told, and "B A N G" !! , it worked as told by you !
thanks again..:good:
Xennet said:
Did u have your bootloader unlocked and on what OOS were u on, before u upgraded...
Click to expand...
Click to collapse
I had my bootloader unlocked.
I was on oos 5.0.8 latest stable build.
Also i discovered a workaround.
Steps below to keep your app data, unlocked bootloader and update to pie.
1)First upgrade the twrp to latest 3.3.0-1
2)remove any kind of lock in the system.
{otherwise it creates issues at the last point by not allowing us to enter the phone past lock screen.
[ If forgot to do so like me Workaround(perform after step 14 only) is to reboot to twrp and deleting the file located at /data/system/locksettings.db using twrp file manager (trick picked from OnePlus official rooting guide).
Then reboot into system and create the same locking method to retain fingerprints and facelock]
But for some people it would be better to remove locks in the first place from system before taking a full backup using twrp because you can always forget which file needs to be deleted or bymistakely if wrong file is deleted then it will cause issues}
3) reboot to twrp and take a COMPLETE BACKUP IN AN EXTERNAL DEVICE . Internal backup won't help.
It would be better if you don't compress it.(in rare cases it led me to corrupted backup in the past with previous twrp versions)
4)after taking backup don't go out of twrp and using MTP
Copy the whole internal storage to pc .
Bellow part isn't necessary but it would be better if you do it.
Also check the twrp backups digest for each created partition just to be on safer side.( It's better to be safe than sorry.)
So that you can make sure that your backup isn't corrupted.
5) download the community pie beta build and patched boot image for pie on the external storage like an otg (which i used).
Sha256 for OnePlus 3T beta build is
837d0f972ce7a10e422ddbf4d96d37cf3d84422ee5717c37a0ee5c3e1419d3c0
Also sha256 for OnePlus 3T patched boot image is
e2619b029e2f14f8cbe3c3b9306181e6688f038f39e8fcd4d5dea823360dcce0
6)wipe everything in twrp using format data option.
7) reboot to recovery again immediately using twrp otherwise twrp won't be able to access data partition afterwards.
8)flash the community beta build and immediately after that the patched pie boot image.
9) reboot to twrp again
10)flash magisk if you want.
11) reboot to system. After the system is started don't enter anything.
Instead again reboot to twrp.
12)while in twrp connect the mobile to pc and delete all the new folders and files in new internal storage.
After that copy the old internal storage contents to your mobile.
Just wait even i was exhausted. But it worked out well.
13)after that restore only the data partition from the nandroid backup which you made using twrp in the start of this guide
14) reboot to system and your data is still there in your mobile with pie community beta build and also unlocked bootloader
Proof that i succeeded
Now its time for me to enjoy my pie and go to sleep.
For you it's time to prepare your own pie
Xennet said:
That's in line....
Hmmmmmm it's a Twrp problem...the problem is with decryption of pie data by twrp...as stated earlier by @a0879, the patched boot image works perfectly with already decrypted data partitions without losing data...
But @Yudh, the patched boot image did it's work by not letting twrp being overwritten by the stock recovery or else you would have been in trouble...
Click to expand...
Click to collapse
The problem isn't with twrp i think because
After rebooting to recovery after flashing the pie beta and patched boot image
Even the system couldn't access the data partition it asked me to reset my phone by saying the data partition is corrupted (which in reality wasn't because i was able to recover the data)
So after i formatted it via twrp and rebooted again into twrp
Both the system and twrp were able to decrypt it.
I think something about encryption is changed in pie in oos
I successfully flash the open beta pie following the op's instruction.! Decrypted with no dm-verity message! Thank you Xennet!
I was on Aosip before and I didn't loose my data!
Sent from my OnePlus 3T using XDA Labs
As @a0879 and @xarrismoto have provided proof it's 100% clear that the patched boot image and force encryption disabler zip is able to update Oreo to pie without losing data if the phone is in DECRYPTED STATE ...
Now the problem is for encrypted phones...
Now as @Yudh mentioned it is definitely due to a change in the encryption in pie the data wipe is happening..that's sure..
But the question is if you have a locked bootloader and stock recovery, you are able to update from Oreo to pie without lose of data??...but with twrp you can't....
So the question is, whether the problem of encryption is not handled by twrp or by the system in pie itself....
xarrismoto said:
I successfully flash the open beta pie following the op's instruction.! Decrypted with no dm-verity message! Thank you Xennet!
I was on Aosip before and I didn't loose my data!
Click to expand...
Click to collapse
Can you please elaborate a bit more and it will be most helpful post of the day. As i was on closed beta and lost my data on flashing closed beta however afterwards i flashed custom roms and now my device is encrypted and locked bootloader having TWRP running Colt PIE OS. If i flashed decryption zip and modified boot then my data will be wiped or not? If not then please share your steps. Thanks
Sent from my ONEPLUS A3003 using Tapatalk
MirzaAwais said:
Can you please elaborate a bit more as its most helpful post of the day. As i was on closed beta and lost my data on flashing closed beta however afterwards i flashed custom roms and now my device is encrypted and locked bootloader having TWRP running Colt PIE OS. If i flashed decryption zip and modified boot then my data will be wiped or not? If not then please share your steps. Thanks
Click to expand...
Click to collapse
I don't think it will work for you as you are encrypted!
I was decrypted before and I stay decrypted after I flash Pie rom. I use latest TWRP 3.3.0.1 and magisk v19.0,also my bootloader is unlock
I followed the instruction from Op which is PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED
Sent from my OnePlus 3T using XDA Labs
Related
I don't have a PC either but I have TWRP installed!
the only way if to find someone who does a full TWRP backup of Android N (untouched) and upload to you.
you put it in TWRP folder and restore it. then you need to flash the boot.ing for android N.
it is a long way and I doubt you will find a backup uploaded since it is around 5GB.
ZacksBuilds said:
I don't have a PC either but I have TWRP installed!
Click to expand...
Click to collapse
Download the DP3 image from Google then unpack it and transfer it to your phone. You can flash system, boot, and vendor in TWRP 3.0. The radio must be flashed in fastboot. You will want to do a factory reset before flashing N IMG's. If you want continued access to TWRP after flashing Android N, you must be decrypted. TWRP does not work with Android N unless decrypted.
Alternatively, use fastboot to install the factory image. You still need to be decrytped to use TWRP on N.
SlimSnoopOS said:
Download the DP3 image from Google then unpack it and transfer it to your phone. You can flash system, boot, and vendor in TWRP 3.0. The radio must be flashed in fastboot. You will want to do a factory reset before flashing N IMG's. If you want continued access to TWRP after flashing Android N, you must be decrypted. TWRP does not work with Android N unless decrypted.
Alternatively, use fastboot to install the factory image. You still need to be decrytped to use TWRP on N.
Click to expand...
Click to collapse
How can I install a decrypted version of N?
ZacksBuilds said:
How can I install a decrypted version of N?
Click to expand...
Click to collapse
Fair warning. I have not done this nor do I use N previews. I am decrypted on MM though for several months. Also, I strongly suggest having a PC on standby so you can troubleshoot any issues that will arise.
In TWRP, do a backup then transfer that to a backup device. While in TWRP 3.0:
-Flash the vendor and system from N DP3
-Flash this DP3 modified boot
-Flash SuperSU 2.7x
-Wipe internal storage via TWRP. This step erases everything from your phone and is necessary to remove the encryption. Fastboot format userdata also does this from a PC.
Once you boot up, the phone should indicate you are not encrypted wherever that is located in Settings. If done properly, you should still have complete access to TWRP 3.0.
Notice that radio and bootloader are not mentioned. It is my understanding these have been updated in DP3. You need a computer to flash these two files. If you notice signal issues or anything like this, you are using older radio and bootloader combo than is specified for DP3.
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
It was released a few days ago, just go with custom or wait for working solution
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
No-verity didn't work for me but remove encryption.zip did.
this didn't work for me, it resulted in a bootloop
ric69 said:
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
Click to expand...
Click to collapse
fre78 said:
this didn't work for me, it resulted in a bootloop
Click to expand...
Click to collapse
Sorry for you. check Mount system or data or enable MTP. Internal storage was probably still at 0
I rebooted more than 10times it's ok here
zainbfaisal said:
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
Click to expand...
Click to collapse
sir may i ask how come ur able to have twrp .
how dd u install twrp on android 8.0 UK firmware?
thanks for help
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
OREO stock keeps encrypting DATA partition
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
NewbieFTW said:
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
Click to expand...
Click to collapse
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
skydivider said:
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
Click to expand...
Click to collapse
Magisk removes the encryption disabler .zip for some reason.
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
zainbfaisal said:
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
Click to expand...
Click to collapse
I'm sorry then, I don't know what to say. It worked for me.
I needed reinstal magisk after boot for root, but worked for me...
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
When this happend to me, i hit format data and typed yes, when i mount on TWRP i can see my storage again
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
miguelan.ruiz said:
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
Click to expand...
Click to collapse
Samsung Pay will, at the moment, probably never work again because it trips Knox.
For Samsung Health the fix is still the same: install a build.prop editor and change the value of RO.Config.Tima from 1 to 0.
not for me
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
doesn't work for me
Apparently there are 2 kind of users here.
One part did manage to install stock Oreo (BTU? other CSC?) , with root (magisk? superSu?) and a working TWRP (3.2.1?) which is not read-only on our beloved S7 Edge (SM-G935F)
The other part did not manage to setup this particular config.
It would be nice to have a detailed step-by-step guide from scratch by someone who managed to do it, so we can reproduce it.
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Ebeninyo said:
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Click to expand...
Click to collapse
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
DrCow said:
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Edit: after flashing magisk reboot your phone once more. (i didn't knew it before. I booted into my os and checked magisk app to see if root was successfull but it didn't show me. I wiped everything down and flashed magisk again. Same thing happened. Rebooted my phone and saw root was on )
Ebeninyo said:
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Click to expand...
Click to collapse
Will try it on the weekend.. I had some problems restoring my previous backup so i rather be home when i do it
Sent from my ONEPLUS A5000 using Tapatalk
Edit:
Wait the wifi and the LTE problem can be caused by the recovery?
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
i ended up giving up..
im trying to do a clean flash
but the moment i flash the recovery and trying to go into the recovery
boom
black screen
i tried it multiple times both with codework 3.2.3 and blu_spark
Edit: Flash universal codework 3.2.1 does get me into recovery
im gonna restore my backup...for now
Z-Blade said:
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Click to expand...
Click to collapse
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
lorrdvader said:
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
Click to expand...
Click to collapse
No, it wont because all of that is stored in the Internal Storage. So as long as you don't check that, you will still have your data. However, I personally wipe everything including the internal storage when moving to a new rom. I prefer to start with a complete clean slate but it is optional.
I cannot root my OP5. I have followed all of the directions unless I'm missing something. A week ago I previously switched to LineageOS but didn't like it so far. So I'm comfortable flashing ROMS.
1. I then downloaded the OOS official ROM, then loaded.
2. Update to most recent OOS (9.0.3) via OTA
3. Followed by factory reset to completely clear TWRP (which was downloaded via official website).
4. Downloaded TWRP
5. *Flash* No verity-opt-encrypt
6. Rebooted to TWRP
7. Downloaded Magisk zip, then flashed
8. Downloaded Magisk apk
9. Open Magisk app *shows* "Magisk is not installed*
I'm thinking maybe I've messed my phone FUBAR up or just completely doing wrong.
*sorry if this has already been answered as well or is posted in the wrong category*
sjonesd3 said:
I cannot root my OP5. I have followed all of the directions unless I'm missing something. A week ago I previously switched to LineageOS but didn't like it so far. So I'm comfortable flashing ROMS.
1. I then downloaded the OOS official ROM, then loaded.
2. Update to most recent OOS (9.0.3) via OTA
3. Followed by factory reset to completely clear TWRP (which was downloaded via official website).
4. Downloaded TWRP
5. *Flash* No verity-opt-encrypt
6. Rebooted to TWRP
7. Downloaded Magisk zip, then flashed
8. Downloaded Magisk apk
9. Open Magisk app *shows* "Magisk is not installed*
I'm thinking maybe I've messed my phone FUBAR up or just completely doing wrong.
*sorry if this has already been answered as well or is posted in the wrong category*
Click to expand...
Click to collapse
The instructions you need to follow are here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
You did not mention any file versions from rom, twrp, magisk.
What does the twrp log says? Are there any errors why magisk isn't installing sucessfully?
strongst said:
The instructions you need to follow are here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
You did not mention any file versions from rom, twrp, magisk.
What does the twrp log says? Are there any errors why magisk isn't installing sucessfully?
Click to expand...
Click to collapse
Sorry for not including the rom type. I was gonna try & run the official stock rom, while rooted. I know it was the TWRP from the official TWRP site "twrp-3.2.3-0-cheeseburger.img". Magisk was the most recent version a "Magisk-v18.1.zip". I don't think there were errors, but I can definitely try again.
I am going to try following those instructions. With me already being on "OxygenOS 9.0.4" via OTA update would I just need to cancel some parts? And to make sure that I flashed blu-spark correctly. I just drag then flash that while under TWRP correct?
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
sjonesd3 said:
Sorry for not including the rom type. I was gonna try & run the official stock rom, while rooted. I know it was the TWRP from the official TWRP site "twrp-3.2.3-0-cheeseburger.img". Magisk was the most recent version a "Magisk-v18.1.zip". I don't think there were errors, but I can definitely try again.
I am going to try following those instructions. With me already being on "OxygenOS 9.0.4" via OTA update would I just need to cancel some parts? And to make sure that I flashed blu-spark correctly. I just drag then flash that while under TWRP correct?
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
Click to expand...
Click to collapse
Use latest Codeworkx twrp(link in the instructions) and flash it with your current twrp
Then flash magisk 18.1 and watch the log for errors!
Then flash no verity patch(if you were decrypted before and want to stay, otherwise please inform me!)
Your quoted instructions are the ones for clean flash the whole rom. DON'T DO THIS! there are also instructions for updating
strongst said:
Use latest Codeworkx twrp(link in the instructions) and flash it with your current twrp
Then flash magisk 18.1 and watch the log for errors!
Then flash no verity patch(if you were decrypted before and want to stay, otherwise please inform me!)
Your quoted instructions are the ones for clean flash the whole rom. DON'T DO THIS! there are also instructions for updating
Click to expand...
Click to collapse
I followed this right in order. And right when it was time to reboot, it was a black screen with a blue LED light. Looked it up, said that it's bricked/stuck in boot loop
sjonesd3 said:
I followed this right in order. And right when it was time to reboot, it was a black screen with a blue LED light. Looked it up, said that it's bricked/stuck in boot loop
Click to expand...
Click to collapse
Firmware issue. Your device is most likely on a firmware other then the one that twrp supports.
So what was the last oxygenOS firmware / rom you use and which twrp(file name) did you flash?
Within the flashing instructions it's written that you need to be on 5.1.7 before flashing 9.0.x
Please give me instruction!
What I have done to there:
1. Unlocked bootloader
2. Boot TWRP .img file
3. Install recovery ram disk from the same .img file
4. Reboot to TWRP
5. Install TWRP installer .zip file
6. Reboot to TWRP
7. Wipe system, data, dalvik partitions
8. Flash Havoc and TWRP installer
9. Reboot to TWRP
10. PARTITIONS ENCRYPTED/UNABLE TO FLASH GAPPS
I'm using TWRP UNOFFICIAL BY MAURONOFRIO.
What to do now?
I'm tired! Give me instruction!
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Maybe this thread will help.
dj_ooms said:
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Click to expand...
Click to collapse
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
ALYSKY said:
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
Click to expand...
Click to collapse
Its the third post (link) in the thread I linked to....