Database Develop

HELP PLEASE! Stuck in bootloader, NEXUS 6

Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.

Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.

Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app

Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518

I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking

toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.

sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.

idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.

sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.

toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.

sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?

Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.

idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.

You don't need adb.

sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?

jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked

sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.

rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled

Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6

hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)

BRICK? Stuck at bootanimation

Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?

jewnersey said:
Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?
Click to expand...
Click to collapse
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?

Evolution_Freak said:
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?
Click to expand...
Click to collapse
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
just saw your thread.. ugh

formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD

jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Glad you're OK. :good:

jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Good job:good:

Bootloader not unlocking (Asus Zenfone Go ZB452KG)

Hey people, first time in this section so I'm gonna go straight to the chase...
I've been having some troubles unlocking this phone's bootloader
http://www.gsmarena.com/asus_zenfone_go_zb452kg-8097.php
Here's the thing
I've already enabled "Enable OEM unlock" in Developer Options
I've already unlocked many devices and this is the first time i got this problem
When going in bootloader and doing
Code:
fastboot oem unlock
It's stuck in
Code:
...
waited for 5 mins... NONE, still stuck
Reboot and did nothing, bootloader still locked
So I'm gonna need some help in this freakin phone :fingers-crossed:

How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...

BallisticSmith said:
How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...
Click to expand...
Click to collapse
Downgrade to the very first firmware version

veez21 said:
Downgrade to the very first firmware version
Click to expand...
Click to collapse
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one

BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware

veez21 said:
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware
Click to expand...
Click to collapse
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english

Str1kman said:
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english
Click to expand...
Click to collapse
You can download it, then flash(needs root) the very first stock recovery and then you can flash the firmware?

this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.

yankee77 said:
this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.
Click to expand...
Click to collapse
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.

Mr.haikal

veez21 said:
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.
Click to expand...
Click to collapse
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D

Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_...s/download/master/twrp-3.2.1-0-ASUS_X014D.img
Source: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
Cool, I'll try it when I get the device on my hands. I don't have it anymore.
EDIT: It works wew ?

Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
+1 worked after i installed the drivers from Asus PCLink. Anyone has a custom kernel or ...

BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
I got root access with KingRoot and then flashed TWRP with Flashify.
Somehow that gave me access to bootloader without the necessity to downgrade the firmware.

Mi A2 ?? Need help

My mi a2 last updated to 19/04/05 pie version, then i install the Google camera using below steps..
1. Turn on debugging mode/oem & turn off the phone
2. Then power button+vol dwn Fastboot mode & connect to pc (Pc already have the adb)
3. In pc>adb>folder>Cmd> type "fastboot oem unlock"
4. Then factory reset the phone and reboot again to fastboot mode
5. Then boot the patched image for phone
6. Then install the magisk and gcam work perfectly.
Simply i used these methods
the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
But then I tried to relock the bootloader, using below commands on cmd
1. "adb reboot-bootloader"
2."fastboot oem lock"
I tried these 2 commands 4 or 5 times
But phone is not power on with locked bootloader. Then I unlock again oem and try again,, But not working,
Then i unlock bootloader again and try these commands to lock it again,
1. "adb reboot-bootloader"
2."fastboot flashing lock"
3. "fastboot oem lock"
Unfortunately it is not work, also i can't give command "fastboot oem unlock", also i can't turn on my phone, Please help me... I want to restore my phone to working mode... Please help me, Quick, urgent :crying::crying::crying::crying:

No one is replying, I asked two questions about root and custom rom but these d!cks are so enormous that they don't want to help anyone else:

shailendra1993 said:
No one is replying, I asked two questions about root and custom rom but these d!cks are so enormous that they don't want to help anyone else:
Click to expand...
Click to collapse
Bro, you have to flash non patched boot.img before relocking bootloader.
After you did all of above for enabling gcam, you have to flash stock/ non patched boot img.
Btw, if you relock bootloader gcam wont work any more.
And you have to be patiente for solution.

shailendra1993 said:
No one is replying, I asked two questions about root and custom rom but these d!cks are so enormous that they don't want to help anyone else:
Click to expand...
Click to collapse
Yeah, i need a solution for it, but no one answering, My phone load fastboot mode only,:crying::crying:

Androidman12345 said:
Yeah, i need a solution for it, but no one answering, My phone load fastboot mode only,:crying::crying:
Click to expand...
Click to collapse
Flash a full fastboot image. Relock the bootloader and enjoy android one.
The lack of camera2 api is better than a paper weight?

Moto Z3 play bootloop with bootloader locked

Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance

sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs

sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!

sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?

sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...

sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.

kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.

sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?

kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...

$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.

Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....

Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución

To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.