yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
There are two different full ota files

Going to try now
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
Works finally

First post updated
[Huawei Mate 9 Guides, News, & Discussion] qrtnielsen:
Hi,

sorry, I chose the first one from top of the list.

Hope you get it:)

Kurt
[Huawei Mate 9 Guides, News, & Discussion] Texan1:
Aaarrgghhh...had my hopes up, just downloaded the correct, full OTA version (all 2.6GB worth) as suggested... and once again it has failed authorisation for me :mad::mad::mad:
[Huawei Mate 9 Guides, News, & Discussion] qrtnielsen:
Hi Tex!

Two questions:

1. are you on the same code C636?

2. did you chose the FF option of sending your IMEI? I suppose that you updated FF to the latest ver.

Good luck

Kurt
[Huawei Mate 9 Guides, News, & Discussion] Texan1:
Hi Kurt,

Yes, on MHA-L29C636B172.

Yes, sent my IMEI and got the message saying it is approved, also running latest version of FF.

This has been so frustrating!
[Huawei Mate 9 Guides, News, & Discussion] qrtnielsen:
Hi Tex!

You are absolutely right about the "special peculiary" update policy - or rather very irritating policy - from Huawei's side. They are selling the mate at at rather high price, telling lies about which type of ram they include, at start mending the phone at a very slow and unpredictable way. In my case the touchscreen have not been working properly before this B181 update.

I sincerely hope you get your proper update soon. So you have to keep trying :D

Kurt
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
There are two full ota files

Are you choosing the one with the "85027" at the end? That is the only one that passes authentication
[Huawei Mate 9 Guides, News, & Discussion] Texan1:
Yes, definitely have been choosing the 85027 file (the other full OTA which is 85049 is showing as not approved when I check it anyway), have tried twice now and wasted 5GB+ data doing so!
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
Hmm... Not sure what too suggest...I updated two mate 9's from b172 to b181 this evening without issues
[Huawei Mate 9 Guides, News, & Discussion] gurita:
Works with b181...:good:
[Huawei Mate 9 Guides, News, & Discussion] onslaught86:
You are not alone, no joy here in NZ either.

Given it's the same hardware with the same software build, I'm wondering if they're checking against the MNC/MCC of the installed SIM card(s) when authenticating. May be worth trying without a SIM installed.

A previous update (156?) passed auth when a new Huawei ID was created for a region that had the update approved, so there may be several components at work here. Keen to find out the common elements between devices that have and have not passed the auth check for the update to make this easier in future.

EDIT: Nope, removing the SIM (and switching regions) achieved nothing, still fails auth. Must be server-side.
[Huawei Mate 9 Guides, News, & Discussion] lupin87:
Guys, I have problem with flashing firmware via Firmware Finder.

I'm now in C635B170, I tried to flash C636B181 but got authentication failed, then I flashed C567B190.

It can be flashed succesfully but in Build number still C635B170.

Now I dont have System Update option in Settings

What should I do now? Any help is appriciated !

Thank you,
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
I went from b158 to b172 to b181

Both far away from spceas

I'm in Trinidad (Caribbean) on Digicel
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
Not sure

But there is a system update on the app drawer as well

If all else fails.... They backup and try a factory reset is all I can think of

HOWEVER the a c636 can only flash c636 updates

Same with c567 and c567 updates

There aren't interchangable and should fail the authentication process..... Would cause problems even if you got through

Flashing to a different region is possible; but not with firmware finder. There is another popular topic on here about that process
[Huawei Mate 9 Guides, News, & Discussion] Walton_Melb:
When I select the full 85027 update and select Download there are 3 options with check boxes.

Can someone explain what these are for?

There is

- update.zip

- public/update_data_full_public.zip

- MHA-L29_hw_spcseas/update_full_MHA-L29_hw_spcseas.zip

Thanks
[Huawei Mate 9 Guides, News, & Discussion] novastar1:
Don't download from there

Press register for update

Follow the instructions there... Really just to temporarily change your dns ( can be done in your phones modify WiFi settings)

Then when you check for update the usual way in the stock system update... You'll see the update you registered
[Huawei Mate 9 Guides, News, & Discussion] Walton_Melb:
Thank you - downloading now

EDIT - hmm now it wants to continually download a patch of 717MB - 7 times so far.

not a good outcomes as it seems to be in a download loop
[Huawei Mate 9 Guides, News, & Discussion] onslaught86:
A step was left out of the instructions. After the update has popped up in the system update UI, pause it and remove the proxy from your WiFi settings. Then you won't be stuck in a download loop.
[Huawei Mate 9 Guides, News, & Discussion] Walton_Melb:
Thanks.

I ended up doing that but the install then fails.

I'll try again tomorrow.
[Huawei Mate 9 Guides, News, & Discussion] adarwis:
Failed on authentication :(
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
Am fed up with the Firmware Finder app. I check the status of the firmware I want to download and it says approved. I download it and then authorisation failed. Why say it's approved if it's not? Have checked many times and always a red herring. I would rather it did not lie so I wouldn't waste multiple times downloading over 2 gigs of data. Sort it out Dev!

---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------

I did everything you did. The app said B181 was approved and yet authorisation failed when I tried to install. Argh this is so frustrating!!
[Huawei Mate 9 Guides, News, & Discussion] gurita:
Try this for me is work.
[Huawei Mate 9 Guides, News, & Discussion] Swan Princess:
Just use the HWOTA method to upgrade your firmware and stop complaining about FF's dev, eh?
[Huawei Mate 9 Guides, News, & Discussion] 012345678:
you should try my tutorial
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
Why can't I complain? The app has an option that does not work. Have you not read others too have checked and it said it was approved and yet authorisation failed at the end? It's not just me. We waste time and data each time we check. False hopes. I would rather the Dev just remove that option completely if it's not working well. If nobody complains then the problem is not seen as an issue and no action is taken.

I have problems with my current ROM B172 and all I want to do is upgrade to the latest official B181 ROM to see if it fixes them. I want to upgrade without unlocking bootloader or rooting or installing TWRP. I don't want to screw up my Android Pay by those methods.
[Huawei Mate 9 Guides, News, & Discussion] 012345678:
give it a try with my solution

https://xdaforums.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
Ok but do I need to unlock bootloader or root?
[Huawei Mate 9 Guides, News, & Discussion] 012345678:
yes and no, its your choice. If you want to rebrand to another Build range 567/432 ect you need to unlock and rebrand, for just to rebrand another firmware build in your firmware you can look for your firmware you wish for and can set it on active in Firmware Finder.
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
I just want to update and stay on C636 branch.
[Huawei Mate 9 Guides, News, & Discussion] 012345678:
then just go in e recovery and try it, Use my Tutorial for it
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
Alas I can't change the DNS settings of my router. My provider won't allow it.
[Huawei Mate 9 Guides, News, & Discussion] 012345678:
maybe you can try a dns Tool in playstore, you can use the firmware Finder App too, to create the proxy for it
[Huawei Mate 9 Guides, News, & Discussion] Texan1:
Well blow me down but B181 has suddenly decided to work for me! I used the DNS method (which I had tried before), it downloaded the full 2.6GB version but when it got to the authentication stage kept saying the server was unavailable and to try again later.

That had also happened before and then when I moved away from my wifi and switched to 4G I'd get the authentication failed message. This morning it decided to work and I'm now on B181! :)
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
So after getting an authentication failed message it always say it will delete the download. So if you are saying this morning it decided to work, does that mean you re downloaded it?
[Huawei Mate 9 Guides, News, & Discussion] tboy2000:
Well I did exactly what you did. Said server was busy and try again later. So I clicked ok. Turned off WiFi and all of a sudden it rebooted and installed B181. I can't believe it after all this time. A big thank you as if it wasn't for your post I wouldn't have tried again.
[Huawei Mate 9 Guides, News, & Discussion] onslaught86:
Brilliant, ta.

I note that Firmware Finder now reports that the B181 update is auth'd for install both with and without IMEI - previously it said unauth'd when submitted without.

The smaller OTA works as well as the larger full update.
[Huawei Mate 9 Guides, News, & Discussion] zayidhs:
Update worked at the first go. UI seems snappier and animation transition is smoother.

Hope there'll be improvements in battery also :)
[Galaxy S6 Q&A, Help & Troubleshooting] S10e:
I've been having a serious as well as a very strange problem with the sound output of my device and there's an app causing it. All of this is happening on Nougat (even on different CSC firmwares) and never happened on Marshmallow.

Facebook Messenger is the cause of the problem. After some time using messenger, ALL notifications & ringtones (messenger, normal messages, call ringtones; everything, even alarms) suddenly doesn't sound. Even vibration doesn't work, but taps do sound as I can hear them. For example, if the bug is present and I turn on an alarm, or someone calls me, I will not notice as there is no sound and no vibration, while the sound is full up and on SOUND mode.

The fix is force closing the messenger app from the recent screen. Everything will get back to normal then. Uninstalling the Messenger app will remove the bug for good and I can use the Messenger Lite app as it doesn't have this problem, but it is very limited and I use the Messenger app very regularly and surely can't uninstall it.

I have now noticed that while the bug is present and I try to play music, I get the error 'Failed to play track' in the stock Music app. Once again, the fix is the one mentioned above.

Anyone encountered this issue? I've sent Facebook Messenger an email with my problem, but with no response. Help would very much be appreciated.

Phone: Samsung Galaxy S6 SM-G920F

Version: 7.0 Nougat

CSC: latest BTU (but also happened on the DBT version)

Regards,
[LeEco Le Max 2 Questions & Answers] yurtesen:
Hello,

I have TWRP 3.1.1-0-x2 installed and I am able to boot into it from power menu by selecting recovery. However when I try to install LineageOS OTA updates it says "Unable to reboot into recovery"

I have searched around a lot and all I could find was that this was a problem in LeEco LePro3 and somebody came up with a fix..

Does anybody know how to fix this issue on LeEco Le Max 2 - X2 ?

Thanks
[Google Pixel Guides, News, & Discussion] phonepersonality:
Since the May Security Update, there have been changes.

I won't get into that here, as there are already a number of threads where the new AVB process and what it means for updates and root is discussed at length on this forum.

For example - https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606/page16

I'm just going to outline my process for installing the new security updates via full image (Not OTA) and then rooting the phone via TWRP.

A few things to bear in mind first.

You will need to have the following:

0. Know how to use ADB/Fastboot and have them installed. If not, you should please do some research first.

1. Full Image for Pixel (https://developers.google.com/android/ota)

2. TWRP boot image and zip files (https://dl.twrp.me/sailfish/)

3. Latest SuperSU by Chainfire (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip)

4. VerifiedBootSigner by Chainfire (https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606)

Also...I don't make use of the vendor provided flashing scripts, I simply use the script commands and eliminate the '-w' flag manually.

*The SuperSu, TWRP and VerifiedBootSigner zips need to be saved to your phone*

From the bootloader ->

fastboot flash bootloader bootloader-sailfish-8996-012001-1704121145.img

fastboot reboot-bootloader

fastboot flash radio radio-sailfish-8996-012901-1702171013.img

fastboot reboot-bootloader

fastboot update image-sailfish-njh47b.zip

***The phone will automatically reboot at this phase and you will need to reboot back into the bootloader to continue either by manual means or by using "adb reboot-bootoader"

fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img

from TWRP (using files saved on phone) ->

TWRP install twrp-pixel-installer-sailfish-3.1.0-0RC2.zip

reboot TWRP

TWRP install SR3-SuperSU-v2.79-SR3-20170114223742.zip

TWRP install VerifiedBootSigner-v8.zip

reboot system

Edit - You should also update your SuperSU binary to 2.82 from within the app once you're booted into Android.

You're Done!

DISCLAIMER

I didn't create any of these files or take credit for them in anyway. This is simply an instructional that I hope will help many of you.

It requires some proficiency in using fastboot and TWRP.

If you don't know what you're doing and mess up your device, I take no responsibility for your actions or the results.
[Google Pixel Guides, News, & Discussion] churchmice:
gonna give it a try, thanks dude.
[Google Pixel Guides, News, & Discussion] churchmice:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
[Google Pixel Guides, News, & Discussion] phonepersonality:
You're right.

I should update the instructions about that.

The reboot isn't really an issue, but it does add an additional step and some inconvenience.
[Google Pixel Guides, News, & Discussion] gubacsek:
fastboot has an option to skip reboot:

--skip-reboot

so the command would be something like: fastboot --skip-reboot update image-sailfish-njh47b.zip
[Google Pixel Guides, News, & Discussion] TENN3R:
Can't we just use ota? Like:

- sideload ota

- let reboot

- reboot bootloader

- boot twrp rc1

- flash twrp rc1

- flash bootloader signer

- reboot recovery

- flash root

- optional kernel

- flash bootloader signer

- reboot

I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
[Google Pixel Guides, News, & Discussion] phonepersonality:
If you'd like.

I don't like to use the OTA files, personally.
[Google Pixel Guides, News, & Discussion] mikeprius:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
[Google Pixel Guides, News, & Discussion] Tulsadiver:
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
[Google Pixel Guides, News, & Discussion] mikeprius:
I did manual fastboot commands earlier, not the autoscript, automatically wiped my data.

---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------

Not sure what happened. Just pretty much treated like a dirty flash and fastboot flash the image. It must have detected the prior and wiped it. Had the thing rooted which is the only thing I can think of, it was not untouched stock.
[Google Pixel Guides, News, & Discussion] TENN3R:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.

Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
[Google Pixel Guides, News, & Discussion] joeybobo:
Did anyone else have to install the TWRP 3.1 zip via USB-OTG? After flashing the full factory image for June 2017, rebooting to system, rebooting to bootloader then running fastboot boot twrp3.0.2-RC1.img, I wasn't prompted to enter my password so my user data remained encrypted and I couldn't install the TWRP 3.1 zip from the internal SD card, had to load it on a usb dongle and mount USB-OTG storage.
[Google Pixel Guides, News, & Discussion] mikeprius:
I've tried to take out the -w erase flag. I've also tried to reflash the stock boot in the past when reloading a new kernel. Not sure if it is triggering some kind of system default but it just auto wipes. It's not the end of the world, I have everything backed up, I just have to restore everything. Just have not had any luck
[Google Pixel Guides, News, & Discussion] TENN3R:
Guys I can confirm also sideload ota method works flawlessly, 7.1.2 june rooted
[Google Pixel Guides, News, & Discussion] Coronado is dead:
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
[Google Pixel Guides, News, & Discussion] alluringreality:
A phone setup according to this thread is not expected to pass the Safetynet check. I've been updating with SuperSU using FlashFire, and my phone just shows Netflix VR in the Play Store. The Magisk discussions are primarily the threads that have been active recently for having root and passing Safetynet.

Pixel discussion:

https://xdaforums.com/pixel/how-to/magisk-pixel-t3573845

Pixel XL discussion:

https://xdaforums.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
[Google Pixel Guides, News, & Discussion] Flitskikker:
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.

My current steps are:

1) adb reboot recovery

2) adb sideload ota-update.zip

3 Reboot and check if everything is okay (root and TWRP are lost, data are not)

4) adb reboot bootloader

5) fastboot boot TWRP.img

6) Flash TWRP and SuperSU

7) Flash boot signer

8) Reboot
[Google Pixel Guides, News, & Discussion] TENN3R:
I use the same method I don't think there are any others
[Google Pixel Guides, News, & Discussion] Flitskikker:
Thanks for confirming. :)
[Google Pixel Guides, News, & Discussion] smithilberry:
Does this VerifiedBootSigner-v8.zip apply to the August security patch as well?
[Honor 4x Questions & Answers] Zizo17:
Hello to all of you , mates

I think all of you have seen this amount of custom roms realsed for p8lite , it's really a huge effort of Open Kirin Team

But , it wont work with our 4x because of diffrent wifi card ( boot.img ) on general , other missing fixes too

I wish this thread will help us to make any of it works with 4x , sharing informations , questions and news will be good

Regards
[Honor 4x Questions & Answers] adriansticoid:
You can reach out to the OpenKirin team for this request. :)

---------- Post added at 03:53 AM ---------- Previous post was at 03:49 AM ----------

Did you already read this? https://xdaforums.com/honor-4x/how-to/xepeleato-lineageos-4x-kirin-620-t3542419/page1
[Honor 4x Questions & Answers] Zizo17:
Thanks my friend

I will try to contact with them .. btw I have flashed the build you mentioned by xepeato , it boots with bugs of course
[Honor 4x Questions & Answers] adriansticoid:
Yes because it is still in development. Give it more time and it will be stable for sure. ;)
[Honor 4x Questions & Answers] Zizo17:
I meant that xepeato was able to make an edited boot.img for 4x before , I know that was buggy but I was so excited to test it
[Honor 4x Questions & Answers] gopinaidu77:
The team is doing collosal efforts right now. Kindly wait and I'm sure Kirin 620 users will get what they want. :)
[Honor 4x Questions & Answers] jerryhou85:
I believe now it is overwhelming for OpenKirin team with too many tasks to tackle. Time can fix most issues. Just wait for it. :)
[Honor 4x Questions & Answers] adriansticoid:
Yes. Imagine the number of Honor devices they maintain.
[Honor 4x Questions & Answers] gopinaidu77:
Yes they are maintaining 4-5 days
[Honor 4x Questions & Answers] adriansticoid:
Amazing perseverance they got. :D
[Honor 4x Questions & Answers] gopinaidu77:
They had all mentioned devices is it?
[Honor 4x Questions & Answers] adriansticoid:
No. They even have P8 and P9 if I'm not mistaken
[Honor 4x Questions & Answers] gopinaidu77:
So they are working with all kirin models unified .
[Samsung Gear S2] almorabitms:
Salam. I have gear s2 3g connected to my galaxy s7 duos via Bluetooth. How can I choose between the two sim cards when making call directly from the gear s2 3g without referring to my phone.? Actually I have to launch call from my gear and choose the card sim on my phone..

Forgive my English ??
[ZTE Axon 7 Questions & Answers] ChiDi9901:
I prefer using the touch feedback sound when tapping on my screen. Now, the only thing that drives me a bit crazy is that whenever I touch the back button or the recent app button, I hear some kind of double popping sound instead of one clear pop. Funnily, it only happens on these two buttons, no where else. Tapping something on the screen is no problem. Even tapping the home button sounds normal.

By the way, I'm using the European model with the latest Nougat firmware.

I want to know if this problem is just on my device or if other people also hear this? Is there a quick fix maybe? Did it happen before in older firmwares? (I recently got this phone and I updated it straight to the latest version...)
[ZTE Axon 7 Questions & Answers] Choose an username...:
I always use my device on vibrator and found out that the vibrator will vibrate twice sometimes when touching the buttons. What the hecc

This would mean that the actual problem is the detection of touches. I'd love to be a dev just to see how they implemented things like that one

ZTE made a lot of these hard coded stuff here and there... notif led, vibrator strength...
[ZTE Axon 7 Questions & Answers] ChiDi9901:
So I guess it's not an isolated problem ?
[ZTE Axon 7 Questions & Answers] MrMD69:
Nah you are not "solo" with that trouble. I've also found that this bug occours sometimes. A2017G B04 here.
[JAMin, XDA Neo, S200 ROM Development] k0ster:
I glad to give you the NEW version of Animated Startup for Prophet!

As you know for nowadays we use files from Touch.

Such as:

HTCUtil.dll

HTClib.dll

But now i present you the animation based on HTCInit.dll :D

I think that this is more good for our device.

Attached cab consist of:

1. HTCinit.dll

2. StartupAnimation.dll

3. Animation.dll

4. Playsnd.dll - i dont check the StartUp sound

5. Animated.gif - from Touch

If you want to use yours favorite animation, just rename it to animated.gif and copy with replace to yours device in windows folder

Dimensions of Animated.gif must be 240*320 in portrait orientation.
[JAMin, XDA Neo, S200 ROM Development] ninjaz:
Thanks, works great!
[JAMin, XDA Neo, S200 ROM Development] anubis.genix:
soo, how does it look like? could you provide some pictures?
[JAMin, XDA Neo, S200 ROM Development] ninjaz:
This is animation.
[JAMin, XDA Neo, S200 ROM Development] farzin_silver:
coooool

is any way come back to default after install ?
[JAMin, XDA Neo, S200 ROM Development] varanusvincent:
just uninstall it.. and you will have your old one.

:)
[JAMin, XDA Neo, S200 ROM Development] anubis.genix:
looks great!

nice work