Frist off Im not responsible for anything that happens to your phone!!!
MUST HAVE UNLOCK BOOTLOADER!!
Steps to root
If you are on 11.2.6.6. and rooted
to take update you must flash stock boot.img can be found in link
reboot to bootloader
fastboot flash boot boot11.2.6.6 .img
once done
fastboot reboot
take update
once update is completed
reboot to bootloader
now down load the PATCHEDBOOT.IMG
and flash
fastboot flash boot patched-11.2.7.7.img
once done
fastboot reboot
BOOM NOW YOUR AR ROOTED!!!
STOCK 11.2.6.6 FIXED AND TESTED THANKS TO
mattie_49
LINKS / HELP
BOOT.IMGS
HELP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Josh McGrath said:
View attachment 5335417
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Click to expand...
Click to collapse
please try new uploaded stock boot imgs there fixed now sorry
so, what I (a newbie to rooting without TWRP) should understand is that if I am on stock I just have to unlock bootloader and flash the patched .img?
FizzyAps said:
please try new uploaded stock boot imgs there fixed now sorry
Click to expand...
Click to collapse
Just updated through updated stock image. Thanks for all your efforts
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Won't let me download the OTA after going back to stock bootloader. I have my CN OP9 cross flashed to global. I keep getting Couldn't Update Installation Problem. Guess i'll wait for Oxygen Update.
notiflux said:
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Click to expand...
Click to collapse
You can't install they update if rooted it errors out
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
infamousvincci said:
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
Click to expand...
Click to collapse
please click the help link we have untouched stock 11.2.5.5 there
FizzyAps said:
You can't install they update if rooted it errors out
Click to expand...
Click to collapse
if it detects that your device is rooted, it will switch to downloading the full update instead of the incremental one. Maybe it is different on global ROM, but that's what worked for me
Thanks, updated from 11.2.4.4 with the stock boot img i found in the other thread with this guide.
Related
I have an unlocked rooted 4.4 and need to update to the latest os and modem drivers.
What is the best way and how do I get tethering and root back after I do it?
Pay for sunshine get boot loader unlock flash moto x ROM that is modded
I already have it unlocked.
Where can I get the latest 4.4.4 rooted and can I flash it directly over the current rooted 4.4?
Also where can I get the latest modem drivers?
If you are boot loader unlocked you are already good to go, you can root with a quick flash of a custom recovery
Durteedee said:
If you are boot loader unlocked you are already good to go, you can root with a quick flash of a custom recovery
Click to expand...
Click to collapse
I have TWRP and rooted I need the latest modem drivers and os update
http://motofirmware.center/files/
This site was down for a while, but it seems to be back in a limited fashion right now.
You will need to reinstall TWRP and flash Superuser/SuperSU to regain root after flashing the files most likely. As for tethering, if you plan to stay with a Droid Maxx ROM, you can take a look at this link.
http://forum.xda-developers.com/droid-ultra/orig-development/mod-native-tether-build-24-3-7-t3019059
Do I need to remove TWRP first?
gatortuba said:
Do I need to remove TWRP first?
Click to expand...
Click to collapse
You have to flash that image with RSDLite if I recall correctly. If you leave the xml file the way it is, I believe it will wipe your TWRP and flash the stock recovery in the process, not positive as I haven't done it for a few months. You can reinstall TWRP and root afterwards.
Diocat said:
You have to flash that image with RSDLite if I recall correctly. If you leave the xml file the way it is, I believe it will wipe your TWRP and flash the stock recovery in the process, not positive as I haven't done it for a few months. You can reinstall TWRP and root afterwards.
Click to expand...
Click to collapse
All done, just manually flashed everything but the bootloader.
What are the exact steps?
I have an unlocked boot loader on my Droid Maxx. Currently phone is on 4.4.
Now I am interested in updating it to the latest OTA without losing root.
I understand that if I first install TWRP, I would not be able to take OTA updates. In that case I have to download the update files from the link above and flash via RSD Iite. Is that correct?
Is it not simpler for me to take all the OTA's first (and lose root in the process.) Then, I can still install TWRP and then install SuperSU?
So, yesterday I took four OTA updates and moved from 19.xx to the latest 4.4.4.
I am still rooted and with BL unlocked.
No TWRP ever installed.
Temp root with root king droid maxxx4.4.4!!
I upgraded to the new version of king root today and ran it. I was able to get temp root. I have full access to everything for su. Tested multiple root apps. Will you please post this info some where so as to help my fellow droid maxxx4.4.4 peers?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://postimg.org/image/lcg60jaj3
I'm running a rooted SM-J700P
Will I ever be able to get an update to Android nougat, either through a custom ROM or official update?
I was not able to flash TWRP successfully, I would have to use Odin to flash a custom ROM
Virgin mobile galaxy J700P
adhdluke said:
I'm running a rooted SM-J700P
Will I ever be able to get an update to Android nougat, either through a custom ROM or official update?
I was not able to flash TWRP successfully, I would have to use Odin to flash a custom ROM
Click to expand...
Click to collapse
Did you flash root program threw odin if you flash twrp threw odin 3.12.5 on check auto reboot pull battery boot into recovery an flash superSU SR5 2.8.2 zip then boot system !
J700P has Oreo.
I just got nougat 7.1.1 official update on my boost mobile j700p yesterday and it runs way faster and smoother
J700p
bprsk8r4272 said:
I just got nougat 7.1.1 official update on my boost mobile j700p yesterday and it runs way faster and smoother
Click to expand...
Click to collapse
Thanks for your post I'm on virgin mobile got the update today after going back to stock firmware thanks for the heads up !!
I JUST got the nougat update but now old rooting method no longer works. Is there not a new one yet?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
J700P
jrock77420 said:
I JUST got the nougat update but now old rooting method no longer works. Is there not a new one yet?
Click to expand...
Click to collapse
Has any one tried twerp then superSU st 2.8.5 zip or Magisk ?
Can anyone get the Odin flash file for this? I bricked mine playing around trying to re-root and I cannot find anywhere to download it. Trying to re-flash marshmallow doesn't work
J700P
fedaykinofdune said:
Can anyone get the Odin flash file for this? I bricked mine playing around trying to re-root and I cannot find anywhere to download it. Trying to re-flash marshmallow doesn't work
Click to expand...
Click to collapse
What rooting process did you use ? Try factory reset then reinstall twrp unclick auto reboot in Odin pull battery boot twrp flash Magisk then SR superSU 2.8.2 zip an reboot see if that works it may take up to 8 minutes to boot !!
peter couniaz said:
What rooting process did you use ? Try factory reset then reinstall twrp unclick auto reboot in Odin pull battery boot twrp flash Magisk then SR superSU 2.8.2 zip an reboot see if that works it may take up to 8 minutes to boot !!
Click to expand...
Click to collapse
You should always be flashing the latest SuperSU or Magisk, older versions can cause issues.
minz1 said:
You should always be flashing the latest SuperSU or Magisk, older versions can cause issues.
Click to expand...
Click to collapse
I flashed SuperSU, I had debated factory resetting before trying it but I figured what the hell... Just ended up with a frozen boot screen, but could still interact with the UI (volume, swipe unlock, ok google, etc). Then to make things worse, I accidentally wiped system when I went back in to try again. Yeah...
I managed to build myself an odin flash file to downgrade to AQF3, but of course bootloader and fw versions stayed as BQJ2, even without root software update was still unhappy so couldn't just OTA back to 7.1.1. I went ahead and installed your Lineage 14.1 for the time being, which I'd been holding off doing until I got to test drive the official Nougat because (for some reason) I really enjoy the stock ROM.
I've spent the last 2 days scouring every shady site I could find to hunt down the stock J700PVPE2BQJ2 OTA file, either an update zip or odin flash would be fine, I think. So lame that I spent the better part of 2017 waiting for the official update instead of installing Lineage, how embarrassing.
Anyhow, if anyone would be awesome and snatch the OTA file and upload it somewhere, I'm sure there'd be many grateful people!
peter couniaz said:
Thanks for your post I'm on virgin mobile got the update today after going back to stock firmware thanks for the heads up !!
Click to expand...
Click to collapse
yup no problem
Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and the latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"
Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?
Edit:
Was able to boot without issue with the latest Magisk Canary 04995881 (21002).
Apparently, it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271
I'm willing to help anyone else suffering from this issue get their phones booting back up.
nontheoretical said:
Updated to Android 11 (clean install) and can't get Magisk patched image to boot.
I'm using manager 8.0.2(307) and latest Magisk is 21.0
I patched the boot image from the website, flash successfully, but it reboots to the bootloader saying "no valid slot to boot"
Is anyone else having this issue?
I know the unpatched boot image is ok because when I flash it back it boots up fine.
Am I missing anything?
Thanks in advance.
Click to expand...
Click to collapse
Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812
I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.
dcarvil said:
Did you disable or remove all modules? See https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-705764812
I have no modules installed, and had no problems with the Sept. update. I have not yet tried October.
Click to expand...
Click to collapse
I'm on the Oct update and I don't have any modules installed.
It's a clean install so I haven't even had the chance to install modules yet.
I might downgrade to Sept update if I can't root soon.
Apparently it's related to these issues:
https://github.com/topjohnwu/Magisk/issues/3277
https://github.com/topjohnwu/Magisk/issues/3271
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Bubbler4343 said:
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Click to expand...
Click to collapse
There are some recent comments on running the remove-module script in the github link in post 2. Hopefully something there will help.
Bubbler4343 said:
I am also having the "no valid slot to boot" error. I updated ota google play system update and then got an error to factory reset or try again. I have been trying to flash-all without -w to september and october factory images but still keep getting the error and cannot boot into system.
Can anyone help me fix this issue? I'm unable to use the adb magisk remove-module script.
Click to expand...
Click to collapse
Not sure about the removing of the modules (maybe try the safe mode trigger built into the new Magisk?)
I was able to successfully boot by flashing the stock boot image, the updating to the latest Magisk Canary 04995881 (21002)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like this was updated recently due to the two issues I listed earlier.
I'm gonna keep my magisk_patched.img for this build of Magisk and try with the latest beta and stable releases as they come out.
I'm happy to help anyone else get their build to boot, provide checksums for sanity checks, etc.
I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!
Directly flashing an image over Android 10 with boot.img patched throws it into fastboot
EndlessBliss said:
I can confirm that flashing the 11 image in its stock form first, letting Android upgrade your user data, then flashing the image with the patched boot.img file works!
Directly flashing an image over Android 10 with boot.img patched throws it into fastboot
Click to expand...
Click to collapse
Are you using Canary or Stable?
I had to switch to Canary to get it to boot.
I was coming from a clean install so I had no user data to upgrade.
I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL
EndlessBliss said:
I'm coming from a very unclean install and it worked perfectly with this method. Switched to Beta in Magisk Manager and running 21.0 (21000) on a Pixel 4 XL
Click to expand...
Click to collapse
It looks like this was only reported by users on pixel 3a and older models.
My phone gave me the update download notification, but somehow cannot download the OTA - get an error each time. Anyone else on global has same problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same problem here.
I have a T-mobile device converted to global & rooted. Could it have anything to do with this?
I'm on T-Mobile but bought from OnePlus directly. Same problem.
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
sjgoel said:
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
Click to expand...
Click to collapse
I tried the whole restore images and it failed so I tried to fastboot boot the unpatched 11.0.2.2. it booted but no wifi for. Whatever reason. I tried to download 11.0.4.4 on cellular but I don't have a stable signal so it kept failing. Can someone please post the 11.0.4.4 download image and post a link. It would be most appreciated. I cannot find any other way to download it.
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
It seems so. With an unpatched boot I can try to download, but with a patched boot it gives an error. I'm starting to lose my fondness for OnePlus.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
Agree, never experienced this earlier.
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Yes, that was it. I had to MSM back to TMobile A10, unlock bootloader, convert to global A10, and then OTA to 11.0.4.4 - and then root.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Will wait for that full update. TY!
Disregard
If you're using the global version you can use these, 11.0.4.4.IN21AA global kernels patched and stock, tested on an IN2010.
Stock: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.img
MD5: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.md5
Patched: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.img
MD5: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.md5
For any other version you can d/load and install with a rooted device if you temporarily remove root, I've just done it this way. This assumes you have a stock and patched boot.img for your current ROM available (either in Magisk as a backup image or somewhere else). 4.4 wouldn't download whist I had the patched kernel installed, yes a new OP method.
1. Disable (no need to delete) your Magisk modules (to be safe)
2. Flash the stock boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot flash boot <stock_boot>.img
3. Reboot and test, just to be sure (you shouldn't have root)
4. Boot from the patched (root) boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot boot <patched_boot>.img
5. Now you'll have root back but the stock image will still be installed
6. Download the update, if it's taking a long time hit pause them resume a couple of times
7. Install the update and DO NOT REBOOT!
8. Open Magisk and install via direct method and DO NOT REBOOT!
9. Install Magisk again but this time use install to inactive slot method
10. Reboot when prompted
11. Reenable your Magisk modules
Full update is now available for download
aieromon said:
Full update is now available for download
Click to expand...
Click to collapse
Thanks.
Full update link: https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
At my request, the same user yurxxl from the 4PDA forum collected this recovery for us.
<><><><><><><>Attention!!!Recovery just for stock firmware on the 12th android, and customs based on them, including customs on the 13th android.
Kernel Source: prebuilt stock generic kernel image
Guys, even though I had a joint with the "fox", even though I recovered it and put it on the drain, which then on the custom, and stitched the magisk several times, everything loaded perfectly and worked, but when I decided to make the archive below, I stitched the "fox", well, and accordingly I wanted to put the magisk, and figushki, the installation goes fine, but the recovery is not loaded.
I'm just in ....E.
So be careful, I wrote to the author, but I can't even imagine the reason, but it looks like the whole snag is in reassembling the recovery in the magisk, just like the same archive below, also reassembles the recovery, but after that everything works fine.
++++++++++++++++++++
And about the mentioned archive, for whom it is very important to have the newest core, I have collected an archive for recovery.I checked the installation in both twrp and fox, it works fine.Well, screenshots to boot.
it was
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
has become
Guys, who have an error when flashing the archive above in OR, try this one
What does this kernel do?
htcspark said:
What does this kernel do?
Click to expand...
Click to collapse
Nothing, it's just that all custom recoveries (twrp and orangefox) use the kernel from global firmware 13.0.4.0, this archive flashes the kernel from the latest global firmware 13.0.5.0
Sometimes I lose my 4g connection, I have to force it to 3g, and then I can go back to 4g.
Does this mean I'm on an older kernel?
I'm running evolution rom android 13.
1
CoopZor said:
Sometimes I lose my 4g connection, I have to force it to 3g, and then I can go back to 4g.
Does this mean I'm on an older kernel?
I'm running evolution rom android 13. View attachment 5868749
Click to expand...
Click to collapse
No, I had this firmware, that's not the point.
But if you want to check, you can completely update the kernel.
I installed this firmware, I will see if I still lose my 4g connection.
I keep you guys updated.
Thanx for the help.
arraki said:
No, I had this firmware, that's not the point.
But if you want to check, you can completely update the kernel.
Click to expand...
Click to collapse
PixelExtended was posted in telegram, but the most interesting thing is that it is written that it is assembled on the latest firmware 13.0.7.0, and that it is a global that is distributed through MiPilot, **** else to do something on the 12th android, it is not clear, well, okay.
I took out the boot from there and compiled an archive for recovery, and the truth is that the kernel is now from March
Who is interested, we try
I kept forgetting to write
Guys, I wrote above about the bug with installing a magisk on custom with this recovery, the solution to this problem is the firmware along with recovery and vendor_boot, a special item has been added to the recovery for this.
You can put this
Hello there! Is there any way to keep the recovery after a xiaomi.eu update. It gets reverted to the stock one
SpookieGames said:
Hello there! Is there any way to keep the recovery after a xiaomi.eu update. It gets reverted to the stock one
Click to expand...
Click to collapse
As I wrote in the twrp topic, the recovery is in boot, so it will always be changed to stock or custom.recovery in the case of customs during firmware/update.
Just after the firmware /update it needs to be reinstalled again.
The latest firmware from xiaomi.eu already hybrid, it can be completely installed through recovery.
Since we have two ways of firmware, the first is stock-based customs, they are usually put in the active slot, so after the firmware, you just need to re-flash the recovery.
But all customs, such as Evo, are put in an inactive slot, you can understand this from the log in the recovery, in theory, the firmware stock updates should also be put, as the last one is put from xiaomi.eu , I do not know, as I do not want to update yet.
So, if the firmware occurs in an inactive slot, then in this case, after installing the firmware, in the "reboot" recovery point, first switch the slot (which will be visible at this point), then we re-flash the recovery, well, vendor_boot, if we set custom.
I updated the first post, added a new build, the markup was corrected in it, some elements did not match, and most importantly, now the recovery can save screenshots to the SD card, the choice depends on where the backup is selected
How to install it?
Am gonna flash this but before I flash ... can someone tell me if this is with root?
Edit : I flashed it and it worked very good
arraki said:
I updated the first post, added a new build, the markup was corrected in it, some elements did not match, and most importantly, now the recovery can save screenshots to the SD card, the choice depends on where the backup is selected
View attachment 5885819
Click to expand...
Click to collapse
Do I flash it as fastboot flash recovery or fastboot flash boot
Edit : just flashed it worked perfectly thanks
If I downloaded orange fox do I have to flash stock_kernel in orange fox or not necessary?
Edit : just flashed it worked perfectly without stock kernel
Device : redmi note 11 pro + 5g global (SKCIMIXM) works perfectly on this device
can i flash this recovery as an img file?
I just got my 11E Pro to get MIUI 14 which now have vendor boot as recovery. As expected, the recovery no longer work when trying to flash to boot
(And yes it works normally when I'm on MIUI 13, despite having Global kernel in orangefox)
We need new orangefox for veux once MIUI 14 rolls out