Does anybody know where the OTA file is being saved in our phone?
I'm downloading the file now but I won't be installing it yet until I put back my stock recovery.
Nevermind. I already found the location. If anyone wants to know, it can be found in data/data/com.zte.zdm/files
Can you confirm the location. I am on 7.1.1 and trying to save the latest OTA (on A2017G). Under /data, I only have a mail directory and nothing else.
piet8stevens said:
Can you confirm the location. I am on 7.1.1 and trying to save the latest OTA (on A2017G). Under /data, I only have a mail directory and nothing else.
Click to expand...
Click to collapse
Is your phone rooted?
otaconremo said:
Is your phone rooted?
Click to expand...
Click to collapse
No, not yet. Am trying to do so via magisk.
piet8stevens said:
No, not yet. Am trying to do so via magisk.
Click to expand...
Click to collapse
I see. I think you can view that location once you're rooted.
piet8stevens said:
No, not yet. Am trying to do so via magisk.
Click to expand...
Click to collapse
Magisk doesn't work on our phone. Use SuperSU.
crashnova said:
Magisk doesn't work on our phone. Use SuperSU.
Click to expand...
Click to collapse
Interesting but I don't get it. The entire Badboyz ROM is based on Magisk. And it runs on my phone. ?
piet8stevens said:
Interesting but I don't get it. The entire Badboyz ROM is based on Magisk. And it runs on my phone. ?
Click to expand...
Click to collapse
They don't use the newest version magisk. Try pulling the zip from their room that contains magisk and flash it. I've tried and had no luck. It would cause the phone to bootloop.
otaconremo said:
Does anybody know where the OTA file is being saved in our phone?
I'm downloading the file now but I won't be installing it yet until I put back my stock recovery.
Click to expand...
Click to collapse
Did you use flashfire or something like that to flash stock recovery? I made a backup in TWRP thought about trying to restore stock recovery with that. I have did it on other phones just not this one.
neo4uo said:
Did you use flashfire or something like that to flash stock recovery? I made a backup in TWRP thought about trying to restore stock recovery with that. I have did it on other phones just not this one.
Click to expand...
Click to collapse
Usually I just use the backup boot and recovery I have when I installed twrp using tenfar's tool. I flash my backup images in twrp. Then, i use adb sideload to upgrade rather than sd method.
otaconremo said:
I see. I think you can view that location once you're rooted.
Click to expand...
Click to collapse
Thank you. But when I am rooted, do I still receive OTAs?
piet8stevens said:
Thank you. But when I am rooted, do I still receive OTAs?
Click to expand...
Click to collapse
yes, you can still receive and download the OTA like I how figured out the location.
However, you can't update using the downloaded OTA file unless you revert your boot and recovery partitions to stock.
otaconremo said:
yes, you can still receive and download the OTA like I how figured out the location.
However, you can't update using the downloaded OTA file unless you revert your boot and recovery partitions to stock.
Click to expand...
Click to collapse
Thank you. I have now a rooted stock phone. I received the OTA, but there is no /data/data. Anything I need to do?
piet8stevens said:
Thank you. I have now a rooted stock phone. I received the OTA, but there is no /data/data. Anything I need to do?
Click to expand...
Click to collapse
Are you using root explorer? I think you need to download the ota update first but don't install.
Also, are trying to update to nougat? Here's the latest b15 rom on the official site.
http://www.zte.com.cn/china/sitecor...?id=B4C0ACE418834F588FED0C72D6046C78#software
otaconremo said:
Are you using root explorer? I think you need to download the ota update first but don't install.
Also, are trying to update to nougat? Here's the latest b15 rom on the official site.
http://www.zte.com.cn/china/sitecor...?id=B4C0ACE418834F588FED0C72D6046C78#software
Click to expand...
Click to collapse
OK, finally got it. Thank you so much.
Related
Hi guys. I have a small question and maybe a problem. I have Nexus 4 rooted with unlocked boot loader, and TWRP installed on it. And as I think with stock rom, because only done everything to root, but nothing else.
Now I have a problem: phone offering to update to 4.3. I press update. It updating and restarting, but after restart it loads TWRP. And what should I do next to finish update? Because I don't know how to make it finish updating with TWRP? What should I do with TWRP to do so? I will be very thankful for any help. Because twice was making update, but still on 4.2.2.
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
You can actually OTA with TWRP.. The device should load into TWRP and complete the update. After the update you will lose TWRP and root
Rizy7 said:
You can actually OTA with TWRP.. The device should load into TWRP and complete the update. After the update you will lose TWRP and root
Click to expand...
Click to collapse
I have seen this in 4.2.2 but not on 4.3. Could you please elaborate a bit more? How did you accomplish this with all these new security policies in 4.3? Thanks.
Mercado_Negro said:
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
Click to expand...
Click to collapse
This is incorrect. The best way to update is download the ota zip from here http://forum.xda-developers.com/showthread.php?t=2145848
Go to twrp recovery flash the ota zip then SU zip v1.51 reboot done. Now you got 4.3 with root and you won't lose your recovery
From my BLACKED OUT N4
spaceman860 said:
This is incorrect. The best way to update is download the ota zip from here http://forum.xda-developers.com/showthread.php?t=2145848
Go to twrp recovery flash the ota zip then SU zip v1.51 reboot done. Now you got 4.3 with root and you won't lose your recovery
From my BLACKED OUT N4
Click to expand...
Click to collapse
Sorry if it sounded incorrect to you but what you just suggested, although it works, it is not an OTA update per definition as far as I know. Please correct me if I'm wrong.
Mercado_Negro said:
Sorry if it sounded incorrect to you but what you just suggested, although it works, it is not an OTA update per definition as far as I know. Please correct me if I'm wrong.
Click to expand...
Click to collapse
When you get the notification saying there is a update on your phone you select it and it downloads flashes the ota zip. What I said is the same thing except you download it and flash it your self and by doing it this way you can flash the SU zip at the same time and not lose root or recovery.
From my BLACKED OUT N4
spaceman860 said:
When you get the notification saying there is a update on your phone you select it and it downloads flashes the ota zip. What I said is the same thing except you download it and flash it your self and by doing it this way you can flash the SU zip at the same time and not lose root or recovery.
From my BLACKED OUT N4
Click to expand...
Click to collapse
Thanks, your post above made me read that thread you linked and while it works, it's not a real OTA (notification from Google or OEMs), but let's not fall into semantics here, the thing is it works and does the job pretty much like a real OTA. Thanks again, I learned (and downloaded) something new today
Mercado_Negro said:
Thanks, your post above made me read that thread you linked and while it works, it's not a real OTA (notification from Google or OEMs), but let's not fall into semantics here, the thing is it works and does the job pretty much like a real OTA. Thanks again, I learned (and downloaded) something new today
Click to expand...
Click to collapse
The zip in the link is from Google. When someone got the notification on there phone they posted the link to the zip it would be the same file if you received it on your phone
From my BLACKED OUT N4
spaceman860 said:
The zip in the link is from Google. When someone got the notification on there phone they posted the link to the zip it would be the same file if you received it on your phone
From my BLACKED OUT N4
Click to expand...
Click to collapse
I know my friend I'm just trying to say that the affirmation "yes, you can update via OTA using a custom recovery" is not valid for someone getting the notification which is the common scenario for most people. Anyways, it's all good :thumbsup:
Mercado_Negro said:
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
Click to expand...
Click to collapse
If I flash the stick recovery will I lose any data such as pics n vids?
rabidrotty said:
If I flash the stick recovery will I lose any data such as pics n vids?
Click to expand...
Click to collapse
No, you won't.
Mercado_Negro said:
No, you won't.
Click to expand...
Click to collapse
Awessome thanks bud. It's been awhile and I forgot if it did or not. You rock.
So my scenario.
I'm on the unlocked B20_boot Build. Rooted. TWRP.
What files are needed to upgrade to B27?
What are the step by step?
I have read through the different threads, but it is confusing at times and rather not make a mistake. It would probably benefit multiple people.
Cheers!
I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.
bhazard451 said:
I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.
Click to expand...
Click to collapse
Change the .up to .zip and try again. This is the safest method to B27.
jkuczera said:
Change the .up to .zip and try again. This is the safest method to B27.
Click to expand...
Click to collapse
Changing it to .zip does not work.
B4oE said:
Changing it to .zip does not work.
Click to expand...
Click to collapse
From stock recovery?
jkuczera said:
From stock recovery?
Click to expand...
Click to collapse
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/downlo...TE A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Maybe verify checksum? That's the method I used (from SD card).
Interesting. ADB Sideload should work if the Apply Update from SD Card method doesn't.
B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.
DrakenFX said:
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.
Click to expand...
Click to collapse
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.
B4oE said:
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.
Click to expand...
Click to collapse
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.
bhazard451 said:
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.
Click to expand...
Click to collapse
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?
swehes said:
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?
Click to expand...
Click to collapse
The best way would be a System Image from ZTE, but we are SOL on that for now.
Hey Guys, Recently i installed viper4arise on my Huawei P8 Lite 2017 using TWRP and theres an error, Music is OKAY except phones default sounds. Like Notification Sounds,Ringtones, Etc.
So i think the best solution is to have a fresh ROM again,
Wondering if i was able to install a new ROM without affecting it. Because my system for now was not fresh (ROOTED,BUSYBOX)
To make it clear. (Sorry for my english)
I am worried if the ROM that i was going to install will be effected of my current ROM? Because its Rooted, Busybox installed, And have a SOUND issue.
Thanks in advance ?
EXE bahotin said:
Hey Guys, Recently i installed viper4arise on my Huawei P8 Lite 2017 using TWRP and theres an error, Music is OKAY except phones default sounds. Like Notification Sounds,Ringtones, Etc.
So i think the best solution is to have a fresh ROM again,
Wondering if i was able to install a new ROM without affecting it. Because my system for now was not fresh (ROOTED,BUSYBOX)
To make it clear. (Sorry for my english)
I am worried if the ROM that i was going to install will be effected of my current ROM? Because its Rooted, Busybox installed, And have a SOUND issue.
Thanks in advance
Click to expand...
Click to collapse
Extract the download, copy te folder "audio" to system/media and your sounds are be back.
https://mega.nz/#!c8c13BTK!N-q2faCyVKCQmzFkLtar9INNN2W7qUQoytzWLlN7qbE
ChinHon said:
Extract the download, copy te folder "audio" to system/media and your sounds are be back.
https://mega.nz/#!c8c13BTK!N-q2faCyVKCQmzFkLtar9INNN2W7qUQoytzWLlN7qbE
Click to expand...
Click to collapse
Good evening ChinHon
May I ask you if I can restore your B164 backup on my C109 (orange all) , reunlock bootloader after the restore and this way have the phone debranded ? Thanks for your help ...
Sorry OP for the off topic...
ChinHon said:
Extract the download, copy te folder "audio" to system/media and your sounds are be back.
https://mega.nz/#!c8c13BTK!N-q2faCyVKCQmzFkLtar9INNN2W7qUQoytzWLlN7qbE
Click to expand...
Click to collapse
okay sir I'll try it
One can never predict this to 100%. With a user it works. With other not.
I have from the Debranding no knowledge.
ChinHon said:
One can never predict this to 100%. With a user it works. With other not.
I have from the Debranding no knowledge.
Click to expand...
Click to collapse
Sad to say but it won't work. I think its not the audio file. its from the Viper4arise drivers thats not compatible for me. Sad to say Viper4Arise dont have a flashable uninstaller.
EXE bahotin said:
Sad to say but it won't work. I think its not the audio file. its from the Viper4arise drivers thats not compatible for me. Sad to say Viper4Arise dont have a flashable uninstaller.
Click to expand...
Click to collapse
the only solution that i think is to have a fresh stock rom again. so my question is, if i flash stock rom using system update. it is possible to be fixed?
ChinHon said:
One can never predict this to 100%. With a user it works. With other not.
I have from the Debranding no knowledge.
Click to expand...
Click to collapse
my current phone is rooted, busybox installed. do i need to uninstall those first. before flashing stock ROM?
the viper4arise drivers was installed on system/lib folder.
can i copy the lib folder from my stock rom?
You must uninstall nothing. Updates ignore this.
Only the stock recovery is necessary.
Try first a factoryreset from stock recovery.
ChinHon said:
You must uninstall nothing. Updates ignore this.
Only the stock recovery is necessary.
Try first a factoryreset from stock recovery.
Click to expand...
Click to collapse
you mean sir its not necessary to uninstall supersu and busybox before flashing a full firmware on system upgrade?
ChinHon said:
You must uninstall nothing. Updates ignore this.
Only the stock recovery is necessary.
Try first a factoryreset from stock recovery.
Click to expand...
Click to collapse
you mean sir i dont need to uninstall supersu or busybox when flashing a full firmware on system upgrade?
Unroot is not necessary.
ChinHon said:
Unroot is not necessary.
Click to expand...
Click to collapse
thank you sir. I'll try it
ChinHon said:
Unroot is not necessary.
Click to expand...
Click to collapse
do you think sir. flashing using system upgrades can fix this issue? or the viper drivers will deleted. or Its just stick on my system ?
I think the drivers are not the reason, but not complete firmware. Making the update.
ChinHon said:
I think the drivers are not the reason, but not complete firmware. Making the update.
Click to expand...
Click to collapse
do you think i was able to install full firmware via system upgrade again? my current build number was B123 and the firmware that is only available on PRA LX2 was B123.
I was able to flash B123 before, when my build number was B160
This becomes nothing. You can get full firmware only as OTA update/ upgrade. Differently it goes only like in mine rootthread is described.
ChinHon said:
This becomes nothing. You can get full firmware only as OTA update/ upgrade. Differently it goes only like in mine rootthread is described.
Click to expand...
Click to collapse
i was able to get full ota. using firmware finder then make a proxy settings to flash on system upgrade
I currently on Oreo Beta 2, but my phone is rooted. Is there any way to update to Beta 3 and root again without losing all my data? I'm a bit of a noob to both rooting and android. Is there a way to back it all up and just import it back in or something? Thanks in advance. :good:
ecstaticnoodle said:
I currently on Oreo Beta 2, but my phone is rooted. Is there any way to update to Beta 3 and root again without losing all my data? I'm a bit of a noob to both rooting and android. Is there a way to back it all up and just import it back in or something? Thanks in advance. :good:
Click to expand...
Click to collapse
Yes. No problem at all...
1. Install twrp-11 via Fastboot
2. ADB sideload ROM
3. Install TWRP again via Fastboot
4. Flash boot.img Oreo 3 in recovery
5. Flash Magisk 15.3 afterwards
ecstaticnoodle said:
I currently on Oreo Beta 2, but my phone is rooted. Is there any way to update to Beta 3 and root again without losing all my data? I'm a bit of a noob to both rooting and android. Is there a way to back it all up and just import it back in or something? Thanks in advance. :good:
Click to expand...
Click to collapse
Yes.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Use the Beta 3 here. Flash via fastboot.
Root the B3 like you did the B2. No data loss.
I did it yesterday.
vergilbt said:
Yes. No problem at all...
1. Install twrp-11 via Fastboot
2. ADB sideload ROM
3. Install TWRP again via Fastboot
4. Flash boot.img Oreo 3 in recovery
5. Flash Magisk 15.3 afterwards
Click to expand...
Click to collapse
You don't even have to sideload it if you're using the factory zip. Just flash it like you would any other ROM in TWRP.
But it's an successful way...
We all know that different methods possible...
I was just offering a little less convoluted way of doing it. I didn't realize the king had spoken.
King is dead... Where is the king?
[emoji6]
I seem to be stuck after step 1
I tried to flash via twrp and got the following error:
Invalid zip file format!
Error installing zip file '/sdcard/OPM1.170911.254_back_to_stock .zip'
So i tried to sideload via adb and got an error in there too
opening 'OPM1.170911.254_back_to_stock.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Any help?
morphius88 said:
I seem to be stuck after step 1
I tried to flash via twrp and got the following error:
Invalid zip file format!
Error installing zip file '/sdcard/OPM1.170911.254_back_to_stock .zip'
So i tried to sideload via adb and got an error in there too
opening 'OPM1.170911.254_back_to_stock.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Any help?
Click to expand...
Click to collapse
If you want to flash it in TWRP, just use the factory zip from the Essential website.
https://www.essential.com/developer/beta-builds
spotmark said:
If you want to flash it in TWRP, just use the factory zip from the Essential website.
https://www.essential.com/developer/beta-builds
Click to expand...
Click to collapse
will that wipe my data?
morphius88 said:
will that wipe my data?
Click to expand...
Click to collapse
Nope.
spotmark said:
Nope.
Click to expand...
Click to collapse
OK Thanks, I already had the file downloaded earlier today, trying it now. Fingers crossed.
tech_head said:
Yes.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Use the Beta 3 here. Flash via fastboot.
Root the B3 like you did the B2. No data loss.
I did it yesterday.
Click to expand...
Click to collapse
When I try to use that zip file it tells me that it is an invalid zip file in twrp... what should I do?
ecstaticnoodle said:
When I try to use that zip file it tells me that it is an invalid zip file in twrp... what should I do?
Click to expand...
Click to collapse
Are you using the file you got from essential website?
Spotmark said it has to be from there not the one from xda
morphius88 said:
Are you using the file you got from essential website?
Spotmark said it has to be from there not the one from xda
Click to expand...
Click to collapse
Whoops. I was hitting the wrong one lol let me try it again.
morphius88 said:
Are you using the file you got from essential website?
Spotmark said it has to be from there not the one from xda
Click to expand...
Click to collapse
I don't know if it makes a difference (don't see why it would), but I renamed it OB3 before I put it on my phone's storage.
Spotmark, I was able to flash the update from the essential website via twrp. Everything else went smoothly after that and I am now back in and rooted. All the data is here as well.
Thank you for your help.
morphius88 said:
Spotmark, I was able to flash the update from the essential website via twrp. Everything else went smoothly after that and I am now back in and rooted. All the data is here as well.
Thank you for your help.
Click to expand...
Click to collapse
Glad I could be of assistance. :highfive:
So this week i hadn't time enough to install the august update since my phone is rooted so i decided to do it now. What i did before trying to download the update :
1.Deleted all magisk modules that i had then rebooted
2.Unistalled magisk using restore image then rebooted
3.Went to sys update downloaded and it says installation failed
What do to? I'm not rooted now and i don't have twrp installed.
PS. don't want to install it via fastboot/miflash
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
emiljano539 said:
PS. don't want to install it via fastboot/miflash
Click to expand...
Click to collapse
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
sipollo said:
If you don't want to use Miflash (Why ?) you can boot temporary TWRP and flash .zip here:
https://forum.xda-developers.com/showpost.php?p=77353883&postcount=542
Click to expand...
Click to collapse
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
emiljano539 said:
Do i lose my data if i flash this via twrp?
Idk i don't really trust miflash
Click to expand...
Click to collapse
You won't lose your data.
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
flashed the stock boot image tried to install it but again it shows that error , i guess the only thing i can do is to flash it manually via fastboot/miflash
sipollo said:
You won't lose your data.
Click to expand...
Click to collapse
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
emiljano539 said:
Okay thanks, do i have to remove the magisk and flash the stock boot.img or it doesn't matter?
Click to expand...
Click to collapse
It doesn't matter. You'll have to reinstall Magisk (if you want to).
sipollo said:
It doesn't matter. You'll have to reinstall Magisk (if you want to).
Click to expand...
Click to collapse
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
emiljano539 said:
which one should i install from them because there are 2 tissot-T files ( for twrp)
"tissot-T-OPM1.171019.026.8.8.23.zip" or "tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip" ?
Click to expand...
Click to collapse
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
sipollo said:
tissot-T-OPM1.171019.026.V9.6.5.0.ODHMIFE.zip
The other file is the latest beta.
Click to expand...
Click to collapse
I installed the zip from twrp and now after reboot i am stucked in bootloop now i can't even boot into twrp. What to do?
After i flashed it in the end says:
Failed to mount /system Invalid argument
Which TWRP did you use?
sipollo said:
Which TWRP did you use?
Click to expand...
Click to collapse
the official one. what version should i use?
its funny now that i flashed the stock rom via mi flash tool and now again the installation shows error..
ludditefornow said:
Follow this guide in future. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
To fix your problem now, find a stock boot image for your update version you are currently on and flash it.
Click to expand...
Click to collapse
I'm facing same issue and I was following the guide.
Same here, can't install set Ota, even after remove magisk.
Other thing, cell won't show screen to put pin to boot, previous pin of sim so I think encryption is disable!? Any idea?