Just checked for updates and this popped up. Enjoy.
Link for the download is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip
I just got this too! Do you know how I can update having twrp installed?
I just tried to install the smaller update above, it failed and now I'm downloading a 1.8gb version. Of you have TWRP installed, I'd probably just download the older OTA and fastboot flash boot boot.img from that OTA.
faddys123 said:
I just got this too! Do you know how I can update having twrp installed?
Click to expand...
Click to collapse
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
xreactx said:
You should be able to install it like normal but ensure when your device reboots you enter your password to enter twrp. If that doesn't work just reboot into twrp and install it by selecting it from the downloaded ROM directory (I forget what the folder is called but it's not the normal download folder). You will have to reflash twrp afterwards.
Click to expand...
Click to collapse
This *should* would too.
Filename for the big file is: miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip we should be able to assemble the whole bigota.somethingsomethingsomething.darkside.xiaomi.downloads url using that, but I'm not at a computer and going to be late for work as is.
Sent from my Mi MIX 3 using Tapatalk
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now ?
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
faddys123 said:
Ok got it installed i downloaded the 1.8gb flashed it via twrp then flashed twrp again and installed magisk all it working now
Noticed a few new things battery percentage text is now inside the battery icon!
Also there's a new 'suggestions' in the recents view, it can be turned off in the settings
Click to expand...
Click to collapse
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
The URL for the big OTA (1.8gb) is: http://bigota.d.miui.com/V10.2.1.0.PEEMIXM/miui_MIMIX3Global_V10.2.1.0.PEEMIXM_9dc43870b4_9.0.zip
PWn3R said:
What version of Magisk did you install? I tried 17.3 and have a bootlooping phone.
Click to expand...
Click to collapse
Using 17.3 as well mate
faddys123 said:
Using 17.3 as well mate
Click to expand...
Click to collapse
I just tried downloading a fresh copy of the Magisk zip. Same result. The phone starts booting then reboots into recovery. I don't know why this doesn't work. Did you have a "global" version of the phone? If so, can you backup your boot image with TWRP (the Magisk rooted one) and post it so we can try downloading and installing to see if it works on a Chinese phone?
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
eseanq said:
Is it normal for the update size to not be displayed? This is my first update using a Xiaomi device & found it odd to not know how large a update was.
Click to expand...
Click to collapse
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
PWn3R said:
Mine showed the size for the small incremental which failed and for the full OTA which installed sucessfully. I have not been able to root this with Magisk, no matter what I tried. Every attempt at rooting with SuperSU or Magisk caused the device to bootloop and go back to recovery.
Click to expand...
Click to collapse
Where does the file size show up?
eseanq said:
Where does the file size show up?
Click to expand...
Click to collapse
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
PWn3R said:
It showed it in the text right below the MIUI logo on the updates page. Check the screenshot in the OP
Click to expand...
Click to collapse
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
eseanq said:
Oh ****.. I'm guessing its the 599M? For some reason I thought that was part of the build. :laugh: Lmao.
Click to expand...
Click to collapse
Yeah, that's the update download size. Don't be surprised when the 599 one fails to install (if you have stock recovery). It will download a 1.8GB one (the one I linked to in the OP now) and that one will install as expected. I think you can install either with TWRP if you want. GLHF
anyone figured how to root this? I flashed twrp then flash magisk 17.3 but it kept bootlooping to twrp.
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Great Update! Many things changed that are not mentioned in the changelog! Finaly notifications in the AOD! ?*?*
PWn3R said:
No, I've tried everything. I have a suspicion we can root this on the Chinese device after we have fastboot images.
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
I think this too.
Related
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
MColbath said:
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
Click to expand...
Click to collapse
Do you still have root? What was the error?
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
MColbath said:
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you outline the exact steps you are doing to flash?
mdamaged said:
Can you outline the exact steps you are doing to flash?
Click to expand...
Click to collapse
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
MColbath said:
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
Click to expand...
Click to collapse
In the process of resetting back to factory, did it relock your bootloader? I ask only because some tools do this automatically. I had to ask.
mdamaged said:
In the process of resetting back to factory, did it relock you bootloader? I ask only because some tools do this automatically. I had to ask.
Click to expand...
Click to collapse
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
MColbath said:
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
Click to expand...
Click to collapse
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it (a suggestion to use goo was here, but forget that).
If you can boot into twrp using the above suggestion, you can at least root and get some stuff done while waiting for a fix or update or someone more knowledgeable than I to solve your issue.
The only thing I can think of is that the bootloader changed and we are back to where you started, waiting for them to update it for your bootloader.
mdamaged said:
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it and try using...goo manager (never used this myself heard some good, some bad things, about it YMMV etc etc).
Click to expand...
Click to collapse
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
MColbath said:
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
Click to expand...
Click to collapse
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Okay seems good.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
MColbath said:
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
Click to expand...
Click to collapse
No problem, thanks for the update.
mdamaged said:
No problem, thanks for the update.
Click to expand...
Click to collapse
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
MColbath said:
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
Click to expand...
Click to collapse
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or location or added a new one (with a diff name) or did something with the permissions so it could not be renamed, and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
mdamaged said:
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or added a new one (with a diff name), and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
Click to expand...
Click to collapse
Yeah there are new backup files all over the place in System partition.
MColbath said:
Yeah there are new backup files all over the place in System partition.
Click to expand...
Click to collapse
Stupid providers.
mdamaged said:
Stupid providers.
Click to expand...
Click to collapse
I'm checking the developer block section of recovery right now.
I'll upload the log for the recovery too. Hold on.
Here it is.
MColbath said:
Here it is.
Click to expand...
Click to collapse
Is there a file in /system named recovery-from-boot.p?
It is a little annoying that I can't use OTA because of my custom recovery (TWRP).
As of now I need root for 1 thing: backing up my apps.
Is there any way to backup apps the same as in Titanium backup (with the data of the apps) but without root?
This way I could use the OTA to update the phone
Thanks,
orma
Try out Helium Backup. It's free on the app store. You need to install this app on a PC however to enable backing up.
I tried it, but some apps cannot be backed up and the one I need the most is also in the list.
Is there any other way?
Here's what to do, root your phone and then get flashfire. You'll be able to flash the ota with it maintaining root and a custom recovery if you use it. You can also create backups with flashfire. You get the best of both worlds. Don't forget you can also download the ota's from Google if you can't wait for them to be pushed to your phone. It's also easier this way.
Can't I just use TWRP to flash the ota image?
I already have it installed
You'll loose root and twrp for sure and I don't think it will flash because you have twrp installed.
jd1639 said:
You'll loose root and twrp for sure and I don't think it will flash because you have twrp installed.
Click to expand...
Click to collapse
I looked in the comments about the app and a lot of people say that it's not working in Android Oreo.
I want to use it to flash the new oreo September security update.
Should I still use it?
It's working on my 5x with Oreo. I flashed Oreo with it and the sept update.
jd1639 said:
It's working on my 5x with Oreo. I flashed Oreo with it and the sept update.
Click to expand...
Click to collapse
okay, i will try and update. so i just download it from the playstore?
Yes. Some of its self explanatory. You're going to want to inject supersu, everoot, and in reboot have normal and preserve recovery checked.
jd1639 said:
Yes. Some of its self explanatory. You're going to want to inject supersu, everoot, and in reboot have normal and preserve recovery checked.
Click to expand...
Click to collapse
I downloaded the zip file from google site to my nexus 5x and the app doesn't recognizes it to be flashed.
it does recognize the zip file of supersu (already have it installed)
what should i do?
orma1 said:
I downloaded the zip file from google site to my nexus 5x and the app doesn't recognizes it to be flashed.
it does recognize the zip file of supersu (already have it installed)
what should i do?
Click to expand...
Click to collapse
That doesn't make any sense. I've done this 20 or more times with various nexus devices. It's possible the file was corrupted while downloading. Can you find the file on your device. It'd try downloading it again.
You're using the flash zip or ota and not firmware package?
jd1639 said:
That doesn't make any sense. I've done this 20 or more times with various nexus devices. It's possible the file was corrupted while downloading. Can you find the file on your device. It'd try downloading it again.
You're using the flash zip or ota and not firmware package?
Click to expand...
Click to collapse
Downloaded it from here: https://developers.google.com/android/images
from factory images tab
edit: downloaded from the Full OTA Images tab and it does recognize it should i flash it?
i used flash zip or ota
orma1 said:
Downloaded it from here: https://developers.google.com/android/images
from factory images tab
edit: downloaded from the Full OTA Images tab and it does recognize it should i flash it?
i used flash zip or ota
Click to expand...
Click to collapse
Yes. The full ota is the right file.
jd1639 said:
Yes. The full ota is the right file.
Click to expand...
Click to collapse
I have those 3 options to check:
auto-mount
mount /system read/write
restore boot and recovery images
which one to check
orma1 said:
I have those 3 options to check:
auto-mount
mount /system read/write
restore boot and recovery images
which one to check
Click to expand...
Click to collapse
Only have restore boot and recovery
jd1639 said:
Only have restore boot and recovery
Click to expand...
Click to collapse
sorry for all of those question but the description of this make it sound like it would install the stock recovery instead of twrp
the description: Attempt restore stock boot and recovery images before flashing. May be required for some OTAs. Disable for non-OTA updates.
When you hit the check mark on that screen you'll be brought to another screen. On that one you'll see reboot. Click on that and you'll have the option to preserve recovery. That's were it'll keep twrp on your device. So restore boot and recovery is the correct setting
jd1639 said:
When you hit the check mark on that screen you'll be brought to another screen. On that one you'll see reboot. Click on that and you'll have the option to preserve recovery. That's were it'll keep twrp on your device. So restore boot and recovery is the correct setting
Click to expand...
Click to collapse
oh ok Thank you very much!
edit: it worked fine Thanks
orma1 said:
oh ok Thank you very much!
Click to expand...
Click to collapse
No problem
Hello
Can some send me a TWRP backup of their Mate SE? I only need the boot image. Please just the boot partition. I don't have a good internet where I am at right now and I bricked. Thanks!
Sandman-007 said:
Hello
Can some send me a TWRP backup of their Mate SE? I only need the boot image. Please just the boot partition. I don't have a good internet where I am at right now and I bricked. Thanks!
Click to expand...
Click to collapse
Unlocked for a whole , what, 3 hours , and you brick already.
Sorry had to do that.
I don't have mate , but 7x the roms are supposedly basically the same. At least the 7x custom roms work on se.
I have boot image uploaded , along with the the rest of the partitions , as separate files. On Android file host. You can. Try to use that.
As far as mate back up I have found one, but it is whole backup.
https://androidfilehost.com/?w=files&flid=261152
mrmazak said:
Unlocked for a whole , what, 3 hours , and you brick already.
Sorry had to do that.
I don't have mate , but 7x the roms are supposedly basically the same. At least the 7x custom roms work on se.
I have boot image uploaded , along with the the rest of the partitions , as separate files. On Android file host. You can. Try to use that.
As far as mate back up I have found one, but it is whole backup.
https://androidfilehost.com/?w=files&flid=261152
Click to expand...
Click to collapse
LOL what can I say, I took one for the team!
Thanks, I actually found a boot.img for a 7x that I fastboot flashed but it didn't help. I am downloading a Full TWRP backup for the Mate SE that I found but my internet at my GFs is real slow so gonna take a couple hours. I'll update.
What Roms for 7x work on SE? Maybe I will just flash one of those? My phone wasn't on Oreo so I don't imagine an Oreo ROM working,
Oh and I bricked by flashing Magisk and no-verify 4.1. I knew I shouldve stayed away from Magisk and just flashed SuperSU
Sandman-007 said:
LOL what can I say, I took one for the team!
Thanks, I actually found a boot.img for a 7x that I fastboot flashed but it didn't help. I am downloading a Full TWRP backup for the Mate SE that I found but my internet at my GFs is real slow so gonna take a couple hours. I'll update.
What Roms for 7x work on SE? Maybe I will just flash one of those? My phone wasn't on Oreo so I don't imagine an Oreo ROM working,
Oh and I bricked by flashing Magisk and no-verify 4.1. I knew I shouldve stayed away from Magisk and just flashed SuperSU
Click to expand...
Click to collapse
I have it downloaded already and have put the images up as files.
***updating this in 5 minutes with link***
mrmazak said:
I have it downloaded already and have put the images up as files.
***updating this in 5 minutes with link***
Click to expand...
Click to collapse
Ok Thanks. So which Rom were u referring too because I only see one and it's Oreo based.
Sandman-007 said:
Ok Thanks. So which Rom were u referring too because I only see one and it's Oreo based.
Click to expand...
Click to collapse
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
mrmazak said:
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
Click to expand...
Click to collapse
Thanks downloading now. I do believe it was the manual Oreo. It works for the L31
Sandman-007 said:
Thanks downloading now. I do believe it was the manual Oreo. It works for the L31
Click to expand...
Click to collapse
found the post i remeber reading.
https://forum.xda-developers.com/showpost.php?p=76286950&postcount=159
mrmazak said:
I'm reading through the Mate thread again to see which ones. I think it was the manual Oreo update that worked, but have not found that claim yet.
here is link to folder, still uploading files , but boot is ready
https://www.androidfilehost.com/?w=files&flid=266003
Click to expand...
Click to collapse
Thank You! That worked! My phone boots. That funny because I tried 2 other boot.img for the 7x but they didn't work. Thanks!
Edit: Welp Spoke too soon. I boot but get a black screen once I hit home screen. Trying a Factory reset. I did one earlier but ehhh...
Sandman-007 said:
Thank You! That worked! My phone boots. That funny because I tried 2 other boot.img for the 7x but they didn't work. Thanks!
Edit: Welp Spoke too soon. I boot but get a black screen once I hit home screen.
Click to expand...
Click to collapse
that last boot is from mate backup.
try to go inside , to dark room to see if screen is really blank or just turned down real low.
the brightness on these seem to be able to go way too low.
mrmazak said:
that last boot is from mate backup.
try to go inside , to dark room to see if screen is really blank or just turned down real low.
the brightness on these seem to be able to go way too low.
Click to expand...
Click to collapse
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Sandman-007 said:
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Click to expand...
Click to collapse
well, lets review what you did , and maybe figure out what is "broke" maybe less drastic than system flash is needed.
mrmazak said:
well, lets review what you did , and maybe figure out what is "broke" maybe less drastic than system flash is needed.
Click to expand...
Click to collapse
Ok. SO after I unlocked my bootloader I flashes TWRP 3.1.1-0. I can't find 3.1.1-1 for the 7x even tho that is the one ppl say to use since it supports decrypt.
Then I flashed the latest Magisk and no-verity 4.1. When my system didn't boot I tried n-verity 6.0 then 5.1 as I thought I was using the wrong version but it didn't help.
I did try flashing the uninstaller for Magisk but it fails to flash. Can't find /Vender it says. Honestly I should've just flashed SuperSU.
Sandman-007 said:
Ok. SO after I unlocked my bootloader I flashes TWRP 3.1.1-0. I can't find 3.1.1-1 for the 7x even tho that is the one ppl say to use since it supports decrypt.
Then I flashed the latest Magisk and no-verity 4.1. When my system didn't boot I tried n-verity 6.0 then 5.1 as I thought I was using the wrong version but it didn't help.
I did try flashing the uninstaller for Magisk but it fails to flash. Can't find /Vender it says. Honestly I should've just flashed SuperSU.
Click to expand...
Click to collapse
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
mrmazak said:
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
Click to expand...
Click to collapse
Thank you. It'll be a few hours but I will get back to you!
mrmazak said:
Maybe need to flash vendor partition.
Still uploading that file. Is at 33%Done
It is 822 mb
Version I am putting up is from the b130 backup
Check back in file host folder in about 15-20 minutes. Or continue with the original full backup download. Done
Click to expand...
Click to collapse
Well I tried flashing Boot, System and Vender and I still have the blank screen. I even wiped system and Data then reflashed. I suspect the system.img is different for Mate SE and I am flashing 7x System.img
Sandman-007 said:
Well I tried flashing Boot, System and Vender and I still have the blank screen. I even wiped system and Data then reflashed. I suspect the system.img is different for Mate SE and I am flashing 7x System.img
Click to expand...
Click to collapse
The folder I shared is the mate se backup.
mrmazak said:
The folder I shared is the mate se backup.
Click to expand...
Click to collapse
Any suggestions then because I flashed all the files after a full wipe and I still get a Black Screen with nav bar showing and power options showing but no launcher
Sandman-007 said:
I can see the nav bar and the power menu options. Launcher just wont start. I think I need to flash system image
Click to expand...
Click to collapse
i bricked mine within a day, same reason: magisk + no-verify. Can't say for sure why, I installed magisk ok, no-verify had zip error, but installed anyway, then I wiped caches. result = no boot. Maybe I shouldn't have wiped?
I was able to recover using someone else's backup imgs and part of the process here:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I used fastboot to flash the system and boot imgs and used twrp to flash the vendor img. I think that was the trick, just using fastboot to flash the vendor resulted in the black screen with nav controls only.
drunkle said:
i bricked mine within a day, same reason: magisk + no-verify. Can't say for sure why, I installed magisk ok, no-verify had zip error, but installed anyway, then I wiped caches. result = no boot. Maybe I shouldn't have wiped?
I was able to recover using someone else's backup imgs and part of the process here:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I used fastboot to flash the system and boot imgs and used twrp to flash the vendor img. I think that was the trick, just using fastboot to flash the vendor resulted in the black screen with nav controls only.
Click to expand...
Click to collapse
OK I tried that. Selected the vender partition in TWRP and flashed vender img on top. Still black screen.
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse
Already prompted to install 11.2.7.7. About to install/re-root.
Normal process for taking the OTA and keeping root worked without any issue.
are you doing both Direct & Inactive slot Install before Reboot?
dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
where did you get it?
dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
Can you give me the kernel patch file? magisk
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Fre$h said:
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Click to expand...
Click to collapse
I just did that and nothing has changed. If someone can give the 11.2.7.7aa image, that would help alot
galaxys said:
are you doing both Direct & Inactive slot Install before Reboot?
Click to expand...
Click to collapse
Yes
vibrantliker said:
where did you get it?
Click to expand...
Click to collapse
Just through the normal system updater.
dimmed said:
Can you give me the kernel patch file? magisk
Click to expand...
Click to collapse
No, sorry, I don't do this.
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
I followed my normal process (I don't use any Magisk modules):
Magisk Uninstall->Restore Images (do not reboot)
Take OTA (do not reboot)
Install Magisk to both active and inactive
Reboot
Worked without issue, as always.
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
egandt said:
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
Click to expand...
Click to collapse
Yeah, I don't do any custom kernel stuff or magisk modules, I cannot personally comment. What I know, for me, is the process fails 100% of the time if I don't do the Magisk image restore and it succeeds 100% of the time if I do.
I am currently on 11.2.4.4 AA (Global), rooted. Can I upgrade to the EU ROM since they tend to get full updates while AA has not been? If so, do I just flash the 11.2.6.6 EU ROM or should I flash 11.2.4.4 EU ROM then flash a more up-to-date ROM? If I flash the EU ROM, would I loose anything?
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Not sure if this was for someone specific for their unique circumstance. If this was just meant generally, then it is inaccurate.
I don't use Oxygen Updater. I just take the incremental OTA using the steps I mentioned.
Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Just letting you know, Oxygen Updater is stuck on 11.2.4.4, as is the OnePlus website.
dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Atul Menon said:
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Click to expand...
Click to collapse
Easy. You open magisk and restore stock boot. Don't reboot yet. Download and install update. Don't reboot yet. Open magisk and install to inactive slot. Reboot.
dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
thirtythr33 said:
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
Click to expand...
Click to collapse
Works for me every time...that way just post it.
netgar said:
Works for me every time...that way just post it.
Click to expand...
Click to collapse
yeah my system reports 11.2.4.4, yet have an incremental update for 11.2.7.7, which is odd for a number of reasons. long story short I'm sure it will cause me issues to try applying an incremental update that is not in order, but idk why 11.2.7.7 is showing up on my system, bc 11.2.6.6 never installed (or the system doesn't report it did)