Related
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.
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
memocatcher said:
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Thanks
dgunn said:
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
Click to expand...
Click to collapse
Lol... And after that there will be a new build in another week...
The more updates, the better. We won't complain, do we? I'm glad, we don't suffer for updates like SAMEsung-users do.
Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Updating via twrp and then (before reboot) re flashing twrp.zip and magisk will grant you to maintain twrp and root
Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Bradl79 said:
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Click to expand...
Click to collapse
Should i have to change slot after twrp flash of full rom
The easiest way is to download and install the update through the settings app then BEFORE you reboot open Magisk, click install then install to second slot.
No flash or worrying
sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
Download the ota.zip, reboot to TWRP, flash ota, flash TWRP.zip, reboot to OS, reboot to recovery again if you want magisk and install magisk zip. Done. No data loss or changing settings.
For those experiencing this DATA 0 sum and unable to mount DATA on a rooted S7 Edge device if upgrading to Oreo.
I had this issue and solved it by re-installing CF-Auto Root from h*ttps://desktop.firmware.mobi/ (without the asterisk*).
Simply follow the instructions to create the CF-Auto root files for your particular device and run it thru ODIN .
My DATA count reappeared after the ODIN was completed. Now I'm able to backup my ROM as well as the DATA.
Hope this helps a few souls on XDA as it worked for me.
By the way... this works just fine with the "TGP_G93xx_XXU3ERL3_v2.7.0" as well as with an Oreo Stock rom.
After install, Data was displaying zero.
Ran the CF-Auto Root using Odin included in the package created on firmware.mobi
and Data is working fine.
I had a similar problem over the month for it, a TWRP change helped
I have the same problem with TGP custom firmware on oreo 8. The only solution I habe found is to format data first. But this is very time wasting with backup making.
Can I install cf auto root when magisk is installed?
Pow35 said:
For those experiencing this DATA 0 sum and unable to mount DATA on a rooted S7 Edge device if upgrading to Oreo.
I had this issue and solved it by re-installing CF-Auto Root from h*ttps://desktop.firmware.mobi/ (without the asterisk*).
Simply follow the instructions to create the CF-Auto root files for your particular device and run it thru ODIN .
My DATA count reappeared after the ODIN was completed. Now I'm able to backup my ROM as well as the DATA.
Hope this helps a few souls on XDA as it worked for me.
Click to expand...
Click to collapse
Dont have CF-Auto Root for SC-02H DCM?
siderxx22 said:
I have the same problem with TGP custom firmware on oreo 8. The only solution I habe found is to format data first. But this is very time wasting with backup making.
Can I install cf auto root when magisk is installed?
Click to expand...
Click to collapse
i installed the GTP Kernel 6.12 today and after completed, it was showing again "Failed to mount /data (invalid argument)" so...
I ran CF-Auto Root again and my Data Count was back on.
I did have to run the TWRP thru ODIN then ran SuperSU zip file thru TWRP to regain root... then everything was back to normal.
It seems that I do have to run CF-auto Root every time I do an upgrade to the Oreo Rom or Kernel...
I lose the Data Count but I DO NOT FORMAT IT!!! I simply run CF-Auto Root to regain the count... then run TWRP and SuperSU if needed.
It should work with Magisk as well... altho, I wouldn't be surprised if you had to run the ZIP file again to gain Root again.
Pow35 said:
i installed the GTP Kernel 6.12 today and after completed, it was showing again "Failed to mount /data (invalid argument)" so...
I ran CF-Auto Root again and my Data Count was back on.
I did have to run the TWRP thru ODIN then ran SuperSU zip file thru TWRP to regain root... then everything was back to normal.
It seems that I do have to run CF-auto Root every time I do an upgrade to the Oreo Rom or Kernel...
I lose the Data Count but I DO NOT FORMAT IT!!! I simply run CF-Auto Root to regain the count... then run TWRP and SuperSU if needed.
It should work with Magisk as well... altho, I wouldn't be surprised if you had to run the ZIP file again to gain Root again.
Click to expand...
Click to collapse
for Failed to mount /data (invalid argument) try ->
https://www.youtube.com/watch?v=T-7neHzSIvc
linus2014 said:
for Failed to mount /data (invalid argument) try ->
https://www.youtube.com/watch?v=T-7neHzSIvc
Click to expand...
Click to collapse
I'm sorry linus2014 but... your video requires to format the partition(DATA) in order to repair it and I can see that your issue is the entire system is refusing
to mount as you're unable to even format in the first place.
In the situation that I am referring to, I am able to format the phone and reinstall without any problem.
The issue is that after Installing the Oreo ROM, although able to do a full Backup in TWRP, It becomes impossible to backup the DATA with it as the Count is ZERO.
I've tried your solution before as well but... It literally removes all the DATA (APPS) as it actually formats the Partition(DATA) in order to do the repair.
That requires to reinstall everything and is time consuming.
So, what I do is simply what I've explained in my post... I do not do a repair, I simply run CF-Auto Root and afterwards, my DATA count shows the
actual value once again and this, without losing any APPS.
I do have to reinstall TWRP and SuperSU but, this is peanuts compared to reinstalling all APPS and settings.
Thanks for the post, it is most appreciated.
drnism said:
Dont have CF-Auto Root for SC-02H DCM?
Click to expand...
Click to collapse
They don't seem to have anything for the Japanese Edge, Is your Phone, OEM locked? It would be one of the reason it's not available perhaps.
Is this 'failed to mount /data' issue a bug in TWRP? Would like to unterstand why TWRP failed with this error after a successful setup of oreo?
siderxx22 said:
Is this 'failed to mount /data' issue a bug in TWRP? Would like to unterstand why TWRP failed with this error after a successful setup of oreo?
Click to expand...
Click to collapse
In my situation, after completing the Installation of the Custom ROM, TWRP needed to reinstall it. DATA Count was showing
as well as the DATA mounted properly until I began installing APPs, then DATA fail to mount but everything else worked just fine.
Using the STOCK Rom for the SM-G935-W8, Rooting and TWRP worked fine even after installing the APPs.
Just an observation as I have no knowledge of programming.
Pow35 said:
i installed the GTP Kernel 6.12 today and after completed, it was showing again "Failed to mount /data (invalid argument)" so...
I ran CF-Auto Root again and my Data Count was back on.
I did have to run the TWRP thru ODIN then ran SuperSU zip file thru TWRP to regain root... then everything was back to normal.
It seems that I do have to run CF-auto Root every time I do an upgrade to the Oreo Rom or Kernel...
I lose the Data Count but I DO NOT FORMAT IT!!! I simply run CF-Auto Root to regain the count... then run TWRP and SuperSU if needed.
It should work with Magisk as well... altho, I wouldn't be surprised if you had to run the ZIP file again to gain Root again.
Click to expand...
Click to collapse
no need so confusing...just flash this file first with twrp if you want updating your rom or kernel after updated flash this file again to keep it mounted than to gain root just flash magisk.zip or supersu zip...
Thank you!
I'm not a programmer but just someone who found a way to solve an issue the way I was able to... and trying to offer my limited knowledge in hoping someone would provide a better option.
Thank you for providing this file. It will save time.
another option for this...if you really can't mount data just use modded twrp from @Tkkg1994
https://forum.xda-developers.com/s7...te-3-0-0-0-t3334084/post77296095#post77296095
Pow35 said:
For those experiencing this DATA 0 sum and unable to mount DATA on a rooted S7 Edge device if upgrading to Oreo.
I had this issue and solved it by re-installing CF-Auto Root from h*ttps://desktop.firmware.mobi/ (without the asterisk*).
Simply follow the instructions to create the CF-Auto root files for your particular device and run it thru ODIN .
My DATA count reappeared after the ODIN was completed. Now I'm able to backup my ROM as well as the DATA.
Hope this helps a few souls on XDA as it worked for me.
Click to expand...
Click to collapse
Hi,
Once the phone model has been selected, you need to load what:
Boot image
Recovery Image
Boot + Recovery Image
and in which format?
Thank you
texas2607 said:
Hi,
Once the phone model has been selected, you need to load what:
Boot image
Recovery Image
Boot + Recovery Image
and in which format?
Thank you
Click to expand...
Click to collapse
Are you using odin?
Then you need .tar files
Hi,
in fact I just saw that my phone (SM-G935F under Oreo with the rom G935FXXS4ESC5) is not compatible with Cf-Auto root. That's why I was looking for the loading link
Do you have another solution for my SM-G935F with the rom G935FXXS4ESC5 ?
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Guys, I upgraded my POCO F2 PRO to MIUI V12.5.1.0.RJKMIXM (Android 11). Unfortunately TWRP and Magisk versions are not compatible with Android 11 and has problems.
Before upgrading I was on MIUI 12.0.4 Android 10 and both TWRP and magisk was working without problem.
Now, I tried both ManuelBlanco's and LR Team's TWRP versions and the problems is the same. When I click select storage, internal Storage (0.00 MB) seems 0 MB. Data can't be mounted.
Also, Magisk Root does't work on that ROM. I tried to root the phone with several versions of magisk both by patching or flashing zip files but the phone bootloops every time with patched boot.img
As a result now I can't use TWRP and root functions. Are there any one who succeed to make them work on that last update without wiping data or formatting data? I have lots of settings and data on the phone so I don't want to try other options of wiping or formatting.
Thanks,
Any news magisk for latest miui rjomixm v12.0.5.1
Bogazicili90 said:
Guys, I upgraded my POCO F2 PRO to MIUI V12.5.1.0.RJKMIXM (Android 11). Unfortunately TWRP and Magisk versions are not compatible with Android 11 and has problems.
Before upgrading I was on MIUI 12.0.4 Android 10 and both TWRP and magisk was working without problem.
Now, I tried both ManuelBlanco's and LR Team's TWRP versions and the problems is the same. When I click select storage, internal Storage (0.00 MB) seems 0 MB. Data can't be mounted.
Also, Magisk Root does't work on that ROM. I tried to root the phone with several versions of magisk both by patching or flashing zip files but the phone bootloops every time with patched boot.img
As a result now I can't use TWRP and root functions. Are there any one who succeed to make them work on that last update without wiping data or formatting data? I have lots of settings and data on the phone so I don't want to try other options of wiping or formatting.
Thanks,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...y-net-pass-without-twrp.4223939/post-85443839
NOSS8 said:
https://forum.xda-developers.com/t/...y-net-pass-without-twrp.4223939/post-85443839
Click to expand...
Click to collapse
This method DOES NOT work. I tried this option before opening this thread. Magisk manager doesn't patch the boot. img correctly. After flashing new boot.img the phone doesn't boot and it drops into bootloop. It only boots after reflashing the original boot.img
It seems, still, there is no way to root Android 11 with Miui 12.5.1 on POCO F2 PRO
Bogazicili90 said:
This method DOES NOT work. I tried this option before opening this thread. Magisk manager doesn't patch the boot. img correctly. After flashing new boot.img the phone doesn't boot and it drops into bootloop. It only boots after reflashing the original boot.img
It seems, still, there is no way to root Android 11 with Miui 12.5.1 on POCO F2 PRO
Click to expand...
Click to collapse
Patched boot.img and working normally like before
Dadovvv said:
Patched boot.img and working normally like before
Click to expand...
Click to collapse
Did you formatted data or the internal storage after flashing the patched boot.img?
I read some suggestions to format data after rooting. I didn't try this since I don't want to lose all my settings and internal data.
Bogazicili90 said:
Did you formatted data or the internal storage after flashing the patched boot.img?
I read some suggestions to format data after rooting. I didn't try this since I don't want to lose all my settings and internal data.
Click to expand...
Click to collapse
I did clean flash new 12.5.1 fastboot rom, after first boot i flashed patched boot.img.
Dadovvv said:
I did clean flash new 12.5.1 fastboot rom, after first boot i flashed patched boot.img.
Click to expand...
Click to collapse
This is why I say it DOES NOT work. I don't have to format my data to only just root. I don't want to lose all my data. And I declared this on the starting thread. It doesn't work just with upgrading the MIUI. Before Android 11 it was working without formatting data.
Any news on this search yet?
HValenti said:
Any news on this search yet?
Click to expand...
Click to collapse
No solution. There is not a new version of Magisk that solves this bootloop issue. You have to format all the data after rooting with magisk to make it work. I'm using without root and TWRP.
Bogazicili90 said:
No solution. There is not a new version of Magisk that solves this bootloop issue. You have to format all the data after rooting with magisk to make it work. I'm using without root and TWRP.
Click to expand...
Click to collapse
Are you sure about formating data? I mean, are you sure that if you format the data (after flashing the patched boot) the phone will boot? Myself, I am not sure actually, as I have not seen it anywhere explicitly.
Unfortunately, according to Magisk news, any new version when eventually is published (maybe long enough), will have ditched the Magisk hide feature... So, maybe it is not worth to wait for newer version...
HValenti said:
Are you sure about formating data? I mean, are you sure that if you format the data (after flashing the patched boot) the phone will boot? Myself, I am not sure actually, as I have not seen it anywhere explicitly.
Unfortunately, according to Magisk news, any new version when eventually is published (maybe long enough), will have ditched the Magisk hide feature... So, maybe it is not worth to wait for newer version...
Click to expand...
Click to collapse
I'm not sure, I haven't tried it and won't try. I just read it on some comments. They claim that after formatting Data the phone boots normally.
Bogazicili90 said:
I'm not sure, I haven't tried it and won't try. I just read it on some comments. They claim that after formatting Data the phone boots normally.
Click to expand...
Click to collapse
I can understand you, I am in the same place.
HValenti said:
I can understand you, I am in the same place.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...-global-for-poco-f2-pro.4303453/post-85449319
Clean flash before not after.
I'm currently on 12.5.2.0 (RJKEUXM), what I did was :
1) Installed the rom via LM recovery an dpatched boot img via magisk app
2) Installed magisk v22.1.zip (with adb to install recovery (fasboot flash recovery NAMETWRP.img)
3) boot recovery with adb (fastboot boot NAMETWRP.img)
4) In recovery, I installed magisk v22.1.zip). I didn't installed "no verify opt encrypt" as it bootlooped me in fastboot.
Now it is working great ( I didn't factory reset my phone or wiped any data).
harisdu95 said:
I'm currently on 12.5.2.0 (RJKEUXM), what I did was :
1) Installed the rom via LM recovery an dpatched boot img via magisk app
2) Installed magisk v22.1.zip (with adb to install recovery (fasboot flash recovery NAMETWRP.img)
3) boot recovery with adb (fastboot boot NAMETWRP.img)
4) In recovery, I installed magisk v22.1.zip). I didn't installed "no verify opt encrypt" as it bootlooped me in fastboot.
Now it is working great ( I didn't factory reset my phone or wiped any data).
Click to expand...
Click to collapse
thanks for the tips but:
what's LM recovery? link please
which rom is better for daily use?
what is a Dpatched you mean a magisk patched boot image?