Related
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
rinampa said:
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
Click to expand...
Click to collapse
At the time, I do not know either what is causing this. Because the Oreo rom is rather bugged a bit. (Lower audio, wifi not turning on once it's off and now this)
What twrp should i use for nougat version?
HnsAlczr said:
What twrp should i use for nougat version?
Click to expand...
Click to collapse
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
+)KEV1N(+ said:
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
Click to expand...
Click to collapse
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
HnsAlczr said:
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
Click to expand...
Click to collapse
Did you upgrade your system to Oreo? If so, did you have substratum themes on?
I wonder when he opens the twrp he asks for the PIN number , password or something?
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
ZueiraBR said:
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
Click to expand...
Click to collapse
https://www.asus.com/br/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/,Select the android operating system, Versão UnlockTool_2018_0629(android O)
2018/06/29740.7 KBytes.
Read the instructions carefully.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Hi all, does not work with WW-80.30.76.10 . Help me please
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Delaias1995 said:
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Click to expand...
Click to collapse
Installed twrp by fastboot goes into recovery in twrp restart the always by twrp.
After updating to twrp new version I can not update more firmware, I have to download recovery stock
I am having problems in twrp I can not install rom always error 7 in this last update how to solve?
Please, I appreciate your help.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Is there any UN-OFFICIAL unlock method ? tks
Can someone help me? I can't find the correct version (or doesn't even exist) of twrp for my zenfone zoom s.
(UL-Z01H-WW-80.30.76.74)
Hi using latest updated stock rom with root..
Magisk
New August update doesn’t install..
Before i used to install updates in root..
Now cant..
Help..
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
garylawwd said:
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
Click to expand...
Click to collapse
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Sami Devo said:
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Click to expand...
Click to collapse
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
My build..
garylawwd said:
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
Click to expand...
Click to collapse
But i had custom recovery and it installed before..the boot.img have to match with current build? For fastboot flash?? And which slot i have to flash the boot?
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
_mysiak_ said:
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Click to expand...
Click to collapse
This link u give is for flash fastboot rom
Should i uninstall magisk and try?
Sami Devo said:
This link u give is for flash fastboot rom
Click to expand...
Click to collapse
Maybe try to read it at least one more time..
same but different problem.
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
I have no custom recovery, or magisk but have same problem
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM of Build 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring stock boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Sami Devo said:
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM offer BL 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Click to expand...
Click to collapse
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
weeeeeeeb said:
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
Click to expand...
Click to collapse
???Yah.. i have some apps which i must use! Such as greenify , titanium backup.. those r core of root..
Am looking forward to meet another update challenge. Am ready.
weeeeeeeb said:
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
Click to expand...
Click to collapse
No its not weird. Becoz july update n also August both have to installed by u...thats y its not only 35mb.ur build is too old. It ought to be a big update
Tyrese117 said:
I have no custom recovery, or magisk but have same problem
Click to expand...
Click to collapse
Then u need to flash fastboot rom
Sami Devo said:
Then u need to flash fastboot rom
Click to expand...
Click to collapse
I have installed July patch without any problem
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Tyrese117 said:
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Click to expand...
Click to collapse
this is very hard work.. i cant do that in every month and retaining root again!
So there's a number of discussions about what to try when an update has gone bad, or how to get to DN2103_11_A.10 and get root, but there's no guide on how to update from a rooted A.10 to a rooted A.11, and apparently a lot of things to do wrong.
What's the recommended way to update a rooted Nord 2? What are the biggest risks (WiFi/Bluetooth, IMEI,...)?
See here https://forum.xda-developers.com/t/...2103_11_a-07-10-eea-rom.4331695/post-85755357
NetSoerfer said:
So there's a number of discussions about what to try when an update has gone bad, or how to get to DN2103_11_A.10 and get root, but there's no guide on how to update from a rooted A.10 to a rooted A.11, and apparently a lot of things to do wrong.
What's the recommended way to update a rooted Nord 2? What are the biggest risks (WiFi/Bluetooth, IMEI,...)?
Click to expand...
Click to collapse
its simple:
- flash stock boot.img for your firmwre version in twrp, dont reboot
- flash update.zip, dont reboot
- flash magisk.zip, reboot to bootloader
- flash vbmeta.img with the disable commands
Thanks, that actually helps a lot
NetSoerfer said:
Thanks, that actually helps a lot
Click to expand...
Click to collapse
You don't need to boot to fastboot and flash Vbmeta
Reboot after flashing boot.img can be skippable.
After flashing update zip you can use magisk zip to install to gain root but i didn't tested please tell us if it's working