Soft Brick/Bootloop Fix Solutions? - Huawei P20 Pro Questions & Answers

Good day all. Long time lurker of these forums, and I am officially throwing in the towel on my amateur attempts to update my P20 Pro (CLT-L29 C636) from Android 8 to something newer. I've managed to soft brick the thing, getting stuck in a boot loop. I can get to fastboot, and I can (sometimes) get it to enter dload mode with an OTG cable and a thumb drive. I messed something up early on in the process and I am completely unable to go any further. Dload gets to 5% then fails every time, with every thumb drive I've used.
I am willing to accept that I just don't have the technical ability to take this journey any further. Being that I live in the US (Western New York), Huawei lists no official repair centers in the states. Are there any trusted 3rd party repair services I could send my phone to and have an expert attempt to repair the software? At this point it's been bootlooping so long the Huawei logo is ghosted onto the AMOLED screen. I would love to have this phone operational again.
Any thoughts I would greatly appreciate it!

Hold Both Vol + Power until Emergency Rescue pops up.
After that, restore Stock, unlock Bootloader, install any android 10/11/12 GSI u want.

Tried that. It's stuck in bootloop and only occasionally responds to boot prompts. On the couple of times it got past dload failed and prompted me with invalid install and offered to boot to Emergency Recovery, it fails to load the recovery dialog and drops back into a boot loop.
I promise, I have been back and forth with attempts on this phone for four months, and if I thought there was any new surface level tip or trick I haven't tried, I would still be searching. I feel like it's at a point where only specialized software or a physical test point, or something else beyond my technical ability will fix this phone.
I do appreciate the suggestion, though.

Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?

aLcaTr4z said:
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
Click to expand...
Click to collapse
Sorry if I sent the wrong impression. The bootloader is still locked. It is only carrier unlocked.
I can locate it on DC-Unlocker on fastboot but it won't let me load any files to it.

With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?

aLcaTr4z said:
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
Click to expand...
Click to collapse
Oh yeah. HiSuite recovery states that this model isn't compatible with eRecovery and to take the phone to a service center.

Related

Bricked Huawei P10 phone by wiping system. Desperate to put Stock on it. (help :()

Dear All!
Here is one desperate guy turning to you because I see from some XDA posts, that you know about twrp and Huawei devices quite something.
At first, I don't want to waste your time. If you can help me, I will be happy to compensate it because I'm quite serious on this (and desperate as well).
I'm a beginner on Android rooting world, and in a nutshell, I enjoy just putting my Android device to the limits and enjoy using them to the fullest.
Bad thing, that I sometimes take too much risk and this time it ended with a (Soft) bricked phone.
The phone is from a rental company, that is why I'm so stressed to get it back and going.
So getting to the point:
Device: Huawei P10, VTR-L29C432B123
(C432, as I understand, is European version and it's important here)
Current state: Device is unlocked, rooted and with TWRP 3.1.1. (TWRP installed by this post https://forum.xda-developers.com/p10/development/testers-twrp-t3585256 and rooted by this post https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946)
After installing TWRP and Rooting device I happily enjoyed using it for some time but
things went wrong when I started to try to put back Stock rom. (+ unroot and lock the device as well).
I tried multiple posts on the internet and didn't succeed. Unfortunately, FLashify and alike apps didn't work (or crashed after installing) on my P10, therefore, I turned to TWRP.
At first, I tried to install stock firmware downloaded from Firmware Finder but TWRP put out error:
E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip '/external_sd/dload-draft/update.zip
Then I tried some other ways and turned to wipe section. Deleted Catches and data and then also system. This I believe f-ed things up and (of course) I could not boot anymore.
Can you instruct me on installing Stock rom for my device and get it back and running?
Thank you very much and please let me know if some more info is necessary!
@paratox @OldDroid @XePeleato @Dejan Kruljac Guys, if you could take a look on this and give me a direction - I would be enormously thankful!
As you found out Huaweis work a little different. I used this to rebrand my P10: https://forum.xda-developers.com/showpost.php?p=72140996&postcount=10
I guess you can also use it to debrick your phone.
M1chiel said:
As you found out Huaweis work a little different. I used this to rebrand my P10: https://forum.xda-developers.com/showpost.php?p=72140996&postcount=10
I guess you can also use it to debrick your phone.
Click to expand...
Click to collapse
What does it mean to debrand a device?
It helped. Jeezh
M1chiel said:
As you found out Huaweis work a little different. I used this to rebrand my P10: https://forum.xda-developers.com/showpost.php?p=72140996&postcount=10
I guess you can also use it to debrick your phone.
Click to expand...
Click to collapse
I'm shocked! Please take this as a complement but you are one sick mother****er. I can not believe how easy it was. It's like I pressed 'Enter' couple of times and that's it. Wow!
Man I owe you. How can I say thanks? How can I support work that you are doing? The way of how this tutorial was made make me want to be a better person and help others more. Huge thank you
Jaunpetrovics said:
I'm shocked! Please take this as a complement but you are one sick mother****er. I can not believe how easy it was. It's like I pressed 'Enter' couple of times and that's it. Wow!
Man I owe you. How can I say thanks? How can I support work that you are doing? The way of how this tutorial was made make me want to be a better person and help others more. Huge thank you
Click to expand...
Click to collapse
You are welcome, but actually you must thank @crucky and @mankindtw !
I recently got the P10 after two Sony devices and a Samsung, so it was confusing for me as well. I am happy it worked for you .
Debranding is installing a rom for another region, another carrier or a change from dual to single sim (or the other way around).
M1chiel said:
You are welcome, but actually you must thank @crucky and @mankindtw !
I recently got the P10 after two Sony devices and a Samsung, so it was confusing for me as well. I am happy it worked for you .
Debranding is installing a rom for another region, another carrier or a change from dual to single sim (or the other way around).
Click to expand...
Click to collapse
He's right. My P10 had no os installed no recovery and the huawei e recovery wasnt working, this thing will fix the most bricked of phones. 10/10 would brick again. :good:
Would my phone work ?
M1chiel said:
As you found out Huaweis work a little different. I used this to rebrand my P10: https://forum.xda-developers.com/showpost.php?p=72140996&postcount=10
I guess you can also use it to debrick your phone.
Click to expand...
Click to collapse
edit : I have relocked my bootloader which leaves me no TWRP
Would this also work for me (VTR-L09)
I bought the phone from Vodafone Australia and I am stuck in erecovery right now, when I try to update through the dload using a FAT32 sd card the update.app won't even copy onto the sd card as it is larger than 4GB. When I try to do it using an sd card formatted to NTFS it stops at 5% and states "software install failed!"
Please help me on what to do... any help would be appreciated
Huawei P20 lite dead
Guys please help me aswell
One day not long ago a did a hard reset on my Huawei P20 Lite to free up some space and delete junk files while the device was resetting without me even noticing i accidentilly held the power button and the device died.
But currently i'm getting the green screen with the red and blue blocks inside it.
The phone does not boot at all it only glich the green screen for about half a second when i press and hold the power button. I did the FASTBOOT&RESCUE MODE thing but dont know anything else and ow yes on fastboot mode it says PHONE LOCKED
PLEASE HELP ME
YulmarRSA said:
Guys please help me aswell
One day not long ago a did a hard reset on my Huawei P20 Lite to free up some space and delete junk files while the device was resetting without me even noticing i accidentilly held the power button and the device died.
But currently i'm getting the green screen with the red and blue blocks inside it.
The phone does not boot at all it only glich the green screen for about half a second when i press and hold the power button. I did the FASTBOOT&RESCUE MODE thing but dont know anything else and ow yes on fastboot mode it says PHONE LOCKED
PLEASE HELP ME
Click to expand...
Click to collapse
I can assume that your memory is out of order.
I understood correctly, when you turn on the cubes? You did not flash board firmware?

Stuck on honor logo

Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
iantechie1979 said:
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
iantechie1979 said:
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Flash these files and it should, most probably, be fine.
use dload method as given here- https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
as there are many different opinions on this method of using only update.app file but thats not true and it should be all the files.
Main file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v71812/f1/full/update.zip
Data file- http://update.hicloud.com:8180/TDS/...1812/f1/full/hw/eu/update_data_full_hw_eu.zip
Flash both the files in order. 1st file will restore your system but then you need to have 2nd file so that apps are installed and all working fine.
After 1st file, it may reboot on its own and stuck on honor logo, reboot to recovery and then do factory reset, it will be fine.
Then let it boot to set up. Dont set your phone. Shutdown and flash the 2nd file.
boot and set up.
Good luck. Please provide feedback once done. In case of further issue, let me know and will dig more into this.
Oh this is hard.
chrisleLP said:
Oh this is hard.
Click to expand...
Click to collapse
What is hard?
shashank1320 said:
What is hard?
Click to expand...
Click to collapse
This problem.
chrisleLP said:
This problem.
Click to expand...
Click to collapse
you cant follow simple instructions? you shouldnt be on this forum if youre not ready to lose data or brick your device.
Thanks for your input so far people. Much appreciated. @shashank1320 I am downloading the files you suggested and will flash them exactly according to your instructions. I will get back to you in a couple of days with the result. Fingers crossed.
gopinaidu77 said:
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
Click to expand...
Click to collapse
Unfortunately my warranty has expired. The annoying thing is that if i had sent my device off six months ago when this first happened it would still be under warranty but in the UK there is only 1 service center, yes 1, and its hundreds of miles away! So i figured i could solve it myself. You live and learn.
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
iantechie1979 said:
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
Click to expand...
Click to collapse
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
shashank1320 said:
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
Click to expand...
Click to collapse
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
iantechie1979 said:
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
Click to expand...
Click to collapse
Did you flash those files i given? If not can try. Else i will have to look for other alternative
yeah i downloaded those files you had mentioned in your post and followed the instructions to the letter.
I've got a suggestion if you have tried all these above.
Can you try the following on ADB and then try to unlock OEM again.
fastboot oem relock YourUnlockCode
I've done the same and it helped, even when bootloader displayed UNLOCKED. Please try it. :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
NameNotFound74 said:
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
Click to expand...
Click to collapse
Try unlocking the bootloader again even if it is unlocked. It will factory reset the device and it should boot fine. Have stuck on this many a time and this was the method i followed.

[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

Phone bricked, won't turn on. Help please!

Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.
Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)

Question Bricked OP 10 Pro - Help

Hello All,
I managed to brick my OP 10 Pro
It happened when I locked the bootloader before uninstalling Magisk.
I am now in a forever bootloop, see video:
Your browser is not able to display this video.
It will not boot into fastboot for love nor money.
There is no time for adb to load into fastboot as it is constantly resetting.
If I hold all three buttons when it is not connected to anything, it does nothing.
If I hold all three buttons while the phone is connected to the computer, it goes into EDL mode and Qualcomm drivers appear in the device manager, but it still fails to shows as 'adb devices' or 'fastboot devices'
I dont know what to do.
Help :-/
Lynxy0 said:
Hello All,
I managed to brick my OP 10 Pro
It happened when I locked the bootloader before uninstalling Magisk.
I am now in a forever bootloop, see video:
View attachment 5586583
It will not boot into fastboot for love nor money.
There is no time for adb to load into fastboot as it is constantly resetting.
If I hold all three buttons when it is not connected to anything, it does nothing.
If I hold all three buttons while the phone is connected to the computer, it goes into EDL mode and Qualcomm drivers appear in the device manager, but it still fails to shows as 'adb devices' or 'fastboot devices'
I dont know what to do.
Help :-/
Click to expand...
Click to collapse
Need msm
Theres no msm tool yet you have to wait for it
Is there anyone that had a look on Baido ?I tried everything under the sun.
I downloaded this from mega which has the full firmware files
https://mega.nz/folder/vMYSxBgI#LJXkyX-Ue9a4iFZPQmc80w
The closest I got was downloading the QFIL to flash it in EDL mode, but I couldnt get it to work...
I once took a bricked OP6 (hardly a month old) to service center. They fixed it, no questions asked.
I guess times are tough. GSMMAFIA steals OP software and sells it to you.
g96818 said:
I guess times are tough. GSMMAFIA steals OP software and sells it to you.
Click to expand...
Click to collapse
Considering there's a thred in this forum exactly for that...
The same thing happened to me on my NE2215...
Told OPO support it was the latest update that did it.. they are offering to repair it, still under warranty, for free.
from what I hear it can take 3weeks to 3 months to get it back.
Need a MSM tool
How I happened to me...
i wanted to get the latest OTA, so I removed Magisk, changes boo.img back to stock, reset the phone, and then when to turn flashing off (lock the bootloader)
on the rest step of Locking the bootloader back, is when it looped into this as well....
I know this isnt helpful right now, but NEVER re-lock your bootloader. I've seen far too many people brick their ****. Why unlock it to begin with? When you relock the bootloader, anything that's not signed will not boot. I hope you get your phone fixed. Good luck to you bud
can you please tell me your mobile after hard brick have a pc connection ? beacause my phone also bricked and totally terned off no button combination no charging no pc connection
<Moderator Edit>: Quote removed since post deleted.
lordxcom said:
The same thing happened to me on my NE2215...
Told OPO support it was the latest update that did it.. they are offering to repair it, still under warranty, for free.
from what I hear it can take 3weeks to 3 months to get it back.
Need a MSM tool
How I happened to me...
i wanted to get the latest OTA, so I removed Magisk, changes boo.img back to stock, reset the phone, and then when to turn flashing off (lock the bootloader)
on the rest step of Locking the bootloader back, is when it looped into this as well....
Click to expand...
Click to collapse
Why did you try a super complicated route to update? There is no need to do reboot or lock your bootloader after restoring (not removing) magisk in order to do the ota update.
g96818 said:
Why did you try a super complicated route to update? There is no need to do reboot or lock your bootloader after restoring (not removing) magisk in order to do the ota update.
Click to expand...
Click to collapse
i took the old approach it appears... what is the new way to roll ?
lordxcom said:
i took the old approach it appears... what is the new way to roll ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
Eventually, I took out insurance on the phone and a week later I said its not working. Insurance support werent very technical and they replaced my phone after a week. Alernatively, I could of sent it off to OP...
i bricked my op10p same way like you... i went to store where i bought it and they sent it to repair after that i got info that they switched motherboard from it
File Unbrick : https://drive.google.com/file/d/1Hmu1SFF9N3fzIczg9L1WjBGwNEjTa0y7/view?usp=sharing
Mod Edit: YouTube Video Link Removed
maison1989 said:
File Unbrick : https://drive.google.com/file/d/1Hmu1SFF9N3fzIczg9L1WjBGwNEjTa0y7/view?usp=sharing
Video
Mod Edit: YouTube Video Link Removed
Click to expand...
Click to collapse
a complaint. Submit your login information.
El mismo problema aquí, ¿has logrado resolverlo?
Same problem here can you help me please
kurador911 said:
El mismo problema aquí, ¿has logrado resolverlo?
Same problem here can you help me please
Click to expand...
Click to collapse
Best solution: throw your phone in trash, also boycott OppoPlus and don't buy from BugPlus anymore
F*ck OnePlus !!
Everyone listen to the google logo user. Oppo is hostile to rom developers and releases broken source code and restricts msm. They're just the apple of android products nowadays

Categories

Resources