Testpoint Mate 10 PRO (BLA) - Huawei Mate 10 Guides, News, & Discussion

Hello
This Testpoint Mate 10 PRO ( model
BLA-AL00 BLA-L09 BLA-L29 BLA-A09

Looks like a testpoint!

Hello brother. if im not wrong this Phone using HiSilocon CPU... does it have TP too?.. if it does what tool will i use to flash ?
Best Regards

pretty much all huawei hisilicon devices have a testpoint somewhere, most are documented if not just connect the device and short the most likely points until you find it. as for the best tool its probably currently DCphoenix

HI all,
I have a bricked Mate 10 pro (yeah boohoo), but I think it might be fixed using testpoint method and DC phoenix. However I'm unfamiliar with how the testpoint proedure works and some guidance is much appreciated. I have opened my device, found the tespoint and soldered some wire to it so I can ground it easily. But... I don't know what to expect and what should (or shouldn't) happen.
Can someone please explain:
- first, do I need special drivers?
- at what point should I ground the testpoint:
- with or without batery connected?
- with or without USB cable connected?
- while powered off, while in fastboot mode or while in erecovery? Any other mode is not working on my device, so no system, just fastboot or erecovery
- should I just ground it briefly and then release or keep grounded during the whole process?
So far I haven't had any luck getting DC Phoenix to recognise the device as in forced upgrade mode. Any help is much appreciated, as the DC unlocker crew haven't offered any help at all...
Rgds,
David

Unbrick BLA-A09
Can a Huawei Mate 10 Pro BLA-A09 US version be unbricked by using the test point method? I looked everywhere but only found the method for other versions. May someone guide me to the right direction. I attempted to research through the DC unlocker site as some of the forums refer to this site but from what I can see it only shows the other versions to be compatible. I also need a guide on how to do this process and were to locate the needed files thanks.

pacoe said:
Can a Huawei Mate 10 Pro BLA-A09 US version be unbricked by using the test point method? I looked everywhere but only found the method for other versions. May someone guide me to the right direction. I attempted to research through the DC unlocker site as some of the forums refer to this site but from what I can see it only shows the other versions to be compatible. I also need a guide on how to do this process and were to locate the needed files thanks.
Click to expand...
Click to collapse
If DC Phoenix has the bootloader files required for A09, then sure. But I don't know if they do nor do I have an account to login to check.

Related

Bricked P20 Pro

Hi,
I really hope somebody can help. I've bricked my P20 Pro and looking for a solution...
Quick rundown of how I got here and relevant info:
Original model CLT-L09 8.1.0.103 (C782)
Rebranded with FunkyHuawei to CLT-L29
Was running firmware CLT-L29 8.1.0.110 (C782)
Updated to CLT-L29 8.1.0.120a (C432) using @Atarii 's method from this post https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085 (booted fine, no issues except wasn't passing safetynet and build number was messed up when viewed in settings) so I wasn't happy and decided to flash back to CLT-L29 8.1.0.110 (C782) using the same method.
When I issued the adb commands
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
I did so as 3 separate commands - pressing enter after each echo command, instead of copy/pasting the whole command as one.
Rebooted to recovery and the update was verified and started to flash but phone went blank mid-way through and hasn't powered on since. Device was at 96% battery when started flashing.
I now can't boot to fastboot, eRecovery, system, recovery... nothing.
I have successfully installed drivers so that when I connect the phone with USB it is recognized as HUAWEI USB COM 1.0 in device manager.
I do believe there is some way to recover from this. I have tried FunkyHuawei unbrick tool but that requires to be booted in fastboot. Tried DC Phoenix but the board software for P20 pro is not available.
If anyone knows anything that might help me out of this situation I'd be eternally grateful.
Thanks!
Currently, there is no way to recover. That might change in the future.
No commercial unbricking tools support the P20 Pro yet. Even if you were to find board software (for example Mate 10 board software is compatible enough to get you into fastboot, most likely) you won't be able to flash everything you need to, as the tools to do so aren't yet compatible.
I think your two choices are to wait until P20 support can be added to commercial unbricking tools, or to try having the device repaired/replaced under warranty, as it will be diagnosed as a hardware problem by Huawei (and it very well may be, if it just shut off without warning like that.)
I did exactly the same thing. Nothing working at all. Not even fastboot. Will the service center be able to fix this?
I can't offer any help here, but would like to know what might have caused this. Do you think it was because you attempted to downgrade the firmware?
I believe so. I was on 120 and tried to install 107 as 120 did not report model correctly
I've read somewhere here on XDA threads you can anything with your p20 pro but no downgrade at least for right now.
djlukas1983 said:
I've read somewhere here on XDA threads you can anything with your p20 pro but no downgrade at least for right now.
Click to expand...
Click to collapse
Probably going by this guy's experience!
Good Luck Original Poster!
FWIW and I know it's of no help but SafetyNet Test always fails with new f/w but usually it gets approved within a few days. When I upgraded from 103 to 110 it took 5 days.
have u fixed?? i have same problem it doesn't show any image but I have p20
Elizage2015 said:
have u fixed?? i have same problem it doesn't show any image but I have p20
Click to expand...
Click to collapse
He got it swayed out pal, if you've done the same thing I'd say so the same, if the device is powerless then it'll just get swapped out for a new one.
dladz said:
He got it swayed out pal, if you've done the same thing I'd say so the same, if the device is powerless then it'll just get swapped out for a new one.
Click to expand...
Click to collapse
is there any chance to power on device?? (
Elizage2015 said:
is there any chance to power on device?? (
Click to expand...
Click to collapse
I couldn't power mine on at all. As @duraaraa said unbricking tools aren't supporting P20 Pro yet. I took mine back to my provider and they replaced the main board after they couldn't fix it
Elizage2015 said:
is there any chance to power on device?? (
Click to expand...
Click to collapse
Just get it swapped, if you can't see the device neither can they, straight swap
No need to pay to anyone, finally solved. Try and let me know
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
My p20 pro was in Huawei usb 1.0 mode. With the dc-unlocker tool I got into fastboot and retrieved my phone.
MichelKastro said:
My p20 pro was in Huawei usb 1.0 mode. With the dc-unlocker tool I got into fastboot and retrieved my phone.
Click to expand...
Click to collapse
can you tell wich steps you followed to retrieve your phone?

[BRICKED] fastboot mode with black screen

So.. My Huawei P10 won't boot neither into system nor recovery, the screen is off and there's no LED indication.
It is recognized in fastboot, I can erase and flash both system and recovery, though rebooting the device does nothing, it just shows up in fastboot again, still with screen off.
Is there any way to save this phone? I installed a new battery too.
dc pheonix and hcu client did not help either.
:crying:
I have the same issue. Hard brick, doesnt turn on after I upgraded to oreo.
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
NowLearn said:
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
Click to expand...
Click to collapse
For adb it’s needed that the phone starts completely into system or twrp - both not possible for me.
With fastboot it’s not possible to flash eRecovery, just recovery.
Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
Yes, I tried the same, and also got the security patch warning, though little did I know I could get a refund. I did not try the 'test point' method. Not sure if I get it, do you connect/solder usb-cable onto the phone's motherboard?
You need to connect the test point to ground, you can use the shielding right beside of it. Take a small wire or tweezers for it.
I did it like this:
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
DC should work now. But if it doesn’t, write it in the dc forums and you’ll get refund
Huawei P10 Successfully Recovered from Fastboot black screen on latest Security 9.
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
chsaim said:
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
Click to expand...
Click to collapse
Can you explain exactly how?
Jannomag said:
Can you explain exactly how?[/QUOTE
you need to know exactly build number and flash latest firmware according to build number with chimera tool.
make sure that phone is in fastboot mode... am sorry if i cant explained well ... for more details write me at [email protected]
Click to expand...
Click to collapse
Yes, please share some information how can we recover our dead p10. It would greatly help the community. Thank you
I tried it with DC and Chimera. Both aren't working for me, because of the security patches. Huawei did some deep changes between October and December 2018 and made it very hard to flash even with test points - another reason for me to leave Huawei to my alltime smartphone enemy Samsung...
The DC-Phoenix and Chimera teams are working hard on a solution, take a look at their forums and you'll notice that many people have this problems, just because Huawei ****ed it up.
I mean, we did all something wrong, otherwise this threat won't exist. But Huawei made it hard for us to revive the devices and this reminds me of Apples politics. Huawei doesn't need to give support to unlocked phones but it's very unfair to prevent their customers from doing what they want including unlocking.
Back to topic:
Follow the forums of DC and Chimera. If you found any solution or fix, please post it here.
My device, also bricked while flashing the wrong firmware for rolling back from pie, shows just black screen and fastboot is working.
Test point didn't work, also Chimera couldn't flash anything.
My device gets quiet warm while in fastboot, so I disconnected the battery to prevent deep discharging.
Dear the same situation was happened with my p10 but i recovered... So if you want to recover your phone then give ultra view id and pass....... If you have chimera and dc phoenix you can make it possible.. But remember you must need to know exactly build number
If any one needs my help here is my WhatsApp contact me anytime... +923007969629
If you can share the steps. It would help the community thank you @chsaim
Yes, please share the steps to help the community.
Thanks!
There's absolutely no reason for not sharing the steps in a simple tutorial. Instead @chsaim is begging for remote access to our computers, I don't know why.
I chatted a lot with Chimera support and they told me that there's currently not way to recover, with faulty partitions caused by flashing, with the Dec.2018 security patches and newer. This included the firmware 382, on some 380 devices it doesn't work either.
They also want to send me an E-Mail when they find a solution for this. For now I got my money back from them - great support, also the DC team.
I'm happy to get a used mainboard from local market and now have my P10 as spare phone.
yeap.same **** again with Huawei phones.ı want to try pie rom and when ı try rollback oreo phones turn off and not open again.this is not like a other hard or soft brick problem because I have a experiance about other problems.phone cant charge or pc can't see the device ı cant see red led too.just dead.ı use this phone 2 years but never buying huawei again neverrrr.anybody found a solition ?
Jannomag said:
You need to connect the test point to ground...
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
...
Click to expand...
Click to collapse
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
I can access fastboot with dc-phoenix. Once I tried to send erecovery, recovery, or kernel w
Through cmd. It reads but it can't write. That's where I get stuck. If dc it's able to write then I would be able to recover my dead phone. Thank you
lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
Test point needs to be shorted until the computer recognizes the P10 as an USB serial device. You need drivers for this, which you can get from DC Phoenix.
DC couldn't flash the bootloader:
Code:
BOOTLOADER File to update: Kirin960_T0_A7.0_V1
20.02.2019 21:34:26 Starting to write device...
Writing bootloader...
Error writing Bootloader
20.02.2019 21:35:36 Writing device finished - INCOMPLETE

Mate 10 pro testpoint guidance (bricked)

Hi all,
I have a bricked Mate 10 pro (yeah boohoo), but I think it might be fixed using testpoint method and DC phoenix. However I'm unfamiliar with how the testpoint proedure works and some guidance is much appreciated. I have opened my device, found the tespoint and soldered some wire to it so I can ground it easily. But... I don't know what to expect and what should (or shouldn't) happen.
Can someone please explain:
- first, do I need special drivers?
- at what point should I ground the testpoint:
- with or without batery connected?
- with or without USB cable connected?
- while powered off, while in fastboot mode or while in erecovery? Any other mode is not working on my device, so no system, just fastboot or erecovery
- should I just ground it briefly and then release or keep grounded during the whole process?
So far I haven't had any luck getting DC Phoenix to recognise the device as in forced upgrade mode. Any help is much appreciated, as the DC unlocker crew haven't offered any help at all...
Rgds,
David

I want to unbrick mi9 wiht testpoint to edl mode.

I want to unbrick mi9 wiht testpoint to edl mode.
Where i can find for mi 9 testpoint?
Testpoint Mi 9 by PiLyTam is not working.
khlaikran said:
I want to unbrick mi9 wiht testpoint to edl mode.
Where i can find for mi 9 testpoint?
Testpoint Mi 9 by PiLyTam is not working.
Click to expand...
Click to collapse
You don't need that.
I unbricked mine with the Mitool Pro from bootloader locked and "system has been destroyed"
PRolo said:
You don't need that.
I unbricked mine with the Mitool Pro from bootloader locked and "system has been destroyed"
Click to expand...
Click to collapse
If you know such a method, please open a topic and create a guideline, will be beneficial for more users in such situation!
I'll try to make it tonight.
Sent from my MI 9 using XDA Labs
PRolo said:
You don't need that.
I unbricked mine with the Mitool Pro from bootloader locked and "system has been destroyed"
Click to expand...
Click to collapse
What did you do it?
khlaikran said:
What did you do it?
Click to expand...
Click to collapse
I've published the tread that i've promissed to you.
Sent from my MI 9 using XDA Labs
If you know about the testpoint pin or edl mode, i guess you are in big trouble and doing a lot of research about it now or even talked to those guys who can remote in to your pc and unbrick your device using TeamViewer
My advice is dont waste your time, just find a way to send it back to China to get it fix.
Nobody have any clues about this testpoint pin and PiLyTam is BS, testpoint pin on all other Xiaomi model will be close together, HTF that this model can be so far away that you cant even use tweezer to short it?
BTW, if your phone is in below condition, not just one but all combined. Trust me, dont waste your time
- your phone is in bootloop and your phone have no OS installed because you have already delete it with TWRP
- bootloader is locked
- you have using that sh1tty xiaomi flashtool and haven't noticed that "flash and lock" was selected by default
Oh and by the way, welcome to the sh1tty group of being xiaomi's customers, dont get me wrong the phone is great but if you are not in China and using "grey products" you are on your own
tawa2525 said:
If you know about the testpoint pin or edl mode, i guess you are in big trouble and doing a lot of research about it now or even talked to those guys who can remote in to your pc and unbrick your device using TeamViewer
My advice is dont waste your time, just find a way to send it back to China to get it fix.
Nobody have any clues about this testpoint pin and PiLyTam is BS, testpoint pin on all other Xiaomi model will be close together, HTF that this model can be so far away that you cant even use tweezer to short it?
BTW, if your phone is in below condition, not just one but all combined. Trust me, dont waste your time
- your phone is in bootloop and your phone have no OS installed because you have already delete it with TWRP
- bootloader is locked
- you have using that sh1tty xiaomi flashtool and haven't noticed that "flash and lock" was selected by default
Oh and by the way, welcome to the sh1tty group of being xiaomi's customers, dont get me wrong the phone is great but if you are not in China and using "grey products" you are on your own
Click to expand...
Click to collapse
Hey boy!
I think i can help you without send mi 9 back to china. But i want you have one acc xiaomi authorized.
Ib for me now.
Possibly Wrong Pins
I believe the pins are the wrong pins. I've been trying different methods of entering EDL mode on my own bricked Mi 9 (locked bootloader + the system is destroyed) and cannot enter EDL mode no matter what I try. Has anyone been successful?
PRolo said:
I've published the tread that i've promissed to you.
Sent from my MI 9 using XDA Labs
Click to expand...
Click to collapse
I'm not bricked, but can you provide a link to your guide - may help others find it!
cheers
EDIT: his thread is here
mode1 said:
I believe the pins are the wrong pins. I've been trying different methods of entering EDL mode on my own bricked Mi 9 (locked bootloader + the system is destroyed) and cannot enter EDL mode no matter what I try. Has anyone been successful?
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=943335&st=1380#entry84949424
Have a look here for test point. You will need to read it properly saying something about serious problems later. Not sure if he is talking about the battery or the cable that hides the pins to be disconnected.
Clarkie_955i said:
http://4pda.ru/forum/index.php?showtopic=943335&st=1380#entry84949424
Have a look here for test point. You will need to read it properly saying something about serious problems later. Not sure if he is talking about the battery or the cable that hides the pins to be disconnected.
Click to expand...
Click to collapse
**Continue at your own risk**
You'll have to detach battery cable first before attempting to circuit the 2 testpoints as shown on the picture. Don't forget !
In order to reach the 2 points you'll have to disconnect the ribbon cable as shown in the video. Then connect the 2 points (with a clip or anything that can connect both) and reconnect the ribbon cable again (keep holding the 2 points).
That would be it
MI9-testpoint vid
thnx hell3x / 4pda
raystef66 said:
**Continue at your own risk**
You'll have to detach battery cable first before attempting to circuit the 2 testpoints as shown on the picture. Don't forget !
In order to reach the 2 points you'll have to disconnect the ribbon cable as shown in the video. Then connect the 2 points (with a clip or anything that can connect both) and reconnect the ribbon cable again (keep holding the 2 points).
That would be it
MI9-testpoint vid
thnx hell3x / 4pda
Click to expand...
Click to collapse
Thanks for the info and the video. Couldn't get the video to work not a member on 4pda
Clarkie_955i said:
Thanks for the info and the video. Couldn't get the video to work not a member on 4pda
Click to expand...
Click to collapse
The video is now on youtube watch?v=IaibckV1E2s (I can't post links yet). I've tried to do this but still couldn't get it to work though. Does anyone have any suggestions?
hello
i have same problem like you..no soultion a this moment. i wait like you some help
is there anyone have the Mi9 EDL auth account ? i really need that badly. so i can flash the correct rom.....
@b0ltun
Contact with him via telegram app

Sigma Key for Kirin 990 5G for real? rooting next?

I am wondering if i buy the sigma key for huawei.
I i manage to unlock the bootloader.
(ref: https://gsmserver.com/sigma-pack-3-...urce=dfp&utm_medium=banner&utm_content=728x90)
What are the odds for me to flash boot with twrp / Magisk manager?
Would be nice to get an answer to that before buying this for 129USD.
Anyone have any input?
My main reason for this is to get device certified i playstore and make the cts profile "true" to make gpay working for this phone. (i did this for the mate 20 pro when i rooted that)
So , if sigmakey unlocks bootloader will this theory work?
Wil be happy for inputs from the community an people that know filesystems, boot images, twrp, and rooting...
(i have seen 2 videos online with the "unlocked warning boot screen" that comes up when rooted on a P40 Pro so someone has done it)
regards, Kenneth - Norway
Why don't you ask the seller?
dasklney said:
Why don't you ask the seller?
Click to expand...
Click to collapse
Tried
Did you buy it already and if so are you willing to help me for a humble compensation of course. I have kirin 990 on Huawei p40 5g and i totally bricked it so my only chance lies in Sigmakey and USB (no ADB detects the device, only USB COM 1.0 succesfull, but no connection to push files or boot etc.) Also, are you familiar enough how we should proceed IF you can of course!
First at all.... Do you have the box or dongle?
rrzrbg said:
First at all.... Do you have the box or dongle?
Click to expand...
Click to collapse
well we dont need it for this as it can be done remotely only through USB! However I found a guy who did this already and its unbricked! thanks anyways - just so you know - not everytime you need BOX
bootloader unlock only via usb? very nice....
SInce EMUI10 Huawei closed all Unlock Bootloader You can't find oem unlock menu in the Developer page, so its impossible to UBL using sigmakey
Leaving Huawei for oneplus. I am sick of this ****
fromiOS2Android said:
Leaving Huawei for oneplus. I am sick of this ****
Click to expand...
Click to collapse
Well unfortunately I left OnePlus for Huawei... My OnePlus died and the new one costs 1000 bucks - no thanks - not the OnePlus that it used to be They were the best, but this price range... **** this
firlando said:
SInce EMUI10 Huawei closed all Unlock Bootloader You can't find oem unlock menu in the Developer page, so its impossible to UBL using sigmakey
Click to expand...
Click to collapse
Dunno how that guy did it, but on his video it shows:
danielEMZ said:
Dunno how that guy did it, but on his video it shows:
Click to expand...
Click to collapse
yes, this phone demo unit directly from Huawei for Review/Media purpose only.

Categories

Resources