Phone rebooting after HiProxy / HiSuite upgrade - Huawei P40 Pro Questions & Answers

Seems liked i have wrecked my device - i forced an update to .182 using hisuite proxy and hisuite. now the phone boots up is fine for 20-30 seconds and then just reboots. IMEI says unkown in settings. any ideas how to fix?

Nobody able to help?

I think I killed my phone
So far, it seems to me paying tools are failing on LGRP6 builds and on P40Pro+ devices without using physical testpoint mode. When software testpoint mode just works fine on LGRP4 builds and P40Pro device. For anyone with a bricked phone, oslo83...
forum.xda-developers.com

Related

Bricked mate 8 NXT-L29C185B320

Hi, I tried to get update from C185B320 to C185B560 through https://forum.xda-developers.com/mate-8/general/update-to-nougat-easiest-playstore-app-t3554957, but it didnt go well, so i rollback (coz people saying it works with lesser verison than C185B320) to C900B500 (i think, maybe B320).
Then i unlocked bootloader, installed recovery and twrp, then i tried to root my phone, but it didnt go well too. It only showed me that orange text, that it is unlocked and not safe or something like that, and device is booting in 5 sec, but never happened. I managed to somehow install back C185B160 (not sure how) and rooted phone correctly. Then i tried to rebrand to EU (C432) with guide https://www.youtube.com/watch?v=JZVsIKtdgV4. But at the end, i was getting C900B320, so i went back to C185B160 and it downloaded B560 update(with that app), so i was happy, put into DLOAD and started update, but it failed 5%, so i tried another update (C185B162) and after i put this into DLOAD and succesfully updated phone, it is not responding anymore. Display not working, phone not vibrating when restarting, led when it is plugged into the wall, or PC not lightning up. Only when working with SRK, or italian knife and reboot phone, it makes sounds when you disconnect your device from your pc and connect back in.
Can you please help me, i am pretty screwed up.
EDIT: ok i managed to get into the phone again, but my sim is not working (in DC phoenix is shown at the begining as Current version: NextL09C185EMUI50, but later as Build number: :NXT-L29C185B320, Product model: HUAWEI NXT-L29 how can i make my simcard working again?
Hi, how get back in your phone? i´m in the same trouble but i cant back in the fastboot or something again? Thanks in advance.
Federico
SEoR said:
Hi, I tried to get update from C185B320 to C185B560 through https://forum.xda-developers.com/mate-8/general/update-to-nougat-easiest-playstore-app-t3554957, but it didnt go well, so i rollback (coz people saying it works with lesser verison than C185B320) to C900B500 (i think, maybe B320).
Then i unlocked bootloader, installed recovery and twrp, then i tried to root my phone, but it didnt go well too. It only showed me that orange text, that it is unlocked and not safe or something like that, and device is booting in 5 sec, but never happened. I managed to somehow install back C185B160 (not sure how) and rooted phone correctly. Then i tried to rebrand to EU (C432) with guide https://www.youtube.com/watch?v=JZVsIKtdgV4. But at the end, i was getting C900B320, so i went back to C185B160 and it downloaded B560 update(with that app), so i was happy, put into DLOAD and started update, but it failed 5%, so i tried another update (C185B162) and after i put this into DLOAD and succesfully updated phone, it is not responding anymore. Display not working, phone not vibrating when restarting, led when it is plugged into the wall, or PC not lightning up. Only when working with SRK, or italian knife and reboot phone, it makes sounds when you disconnect your device from your pc and connect back in.
Can you please help me, i am pretty screwed up.
EDIT: ok i managed to get into the phone again, but my sim is not working (in DC phoenix is shown at the begining as Current version: NextL09C185EMUI50, but later as Build number: :NXT-L29C185B320, Product model: HUAWEI NXT-L29 how can i make my simcard working again?
Click to expand...
Click to collapse
First of all i tried unbrick via srk tool, but didnt work for me, si i used dcphoenix tool and it worked
Thanks, what tool of all of DCPhoenix?
SEoR said:
First of all i tried unbrick via srk tool, but didnt work for me, si i used dcphoenix tool and it worked
Click to expand...
Click to collapse

Flashing a mate 8 problem

Hi hope someone can advise as I'm loosing the will to live
I've a mate 8 NXT-L29C636 which I believe is asia region although I've from the UK
I was running stock android 6 with EMUI 4.0
When I ask it to check for any update, it always came back with no updates.
I saw plenty of threads saying they had updated to android 7 and 8 and how they done it.
So I downloaded Firmware Finder from Google play and without too much difficulty managed to start installing firmware. That's when my problems started
This was two weeks ago and I've been spending 100+ hours trying to recover.
I think it failed a 5% or something and since then my phone will not boot properly.
I can only fastboot it and sometimes to erecovery and EMUI to wipe/factory reset
Searching forums it seems DC Phoenix was the only software that could help so I bought it.
So far I've tried flashing firmware from DC-Unlocker site in standard more but all goes ok with success for all the partitions but it requires the phone to put into upgrade mode, something my phone never does and I can't force it.
So that leaves me with advanced mode, again all successful but booting the phone just gives the huawei logo then reboots again
I've tried different stock roms NXT-L29C636 but they all claim successful but still can't boot my phone
I've followed the steps in DC-Phoenix instructions to no avail.
The last step today meant shorting a pin to ground to force the phone into a mode when it was seen as windows as Huawei USB COM device, which seemed to work.
The instructions claimed I can use any NXT board flash as they're all the same and again all successful i used
NXT-AL10_M00A102_Board Software_Global _Nonspecific_Android 6.0_EMUI 4.0_05021WLB_4.dtwork
but the log file now says build is;
Build number: HLNXTAL10BM00A102
Model: HUAWEI NXT-L29
Battery state: 3249mv
from
Build number: :NXT-L29C432B192
Model: HUAWEI NXT-L29
Battery state: 7035mv
So my question is am I using the wrong firmware? It is always successful so I don't think it's bricked but I can't work out what I'm doing wrong.
Other things to mention is pressing vol - and vol + and power with sd card and dload doesn't work either.
Sorry for long post and thanks for reading
Any help very much appreciated
No-one? I didn't expect a reply right away, but I can't be the only one with questions? Is there a better forum to post on?
Thank you
so for any noobs out there, got this work. My problem was the phone would never go into upgrade mode. The problem was in device manager (windows 7x64 but doesn't matter which version of windows), was when DC-Phoenix tried to put the phone in upgrade mode the command was sent and acted on but device manager showed warning triangles that it didn't have a driver or the driver was only partially loaded.
When I directed it to the downloaded Hi-Suite (which has all the drivers) it loaded the driver(s) there are TWO drivers on virtual COM ports. So if you phone is not going into upgrade mode best to check that Windows can actually see these TWO COM ports.
Hope this helps someone

OnePlus 7 Pro not detected by PC at all (only in EDL/MSM mode)

Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.

HUAWEI P40 Lite Soft brick

Model:Huawei p40 lite
Hello, recently I flashed most propably bad firmware version and now the device seems to be soft bricked.
Black screen, no vibration while pressing power button, nothing.
However when I connect phone to PC, it does detect a device, I download HiSuite and device gets detected as Sooner ADB interface, but via HiSuite shows that recovery is not supported within the model.
ADB is also installed but devices show no devices at all.
When I press power button and volume down it seems to enter another state but device name/driver is the same. No fastboot.
It seems like it is not dead at all but I would have to use somekind of flash tool.
Any ideas would be appreciated
Thanks
Hi, is there a solution?
I need a solution to. Someone?
I am in the same situation. Is there someone to help?

Huawei P30 (ELE-L29 11.0.0.159 C431) TEST POINT AND DOWNGRADE PROBLEM

Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Experiencing the same problem, but i can get even in Tespoint mode. The Computer just wont list my phone and i can do absolutley nothing. Now the phone is a piece of Garbage?
Xynactra said:
Experiencing the same problem, but i can get even in Tespoint mode. The Computer just wont list my phone and i can do absolutley nothing. Now the phone is a piece of Garbage?
Click to expand...
Click to collapse
There is a way by SigmaKey Tools. But it's really expensive. In SigmaKey, there is a process that allowing you to flash the stock rom files (update.app and ptable.app). That means you can downgrade the firmware version without any problem or USB port lock. If you try to enable hardware test point and disassemble the phone, you can't connect the phone to PC in EMUI 11. So if you downgrade without USB port lock, you can enable the test point to. So there is only way to unlock bootloader and root Huawei phone is SigmaKey Tool. But too expensive for only one using.
I had the same problem. Phone was not detected in EDL mode. What i actually did to solve it is to pres left side of the board (so it makes contact with pins under it). holding it pressed i connected test point and usb c. and it all worked well
MrMutlu said:
There is a way by SigmaKey Tools. But it's really expensive. In SigmaKey, there is a process that allowing you to flash the stock rom files (update.app and ptable.app). That means you can downgrade the firmware version without any problem or USB port lock. If you try to enable hardware test point and disassemble the phone, you can't connect the phone to PC in EMUI 11. So if you downgrade without USB port lock, you can enable the test point to. So there is only way to unlock bootloader and root Huawei phone is SigmaKey Tool. But too expensive for only one using.
Click to expand...
Click to collapse
I have sigma box but it's all the same after downgrade usb function is locked.
Hi. Excuse me for writing in this section but i don't know who to talk to. I have Huawei Y6 2018 (ATU L21) and tried to flash via TWRP many custom ROMs witn no success. Everytime i get error 9 in TWRP. All Y6 roms in the net are like this one from the link below.
Huawei Honor 7A 2018 ATU-L21 hw eu HLRCF Atomu-L21 8.0.0.155(C432CUSTC432D1) Firmware 8.0.0 r1 EMUI8.0 05015CHD [androidhost.ru].zip - AndroidHost.RU
Download file - Huawei Honor 7A 2018 ATU-L21 hw eu HLRCF Atomu-L21 8.0.0.155(C432CUSTC432D1) Firmware 8.0.0 r1 EMUI8.0 05015CHD [androidhost.ru].zip
androidhost.ru
I also tried to open the zip file. There are two folders in it - "ReleaseDoc" and "Software". The software folder contains "dload" folder and in it "ATU-L21_hw_eu" folder with "update_sd_ATU-L21_hw_eu.zip" Also tried to flash this zip but again with no success and the same error. Where am i wrong. How to flash this ROM or maybe i have to install another version of TWRP. Mine is 3.3.1. Thanks in advance.
Pisonja said:
I had the same problem. Phone was not detected in EDL mode. What i actually did to solve it is to pres left side of the board (so it makes contact with pins under it). holding it pressed i connected test point and usb c. and it all worked well
Click to expand...
Click to collapse
Hi. I have the same problem. ele-l29 device open to go to edl with test points but it doesn't work.
It remains on a black screen but the PC does not show it on the devices. You say you pressed the left side ... but what?
novembre.973 said:
Hi. I have the same problem. ele-l29 device open to go to edl with test points but it doesn't work.
It remains on a black screen but the PC does not show it on the devices. You say you pressed the left side ... but what?
Click to expand...
Click to collapse
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
the problem of edl mode: just build a cable with a 10k resistor and use that to go into edl mode. better if the cable is equipped with a 10k resistor exclusion button because the telephone with the resistor connected can ONLY work in edl. so if any software needs to exit edl mode (eg: switch to fastboot) you can exclude the resistance and make the cable work normally.
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
USB/fast boot/fast charging and test point not working after downgrade.
I recently downgraded my Mate 20 Pro from EMUI 11.0 aware this would arise. I am now on EMUI 9.0 with USB/fast boot and fast charging working. I can't confirm if this fixed test point as I haven't opened my device yet.
Simple solution was to change the USB-C cable used to perform the downgrade to an alternative one. Everything sprung back to life, I have since reverted back to the original USB-C cable and everything works as expected.
You can find more information on the downgrade procedure I posted here
Helpful Information - Downgrading From EMUI 11 · Issue #127 · ProfessorJTJ/HISuite-Proxy
Professor JTJ if you can include this within the guide it may help others. The guide does mention about loss of fast charge, fast boot, USB and test point. And while I was initially affected too, o...
github.com
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
Hi, just a stupid question. How to exit from hard test point mode? I wanna try it to unlock bootloader on other device, but I'm not sure if after that I can exit from this particular mode. Thank you
MrMutlu said:
Hi, I want to unlock bootloader of my phome and root it via Magisk method. But recently I've discovered that there is no way to unlock bootloader when you upgraded to EMUI 11. Dc-Phoenix + HCU doesn't support after EMUI 10 software testpoint. So the only way is try to Hardware testpoint method. I disassembled the phone and reach the motherboard and testpoint pin without damaged it. I short the testpoint pin with metal ground, plugged the USB and managed to enable the testpoint mode (the screen was black.) But then I saw my computer cannot detect my phone in testpoint mode, there is no "Huawei USB COM 1.0" or "USB Ser". I find drivers for Huawei USB COM 1.0 but still no change at all. I check the "Device Manager -> Install Legacy Driver -> Install From Disc" but there is no Huawei Incorporated drivers. I think my PC's problem that cannot detect my device in testpoint mode is the drivers. Here is what I did step by step;
1- Battery fulled and power off, phones back cover removed carefully and reached the mothet board. Testpoint pin founded.
2- Huawei USB COM 1.0 drivers installed to PC (driver file from PotatoNV GitHub page.)
3- USB-A side plugged to PC and USB-C side is waiting
4- A conductive metal tool (mine is pointed tweezer) grabbed and shorted to pin to metal ground and I keep them so.
5- While keeping the testpoint shorted, I plugged the USB-C side to phone and waited couple of second.
Then when I look at the PC, there is no change. No device detected. First, I was think that I couldn't manage the testpoint shorting but when I plugged the Phone to PC without shorting, the Huawei boot screen appears. When I short the testpoint and plugged it, the screen is black which means the device is in test point mode. But then, PC is not detecting my phone. So my guess is that the problem is the drivers.
I find out I could use the HiSuite Proxy app to downgrade from EMUI 11 to EMUI 10 so I can use the DC-Phoenix + HCU, but I tried this method before disassembling the phone. It didn't work that time. 2 days ago, I tried again this method to downgrade and use the software testpoint and I successfully downgraded it. The problem was HiSuite 10.0.0.550 cannot flash EMUI 11 but HiSuite 10.1.... can flash EMUI 11. I was in 11.0.0.159 firmware version and downgraded to 10.1.0.150 firmware version.
After that day, I decided to start to unlock method by DC-Phoenix and HCU but before buying timed licence I want to be sure that everything is okey. First, I plugged to phone to PC and that is the end of the way. There is no way to connecting PC after downgrade. I searched it from XDA and find out that after some security patchs or firmware versions if you try to downgrade, your USB activities are locked. And when you reach to latest version (version before I downgrade from), USB problem is solved. This is about the Huawei's new security patch, I guess. Many of Huawei P40 user is complaining about same problem. They are telling that in P40 after 11.0.0.180 update, if they try to downgrade, there USB functions are limited (no fast charge, no OTG or USB driver, no PC connecting). So, if you're using your Huawei phone and you are in EMUI 11 and after some update you will be get this problem too. There is no way to unlock bootloader or root on EMUI 11. There is no way to downgrade. But I searched and find out that you can flash any stock rom by SigmaKey. It is very expensive but you can flash stock rom to downgrade. You need just dload files (that 3 zips) and unzip the update.app and ptable.app files. Do that for 3 zip packages. And you can flash roms without any problem.
What I tried and discovered is dload method won't work this USB problem. Everyone knows that you can't downgrade from EMUI 11 by dload method. I downgrade with HiSuite Proxy to EMUI 10.1.0.150 and after downgrade I tried to dload method to upgrade firmware to 10.1.0.161. Dload is failed in %94 and I restarted device. The version is upgraded to 10.1.0.161 and all user data formatted but USB problem is not solved. When I upgraded to latest firmware, the problem is solved. But I want to downgrade without any problem and root this phone.
My biggest advice to anyone who have the Huawei phone, DO NOT UPGRADE YOUR PHONE WITHOUT SEARCHING THE NEW VERSION. IT IS LIKE HUAWEI FORCING EVERYONE TO UPGRADING THERE PHONE OR CANNOT DOWNGRADE TO ANY FRIMWARE.
Does anyone has same problem with me? What is the solution for this? I removed the back of the phone for nothing? I have to unlock the bootloader and root this device. I would really appreciated if you can help me.
Click to expand...
Click to collapse
A successful downgrade per the above is required in conjunction with a
Huawei (HarmonyOS) testpoint cable (Huawei USB COM 1.0)​Otherwise, whilst enabled Test Point mode will not work.
EnryP said:
Hi, just a stupid question. How to exit from hard test point mode? I wanna try it to unlock bootloader on other device, but I'm not sure if after that I can exit from this particular mode. Thank you.
Click to expand...
Click to collapse
If you used Test Point, the phone will be in Factory Mode only temporarily. If you do a hard reset for example, it will automatically exit the Factory Mode.
Loggsie said:
If you used Test Point, the phone will be in Factory Mode only temporarily. If you do a hard reset for example, it will automatically exit the Factory Mode.
Click to expand...
Click to collapse
Thank you for replying me.
So, for exit test mode I have to do an action such as a factory reset with softwares like DC Unlocker, SigmaKey etc.. but,for example, I can't just turn off the phone to leave it or use any button combination. Am I RIght?
EnryP said:
Thank you for replying me.
So, for exit test mode I have to do an action such as a factory reset with softwares like DC Unlocker, SigmaKey etc.. but,for example, I can't just turn off the phone to leave it or use any button combination. Am I RIght?
Click to expand...
Click to collapse
A hard reset is a simple rebooting of your phone using the hardware buttons i.e. holding power and volume down simultaneously (varies per device). A factory reset isn't needed, this is when you erase data.
Loggsie said:
A hard reset is a simple rebooting of your phone using the hardware buttons i.e. holding power and volume down simultaneously (varies per device). A factory reset isn't needed, this is when you erase data.
Click to expand...
Click to collapse
Okay, but let's suppose that I enter hardware test point mode but then I don't do (or I can't do) any action with the softwares mentioned before (let's suppose because PC doesn't recognize the phone) Is there a way to quit this mode? For example, what happen if the phone get turned off? Thank you again.
Edit: My bad, I confused hard reset with factory reset. Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)
EnryP said:
Okay, but let's suppose that I enter hardware test point mode but then I don't do (or I can't do) any action with the softwares mentioned before (let's suppose because PC doesn't recognize the phone) Is there a way to quit this mode? For example, what happen if the phone get turned off? Thank you again.
Edit: My bad, I confused hard reset with factory reset. Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)
Click to expand...
Click to collapse
Yes exactly this 'Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)'.
EnryP said:
Okay, but let's suppose that I enter hardware test point mode but then I don't do (or I can't do) any action with the softwares mentioned before (let's suppose because PC doesn't recognize the phone) Is there a way to quit this mode? For example, what happen if the phone get turned off? Thank you again.
Edit: My bad, I confused hard reset with factory reset. Therefore to exit test point mode I can perform an hard reset (reboot the phone wth buttons combination)
Click to expand...
Click to collapse
You can just disconnect the battery, unplug cable and connect battery back
It can be solve by modified cable by using 10k resistor between on red and green wire
USB will works on downgraded devices (TEST PONT, Fastboot, MTP, etc.)
{
"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"
}

Categories

Resources