Related
Processor: Qualcomm MSM8926 Quad-core 1.2Ghz
Platform/OS: Android 4.4.2
Kernel: 3.4.0-gc6284e5-dirty
Buildnr: LTE_S0201121.0_S50_0.015.00
Framaroot shows Aragorn as only exploit (although this is not a Samsung) whichs fails with error #6.
Any advise on more testing that is available or other remedies & possibly known path to investigate?
(The device is new & out since oct, 1 2014)
There is more technical info on: http: // catphones.com / en-gb / phones / s50-smartphone /
Cat s50 root
Hi,
Whenever you insert a micro SD card in the device, the device the same complains or can not connect to download images, videos, music ...
The device we complains micro sd card but can not do anything with it. From the Play Store I downloaded the app "ES File Explorer". When transferring the images from internal memory to micro sd card, notice was that it must be the root device.
How to root the device, have you anything to it?
external sd-card ist useable without root
You dont need root to use an external sd-card. But you cannot write directly into the external sd-card for security reasons. Only installed apps are allowed the store their data there.
When you insert the sd-card, android put a folder named Android/Data into the root-folder of the sd-card. Apps who are modified for external sd-card use, put their own folder in there, which is writable only for this app. For instance, my navigation app store its data to the external sd-card.
If you want to copy your music to the external sd-card, you have to use a computer. The phone is mounted as external device. Then drag and drop your mp3 to the external sd-card. I have made a folder Music on the external sd and copyied my mp3 collection in there.
Greetings
hannesausmwald
My original question about rooting the device is not for storing data on SD. It is more about controlling the device and be able to make a proper backup. Under my control.
So the question still is How to attack this problem. Searching leads to a lot of unusable approaches. (Mostly because they reference OLDer firmware. This firm ware is from last summer).
If more info is needed please indicate what is needed.
Hi noci2,
I've succesfully rooted my S50 with Root Genius BUT new OTAs may not work.
In my case the new update (LTE_S0201121.0_S50_0.017.00_E01) has unrooted the phone and left it crippled (root is lost, partly removed and can't be gained till now and worst thing is: I can't update/root/unroot the phone hence I'm stuck with the 0.016 firmware). Anything else works fine so I'm just waiting for a stock rom + recovery / flash tool + image of the original firmware to undo the "damage" (no root and no updates).
kevin22
P.S.: I would be very grateful if anybody could support a backup image or something (one day)
borstie22 said:
Hi noci2,
the new update (LTE_S0201121.0_S50_0.017.00_E01) ...
I would be very grateful if anybody could support a backup image or something (one day)
Click to expand...
Click to collapse
New OTA? My baseband number is LTE_S0201121.0_S50_0.015.00 and a new update is not available till now via OTA (here in Europe/Germany) What is changed?
I would like to have a backup image too.
Well, that's odd. I'm living in Germany, too.... maybe it depends on your carrier (mine is o2). In version 0.016 the Cat App Store was removed (I've contacted the support and they told me that it'll be back in 0.017 with some improvements). Further LTE was optimized (in 0.016).
Summary:
0.015 - base firmware
0.016 - first update (LTE improvements and Cat App Sotre removed)
0.017 - Cat App store should be back and maybe some minor changes (size is 45,4MB) ... and I can't test it :crying:
kevin22
borstie22 said:
Well, that's odd. I'm living in Germany, too.... maybe it depends on your carrier (mine is o2). In version 0.016 the Cat App Store was removed (I've contacted the support and they told me that it'll be back in 0.017 with some improvements). Further LTE was optimized (in 0.016).
Summary:
0.015 - base firmware
0.016 - first update (LTE improvements and Cat App Sotre removed)
0.017 - Cat App store should be back and maybe some minor changes (size is 45,4MB) ... and I can't test it :crying:
kevin22
Click to expand...
Click to collapse
Hi Kevin,
I am also an o2 - customer, so that cannot be the reason. I will contact the support. Maybe they can tell me whats wrong.
Greetings
Hannes
Hi guys,
I'm on 0.016 as well and it shows me I can upgrade to 0.017, but it always fails (download - reboot - after reboot there is a message in notification area, saying that upgrade failed). Do you know more about this?
Regards
I'm in Holland, no OTA available
mine only gives "server error" when explicitely checking if an update is available.
Hi herdt,
I've got exactly the same problem with the update. Seems like my "partly rooted" ROM isn't the troublemaker after all. Maybe there's a flaw in the OTA itself?
Hi!
I am in Estonia and today I got my first update (had .15). It installed successfully and now I have _0.017.00. I had only tried rooting it before with towelroot which failed.
Framaroot still shows Aragorn as only option. Towelroot fails.
Cat appstore looks the same.
Kernel version: 3.4.0-gd73c047-dirty
Hey guys!
Same problem in Switzerland. Unrooted so far (though have been desperately trying to). No OTA yet, still on 015. OTA update doesn't complain when checking for updates, just saying that none are available. Had to turn off LTE since it has been pretty volatile.
hannesausmwald said:
I will contact the support. Maybe they can tell me whats wrong.
Click to expand...
Click to collapse
I wrote to support and asked about the OTA 0.017.00 The support-staff member wrote me back, that this update is only available via OTA, but not for all regions. The availability depends on the CID-Number which is displayed when you call the #02# (Mine is E01) When the update is available I will get a push message.
On my further askings, on which point in time I will get the OTA and about the purpose to upgrade the phone to Android 4.4.4 or 5, comes nothing concretely. Version 0.015.00 is up-to-date, wrote the staff-member, and I will get a push message. Upgrades are not decided till now.
But when it is up-to-date, why we have other users like borstie22, who has got 0.016.00 via OTA?
I think they are momentarily a little bit confused themselves. My S50 is also E01 and I get an update notification (0.017) but the support told me that 0.016 is the current E01 firmware yada yada yada ("you'll get a push message when the time has come").
Once again: I think we need the help of some clever xda-developers to unleash the true performance of this phone and it's software (Bullitt seems to be somewhat overchallenged with that).
borstie22
Got the E01 (0.015) as well, no updates so far. I'm really looking forward for it since it will hopefully solve the terrible LTE instability I'm experiencing, in general the network (voice as well) is much worse than my old nexus 4. Do you guys made the same experience or is yours stable? I already asked for a 2nd (new) SIM but got the same flakiness. I guess its time to contact support.
Edit: I just realized they don't even list the s50 in their support section nor in the contact form. Weird.
I haven't had any issues, but that support thing is a bit weird. I tried contacting them through contact form, regarding windows USB drivers to get the phone recognized for ADB. There was no response at all.
Stumbled on this thread looking for root, as It would've been Ok for me to read logs from phone directly.
Driver problem got sorted by updating SDK and explicitly telling Windows to use the generic android drivers that came with it.
That doesn't sound very promising. I just ordered my s50, should arrive tomorrow. I'll report back what CID and firmware I have and if I can update.
The LTE thing doesn't sound good at all.
So I sent them an email 2days ago late in the evening and got a reply concerning the LTE issues this morning: They basically recommend to turn LTE off which indeed improves the stability, no random blackouts anymore but general network reception (voice calls) is still beyond good and evil. My dear co-workers with other phones and LTE enabled have no problems at all (same carrier, same place, same contract). About the missing S50 info/support on their site: They're working on it. Anyway I just replied to see whats going on with the updates, lets see. Well at least they answer to support requests :good:
---------- Post added at 10:09 PM ---------- Previous post was at 10:04 PM ----------
d3l1 said:
That doesn't sound very promising. I just ordered my s50, should arrive tomorrow. I'll report back what CID and firmware I have and if I can update.
The LTE thing doesn't sound good at all.
Click to expand...
Click to collapse
You got any news on your device? LTE works fine?
Lots are talking about firmware update, but what about actual root ?
At the end of the update in question was published by the official units.
Notice that the beta version is.
resource connection : https://bbs.nubia.cn/thread-1462621-1-1.html
As an informative question: If we update the rooted and installed gapps in all versions, can there be a problem?
For example, you may be deprived of gappa until you have Brick or New root?
chinese english translation is bad because i did not understand.
*Changes*
* JOS updated X-JOS
* Android 8.1 version updated Android 9.0
*System optimization : system performance, enhance the overall fluency
*optimization: system stability
*optimization: Android update security patches
*smart card services added: "fast application" card and enjoy the native application experience the performance of third-party applications
*optimization: Some third-party application stability
*fix: part of the game (the king of glory, to stimulate the battlefield) probability of the emergence of flash back problems
this update optimized content including but not limited to the above-listed items
Note precautions: ● This is a trial version upgrade, only support SD card upgrade package: After you download this version of the full SD card pack, then click on "Settings" -> "System Update" -> "button in the upper right corner function" -> "local upgrade", select SD card pack, click the "install now" wait upgrade is complete;●trial version where there may be imperfections on experience details, please according to their own circumstances choose to upgrade;●upgrade this version P Andrews after, if you want to roll back to previous versions, you need to back up phone data,Shuangqing SD card pack before upgrading history, after the completion of normal use;● Make sure the phone battery before upgrading adequate and mobile phone data backup (recommended use its own backup software), so as not to cause the phone to upgrade data loss; ●before upgrading, cancellation of various screen lock, the upgrade process, make sure the phone flat, and not arbitrarily touch the screen, follow the onscreen prompts ;● as already get Root privileges, be sure to remove the Root privileges, the state returned to normal version, and restore the factory settings before upgrading, otherwise easily lead to the escalation Defeated.
Download Link: http://romdownload.nubia.com/nubiaX/V3.05/NX616J-update.zip
Altarnatife Download Link : https://drive.google.com/file/d/1AqeiP-uQYI5jq7m1SabJ51h1MFn31pkn/edit
Thanks : @Ravira43
MD5 code: 66DD854D61C742326C01200E580E2952
It's not possible to download, tried using china vpn and without.
The download dies after 100mb
Could you upload it to another location (maybe google?)
Ravira43 said:
It's not possible to download, tried using china vpn and without.
The download dies after 100mb
Could you upload it to another location (maybe google?)
Click to expand...
Click to collapse
Hi. I need to ask. What does this mean? Does this include Play Store? Is it a global version?
Or is it just another Chinese ROM?
Thank you!
Ravira43 said:
It's not possible to download, tried using china vpn and without.
The download dies after 100mb
Could you upload it to another location (maybe google?)
Click to expand...
Click to collapse
Used " internet download menager " and search google " idm 16 part download" use.
gigilex said:
Hi. I need to ask. What does this mean? Does this include Play Store? Is it a global version?
Or is it just another Chinese ROM?
Thank you!
Click to expand...
Click to collapse
No, only Chinese ROM. unlucky.
But İnstall new Play store way
1. https://bbs.nubia.cn/thread-1464227-1-1.html
2. https://bbs.nubia.cn/thread-1462852-1-1.html
Never mind, a friend of mine has already downloaded and uploaded it on google.
Can't paste the link, because I'm a new member.
Ravira43 said:
Never mind, a friend of mine has already downloaded and uploaded it on google.
Can't paste the link, because I'm a new member.
Click to expand...
Click to collapse
I'm glad you got the solution.
I can publish the link if you throw it.
Guys I have just received an OTA update 1.4gb version 3.05 on my phone.
I would install it but my fear is to loose all data and settings.
Did anyone installed it?
I've also received the OTA update, I would try it but the chinese links for Gapps are nor working (source download not posssible)
Does anyone know how to unroot the terminal?
When local updating to 3.05, the terminal will brick.
How to install Android 9
I've installed it the following way.
Downloaded the new android version to my Nubia X.
Started localupdate via phone --> settings --> update --> localupdate.
Android 9 installed automatically without problems. Your phone should now be unrooted.
Now you need the Root-toolkit for v3.05 --> works only in windows :/
Connect your phone via usb in fastbootmode (you need to activate usb-debugging before)
Execute the root toolkit v3.05
can't post the link, somebody else have to do it.
a window opens --> close it (can't read chinese language)
another window should open --> klick on root.
wait after "success" appears.
Your phone should be restarting.
I'm using android 9 on my nubia x since a month and its working way better then android 8.
I'm not responsible if you brick your phone.
I give no guarantee
Ravira43 said:
I've installed it the following way.
Downloaded the new android version to my Nubia X.
Started localupdate via phone --> settings --> update --> localupdate.
Android 9 installed automatically without problems. Your phone should now be unrooted.
Now you need the Root-toolkit for v3.05 --> works only in windows :/
Connect your phone via usb in fastbootmode (you need to activate usb-debugging before)
Execute the root toolkit v3.05
can't post the link, somebody else have to do it.
a window opens --> close it (can't read chinese language)
another window should open --> klick on root.
wait after "success" appears.
Your phone should be restarting.
I'm using android 9 on my nubia x since a month and its working way better then android 8.
I'm not responsible if you brick your phone.
I give no guarantee
Click to expand...
Click to collapse
hi i run android 9 on my nubia x rooted, but how can we get Gapps working on it please ? thanks
I have twrp running on it too.
Ravira43 said:
I've installed it the following way.
Downloaded the new android version to my Nubia X.
Started localupdate via phone --> settings --> update --> localupdate.
Android 9 installed automatically without problems. Your phone should now be unrooted.
Now you need the Root-toolkit for v3.05 --> works only in windows :/
Connect your phone via usb in fastbootmode (you need to activate usb-debugging before)
Execute the root toolkit v3.05
can't post the link, somebody else have to do it.
a window opens --> close it (can't read chinese language)
another window should open --> klick on root.
wait after "success" appears.
Your phone should be restarting.
I'm using android 9 on my nubia x since a month and its working way better then android 8.
I'm not responsible if you brick your phone.
I give no guarantee
Click to expand...
Click to collapse
it's ok everything work fine, Nubia x android 9 with all google services OK exept voice match ( OK google from screen).
elnas1369 said:
it's ok everything work fine, Nubia x android 9 with all google services OK exept voice match ( OK google from screen).
Click to expand...
Click to collapse
Yeah I'm also looking for a solution how to remove this ****ty nubia voice and replace it with google.
Yeah it could be nice to replace it with Google assistant
I would install Android 9 but my fear is to loose all configurations, permissions, etc and It will take long time to reconfigure every thing.
My question is : is it really worth to install it or there are more or less the same performance?
Anyone knows if nubia X will have final android 9?
Guys!! I know this sounds stupid but I have no "update" option in my settings!! Please help if you know what is going on with my new Nubia X!
Shahin13 said:
Guys!! I know this sounds stupid but I have no "update" option in my settings!! Please help if you know what is going on with my new Nubia X!
Click to expand...
Click to collapse
Download the rom for Android 9, got to settings -> "System update", then from the menu up, select "Local update".
No issues with 3.05 - works fine, nothings from the apps, data or setting is flushed. But the phone is unrooted and you need to process it again.
But recently I have updated it from 3.03 to 3.11 and I can't find the root tool.
Anyone has idea where to find it?
Thanks.
3.11 play store
Looking allsou the rooting tool for 3.11. Needed play store.
【Version】16.0420.2006.30
【Model Name】ROG Phone (ZS600KL)
【Release Date】2020/08/11
【Release Note】
Improved the audio quality of the speaker when playing games.
3rd party app compability improved: QMZG
Updated Android security patch
Source : https://zentalk.asus.com/en/discuss...e-zs600kl-ww-16-0420-2006-30-android-p#latest
I am looking forward to all the beta testers that will complain about issues in this topic before i upgrade to P in 6 months
I am 99% sure that most things will not work, for example Magisk, edXposed, gravity box......
Anyone got the update?
imkentoy said:
Anyone got the update?
Click to expand...
Click to collapse
nope !!!!!!!!!!!!!!!!!!!!!!!!!!!
User War10K from Zen Talk communities has uploaded the WW Firmware link:
【Version】
16.0410.1910.91
【Model Name】
ROG Phone (ZS600KL)
【Release Date】
2019/11/28
https://www.asus.com/zentalk/forum....extra=page=1&filter=lastpost&orderby=lastpost
krkdesigns said:
User War10K from Zen Talk communities has uploaded the WW Firmware:
【Version】
16.0410.1910.91
【Model Name】
ROG Phone (ZS600KL)
【Release Date】
2019/11/28
https://www.asus.com/zentalk/forum....extra=page=1&filter=lastpost&orderby=lastpost
Click to expand...
Click to collapse
NO he didn´t !!!!
I downloaded the link and it worked perfectly. I have the update and it looks good. thanks for the tip and have a nice weekend
snoopy-doopy said:
NO he didn´t !!!!
Click to expand...
Click to collapse
Technically you're correct; he provided a link. But the link is valid.
I downloaded the file and flashed it, for now it works great
thx
krkdesigns said:
User War10K from Zen Talk communities has uploaded the WW Firmware:
【Version】
16.0410.1910.91
【Model Name】
ROG Phone (ZS600KL)
【Release Date】
2019/11/28
https://www.asus.com/zentalk/forum....extra=page=1&filter=lastpost&orderby=lastpost
Click to expand...
Click to collapse
Thanks for the link. Updated OP
That was a direct download link from asus server.
I've got serval bootloops before it start normally, plus the fist install i needed to format because failed boot, so it's very unstable and i'm also notice there no full stock recovery, but hopefully it will get one on stable.
Edit: it's happend again, it's not safe to use.
No OTA yet in HKG....keeps pressing the update button....
This will work on WW_ZS600KL ?
mauronofrio said:
This will work on WW_ZS600KL ?
Click to expand...
Click to collapse
Offical firmware website:
https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
New update WW-16.0410.1910.95
【Version】16.0410.1910.95
【Model Name】ROG Phone (ZS600KL)
【Release Date】2019/12/16
【Release Note】
Android P to Android P
1. User will encounter a brief black screen last for 3 to 5 minutes (Depending on the amount of data) after it finished the FOTA and reboot. Please do not force reboot the device because of the system has been checking, it would return to normal very soon.
2. Fixed the issue that TwinApps occasional not able to be launched
3. Fixed the Audio wizard can not be used in Russia
4. Fixed display error of Classic Theme Settings
5. Disabled BSNL VoLTE function in India
6. Fixed that screenshot could not be read by computer when device connects with computer
7. Fixed the game of Arena of Valor noise issue when live streaming with front camera
Android O to Android P
1. Upgraded system to Android P
2. User will encounter a brief black screen last for 3 to 5 minutes (Depending on the amount of data) after it finished the FOTA and reboot. Please do not force reboot the device because of the system has been checking, it would return to normal very soon.
3. Removed Page Marker, ZeniMoji, Report Location in Safeguard, weather animation setting, AI charging
4. Removed the Yandex cloud opetion of File Manager Application
5. Upgraded Game Center to Armoury Crate with whole new design
6. Added "Adaptive brightness", "Adaptive Battery", "New notifications", "Status bar icon manager", "Screen recorder", and "Local backup" in Settings
7. Upgraded Game Genie panel with new design and features
8. Added Android P "Swipe up on Home button" gesture
9. Support 24-hour forecast in Weather application
10. Revamped Mobile Manager, Contacts, File Manager, Calculator, Clock, Gallery, and Weather applications
Source : https://zentalk.asus.com/en/discuss...e-zs600kl-ww-16-0410-1910-95-android-p#latest
Do not update to android 9
Issue with phone callsAfter the update to Android pie, call drop in seconds while using bluetooth. This happens with the preloaded app and whatsapp calls.
Can anyone confirm if Volte still work after this update?
every time I tried to sideload the new firmware I get an error message "adb: failed to read command: No error" any suggestions to get it flashed to P?
mbze430 said:
every time I tried to sideload the new firmware I get an error message "adb: failed to read command: No error" any suggestions to get it flashed to P?
Click to expand...
Click to collapse
updating to pie its not working by sideloading you need to save the pie file to your storage and if you cant access your phone you can try flash the latest RAW File just find in other forums.
Well, after trying the RAW file a second time, it is now working. No clue what the deal was before. It shouldn't have even had Magisk installed still after flashing that RAW file, but it did, and was causing the problems.
Second flash actually reset everything. Can't delete this post though.
Android 10 last build that came out this march solved lots of problems but still had one that was unforgivable for me, the low volume of voice recording while using whatsapp, telegram and messenger, so I looked for a way to make a downgrade to android 9 and without having to unlock bootloader and I found one that worked and want to share with you:
Requirements/materials:
-Sony drivers for your phone (I got them by installing latest version of Sony PC companion)
-New flasher v20 (original thread: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426)
-XperiFirm (to download Android 9 firmware.) (you can get it by downloading flashtool or from the original post:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142)
-flashtool (I used 0.9.27.0 version) https://mega.nz/#!g24hXIQa!L22-invd46Onx7pzAEf0C4tkrAe87AR1JftRni8G6rA
Instructions:
1-open Xperifirm to download your firmware:
look your phone on the left side, then your specific model (in my case it was H8314, if you dont know your model check in your phone settings) once you selected your phone Xperifirm will show a list of firmwares on the right side, select one of the builds with the number 52.0.A.11.32 on it if you want the latest build of Android 9. In my case 52.0.A.11.32/R3B from chile worked (i´m from mexico). Once you have selected your build then click on the square button that is below of "availanle firmware" and a windows will open and show you two options to download the files, you hit the "Download" button. then another window will open and the program will start downloading your firmware.
Once it`s downloaded you should get this files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
except the folder that says "Decrypted", I will explain about such folder later.
2-Open Flashtool and Decrypt the firmware files
2.1-select the next options on the menu: Tools>Bundles>FILESET Decrypt
2.2-look for the path of the folder in which you downloaded your firmware, and then move to the right the three files you have on the left and click on convert.
It will take around five minutes to convert all the files, Once flashtool is done with that, it will ask you to create a bundle, click on "cancel" to close the window. So now if you look at the folder where you have the firmware files you got a new folder called "Decrypted" that I mentioned and that you saw in the picture above in step 1, if you open it, it will look like this:
with a folder called "boot" and another called "partition", and some files as well.
3-Download (if you have not) and extract New flasher v20 in a new folder
(link posted above in the "Requirements/materials" section)
You should get this files:
4-Preparing the firmware files:
4.1-open the firmware folder, select and delete all of the .ta files in the main folder.
4.2-Now open the ‘boot’ folder within the main firmware folder. There is one .ta file in here called ‘Apollo_XBootConfig_MiscTA‘ that you also need to delete.
(Note: something else instead of "apollo" could be in the name of the file depending on your phone model)
4.3-Now the final step in preparing your firmware, is to copy the entire contents of the firmware folder to the Newflasher folder.
Once complete, your Newflasher folder should look like something below. The highlighted files are those copied across from your firmware folder.
5-Flash Xperia firmware
If you’ve reached this stage, then that’s the hardest part done. This next section involves the process of actually flashing your Sony Xperia device.
5.1-Connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. You will see the led of your phone turns on and stays on, (that means it entered into flashmode)
5.2-Double click the ‘newflasher’ application as highlighted below.
5.3-A Windows command prompt will now open. It will ask you if you want to perform an optional step (if you need a gordongate flash drive) Type ‘n’ for no and press Enter.
5.4-newflasher will will ask you again if you want to perform an optional step, (dump trim area) Type ‘n’ for no and press Enter.
5.5-newflasher will ask you if you want to perform another optional step (flash bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots)Type "n" for no and press Enter.
5.6-Your Sony Xperia device will now begin to flash new firmware.
You will see some files going through during the flashing
5.7-newflasher will ask you if you want to perform another optional step(flash persist partition).Type "n" for no and press Enter.
You will see some other files going through the screen
6- Once complete, you will receive a message that “You can disconnect your device when you close newflasher.exe“.
Congratulations, your Sony Xperia device has now been successfully flashed to new firmware.
7-Disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected. To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
Final Note:
-some parts of this guide were obtained from here: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
I Did my best to attach good screenshots so the follow of the process could be be easier but I just realized the pictures are very tiny and pixelated, sorry, hopefully you will still understand as everything is explained in a very detailed way. If you know a goos site to attach images that I could use please let me know.
Oh, no. XperiFirm shows only the Android 10 firmware for H8314 in USA (Verizon). Verizon has no GSM, so Sony tweaked the US model to place calls ONLY over LTE. Where can I find the Android 9 firmware for USA?
UncleDick said:
Oh, no. XperiFirm shows only the Android 10 firmware for H8314 in USA (Verizon). Verizon has no GSM, so Sony tweaked the US model to place calls ONLY over LTE. Where can I find the Android 9 firmware for USA?
Click to expand...
Click to collapse
my thoughts about that are:
1-why are you looking for android 10 in this phone if it has so many bugs?
2does it really needs to be from USA? I dont think thats the only country with such configuration over calls.
and finally: 3- I think that such problem could be solved through configuration? or it has to do with the rom files?
ferluna18 said:
my thoughts about that are:
1-why are you looking for android 10 in this phone if it has so many bugs?
2does it really needs to be from USA? I dont think thats the only country with such configuration over calls.
and finally: 3- I think that such problem could be solved through configuration? or it has to do with the rom files?
Click to expand...
Click to collapse
Very good questions, thanks.
1. Why Android 10? Several thoughts. (a) the phone keeps bugging me to do it. (b) there may be features in Android 10 that would appear to me. (c) As far as I can tell, Android 9 is no longer getting any security fixes Having had several Android phones in the past that almost never got a security update, I have been pretty smug about my Sony "keeping up".
2. USA? Actually, "Global System for Mobile" (GSM) seems to mean "everybody in the whole planet except US and Japan." The Dual SIM version of the XZ2 Compact doesn't work on Verizon, only the H8413". Not being able to retreat to the "official" Android 9 for Verizon just worries me.
3. Configuration? Not willing to bet that Sony did not bury some code specific to Verizon in the "Official USA" firmware.
I absolutely LOVE this phone. Over the past year, it has become essential to my life. (Reads my diabetic sensor. Monitors my home security system. Keeps track of Amazon packages. Handles my 10 email accounts. Is my kitchen timer. Manages (what's left of) my calendar.) Seems like I pull out the phone at least 20-30 times a day. If I upgrade to Android 10 and it mangles my phone, I will be SO frustrated.
It is a great comfort that these forums have so many capable volunteers. If I start seeing posts, "Hey, I upgraded my Verizon H8413 and it works great!" , then I'll be much more likely to do it. So far, I simply don't see posts like that, only the opposite. And, "there's no way back." (I am sort of kicking myself that I failed to buy a second H8413 when they were on sale everywhere. I could just move the SIM card to it if Android 10 wrecks my current phone. That's how goofy I am. $400 for peace of mind.)
I understand, I have noticed something interesting about the update notification thing , I bought my phone on USA (xz2 compact single sim unlocked version) and of course it came with a US firmware so Igot the notification to update to Android 10 but very late, I don't know why, (android 10 March version) and I was hesitant about accepting such update but I did, then everything was okay except voice notes, the thing is that I decided to downgrade using the method I posted in this guide and installed a non US firmware, I have been using such firmware for like two weeks and the update center says that the next Android version is Android 10 but it doesn't give me the fastidious notification telling me that there is a mew update for my phone.
Hi, in Xperifirm Android 9 for H8324 ist just available as Rom for Saudi Arabia (52.0.A.11.32/R4B). Can I use this Rom for Europe, and is it including german language? Does anybodyknow?
Greetings Odiad
odiad said:
Hi, in Xperifirm Android 9 for H8324 ist just available as Rom for Saudi Arabia (52.0.A.11.32/R4B). Can I use this Rom for Europe, and is it including german language? Does anybodyknow?
Greetings Odiad
Click to expand...
Click to collapse
I successfully flashed the Saudi Arabian version 52.0.A.11.32/R4B from XperiFirm onto my XZ2c. There is possibility to choose German as language. My carrier (Tele2 / Sweden) works fine.
I was struggling trying to flash the phone using FlashTool and its .fsc scripts, but when i used newflasher with the advice given in this thread it worked perfectly.
Good luck!
PS. No more unresponsive touchscreen!
pyraohms said:
I successfully flashed the Saudi Arabian version 52.0.A.11.32/R4B from XperiFirm onto my XZ2c. There is possibility to choose German as language. My carrier (Tele2 / Sweden) works fine.
I was struggling trying to flash the phone using FlashTool and its .fsc scripts, but when i used newflasher with the advice given in this thread it worked perfectly.
Good luck!
PS. No more unresponsive touchscreen!
Click to expand...
Click to collapse
Hi Pyraohms.
-> Just to be sure - you did the downgrade with locked bootloader, correct?
-> And do you have now the update-info for android 10 in notification? Or is updating after downgrade just manually possible (if a perfect Android 10 will appear)?
Edit: I couldn't wait for an answer, because Android 10 annoyed me again. I tried successfully to downgrade with locked bootloader. All went fine. Now on Android 9 again fingerprintsensor works great again without lags..... I forgot how good it feels
odiad said:
Edit: I couldn't wait for an answer, because Android 10 annoyed me again. I tried successfully to downgrade with locked bootloader. All went fine. Now on Android 9 again fingerprintsensor works great again without lags..... I forgot how good it feels
Click to expand...
Click to collapse
Nice. Yeah, the fingeprint sensor works much better with A9, but I still get random freezes when unlocking and the screen becomes unresponsive until I hit the power button to lock and then use the sensor to unlock again. Does anybody else experience this?
I will probably send the unit for repair before my warranty is out. Should probably install the nordic version of A10 first though.
pyraohms said:
Nice. Yeah, the fingeprint sensor works much better with A9, but I still get random freezes when unlocking and the screen becomes unresponsive until I hit the power button to lock and then use the sensor to unlock again. Does anybody else experience this?.
Click to expand...
Click to collapse
Hi pyraohms. Up to now I haven't had this problem. Not with the original Android 9 (before update to Android 10), and also not after downgrading according to the guide in this thread.
Good luck that you can solve this....
odiad said:
Hi pyraohms. Up to now I haven't had this problem. Not with the original Android 9 (before update to Android 10), and also not after downgrading according to the guide in this thread.
Good luck that you can solve this....
Click to expand...
Click to collapse
Do you know which firmware version that you had before? Latest A9? If not, maybe we can get hold of an old version that do not have these issues somehow.
EDIT: Im downloading 52.0.A.3.27 from XperiFirm to try it now.
Has anyone been able to verify that flashing the Chile firmware on an H8314 on the Verizon network is possible?
I'd really love to get my phone's usability back!! But I'm also afraid to flash something that might not work as this is pretty much right at the edge of my technical scope. I think I would not know how to fix it if the firmware didn't work right.
pyraohms said:
I successfully flashed the Saudi Arabian version 52.0.A.11.32/R4B from XperiFirm onto my XZ2c. There is possibility to choose German as language. My carrier (Tele2 / Sweden) works fine.
I was struggling trying to flash the phone using FlashTool and its .fsc scripts, but when i used newflasher with the advice given in this thread it worked perfectly.
Good luck!
PS. No more unresponsive touchscreen!
Click to expand...
Click to collapse
Is it still the case that downgrading from android 10 51.1.A.0.672 to android 9 52.0.A.11.32 fixes the touchscreen issues?
theuchi said:
Is it still the case that downgrading from android 10 51.1.A.0.672 to android 9 52.0.A.11.32 fixes the touchscreen issues?
Click to expand...
Click to collapse
Unfortunately no. I tried this but when problems persisted I had the unit sent for repair. And I got it back with the remark "firmware reinstalled - passes functional tests". Phone was working OK for some week, then the touchscreen issues got back :/
hello,
according to this downgrade instruction I have to delete .ta-files. What is the reason for that? I am asking because I was on LOS17 (open bootloader and twrp), but had randomly freezing screen and I went back to android 9 using News-flasher (as described in this instruction). Now sometimes I have also in Stock Android 9 randomly freeze of screen. I never had this when I was in Android 9 before Android and LOS17 . So reason could be bootloader/twrp, or maybe that anything from LOS17 remains after flashing stock android 9.
- Is flashing Android 9 including delete .ta-files before just a kind of partly installation, that parts of former Rom can be still in firmware?
- What happens if .ta-files are not deleted before flashing?
Greetings Odiad
ferluna18 said:
Android 10 last build that came out this march solved lots of problems but still had one that was unforgivable for me, the low volume of voice recording while using whatsapp, telegram and messenger, so I looked for a way to make a downgrade to android 9 and without having to unlock bootloader and I found one that worked and want to share with you:
Requirements/materials:
-Sony drivers for your phone (I got them by installing latest version of Sony PC companion)
-New flasher v20 (original thread: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426)
-XperiFirm (to download Android 9 firmware.) (you can get it by downloading flashtool or from the original post:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142)
-flashtool (I used 0.9.27.0 version) https://mega.nz/#!g24hXIQa!L22-invd46Onx7pzAEf0C4tkrAe87AR1JftRni8G6rA
Instructions:
1-open Xperifirm to download your firmware:
look your phone on the left side, then your specific model (in my case it was H8314, if you dont know your model check in your phone settings) once you selected your phone Xperifirm will show a list of firmwares on the right side, select one of the builds with the number 52.0.A.11.32 on it if you want the latest build of Android 9. In my case 52.0.A.11.32/R3B from chile worked (i´m from mexico). Once you have selected your build then click on the square button that is below of "availanle firmware" and a windows will open and show you two options to download the files, you hit the "Download" button. then another window will open and the program will start downloading your firmware.
Once it`s downloaded you should get this files:
except the folder that says "Decrypted", I will explain about such folder later.
2-Open Flashtool and Decrypt the firmware files
2.1-select the next options on the menu: Tools>Bundles>FILESET Decrypt
2.2-look for the path of the folder in which you downloaded your firmware, and then move to the right the three files you have on the left and click on convert.
It will take around five minutes to convert all the files, Once flashtool is done with that, it will ask you to create a bundle, click on "cancel" to close the window. So now if you look at the folder where you have the firmware files you got a new folder called "Decrypted" that I mentioned and that you saw in the picture above in step 1, if you open it, it will look like this:
with a folder called "boot" and another called "partition", and some files as well.
3-Download (if you have not) and extract New flasher v20 in a new folder
(link posted above in the "Requirements/materials" section)
You should get this files:
4-Preparing the firmware files:
4.1-open the firmware folder, select and delete all of the .ta files in the main folder.
4.2-Now open the ‘boot’ folder within the main firmware folder. There is one .ta file in here called ‘Apollo_XBootConfig_MiscTA‘ that you also need to delete.
(Note: something else instead of "apollo" could be in the name of the file depending on your phone model)
4.3-Now the final step in preparing your firmware, is to copy the entire contents of the firmware folder to the Newflasher folder.
Once complete, your Newflasher folder should look like something below. The highlighted files are those copied across from your firmware folder.
5-Flash Xperia firmware
If you’ve reached this stage, then that’s the hardest part done. This next section involves the process of actually flashing your Sony Xperia device.
5.1-Connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. You will see the led of your phone turns on and stays on, (that means it entered into flashmode)
5.2-Double click the ‘newflasher’ application as highlighted below.
5.3-A Windows command prompt will now open. It will ask you if you want to perform an optional step (if you need a gordongate flash drive) Type ‘n’ for no and press Enter.
5.4-newflasher will will ask you again if you want to perform an optional step, (dump trim area) Type ‘n’ for no and press Enter.
5.5-newflasher will ask you if you want to perform another optional step (flash bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots)Type "n" for no and press Enter.
5.6-Your Sony Xperia device will now begin to flash new firmware.
You will see some files going through during the flashing
5.7-newflasher will ask you if you want to perform another optional step(flash persist partition).Type "n" for no and press Enter.
You will see some other files going through the screen
6- Once complete, you will receive a message that “You can disconnect your device when you close newflasher.exe“.
Congratulations, your Sony Xperia device has now been successfully flashed to new firmware.
7-Disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected. To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
Final Note:
-some parts of this guide were obtained from here: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Click to expand...
Click to collapse
Thank you so much for this bro. Android 10 for my xperia xz2 compact ruined my device. Now after i follow your tutorial/instructions to downgrade to Android 9, my xperia xz2 compact become smooth as new specially the fingerprint now is very quick responsive.
ferluna18 said:
Android 10 last build that came out this march solved lots of problems but still had one that was unforgivable for me, the low volume of voice recording while using whatsapp, telegram and messenger, so I looked for a way to make a downgrade to android 9 and without having to unlock bootloader and I found one that worked and want to share with you:
Requirements/materials:
-Sony drivers for your phone (I got them by installing latest version of Sony PC companion)
-New flasher v20 (original thread: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426)
-XperiFirm (to download Android 9 firmware.) (you can get it by downloading flashtool or from the original post:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142)
-flashtool (I used 0.9.27.0 version) https://mega.nz/#!g24hXIQa!L22-invd46Onx7pzAEf0C4tkrAe87AR1JftRni8G6rA
Instructions:
1-open Xperifirm to download your firmware:
look your phone on the left side, then your specific model (in my case it was H8314, if you dont know your model check in your phone settings) once you selected your phone Xperifirm will show a list of firmwares on the right side, select one of the builds with the number 52.0.A.11.32 on it if you want the latest build of Android 9. In my case 52.0.A.11.32/R3B from chile worked (i´m from mexico). Once you have selected your build then click on the square button that is below of "availanle firmware" and a windows will open and show you two options to download the files, you hit the "Download" button. then another window will open and the program will start downloading your firmware.
Once it`s downloaded you should get this files:
except the folder that says "Decrypted", I will explain about such folder later.
2-Open Flashtool and Decrypt the firmware files
2.1-select the next options on the menu: Tools>Bundles>FILESET Decrypt
2.2-look for the path of the folder in which you downloaded your firmware, and then move to the right the three files you have on the left and click on convert.
It will take around five minutes to convert all the files, Once flashtool is done with that, it will ask you to create a bundle, click on "cancel" to close the window. So now if you look at the folder where you have the firmware files you got a new folder called "Decrypted" that I mentioned and that you saw in the picture above in step 1, if you open it, it will look like this:
with a folder called "boot" and another called "partition", and some files as well.
3-Download (if you have not) and extract New flasher v20 in a new folder
(link posted above in the "Requirements/materials" section)
You should get this files:
4-Preparing the firmware files:
4.1-open the firmware folder, select and delete all of the .ta files in the main folder.
4.2-Now open the ‘boot’ folder within the main firmware folder. There is one .ta file in here called ‘Apollo_XBootConfig_MiscTA‘ that you also need to delete.
(Note: something else instead of "apollo" could be in the name of the file depending on your phone model)
4.3-Now the final step in preparing your firmware, is to copy the entire contents of the firmware folder to the Newflasher folder.
Once complete, your Newflasher folder should look like something below. The highlighted files are those copied across from your firmware folder.
5-Flash Xperia firmware
If you’ve reached this stage, then that’s the hardest part done. This next section involves the process of actually flashing your Sony Xperia device.
5.1-Connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. You will see the led of your phone turns on and stays on, (that means it entered into flashmode)
5.2-Double click the ‘newflasher’ application as highlighted below.
5.3-A Windows command prompt will now open. It will ask you if you want to perform an optional step (if you need a gordongate flash drive) Type ‘n’ for no and press Enter.
5.4-newflasher will will ask you again if you want to perform an optional step, (dump trim area) Type ‘n’ for no and press Enter.
5.5-newflasher will ask you if you want to perform another optional step (flash bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots)Type "n" for no and press Enter.
5.6-Your Sony Xperia device will now begin to flash new firmware.
You will see some files going through during the flashing
5.7-newflasher will ask you if you want to perform another optional step(flash persist partition).Type "n" for no and press Enter.
You will see some other files going through the screen
6- Once complete, you will receive a message that “You can disconnect your device when you close newflasher.exe“.
Congratulations, your Sony Xperia device has now been successfully flashed to new firmware.
7-Disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected. To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
Final Note:
-some parts of this guide were obtained from here: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Click to expand...
Click to collapse
Hi. Could you reload or restore the pictures attached in the first post?
dario82ct said:
Hi. Could you reload or restore the pictures attached in the first post?
Click to expand...
Click to collapse
Would really appreciate this as well. I got my phone back from Sony repairs under warranty but it's a refurbed phone with Android 10. Ew. With 5 mins of Pokego it drains 2% already so I am really anxious about either the battery life on this refurbed phone is **** (I had 92% on my old handset from 2 years of use), or if it's Android 10 being the culprit.
Also if this method doesn't include unlocking bootloader, does it mean my warranty won't be voided? (Any idea, I got 4 months left on warranty).
Instead of getting the software from xperifirm since it's all android 10 on it now, I downloaded the prev version I had of Pie 52.0.A.3.27 from the Sony developer website. Would I be able to use that instead? I tried unpacking it but it's so different to the files that I downloaded from xperifirm..... sorry I have no idea what I am doing.
Alternatively, would it be safe to download and flash the "Commercial and Journalists" version (I live in New Zealand) since it seems like it's the only Pie build on Xperifirm?
harpnote said:
Would really appreciate this as well. I got my phone back from Sony repairs under warranty but it's a refurbed phone with Android 10. Ew. With 5 mins of Pokego it drains 2% already so I am really anxious about either the battery life on this refurbed phone is **** (I had 92% on my old handset from 2 years of use), or if it's Android 10 being the culprit.
Also if this method doesn't include unlocking bootloader, does it mean my warranty won't be voided? (Any idea, I got 4 months left on warranty).
Instead of getting the software from xperifirm since it's all android 10 on it now, I downloaded the prev version I had of Pie 52.0.A.3.27 from the Sony developer website. Would I be able to use that instead? I tried unpacking it but it's so different to the files that I downloaded from xperifirm..... sorry I have no idea what I am doing.
Alternatively, would it be safe to download and flash the "Commercial and Journalists" version (I live in New Zealand) since it seems like it's the only Pie build on Xperifirm?
Click to expand...
Click to collapse
Hello. I have downgraded to android 8 (having tried them all since I bought the phone, it's my favorite), and everything works great again! The fingerprint sensor is very fast, no more bugs in whatsapp audio messages, the battery lasts much longer than Android 10.
The procedure in the first post is slightly imperfect, as on Xperifirm, the firmwares are downloaded already decrypted (in practice you have to skip steps 2 and 2.1 of the guide).
Obviously I don't take responsibility, but it worked for me.
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 !