Good news for chinese firmware
rambik33 said:
Good news for chinese firmware
Click to expand...
Click to collapse
Hello
I took my p9 lite vns-l31c432. OK
I made it go to was-al00c00b240. OK
i reflected huawei's recovery.img stock and i closed the bootloader.
it works properly.
NOW.
I tested ota update with the phone, does not work.
I tested finder does not work.
i tested huawei updater v2.0, does not work.
I tested update on the pc with hisuite, does not work.
I can not register for the beta, I do not have a Chinese phone number, I am in France.
And
of course dload method, sofware install failed!
do you have an idea to try to start it?
Sim is not work?
rambik33 said:
Sim is not work?
Click to expand...
Click to collapse
Yes work
What the ota you try install?
We cant install it right ?
kisvagen said:
We cant install it right ?
Click to expand...
Click to collapse
Yes
Need wait few weeks)
Okay mate thanks for the info my model is : was lx1c432 . Dual sim . Hope the oreo will be better than nougat xd
Chisetdel31260 said:
Hello
I took my p9 lite vns-l31c432. OK
I made it go to was-al00c00b240. OK
i reflected huawei's recovery.img stock and i closed the bootloader.
it works properly.
NOW.
I tested ota update with the phone, does not work.
I tested finder does not work.
i tested huawei updater v2.0, does not work.
I tested update on the pc with hisuite, does not work.
I can not register for the beta, I do not have a Chinese phone number, I am in France.
And
of course dload method, sofware install failed!
do you have an idea to try to start it?
Click to expand...
Click to collapse
Nice try man! Ok, did you try to update b311 using ffinder, or just with beta program? Now, I see that they remove beta b311 from ffinder...
Also, just keep it in mind that Emui 8 change some partitions including recovery sectors. So, we dont have Twrp for emui 8 for our models, and its big posibillity to stuck on some beta emui 8 lets say Al00C00 without any chance to rollback to Emui 5 and destroy partitions, brick your phone trying that. Just wait for custom recovery for Emui 8 for Kirin 658, after that u can do some experiments ?
Regards.
Alexxxx1 said:
Nice try man! Ok, did you try to update b311 using ffinder, or just with beta program? Now, I see that they remove beta b311 from ffinder...
Also, just keep it in mind that Emui 8 change some partitions including recovery sectors. So, we dont have Twrp for emui 8 for our models, and its big posibillity to stuck on some beta emui 8 lets say Al00C00 without any chance to rollback to Emui 5 and destroy partitions, brick your phone trying that. Just wait for custom recovery for Emui 8 for Kirin 658, after that u can do some experiments
Regards.
Click to expand...
Click to collapse
new tests.
Too bad, I tried DC-Phoenix V50 with 15 credits.
to install b331-log, after having restarted the installation 4 or 5 times, he finished installing it completely. I wonder how dc-phoenix can create a new partition.
and that on xda, there is no dev that could create an equivallent toolkit.
But, the p9 lite remains on a black screen, the volume and power buttons do not respond anymore.
no led lights up. But it still remains recognized in fastboot mode.
so, I can always go back to a clean device.
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)
Hello,
I've been searching for days for a way to unlock bootloader/root my p8 lite 2017 (PRA-LX1 with EMUI 8), I've tried a lot of things, read of lot of topics, and at this point, I don't know if it is even possible.
I read that it is possible to root my phone by downgrading it to android 5 so I tried, but I think I need to have android 6 since nothing really happens. I put the update files in the dload directory, my phone starts and shows the update screen, then it starts and nothing has changed.
I tried to reset to factory settings, hoping it would go back to a previous android version but it's still on EMUI 8.
I tried that dc unlock software, but since my phone uses android 8, it seems that the guy want 25€ to give the code...
I want to install Lineage Os and root my phone, that's all. Is there a way to perform that for me or do I have to forget the idea ?
Thank you for your time.
it seems my topic is not in the proper forum, sorry for the mistake...
Th3BiSh0p said:
Hello,
I've been searching for days for a way to unlock bootloader/root my p8 lite 2017 (PRA-LX1 with EMUI 8), I've tried a lot of things, read of lot of topics, and at this point, I don't know if it is even possible.
I read that it is possible to root my phone by downgrading it to android 5 so I tried, but I think I need to have android 6 since nothing really happens. I put the update files in the dload directory, my phone starts and shows the update screen, then it starts and nothing has changed.
I tried to reset to factory settings, hoping it would go back to a previous android version but it's still on EMUI 8.
I tried that dc unlock software, but since my phone uses android 8, it seems that the guy want 25€ to give the code...
I want to install Lineage Os and root my phone, that's all. Is there a way to perform that for me or do I have to forget the idea ?
Thank you for your time.
Click to expand...
Click to collapse
All I found is that you should stay below B374 - Emui and Android 8.0.0 are fine ...
use dcUnlocker from playstore - pay a few Euro / $$ and you'll receive an unlock code for use in adb fastboot
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?
I considered myself to be noob here . It's my fault not to did a lot of research as possible before I proceed my upgrade since I wanted my Huawei Mate 20 Pro (LYA-AL00) (chinese version with no finger print) to run Android 10 instead of 9 (Which I didn't know what version I was using but I believe it was the latest of Android 9 for Mate 20 Pro). What I did was following this guide >
https://ministryofsolutions.com/202...-emui10-android-10-stock-firmware-update.html
everything described in the above link seems legit so I immediately follow step by step and download the stock firmware almost 5 hours. After using OTA with dload I saw the screen install the firmware successfully. However, after few minute the phone boot up and it showed "your device has loaded a different operating system". In such case, I couldn't do anything with erecovery or even using the hstool here: https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
by using the method above, i stuck at (install recovery or install system) where my phone screen show circle with 5% processing, then hi suite say failed recovery. In such case, I believed I might install the wrong firmware which isn't allow for my phone? If it is wrong why the phone allow to install the firmware via dload? If not compatible or wrong should not let user process the work.
Right now I stuck at (Your device is loaded a different operating system) and nothing I can do in erecovery including using wifi to update. Can anyone help? Thank you
Sorry for my bad english.
NEED HELP !!!! same problem on lya l09
i used hisuite to update my mate 20 pro LYA L09 to emui 10 ( the official way ) after the update was installed my phone was stuck in this black screen " your device has loaded a different operating software " . i tried using erecovery " get package info failed"
OTG DLoad package method, if works you will be fine. If not, try DC phoenix with a Dload package. Last time I experienced same thing. Then DC phoenix helps.