Related
Please i need help fast. Im going away tomorrow and i need my phone. I had gms successfully installed earlier today, but i accidentally deleted something and it stopped working, so i factory reset multiple times, even upgraded to emui 11 but still my p40 pro wont recognise its plugged into a computer. i need this to be able to re-install gms, the phone is useless without it. Please if you see this and can help please do.
Thanks in advance
also when i try to enable usb debugging and exit and go back in, usb debugging is disabled. i thought resetting would fix it but apparantly reset isnt a full reset i am ****ed without you guys's help
factory reset didnt work either
clearing the cache didnt work either
i managed to reset it , and i managed to install google, i had fast charging and i was able to connect my phone to pc again, but as soon as i got google fast charging and the usb ability dissappeared
stupid question: are you sure you have pushed the USB plug in FULLY (requires some force)? I made the same mistake yesterday when I got the phone... charging started with the plug only inserted halfway, but PC connection was only established when the plug was inserted all the way.
Same problem here, too. Emui 11, 11.0.0.193, C432E3R5P3 . Read about same problem in german forum's, too. Couldn't downgrade now. No PC connection, no fast charge, no symbol to choose between charge, data or photo mode. Tested with many cables and fast chargers (my woman's p40pro works perfect with same .193 version) Tried to choose "download last version" in recovery mode, but nothing new after that try. So my only hope is the next Huawei update version.
hi man
i have a same problem
my phone is huawei p40 pro
how to fix usb c port of the phone not function only charging , no fastboot ,no mtp ,no usb debugging ,no hdb
this is what i did
at the first usb c works fine
untill i did downgraded from version 11.0.0.190(c185R3) to version EMUI 11.0.0.153(c185R3)
i used hisuite proxy method and i got firmwares from https://www.firmfinder.ml/
after phone bootup 11.0.0.153 firmware , it seems usb c port disabled and just charging works
even i couldn't toggle usb debugging and change usb mode to MTP
after that i again downgraded to 10.1.0.114(c185R3) and nothing change . still usb c disabled
so i couldn't connect my phone to usb , and even i couldn't use usb otg
so i decided to use my phone itself's online update. i run updating first to 10.1.0.183 and nothing changed
again updated with itself's online update. update to 11.0.0.153 and still nothing changed
finaly the last firmware update. i updated with itself's online update to 11.0.0.195 . and see usb c work , even usb otg , and usb debugging and MTP , all works perfect
can you explain what happend on my phone and why usb don't work when i use hisuite proxy method ?
i did it again and again , all same result
same problems as you guys , It seems that the official update with the phone itself can only solve the problem
Our beloved Huawei made some changes on the firmware. Long live Huawei!
LE: They do a lot of work to prevent downgrade and install Google on their phones. I think this workaround is on international firmware (phones) only.
try to change your data cable.
Transfer WhatsApp from Android to iPhone
blitzlee06 said:
try to change your data cable.
Transfer WhatsApp from Android to Iphone
Click to expand...
Click to collapse
No chance.
someone in p20pro forum told this way:
you type *#*# 2846579#*#* in phonepad and it takes you to project menu,then you press background settings and then change port mode from hisuite to google...then it is detected by adb...easy
Click to expand...
Click to collapse
USB Debugging not working
I can toggle the option in the developer menu, but it don't show on the PC. If I exit that menu and go back in, USB debugging is off again. I've tried a restart without affect. Any ideas?
forum.xda-developers.com
i am now downgrading again to see if this way works
badmania98 said:
No chance.
Click to expand...
Click to collapse
did you ever test latest firmware?
try to update to 11.0.0.195 by phone itself ( settings > system & update > software update )
EAGLEBOOY said:
did you ever test latest firmware?
try to update to 11.0.0.195 by phone itself ( settings > system & update > software update )
Click to expand...
Click to collapse
What is the clue? If you downgrade you will lose the USB connection to PC. If you update to the last firmware version you will gain the connection back (99,99%).
badmania98 said:
What is the clue? If you downgrade you will lose the USB connection to PC. If you update to the last firmware version you will gain the connection back (99,99%).
Click to expand...
Click to collapse
exactly true
i tested again , 1 more time, still same as i said before
I tested all the methods, there is no way to fix it except the update by itself to build 11.0.0.195
i am now again upgrading to .195 to fix issue
{
"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"
}
EAGLEBOOY said:
exactly true
i tested again , 1 more time, still same as i said before
I tested all the methods, there is no way to fix it except the update by itself to build 11.0.0.195
i am now again upgrading to .195 to fix issue
View attachment 5392867View attachment 5392869
Click to expand...
Click to collapse
So, we have the same opinion. This is it. Thanks Huawei!
I am happy with my 10.1.0.121.
Hi there,
Huawei July Patch 2021 close all posibility to downgrade the FIRMWARE, it can be done with Hisuite Proxy but you have to choose the correct FIRMWARE and suitable to your Phone region. Once it done you can fix the "DISABLE USB" by doing OTA update to latest FIRMWARE to make it works.
When you choose the wrong cust/preload/mainFW your phone will be locked with that current FIRMWARE with "DISABLE USB" forever, you can solve this by searching the correct FIRMWARE and flash it using NMCARD the FIRMWARE should be a Higher than your Current FIRMWARE INSTALLED. after all done you can get OTA update and do OTA Update to latest FIRMWARE to make USB WORK.
Please be NOTED : Testpoin Not Working with latest July 2021 Firmware Patch so Huawei Block any downgrade posibility
I found 2 Brand USB Thumbdrive which is work with "DISABLE USB" you can do such Dload or restore Lzplay to instal GMS before update with OTA UPDATE. Here I attached the USB Thumb Drive.
badmania98 said:
So, we have the same opinion. This is it. Thanks Huawei!
I am happy with my 10.1.0.121.
Click to expand...
Click to collapse
is usb works on .121 ?
i am on 11.0.0.195 now , and usb works perfect
EAGLEBOOY said:
is usb works on .121 ?
i am on 11.0.0.195 now , and usb works perfect
Click to expand...
Click to collapse
It works, but my phone was not updated to the EMUI 11.0.19x versions. I knew what Huawei do with their firmware, and I stopped update the EMUI.
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"
}
Hello everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it
optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"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"
}
Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?
optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...
S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?
Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)
Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got
Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.
EDIT: Solution here https://forum.xda-developers.com/t/fixed-issue-with-msm-tool-on-le2110.4452133/post-86963931
Hi everyone, after hours of internet searches and scratching my head trying different methods over and over, I've decided to post here asking for help since I'm totally lost.
First of all, I got a bricked Oneplus 9 LE2110 (chinese model) that I'm trying to restore to any semblance of operation.
I've followed this FizzyAps tutorial https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
I got the drivers installed and MDM recognizes the device.
{
"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"
}
The first weird behavior I have is that whenever every 10 seconds or so, the device disconnects from the computer, then automatically reconnects again (I get the windows sound of a new usb device plugged in and out, and also the device is removed from the device manager and MSM).
Anyway, whenever I try to flash the phone with the configuration above, I get one of the following errors:
The dreaded "Sahara Communication Failed" If I just follow the tutorial to the letter.
If I hold volume UP+DOWN pressed at all times after connecting the phone, the error I get is different;
As a last resort, I tried using the Lite Firehose checkbox, but then it MSM prompts that the image does not match the device:
I was unable to find an image for LE2110 anywhere on the internet, but according to reports from other forum posts, the firmware I'm using (lemonade_22_O.07_210412.ops) should work.
Anyway, if anyone has a OEM LE2110 image that can be shared, it would be helpful.
Can anyone help me fix this issue?
Worth mentioning that I've tried multiple different USB ports, but I'm not using the OEM cable since my computer does not have a USB-C port, and the cable which came with the phone is USB-C on both ends. I'm using a high quality USB 3.1 cable instead.
Windows firewall and antivirus are disabled while trying to flash the phone.
About booting into EDL, the phone does not give any cue, as I just get an unlit black screen at all times, even when the device is recognized as QDLoader9008. I tried powering it off first by holding power for 15 seconds and even let the battery dry for a month, but when trying again the results were the same.
Replying to myself to confirm that this zip fixes the issue with the default configuration:
ONE PLUS 9 EU MSM TOOL TESTED
This was a Untested MSM .OPS file for the EU Variant use at your own risk. This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof. This will fail verification when pressing...
forum.xda-developers.com
Anyone with LE2110 don't use FizzyApps tutorial or files, please use this link instead.
GryphusR said:
Replying to myself to confirm that this zip fixes the issue with the default configuration:
ONE PLUS 9 EU MSM TOOL TESTED
This was a Untested MSM .OPS file for the EU Variant use at your own risk. This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof. This will fail verification when pressing...
forum.xda-developers.com
Anyone with LE2110 don't use FizzyApps tutorial or files, please use this link instead.
Click to expand...
Click to collapse
Interesting. Sounds like the tool posted there may be a universal MSM like the Indian 9 Pro's then because it shouldn't have worked for your device either if it was a Chinese variant.
EtherealRemnant said:
Interesting. Sounds like the tool posted there may be a universal MSM like the Indian 9 Pro's then because it shouldn't have worked for your device either if it was a Chinese variant.
Click to expand...
Click to collapse
I was also surprised because I got the phone bricked on the first place by trying to flash an EU ROM instead than the Global ROM. But since another person with a LE2110 said it worked, I decided to give it a try and indeed it worked at the first attempt.
On the original FizzyApps thread, someone said that LE2110 also work, but for whatever reason it does not. Being a Chinese variant it would not surprise me if there are different "revisions" of LE2110 model number, and perhaps some are incompatible with older versions of the FW
GryphusR said:
EDIT: Solution here https://forum.xda-developers.com/t/fixed-issue-with-msm-tool-on-le2110.4452133/post-86963931
Hi everyone, after hours of internet searches and scratching my head trying different methods over and over, I've decided to post here asking for help since I'm totally lost.
First of all, I got a bricked Oneplus 9 LE2110 (chinese model) that I'm trying to restore to any semblance of operation.
I've followed this FizzyAps tutorial https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
I got the drivers installed and MDM recognizes the device.
View attachment 5626537
View attachment 5626541
The first weird behavior I have is that whenever every 10 seconds or so, the device disconnects from the computer, then automatically reconnects again (I get the windows sound of a new usb device plugged in and out, and also the device is removed from the device manager and MSM).
Anyway, whenever I try to flash the phone with the configuration above, I get one of the following errors:
The dreaded "Sahara Communication Failed" If I just follow the tutorial to the letter.
View attachment 5626547
If I hold volume UP+DOWN pressed at all times after connecting the phone, the error I get is different;
View attachment 5626549
As a last resort, I tried using the Lite Firehose checkbox, but then it MSM prompts that the image does not match the device:
View attachment 5626551
I was unable to find an image for LE2110 anywhere on the internet, but according to reports from other forum posts, the firmware I'm using (lemonade_22_O.07_210412.ops) should work.
Anyway, if anyone has a OEM LE2110 image that can be shared, it would be helpful.
Can anyone help me fix this issue?
Worth mentioning that I've tried multiple different USB ports, but I'm not using the OEM cable since my computer does not have a USB-C port, and the cable which came with the phone is USB-C on both ends. I'm using a high quality USB 3.1 cable instead.
Windows firewall and antivirus are disabled while trying to flash the phone.
About booting into EDL, the phone does not give any cue, as I just get an unlit black screen at all times, even when the device is recognized as QDLoader9008. I tried powering it off first by holding power for 15 seconds and even let the battery dry for a month, but when trying again the results were the same.
Click to expand...
Click to collapse
It meant to have a black screen in edl mode, I got driver from op remote flash team & MSM tool which worked on op9 & pro version of global. Mine a le2110 too . I still had bugs after flashing global so the remote team flashed it with Chinese ROM & I flashed it back to oxygen using fizzys ROM , works great now but after updating OTA it says my device is a le2115 OP said that's normal , here's link m8 https://mega.nz/folder/wTZRkKyA#q146JvIeKkD2B6qnIN9F2Q
I had problem with driver because I got AMD CPU, always use original cable when flashing , I keep one for that , it's a signed driver as well
It worked one month ago, but I played with my phone again and this MSM tool doesnt work now even with the same cable (now im trying different cables) in the same port i used last time
it fails at Firehose GetUfsInfo but if i continue holding volume+, it will get to FirehoseCheckRSP Failed Errno 258
Hello Everyone.. here is the Instructions for OnePlus Nord CE 2-
Note:
backup Internal storage, contact message etc before process
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file.
1. Reading Firmware from Device
we download Require files USBDK Driver, Mediatek Driver & The Program
We Install both USBDK and Mediatek driver on our computer
disable windows defender and extract Program
Run Program
Select 'Firmware reader' Option and Mark The Full Firmware Option and Click 'Start Button'
{
"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"
}
turn Phone off, Press Volume up and down key and Insert USB
Reading Process Started. it will take around 15Min, once done we collect Firmware in Out Directory (it will Include nvram too)
unlocking bootloader:
there is a fastboot access issue on this device, you can try exploit method which is located Mediatek/service section...
bypass FRP lock:
From the very first Screen we Select FRP bypass Option and click 'START' Button
turn Phone off press volume up and down key and then insert usb
once done we disconnect device
Flashing Firmware:
we Go to Mediatek/Firmware Flashing Option
Select second Method 'write all partition' locate the firmware folder
click 'flash' button
turn phone off Press Volume up & down key and then inset usb
wait until success. done
Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?
trohn_javolta said:
Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?
Click to expand...
Click to collapse
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader
mark332 said:
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader
Click to expand...
Click to collapse
Turns out my work laptops antivirus instantly removed the .exe
Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.
trohn_javolta said:
Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.
Click to expand...
Click to collapse
The same story for me, the phone can't be put in preload or download mode or whatever they call it. I know one thing it is my last Oneplus phone if they're all going to be pain in the arse like this one. I guess it's back to my old 6t for another while then.
Accessing it by way of Recovery mode is also broken. To try it yourself, boot in to Recovery, connect your phone to your computer with usb-c cable. Multi-tap version number, it will eventually ask you if you want download mode and you click yes. It will attempt reboot into download mode, fail and then will `normal` boot phone.
trohn_javolta said:
Turns out my work laptops antivirus instantly removed the .exe
Click to expand...
Click to collapse
fixed a clean version + code available in public https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`
Quaicheist said:
Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`
Click to expand...
Click to collapse
connect in Proper way= install Latest usbdk and mtk driver, start process turn Phone off press volume up & down key and then Insert USB, once the Phone is detected release keys
Thanks for the info, though I have been doing that setup all along. I dual windoze and Linux. My windows is a custom minimal version of windows 10 with feck all on it. I upgraded this phone to stock 12 beta yesterday and ROM2Box for a wonder is happily doing a dump of that. It should be interesting when I downgrade to stock 11 and try to do a dump of that.
@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?
Quaicheist said:
@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?
Click to expand...
Click to collapse
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Hi @mark332, sorry I wasn't able to get to you sooner about this. Coredump was only possible with OxygenOS 12.1 beta, BROM was definitely locked down in 11. I succeeded with 12 but 'out' folder looks incomplete, files like ''preloader' which is in the beta package are missing from the dump. I don't think I would be able return to stock with ROM2box, maybe manually with fastboot commands.
Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.
Quaicheist said:
Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.
Click to expand...
Click to collapse
I'm just curious how did you downgrade?
mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Brom is enabled on A11 I've reflashed my device recovery partition when i was stuck
ko_hi said:
I'm just curious how did you downgrade?
Click to expand...
Click to collapse
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581
Quaicheist said:
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581
Click to expand...
Click to collapse
I guess if BROM mode works, use the bypass method to flash back to A11.v
Ah you see, the fecking phone managed to rollback to 11 but the touch screen driver is broken I guess. Physical buttons work but touch is broken. So I have contacted Oneplus tech support so we'll see what response I get tomorrow.