Related
Hello,
I just want to thank anyone in advance for taking their time in reading this and trying to assist.
My situation is that I have a Mediapad x2 702L which when I purchased it, it said it was unlocked.
I go to the recovery screen and it shows unlocked but I couldn't flash anything using adb got an error saying "adb failed (remote: command not allowed)"
so I downloaded dc-unlocker, when I used that I only had the option to FBR. well I did that several times after bricking my device and had to pay $15 each time for a flash to work.
I ended up spending like $90 on this and I was able to get my device unbricked flashed back to GEM 702L B003 stock firmware, that was the only way to get it to work.
from there I was able to get root and I attempted to use several flasher .apks to flash recovery to twrp because it would not work using adb, I would have it installed but then
after the reboot it would lose it. Now at this point My internal SD card is showing it only has 4 gig's of memory when it used to have 32gig's of memory.
if I go to terminal and check partitions I have so many
cat /proc/partitions
I am unable to take a screen shot on my phone to post either
but I was wondering if anybody has ever came across this
or could assist with helping me fix my partition table
Thank you again for all your assistance.
Factory Reset?
I'm unable to do that via dc locker gives me an error now due to the partition being off
USB debugging enabled to use ADB?
Thank you very much guys, I was able to put a copy of android 6.0 on the sd and install a local update then I was able to go back to factory settings and the issue was resolved.
Another thing I noticed is that I keep loosing TWRP?
I had it on there for like 10 minutes and flashed root and two different roms
and then when I tried to boot back into recovery it showed me the stock e-recovery
I had the X2-TWRP-3.0-2-BLACK-BLUE.img flashed for my TWRP.
any idea why I keep loosing it?
You Update Local over Stock Recovery,if you want install Twrp to Android 6.0 use this
https://drive.google.com/file/d/0B5I_q70mNuR4bXJTX3JmdzZZTWs/view?usp=sharing
and flash via fastboot
You can flash TWRP to recovery2 partion as well: For example
fastboot flash recovery2 X2-TWRP-3.0-2-BLACK-BLUE.img
Then keep USB connected when rebooting and holding VOLUME UP key.
This starts TWRP.
If you are not USB connected, the standard recovery will start.
This allows to do factory resets and firmware updates without flashing recovery.img for your version again.
A dload will overwrite the recovery2 partition with the "e-recovery". In this case you will have to flash twrp again.
It's not normal that you have to pay more than once for DC-unlocker booloader It's the same code. Maybe you used the option "Get unlock code"
This is a option for SIM locked phone, but not to unlock bootloader.
"Get bootloader code" is the correct one. You can write down it and use it again and again if neccessary. (I never had to unlock twice)
fastboot oem unlock xxxx does the unlocking. That's all.
I would write do DC-unlocker and ask for return the money.
At The first i wanted sorry for by not good english.
Today i unlocked bootloader and rooted my honor 8 al10(china version)
Then I wanted to change firmware version to europe.
When i used the SRKtool and choose option ""change to oeminfo and custom.bin-EU<L09-C432> "" my phone restarted and show info about damage system and recommended wipe.
Then the system stopped working. My TWRP has been deleted. My rom C00B387 is not available for download.
I downloaded C00B135 and tried:
restore system using the Volume+ , Volume- and power button from dload folder
separate boot, recovery and system.img by HuaweiUpdateExtractor and install used ADB in fastboot mode
install only TWRP
used system eRecovery repair rom using wifi, but it happened fast failed
All method not working
I have a little experience with samsung and sony. Honor 8 is my first Huawei phone
Please help me, I very need working phone
Please write to me in simple words
I hope you will help me because fastboot works
Mysia said:
At The first i wanted sorry for by not good english.
Today i unlocked bootloader and rooted my honor 8 al10(china version)
Then I wanted to change firmware version to europe.
When i used the SRKtool and choose option ""change to oeminfo and custom.bin-EU<L09-C432> "" my phone restarted and show info about damage system and recommended wipe.
Then the system stopped working. My TWRP has been deleted. My rom C00B387 is not available for download.
I downloaded C00B135 and tried:
restore system using the Volume+ , Volume- and power button from dload folder
separate boot, recovery and system.img by HuaweiUpdateExtractor and install used ADB in fastboot mode
install only TWRP
used system eRecovery repair rom using wifi, but it happened fast failed
All method not working
I have a little experience with samsung and sony. Honor 8 is my first Huawei phone
Please help me, I very need working phone
Please write to me in simple words
I hope you will help me because fastboot works
Click to expand...
Click to collapse
install this https://forum.xda-developers.com/honor-8/development/frd-l09-tastynoogat-v1-0-04-12-17-t3588491 if fails
then follow
this
https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
Rebranding Honor 8 FRD-AL10 to FRD-L19 is Easy
I converted two mint FRD-AL10 to FRD-L19 versions yesterday. They have since both taken OTA updates over WiFi. One is at FRDL19C432B360 and the other took an additional update to FRDL19C432B380. I am in the Western United States, the phones know they are here too, but believe they are destined for Europe. When I take a local call, a +1 automatically shows up in front of the number on the call log. When I browse to Yahoo the phone goes to the Yahoo United Kingdom and Ireland home page. The FRD-AL10 phones were both at EMUI 5.0 and Android 7.0 and still at EMUI 5.0 and Android 7.0 after being rebranded to FRD-L19 UK. Everything works including dual SIMs. There is no remnant of Chinese apps, no pinyin characters anywhere. There are absolutely no problems. You do not need to root your phone with this method and you will end up with factory new like European firmware load.
Search these forums and obtain the following files:
Huwaei USB Drivers
DC Unlocker client
Minimal ADB and Fastboot
TWRP-3.1.1-1-frd.img
Honor%208_Rollback%20Package_FRD-L19_from%20Android%207.0%20EMUI%205.0%20to%20Android%206.0%20EMUI%204.1_C900B300_UK.rar
FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip
Format an SDXD memory card. Make sure it is class 10 speed.
Unarchive the rollback package and copy the entire dload folder to the SD card root directory.
Copy FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip to the SD card root folder.
Install the Huwaei USB drivers on your PC and phone.
Install DC Unlocker client on your phone.
Install Minimal ADB and Fastboot on your PC.
Copy twrp-3.1.1-1-frd.img into the Minimal ADB and Fastboot folder.
Enable USB debugging on your phone. Enter the system app and tap your build number 5 times and the developer mode becomes available.
In developer mode enable USB debugging and if OEM unlock is there, turn it on. It will likely not be there on the Chinese version, so if you don't see OEM unlock don't worry.
Accept the USB prompts on your phone. Reject communication with Huwaei Suite, Huwaei App, etc., and close them.
Follow the DC Unlocker instructions, buy credit with PayPal, and write down the bootloader code when you see it.
Unlock the bootloader. Open a command prompt in the Minimal ADB and Fastboot folder.
Enter
adb devices
The response should return the serial number of your phone proving USB communication
Enter
adb reboot bootloader
Your phone should now display the fastboot recovery screen
Enter
fastboot devices
The response should return the serial number of your phone
Enter
fastboot OEM unlock [your boot code here]
Your phone will factory reset and is now unlocked. Power down and reboot the phone.
Go to system app, developer, and turn on USB debugging, as before accept USB prompts, and reject and close Huwaei apps.
Open a command prompt in the Minimal ADB and Fastboot folder.
Enter
adb devices
Enter
adb reboot bootloader
The phone should now once again be at the fastboot recovery screen
Enter
fastboot devices
If your phone’s serial number is returned, you have communication.
Now install TWRP.
Enter
fastboot flash recovery twrp-3.1.1-1-frd.img
When the flash writing is done install the SD card and enter
flashboot reboot
Hold down the volume up and power buttons as the phone boots up, you can release the power button at the blue honor screen, but continue to hold down the volume up until you see TWRP.
Tap the install button
Tap Select storage and select the SD card.
Select the FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip file and swipe to flash.
When the flashing is done, your oem.info has been changed to Europe.
Select reboot to system.
Hold down volume up, volume down and power simultaneously while it reboots, continue to hold until the phone is in Huwaei erecovery mode.
Erecovery will force the phone to install the update.app file in the dload folder from the sd card. It will take several minutes.
When complete let the phone reboot on its own and hookup WiFi, enable USB debugging and let Huwaei apps hookup. Your phone will appear to be a legitimate European model to the network and will immediately begin to take OTA updates. Your boot loader is locked again, you are not rooted, TWRP is gone and you have a stock UK European version FRD-L19 in your hands.
BLClark said:
I converted two mint FRD-AL10 to FRD-L19 versions yesterday. They have since both taken OTA updates over WiFi. One is at FRDL19C432B360 and the other took an additional update to FRDL19C432B380. I am in the Western United States, the phones know they are here too, but believe they are destined for Europe. When I take a local call, a +1 automatically shows up in front of the number on the call log. When I browse to Yahoo the phone goes to the Yahoo United Kingdom and Ireland home page. The FRD-AL10 phones were both at EMUI 5.0 and Android 7.0 and still at EMUI 5.0 and Android 7.0 after being rebranded to FRD-L19 UK. Everything works including dual SIMs. There is no remnant of Chinese apps, no pinyin characters anywhere. There are absolutely no problems. You do not need to root your phone with this method and you will end up with factory new like European firmware load.
Search these forums and obtain the following files:
Huwaei USB Drivers
DC Unlocker client
Minimal ADB and Fastboot
TWRP-3.1.1-1-frd.img
Honor%208_Rollback%20Package_FRD-L19_from%20Android%207.0%20EMUI%205.0%20to%20Android%206.0%20EMUI%204.1_C900B300_UK.rar
FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip
Format an SDXD memory card. Make sure it is class 10 speed.
Unarchive the rollback package and copy the entire dload folder to the SD card root directory.
Copy FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip to the SD card root folder.
Install the Huwaei USB drivers on your PC and phone.
Install DC Unlocker client on your phone.
Install Minimal ADB and Fastboot on your PC.
Copy twrp-3.1.1-1-frd.img into the Minimal ADB and Fastboot folder.
Enable USB debugging on your phone. Enter the system app and tap your build number 5 times and the developer mode becomes available.
In developer mode enable USB debugging and if OEM unlock is there, turn it on. It will likely not be there on the Chinese version, so if you don't see OEM unlock don't worry.
Accept the USB prompts on your phone. Reject communication with Huwaei Suite, Huwaei App, etc., and close them.
Follow the DC Unlocker instructions, buy credit with PayPal, and write down the bootloader code when you see it.
Unlock the bootloader. Open a command prompt in the Minimal ADB and Fastboot folder.
Enter
adb devices
The response should return the serial number of your phone proving USB communication
Enter
adb reboot bootloader
Your phone should now display the fastboot recovery screen
Enter
fastboot devices
The response should return the serial number of your phone
Enter
fastboot OEM unlock [your boot code here]
Your phone will factory reset and is now unlocked. Power down and reboot the phone.
Go to system app, developer, and turn on USB debugging, as before accept USB prompts, and reject and close Huwaei apps.
Open a command prompt in the Minimal ADB and Fastboot folder.
Enter
adb devices
Enter
adb reboot bootloader
The phone should now once again be at the fastboot recovery screen
Enter
fastboot devices
If your phone’s serial number is returned, you have communication.
Now install TWRP.
Enter
fastboot flash recovery twrp-3.1.1-1-frd.img
When the flash writing is done install the SD card and enter
flashboot reboot
Hold down the volume up and power buttons as the phone boots up, you can release the power button at the blue honor screen, but continue to hold down the volume up until you see TWRP.
Tap the install button
Tap Select storage and select the SD card.
Select the FRD-L19C432B131-hw-eu-OPU_TWRP_FRD.zip file and swipe to flash.
When the flashing is done, your oem.info has been changed to Europe.
Select reboot to system.
Hold down volume up, volume down and power simultaneously while it reboots, continue to hold until the phone is in Huwaei erecovery mode.
Erecovery will force the phone to install the update.app file in the dload folder from the sd card. It will take several minutes.
When complete let the phone reboot on its own and hookup WiFi, enable USB debugging and let Huwaei apps hookup. Your phone will appear to be a legitimate European model to the network and will immediately begin to take OTA updates. Your boot loader is locked again, you are not rooted, TWRP is gone and you have a stock UK European version FRD-L19 in your hands.
Click to expand...
Click to collapse
I was really impressed for your comment ,really you explained each and every step .
Also i had a rebranding thread for frdl19 https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
venugopalu007 i dont have twrp and my phone version is al10
BLClark thank you for god guide, bat i can,t do it..... because install twrp or something and turn system on is not possible
At the moment i want only turn on my phone ;/
Mysia said:
venugopalu007 i dont have twrp and my phone version is al10
BLClark thank you for god guide, bat i can,t do it..... because install twrp or something and turn system on is not possible
At the moment i want only turn on my phone ;/
Click to expand...
Click to collapse
Flash the twrp https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
And it will works , my friend has same problem ,i sorted out for him , it s very hard process if your device is not charging
I do it all before bricked Now i can't repeat install twrp because i can't turn on my system
Now i can't install twrp in fastboot mode.
Mysia said:
I do it all before bricked Now i can't repeat install twrp because i can't turn on my system
Now i can't install twrp in fastboot mode.
Click to expand...
Click to collapse
try to relock and unlock bootloader again
how? this instruction is for running system.
I must install anything only in fastboot&rescue mode
Mysia said:
how? this instruction is for running system.
I must install anything only in fastboot&rescue mode
Click to expand...
Click to collapse
can you please be more clear!
ok , little succes. I rollbacked and install FRD-C00B135 by dload folder. (its chineese Marshmallow)
Next i need install european nougat for my AL-10
Any suggestions?
Mysia said:
ok , little succes. I rollbacked and install FRD-C00B135 by dload folder. (its chineese Marshmallow)
Next i need install european nougat for my AL-10
Any suggestions?
Click to expand...
Click to collapse
how did you u ?have to rebrand to install europen nougat
BLClark said:
I converted two mint FRD-AL10 to FRD-L19 versions yesterday. They have since both taken OTA updates over WiFi. One is at FRDL19C432B360 and the other took an additional update to FRDL19C432B380.nds.
Click to expand...
Click to collapse
really impressive about ur comment. But can u please tell me how to update to B380? I can only update to B360 and check OTA is no update
I had a Chinese version DL00 -> already rebrand to L19 by venugopan method
TheHunterVN said:
really impressive about ur comment. But can u please tell me how to update to B380? I can only update to B360 and check OTA is no update
I had a Chinese version DL00 -> already rebrand to L19 by venugopan method
Click to expand...
Click to collapse
try a reset and chech the updater app (download and install full package )
venugopalu007 said:
try a reset and chech the updater app (download and install full package )
Click to expand...
Click to collapse
cant bro, many times
TheHunterVN said:
cant bro, many times
Click to expand...
Click to collapse
wait for the update or make a full back and try the firmware finder firmwares , may be with some luck also
EMUI 5 and higher Encryts the Phone
Mysia said:
At The first i wanted sorry for by not good english.
Today i unlocked bootloader and rooted my honor 8 al10(china version)
Then I wanted to change firmware version to europe.
When i used the SRKtool and choose option ""change to oeminfo and custom.bin-EU<L09-C432> "" my phone restarted and show info about damage system and recommended wipe.
Then the system stopped working. My TWRP has been deleted. My rom C00B387 is not available for download.
I downloaded C00B135 and tried:
restore system using the Volume+ , Volume- and power button from dload folder
separate boot, recovery and system.img by HuaweiUpdateExtractor and install used ADB in fastboot mode
install only TWRP
used system eRecovery repair rom using wifi, but it happened fast failed
All method not working
I have a little experience with samsung and sony. Honor 8 is my first Huawei phone
Please help me, I very need working phone
Please write to me in simple words
I hope you will help me because fastboot works
Click to expand...
Click to collapse
It looks like you are trying to flash a stock recovery cn.img
If you are at EMUI 5 and I think you are, use the twrp-3.1.1-1-frd.img
It will decrypt the encryption. Other recovery images here cannot decrypt and you must reformat the data partion to use them with EMUI 5. Also, if you root use the SuperSU vesion available from these forums specifically for use with EMUI 5 in the file name. Search for it. Again encryption is involved.
If you can get into fastboot you can fix it. At the bottom of the fastboot screen it should say phone unlocked. If it says locked you will need to unlock the bootloader again.
Always make sure you have USB communication between fastboot and the phone. For some reason Huwaei phones will sometimes disable USB debugging with power down and power up. You need to check each time.
BLClark said:
It looks like you are trying to flash a stock recovery cn.img
If you are at EMUI 5 and I think you are, use the twrp-3.1.1-1-frd.img
It will decrypt the encryption. Other recovery images here cannot decrypt and you must reformat the data partion to use them with EMUI 5. Also, if you root use the SuperSU vesion available from these forums specifically for use with EMUI 5 in the file name. Search for it. Again encryption is involved.
If you can get into fastboot you can fix it. At the bottom of the fastboot screen it should say phone unlocked. If it says locked you will need to unlock the bootloader again.
Always make sure you have U
I think my oeminfo changed succes from CN to EU
Before reunlock bootloader i haved vendor-hw and country-EU
At the moment i Have chineese room emui 4.1 C00B135(marshmallow) . After reunlock bootloader and install twrp 3020(chinese or english language) i lost my Vendor and country info(file not exist)
Not exist vendor and country is no problem?
Which version europe nougat will be stable for my CHINESE AL10?
Can i install rom in one step by TWRP?
Click to expand...
Click to collapse
Rollback to EMUI 4.1 C900B300 UK
Search for EMUI 4.1_C900B300, find and use the update.app in this file
Honor%208_Rollback%20Package_FRD-L19_from%20Android%207.0%20EMUI%205.0%20to%20Android%206.0%20EMUI%204.1_C900B300_UK.rar
This is the official Huwaei FRD-L19 rollback package. It rolls your firmware back to the first UK European release of the FRD-L19. It is a full firmware load and will replace everything.
If you get this on your phone, before erecovery is complete or immediately after, your phone will begin taking OTA updates and all will be fine.
If you can get into flashboot, you should be able to get into erecovery, put dload/update.app in the root folder of your sd card, hold volume up, volume down and power throughout bootup.
If erecovery fails the oem info on your phone is not set to europe. Find and install the MT Huwaei Multi-Tool version 7 from the MT forum. Use it to change your oem info and try erecovery again.
The Multi-Tool can do much more without the need to type individual lines of adb and fastboot commands. To run, you execute one of the .bat files in a command window. You will only have two command menu language choices, Russian or English. Choose ru.bat or en.bat accordingly. Try the menu commands without your phone plugged in first.
Thanks friend. I will try id after work. Today in night i tried install rollback(al19 UK) and romC432B131-UK downloaded by hihonor.com. Install by DLOAD folder not work :/ while i pressed three button Phone switch on and stop on (HONOR ON BLUE SCREEN). Install not opened why? Next i tried install only ROM by fastboot. All files install successfull, but recovery.img not work. (maybe file is damaged?) Finally i repeat installed successfull chinese marshmallow b135.
Anyone have good download link working Al19 rom for my AL10?
Sorry for my not good English and very low experience
Hello all,
First of all I looked for a (sub) forum for the Honor 6x BLN-L21, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my Honor 6X (BLN-L21 All model)...
The phone is running the stock B361 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last Month y (sep 24, 2017) there was an OTA update to B373 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B360, B371 and B373 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".
This adb server's $ADB_VENDOR_KEYS is not set"- is when your USB debugging is either not enabled or havent accepted the RSA keys. (faced this on ELIte v^)
FRP unlock comamnd wont work as your USB debugging is disabled and hence OEM unlock option is disabled as well.
Manually flashing any .img wont work as FRP is locked.
Only way to restore is dload or service center.
I have the same phone with exactly the same problem ......
any solution ????
aamszia said:
I have the same phone with exactly the same problem ......
any solution ????
Click to expand...
Click to collapse
Are you on stock rom or custom?
What are you trying and what is the result?
Build number?
What all you tried?
shashank1320 said:
Are you on stock rom or custom?
What are you trying and what is the result?
Build number?
What all you tried?
Click to expand...
Click to collapse
Well phone is repaired ( by Sigma KEY Fastboot flashing ) ( Update.app )
B361
First flashed " update_data_full_BLN-L21_hw_meafnaf.zip " by Fastboot
than update.zip ( 1.55 GB ) Dload by SDCARD ....
now its repaired ..
aamszia said:
Well phone is repaired ( by Sigma KEY Fastboot flashing ) ( Update.app )
B361
First flashed " update_data_full_BLN-L21_hw_meafnaf.zip " by Fastboot
than update.zip ( 1.55 GB ) Dload by SDCARD ....
now its repaired ..
Click to expand...
Click to collapse
i want to try this what command you use with the fastboot ? i have a bricked honor 6x andi think its the only thing i have not tried yet please help
i have not use any commands ..
i have used sigma key software .. ( PAID BOX ) ..
well we booted the phone up. we dloaded the firmware BLN-L21C432B360 for the european model. it booted up fine, but now shows nrdm90 teskeys and generic a15. he dloaded the data folder but still its on nrdm 90 test keys. any solution. or try b361 now? @shashank1320
Nithin.15 said:
well we booted the phone up. we dloaded the firmware BLN-L21C432B360 for the european model. it booted up fine, but now shows nrdm90 teskeys and generic a15. he dloaded the data folder but still its on nrdm 90 test keys. any solution. or try b361 now? @shashank1320
Click to expand...
Click to collapse
Ok. Now flash the oeminfo file for BLN-L21 and it will reset the phone with correct formware and device details.
shashank1320 said:
Ok. Now flash the oeminfo file for BLN-L21 and it will reset the phone with correct formware and device details.
Click to expand...
Click to collapse
well oeminfo or the data zip via dload ?
Nithin.15 said:
well oeminfo or the data zip via dload ?
Click to expand...
Click to collapse
Oeminfo via multi tool ir twrp.data file is for regaining the updater app, theme, clock etc but oeminfo will fix your issue of generic device or nrd-test keys.
shashank1320 said:
Oeminfo via multi tool ir twrp.data file is for regaining the updater app, theme, clock multi tool got it.
Click to expand...
Click to collapse
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
WARNING
By doing this you may lose your data, this is intended for when you have nowhere else to turn to.
Back Story
Hi All,
Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
After the installation, I tried to install a bunch of ROM's, I messed up a bit.
Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.
So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.
Ton of files in there, the files i just mentioned which are all .img files and some others.
In the end i needed several to get a perfect restore which has worked every single time without fail.
As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way Yaay, also what to do and where to obtain the firmwares from my experiences.
Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.
Good luck, any questions let me know. :good:
START HERE
*NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
They require an account to be made but besides that they were faster and had more choice.
Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...
Anyway, moving on........
FILES
At the foot of this guide is a link, inside it is everything you should require in order to complete this guide
ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)
IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
Move all of them after downloading to the ADB folder in C:\ADB
CACHE.img
CUST.img
ERECOVERY_RAMDI.img
KERNEL.img
RECOVERY_RAMDIS.img
USERDATA.img
VENDOR.img
SYSTEM.img
EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.
Pre-requisites
- A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
- A device variant of either L-09 or L-29 (others may work but i have not tested)
- A device variant of c432 (the 782 may work but i have not tested)
- Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
- Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
- I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
- A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can
GUIDE
On your computer / laptop
STEP 1 Download all the files from the mega link provided.
STEP 2 Copy the ADB Folder to the root of C: so it looks like this
C:\ADB
STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.
STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear
STEP 5 In the black window type the following:
cd c:\adb then press Enter
STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows
On your Phone
STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.
On your computer / laptop
Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img
*NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
You could then press the tab key and scroll through the files in the folder.
eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img
PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash userdata USERDATA.img
fastboot flash kernel KERNEL.img
fastboot flash vendor VENDOR.img
fastboot flash system SYSTEM.img
STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.
fastboot reboot
If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190
You can then root and use your device as you see fit.
Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN )
NOTE: they actually now have, sorry
https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg
Any questions, please ask away and i'll do what i can to help
c:\ADB>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (176429 KB)...
OKAY [ 4.121s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.130s
OEM is LOCKED
@mdda7
You must have an unlocked bootloader.
titi66200 said:
@mdda7
You must have an unlocked bootloader.
Click to expand...
Click to collapse
bootloader is unlocked
but
OEM is locked
mdda7 said:
bootloader is unlocked
but
OEM is locked
Click to expand...
Click to collapse
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
dladz said:
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
Click to expand...
Click to collapse
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
mdda7 said:
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
Click to expand...
Click to collapse
OEM unlocking needs to be off mate, 108 shouldn't matter but i believe that it's the version that has the OEM greyed out.
There is a way around it but i'm not sure.
any way?
mdda7 said:
any way?
Click to expand...
Click to collapse
Certainly not with this method as you don't meet the pre-requisites.
That being said I suppose some kind of low level flash tool may work, like i said before a paid for service maybe?
Lets find out everything there is to know.
So your bootloader is unlocked.
Have do you have TWRP installed?
Did any of the images i've listed actually flash successfully?
Have you tried to use eRecovery? or Hi Suite (neither of these worked for me hence this guide)
Beyond that i suppose the only way would be a paid service but their pre-requisites may be the same as mine. In that case I would say you're out of luck, afaik this guide is essentially the lowest you can go. I don't believe anything will work without OEM unlocking turned on.
How do you get onto the firmware you're currently on ? 108 and what state is the phone in right now?
What works? Whats accessible?
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
~clumsy~ said:
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
Click to expand...
Click to collapse
Haha no worries fella.
dladz said:
Haha no worries fella.
Click to expand...
Click to collapse
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
chrissyyyw said:
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
Click to expand...
Click to collapse
Weird. Not sure pal. This is what I did when I was stuck. Did you read everything and follow to the letter? A higher or same firmware?
On fastboot reboot the pc saying it's disconnected is correct. Should have come on.
Does anything ever come on screen?
Thank you, life saver!!
:good:
Johnny Eng said:
Thank you, life saver!!
Click to expand...
Click to collapse
You're very welcome Use the thanks button buddy :good:
dladz said:
:good:
You're very welcome Use the thanks button buddy :good:
Click to expand...
Click to collapse
Done buddy ?
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Johnny Eng said:
Done buddy
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Click to expand...
Click to collapse
Which FW version did you flash? I’ve got the same on .282
chrissyyyw said:
Which FW version did you flash? I’ve got the same on .282
Click to expand...
Click to collapse
As i'm still on 190 I wouldn't know this, but would it be possible that userdata isn't actually a part of the update app no more?
Seeing as it still works I would assume that is the case.
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
chrissyyyw said:
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
Click to expand...
Click to collapse
No because you're going to be picking them via fastboot anyway, I don't believe the name matters.
The ones in the update I used were not named like that IIRC.