Hey everyone, I messed up today trying to root with Magisk using a firmware zip with a different incremental version (but same OOS version) as my device. After flashing the patched boot.img my device is stuck in a bootloop. Unable to boot into system (the text "turn off" with a progress/loading bar shown on my wallpaper), fastboot is still available.
Firmware version before flashing: IN2013_11.C.36_1360_202210310935
Firmware version that the wrong boot.img was extracted from: IN2013_11.C.36_1360_202210171428 (from this thread, under "signed flashable zips>Europe")
Magisk version: 25.2
Recovery: stock
TWRP?: no
I would rather not have to go through the MSM route/fully restore to stock firmware as I am under the impression that these will wipe my data.
I'm now looking for anyone who has the full firmware zip for OOS 12 incremental version (IN2013_11.C.36_1360_202210310935) so that I can extract the stock boot.img file myself. I'm hoping that this manages to fix my mistake.
If anyone is currently running this version and also has TWRP it would also be great if you can follow this guide to extract your boot.img directly from your device.
Another option I am looking into is to flash a stock ROM (with a different build number but the same OOS version: IN2013_11.C.36_1360_202210171428) into my inactive slot without wiping data, I'm not sure if that's wise. Does anyone know if that will work?
update:
- tried booting into older versions of IN2013 firmware using fastboot boot boot.img to no avail.
- Based on the fact that I definitely did an OTA incremental update after upgrading to OOS 12 before, maybe the boot.img was tied to the incremental update zips instead. So, I tried extracting boot.img from incremental update zips (from here, importantly did not have C.36 incremental zips yet) using the FastbootEnhance payload dumping tool, but got the error "multiple dst in one operation" and was unable to continue with this idea.
possible solutions:
1. Flash a full stock firmware to partition A and boot to that. Will this wipe my data?
2. Wait for a full stock firmware zip of IN2013_11.C.36_1360_202210310935 and extract the boot.img myself to flash.
3. Wait for an incremental update zip for C.36 to be uploaded.
4. Somehow find and transfer the stock boot.img that Magisk supposedly makes a backup of when you patch boot.img with the app.
update 2: FIXED
Tried IN2015_11.C.36_1360_202210310935 from this thread for fun. Extracted the boot.img from this one and flashed it. It somehow worked even though it's for a different version????
Doubled checked Oxygen Updater and I am indeed running OTA version IN2013_11.C.36_1360_202210310935.
Related
This is only for devices currently on 4.4 or rooted 5.1 w/ moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Note 12/2/2015:
Development on this has been discontinued with the release of the SunShine bootloader unlock.
To use SunShine without having to deal with KingRoot, you can flash the Rooted v3 system img and then use SunShine to unlock. This is the most stable method if you can use mofo.
After unlocking using SunShine, please flash the latest bootloader/radio images from here. This will bring your phone completely up to date and provide a more stable experience with custom ROMs.
These images are still flashable after unlocking your bootloader if you'd like a stable, closest-to-stock ROM possible.
Instead of using mofo to flash the system image, you can just use
Code:
fastboot flash system filename-goes-here.img
You can then flash your own tweaks like Xposed.
I'd recommend making a back up of the stock ROM in TWRP so you have a stable base to go back to if anything goes wrong.
Note 10/10/2015:
Updated all images to the latest OTA update (SU4TL-44) and included the latest official Xposed version (v75) in extras v5.
Follow the instructions with 5.1_images_v4.zip to flash the updated firmware images.
Note 9/5/2015:
Updated extras (v4) to include the latest official Xposed version (v73). Read the previous note for more information.
Note 8/31/2015:
Updated extras to the latest official Xposed version (v72). Reflashing all of the images is not required, only the extras system.img using mofo.
You can download the full extras image (1.5gb), or if you already have the rooted v2 image, use the extras v3 patch (8mb) with the instructions below.
Using the rooted v2 image + patch will allow you to update in the future without redownloading the entire image (as long as you keep the original after patching).
Note 7/23/2015:
Updated to the latest OTA (23.11.39). Make sure to follow instructions and reflash all images from the latest zip.
Unfortunately, I couldn't provide a patch to go from rooted image v1->v2, so a redownload is needed.
When applying the latest extras, make sure you're applying it to the rooted image v2.
Files (updated 10/10/2015 w/ latest OTA & extras v5)
5.1 firmware images (v4)
SHA1: 8be8a19664e6ba5aa556838bb3f744cdbf41f2ef
Stock 5.1 system image (v3)
SHA1: 1e67fc22331f035e9f3bd6c28d81fb173dd86a3e
Rooted 5.1 system image (v3)
SHA1: b8ff04d7f6ad9de31292cf62da94a3d80d3e373c
Extras 5.1 system image (rooted v3 + extras v5) (see below for details)
SHA1: 126744919f86132c05d15e79373ea759f74e37cf
Instructions
A data wipe is not required, but please back up any important data beforehand in case something goes wrong.
After extracting 5.1_images_v4.zip, reboot into bootloader and run the following commands to prepare your phone for the latest 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem modem.img
fastboot flash mdm1m9kefs3 fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash recovery recovery.img
fastboot erase ddr
fastboot reboot-bootloader
Then use mofo to flash the system image of your choice and reboot.
After flashing a system image, the first boot will stay on the Motorola logo for an extra 30 seconds to 1 minute. This is rebuilding the cache partition (erased by moforoot after every flash).
If your phone doesn't boot after 5 minutes (and isn't showing the "Upgrading apps" dialog), try formatting the cache in recovery by doing the following:
While phone is off, hold the volume down button and turn it on to boot into bootloader. Use the volume keys to find the recovery option and press power to confirm.
Once you see the dead Android (it may also say "No Command", this is normal), pull up the recovery menu by holding power and pressing volume up (5.1 recovery is different than 4.4) and use the wipe cache option.
If the screen is blank in recovery with a periodically flashing Android icon, try booting the phone normally and trying again. This happened to me a few times, and I theorize it's because of the cache partition not being formatted after erased.
Extras (updated 10/10/2015 w/ latest OTA & Xposed official v75)
Download patch (v5)
SHA1: 451be2eef3df509facf16b807c6fc665c8fac090
If you don't want to deal with patching the image using xdelta3, you can download the full extras image in the Files section above.
This will prevent you from updating without redownloading the whole image in the future, but is easier for less experienced users.
Current extras:
Xposed official v75 (download APK from here)
(optional) ad blocking
busybox/sqlite3
tethering enabled
To apply the patch, use the rooted v3 image (not an already patched image) as a base, and follow the patching instructions (using xdelta3) in this post.
After patching the system.img with the extras, you'll use mofo to flash the patched image.
To use ad blocking, download AdAway (available in F-Droid) and enable it. Make sure the "Target hosts file" is set to "/data/hosts" in settings.
shouldnt we also be updating the radio?
diabl0w said:
shouldnt we also be updating the radio?
Click to expand...
Click to collapse
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
firstEncounter said:
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
Click to expand...
Click to collapse
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
edit: when i did the downgrade (4.4.4 to 4.4.2 radio) it disabled the ability to turn on wifi and log messages gave the error wifistatemachine: failed to load wifi driver
diabl0w said:
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
Click to expand...
Click to collapse
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
firstEncounter said:
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
Click to expand...
Click to collapse
check my edit
diabl0w said:
check my edit
Click to expand...
Click to collapse
Radios won't be compatible across ROM versions. You would flash the 4.4.4 radio if downgrading to a 4.4.4 image, not while running 5.1.
Ummmmm. Is this a dream? Someone pinch me...... There's no one around....... Can this really be true!? I'm afraid to try it and bork everything.
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot erase ddr
(Commands based on this post. Thanks @mikeoswego and @JulesJam!)
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Why aren't you flashing 5.1 recovery?
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
Missed that command in the OP. Thanks!
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
So we should do that command as well?
janitorjohnson said:
So we should do that command as well?
Click to expand...
Click to collapse
I had trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
JulesJam said:
I has trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
Click to expand...
Click to collapse
Is that the final command?
trikotret said:
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
No, it's completely stock with SuperSU installed.
janitorjohnson said:
Is that the final command?
Click to expand...
Click to collapse
I do
logo
boot
recovery
radios
But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.
---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------
firstEncounter said:
No, it's completely stock with SuperSU installed.
Click to expand...
Click to collapse
I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.
https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0
PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.
It should be easy for someone to modify the buildprop so you can have free tether.
works like a charm
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X
Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
firstEncounter said:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
Click to expand...
Click to collapse
Thank you! You are working mighty quickly I must say. We all really appreciate it!
I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.
After I let LP boot up, I could enter into recovery and factory reset without a problem.
Current Firmware: MHA-L09C346B136
I would like to apply the OTA firmware update but I can't since I had flashed TWRP and superuser a long time ago.
I've been googling around for the last 2 hours but I'm not still not sure what to do. The most relevant thread I found was: https://forum.xda-developers.com/mate-9/help/upgrade-firmware-due-to-twrp-root-t3591428
- "Flash original recovery.img from your firmware file via fastboot then upgrade your firmware via ota"
I've been searching around for my firmware but I can't seem to find it anywhere. Would any MHA-L09 firmware work?
And once I do find the firmware file, what other steps are there?
Do I need to extract recovery.img from the firmware using HuaweiUpdateExtractor or something like that?
Do I run the command fastboot flash recovery recovery.img after I find the recovery image?
triplemonitor said:
Current Firmware: MHA-L09C346B136
I would like to apply the OTA firmware update but I can't since I had flashed TWRP and superuser a long time ago.
I've been googling around for the last 2 hours but I'm not still not sure what to do. The most relevant thread I found was: https://forum.xda-developers.com/mate-9/help/upgrade-firmware-due-to-twrp-root-t3591428
- "Flash original recovery.img from your firmware file via fastboot then upgrade your firmware via ota"
I've been searching around for my firmware but I can't seem to find it anywhere. Would any MHA-L09 firmware work?
And once I do find the firmware file, what other steps are there?
Do I need to extract recovery.img from the firmware using HuaweiUpdateExtractor or something like that?
Do I run the command fastboot flash recovery recovery.img after I find the recovery image?
Click to expand...
Click to collapse
You could probably use L09C33B136 and extract recovery.img from that, then flash using fastboot as you said. Worst case you have to flash back TWRP if recovery doesn't work.
Do you know if you've modified /system, /product or /vendor? If you have you won't be able to install OTA, it will fail when checking if those partitions are modified.
If you want to update using full firmware you will have to rebrand.
ante0 said:
You could probably use L09C33B136 and extract recovery.img from that, then flash using fastboot as you said. Worst case you have to flash back TWRP if recovery doesn't work.
Click to expand...
Click to collapse
Thanks! I flashed the recovery.img file from that firmware as you suggested and now I have the latest firmware.
I noticed that the incremental firmware update that was already downloaded to my phone failed halfway though. Upon rebooting, I checked for updates again and this time round, it decided to download the full firmware instead which ended up being applied successfully.
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Sturdy_99 said:
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Click to expand...
Click to collapse
Hi. I am in the same position. Can I get a link to the boot.img file that you used?
The link is dead
Sturdy_99 said:
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Click to expand...
Click to collapse
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Heelixx said:
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Click to expand...
Click to collapse
Did u extract the boot.img from stable Open Beta release? Can you provide the links to oos12 ota and boot.img?
Sturdy_99 said:
Did u extract the boot.img from stable Open Beta release? Can you provide the links to oos12 ota and boot.img?
Click to expand...
Click to collapse
This is where you can find the links to the OOS12 OTA, https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-stable/
For some reason, I thought I uploaded the boot.img file in my previous reply but it seems not. Here's the link to download the one I extracted, https://gofile.io/d/BoqcM0
Heelixx said:
This is where you can find the links to the OOS12 OTA, https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-stable/
For some reason, I thought I uploaded the boot.img file in my previous reply but it seems not. Here's the link to download the one I extracted, https://gofile.io/d/BoqcM0
Click to expand...
Click to collapse
Great thats open beta, looks like many have been impacted with this. Thanks for the boot .img
Where you on stable release or open beta before upgrading?
Sturdy_99 said:
Great thats open beta, looks like many have been impacted with this. Thanks for the boot .img
Where you on stable release or open beta before upgrading?
Click to expand...
Click to collapse
I was on stable release before upgrading.
Strange that it's open beta when the headline says Stable OxygenOS 12. Oneplus is confusing people
Heelixx said:
I was on stable release before upgrading.
Strange that it's open beta when the headline says Stable OxygenOS 12. Oneplus is confusing people
Click to expand...
Click to collapse
Great, Thanks, ill give it a try.
Heelixx said:
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Click to expand...
Click to collapse
Does that mean, it would boot fine, if you do not install magisk before rebooting? In that case, you reinstall majgisk?
mzahs said:
Does that mean, it would boot fine, if you do not install magisk before rebooting? In that case, you reinstall majgisk?
Click to expand...
Click to collapse
So it would boot fine if I don't install magisk before rebooting.
However, I did flash the update again recently and then flashed the magisk patched boot image but I got stuck in a bootloop again. I don't know if I'm doing something wrong. So I'm without root on my phone at the moment
So I see a lot of people using magisk patched boot images that are really old. It'd be better to patch the image yourself from magisk and use that. The problem might be that it's not that easy to extract it.
You can find most of the stuff from stock rom extracted by me here. The files were extracted from the Indian varient. Make sure to use the appropriate files for your stock rom. The index site does have other files like some old and unstable kernels so don't go flashing everything you see from the root directory. This just started as a personal archive. The domain is free, so idk how long it'll stay active either.
As always, use everything at your own risk.
Do Magisk versions newer than v24.3 work this way?
newt23 said:
Do Magisk versions newer than v24.3 work this way?
Click to expand...
Click to collapse
Yes, patching the boot image is the recommended way to install Magisk.
The official guide does ask to patch AP wholly for samsung devices, but patching the boot image itself is faster.
Official Guide
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
newt23 said:
I don't understand why I get bootloops if I update to v25.x from v24.3 from the Magisk app (using direct method). As I understand it, it also (re-)patches the boot image.
Click to expand...
Click to collapse
That's how I updated too. Try flashing the magisk zip directly.
Or, only update the magisk app, patch the boot image, rename it as boot.img, put it in a tar file, and then flash it to "AP" using Odin.
Hmm... this is funny. I patched the stock boot image and flashed it using Odin and still got bootloops. I took a full nandroid backup beforehand so I was able to get everything working by flashing TWRP again and restoring the previous boot image.
I get bootloops if I install v25.x from TWRP after installing a rom or update to v25.x from v24.3 directly or by patching the stock boot image. The only one that's left now is flashing v25.x zip from TWRP (while having a functioning system with v24.3) but something tells me it's going to end in bootloops too.
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
When I start the process by uninstalling Magisk before I download the update and then would re-install Magisk to the inactive slot to retain root I get the errror message "Stock image does not exist".
I'm imagining this is because I did not patch the stock image myself. After MSM-ing back to OOS11 and updating to OOS13 I rooted by flashing a F13 image that I found on these forums that was already patched.
What can I do? Thanks in advance
Click to expand...
Click to collapse
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
TheNewHEROBRINE said:
I never add problems updating my 8T while it was rooted. I never restored the stock image before installing the update, I would just install to inactive slot before rebooting when the update finished.
Anyway, if you want to be super safe you could extract the stock boot.img from the full update package of your current version and flash it (it would be the same as restoring the stock image with Magisk). Btw I suggest you never flash images patched by others to avoid this exact problem. You can still use images from others if you want, just boot them (fastboot boot boot.img) instead of flashing them and then do a direct install with Magisk.
Click to expand...
Click to collapse
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
kevinco1 said:
So if I booted the F13 image I previously used and then did a direct install, Magisk would then make that backup IMG file and then I can proceed with the update to F15?
Or can I not boot the F13 image and do a direct install if I've already flashed it?
Click to expand...
Click to collapse
I think that Magisk backups the currently flashed boot image, so if you just boot the stock image it would backup the patched image.
kevinco1 said:
Hey I am on KB2003.F13 and wanted to upgrade to F15.
Click to expand...
Click to collapse
Update straightforward to F.62