Whenever I am trying to flash open Beta 7 with magisk and a kernel and then the No Verity zip , device boots with no with no signal and then I start setting up the device it hangs it hangs on the screen where it asks for the name of the device then it again reboots then this process goes on and I am unable to skip the test to the home screen my flashing procedure is as follows.
Clean flash open Beta 7 then reboot to recovery after clearing cache and Dalvik cache I flash magisk with a kernel zip flash or bluespark then the no Verity zip . Please help me out.
Aarju said:
Whenever I am trying to flash open Beta 7 with magisk and a kernel and then the No Verity zip , device boots with no with no signal and then I start setting up the device it hangs it hangs on the screen where it asks for the name of the device then it again reboots then this process goes on and I am unable to skip the test to the home screen my flashing procedure is as follows.
Clean flash open Beta 7 then reboot to recovery after clearing cache and Dalvik cache I flash magisk with a kernel zip flash or bluespark then the no Verity zip . Please help me out.
Click to expand...
Click to collapse
Are you using the latest twrp ? Also if decryption is not that important then try flashing Magisk after the 1st boot as it is known to sometimes cause bootloops and issues
Thesuprememonkey said:
Are you using the latest twrp ? Also if decryption is not that important then try flashing Magisk after the 1st boot as it is known to sometimes cause bootloops and issues
Click to expand...
Click to collapse
I am using blue spark latest recovery and decryption is important to me as it enhances the performance by some margin .By the way what's your set up ????
Thanks for your reply .
Aarju said:
Whenever I am trying to flash open Beta 7 with magisk and a kernel and then the No Verity zip , device boots with no with no signal and then I start setting up the device it hangs it hangs on the screen where it asks for the name of the device then it again reboots then this process goes on and I am unable to skip the test to the home screen my flashing procedure is as follows.
Clean flash open Beta 7 then reboot to recovery after clearing cache and Dalvik cache I flash magisk with a kernel zip flash or bluespark then the no Verity zip . Please help me out.
Click to expand...
Click to collapse
I have the same issue....
ELoTRIX said:
I have the same issue....
Click to expand...
Click to collapse
What to do now ..??
Aarju said:
What to do now ..??
Click to expand...
Click to collapse
I don't know... are you decrypted or encrypted?
ELoTRIX said:
I don't know... are you decrypted or encrypted?
Click to expand...
Click to collapse
I want to flash decrypted but can't.
Related
I have a moto g5 plus xt1687 and I was able to unlock the boot loader and install TWRP successfully. I then install no-verity-opt-encrypt-5.1.zip without trouble and reboot to TWRP again. When I try and install Magisk v14 I get the error message "/system could not be mounted"
I have wiped the system earlier so I do not have an operating system installed anymore but I can get into TWRP. What are my solutions? Thanks.
Flash a custom rom in TWRP or reflash stock with fastboot.
Sent from my Moto G (5) Plus using Tapatalk
Custom rom
riggerman0421 said:
Flash a custom rom in TWRP or reflash stock with fastboot.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Where can I find the custom rom for moto g5 plus xt1687? Thanks
s_beckett said:
I have a moto g5 plus xt1687 and I was able to unlock the boot loader and install TWRP successfully. I then install no-verity-opt-encrypt-5.1.zip without trouble and reboot to TWRP again. When I try and install Magisk v14 I get the error message "/system could not be mounted"
Click to expand...
Click to collapse
Hi,
If you install the ElementalX custom kernel v1.02 then you fix the error.
Futhermore, with this kernel you don't need the "no-verity-patch"... as I advise that this patch writes the SYSTEM partition... so you lost the option for OTAs.
Here the thread to download this custom kernel:
http://forum.xda-developers.com/g5-plus/development/kernel-elementalx-1-00-moto-g5-plus-t3614211
Regards!
ElementaX
manos78 said:
Hi,
If you install the ElementalX custom kernel v1.02 then you fix the error.
Futhermore, with this kernel you don't need the "no-verity-patch"... as I advise that this patch writes the SYSTEM partition... so you lost the option for OTAs.
Here the thread to download this custom kernel:
http://forum.xda-developers.com/g5-plus/development/kernel-elementalx-1-00-moto-g5-plus-t3614211
Regards!
Click to expand...
Click to collapse
I installed LineageOS and then ElementalX and when I reboot it takes me back to TWRP. Are my steps wrong? The bigger question is why am I getting the "/system could not be mounted" when I installed magisk v14 so remain unrooted??. I followed the steps carefully. What is a clear path out of this mess? Very frustrating. Any assistance is appreciated.
s_beckett said:
I installed LineageOS and then ElementalX and when I reboot it takes me back to TWRP. Are my steps wrong? The bigger question is why am I getting the "/system could not be mounted" when I installed magisk v14 so remain unrooted??. I followed the steps carefully. What is a clear path out of this mess? Very frustrating. Any assistance is appreciated.
Click to expand...
Click to collapse
Hi,
I'm on stock, so if you use LineageOS, then this is my recomendation:
- Reinstall Lineage and check that all works (remeber to do "wipe cache" after install it and before boot it).
- Then install the ElementalX-los version, and reboot. Check that all works.
- Finally, after a full reboot install Magisk v14.0.
If the error of mount in Magisk continues, ask @flar2 to fix the "los" version like the Stock-1.02.
Regards.
Some success
manos78 said:
Hi,
I'm on stock, so if you use LineageOS, then this is my recomendation:
- Reinstall Lineage and check that all works (remeber to do "wipe cache" after install it and before boot it).
- Then install the ElementalX-los version, and reboot. Check that all works.
- Finally, after a full reboot install Magisk v14.0.
If the error of mount in Magisk continues, ask @flar2 to fix the "los" version like the Stock-1.02.
Regards.
Click to expand...
Click to collapse
I was able to install magisk v14, then I installed PureNexus and the suggested gapps. When I reboot I kept going back to TWRP but if I go to the bootloader I am able to start the PureNexus OS without issue (no decrypt error). When I do a root check it indicates I am not rooted. What should I do in the proper order? Should I install no-verity-opt-encrypt-5.1. and "Magisk-v14 again without causing a problem, is that the solution? How many times can you reinstall that those files. Thank for your help.
s_beckett said:
I was able to install magisk v14, then I installed PureNexus and the suggested gapps. When I reboot I kept going back to TWRP but if I go to the bootloader I am able to start the PureNexus OS without issue (no decrypt error). When I do a root check it indicates I am not rooted. What should I do in the proper order? Should I install no-verity-opt-encrypt-5.1. and "Magisk-v14 again without causing a problem, is that the solution? How many times can you reinstall that those files. Thank for your help.
Click to expand...
Click to collapse
Sorry?
Magisk will need to be installed after then ROM and the Kernel.
Futhermore, if you use the proper kernel, you don't need to install the "no-verity-opt-encrypt-5.1".
Please, do it in this order:
1) Install PureNexus or your preferable ROM.
2) Boot and check it (don't configure, only a simple check).
3) Reboot to TWRP and install the ZIP of the custom kernel (I recomend ElementalX).
4) Boot and check it (again don't configure).
5) Reboot to TWRP and re-format the "Data" partition (select "f2fs" if it has another filesystem)... this will disable the "encryption enforcement" (as it formats withtout encryption and the kernel disables the enforcement).
6) Boot and configure.
7) Reboot to TWRP and install Magisk v14.
8) Boot and check MagiskManager, you're now rooted.
9) If you like install Xposed for Magisk and configure it.
That's all!
manos78 said:
Sorry?
Magisk will need to be installed after then ROM and the Kernel.
Futhermore, if you use the proper kernel, you don't need to install the "no-verity-opt-encrypt-5.1".
Please, do it in this order:
1) Install PureNexus or your preferable ROM.
2) Boot and check it (don't configure, only a simple check).
3) Reboot to TWRP and install the ZIP of the custom kernel (I recomend ElementalX).
4) Boot and check it (again don't configure).
5) Reboot to TWRP and re-format the "Data" partition (select "f2fs" if it has another filesystem)... this will disable the "encryption enforcement" (as it formats withtout encryption and the kernel disables the enforcement).
6) Boot and configure.
7) Reboot to TWRP and install Magisk v14.
8) Boot and check MagiskManager, you're now rooted.
9) If you like install Xposed for Magisk and configure it.
That's all!
Click to expand...
Click to collapse
First off really appreciate your help and patience with me. Followed your guidelines have root and PureNexus is working ok. One last issue that persists. Every time I reboot it goes directly to TWRP. I have to go to the bootloader and start the OS that way. How can I get it to boot directly into the OS? Thanks again.
s_beckett said:
First off really appreciate your help and patience with me. Followed your guidelines have root and PureNexus is working ok. One last issue that persists. Every time I reboot it goes directly to TWRP. I have to go to the bootloader and start the OS that way. How can I get it to boot directly into the OS? Thanks again.
Click to expand...
Click to collapse
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
manos78 said:
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
Click to expand...
Click to collapse
Unfortunately this did not work. Are there any other options?
s_beckett said:
Unfortunately this did not work. Are there any other options?
Click to expand...
Click to collapse
Enter into bootloader mode, connect your phone to the PC and type "fastboot continue" command in ADB.
manos78 said:
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
Click to expand...
Click to collapse
I have found success! I wiped the drive in TWRP and install Stoneware v67 then installed magisk v14 and the boot process is now directly to the OS and it is rooted. I did not load a custom ROM but it is working fine. Frankly, I really do not understand which ROM needs a custom one or not and wish there were clear instruction on this matter as there are so many ROMs and some did not install or work well when I tried them. In any event, I appreciate your ongoing assistance and patience with me.
s_beckett said:
I have found success! I wiped the drive in TWRP and install Stoneware v67 then installed magisk v14 and the boot process is now directly to the OS and it is rooted.
Click to expand...
Click to collapse
Great!
The behaviour you have observed is because at some point the "reboot cause" (the trigger that launch the recovery at every boot) isn't cleared or is everytime set incorrectly. If you found a method for clear the cause, then you can continue...
I have bricked my phone the issue I am facing is I don't own and can't afford an SD card to sideload the rom onto my phone is there a 7.0 stock based rom that is flashable via TWRP or? Really need some ideas need to fix this device.
If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.
wang1chung said:
If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.
Click to expand...
Click to collapse
I use root and both but when I decided to remove root and was looking at installing another rom it failed now I don't see any twrp flashable roms for my device would you know of any? I tried stock but it can't be flashed from TWRP sadly I have no bootable rom at the moment.
@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.
wang1chung said:
@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.
Click to expand...
Click to collapse
I have never modified that before what would I need to modify to get it working?
@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.
wang1chung said:
@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.
Click to expand...
Click to collapse
I will give that a shot turns out a factory reset did not start up device so this is my last choice as I can still access recovery
edit: so after modifying the script it did flash without an issue but it still has failed to boot reloading the bootloader.
Flash magisk or the no verify file
wang1chung said:
Flash magisk or the no verify file
Click to expand...
Click to collapse
the no verify file was flashed when I rooted this device
Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?
wang1chung said:
Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?
Click to expand...
Click to collapse
I tried flashing Unofficial LineageOS 14.1 for ZE552KL by basenode with opengapps it just failed to flash not an error 7 it actually gave me a wrong device error although I know I have the ze552kL model. and since then it don' boot it tries to you see the asus logo and it just restarts again in a boot loop
Flash magisk right now, then wipe cache and dalvik
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Thanks for the info will give that a shot as soon as I do get home from work. Just ablittle annoyed that first phone I have ever bricked
[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind
mastermarkofroms said:
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792
[email protected]@ said:
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792
Click to expand...
Click to collapse
Problem solved back on stock thanks for all the help @everyone
mastermarkofroms said:
Problem solved back on stock thanks for all the help @everyone
Click to expand...
Click to collapse
I thought you ask for the LOS rom.
I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me
mastermarkofroms said:
I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me
Click to expand...
Click to collapse
Which rom?
I have a rooted OnePlus 5 on the latest beta and I'm trying to flash back to the latest stable OOS through TWRP. When TWRP starts, it asks for a decryption password which I never set -- I have a lockscreen pattern. I made the mistake of trying to flash with a pattern and face unlock. Is there a workaround for this? I tried to sideload another stable zip but for some reason I get an "System.ui has crashed" error. Can anyone help?
Try formatting data in twrp via wipe option.
Reboot in to recovery/
Then try flashing any ROM.
Sent from my OnePlus 5 using Tapatalk
smohanv said:
Try formatting data in twrp via wipe option.
Reboot in to recovery/
Then try flashing any ROM.
Click to expand...
Click to collapse
Yeah, that's what I eventually had to do. Thanks anyway
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Factory reset from TWRP?
yes
null0seven said:
yes
Click to expand...
Click to collapse
So, do you mean the classic Wipe data, cache and dalvik?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
TWRP Users
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Click to expand...
Click to collapse
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Galeanatur said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Click to expand...
Click to collapse
I don't have the OTA but the full rom, isn't simplier to update with the full ROM?
I think I'm going to try the null0seven's solution
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Ok, I've done this and actually is even worse, the device started to boot in recovery again and TWRP doesn't recognize that the internal storage is crypted, so i can't even access the internal storage (it shows only strange folders), so, now I can't flash the nandroid backup anymore.
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
null0seven said:
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
Click to expand...
Click to collapse
So I've to Full wipe and then adb sideload the ROM? Because at the current state I can't even boot the device, it always starts in TWRP
Edit: I've also tried the blue_spark's version but nothing changed, TWRP can't recognize the encrypted storage
you can try this first.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
fuji97 said:
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Click to expand...
Click to collapse
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
ebproject said:
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
Click to expand...
Click to collapse
No, I flashed the full ROM downloaded from the OnePlus server
Have you tried formatting data?
Cablespider said:
Format data.
Click to expand...
Click to collapse
So, full format data and flash rom + TWRP + Magisk?
fuji97 said:
No, I flashed the full ROM downloaded from the OnePlus server
Click to expand...
Click to collapse
You're best bet is to use the MSM tool
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
fuji97 said:
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
Click to expand...
Click to collapse
Maybe it was a Magisk module that caused it. I removed pixel module from Magisk and it done the same to me.
Sorry for my wrong English
I am currently on stock miui 10.3.6.0 .I have unlocked the bootloader,Installed TWRP recovery & rooted my device with magisk.Now i am unable to get the latest miui 10.3.7.0 update.!
Is there any way in whick i can update my device to latest miui rom?
If there please help me.
I am not finding any link which is helping me.
I downloaded latest miui recovery rom from here but unfortunately there is an error i.e flash all.bat is missing in xiaomiflashtool.Tried to flash the same rom through TWRP but there again is an error i.e compatibility zip missing.
a download link to miui 10.3.7.0 fastboot rom will be appreciated.please help
Thanks in advance
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409/page2
Download the full recovery rom from here: https://xiaomifirmwareupdater.com/miui/
darhma said:
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409/page2
Download the full recovery rom from here: https://xiaomifirmwareupdater.com/miui/
Click to expand...
Click to collapse
Thanks very much it helped. I have downloaded fastboot Rom and flashed it. I have another big issue,after flashing 10.3.7.0 update I got miui stock recovery Installed so I again.
Flashed twrp from fastboot.
Then format data.
Flash magisk.
And reboot.
But after successful reboot and setup when I choose to use pattern or pin or password as authentication.The device is not recognizing my correct pin or password.It says password incorrect. Please help I am not finding any solution for this.
What is the correct pattern to install recovery to successful magisk install.
Thanks
ChandrakantBelell said:
Thanks very much it helped. I have downloaded fastboot Rom and flashed it. I have another big issue,after flashing 10.3.7.0 update I got miui stock recovery Installed so I again.
Flashed twrp from fastboot.
Then format data.
Flash magisk.
And reboot.
But after successful reboot and setup when I choose to use pattern or pin or password as authentication.The device is not recognizing my correct pin or password.It says password incorrect. Please help I am not finding any solution for this.
What is the correct pattern to install recovery to successful magisk install.
Thanks
Click to expand...
Click to collapse
Why did you used fastboot rom instead of the recovery rom? This way you didn't update the rom but reinstalled it. So I think that the only way to get rid of the password request is to format data partition from recovery and then install magisk. Next time you have to update you have to download the RECOVERY rom, dirty flash it and flash magisk before rebooting to system.
darhma said:
Why did you used fastboot rom instead of the recovery rom? This way you didn't update the rom but reinstalled it. So I think that the only way to get rid of the password request is to format data partition from recovery and then install magisk. Next time you have to update you have to download the RECOVERY rom, dirty flash it and flash magisk before rebooting to system.
Click to expand...
Click to collapse
Ok thanku.So now i have to flash TWRP recovery.then boot into recovery wipe data then install magisk right? Is there any other zip to flash? What is vm verity zip? I have to flash that also?
ChandrakantBelell said:
Ok thanku.So now i have to flash TWRP recovery.then boot into recovery wipe data then install magisk right? Is there any other zip to flash? What is vm verity zip? I have to flash that also?
Click to expand...
Click to collapse
You have to flash twrp reboot to recovery if it asks for a password format data then install magisk. Vbmeta is needed just when you change rom from miui to aosp, so in this case you don't need it