Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.
Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates
csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.
city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.
The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743
So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again
Android newbie trying to do a 6.20.651.3 update on a HTC One M8 Sprint variant. I’ve tried the direct download method, I get to 1.06gb, download successful, verified, unzipping update then reboots and flashes up some errors and goes into TWRP recovery.
I have also had a few goes at it from Windows running RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.EXE that fails as well with an error 155: unknown error: cannot update Android phone, please get the correct ROM update utility and try again or just hangs there on 0% for 30 mins.
Device has s-off and is rooted - at least Root Checker app says it is but it can also report not properly installed. I've just tried the direct download method once more having used the Root Check app to confirm that it is rooted but with same result.
Can anyone give me a few pointers in terms of what I have to do to get this to work. Help much appreciated.
You won't be able to take the OTA update with TWRP installed. As for running the latest RUU, you have to have the latest firmware installed first. You'll also need the latest version of TWRP if you want to flash a MM ROM. Check OMJ's RUU thread in Android Development for more info.
An alternative to taking the OTA or running the RUU would be to update your firmware & TWRP recovery, then flash a stock rooted MM ROM.
Thanks for your response. It has given me some understanding of the different types of update. I checked my TWRP and it is 2.8.7.0, which is the latest, and tried a firmware update using the firmware update utility from here
http://forum.xda-developers.com/showthread.php?t=2729173
and downloaded one of the non-Harman extracted firmware versions, renamed to rom.zip, put it in required folder and ran ARUWizard.exe and it is stuck on updating (0/1) sending, has been for 15 mins so I can assume that this will not work.
Any ideas? There are four variants: full, full signed, with / without recovery, boot. Am I running the wrong firmware?
Download the modified MM firmware (no boot or recovery) and place it on your external SD card and rename the file 0P6BIMG.zip (make sure the file doesn't have an extra .zip extension on the end). Reboot to the boot loader and update your firmware when prompted. As for TWRP, there is a newer version available. Check the last couple of pages of the TWRP thread in Original Development. It's version 2.8.9.0.
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
mp
check your mp
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Download the file linked below. Once you've done that, click the link in my signature for the M8 hboot guide. Scroll down to the section on firmware updates (it's in the very first post) and follow my instructions in my guide to update your firmware.
https://www.androidfilehost.com/?fid=24391638059059964
After an attempt to upgrade to Lollipop, the phone froze after software installation when it rebooted.
I was able to restore the phone from a cwm backup file to 4.4.3 and at the moment everything is working great except I cannot update to Lollipop now.
I get this error message:
Package expects build fingerprint of htc/brightstarus_wwe/m:4.4.3/KTU84L/356475.2:usr/release-keys; or
htc/brightstarus_wwe/m7:5.0.2/LRX22G/468180.7:usr/release-keys
this device has htc/brightstarus_wwe/m7:5.0.2/LRX22G/468180.21:usr/release-keys
Here is the phone history of the update attempts:
Device is HTC One M7 WWE Developer Edition 2Gb / 64GB
Device is unlocked and rooted
Device had Android 4.4.3
I flashed the stock recovery to the phone then attempted to install the Lollipop update.
Half way through the installation the operation crashed and phone was in-operatable.
I was able to restore the phone to 4.4.3 from clockworkmod recovery backup.
At this point the phone was working, but slowly.
Everything in the About / Software indicated that the software was 4.4.3 / 6.07.1540.2
However the OS from Hboot screen indicated 7.17.1540.2
Left the phone as is for a long time as it was usable, then had a problem with my SMS application, ultimately I did a factory reset and everything fixed, phone working good.
So now I reflashed the stock recovery again (7.17.1540.7) and tried to install the lollipop update again. It worked this time. 7.17.1540.2 working.
I then got the notice that there was another update (7.17.1520.21) so I tried to install this update.
After the install the phone re-booted and it froze at the HTC / Android screen; I left it for one hour and it did not come to life.
After a reboot the phone would come to this screen then go blank and nothing.
I attempted to re install from clockworkmod recovery restore but it would not work this time.
Had several Lollipop backup files - none worked - thought it was dead.
After some time I did get one to restore but none of the lollipop versions restored worked; I had an older file with 4.4.3 which worked. Phone is now back to 4.4.3
OK now with stock recovery flashed again (7.17.1540.7) I tried the update again to lollipop, but a short ways into the install the operation aborts creating error message as above.
So everything in the About / Software indicates it is 4.4.3 /6.07.1540.2
However the Hboot screen is showing OS 7.17.1540.21 now. Obviously from the last upgrade attempt.
It was a similar situation the first time I was successful installing the lollipop upgrade; the phone indicated that it had version 4.4.3 /6.07.1540.2 but the Hboot OS indicated it had OS 7.17.1540.2 (from the crashed update attempt I guess)
So could someone advise on best coarse of action to try and update this software now to Lollipop?
Could I re-flash something like the kitkat version of boot image? Would this correct the OS version reported by HBoot?
Other options I have found would be to install the RUU factory file:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
But I'm concerned that if this fails due to operating system modifactions the phone may brick, as warned at the site.
Also I have found a TRWP backup file from lollipop upgrade which I could install TRWP recovery and attempt a restore from this file?
Any suggestions?
Just use the RUU, you CANNOT OTA to Lollipop+ if you have rooted the phone without RUUing back to total stock..
Reggi747 said:
So everything in the About / Software indicates it is 4.4.3 /6.07.1540.2
However the Hboot screen is showing OS 7.17.1540.21 now. Obviously from the last upgrade attempt.
Click to expand...
Click to collapse
You must understand here that these 2 numbers are indicating 2 different things. The number you'll find in About/Software is the software version (your rom version). The number you'll find when booted in hboot is the firmware version. In order to install ota updates, everything must be 100% stock and the firmware installed must match the software version (because the firmware is also updated during an ota).
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.51.exe
But I'm concerned that if this fails due to operating system modifactions the phone may brick, as warned at the site.
Click to expand...
Click to collapse
Flashing this file is the best solution, doesn't matters if your system is modified, it will revert everything back to stock and you'll be on the latest version.
Updating from an update fileI have been seeing a lot of posts about people not receiving the OTA on their phone, and got tired of linking my instructions, so I decided to make a separate post
Download the version that you need from the Asus Zenfone 8 Support page (Note that if you are not on the latest Android 11 firmware (30.12.112.72), you will not be able to Android 12. So you need to do these steps with the latest Android 11, and then re-do them for the Android 12 firmware)
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
not work for me :/
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
eVen123 said:
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
Click to expand...
Click to collapse
I think that what is needed is to update to the latest firmware, then Android 12. So if you are already on Android 11, but not latest firmware, install it with the instructions, then do the same to update to Android 12's latest version.
drum94 said:
not work for me :/
Click to expand...
Click to collapse
What part does not work? Please be more specific and also, you should re-read the steps more carefully, in case you missed something
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
drum94 said:
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
Click to expand...
Click to collapse
It also depends what prefix your installation has. See the first letters
UL-...
If you are from some other region, it could be that UL- is not a fitting upgrade option for you. As far as I can tell, it's not possible to tell which of the versions you have.
I give you the build number which is marked in the software information:
RKQ1.2021022.002.30.12.112.72
I have the right version or not suddenly?
Thank you for the quick tutorial. I was doing this via fastboot till now.
However: I upgraded to the latest firmware BEFORE Android 12. No issues.
Then I upgraded to the Android 12 firmware: stuck. Gave me some kind of ram dump, reboot returned me to the same error: bootloop. I was able to reboot and get to the bootloader. After selecting "recovery" it actually booted Android. And now for the weird part: it looks like I have a mix of Android 11 and Android 12 now! The phone is all but unusable for how slow it is. But the main UI looks like Android 11 still, but things like the reboot screen now look like Android 12. Bizarre...
I was at least able to enable ADB debug again, so I think I will be able to recover the phone. Still a weird issue though. Don't know if flashing with fastboot would have prevented it...
If anything fails, you can always try the Asus flash script it will solve most of the issues with your phone, just note that it installs Android 11 (30.11.51.115)
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
EDIT: nvm, I saw your other reply, you alreay tried that. Were you able to get it working again?
Going from WW-30.12.112.82 to WW-31.1004.0404.107 worked flawlessly, i did not lose settings or data on that upgrade (but I want to stress that a good backup is STILL a very good thing to have!) It then started downloading the 31.1010.0410.43 upgrade on its own. (shown in the ui as SKQ1.210821.001.31.1010.0410.43)
Why didn't I upgrade to the latest one myself? Simple: I goofed up and downloaded the older one.
change the name in UL-ASUS_I006D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Hi, has anyone tried to upgrade a firmware that has Magisk and TWRP installed? Today Android 13 has been released for the Zenfone 8, but I wouldn't really like to do something really dumb such as upgrading, rebooting to recovery to reinstall Magisk only to discover that TWRP has been replaced by the stock recovery and the phone completely erases any data it has stored.
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Rokcy98 said:
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Click to expand...
Click to collapse
Thank you! As this is my first phone with A/B slots, I wasn't completely sure about how to proceed. I'll follow your instructions! The only thing I don't get is where is TWRP stored and why it won't be overwritten by the update.
EDIT: installed successfully, thanks!