Related
I bought a chinese Huawei Mate 8 NXT-DL00. It is now unlocked, thanks to DC-unlocker:good:
It communicates with adb, and reboots in bootloader. For some reason adb will not flash TWRP 3.0.2.0. (or any other TWRP). Is there a known TWRP for DL00 chinese, or is it the same as AL-10?
is FRP unlocked?
No, FRP is not unlocked now, but I have unlocked in on DC before. After reboot it shows locked message in bootloader.
I see now that you mention it that it's possible to have the FRP stay unlocked. Is that necessary to flash twrp and SU?
Think City said:
No, FRP is not unlocked now, but I have unlocked in on DC before. After reboot it shows locked message in bootloader.
I see now that you mention it that it's possible to have the FRP stay unlocked. Is that necessary to flash twrp and SU?
Click to expand...
Click to collapse
In "Developer options", I do not have the "Enable OEM unlock" option. Does that mean my chinese phone does not have FRP?
Think City said:
I bought a chinese Huawei Mate 8 NXT-DL00. It is now unlocked, thanks to DC-unlocker:good:
It communicates with adb, and reboots in bootloader. For some reason adb will not flash TWRP 3.0.2.0. (or any other TWRP). Is there a known TWRP for DL00 chinese, or is it the same as AL-10?
Click to expand...
Click to collapse
The Chinese model does not have this option to Enable OEM unlock, and need not, in the Chinese versions google has less activity, which protects and blocks the device are the options of Huawei. In your case, only if you have installed the system in another model, international for example, then yes there would be this option, but it would not work. I did this idiocy, and I was blocked FRP, only the DC unlocker could release the lock. Anyway, it is not original firmware of another model, which is the version of your system? If you are in DL00C17B320 or above this, you need to downgrade to EMUI 4.0. In versions above it as the 320 for example, the system does not accept commands via fastboot. Only commands that do NOT change anything. And yes, everything works in AL10, DL00 serves in, you can install without fear ARE the same model, the difference is just the operator.
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
MarceloAF said:
The Chinese model does not have this option to Enable OEM unlock, and need not, in the Chinese versions google has less activity, which protects and blocks the device are the options of Huawei. In your case, only if you have installed the system in another model, international for example, then yes there would be this option, but it would not work. I did this idiocy, and I was blocked FRP, only the DC unlocker could release the lock. Anyway, it is not original firmware of another model, which is the version of your system? If you are in DL00C17B320 or above this, you need to downgrade to EMUI 4.0. In versions above it as the 320 for example, the system does not accept commands via fastboot. Only commands that do NOT change anything. And yes, everything works in AL10, DL00 serves in, you can install without fear ARE the same model, the difference is just the operator.
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
Click to expand...
Click to collapse
My system is DL00C17B197. I still can't flash twrp. ADB says: "error: cannot load "twrp.img"". Must I unlock the chinese carriers, or something?
Think City said:
My system is DL00C17B197. I still can't flash twrp. ADB says: "error: cannot load "twrp.img"". Must I unlock the chinese carriers, or something?
Click to expand...
Click to collapse
Forgive me for the delay, I only saw it now. I do not think so, does your mistake look like something else, the bootloader, it's unlocked?
Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new
I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.
I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"
AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.
And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.
no I have no phones now with similar problems, but at different stages of the same issue.
My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)
and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.
ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
Have you tried the fastboot oem unlock command?
DR_HAX34 said:
Have you tried the fastboot oem unlock command?
Click to expand...
Click to collapse
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"
I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
TheWoerbler said:
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
Click to expand...
Click to collapse
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
bluestudy said:
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
Click to expand...
Click to collapse
So I installed the factory image from ZTE's website, which uninstalled twrp and SuperSU (which I knew it would), but I am still unable to use fastboot commands. What might be causing this problem?
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
iNaruX said:
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
Click to expand...
Click to collapse
So I changed some settings in Windows Device Manager, now fastboot is working...kinda. I type "fastboot oem lock" and it hangs up for 5 seconds and gives me the error "FAILED (command write failed (Unknown error))...
I solve one problem, and another pops up... Thoughts?
EDIT: In regards to DrakenFX's fastboot command zip, where would I get that? Is it the full systemstock?
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
iNaruX said:
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
Click to expand...
Click to collapse
I am currently running B29 (6.0.1). Will this still work, even though I am on a different version of Android? Or should I update to B19?
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
iNaruX said:
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
Click to expand...
Click to collapse
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
TheWoerbler said:
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
Click to expand...
Click to collapse
Haha cheers, I think you got it, I sent that guide just to enable fastboot commands, glad it worked :good:
I need to re-lock the bootloader on my A2017U. I put in a warranty repair claim with ZTE for a dead SIM2 slot. They said if I could relock it to stock, they would not charge the $79.99 out-of-warranty fee.
My only concern with the guides above is that I'm on the RR Nougat ROM. Will any of the links above work for me?
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
TheBoozer said:
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
Click to expand...
Click to collapse
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
soren25 said:
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Click to expand...
Click to collapse
Thank you very much for your help, I am now back to stock B15. The only thing left for me is to relock the bootloader.
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.
Hello, I recently purchased the T-mobile version of the 6T (bad idea) that had a locked bootloader, and tried to flash it to the international version so I can root the device. I followed this post in hopes of achieving it. The device will no longer boot. The screen quickly flashes with a Oneplus logo with "fastboot mode" underneath then I am met with this error: "Build version and HW is not match!". Is it completely bricked? Can I flash back to a T-Mobile OS?
If it is truly bricked I am curious if someone could explain why it may have happened. As in, has T-Mobile changed some the checks involved with flashing to the international version? Or was it because the device was running the latest Oxygen OS, is it impossible to downgrade this way? I am genuinely curious and want to take this as a bitter learning experience.
Thanks for your input.
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Pain-N-Panic said:
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Click to expand...
Click to collapse
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Did you get it all figured out? If not here's a semi detailed version of what I had to do with my tmobile 6t, because I had issues as well. Mainly my phone not showing up in msm tool. Only wanted to work after it had Android 9. Also I had little sleep the night I did this so I'm trying to recall the best I can.
Assuming your phone shows in msm tool at this point
Used msm tool to flashed older A9 ops https://androidfilehost.com/?fid=11410963190603895067
Boot in and enable adb and oem bootloader unlock
Boot to bootloader and unlock it
Flashed first A10 OOS https://androidfilehost.com/?fid=4349826312261819701
Flashed 10.3.7 to both slots with twrp https://androidfilehost.com/?fid=10763459528675591630
Flash rom
Flash Magisk
Profit
Some of this could be redundant, but my late night research and trial and error paid off.
GoldfishSnack said:
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Click to expand...
Click to collapse
Well I'm glad you were able to get it up and running. I highly suggest unlocking that bootloader as soon as you can....having an unlocked BL is key to getting out of a lot of bricked situations.