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
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?
Hi dudes! Im trying to find a way to install Monthly Updates without loose the root and the custom recovery, some body can tell me how? Because im really want update to Oreo but i want be root user and dont have to make a clean install system every month... exist the way? Please help.... And Thanks!
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
You can use Flashfire.
nowster said:
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
Click to expand...
Click to collapse
Okey, but using adb?
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
How dude? Can you tech me please?
Aijen said:
How dude? Can you tech me please?
Click to expand...
Click to collapse
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Yes, you can use TWRP's "Advanced" adb sideload feature to install Magisk zip.
"adb" only works when Android is running (or some recovery images are running). When the phone is in bootloader mode the tool you need is "fastboot".
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Thanks a lot! I will tried to do it!
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Are you do that method without problems?
Aijen said:
Are you do that method without problems?
Click to expand...
Click to collapse
Yes it worked for me. But if you have twrp make a nandroid backup.
fnldstntn said:
Yes it worked for me. But if you have twrp make a nandroid backup.
Click to expand...
Click to collapse
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
fnldstntn said:
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Aijen said:
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
Click to expand...
Click to collapse
i dont remember
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Click to expand...
Click to collapse
i dont know.
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk?
Click to expand...
Click to collapse
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
zo1021 said:
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
Click to expand...
Click to collapse
Using the logic need to reflash it again
nowster said:
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
Click to expand...
Click to collapse
Sounds logic to me....
FlashFire is saying that the update will likely fail because the OTA update is a block level update. Suggestions on how to get around this?
Hi all,
Good news is I get the "how to root" stuff. But one aspect remains a bit unclear.
I did search but I didn't find a clear answer. If I would clean flash a full update (signed flashable zip), do you loose TWRP and root?
If yes, is the only option to reinstall TWRP-recovery and reroot?
kr,
Jeroen
You wouldn't lose TWRP, but root might give you problems depending on what method you used to root.
Best to do a full unroot, flash update, then re-root.
xocomaox said:
You wouldn't lose TWRP, but root might give you problems depending on what method you used to root.
Best to do a full unroot, flash update, then re-root.
Click to expand...
Click to collapse
Method would be just flashing Su or Magisk from TWRP. A full unroot is the same as a clean flash I suppose?
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
xocomaox said:
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
Click to expand...
Click to collapse
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Jeroen1000 said:
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Click to expand...
Click to collapse
I just got mine. Already unlocked bootloader.. Flashing TWRP now.. Then I will flash the latest update to see how it goes.
Jeroen1000 said:
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Click to expand...
Click to collapse
Okay, so I had TWRP installed and no Magisk. I took the OTA through System Update screen...
I lost TWRP and gained stock recovery back. Everything else went fine. So I guess system update wipes TWRP! Oh, well. Easy fix.
Wait for OTA updates this is normal. You need full ROM flashable zips. For the 5 there was a topic in which they got posted. Don't know yet for the 5T. But as you say rerooting is hardly a chore
xocomaox said:
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
Click to expand...
Click to collapse
From the heck of it today I tried uninstalling magisk by flashing the uninstaller in twrp and through magisk manager in system. After both methods my phone wouldn't get past the OnePlus splash screen.
How can you get phone to boot after unrooting and restoring the stock boot image through Magisk?
Dazed No More said:
From the heck of it today I tried uninstalling magisk by flashing the uninstaller in twrp and through magisk manager in system. After both methods my phone wouldn't get past the OnePlus splash screen.
How can you get phone to boot after unrooting and restoring the stock boot image through Magisk?
Click to expand...
Click to collapse
Hmm, that is interesting. Try taking the OTA zip using the official method (but use TWRP file manager to move it in place).
Or just flash official system image. You can get it from this forum.
Losing TWRP
Help! Trying to install twrp. Able to flash, but after reboot, phone reverts back to original recovery. Also, while in twrp- was not able to do anything... Figure something to do with encryption? In twrp formatted data, then was able to back up... Thought it fixed the problem, but still reverting back to original.
Thanks.
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
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.