Hello!
So i want to root my NB1 but from what i read these couple of days, TWRP is incompatible with September and October security patch. I know that May and June are so my question is:
When on my slot A is the October patch and on my slot B is the September one how can i downgrade the B slot to May??? It would be really helpful if somebody explain that. I've tried to BOOT ( not flash) May prerooted img but the phone is stuck on powered by android logo.
U say twrp working in september security. So change ur phone to slot B.
Go to download mode. And use command
Fasboot reboot booloader (for enter download mode again)
Fastboot boot twrp
If it not boot to twro this mean twrp not comfortable with september.
If u want downgrade use ost tool 6.0.4 or ntool
To downgrade, here's a description:
https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
You will flash then Oreo SW with may security patch where TWRP works fine.
Use this workaround for flashing Oreo software with OST 6.0.4
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Other possibility would be to change slot assuming that the other one is on August security patch
Last but not least is to use patched boot img, the description is also on XDA forum in Nokia 8 section
czupyt said:
To downgrade, here's a description:
https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
You will flash then Oreo SW with may security patch where TWRP works fine.
Use this workaround for flashing Oreo software with OST 6.0.4
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Other possibility would be to change slot assuming that the other one is on August security patch
Last but not least is to use patched boot img, the description is also on XDA forum in Nokia 8 section
Click to expand...
Click to collapse
Thank you i'll try that.
Any feedback?
Mo4o293 said:
Thank you i'll try that.
Click to expand...
Click to collapse
I met exactly the same situation like the yours. Slot A on September and Slot B on October SP.
I cannot root it with any method in the forum on both the two slots. ( TWRP/ pre-rooted boot)
To downgrade, both the OST LA 6.12 /6.04 cannot downgrade my nokia TA-1052 with Sep/Oct SP.
Depression... I cannot live with an unrooted phone...:crying::crying:
Edit: finally rooted it. Solution: https://forum.xda-developers.com/nok...t3848390/page6, #58
smallerxie said:
I met exactly the same situation like the yours. Slot A on September and Slot B on October SP.
I cannot root it with any method in the forum on both the two slots. ( TWRP/ pre-rooted boot)
To downgrade, both the OST LA 6.12 /6.04 cannot downgrade my nokia TA-1052 with Sep/Oct SP.
Depression... I cannot live with an unrooted phone...:crying::crying:
Click to expand...
Click to collapse
My slot A is with October patch and B is with September. Also i dont want to try OST LA because this phone is my daily driver and i already have my old rooted phone. If you want to root your phone we need to wait for TWRP update. Really hope the maintainer update it soon to work with Sep and Oct patches.
Mo4o293 said:
My slot A is with October patch and B is with September. Also i dont want to try OST LA because this phone is my daily driver and i already have my old rooted phone. If you want to root your phone we need to wait for TWRP update. Really hope the maintainer update it soon to work with Sep and Oct patches.
Click to expand...
Click to collapse
I finally rooted it!
Here is my solution: https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390/page6, #58
smallerxie said:
I finally rooted it!
Here is my solution: https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390/page6, #58
Click to expand...
Click to collapse
So you are saying that i have to use "fastboot flash boot patched.img" instead of "fastboot boot patched.img"?
Edit: soo.....BRO YOU ARE MY GOD. OMG IT WORKS . THANK YOU A LOT AND SRY FOR THE CAPS LOCK. The wifi works perfectly and i'm rooted now!
Mo4o293 said:
So you are saying that i have to use "fastboot flash boot patched.img" instead of "fastboot boot patched.img"?
Edit: soo.....BRO YOU ARE MY GOD. OMG IT WORKS . THANK YOU A LOT AND SRY FOR THE CAPS LOCK. The wifi works perfectly and i'm rooted now!
Click to expand...
Click to collapse
You are welcome
Related
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Mae7 said:
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Click to expand...
Click to collapse
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Mae7 said:
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Click to expand...
Click to collapse
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Jakets said:
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Click to expand...
Click to collapse
Not sure. It's probably disabled for a custom ROM.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Fat Rat Bastard said:
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Click to expand...
Click to collapse
Yeah I actually ended up going with a V17 firmware.
Title says all. This is for the American Retail variant. Does not include Oreo.
Glad to see that Moto is being consistent with Security patches though!
Edit:. I meant April 1st 2018!
This is for all varients
reteu,retbr,Retin also got updates
Sent from my Moto G5S Plus using XDA Labs
Yet to be seen in retapac though
Adi5 said:
This is for all varients
reteu,retbr,Retin also got updates
Click to expand...
Click to collapse
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
JaggedPill said:
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
Click to expand...
Click to collapse
I didn't had notification,now flashed custom rom
Flash full firmware for ur software channel
Retid here, still no updates
Got it..retin software channel.
In retla was not released
April Patch also released for retapac ?
I only just got 116-48-12 yesterday on retus, so I'm not gonna hold my breath.
you can edit the thread title by editing your post and pressing "go advanced"
Meanwhile retgb is still on October 2017. This is the last time I buy Motorola.
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
championc said:
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
Click to expand...
Click to collapse
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Juancasa14 said:
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Click to expand...
Click to collapse
U can update with unlocked bootloader. Only without mods like root or twrp
Adi5 said:
U can update with unlocked bootloader. Only without mods like root or twrp
Click to expand...
Click to collapse
Yeah I know, sorry if I didn't make myself clear, thanks for explaining
Championc were you able to recover your phone?
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
jojojones said:
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
Click to expand...
Click to collapse
What I did (might be an easier way but this was fast and easy):
1) Uninstall/remove Magisk.
2) Re-flash firmware over current system but don't do 'fastboot erase userdata'
3) Boot into your system and take all the OTA's
4) Re-install Magisk via TWRP
Took about 10 minutes. Longest part was waiting for OTA's to install.
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
Did not work for me. Nothing has so far.
jojojones said:
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Click to expand...
Click to collapse
Use this guide:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Remove command "fastboot erase userdata" from script flash-all.bat/flash-all.sh.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I've tried this, and it didn't work. Ended up having to boot into TWRP, uninstall Magisk, and then reboot. Haven't bothered trying to update since I attempted that.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
tjololo12 said:
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
Click to expand...
Click to collapse
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
ptn107 said:
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
Click to expand...
Click to collapse
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
tjololo12 said:
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
Click to expand...
Click to collapse
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Comby_sk said:
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Click to expand...
Click to collapse
Thanks, the rom is exactly what I was looking for, I just wasn't sure which one to use. I'd hate to install the wrong rom and mess something up.
EDIT: I did get a chance to try it and you're correct, there is no way to install an OTA to this device without fully reflashing the stock rom, taking the OTA, then installing Magisk. I tried the following steps:
1. Flash ROM given from androidfilehost
2. Reboot, wait for OTA notification
3. Boot to bootloader
4. use fastboot to temporarily boot twrp
5. flash magisk 17.1 zipfile
6. reboot to system, verify that magisk/root is installed
7. Uninstall magisk using magisk manager "Restore Images" as given in the tips.md file
8. Take OTA
the OTA still failed, so even though TWRP wasn't installed and it was still the stock recovery, I was unable to install the OTA. Shame, it'd be nice if we could get this to work, but oh well.
Hi,
I just unlocked my X4 (XT1900-2) to try Magisk and all worked good.
Now, when I wanted to revert, I just installed the stock image using fastboot and adb.
After installing them and re-locking my bootloader I was not able to change my system status to Official(I installed Ryzen Kernel before).
Nor I am able to install any OTA to change it to Official, can anyone tell me how can I install OTA update and change my status to Official and be stock again.
Please help!!!
Thanks in advance,
Divanshu Chauhan
Can you provide the information of system flashed because if correct system has been flashed then the status should change to official. Try reflashing the system.
Shreyas17 said:
Can you provide the information of system flashed because if correct system has been flashed then the status should change to official. Try reflashing the system.
Click to expand...
Click to collapse
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
AgentDivanshu said:
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
Click to expand...
Click to collapse
The system seems to be correct but its not official signed image so try to reflash the system or factory reset or try to get latest system signed image flash it and then check the status.
But many users have faced this problem even after flashing stock rom and relocking the bootloader they were unable to install ota.
Shreyas17 said:
The system seems to be correct but its not official signed image so try to reflash the system or factory reset or try to get latest system signed image flash it and then check the status.
But many users have faced this problem even after flashing stock rom and relocking the bootloader they were unable to install ota.
Click to expand...
Click to collapse
Tried it again, but was not able to get it back to official.
Any other ideas??
:crying::crying:
Should I try flashing this image -
https://androidfilehost.com/?fid=746163614322270003
AgentDivanshu said:
Tried it again, but was not able to get it back to official.
Any other ideas??
:crying::crying:
Should I try flashing this image -
https://androidfilehost.com/?fid=746163614322270003
Click to expand...
Click to collapse
You can try but make sure this stock rom is for xt1900-2 ,the other option is to wait till motorola releases signed images for the device ? or to visit the authorized service center they might flash the system and give your device back in official state.
Shreyas17 said:
You can try but make sure this stock rom is for xt1900-2 ,the other option is to wait till motorola releases signed images for the device ? or to visit the authorized service center they might flash the system and give your device back in official state.
Click to expand...
Click to collapse
Well, I can't take device to authorised service centre because my warranty is void now.
Can you tell me the estimated time till motorola releases signed images for my device?
AgentDivanshu said:
Well, I can't take device to authorised service centre because my warranty is void now.
Can you tell me the estimated time till motorola releases signed images for my device?
Click to expand...
Click to collapse
Its upto motorola when to release the signed images for the device but you can try to flash system from the link
https://androidfilehost.com/?w=files&flid=229118
Select the payton image that has latest build and for safety i would suggest unlock your bootloader and try to flash the system .
Try to flash PAYTON_OPWS28.46-21-9 from the link it might help.
Shreyas17 said:
Its upto motorola when to release the signed images for the device but you can try to flash system from the link
https://androidfilehost.com/?w=files&flid=229118
Select the payton image that has latest build and for safety i would suggest unlock your bootloader and try to flash the system .
Try to flash PAYTON_OPWS28.46-21-9 from the link it might help.
Click to expand...
Click to collapse
My device hasn't got the 8.1 update, I was on Oreo when I rooted. After installing the flash again, I am getting OTA Update but error is show.
Error attached as screenshot
[Deleted]
AgentDivanshu said:
My device hasn't got the 8.1 update, I was on Oreo when I rooted. After installing the flash again, I am getting OTA Update but error is show.
Error attached as screenshot
Click to expand...
Click to collapse
Till now user of xt1900-2 have not received 8.1 all are on 8.0.0 latest update is of 1 october 2018 security patch.
Can you tell on what security patch is your device running.
Shreyas17 said:
Till now user of xt1900-2 have not received 8.1 all are on 8.0.0 latest update is of 1 october 2018 security patch.
Can you tell on what security patch is your device running.
Click to expand...
Click to collapse
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
AgentDivanshu said:
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
Click to expand...
Click to collapse
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
AgentDivanshu said:
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
Click to expand...
Click to collapse
so i guess you will have to wait till firmware is released with latest security patch because you have broken ota so only option left is to update device using fastboot . Did you get any error like pre-validation failed while returning back to stock ?
You won`t be able to install ota until your device status changes from modified to official.
Shreyas17 said:
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
so i guess you will have to wait till firmware is released with latest security patch because you have broken ota so only option left is to update device using fastboot . Did you get any error like pre-validation failed while returning back to stock ?
You won`t be able to install ota until your device status changes from modified to official.
Click to expand...
Click to collapse
I get error like system is modified/corrupt.
Should I flash xt1900-7, xt1900-6 or xt1900-1 version?
Also when I flashed xt1900-1 version, it showed me something like 'Mode has been set to logging' on Moto Logo
AgentDivanshu said:
I get error like system is modified/corrupt.
Should I flash xt1900-7, xt1900-6 or xt1900-1 version?
Also when I flashed xt1900-1 version, it showed me something like 'Mode has been set to logging' on Moto Logo
Click to expand...
Click to collapse
I have seen video tutorials in which they flashed android one firmware on retail but you will have to keep bootloader unlocked .But i would suggest you to flash custom rom if you keep bootloader unlocked atleast you will get additional features and once moto x4 recieves android 9 update then you might get official system image to flash via fastboot and return back to stock. Search on youtube for tutorials it might help you ?
Shreyas17 said:
I have seen video tutorials in which they flashed android one firmware on retail but you will have to keep bootloader unlocked .But i would suggest you to flash custom rom if you keep bootloader unlocked atleast you will get additional features and once moto x4 recieves android 9 update then you might get official system image to flash via fastboot and return back to stock. Search on youtube for tutorials it might help you ?
Click to expand...
Click to collapse
But how will I update to Android Pie if installation fails again??!
Will Motorola release factory image for xt1900-2 then?
AgentDivanshu said:
But how will I update to Android Pie if installation fails again??!
Will Motorola release factory image for xt1900-2 then?
Click to expand...
Click to collapse
They might release the system images till then or you might get stock rom zip available the way oreo stock rom is available now so you will be able to update your device to android 9 via fastboot not by ota ?
AgentDivanshu said:
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
Click to expand...
Click to collapse
Hey. I used this rom as well to move back to stock but OTA's work fine for me. Currently on the 1 Oct patch. I still get the warning message during bootup even if I relock it. But apart from that everything else works fine.
The only thing different I have done is use the flash script from the below linked thread. Not that it should have made any difference but you guys might as well try and see.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
varunbala said:
Hey. I used this rom as well to move back to stock but OTA's work fine for me. Currently on the 1 Oct patch. I still get the warning message during bootup even if I relock it. But apart from that everything else works fine.
The only thing different I have done is use the flash script from the below linked thread. Not that it should have made any difference but you guys might as well try and see.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Click to expand...
Click to collapse
Have you re-locked your bootloader after flashing this script?
Did you use Linux or Windows?
I tried relocking but then the warning changes to that of a unsigned system image being used. Don't remember the exact wordings. So then I moved to back to unlocked bootloader.
I am using windows.
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
matheusgoes said:
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
Click to expand...
Click to collapse
Try flashing stock ROM, it worked for me
Firexxe69 said:
Try flashing stock ROM, it worked for me
Click to expand...
Click to collapse
I've never flash any ROM. Do you have any tutorial I can follow?
matheusgoes said:
I've never flash any ROM. Do you have any tutorial I can follow?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Firexxe69 said:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Click to expand...
Click to collapse
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Maharram said:
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Click to expand...
Click to collapse
I never tried it, but when i'm on december patch, i flashed the december patch, then update it from system update. Make sure to backup your data because it may erase your data.
I tried to flash december s.p.
Got the message "Flashing error bluetooth_a" mi flash tool. Do someone know how to solve it?