Related
Note: None of these files have been tested mainly because I want to keep root on my device. If someone (preferably a recognized developer) can confirm that you can still root the device on this update, I will edit the thread to appear safe to novice/semi-inexperienced users. Because I haven't tested these files, I'm gonna assume its a January security patch.
Here I have pulled the latest FOTA update for the SM-T337A. I know right, I thought this device would never get another update, but it did! Down below I have uploaded the original, untouched .CFG update file and my own compiled .ZIP update file. Not that any of them are different, but if one fails to flash, there's the other file to try.
New PDA Version: T337AUCU2BOH5
New CSC Version: T337AATT2BOH5
Bootloader Version: Bootloader V2 (So you can downgrade back to the BOH4 firmware)
Please feel free to ask any questions or report any problems down below.
EDIT: I will begin creating Odin packages for this update and release them in place of the zip files if/when they are completed.
--Download Links--
Original .CFG File: https://mega.nz/#!r940XJLB!OUne16ltPYkOqfNBbzA5W08f8LwvYT_os--agbGzFq4
Compiled .ZIP File: https://mega.nz/#!fkoW0JKB!aR2uZYlthtmW7Us0uBmP6-BZrmhKiJrRaVrbdkq-bx8
Cheers!
Thank you very much as always @KingOfTheNet , is there any chance you can make an Odin firmware file too, or would that require you taking the update (which I understand very much why you wouldn't want to, without knowing for sure)?
Also I shall mirror the update.zip file on AFH if you'd like (it doesn't accept cfg files)
thisisapoorusernamechoice said:
Thank you very much as always @KingOfTheNet , is there any chance you can make an Odin firmware file too, or would that require you taking the update (which I understand very much why you wouldn't want to, without knowing for sure)?
Also I shall mirror the update.zip file on AFH if you'd like (it doesn't accept cfg files)
Click to expand...
Click to collapse
I'm 99% sure it's just a January security patch, so I'm not sure if it would be worth making an Odin file for it. If AT&T where to release a Marshmallow or Nougat update (which we all know isn't gonna happen) then I would make one for that. Making the Odin file for the Lollipop firmware took me like 4 months
Also feel free to mirror the file(s) to AFH, please be sure to credit me though, assuming they flash without issues. I didn't test it on mine because I want to keep root until I can verify that it can still be achieved on this new update. I'm just surprised AT&T is still updating this thing.
Cheers!
Do you have patch notes, what was fixed?
Thanks.
KGB7 said:
Do you have patch notes, what was fixed?
Thanks.
Click to expand...
Click to collapse
I would imagine AT&T or Samsung would release them somewhere on their website. In my opinion, security updates are made to keep your device guarded against new root methods and viruses, which is exactly why I didn't flash the update myself, to keep root.
[OBSOLETE] @yshalsager As of 8.8.16 flashable TWRP non ARB Firmware now available see thread.
[GUIDE] Updating Modem, Bluetooth and DSP! ~~~ Without triggering ARP on WHYRED!
For anyone on customs rom and need to updated the above partitions?
The commands to flash them in fastboot are: -
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
pause
I just created a bat file (windows) with the above content.
All I need do in future is download a firmware from here, extract the three files and place the bat file in the same folder, and run it.
^^^ Note I have adb/fastboot setup with a global path in windows.
Haven't tested in operation yet but in theory should work. I'm on 8.7.5 Beta firmware at present and see no need to update until the custom rom in use requires update files.
Above 3 files have been reported safe to flash here (Thanks @aank) , without effecting the bootloader, so not to trigger ARP.
First two files are self explained.
DSP (Digital Signal Processor)
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
Attached is a sample bat file, just remove the .txt from the end of the file name.
I posted this before in the Everything About Anti Roll-back [Whyred] by @AL_IRAQI , but would probably get lost there.
Edit: - Edited the batch file to include a "pause", in case you double click instead of running in CMD/POWERSHELL window.
Cool, hope it works if i ever need it. Thanks
thx tested it, it works, i am still on anti 3 after updating these 3
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
rizdar said:
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
Click to expand...
Click to collapse
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
@corkiejp Do you recommend flashing the firmware files from 9.5.19 or the ones from 8.7.26 when moving to a custom rom?
corkiejp said:
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
Click to expand...
Click to collapse
I'm on Arrow OS right now.
But after I do the steps above, it seems like nothings changed.
The signal is still the same.
It's happening on all custom ROMs, is it because my providers?
Edit: I was on 8.7.26 (Masik U 2.2)
@eyebiz
I would stick with whatever firmware your device has at present. It is probably more recent than firmware recommend by custom roms.
There is really no reason to update firmware, if your device is working well with what you have!
If the rom recommends a specific firmware, then you may need to upgrade, but don't downgrade firmware to match.
If I'm flashing firmware, I usually use the version from beta roms, as that is often the more recent firmware.
I only update roms, once a month when security patches included. And patch the firmware at the same time.
@rizdar Your network provider maybe the problem, check your APN settings with the recommend settings of your provider.
The three files mentioned in this thread, may not be alter from one firmware to the next. It is usually the bootloader (which we need to avoid for ARP) that regularly changes.
You could compare files and hashes from different firmware to see if there is changes.
Hi @corkiejp
I've created TWRP flashable .zip with latest stable modem, dsp and bluetooth here :
https://drive.google.com/file/d/1eYys31FFgdxz4GyMFgMiuvoTWwwgER1Y/view?usp=drivesdk
The ARB should be fine as well,
I've tried myself, flashed it on top of 9.6.3 fw less ROM.
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
corkiejp said:
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
Click to expand...
Click to collapse
Oh, no, am not on xiaomi.eu. Just happen to look around the fw less thread, and it seems there's a need for a TWRP flashable zip for radio only update,
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
I didnt delete too much files from firmware update folder, only one i think is really safe to delete.
Alright, i will modify the file name.
It contain 8.8.16 Global files.
otonieru said:
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
Click to expand...
Click to collapse
Have you a link to git, it would be easier to just download the three files for me, than extracting them from Firmware zips.
Apparently those firmware files are safe. I flashed them with a .zip file I put together. For anyone that wants to try you can download it from here.
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
lol. you spoiled the surprise, it was a test. I'll release it soon
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
I edited the original one and signed the .zip, it seems to be working. Although the cell power consumption is still quite high so far.
deleted
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
ahsnali said:
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
Click to expand...
Click to collapse
It may or may not help your situation. If your worried about your anti version, there is non arb firmware zips available with just them files.
VoLTE is broken on most PIE roms (I believe based on discussions in TE) , check your rom thread and see if anyone else has it working. Or if there is Patch to enable it.
HiSuiteLauncher
EMUI 9 fix and EMUI 10 Instructions here: Post. JSON file UPDATED!!!
A Launcher for HiSuite which grabs its ssl calls and hooks them so you can update to EMUI 9.1.
What does it do?
It will launch an instance of HiSuite, Huawei Smartphone PC Manager, if installed. This instance will have a hook to ssl calls made by HiSuite to HiCloud. So we can now handle responses by editing a simple text file for a full ota update. It won't touch anything else. With an update response, HiSuite should now handle the update process including the rollback option if available and a proper imei authorization to HiCloud. This is a way to force an update to your Huawei/Honor smartphone with a standard tool.
Setup and General Info
You will need FirmwareFinder (TeamMT). If you've been around Huawei/Honor forums you should already know what it is. With FF we can track ota updates and even run an authorization test for an update. This is important because we're gonna be using the ota ID and its full link to pass to HiSuite. If you spot an update and your device is not yet authorized to install it your phone will most likely avoid it either.
!IMPORTANT!: I've been using this method since march/19 without any problems. No wipes, connectivity losses, call problems, weird behavior whatsoever. In fact, I'm running EMUI 9.1 now. I don't know how you can ensure the ID you picked is the right one for your device - considering you are using the search correctly: for my Honor 10 C636 I search for COL-L29C636. You might notice the name of the device seems a bit strange and here comes a massive confusion. Col-L29 is now COL-LGRP2-OVS (C636 is overseas) with a bunch of small step rom versions like .226 .227. 228 .229. I usually pick the very first version my phone is authorized for. So my last update was .227. After the update I tested my phone for others versions like .228 and .229 and my phone was authorized for those too. Go figure!
Since HiSuite 9+ the cust info is in the update request and I believe HiCloud suggests the right package for your phone. The reason behind this is because the ota file I get sometimes it's different in size and checksum from the one you get from FF even if it's the same ID. Total speculation here. The cust and preload info have their own json structure. Please revisit the json file below. You can find find cust and preload data in FF simply by searching <your phone model>-<cust/preload>. They both feature their own IDs and urls and they are separated by EMUI versions (Android version).
ALWAYS take note of the rollback ID suggested by HiCloud. It might look like it's just a regular version but it's not! An update and a rollback IDs are different, with different flash scripts. HiCloud will send rollback data with major updates like from EMUI 8.1 to EMUI 9; EMUI 9 to EMUI 9.1. You can spot both IDs in FF as well.
Instructions:
Just extract the zip folder to any suitable folder in your computer and run the Launcher.exe. A console window will popup and HiSuite will appear right after. You can monitor HiSuite calls in the console window.
Remove root and TWRP. You have to be full stock.
Backup data. Even HiSuite will ask you to do it.
Be prepared to download at least 4Gb of data while keeping your phone plugged to your pc.
You will need a very basic understanding of json data structure.
You have 2 files that should remain in the main folder of the launcher:
hisuite9_request_update.txt: you should add the ID to "versionID" and full link to the update ota in "url". Get those from FF.
Please notice that there is a pattern here. The "url" data doesn't include the actual file. UPDATED!!!
{
"status":"0",
"versionPackageCheckResults":[
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:41:07+0000",
"description":"COL-LGRP2-OVS 10.0.0.177",
"name":"COL-LGRP2-OVS 10.0.0.177",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<UPDATE ID GOES HERE>/f1/",
"version":"COL-LGRP2-OVS 10.0.0.177",
"versionID":"UPDATE ID GOES HERE"
}
],
"versionPackageType":2,
"checkEnd":"1"
},
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:03:11+0000",
"description":"COL-L29-CUST 10.0.0.3(C636)",
"name":"COL-L29-CUST 10.0.0.3(C636)",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<CUST ID>/f1/",
"version":"COL-L29-CUST 10.0.0.3(C636)",
"versionID":"CUST ID"
}
],
"versionPackageType":3,
"checkEnd":"1"
},
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:03:11+0000",
"description":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"name":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<PRELOAD ID>/f1/",
"version":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"versionID":"PRELOAD ID"
}
],
"versionPackageType":4,
"checkEnd":"1"
}
]
}
IMEI.txt: add the first IMEI of your phone to the first line of this file.
Hit Update in HiSuite and you should see the red dot indicating an ota update (in fact, the update you added in the file above).
log.txt: this file holds the requests/responses during the current session.
Launcher.exe.config: here you can find a few setup options like hisuite folder.
Bugs
- Well, as far as I'm concerned you shouldn't face any bugs since it's pretty straight forward. BUT, please take my advice: if you're not sure about which update to go for avoid it altogether.
- It does not work with incremental updates. The recovery will reject it.
- In your phone, about phone page, it might not show the update changelog. Sometimes it does show, sometimes it doesn't.
- I cannot confirm this but since I always update my phone through this method I don't get incremental updates anymore. I don't know if it's because I'm always way ahead (updates usually take forever to reach my phone before and that's why I've been doing all of this) or anything else.
Notes:
- I have to thank Smaehtin (XDA) for kindly answering my request to support this tool for Honor 10 and for actually providing this method.
- Although I'm a professional developer (ERP stuff), I'm not used to C# so the code might look a bit messy and funky here and there. I'm sorry for that.
- The solution used is from a freeware compiler, SharDevelop (http://www.icsharpcode.net/OpenSource/SD/).
- Disclaimer here, I am not responsible for any damage you (your phone) might suffer from attempting this. I tested it myself several times in my phone, Honor 10 C636 (COL-L29C636). HiSuite will handle the whole update process but you still can provide wrong data as of wrong IDs or wrong url.
- We are using EasyHook (https://easyhook.github.io/) and Newtonsoft.Json (https://www.newtonsoft.com/json) libs.
Source:
https://github.com/magnot/HiSuiteLauncher
Many thanks for the instructions ??
Success update to emui 9.1.0.325 with this guide.
Same all ok ! thanks ! OFF TOPIC:anyone know how to disable suggestion on drawer ?
Thanks, works like a charm!
this made my day, many thanks superb tool
@MagnoT Thanks for your work , new version available , I change only version ID and Url link its ok to update ?
Any idea how to spoof only IMEI.txt ?
-Giving us the mean with an early device 's imei to force install the right next update or check what is latest hicloud's OVS FullOTA-MF for a device's cust region and imei.
oslo83 said:
Any idea how to spoof only IMEI.txt ?
-Giving us the mean with an early device 's imei to force install the right next update or check what is latest hicloud's OVS FullOTA-MF for a device's cust region and imei.
Click to expand...
Click to collapse
I wouldn't do that. There's no need to rush an update that way. And if you're not yet authorized for an update the recovery will just reject it.
leap_ahead said:
@MagnoT Thanks for your work , new version available , I change only version ID and Url link its ok to update ?
Click to expand...
Click to collapse
Yep, if you have FF confirmation for your device!
.326 is available in FF for quite some time. It's the August EMUI 9.1 security patch update but my device is not authorized for it just yet. The ID is 297131. I'll wait.
MagnoT said:
I wouldn't do that. There's no need to rush an update that way. And if you're not yet authorized for an update the recovery will just reject it.
Click to expand...
Click to collapse
I will do.
I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
Late 9.1 OVS build are surely/maybe cust specific now...
By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.
Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)
-But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
-Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)
MagnoT said:
Yep, if you have FF confirmation for your device!
.326 is available in FF for quite some time. It's the August EMUI 9.1 security patch update but my device is not authorized for it just yet. The ID is 297131. I'll wait.
Click to expand...
Click to collapse
You can check. 330! But still in july update
oslo83 said:
I will do.
I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
Late 9.1 OVS build are surely/maybe cust specific now...
By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.
Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)
-But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
-Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)
Click to expand...
Click to collapse
I guess I get what you mean. In the source code there's an entry to spoof imei which I converted to read from file but that's for the authorization request. Still, I wouldn't go for it. As for knowing in advance the latest/next update roll out based on imei spoofing that would be kinda hard to accomplish imo because... well, it's random and the effort doesn't pay off. I'll have a look into it and update the tool.
leap_ahead said:
You can check. 330! But still in july update
Click to expand...
Click to collapse
.330 it's a july security patch for EMUI 9.1. I believe it's still an entry to EMUI 9.1 just like .325. That's the mess we get with this OVS thing... different versions of the same patch all approved. I'll wait for the august update.
MagnoT said:
.330 it's a july security patch for EMUI 9.1. I believe it's still an entry to EMUI 9.1 just like .325. That's the mess we get with this OVS thing... different versions of the same patch all approved. I'll wait for the august update.
Click to expand...
Click to collapse
I flash 326 over 330 all ok !
326 is approved for my device, upgrading now thx to this magic tool
leap_ahead said:
I flash 326 over 330 all ok !
Click to expand...
Click to collapse
Ing.King said:
326 is approved for my device, upgrading now thx to this magic tool
Click to expand...
Click to collapse
Thanks for the info guys! :good: I just checked FF and now I'm approved for the .326 update. I'll flash it tonight.
Just my curiosity, can i use it for the honor view 10?
Any Huawei/Honor device EMUI 9 or 9.1
chainsmkgbstrd said:
Just my curiosity, can i use it for the honor view 10?
Click to expand...
Click to collapse
Honestly it should work for any hisuite compatible device. You just have to take note of the device id, correct name tags and of course make sure the update you're going for is approved for it and set it up.
Model - ROG Phone 5 Ultimate (Possibly ROG Phone 5 as well see here )
2021/11/05
Version Name - WW-18.0840.2109.188
Release Date - 2021/11/05
OTA Download Link - Download
RAW Download Link - PENDING
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2109.188 for WW/JP/EU/RU only*
This firmware is only for ROG Phone 5 WW/JP/EU version use and not applicable to ROG Phone 5S/5S Pro series models.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1. Optimize the charging experience function
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
Spoiler
2021/08/24
Version Name - WW-18.0840.2107.151
Release Date - 2021/08/24
OTA Download Link - Download
RAW Download Link - Download
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2107.151 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed issue with sending MMS messages on Optus Australia
3.Fixed an issue where some videos played through apps would get stuck and without response.
4.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
For JP SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed an issue where some videos played through apps would get stuck and without response.
3.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
*********************************************************************************************************************
2021/07/22
Version Name - WW18.0840.2106.86
Release Date - 2021/07/22
OTA Download Link - Download
RAW Download Link - Waiting
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2106.86 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Improved Item:
1. Updated Android security patch to 2021-06
2. Fixed an issue where the game would crash when using multiple windows to open the settings and change the system navigation
3. Fixed the problem of broken sound when using screen recording
4. Fixed the problem of low notification sound when using Bluetooth headsets in standby mode
5. Fixed an issue where blocking notifications in the game could not block Facebook messenger notifications
6. Fixed the problem of reduced call volume
7. Fixed the problem of using a microphone to record the voice of a team in the game, and the problem of not being able to record your own voice
8. Fixed the problem that the 5G network cannot be detected when connected to the GT-AX11000 router
9. Fixed a serious delay in the screen when entering the game with Geforce Now
10. Optimize touch experience
11. Fix sound effect for speaker playback.
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
twistedumbrella said:
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
Click to expand...
Click to collapse
It is the same, I'm looking for the RAW File.
JazonX said:
It is the same, I'm looking for the RAW File.
Click to expand...
Click to collapse
Wouldn't it also be the same then?
twistedumbrella said:
Wouldn't it also be the same then?
Click to expand...
Click to collapse
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Well... I can at least take some of your worries... OTAs won't be a thing after you unlocked your bootloader. You need to manually install them via magisk again. So there is no chance these automatic updates will break your phone.
Furthermore you don't have to worry about root + TWRP as well because there is no twrp for this phone and I doubt there will be one in the next time.
But applying updates and keeping root access without loosing your user data should be no problem. Magisk has special options for this and many people here update that way without bootloops and soft bricks.
JazonX said:
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Click to expand...
Click to collapse
I think you completely misunderstood my comment. I was saying that if the firmware for both models is the same, it is likely the raw files for both are the same (but still separate from the firmware).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to be a low-level rebuild. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
twistedumbrella said:
I think you completely misunderstood my comment, but I am sure someone new will appreciate the explanation (with a few corrections).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to wipe your data, while the regular firmware upgrades are not. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Click to expand...
Click to collapse
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
JazonX said:
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
Click to expand...
Click to collapse
Then apparently it has changed. I didn't have a ROG II, but I have the ROG 5 in hand. I couldn't tell you what has changed, though.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
twistedumbrella said:
Then apparently it has changed. I didn't have a ROG II, but I actually have my ROG 5. Couldn't tell you what else has changed.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Click to expand...
Click to collapse
Ohh .. In that case I was super wrong, and apologies over my misinformation.
Yeah, Actually ROG II Raw files had a Flash-all file which installs the full firmware, and reboots.
I even had a source (A Persian website) to get these when the OTA releases.
I was on windows, and usually after a RAW installation, the cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before.
Guess we gotta stick to ASUS OTA files from the support site then.
Thanks a lot ! : )
These updates come with a flash_raw script that looks more or less harmless. There is no visible wipe command included, but the phone did appear wiped after installing.
The flash_all, on the other hand, has a rather obvious section to opt in or out of an erase that opting out on Linux and Windows. I think the wipe isn't as much a wipe as it overwrites the partition.
I typically install my firmware with fastboot using a slightly modified version of the flash_all script and an unpacked payload. Somehow I broke the installer, which gives me a chance to test the raw again.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
JazonX said:
The cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before
Click to expand...
Click to collapse
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Anubarak16 said:
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Click to expand...
Click to collapse
I think Art broke that. If I remember the explanation, the idea was to create something like the old odex layout that was less sloppy. The code that used to be cached is now broken out into a physical file alongside the application. It's also how apps like *that one everyone remembers for IAP* are able to modify code without breaking signatures.
Successfully rooted using the same commands from here and the root images in the OP.
JazonX said:
Successfully rooted using the same commands from here and the root images in the OP.
Click to expand...
Click to collapse
Any word on the raw firmware? What about the existing boot images?
twistedumbrella said:
Any word on the raw firmware? What about the existing boot images?
Click to expand...
Click to collapse
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
JazonX said:
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
Click to expand...
Click to collapse
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
twistedumbrella said:
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
Click to expand...
Click to collapse
Patching own images are always reliable...
SafetyNet Passed with this fix !
JazonX said:
Patching own images are always reliable...
SafetyNet Passed with this fix !
Click to expand...
Click to collapse
Glad you found it. Good luck.
I flashed the raw firmware. It was a downgrade and my device was already set up and in use, but it included the scripts and commands to install without a wipe (finally). Moving the latest firmware to the sdcard allowed me to update almost immediately after finishing the flash.
I would assume it works on the Ultimate, since everything else has been identical and the date on that package is the same as the software image.
New update !
While working with something else, I messed up a bit. I need the full OTA for kb2001_11.c.15 (Indian variant) so I can restore the original boot partition
It's still not available here. Any idea where I can find it urgently?
- https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
- Oxygen Updator app
I don't need it anymore. Can't find a button to delete the thread.
Hi @VarunAgw. Could you please tell me how you resolved your problem? Did you get a zip from which you could extract boot?
achinko95 said:
Hi @VarunAgw. Could you please tell me how you resolved your problem? Did you get a zip from which you could extract boot?
Click to expand...
Click to collapse
Yes.
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
I had the full version of full OTA before the latest one (you can find it online), which I extracted using this tool.
Then I update the extracted files with the increamental update of latest version using Incremental OTA feature of this tool.
This way I was able to generate the latest c.15
Awesome. Thanks for the reply
VarunAgw said:
Yes.
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
I had the full version of full OTA before the latest one (you can find it online), which I extracted using this tool.
Then I update the extracted files with the increamental update of latest version using Incremental OTA feature of this tool.
This way I was able to generate the latest c.15
Click to expand...
Click to collapse
Can you do on this way full package C21 for KB2005 and upload it? Please.