I am using magisk systemless and I followed the guide carefully to make it survive the OTA. Unfortunately, it doesn't pass step 1 when installing. I did not touch the system the entire time I was using magisk. What other options do I have for me to have the december patch? Thanks.
Follow my guide, might able to help you
https://forum.xda-developers.com/showpost.php?p=74790371&postcount=83
Press thanks if it helped you.
Just flash full november rom (fastboot rom) using mi flash tool, don't forget to tick save user data. December update should push through without any probs now
wulfe13 said:
Just flash full november rom (fastboot rom) using mi flash tool, don't forget to tick save user data. December update should push through without any probs now
Click to expand...
Click to collapse
just now flashed full november fastboot rom too , but i cant see to get an ota update . i need to do what ? now i have unlocked bootloader , magisk 14.5 . whenever i sideload ota.zip (dec ota) it cause failed with error code 255 if i remember correctly.
myself379 said:
Follow my guide, might able to help you
https://forum.xda-developers.com/showpost.php?p=74790371&postcount=83
Press thanks if it helped you.
Click to expand...
Click to collapse
Thanks for the tip. Will I sideload the october patch using the stock recovery? Or is it possible to just flash the novemver stock boot.img via fastboot.
wulfe13 said:
Just flash full november rom (fastboot rom) using mi flash tool, don't forget to tick save user data. December update should push through without any probs now
Click to expand...
Click to collapse
Downloading now.
wulfe13 said:
Just flash full november rom (fastboot rom) using mi flash tool, don't forget to tick save user data. December update should push through without any probs now
Click to expand...
Click to collapse
Can I get a link of november rom? Can find it using google. Thanks.
cyberangel22k said:
Can I get a link of november rom? Can find it using google. Thanks.
Click to expand...
Click to collapse
https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
pihpih95 said:
just now flashed full november fastboot rom too , but i cant see to get an ota update . i need to do what ? now i have unlocked bootloader , magisk 14.5 . whenever i sideload ota.zip (dec ota) it cause failed with error code 255 if i remember correctly.
Click to expand...
Click to collapse
after flashing full november rom, you should do normal OTA update . do that before installing magisk again to avoid complications
wulfe13 said:
after flashing full november rom, you should do normal OTA update . do that before installing magisk again to avoid complications
Click to expand...
Click to collapse
I will reflash November rom again later and will give u a feedback if it is work .
Mi flash does not work on my pc .
Edit: anyone knows how to fix this?
Aman301582 said:
Mi flash does not work on my pc .
Edit: anyone knows how to fix this?
Click to expand...
Click to collapse
I'm not sure why it doesn't work on your PC, but maybe you could place the tissot_images folder on drive C root directory.
December updates ruined my google apps , playstore shows the error {rh-01}, play services cannot be accessed by most of the games, and i cannot backup my data any more..
sreenucr7 said:
December updates ruined my google apps , playstore shows the error {rh-01}, play services cannot be accessed by most of the games, and i cannot backup my data any more..
Click to expand...
Click to collapse
Just wondering, did you clear the google framework services data to force the OTA update arrival?
_mysiak_ said:
Just wondering, did you clear the google framework services data to force the OTA update arrival?
Click to expand...
Click to collapse
Yea I did,
sreenucr7 said:
Yea I did,
Click to expand...
Click to collapse
So this is the reason for all your problems you described...
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
sreenucr7 said:
Yea I did,
Click to expand...
Click to collapse
So it's not the update which caused the problem, but it was you Clear data of play store, play store services and all apps which are broken and set them from scratch. If it won't help, remove and add your google account again. With bit of luck you'll get it working again.
_mysiak_ said:
So it's not the update which caused the problem, but it was you Clear data of play store, play store services and all apps which are broken and set them from scratch. If it won't help, remove and add your google account again. With bit of luck you'll get it working again.
Click to expand...
Click to collapse
Yea it worked clearing cache helped
Aman301582 said:
Mi flash does not work on my pc .
Edit: anyone knows how to fix this?
Click to expand...
Click to collapse
MiFlash is basically a GUI for the batch scripts that come with the ROM when downloaded from MIUI.
You can download the ROM from here and follow the flashing guide linked there or you can do all that work manually.
However, that requires being familiar with command line, fastboot, Windows batch scripts, etc. Here is how to do it, in short:
Install Android's platform tools;
Install the USB drivers required for fastboot;
Download the ROM archive and extract it, and its content;
Inspect and run flash_all_except_storage.bat from the extracted ROM.
I get this error with the same setup (from November update). Does bootloader need to be locked for otas to work? I've tried uninstalling magisk and rebooting to no avail.
Related
hello guys
i am not getting any update after 7.10.14
can any one also facing it
i am rooted with magisk and also twrp is installed
i have also done no. of tweaks on my device
is there any solution to solve it
Red_Man 898 said:
hello guys
i am not getting any update after 7.10.14
can any one also facing it
i am rooted with magisk and also twrp is installed
i have also done no. of tweaks on my device
is there any solution to solve it
Click to expand...
Click to collapse
Same this side. I can see there is an update from the notifications. When I am clicking it.. its not opening.
Sent from my ONEPLUS A3003 using Tapatalk
When you install twrp, forget about updates. You need to flash full stock image using miflash application on Windows. I had the same problem, flashed stock images using miflash and update worked! I did not even lose my phone data.
Edit: Just boot into twrp to flash magisk. Don't flash twrp or system update will fill after downloading.
I was in the same situation (even if i've never flashed twrp).
Solved by flashing 17.10.30 Rom (after that I got the update)
Cheers.
tonycapuozzo said:
I was in the same situation (even if i've never flashed twrp).
Solved by flashing 17.10.30 Rom (after that I got the update)
Cheers.
Click to expand...
Click to collapse
How do I flash this version now ? I am already on 17.10.30
ProudRed said:
How do I flash this version now ? I am already on 17.10.30
Click to expand...
Click to collapse
Well...try re-flashing the same image or wait for the full November Rom.
Cheers
tonycapuozzo said:
Well...try re-flashing the same image or wait for the full November Rom.
Cheers
Click to expand...
Click to collapse
Just the boot image ? Where do I get the extracted boot image ?
If you have done multiple tweaks, I suppose that those were done to system directly. In such case you'll need to flash system partition as well. Both are included in full ROM, just extract them from archive http://en.miui.com/download-333.html.
https://www.youtube.com/watch?v=5Ozdhl-JdvU
give it a try.
If not getting updates (like: Your phone is already update) try to clean Google Service Framework app data from Settings - App - 3 dots on corner - Show system apps
If your device is rooted, then make clean installation of os. There will be ota update.
I am stock not rooted nor unlocked. Ad still stuck no more updates for me
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:
Hey everyone, I need some help.
I have Magisk installed, and wanted to preserve root acces throughout the update (may security patch, ~80MB). I used this guide to do it, uninstalled Magisk, installed it on 2nd slot during phase 2, rebooted: bootloop. Stuck in an endless cycle: the kernel loads, but always reboots during the andorid one boot animation.
I'm looking for a way to make it functional while not losing my data, or a way to copy my data to a PC before flashing.
What can I do now?
Thanks in advance.
Flash stock ROM
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Indiangautam said:
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Click to expand...
Click to collapse
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
droidx8 said:
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
Click to expand...
Click to collapse
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Indiangautam said:
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Click to expand...
Click to collapse
Well let's not do that then, there could be another way... Thanks anyway!
droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
As you wish....but if want to try my process then definitely your phone will bootup
droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
You can choose to not wipe your data.
It's the "flash all except storage.bat"
You can download the last firmware here
http://en.miui.com/getrom.php?r=333&m=yes&app=false
You must have fastboot on your PC windows or Linux
So if you have a Windows just search how to install fastboot on Windows there's some great one on xda
Unzip the firmware open the flash all except storage bat
Remove both lines that contains
-OEM unlock
-OEM lock
Otherwise your data will be wiped and as you use magisk you want an unlocked bootloader
Open a powershell windows where the .bat file is
Then type without the quotes
"./flash_all_except_storage.bat"
Flashing procedure will take a few minutes on system partition but don't freak out
Once it's done reboot you'll be on 9.5.11 ROM version
You'll receive a 60mb ota to have the last one which is 9.11.13
You can boot TWRP to flash magisk now
And on next update download the last firmware
9.5.13 should be on the first link I gave you (there is always a delay between ota that are just patch and a full firmware that contains all the files)
Flash the boot.img or just reflash the ROM like above apply ota and reflash magisk
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Dead-neM said:
You can choose to not wipe your data.
It's the "flash all except storage.bat"
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Click to expand...
Click to collapse
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
droidx8 said:
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
Click to expand...
Click to collapse
Really nice to hear. Have fun with this little Beasty device
The October Security Patch for those on OPP28.85-16 has come out.
You can sideload the OTA if you're on untouched OPP28.85-16 or flash the TWRP zip if you've have TWRP.
Edit:
For the TWRP flashable zip, check this thread .
I removed it from this thread after I realized it's not OPPS28.85-16-2 but OPPS28.85-13-2
Notice that if you're on retca or reteu channel, or any other channel where you've got an Oreo version other than OPP28.85-16, then you should either wait for the OTA notification to pop up on your phone or flash the TWRP flashablr zip.
THIS OTA ZIP IS ONLY COMPATIBLE WITH OPP28.85-16. FLASHING IT OVER OPP28.85-13 OR ANY OTHER VERSION WILL HARD BRICK YOUR DEVICE
That is because this OTA patches the device's gpt table. So if you're not on OPP28.85-16 and sideload this= :crying::crying: goodbye Cedric
Downloads:
OTA : https://drive.google.com/file/d/1PHJqkdFgS-erSJ0jc54cTWvUrNRQWfZJ/view?usp=drivesdk
PS I removed the TWRP link, it's actually for OPPS28.85-13-2
Sorry for the bad edition, I'm sleepy and don't have a computer around.
Flashed the twrp ota by Nzedpred yesterday and it's working like a charm. Previously I was on OPP28.85-16
Hi, i'm having some troubles to make my moto g5 identified when i'm gonna sideload the ota. how can I solve it?
merlinolillo said:
Flashed the twrp ota by Nzedpred yesterday and it's working like a charm. Previously I was on OPP28.85-16
Click to expand...
Click to collapse
Twrp Dirty flash works or i should do clean install?
the TWRP-Link shows a ...13-2, not a ...16-2, is this correct?
can not update from ota package.
every time I check for updates, Moto Update doesn't recognize local packages. Had to apply patch via Recovery
iKnocks said:
Hi, i'm having some troubles to make my moto g5 identified when i'm gonna sideload the ota. how can I solve it?
Click to expand...
Click to collapse
Have you installed the usb drivers from Motorola's website?
If you didnt, then do it, but if you've already done so and still the phone is not detected, type %tmp% on your file explorers address bar (assuming you're on windows) and and then search for .msi fules. Find the .msi correspondent to your Motorola drivers and install it mannualy.
ahmedAZ said:
Twrp Dirty flash works or i should do clean install?
Click to expand...
Click to collapse
If you were on stock a dirty flash works, if you were on a custom ROM you'll get lots of bugs
kare_meesner said:
the TWRP-Link shows a ...13-2, not a ...16-2, is this correct?
Click to expand...
Click to collapse
Yeah it's indeed OPPS28.85-13-2, Ill make a separate thread for it
PsyClip-R said:
can not update from ota package.
every time I check for updates, Moto Update doesn't recognize local packages. Had to apply patch via Recovery
Click to expand...
Click to collapse
No, that's not the way you do it. You have to install Motorola usb drivers, then install ADB/platform-tools, then enable usb debugging and connect the to the pc using the usb cable.
After you've done that you'll type adb devices and you should see your phone's serial number. If that shows up, type adb sideload ota-filename.zip
ahmedAZ said:
Twrp Dirty flash works or i should do clean install?
Click to expand...
Click to collapse
Yes, I made a dirty flash and it works perfectly
merlinolillo said:
Yes, I made a dirty flash and it works perfectly
Click to expand...
Click to collapse
you dont have any problems with gmail sync?
OTA Side load not working for me. Get Error 7.
Downloaded earlier that day the twrp File and installed, but then I saw that this was -13-2. Completely delete my G5 again and installed 85-16 again.
Now downloaded the OTA File, in TWRP used ADB Sideload (adb devices showed my G5) but ended with Error 7.
freeZbies said:
Have you installed the usb drivers from Motorola's website?
If you didnt, then do it, but if you've already done so and still the phone is not detected, type %tmp% on your file explorers address bar (assuming you're on windows) and and then search for .msi fules. Find the .msi correspondent to your Motorola drivers and install it mannualy.
Now it worked, thank you btw
Click to expand...
Click to collapse
woozie.2007 said:
you dont have any problems with gmail sync?
Click to expand...
Click to collapse
Not at all. Gmail sync is working fine at me
merlinolillo said:
Not at all. Gmail sync is working fine at me
Click to expand...
Click to collapse
for me doesnt, is syncing after half an hour or even one hour, but if i unlock the screen is syncing in few seconds
can you upload full oreo stock rom after october patch?
I need it to relock bootloader , other roms not working
Street_Fighter said:
can you upload full oreo stock rom after october patch?
I need it to relock bootloader , other roms not working
Click to expand...
Click to collapse
I haven't heard of that being available out there, but u can relock using the firmware provided in this thread and apply this OTA afterwards, that way you'll have a relocked bootloader and will be in the latest security patch, although if you're not on retus/retbr/retin I recommend you to find a firmware specific to your channel (even if it's an old one) and relock your bootloader using it, and then apply the OTA's that pop up on your notifications, so as not to relock the bootloader with a firmware from another channel, which will prevent you from receiving future otas.
But if you're on one of the three quoted channels you should be fine when fastbooting this firmware.
this update fix the wifi tethering of third-party applications?
Hello all,
I am several versions behind on my P2XL simply because it is rooted and I have to it manually. Haven't had time to do it but I know I am missing out on several security updates that seem to be rather important so it is time to update. I would prefer not to wipe my phone; however, since j am so many versions behind maybe it's better to do so?
Curious am I able to just install the February update over my current October build or do I have to push each update to the device before moving to the next?
Please let me know, thanks so much
cwburns32 said:
Hello all,
I am several versions behind on my P2XL simply because it is rooted and I have to it manually. Haven't had time to do it but I know I am missing out on several security updates that seem to be rather important so it is time to update. I would prefer not to wipe my phone; however, since j am so many versions behind maybe it's better to do so?
Curious am I able to just install the February update over my current October build or do I have to push each update to the device before moving to the next?
Please let me know, thanks so much
Click to expand...
Click to collapse
You can just use the Feb update. You don't need to go thru all the updates to that point. And you don't have to wipe the device. Just run the flash all batch file in the factory image with the -w removed.
You will have to download the full ota from Google's page and flash it if you want to skip every incremental update.
Sent from my Pixel 2 XL using XDA Labs
And/or you can flash the February OTA via twrp if fastboot isn't your cup-o-tea. However, no matter what route you choose, you'll still have to install twrp and root again. Happy flashing :good:
jd1639 said:
You can just use the Feb update. You don't need to go thru all the updates to that point. And you don't have to wipe the device. Just run the flash all batch file in the factory image with the -w removed.
Click to expand...
Click to collapse
MrMeeseeks said:
You will have to download the full ota from Google's page and flash it if you want to skip every incremental update.
Click to expand...
Click to collapse
Badger50 said:
And/or you can flash the February OTA via twrp if fastboot isn't your cup-o-tea. However, no matter what route you choose, you'll still have to install twrp and root again. Happy flashing :good:
Click to expand...
Click to collapse
Thank you all!! Fastboot or TWRP work for me. Glad I don't need to wipe device.
Any issues with rooting on new Feb patch? Or same process with Magisk as it's been?
cwburns32 said:
Thank you all!! Fastboot or TWRP work for me. Glad I don't need to wipe device.
Any issues with rooting on new Feb patch? Or same process with Magisk as it's been?
Click to expand...
Click to collapse
Same process, no issues.
jd1639 said:
Same process, no issues.
Click to expand...
Click to collapse
What he said! :laugh:
jd1639 said:
Same process, no issues.
Click to expand...
Click to collapse
Badger50 said:
What he said! :laugh:
Click to expand...
Click to collapse
Sounds good!! Any one using Viper4Android on the new Feb build? If so, how is it working? Thanks!
cwburns32 said:
Sounds good!! Any one using Viper4Android on the new Feb build? If so, how is it working? Thanks!
Click to expand...
Click to collapse
The 3.3 version magisk module working fine for me :good:
Badger50 said:
The 3.3 version magisk module working fine for me :good:
Click to expand...
Click to collapse
Are you also using Dolby on top of Viper, I was for a while with great results but can't seem to find Dolby 9 as opposed to the 8.1 I was using previously.
Flashing via ADB without -w , I recall doing this previously but don't remember what I need to exactly in the commands so I don't have to wipe phone. Could someone please kindly advise?
cwburns32 said:
Are you also using Dolby on top of Viper, I was for a while with great results but can't seem to find Dolby 9 as opposed to the 8.1 I was using previously.
Flashing via ADB without -w , I recall doing this previously but don't remember what I need to exactly in the commands so I don't have to wipe phone. Could someone please kindly advise?
Click to expand...
Click to collapse
Yep, using Dolby as well. Here, you can use my copy :good: https://drive.google.com/file/d/1B5oSZ96oi7JC_IQnU1qiNPwQWPjr72aL/view?usp=drivesdk
As far as updating, make sure your platform-tools are up to date. Extract the February update, and place all those files in your platform-tools folder.
Then edit the flash-all.bat file, removing the -w, and leaving a space between the remaining words, and save the edit.
Put your phone in bootloader mode, plug it in to your pc, open a command prompt on your platform-tools folder, and type: fastboot flash-all
Let it do it's thing, then boot up to the OS to make sure it's all good.
Then fastboot into twrp, flash the twrp installer zip, then flash magisk zip, then your custom kernel(if used) Boot up, and there ya go
Badger50 said:
Yep, using Dolby as well. Here, you can use my copy :good: https://drive.google.com/file/d/1B5oSZ96oi7JC_IQnU1qiNPwQWPjr72aL/view?usp=drivesdk
As far as updating, make sure your platform-tools are up to date. Extract the February update, and place all those files in your platform-tools folder.
Then edit the flash-all.bat file, removing the -w, and leaving a space between the remaining words, and save the edit.
Put your phone in bootloader mode, plug it in to your pc, open a command prompt on your platform-tools folder, and type: fastboot flash-all
Let it do it's thing, then boot up to the OS to make sure it's all good.
Then fastboot into twrp, flash the twrp installer zip, then flash magisk zip, then your custom kernel(if used) Boot up, and there ya go
Click to expand...
Click to collapse
Lol my luck...
I just flashed your dolby version but it just fc's after showing the Dolby opening screen for a couple seconds.
Any other mods needed?
CyberpodS2 said:
Lol my luck...
I just flashed your dolby version but it just fc's after showing the Dolby opening screen for a couple seconds.
Any other mods needed?
Click to expand...
Click to collapse
Yeah, uninstall any other sound mods you have. Then flash the Dolby.zip in twrp, then install ViPER4Android FX version 3.3 magisk module, reboot, then install the AML module. Then you should be good :good: