Hi all
I experience kinda weird behaviour with my OP6T.
I wiped and upgraded to Android 10 a few days ago (10.3.1). I installed TWRP and immediatyl flashed Magisk using @mauronofrio all-in-one tool. I boot up, installed what I needed and all was going good.
By using the phone I noticed that in drawer there was 2 file manager app: one I think was from Google. So I downloaded an uninstaller and deleted it. After that I discovered that, without "File" (app name) I was unable to give folder access to Poweramp scan function (it was just saying the File app keep crashing).
I tried to install it again but nothing.
Now, the good stuff. Keep in mind root was working good. I also successfuly rebooted phone multiple time with no issues.
After I tried to install File app, I restarted my phone and, surprise, it keep stuck on bootloader warning screen for like 30 seconds and after it goes into recovery (TWRP).
I tried to flash recovery again together with Magisk but nothing. Same result (sometimes it wasn't even boot in TWRP but standard fastboot screen). In the end, I tried just flashing TWRP without Magisk and surprise: it booted. Without root of course.
I did some other tests, tried again (including trying to boot from slot B but that doesn't work and no decrypt message appear).
I don't understand what is going on.
What can I do further ? On Android 9 I experienced something like that but with a normal TWRP/Magisk flash it was returning all normal. It's strange because the advice from AIO says to flash TWRP and Magisk otherwise I brick the phone.
Recap:
Only TWRP installed on partiton A/B -> Phone boot with no root
TWRP (partion A/B) + Magisk (only partition A ?) -> Phone doesn't boot and go in recovery
Thanks
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
mauronofrio said:
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
Click to expand...
Click to collapse
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
rootgen said:
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
Click to expand...
Click to collapse
So maybe is something else
mauronofrio said:
So maybe is something else
Click to expand...
Click to collapse
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
rootgen said:
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
The installer patch both slots regardless of everything
Hmm, I might have missed it but after you flashed trwp to your phone did you reboot back to recovery then install root.. just asking..
Related
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?
auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.
UPDATE - Did not manage to find a way to get TWRP installed permanently but did manage to install Lineage OS 16 (which was my end goal) via hotboot of their recovery IMG, so happy with that at least! Appreciate any help given!
Not sure what I am doing wrong. have never come across this before!
I just completely reset my phone to stock via MiFlash
I then boot into TWRP recovery from Fastboot
I then install the TWRP installer in TWRP
I then reboot to recovery but get 'The System has been Destroyed'
I can still boot into the stock ROM
I can still boot into Fastboot
I just can't seem to get TWRP to install, I can only access it in hotboot
Any help would be amazing!
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Oh well damn, I will give that a shot thank you!
Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Never install twrp on stock pie. You'll get the same message. Hotboot it only.
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
From what I have tried it seems that it is a bug with stock pie, custom roms with pie and stock oreo don't have this problem.
Anyway, you can basically get the same functionality by hotbooting but it's less convenient.
I have TWRP installed and resurrection remix. Maybe their TWRP works for you, just check the instructions and give it a try.
I think you should install TWRP in both slot A and B for it to work.
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Weird, it used to work for me when I was on stock pie.
I'm on a custom rom right now so I cannot test if it still works.
Sorry
I also have the same problem but now I'm on a custom rom and the TWRP without magisk works, but I would like to try an sGSI, on a custom rom does the procedure work?
Try another twrp
I'm here also had the same problem on mi A2 lite
But Rom run smooth and stable for a long time that I even forgot I have no twrp. Instead I backed up with titanium bk just in case. So ,Hotbooted with adb.... less convinient but u get to where u wanna flash though
I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.
Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.
Well i was just flasing my new boot.img that was patched with magdisk dowloaded the correct version 11.0.4.4 - EU IN11BA -IN2023 package from oficial one plus sites after the flash evering worked kinda ok the device rebooted like 3 times it was already rooted before so magdisk was loading all modules i guess everything loaded ok after third reset i ve gone ahed tested it for some time then something happend i was all of sudden unable to launch any apps and the ones that launched crashed withni 10s well i said to myself i ve seen this before on my huawei p9 and what i did there to fix this was clearing dalvik cashe then reset (huawei was running RR from open kirin and android 8) on huawei the main cause for this was messing with the cahe with lucky patcher well it even has a clear dalvik cache funuction so i launched the app on one plus and cleared the dalvik cache and after restart i got into boot looping with no ending (well after that i went to internet to read that dalvik cache is not even a think) so i tried to flash back the stock boot well that didnt fix so if somebody could point me to how to restore the device with keeping the data it would be appreciated i tried some restores like flashing some system partitons and overall trying to flash stuff from this guide https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/ with the updated version 11.0.4.4 of the ota package well nothing really happed half of the partitions are renamed and i dindt find the names for them anywere so i gave up to find help here.
So yea just a simple reboot to fix the device isnt enough for me i always have to "fix" something diferently.
well i ve let the device boot loop for some time and well i got at least some error
Boot Reason : fs_mgr_mount_all
unable to parse kernel log. for more debug information.
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
So i maybeee destroyed the partitions i guess. (well my thinking is that the LP didnt find the partiton so it tried to format something that was similar to it maybe acros multiple partitons and did kinda nasty wipe.)
First try to boot into the device via safe mode.
If that works just reboot again then all your magisk modules will be disabled.. You absolutely should disable them all before you update/root.
I have a thread for this in the guides section.
If however the safe mode didn't work then you could boot (not flash) a patched boot.img, if it boots then you can go ahead and disable the magisk modules and then go to install and install directly within magisk to make root permanent.
Only if the above works should you attempt to turn any modules back on and only if they're rated to work on 4.4
I would recommend running the remove magisk modules adb command which can also be found in my guide, if the above doesn't work, instructions for running it in the thread.
If none of this works you could maybe go down the route of flashing partitions but personally I'd just MSM and bite the bullet.
Good luck
dladz said:
First try to boot into the device via safe mode.
If that works just reboot again then all your magisk modules will be disabled.. You absolutely should disable them all before you update/root.
I have a thread for this in the guides section.
If however the safe mode didn't work then you could boot (not flash) a patched boot.img, if it boots then you can go ahead and disable the magisk modules and then go to install and install directly within magisk to make root permanent.
Only if the above works should you attempt to turn any modules back on and only if they're rated to work on 4.4
I would recommend running the remove magisk modules adb command which can also be found in my guide, if the above doesn't work, instructions for running it in the thread.
If none of this works you could maybe go down the route of flashing partitions but personally I'd just MSM and bite the bullet.
Good luck
Click to expand...
Click to collapse
Well i would like to try booting it into safe mode but the pohone after i ve letted it to boot loop for like 10 mins desnt event try to boot again i changed nothing so i guess something got modified in the phone to prevent bootloops when i power it on it just reboots into recovery and it would be really nice if you could give me links to those guides i just cant find them thanks