Patched boot 10.0.12.0
Did you enable camera 2api and install Gcam after installing patch boot 10.0.5? If yes, can you please share the entire process?
S Advance User said:
Did you enable camera 2api and install Gcam after installing patch boot 10.0.5? If yes, can you please share the entire process?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766/page1
I accidentally updated my phone, and it gave me a bootloop, so i flashed the patched img and it worked, but now my wi-fi doesn't work, did you have any problem with this?
ThaiDai said:
Stock boot image extracted from payload.bin of OTA 10.0.5.0.
Patched boot was generated with Magisk.
Flashed it with fastboot and the Mi A2 was rooted again.
Click to expand...
Click to collapse
Patched boot from 10.07?
Sent from my Mi A2 using Tapatalk
alenaki123 said:
Patched boot from 10.07?
Click to expand...
Click to collapse
HERE (search rules)
Once more, as "enveloped" link is not seen by @e2vinay ...
https://forum.xda-developers.com/showpost.php?p=79215031&postcount=102
Hi
My Mi A2 has got latest OTA and version is v10.0.7.0.PDIMIXM
can you please provide original and patched boot
Thanks in advance
e2vinay said:
Hi
My Mi A2 has got latest OTA and version is v10.0.7.0.PDIMIXM
can you please provide original and patched boot
Thanks in advance
Click to expand...
Click to collapse
Its link up
Sent from my Mi A2 using Tapatalk
The Patch Boot Link is not working Can You Please Update it
S Advance User said:
Did you enable camera 2api and install Gcam after installing patch boot 10.0.5? If yes, can you please share the entire process?
Click to expand...
Click to collapse
I enabled camera2api yesterday by temporary root access using 10.7.0 patched boot
weppull said:
The Patch Boot Link is not working Can You Please Update it
Click to expand...
Click to collapse
Just now (to test on your request) successfully downloaded Patched boot.img 10.0.5.0 from the thread OP and Patched boot.img 10.0.7.0 from the link given 4 posts above yours
Aerobatic said:
Just now (to test on your request) successfully downloaded Patched boot.img 10.0.5.0 from the thread OP and Patched boot.img 10.0.7.0 from the link given 4 posts above yours
Click to expand...
Click to collapse
Link is working fine But
I've Used Patched Boot.img 10.0.2.0 and my Build No is 10.0.7 and My phone is Stuck on Android one Logo Any solution for this.....?
weppull said:
I've Used Patched Boot.img 10.0.2.0 and my Build No is 10.0.7 and My phone is Stuck on Android one Logo Any solution for this.....?
Click to expand...
Click to collapse
Please be more accurate in describing your problem next time (Quote: "The Patch Boot Link is not working").
And what stops you from using 1st original 10.0.7.0 boot?:
1. in bootloader mode in CMD window with admin rights after checking that phone is responsive ["fastboot devices"}. - boot into stock kernel ["fastboot boot boot.img"].
If phone boots OK, than you can:
- flash stock kernel (but you will need to know whcih A/B slot is active, see guides here),
- and/or check if patched boot is working as well:
2. in bootloader mode in CMD window with admin rights after checking that phone is responsive ["fastboot devices"}. - boot into patched kernel ["fastboot boot patched_boot.img"].
If phone boots OK, than you can get Magisk root , etc. See guides in this forum.
Update 10.0.8.0
Updated to 10.0.8.0.
stock and patched boot image in first post.
Fastboot rom
https://drive.google.com/file/d/1YkfN3bNxMSlxB4FAaLGKHSRYDGrCjeti/view
ThaiDai said:
Stock boot image extracted from 10.0.8.0
Patched boot was generated with Magisk.
Flashed it with fastboot and the Mi A2 was rooted again.
Click to expand...
Click to collapse
Could you please re-upload the patched boot img for V10.0.8.0.PDIMIXM. The files are not there right now...
jeevanthespark said:
Could you please re-upload the patched boot img for V10.0.8.0.PDIMIXM. The files are not there right now...
Click to expand...
Click to collapse
both links is working correctly
try another browser,vpn,or user agent
ThaiDai said:
Updated to 10.0.8.0.
stock and patched boot image in first post.
Click to expand...
Click to collapse
Can I use this for V10.0.8.0.PDIMIXM? I could see there are different versions like V10.0.8.0.PDLMIXM on the internet... Which model is this patched boot img?
---------- Post added at 02:48 PM ---------- Previous post was at 01:53 PM ----------
daitalos said:
both links is working correctly
try another browser,vpn,or user agent
Click to expand...
Click to collapse
Downloaded using VPN. Thanks
stock boot missing
ThaiDai said:
Stock boot image extracted from 10.0.8.0
Patched boot was generated with Magisk.
Flashed it with fastboot and the Mi A2 was rooted again.
Click to expand...
Click to collapse
Hi, tried downloading the stock boot and the error 410 Gone popped up.
If you could sort the link out or generate another link, it would be really appreciated.
Also, with the stock boot image provided, I can root my device without bricking provided that I follow all the correct steps yes?
Thanks in advance
mi a1
plz provide, mi a1 april pached boot.img
Related
hi there it's been a loooong time search on the internet and ... no answers to my problems so yeah hello !
I have a Zenfone 2 laser ZE500KL and a custom recovery (twrp 2.8.7.7) and my phone have no OS installed (i don't know why) i tried many times to install the asus marshmallow update from fastboot, adb push, adb sideload, but nothing work and i have a little word saying "This package is for WW_phone devices; this is a omni_Z00E" followed by "Updater process ended with ERROR: 7" and "Error installing zip finle '/sdcard/UL-ASUS_Z00E-WW-13.10.7.2-user.zip'" i don't know what this mean and i want to know because i am a little lost.
thanks
alex
edit of 19/06/2016
YAY finally it finished after days of "no my phone wil never work again" it's finally over with a big YAY
so thanks to @sziraqui for his help and @tanker456 for the last help he gives me before i give up you two guys are the best !
so for more info and help i give you these two guys that are awesome !
contents box
http://forum.xda-developers.com/zenfone-2-laser/help/unable-update-to-marshmallow-via-ota-t3389876
Sziraqui
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
Tanker456
try this firmware called backtostock here
http://forum.xda-developers.com/zenf...flash-t3365237
it will work for sure. but if it dosen't
you can go with this one too
http://forum.xda-developers.com/zenf...550kl-t3236264
Alex07060 there is boot image of 1.13 firmware, u can try that
LuK1447 post that saved my life too
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
Click to expand...
Click to collapse
Hi have the same problame i have searched and you can flash http://androiding.how/install-ota-update-twrp-zenfone-2/ try this method please and say if it work or no
Alex070609 said:
hi there it's been a loooong time search on the internet and ... no answers to my problems
"This package is for WW_phone devices; this is a omni_Z00E" followed by "Updater process ended with ERROR: 7" and "Error installing zip finle '/sdcard/UL-ASUS_Z00E-WW-13.10.7.2-user."
Click to expand...
Click to collapse
If you had spent enough time searching on xda, you would have got the solution. I posted a solution to this here http://forum.xda-developers.com/zenfone-2-laser/help/unable-update-to-marshmallow-via-ota-t3389876 And the thread is marked "solved" which means it worked.
sziraqui said:
Apparently, your current recovery version does not match with your current firmware version. There are two possible workarounds-
1. Wipe system by executing "fastboot erase system" in fastboot mode. Then reflash latest official asus lollipop ROM. This will fix the recovery and firmware mismatch and you will then be able to flash MM via stock recovery.
2. If you are experienced with edit8ng updater-script, Extract all contents of MM ota. Open updater-script and remove all asserts and lines that say "abort". Then compress the contents again. (You can't edit without extracting coz zip is signed). Flash this modified ota zip via TWRP.
If you still can't flash it or you are unable to edit updater-script, pm me, I have downloaded the MM ROM, I will send you modified updater-script.
I can even convert this ota into .imgs so that you can flash directly via fastboot
Click to expand...
Click to collapse
Click on the small "play" icon in below quote and you will be redirected to the original post where I uploaded updater-script. This also answers @ericpeacock79 's question on flashing stock rom on twrp.
sziraqui said:
alright, download the updater-script from attachment. Flash via TWRP.
Detailed instructions-
First extract entire ota zip. Delete the original updater-script.
Then extract "updater-script_modified.zip"
Copy the extracted "updater-script" to extracted ota at the right location. (META-INF/com/google/android)
Compress the ota files as a zip using 7zip or winrar. Compression level "normal" . DONT USE ANY ANDROID APP FOR COMPRESSING, USE WINDOWS/LINUX APP ONLY.
Flash the modified zip via TWRP recovery
Click to expand...
Click to collapse
@sziraqui You are awesome. Thank you.
Click on the small "play" icon in below quote and you will be redirected to the original post where I uploaded updater-script. This also answers @ericpeacock79 's question on flashing stock rom on twrp.[/QUOTE]
Feels good when sum1 helps even if there is a repeated question. Most people will say "search before you post/ don't bump the forum/ etc. and provide links which are difficult for new users to follow. You are one of the few devs who are offer REAL help. Hatts off!
sziraqui said:
If you had spent enough time searching on xda, you would have got the solution. I posted a solution to this here http://forum.xda-developers.com/zenfone-2-laser/help/unable-update-to-marshmallow-via-ota-t3389876 And the thread is marked "solved" which means it worked.
Click on the small "play" icon in below quote and you will be redirected to the original post where I uploaded updater-script. This also answers @ericpeacock79 's question on flashing stock rom on twrp.
Click to expand...
Click to collapse
Hi i have the same problame problame and i have the stock firmware as a zip file do you can help me
@sziraqui Yes it works the installation is done BUT i got an new error "ERROR: Can't load invalid boot image" i need a little bit more help and many thanks for the help give to me right now its fantastic
Alex
Alex070609 said:
@sziraqui Yes it works the installation is done BUT i got an new error "ERROR: Can't load invalid boot image" i need a little bit more help and many thanks for the help give to me right now its fantastic
Alex
Click to expand...
Click to collapse
Hey please if you can do it for me and upload the Rom modified because my computer is broken
Alex070609 said:
@sziraqui Yes it works the installation is done BUT i got an new error "ERROR: Can't load invalid boot image" i need a little bit more help and many thanks for the help give to me right now its fantastic
Alex
Click to expand...
Click to collapse
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
---------- Post added at 01:56 PM ---------- Previous post was at 01:56 PM ----------
sziraqui said:
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
Click to expand...
Click to collapse
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
i have actually a right bootloader (official) but each time i triying to flash a boot.img it says file corrupted so i don't know how to do it do you have a boot.img correct to do that ?
thanks in advance
alex
sziraqui said:
What are you trying to flash? Custom kernel? Stock boot.img?
Either the .img is corrupt/incompletely downloaded OR you have unlocked boot loader using unofficial method.
1. Download the boot.img and try again
2. If it still gives error, you do not have a proper bootloader unlock. Try flashing twrp that is confirmed working by you, to verify if bootloader is properly unlocked or not.
Click to expand...
Click to collapse
Hey please does this method work a full Rom
hu what ?
@sziraqui Okey news of the day i find a correct boot.img but i get a bootloop yeah ! so what can i do now ?
alex
The problem u must do is find stock recovery of firmware 6.0 then u can sideload stock rom 6.0 ^^
I use ze500kg same ur phone, maybe i can help you
Contact me facebook: [email protected]
mohamedelkholy said:
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
---------- Post added at 01:56 PM ---------- Previous post was at 01:56 PM ----------
My bootloader is unlocked unofficial and i need to flash the stock Rom using twrp
Click to expand...
Click to collapse
try this firmware called backtostock here
http://forum.xda-developers.com/zen...guide-how-to-revert-to-stock-reflash-t3365237
it will work for sure. but if it dosen't
you can go with this one too
http://forum.xda-developers.com/zenfone-2-laser/general/root-ze550kl-t3236264
Alex07060 there is boot image of 1.13 firmware, u can try that
well with your indications a get a bootloop something else could help ? @tanker456
Alex070609 said:
well with your indications a get a bootloop something else could help ? @tanker456
Click to expand...
Click to collapse
i didn't understand what said,
did u get a bootloop or
are say that u would get a bootloop
Sent from my ASUS_Z00LD using XDA-Developers mobile app
look i had a bootloop ~20 mins and retry with a second link post and voila ! i get a phone that work it's done
Alex070609 said:
look i had a bootloop ~20 mins and retry with a second link post and voila ! i get a phone that work it's done
Click to expand...
Click to collapse
hmm good to hear it
Sent from my ASUS_Z00LD using XDA-Developers mobile app
Hello all,
When still on Android 10 I had Magisk stable installed and working.
Now, after upgrade to Android 11 I cannot get it to work.
Here's what I did:
- first off, I have factory reset the phone (without erasing external storage) because of WiFi not working anymore on Android 10 (Omega kernel problem maybe?).
- update the phone to Android 11 in Settings, System, System updates (now I'm on Android 11 build IN2023_15_200930)
- install Magisk Manager from here
- download the firmware from here
- extract boot.img from firmware zip file
- copy boot image from pc to mobile
- patch boot image with Magisk manager
- copy magisk_patched.img from mobile to pc
- flash magisk_patched.img
Code:
❯ fastboot flash boot magisk_patched.img
Sending 'boot_a' (43464 KB) OKAY [ 1.824s]
Writing 'boot_a' OKAY [ 0.131s]
Finished. Total time: 1.966s
- reboot the device
Now, when I open Magisk Manager, it says Magisk Installed ' N/A' and I expect to be able to install Magisk using 'direct install'.
However this option 'direct install' is not shown, only Download Zip Only & Select and Patch a File.
What is missing here?
Any help is appreciated!
Edit: I got it working using canary build of magisk manager in stead of the stable build.
Got the same issue plus the phone sometimes turn into a bootloop.
saphirrot said:
Got the same issue plus the phone sometimes turn into a bootloop.
Click to expand...
Click to collapse
I got it working using canary build of magisk manager in stead of the stable build.
lvbaal said:
I got it working using canary build of magisk manager in stead of the stable build.
Click to expand...
Click to collapse
I tried both, same result
saphirrot said:
I tried both, same result
Click to expand...
Click to collapse
Flash to both slots. Not just one.
Fastboot flash boot_a "name of boot IMG"
Fastboot flash boot_b "name of boot IMG"
saphirrot said:
I tried both, same result
Click to expand...
Click to collapse
Maybe Wipe Cache in recovery? I did that anyway
Tried wiping Cache and flashing to both Slots.. still bootloop..
saphirrot said:
Tried wiping Cache and flashing to both Slots.. still bootloop..
Click to expand...
Click to collapse
Sorry for you man! Maybe this than?
Uploaded some logs, maybe someone can helpView attachment 2020-10-11_16.00.zip
@saphirrot
Quite possible it's the magisk patched image you're using, obtain another, best to extract it yourself.
dladz said:
Quite possible it's the magisk patched image you're using, obtain another, best to extract it yourself.
Click to expand...
Click to collapse
Patched my own boot.img, still the same issue... thats so Strange, because I havent modified anything after the o11 Update..
saphirrot said:
Patched my own boot.img, still the same issue... thats so Strange, because I havent modified anything after the o11 Update..
Click to expand...
Click to collapse
Don't flash twrp whatever you do it'll end up in crash mode, not suggesting you will but a chap I was helping did it and that's what happened. Forced him to use MSM tool.
Try another patched image, if you're on EU/UK then I have one in my thread in the guides section. Just don't do anything else. If needs be I can upload a stock boot.img if your get stuck in a boot loop, least then your can boot.
What version of magisk did you use to patch?
Also what was the commands you used to flash it in fastboot?
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
saphirrot said:
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
Click to expand...
Click to collapse
Dont flash your image just boot it first. And if it boots and you have root you can install magisk from manager permanently
Had to factory Reset the Phone, now root works fine
Same Problem
yeah same problem here... you can exit the bootloop by flashing the stock boot.img on it.
But still, neither canary or the standard does work for rooting.
saphirrot said:
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
Click to expand...
Click to collapse
Were you using lucky patcher?? Sounds a lot like you are.
dladz said:
We're you using lucky patcher?? Sounds a lot like you are.
Click to expand...
Click to collapse
So you're saying that lucky patcher is the problem?
MrZaga said:
So you're saying that lucky patcher is the problem?
Click to expand...
Click to collapse
Lol well that depends mate, are/ were you using it.
Lucky patcher breaks so much when it's used, bootlooping is one of those symptoms.
I intend to make a thread saying do not use it as you're the fifth person I've seen now with issues I've troubleshooted and the culprit was that stupid app.
dladz said:
Lol well that depends mate, are/ were you using it.
Lucky patcher breaks so much when it's used, bootlooping is one of those symptoms.
I intend to make a thread saying do not use it as you're the fifth person I've seen now with issues I've troubleshooted and the culprit was that stupid app.
Click to expand...
Click to collapse
As it sounds, uninstalling doesn't help then. But do you know why it bootloops only when using the patched img, and not when using the stock img?
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.
MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.
Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?
Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches
What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.
It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.
h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13 and F.15
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot" ~name of img~
Profit!
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Thank's
BobbyLynn said:
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot magisk_patched-25200_575Sf.img"
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Click to expand...
Click to collapse
what if there is ota update?
MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
BobbyLynn said:
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
Click to expand...
Click to collapse
okay thx , much appreciated
BobbyLynn said:
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
Click to expand...
Click to collapse
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
MevishL said:
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
Click to expand...
Click to collapse
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
BobbyLynn said:
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
Click to expand...
Click to collapse
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
MevishL said:
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
Click to expand...
Click to collapse
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
now u made it clear in my head , thx for all
MevishL said:
now u made it clear in my head , thx for all
Click to expand...
Click to collapse
No problem. If you run into any problems just let me know and I'll do what I can to figure out the simplest solution
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Can these instructions be used for the KB2007?
kevinco1 said:
Can these instructions be used for the KB2007?
Click to expand...
Click to collapse
If it's Android 13 11_F.13 then yes. But Orange Fox has a working recovery for A13 on our phone. So you can always flash Magisk that way if you want
MrOnizuka said:
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Click to expand...
Click to collapse
As long as I have this phone I'll continue to post the patched boot.img after each update
BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Marduc said:
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
Click to expand...
Click to collapse
Thanks for reminding me. I'll upload the new boot.img shortly
MevishL said:
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Click to expand...
Click to collapse
You did flash unmodified boot.img before trying to update? Well, honestly idk why it won't install. Maybe you should try a different method of installing the update, like manually installing it
OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]
Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks
LinhBT said:
OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]
Click to expand...
Click to collapse
Thank you so much man! May I ask how do you extract boot.img from incremental updates?
karib97 said:
Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks
Click to expand...
Click to collapse
Yes, if your bootloader is unlocked.
LinkinLover2013 said:
Thank you so much man! May I ask how do you extract boot.img from incremental updates?
Click to expand...
Click to collapse
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015
LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!
LinhBT said:
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015
Click to expand...
Click to collapse
Ye I have IN2015.
LinhBT said:
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!
Click to expand...
Click to collapse
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.
LinkinLover2013 said:
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.
Click to expand...
Click to collapse
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...
LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...
Click to expand...
Click to collapse
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?
LinhBT said:
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?
Click to expand...
Click to collapse
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that? Also do you have an app that works for updating with oxygen updater pls? I downloaded a zip but can´t find an working updater app that install zips...
LinkinLover2013 said:
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that?
Click to expand...
Click to collapse
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )
LinhBT said:
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )
Click to expand...
Click to collapse
Well. Where can I find Vbmeta.img for F15 pls?
LinkinLover2013 said:
Well. Where can I find Vbmeta.img for F15 pls?
Click to expand...
Click to collapse
I used these files!
LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.
LinkinLover2013 said:
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.
Click to expand...
Click to collapse
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?
LinhBT said:
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?
Click to expand...
Click to collapse
So you do it in this order: Go to magisk and select flash to inactive slot -> do OTA update through OPlocalupdate app -> restart phone? Does it have any effect to select flashing magisk to inactive slot before I start OTA udpate? Because it seems like the incremental OTA udpates can install only on unrooted phone with Stock boot.img if I leave it rooted it always stops due to error.