Hi,
This is a patch that can be used with HSTool by mikeos to upgrade your Mate 20 Pro.
If the FH patch is working just fine for you then you don't need this. If had previously used the FunyHauwei patch and it didn't work then you may still need to remove its entry from your host file "80.255.11.142 query.hicloud.com" to get this one working.
After you setup HiSuite 9.0.2.301 run this patch and you should be good to go
Device not supported message!
Fresh Install Windows -10
My device : LYA-L0C C792 Canadian carrier unlock single sim.
Followed each and every step mentioned in hstool but still not succeed.
Any clue what is the problem or my device actually not supported.
Thanks,
goldybewon
Don't forget you have to run the patch as admin or it doesn't update properly.
Also double check that hosts file has saved correctly.
Grondah said:
Don't forget you have to run the patch as admin or it doesn't update properly.
Also double check that hosts file has saved correctly.
Click to expand...
Click to collapse
Did everything but still not succeed. It confirm my device not supported.
Two days try and error period no matter what OS or PC.
Patch, Host file editing, Notepad ++, Fresh Win 10 OS, Administrative Rights.
Hard luck.
Thanks,
goldybewon
goldybewon said:
Device not supported message!
Fresh Install Windows -10
My device : LYA-L0C C792 Canadian carrier unlock single sim.
Followed each and every step mentioned in hstool but still not succeed.
Any clue what is the problem or my device actually not supported.
Thanks,
goldybewon
Click to expand...
Click to collapse
Double check your host file and make sure you don't have any entries for query.hicloud.com as that will result in that device actually not supported error (The FH patch puts that in even if it didn't work for you)
The step in HSTool where it asks to edit your host file and start HiSuite, just disconnect your internet ... reconnect at the step it asks you the 2nd time
LYA-AL00 got this error, how to fix this ? this phone com from china region
Xalies said:
Hi,
This is a patch that can be used with HSTool by mikeos to upgrade your Mate 20 Pro.
If the FH patch is working just fine for you then you don't need this. If had previously used the FunyHauwei patch and it didn't work then you may still need to remove its entry from your host file "80.255.11.142 query.hicloud.com" to get this one working.
After you setup HiSuite 9.0.2.301 run this patch and you should be good to go
Click to expand...
Click to collapse
Thanks for this keeping alive
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Hi, Is there a newer version to enable support for P30 and P30 Pro?
JazonX said:
Hi, Is there a newer version to enable support for P30 and P30 Pro?
Click to expand...
Click to collapse
In funkyhuawei payiment web there are some version, i dont know if there are in free sites
Enviado desde mi LYA-L29 mediante Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
JazonX said:
Hi, Is there a newer version to enable support for P30 and P30 Pro?
Click to expand...
Click to collapse
In This page must be use search option to find p30pro firmware
https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=Ele&firmware_page=0
Enviado desde mi LYA-L29 mediante Tapatalk
Didn't work for me
Xalies said:
Hi,
This is a patch that can be used with HSTool by mikeos to upgrade your Mate 20 Pro.
If the FH patch is working just fine for you then you don't need this. If had previously used the FunyHauwei patch and it didn't work then you may still need to remove its entry from your host file "80.255.11.142 query.hicloud.com" to get this one working.
After you setup... run this patch and you should be good to go[/QUOTHi
I followed the steps and still receiving the same error message. My device is not supported. Checked host file and is clean (all lines is commented)
My phone is BND-L34. Any suggestions?
Click to expand...
Click to collapse
I've got a probelm on a huawei mate 20 pro using that patch, one hisuite has downloaded the file an decompressed it, than it has installed the recovery it gaves me an error, impossible to install recovery.
wheres the patch?
Related
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Stransky said:
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Am on 8.1 global variant. How are you still on Feb?
Scarkinyua said:
Am on 8.1 global variant. How are you still on Feb?
Click to expand...
Click to collapse
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
AchinPakhi said:
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Click to expand...
Click to collapse
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
They've also removed the functionality in which you can navigate using the fingerprint sensor ?
After the may 2018 update I noticed some 4G connectivity issues: no more internet. By moments, the phone would switch to 3G and then internet would work.
I thought I did something bad, so I reset APNs, etc. no luck. I even completely wiped the phone, but that did not change anything.
Then I saw this thread on Nokia forum:
https://community.phones.nokia.com/support/discussions/topics/7000025066
For now, by forcing 3G, I can get internet all the time, but I hope this fix will be temporary.
Scarkinyua said:
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
Click to expand...
Click to collapse
ah sorry for a super late reply.. if u have already set up trusted face then it's already been activated.. just lock the screen and turn on using the power button.. there will be a small face icon at the bottom middle of the screen .. when it recognized ur face it will show a unlocked lock(open lock) icon.. then just swipe up the screen...
TA-1062
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Stransky said:
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Much easier with the roll back firmware and sideload using ADB or straight from recovery.
Done the ADB and got 8.1 April version (no wipe and everything seem to work fine).
After that got OTA update to May security patch.
More here: https://forum.xda-developers.com/showpost.php?p=76546067&postcount=56
It may be working without enrollment to developer preview. Someone uploaded the zip.
Alfaroerik87 said:
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Click to expand...
Click to collapse
I'm also stuck on 8.0 1062.
Flameboy42 said:
I'm also stuck on 8.0 1062.
Click to expand...
Click to collapse
I'm on 8.1 :/
Alfaroerik87 said:
I'm on 8.1 :/
Click to expand...
Click to collapse
What's your location?
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
tkiafar said:
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
Click to expand...
Click to collapse
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
Flameboy42 said:
What's your location?
Click to expand...
Click to collapse
I'm from Chile
Alfaroerik87 said:
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
I'm from Chile
Click to expand...
Click to collapse
Main directory is the same directory you open first when you connect your device for file transfer, that contains "alarms , android, data" directories. I put the file there without renaming it, and dialed the code. There are posts on the same thread that cover file not found issue, check them out. In any case if it doesn't find the file the only option is ADB sideload.
Face unlock was added
Face unlock was added and security patch updated to may
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
Hello,
i have the problem with google pay.
The safetycheck says cts: false.
I have the build 9.1.0.241
who can fix this problem?
thanks in advance
I had the same, it's not verified by Google, I went to 9.1.0.311 and it worked fine.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
It's not fixable without a firmware flash
It looks like this is a pretty common issue with P20 Pro users and here isn't a solution or a fix yet. Download to 9.1.0.311 until a fix has been implemented.
downgrade your firmware to previous version
Is it possible to downgrade without losing data ?!
Edit :Can someone point out a tutorial to downgrade?!
tnnuy said:
Is it possible to downgrade without losing data ?!
Edit :Can someone point out a tutorial to downgrade?!
Click to expand...
Click to collapse
Install Huawei HiSuite on PC, Connect your phone to PC, once the HiSuite recognized your phone, go to Software Update, it will say your phone has the latest software available. Click the "Other software versions" (or something like that) below, and it will show you the earlier firmware versions. Select something you know it works well, and just go ahead with it.
You should also backup your data using HiSuite before doing the downgrade, just in case if you need to restore them later.
spiderx_mm said:
Install Huawei HiSuite on PC, Connect your phone to PC, once the HiSuite recognized your phone, go to Software Update, it will say your phone has the latest software available. Click the "Other software versions" (or something like that) below, and it will show you the earlier firmware versions. Select something you know it works well, and just go ahead with it.
You should also backup your data using HiSuite before doing the downgrade, just in case if you need to restore them later.
Click to expand...
Click to collapse
I tried to do that and other ways and I just brick my p20 pro
Unlocked bootloader ?
I already solved my problem .. I used the Multi-Tool 8, and I used the unbrick part and flashed the img
yes @veimus my bootloader is unlocked.
Good afternoon,
So I got a Mate 10 Dual sim ALP-l29 (C636). I used to be on EMUI 10, but I want to root it (for one reason only, unlock camera api to get raw on the monochrome sensor).
I managed to roll back 2 times and ends up with 8.0.0.143 with the security patch of 1 october 2018. Unfortunately I need to be on June 2018 to be able to unlock the bootloader and then, root it.
So I tried hisuite proxy and copy paste links to try to get to an older firmware but I'm stuck.
Ideally I want ALP-L29C636B136 (8.0.0.136)
What should I put for CUST and PRELOAD ?
ALP-L29-OVS 8.0.0.136
ALP-L29-CUST 8.0.0136(C636)
ALP-L29-PRELOAD 8.0.0.136(C636R1)
I tried, hisuite, it download the files but then it stops at the install and failed.
I tried via the sd card and dload folder but stops at 5%.
A bit lost, if someone could help that would be awesome !
julientaming said:
Good afternoon,
So I got a Mate 10 Dual sim ALP-l29 (C636). I used to be on EMUI 10, but I want to root it (for one reason only, unlock camera api to get raw on the monochrome sensor).
I managed to roll back 2 times and ends up with 8.0.0.143 with the security patch of 1 october 2018. Unfortunately I need to be on June 2018 to be able to unlock the bootloader and then, root it.
So I tried hisuite proxy and copy paste links to try to get to an older firmware but I'm stuck.
Ideally I want ALP-L29C636B136 (8.0.0.136)
What should I put for CUST and PRELOAD ?
ALP-L29-OVS 8.0.0.136
ALP-L29-CUST 8.0.0136(C636)
ALP-L29-PRELOAD 8.0.0.136(C636R1)
I tried, hisuite, it download the files but then it stops at the install and failed.
I tried via the sd card and dload folder but stops at 5%.
A bit lost, if someone could help that would be awesome !
Click to expand...
Click to collapse
You can't downgrade bellow that version.
Pretoriano80 said:
You can't downgrade bellow that version.
Click to expand...
Click to collapse
Oh crap, there is absolutely no solution ?
julientaming said:
Oh crap, there is absolutely no solution ?
Click to expand...
Click to collapse
There is a solution, but requires the back cover removal and a paid software.
However, if you are interested in camera API, you will be disappointed, because Huawei devices has only limited support, no matter the firmware version.
Pretoriano80 said:
There is a solution, but requires the back cover removal and a paid software.
However, if you are interested in camera API, you will be disappointed, because Huawei devices has only limited support, no matter the firmware version.
Click to expand...
Click to collapse
Isn't possible if I do this solution with the back cover and root the phone to modify the build.prop file with persist.camera.HAL3.enabled=0 ?
julientaming said:
Isn't possible if I do this solution with the back cover and root the phone to modify the build.prop file with persist.camera.HAL3.enabled=0 ?
Click to expand...
Click to collapse
Nope, camera2api support it's always limited. It was like that since Mate 10/Pro was released and sadly Huawei never enabled full support.
Pretoriano80 said:
Nope, camera2api support it's always limited. It was like that since Mate 10/Pro was released and sadly Huawei never enabled full support.
Click to expand...
Click to collapse
ok so I did the ministryofsolutions for 30 $ and it works, I have unlocked the bootloader + rooted my phone. Now I'm exploring files to see if I can find anything about the camera
So I got a Huawei P40 Pro Plus and I used by mistake my software files for P40 Pro. The Pro+ is now stuck and restarts every 2~3 minutes so I don't have enough time to download another version and repair it. I tried with system recovery on HiSuite as suggested in another thread but to no success. I wanted to ask if anyone knows where I can get the Huawei P40 Pro Plus stock firmware (ROM) so that I can flash it. All the ones I find don't have a dload file directory and are missing the SYSTEM.img file (instead there is this weird SUPER.img file).
Thank you in advance
I have the same problem, only on the contrary, I installed firmware from P40 Pro + on my P40 Pro. I am also looking for a solution to the problem, but unsuccessfully so far.
---------- Post added at 08:53 PM ---------- Previous post was at 08:44 PM ----------
Ashacreed said:
So I got a Huawei P40 Pro Plus and I used by mistake my software files for P40 Pro. The Pro+ is now stuck and restarts every 2~3 minutes so I don't have enough time to download another version and repair it. I tried with system recovery on HiSuite as suggested in another thread but to no success. I wanted to ask if anyone knows where I can get the Huawei P40 Pro Plus stock firmware (ROM) so that I can flash it. All the ones I find don't have a dload file directory and are missing the SYSTEM.img file (instead there is this weird SUPER.img file).
Thank you in advance
Click to expand...
Click to collapse
Try to restore via FASTBOOT according to this instruction: https://github.com/ProfessorJTJ/HISuite-Proxy/wiki/System-Recovery-Rom-Instruction-(-Soft-Bricked-)
only you need the correct cust and preload files for your region.
Did the method work for anyone as I am facing the similar behavior
loser said:
Did the method work for anyone as I am facing the similar behavior
Click to expand...
Click to collapse
it worked for the person who posted it but not for me sadly. I bought the MRT software key and it just arrived seconds ago and I will try to repair it today or tomorrow. I wish you luck my dude sadly I don't know how to help. Can you amybe give more information
Would be interesting to know what exactly was done - I am struggling to get the firmware files placed on the right directory for Hisuite to detect and repair the phone . It keeps indicating firmware package files are missing .The background is I went from 1.56 to 1.31 and it has been a constant boot loop since then . Very expensive paperweight at the moment ,
loser said:
Would be interesting to know what exactly was done - I am struggling to get the firmware files placed on the right directory for Hisuite to detect and repair the phone . It keeps indicating firmware package files are missing .The background is I went from 1.56 to 1.31 and it has been a constant boot loop since then . Very expensive paperweight at the moment ,
Click to expand...
Click to collapse
You may be substituting invalid links in hisuite.proxy
You might be right . This is what I followed >
1. Prerequisites- OK
2.Full OTA -Installation Instructions :
You need to find the matching firmwares and link to them in the application.
The above is where I am stuck - how to link and what does ut even mean . I have got the firmware files downloaded , seems like the locked bootloader does not allow to go forward .
Any ideas ?
KINGZ_ said:
You may be substituting invalid links in hisuite.proxy
Click to expand...
Click to collapse
Remember-I am in a bootloop, cannot use hisuite proxy. I have actually downgraded using Hisuite Proxy so that works just fine .
Did you have any luck with the MRTKey >?
---------- Post added at 11:03 AM ---------- Previous post was at 10:27 AM ----------
Ashacreed said:
it worked for the person who posted it but not for me sadly. I bought the MRT software key and it just arrived seconds ago and I will try to repair it today or tomorrow. I wish you luck my dude sadly I don't know how to help. Can you amybe give more information
Click to expand...
Click to collapse
Could you advise what was done ?
Latest update - upgraded to 1.57 by Hisuite Recovery. However the bootloop issue is still not fixed. IMEI is unknown and Camera has become upside down. I have very little chance to get support in my country from the service center where they refuse to support imported models and no option to send to UAE from where the model is from . Any tips will be highly appreciated.
loser said:
Latest update - upgraded to 1.57 by Hisuite Recovery. However the bootloop issue is still not fixed. IMEI is unknown and Camera has become upside down. I have very little chance to get support in my country from the service center where they refuse to support imported models and no option to send to UAE from where the model is from . Any tips will be highly appreciated.
Click to expand...
Click to collapse
You will need to find out using fastboot which version is current on your device, and then use the dload firmware for your region.
To find out how to get the latest firmware information, check Fastboot for the OEM information. PLEASE see post #253 for instructions if needed. Then follow the instructions for recovery via fastboot.
(bootloader) :ELS-N39 10.1.0.157(C185E2R1P1)
OKAY [ 0.004s]
finished. total time: 0.005s
ELS-LGRP4-OVS 10.1.0.157
ELS-N39-CUSTC1851B2 (10.1.0.2)
ELS-N39-PRELOADC185R41B1 (10.1.0.1)
Tried with C185 firmware - recovery fails at 89%. Then the same bootloop continues with the above version ( moved up from the problematic 1.31. Now trying with 1.62 which is an approved firmware .Fingers crossed.
loser said:
ELS-LGRP4-OVS 10.1.0.157
ELS-N39-CUSTC1851B2 (10.1.0.2)
ELS-N39-PRELOADC185R41B1 (10.1.0.1)
Click to expand...
Click to collapse
yes, only if you have p40 pro +, you need a firmware database for p40 +. in my opinion for p40 + this is ELS-LGRP6-OVS
and I can't tell you exactly which PRELOAD file is right for you as there are four of them.
if you just have p40 pro, then cust & preload look for ELS-N29 and firmware ELS-LGRP4-OVS base.
loser said:
Remember-I am in a bootloop, cannot use hisuite proxy. I have actually downgraded using Hisuite Proxy so that works just fine .
Did you have any luck with the MRTKey >?
---------- Post added at 11:03 AM ---------- Previous post was at 10:27 AM ----------
Could you advise what was done ?
Click to expand...
Click to collapse
So far I have tried the MRT Key but it gives me failure when trying to establish a USB connection while the phone is in Fastboot mode. I am trying to find how to fix it right now and I hope it will work. I have tried Hisuite proxy before with versions 156, 144 and 132 but nothing worked for me so I will keep trying with fastbooting and the Key. Sadly I cannot say if it will be successful and if you should buy it for yourself. I found a tutorial on YouTube how to use it but that failure mentioned earlier is in the way and the recovery never gets past 5%.
KINGZ_ said:
yes, only if you have p40 pro +, you need a firmware database for p40 +. in my opinion for p40 + this is ELS-LGRP6-OVS
and I can't tell you exactly which PRELOAD file is right for you as there are four of them.
if you just have p40 pro, then cust & preload look for ELS-N29 and firmware ELS-LGRP4-OVS base.
Click to expand...
Click to collapse
Well I was trying with LGRP4- all this while , which might have been the problem . Thanks for the great hint . Let me give LGRP6 a shot now .
---------- Post added at 06:08 AM ---------- Previous post was at 05:19 AM ----------
loser said:
Well I was trying with LGRP4- all this while , which might have been the problem . Thanks for the great hint . Let me give LGRP6 a shot now .
Click to expand...
Click to collapse
Bummer - Recovery failed at 5%, no change in status unfortunately . While the preload and the cust zips seem to have the region specific C185 tags , there seems to be no way to identify the main file belonging to the same region for making sure all 3 files are correct. Any ideas here ?
loser said:
Bummer - Recovery failed at 5%, no change in status unfortunately . While the preload and the cust zips seem to have the region specific C185 tags , there seems to be no way to identify the main file belonging to the same region for making sure all 3 files are correct. Any ideas here ?
Click to expand...
Click to collapse
Hi there,
Got your PM & read this thread to get more info about your problem.
You would need to use dload firmware for C185. Using other methods like HiSuite Proxy or HiSuite recovery won't help you at this point. Even eRecovery will get you ''Getting package info failled''!
{Mod edit: Link removed! - Oswald Boelcke, Moderator}
@Ashacreed, it seems that you got yourself a hardbricked device, because you've flashed a firmware from a diferent phone model, so in your case a new motherboard is required...
Kdrgs,
SilviuO
SilviuO said:
Hi there,
Got your PM & read this thread to get more info about your problem.
You would need to use dload firmware for C185. Using other methods like HiSuite Proxy or HiSuite recovery won't help you at this point. Even eRecovery will get you ''Getting package info failled''!
@Ashacreed, it seems that you got yourself a hardbricked device, because you've flashed a firmware from a diferent phone model, so in your case a new motherboard is required...
Kdrgs,
SilviuO
Click to expand...
Click to collapse
Dear SilviuO,
Thanks for getting back .
Nothing for C185 listed on easy-firmware , okay to flash with something else ? To be honest I made the most progress with Hisuite proxy method but unable to complete fully beyond 89% and the phone keeps in the bootloop every 1min 15 secs. Camera has become upside down and IMEI has become unknown .
I seem to have little hope .
Thoughts ?
loser said:
Dear SilviuO,
Thanks for getting back .
Nothing for C185 listed on easy-firmware , okay to flash with something else ? To be honest I made the most progress with Hisuite proxy method but unable to complete fully beyond 89% and the phone keeps in the bootloop every 1min 15 secs. Camera has become upside down and IMEI has become unknown .
I seem to have little hope .
Thoughts ?
Click to expand...
Click to collapse
You could try flashing other firmware (ex. for C605 or C432) using this method from my thread. You also need to rename those 2 zips (update_sd_cust&update_sd_preload) to match C185 dload firmware folder names . Be advised that this would be the first time someone tries the method explained on a P40 Pro / P40 Pro+ unit!
Cheers,
SilviuO
SilviuO said:
You could try flashing other firmware (ex. for C605 or C432) using this method from my thread. You also need to rename those 2 zips (update_sd_cust&update_sd_preload) to match C185 dload firmware folder names . Be advised that this would be the first time someone tries the method explained on a P40 Pro / P40 Pro+ unit!
Cheers,
SilviuO
Click to expand...
Click to collapse
Giving it a try as per your guide- wish me luck
---------- Post added at 09:44 AM ---------- Previous post was at 09:15 AM ----------
No luck -Software install failed , Incompatibility with current version . Please download the correct update package .
loser said:
Giving it a try as per your guide- wish me luck
---------- Post added at 09:44 AM ---------- Previous post was at 09:15 AM ----------
No luck -Software install failed , Incompatibility with current version . Please download the correct update package .
Click to expand...
Click to collapse
Guess that you will have to wait for a proper C185 dload firmware with a higher build number than the one you're currently on and try flashing again.
Kdrgs,
SilviuO
Version has upgraded to 1.62 but the issues are not resolved - because the flashing never completed fully looks like . The factor of the main file being not indicated as the main location based file marked for C185 region . I have got cust and preloaded files which C185 version , which seems to be not good enough . Interestingly wipe cache partition and factory reset do not seem to have any impact whatsoever on error , which I find strange based on my Android experience.
ELS-LGRP6-OVS 10.1.0.162
ELS-N39-CUSTC1851B2 (10.1.0.2)
ELS-N39-PRELOADC185R41B1 (10.1.0.1)
any one can post preload and cust file for p40 pro c636 regions, i can find any on the internet.
or anyone can help me unbricked my phone
thank you
kellogsvibrant said:
any one can post preload and cust file for p40 pro c636 regions, i can find any on the internet.
or anyone can help me unbricked my phone
thank you
Click to expand...
Click to collapse
It is better to provide the all story and many, many details. From what EMUI version was on the phone, what methods you used till the current situation. There are so many variables.
sorry, im was on emui 12, then i really need gms to work, reverted back to emui 10, and iupdated to emui 12 using flashdrive trick, i DL wrong firmwaree i guess, then it got bricked stuck on erecovery mode. after i flashed using usb
kellogsvibrant said:
sorry, im was on emui 12, then i really need gms to work, reverted back to emui 10, and iupdated to emui 12 using flashdrive trick, i DL wrong firmwaree i guess, then it got bricked stuck on erecovery mode. after i flashed using usb
Click to expand...
Click to collapse
Write for every step what firmware, files have been used.
I updated my huawei to beta emui12, i got in ang got the OTA for emui 12, but i really need GMS now, then i used hisuite proxy downgraded my p40 pro to emui 10, but cant remmeber exact number, it was success then my pc wont detect my huawei, lastly i tries using the usb otg OTA update. the after restart i get this error
any one can link me full firmware files for this region , il gladly appriciate.
kellogsvibrant said:
any one can link me full firmware files for this region , il gladly appriciate.
Click to expand...
Click to collapse
It is not so easy as you think it is.
In my opinion it is better to go to the service.
It is a slightly chance to fix with HarmonyTP cable + HiSuite Proxy (Recovery OS).
Looking at your questions and answers, you have no idea about how the things works with this phone.
You can try to ask here too:
HISuite Proxy ( Huawei Phones' Updater & Soft-Brick Fixer )
Introduction Simply this application reverse engineers ( modifies ) HISuite, to be able to manipulate its Huawei servers' response data for installing official roms of Huawei, customarily. Features Support for OTA ROMs Support for FullOTA ROMs...
forum.xda-developers.com
or on telegram group here:
Huawei Firm Finder / HiSuite Proxy Support
https://professorjtj.github.io
t.me