I was on OOS12 C.11 and to upgrade to c.15 or c.17 it was failiing.
Searching the internet found that we first need to UNROOT to be able to upgrade.
In Magisk, I restored the images and the upgrade was successful to c.17
But now I lost the Root. Magisk asks for the boot.img to patch.
Should i share the c.11 boot.img or the c.17 boot.img ?
anyone ?
firoz3321 said:
anyone ?
Click to expand...
Click to collapse
You'll need to get a patched image of C17 (or maybe you mean C16). Next time if you do an incremental update, have magisk install itself on the inactive slot after the update finishes installing but before rebooting.
trinidude4 said:
Next time if you do an incremental update, have magisk install itself on the inactive slot after the update finishes installing but before rebooting.
Click to expand...
Click to collapse
I usually do this so never had issues before. but this time upgrade would fail always at 21% then in google i found people mentioning ROOTED Oneplus devices fail upgrade. and clearly after unroot the upgrade was successful but after you unroot the feature you mentioned wont be available.
And yes it was c.17 for India. now received c.20 yesterday. Will try the c.20 boot.img.
I tried extracting the boot.img but c20 doesnt have the boot.img i guess.
As per the instructions for payload dumper i placed the images in old folder from c.11 payload.
used the c.20 payload to extract.
i got 3 images : product.img | system.img | system_ext.img
after these3 images payload dumper had this error message and stopped
"Processing product partition.......Unsupported type = 9"
However when i tried with c.17 boot.img was available
i am now confused wheteher c.11 img or c.17 img to use for the rooting.
please help. I have never had this situation before.
Ok so i loaded the c.11 patched boot and magisk seem to be available. but WIFI is not turning ON. hmmm. weird issues with Android 12.
Well finally i am out of this OOS. installed Evolution X and so far looks good.
Related
I want to install the Magisk but not achieved yet because of TWRP is not available and the stock boot.img not found.
Now OTA is coming(1.02.709.7), so I tried to obtain boot.img from the OTA image by the following steps but didn't succeeded.
Download the OTA image by checking the system update on the device.
The image will be stored on /sdcard/Download/OTA_1.01.709.1-1.02.709.7.zip
Copy the OTA image to PC and extract the file "payload.bin".
Use the payload dumper(Thanks to vm03), dump the boot partition from payload.bin but failed with the following error.
Processing boot partition.Unsupported type = 9
* Type of 9 is IMGDIFF according to what I found (no further info).
* I modified "payload_dumper.py" to dump only the boot partition.
Could someone please share the stock boot.img or TWRP for this device?
or tell me another way to achieve this.
Thanks.
I'm looking for it, too. :crying:
Did you get the 1.03.709.1 version boot.img file?
I don't think OTAs contain the whole boot.img, only the binary diff of the new version.
so far nobody has found a boot.img ? the device is around for some months now...
Is there still nothing? Not even a boot.img?
I will post my stock boot.img, recovery.img, and SW version # once I get to my computer.
Should be able to extract it with ADB/commands.
I'm not able to get anything using ADB/fastboot and no root method is working for me. I wish I had an OTA file to work with so I could patch the boot.img and try that but OTAs have already been done on this phone.
The only thing I've managed to do is unlock the bootloader.
Here is a copy of the OTA zip I'm running on
https://drive.google.com/file/d/122ky9if8FqTKz0tvqVi_8-FkA-GjHX9A/view?usp=drivesdk
And here is the payload.bin from that OTA
payload.bin
drive.google.com
So far I haven't managed to get the boot.img and I have a long day tomorrow. Maybe you guys can come up with something?
Well I downloaded the automated script version of payload dumper located here:
How to extract payload.bin from OTA update or firmware
In a few rare cases, you may need to extract the payload.bin that is part of firmware and OTA update files from some OEMs to get the stock boot and system images. This helps when you are looking un…
nerdschalk.com
And that payload.bin seems to only contain abl.img. Nothing else which is unfortunate.
like i've written before, the OTA simply does not contain the whole boot.img - only the binary difference from the previous build.
with only the difference it is not possible to reconstruct a whole boot.img
the only options i see is wait for a RUU or the kernel source to be published
Another OTA came through 227MB, extracted and only thing in there is abl.img again.
is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img
Did you get the 1.00.468.1 version boot.img file?
I'll try to port twrp this week.
Just wait for the good news
4096abcd said:
I'll try to port twrp this week.
Just wait for the good news
Click to expand...
Click to collapse
please make one also for htc u20 5g if possibile
lostic-b said:
please make one also for htc u20 5g if possibile
Click to expand...
Click to collapse
Still there's no way to unlock the bootloader of U20
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
ViruuZ said:
So i accidentally updated my pixel firmware via official OTA update (security patch 5. january 2021). First i was scared of a bootloop but it all went fine and booted.
Of course my root is gone now, but i want to root it again. Bootloader is still unlocked. Does anyone know, if i can just flash the magist boot.img again and it will boot fine? Or is there a risk that maybe THIS will cause a bootloop?
Thanks!
Click to expand...
Click to collapse
You need to patch the new boot.img.
sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
Thanks for reply! So i extract my current boot.img, but how to patch it?
ViruuZ said:
Thanks for reply! So i extract my current boot.img, but how to patch it?
Click to expand...
Click to collapse
Open Magisk manager app
Select install magisk
Select and Patch a File
Copy new patched boot.img to pc
Flash
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Found my current firmware, will extract it there. Thanks anyway!
ViruuZ said:
well, was a bit hasty here. I knew i could patch it via magisk, but last time there already was a patched image given. How can i extract my boot.img without root now? Or is there maybe a given for the last update?
Click to expand...
Click to collapse
Normally you have to go to google firmware page and download it.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Are you guys having the SafetyNet passed?
sd_shadow said:
You need to patch the new boot.img.
Click to expand...
Click to collapse
No you don't. You only have to repatch the new boot image when a new major Android revision comes out. For example going from Android 11 to 12. I've updated my Pixel 5 every month a new update comes out. And I've always used the same boot.image file. No need to keep wasting your time patching that file. When you look through the OTA files you'll notice that none of those files in the zip file are a boot.image file. Meaning it doesn't touch it when it's doing the OTA.
xT29c said:
You only have to repatch the new boot image when a new major Android revision comes out.
Click to expand...
Click to collapse
That is kind of useful, thank you for sharing. Can someone confirm this?
@hanni2301 Have you succeeded in getting root back ? I got the same problem today....
Why do you ask me?
I always patch the actual boot.img out of the monthly factory image with magisk (beta or Canary) first and flash then the factory image, reboot, flash boot boot.img and afterwards the custom kernel.
@xT29c said that you can reuse ure patched boot.img from last month, as it changes only between different mayor Versions.
So you can save some time, but the process is still the same.
IMO, yes, you should always patch the new boot.img from each months new factory image in Magisk when re-rooting.
Do you need to? i suppose that's up to you. However I think you should want to.
Essentially, you're missing out on any code changes/fixes, etc that Google may have added to the new months kernel.
~ Maybe an idea for a new thread to upload the Pixel 5 stock boot.img from each months new OTA, along with a Magisk patched boot.img. ~
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
leveleyed said:
Same issue losing root. But when I try to open Magisk manager app, it says "upgrade to full Magisk Manager to finish the setup. Download and install?" I click "OK". But the next time I try to open it, it just keeps doing the same thing.
Click to expand...
Click to collapse
I am not sure, but this may be because Magisk Manager is no longer..
get v22
New v22.0 update merges Magisk and Magisk Manager app
Samsung's Galaxy S21 series is now supported too
www.androidpolice.com
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
SeeTurtle said:
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
Click to expand...
Click to collapse
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Click to expand...
Click to collapse
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
SeeTurtle said:
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
Click to expand...
Click to collapse
Did you also flash a custom kernel?
mattie_49 said:
Did you also flash a custom kernel?
Click to expand...
Click to collapse
Yes but I reflashed the stock kernel
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
This doesn't matter
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Unfortunately still getting the same error
I am in the same situation. I only had my OP 9 for a couple of weeks and I came from a OP 5 where rooting and flashing was much easier. It would be good to know what you did to get OOS updated.
So when you download the package, you can use Oxygen Updater to install it. Choose the root package and it will install with Magisk, you will lose Twrp recovery. But you can just flash that back afterwards. Worked like a charm for me
I don't have TWRP cause it's not compatible with Android 12. I've had to factory reset the last 3 updates because of this same issue. When I had TWRP I could update with oxygen update and keep root. Being android 12 I also don't have the option to manually update via the phones update system. I don't mind factory resetting again because I have swift backup. I'd just like to know how to avoid it. Like if I could just flash it with fastboot or something
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Z-Blade said:
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Click to expand...
Click to collapse
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
SeeTurtle said:
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
Click to expand...
Click to collapse
Sweet! I have downloaded the full OTA and extracted the boot.img so I can use Magisk to patch it to get root again. I still haven't gone through the process yet but thanks for letting us know this method works. Also thanks to @illusiveairforce for leading us to the Oxygen Updater app.
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Hi,
What else should I reflash to make sure all root traces are removed ?
abl.img
aop.img
bluetooth.img
boot.img
boot.on mobile.img
cpucp.img
devcfg.img
dsp.img
dtbo.img
engineering_cdt.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
oplusstanvbk.img
oplus_sec.img
product.img
qupfw.img
qweslicstore.img
shrm.img
splash.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img
vm-bootsys.img
xbl.img
xbl_config.img
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
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