[Discussion] Hard-Brick Infos - Huawei Mate 10 Guides, News, & Discussion

Warning !!!​ALP-L29 C636 users should avoid updating or rebranding to ALP-L29C636B134 firmware, dated 16/04.And if they already updated, to stay on that firmware (at least for now).
BLA-L29 C636 users should avoid updating or rebranding to BLA-L29C636B137 firmware, dated 16/04.And if they already updated, to stay on that firmware (at least for now).
Please also read this thread made by @ante0 - >https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 <- you will also find a tool that will help you check the xloader.img
Considering that lately there were quite a few hard-bricks, i invite the users that experienced such bricks to post more details here.
Please use this model when you post :
1) Device = device codename (BLA-L29, ALP-L29, etc)
2) Firmware and Region before Brick = exact firmware and region (B134 C636, B141 C432)
3) Firmware that lead to brick = The firmware version that lead to bricking
4) You were trying to just update your device or you were also trying to rebrand
5) Your device was rebranded or used stock region?
6) Other infos of modifications, update procedures, etc that you did before bricking
Thank you and please stay on topic!

ALP29-C636 on B129 (I believe). Just wanted to update to B134 (non-noxloader) and get face unlock. No rebranding. Tried it with HurUpdater first (which I had never used before). Had TWRP 0.3 installed and included it as a recovery.img when flashing. Ended up in a boot loop, so I turned off and entered download mode and went back to mankindtw's tools. But, thinking maybe something was wrong with my B134 download, I downloaded and repacked B134 noxloader this time around. The update all went well, including exiting out of the final CMD window, but then, in the automatic reboot, the phone just died.

1) ALP-L29
2) Worked just fine with ALP-L29C636B134
3) ALP-L29C636B135
4) update with HWOTA8_Mate10
5) Original ALP-AL00C00 rebranded to ALP-L29
6) nothing else
But I do remember one strange thing, when I updated to ALP-L29C636B134. The zip files I downloaded from hicloud, the repack.bat told me they already were repacked even though I did not do it, yet it updated just fine.
Then the ALP-L29C636B135 zips repacked as usual, and after that I updated with ota.bat and it bricked.

erzbengel said:
1) ALP-L29
2) Worked just fine with ALP-L29C636B134
3) ALP-L29C636B135
4) update with HWOTA8_Mate10
5) Original ALP-AL00C00 rebranded to ALP-L29
6) nothing else
But I do remember one strange thing, when I updated to ALP-L29C636B134. The zip files I downloaded from hicloud, the repack.bat told me they already were repacked even though I did not do it, yet it updated just fine.
Then the ALP-L29C636B135 zips repacked as usual, and after that I updated with ota.bat and it bricked.
Click to expand...
Click to collapse
134 with or without the noxloader version attached to the name??

royhanks3 said:
134 with or without the noxloader version attached to the name??
Click to expand...
Click to collapse
Without the noxloader.

erzbengel said:
Without the noxloader.
Click to expand...
Click to collapse
When I flashed 135 without repacking it flashed fine. Maybe there's an issue with repacking the latest roms and flashing then on our devices
Sent from my ALP-L29 using Tapatalk

) Device = ALPL29
2) Firmware C636B134
3) Firmware that lead to brick C636B134 NO XLOADER
4) Just trying to update wanted to see what the difference was
5) Stock region
6) Just followed HWOTA10 instructions repacked install complete 100% then it rebooted then it took me to the black screen
I sent it back to huawei and they gave me a brand new device but this time i will just be installing magisk

1) Device = BLA-L29
2) Firmware and Region before Brick = B137 C636
3) Firmware that lead to brick = B141 noxloader C432
4) Rebrand
5) My device was rebranded from stock BLA-L09 C34 to L29 C636
6) Just follow HWOTA8's guide. The process was no problem. But after reboot, my phone turned to black screen. It was totally dead.

1- device= bla-l29
2- c636 137
3- i use 2 weak c636 137 i use hwota update to 138 and now brick
4- rebrand and update only hwota for mate 10
5- my orjinal phone bla-al00
6- only use hwota update c636 138 and now brick my phone. Now my phone Black Scren and pc device manager see usb ser.
I use dc phonix al00 board software but not install bootloader.
http://www.imgim.com/68incib2496565.jpg

ooemir said:
1- device= bla-l29
2- c636 137
3- i use 2 weak c636 137 i use hwota update to 138 and now brick
4- rebrand and update only hwota for mate 10
5- my orjinal phone bla-al00
6- only use hwota update c636 138 and now brick my phone. Now my phone Black Scren and pc device manager see usb ser.
I use dc phonix al00 board software but not install bootloader.
http://www.imgim.com/68incib2496565.jpg
Click to expand...
Click to collapse
DC Phoenix or HDE Flasher is used to flash the Board Firmware. But in the case of mate 10 with latest firmware bricked phones, DC Phoenix and HDE Flasher are not capable to flash the Board Firmware even the phone is detected as HUAWEI USB COM 1.0 . So for all those who are trying to install the latest and pre-release builds should avoid this to let their phones alive.
PS: The developers should look into the latest firmware what is causing hard bricks.
Regards

k4fari said:
DC Phoenix or HDE Flasher is used to flash the Board Firmware. But in the case of mate 10 with latest firmware bricked phones, DC Phoenix and HDE Flasher are not capable to flash the Board Firmware even the phone is detected as HUAWEI USB COM 1.0 . So for all those who are trying to install the latest and pre-release builds should avoid this to let their phones alive.
PS: The developers should look into the latest firmware what is causing hard bricks.
Regards
Click to expand...
Click to collapse
This means that Phoenix can't use its "backdoor" anymore.

When phone is bricked DC flashes in factory mode (USB COM 1.0) while backdoor is used in fastboot mode.

k4fari said:
When phone is bricked DC flashes in factory mode (USB COM 1.0) while backdoor is used in fastboot mode.
Click to expand...
Click to collapse
This means USB COM 1.0 is useless without actually connecting the test points, which unfortunately are not available for Mate 10.

1- bla-l29
2- c636 142
3- /////////c432 142///////////
4- update packing instally %50 closed on screen
5- my orjinal phone bla-l29 so rebrand
6- device manager see usb ser.

Pretoriano80 said:
This means USB COM 1.0 is useless without actually connecting the test points, which unfortunately are not available for Mate 10.
Click to expand...
Click to collapse
No, you are not getting the point. The hard bricked phones having no connectivity with Pc need test points, i.e to detect phone as Huawei USB Com 1.0 known as Factory Mode.
HUAWEI Phones have 3 flashing modes: i.e., 1)Fastboot mode, 2) Upgrade Mode (by pressing vol +, vol- and pluging in usb cable), and 3) Factory Mode (Usb Com 1.0).
To flash board firmware phone must be detected in any of three modes . The phone which is already detected and visible as USB SER in Pc doesn't need any test points. USB SER drivers are available to put phone in USB Com 1.0 (factory mode).
The main issue is flashing board firmware as new firmware installation via HWOTA or other HrUpdater are hard bricking the phones. Even though the phone is detect-able as Factory Mode without disassembly and test points , DC Phoenix is unable to flash board firmware.
Hope many things and points are now clear to many of the readers.

did anyone solve the black screen problem ? (hard bric)
how long will we wait

ooemir said:
did anyone solve the black screen problem ? (hard bric)
how long will we wait
Click to expand...
Click to collapse
In all honesty, I do not think we'll be able to solve this issue on our own. The latest updates are seemingly removing the bootloader, or access to it which means we currently don't have the necessary tools to flash board software to the device. More people need to either complain or contact Huawei so we can all get this solved as a community.
Sent from my ALP-L29 using Tapatalk

k4fari said:
No, you are not getting the point. The hard bricked phones having no connectivity with Pc need test points, i.e to detect phone as Huawei USB Com 1.0 known as Factory Mode.
HUAWEI Phones have 3 flashing modes: i.e., 1)Fastboot mode, 2) Upgrade Mode (by pressing vol +, vol- and pluging in usb cable), and 3) Factory Mode (Usb Com 1.0).
To flash board firmware phone must be detected in any of three modes . The phone which is already detected and visible as USB SER in Pc doesn't need any test points. USB SER drivers are available to put phone in USB Com 1.0 (factory mode).
The main issue is flashing board firmware as new firmware installation via HWOTA or other HrUpdater are hard bricking the phones. Even though the phone is detect-able as Factory Mode without disassembly and test points , DC Phoenix is unable to flash board firmware.
Hope many things and points are now clear to many of the readers.
Click to expand...
Click to collapse
I know how Phoenix work, that's why i said that maybe you still need to actually connect test points. The fact that USB Com is available without test points doesn't mean you will be able to flash the board software.And the fact that it doesn't work with kirin970 proves it.
Clearly, these bricks are not hardware failures so if Phoenix cannot flash it in USB Com mode, makes me think that:
1) Test points are needed no matter the port is showing or not
2) Something is wrong with GPT
3) Kirin970 works differently and Phoenix doesn't work in USB Com mode
These are only speculations, obviously.
What Phoenix guys told you when you talked to them, they have any idea why their tool fails?

And regarding to the purpose of this thread, so far my opinion is that the culprits are the firmwares from 16/04 , no the "noxloader" ones. Here's my examples based on the info I've got about these bricks.
1) B132C636 - > B134(noxloader) C636 - > B135 C636 = no brick
2) B132C636 - > B134C636 (16/04)-> B135 C636 = brick
3)B132636 - > B134C636 (16/04) - > B134(noxloader) C636 = brick
So far the only common point (beside C636 brand) is that all those that bricked, at some point they updated to a firmware from 16/04/2018.

Pretoriano80 said:
And regarding to the purpose of this thread, so far my opinion is that the culprits are the firmwares from 16/04 , no the "noxloader" ones. Here's my examples based on the info I've got about these bricks.
1) B132C636 - > B134(noxloader) C636 - > B135 C636 = no brick
2) B132C636 - > B134C636 (16/04)-> B135 C636 = brick
3)B132636 - > B134C636 (16/04) - > B134(noxloader) C636 = brick
So far the only common point (beside C636 brand) is that all those that bricked, at some point they updated to a firmware from 16/04/2018.
Click to expand...
Click to collapse
The support team of Phoenix has clearly said that they dont know whats the issue with their tool and can not give any time frame to make Phoenix working with Mate 10 Board Firmware. Further more , i was on C636B312, i updated to B134 noxloader , Phone was showing NRD90-test , i downgraded to B132 and phone gone dead (black screen i.e USB SER)

Related

Huawei P9 EVA-L09 stuck on eRecovery, factory data reset failed

Hello friends
I find myself in a very delicate situation
I have a P9 EVA-L09 32GB with B181 version of software, android 6.
After a failed update to android 7, the phone only normal starts in eRecovery where i don't have usable options.
The phone can boot in fastboot and it enters fastboot where the 2 options, factory data reset and wipe cache partitions both can be used but at factory data rest says "reset failed" and wipe cache partition doesn't produce any visible change.
The questions is, can this phone be rescued in some way?
Can it be reflashed in any way?
Thank you in advance for your answers
from what i have read on the internet, there are 3 distinct functions:
erecovery = volume up and power
fastboot = volume down and power
fastboot&rescue mode = volume down and connect usb cable plugged into pc and using the hisuite software
i have a microsd card
can i reflash somehow a new firmware ?
i have read of another method using the pc and entering commands from the computer
iconicpaul said:
from what i have read on the internet, there are 3 distinct functions:
erecovery = volume up and power
fastboot = volume down and power
fastboot&rescue mode = volume down and connect usb cable plugged into pc and using the hisuite software
i have a microsd card
can i reflash somehow a new firmware ?
i have read of another method using the pc and entering commands from the computer
Click to expand...
Click to collapse
you need a way to use your sdcard without the phone (sdcard reader or another phone)
if you have this follow this guide strictly:
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
with this guide you will get back to a working 6.0 Firmware and update it to latest Nougat 7.0 firmware.
thank you
i already did some searching on the net and the main issue is the unlocking the bootloader, this must be the first step, without this, its impossible to flash/rewrite anything on the phone
the problem at Huawei phones is that the unlocking is done through a code which either you get it free directly from Huawei or by paying third parties
there is one last problem, the FRP (factory reset protection) feature, which so sar is not very clear to me how it fits into the picture and what it does exactly
the problem of getting an unlock code is further more complicated if the phone cant be accessed from the menu or you do not have the box on which the IMEI, S/N and other data are written
There is no reason to unlock bootloader first. If u follow the guide above it will work. I was in the same situation.
Sent from my EVA-L09 using XDA-Developers Legacy app
xtcislove said:
There is no reason to unlock bootloader first. If u follow the guide above it will work. I was in the same situation.
Click to expand...
Click to collapse
i would like to ask you a different question but related
Is it technically possible for a phone, in this case a P9 to have a specific software version locked on to it? in other words, to be impossible to change the version of the software?
i am asking you because i have managed to reflash my phone and is working again but i was forced to put exactly the same version as before, B181.
iconicpaul said:
i would like to ask you a different question but related
Is it technically possible for a phone, in this case a P9 to have a specific software version locked on to it? in other words, to be impossible to change the version of the software?
i am asking you because i have managed to reflash my phone and is working again but i was forced to put exactly the same version as before, B181.
Click to expand...
Click to collapse
If u are on B181 you can update to any version above if it matches your OEMINFO.
The guide i posted above will change your OEMINFO to C432 (EU Version) and after this u will receive every new update.
Any provide can use its own OEMINFO so if your provide dont push any update abbove 181 you are locked to this.
But again use the guide above strictly and you will get latest Nougat.
Short:
You cant be locked to any software version at least if you are on C432.
i received OTA to B182 and immediately after installation i got OTA update to B372
problem solved, learned a lot about Huawei software system
thank you for your help

Huawei p9 always rebooting every 2 minutes

Hello everyone,
I'm new in xda's forum and so that's my first thread.
I hope you can help me.
I have a Huawei P9 EVA-L09C02B357 that lately it automatically reboot about every 2 minutes. The interesting things is that it happened only if I boot the ROM (stock or not). But in recovery mode (or erecovery) or fastboot mode, this automatic reboot doesnt manifest.
All is started when I have tried to install RROS Nougat on my phones and it was working when i tried to turn off the phone and then turn it on but nothing, the phone was stuck on boot phase.
I decided to switch data file system from f2fs to ext4 and then reinstall it as the guide explains.
https://forum.xda-developers.com/p9/development/rom-t3606185
The ROM worked correctly except the fingerprint sensor.
During the first configuration, it scans my fingerprint but for a bug, i couldnt go over the first scan.
Searching on the internet I understood that the problem could be the modem. But for a mistake I have flashed the wrong fix for the modem (it was for another phone, don't ask me how I didnt notice it).
Now even with stock rom or custom the phone has this automatic reboot. Particularly the stock rom has many bugs every time i flash it, like: there isn't the IMEI, there aren't any preinstalled apps, is really slow in some situations and the default keyboard is the voice typing...
I think the solution is to flash the stock modem, but when I try to flash it via fastboot, it says: "No suitable files selected. Check profiles.xml".
Thanks in advance
P.S. sorry for my bad english :C
Go back to MM version and. Factory reset and upgrade it to nougat
vampirian said:
Go back to MM version and. Factory reset and upgrade it to nougat
Click to expand...
Click to collapse
Hi vampirian,
thank you for the answer.
Sorry the ignorance but... what's MM version?
Party5999 said:
Hi vampirian,
thank you for the answer.
Sorry the ignorance but... what's MM version?
Click to expand...
Click to collapse
MM= MarshMallow, android 6
Nate91 said:
MM= MarshMallow, android 6
Click to expand...
Click to collapse
Can you send me the MM firmware?
To go back to android 6, my phone should have android 7 installed? Cuz now i have some problems to flash it.
UPDATE
Thank you so much vampirian!
I have successfully installed android 6 and the automatic reboot is gone.
Now i'll try to update it and probably retry to install RROS .
(yes i'm stubborn).
Party5999 said:
Thank you so much vampirian!
I have successfully installed android 6 and the automatic reboot is gone.
Now i'll try to update it and probably retry to install RROS .
(yes i'm stubborn).
Click to expand...
Click to collapse
I know I don't write a lot of things or give you all the links. But it was good for you to research and learn more about your device good job and good luck with rros (although is dated and its not really worth, but that's just my opinion )
vampirian said:
I know I don't write a lot of things or give you all the links. But it was good for you to research and learn more about your device good job and good luck with rros (although is dated and its not really worth, but that's just my opinion )
Click to expand...
Click to collapse
Last thing...
The serial number of my phone now is "EVA-L09C900B182". Which firmware for nougat should I download?
Party5999 said:
Last thing...
The serial number of my phone now is "EVA-L09C900B182". Which firmware for nougat should I download?
Click to expand...
Click to collapse
This is not the serial number (of your device) but the stock firmware build mame/number
If you debrand to c432 (EU) from your c900, you will automatically receive (must have SIM card in) OTA updates first to b242 (over your b182) and then further OTA updates up to b399 or even b502
PS: For debranding to c432 you can use this guide
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
zgfg said:
This is not the serial number (of your device) but the stock firmware build mame/number
If you debrand to c432 (EU) from your c900, you will automatically receive (must have SIM card in) OTA updates first to b242 (over your b182) and then further OTA updates up to b399 or even b502
PS: For debranding to c432 you can use this guide
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Click to expand...
Click to collapse
Thank you again for your incredible posts.
The phone is updating now to b2xx (i don't remeber XD)... which ROM for my huawei p9 do you recommend?
Party5999 said:
Thank you again for your incredible posts.
The phone is updating now to b2xx (i don't remeber XD)... which ROM for my huawei p9 do you recommend?
Click to expand...
Click to collapse
If you have debranded to c432 as suggested in my previous post, let it update as far as it gets (b398, b399 or even b502).
Once it stops receiving OTAs, perform Hard reset with wiping Internal memory (you can do it from Settings or from eRecovery)
Btw, if it attempts an OTA but it fails, then go back to the updating screen and choose Full update, instead of (default) differential update.
Which ROM to suggest you - Magic Rainbow v4:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
zgfg said:
If you have debranded to c432 as suggested in my previous post, let it update as far as it gets (b398, b399 or even b502).
Once it stops receiving OTAs, perform Hard reset with wiping Internal memory (you can do it from Settings or from eRecovery)
Btw, if it attempts an OTA but it fails, then go back to the updating screen and choose Full update, instead of (default) differential update.
Which ROM to suggest you - Magic Rainbow v4:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Click to expand...
Click to collapse
Now the phone is installing the b395 update. Is the hard reset necessary?
I knwo the existence of Magic Rainbow but i didn't know that it is based on Emui. I'll download it because i guess it is more stable than RROS.
It seems that i cant go over b395.
Party5999 said:
It seems that i cant go over b395.
Click to expand...
Click to collapse
Are you now on EVA-L09 c432 b395, exactly as that?
You do not receive further OTA, or you received OTA but it failed (in that case force Full update as suggested above)?
If you're really not receiving OTA b398 or b399, try Hard reset with wiping Internal memory - if still mo OTA, install b398 by HWOTA method
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Once you reach b398, you're ready for MR v4.
zgfg said:
Are you now on EVA-L09 c432 b395, exactly as that?
You do not receive further OTA, or you received OTA but it failed (in that case force Full update as suggested above)?
If you're really not receiving OTA b398 or b399, try Hard reset with wiping Internal memory - if still mo OTA, install b398 by HWOTA method
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Once you reach b398, you're ready for MR v4.
Click to expand...
Click to collapse
Yes, I'm on it but at the moment i dont receive any kind of update. I'll try Hard reset tomorrow.
Can you explain the method to make Hard reset, because i dont understand what should I do...
Party5999 said:
Yes, I'm on it but at the moment i dont receive any kind of update. I'll try Hard reset tomorrow.
Can you explain the method to make Hard reset, because i dont understand what should I do...
Click to expand...
Click to collapse
If you boot to eRecvery ( Vol+ and Pow) you will find Hard reset option.
Similarly, under Settings /Advanced Settings/ Reset phone there is also hard reset option - cannot tell you better details, I have TWRP and MR v4, I don't have these options.
Also if you 'dial' ' *#*#2846579#*#* a hidden Project menu will open, with Restore Factory option
zgfg said:
If you boot to eRecvery ( Vol+ and Pow) you will find Hard reset option.
Similarly, under Settings /Advanced Settings/ Reset phone there is also hard reset option - cannot tell you better details, I have TWRP and MR v4, I don't have these options.
Also if you 'dial' ' *#*#2846579#*#* a hidden Project menu will open, with Restore Factory option
Click to expand...
Click to collapse
The only method that i know to go in erecovery, if bootloader is locked, is by using PC and know i can't...
What if I use firmware finder?
Party5999 said:
The only method that i know to go in erecovery, if bootloader is locked, is by using PC and know i can't...
What if I use firmware finder?
Click to expand...
Click to collapse
Both two last options as listed (Settings and Project Menu) are present in stock ROM.
And you can boot to eRecovery as above - shut down, then press and keep pressing Vol+ and Pow together
If not OTA, then the best way for manual updating is HWOTA, I gave you the link also above
But still, you didn't confirm, are you really on EVA L09 c432 b395, ie, you are not on L19 (by mistake)
zgfg said:
Both two last options as listed (Settings and Project Menu) are present in stock ROM.
And you can boot to eRecovery as above - shut down, then press and keep pressing Vol+ and Pow together
If not OTA, then the best way for manual updating is HWOTA, I gave you the link also above
But still, you didn't confirm, are you really on EVA L09 c432 b395, ie, you are not on L19 (by mistake)
Click to expand...
Click to collapse
I was on EVA-L09 c432 b395 and now I'm on b502. I tell you what I did.
I tried to make a reset bt the Project Menu option but, the reset it didn't gave any update...
So I tried with firmware finder (android version) and I used the DNS method. I have chosen the b397 OTA and the updater found it.
During the download, it arrived at 25% and suddenly the phone has found the b502 for a total of 4 patch to download together (I dont know how to explain that thing).
After download the phone reboot for installing phase but it failed... and on boot it appeared a red warning, then i went to erecovery, shut off the phone and go to recovery mode for a factory reset.
Factory reset was a success but on boot the red warning still appear but i tried to continue to boot... fortunately it was all ok but the phone was on b395.
It magically appeared the screen for b502 Full-OTA update and now I have it!
I wouldn't understimate you but I always prefer to try solution by myself.
(sorry again for my bad english)

MAte 10 pro Emui 9 Soft Brick

I've used the region code I've installed 3 days ago and I've used the device 1 day. Then I get my idiot head c185 device I said I am installing C432 Emui 9 u and there the device could not install the software with Hwota anymore. Continuous E enters Recovery Mode. I am trying to do the installation with FAstboot on the computer.
yunusdemir said:
I've used the region code I've installed 3 days ago and I've used the device 1 day. Then I get my idiot head c185 device I said I am installing C432 Emui 9 u and there the device could not install the software with Hwota anymore. Continuous E enters Recovery Mode. I am trying to do the installation with FAstboot on the computer.
Click to expand...
Click to collapse
Try to avoid cross posting issues, it makes it confusing for people trying to answer you and I'd imagine for you to follow potential solutions.

HELP! Bootloop after android pie update using Hisuite

Hi every one. I can't find solution to my problem so I decided to ask your help.
Few days ago I read that I can update my Huawei p10 to android pie officialy through Hisuite. Scanned for update and it said that I'm on the latest android which was emiui 5.1 so I started to look for a way to force it and found solution (will be posted bellow).
After it Hisuite found pie 9.0.1 update and after downloading the files it started installing it. After that it loaded 100% and rebooted, then rebooted again and again and again... shortly realised that it's bootlooping. Tried to turn it off and yet it kept bootlooping, took it apart disconected battery and hopped to enter recovery mode or fastboot, boot as soon as i plug the battery in and put usb or power on button same thing continued and i can't enter those modes whatever i do. Can anyone help me with this?
Oh yeah, I've tryied this methode on mate 9 pro from 5.1 to 9.1 and it worked flawlessly, then right next after that I attempted p10. Also i think i didn't do anything with firmware finder couse i saw update anyway.
Also on backup photo Details it shows build VTR-L09C432B171 ithat was before me trying to update it
Update methode
"Instructions how to get an authorized version of EMUI 9 on EMUI 9 via Firmware Finder
Attention, this method requires more success checks.
1. Add a line to C:\Windows\System32\drivers\etc\hosts
188.225.84.142 query.hicloud.com
2. Download and install HiSuite9.0.2.304, BUT NOT RUN:
3. Replace the files:
httpcomponent.dll move with the replacement in C:/Program Files (x86)/HiSuite or other directory in which the application is installed HiSuite
HiSuiteConfig.xml move with the replacement in C:/Users/YOURUSERNAME/AppData/Local/Hisuite/userdata/UpdateDogDev
4. Open FF (any, I like the smartphone to register - less action)
Looking for a permitted Android 9 for your device on the principle: device_model: VTR-L29 or VTR-L09,
NOTE: Firmware must be approved for your IMEI
Once again, make sure it is permitted, registers the update for eRecovery.
NOTE: There are two types of firmware: CHN, i.e. for Chinese devices and OVS, for all the rest. So if you do not have Chinese firmware, then you need to pay attention exclusively to OVS.
5. Run HiSuite, connect the device, looking for an update, update, enjoy."
IIm still lost. Is there anything i can do?

SOLVED:Soft-brick Huawei P30 pro:Your device has loaded a different operating system

I already sent a private message to a Recognized Contributor on XDA.I think that If post here I could help also other members.
I have problem with my new huawei p30 pro.It was stuck on android 9 and emui 9 ,I tried every official modes to force the update.But I couldn't achieve that.
So I tried with hisuite proxy .I finded my Device model(VOG-L29) region: C431-HW-EEA , then clicked on add rom on firm Finder v2 .The version was the lastest 102.0.0.134
The procedure was smooth and I choosed the right ROM (100% sure!I already have that webpage open)Once finished the smartphone installed the EMUI 12 but once restarted the massage: Your device has loaded a different operating system! scared me .
Do I broke the phone? Is there a way to fix it without changing the motherboard?
Thanks a lot every help will be appreciated so much
Little Update.
I tried several methods trying solving this big issue.
1.Update from Erecovery trying to download and recover the package via WIFI
RESULT:the phone updated from 12.0.0.134 to 12.0.0.149 but once rebooted the
same result with black screen and the massage: Your device has loaded a different operating system
2.I done the same procedure of this guy
I also saved the log file of hisuite and here are the version before I made that mess:
* FirmWare_Base:VOG-LGRP2-OVS 9.1.0.240
* FirmWare_Cust:VOG-L29-CUST 9.1.0.4(C431)
* FirmWare_Preload:VOG-L29-PRELOAD 9.1.0.2(C431R2)
So The ROM I selected on huawei firm finder v2 was good(VOG-l29 102.0.0.134)
I succeeded to Recover and install the previous ROM,the 9.1.240,with hisuite and hisuite proxy
but once finished an error on the p30pro appear: Software install failed.
tried also the 10.0.0.195
I'm thinking about dload with otg or nm card but I don't know the procedure.
Could you guys help me?
Thanks
As the title changed I solved the problem of soft brick.
I write here the tutorial to help those who might have the same problem.
Requirement :OTG cable ,exFat formatted pen drive and the right Firmware to flash.
Create a dload called folder inside the pen drive and put in it the 3 Firmware's .zip file(base,cust and preload)
I specify that my p30 was bricked on version 12, so my first attempt was to load the version
VOG-L29 hw eea VOGUE-L29C 9.1.0.115(C431E4R2P2).
To flash the firmaware from usb pen take the phone off and hold the volume up button for several seconds while we connect to charge the phone .Connect the usb pen and from erecovery choose OTG update mode.
The result was an unbricked p30 pro but no fast charge and usb data tranfer and I can't get any type of update from OTA.
So I downloaded this version:
https://huaweidownload.com/download/p30-pro/vog-l29-2/10-1-0-123/
I flashed my P30 Pro once again, and of course no USB connection and fast charging. But system afetr few minutes started finding upgrades via OTA. Passed from 10.1.0.179 to 10.1.0.201. Of course I let it upgrade.
It was 11.0.0.138 first, then 11.0.0.174(last EMUI version before version 12 ) came and USB connection was restored.
you can also find other firmware here:
https://androidhost.ru/search.html
https://www.hardreset.info/it/devices/huawei/huawei-p30-pro/faq/firmware/huawei-firmware/
Even if I am a programmer I am new in the world of android bricks and I spent 2 afternoons and many attempts to solve the problem.
The last problem concerns the creation of a backup point. I have tried different version of HiSuite and both windows 10 and 8.1.But I couldn't get data from phone
The solution is to install the Androis ADB inteface Drivers while the phone is connected to the PC. I believe that this way data information is injected to the phone as well as installed on the PC.
take the drivers from here: https://oemdrivers.com/usb-adb-interface
or here: https://www.drivermarket.net/adb-fastboot-drivers-v1-4-3-download-for-windows-latest/
once you carry out this procedure you fixed everything

Categories

Resources