Moto G not boot, it just gets in the bootloader screen warning
I'm having the exact same issue, just flashed the latest stable version of CM11 (with gapps obviously) from dhacker's thread in CWM.
Coming from 4.3 with the US version t-mobile moto g.
Stuck on the bootloader unlocked screen.
I thought for a while it was just that the first loadup takes awhile but has been 10 minutes now and am figuring something bad happened.
ignore all the italics, I'm an idiot
Edit: 25 minutes in, have tried connecting the phone to computer and running command prompts to it like I did to get into recovery, device not recognized under cmd "adb devices" or "fastboot devices" when connected to computer
Phone screen goes black for about 0.8 seconds when power button is held down and immediately pops back up into warning bootloader unlocked screen, trying to go into fastboot or anything like with volume down and power button achieves the exact same effect.
Any help would be greatly appreciated.
Edit2: If I hold the power button and down volume for 20 seconds (just ignore when the screen goes black and hold it for 20 seconds) it will boot into fastboot mode
Recovery seems to do nothing but the device is now recognized by the mototool all in one, I will report back if I figure out anything more useful, I am hoping the mototool will save me
Edit3: tried flashing stock recovery, my phone now says in pink "hab check failed for recovery", tried flashing CWM recovery, it seemed to work. I then clicked "fix boot logo" it worked. The phone is now showing the motorola logo but doesn't seem to be doing much else, I'll let it sit for a couple minutes.
Edit4: If none of this works at least you'll have an interesting read about how to further destroy your phone
Tried rebooting to recovery, the mototool thinks it did it but my phone stays stuck at the motorola logo. I then told it to check connection and it now thinks there is no longer a device connected. Tried turning the phone off again, went immediately back to the motorola screen. I seem to be in the same situation except the bootlogo is no longer that ugly text. Back into fastboot mode, lets see what else we can do.
I checked to see if it was recognized by command prompts now and it IS, if you go back under like you were unlocking the bootloader and open up a cmd prompt and type "fastboot devices" it's recognized in this fastboot mode. This has given me new optimism, I'm feeling hopeful that my device is not destroyed, hopeful and very hungry, I will report back in after getting food.
Edit5: I've realized that I have no idea where to go from here, while I can access command prompts I have no idea what commands to put in, I tried hitting "factory" under the fastboot in hopes that it would flash my factory recovery, no such luck, I'm back to the same situation, tried hitting BP tools next because I didn't know what it was and thought it would be helpful, no such luck, back to the same screen, my quickly inflated confidence is now waning, I do have hope that someone can fix this issue but I am thinking that someone is not me.
I hit the recovery button, I'm sure I had done this before but this time it worked, went to restore from sd card, and restored my backup I made right before all these issues, it recovered my device, I then restarted it and everything is good now.
Apparently I am an idiot, but that's okay because my phone is working again now, after only about an hour or something.
TO FIX YOUR ISSUE HOLD DOWN VOLUME AND POWER AT THE SAME TIME FOR 20 SECONDS, IGNORE WHEN THE SCREEN GOES BLACK, KEEP HOLDING FOR ALL 20 SECONDS, CHOOSE RECOVERY, THEN GO BACK TO YOUR BACKUP THAT YOU SAVED BEFORE FLASHING A NEW ROM, RESTART THE DEVICE AND NOW THE DAY IS SAVED
I have tried just about everything I can find to fix my Nexus 7. When powered on it shows the Google logo and hangs there. I have checked the battery connection, checked the other connections that are visible when the cover is taken off and everything is ok. I can boot to the fastboot mode. I plug it in my computer and it loads the drivers. I can a cmd line command "fastboot Devices" and it shows that my device is visible. Then I can enter the command "fastboot oem unlock. the tablet asks for the yes or no question i use the volume up to say yes and the cmd line shows unlocking and erasing but the tablet freezes and nothing happens (for hours). I then hold the power button and shut off the tablet. the command line then says failed because of to many links.
The laptop has not been rooted, this is a bone stock Asus nexus 7 2013.
I am attaching a photo of the fastboot mode screen.
My question is...I am beating a dead horse is my nexus 7 bricked permanently.
I think the problem is not being able to enable USB debugging. Is there a way to enable USB debugging when so can't get into systems in the tablet?
Thanks for the help. if you have any questions please let me know
MWGW
So as the title goes, I was helping my friend.
The phone first suddenly just crashed and went into safe mode and it wouldn't get out of safe mode. Even after rebooting it still doesn't get out of safe mode.
So I suggested to my friend that I help him reinstall his ROM and I was going to flash cm12 for him. So he rebooted the phone into fastboot mode and i did fastboot oem unlock
After fastboot oem unlock, the phone rebooted back into fastboot mode except this time the screen was blinking while the phone was plugged in. When the phone was not plugged in, the screen wouldn't blink but trying to restart it results in a black screen. So I suggested to my friend that the battery is probably low and he said the battery was low when we started. So I told him to plug in the phone to his charger and leave it to charge for a while. We met back after 30 mins and but this time it got even worse. I couldn't even detect the phone in fastboot mode. Previously it had "????? fastboot" when i ran the command fastboot devices but this time there was nothing. Also before we left the phone to charge for 30 mins, slightly after the "???? fastboot" fastboot devices wouldn't turn up anything but fastboot commands like fastboot reboot would work. I tried to install TWRP but it came up with a too many links error.
Now the phone doesn't even get detected by fastboot on windows and we're meeting up irl and im brining my laptop along to try to fix it. Does anybody have any idea about what went wrong?? Im kinda dumbfounded. I have unlocked the bootloader of the oneplus and install a custom rom on my own device but ive never encountered something like this... Any help would be great!
EDIT:
tl;dr - Nexus 5 went into fastboot mode and the screen started blinking after fastboot oem unlock was issued. Previously, it was stuck in safe mode and you couldn't get out of it even if you rebooted. Now it the screen stops blinking if you dont connect the usb cord but the moment you connect the device to an adapter or a computer, the fastboot mode screen just keeps blinking and blinking and the computer can't detect it either so you can't do anything. rebooting with volume up and power also just lands you back in fastboot mode with the blinking. weird ass problem and it looks like im the first. it does say state unlocked though so theres that
I had something similar happen. In my case I had forgotten you have to completely boot up android after doing the oem unlock (not just boot loader). I had to do the opposite, OEM lock bootloader, reboot all the way, then OEM unlock, (again) then reboot all the way. Then continue as before.
It worked for me
I recently bought an Alcatel pop 4s(the unlocked model at best buy)and want to root it. One click roots wont work so i started the hard way. First thing i needed was to unlock the boot loader. Here's my problem, when i hold the power and up button it will take me to the recovery menu and i select to reboot in to boot loader, by doing this the screen turns completely black unless i press the power button at which point it just reboots normally. I also tried using adb reboot-bootloader and it simply reboots my phone. I have also tried plugging in to the computer while on the black screen and again it reboots the phone. There's an option in recovery to enable adb which when i click just tells me to reset and i have and it remains the same after it reboots. I have OEM unlocking enabled as well as usb debugging but i am at a total loss. If someone could help me unlock my boot loader or simply get to it for that matter it would be wonderful. If you could help with a full guide on how to root my Alcatel pop 4s that would be amazing as there is almost absolutely no information about this phone on the internet, thank you.
Hi !
Here`s a long discussion about your question , have a look , I`m afraid that your device must be OEM unlockable otherwise you can`t unlock it
https://forum.xda-developers.com/android/help/alcatel-pop-4s-help-rooting-installing-t3514186
Cheers !
I tried rooting my Pixel 3 tonite and was having success following along with the directions up to the TWRP part. I was able to get it onto my Pixel by typing the fastboot boot twrp-3.2.3-0-blueline.img.
Once the screen popped up on my phone it asked for a password, i just typed in one I use for most things and it went to another screen. I can't remember what i clicked on there but it rebooted and now I get the "your device is corrupt,it can't be trusted to work properly screen.
I can get it to go off that screen by holding power and volume down and I get to the fastboot screen but my platform tools doesn't recognize the device.
I think that is because I clicked of the allow USB debugging right before i did all this because I thought i had it done.
Anyone know if I can get out of this somehow?