Well i have followed multiple tutorials, and idk what im doing wrong, but everytime i go to boot the patched boot image the phone just bootloops. I have tried different versions of magisk stable, beta, canary, but to no avail. I think i need some help, sorry
Thank you
I had to full wipe to stop that from happening. Then the whole Android flash-all, followed by Patched Boot (with latest Magisk) seemed to work fine. Dunno really what caused it. May be left over user data? This thread may help if there is something from a Magisk Module causing the bootloop. I didn't try it during my install attempts but it may be worth a shot?
Exokan said:
I had to full wipe to stop that from happening. Then the whole Android flash-all, followed by Patched Boot (with latest Magisk) seemed to work fine. Dunno really what caused it. May be left over user data? This thread may help if there is something from a Magisk Module causing the bootloop. I didn't try it during my install attempts but it may be worth a shot?
Click to expand...
Click to collapse
would a adb backup up cause any harm? And about how long did it take you to reflash the phone?
Flash the Magisk patched boot to both slots either with a --slot all command or by flashing to one manually changing slots and flashing to the other all before final system boot.
Dallas2346 said:
would a adb backup up cause any harm? And about how long did it take you to reflash the phone?
Click to expand...
Click to collapse
Sorry, missed this (and hopefully you've already resolved the issue). I don't think doing a back up would cause any harm, although to be fair, I've never used adb backup. I don't think it'll help on a restore though. Reflashing took all of 15 minutes... signing in and getting all my apps up and running again was a little tedious as Titanium wasn't restoring some app data correctly (or the apps themselves didn't 'take'). Overall, not the worst.
Related
Made a nandroid of:
- Boot / System Image / Vendor Image / Data / Modem
I attempt to restore this backup in TWRP and it does not error out. However, upon rebooting, the phone just goes into an immediate bootloop showing OnePlus logo and then unlocking warning. Attempted to change slots which didn't work. Not sure why this is failing.
Suggestions on how to successful restore?
azsl1326 said:
Made a nandroid of:
- Boot / System Image / Vendor Image / Data / Modem
I attempt to restore this backup in TWRP and it does not error out. However, upon rebooting, the phone just goes into an immediate bootloop showing OnePlus logo and then unlocking warning. Attempted to change slots which didn't work. Not sure why this is failing.
Suggestions on how to successful restore?
Click to expand...
Click to collapse
Reflash magisk. I think that's how I solved my issue.
mikex8593 said:
Reflash magisk. I think that's how I solved my issue.
Click to expand...
Click to collapse
Thanks!
That seems to have worked. I could have sworn that I tried flashing Magisk, but apparently not. Although, it seems that I lost TWRP somehow in the process. I have been flashing for over 10 years and I have never experienced anything like this phone in regards to flashing. I never know what's going to happen when I flash something on it. It's frustrating.
azsl1326 said:
Thanks!
That seems to have worked. I could have sworn that I tried flashing Magisk, but apparently not. Although, it seems that I lost TWRP somehow in the process. I have been flashing for over 10 years and I have never experienced anything like this phone in regards to flashing. I never know what's going to happen when I flash something on it. It's frustrating.
Click to expand...
Click to collapse
I think restoring boot is what wiped twrp. Yeah, this A/B stuff is challenging.
azsl1326 said:
Thanks!
That seems to have worked. I could have sworn that I tried flashing Magisk, but apparently not. Although, it seems that I lost TWRP somehow in the process. I have been flashing for over 10 years and I have never experienced anything like this phone in regards to flashing. I never know what's going to happen when I flash something on it. It's frustrating.
Click to expand...
Click to collapse
Flashing has not as easily as it used to be, it all started for me on the OP5T, that was such a pain. Don't see things getting any easier though, I don't even flash custom ROMs outside OOS anymore
Bradl79 said:
Flashing has not as easily as it used to be, it all started for me on the OP5T, that was such a pain. Don't see things getting any easier though, I don't even flash custom ROMs outside OOS anymore
Click to expand...
Click to collapse
So what do you select when backing up?
Data
System
Boot
?
Ive been selecting Data, System, Boot, EFS - but havent restored so dont know if it works
I heard someone say that you need to select system image or you may get the "255" error but i could be wrong.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ive been selecting Data, System, Boot, EFS - but havent restored so dont know if it works
I heard someone say that you need to select system image or you may get the "255" error but i could be wrong.
Hello everyone,
I don't know much about partitions but I know something is not right with mine
So, A few days ago my phone got bricked because I flashed crDroid rom. (I did something wrong)
So, after a lot of research, I found an solution to unbrick my phone. So it worked, I booted into software again and I was free to use.
So later, I decided to install an custom rom again (Havoc OS). I installed the rom but after I clean flashed the rom, I got stuck on booting logo.
So, I thought lets see what partition B does. So I booted into partition B and I got stuck on the logo of TWRP. Not sure why.
I really wanna know why this happend and how to fix my device.
(Btw, now my phone is working again and I am on stock os with rooted using Magisk 16,7.)
But just wanna know what I did wrong
I used the instruction in this thread: https://forum.xda-developers.com/oneplus-6/development/enchilada-romcrdroid-t3827070. And after I did that it got bricked.
I hope anyone knows what happend and how to fix my partition!
Friendly regards,
Crewz
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
whizeguy said:
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
Click to expand...
Click to collapse
I did the exact steps as in the thread.
ItsCrewz said:
I did the exact steps as in the thread.
Click to expand...
Click to collapse
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
iElvis said:
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
Click to expand...
Click to collapse
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
ItsCrewz said:
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
Click to expand...
Click to collapse
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
iElvis said:
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
Click to expand...
Click to collapse
Yes I know what it means. But it isn't normal that it boots into twrp and get stuck on the logo
sooooo, potentially this is my fault, but, I forgot to uninstall magisk before updating to 10.3.3.0 and now the device won't boot, just bootloops. I have since uninstalled magisk in twrp, and re-flashed the rom, but am still getting a bootloop.
I feel like a complete wipe and re-flash of everything, including the kernel might fix this, or is it a potential problem with miui 10.3.3.0?
I can connect to the phone via ADB while its booting and /data is mounted, so it seems like the system is trying to boot correctly, but something is failing.
going to try flashing 10.3.2.0 to see if it works then, otherwise, not sure what t try.
ok, well that didn't work, 10.3.3.0 has downgrade protection, so now im just booting into recovery every time
guess i'll try a full flash
I don't have a ton of experience with this but what did you use to flash the update? Did you use the OTA zip from Xiaomi or a version found online? I just updated mine from 10.2.2.0 global to 10.3.2.0 global (which I got from GetDroidTips) without removing Magisk first with no issues. I read in this post that the Vendor image can get corrupted, maybe that's what happened not sure if that helps at all. You might have the right idea with just doing a complete reinstall of stock though, I know it sucks to lose data.
As mentioned above, my guess would be something got corrupted. I would use Mi Flash and reflash the fastboot image for 10.3.3.0.
Couldn't find a fastboot ROM for 10.3.3.0, but luckily had a copy of 10.2.1.0 which I flashed via miflash, had to wipe data to get it to boot though, which irritated me. Something must have got corrupted at some point, oh well, all sorted now (sort of), just need to re-flash twrp
Fastboot ROM for 10.3.30
http://bigota.d.miui.com/V10.3.3.0....XM_20190817.0000.00_9.0_global_0b55a6dd91.tgz
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it
Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes
MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.
Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?
I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?
Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.
Woke up this am to an OOS update and remembered that there's a process to go through to not lose root and magisk, so I look up the thread and follow the simple directions.
Allow the OTA but do not reboot.
Go into Magisk and install again to internal
Stay in Magisk and install to inactive slot
Reboot
I did exactly that and upon reboot, my phone booted to my lockscreen pic and just flashes every second. Even in safe mode it bootloops at a flashing lockscreen.
I followed exactly what I was supposed to do, so is there a step missing? Or was I not supposed to take the OOS update that was being pushed today?
I can access TWRP still, and I do have a full backup available if I need it, but I'd much rather figure out how to move forward.
Thanks for any help you can give me!
OnePlus 7 Pro
stock ROM
TWRP & rooted
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
FlipmodeBG said:
Yup same problem here. I uninstalled magisk from twrp and it booted fine. Will try with older magisk soon but I need the phone up and running today.
Click to expand...
Click to collapse
What exactly did you do to uninstall magisk from TWRP? I don't know how to do this...
Did you go into TWRP file manager and just delete /data/adb/magisk folder?
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
FlipmodeBG said:
Just flash the magisk uninstaller zip
https://github.com/topjohnwu/magisk_files/blob/canary/magisk-uninstaller.zip
Edit:
Did a fresh magisk canary install, now it boots fine. Was probably a module issue, which is weird because I always disable all modules when performing OTA.
Click to expand...
Click to collapse
Thanks for that, didn't work for me though. I keep bootlooping at insecure bootloader warning.
I have messed something up pretty bad, after the last reboot, I'm met with the Qualcomm CrashDump mode -- dmverity device corrupted force dump
kernel_restart
Now I'm stuck, because I've tried to recover my backup, it goes through the process at just over 1000 seconds, has no errors or failures but still won't boot.
I need some help here.
Nevermind, I have to have this phone back up and running ASAP, so I used MSM Tool and started over. I figured spending a few hours setting it back up from scratch was the best way forward at this point.
I'm unclear on what caused this problem... maybe I had a magisk module that didn't disable, or maybe I forgot to disable a substratum layer or something, but I really borked myself all because of an OTA update.
Any further advice on what I might have done or what might have corrected it will still be appreciated because I'm sure there will be another OTA someday and I'd really like to avoid this happening again.
Thanks!
What I do when there is a new Ota is
download the update from the updater app
remove any passwords or finger prints
reboot to twrp
install the Ota
do no reboot
install twrp installer
do no reboot
install magisk
wipe dalvick
reboot
check if Magisk is installed and if not reboot back into twrp and install Magisk again
Hi. Magisk 20.4 not working my device. Has anyone managed to get it working?