Is there a way to update to 4.2.2 using the stock .img from Google without USB? (Due to water damage) I would like to keep root too.
I was thinking to use Bluetooth to send boot.img, system.img, radio.img, bootloader.img and SuperSU.zip to /sdcard then use MobileOdin to flash them but unsure if it'll work.
Current state of Phone
Rooted stock 4.1.1 with latest TWRP recovery
Any ideas?
What's preventing you from downloading the new Rom via WiFi? Then flash in your recovery, or am I missing something here.. Are you trying to update to the latest 4.2.2 OTA? You can run ADB over your network, I personally would download the Latest CM10.1 and be done with it.
freakb18c1 said:
What's preventing you from downloading the new Rom via WiFi? Then flash in your recovery, or am I missing something here.. Are you trying to update to the latest 4.2.2 OTA? You can run ADB over your network, I personally would download the Latest CM10.1 and be done with it.
Click to expand...
Click to collapse
Sorry for not making it clear, yes I want stock 4.2.2 also need to update bootloader and radio, my new plan is this:
1) Download system.img boot.img JDQ39_radio_bootloader.zip (which I found Here) and SuperSU.zip
2) Using Mobile Odin Flash system.img and boot.img
3) Boot into recovery and flash JDQ39_radio_bootloader.zip and SuperSU.zip
4) Wipe
That should work right?
adamgibbo said:
Sorry for not making it clear, yes I want stock 4.2.2 also need to update bootloader and radio, my new plan is this:
1) Download system.img boot.img JDQ39_radio_bootloader.zip (which I found Here) and SuperSU.zip
2) Using Mobile Odin Flash system.img and boot.img
3) Boot into recovery and flash JDQ39_radio_bootloader.zip and SuperSU.zip
4) Wipe
That should work right?
Click to expand...
Click to collapse
It should, yes.
Hello!
There's a guide already on XDA that covers this matter but in a general way and for all devices. That guide was based on the general info you may find on the original installation guide by @topjohnwu. So, all credits go to him.
Anyway, since there ins't a TWRP Recovery for Mi A3 (yet) and since I believe that many of you don't know about this, Iv'e decided to share here the steps I've done in order to root Mi A3.
NOTE: Now that we already have a working TWRP available for Mi A3, to root it you can now simply follow THESE steps after unlocking the bootloader.The guide present on this thread, of course, works as well, so I'll leave it here for those of you who don't want to permanently install TWRP to your device.
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(after rebooting, boot the phone again into fastboot mode)
Code:
fastboot flashing unlock_critical
(for full unlock)
2 - Download Mi A3 stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your phone internal (or external) memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...we never know if we don't need to use it again in the future...you know, to restore the stock boot.img, aka revert to stock...)
If, for your current build, there isn't a stock boot.img released yet, you may get one yourselves. How? READ THIS.EU Build boot images:
---Android 9---For all of you currently on 10.3.7.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.8.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.9.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.11.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.12.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.14.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.15.0 (EU) build, you may download stock boot.img HERE.---Android 10---For all of you currently on 11.0.1.0 (EU) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.2.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.3.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.5.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.6.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.8.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.9.0 (EU) build, you may download stock boot.img HERE.---Android 11---
For all of you currently on 12.0.2.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 12.0.3.0 (EU) build, you may download stock boot.img HERE. (thanks to @lucoz )For all of you currently on 12.0.5.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 12.0.6.0 (EU) build, you may download stock boot.img HERE.
Global Build boot images:
---Android 9---For all of you currently on 10.3.8.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 10.3.14.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)---Android 10---For all of you currently on 11.0.7.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.11.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.14.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.15.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 11.0.22.0 (Global) build, you may download stock boot.img HERE.---Android 11---For all of you currently on 12.0.3.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.4.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.6.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.7.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.8.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.9.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.11.0 (Global) build, you may download stock boot.img HERE.
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Install (again)
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC
Store it on the same folder where you have adb and fastboot
If you can’t find it via MTP, you can pull the file with ADB
Code:
adb pull /sdcard/Download/magisk_patched.img
6 - Uninstall Magisk Manager App from your phone (I'm not sure if this is really needed but I've done it anyway...)
7 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot erase boot
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot continue
(THIS IS IMPORTANT! USE CONTINUE INSTEAD OF REBOOT! You have been warned!!!)
8 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
9 - Enjoy!
All credits goes to topjohnwu and it's incredible work with Magisk.
I cannot be responsible if you turn your phone into a brick. Your phone, your choices, your responsibility!
Thanks!
Been waiting for someone to create a cannonical guide of how to root this phone.
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Also one would assume it disables the OTA update feature, probably better write it.
sirzarmo said:
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Click to expand...
Click to collapse
WiFi problems appears when you flash boot not from your ROM build. Use only the same boot.img to the build number of ROM.
sirzarmo said:
Also one would assume it disables the OTA update feature, probably better write it.
Click to expand...
Click to collapse
It is. But you can still update via Magisk if you don`t touch system partitions. Else - flash manualy.
Wow,
Thank's a lot!
As you said, I didn't know this way to root a device.
sirzarmo said:
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Click to expand...
Click to collapse
That someone was me. But, I believe that happened because I've used boot.img from 10.3.4.0 branch on GitHub (instead of using boot.img from 10.3.5.0 branch) and, also, I've used "fastboot reboot" command instead of "fastboot continue". As soon as the 10.3.5.0 branch appeared online I've decided to test this method again and it worked, that's why I've decided to share this with all community.
sirzarmo said:
Also one would assume it disables the OTA update feature, probably better write it.
Click to expand...
Click to collapse
I don't think it will disable OTA feature. Probably, as soon as a new OTA comes out it will be installed on Slot A (because up until now there's only been one update and it was installed on slot B...so everyone should now be on firmware V10.3.5.0 running on Slot B). So, if I'm not mistaken, the "worst" thing that could happen is to lose root (since the update will be installed on Slot A and boot.img on that Slot is still the stock one).
Cheers!
Typhus_ said:
Cheers!
Click to expand...
Click to collapse
Why thank you dear, I'll root now if so.
Hello!
Well, in fact, this method breaks OTA. It downloads but it doesn't install.
My guess is we need to flash stock boot.img and then apply the OTA update and then patch the new boot.img again.
I've noticed a new boot.img on GitHub today, hopefully it will be the correct one.
Typhus_ said:
Hello!
Well, in fact, this method breaks OTA. It downloads but it doesn't install.
Click to expand...
Click to collapse
You can simply follow this guide, if you do not touch system partitions.
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#devices-with-ab-partitions
Tried it already. It ain't possible because of 2 reasons:
1 - The supposly boot.img backup doesn't exist. Probably Magisk only does it if installed through TWRP and not by patching boot.img
2 - The OTA package fails to install. "A problem has occurred"...while trying to initiate the install.
Enviado do meu Mi A3 através do Tapatalk
When do you think twrp will be released for mi a3?
okay so I installed FDE magisk module now my phone is stuck at the bootscreen. Someone got a stock rom for me ?
You can change slot through fastboot. It will erase all user data (factory reset) but it's better than the phone not booting.
The other possible solution, I've sent you a PM (because external link).
fastboot --set-active=a (or b if you're now on a)
Enviado do meu Mi A3 através do Tapatalk
An offcial stock rom wouldve fixed my problem in no time. I changed the partition and got to a menu where I could chosse to factory reset but its been sitting on formatting data for like half hour...
drozo8o8 said:
An offcial stock rom wouldve fixed my problem in no time. I changed the partition and got to a menu where I could chosse to factory reset but its been sitting on formatting data for like half hour...
Click to expand...
Click to collapse
It should be quite fast...guess you're out of luck for the time being my friend.
By the way, you've used fastboot reboot or fastboot continue after changing slot?
It should be fastboot reboot
Enviado do meu Mi A3 através do Tapatalk
all i need is a proper flash all.bat since oyu gave me the OTA update link with a payload.bin which I extracted with payload_dumper
Typhus_ said:
Tried it already. It ain't possible because of 2 reasons:
1 - The supposly boot.img backup doesn't exist. Probably Magisk only does it if installed through TWRP and not by patching boot.img
Click to expand...
Click to collapse
Manualy patch boot.img in MM and you'll get backup.
This method is useful in Mi CC 9e. Thx
hello, install v10.3.5.0 over v10.3.7.0, now I don't have wifi and the sound does not work, instructions to fix it please ?, I am using the google translator to write here, thanks
You'll have to change slot and boot on that slot. You'll lose all your user data but the phone will boot ok and receive latest OTA. Either that or you have to wait for someone to dump you a stock 10.3.7.0 boot.img in order to fix those issues. On GitHub there isn't a boot.img for latest build yet.
Enviado do meu Mi A3 através do Tapatalk
Typhus_ said:
You'll have to change slot and boot on that slot. You'll lose all your user data but the phone will boot ok and receive latest OTA. Either that or you have to wait for someone to dump you a stock 10.3.7.0 boot.img in order to fix those issues. On GitHub there isn't a boot.img for latest build yet.
Enviado do meu Mi A3 através do Tapatalk
Click to expand...
Click to collapse
Fixed, THANKS YOU very much
Hey all! I'm trying to root my OnePlus 7t but I'm on 10.0.5 stock and I can't find a patched boot.img, or even a stock one to patch in Magisk. I'm on the global variant. If someone could point me in the right direction, that would be grand. I have already read mostly all the posts...
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
I just booted with an older one and flashed the latest magisk
Need 10.0.5 boot.img stock & magisk patched for indian varient
Hey .... Can you help me with the 10.0.5 boot.img , stock & magisk patched for indian varient HD1901 of 7t
ChongoDroid said:
I just booted with an older one and flashed the latest magisk
Click to expand...
Click to collapse
I had tried booting with 10.0.3 while on 10.0.5 , Did not turn out well .
Has anyone on 10.0.5 tried booting w/ the above 10.0.5 patched img ?
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
Click to expand...
Click to collapse
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
hightech316 said:
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
Click to expand...
Click to collapse
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images. You should only need to fastboot boot magisk_patched.img, then open Magisk Manager and install Magisk by choosing the direct install option in the list. You only need the steps I mentioned to have root, and if you flash it to A and B at once you can get stuck in a bootloop. I had that happen at one point from flashing both partitions, and I dont recommend trying it.
SkippRunning said:
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images.
Click to expand...
Click to collapse
Thanks , this can save a headache !
hightech316 said:
Thanks , this can save a headache !
Click to expand...
Click to collapse
Ya, I tried every relevant boot image I could find in the forums, and the device didnt work properly with any of them. The only one that allowed the device to boot successfully caused the wifi and sounds to not work. So I downloaded the full update from OnePlus and extracted it to a folder, then used payload dumper to extract all of the individual images out of the payload.bin file from OnePlus. I copied the boot.img into the phone storage and installed Magisk Manager, then patched the stock boot.img and copied it from the phone to my pc. Then I used fastboot boot magisk_patched.img to make sure the image I made would work. I booted the device and inside Magisk Manager I chose direct install in the list of options and everything went smoothly, and I didnt need to rely on finding images online that would hopefully work.
smokeythebear3 said:
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
Click to expand...
Click to collapse
Thanks a bunch for the share. That was the missing piece that I've been looking for. I have the HD1905 variant and I just used Magisk to patch the stock file you provided. After testing, I'm finally rooted. Thanks again.
I want to root my OnePlus 7T and my Phone is on OxygenOS version 10.0.12.HD65BA, so i need to download the OxygenOS 10.0.12.HD65BA zip-file anywhere, to root my phone.
Normaly i can find the newest version online on www.oneplus.com/de/support/softwareupgrade but there is just the previous version 10.0.11.HD65BA.
So can i download the right file anywhere else or do someone know how long i have to wait, until oneplus uploads the newest version to their website?
Thank you.
Use twrp to grab your existing boot.img then root it with magisk, flash with fastboot.
ba47 said:
I want to root my OnePlus 7T and my Phone is on OxygenOS version 10.0.12.HD65BA, so i need to download the OxygenOS 10.0.12.HD65BA zip-file anywhere, to root my phone.
Normaly i can find the newest version online on www.oneplus.com/de/support/softwareupgrade but there is just the previous version 10.0.11.HD65BA.
So can i download the right file anywhere else or do someone know how long i have to wait, until oneplus uploads the newest version to their website?
Thank you.
Click to expand...
Click to collapse
Check this thread. https://forum.xda-developers.com/oneplus-7t/how-to/oneplus-7t-repo-oxygen-os-builds-t3997037
Downloading it now.
This is the updater version though not the one with the broken out image files. I'll play with TWRP later. My partitions are encrypted and I haven't figured out how to unlock them from TWRP yet. Still new to TWRP on 1+.
[edit]
Screw the TWRP thing. I like easy. I went to this post https://forum.xda-developers.com/apps/magisk/extracting-boot-img-stock-firmware-t3909612 , downloaded the payload extract tool, extracted the payload.bin file inside the OTA. Now I have all the IMG files. Copy boot.img to my device, run Magisk and patch the boot image. Copy it back to my PC, reboot to bootloader, fastboot boot the patched flash to make sure all is well, if all works then flash the boot.img to the device, restart and done. I said easy right? It wasn't bad.
Hello,
About a week ago I updated to MIUI 13 (13.0.2.0.SJEMIXM). My phone (Redmi Note 9T) was rooted and I had a custom recovery (Orange Fox) installed. I flashed the stock recovery and was then able to update. I left the stock recovery on the phone to make it easier to update down the line but did root my phone again.
This morning I was informed that there is a new update (13.0.3.0.SJEMIXM) so I download and installed it. All went well and the phone booted successfully.
I then wanted to have my phone rooted again (magisk) so I just took the boot.img from the previous version (13.0.2.0.SJEMIXM) to be patched since I did not have the factory Rom for the new version (13.0.3.0.SJEMIXM) to retrieve the boot.img file.
I then flashed the patched boot.img via fastboot (fastboot flash boot magisk_pached.img) and my phone started to bootloop.
I also tried flashing the unpatched boot.img but it is still the old one.
I don't know if I did something wrong or if it is just the old boot.img that I need to replace, pls help.
Ps: I have downloaded the OTA update (13.0.3.0.SJEMIXM) but it only contains a boot.img.p file.
Rubz_Mod said:
Hello,
About a week ago I updated to MIUI 13 (13.0.2.0.SJEMIXM). My phone (Redmi Note 9T) was rooted and I had a custom recovery (Orange Fox) installed. I flashed the stock recovery and was then able to update. I left the stock recovery on the phone to make it easier to update down the line but did root my phone again.
This morning I was informed that there is a new update (13.0.3.0.SJEMIXM) so I download and installed it. All went well and the phone booted successfully.
I then wanted to have my phone rooted again (magisk) so I just took the boot.img from the previous version (13.0.2.0.SJEMIXM) to be patched since I did not have the factory Rom for the new version (13.0.3.0.SJEMIXM) to retrieve the boot.img file.
I then flashed the patched boot.img via fastboot (fastboot flash boot magisk_pached.img) and my phone started to bootloop.
I also tried flashing the unpatched boot.img but it is still the old one.
I don't know if I did something wrong or if it is just the old boot.img that I need to replace, pls help.
Ps: I have downloaded the OTA update (13.0.3.0.SJEMIXM) but it only contains a boot.img.p file.
Click to expand...
Click to collapse
Flash the (13.0.3.0.SJEMIXM)boot.img with O.F .
Use Magisk app for rooting the phone.
I fixed the problem.
All I had to do was find new the boot.img and flash it via fastboot.
I then patched the new boot.img file and then I flashed the patched.img via fastboot.
Thanks for your help