After attempting to root my phone and things going along well up to the stage where I flash DM Verity & SuperSU according to this guide after doing those two things my phone is stuck in a Bootloop. Running TWRP 3.0.3 beta 1 and my OOS version before this was 4.0.
Edit: Just as a note I have already cleared my cache with no luck.
Did you format data? Next to factory reset button I had that happen to me i formated data and cleared cache and data in advance settings. Maybe it helps you too
savage166 said:
Did you format data? Next to factory reset button I had that happen to me i formated data and cleared cache and data in advance settings. Maybe it helps you too
Click to expand...
Click to collapse
I did format data after flashing dm-verity and it wiped all of my storage leaving me with an empty /sdcard. After sideloading supersu.zip (not systemless) and flashing it got stuck in a bootloop.
You're not supposed to do dm-verity and supersu. It's one or the other. If you don't want root, use dm-verity otherwise use supersu. Supersu keeps you decrypted like dm-verity does.
Related
I just flashed aicp latest build and got the decryption unsuccessful!!
why is that happening coz i have not encrypted my phone .... i even flashed lineage 15.0 and same is happening pls help me
I had to run the Qualcomm restore tool to get back from this state. Obviously you will loose all data when doing so.
The strange thing is I just flashed the same LineageOS zip as before and ended in this state. [emoji848]
pitrus- said:
I had to run the Qualcomm restore tool to get back from this state. Obviously you will loose all data when doing so.
The strange thing is I just flashed the same LineageOS zip as before and ended in this state. [emoji848]
Click to expand...
Click to collapse
what should I do now?
gulatilakshay said:
what should I do now?
Click to expand...
Click to collapse
format data if you are installing the new rom over a stock oxygem rom that will delete all your data and remove encryption.
From fastboot you need to format userdata (you will loss everything, however you might have already lost everything). You will get formatted decrypted internal storage with reduced size. Don't panic.
Then you required to flash blue_spark TWRP recovery (v50 or latest) from fastboot.
Then boot to recovery and format internal storage from Advance Wipe menu (under Wipe). You will regain the actual internal storage size.
Flash your desired rom.
Thanks
OP, I tried the latest LineageOS unofficial and got the same error. Just reflash a ROM like Cardinal Xtended or an Oreo ROM that you have verified to be working on your phone. Clear System, Data and Cache. All should be well, and you don't have to wipe storage.
Cheers!
Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
roger.hernandez91 said:
Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
Click to expand...
Click to collapse
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
beany23 said:
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
Click to expand...
Click to collapse
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
roger.hernandez91 said:
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
Click to expand...
Click to collapse
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
beany23 said:
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
Click to expand...
Click to collapse
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
roger.hernandez91 said:
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
Click to expand...
Click to collapse
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Yes quick question, did you use Magisk uninstaller package from thread or just uninstall Magisk directly from the app?
Confused on how to uninstall Magisk without encrypting my device or loosing my boot or messing anything like that up
Also, wipe Dalvik cache and cache or just cache only?
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
roger.hernandez91 said:
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
Click to expand...
Click to collapse
Sure you can. Magisk doesn't root the system so all of the files you need to discard are in /data and /cache. You need a copy of the stock kernel in image format, if Magisk didn't make a back up. I gotta say bro, I haven't uninstalled Magisk or tried, so I don't know what's going to happen when you do this.
If your phone force encrypts after flashing the kernel, you may be screwed and have to format data and lose everything. This could possibly also brick your device beyond help. Since you can't mount your system in TWRP, if for some reason it fails encryption or DM-Verify into a bootloop, from the LAF or recocery modification, it won't boot. At least, not until you find a way to mount the system, which I think will be near impossible.
With that being said, if you decide to move forward you can either wipe data and cache or remove the files one by one. Your choice.
Well I gotta say, I've had a hell of a day fixing this thing. System partition got wiped somehow and had to fight to get my backup restored, thankfully I had one. Basically came back from the dead. Ended up wiping my entire internal storage to get TWRP to shut the hell up about decrypting, flashed new recovery again, flashed Magisk v16.4 beta, and now I'm good to go. Didn't have any of the issues mentioned above. And now I'm not having /system mounting problems or the force quits upon flashing a new mod. Everything seems good.
Appreciate y'all. You guys are awesome for taking the time to help.
roger.hernandez91 said:
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Click to expand...
Click to collapse
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
beany23 said:
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
Click to expand...
Click to collapse
Nah man I actually did have to do it from laf recovery because it wasn't working from regular recovery. Had to flash it from both and also formatted data and I was good to go. I got it all figured out.
Cant boot into system after installing miui11. Everytime when i boot into system it reboots into twrp.
nerijusas said:
Cant boot into system after installing miui11. Everytime when i boot into system it reboots into twrp.
Click to expand...
Click to collapse
More details needed if you want some help or all you wanted is some condolence?
P.S. If you don't know what details, just describe what actions have been taken I was on ROM x versions x.x.x with TWRP x, how you flashed MIUI11 and what MIUI11 ROM and version you used.
TWRP version is: 3.3.1-42
I was on original rom and I used this rom: xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10
Procedure: I wiped dalvik/ART cahce, cache, System Data and then installed the rom and rebooted and I am now in bootloop.
P.S I have global version
nerijusas said:
TWRP version is: 3.3.1-42
I was on original rom and I used this rom: xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10
Procedure: I wiped dalvik/ART cahce, cache, System Data and then installed the rom and rebooted and I am now in bootloop.
Click to expand...
Click to collapse
Does your TWRP successfully decrypt data now? Do you have access to files in TWRP? Or you just see strange names.
If that is the case, just format data, it's an option in wipe menu. And then reflash ROM.
btw wiping system is not needed and useless.
Decrypts successfully because i install rom from internal storage and still it doesnt help.
nerijusas said:
Decrypts successfully because i install rom from internal storage and still it doesnt help.
Click to expand...
Click to collapse
Then everything should work, try to read this thread: https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/ , may be you not the only one.
But i would try format data any way. Format will remove everything and will create a fresh unecrypted file system. Wipe only delete files.
If it won't help you may try to flash fastboot ROM, and then format and etc.
btw When you wipe cache/dalvik, it takes some time to boot, it can be 5-10 minutes.
Hello,
I have an Indian K20 pro (Raphaelin), my bootloader has been unlocked. I flashed Indian (10.3.8.0, Android Q) through Abhishek's TWRP. I wanted to check out Miui Mix, so I did the usual, booted in to Recovery (TWRP) then clicked on Format Data, then proceeded to wipe other dalvik, cache, system, internal storage, I then tried to boot in to recovery again so that I could flash the Rom. I was stuck in fastboot, so couldn't proceed further with anything but the Fastboot logo. I then flashed Fastboot Rom (10.3.3.0) through the MiFlash tool. Booted in to the ROM, then flashed Mauronofrio's TWRP, then I repeated the same process Format Data, then, wipe other dalvik, cache, system, internal storage. Now I am back to square stuck with the Fastboot mode which doesn't seem to be losing my sight. While I did flash the fastboot rom again, I'm just hesitant to proceed further without people with experience.
Can someone please help me install Miui Mix? Thank you.
Format data type yes / wipe dalvik , cashe maybe internal but not system.
I hope this will work
Platinum_Pyth0n said:
Hello,
I have an Indian K20 pro (Raphaelin), my bootloader has been unlocked. I flashed Indian (10.3.8.0, Android Q) through Abhishek's TWRP. I wanted to check out Miui Mix, so I did the usual, booted in to Recovery (TWRP) then clicked on Format Data, then proceeded to wipe other dalvik, cache, system, internal storage, I then tried to boot in to recovery again so that I could flash the Rom. I was stuck in fastboot, so couldn't proceed further with anything but the Fastboot logo. I then flashed Fastboot Rom (10.3.3.0) through the MiFlash tool. Booted in to the ROM, then flashed Mauronofrio's TWRP, then I repeated the same process Format Data, then, wipe other dalvik, cache, system, internal storage. Now I am back to square stuck with the Fastboot mode which doesn't seem to be losing my sight. While I did flash the fastboot rom again, I'm just hesitant to proceed further without people with experience.
Can someone please help me install Miui Mix? Thank you.
Click to expand...
Click to collapse
No need to wipe internal storage, it gets wiped when you format data. Don't wipe system.
After formatting data go to the mount menu and unmount data, then mount it again. You should then be able to access the data partition OK, without needing to reboot into TWRP. From here you can move the ROM your want to install onto the phone and then flash it.
Also, after reinstalling the fastboot ROM, make sure you've booted into MIUI at least once before installing TWRP.
ergysramaj said:
Format data type yes / wipe dalvik , cashe maybe internal but not system.
I hope this will work
Click to expand...
Click to collapse
Yup, didn't work. Thank you for helping though.
Now that you have a clean stock fastboot rom flashed, flash twrp, wipe data(use that where you have to type YES), then flash your mix ROM. Don't wile system lol
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
No need to wipe internal storage, it gets wiped when you format data. Don't wipe system.
After formatting data go to the mount menu and unmount data, then mount it again. You should then be able to access the data partition OK, without needing to reboot into TWRP. From here you can move the ROM your want to install onto the phone and then flash it.
Also, after reinstalling the fastboot ROM, make sure you've booted into MIUI at least once before installing TWRP.
Click to expand...
Click to collapse
Hey Robo.5000, we meet again.
A summary of what I have done so far: Installed Fastboot 10.3.3.0, booted into the ROM, then finished setting up the account. Tried to Flash TWRP (Mauro's & Abhishek's) builds, then a Mod on the Telegram group of Miui Mix suggested me to: Format Data, then do the Dalvik Cache, System, Cache, etc, then tried installing the ROM (MiuiMiX_2.2.0_raphael_9.11.7_v11-10_20191107.zip).While installing it tells me that my Phone is Raphaelin and not Raphael. I do not know what to do.
same here always end with fastboot screen when i try to flash a custom rom or root my device via magisk 20.1
device k20 pro 8gb/256 came with mi 9 t pro rom
really appreciated if any one can post step by step to flash cusom rom or root the device
pocophone f1 was my prev device it was easierto flash custom or root
i dont know what i miss
Do not wipe system.
Can i factory reset my Samsung A8 (2018) phone witch is rooted and using Magisk v22
I've flashed TWRP "twrp-3.5.0_9-0-jackpotlte.img.tar" using Odin3_v3.13.3
also installed RMM_Bypass_v3_corsicanu.zip and no-verity-opt-encrypt-6.0.zip
Will my phone remain rooted after a factory reset ?
Should i reïnstall RMM_Bypass_v3_corsicanu.zip and no-verity-opt-encrypt-6.0.zip ?
(Prevent Prenormal KG/RMM State / disable dm-verity to prevent Boot Loop)
Succes !
I've wiped DATA / DALVIC and CACHE using TWRP
Rebooted into recovery, and since DATA was'nt empty i used the Format DATA option
Then i reinstalled RMM_Bypass_v3_corsicanu.zip, no-verity-opt-encrypt-6.0.zip and Magisk
(possible it is not needed, but wanted to be safe and prevent a Boot-loop or an RMM lock)
After a system reboot everything works fine