Hello to all,
I have a problem with my nothing phone. I try to update my phone to version 1.1.8 EEA having an EEA version. The local method keeps showing me error 20.
I have applied the tutorial to pass it via the recovery except that when I try to apply it, it tells me previous installation has failed and if I try to restart the phone, it might crash.
Not wanting to tempt the devil I still did a factory reset and restart the phone. Fortunately no problems but still in version 1.1.7.
I don't understand this error message. The last time I installed an upgrade was 1.1.7 hotfix and there was no problem installing it locally.
Is there any way to fix this error or should I just skip it and hope I don't brick it?
Thank you in advance for your answer
I have the same issue. Not even the official system update OTA works. Installation failed.
i have same issue but i solved it by doing
1. unlock bootloader install any custom rom for few minute than install any official version by flashing boot and vendor boot in fastboot mode and zip in adb sideload mode than reboot and again enter fastboot mode lock boot loader all ota updates will work without any issue
please check this thread :
FIX OTA installation problem
hi mates, recently when i downgraded from Nos 13 to 12 (or) from custom to stock NOS i had faced OTA installation problem (note im bootloader and critical unlocked) OTA update use fail , and local update also getting error. I fixed the issue...
forum.xda-developers.com
Nayakantipavankumar said:
please check this thread :
FIX OTA installation problem
hi mates, recently when i downgraded from Nos 13 to 12 (or) from custom to stock NOS i had faced OTA installation problem (note im bootloader and critical unlocked) OTA update use fail , and local update also getting error. I fixed the issue...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, I'm on 1.1.7 and can't get to 1.1.8.
I'm guessing this is due to a changed boot image from the past. Would the factory reset even be necessary?
Shouldn't it be enough in my case to flash boot and vendor_boot from 1.1.7 EEA full image, to bring the signatures back to where the OTAs work?
Thanks!
OK, I fixed it:
- put 1.1.7 full EEA in "ota" folder on phone (same version as I had before)
- restored boot images via magisk (I think I may have flashed a patched one before, so the hashes didn't match for 1.1.8 OTA; this step is probably not necessary when using full image)
- used local OTA method (*#*#682#*#*)
- rebooted
- installed 1.1.8 from system update
- profit
panni said:
OK, I fixed it:
- put 1.1.7 full EEA in "ota" folder on phone (same version as I had before)
- restored boot images via magisk (I think I may have flashed a patched one before, so the hashes didn't match for 1.1.8 OTA; this step is probably not necessary when using full image)
- used local OTA method (*#*#682#*#*)
- rebooted
- installed 1.1.8 from system update
- profit
Click to expand...
Click to collapse
I have currently a patches boot img 1.1.7. I recovered the image over magisk uninstall already but cannot update over OTA, do you think your method is also working? Can you install the 1.1.7 even if you have 1.1.7 installed? Will the devices be resetted with your method?
paper88 said:
I have currently a patches boot img 1.1.7. I recovered the image over magisk uninstall already but cannot update over OTA, do you think your method is also working? Can you install the 1.1.7 even if you have 1.1.7 installed? Will the devices be resetted with your method?
Click to expand...
Click to collapse
That was exactly my situation. Don't know if it works for you, but for me it worked. Lost no data (works the same as side loading).
Just make sure you use the right full image (EEA or global).
Afterwards upgrade to 1.1.8, reboot, extract the boot.img from the same full image you flashed, patch it with magisk, boot it via fastboot and install magisk directly. Don't flash the modified boot.
panni said:
That was exactly my situation. Don't know if it works for you, but for me it worked. Lost no data (works the same as side loading).
Just make sure you use the right full image (EEA or global).
Afterwards upgrade to 1.1.8, reboot, extract the boot.img from the same full image you flashed, patch it with magisk, boot it via fastboot and install magisk directly. Don't flash the modified boot.
Click to expand...
Click to collapse
Did you update via OTA to 1.1.8 or from where you get the 1.1.8 boot.img?
paper88 said:
Did you update via OTA to 1.1.8 or from where you get the 1.1.8 boot.img?
Click to expand...
Click to collapse
I updated via OTA to 1.1.8 and used the 1.1.7 boot.img to patch it and boot it (not flash it). 1.1.8 doesn't have an updated boot.img.
panni said:
I updated via OTA to 1.1.8 and used the 1.1.7 boot.img to patch it and boot it (not flash it). 1.1.8 doesn't have an updated boot.img.
Click to expand...
Click to collapse
Alright, thats good. I thought 1.1.8 have its own boot.img. And I didn't found the Full ROM to extract it. But I install currently also the 1.1.7 again and will wait after the reboot
panni said:
I updated via OTA to 1.1.8 and used the 1.1.7 boot.img to patch it and boot it (not flash it). 1.1.8 doesn't have an updated boot.img.
Click to expand...
Click to collapse
It worked! Thanks
Hi all,
a little late to post on this topic, but If someone else has this same kind of problem trying to upgrade to 1.1.8 like I had. I have no root and bootloader is locked. I didn't want to try and extract boot images. All I did is I downloaded The full 1.1.7 OTA and installed it with the offline dialer installer. Next reboot I manage to install 1.1.8 through system update.
I also contacted Nothing support, but they didn't have nothing better answer to give me but to do a system reset.
Thanks for all the help!
Related
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.
I'M NOT RESPONSIBLE IF YOUR DEVICE BRICKS, SD CARD DAMAGES OR NUCLEAR WAR STARTS.
Rooting method described below will work on Oreo-running devices ONLY (confirmed on build OPN27.76-12-22 and on OPNS27.76-12-22-9).
Please follow all steps very carefully and make sure you downloaded correct versions of all .zip files mentioned in my instruction!
ROOT (SafetyNet test will PASS!)
1. Download all files listed below:
- twrp-3.2.3-0-addison.img (CLICK)
- Magisk-v17.1.zip or newer if availabe (CLICK)
- f2fsfix-2018.9.2.zip (CLICK)
2. Flash TWRP using Fastboot:
Code:
fastboot flash recovery twrp-3.2.3-0-addison.img
3. Flash Magisk-v17.1.zip (or newer if available).
4. Go to TWRP/Settings and open Terminal.
5. Run both of following commands:
Code:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6. Flash f2fsfix-2018.9.2.zip
7. Reboot (it is crucial in case of installing Xposed afterwards).
8. Optional but recommended: update your Magisk Manager to the latest version (CLICK).
9. Open Magisk -> Modules and update f2fs-loopback-bug-workaround module to the newest version (can be done only via Magisk Manager only if new version of f2fs-loopback-bug-workaround module is available).
10. Enjoy rooted Oreo.
UPDATE 03.10.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 17.1.zip AGAIN (yes.).
3. Flash f2fsfix-2018.9.2.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me).
UPDATE 03.10.2018
XPOSED (be careful: Xposed for Oreo is still in BETA distribution and flashing it will break your SafetyNet!)
1. Open Magisk Manager -> Downloads.
2. Download Xposed Installer (the one from the screen below):
https://image.ibb.co/byLUuK/Xposed_Framework.png
3. Let Magisk install it.
4. Reboot.
5. Open Xposed Installer (you will see orange exclamation mark, don't worry).
6. Reboot once again.
7. Voila.
Hit THANKS if I helped!
Credits:
- @topjohnwu
- @rovo89
- @Artim_96
- @VR25
@rafikowy ah, so basically the problem was with dm-verity and forced encryption? That makes sense. So it would basically also work if you'd not extract the boot.img from the OTA zip and mod it with Magisk manager with both enabled and flash that (might be easier than flashing normal Magisk and then make the changes), so you'd basically just flash the img and the module zip in TWRP.
Well, if no bigger bugs appear I might try the Oreo OTA and root tomorrow. Don't think it will be here on its own till then, even if it's already the official rollout (Indian and brasilian users seem to get it officially)
First magisk manager did not want to open, but a reboot solved. thanks
So, Lenovorola is still "undecided" in regards to patching F2FS.
I wonder why...
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Only a Soak test is available, the link is in the thread in the ROM section. And yes, it doesn't seem to update your bootloader, it was already successfully testet to go back to 7.1.1
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Look at
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120
not work - moto z play - oreo soak
Unfortunately it does not work. : (TWRP prompts for a PIN to decrypt data.) How to select cancel and install Magisk on installation f2fs-loopback-bug-workaround-2018.1.31.zip displays an error that does not detect magisk or is incompatible. How do I format the date everything is installed but the phone does not turn on... Any idea?
Sorry but, if verity is enabled, that means you are unable to modify /system files?
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
You can go back, problem is you will lose IMEI by going back to Nougat.
huma_dawii said:
You can go back, problem is you will lose IMEI by going back to Nougat.
Click to expand...
Click to collapse
I gone back to 7.1.1 Nov patch and everything is OK with my IMEI. Just flash 7.1.1 Plus ROM with TWRP. One issue what I have - In can't mount OEM partition in TWRP.
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Camarda said:
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Click to expand...
Click to collapse
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
St.Noigel said:
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
Click to expand...
Click to collapse
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Camarda said:
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Click to expand...
Click to collapse
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Can i go back to 7.1.1 and relock bootloader ??
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
LovinVEVO said:
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
Click to expand...
Click to collapse
Nope. It's impossible for now. You can`t go back to full stock, because you'll lose your IMEI with flashing full 7.1.1 FW with RSD or fastboot.
St.Noigel said:
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Click to expand...
Click to collapse
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Camarda said:
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Click to expand...
Click to collapse
If you have bootanimation - just wait few minutes
St.Noigel said:
If you have bootanimation - just wait few minutes
Click to expand...
Click to collapse
Just waited for 30 minutes. It wont boot
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Master_T said:
Hi fellows
I wanted to root my Mi 9T, but I don't want to flash a custom rom, I just want to have root on the official rom (global stable).
As I understand, the correct procedure is:
-unlock nootloader
-flash twrp
-flash magisk
But I have a couple of doubts about this, in particular about updates:
-If my phone is unlocked and I have root, will I still receive official updates from xiaomi?
-if yes, do they install via twrp? Do they fail installation? Do I loose root/bootloader unlock if I install them on unlocked/rooted phone?
-if no, is there an alternative way to install updates without losing root every time?
In other words, what is the best way to have a rooted phone but with official, up-to-date rom? (I have no problems downloading/installing updates manually, but having to reapply root every time would be annoying)
Click to expand...
Click to collapse
As I know you could receive updates if you unlock your bootloader and flash magisk, I don't have experience with that, I've read that from other brands people do this and still get their updates.
If I'm wrong correct my.
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
I'm not sure about Mi 9t (have to wait for bootloader unlock), but it was so on Redmi 3s: I can install OTA updates, it goes through TWRP, but after every update I have to flash Magisk.
It was several years ago, so probably they've changed something
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected ?
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
Which twrp and magisk do you use?
grinandbearit said:
Which twrp and magisk do you use?
Click to expand...
Click to collapse
First TWRP that came out (LR Team), but that is because it was the only one available at the time, there might be better ones out now, check the TWRP thread for more info.
Magisk, I used the latest stable release.
Master_T said:
Thanks for your replies guys.
I can now confirm (just tested) that to update a rooted mi9t all you have to do is this:
-flash update zip with twrp (you have to download the update zip from somewhere, like mifirm website, the one downloaded by the update tool is encrypted and won't work!)
-flash magisk
-reboot
Very simple! No need to reflash magisk modules, just the magisk base package and everything works as expected
Click to expand...
Click to collapse
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Edit: wrong quote
fabsen said:
I think it is more simple to do the update and reflash magisk instead of searching for the update package manually, isn't it?
Click to expand...
Click to collapse
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Master_T said:
You mean flash the fastboot rom using a computer and then reinstall twrp and magisk?
Seems more convoluted to me, since you still need to download the rom from an external website and additionally you need a pc and you need to reflash twrp every time.... it'll probably work fine, but it seems more complicated to me
Click to expand...
Click to collapse
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
fabsen said:
Nah, I mean you flash the update you get the usual way. And then magisk afterwards. At least I've never lost twrp with OTA updates.
Click to expand...
Click to collapse
You mean the one downloaded through the miui updater? I can't flash that with twrp, it's encrypted. In fact, I can't even open the zip file with file manager, it says the file is corrupted. How do you decrypt/use it?
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Thank you all, it's nice to find this post before I create a new with the same questions.
I bought a new "Mi 9t", it received the latest OTA update, and it has been unlocked after waiting 170 hours.
MIUI Version: MIUI Global 10.3.11 Stable
Android Version: 9 PKQ1.190302.001
Model Name: M1903F10G
Now I need to root it without flashing twrp, I need to be on the Stock recovery because I don't want to lose the OTA update.
I ran this command :
Code:
C:\adb>fastboot boot recovery.img
Downloading ‘boot.img’ OKAY [ 1.404s]
booting OKAY [ 0.127s]
Finished. Total time: 1.560s
but the device reboot to MI-Recovery 3.0, can someone correct me if I'm wrong? also which twrp version support MIUI Global 10.3.11 Stable?
Matthas said:
Few days ago I got OTA update while having magisk root and TWRP installed. It rebooted phone into TWRP and installed itself through TWRP. So it seems Xiaomi can now detect what recovery you are using and instead send you recovery OTA instead? Sadly I lost TWRP and root this way and needed to find newer TWRP (old one didnt boot and caused bootloop). Rom also didnt boot (after flashing new TWRP) until I flashed magisk.
Click to expand...
Click to collapse
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Master_T said:
Weird, I tried that (downloading update from the updater app and rebooting to twrp to auto-flash it), but TWRP said update was corrupted. I had to download an unencrypted version from mifirm site to flash it with twrp.
Maybe it's a problem with the version of twrp? Which one are you using? I'm using the one from LR Team
Click to expand...
Click to collapse
oh I wish I knew After update when I went to flash back old twrp and magisk it resulted in bootloop so I was flashing all twrp I could find just to make them boot and then be able to flash magisk. However name of my file is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" I think its "fixed" chinese one.
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
akha666 said:
Is "recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150" support for MIUI Global 10.3.11 Stable?
Can I boot from it to root Mi 9T without flashing?
Click to expand...
Click to collapse
Is any expert have an answer to my questions?
Schnedi said:
• You will receive the ota but it won't install
• You'll have to install the full rom and reflash Magisk everytime
• Orange Fox recovery can install ota BUT not available for Mi 9T/K20
Click to expand...
Click to collapse
How do i root global stable rom 10.3.11 without bootlooping? Just rooting and no twarp .
Anyone who needs it
This is T mobile KB2007 boot image (unmodified)
Fresh out of the box
11.1.0.2 KB09CB : boot_11102.img
Security Update November 2020
11.0.6.8 KB09CB: boot_11068.img
OTA Link
https://android.googleapis.com/packages/ota-api/package/52b06537d6cb337f111b279a57b597f9390e6048.zip
January 2021 security update
11.0.7.9 KB09CB
OTA link
https://android.googleapis.com/packages/ota-api/package/99bca5df5c48825512178d8a41575c93370907c9.zip
Original Boot image : boot11079
Magisk canary Patched Boot : Boot11079magisk
How would someone go about installing or flashing this without twrp?
I'm rooted on 11.0.6.8 and want to do the ota to 11.0.7.9 but system update isn't here on my phone
Reserved
spart0n said:
How would someone go about installing or flashing this without twrp?
I'm rooted on 11.0.6.8 and want to do the ota to 11.0.7.9 but system update isn't here on my phone
Click to expand...
Click to collapse
for unlocked bootloader
To install OTA
1- Restore original boot on magisk manager
2- Install OTA and reboot (Install magisk to inactive slot wont work and high risk boot-loop)
3- Once the update is finish, reboot to bootloader
4. Boot (Do NOT FLASH) magisk patched image (fastboot boot magistpatched)
5. Open Magisk Manager and do Magisk Install (Direct Install)
6. Reboot and you are done
hoodred said:
for unlocked bootloader
To install OTA
1- Restore original boot on magisk manager
2- Install OTA and reboot (Install magisk to inactive slot wont work and high risk boot-loop)
3- Once the update is finish, reboot to bootloader
4. Boot (Do NOT FLASH) magisk patched image (fastboot boot magistpatched)
5. Open Magisk Manager and do Magisk Install (Direct Install)
6. Reboot and you are done
Click to expand...
Click to collapse
Do you think I could use a custom recovery (LOS or pixel experience) and use the adb side load and do the ota that way then reflash magisk right after?
spart0n said:
Do you think I could use a custom recovery (LOS or pixel experience) and use the adb side load and do the ota that way then reflash magisk right after?
Click to expand...
Click to collapse
Just restore your boot image
and open system update and hit check update to download and install the ota.
and make sure you dont connect to some funky VPN that for some reason showing your location outside the USA
I would turn off all magisk modules first and then uninstall magisk through the magisk app then install the OTA.
Will OTA wipe data?
Phone services stop working...
Just wanted to say thanks for this! Definitely needed these
NVM
How do I flash these and return to stock? Currently in rooted, but on custom ROM. Thanks in advance.
hoodred said:
January 2021 security update
11.0.7.9 KB09CB
OTA link
https://android.googleapis.com/packages/ota-api/package/99bca5df5c48825512178d8a41575c93370907c9.zip
Original Boot image : boot11079
Magisk canary Patched Boot : Boot11079magisk
Click to expand...
Click to collapse
Any chance could post the boot.img for the latest kb2007 ota
Caltinpla said:
New version: 11.0.8.10
Click to expand...
Click to collapse
Thanks
yes would also like the newest
can anyone supply me with tmobile modem img for 8T... Having serious connections issues. I appreciate it
April 2021 security update
11.0.9.11.KB09CB
OTA Link
https://android.googleapis.com/packages/ota-api/package/caf9f8af0422ecfc8dc56e22dbdd4b0aa5947373.zip
I don't have boot images. Snagged the OTA link by looking at logcat.
hoodred said:
Anyone who needs it
This is T mobile KB2007 boot image (unmodified)
Fresh out of the box
11.1.0.2 KB09CB : boot_11102.img
Security Update November 2020
11.0.6.8 KB09CB: boot_11068.img
OTA Link
https://android.googleapis.com/packages/ota-api/package/52b06537d6cb337f111b279a57b597f9390e6048.zip
Click to expand...
Click to collapse
Thank you! This is exactly what I need to FINALLY (caps for emphasis) get rooted. You're a gentleman and a scholar.
hoodred said:
Anyone who needs it
This is T mobile KB2007 boot image (unmodified)
Fresh out of the box
11.1.0.2 KB09CB : boot_11102.img
Security Update November 2020
11.0.6.8 KB09CB: boot_11068.img
OTA Link
https://android.googleapis.com/packages/ota-api/package/52b06537d6cb337f111b279a57b597f9390e6048.zip
Click to expand...
Click to collapse
Hey there! You uploaded a gold mine! With your permission, may I share this amongst the other groups? You will receive a shout out/due credit for your efforts.
Please let me know and thanks.
How would you install this without magisk?
last time i searched around and got myself in a hard brick situation. please make a guide for this. Noob here
Ashiq.makkar said:
last time i searched around and got myself in a hard brick situation. please make a guide for this. Noob here
Click to expand...
Click to collapse
If you are rooted using Magisk, look here.
Let me know if you need help.
thank you but i tried this and got installation problem when trying to update
For me it worked to do an OTA update with the same version installed.
For example, my phone was rooted to 1.1.7 and I could not update to 1.1.8. So I downloaded 1.1.7 and updated via OTA. After that I could update to 1.1.8 normally. However, the phone must be rooted again.
For the OTA update you have to download the whole OS (https://forum.xda-developers.com/t/...-os-repo-of-nothing-os.4464039/#post-87101175) and then dial *#*#682#*#* in your phone. Now a menu opens in which you can select the OS by browse in the upper right corner. My data has been preserved during the update.
D4yan said:
For me it worked to do an OTA update with the same version installed.
For example, my phone was rooted to 1.1.7 and I could not update to 1.1.8. So I downloaded 1.1.7 and updated via OTA. After that I could update to 1.1.8 normally. However, the phone must be rooted again.
For the OTA update you have to download the whole OS (https://forum.xda-developers.com/t/...-os-repo-of-nothing-os.4464039/#post-87101175) and then dial *#*#682#*#* in your phone. Now a menu opens in which you can select the OS by browse in the upper right corner. My data has been preserved during the update.
Click to expand...
Click to collapse
can you please explain the exact steps?
I'm currently on 1.1.7 rooted with magisk
using some modules and lsposed
Short Guide:
Pretty sure this works across the board with most devices.
If you're doing a OTA and not a manual update:
1. Go into Magisk ~> Uninstall Magisk ~> Restore Images
2. Update via OTA (Do not reboot)
3. Go back into Magisk ~> Install ~> Install to Inactive Slot (After OTA)
4. Reboot
HermitDash said:
Short Guide:
Pretty sure this works across the board with most devices.
If you're doing a OTA and not a manual update:
1. Go into Magisk ~> Uninstall Magisk ~> Restore Images
2. Update via OTA (Do not reboot)
3. Go back into Magisk ~> Install ~> Install to Inactive Slot (After OTA)
4. Reboot
Click to expand...
Click to collapse
tried this. after uninstall magisk by restore images, tried to update via OTA and still getting installation problem
Ashiq.makkar said:
tried this. after uninstall magisk by restore images, tried to update via OTA and still getting installation problem
Click to expand...
Click to collapse
How to manually sideload Nothing OS OTA updates on your Nothing Phone 1
To get the latest Nothing OS update onto your Nothing Phone 1 sooner, you can sideload the update manually. Here's how to do it.
www.xda-developers.com
Manually update yourself to the latest and then reroot.
HermitDash said:
How to manually sideload Nothing OS OTA updates on your Nothing Phone 1
To get the latest Nothing OS update onto your Nothing Phone 1 sooner, you can sideload the update manually. Here's how to do it.
www.xda-developers.com
Manually update yourself to the latest and then reroot.
Click to expand...
Click to collapse
tried manual update and keeps getting different source build is required
I was on 1.1.8 rooted with magisk.
My knowledge isnt the best but my way to update is:
1. Deinstall Magisk.
2. Flash stock boot.img (my version was 1.1.8 so i flash stock boot.img from 1.1.8)
3. Install Update normal over stystem updater
4. Reinstall magsik, done.
I tried it also with restoring magisk and update it over OTA. It worked and it installed, but after I installed Magisk to new slot and restart, it bootlooped 3 times and go back to old version. I think the new Android Versions install the update while restarting. So if you install to new slot with magisk you'll reboot with no OS on the Slot installed. I think the best way is just to uninstall magisk, install update and patch boot img