Hello everyone, I'm new here and I'm looking for help for my P8 lite 2017 Pra-Lx1 L31.
I flashed wrong costomrom, now starts for 2 rectangles blue and green then passes
for eRecovery in Chinese
I have already tried to update for wi-fi and it gives error in the search of the server.
I can access the fastboot mode and I have the unlocked bootloader and the frp locked.
I can not install TWRP through fastboot.
I have already tried UPDATE.APP by dload mode and it gives error or stops at 5%.
I already used several tutos here of the forum but nothing solved.
Has this ever happened to anyone? How can I solve ?
I thanked a charitable soul. :crying::crying::crying:
Edit : Solved
It was days of exaltation and headaches but at last I managed to find the thing.
With a lot of searching I found on the net 1 firm compatible, I did the dload method
* then wipe / data reset, installed TWRP and backed up. Again data reset and
replaces the backup of another PRA-LX1 from a friend.
Voila, I updated and now I have the impeccable PRA-LX1 8.0.0.385 (C432).
The version that had before the brick was PRA-LX1 8.0.0.046 (OC71).
Related
Hello XDA Community,
yesterday i tried to root my Huawei P8 Lite 2017 and failed on it,
now im stuck with a Phone which has bootloader unlocked but FRP Lock so i cant flash anything with fastboot
and im boot looping.
Here are some System Informations
Huawei P8 Lite 2017 PRA-LX1C432
Things i allready tried:
Dload Method
Flashing which didnt work cause of FRP Lock
I just bought that phone recently i really would appreciate some Help
v3CN said:
Hello XDA Community,
yesterday i tried to root my Huawei P8 Lite 2017 and failed on it,
now im stuck with a Phone which has bootloader unlocked but FRP Lock so i cant flash anything with fastboot
and im boot looping.
Here are some System Informations
Huawei P8 Lite 2017 PRA-LX1C432
Things i allready tried:
Dload Method
Flashing which didnt work cause of FRP Lock
I just bought that phone recently i really would appreciate some Help
Click to expand...
Click to collapse
Actually ,a stock firmware flash should help even if bootloader is locked...
Have you tried flashing stok firmwarw again and what errors do you get?
Sent from my VS987 using Tapatalk
user 7 said:
Actually ,a stock firmware flash should help even if bootloader is locked...
Have you tried flashing stok firmwarw again and what errors do you get?
Sent from my VS987 using Tapatalk
Click to expand...
Click to collapse
Hey mate fiirst of all thanks for your reply and all the time I try to flash something with fastboot it say '' failed command not allowed''
now i tried to lock and unlock the bootloader again but once i locked it , it wont let me unlock it again now it says command not allowed aswell
What did you actually do to root ur device?
Systemless root or something else?
Sent from my VS987 using Tapatalk
I tried to root the device to install a spoofing app as system app then tried to unroot with SU App after i did that my phone didnt started anymore then i did a factory reset with TWRP and my Phone finally booted i was able to fill in my screen password but then the screen kept black only thing i saw was the system buttons like home back and so on . i could even get into settings at this stage but i couldnt get into the dev options neither i couldnt factory reset in the normal settings. then i tried to flash a new firmware and since then my FRP was locked which was unlocked before i dont know why and then i became the Error Mode screen all the time i start the phone after that i did what i just said with bootloader re and unlock but like i said it failed too. The Error Mode says Func NO 10 Boot image and ERROR no 2 load failed
Now with a.locked bootloader, you must have a hard time ahead.
If you need a quick solution you can try the dc unlocker . otherwise, you will have to wait until we can sort out a solution
Sent from my VS987 using Tapatalk
Well i was thinking of using the DC Unlocker but im curious of if its working probably since it costs money
cant really anyone help me further
I can't really help in your case. Hope someone takes a look at it.
Please don't mess with your device without knowing how to fix and its possible causes.
still didnt came any further
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
I think DC unlock is not supported for thì this model. Did Did you try Huawei Funky???
Apparently all versions of Honor 9 are supported by DC-unlocker and DC-Pheonix....
ums1405 said:
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
Click to expand...
Click to collapse
Try stock service B130 firmware:
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432b130-capacitive-buttons-100-t3729106
Instead of step 4 do forced upload: VOLUME UP + VOLUME DOWN + POWER
Hi,
I've managed to re flash b150. In doing so I got back recovery and erecovery but when you reach that final stage of the process the phone stops at 5%. When I reboot to recovery, factory reset stops at 35%
Any ideas
?
Sent from my [device_name] using XDA-Developers Legacy app
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
ums1405 said:
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
FRP status is not only on Chinese phones
you need to sew firmware for al10
The phone was rebounded by the shop I bought it from.
It said STF-L09B150 indexical info when the phone was working.
So if I'm going to repair this brick what update files should I use?
Original Chinese or the b150 used when rebranded?
Sent from my [device_name] using XDA-Developers Legacy app
Hi all,
FYI, I've sent the phone back to the shop I bought it from.
I'll take my chances, better than paying money for something that may not work.
Thanks everyone for showing interest in my situation, I let you all know how I get along with this issue.
Ps.: As a community, lets push Huawei/Honor to release Kernel Sources for this model and others like the P10 Plus.
Ps: Huawei/Honor have to realise that a strong developer community adds value and desirability to a product. That's how a product becomes 'Cool' translating into more revenue/customers/profit - eg OnePlus.
.
Hi all, a quick update .....
Sent the phone back and from what I gather the phone actually had an issue with the main board.
Now enjoying a brand new MATE 10 (Non-pro with 6/128gb) in beautiful Obsidian black.
Wonderful.
Back in december/january some users reported a glitch while rebranding STF-AL10 to STF-L09 with the old nougat hwota (at oem bin flashing step).
After editing hwota script, then rebranded : they ended with a FRP locked status.
Their only way to unlock frp was with dcunlocker or funkyhuawei I don't remember.
After frp unlocked, their bootloader wasn't seen through fastboot.
I think this could be solved by regedit a value in registry.
To my knowledge the only public firmware files working with the dload way (3 buttons + usb connected) are the one titled "service repair", the others one won't work dload as they are. They are for hwota or forcing "official" ota.
Hello my name is Aleksander i have bricked my mate 10 lite.
Original phone is rne-l21c432 but i rebranded it few weeks back to c185 for update to OREO.
Yesterday i wannted to update to last rom b332 with HuRUpdater_0.3
It flashed ok but rhere was one error but i didnt mind of that becouse at flashing before yesderday was also error and everything worked ok.
Now i can only get in rescue mode and got this error
Error!
Func NO 15(bl31 image)
Error NO 1(security verify failed)
I tryed to flash with DC-Phoenix and it's not working. Early version of dc-phoenix works for flashing but i got this. dc-phoenix can not activate back door and fb lock state is locked.
Newer versions says that the device is not supported.
I tryed to relock bootloader and unlock again, but now i can not get in to the fastboot anymore. it is looping constantly in that rescue mode and i get that errors Func NO 15 and errror NO1.
I don't know what to do anymore.
Does anybody have any solution to try? .
The Dc-Phoenix did work like few weeks back on my Mate 10 lite.
Thank you for youre response.
rutarvip said:
Hello my name is Aleksander i have bricked my mate 10 lite.
Original phone is rne-l21c432 but i rebranded it few weeks back to c185 for update to OREO.
Yesterday i wannted to update to last rom b332 with HuRUpdater_0.3
It flashed ok but rhere was one error but i didnt mind of that becouse at flashing before yesderday was also error and everything worked ok.
Now i can only get in rescue mode and got this error
Error!
Func NO 15(bl31 image)
Error NO 1(security verify failed)
I tryed to flash with DC-Phoenix and it's not working. Early version of dc-phoenix works for flashing but i got this. dc-phoenix can not activate back door and fb lock state is locked.
Newer versions says that the device is not supported.
I tryed to relock bootloader and unlock again, but now i can not get in to the fastboot anymore. it is looping constantly in that rescue mode and i get that errors Func NO 15 and errror NO1.
I don't know what to do anymore.
Does anybody have any solution to try? .
The Dc-Phoenix did work like few weeks back on my Mate 10 lite.
Thank you for youre response.
Click to expand...
Click to collapse
Is there really no solution ?
My mate 10 lite is bricked too that's why I'm following your post too
Hello to all admin and friends,
Recently i decided to have a try on downgrading my huawei p9 from nougat to marshmallow ... After all done I realize that i installed wrong country firmware... to make it back to my country firmware I re-download all the firmware back.... unfortunately i replace the update.app with the "HUAWEI P9 Rollback Package" and I messed up my entire phone... [now my phone is stuck on HUAWEI LOGO.... well guess im facing a hard brick.. T.T ] on fastboot ... my phone & frp locked... i tried to unlock bootloader, phone n frp all that stuff but still failed.... adb etc has installed tried few tutorial on post and youtube channel step by step but still cant fix my problem... anyone that kind enough willing to help me please?
oeurn.ren said:
Hello to all admin and friends,
Recently i decided to have a try on downgrading my huawei p9 from nougat to marshmallow ... After all done I realize that i installed wrong country firmware... to make it back to my country firmware I re-download all the firmware back.... unfortunately i replace the update.app with the "HUAWEI P9 Rollback Package" and I messed up my entire phone... [now my phone is stuck on HUAWEI LOGO.... well guess im facing a hard brick.. T.T ] on fastboot ... my phone & frp locked... i tried to unlock bootloader, phone n frp all that stuff but still failed.... adb etc has installed tried few tutorial on post and youtube channel step by step but still cant fix my problem... anyone that kind enough willing to help me please?
Click to expand...
Click to collapse
Hi there,
Are you able to connect your phone and can ADB Recognise it?
So, I work somewhere in which phones need to be switched off for security reasons. Every time I leave, I switch mine back on. I noticed in the past few weeks that my Mate 10 would restart itself a few times after I turn it on after work. After a while, it sorts itself out and stops rebooting, with everything returning to normal. A few days ago, it didn't start up properly and took me to Huawei eRecovery. I'd never seen that before. I tried rebooting, but it would keep coming back to eRecovery. I also did a factory reset and cleared the cache and it looked like it was fixed because I saw a white EMUI screen asking me to set the language and all that stuff. However, the screen would soon become unresponsive and the Mate 10 reboot would itself and go back to eRecovery. I tried this a few more times until I thought I got lucky and managed to finish the whole setup process where I see the phone's home screen with the apps. However, when I tried to add my gmail account, the phone once again reset itself back into eRecovery. So I decided to choose the 'Download the latest version and recovery' option. I left that for a while and when I came back I saw that the phone was still in eRecovery. I rebooted a few times and even tried downloading the latest version again, but now it says, 'Getting package info failed'.
The phone was purchased in China. It says on the back, 'ALP-AL00'. I never attempted to rebrand, root or anything like that. All I've ever done is change the system and input language in settings, download the Google Play Store from App Gallery and updated to EMUI 9. I'm really at a loss as to what to do now. There aren't any service centres in my city or state. It's also kind of concerning that other people have posted similar issues and with no responses so far.
Bump
Bump again.
s3rialthrill3r said:
Bump again.
Click to expand...
Click to collapse
Tried to boot into recovery (not eRecovery) and do a factory reset from there?
Pretoriano80 said:
Tried to boot into recovery (not eRecovery) and do a factory reset from there?
Click to expand...
Click to collapse
How do I boot into the non-eRecovery recovery (sounds confusing already)?
s3rialthrill3r said:
How do I boot into the non-eRecovery recovery (sounds confusing already)?
Click to expand...
Click to collapse
shutdown phone remove usb cable from it power button + volume up for 5 seconds then release buttons
hamadazh said:
shutdown phone remove usb cable from it power button + volume up for 5 seconds then release buttons
Click to expand...
Click to collapse
I did that, but it still goes to eRecovery.
Try download mode..if it works, with sdcard and dload folder you can flash your last firmware...
manager77 said:
Try download mode..if it works, with sdcard and dload folder you can flash your last firmware...
Click to expand...
Click to collapse
Are you talking about the 'Download the latest version and recovery' option? I always get a ''Getting package info failed' message. Are you saying that I need to put something on an SD card and then choose that option? Where do I get the firmware and which one is the right one?
Bump
I continue searching the solution.
I have 1,5 yers with the same problem.
No I have solution yet.
Tryed Install manny Firmwares with SD card, Format under eRecovery and HiSute.
I already opened it and change the thermal paste.
Tested internal components...
Unfortunely my Huawei Mate 10 is a ALP-AL00 with a special hardware version (6Gb RAM + 128GB ROM), the International version have only 4Gb RAM.
If the Huawei return bootloader unlock i can try instal a custom rom, but without this code my best smartphone was turned into a paperweights.
I have no idea how to unlock his bootloader (The phone have Android 9.0)
I continue searching the solution.
leo.hyde said:
I have 1,5 yers with the same problem.
No I have solution yet.
Tryed Install manny Firmwares with SD card, Format under eRecovery and HiSute.
I already opened it and change the thermal paste.
Tested internal components...
Unfortunely my Huawei Mate 10 is a ALP-AL00 with a special hardware version (6Gb RAM + 128GB ROM), the International version have only 4Gb RAM.
If the Huawei return bootloader unlock i can try instal a custom rom, but without this code my best smartphone was turned into a paperweights.
I have no idea how to unlock his bootloader (The phone have Android 9.0)
I continue searching the solution.
Click to expand...
Click to collapse
Use testpoint (device back needs to be opened again), flash bootloader using DC Phoenix. Then flash board firmware. In board firmware you can use HCU to get an unlock code. You will need to repair device info using HCU after flashing board, as it will wipe it by default.
Here's a guide for fixing device when on board:
1)Flash oeminfo (own backup) from fastboot, or dump oeminfo using dd in adb shell and flash that one back using fastboot.
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Direct Unlock Network with HCU (device will find no network if not done)
5)Read Bootloader code if you ever used HCU to get code before
6)Download and flash Oreo service firmware from androidhost.ru using a OTG cable and a memory stick to flash it
After this your device should work fine and you will have an unlock code.
Please note that HCU doesn't work on firmware after May 2018, so don't replace Oeminfo after this as that will remove the unlock code generated by HCU.
leo.hyde said:
I have 1,5 yers with the same problem.
No I have solution yet.
Tryed Install manny Firmwares with SD card, Format under eRecovery and HiSute.
I already opened it and change the thermal paste.
Tested internal components...
Unfortunely my Huawei Mate 10 is a ALP-AL00 with a special hardware version (6Gb RAM + 128GB ROM), the International version have only 4Gb RAM.
If the Huawei return bootloader unlock i can try instal a custom rom, but without this code my best smartphone was turned into a paperweights.
I have no idea how to unlock his bootloader (The phone have Android 9.0)
I continue searching the solution.
Click to expand...
Click to collapse
Maybe it's because...
...
...
...
...there is no solution.
It turns out that my phone was defective. A very good friend of mine happened to be making a trip to Shenzhen anyway, so they offered to take the phone with them to sort it all out. It was taken back to the manufacturer. The motherboard was defective. Since it was within warranty, I got a free replacement.