So the new november patch was rolled out and i decided to install it. I was kinda surprised it let me install it while my phone was already rooted in the first place, but as i thought the patch had gotten rid of the root. I tried to root the phone again using the Mi A2 Toolkit by Daha3ker
Link: https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
And now when it tries to reboot it gets stuck on the sliding colours right after the android one logo.
Any help would be much appreciated guys
thanks,
exoticpenguins
tool is outdated. Next time read the full guide. it says :Version 1.0.6 only tested September Update:
Matteo
Related
I made the mistake of installing TWRP and Magisk before updating, and all I get is the "update unsucessful" screen, so now I'm stuck with 7.1.1 on my Android One Moto X4.
I found a factory image of Oreo on firmware.center (can't link it here because new user, but the filename was PAYTON_FI_8.0.0_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) for my device, and would like to know if it's safe to use and how to install it (sites seem to give conflicting information). This thing is brand new, so I'm a bit nervous about messing it up.
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
sleeptab said:
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
Click to expand...
Click to collapse
One last thing, that guide mentions using mfastboot, where do I get it? Is it any different from the regular fastboot?
No it's just normal fastboot.
Flashed it, works great! Thank you! (However, Android File Host was having issues and it took multiple times before a successful download)
So wonder why I have never gotten a single update pretty much since I got this phone 6 months ago. When i got it the first thing i did was unlock the bootloader and rooted it.
So I saw there was a June update of this year. Well I decided to go and look at my phone and oh look! June 1 update! yea from 2017. So when I do an update I get a "Check for update was not available at this time. Try again later"
I don't have any of the update apps blocked with Titanium either. Any help and\or ideas would be great.
On my Turbo it would still get updates, but fail because of TWRP at least and i would flash stock recovery just to update then flash twrp back on.
Thanks
Magisk Manager v16
Rooted
Unlocked
Recovery - TWRP 3.2.1-r16
Build: NPS26.116-45
Stock ROM
Hello, i had Dec 5 OTA + Magisk rooted device.
i tried to update but it said failed. so i uninstalled magisk and restored to stock boot.img but still saying update failed.
someone said to relock bootloader. i tried to relock bootloader and my data got erased.
even after that i tried to update OTA and im still getting failed update.
i dont know what to do now. can anyone please help me.
i have the same problem
help us please
after doing a bit of searching i fixed it.
i simply flashed my device with Stock Rom 10.0.0.2 using Mi Flash Tool. (there are plenty of youtube tutorials).
after that my device installed the OTA updaet without any error.
after that i rooted my device with Magisk. [patched_boot is already been posted on this forum]
so far, haven't come across any problem. Just not satisfied with the volume update. i had a magisk module for low volume fix which worked better.
What's really needed is full images from Xiaomi, so we can start flashing them manually without worrying about OTAs
See how well the DAISY thread is being maintained https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
.
Another repost with the same issue.
Follow this and this
I have flashed the V10.0.13.0.PDLMIXM (and locked back oem) but I still have the google update problem... from June to September 2019 :/... any idea?
Hello, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.
I have a Pixel 5 and today I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version).
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW: I'm still using the canary channel, is this still necessary?
Help.
Was that an update from A11 to A12? If so you're gonna have to jump through some hoops...
Either way, this is very likely not a Magisk issue, but caused by some new verification stuff in Android 12, so the best place for you to find info/help is going to be in your device's forum.
Upgrade was from the October version, so, to the best of my knowledge, Android 12
Still, you're likely going to find the answer in the Pixel 5 forums...