How to Get Stock MIUI OTA Update for Devices With Unlocked Bootloader
Requirements - -- You should be running stock (duhhh)
Instructions - -- Flash Magisk Uninstaller (If Rooted) -- Flash Stock Recovery from Custom Recovery (You should find this in your Stock ROM zip) -- Reboot Device -- Extract boot.img file from recovery rom zip. (Recovery rom's version should be same as the version of the rom you using before doing OTA) -- Now flash that boot.img file from pc using fastboot -- Go to bootloader and connect your device -- Now, flash that boot.img using this command
"fastboot flash boot boot.img"
-- Reboot device. -- Update using Updater app
Notes -- This Does NOT work on Ported MIUI ROMs like MIUI ROG, MIUI Hellas etc. This only Works on Stock! -- The boot.img and recovery.img given below is for Gram (Poco M2 Pro). Though guide remains same for all devices! DO NOT FLASH THE BOOT IMAGE AND RECOVERY IN ANY OTHER DEVICE. WE ARE NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER!
How to Get Stock MIUI OTA Update for Devices With Unlocked Bootloader
Requirements - -- You should be running stock (duhhh)
Instructions - -- Flash Magisk Uninstaller (If Rooted) -- Flash Stock Recovery from Custom Recovery (You should find this in your Stock ROM zip) -- Reboot Device -- Extract boot.img file from recovery rom zip. (Recovery rom's version should be same as the version of the rom you using before doing OTA) -- Now flash that boot.img file from pc using fastboot -- Go to bootloader and connect your device -- Now, flash that boot.img using this command
"fastboot flash boot boot.img"
-- Reboot device. -- Update using Updater app
Notes -- This Does NOT work on Ported MIUI ROMs like MIUI ROG, MIUI Hellas etc. This only Works on Stock! -- The boot.img and recovery.img given below is for Gram (Poco M2 Pro). Though guide remains same for all devices! DO NOT FLASH THE BOOT IMAGE AND RECOVERY IN ANY OTHER DEVICE. WE ARE NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER!
"For Telegram, accountability has always been a problem, which is why it was so popular even before the full-scale war with far-right extremists and terrorists from all over the world," she told AFP from her safe house outside the Ukrainian capital. The next bit isn’t clear, but Durov reportedly claimed that his resignation, dated March 21st, was an April Fools’ prank. TechCrunch implies that it was a matter of principle, but it’s hard to be clear on the wheres, whos and whys. Similarly, on April 17th, the Moscow Times quoted Durov as saying that he quit the company after being pressured to reveal account details about Ukrainians protesting the then-president Viktor Yanukovych. The account, "War on Fakes," was created on February 24, the same day Russian President Vladimir Putin announced a "special military operation" and troops began invading Ukraine. The page is rife with disinformation, according to The Atlantic Council's Digital Forensic Research Lab, which studies digital extremism and published a report examining the channel. The company maintains that it cannot act against individual or group chats, which are “private amongst their participants,” but it will respond to requests in relation to sticker sets, channels and bots which are publicly available. During the invasion of Ukraine, Pavel Durov has wrestled with this issue a lot more prominently than he has before. Channels like Donbass Insider and Bellum Acta, as reported by Foreign Policy, started pumping out pro-Russian propaganda as the invasion began. So much so that the Ukrainian National Security and Defense Council issued a statement labeling which accounts are Russian-backed. Ukrainian officials, in potential violation of the Geneva Convention, have shared imagery of dead and captured Russian soldiers on the platform. "The result is on this photo: fiery 'greetings' to the invaders," the Security Service of Ukraine wrote alongside a photo showing several military vehicles among plumes of black smoke.
from jp
