[Working] Removing Encryption In Twrp Recovery - Nokia 3 Guides, News, & Discussion

Hello Guys,
We have Only 1 Twrp Recovery. And u guys Might be Pissed that it has Encryption. But the Encryption Problem Is Not in the Twrp, it is due to ROM.
Guide to Remove Encryption
1. Boot to Twrp Recovery
2. Do a Factory Reset, Internal Storage Wipe
3. Reboot to Recovery Again
4. Hurray We have Removed the Encryption
F.A.Q'S
1. This Method Removes All Ur Files Which are there in Your Internal Storage.
2. I wont be responsible For the Bricks u Do For Your Device
Do Give a Thanks If U Like My Work

Reserved

ChalapathiRevanth said:
Reserved
Click to expand...
Click to collapse
pls can you tell me what this settings look like after decryption

Nothing Related to Settings
SkaboXD said:
pls can you tell me what this settings look like after decryption
Click to expand...
Click to collapse
That's a Twrp Decryption which we find in Almost All Mtk Devices Running MM, Nougat, Oreo.
Don't Worry, nothing is related to Ur settings/security

ChalapathiRevanth said:
That's a Twrp Decryption which we find in Almost All Mtk Devices Running MM, Nougat, Oreo.
Don't Worry, nothing is related to Ur settings/security
Click to expand...
Click to collapse
no,no,no i know that, i just want to know did encryption setting changed to decrypted.

What do we get with this method?
I would like to see if we can remove the system ones, and gain some performance on that.
Sent from my TA-1032 using Tapatalk

Did not Get you!
SkaboXD said:
no,no,no i know that, i just want to know did encryption setting changed to decrypted.
Click to expand...
Click to collapse
PM Me

Nothing Related To Performance!
Nikola Jovanovic said:
What do we get with this method?
I would like to see if we can remove the system ones, and gain some performance on that.
Sent from my TA-1032 using Tapatalk
Click to expand...
Click to collapse
This Is nothing related to performance, it just removes encryption in Twrp Recovery. So we can see the Internal Storage in Twrp Recovery.
If u Want to Get Performance, Remove the ****ty Apps, which are present with System App Remover!

I can confirm that this method works, i didn't know that it was that simple.

Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!

MoHuToP said:
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
Click to expand...
Click to collapse
yeah, that is only recovery that works, you can brick device if you wipe /system. You should wipe /system only when you are doing full wipe (flashing new ROM). You can wipe /data but it will remove existing non-system apps. I never did twrp backup so you can try.

Does the twrp encryption removal survive ota updates and oreo beta update?

Device Specific Comments
MoHuToP said:
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
Click to expand...
Click to collapse
However Only Device Specific Comments, SkaboXD
I hope This Guy Solved Your Problem

redweaver said:
Does the twrp encryption removal survive ota updates and oreo beta update?
Click to expand...
Click to collapse
I don't think so because every .nb0 file that i flashed have encryption enabled. But after flashing new rom, you can immediately factory reset when you boot to rom to prevent losing data.
---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------
@MoHuToP
ok, i tried full twrp backup, but it stops on system image backup, it stoped around 60%. Backup have 11.5 GB (really huge isn't it).

DELETED

Ok, this method worked on Nougat with SuperSU because SuperSU patched fstab and file contexts successfully. It doesn't work on Oreo because Oreo now have plat_file_contexts and non_plat_file contexts. SuperSU needs to be updated to patch these files succesufully or we need to manually patch it so we can remove encryption.

Just to update this guide: This works only on Nougat. You need to have installed twrp and unlocked bootloader. Magisk doesn't work with this method because it doesn't patch fstab and file contents file so you need to uninstall it by going to Magisk app and clicking uninstall. After that go to TWRP, flash unSu > stock boot.img. You can flash Magisk after that with removed encryption.
Steps:
1. Flash SuperSU 2.79 stable with TWRP
2. Reboot your phone to system.
3. Reboot to TWRP again.
4. Choose Wipe > Swipe to Factory reset
5. Choose Wipe > Advanced > Internal Storage
Now you wiped Data, Cache, Dalvik cache and Internal Storage.
Your phone will have removed encryption now.
If you want Magisk, just flash unSu script > stock boot.img > Magisk
If you update your phone, it will encrypt your phone again so you need to repeat steps again.

I have redmi note 5 mec7s and i instal global stable 9.5.13.0
now phone booting to mesage "encrypting don't reboot your phone" and goes to mi recovery and bootloop
if a make wipe then again booting to mesage "encrypting don't reboot your phone" and goes to mi recovery
how that i remove encrypting from adb or fastboot ?

xabaras666 said:
I have redmi note 5 mec7s and i instal global stable 9.5.13.0
now phone booting to mesage "encrypting don't reboot your phone" and goes to mi recovery and bootloop
if a make wipe then again booting to mesage "encrypting don't reboot your phone" and goes to mi recovery
how that i remove encrypting from adb or fastboot ?
Click to expand...
Click to collapse
This is only for the NOKIA 3 - if you have tried this on a different device there could be the possibility of Bricking it, let's hope not.
I suggest going to your own device forum for assistance.

I have reformatted and factory resetted many times but the issue keeps coming back after I boot into system. To clarify, my steps were to reformat inside the wipe section, boot into recovery and check to see there's no encryption, and then boot back to system to install magisk with the manager app. I have tried adding a factory reset to that process, but that won't work either. My TWRP is 3.2.1-0 and I will try to update it and see if it works. Also, sorry if I reply slow.

Related

Full Access ROOT

Hi there,
I tried to flash the patched boot.img and it bricked my phone, I managed to fix it by flashing the official boot.img. Now, I REALLY want full access root, so does someone know what needs to be altered in the boot.img for this to work? I want to alter my boot.img from my firmware.
Tigas001 said:
Hi there,
I tried to flash the patched boot.img and it bricked my phone, I managed to fix it by flashing the official boot.img. Now, I REALLY want full access root, so does someone know what needs to be altered in the boot.img for this to work? I want to alter my boot.img from my firmware.
Click to expand...
Click to collapse
Hey Tigas,
some users are able to get full root with this patched boot.img from this post:
raimondomartire said:
For kindly request in MAte 9 thread
https://www.androidfilehost.com/?fid=529152257862700042 ---> Patched Mate 9 image. Use only supersu.apk to see root (Don't flash any zip with supersu before)
https://www.androidfilehost.com/?fid=529152257862700052 ---> Clean mate 9 image to patch with my zip in first thread
Click to expand...
Click to collapse
Unfortunately, this method using SuperSU will break your fingerprint/PIN protection.
If you want to try, simply flash the patched img over the stock img (in TWRP) and install SuperSU from the Play store.
Tigas001 said:
Hi there,
[skipped]
Now, I REALLY want full access root...
Click to expand...
Click to collapse
Do you have option to restore your device in case of hardbrick? Obtaining full root on Mate 9 must be done with knowledge what are you doing and what tools are doing...
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
Just to discuss.
Steps 2 and 3 can be merged, if using modified script changes.sh inside of superuser.zip.
Sure, flashing decrypted boot does not require clean stock boot, so we have right boot before installing superuser
But on other side there will be unexpected problems if we will use prepared boot.
I noticed that boot images are different by version. One has additional code to thermal sensors, other doesn't.
Hi also wanted to clarify that this boot image can be flashed on any regular mate 9 and any firmware. Or is it only for a specific version of mate 9 with the same firmware as the boot.img. Thanks for any advice
Sent from my MHA-L09 using XDA-Developers Legacy app
Hi just to update I followed the instructions by ajsmsp78 and gained full root and was able to install meefik busybox and also uninstall system apps which I couldn't do before. When I flashed the boot.img and superuser and booted up some of my apps were missing. I then flashed the public and hw zips for my region and most of them were back. I now have decrypted data and full root. Thanks a lot
Sent from my MHA-L09 using XDA-Developers Legacy app
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
so is that means we can backup n restore thru twrp??
---------- Post added at 03:11 PM ---------- Previous post was at 03:11 PM ----------
JATCHUHAN said:
Hi just to update I followed the instructions by ajsmsp78 and gained full root and was able to install meefik busybox and also uninstall system apps which I couldn't do before. When I flashed the boot.img and superuser and booted up some of my apps were missing. I then flashed the public and hw zips for my region and most of them were back. I now have decrypted data and full root. Thanks a lot
Click to expand...
Click to collapse
did you tried to back up n restore in twrp?
If I flash that boot.img it will brick my phone, I've tried it and had to flash the original boot.img as of now I have the phh superuser root. The flash method I used was fastboot and yes, I have my bootloader unlocked. Been rooting android phones for 5 - 6 years
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
eddmecha said:
so is that means we can backup n restore thru twrp??
Click to expand...
Click to collapse
Yeah, you can. When you are formatting data, encryption is going off. Then need use modified boot to prevent encryption back.
---------- Post added at 06:00 PM ---------- Previous post was at 05:57 PM ----------
Tigas001 said:
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
Click to expand...
Click to collapse
Not really need. If you are interesting only root and writeable system, then don't format data.
Can't say anything about fingerprint sensor - I never used it.
I haven't tried backing up in twrp yet. Will do so later today. When I flashed the public and hw zips all my huawei apps came back but not the extra bloat like Facebook or todoist etc. Not to bothered as I don't need them. The only thing missing was the magazine lock wallpapers but I downloaded replacements from the theme app. All good now. Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
Tigas001 said:
If I flash that boot.img it will brick my phone, I've tried it and had to flash the original boot.img as of now I have the phh superuser root. The flash method I used was fastboot and yes, I have my bootloader unlocked. Been rooting android phones for 5 - 6 years
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
Click to expand...
Click to collapse
I also flashed that boot.img previously and bricked my phone. However this time it worked, the only thing I did different was to wipe data in twrp. Don't know if this made any difference but it worked
Sent from my MHA-L09 using XDA-Developers Legacy app
---------- Post added at 03:35 PM ---------- Previous post was at 03:27 PM ----------
Sent from my MHA-L09 using XDA-Developers Legacy app
If you don't wipe data first to decrypt and then flssh the decrypted boot you'll probably end up in a bootloop. I'll have to make a decrypted boot thread with a few different boot images for those still on older systems (B112, B029 etc)
Thanks that would be great and very helpful to others
Sent from my MHA-L09 using XDA-Developers Legacy app
Someone state that one of the root methods broke the finger print scanner, does this method from @ajsmsg78 correct that issue? And is there any other side effects or "broke" items after the process?
phillymade said:
Someone state that one of the root methods broke the finger print scanner, does this method from @ajsmsg78 correct that issue? And is there any other side effects or "broke" items after the process?
Click to expand...
Click to collapse
Fingerprint works fine for me after rooting.
Have you tried android pay? TiBU works without issues? Any chance OTA updates could still work? Thanks.
For all models...?
Just to be clear; which model do you have? Would the boot.img work for all models? I have the AL00.
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
xfive420 said:
Have you tried android pay? TiBU works without issues? Any chance OTA updates could still work? Thanks.
Click to expand...
Click to collapse
I don't use Android pay but the fingerprint scanner works fine so far for me after rooting. OTA should work fine but I need confirmation of it working by someone.
rbt001 said:
Just to be clear; which model do you have? Would the boot.img work for all models? I have the AL00.
Click to expand...
Click to collapse
I have the MHA-L29C567 US version. I made a boot image thread you can go to for a link to the different boot images.
5[Strogino] said:
Yeah, you can. When you are formatting data, encryption is going off. Then need use modified boot to prevent encryption back..
Click to expand...
Click to collapse
Are you saying that if you just flash superuser to gain root but do not decrypt, you can't do backups and restores with TiBU? And remove system apps? I was under the impression from another thread that decrypting was only necessary for TWRP data access, and would not prevent TiBU features from working.
deleted sorry wrong thread

Hide root?

Sorry if this is in the wrong place, I suppose this is discussion.
Does anyone know a way to hide root from apps like Snapchat? None of the old methods seem to work, presumably because root works differently for this phone/Marshmallow, unless I'm making that up.
make sure you login to Snapchat before you root.
hugeguy said:
make sure you login to Snapchat before you root.
Click to expand...
Click to collapse
I tried unrooting, but it still didn't let me log in. :L No better option than that?
Darkscan said:
I tried unrooting, but it still didn't let me log in. :L No better option than that?
Click to expand...
Click to collapse
nope.. I had to reinstall the Rom and Login and then root the phone. After that you can take a backup of Snapchat with data using titanium pro
I think you can use suhide but i don't think it support nougat yet
Sent from my Pixel using Tapatalk
Have not tried it but there are some mods to make suhide work.
https://forum.xda-developers.com/pixel-xl/how-to/suhide-real-pixel-t3520001/page36
TonikJDK said:
Have not tried it but there are some mods to make suhide work.
https://forum.xda-developers.com/pixel-xl/how-to/suhide-real-pixel-t3520001/page36
Click to expand...
Click to collapse
Any chance there's a condensed version somewhere that doesn't make me go through 36 pages to find out what everyone's referencing?
See this is what I do. In twrp I click on the reboot tab then click on b I reset it will load in the b partition. I go to format advance options reset everything except your storage. Install ROM reinstall twrp reboot let screen load do your setup reboot to recovery make sure you are on partition b in reboot section go back install su zip. Reboot. Now restart phone to recovery click on reboot then hit partition a should lisd up on A partition dirty flash your rom.
Now partition A is stock no root. And partition B is rooted with su and I believe what changes you do on the rooted partition changes the non rooted partition since they share the same data. One is root one is not only down side is you need to restart to twrp to change partitions.
To me this us better the magisk. And any other options
Since magisk works but will fail at anytime and may take a couple restarts to get back up and running
Sorry about grammer hope you understand what I'm sayong
cgrimm9 said:
See this is what I do. In twrp I click on the reboot tab then click on b I reset it will load in the b partition. I go to format advance options reset everything except your storage. Install ROM reinstall twrp reboot let screen load do your setup reboot to recovery make sure you are on partition b in reboot section go back install su zip. Reboot. Now restart phone to recovery click on reboot then hit partition a should lisd up on A partition dirty flash your rom.
Now partition A is stock no root. And partition B is rooted with su and I believe what changes you do on the rooted partition changes the non rooted partition since they share the same data. One is root one is not only down side is you need to restart to twrp to change partitions.
To me this us better the magisk. And any other options
Since magisk works but will fail at anytime and may take a couple restarts to get back up and running
Sorry about grammer hope you understand what I'm sayong
Click to expand...
Click to collapse
I think I know what you're saying, but I'm not 100% sure and also don't know enough about how partitions work to want to embark on that endeavor.
Darkscan said:
I think I know what you're saying, but I'm not 100% sure and also don't know enough about how partitions work to want to embark on that endeavor.
Click to expand...
Click to collapse
Yeah same boat here.. would love to venture out and learn how both partitions work.. would love to do what that user described as I know it is doable with having two partitions... but on another note, I saw a thread to users who were softbricking their device by misusing the reboot to different partition options.. so i have decided to stay away from this until a more compatible TWRP can evolve and it's not tax season
Experimental magisk works fine to hide root. There is a thread.
Sent from my Pixel using Tapatalk
I ended up redoing my phone for the latest update. Decided to stay stock I did install TWRP then decided to run magisk it's not full root but does what I need.here is how I installed it.
1) Dirty or clean flash
2) Flash TWRP
3) Boot to System
4) Reboot to TWRP
5) Flash ElementalX kernel
6) Flash Magisk 11.6
7) Flash TWRP
8) Boot to System
9) reboot system again
10) open up magisk manager you should have magisk root
11) go to settings Enable Magisk Hide enable BusyBox enable systemless hosts
12) reboot phone open magisk manager you should now have magisk root and safety net green Android pay will work and so will apps like Snapchat pokemon go that direction modified systems.
Does magisk root allow root file management and/or Ad Away?

Confused about root

This thread is not about "How do I install twrp" etc. But maybe this can help some of us.
I got a question. If I install twrp and root, am I still able to install system updates? For example, oxygen 5.1.6 comes out. How do I install it?
Have a nice day!
Sconny said:
This thread is not about "How do I install twrp" etc. But maybe this can help some of us.
I got a question. If I install twrp and root, am I still able to install system updates? For example, oxygen 5.1.6 comes out. How do I install it?
Have a nice day!
Click to expand...
Click to collapse
Probably not if it's rooted,in terms of it updating its self. Most likely someone will upload a zip file to flash over the old version though
Sent from my [device_name] using XDA-Developers Legacy app
Download the full room zip file, install with TWRP just as you would with a custom rom. You will lose root so you would have to repeat that process. It may differ because of the a/b partitioning, but that is how it worked on op3t. As always, backup data. And also SDcard in case you can't decrypt. Also delete lock screen before flashing.
mikex8593 said:
Download the full room zip file, install with TWRP just as you would with a custom rom. You will lose root so you would have to repeat that process. It may differ because of the a/b partitioning, but that is how it worked on op3t. As always, backup data. And also SDcard in case you can't decrypt. Also delete lock screen before flashing.
Click to expand...
Click to collapse
What if I have Xposed installed? Will the update go fine with that as long as I disable Substratum overlays and am flashing the full zip and then root afterwards? Or do I have to disable Xposed in Magisk or what? (I use systemless xposed)
mikex8593 said:
Download the full room zip file, install with TWRP just as you would with a custom rom. You will lose root so you would have to repeat that process. It may differ because of the a/b partitioning, but that is how it worked on op3t. As always, backup data. And also SDcard in case you can't decrypt. Also delete lock screen before flashing.
Click to expand...
Click to collapse
Why do I have to delete lockscreen?
Sconny said:
Why do I have to delete lockscreen?
Click to expand...
Click to collapse
What he means is delete the lock screen security so a pin/pattern/face unlock/figerprints... anything other then swipe to unlock your phone because if you have them set and you install a new ROM or flash the Stock ROM then it can't decrypt your phone data or recognize your security on the new ROM.
This also goes for doing a nandroid backup of any current ROM you have installed. Delete all security before booting into TWRP and backing up your ROM.
Eric214 said:
What he means is delete the lock screen security so a pin/pattern/face unlock/figerprints... anything other then swipe to unlock your phone because if you have them set and you install a new ROM or flash the Stock ROM then it can't decrypt your phone data or recognize your security on the new ROM.
This also goes for doing a nandroid backup of any current ROM you have installed. Delete all security before booting into TWRP and backing up your ROM.
Click to expand...
Click to collapse
Oh that's something new to me. But thanks, really
No Worries! Glad to be of help.
NateDev said:
What if I have Xposed installed? Will the update go fine with that as long as I disable Substratum overlays and am flashing the full zip and then root afterwards? Or do I have to disable Xposed in Magisk or what? (I use systemless xposed)
Click to expand...
Click to collapse
Regardless, it will still wipe system. Think of it as a complete factory reset. It will reinstall the full system and data of a brand new room.

[SOLVED] Stuck on TWRP splash screen after restore

Just tried to restore a backup for the first time using official TWRP. At the end of restore it had red text saying something like couldn't mount system but said restore complete. Tried booting and it gives the unlock warning then goes to black screen and led light out up constantly and doesn't boot. I try to boot back into recovery and just stays on TWRP splash screen. What did I do wrong and how do I fix this?
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Bradl79 said:
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Just did. I can successfully boot into twrp now every time but still wont boot into OOS. Still have black screen and white solid led.
Do u have the stock oxygenos full zip on ur phone?
Bradl79 said:
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Bradl79 said:
Do u have the stock oxygenos full zip on ur phone?
Click to expand...
Click to collapse
No. Can I download it from the oneplus site and transfer it via twrp file manager?
U may be better off using this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It is going to wipe ur internal storage though
vinnievegas said:
Just did. I can successfully boot into twrp now every time but still wont boot into OOS. Still have black screen and white solid led.
Click to expand...
Click to collapse
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
What full rom zip?
vinnievegas said:
What full rom zip?
Click to expand...
Click to collapse
Whatever OOS version you want. It will make you stock after a flash with official TWRP, but since you restore data from your backup, it will keep all apps and settings. That's why you flash TWRP.zip after OTA.zip finishes. It will replace your boot IMG with stock. Then after you boot into system, you can install magisk by flashing again in TWRP. You can't flash magisk right away because of the a/b partition. Causes an error.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
You can download full ROM zip of your choice from this thread. Either will work.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
mikex8593 said:
Whatever OOS version you want. It will make you stock after a flash with official TWRP, but since you restore data from your backup, it will keep all apps and settings. That's why you flash TWRP.zip after OTA.zip finishes. It will replace your boot IMG with stock. Then after you boot into system, you can install magisk by flashing again in TWRP. You can't flash magisk right away because of the a/b partition. Causes an error.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
You can download full ROM zip of your choice from this thread. Either will work.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Click to expand...
Click to collapse
How do I get the rom to my phone?
vinnievegas said:
How do I get the rom to my phone?
Click to expand...
Click to collapse
I believe OTG works in official TWRP if you have OTG cable and usb. MTP works in unofficial TWRP but I'm not sure which one I that was. May have been this one but don't flash the fix. I think the fix disables MTP
https://forum.xda-developers.com/oneplus-6/how-to/recovery-twrp-3-2-1-1-hydrogen-oxygen-t3795770
Let me know how/if it works out for you.
Bradl79 said:
U may be better off using this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It is going to wipe ur internal storage though
Click to expand...
Click to collapse
This saved me. Thank you so much. I wish I could have got the suggestion below to work cause I had a lot set up.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
I never could get the older unofficial twrp to boot so I couldn't transfer the rom. Had to use above suggestion. Thanks so much for all of you guys help. I'm just so happy to have a working phone again....
I did make a cloud backup of one of my twrp backups. wondering if I can restore that data once I've got twrp installed again and rooted?
vinnievegas said:
This saved me. Thank you so much. I wish I could have got the suggestion below to work cause I had a lot set up.
I never could get the older unofficial twrp to boot so I couldn't transfer the rom. Had to use above suggestion. Thanks so much for all of you guys help. I'm just so happy to have a working phone again....
I did make a cloud backup of one of my twrp backups. wondering if I can restore that data once I've got twrp installed again and rooted?
Click to expand...
Click to collapse
That should work. Just wipe data and cache in TWRP, then restore data from your old backup. I'd recommend keeping a zip file in internal storage of the ROM in case of emergency. That way you can recover without having to wipe internal storage again.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
Old thread but thanks! I had same problem and your method worked for Xiaomi Mi A1
Similar, but reinstalling from scratch. I don want to preserve any data on divice.
By mounting Data partition from TWRP this is what you can see among other things
Internal Storage
NitrogenOS-Updates
Nitrogen-OS-P-kenzo-20190519.zip
I don't remember what next. Any link any link is sufficient and very welcome.
Also a suggestion on where to go to ask, if this is not the right place!
Mi device "xiaomi 3", is perfect for me!

Flashed 5.1.11 via TWRP now reboots to TWRP?

I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
double post
skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to
ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..
WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?
Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??

Categories

Resources