can i use c.33 patched boot img to root c.36 ? or i need to downgrade to c.33 ?
MevishL said:
can i use c.33 patched boot img to root c.36 ? or i need to downgrade to c.33 ?
Click to expand...
Click to collapse
Why can't you use patched boot img of c.36?
TheNewHEROBRINE said:
Why can't you use patched boot img of c.36?
Click to expand...
Click to collapse
because i used oxygen updater app and it shows only full rom of c.33 . i extracted boot.img from it. i can't find c.36 boot.img
MevishL said:
because i used oxygen updater app and it shows only full rom of c.33 . i extracted boot.img from it. i can't find c.36 boot.img
Click to expand...
Click to collapse
Do you have TWRP installed?
TheNewHEROBRINE said:
Do you have TWRP installed?
Click to expand...
Click to collapse
nope , still waiting for unlock token to unlock bootloader. how to root using twrp?
MevishL said:
nope , still waiting for unlock token to unlock bootloader. how to root using twrp?
Click to expand...
Click to collapse
If you make a backup of the boot partition, TWRP will create a file called boot.emmc.win that is nothing different than a boot.img file. You can then pass it to Magisk to patch it.
TheNewHEROBRINE said:
If you make a backup of the boot partition, TWRP will create a file called boot.emmc.win that is nothing different than a boot.img file. You can then pass it to Magisk to patch it.
Click to expand...
Click to collapse
ok thnk u so much , will try it
TheNewHEROBRINE said:
If you make a backup of the boot partition, TWRP will create a file called boot.emmc.win that is nothing different than a boot.img file. You can then pass it to Magisk to patch it.
Click to expand...
Click to collapse
what if my device get bricked , can i unbrick it by flashing c.33 full rom in msm?
MevishL said:
because i used oxygen updater app and it shows only full rom of c.33 . i extracted boot.img from it. i can't find c.36 boot.img
Click to expand...
Click to collapse
[KB2003] Stock & Magisk patched boot.img (latest KB2003_11.C.33)
Hello everyone! Welcome to the thread I was hoping to see every time OnePlus would release a new update... Eventually I decided to do it myself! In the link below you can download stock & Magisk patched boot.img files of given OOS versions for...
forum.xda-developers.com
MevishL said:
can i use c.33 patched boot img to root c.36 ? or i need to downgrade to c.33 ?
Click to expand...
Click to collapse
This worked for me but just boot it without flashing by using "fastboot boot boot.img", that way if it fails your boot partition is still in tact. Once booted you can use Magisk direct install to patch your c.36 boot.
Related
FRD-L09C432 pre-root booted (superuser-r310)
1. Unlock booloader
2. Flash boot.img via fastboot
3. Install phh.superuser https://play.google.com/store/apps/details?id=me.phh.superuser
B381 Boot.img http://www.datafilehost.com/d/3204ea04
B389 Boot.img http://www.datafilehost.com/d/079e483c
B392SP01 Boot.img http://www.datafilehost.com/d/874fb9b1
Ps: i will keep update rooted boot when a new version is released, but only for L09C432.
So if I want to flash that, I have to be already on B381?
There's no need for this, as we can already root B381 through recovery using SuperSU or PHH. Also, when you flash an SU zip you can also flash the unSU zip to recover from bootloops where as flashing a boot.img has no fallback
NeophyteGS2 said:
There's no need for this, as we can already root B381 through recovery using SuperSU or PHH. Also, when you flash an SU zip you can also flash the unSU zip to recover from bootloops where as flashing a boot.img has no fallback
Click to expand...
Click to collapse
unsu zip? where's that file? is for supersu unroot?
deadko said:
unsu zip? where's that file? is for supersu unroot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=63615067
oberfeldwedler said:
So if I want to flash that, I have to be already on B381?
Click to expand...
Click to collapse
Yes.
NeophyteGS2 said:
There's no need for this, as we can already root B381 through recovery using SuperSU or PHH. Also, when you flash an SU zip you can also flash the unSU zip to recover from bootloops where as flashing a boot.img has no fallback
Click to expand...
Click to collapse
It's aimed to users that like to stay with stock recovery.
You can easy resore stock boot image via flashboot.
Hi!
Perfecto
Thank you very much.
For what is this? (Para qué sirve esto?)
TheDave86 said:
For what is this? (Para qué sirve esto?)
Click to expand...
Click to collapse
Root.
B389 rooted Boot.img added to first post
B392SP01 rooted Boot.img added to first post.
Thanks bro .
Thanks a lot. But how can i change my AL10C000 to L09C432?
n_polo said:
Thanks a lot. But how can i change my AL10C000 to L09C432?
Click to expand...
Click to collapse
? Have to rebrand.
venugopalu007 said:
? Have to rebrand.
Click to expand...
Click to collapse
Yes，use some apps. Then , I can flash L09C432B360 and update to B392 of eu.
Can you add b399 version?
After testing Several Twrp recoveries & root zips attempts. Finaly I have rooted my phone.
Now i am going to tell you guys.
How i did that.
first of all download Magisk Manager App Version: v5.3.0 from Below link
HTML:
http://tiny.cc/latestmanager
Now copy stock boot img of your honor 8 lite into honor 8 lite memory. internal or sdcard up to you.
open Magisk app select install then it will ask Download Zip Only & Patch boot image.
select Patch boot image. it will explore your files. select stock boot.img. which you copied earlier. Now Magisk will download Magisk latest zip from its server & patch your provided boot.img.
Now restart your phone into fastboot mode Flash Patch boot image. you are done.
i am using twrp-3.1.1-2-v1-prague recovery.
This method requires to unlock the phone bootloader first?
andr01d3 said:
This method requires to unlock the phone bootloader first?
Click to expand...
Click to collapse
Yeah bro
liboct87 said:
Finaly I have rooted my phone.
Click to expand...
Click to collapse
Did you take a backup of your original boot image? Can you upload somewhere?
jusma said:
Did you take a backup of your original boot image? Can you upload somewhere?
Click to expand...
Click to collapse
i had got the boot img frm below firmware...
https://forum.xda-developers.com/8-lite/development/stock-rom-pra-la1c185b165-emui-5-0-t3740504
Can anyone upload a Magisk patched boot image for 10.0.1GM57AA? The model that I have is GM1900. When I try to patch it myself on Magisk, I get an error saying "process error"
Anyone able to help?
Heelixx said:
Anyone able to help?
Click to expand...
Click to collapse
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
meltbanana said:
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
Click to expand...
Click to collapse
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Heelixx said:
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Click to expand...
Click to collapse
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
meltbanana said:
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
Click to expand...
Click to collapse
I flashed the 4.14.117-perf+.img that you uploaded and then I booted in TWRP and flashed my original stock boot image. While still in TWRP, I flashed the zip of Magisk and then I rebooted. That got it working. So I'm rooted now. Thanks for sending me the image. I appreciate it!
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
lvints said:
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
Click to expand...
Click to collapse
I was rooted on 10.0 and then I upgraded to 10.0.1
There is a procedure for upgrading to 10.0.1 and still keeping root. I wasn't aware of this and after I got the update, I restarted my device and ended up without root access.
A Magisk patched boot image is important for getting your device rooted.
If you're asking for the procedure to root your device, then you can follow this link which explains it, https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
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
hello , i want to restore stock recovery.img , and i have orangefox recovery. i dont want to downgrade . and may i use recovery.img of f.13?
MevishL said:
hello , i want to restore stock recovery.img , and i have orangefox recovery. i dont want to downgrade . and may i use recovery.img of f.13?
Click to expand...
Click to collapse
Extract if from firmware and flash to recovery partition.
Rootk1t said:
Extract if from firmware and flash to recovery partition.
Click to expand...
Click to collapse
f.15 is an incremental update.
f.13 is a full update , can i use recovery.img from f.13?
MevishL said:
f.15 is an incremental update.
f.13 is a full update , can i use recovery.img from f.13?
Click to expand...
Click to collapse
Link is to F.15 full ^
Its for KB2003, but recovery images should be identical between KB2001/2003/2005.
Rootk1t said:
Link is to F.15 full ^
Its for KB2003, but recovery images should be identical between KB2001/2003/2005.
Click to expand...
Click to collapse
okay thank you