Database Develop

Double Tap 2 Wake: please test

Hi,
Has anybody tested the following DT2W on Mate8
It is a post to enable double tap to wake on Huawei devices and it is possible that it work on the P9.
I did the changes and have been able to get it working partially. I get the settings option to enable/disable dt2w but I can only double tap the lockscreen to sleep the device. Double tap 2 wake does not work for me.
If anybody could test on their P9 so that we can rule out if this works or not?
There was one mention of a P9 user that validated it working on the MM rom for the P9 (B182) but I am on B378 Nougat so perhaps this is the issue.

What are that changes?

laboratik said:
Hi,
Has anybody tested the following DT2W on Mate8
It is a post to enable double tap to wake on Huawei devices and it is possible that it work on the P9.
I did the changes and have been able to get it working partially. I get the settings option to enable/disable dt2w but I can only double tap the lockscreen to sleep the device. Double tap 2 wake does not work for me.
If anybody could test on their P9 so that we can rule out if this works or not?
There was one mention of a P9 user that validated it working on the MM rom for the P9 (B182) but I am on B378 Nougat so perhaps this is the issue.
Click to expand...
Click to collapse
P9 - B378 nougat
4 double-tap the alarm is activated.
4.1 [Component 1]
4.2 [Component 2]
4.3 installs the application called Root Browser. [Google Play link]. Total Commander can be installed!
Root Browser 4.4 launch, and look for the system / buildprop file and then deleted. (Do not then reboot the phone because bootloop will!)
4.5 We find the system / emulsifying / base / xml / hw_easywakeupmotion_config.xml and delete files.
Then start the Total Commander 4.6, then copied the downloaded files into place and set the jogosutságokat. (Without it does not work TELO).
Buildporp the system folder, the hw_easywakeupmotion_config.xml the system / emiu / base / xml folder.
Set 4.7 Eligibility. Both press and hold the Total Commander file and selecting the properties, and then change the permissions from the pictures.
Then restart your phone. If everything went well, the settings> Intelligent Assistant> Motion Control section, a new menu item, called Double-tap appears.
Note Buildprop also contains a variety of tuning.
https://logout.hu/blog/cunaja/index.html

laboratik said:
Hi,
Has anybody tested the following DT2W on Mate8
It is a post to enable double tap to wake on Huawei devices and it is possible that it work on the P9.
I did the changes and have been able to get it working partially. I get the settings option to enable/disable dt2w but I can only double tap the lockscreen to sleep the device. Double tap 2 wake does not work for me.
If anybody could test on their P9 so that we can rule out if this works or not?
There was one mention of a P9 user that validated it working on the MM rom for the P9 (B182) but I am on B378 Nougat so perhaps this is the issue.
Click to expand...
Click to collapse
I'm on B378 as well, and it's working fine for me.
The only issue that I'm having it's that sometimes the screen takes 2 or 3 seconds before turning on. But it rarely happens.

lfer123 said:
I'm on B378 as well, and it's working fine for me.
The only issue that I'm having it's that sometimes the screen takes 2 or 3 seconds before turning on. But it rarely happens.
Click to expand...
Click to collapse
Good to know it works.
Do you have the smart cover enabled?
Which version of the B378 did you install and how. Was it just the OTA or a full install? Via dload?
I am trying to figure out why it does not work on my end.
Thanks

laboratik said:
Good to know it works.
Do you have the smart cover enabled?
Which version of the B378 did you install and how. Was it just the OTA or a full install? Via dload?
I am trying to figure out why it does not work on my end.
Thanks
Click to expand...
Click to collapse
I installed B361 using this. Then, I received B378 via OTA.
Before that, I installed B361 using the B322 firmware, and I had several bugs, like missing NFC. But I didn't test DT2W then.
If you installed B360 or B361 using a beta firmware, I suggest you to do a rollback to Marshmallow, and then install B378 or B361 via OTA if avaliable.

Not working for me on L09 with B378.
But I would seriously kiss you guys if someone finds a way to make it work

Huawei ALE-L21C432B600 can't update to newer version

So after i've got this security update the local update option gone.Second sim card stooped functioned.
I downloaded the newest update the 608 and put it both as update.zip in DLOAD file and in root. After this I tried with volume + - and power button doing the updaten it reached 4% and after that said update failed. Also I tried dialing the hidden menu. Got in there and pushed the system upgrade from SDcard. The message says no update found. Somebody who knows the solution help!!!

theo888 said:
So after i've got this security update the local update option gone.Second sim card stooped functioned.
I downloaded the newest update the 608 and put it both as update.zip in DLOAD file and in root. After this I tried with volume + - and power button doing the updaten it reached 4% and after that said update failed. Also I tried dialing the hidden menu. Got in there and pushed the system upgrade from SDcard. The message says no update found. Somebody who knows the solution help!!!
Click to expand...
Click to collapse
You have 2 update zip, try the one that doesn't have inside the patch folder.
Must only have the update.app file
.

I only got to B601 - I don't think there is a newer version and for the custom ROMs, you don't need it.
Resurrection Remix (which has LineageOS features and more) Nougat is working perfectly for me on B601.
Back up your /system and just give it a shot with B600 - it'll probably work.

theo888 said:
So after i've got this security update the local update option gone.Second sim card stooped functioned.
I downloaded the newest update the 608 and put it both as update.zip in DLOAD file and in root. After this I tried with volume + - and power button doing the updaten it reached 4% and after that said update failed. Also I tried dialing the hidden menu. Got in there and pushed the system upgrade from SDcard. The message says no update found. Somebody who knows the solution help!!!
Click to expand...
Click to collapse
Seems to me like you have the stock recovery. Your problem looks like the perfect opportunity to start playing around with some custom roms.
If I were you I would
- unlock the bootloader
- install TWRP 3.1.1.
- install a custom rom
There are plenty of ROMs available, based on Android 5, 6, 7 or Stock . If you want to keep your overall P8 lite "look and feel" and use the dual sim feature best would be
(of course in my opinion, other may think different) the C432B608 DS P8 Lite EMUI Basic from this thread.
https://forum.xda-developers.com/p8lite/general/rom-c432b604-ds-p8-lite-emui-basic-t3652417
Be sure to save your data first, because this will lead to a complete wipe and facttory reset of your phone.
rgds
Lex

Stopping PIE Update

I want to prevent PIE from updating on my Note 9, Unlocked US Snapdragon
In reading various threads, some users have disabled:
1) Software update (green icon) (underlying com.sec.android.soagent)
2) Software update (blue icon) (underlying com.wssyncmldm)
3) Both of the above.
All that I want to do is prevent PIE from downloading and installing over Oreo.
Can someone clarify which of the above actually need to be disabled for this purpose?
Additional Background:
I enabled Developer Mode, turned off "Auto update system", but the Notification for PIE still came.
I "ignored" it by pressing the Home button (I did not press "later" or "download")
So it never actually started downloading/installing.
I did disable #2 above using ADB, the PIE Notification went away.
Just want to confirm whether/not #1 also needs to be disabled to prevent PIE from being served

JohnNadeau said:
I want to prevent PIE from updating on my Note 9, Unlocked US Snapdragon
In reading various threads, some users have disabled:
1) Software update (green icon) (underlying com.sec.android.soagent)
2) Software update (blue icon) (underlying com.wssyncmldm)
3) Both of the above.
All that I want to do is prevent PIE from downloading and installing over Oreo.
Can someone clarify which of the above actually need to be disabled for this purpose?
Additional Background:
I enabled Developer Mode, turned off "Auto update system", but the Notification for PIE still came.
I "ignored" it by pressing the Home button (I did not press "later" or "download")
So it never actually started downloading/installing.
I did disable #2 above using ADB, the PIE Notification went away.
Just want to confirm whether/not #1 also needs to be disabled to prevent PIE from being served
Click to expand...
Click to collapse
1. open the settings
2. Navigate to "Software Update" and select the entry
3. Now deactivate the "Automatic Updates" option
OR
Settings
Software update or settings
Lock screen & Security
Security Policy updates
set your updates to "manual"

bober10113 said:
1. open the settings
2. Navigate to "Software Update" and select the entry
3. Now deactivate the "Automatic Updates" option
OR
Settings
Software update or settings
Lock screen & Security
Security Policy updates
set your updates to "manual"
Click to expand...
Click to collapse
Thank you Bober.
Are you saying that either method above should prevent PIE from coming, or do both need to be done?
I had previously performed your first method (turned off "Automatic Updates" in "Settings, Software Updates"),
and as well turned off "Auto Update System" in "Settings, Developer Options".
But those steps did not stop PIE notifications.
I had not yet attempted turning off "Security Policy Updates" (in "Settings, Biometrics and Security, Other Security Settings, Security Policy Updates").
But based upon some other threads, it sounds like even that would just postpone the inevitable PIE notification, and ultimately, one or both of the Software Updates packages needed to be disabled (with a Package Disabler or ADB).
When I disabled the "Software update" (blue icon) (underlying com.wssyncmldm), the PIE notification immediately went away and has not come back since, even after several reboots. I've done this on four Note 9's... so far... all are behaving the same way.

JohnNadeau said:
Thank you Bober.
Are you saying that either method above should prevent PIE from coming, or do both need to be done?
I had previously performed your first method (turned off "Automatic Updates" in "Settings, Software Updates"),
and as well turned off "Auto Update System" in "Settings, Developer Options".
But those steps did not stop PIE notifications.
I had not yet attempted turning off "Security Policy Updates" (in "Settings, Biometrics and Security, Other Security Settings, Security Policy Updates").
But based upon some other threads, it sounds like even that would just postpone the inevitable PIE notification, and ultimately, one or both of the Software Updates packages needed to be disabled (with a Package Disabler or ADB).
When I disabled the "Software update" (blue icon) (underlying com.wssyncmldm), the PIE notification immediately went away and has not come back since, even after several reboots. I've done this on four Note 9's... so far... all are behaving the same way.
Click to expand...
Click to collapse
not 100% sure but i though it was worth trying. my phone is rooted so i never get OTA anyways. so i cannot tell for sure.

bober10113 said:
not 100% sure but i though it was worth trying. my phone is rooted so i never get OTA anyways. so i cannot tell for sure.
Click to expand...
Click to collapse
OK... Understood!
I do appreciate the ideas/input.
Thanks

Tried extensively to downgrade from pie 9.0 back to November Oreo 8.1.0 and failed missreably. I tried everything suggested everywhere that "claimed" would prevent the phone from updating back to pie after reverting back to Oreo. I am on SNAPDRAGON SM-N960W 6GB/128GB ESK (EASTLINK MOBILE CARRIER) HERE IN NOVA SCOTIA CANADA. I had to use Odin version 3.13.1 3B Modded version and downgrade was achieved successfully. I even disabled Samsung update packages one with green icon, and other one was blue. I turned off security updates, auto software updates, and in developer menu auto the automatic system updates. I did all this with Sim card out & wifi off. Here is the post of what I tried. I think it's a waste of time and a major letdown that we are being forced to upgrade a phone that some wanted to keep on Oreo, who's phone is it, ours or are we just being forced to have to spend money time & time again because they are forcing changes to a product that "" I "" paid for and was happy with the way it was. Anyway if your curious read details here....
https://forum.xda-developers.com/galaxy-note-9/help/downgrade-to-android-oreo-t3890956/post79031596

If you want to prevent the Update-Message and if you want to keep Knox 0x0, just flash annother "CP" via Odin.
"CP" is the Modem. You can flash 8.1 CP-Modemfiles when you use 9.0. No Problem ! And knox stays 0x0.
But you loos OTA.
If you want OTA back, flash the CP-File matching the ROM-Version.
A great thing if you flashed back to 8.1 via Odin. When you flash 8.1 via Odin, you can flash annother CP and you dont get OTA´s anymore.

TWiiTCH said:
Tried extensively to downgrade from pie 9.0 back to November Oreo 8.1.0 and failed missreably. I tried everything suggested everywhere that "claimed" would prevent the phone from updating back to pie after reverting back to Oreo. I am on SNAPDRAGON SM-N960W 6GB/128GB ESK (EASTLINK MOBILE CARRIER) HERE IN NOVA SCOTIA CANADA. I had to use Odin version 3.13.1 3B Modded version and downgrade was achieved successfully. I even disabled Samsung update packages one with green icon, and other one was blue. I turned off security updates, auto software updates, and in developer menu auto the automatic system updates. I did all this with Sim card out & wifi off. Here is the post of what I tried. I think it's a waste of time and a major letdown that we are being forced to upgrade a phone that some wanted to keep on Oreo, who's phone is it, ours or are we just being forced to have to spend money time & time again because they are forcing changes to a product that "" I "" paid for and was happy with the way it was. Anyway if your curious read details here....
https://forum.xda-developers.com/galaxy-note-9/help/downgrade-to-android-oreo-t3890956/post79031596
Click to expand...
Click to collapse
Here are the settings I was told to change before inserting Sim or connecting to WiFi... First I turned "off" auto update system in developer menu.
{
"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"
}
Then I was told to turn off security policy updates. Red circle is not the right setting, I hit it by mistake first go round, so i had to start all over. Green circle is the setting you need to tap on to get to where you turn of security policy updates.
Last option I disabled was in the software updates in settings menu. What i turned off was auto update, do not hit other setting I pointed to labeled "update now, kinda obvious as to why"
I even disabled the two Samsung update packages I found once I had downgraded to Oreo, one was blue icon & the other was green.
After I did all of these steps, I then inserted my sim & SD card which was empty. Went to bed with fresh setup as I did not use home CSC. Phone was 100% factory Oreo now. I then did a factory reset/cache wipe, went back in to Oreo and set it up and then did all the steps in the order shown here and changed all update settings before inserting my Sim & SD card for final step. Did I miss something or do something in the wrong order? I used modded odin also, regular is for exynos. I am on a SM-N960W Snapdragon Canadian ESK variant. Eastlink Wireless is ESK mobile provider. I'm lost & would like Oreo back! ?
If anyone is successful please share, my phone was fine until I awoke next day to find an upgrade to pie notification.

package disabler pro from app store. i have not had any notifications for the pie up date since.
I also debranded my note. so PDP works for me.
I had a US VZW branded device. VZW was forcing me to update I could not turn it off only decline up to 9 times.
I installed the US XAA unbranded firmware with the modded Odin.
got the pie update notification once, declined it turned off the auto updates and used PDP to block no more messages about pie
---------- Post added at 08:32 PM ---------- Previous post was at 08:18 PM ----------
TWiiTCH said:
Here are the settings I was told to change before inserting Sim or connecting to WiFi... First I turned "off" auto update system in developer menu.
Then I was told to turn off security policy updates. Red circle is not the right setting, I hit it by mistake first go round, so i had to start all over. Green circle is the setting you need to tap on to get to where you turn of security policy updates.
Last option I disabled was in the software updates in settings menu. What i turned off was auto update, do not hit other setting I pointed to labeled "update now, kinda obvious as to why"
I even disabled the two Samsung update packages I found once I had downgraded to Oreo, one was blue icon & the other was green.
After I did all of these steps, I then inserted my sim & SD card which was empty. Went to bed with fresh setup as I did not use home CSC. Phone was 100% factory Oreo now. I then did a factory reset/cache wipe, went back in to Oreo and set it up and then did all the steps in the order shown here and changed all update settings before inserting my Sim & SD card for final step. Did I miss something or do something in the wrong order? I used modded odin also, regular is for exynos. I am on a SM-N960W Snapdragon Canadian ESK variant. Eastlink Wireless is ESK mobile provider. I'm lost & would like Oreo back!
If anyone is successful please share, my phone was fine until I awoke next day to find an upgrade to pie notification.
Click to expand...
Click to collapse
Are you on the ESK branded firmware?
I was on VZW in the US and they force you to update. the easiest way for me was to flash the US XAA firmware. i think for canada it is XAC but if there are any carrier features you will probably loose the feature

Following up...
So far, no more Pie Update Notifications since my original post... on four Note 9's (specific model info below).
As others have mentioned above, I had tried toggling off the Software Auto Update settings in Developer Mode and various Settings menus, but the Pie Notification still came through.
I then used ADB to disable the "Software update" (blue icon) (underlying package is com.wssyncmldm).
Specific Model & OS Information:
Galaxy Note 9 US Unlocked Snapdragon
Model Number: SM-N960UZKAXAA
Model (Settings/About Phone): SM-N960U1
Android 8.1.0 AP/CP N960U1UEU1ARL1
Android 8.1.0 CSC N960U1OYM1ARL1

The license key was just about to expire for using AdHell3 to disable the update apps.
I went to the web site and DLed Package Disabler Pro and paid the $4 to activate it. It's been 24 hours since the switch and all is well.
I asked the Dev if it would try to update from the Play Store and he said it would not. I will receive an email if an update is available on their web site.

For delete notification about update to pie flash only older/different modem from default. I have last oreo so flashed older modem, then any update info just gone, even from settings. Of course i disabled all system update etc.
I don't use disablers from a long time because i do not trust them, especially a lot of permissions required for install.

Would someone be so kind to post the necessary ADB commands for disabling the important packages? Somehow I didn´t find them in all these downgrade threads on XDA

brooon said:
Would someone be so kind to post the necessary ADB commands for disabling the important packages? Somehow I didn´t find them in all these downgrade threads on XDA
Click to expand...
Click to collapse
Hi Brooon,
Some background...
As mentioned in the original post, there are two System Apps named "Software Update":
1) Software update (with a green icon) (underlying com.sec.android.soagent)
2) Software update (with a blue icon) (underlying com.wssyncmldm)
I only disabled com.wssyncmldm.
I did this on four Note 9 US Unlocked and none have since received the PIE update notice since March 22nd, 2019.
Here are the steps I used:
Installed ADB on Windows 10 Computer: Great Overview Here on ADB
Phone: Settings/DeveloperOptions/USB Debugging: ON
Connect USB Cable (watch for prompts)
Computer: Open a Command Prompt; Type in: c:\adb; adb devices; adb shell
Computer: pm disable-user --user 0 com.wssyncmldm
THAT disables the Second/BLUE "Software Update" (com.wssyncmldm)
Phone: Turn USB Debugging: OFF
Confirm it is Disabled:
Phone: Settings/Apps/Menu/ShowSystemApps,
Scroll Down to Software Updates
Blue should indicate "disabled"
Reboot; Confirm
Hope this helps.

Perfect, thx! You just earned a thumbUp
My problem is that I'm on U2 Bootloader. seems like my chances to rollBack just vanished...

brooon said:
Perfect, thx! You just earned a thumbUp
My problem is that I'm on U2 Bootloader. seems like my chances to rollBack just vanished...
Click to expand...
Click to collapse
nonsense!
n960FXXS2ARL3 is BL v2 and is Oreo:
https://updato.com/firmware-archive-select-model?record=7DAEF9AE04B011E99F15FA163EE8F90B
that one is the last BTU uk region on oreo.
there are more recent oreo versions too but different csc region than UK.
https://updato.com/firmware-archive...eo(Android+8.1.0)&order=date&dir=desc&exact=1
so if i were you I'd flash the full BTU firmware and let it boot once. no need to do the initial setup.
then id go back in dl mode and flash a N960FXXS2ASB1
firmware from the link abive.
in odin fill BL,AP and CP slots only so that u stay on an english csc. ull have lastest oreo patches and unbranded UK csc.

JohnNadeau said:
Following up...
So far, no more Pie Update Notifications since my original post... on four Note 9's (specific model info below).
As others have mentioned above, I had tried toggling off the Software Auto Update settings in Developer Mode and various Settings menus, but the Pie Notification still came through.
I then used ADB to disable the "Software update" (blue icon) (underlying package is com.wssyncmldm).
Specific Model & OS Information:
Galaxy Note 9 US Unlocked Snapdragon
Model Number: SM-N960UZKAXAA
Model (Settings/About Phone): SM-N960U1
Android 8.1.0 AP/CP N960U1UEU1ARL1
Android 8.1.0 CSC N960U1OYM1ARL1
Click to expand...
Click to collapse
Thanks for specifying the package name that needed to be disabled in order to stop OTA updates, package com.wssyncmldm. I didn't use package disabler, I used the ADB method like you did. I will post a link after this message to the article I found & you may have found or figured out through knowledge, for me the "found" way applied not the "knowledge" way it will show others how to do this. I found the article explained all the steps very straight forward.
Once you have your drivers installed and ADB on your computer and a command prompt open, The main thing it involves is a line of code that you type in, it looks like this....
pm uninstall -k --user 0 com.wssyncmldm
In front of "user" it is a double hyphen if you can only see a single one. On my phone it looks like a single hyphen only a touch longer than an actual one. Maybe it's the font I'm using but i thought I should mention that for those of you who may see it as a single one and say this guy is a moron, what he got me to type doesn't do Jack. Copy & paste it, it'll work
If you wish to re-enable your OTA update capabilities, just re-enable the same package that you disabled. To do this the code looks like the following all one line if you are copy & pasting, on phone it takes up 2 lines but it's all one code/command entry...
adb shell cmd package install-existing com.wssyncmldm
Happy Oreo Days Everyone, Phone Recording is working again now its like twisting that Oreo cookie and licking that sweet white filling out again MMmmm...
Site & steps here...
https://www.google.com/amp/s/www.xd...arrier-oem-bloatware-without-root-access/amp/
Also I use call recorder by skvalex. This is my main reason for downgrading & disabling Android Pie & future updates. Oreo works fine for now and I can re-enable updates later using this method if I want to upgrade. I don't know if other recorders are this way, but it looks like the Play Store or Android has forced the leftover call recorders to stop displaying incoming callers phone numbers or details, but I got my version directly from developers website and it does not have to deal with that bs because it is not the version that is in the Play Store. Just wanted to note that in case other call recorders surprise you with that message. Grab a working call recorder before they are removed from the store fully & for good. Wouldn't surprise me if that happens.
Here Is A Fast Samsung Firmware Download Server That Is Free Is Here...
https://updato.com/firmware-archive-select-model

this thread reminds me of windows xp and window 7.
no matter how long you want to live in the past, the rest of the internet will not wait for you.
meaning that security patches are there for a reason and although it might seem like planned obsolescence, major OS upgrades are a thing and arent going away.
we all know how privacy and security are important now a days. with countless examples of 0 day exploits being found, purposely forcing your device to not get updated is kind of like refusing to get vaccinated.
all i can say is good riddance.
when i get a recall in the mail for my car, i do it. i don't throw the notice away.

bober10113 said:
this thread reminds me of windows xp and window 7.
when i get a recall in the mail for my car, i do it. i don't throw the notice away.
Click to expand...
Click to collapse
Hardly an apple to apples comparison between an automotive recall and a phone OS update.
A phone with an old OS likely will not have its brakes fail and kill someone.

pizza_pablo said:
Hardly an apple to apples comparison between an automotive recall and a phone OS update.
A phone with an old OS likely will not have its brakes fail and kill someone.
Click to expand...
Click to collapse
the outcome severity might be different but it is still a negative outcome which usually negative things are baaaad.
secure things are gooood.
you could have just as well called me out on the vaccination analogy as well but i guess you gear heads are more sensitive when it come to cars. but my answer would have been just the same irregardless:
-its something that you don't want.

[SOLVED] Stuck on EMUI 8.1 after repairing the Device

//check post 13 and 14 for two solutions
Hi I'm in a strange situation after the phone has been repaired in a Huawei center: my phone comeback with another motherboard and with an Old EMUI 8.1.0.163 version based on Android 8 with July 2019 security patch and since a new IMEI all my Ota updates got lost.
I've waited 3 weeks and no Ota update comes, nothing also with official Hisuite. I checked on FF but the first strange thing: almost every build after mine are already approved 9.1.341 / 345 / 346 / 351 / 361. Every builds says "approved" except for: 9.1.0.311 . This is the one immediately after mine (I repeat 8.1.0.163) and it's the basically the only one "not approved".
So I thought "maybe if I force the .311 update I'll get all the other builds by OTA" and then tried with the DLOAD method (that I already used in past) with THIS FIRMWARE. Nothing to do, it start but get "Software instal failed. Incompatibility with current version" that is very strange because firmware is correct.
Since I didn't found any other rom newer flashable with Dload method I opted for Plan B and tried with the modded Hisuite app. Tried firstly with .311 build, it start the dowload and all, put in the phone but when boot in recovery it's lock at 5% and then after a while said "update error" and reboot without installing it.
For the last things I tried still with modded Hisuite but with different builds (345, 351 and 361) but for none of these the download start (both full package and ota). Hisuite found the updates but when I press download it says "no connection" and also it didn't show the changelog (like it did with the .311). Tried Also few build newer than mine that are EMUI 9.0 and not 9.1 thought maybe I've to pass before from the 9.0 to get the 9.1 but same (no changelog + connection error)
In the end what did you suggest except "wait for OTA"? Is there somewhere newer builds (like .345) flashable with Dload method? Or a "fix" for Hisuite builds with the "no connection error" and with no changelog?
Thanks in Advance
Screenshot of mine build and FF:
{
"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"
}

Did you change the dns in your computer? As the tutorial of hisuite nodded said? The host file
Albe95 said:
Hi I'm in a strange situation after the phone has been repaired in a Huawei center: my phone comeback with another motherboard and with an Old EMUI 8.1.0.163 version based on Android 8 with July 2019 security patch and since a new IMEI all my Ota updates got lost.
I've waited 3 weeks and no Ota update comes, nothing also with official Hisuite. I checked on FF but the first strange thing: almost every build after mine are already approved 9.1.341 / 345 / 346 / 351 / 361. Every builds says "approved" except for: 9.1.0.311 . This is the one immediately after mine (I repeat 8.1.0.163) and it's the basically the only one "not approved".
So I thought "maybe if I force the .311 update I'll get all the other builds by OTA" and then tried with the DLOAD method (that I already used in past) with THIS FIRMWARE. Nothing to do, it start but get "Software instal failed. Incompatibility with current version" that is very strange because firmware is correct.
Since I didn't found any other rom newer flashable with Dload method I opted for Plan B and tried with the modded Hisuite app. Tried firstly with .311 build, it start the dowload and all, put in the phone but when boot in recovery it's lock at 5% and then after a while said "update error" and reboot without installing it.
For the last things I tried still with modded Hisuite but with different builds (345, 351 and 361) but for none of these the download start (both full package and ota). Hisuite found the updates but when I press download it says "no connection" and also it didn't show the changelog (like it did with the .311). Tried Also few build newer than mine that are EMUI 9.0 and not 9.1 thought maybe I've to pass before from the 9.0 to get the 9.1 but same (no changelog + connection error)
In the end what did you suggest except "wait for OTA"? Is there somewhere newer builds (like .345) flashable with Dload method? Or a "fix" for Hisuite builds with the "no connection error" and with no changelog?
Thanks in Advance
Screenshot of mine build and FF:
Click to expand...
Click to collapse

Luis2k33-XDA said:
Did you change the dns in your computer? As the tutorial of hisuite nodded said? The host file
Click to expand...
Click to collapse
Yup otherwise mine modded Hi Suite would not have seen the build .311 and all the other builds I've tried. 99% sure about the hostfile need to re check better

I told you that cause when I register the ip of my connection, sometimes I use VPN services, and I got error about connection, but when I am in the right ip everything worked, also try some different 311 firmwares from FF, cause I had the experience that when I had one approved but its not for my device I got error in installing it, it stops always in 5%, but if I register another 311 firmware from the list, until I find what works, it can be installed, this is the point now with the firmwares from FF, I recommend to you to install Android 9 before 9.1
Albe95 said:
Yup otherwise mine modded Hi Suite would not have seen the build .311 and all the others I've tried.
Click to expand...
Click to collapse

You talk about phone or PC when you wrote about the VPN? Also another question: did you see the changelog when you choose a firmware?
I also thought about 9.0 but I don't think there are build based on 9.0. newer than mine. I'm scared of flashing build based on older security patch, highly risk of bootloop
Luis2k33-XDA said:
I told you that cause when I register the ip of my connection, sometimes I use VPN services, and I got error about connection, but when I am in the right ip everything worked, also try some different 311 firmwares from FF, cause I had the experience that when I had one approved but its not for my device I got error in installing it, it stops always in 5%, but if I register another 311 firmware from the list, until I find what works, it can be installed, this is the point now with the firmwares from FF, I recommend to you to install Android 9 before 9.1
Click to expand...
Click to collapse

I said About PC, what I do normally is with the FF app in the phone, I register the firmware I want to update, if it's available, after register in the phone app I go to the pc and connect the phone, and through hisuite modded appears the new update, it's very strange that your phone don't get new updates through Ota, maybe you can speak through hicare with the support about it, sometimes I went back to older firmwares for example if I didn't like the performance I went back and everything works normally

Luis2k33-XDA said:
Did you change the dns in your computer? As the tutorial of hisuite nodded said? The host file
Click to expand...
Click to collapse
I had same problem after mothert repair ,stuck on 8.1.0.163. Find any solution?

TheMax777 said:
I had same problem after mothert repair ,stuck on 8.1.0.163. Find any solution?
Click to expand...
Click to collapse
Had to try the procedure via phone hotspot. If it not work then will try to contact the Hicare assistance as said by Luis

Luis2k33-XDA said:
I said About PC, what I do normally is with the FF app in the phone, I register the firmware I want to update, if it's available, after register in the phone app I go to the pc and connect the phone, and through hisuite modded appears the new update, it's very strange that your phone don't get new updates through Ota, maybe you can speak through hicare with the support about it, sometimes I went back to older firmwares for example if I didn't like the performance I went back and everything works normally
Click to expand...
Click to collapse
Still have to try the hotspot procedure but I've talk with hicare support: nothing to do, since July 2019 they can't no more force Ota update the only way they said to me was to re-send in repairing center. And also they said if I'm stuck on July patch with Android 8 probably I'll never get new update, even if I wait months and months. What a mess...

You can install android 9 through hisuite modded, not the last update for example try 328 firmware, and after that search for new update through EMUI and download 345 firmware that is the last at the moment, and you will have an official Ota firmware, this is what I did the other day after tried 361 firmware and didn't like how works
Albe95 said:
Still have to try the hotspot procedure but I've talk with hicare support: nothing to do, since July 2019 they can't no more force Ota update the only way they said to me was to re-send in repairing center. And also they said if I'm stuck on July patch with Android 8 probably I'll never get new update, even if I wait months and months. What a mess...
Click to expand...
Click to collapse

Luis2k33-XDA said:
You can install android 9 through hisuite modded, not the last update for example try 328 firmware, and after that search for new update through EMUI and download 345 firmware that is the last at the moment, and you will have an official Ota firmware, this is what I did the other day after tried 361 firmware and didn't like how works
Click to expand...
Click to collapse
Ok I'll try thanks buddy. And for your modded Hisuite too you can't read the Changelog while you find for update? Sorry for loosing time just want to figure out if I've all setted correctly.

What I do is register it in the FF app, in the app you can see the change log, register the firmware with the ip of your internet and with hisuite modded everything is easy
https://forum.xda-developers.com/to...-finder-team-mt-t3469146/page144#post79988916
Albe95 said:
Ok I'll try thanks buddy. And for your modded Hisuite too you can't read the Changelog while you find for update? Sorry for loosing time just want to figure out if I've all setted correctly.
Click to expand...
Click to collapse

Albe95 said:
Hi I'm in a strange situation after the phone has been repaired in a Huawei center: my phone comeback with another motherboard and with an Old EMUI 8.1.0.163 version based on Android 8 with July 2019 security patch and since a new IMEI all my Ota updates got lost.
I've waited 3 weeks and no Ota update comes, nothing also with official Hisuite. I checked on FF but the first strange thing: almost every build after mine are already approved 9.1.341 / 345 / 346 / 351 / 361. Every builds says "approved" except for: 9.1.0.311 . This is the one immediately after mine (I repeat 8.1.0.163) and it's the basically the only one "not approved".
So I thought "maybe if I force the .311 update I'll get all the other builds by OTA" and then tried with the DLOAD method (that I already used in past) with THIS FIRMWARE. Nothing to do, it start but get "Software instal failed. Incompatibility with current version" that is very strange because firmware is correct.
Since I didn't found any other rom newer flashable with Dload method I opted for Plan B and tried with the modded Hisuite app. Tried firstly with .311 build, it start the dowload and all, put in the phone but when boot in recovery it's lock at 5% and then after a while said "update error" and reboot without installing it.
For the last things I tried still with modded Hisuite but with different builds (345, 351 and 361) but for none of these the download start (both full package and ota). Hisuite found the updates but when I press download it says "no connection" and also it didn't show the changelog (like it did with the .311). Tried Also few build newer than mine that are EMUI 9.0 and not 9.1 thought maybe I've to pass before from the 9.0 to get the 9.1 but same (no changelog + connection error)
In the end what did you suggest except "wait for OTA"? Is there somewhere newer builds (like .345) flashable with Dload method? Or a "fix" for Hisuite builds with the "no connection error" and with no changelog?
Thanks in Advance
Screenshot of mine build and FF:
Click to expand...
Click to collapse
I found the solution!!!
Install moded hisuite https://forum.xda-developers.com/to...-finder-team-mt-t3469146/page144#post79988916
From FF downgrade to 8.1.0.157 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2943/g1604/v199754/f1/full/update.zip
then Phone automatically updates from OTA 8.1.0.157 to 9.1 xxx

TheMax777 said:
I found the solution!!!
Install moded hisuite https://forum.xda-developers.com/to...-finder-team-mt-t3469146/page144#post79988916
From FF downgrade to 8.1.0.157 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2943/g1604/v199754/f1/full/update.zip
then Phone automatically updates from OTA 8.1.0.157 to 9.1 xxx
Click to expand...
Click to collapse
Found a solution too! Installed this firmware with dload method without issue and got 9.1 finally. Thanks to all

Downgrading with HiSuite (No Internet connection errror)

So i've tried all of the solutions to getting GMS and not had any luck so far unfortunantly.
I've gathered from various forum threads that i need to downgrade from build 11.0.0.168 to something like 10.0.0.xxx, before i can use Googlefier
I can't get HiSuite 10.0.0.510_OVE to work (Get an error on my phone about the app needing location permission, which i can't toggle on anywhere), so i am using HiSuite 11.0.0.510_OVE instead as instructed in a youtube video i found.
I get the software installed on PC+Phone and press "Update" and get no error messages, only a note that i am using the latest version.
Then i run the proxy as described in:
Googlefier - Install GMS on Huawei/Honor
Wecome to Googlefier, After a successful tool for LG G2 and LG G3 owners (AutoRec), but after a long pause, here is something new and I hope useful Googlefier is a simple tool, designed to help you install GMS on your Huawei/Honor device...
forum.xda-developers.com
The proxy runs fine seemingly,
HiSuiteProxy.PNG
drive.google.com
But when i press update now i get the "No internet connection. Please check your network Settings." Error.
I can't find many posts about this issue when i google, except this one:
[SOLUTION] hisuite no internet connection
maybe usefull to someone , guys im trying to rollback my mate 10 to previous emui version using hisuite in windown10 , but it keep pop up "no internet connection" message . trying to find solution everywhere but cant seems to find any solution ...
forum.xda-developers.com
I've tried everything suggested there with no luck. I don't have any anti-virus installed except Windows, and i disabled that entirely for this.
Any ideas on how to fix the "No internet connection" issue would be greatly appreciated.

i get a little bit different problem here, im trying to downgrade my P40 Pro ELS-LGRP4 10.1.0.166 to ELS-LGRP4 10.1.0.131 using hisuite + hisuite proxy combination, hisuite proxy run fine without problem, but when i try to check update from hisuite, it's always show "you're now using the latest official version" without "switch to another version" options.
I already try hisuite from different version (10.1.0.550, 10.0.0.510, 10.0.1.100), and try hisuite proxy from different version (1.8.8(latest), 1.8.6, and bender007 modification), but the result always same, it's always showing "you're now using the latest official version".
this is the steps I already taken to run hisuite proxy before running hisuite:
1. open hisuite proxy
2. fill the Packaget URL box with ELS-LGRP4 10.1.0.131 firmware url from firmware finder, fill the the version box with ELS-LGRP4 10.1.0.131 string from firmware finder; (in another test, i try to fill cust pkg, preload pkg and the version string, tick point version, tick CUST PKG box, tick Preload PKG)
3. patching httpcomponent in hisuite folder
4. run setup
5. open hisuite and connect the phone
but, whatever steps I try, hisuite always show that "you're now using the latest official version" message everytime I checking system update on hisuite
Note:
1. hisuite connection setting already ticked on proxy as the hisuite proxy recommended (127.0.0.1, port 7777)
2. already check host file, and it's normal, no hicloud whatsoever
3. no antivirus installed
4. already set windows firewall off
5. already try from different PC
maybe someone can help me too fixing this issue here?
Spoiler: hisuite + hisuite proxy problem
{
"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"
}

I managed to downgrade from EMUI 11 to EMUI 10 without using Proxy now aswell, so i'm down to 10.1.0.176 which is a step in the right direction. But now i run into the exact same issue as you describe "You're now using the latest official version"

After downgrading to 176 version i could actually use the memory card method which hadn't worked before. Got everything installed now, working perfectly (no notifications yet though).
Oh the joy!

I can't find any x.131 firmware on firmware finder and old links all are dead.
someone has a solution for this?

Nicobisgaard said:
After downgrading to 176 version i could actually use the memory card method which hadn't worked before. Got everything installed now, working perfectly (no notifications yet though).
Oh the joy!
Click to expand...
Click to collapse
Which firmware did you install? i tried with C636 from bender007 didn't work for me i got the exact same issue

Nicobisgaard said:
After downgrading to 176 version i could actually use the memory card method which hadn't worked before. Got everything installed now, working perfectly (no notifications yet though).
Oh the joy!
Click to expand...
Click to collapse
congrats dude, I want to try to dload downgrade my device too, but I'm afraid bricking my device if its wrong flashing firmware
can u tell me what firmware did you use? is was just base package firmware? or with cust and preload package?

I had the same issue, could downgrade to 176 using HiSuite then I used the OTG recovery with a firmware I was able to download. Version 121 (els-nx9-10.1.0.121(C432E8R5P2)) as my phone is a C432. Worked like a charm, an OTG adapter is only a couple of £/$ Mine cost £5 for two from Amazon.

kh4lzd said:
i get a little bit different problem here, im trying to downgrade my P40 Pro ELS-LGRP4 10.1.0.166 to ELS-LGRP4 10.1.0.131 using hisuite + hisuite proxy combination, hisuite proxy run fine without problem, but when i try to check update from hisuite, it's always show "you're now using the latest official version" without "switch to another version" options.
I already try hisuite from different version (10.1.0.550, 10.0.0.510, 10.0.1.100), and try hisuite proxy from different version (1.8.8(latest), 1.8.6, and bender007 modification), but the result always same, it's always showing "you're now using the latest official version".
this is the steps I already taken to run hisuite proxy before running hisuite:
1. open hisuite proxy
2. fill the Packaget URL box with ELS-LGRP4 10.1.0.131 firmware url from firmware finder, fill the the version box with ELS-LGRP4 10.1.0.131 string from firmware finder; (in another test, i try to fill cust pkg, preload pkg and the version string, tick point version, tick CUST PKG box, tick Preload PKG)
3. patching httpcomponent in hisuite folder
4. run setup
5. open hisuite and connect the phone
but, whatever steps I try, hisuite always show that "you're now using the latest official version" message everytime I checking system update on hisuite
Note:
1. hisuite connection setting already ticked on proxy as the hisuite proxy recommended (127.0.0.1, port 7777)
2. already check host file, and it's normal, no hicloud whatsoever
3. no antivirus installed
4. already set windows firewall off
5. already try from different PC
maybe someone can help me too fixing this issue here?
Spoiler: hisuite + hisuite proxy problem
View attachment 5236569View attachment 5236567
Click to expand...
Click to collapse
I have the same problem. Did you try sdcard method? My P40 pro is 10.1.0.176.

gnasher666 said:
I had the same issue, could downgrade to 176 using HiSuite then I used the OTG recovery with a firmware I was able to download. Version 121 (els-nx9-10.1.0.121(C432E8R5P2)) as my phone is a C432. Worked like a charm, an OTG adapter is only a couple of £/$ Mine cost £5 for two from Amazon.
Click to expand...
Click to collapse
I am 176 and c432. Will try the OTG method. Thank you

gnasher666 said:
I had the same issue, could downgrade to 176 using HiSuite then I used the OTG recovery with a firmware I was able to download. Version 121 (els-nx9-10.1.0.121(C432E8R5P2)) as my phone is a C432. Worked like a charm, an OTG adapter is only a couple of £/$ Mine cost £5 for two from Amazon.
Click to expand...
Click to collapse
dload firmware? please post a link.

starbase64 said:
dload firmware? please post a link.
Click to expand...
Click to collapse
Here is the link: https://drive.google.com/file/d/1Bjht-0HIBUSGj84yvyqaiLVzMvcy30Tt/view

Hey guys i was in same boat like others, stuck on 176 firmware, tried this thread and download c134 firmware today, it is for people stuck on C636 i had almost given up
[GUIDE] Fix Broken OTA Updates After Downgrade & Have EMUI 11 With GMS (C636)

Eh maybe i can shoot in a tip here.
I just came from 11.0.0.168. I did this
awais_666 said:
Hey guys i was in same boat like others, stuck on 176 firmware, tried this thread and download c134 firmware today, it is for people stuck on C636 i had almost given up
[GUIDE] Fix Broken OTA Updates After Downgrade & Have EMUI 11 With GMS (C636)
Click to expand...
Click to collapse
What do you mean stuck on c636? c636 is only the region spesification. It has nothing to do with software/firmware. Only thing you need to check is that the software i compatible to your region. 636,432 etc....

Maybe this could help...
I came from 11.0.0.168. I reset my phone and am now running 10.1.0.134 software (432 region) Here is what i did:
1. use hisuite 11 to downgrade to 10.1.0.176.
2. use hisuite 10.x.x.550OVE and firmwarefinder on PC to downgrade to 10.1.0.134 (131)
3. Got error with hisuite proxy (No internet connection)
4. Remember to restart computer after change from hisuite 11 to husuite 10.
5. Now i got "You are using the latest software"
6. Use the register for proxy in firmwarefinder (at the top bar)
7. Update your computer's network connection with the correct DNS from firmware finder.
8. Now hisute proxy/firmware finder should work as before and all the files are there without error.
9. Download over the net with proxy.
10. Voila. 10.1.0.134 is installed.
11. Start from scratch with GMS (googlefier or manual)
(i did manual and use the indonesian file after donating to get no errors and notification even after restart. )
12. A fully working P40 Pro inc. GPS, GMS, Notification, Playstore and no error.
Only Google pay not working due to cts profile "false". Can only be fixed with root.
Hope this help some of you guys.
PS! After updating the correct DNS in your network card og router all the files in firmwarefinder works normally like before.
Stay safe

I successful passed steps 7 and 8.
7. Update your computer's network connection with the correct DNS from firmware finder.
8. Now hisute proxy/firmware finder should work as before and all the files are there without error.
After that HiSuite offers me the wished update (10.1.0.117). When I click update and confirm the privacy settings HiSuite wants to start the update progress by downloading the firmware. I then get an error message that there is no internet connection and the update is aborted.
I tried to play around with the proxy and DNS settings, but no success. Is it because the Team MT downloads are down? Or can anyone else help me with this?

leifstar81 said:
I successful passed steps 7 and 8.
7. Update your computer's network connection with the correct DNS from firmware finder.
8. Now hisute proxy/firmware finder should work as before and all the files are there without error.
After that HiSuite offers me the wished update (10.1.0.117). When I click update and confirm the privacy settings HiSuite wants to start the update progress by downloading the firmware. I then get an error message that there is no internet connection and the update is aborted.
I tried to play around with the proxy and DNS settings, but no success. Is it because the Team MT downloads are down? Or can anyone else help me with this?
Click to expand...
Click to collapse
I did restart my computer and did the prosess over again. Than it worked... Thats all i can say.
Team MT files are not down, they are Just not reachable until you change dns...

fromiOS2Android said:
I did restart my computer and did the prosess over again. Than it worked... Thats all i can say.
Team MT files are not down, they are Just not reachable until you change dns...
Click to expand...
Click to collapse
Thank you for your quick reply. I will try again, but these DNS settings didn't work so far. I changed the IP4 settings in the windows options -> network adapter.

leifstar81 said:
Thank you for your quick reply. I will try again, but these DNS settings didn't work so far. I changed the IP4 settings in the windows options -> network adapter.
Click to expand...
Click to collapse
Same as i did... I did it 2 or three times and then i started downloading you could always try to change the ruter settings instead of the network adapter

fromiOS2Android said:
Same as i did... I did it 2 or three times and then i started downloading you could always try to change the ruter settings instead of the network adapter
Click to expand...
Click to collapse
I tried everything now, multiple computers, changing DNS on the network settings in windows and in the router. Nothing works. Once in between HiSuite offers me the right update, but whenever the download is initiated the connection fails. Anyone has more good hints? Because I am running out of ideas.
I have ordered a OTG cable just in case I cannot make it work. But that still leaves me with the task to find a firmware to download. I thought of the JNY-LGPR2-OVS 10.0.1.136 or 10.0.1.117. Where can I find these?