Related
HI all,
I have just bought an open box nexus 10 which means its new but has been opened and apparently been tested to be working. the company i bought it off say they tested it working before sending it out to me..
I got it today and started it, it loaded fine then asked for me google details and wifi..
Once done it loaded fine and i was on the home screen, it then rebooted itself and then since then it has not been able to reboot, it says the white google then some colours start to come in from the sides and it reboots again..
I have tried to go into recovery and factory reset both cache and data but that didnt work..
I am just trying the nexus toolkit now but i have no idea of which version of android it is actually running right now or have any idea if USB debugging is activated but i assume it isnt as i have not had a chance to do it..
Any help would be greatly appreciated, i dont really want to return it as it is from a friends company and i got it at cost price and he has no stock left!
device information
Prod Name - Manta
H/W - 8
bootloader - MANTAMF01
Carrier info - none
Lock state - locked
Roboot mode flag - None
if any of that helps?
device information
Prod Name - Manta
H/W - 8
bootloader - MANTAMF01
Carrier info - none
Lock state - locked
Roboot mode flag - None
if any of that helps?
Do the colors make 4 circles and twirl around in a circle? If so your on KitKat. If it names an x shape your on jelly bean. Just use the toolkit select the version your on. I'm guessing your on 4.4 or 4.4.2 KitKat. Then select flash back to stock or whatever the option is. IRS all the way on the right.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
I have managed to go through one full cycle of trying to flash the 4.4.2 from the toolkit but it says failed remote - locked use fastboot oem unlock. then after that it simply says booting up your freshly flashed device...
But if i try to reboot it does the same thing, problem i am having is that the bootloop doesnt even allow the colours to merge from the sides it reboots even before they meet in the middle of the screen??
ANy idea what to do now?
ps thanks for the reply!
talboy said:
I have managed to go through one full cycle of trying to flash the 4.4.2 from the toolkit but it says failed remote - locked use fastboot oem unlock. then after that it simply says booting up your freshly flashed device...
But if i try to reboot it does the same thing, problem i am having is that the bootloop doesnt even allow the colours to merge from the sides it reboots even before they meet in the middle of the screen??
ANy idea what to do now?
ps thanks for the reply!
Click to expand...
Click to collapse
OK. Open up the folder with the downloaded factory image from the toolkit. You'll find it under data/factory images I think in the toolkit files. Extract it. Are you familiar with adb? Because you'll need it. Copy the system, userdata, boot, and recovery images that we just extracted and paste them in the data folder. From there (I'm assuming you use windows) open a command window by holding shift and right clicking and you'll see the option. After that type "fastboot devices" then enter without the quotations and you should see you're device listed. (It needs to be connected in fast boot mode via USB cable). From there you need to use the commands "fastboot flash system system.img" repeat this with the boot, recovery, and userdata. But replace the system and system.img with the appropriate word fur example "fastboot flash boot boot.img" without quotes. That is a manual way of resetting. it should fix any soft ware issues. If that Durant work it might be a hard ware problem b and you might need to return it but in pretty sure it should.
Good luck and of you need any help or explanations just ask.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
abdel12345 said:
OK. Open up the folder with the downloaded factory image from the toolkit. You'll find it under data/factory images I think in the toolkit files. Extract it. Are you familiar with adb? Because you'll need it. Copy the system, userdata, boot, and recovery images that we just extracted and paste them in the data folder. From there (I'm assuming you use windows) open a command window by holding shift and right clicking and you'll see the option. After that type "fastboot devices" then enter without the quotations and you should see you're device listed. (It needs to be connected in fast boot mode via USB cable). From there you need to use the commands "fastboot flash system system.img" repeat this with the boot, recovery, and userdata. But replace the system and system.img with the appropriate word fur example "fastboot flash boot boot.img" without quotes. That is a manual way of resetting. it should fix any soft ware issues. If that Durant work it might be a hard ware problem b and you might need to return it but in pretty sure it should.
Good luck and of you need any help or explanations just ask.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Click to expand...
Click to collapse
Massive thanks for this explanation..
I am not sure what ADB is? do i need to have any specific software or do i simply follow the instructios that you have given?
Just follow the instructions. Normally you'd need to download a package but that comes with the wug tool kit so your all ready to go.
Also If you want to unlock the bootloader beforehand type in "fastboot oem unlock" it'll make it easier if you ever want to flash a custom rom or recovery later because it wipes all your days and since you have no data you might as well do it now. But if your not interested in ROM then don't bother.
Also please press thee thanks Button if it helps. Thanks
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
abdel12345 said:
Just follow the instructions. Normally you'd need to download a package but that comes with the wug tool kit so your all ready to go.
Also If you want to unlock the bootloader beforehand type in "fastboot oem unlock" it'll make it easier if you ever want to flash a custom rom or recovery later because it wipes all your days and since you have no data you might as well do it now. But if your not interested in ROM then don't bother.
Also please press thee thanks Button if it helps. Thanks
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Click to expand...
Click to collapse
ok so i am stuck right at the start, im sorry! So to open the command prompt i hold shift and right click, there is no option for command prompt? Should i just open CMD as normal?
talboy said:
ok so i am stuck right at the start, im sorry! So to open the command prompt i hold shift and right click, there is no option for command prompt? Should i just open CMD as normal?
Click to expand...
Click to collapse
You need to be in the folder. Open the folder then hold shift then open it. Is that what you did?
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
abdel12345 said:
You need to be in the folder. Open the folder then hold shift then open it. Is that what you did?
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Click to expand...
Click to collapse
Sorry i got it, right click when in the data folder.. command open with the wugfresh development
just going through the process now as i type.. first one failed saying invalid partition but then said about flashboot oem unlock so i have done that first and it now seems to be allowing the system.img to be flashed..
fingers crossed it works!
ok flashed all of the .img resterted it and now it just says google on the screen with an unlocked padlock at the bottom, been like that for 30 secs so far, seems to have done somehting as previously it was just going into the animation and restarting..
Should i be doing a factory reset?
talboy said:
ok flashed all of the .img resterted it and now it just says google on the screen with an unlocked padlock at the bottom, been like that for 30 secs so far, seems to have done somehting as previously it was just going into the animation and restarting..
Should i be doing a factory reset?
Click to expand...
Click to collapse
If it shows the Google image then there's a kernel so the boot image was successful but if it doesn't go past it means you have no ROM so the system flash must have failed. Terry flashing system again. Sorry for the late response
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
no problem thanks for the help so far!! just reflashed system this time it it is coming up with the google sign and unlocked pad and its doing the same as before now...
its just starting the animation for a milisec then rebooting...
any idea?
talboy said:
no problem thanks for the help so far!! just reflashed system this time it it is coming up with the google sign and unlocked pad and its doing the same as before now...
its just starting the animation for a milisec then rebooting...
any idea?
Click to expand...
Click to collapse
I'm not sure why it isn't working
Well now that your boot loader is unlocked you can try the toolkit again and see of it works. Use the option that says factory reset or unbrick or whatever it says and choose stuck in bootloop. Then follow the instructions if that v doesn't work is recommend locking the bootloader using "fastboot oem lock" and trying to return it.
Or you could wait a little and see if someo else has ideas. Try the toolkit again first though
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
thanks man you have been super helpful an di appreciate it a lot, hopefully it starts to work if not at least we gave it a chance.
Ill try the toolkit again and see if that does anything if not then back it goes!
retried the toolkit same thing, no joy still doesnt work...
thanks for the help..
does anyone else have any ideas? if not back it goes tomorrow
talboy said:
retried the toolkit same thing, no joy still doesnt work...
thanks for the help..
does anyone else have any ideas? if not back it goes tomorrow
Click to expand...
Click to collapse
Make sure if you return it to do the lock bootloader command first.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
scbikep2 said:
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
Click to expand...
Click to collapse
A clear explanation of the problem alone with everything that you have tried will do for reporting hardware/software issues and also help others help you.
Sent from my Nexus 5 using Tapatalk
I shattered the screen of my 2015 X pure.
I am sending it back to Motorola for screen replacement.
I want to factory reset, but the screen is not responsive. I can see the screen.. well the lock screen, as touching anywhere on the screen does nothing.
i have tried to hold power button 10 seconds to turn off... from there i can hold power and down volume until enter bootloader mode.. or whatever that is.... I cannot see anyway to factory reset from there either!!
It is bad enough that i cannot get the files off the phone because, thanks to Marshmellow, you can no longer just hook up to computer and have it open a folder.. it goes in in a different mode now, and you have to change it on hte phone.... which i can't do... lucky me.. .isn't progress great?
Anyway, if someone can help me, it'd be appreciated.
thanks.
TWRP custom recovery enables adb and mtp without any touches, so you could recover your files via usb if you have TWRP. Was your bootloader unlocked? It has to be to run TWRP, and you have to enable a setting with the touchscreen to allow bootloader unlocking. If your bootloader is unlocked and you have, or are willing to install TWRP then I think you can get at your files. If your bootloader is locked I think your stuck.
Fastboot will work to factory reset with no touchscreen if you must. While in that bootloader mode plug it into a PC and use the following commands:
Code:
fastboot erase userdata
fastboot erase cache
Pretty much same thing as a factory reset, no touchscreen required. Now those lenovo techs won't be able to check out all your funny cat pictures.
Don't have a working fastboot/adb PC? Check out Heisenberg's guide for how to set that up.
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.
I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app
Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.
Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.
Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.
Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.
Wife's phone got stuck in a bootloop last night, just stayed on the moto logo. Tried wiping cache and then data from recovery. phone now boots to moto then a black screen. I can see the device in fastboot, but not in recovery. I want to unlock the phone so that I can reflash the OS either from a custom recovery or from fastboot, but since I cant fully boot, I cant get to the developer options. This phone has never been unlocked/rooted or anything.
Is there a way to unlock the bootloader without going into the developer options and enabling it?
rokenford said:
Wife's phone got stuck in a bootloop last night, just stayed on the moto logo. Tried wiping cache and then data from recovery. phone now boots to moto then a black screen. I can see the device in fastboot, but not in recovery. I want to unlock the phone so that I can reflash the OS either from a custom recovery or from fastboot, but since I cant fully boot, I cant get to the developer options. This phone has never been unlocked/rooted or anything.
Is there a way to unlock the bootloader without going into the developer options and enabling it?
Click to expand...
Click to collapse
No there is no way to unlock bootloader without allowing OEM unlock, you're gonna wanna flash the latest version of stock available for your phone. Unfortunately I'm not very familiar with the commands so maybe another user can chime in here!
rokenford said:
Is there a way to unlock the bootloader without going into the developer options and enabling it?
Click to expand...
Click to collapse
You cannot unlock BL without "allow oem unlock" enabled.
Usb debugging you can't enable with fastboot.
You can try to erase with commands:
fastboot erase userdata
fastboot erase cache
fastboot erase customize
fastboot reboot
Give it some time.
How long are you waiting for it to boot after a factory reset? This can take 30 minutes... sometimes more.
acejavelin said:
How long are you waiting for it to boot after a factory reset? This can take 30 minutes... sometimes more.
Click to expand...
Click to collapse
I've waited at least 20 mins (not really timing it.) but with the black screen (screen on, not displaying anything) after the boot screen, how can I be sure its actually doing anything?
Honestly... Locked and stock there isn't much you can do. If we had the latest firmware image, maybe, but we are a release behind with no way knowing when, or if, we will ever get the current one.
There are two likely cases here for the cause of this problem... Actually, the cause is corruption of data on the internal emmc chip, the reason behind that corruption is the issue. It is either a faulty emmc chip or a fluke from cosmic radiation, static electricity, or who knows what. Either way, there since a factory reset isn't fixing it and we don't have a current firmware image your only option is send it in to Moto or replace it.