9.0.0.187 OTA released for C432 - Huawei Mate 20 X Guides, News, & Discussion

Android security patch: 1 February 2019
Kernel version: 4.9.97
{
"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"
}

Usually the C636 would get the updates before C432 but seems to be the other way around this time.

still no color ai for pictures?

We are releasing monthly security updates for flagship models. This security update includes Google and Huawei patches.
Click to expand...
Click to collapse
Great news, but why not march security update now? It's already listed on the website.
https://consumer.huawei.com/en/support/bulletin/2019/3/

C636 stuck on 184 still...

C432 stuck on 9.0.0.172 with security patch from 1 December 2018 here in the UK.
I am not impressed when I read of so many others getting newer updates. I check for updates a few timer every day, but always get the response that my phone has the latest software. Made worse that the boot loader is locked and I am not aware of any means to flash newer software versions myself as I have done with previous phones.
AJP

I saw on funki site that 191 version is available, Huawei is really slow af

I worked out a way to force an full update, which appears to have worked, at least for me.
From the Settings menu, choose Apps, then Apps again, find Software update and select it. Then choose Storage, and first CLEAR CACHE and then CLEAR DATA. Then go back out to Settings and choose System then Software Update again. This time choose the three dots at the top right hand side and ask for full update. This finally triggered my mobile to update from .172 to the new .187 mentioned in the OP.
My phone has just upgraded after downloading a full 3.3 GB instead of the incremental updates. Phew, so all is now well with the world...
AJP

ajp558 said:
I worked out a way to force an full update, which appears to have worked, at least for me.
From the Settings menu, choose Apps, then Apps again, find Software update and select it. Then choose Storage, and first CLEAR CACHE and then CLEAR DATA. Then go back out to Settings and choose System then Software Update again. This time choose the three dots at the top right hand side and ask for full update. This finally triggered my mobile to update from .172 to the new .187 mentioned in the OP.
My phone has just upgraded after downloading a full 3.3 GB instead of the incremental updates. Phew, so all is now well with the world...
AJP
Click to expand...
Click to collapse
Cheers AJP, that worked for me.

Doesn't work on C636

Just got this notification.

ajp558 said:
I worked out a way to force an full update, which appears to have worked, at least for me.
From the Settings menu, choose Apps, then Apps again, find Software update and select it. Then choose Storage, and first CLEAR CACHE and then CLEAR DATA. Then go back out to Settings and choose System then Software Update again. This time choose the three dots at the top right hand side and ask for full update. This finally triggered my mobile to update from .172 to the new .187 mentioned in the OP.
My phone has just upgraded after downloading a full 3.3 GB instead of the incremental updates. Phew, so all is now well with the world...
AJP
Click to expand...
Click to collapse
Thanks mate that also worked for me to, downloading now

Related

[Tutorial] Capture Samsung OTA Update to .bin File

***Mods - I think this belongs here (whether it's useful or not). If not, have your way with it. Thanks!***
I recently had to re-flash my firmware after poking a little too deeply into my /system folder. Once I got back up and running, I checked for software updates and there was one (I imagine to take me to UELA1?). Downloaded it, asked to reboot and it failed. I thought if I could find the update, I could apply it through ADB or CWM...that's not the case either. But, here's the steps I took to find it...and unfortunately, my method requires some paid software. There may be another, cheaper way to do it, but I like easy.
Go to "Settings" > "About Device" > "Software Update" > "Update". If you've never done this, it's going to ask you what country your in.
Click on "Download" on the next screen and take note of the size of the file.
{
"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"
}
It should download the package and then ask if you want to install it or wait til later. Choose "Later" and pick any amount of time that suits you.
Knowing that in order for it to install an update at the next reboot, I figured there would have to be an auto start entry somewhere. I started up JRummy's ROM Toolbox Pro and selected "Auto Start Manager". Sure enough, there were two "Software Update" entries...
Long press on one of them and choose "Manage"
If you got lucky, like me, the "Application Info" screen will pop up and you'll see under "Storage" that it's using around the same amount of space as the download needed. If not, long press on the other and select "Manage".
Now, fire up Speed Software's SQLite Editor and it should've parsed all of the SQLite databases on your phone and given you a list of them, like so...
Now this is trial & error...select the "Software Update" database and I happen to know we're looking for one with the "wssdmdatabase.db" in it...
Select the "wssdmdatabase.db" database and you should get a screen resembling this...
Now select "Fumo" and long press the only entry under "Fumo" and select "Edit Record". You'll be presented with the following screen...
You're concerned with the entry with the arrow next to it. Enter it exactly as you see it in your browser and it will download the file to your PC. Voila!
Now, you're asking what do we do with the .bin file...good question. I was hoping someone on here might have an answer to that. Mainly because I can't stand Samsung's bloatware called "Kies". I'd love to be able to find a way to update our tabs even after root and all that good stuff.
Excellent Find! Congrats. Love It.
Will this file ever dissappear if not installed? for example, I know Kies updates will be auto deleted within about 2 minutes after updating.
bravo.
sbin/redbend_ua is used for flashing FOTA. And Kies updates are encrypted, if that helps any.
chrisrotolo said:
Excellent Find! Congrats. Love It.
Will this file ever dissappear if not installed? for example, I know Kies updates will be auto deleted within about 2 minutes after updating.
bravo.
sbin/redbend_ua is used for flashing FOTA. And Kies updates are encrypted, if that helps any.
Click to expand...
Click to collapse
As this file now resides on your PC (or on your tab, as this process works from it also), it should remain there until you delete it.
I use kies windows temp folder capturing .md5 method
Why don't you just download the update from Samsung update server and flash it with Odin?

How do I disable OTA notifications on a rooted S7 (android v6)?

On my S6, when it was rooted, OTA updates and all OTA notifications disappeared immediately.
But not the same on the S7. Admittedly I rooted it *after* the android v7 OTA update started appearing.
Now I see it in two places:
1) Under Settings it says Software update - tap here to update the firmware...
2) In the pulldown notification panel I see Software Update - download failed
What is the procedure for cleaning all this up? I am a hardware/software developer. I have e.g. Root Explorer, Titanium Backup, MyBackupPro, Disable Service... I have googled all over the place and found various things but none of them appear on my phone.
Actually I am not sure it is trying to download the updates. It may just be popping up the "failed" notifications.
I did clear the cache partition (power+home+vol up) but that didn't remove the nags and the failed update notifications.
I would really appreciate some help. Android 6.0.1.
Try clearing data from the software update apps in Settings > Apps > 3 dots top right menu > Show system apps > Software update (There are two) > Storage > Clear Data
If you cleared the cache already, you can hit the "Install update" button and it will fail as you already deleted the system update file
Thank you.
I cleared the storage for the first app, and the clearing buttons for the 2nd one were greyed-out.
The nags are still there. This time I have done screenshots:
{
"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"
}
What concerns me about the last one is that if I select Download it will probably download the OTA update and apply it, wiping out the root.
Incidentally, the Android Pay app still starts up, which isn't supposed to work after a root I have read about some root methods which preserve this but the procedures were complicated and I didn't apply it AFAIK. I used these:
OTA shouldn't download if you are rooted, it will fail
Are you definitely rooted? That's an old version of ODIN, should be using 3.12.3 or newer, I've not rooted mine but from what I hear *(Could be Nougat only) CF Auto root doesn't work, needs SuperSU zip flashed from TWRP
But like I say I haven't rooted so am not up to date with what does and doesn't work atm
Worst comes to worst, you flash Marshmallow stock ROM again and start fresh if it does update you to Nougat
There is root for Nougat too btw (Which model S7?)
Root Checker reports rooted OK. Root Explorer sees everything. So it does appear to be rooted, in the traditional sense. Titanium Backup also works as it normally does on a rooted phone (I also have a rooted S6 v5 and T705 v4.4.2).
The reason I didn't update the OS is because I have loads of apps installed and I don't want to lose the config. I haven't been able to find out what exactly disappears but there are widespread reports of the update losing lots of app config.
Do you think I should try the download and maybe that will fail and clear the nags?
The S7 is a UK official stock one, SM-G930F 6.0.1 G930FXXU1BPJJ.
Since I know how to wipe the cache, I thought it should be safe to download the update. Even though the phone is rooted, that did work! So I downloaded the 1.2GB and then wiped the cache partition. But the two nags (the one appearing under Settings, every time the app is started) and this one which appears when I click on the nag in the pulldown list (apologies for not using the correct terminology):
are still there.
What will be interesting is whether the big popup nag (which has been appearing many times each day, with the frequency increasing recently) will disappear. I have not seen it yet this morning...
Surely, on a rooted phone, one can drop in some file(s), or rename some files, to block the updates? There is a ton of stuff on this for previous android versions online but as usual most of it doesn't work on this phone - the files are usually missing.
EDIT: it must also be possible to set up a "lmhosts" file which blocks the Samsung update server domain. I found this
https://www.howtogeek.com/140576/how-to-edit-the-hosts-file-on-android-and-block-web-sites/
and it seems very simple. I just need to find out the domain The hosts file is under /system/etc. It contains just
127.0.0.1 localhost
::1 ip6-localhost
Also, this
https://source.android.com/devices/tech/ota/
suggests that renaming e.g. otacerts.zip would stop OTA. I have renamed it to otacerts.zip-bak and that has done something. The above screenshot still appears but after about 10 seconds! This is of little use so I renamed it back. I suspect that messing with the certificates file just prevents the update installing, but doesn't prevent the nag and the download.
The funniest thing is that I have a phone with full root access but Android Pay works. I have been using it all day today
Clearly, for an S7 with this specific firmware and using that specific version of Odin, this is what you get... Extremely useful.
Well, no more response here, but I fixed the main nag - the one in the pulldown list. I used this method
https://forum.xda-developers.com/verizon-s7-edge/help/block-nougat-update-t3581529
i.e. BK Package Disabler Pro and see posts #7 onwards. The one to search for was com.wssyncmldm and disabling that and rebooting the phone did it.
This is S7 (not Edge) on android v6 (lollipop I think it is called).
I still get the Software Update thing under Settings but it is dead - clicking on it does nothing so it is harmless.

New update now live (MR1 -Oreo 8.1)

{
"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"
}
Not included in the changelog is the addition of a feature from Paranoid Android, locking recent tasks! And multitouch has also been fixed
Update is a rollout so you may not have it yet.
Factory images now live, check out @linuxct post here
If you come across any bugs please be detailed about it and leave bug reports.
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Wow, just when I finished wiping all my data and installing a Resurrection Remix. Ironic.
Is there any way to extract the camera apk to install it in my current ROM?
guys please i need help. has anyone successfully installed razers stock img files?
After the update, my sim card is no longer being detected. I tried restarting, shutting down, and turning back on. It was working perfectly fine before I restarted after updating.
Edit: It may be the sim card actually died. I tried it on another phone and it doesn't work there either. So it seems like coincidence that it died after the update.
Hmmmmm update fails for me. Not rooted bootloader locked. Error couldn't update installation issue helpfull error.
Fastboot images now live: https://developer.razer.com/razer-phone-dev-tools/factory-images/
Direct link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Taking a hell of a long time to install.... I'm using Snap Camera these days, which is great, I wonder what the new portrait mode is like..... But I can't see me changing back to stock now..
What is the best way to update when I'm rooted and have TWRP installed?
SeriousFlash said:
What is the best way to update when I'm rooted and have TWRP installed?
Click to expand...
Click to collapse
Use the factory images posted here
My update also fails when I'm not rooted and have my bootloader locked
My may update is now installing itself. I do wish it had prompted me rather than having to run a manual update as I was just going through some setting and clicked the update in error.
Updated and noticed loads of fixes, however, Bluetooth is now a complete no go with my car stereo. Sometimes I manage to actually connect it and can play music by pressing play on the phone but no song titles are shown on the car and music playback controls don't work at all... Has anyone had a similar issue or an idea as to what's wrong?
linuxct said:
Use the factory images posted here
Click to expand...
Click to collapse
How would I go about doing that then?
Make sure you go to Settings, system and Razer Preferences and Disable the Share Data again... it gets turned on with the update.
Got the OTA this Morning on my Three branded device and installed without issue.
Nice to see a timely release of the monthly security fixes - is this a benefit of Project Treble support ?
ccjack said:
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Click to expand...
Click to collapse
Just use the factory images but before flashing, edit the flash_all.bat go to the line that reads %fastboot_cmd% erase userdata" and put a pound "#" sign before the line so that adb ignores that line. Also do the same at the end of the script where you see "%fastboot_cmd% reboot". Doing the following will stop the script from formatting your data partition and keep your phone in download mode after the flashing process. Now you can do the "fastboot boot twrp-whatever-filename.img" and boot to twrp like you were to root like before and once in twrp, flash twrp zip and magisk zip same as before. Everything should work fine now.
Again. Make sure you edit the bat file so the factory images dont factory reset your data partition.
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Is there still no way to update and keep twrp?
navin2max said:
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Click to expand...
Click to collapse
Where I can fine a Nokia cam app?

Which GMS workaround is still working without hiccups?

Thinking whether to buy a used P40 Pro which is going cheap right now, but looking at all the guides/threads, it seems there are still many hoops to jump around and Google keeps blocking these loopholes.
Is this accurate? Any sure-fire way for GMS to work on P40 Pro before I purchase them?
Thanks!
dylansmith said:
Thinking whether to buy a used P40 Pro which is going cheap right now, but looking at all the guides/threads, it seems there are still many hoops to jump around and Google keeps blocking these loopholes.
Is this accurate? Any sure-fire way for GMS to work on P40 Pro before I purchase them?
Thanks!
Click to expand...
Click to collapse
There is working method but the main thing is to be at the right FW version at the start to let install the GMS.
Once done you can easily update your phone without issues.
The problems you read here and there are mainly caused by users who don't want to downgrade to the right FW version.
Or by users not knowing (or not reading) the how to downgrade.
From my side it is running perfectly (banks apps and all others) since the beginning.
It is a must buy if the prices are going down ?
Does this mean we will always be stuck on the old firmware and won't be able to receive the latest security patches? Sounds worrying to me, and not sure whether that's worth the upgrade from my P30 Pro.. ?
You will receive new updates and security patches. You just have to follow the instructions exactly.
May I check whether this guide is the latest and can be installed along with microG?
https://forum.xda-developers.com/hu...uide-method-to-install-google-mobile-t4120143
Hi guys, I got stuck at this screen when trying to downgrade my firmware. Have already disabled all firewall and windows security. Why is it still showing no internet connection??
Also I noticed I'm unable to paste the full URL in the Proxy. Is this normal?
http://update.dbankcdn.com/TDS/data/files/p3/s15/G5633/g1604/v410049/f1/full//update_full_base.zip
{
"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"
}
try again with older HiSuite Version: 10.0.0.510: https://www.dropbox.com/s/y5d70lvntv5z9jk/HiSuite_10.0.0.510_OVE.zip?dl=1
İt has to be a great deal for you to go through all that hassle. Otherwise not worth it
starbase64 said:
try again with older HiSuite Version: 10.0.0.510: https://www.dropbox.com/s/y5d70lvntv5z9jk/HiSuite_10.0.0.510_OVE.zip?dl=1
Click to expand...
Click to collapse
now I managed to flash & install the firmware, but upon phone auto-reboot, it says the data partition is corrupted. what should I do?
dylansmith said:
now I managed to flash & install the firmware, but upon phone auto-reboot, it says the data partition is corrupted. what should I do?
Click to expand...
Click to collapse
Just format it and the phone will boot. This is part of the process.
Have gms working perfectly on my p40 pro
My issue now is being stuck on firmware 131. OTA doesn't detect new updates and HiSuite shows no Internet connection even though there's no proxy and my Internet is working well.
Risk free??
Is there a risk of adding malware using any of the methods described for adding Google services?
downgraded to 131 to install GMS first, then upgraded to 142 and 172 via OTA thereafter. now on 172.
When switching off WiFi to go to Mobile Data mode, the phone does NOT get any data unless I toggle between
LTE/WDCMA/GSM
and
WDCMA/GSM
MANUALLY.
I have to do this EVERY TIME I go from WiFi to Mobile Data mode. Any way to overcome this issue?

Cannot find updates on rooted phone

Hello,
I have a rooted EU phone (4a, not the 5g version). The OTA updater does not find the security updates, and all the rooting guides seem to indicate that they should show.
{
"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"
}
How can I check what's going on?
Long, more detailed version:
I have rooted my Pixel 4a (using Magisk). I think I have done things right¹, but my phone seems to be unable to find the November security update. I thought it was just a lag in the rollout of the update, but I got a message warning me that "it has been two weeks and I haven't installed the update yet".
When I go to Settings → System → Advanced → System update, it tells me my system is up to date, with Android 11 and the security update from the 5th October 2020.
I have tried removing Magisk to no avail, the update still does not show.
Does anybody know what's happening, or what I am missing?
¹ For what it's worth, the flashed version of the OS is sunfish-rp1a.201005.006 (using the flash-all.sh, then I have flashed the bootloader that came with it, patched with Magisk Manager beforehand).
You will need to flash back the stock boot.img and then search for updates, as if you mess with that (you did by rooting) you wont get OTA updates.
Thanks. I'll try that once I've figured how to do a full system backup.
You could simply sidleload the ota since you know it's there
Beware u will need to repatch your boot.img to have root again after applying the dec ota update.
I just tried sideloading the december OTA update (201205.008). It seemed sucessful from adb, but got stuck on the boot animation for a few minutes, and I ended up force-rebooting the phone. When the operating system started, I was still on 201005.006.
To be completely honest, I'm far too unfamiliar with the Android flashing and boot process to be confident in anything I'm doing here. I'm fairly comfortable with Linux and its boot process, but Android albeit similar is too different. I need to read up on that.

Categories

Resources