i use Emui 9 9.0.1.158 in my mate9
try full wipe and after 26% failed, try relock bootloader and no go too
C:\adb>fastboot oem relock ..........
...
FAILED (remote: root type is risk)
finished. total time: 0.009s
device starts turn on ok but no possible format and no relock bootloader.
why ??
???????
Go back to emui 8 by hisuite and then relock bootloader.
Nextstar said:
Go back to emui 8 by hisuite and then relock bootloader.
Click to expand...
Click to collapse
hisuite no back options emui 9 for 8 here
Related
Hello Everybody,
I Have NXT-L29C185, just updated to B320 with dload method then I unlocked the bootloader.
When I flashed TWRP through fastboot, it gave me this error
sending 'recovery' (17280 KB)...
OKAY [ 0.370s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.401s
Click to expand...
Click to collapse
in the Bootlader screen, there is "Phone Unlocked" and "FRP Lock"
Please Help me to flash TWRP
Thank you
Monc3f said:
Hello Everybody,
I Have NXT-L29C185, just updated to B320 with dload method then I unlocked the bootloader.
When I flashed TWRP through fastboot, it gave me this error
in the Bootlader screen, there is "Phone Unlocked" and "FRP Lock"
Please Help me to flash TWRP
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/mate-8/general/guide-how-to-unlock-frp-free-t3388810
hamadazh said:
http://forum.xda-developers.com/mate-8/general/guide-how-to-unlock-frp-free-t3388810
Click to expand...
Click to collapse
it WORKS :highfive: thank you
Monc3f said:
Hello Everybody,
I Have NXT-L29C185, just updated to B320 with dload method then I unlocked the bootloader.
When I flashed TWRP through fastboot, it gave me this error
in the Bootlader screen, there is "Phone Unlocked" and "FRP Lock"
Please Help me to flash TWRP
Thank you
Click to expand...
Click to collapse
Hey where did u get the update file for L29C185B320
So I've pretty much hit a wall. I have unlocked bootoader, and everytime I try to enter into factory resetting via volume + power button, it'll boot into "your device is booting now..." and it'll stay there. Same thing if I try to do it via the settings.
Whenever I try to install custom recovery or anything, I get this message.
C:\adb>fastboot flash recovery TWRP-CN.img
target reported max download size of 471859200 bytes
sending 'recovery' (29218 KB)...
OKAY [ 0.789s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.804s
I've tried all sorts of twrp files. My phone has locked me out of changing anything from adb commands it seems. How do I fix this?
My FRP is also locked, if that matters. I've tried to delete all accounts from my phone, as well as the "find my phone" option.
I'm on Anroid 7, EMUI 5.
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot devices
73QDU16B22001173 fastboot
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (remote: Command not allowed)
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format cache
FAILED (remote: Command not allowed)
OEM is greyed out in the developer settings, I can't activate it or decative.
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
TomboIa said:
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
Click to expand...
Click to collapse
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Zebieok said:
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Click to expand...
Click to collapse
Dont share your unlock key here, and are you sure that was your bootloader unlock keys.
Frp lock means your bootloader is locked.
FRP lock is a security action, for remove them you must boot a device and remove all google accounts.
Unfortunately this casw happened to me, when i want factory reset my phone, his dead and i cant boot it again just fastboot work but FRP LOCK activate and i cant flash any thing, give error command not allowed, in last i have to go to repair services, and they do this with hard box (maybe chimera or sigma.. Or other).
If you can boot your device you can do any thing, but if your device get bootloop go to services center.
im getting this error after trying to unlock the bootloader . my device is 6045I
C:\Users\Oscar\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x1bbb oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.003s
any of you know how to solve. ?
my main problem is that due to install a theme i lost my camera. the main camera dont work. i made a factory reset without results.
my next steps is trying to install TWRP to flash a clean installation of the ROM but im stucked at unlocking the bootloader
PS: Also if anyone know how to solve the camera error thanks in advance
you can't unlock bl with MM. you have to downgrade to LL to restore fastboot command.
search on this forum for more info.
no more idol3 for me.
murigny64 said:
you can't unlock bl with MM. you have to downgrade to LL to restore fastboot command.
search on this forum for more info.
no more idol3 for me.
Click to expand...
Click to collapse
thanks
I can`t unlock bootloader, I get the following error:
FAILED (remote: Command not allowed)
finished. total time: 0.018s
Phone relocked. FRP Lock. Can't boot normally. Stuck in eRecovery or in bootloader mode.
dj_adri said:
I can`t unlock bootloader, I get the following error:
FAILED (remote: Command not allowed)
finished. total time: 0.018s
Phone relocked. FRP Lock. Can't boot normally. Stuck in eRecovery or in bootloader mode.
Click to expand...
Click to collapse
Unfortunately, because of the FRP lock, is what is causing the commands to fail.
Were you doing anything prior to trying to unlock the bootloader?
What model do you have?
dj_adri said:
I can`t unlock bootloader, I get the following error:
FAILED (remote: Command not allowed)
finished. total time: 0.018s
Phone relocked. FRP Lock. Can't boot normally. Stuck in eRecovery or in bootloader mode.
Click to expand...
Click to collapse
you must logout huawei id before unlock bootloader
ccchill said:
you must logout huawei id before unlock bootloader
Click to expand...
Click to collapse
How do I do it? The phone is in bootloop
Wirmpolter said:
Unfortunately, because of the FRP lock, is what is causing the commands to fail.
Were you doing anything prior to trying to unlock the bootloader?
What model do you have?
Click to expand...
Click to collapse
MHA-L09C02 but is rebranded to mha-l29c432b363. I close the bootloader because i flash xposed and the phone entered to bootloop, I could have closed it but now I can not open it.
Have you solve it? Unfortunatelly i have the same issue:crying:
dj_adri said:
MHA-L09C02 but is rebranded to mha-l29c432b363. I close the bootloader because i flash xposed and the phone entered to bootloop, I could have closed it but now I can not open it.
Click to expand...
Click to collapse
Yeah, seems xposed causes this type of issue for everyone I've heard who tries to install it.
Can you still get into erecovery?
Icaxus said:
Have you solve it? Unfortunatelly i have the same issue:crying:
Click to expand...
Click to collapse
Yes, this is the only solution without pay:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
I was on Android 9.1, used magisk etc.. so phone was rooted everything fine... Now I updated to Android 10 Emui 10, and I have two problems...
1. USB debug option somehow turn of in developer options... Buttnon turn off auto, after I exit from options. I treied restore defaults and activated again but same.. Never mind, i see phone in adb devices and fastboot devices... Maybe is just cosmetics problem...
2. Main problem is that now I cant "fastboot flash recovery_ramdisk magisk_patched.img", because it says...
Sending 'recovery_ramdisk' (27442 KB) OKAY [ 0.613s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Someone says that after phone is updated he has hat same problem and he Re-locked bootloader and it was fine after that...
In bootloader screen my phone says PHONE UNLOCKED and FRP UNLOCK... so everything is fine... Also oem unlock is enabled in developer options...
How I can solve this? Does the option to re-lock bootloader erase my data and turn to factory reset... And how to do this...
Please give me solutions... with detail commands.. If it possible just not to factory reset and lost my data...
Thanks...
Sorry! I think, you found out, that EMUI10 in not rootable.