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
Related
Solved.
AL10, NXT-C900B133, rescue0.3, NEXT
I unlocked bootloader, installed TWRP, and rooted using SuperSU with no problem by following these directions:
http://forum.xda-developers.com/mate-8/general/guide-unlock-bootloader-root-install-t3301371
I then formatted data using TWRP wipe, then tried to install Stock Rooted No Encrypted Boot from
http://forum.xda-developers.com/mate-8/development/rom-stock-rooted-encrypted-boot-t3303606
The phone never gets past "...unlocked...booting now...." (I did not install insecure_boot because I had trouble finding it---it is not in Mate 8 Android Development, only in Mate 8 Original Android Development.)
I can get to fastboot and to the Huawei recovery in Chinese (which doesn't work---wifi downloading stops with an exclamation point), but TWRP is gone, and I can't get it back by reflashing it. I've tried HiSuite recovery, unbricking using the Italian knife following these instructions:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
with various roms, and I've tried force flashing an UPDATE.APP from /sdcard/dload. No joy.
I caused the problem by installing a B331 rom when I was at B133—dyslexic much? Once I got TWRP back, flashing a B180 rom worked fine.
The difficulty was getting TWRP back. To do that, I flashed the following files using fastboot—it may be overkill:
TWRP-2.8.7.0-ENG.img,
insecure_boot_b331.img,
and the files in
L29Fastboot.rar.
TWRP
Hey ho!
I had exactly the same problem yesterday.
I figured out my system only was able to boot when I hold down [vol-]&[power].
Then the "not trusted message" had a few more lines and the phone booted up.
When it's up again, you can use adb to reboot to fastboot: adb reboot bootloader
You can also try to go directly to recovery if you alrteady flashed it: adb reboot recovery
From threre you can try again.
btw: I had to use a complete different TWRP version. 3.x somewhat. I think it was from here: http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
Info: I was NOT able to use [vol+]&[power] for Recovery, eRecovery or anything else. I was just stuck.
I hope it helps.
I recommend after getting your device back on track to use twrp to make a recovery on your microsd card. That way u have a sure chance of getting bwck to working order
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
iAngus said:
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
Click to expand...
Click to collapse
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Click to expand...
Click to collapse
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
iAngus said:
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
Click to expand...
Click to collapse
you could fix the same problem I have is not to do help me
Hallo everybody!
I'm on stock ROM NXT-L29C432B192 and since yesterday my Mate 8 is proposing the new Rom B560.
I installed TWRP and rooted my phone, besides I left the bootloader unlocked.
Since I no longer have the stock recovery, it's impossible to install the Rom update, that's why I'm trying to return to the stock recovery.
I used the thailand tool (I also used to upgrade to B192 on december) to restore the recovery: it seems to work as it copies files on the device, but at the end of the copy the phone stays on bootloader mode and the tool on a "waiting for device" state. If I reboot the phone, TWRP is still there.
I tried the "manual" way upgrading ADB drivers and using minimal-adb files, but while the command "adb devices" reports my device in an "offline" status, the "fastboot devices" reports nothing.
Obviously I activated the USB debug on the phone ...
Any suggestion? What am I doing wrong or forgetting about?
Many thanks,
Enrico
Do you reboot in Twrp and type fastboot devices or in Bootloader?
I managed to download recent "Minimal ADB and Fastboot" files that show my device no more as offline, but when I reboot in Fastboot&Rescue Mode my device is no longer visible and the command "fastboot devices" returns nothing ... if I try the command "fastboot flash recovery recovery.img" it says "waiting for any device" while my device is on Fastboot mode and connected. USB Debug is activated and re-authorized from scratch ...
letschky said:
Do you reboot in Twrp and type fastboot devices or in Bootloader?
Click to expand...
Click to collapse
In Bootloader ...
Go in your Pc to the Devicemanager and looking the Driver.I thinky you use the wrong Driver,the right name is the name with sooner bla bla bla...
You can change the Driver manually in Devicemanager,named Android sooner .....
I hope you understand my bad english,sorry
letschky said:
Do you reboot in Twrp and type fastboot devices or in Bootloader?
Click to expand...
Click to collapse
letschky said:
Go in your Pc to the Devicemanager and looking the Driver.I thinky you use the wrong Driver,the right name is the name with sooner bla bla bla...
You can change the Driver manually in Devicemanager,named Android sooner .....
I hope you understand my bad english,sorry
Click to expand...
Click to collapse
Thank you, that's probably the reason, anyway I meanwhile solved by using my Mac instead of my PC ... as always ...
Now I've the stock recovery, but the update process starts and then (around 25%)reports an error and I have to reboot and download the whole update again ... and again ... and again ... I'm stuck there now ...
Anyone else had this update problem?
What you want,Update to Nougat B560 from B192?
letschky said:
What you want,Update to Nougat B560 from B192?
Click to expand...
Click to collapse
Yes, that's what I want: upgrade from B192 to B560.
I also extracted RECOVERY.img from B560 UPDATE file and installed it through fastboot.
My mate 8 downloads the update, reboot to install it and stay stuck on the "your device is unlocked so cannot be trusted - bla bla bla - booting now".
I have to reboot several times (volume down + power) to have it restarting ... on B192, of course ...
Factory Reset?
So, now you are on B192 rom with B560 stock recovery?
You have to flash B192 stock recovery if you want to update to B560.
Let me know...
konroma said:
So, now you are on B192 rom with B560 stock recovery?
You have to flash B192 stock recovery if you want to update to B560.
Let me know...
Click to expand...
Click to collapse
Great! That solved my problem: so, if you need to upgrade you have to first install the recovery coming from your actual version! That's crazy, it cannot be an earlier recovery or a more recent one, it has to be that one!
Thank you all for the precious suggestions.
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
Hello everyone,
I bought a brand new FDR-L14 in the US and brought it to my country Argentina. After a few days the phone's WiFi died while i was downloading Nougat via regular EMUI updater. I finished downloading the remaining 5% using the data package and booted with the new android version with no issues aside from still not having WiFi. This is not a wifi signal issue since i just cannot turn it on. I read in a forum that maybe if i downgraded back to MM the Wifi issue could be solved. So this is what i did:
1. Downloaded the Rollback Package from the Honor site
2. Downloaded an full MM from Firmware Finder for the FDR-L14 version. The one listed in the support section of the Honor US site is for the L04 version.
3. Successfully ran the rollback package via DLOAD method (SD Card + 3 button method)
4. Successfully installed the MM version via DLOAD method (SD Card + 3 button method)
After this i booted normally but still no Wifi and this is where i messed up:
Instead of updating to Nougat using HICare (since i didn't have Wifi) i tried to force another update using DLOAD with Nougat. The update failed at 5% and i started to panic, so i also ran the rollback package successfully via DLOAD with no issues. After that, the phone just bricked : it stays at the blue screen with the logo forever.
So this is the current situation:
- No debugging enabled so i cannot unlock via fastboot.
- Both FRP and Bootloader Locked
- 3 button method doesn't work: Tried to activate it with the rollback package and 3 other update packages. It just doesn't work anymore.
- Fastboot works fine and I'm able to list the device while connected to a PC by running "fastboot devices" in CMD. The only problem is that since everything is locked i cannot flash any images or recovery.
- Recovery doesn't work either (Power and Volume Up)
- The cost of sending the phone back to the US is probably half the phone's price
- The warranty isn't valid here.
Is there something i can do to unbrick it? Ive been browsing the forums for 3 days and couldn't find anything aside from maybe trying to reflash an image using DC-Phoenix.
Any help is greatly appreciated!
vaya faena amigo, ya es mala suerte
what a mess
Any ideas? Im in a dead end here
Bump cause still in the same situation. Would appreciate any help!
XAsprosX said:
Bump cause still in the same situation. Would appreciate any help!
Click to expand...
Click to collapse
whoa! this makes 2 of us! i would also appreciate some help.
You said your fastboot works, did you try to flash the update.app using adb?
Saeem said:
You said your fastboot works, did you try to flash the update.app using adb?
Click to expand...
Click to collapse
ADB Commands are not allowed and cannot even Flash using flashboot because USB Debugging was disabled when it bricked.
XAsprosX said:
ADB Commands are not allowed and cannot even Flash using flashboot because USB Debugging was disabled when it bricked.
Click to expand...
Click to collapse
You said you can boot your device to fastboot mode then why aren't you allowed to flash anything in fastboot using ADB? As Much as I know you don't in fastboot mode it doesn't matter if USB debugging is turned on or off.
Saeem said:
You said you can boot your device to fastboot mode then why aren't you allowed to flash anything in fastboot using ADB? As Much as I know you don't in fastboot mode it doesn't matter if USB debugging is turned on or off.
Click to expand...
Click to collapse
With Bootloader and FRP Locked and no debug mode you cannot run any fastboot commands that will alter the system. It gives an error saying "Remote: Command not allowed".
XAsprosX said:
With Bootloader and FRP Locked and no debug mode you cannot run any fastboot commands that will alter the system. It gives an error saying "Remote: Command not allowed".
Click to expand...
Click to collapse
I didn't know that. As much as I remember I was able to flash my Mate 7 without unlocking the FRP lock. Maybe @Rommco05 can help you a little..........
Rommco05 said:
phone is recognized in fastboot?
Click to expand...
Click to collapse
He says Yes but it shows some kind of foreign command. Don't you think something is not right with his ADB?
XAsprosX said:
Hello everyone,
I bought a brand new FDR-L14 in the US and brought it to my country Argentina. After a few days the phone's WiFi died while i was downloading Nougat via regular EMUI updater. I finished downloading the remaining 5% using the data package and booted with the new android version with no issues aside from still not having WiFi. This is not a wifi signal issue since i just cannot turn it on. I read in a forum that maybe if i downgraded back to MM the Wifi issue could be solved. So this is what i did:
1. Downloaded the Rollback Package from the Honor site
2. Downloaded an full MM from Firmware Finder for the FDR-L14 version. The one listed in the support section of the Honor US site is for the L04 version.
3. Successfully ran the rollback package via DLOAD method (SD Card + 3 button method)
4. Successfully installed the MM version via DLOAD method (SD Card + 3 button method)
After this i booted normally but still no Wifi and this is where i messed up:
Instead of updating to Nougat using HICare (since i didn't have Wifi) i tried to force another update using DLOAD with Nougat. The update failed at 5% and i started to panic, so i also ran the rollback package successfully via DLOAD with no issues. After that, the phone just bricked : it stays at the blue screen with the logo forever.
So this is the current situation:
- No debugging enabled so i cannot unlock via fastboot.
- Both FRP and Bootloader Locked
- 3 button method doesn't work: Tried to activate it with the rollback package and 3 other update packages. It just doesn't work anymore.
- Fastboot works fine and I'm able to list the device while connected to a PC by running "fastboot devices" in CMD. The only problem is that since everything is locked i cannot flash any images or recovery.
- Recovery doesn't work either (Power and Volume Up)
- The cost of sending the phone back to the US is probably half the phone's price
- The warranty isn't valid here.
Is there something i can do to unbrick it? Ive been browsing the forums for 3 days and couldn't find anything aside from maybe trying to reflash an image using DC-Phoenix.
Any help is greatly appreciated!
Click to expand...
Click to collapse
Did you fix it? I have the same problem
Same as title
Was changing the oeminfo.zip file and from then it did not work when i rebooted in fastboot. Please help. Used guide from shashank1320.
edit: can't seem to get into fastboot and even the recovery is not working- just says 'getting package info failed'.
edit: now able to get into fastboot and it says phone is locked but frp is unlocked
Bobbuu said:
Same as title
Was changing the oeminfo.zip file and from then it did not work when i rebooted in fastboot. Please help. Used guide from shashank1320.
edit: can't seem to get into fastboot and even the recovery is not working- just says 'getting package info failed'.
edit: now able to get into fastboot and it says phone is locked but frp is unlocked
Click to expand...
Click to collapse
Are you on EMUI 5 or 8? In fastboot connect phone to PC and in Command Prompt/Power Shell run command:
fastboot oem unlock <your15digitunlockcode>
After that phone Will factory reset. That should fix it. If it doesn't, well that's another problem.
Mannan Qamar said:
Are you on EMUI 5 or 8? In fastboot connect phone to PC and in Command Prompt/Power Shell run command:
fastboot oem unlock <your15digitunlockcode>
After that phone Will factory reset. That should fix it. If it doesn't, well that's another problem.
Click to expand...
Click to collapse
Thanks, this has been resolved using dload method. I had a update file on it that i wasnt aware of.
I couldnt do fastboot as phone was connected to pc but not shown?