I have the XT1550 variant on stock 6.0.1 ROM and Fire Kernel, rooted and xposed is installed and I have changed the boot animation. It's been months since I have rooted, xposed was installed 2 weeks ago and Fire Kernel a week ago (able to reboot before flashing kernel). Today there was an update to an xposed module I had installed so I rebooted to enable it, but now the phone won't boot up. The Moto logo shows but then the screen turns off and the phone doesn't boot up. I tried restoring the stock kernel(didn't work), then tried factory resetting through TWRP (didn't work). What should I do? Should I reflash the stock firmware? When I tried to, the command "fastboot flash partition gpt.bin" returned the error - "cannot load gpt.bin". So, I didnt flash the firmware and directly skipped to the step - "fastboot oem fb_mode_clear" and now am trying to restore to an older backup from TWRP. Is this the right way? Please help!
Thanks in advance!
Tron_Legacy1680 said:
I have the XT1550 variant on stock 6.0.1 ROM and Fire Kernel, rooted and xposed is installed and I have changed the boot animation. It's been months since I have rooted, xposed was installed 2 weeks ago and Fire Kernel a week ago (able to reboot before flashing kernel). Today there was an update to an xposed module I had installed so I rebooted to enable it, but now the phone won't boot up. The Moto logo shows but then the screen turns off and the phone doesn't boot up. I tried restoring the stock kernel(didn't work), then tried factory resetting through TWRP (didn't work). What should I do? Should I reflash the stock firmware? When I tried to, the command "fastboot flash partition gpt.bin" returned the error - "cannot load gpt.bin". So, I didnt flash the firmware and directly skipped to the step - "fastboot oem fb_mode_clear" and now am trying to restore to an older backup from TWRP. Is this the right way? Please help!
Thanks in advance!
Click to expand...
Click to collapse
Your flashing error is in regard to fastboot.exe not being able to find gpt.bin, it has nothing to do with the phone...
Restoring a working TWRP backup is the correct solution. If you want to go back to stock, that is a different thing entirely and should only be a last resort.
[RANT]This is why I am absolutely opposed to Xposed, and even rooting, on modern stock devices... either leave it pure stock or flash a custom ROM, quit trying to f*ck with stock because it often ends badly. Xposed is nothing but problems, always has been and always will be, even if they figure out how to make it work in Nougat and later (which is questionable at best) it is one of the most dangerous things you can to do your device especially if you don't how to handles things like what happened to you, because they will happen. Rooting breaks OTAs and several features... If you want root, or to change your battery indicator, or whatever you use to customize your installation, use a custom ROM without Xposed (it NEVER belongs on a custom ROM). If you absolutely insist on rooting stock and using Xposed, backup, backup, and backup again, at every step in the process, and keep a backup off the device to and know how to get it back to working condition, because it will break, maybe not today or tomorrow, but someday.[/RANT]
And BTW, this is NOT pointed directly at the OP, it is more general than that, so I mean no offense. I also have the utmost respect for the developers and the work they do on these projects, it is a huge undertaking and they have made great strides for the Android community.
OK, I tried to restore an earlier backup from twrp but when it tried to restore the data partition there was an error, probably because when I tried to flash stock firmware, you have to factory reset from stock recovery, which probably deleted the data partition. So, I still tried to boot it and it booted up and I had to set up the device again. But not there are other problems, one of them being, apps can't write to SD card. For example ES File Explorer has a dialogue where you have to select the root of the SD card to allow writing to it. When I select it, the task that is running is stuck. And a lot of play services problems. Should I try and reboot to see if those are fixed?
BTW thank you a lot for replying and helping me!
Probably you've messed it up. Maybe another factory reset from settings would help.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Probably you've messed it up. Maybe another factory reset from settings would help.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I can try that. I was thinking that instead of flashing stock firmware again, could I just flash CM 7.1 as I was going to do it anyway. Will that cause any problems?
Thanks!
Tron_Legacy1680 said:
I can try that. I was thinking that instead of flashing stock firmware again, could I just flash CM 7.1 as I was going to do it anyway. Will that cause any problems?
Thanks!
Click to expand...
Click to collapse
It shouldn't be any problem. You can go ahead and install any custom rom [emoji106]
Broadcasted from Zeta Reticuli
Gravemind2015 said:
It shouldn't be any problem. You can go ahead and install any custom rom [emoji106]
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I'm going to do that then! Thanks a lot for helping!
Related
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?
samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?
Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode
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