Related
I noticed the audio level can sometimes be a little low, despite being at the same volume setting. Restarting the device seems to resolve the issue, though In looking for the audio settings it appears as though i don't have any audio options, i.e Histen sound and audio equalizer. These options were previously available under EMUI 5.1, but not on EMUI 8.
Any ideas?
I'm on EMUI 8 and everything is here. Do you have any mod installed? https://imgur.com/b5XnFBy https://imgur.com/Khb5cWt
Paulo87 said:
I'm on EMUI 8 and everything is here. Do you have any mod installed? https://imgur.com/b5XnFBy https://imgur.com/Khb5cWt
Click to expand...
Click to collapse
Thanks. No mods are installed for audio. This is what i see:
https://imgur.com/a/IncHN
My 'about phone' page shows exactly what yours does.
@mightyjcb :
What's your firmware version ?
C900B321 ?
mightyjcb said:
Thanks. No mods are installed for audio. This is what i see:
https://imgur.com/a/IncHN
My 'about phone' page shows exactly what yours does.
Click to expand...
Click to collapse
If your version is C432, i would suggest that you backup everything, plug it to your pc and restore your phone.
If you have a different version, it might be due to licensing. Best of luck :good:
oslo83 said:
@mightyjcb :
What's your firmware version ?
C900B321 ?
Click to expand...
Click to collapse
I'm using C432. Running b360a
mightyjcb said:
I'm using C432. Running b360a
Click to expand...
Click to collapse
And you updated from wich version ? Any rebrand during the way ?
Are you using a simcard ? Which carrier, mnc and mcc ?
I saw some histen config references on some xml or prop...
oslo83 said:
And you updated from wich version ? Any rebrand during the way ?
Are you using a simcard ? Which carrier, mnc and mcc ?
I saw some histen config references on some xml or prop...
Click to expand...
Click to collapse
I updated to Oreo B360 using the OldDroid method from what i think was the last update issued to Nougat OTA by Huawei/Honor.
I then installed LOS 15.1 and reverted back to EMUI 8 by flashing :
System (stock)
Recovery (stock)
KERNEL_B360a_TOUCH_FIX, then flashed the stock kernel over the touch fix image.
Mostly from your advice in thread https://forum.xda-developers.com/honor-9/help/oreo-nougat-recovery-stf-l09-t3760961)
No rebranding took place.
I have a sim card in the phone on the Giff Gaff network (Uses o2 infrastructure).
MCC: 234
MNC: 10
Cheers
No viper4android ?
Bluetooth headset ?
Sincebyou reverted back to EMUI 8 from LOS15 by flashing stock System then stock recovery:
Did you performed a full system wipe in stock recovery ? This may bee needed.
Matte, if you have a pc, connect your phone to your pc and in hisuite there's an option to restore your phone. It will install the latest full package. If you don't own a pc or don't want to use your pc, you can always try going in to the settings menu> System> System update> Options> Download latest full package.
Make sure you backup all of your data in both cases. Good luck.
oslo83 said:
No viper4android ?
Bluetooth headset ?
Sincebyou reverted back to EMUI 8 from LOS15 by flashing stock System then stock recovery:
Did you performed a full system wipe in stock recovery ? This may bee needed.
Click to expand...
Click to collapse
No viper4android has ever been installed. No bluetooth headset has ever been used with the device.
A full system wipe and stock recovery was necessary in order to go back to EMUI8 from LOS.
Paulo87 said:
Matte, if you have a pc, connect your phone to your pc and in hisuite there's an option to restore your phone. It will install the latest full package. If you don't own a pc or don't want to use your pc, you can always try going in to the settings menu> System> System update> Options> Download latest full package.
Make sure you backup all of your data in both cases. Good luck.
Click to expand...
Click to collapse
I can try the restore using Hisuite on my PC later. In the meantime, using the 'Download latest full package' simply returns no update available. The same to pressing 'Check For Updates' on the System Updates page. Which i think is probably the correct behavior given that i am running the latest version available.
I have exactly same problem as you. No Histen sound effects nor audio equalizer. Volume after restart is great, then i can pick up phone after few hours and it's really quiet on max volume. Did you debloat your phone ? Because i accidentally deleted stock music app, it could have something to do with it.
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
robenzo420 said:
I have exactly same problem as you. No Histen sound effects nor audio equalizer. Volume after restart is great, then i can pick up phone after few hours and it's really quiet on max volume. Did you debloat your phone ? Because i accidentally deleted stock music app, it could have something to do with it.
Click to expand...
Click to collapse
I cant say for certain, but don't think i deleted that app.
Be interesting to know exactly how we both managed to do this to these devices. Sadly, i do not think there is the developer support available to answer it.
mightyjcb said:
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
Click to expand...
Click to collapse
No OTA for me, probably because i'm unlocked and rooted. Check my post history i found temporary fix for me, no low volume anymore.
mightyjcb said:
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
Click to expand...
Click to collapse
No, i'm still running older build. What is 360 kernel fix? I flashed something kernel related for enabling buttons on my phone.
robenzo420 said:
No OTA for me, probably because i'm unlocked and rooted. Check my post history i found temporary fix for me, no low volume anymore.
Click to expand...
Click to collapse
I believe you are correct. Rooting will mean that you are unable to update the device OTA. I am not so sure about OTA updates with the device unlocked.
robenzo420 said:
No, i'm still running older build. What is 360 kernel fix? I flashed something kernel related for enabling buttons on my phone.
Click to expand...
Click to collapse
Then that is most likely the kernel image i referred to. It has a fix for buttons among other things. (If you want, you can flash the stock kernel image over the custom one you have now, and it will leave buttons active etc.)
As i say, this issue is now resolved.
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.
These update packages should work on global variant Nokia X6.
Usage:
Confirm your current version by dialing *#*#227#*#* before update.
Then download the package and rename to the specific filename I gave, place it to root directory of internal storage and dial *#*#874#*#* to update.
After the update procedure completed, update package will be deleted from your phone automatically.
Global Release:
Note: From DRG-250A build, it blocked current bootloader unlock method, be careful.
Click to expand...
Click to collapse
June 2018 to August 2018 (DRG-250A-0-00WW-B05-229D-0-00WW-B01-update.zip)
August 2018 to September 2018 (DRG-250B-0-00WW-B01-250A-0-00WW-B05-update.zip)
Android Pie November 2018 (DRG-330B-0-00WW-B01-update.zip)
Thanks for your work supporting our device!
Do you have boot image of 250A version?
izkyline said:
Do you have boot image of 250A version?
Click to expand...
Click to collapse
Yes that would be handy. I read that payload_dumper doesn't work on incremental updates. I'm still looking for ways to extract a boot.img
Hi bro I need to unlock the blltloader for my nonia 6.1 ta-1050 . If you could help me plzz
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
My nokia
DRG-250A-boot_patched.img patched with Magisk v17.1:
https://www111.zippyshare.com/v/12gKJE7u/file.html
how to update the path for x6
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
google play pretent CN OTA?
Boss,
After discuss with many other user, we think it is because I am using China version rom, but installed Google play, which pretent OTA update.
Do you think so? Could you give us a solution?
I bought the phone from ebay. I just need OTA.
yshgcs said:
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
Click to expand...
Click to collapse
Will this work on Android one varient i.e , Nokia 6.1 plus?
Do you have boot image of 250B version? I need root my device, boot September, help me
thaidaidong25 said:
Do you have boot image of 250B version? I need root my device, boot September, help me
Click to expand...
Click to collapse
Use the boot image from Nokia 7 Plus. They work. Just don't flash it, only boot it.
thanks for sharing, i just installed the pie version on my nokia 6.1 plus
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
xoxoJoelxoxo said:
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
Click to expand...
Click to collapse
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
DJBhardwaj said:
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
Click to expand...
Click to collapse
Well, that didn't do the trick, but I just simply clicked 'disable' after wiping the data and it gave me a message of "uninstalling app and installing factory camera app" which worked beautifully.
Now everything's working fine.
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
snowdance said:
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
Click to expand...
Click to collapse
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
hoatongoc said:
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
Click to expand...
Click to collapse
already installed it last night, and it work's !
thank's for the reply
Will I still receive OTA updates by HMD for my device when I check for it?
xoxoJoelxoxo said:
Will I still receive OTA updates by HMD for my device when I check for it?
Click to expand...
Click to collapse
you will, i already ask it with the support center from my country in indonesia
Hi,
I have Honor 9 Build 9.1.0.210(C432).
I have a security patch update message (small update of about 26MB), after downloading the phone resets but boots to system and not recovery, so the update doesn't install.
I don't have a custom recovery.
What can I do?
Thank you
No one has any solution?
I had the same problem if it was unrooted, the patch would take. If rooted I'd keep getting noticed to update, but they never worked.
I just ended up spoofing the version and being done with it. If you figure out a solution, please let me know
shiboby said:
I had the same problem if it was unrooted, the patch would take. If rooted I'd keep getting noticed to update, but they never worked.
I just ended up spoofing the version and being done with it. If you figure out a solution, please let me know
Click to expand...
Click to collapse
What do you mean by "spoofing the version"?
I didn't find any solution yet
I used a terminal emulator to change what the phone thought the software version was.
shiboby said:
I used a terminal emulator to change what the phone thought the software version was.
Click to expand...
Click to collapse
Do you have a guide how to do it?
How changing the version help in that regard?
Clonimus said:
Do you have a guide how to do it?
How changing the version help in that regard?
Click to expand...
Click to collapse
If you change the version number to one beyond what the server has, then it won't think it needs to download one.
For the version I was using, what I did was:
1. set ro.comp.hl.product_base_version to "STF-LGRP2-OVS 9.1.0.215"
2. Create new custom prop: "ro.comp.hl.product_cust_version" and set to "STF-L09-CUST 10.0.0.5(C432)"
3. Create new custom prop: "ro.comp.hl.product_preload_version" and set "STF-L09-PRELOAD 10.0.0.5(C432R1)"
shiboby said:
If you change the version number to one beyond what the server has, then it won't think it needs to download one.
For the version I was using, what I did was:
1. set ro.comp.hl.product_base_version to "STF-LGRP2-OVS 9.1.0.215"
2. Create new custom prop: "ro.comp.hl.product_cust_version" and set to "STF-L09-CUST 10.0.0.5(C432)"
3. Create new custom prop: "ro.comp.hl.product_preload_version" and set "STF-L09-PRELOAD 10.0.0.5(C432R1)"
Click to expand...
Click to collapse
So basically you prevented the phone from prompting to update?
I thought you found a way to force the update.
Clonimus said:
So basically you prevented the phone from prompting to update?
I thought you found a way to force the update.
Click to expand...
Click to collapse
correct. It seems that if the phone is rooted, it will not update. The choice as I saw it was live with the persistent prompts to update or stop it prompting the updates.
"SOLVED"
I uploaded/copied the 3gb into my local download folder > update using the "choose update package" method, and failed.
The message said "Can't verify update, Can't flash this stable ROM". Any idea why?
Im currently on 13.0.10.0 (Android 11)
Update : Updated to V13.0.7.0.SKEMIXM as of 21 December 2022. Technically "fixed"
Have you tried redownloading it? Sometimes a wayward bit on a big download like this can mess up the checksum and prevent verification.
Jedi3815 said:
Im currently on 13.0.10.0 (Android 11)
Click to expand...
Click to collapse
Hang on, are you're trying to downgrade? I don't know how well that is supported via the built-in update functionality. Or is this a typo - I can't find 13.0.10.0 for this device?
aricooperdavis said:
Have you tried redownloading it? Sometimes a wayward bit on a big download like this can mess up the checksum and prevent verification.
Click to expand...
Click to collapse
Yes, about 5 times from 5 different sources. All failed
aricooperdavis said:
Hang on, are you're trying to downgrade? I don't know how well that is supported via the built-in update functionality. Is this a typo, I can't find 13.0.10.0 for this device.
Click to expand...
Click to collapse
Nope. Currently 13.0.10 android 11, wanting to upgrade to 13.0.5 android 12.
Ah I see. I have no idea how the OTA update system works with different android versions, sorry
I
aricooperdavis said:
Hang on, are you're trying to downgrade? I don't know how well that is supported via the built-in update functionality. Or is this a typo - I can't find 13.0.10.0 for this device?
Click to expand...
Click to collapse
The device was on v 13.0.10 for the latest Android 11 build. V 13.0.5 was the new MIUI build for Android 12, and for me brought a plethora of bugs. Immediately after the update, I received another notification for an update available, v13.0.6, which sort of fixed a couple of these bugs (such as a broken fingerprint sensor, akin to what Pixels experienced late last year) and I performed a factory reset afterwards. Most of them are gone now, but it's a complete mess this update system/ model.
Jedi3815 said:
Nope. Currently 13.0.10 android 11, wanting to upgrade to 13.0.5 android 12.
Click to expand...
Click to collapse
Try pausing the update from your system update settings pane, go into download, delete the package and restart download after a reboot.
Frank_Kinuthia said:
Try pausing the update from your system update settings pane, go into download, delete the package and restart download after a reboot.
Click to expand...
Click to collapse
I did that before, still fail. Now they have released the 13.0.6 Android 12 version, successful. so yeay.