Database Users

Bootloop With locked bootloader 7.0

My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..

So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.

no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .

I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview

After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?

Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.

Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?

Here you go
google.com/android/beta

do you remember what you did to get it to boot?

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.

boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot

noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.

Ill try that.. but isnt the warranty voided because the bootloader is unlocked?

noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.

Phone is locked with factory(?) password after relocking bootloader, no recovery mode

Hi guys, I tried flashing stock rom and re-locking the bootloader so that I could have the phone completely stock. However, after re-locking the bootloader, I seem to have bricked the phone. I've scoured the forum for fixes, tried tenfar's tool, and nothing has worked yet. Hopefully someone has come across this situation before and can advise me on how to get my phone working again.
So how I got to this point.
-Originally the phone was on stock rom, rooted, with official TWRP recovery.
-Booted into TWRP, wiped cache, dalvik, data.
-Flashed ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip.
-Flashed ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip.
-Rebooted phone, went through initial setup, then turned on Allow OEM Unlocking in Dev Options.
-Rebooted back into TWRP, used Minimal ADB to fastboot oem lock.
So the phone rebooted twice from there, and seemed like it was going to boot properly, but the first screen that appeared was a lock screen asking for the password. I didn't set any passwords, and couldn't find any default factory passwords even looking through the zteusa forums on posts for similar situations. Then I tried rebooting into the bootloader to factory reset the phone, but trying to boot into the bootloader only leads to a black screen after the ZTE boot logo. That's where I'm currently stuck. No matter what I try, be it tenfar's tool, I can't get into anything but the black screen or the password-locked screen.
Using tenfar's tool, after I issue the axon7root.exe -p 3 command, it shows the next two lines, up to Version 1.10, then does nothing else. I'm not sure if this is because I flashed B29, and the tool only goes up to B27.
Any advice would be greatly appreciated!

Tennear's tool for flashing a boot and recovery image seems the most promising I think, but I don't quite understand how to use it.

-Rebooted back into TWRP, used Minimal ADB to fastboot oem lock.
Click to expand...
Click to collapse
First, you shouldn't (can't?) relock the bootloader while you're using a custom recovery. Additionally, I don't think you can issue fastboot commands to recovery.
Boot into TWRP and do a factory reset from there.
If not, flash the ZTE B29 image either via stock recovery (flashed via TWRP/tenfar's tool), or edit the install script to make it flashable via TWRP.

Nexus 6P: Default Bootloader Setting; Locked?

Sorry for the confusing title but I'm curious...
Being fairly new to Android in general and a total newbie regarding rooting these devices (a Nexus 6P in my case), I'm finding myself questioning some of the features and functions as they're related to rooting. In this instance, I'm wondering about "OEM unlocking" as it's listed in Developer Options. I've successfully flashed several factory OEM images that past few days as well as flashed TWRP, installed SuperSU, made backups of those images and all has worked out fine. From Marshmallow to Nougat 7.1.1 and to now what I've recently flashed, Android O, all the flashing of OEM software and using TWRP to recovery those backup factory images I'd made has worked, all's gone well without a hitch.
When I first activated Developer Options in settings when the phone was brand new, fresh out of the box, I noticed that "OEM unlocking" was in locked bootloader status. I'm guessing that's a factory default kernel or OS setting. Why is it that after unlocking the bootloader and flashing a complete factory zip image, when I go into Developer Options, the "OEM unlocking" is now displaying "Bootloader is already unlocked"? If it's a complete factory image that's been flashed, wouldn't "OEM unlocking" be locked by default because it's stock OEM software that's been installed? Guess I'm wondering if there are settings (like bootloader) that are not part of factory software images and reside in some hidden partition or in firmware or . . . .
By the way, the only reason I'm flashing all these different images via TWRP recovery or not, is to become familiar with rooting basics, command prompts, curiosity and 'cause it's fun, at least for now. Guess it'll really get interesting when I start messing with custom ROMs.
Welcome to my confusion.

ChipperD said:
Sorry for the confusing title but I'm curious...
Being fairly new to Android in general and a total newbie regarding rooting these devices (a Nexus 6P in my case), I'm finding myself questioning some of the features and functions as they're related to rooting. In this instance, I'm wondering about "OEM unlocking" as it's listed in Developer Options. I've successfully flashed several factory OEM images that past few days as well as flashed TWRP, installed SuperSU, made backups of those images and all has worked out fine. From Marshmallow to Nougat 7.1.1 and to now what I've recently flashed, Android O, all the flashing of OEM software and using TWRP to recovery those backup factory images I'd made has worked, all's gone well without a hitch.
When I first activated Developer Options in settings when the phone was brand new, fresh out of the box, I noticed that "OEM unlocking" was in locked bootloader status. I'm guessing that's a factory default kernel or OS setting. Why is it that after unlocking the bootloader and flashing a complete factory zip image, when I go into Developer Options, the "OEM unlocking" is now displaying "Bootloader is already unlocked"? If it's a complete factory image that's been flashed, wouldn't "OEM unlocking" be locked by default because it's stock, OEM software that's been installed? Guess I'm wondering if there are settings (like bootloader) that are not part of factory software images and reside in some hidden partition or in firmware or . . . .
By the way, the only reason I'm flashing all these different images via TWRP recovery or not, is to become familiar with rooting basics, command prompts, curiosity and 'cause it's fun, at least for now. Guess it'll really get interesting when I start messing with custom ROMs.
Welcome to my confusion.
Click to expand...
Click to collapse
Hello...
Once you allow "OEM unlocking" in developer options, it allows you to unlock your bootloader. Which you certainly did by:
fastboot flashing unlock
In bootloader...
You can flash as much as you want, the bootloader will remain unlocked. I don't know what partition keeps a record of the command, but flashing​ a new image doesn't lock as you can see. As long as you don't relock using:
fastboot flashing lock
Don't do it if you are not full stock, because you can't flash anything if something goes wrong...
Cheers...

If it's one take away I've come away with so far after reading several posts here at XDA, ones that include tales of rooting gone bad, it's to NOT lock the bootloader unlesss the device is back to stock (thanks Heisenberg). Fortunately, I'd read that before moving to and from locked bootloader status'. Thanks for the reminder, too!

How to Stock FW and Relock Bootloader? OP5

Hi all,
I've wanted to go back to Stock OS but when i type "fastboot oem lock" it says "FAILED <remote: Flashing Lock is not allowed."
Everything boots normally to OS 4.5.2. In DEV options the Unlock Bootloader is greyed out and says bootloader is already unlocked.
What can i do?
Cheers

These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5

reayard said:
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
Click to expand...
Click to collapse
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).

r1card0amr said:
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
Click to expand...
Click to collapse
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..

mohan_kr said:
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
Click to expand...
Click to collapse
Hello. I first thing I do always is to install drivers. I start by connecting the phone to the laptop in charge mode, then in transfer files mode, MTP or camera. In this way he will recognise all the drivers your laptop needs.
Also I enter in fastboot mode and recovery so the laptop can recognise the drivers and always reboot laptop and phone just to double check.
What I did was: go to Developer Options and enabled Unlock Bootloader and USB Debugging.
Then I accepted the laptop request on my phone and all drives were OK.
I run CMD and typed fastboot devices to see if it recognises my phone and it displayed a serial number. So I proceed next to type fastboot oem unlock and the process went OK and on my phone it asked Yes or No to unlock and I choose yes.
Then I flash a twrp image by typing on CMD: fastboot flash recovery recovery.img (my twrp I'm had other name so I rename it. You need to enable "Show file extensions" in Windows so you can see what the extension is).
I then type fastboot boot recovery.img and the phone entered in Recovery Mode in this case TWRP.
My phone was always connected to the laptop and he open the internal storage window so I drag the supersu inside.
Then on TWRP I wiped dalvik and cache and I went to Install and installed the SupeSU on my internal memory root.
The phone then rebooted and ready to go.
But then I went to developer options and the Unlock bootloader was greyed out. I unroot my phone and flashed a stock recovery for OP5 and the stock image 4.5.2 and when I type fastboot oem lock it always says it can't be flashed.
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Just installed supersu to try an app. I never install 3rd party roms.

r1card0amr said:
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Click to expand...
Click to collapse
the warranty is not voided with unlocked bootloader..
https://oneplus.net/hk/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty

I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.

r1card0amr said:
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
Click to expand...
Click to collapse
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.

Hogyoku said:
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Click to expand...
Click to collapse
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.

I rooted my device with Magisk, and now I want to restore it to factory state.
I flashed stock recovery and OOS several times, wiped everything but fastboot oem lock failed all times (FAILED (remote: Flashing Lock is not allowed)).
Can you help me?
What should I do to relock bootloader?

here is your solution
r1card0amr said:
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
Click to expand...
Click to collapse
here in this video u can see in detail how to lock bootloader. hope this help you
https://www.youtube.com/watch?v=CQYCSdDUdAU

HOW TO RELOCK..
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.

I usually do it this way (successfully):
Wipe everything but OTG in TWRP
Format data
Reboot to TWRP
Flash the full stock OOS zip
Reboot to fastboot
Flash stock recovery
Lock bootloader with the fastboot lock command

Has anyone made any progress with this? I too am having the issue as described and have tried the solution by Ricyksydhu, along with solutions from various other places around the net.

Got stuck on Android one logo

Hello sir,
Recently my internal storage got almost full ,it flashed repeated warnings that "some system functions may go wrong,please freeup some space".I just did not paid much attention to it and proceeded to download a file when my internal storage level was less than 100 mb and then suddenly my phone got switched off.when I tried to switch it on it got stuck in the middle with Android one logo .please help me to solve this problem as I don't to lose my data.

Hi Rakesh,
Is you issue get resolved?
I have also got warnings of internal storage full in my MI-A1 and after that my phone got switched off. I also tried to switched on and it got stuck at android one logo.
Please help me out if your issue get resolved?

Try booting in TWRP and using the file manager to delete some user data to make space.

barrack1 said:
Try booting in TWRP and using the file manager to delete some user data to make space.
Click to expand...
Click to collapse
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.

saurabhsh23 said:
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
Click to expand...
Click to collapse
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.

manpildo said:
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
Click to expand...
Click to collapse
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?

saurabhsh23 said:
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
Click to expand...
Click to collapse
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.

manpildo said:
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
Click to expand...
Click to collapse
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.

saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
Click to expand...
Click to collapse
Yes, unlocking bootloader wipes data.

saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
Click to expand...
Click to collapse
No, if you wipe your phone through recovery you won't need to flash anything. It just deletes all your stuff without touching the system.

Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713

Any update here please?
vaibhav08 said:
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Click to expand...
Click to collapse

Guys pls help me i got stuck on boot logo i want to flash stock rom pls help me

I'm in the same boat. Unable to access developer options as phone won't boot and its stuck at the android one logo.
Fastboot oem unlock gives error Flashing Unlock is not allowed.
Is there anyway around this?

I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.

Face_11 said:
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Click to expand...
Click to collapse
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking

jack_21 said:
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
Click to expand...
Click to collapse
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s

Face_11 said:
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Click to expand...
Click to collapse
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery

jack_21 said:
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
Click to expand...
Click to collapse
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.

Face_11 said:
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Click to expand...
Click to collapse
If you see a triangle, you are in recovery mode
You need to press a button combination to see options, Search on Google for that