Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links):
EU NE2213_11_A.12
Stock boot.img - link
EU NE2213_11_A.10
Stock boot.img - link
Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come.
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.
Related
I'd like to do a clean re-install of the OS before moving everything over to the phone ... but I don't see any downloads for the 3T on the OP downloads page?
http://downloads.oneplus.net/
zim2dive said:
I'd like to do a clean re-install of the OS before moving everything over to the phone ... but I don't see any downloads for the 3T on the OP downloads page?
http://downloads.oneplus.net/
Click to expand...
Click to collapse
Not that I know of. Im bricked until they release them
Atlantian said:
Not that I know of. Im bricked until they release them
Click to expand...
Click to collapse
Dare I ask what went wrong?
I was going to unlock the bootloader (since it would require a full wipe if I waited and did it later), but otherwise stop there (I don't think changing recovery or rooting result in any need to wipe)
There is a full OTA zip in the 2nd post of the TWRP thread. This may solved your problem. But I do suggest you read the whole thread, as there maybe info that regard to your bootloader issue. I noticed that some of the OP3T came with OOS 3.5.1, which have issue w/ custom recovery. So you have to upgrade to 3.5.3.
PS: there is this full backup available also.
someone0 said:
There is a full OTA zip in the 2nd post of the TWRP thread. This may solved your problem. But I do suggest you read the whole thread, as there maybe info that regard to your bootloader issue. I noticed that some of the OP3T came with OOS 3.5.1, which have issue w/ custom recovery. So you have to upgrade to 3.5.3.
PS: there is this full backup available also.
Click to expand...
Click to collapse
I don't have the phone yet ..just ordered it but I'm interested..... how to install the ota zip on stock recovery??...
Sorry for the#noob guestion # but I'm coming from lg and op3 is totally new for me....
cultofluna said:
I don't have the phone yet ..just ordered it but I'm interested..... how to install the ota zip on stock recovery??...
Sorry for the#noob guestion # but I'm coming from lg and op3 is totally new for me....
Click to expand...
Click to collapse
After mucking around with TWRP/Root, I decided I wanted to try the plain vanilla SafetyNet-compliant OxygenOS experience. In TWRP, I flashed the 3.5.3 OTA from here. I rebooted my phone into Fastboot and relocked the bootloader, then rebooted back into OxygenOS. I think relocking the bootloader and flashing the OTA are interchangeable.
Also, from what I recall, if you want to flash the file through the stock recovery, have the file downloaded to the root of your internal storage partition and name it ota.zip. Either download it while in the OS, or use Fastboot mode and use adb push to upload it from your computer to your phone through USB. Reboot into Recovery and there should be an option to update.
Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.
I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*
Hi folks,
What we used as beta ROM is now published as official stable release known as version RMX1991_11.C.12 for Chinese model of Realme X2.
Probably anyone can upgrade the phone now in any possible way.
The bad news is FP stops working as soon as you patch vbmeta for disabling AVB...
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
yakovpol said:
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
Click to expand...
Click to collapse
Then, you will not loose fingerprint?
AlAneed said:
Then, you will not loose fingerprint?
Click to expand...
Click to collapse
Exactly
yakovpol said:
Exactly
Click to expand...
Click to collapse
Magisk can be installed and we still have the fingerprint working?
AlAneed said:
Magisk can be installed and we still have the fingerprint working?
Click to expand...
Click to collapse
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
yakovpol said:
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
Click to expand...
Click to collapse
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
I will try to search for it. Is it just a normal app to install from Play store? or requires other method?
One more thing, TWRP working with it or no?
Thanks
---------- Post added 10th April 2020 at 12:36 AM ---------- Previous post was 9th April 2020 at 11:38 PM ----------
I guess I am not able to understand how to do root? I searched for system base root in the web with no luck
Would you mind explaining how to do root without Magisk?
osamanazim said:
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
Click to expand...
Click to collapse
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
yakovpol said:
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
Click to expand...
Click to collapse
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Mikelsteven said:
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Click to expand...
Click to collapse
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
yakovpol said:
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
Click to expand...
Click to collapse
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Put some labour on searching through Internet please. So you will be sure if to update or not
To me it works just fine.
Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Black Screen problems while playing COD Mobile. Iit is a common problem on sobre Android 10 upgraded devices.
But all the rest of software running and working smoothly.
can someone please confirm if the feature of Waze returning to top during voice call is working? i have the globalized version by mettis and it doesn't work there (have CN device)
I am on the china model M2102K1C with the global rom installed. I rooted using the following method https://forum.xda-developers.com/t/...irmware-download-needed.4301241/post-85282829 which meant not overwriting the recovery and only booting thru the twrp file in my adb folder. This made it possible to get OTAs.
I just got the update available for download message and before I install it I would like to be sure I can re root using the same method and that the twrp version still works on miui 13.
the reason i want to check first is that i remember using other phones that sometimes a major update had necessitated an update for twrp to work with it.
you can root on miui 13 by patching the boot.img , like on all android 12 releases. Due to non working twrp on a12.
So if you want a working TWRP you cant update.. After update to miui 13 it will be a12.
use this link for info: https://xiaomi.eu/community/threads/howto-magisk-install-without-twrp.64511/#post-643958
marcel112 said:
you can root on miui 13 by patching the boot.img , like on all android 12 releases. Due to non working twrp on a12.
So if you want a working TWRP you cant update.. After update to miui 13 it will be a12.
use this link for info: https://xiaomi.eu/community/threads/howto-magisk-install-without-twrp.64511/#post-643958
Click to expand...
Click to collapse
thanks I have rooted several other phones on A12. I might wait until I research a bit more on this one as its my first Xiaomi phone. I was hoping the TWRP made for android 11 would still work on A12. ...or if i can hold off wait until there is a twrp for this phone compatible with A12.
tensux said:
thanks I have rooted several other phones on A12. I might wait until I research a bit more on this one as its my first Xiaomi phone. I was hoping the TWRP made for android 11 would still work on A12. ...or if i can hold off wait until there is a twrp for this phone compatible with A12.
Click to expand...
Click to collapse
idk, i know there are working a12 twrp for mi 10 and 10 pro, but i dont know when and if it will come for 11 ultra. and when it will come... there are no twrp files for yet... if it is only for root, just use pathed boot.img.... its really easy
marcel112 said:
idk, i know there are working a12 twrp for mi 10 and 10 pro, but i dont know when and if it will come for 11 ultra. and when it will come... there are no twrp files for yet... if it is only for root, just use pathed boot.img.... its really easy
Click to expand...
Click to collapse
thanks I know I am going to end up trying it. with the other phones I was more familiar with fixing a soft brick, so that's why I am nervous about it. I already started the upgrade haha.
its nearly impossible to brick this device( i am told, lol)
You can allways reflash using miflash to stock, just be aware off untick lock
marcel112 said:
its nearly impossible to brick this device( i am told, lol)
You can allways reflash using miflash to stock, just be aware off untick lock
Click to expand...
Click to collapse
uggh looks like I am going to need to learn how to use miflash. im not sure what i did. I didnt flash anything but rebooted to system from fastboot, and now the screen is blank. My laptop recognizes enough to beep when i plug and unplug the usb cord, but adb does not see it.
read this https://forum.xda-developers.com/t/global-miui-13-link-added-awesome-update.4410931/post-86528887
adn this https://forum.xda-developers.com/t/new-to-mi-11-ultra-with-rom-problems.4411617/post-86527355
tensux said:
uggh looks like I am going to need to learn how to use miflash. im not sure what i did. I didnt flash anything but rebooted to system from fastboot, and now the screen is blank. My laptop recognizes enough to beep when i plug and unplug the usb cord, but adb does not see it.
Click to expand...
Click to collapse
For some reason it is losing sanity when you have an open BL and twrp etc installed and trying to update to miui13. Just make sure you have a backup.
I have never used MiFlash before. I believe my computer does see the phone. I was on miui_STARGlobal_V13.0.2.0.SKAMIXM_eecc15ab63_12.0. I am not finding a global fastboot rom for A12 (only the full rom).
The previous versions 12.58 does have a fastboot rom available. Using other phones it was not always possible to downgrade. Would it be possible to flash 12.5.8 on this, or will I need to flash the china version of A12 that has a fastboot rom available?
marcel112 said:
you can root on miui 13 by patching the boot.img , like on all android 12 releases. Due to non working twrp on a12.
So if you want a working TWRP you cant update.. After update to miui 13 it will be a12.
use this link for info: https://xiaomi.eu/community/threads/howto-magisk-install-without-twrp.64511/#post-643958
Click to expand...
Click to collapse
Problem is you can use watever boot img or the one from the specific fastboot rom? because I updated to global 13.0.2 and there is no fastboot version available yet and so no boot img
xNAPx said:
Problem is you can use watever boot img or the one from the specific fastboot rom? because I updated to global 13.0.2 and there is no fastboot version available yet and so no boot img
Click to expand...
Click to collapse
also stuck on this issue, do you know which boot image source we use now? i am also on 13,0,2 global and need root...
There is, take a look at the "beta" thread, it has all you need for A13 rooting
munky-head said:
There is, take a look at the "beta" thread, it has all you need for A13 rooting
Click to expand...
Click to collapse
thanks, but can you be a bit more specific, ive been rooting my every android but this is my first Xioami ever so i am new to this.... which beta thread - a beta firmware - higher version which i download and extract to get the boot.img?
thanks
Yes. Whatever version you have installed, you can find a suitable root image from the link:
xdroms
Download xdroms for free. None
sourceforge.net
Then, it's a matter of typing fastboot flash boot rooted_boot.img and fastboot boot rooted_boot.img (with rooted_boot being whatever image you're running).
I'm currently running the latest Global Stable version, so the root I flashed was [ROOT]miui_STARIDGlobal_V13.0.2.0.SKAIDXM_8e7ececfcf_12.0_by_XD
munky-head said:
Yes. Whatever version you have installed, you can find a suitable root image from the link:
xdroms
Download xdroms for free. None
sourceforge.net
Then, it's a matter of typing fastboot flash boot rooted_boot.img and fastboot boot rooted_boot.img (with rooted_boot being whatever image you're running).
I'm currently running the latest Global Stable version, so the root I flashed was [ROOT]miui_STARIDGlobal_V13.0.2.0.SKAIDXM_8e7ececfcf_12.0_by_XD
Click to expand...
Click to collapse
There is also [ROOT]miui_STARGlobal_V13.0.2.0.SKAMIXM_eecc15ab63_12.0_by_XD.7z
Which one is best for the latest Global stable 13.0.2.0? It also says [Root], what does it mean? It is already rooted? As far as I know with the fastboot method you need to patch the boot.img via magisk first and than flash it via adb
It's a pre-patched boot.img file
So we just need to flash it, but which one of the two?
tensux said:
thanks I have rooted several other phones on A12. I might wait until I research a bit more on this one as its my first Xiaomi phone. I was hoping the TWRP made for android 11 would still work on A12. ...or if i can hold off wait until there is a twrp for this phone compatible with A12.
Click to expand...
Click to collapse
I wait to for the TWRP and im happy for that, Miu 12.5.20 is rock stable... All i want for my phone
xNAPx said:
So we just need to flash it, but which one of the two?
Click to expand...
Click to collapse
you got it working?
Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
kawala8888 said:
Is there already a way to root on android 13 for redmi note 10 pro? Twrp? I can't find anything so far, maybe someone knows something?
Click to expand...
Click to collapse
Same as on Android 12. That was the one with the issue decrypting in custom recovery.
Can't you just fix boot.img with Magisk and then fastboot flash it?
hyperboarean said:
Can't you just fix boot.img with Magisk and then fastboot flash it?
Click to expand...
Click to collapse
Yep.
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Clawsman said:
so, i bought my new redmi note 10 pro yesterday.
its on android 12, miui 13. and it asks me to upgrade.
i havent upgraded yet, thinking maybe rooting it with twrp and all, would be difficult.
Should i keep the current version and root it. or am i ok to upgrade it and then rooting it?
seeing this thread, it seems like im ok with upgrading and rooting. but want to make sure.
Click to expand...
Click to collapse
Wait the days until you are unlocked, in case something borks during that procedure.
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Clawsman said:
thank you for replying.
well, i couldn't wait, considering the new update is lighter and better. so i just updated it and everything went smooth. What is the best way of rooting it? i mean, should i go with or without the twrp. any bugs with the twrp. or is there any better recovery to flash.
Click to expand...
Click to collapse
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
hyperboarean said:
I'd just fix boot.img with Magisk to root. TWRP is mostly just for flashing different roms, and our phones use 2 different touch screens, so your might not even work in TWRT.
Click to expand...
Click to collapse
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Clawsman said:
I have been using TWRP on every device i have rooted. i just love the TWRP recovery. because, as you said, it allows me to flash different kind of roms and it allows me to backup my current rom.
i am probably not going to flash any custom roms on this device, but i would like to have the opportunity to backup my current rom for flashing it later on if needed.
Will i be able to do this with the fixed boot.img and Magisk?
Click to expand...
Click to collapse
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
hyperboarean said:
Magisk is just for root and different modules (like viper4android). You need TWRP to backup rom, but as I said touch might not work for you, check the TWRP touch not working posts.
Click to expand...
Click to collapse
well, it seems "not worth it". until an official TWRP is released.
And if i decide flash boot.img/Magisk or TWRP, mtk will restore my device back to its locked/stocked state?