Hi All,
Can someone guide me to relock the bootloader? I'm getting the error below.
FAILED (remote: root type is risk)
Thanks in advance.
Try the solution posted by FineFeather (post #15) in this thread: Problem re-lock bootloader (remote: root type is risk) - NXT-L09
Different Huawei phones, but the principle should be the same. Just make sure to use the stock recovery & stock rom of your phone's exact full model number.
Bit of a longer method posted here by DigiGoon for the Honor 7 (again, use a rom meant for your phone's exact full model only): https://forum.xda-developers.com/showpost.php?p=64227910&postcount=8
Related
Dear Owners of Redmi Note 3 (SnapDragon) !By results of my experience of the positive unlocking of two phones, I propose for you the full instruction for unlock of bootloader and flashing of custom recovery (twrp-3.0.2-1-kenzo.img). This Instruction was compiled from information in Internet. You can download Instruction and all required files by links:
Instruction (pdf file):
https://mega.nz/#!HAtkHKqA!Fmtgx24zvPH8mQ1EMwlr5GC3dO6iSBE6canBdvJhJPc
Files for unlocking (zip archive, 1.27 Gb):
https://mega.nz/#!fZVyACxD!4TEa-fpw0usemj-wwvIY2vYw85dHrYZYgmkwaBTo7wY
It's working! But:
"DO IT AT YOUR OWN RISK. I'm not responsible For warranty Void or Bricks Phones."
Is this the official method?
No
I brick my phone doing this and now i cant unbrick... When i conect to USB a red led still flashing like edl mode but my pc doesnt recognize him...
Rajdip said:
Is this the official method?
Click to expand...
Click to collapse
No, the only official way now is to request Unlock Permission from the Xiaomi team
- http://www.miui.com/unlock/
i have unlocked using this method from the original thread. works fine now rooted
- http://forum.xda-developers.com/redmi-note-3/how-to/redmi-note3-prokenzo-guiderom-global-t3341102
i think TS should give credit to original thread. thank you
i hardbrick my device using your instructions ((( It is no working for me (( how i restore my device??
error on miflash
(0x80004005: FAILED(remote: device is locked. Cannot flash images)
It's no official method. Official method is the request to Xiaomi. I used this method by using Win 7 for two phones which were on MIUI 7.1.7.0 Global . And method should be used on only 64-bit PC. There are a lot of problem due to improperly installed drivers on PC or/and due to mistakes in flashing process (not following of instructions). For unbrick I propose to try some methods from Internet (MIUI forum and other). If result will be absent then only test points will help you.
This post from black_jet
link: http://forum.xda-developers.com/red...ng-redmi-note3-hardbrickhs-usb-t3351325/page3
about unbrick by test points.
s_wheel said:
It's no official method. Official method is the request to Xiaomi. I used this method by using Win 7 for two phones which were on MIUI 7.1.7.0 Global . And method should be used on only 64-bit PC. There are a lot of problem due to improperly installed drivers on PC or/and due to mistakes in flashing process (not following of instructions). For unbrick I propose to try some methods from Internet (MIUI forum and other). If result will be absent then only test points will help you.
Click to expand...
Click to collapse
I unbrick with fastboot with: "fastboot oem unlock-go"
X-Genji said:
I unbrick with fastboot with: "fastboot oem unlock-go"
Click to expand...
Click to collapse
Congratulations!!
You had a soft brick only! It was as a result of "not follow of instruction".
Please, be careful for flashing of MIUI !!!
Backup your EFS guys. I lost mine and still looking for a redmi note 3 qcn file to recovery my network. lol
T-REX-XP said:
i hardbrick my device using your instructions ((( It is no working for me (( how i restore my device??
error on miflash
(0x80004005: FAILED(remote: device is locked. Cannot flash images)
Click to expand...
Click to collapse
Yep that what happened to me when I incorrectly flashed it.
I revived it using this method:
http://en.miui.com/thread-245347-1-1.html
It's actually pretty easy than it looks.
I followed your instructions and everything worked fine. If you get stuck in EDL Mode then boot to fastboot or Recovery and do a wipe.
Thank you a lot for this info.
The guy on Miui forums forgot a crucial part on his instructions and it was to enable OEM unlock. I failed twice when doing his tutorial and even hard bricked my phone. Lucky me I had the guts to test point it out from there.
With your instructions I finally did it and can remove this crappy, horrible iOS ripoff that is MIUI.
Also I'll start to give some kernel love to this phone very shortly.
Regards.
T-REX-XP said:
i hardbrick my device using your instructions ((( It is no working for me (( how i restore my device??
error on miflash
(0x80004005: FAILED(remote: device is locked. Cannot flash images)
Click to expand...
Click to collapse
had you enable OEM Unlock ?
X-Genji said:
I unbrick with fastboot with: "fastboot oem unlock-go"
Click to expand...
Click to collapse
You are a life saver!
T-REX-XP said:
i hardbrick my device using your instructions ((( It is no working for me (( how i restore my device??
error on miflash
(0x80004005: FAILED(remote: device is locked. Cannot flash images)
Click to expand...
Click to collapse
Me too
Any help?
Now I can´t even get to recovery or EDL screens. I only got Mi Logo bootloop
I can get fastboot access holding down Vol "-" + Power button (after holding the two buttons two times!. The first one I have a fastboot screen and inmediatly bootlop. The second time always work)
I also tried the "oem unclock-go":
d:\Android\android-sdk-windows\platform-tools>fastboot oem unlock-go
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.009s
Is there somehow I can RE-lock the bootloader, UN-root my mate 8 - L09 and reset everything like it was when it was new?
edit:
This is what I have done until now.
- flashed to stock recovery (phone is not rooted any more)
- factory reset
Then when I try to relock the the bootloader , I get message FAILED (remote: root type is risk)
fastboot oem relock ****************
...
FAILED (remote: root type is risk)
finished. total time: 0.970s
Someone know how to resolve this issue?
Could this be fixed by installing fresh and untouched complete firmware from huawei?
If yes, some know which link to use for my device and version?
Model number: HUAWEI NXT-L09
Buld number: NXT-L09C432B152
All help is highly apprechiated.
Can someone please delete this thread - I created a new thread in the troubleshooting section.
http://forum.xda-developers.com/mate-8/help/problem-lock-bootloader-remote-root-t3363216
Hi all
I searched this, but I question here,
1 - When you unroot , put stock and update an ota, it blocks the bootloader?
2 - and the when unlocked, format all to factory?
3 - In what moment the bootloader is blocked? only when first unlock is done?
Thanks in advance, I have an honor 7 and I Know how it works, but this honor 8 L09?
1. probably
2. u can prevent factory reset if unlocked earlier
3. idk what the question means
LastStandingDroid said:
1. probably
2. u can prevent factory reset if unlocked earlier
3. idk what the question means
Click to expand...
Click to collapse
3 - well, the main question is if in every ota update , it locks the boootloader and when unlock, format all ...this is the main question
in honor 7, I unroot, apply the ota and root again with no problems
sorry for my english
deadko said:
3 - well, the main question is if in every ota update , it locks the boootloader and when unlock, format all ...this is the main question
in honor 7, I unroot, apply the ota and root again with no problems
sorry for my english
Click to expand...
Click to collapse
lock bootloader i can't tell, if it does u can unlock the bootloader and again, and straight after flash TWRP it won't wipe the internal SD
Hi. bought an al-10 from china which apparently is flashed. There are a few things not working on phone so apart from trying to get help from seller, i have attempted the flashing myself. i have gone thru a few threads and watched TK vid on flashing twrp and rooting and roni on unlocking bootloader. now, considering the device is flashed i understand the bootloader is still unlocked (in fastboot says phone unlocked). in dev options there is no OEM unlocking option. i cannot get lock state through the code in dialler. when i try to flash twrp, sending recovery OKAY, writing recovery FAILED <remote: command not allowed> so cannot really get to rooting stage
Thank you for the time.
ptwarecki said:
Hi. bought an al-10 from china which apparently is flashed. There are a few things not working on phone so apart from trying to get help from seller, i have attempted the flashing myself. i have gone thru a few threads and watched TK vid on flashing twrp and rooting and roni on unlocking bootloader. now, considering the device is flashed i understand the bootloader is still unlocked (in fastboot says phone unlocked). in dev options there is no OEM unlocking option. i cannot get lock state through the code in dialler. when i try to flash twrp, sending recovery OKAY, writing recovery FAILED <remote: command not allowed> so cannot really get to rooting stage
Thank you for the time.
Click to expand...
Click to collapse
And the device is? Did u use fastboot flash recovery recovery.img
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
And the device is? Did u use fastboot flash recovery recovery.img
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Hi.
Sorry device is honor 8 frd-al10.
It was fastboot flash recovery twrp_cn.img
I have just received a message from seller stating it was flashed with eu firmware. I have it as frd c900b120. Should i be using the image for FRD-L09 or FRD-L19 in this case ?
Thank you.
Hi all
I'm stuck installing TWRP. I found several posts about it, but I'm not sure if they will be working for my version. I have a A2017G on B06. So:
I tried backing up stock boot and recovery with axon7backup, but the files are way bigger and (of course) have a different MD5sum as the ones found in the stock update of B06 ZTE Germany provides. Is "axon7backup" supported for A2017G B06? If so, can you provide me a link of "axon7root" or is the one for A2017G B03 working?
Can I use twrp-3.0.2-2-a2017u.img for A2017G?
If found somewhere "oem unlock" or "flashing unlock" should work in fastboot made. Fastboot finds the device, but both commands result in "FAILED (remote: unknown command)". OEM unlock is enabled in development settings. So I guess this doesn't work for A2017G B06, but I can't seem to find what is.
Sorry for the newbie questions. Hope anyway is willing to help me out. Thnx!
If I am not mistaken, only the US model has the opportunity to get the bootloader unlocked, but don't quote me on that. With the US models, you have to submit an unlock request in order to even try to unlock the booloader.
Hi, I have Asia-Pacific version of the Huawei Mediapad M3 (BTV-W09C209B005). I'm trying to flash TWRP to gain root access, but I'm encountering problems in the preliminary stage. I've searched for similar problems in the forum, but couldn't find a solution that works for me.
So here are the steps I've done:
1. I received the official bootloader code from Huawei.
2. I used ADB and Fastboot to unlock the bootloader, but I noticed something peculiar: the screen says
Phone UNLOCKED
FRP UNLOCKED
I am the first owner of the tablet, so I was surprised to see that it was already unlocked. In any case, I tried the fastboot oem unlock command, and it returned this error:
FAILED (remote: password wrong)
3. I tried to proceed to TWRP flash on the assumption that the phone was already unlocked. But I get this error:
sending 'recovery' (23794 KB)....
OKAY [ 0.740s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished, total time: 0.740s
4. I tried relocking the bootloader, as per several XDA threads, before unlocking again. But I once again encounter an error:
FAILED (remote: stat not match)
I already contacted Huawei to make sure that the unlock code they sent me was correct, but I doubt that it'd be wrong because they probably just paste it after generating it in the system.
Any ideas how to proceed?
Interesting, first off if you want to check and see if you phone is BL is unlocked go to Settings, Developer Options and see if your OEM unlocking is grayed or doesn't move..if it doesn't move or grayed out then it's unlocked.. if it moves the it not unlocked.. check that your fastboot /adb are set up correctly. Though the easiest way to this ( unlocking the BL and flashng TWRP) would be to get Huawei Multi-Tool v8 by Team MT and use it,, ( grab the one in the Honor 8, as I know it does work) and make sure you ave the correct TWRP for your tablet..
lilbrat said:
Interesting, first off if you want to check and see if you phone is BL is unlocked go to Settings, Developer Options and see if your OEM unlocking is grayed or doesn't move..if it doesn't move or grayed out then it's unlocked.. if it moves the it not unlocked.. check that your fastboot /adb are set up correctly. Though the easiest way to this ( unlocking the BL and flashng TWRP) would be to get Huawei Multi-Tool v8 by Team MT and use it,, ( grab the one in the Honor 8, as I know it does work) and make sure you ave the correct TWRP for your tablet..
Click to expand...
Click to collapse
Thanks for pointing me the Huawei multi-tool. So I tried that, and as suspected, the device is still locked. I am able to toggle the OEM unlocking and the tool says so through the lock status (oem lock-state info LOCKED). I proceeded unlocking with the tool, but I received the same error: FAILED (remote: password wrong)
The unlock code doesn't seem to be the problem because the tool displayed the corresponding serial number and it was a match. So there's something preventing me from unlocking the bootloader--it's probably the same reason why the fastboot says "PHONE Unlocked" even though it actually isn't. Again, I can't do the relock trick because the device wouldn't accept the Huwei unlock code.
Thoughts?
Hmm, why do some of these seem to be so picky when it comes to unlocking.. The multi too will copy what ever code you but in, sorry for the questions just trying to help narrow it down.. in the developer section there are 3 things that need to be ticked,, OEM unlocking, USB debugging and and allow ADB debugging in charge only mode.. Maybe you software got out of wack.. read here ( https://forum.xda-developers.com/mediapad-m3/help/bricked-mediapad-m3-t3746893) as it may help.. Not sure if HiSuite can restore it.
OEM unlocking and USB debugging are "working" in the sense that I can send commands from the PC via USB. It's just that I can't properly unlock the phone. I updated the drivers to see if that's the problem, but I still encounter the same error. I basically couldn't move forward with the link you sent because the first step was to unlock the device and I couldn't get past that. When I try to unlock the error is still 'FAILED (remote: password wrong)'.
I've seen some threads from other Huawei devices that suggest rolling back the firmware, but this is the first time I'm trying to root this device. And it's still on Marshmallow, which is the version that came with the first release of the Mediapad M3, so basically there's nothing to roll back to.
Why not upgrade to 7 as that is where most of the newer threads are written for plus it will redo your boot loader... giving you a clean slate to work with..and that might be your issue..
I can't update to 7 because Huawei stopped providing updates for my region. I failed to mention that the reason why I'm trying to unlock the device is to change the region and upgrade to 7.
May I ask where you are?
From Southeast Asia, but the tablet was imported from China. I planned to convert it to the European version so I can at least upgrade to Nougat. I'm still stuck though.
So Huawei sent me a new unlock key and it works! Problem solved!
cescpistol said:
From Southeast Asia, but the tablet was imported from China. I planned to convert it to the European version so I can at least upgrade to Nougat. I'm still stuck though.
Click to expand...
Click to collapse
Imy model also seas... Has updated to nougat without changging to us.