Related
Here a more complete guide.
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive
Great news!
thanks for the guide buddy.
Please explain by video?
Stock camera workink? Or need flash mi a1 cam module?
blue4 said:
Stock camera workink? Or need flash mi a1 cam module?
Click to expand...
Click to collapse
everything is working
you just can't set password for hotspot
if you are using your phone as a hotspot. it will be open
Gapps?
ouroboros12 said:
Gapps?
Click to expand...
Click to collapse
Since this guide's first step is to install TWRP, use TWRP to flash the latest Gapps.
On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?
rosiepie said:
On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?
Click to expand...
Click to collapse
It's the same because now encryption is disabled(formatting data in the classic way with encryption enabled cause a bootloop, this is why i suggest to use userdata from stock).
I will update mainpost.
When you flash userdata.img, why is from stock rom and not from your actual rom?.
Txatxiquesi said:
When you flash userdata.img, why is from stock rom and not from your actual rom?.
Click to expand...
Click to collapse
Because the one from your actual rom is encrypted and can't be read by other roms(if not you can skip this step, but i assume not).
I don't know why formatting with twrp cause a bootloop if device is encrypted, the only way i've found to clean data without issue is flashing userdata from stock... if anyone find another please tell me .
Thx for guide. Working.
blue4 said:
Thx for guide. Working.
Click to expand...
Click to collapse
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?
Thank you for this guide! Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data. "Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs. Best results - no bugs @All I got with the combination of @yshalsager´s twrp (18.08.) as kernel combined with stock 9.6.4.0 (july sec patch). You can patch the old twrp with the official afterwards.
Twrp inofficial yshalsager: - mtp not working, vendor not able to being backuped vs official twrp: sdcard not working... And no twrp that can work with pie encryption... Hopefully some dev will find a solution!
Voodoojonny said:
Thank you for this guide!
Click to expand...
Click to collapse
Welcome!
Voodoojonny said:
Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data.
Click to expand...
Click to collapse
I've seen that re-installing twrp fixes, could you try?
Voodoojonny said:
"Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
Click to expand...
Click to collapse
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Voodoojonny said:
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs.
Click to expand...
Click to collapse
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?
mac12m99 said:
Welcome!
I've seen that re-installing twrp fixes, could you try?
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?
Click to expand...
Click to collapse
I tried to reinstall twrp with
a) patched stock 9.6.4.0 with and without dm-verity
b) patched stock 9.6.9.0 same as above
Both leads to bootloop flashing userdata.bin doesn't fix
c) a and b with magisk and permissiver - > bootloop
Only Yshalsager's twrp as boot with 9.6.4.0 vendor works... All other vendors: broken wifi; all other kernels: bootloop (no dm verity, permissiver, root - nothing helps)
And if you flash userdata.bin you can read data with twrp, but booting havoc will change data, sothat twrp can't read it anymore. Flashing official twrp installer doesn't change anything...
It'slike a circle... Simply: stock twrp is only compatible with encryption of stock userdata... Only solution: decrypt...
I will send you logs tomorrow! Thank you!
mac12m99 said:
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?
Click to expand...
Click to collapse
Yes and no. I flashed directly patched_boot.img for magisk and only booted twrp with fastboot for flashing Gapps and format data. But this procedure is good. The rom is very fast but sometimes micro-lagging more than stock.
Offline charging not work. (Rooted boot.img issue)
---------- Post added at 09:53 PM ---------- Previous post was at 09:07 PM ----------
Pixel Experience working too and smoother than Havoc for me. (Cam)
Apparently, since the last build of Havoc, is not necesary changing selinux, no bootloop on enforcing.
mac12m99 said:
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive
Click to expand...
Click to collapse
Installed aex, the camera does not work. Havoc does not work either.But there is a good news. I made a backup in twrp and then restored it. Restoration of backups works fine.
Then I tried to flash the gsi project treble. In twrp, I did wipe data, system, dalvick and internal storage. then it rebooted into twrp.connected to the computer and downloaded gsi havoc.a, then clicked the installation setting img. and chose the system image. after installation, I rebooted the phone in twrp, and then booted into the system. and the system worked well. the camera and hotspot did not work.
I think many problems people are having here are due to the fact the tutorial, while useful, is incomplete. I had to stuggle a bit but I got everything working as it should (well, besides SELinux Enforcing). I can make a clear English-language thorough tutorial if anyone wants. I don't want to steal anyone's thunder.
Enjoying some Havoc Pie myself atm
Hey there, I've tried installing the blu_spark TWRP, I've temporarily installed v9.86 .img file via fastboot, then tried flashing the zip for blu_spark TWRP, however every time I reboot into recovery it becomes the default OnePlus recovery. I don't get a "slide to allow system modifications" at the start, is that a problem? Thanks in advance!
If this can help, i fastbooted the Blu_Spark, flashed what i needed (magisk) and then flashed the official TWRP, i have the official now installed, not the Blu_Spark (i still prefer use the Blu_spark anyway for every official update, just in case)
Ok
Perfect
NeroNext said:
If this can help, i fastbooted the Blu_Spark, flashed what i needed (magisk) and then flashed the official TWRP, i have the official now installed, not the Blu_Spark (i still prefer use the Blu_spark anyway for every official update, just in case)
Click to expand...
Click to collapse
I have a big problem… On my op6 i have android pie version 9.0.2 ( the last one ) and already I have unlocked the bootloader but when i charge by fastboot mode any versions of twrp.img ( blu spark and the last one of enchilada, version 3.2.3 ) when I tap on "Install" go directly on sdcard and here I see many folders with strange name….like "oPgjjhFrhgh65bfgHg"... and there aren't the normal folder's names into sdcard… so I don't see also the zip file for install Twrp or Magisk...Can you help me please?
Fastboot to Recovery using the blu_spark Image. In twrp Flash the zip and the twrp should be still there after a reboot
unrated87 said:
Fastboot to Recovery using the blu_spark Image. In twrp Flash the zip and the twrp should be still there after a reboot
Click to expand...
Click to collapse
Thank you for your answer!! But the problem that I have is when I fastboot to recovery using The Blu Spark Image: when I have done this when i push on " Install " I can see only strange folders with strange names like " 0fjhsgegfjhjskhgf".... and I can not see the normal folders with the normal name into sdcard... How I said already I have the bootloader unlocked and I have the stock rom 9.0.2 on my op6.
data corrupted
more_than_hater said:
data corrupted
Click to expand...
Click to collapse
So, what I have to do?
Format data probably?
unrated87 said:
Format data probably?
Click to expand...
Click to collapse
Thank you unrated! I try and I say you. Only another little question : I format data by twrp, is it correct? and after I reboot without to reinstall the stock rom, is it correct?
scarface77 said:
Thank you for your answer!! But the problem that I have is when I fastboot to recovery using The Blu Spark Image: when I have done this when i push on " Install " I can see only strange folders with strange names like " 0fjhsgegfjhjskhgf".... and I can not see the normal folders with the normal name into sdcard... How I said already I have the bootloader unlocked and I have the stock rom 9.0.2 on my op6.
Click to expand...
Click to collapse
No data is corrupted. Before doing this remove any screen lock (pin or swipe) and your data will not show up as encrypted anymore. It is twrp bug afaik.
roel1976 said:
No data is corrupted. Before doing this remove any screen lock (pin or swipe) and your data will not show up as encrypted anymore. It is twrp bug afaik.
Click to expand...
Click to collapse
This night I try to root my op6 by fastboot TWRP without any pin or facelock or swipe ( without any kind of screen lock ) and if I solve my problem you'll become my hero!!!!!
roel1976 said:
No data is corrupted. Before doing this remove any screen lock (pin or swipe) and your data will not show up as encrypted anymore. It is twrp bug afaik.
Click to expand...
Click to collapse
Roel1976 you are my hero!!!! Thank you so much!!!!!! You have solved my problem!!! Thanks thanks thanks thanks…..I was going to be crazy because i tried many and many time to root my op6 reinstalling many and many time the stock rom pie and at last you arrived….and you solved my problem!!!
So there is a bug into the last versions of all TWRP, enchilada and blu spark: if we have a lock screen (PIN , Sequence, facial lock screen) into the sdcard of TWRP we see strange folder's names like "OFgsjdhdfkeiu564sflk"...
If we disable all lock screen (PIN, Sequence, facial lock…) and reboot in fastboot and load TWRP, how a kind of magic, we can see all folders with the normal name and all zip and .img that we have copied into!!!
So is not a data corrupted and so we have not to format data, but we have only to disable all kind of lock screen!!!
Roel 1976 thank you so much everywhere you are!!!
haha thanks mate, happy to be of assistance. I just found someone who suggests a solution to the encrypted data problem:
https://forum.xda-developers.com/showpost.php?p=78100903&postcount=3150
Hi,
So I followed this tutorial https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/ (but I used more up to date downloads links than what was on the article) to update my phone to the latest oxygenos on my OnePlus 6.
The install went well, I could reboot on my phone without problems. The thing is when I ran magisk manager it said that magisk wasn't installed. So I rebooted to twrp and flashed again magisk then rebooted. Now when the phone rebooted and asked me for my pin number it automatically went to "Shutting down phone" and rebooted to twrp. So I flashed the magisk uninstaller but it didn't rebooted well. Then I thought I had to switch the active slot, so in twrp I switched to slot A. Then it rebooted on fastboot. I understood I did something really bad so I ran "fastboot --set_active=b" on my computer.
Now my phone cannot actually boot and everytime I get in twrp except that now it doesn't ask me to unlock the phone to decrypt it and just asks me if I want to get into twrp in read only mode. When I navigate to /sdcard, it is full of weird folder name which is because, if I understand well, twrp has failed to decrypt it.
Is my phone bricked? Can I recover data? Can I repair my installation?
EDIT: if you need more informations that I forgot to give don't hesitate to ask.
EDIT2: I tried to reboot to fastboot mode and issue on my computer "fastboot boot twrp-3.2.3-1-enchilada.img" to see if the official twrp could decrypt the data (I'm currently using bluespark's twrp). I get the following error: "FAILED (remote: unknown command)". I understand now I'm pretty ****ed. Right now I'd only like to recover my data (mostly hundreds of pictures) and then flash a stock rom (except if it's actually possible to repair the system and boot normally). How can I decrypt /sdcard if twrp can't do it?
Thanks in advance for your help, I'm pretty lost right now and it's quite an urgent situation.
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Thank you for your answer, everything's back to normal
I'll make sure to follow the official tutorials next time.
only4dank said:
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Click to expand...
Click to collapse
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
thejase said:
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
Click to expand...
Click to collapse
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
only4dank said:
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
Click to expand...
Click to collapse
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
thejase said:
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
Click to expand...
Click to collapse
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
only4dank said:
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
Click to expand...
Click to collapse
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
ante0 said:
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
Click to expand...
Click to collapse
Same. But if you install it with version 8.0 after the update, it works again. Just f.y.i..
noom4_5 said:
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Click to expand...
Click to collapse
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
wwwryan said:
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
Click to expand...
Click to collapse
Answered my own question but wanted to leave this here for others just in case it is helpful. Using twrp-3.2.3-x_blu_spark_v9.91_op6.img I was able to fastboot boot the img file and this version of TWRP offered to decrypt. From there first thing I did was adb pull my entire sdcard to my PC for save keeping.
My issue was a result of restoring from an earlier backup to recover some data. I had recently updated to 9.0.5 but accidentally deleted something I had no backup for so was restoring a previous TWRP back from 9.0.4. After the restore I couldn't boot the OS and all official version of TWRP would no longer offer to decrypt my data. Of course, I could not restore the backup I had just taken either since it was encrypted on the internal SD card. From now on I will just take TWRP backups to external storage via OTG USB and not even risk it.
Happened to me a few days ago
You can NOT recover your data. But you will be able to fix your phone.
Just do a Factory Reset from TWRP (Wipes Everything) and a wipe of system etc
Then just sideload or put the latest OOS back on the phone and install it.
Trust me, I have tried everything for trying to recover and decrypt the data... Somehow our phones did change the Encryption Keys from /data/unencrypted so there is no way to recover unless you can get the same key out of luck of using the encryption algorithm and salting process that Android uses.
https://imgur.com/y8ENw77
https://imgur.com/q7BPOCy
I've done this a few times. Actually... every time I update; save for the last two times. Just two notes that you already seem to have figured out:
1) Always remember turn off your active modules. (Just turn them off, you don't need to uninstall them.) Simply doing that seems to have fix OTA issues for me. I try to do it before I even download the update and definitely before I install it.
2) No matter how badly I foul up (except for the first time), I never wipe it when trying to fix it. Just side boot Blu Spark TWRP and flash the OS again. Boot it up once without root. Then go ahead to side boot Blu Spark TWRP again to root. I never install TWRP to the device at all. Even with Blu Spark, it seems to get iffy with me. If I want to flash something, I just let it wait until I'm home so I can side load Blu Spark.
Hello, been running twrp with encryption on Lineage OS 16 without problems for 6 months. But yesterday I flashed new android Q factory image and was unable to decrypt my data in twrp, even when I put the right password in it says ''password failed, please try again''. I tried flashing various factory images, custom roms even Lineage 16 but problem persists. I had this same problem back then when I first bought this phone but managed to solve it, I can't remember how I did it. TWRP is up to date. Any ideas? thanks.
It's TWRP issue. Sadly TWRP 3.3.1 is not available in zip format. Only in .img format. In 3.3.1 this problem is resolved.
As workaround you can remove any PIN, fingerprint and set security to none in setting and you won't have to enter anything in TWRP. Do whatever you want in TWRP and then set up PIN and fingerprint again.
matusala said:
It's TWRP issue. Sadly TWRP 3.3.1 is not available in zip format. Only in .img format. In 3.3.1 this problem is resolved.
As workaround you can remove any PIN, fingerprint and set security to none in setting and you won't have to enter anything in TWRP. Do whatever you want in TWRP and then set up PIN and fingerprint again.
Click to expand...
Click to collapse
Yeah I know this, but why did it started to do this after flashing Q factory image? TWRP worked without any problem on various custom roms. Actually now I remembered that while flashing Q factory image there was a problem mounting vendor and system partition, so I went back and flashed Lineage 16 and there this TWRP password thing started if I remember correctly.
I came here looking for the answer to this very issue.
I shot off an email to TWRP if they were going to update the latest zip to 3.3.1 because fastbooting to the img works fine.
I might try the trick of removing pin and security and try again.
I have the same problem but with 9.0, if I have a pin it's ok it decrypts just fine but when I have the fingerprint set up I get this problem, it kinda blows, I'm not using twrp everyday but it still blows that you have to disable security Everytime you want to use it, also, last night I used twrp with the security on it could not decrypt so and when i tried to reboot into system, I got the prompt to install the twrp app, I screwed up and used the slider instead of the button to cancel the installation and it messed up the system, so watch out for that crap.
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Did you try with Miflash?
try with MiFlash. Flash stock rom in fastboot mode
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Thelm76 said:
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Click to expand...
Click to collapse
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
dhaern said:
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
Click to expand...
Click to collapse
Well that the thing I tried when I accidentally replaced my boot partition... And my phone was only booting on twrp or fastboot... also the weird thing I found is that /data/adb didn't exist
But many thanks to you all it works now.
I'll maybe try to make a guide on how to install Magisk on the Xiaomi EU weekly rom, as android 11 is only supported by the canary build. (if I manage to find a way to properly remove defective modules in TWRP :fingers-crossed
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Tecardo said:
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Click to expand...
Click to collapse
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
If you want everything to work you need to format data!!
Thats the point why using android 11 roms is hard, twrp cant decrypt it (until you flash rom with a10 and then a11 because partition is encrypted in a10 style)
Thelm76 said:
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
Click to expand...
Click to collapse
That's easy to fix, you installed Android 11 or? Don't use pin, use gesture. Twrp can't decrypt android 11 pin right now
Thelm76 said:
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Click to expand...
Click to collapse
NO flash only fastboot boot twrp.img