Related
With modified twrp 28 i flashed ROM -> reboot to system -> system->reboot recovery -> flashed supersu 2.79 -> reboot to system gets stuck at the boot animation for about 20 minutes. i re flashed the ROM and using it without root. Followed the same for beta 9 without any issues(2.78 SR5 then).
Now, I tried with 2.79 and 2.79 SR1, both same issue. I see couple of people mentioning root is working with 2.79, so looks like i am have some issue with my phone or missing something
Try wiping cache/dalvik. If that doesnt work wipe system and reflash the rom and supersu. Good luck!
Are you on the latest firmware? Because I'm on the Sultan ROM, which requires the latest firmware, and I'm having a ton of issues with root and the supersu app. I finally got supersu to install, but it's just unstable
Working for me:
flash ROM
flash TWRP. img
reboot to recovery
flash supersu (and other system mod eg. Viper...)
wipe dalvik/art and cache
than reboot to system.
Use Phh superuser. For some reason other superusers break F2FS. I have no clue how you guys get TWRP 28 to work but it keeps asking for a pin even when my phone is decrypted.
papzi57 said:
Working for me:
flash ROM
flash TWRP. img
reboot to recovery
flash supersu (and other system mod eg. Viper...)
wipe dalvik/art and cache
than reboot to system.
Click to expand...
Click to collapse
So right
Sent from my ONEPLUS A3003 using Tapatalk
Puddi_Puddin said:
Use Phh superuser. For some reason other superusers break F2FS. I have no clue how you guys get TWRP 28 to work but it keeps asking for a pin even when my phone is decrypted.
Click to expand...
Click to collapse
I always use TWRP and SuperSU, when it comes to rooting.
But that sounds interesting !
Could you elaborate ?? Could you give all very steps you've done ? Any success rate ?
You should never flash OOS Rom with TWRP, you must restore the stock recovery before then after you can flash TWRP and SuperSU.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_10/
I just flashed SuperSU 2.79 SR1 on my Open Beta 10.
I followed the same procedure I did when I rooted Open Beta 9:
adb sideload SR1-SuperSU-v2.79-SR1.zip
Did this under TWRP mod28 (Advanced/ADB_Sideload), not OnePlus recovery.
And...
Yes ! I'm now rooted on Open Beta 10 !
That was successful... on my encrypted F2FS filesystem.
Does anyone know if xposed is working with open beta 10?
Skickat från min ONEPLUS A3003 via Tapatalk
nabeelio said:
Are you on the latest firmware? Because I'm on the Sultan ROM, which requires the latest firmware, and I'm having a ton of issues with root and the supersu app. I finally got supersu to install, but it's just unstable
Click to expand...
Click to collapse
You don't need the last one.
You need the 3.2.6 at least if I remember right.
I'm using the 3.2.7 because I plan to upgrade to OP3T's battery (incompatible with the last one, the 3.2.8) and all is fine for me.
I'm rooted with SuperSU too.
REiced said:
Does anyone know if xposed is working with open beta 10?
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Xposed isn't compatible with android nougat regardless of what ROM you are on
Fixed my bootloop issue - removed xposed and all modules, removed magisk and all modules. Removing magisk was also causing bootloops, so I had to reinstall supersu afterwards, which seemed to cure it. And woops, you're on Nougat, but cleaning everything out might help
It is not SuperSu that is unstable or an issue with TWRP that causes the problems, such as breaking root, but rather the boot image that comes with 10. After installing ten, my root was broken and then I noticed in TWRP that my data partition wasn't mounting. So I reformatted the data partition to f2fs from emmc that it formats it as. However, when I rebooted, it took an extra long time before starting up and when it did finally boot up, root was broken again. I then reasoned that the problem lies with the boot image as when one reboots, it will then reformat and encrypt your data partition and break root. I simply flashed and older boot image (both beta 8 or 9 work) and the data partition mounts and I have installed SuperSu, Greenify, Root Browser and Root Deleter. All root apps are working fine and when I reboot, I no longer have any issues. Steps I used. install Beta 10, boot to fastboot and flash older boot image (Don't forget to clear the cache/dalvick). Reboot to TWRP and wipe/reformat your data partition. Flash SuperSu and setup as normal, since you will need to go through the setup again after blowing away the data partition.
---------- Post added at 10:18 AM ---------- Previous post was at 09:27 AM ----------
BTW, I tested it by reflashing the boot image from Beta 10 again and it formatted and encrypted the partition once again. So the issue definitely lies in the boot image that is included with Beta 10. Flash an older boot image, such as the one from Beta 9, as a temporary workaround.
jim262 said:
It is not SuperSu that is unstable or an issue with TWRP that causes the problems, such as breaking root, but rather the boot image that comes with 10. After installing ten, my root was broken and then I noticed in TWRP that my data partition wasn't mounting. So I reformatted the data partition to f2fs from emmc that it formats it as. However, when I rebooted, it took an extra long time before starting up and when it did finally boot up, root was broken again. I then reasoned that the problem lies with the boot image as when one reboots, it will then reformat and encrypt your data partition and break root. I simply flashed and older boot image (both beta 8 or 9 work) and the data partition mounts and I have installed SuperSu, Greenify, Root Browser and Root Deleter. All root apps are working fine and when I reboot, I no longer have any issues. Steps I used. install Beta 10, boot to fastboot and flash older boot image (Don't forget to clear the cache/dalvick). Reboot to TWRP and wipe/reformat your data partition. Flash SuperSu and setup as normal, since you will need to go through the setup again after blowing away the data partition.
---------- Post added at 10:18 AM ---------- Previous post was at 09:27 AM ----------
BTW, I tested it by reflashing the boot image from Beta 10 again and it formatted and encrypted the partition once again. So the issue definitely lies in the boot image that is included with Beta 10. Flash an older boot image, such as the one from Beta 9, as a temporary workaround.
Click to expand...
Click to collapse
It looks like I am having the same issue.
Did you just extract the boot.img from the Beta 9 Rom zip and flash it like the following:
Code:
fastboot flash boot boot.img
Tybalt said:
It looks like I am having the same issue.
Did you just extract the boot.img from the Beta 9 Rom zip and flash it like the following:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just extracted the image from the zip and flashed it in fastboot using method above.
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
I have two questions. What is causing this problem? And second, any way I can use fastboot to downgrade firmware 3.2.6, so that I can at least access my internal storage and back it up. I got loads of data in there.
Djalaal said:
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
Hi I made that too with this rom! (https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-5-8-0-oms-t3527344) I think it is that 3.0.3 TWRP that did it! I hawe to wipe everything but i got it working! with these instruction https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ Method 2 worked for me but it wipes all! there seemed to be instructions for not loosing all but i cant test it
Click to expand...
Click to collapse
I have found a solution. Even without decrypting /data, you can still get into recovery (except you can't read your data partition). This is key. What I did is simply use recovery sideload to flash the old 3.2.6 firmware (apparently flashing works even without decryption), use fastboot to flash twrp 3.0.1, and backup all my data to the computer via mtp. Then I completely wiped everything, flashed the new firmware and recovery, and decryption worked.
Hello everyone,
i just installed the new oreo update from oneplus. everything worked just fine, but i lost my root with magisk.
i still have the original recovery and just boot twrp via fastboot when needed.
but after the the update i dont have any "decrypt storage" option in twrp anymore.
how can i mount my /data partition in twrp and how can i install magisk again?
same problem here ... waiting for help
You're probably using an older version of TWRP that can't mount /data on Oreo ROM.
Just download either Blu_Spark TWRP or Codeworkx TWRP.
same problem here
HueleSnaiL said:
You're probably using an older version of TWRP that can't mount /data on Oreo ROM.
Just download either Blu_Spark TWRP or Codeworkx TWRP.
Click to expand...
Click to collapse
Nothing much one could add.
Disable forced encryption of data partition
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
To encrypt the rom again, flash encrypt(pie).zip and format /data
What is the meaning of forced encryption on data partition
#ArtFuL said:
Disable forced encryption of data partition
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
Click to expand...
Click to collapse
In which recovery stock or on custom recovery?
Sdsahu101 said:
In which recovery stock or on custom recovery?
Click to expand...
Click to collapse
Custom recovery
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
nice_guy75 said:
Can I update to Pie via TWRP, after editing updater-script, if yes, can I flash decrypt.zip just after updating without formatting data. Actually, I don't want to format my device and install all the applications again.
Is 1903.064 is stable enough to use, I mean cam2api, screen flickering, PUBG on HD setting, charging time it was taking too long to charge earlier, reduced battery backup, screen brightness, cracking sound, double tap was also not working.
Click to expand...
Click to collapse
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
#ArtFuL said:
Yes. You can. But if the phone is encrypted and flashing decrypt for the first time, decryption comes into effect only after formatting data
Click to expand...
Click to collapse
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
nice_guy75 said:
No, Mine is decrypted. I am on Oreo with TWRP and already flashed decrypt.zip of Oreo? So can I flash 1903.064 zip via TWRP, after editing updater script and then flash decrypt.zip of Pie, to save my data partition?
I hope decrypt.zip of Pie does not format data while flashing.....
Click to expand...
Click to collapse
Then no need to format. You won't loose data
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
kayamokid said:
is this necessary if i will go for custom rom? i mean just like in oreo, can i use the decrypt.zip for oreo to stock pie in order to decrypt my device? or i will use this one for pie? just to clarify sir.
Click to expand...
Click to collapse
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
legacy07 said:
Flashing decrypt oreo infact caused many problems on wifi/modem for many users. Also decrypt oreo didn't worked on pie for some users. So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
it meams its just like the updated version of decrypt.zip? thanks sir.
Which one of these two files should be flashed
Karthik kollapureddy said:
Which one of these two files should be flashed
Click to expand...
Click to collapse
Choose according to whether you have to encrypt or decrypt
legacy07 said:
Choose according to whether you have to encrypt or decrypt
Click to expand...
Click to collapse
I'm a beginner so would you please tell me what's encypt and decrypt
---------- Post added at 06:32 AM ---------- Previous post was at 06:29 AM ----------
Karthik kollapureddy said:
I'm a beginner so would you please tell me what's encypt and decrypt
Click to expand...
Click to collapse
I'm confused and the rooting step
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
sintoo said:
Hi all. I have zenfone updated to Oreo/android 8.1.
Phone model Z01BDC = ZC551KL .
What should I do to apply this patch to decrypt my /data ?
I installed TWRP 3.1.0.0 and the fact that /data is Encrypted is a problem.
Thank you.
Click to expand...
Click to collapse
This mod works in X01BD and X00TD. Not sure if it work for Z01BD. You can flash this patch by following the steps in the thread but success isn't guaranteed. Take a system backup as if anything goes wrong. Also be ready to loose your data
legacy07 said:
... So flashing decrypt pie is recommended for Oreo too.
Click to expand...
Click to collapse
I'm not sure about that... I am flashing this file (decrypt pie) for Oreo just. The phone does not boot in this case. I was forced to flashing old decrypt file for Oreo after and it all worked again.
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
anagramgenius said:
It's not working with Official TWRP 3.3.1-0. I'm using stock Pie .065. Every time I reboot to system, it starts encrypting my device and when I reboot to recovery, TWRP is gone and I'll be booted to stock recovery. Then I flashed TWRP and checked the fstab.qcom. It was never patched. With OFRP, I don't have this issue as it patches fstab.qcom automatically after flashing a zip. But with the zip provided in OP, I'm unable to disable forced encryption. I don't get any error while flashing the zip though. Does any other file needs to be patched to disable forced encryption other than fstab.qcom?
Click to expand...
Click to collapse
I think twrp official has decryption issues. Check with twrp 3.2.3
legacy07 said:
I think twrp official has decryption issues. Check with twrp 3.2.3
Click to expand...
Click to collapse
I checked with Rk585's TWRP 3.2.3 too. Same issue persists. It worked fine when I was in Oreo.
After flashing the zip, I booted back to recovery and copied the fstab.qcom to my PC to check if it has been replaced with the flashed zip. It did replace it. But when I boot to system, it starts encrypting my device and TWRP gets replaced by stock recovery. So I flashed the TWRP again and checked the fstab.qcom. Voila. It was unpatched. I don't know what is happening during the boot. The patched fstab is getting replaced by original fstab.
Edit: Seems there is a problem with the zip I guess. Or more files need to be patched to disable forced encryption in stock Pie rom. I tested in both PBRP and OFRP.
Case 1: I flashed stock rom in Official TWRP, then flashed PBRP zip and booted into PBRP. After booting into PBRP, it doesn't automatically disable forced encryption if no rom zip is flashed in it. So I flashed the decrypt zip provided in this OP. Then I booted to system, it started encrypting my device.
Case 2: I flashed stock rom in Official TWRP, then flashed OFRP zip and booted into OFRP. After booting into OFRP, it automatically disabled forced encryption even though no rom zip was flashed. Hence after booting into system, it didn't automatically encrypt my device as forced encryption was disabled automatically by OFRP.
So PBRP and OFRP do something else to disable forced encryption other than just patching fstab.qcom. Atleast in stock Pie rom. That's why I'm unable to disable forced encryption by flashing decrypt zip in any of the recoveries unless it is patched by recoveries themselves.
I'm flashing TWRP version from official TWRP website for poco F3. Successfully flash temporary and make it permanent using flash this TWRP version.
Boot up to stock miui (im not flashing custom rom yet), work fine. I want to flash magisk, but TWRP wong detect storage or the magisk zip. Anyone can help?
Official TWRP doesn't support Android 12's Encryption yet, that's why /data partition appears empty.
You need to use unofficial TWRP "skkk": https://dl.akr-developers.com/?dir=skkk/TWRP/A12
cyanGalaxy said:
Official TWRP doesn't support Android 12's Encryption yet, that's why /data partition appears empty.
You need to use unofficial TWRP "skkk": https://dl.akr-developers.com/?dir=skkk/TWRP/A12
Click to expand...
Click to collapse
Thank you. I will try this version.
Edit: It works. Thank you sir!!