HELP! Unable to boot to bootloader! - Ascend Mate 7 Q&A, Help & Troubleshooting

I am in the process of rooting my phone and have already unlocked the phone but for some reason I am unable to boot into the bootloader. I have a MT7-CL00 and I have tried pressing the buttons on the phone, but every time I go into the normal boot mode.
I have USB debugging activated and I am able to connect with ADB / Fastboot and when I type ADB devices my device is shown as active.
When I type fastboot reboot I just get a message < waiting for any device >
Have I some now turned off the bootloader booting method on my phone?
Is there an alternate way to trigger the phone to boot into the bootloader?
Thanks!

Type adb reboot bootloader
Then fastboot devices, if it detects run further desired fasboot commands.
Sent from my HUAWEI MT7-L09 using XDA Free mobile app

Related

Bootlooping, Recovery Corrupted, Cant enable USB Debugging am I screwed?

After messing around with my shield last night and not being able to get root access on cm12. I tried to reinstall one of the ota updates from a while back. Now I am bootlooping and when I try to boot into CWM it looks to be corrupted and doesn't load. I cant use ADB because usb debugging is no longer active. Does anybody have any suggestions to re-install recovery or somehow enable debugging or am I dead in the water here? Any help would be greatly appreciated
Is your bootloader unlocked?
Can you get into fastboot mode?
HW method:
Turn off the device
Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
Click to expand...
Click to collapse
If you can get into fastboot mode and your bootloader is unlocked, you can use a command like "fastboot boot recovery.img" to have the device boot a recovery.img from your computer without flashing anything.
If you can get into fastboot mode, but your bootloader isn't unlocked you could try unlocking your bootloader, but this will wipe your data - so only try this if you don't have anything important saved. The command is "fastboot oem unlock".
~Troop
The bootloader is unlocked Whenever I try fastboot mode the device is not recognized because USB debugging is disabled .
Update: Fixed

Nexus 5 Cannot Perform Unlock

I have Nexus 5 phone which was not turning on a few days back. I kept it aside so that battery drains fully.
Now when I turn on the phone, it is on Google Logo Boot-Loop. When I press Power and Volume Down, I can boot into fastboot mode.
In fastboot mode, the device says it is locked and i send the following commands:
fastboot devices
fastboot oem unlock (Select Yes on Screen and Confirm as well)
fastboot reboot
Click to expand...
Click to collapse
After this, ideally the bootloader should be unlocked, but the phone still remains in boot loop and when put into fastboot mode, it again shows device is locked.
I don't know what all is happening. Is there anything I can try now? Even fastboot boot recover.img is not working as phone boots into custom recovery for some time and then reboots automatically.

No download mode - LG Mobile Driver problem?

Hello, I have problem with my softbricked Nexus 5.
phone is full stock
bootloader is locked
USB debugging is not enabled
Android 6.0.1
all buttons are working
USB socket is fine
Factory reset from recovery mode is not working - still bootlooping
My purpose is to bring it to live, but I am stuck. Due to locked bootloader I have to use LG Flash Tool. Some time ago I used it with my other Nexus 5 and it was fine - worked excellent. Now I want to do it again with other phone but I am stuck on start: Can't enter download mode (volume up+usb cable). When I am trying to enter to download mode,charging battery icon appears and after few seconds my phone is being recognized as MTP USB device in device manager. I thought it is a problem with the phone, but tried with another working Nexus and there is no difference - it looks like problem with phone-pc connection to me. I tried few cables (original samsung and nokia) and two pc's - no difference. Tried all USB ports etc. Clean reinstall (with registry keys delete) doesn't help, updated version 4.2 neither. Do you have any ideas how to fix it?
Download mode? Never heard of that on the Nexus 5. There is a fastboot mode for flashing stock ROMs and to unlock the bootloader.
I recommend unlocking the bootloader and using NRT to flash a stock ROM.
audit13 said:
Download mode? Never heard of that on the Nexus 5. There is a fastboot mode for flashing stock ROMs and to unlock the bootloader.
I recommend unlocking the bootloader and using NRT to flash a stock ROM.
Click to expand...
Click to collapse
I have NRT but problem is that to unlock bootloader I have to enable USB debugging - I can't do it with bootlooping phone.
Bootloader can be unlocked without enabling debugging as you are not running adb commands, you need to run fastboot commands.
audit13 said:
Download mode? Never heard of that on the Nexus 5. There is a fastboot mode for flashing stock ROMs and to unlock the bootloader.
I recommend unlocking the bootloader and using NRT to flash a stock ROM.
Click to expand...
Click to collapse
audit13 said:
Bootloader can be unlocked without enabling debugging as you are not running adb commands, you need to run fastboot commands.
Click to expand...
Click to collapse
Thanks! Can I do it with NRT also?
Easiest way to unlock the bootloader on a windows machine is to do this:
make sure that the necessary fast boot drivers are installed;
boot phone into fast boot mode by holding down volume up, volume down, and power;
connect the phone to the computer;
type "fastboot oem unlock" without the quotation marks and press enter key.
Unlocking will wipe the phone.
Once unlocked, you can flash a stock ROM using fastboot commands.
audit13 said:
Easiest way to unlock the bootloader on a windows machine is to do this:
make sure that the necessary fast boot drivers are installed;
boot phone into fast boot mode by holding down volume up, volume down, and power;
connect the phone to the computer;
type "fastboot oem unlock" without the quotation marks and press enter key.
Unlocking will wipe the phone.
Once unlocked, you can flash a stock ROM using fastboot commands.
Click to expand...
Click to collapse
Ok I did it. Do I have to proceed "fastboot reboot" command? when I am doing it it reboots and still bootlooping. When I enter bootloader it is locked again
If the bootloader relocks itself when the phone is rebooted, the memory chip is damaged and will need a motherboard replacement.

cannot unlock Fastboot Mode oem unlock

Fastboot Mode
prodcut_name - sdm845
variant - sdm ufs
bootloader version -
baseband version -
serial number - af102b7a
secure boot - yes
device state - locked
what i tried
adm devices - empty
fastboot devices - af102b7a
fastboot oem unlock FAILED (remote: `flashing unlock is not allowed
fastboot rerror command failed
the windows device manager i installed google android bootloader interface because i cannot install the oneplus specific driver it exits with error message
I cannot go to recovery mode from fastboot nor change any setting like enable oem un-lock or usb debbuging option
Any chance to unlock and flash the with new image
Enable Oem unlocking in developer options
@Tab E mercy but i can^t exit out of the fastbood mode to chagne the settings i`m locked inside this bootloader mode and cant do anything else but try with fastboot oem unlock...
Try
Code:
fastboot devices
fastboot reboot
@jwoegerbauer the commands work the oneplus is rebooting into the fastbood mode again i need to exit the fastbood mode because maybe the os deleted and can only use fastboot mode to flash it or else i dont know how to exit the fastboot.
I don`t know if developer mode is on or if oem lock is unlocked but since i cannot go back into the oss of the system what can i do to recover the device completely
i`m stuck in this fastboot mode and no commaand is helping to get out of it what is the solution_maybe to take out the battery it is really hard have you had the same issues?
Whether phone should run in ADB mode or Fastboot mode or Recovery mode or ADB Sideload mode is set via a kernel flag read by bootloader when phone boots up. Pulling out phone's battery doesn't change this flag.
Typically to boot Android in NORMAL mode you run
Code:
adb devices
adb reboot

Pc can't communicate when in bootloader(tried everything)....

I just purchased a OnePlus Nord N10 5G (BE2026)
Originally it was running OxygenOs 10.x.x.x
Following guides from oneplus website and here on XDA I was able to successfully unlock the bootloader and of course ADB worked fine as well as Fastboot in the bootloader etc...
After unlocking the bootloader I realized that OxygenOs 11.0.2.BE86AA was available via OTA. Which is now what the phone is currently running.
***MAIN ISSUE***
after unlocking the bootloader in order to gain root access via TWRP and Magisk my PC fails to find any devices while the phone is in Fastboot mode... ADB still works just fine but as soon as I run "adb reboot bootloader" or boot to bootloader via buttons the PC will not detect the phone any longer while in the bootloader or Fastboot mode...
I have triple checked that:
SDK USB drivers
ONEPLUS USB DRIVERS
Windows Universal USB drivers
USB Debugging
OEM Unlocking
PC is granted developer access
newest version of ADB & Fastboot
and everything else I can find on this issue searching Google & XDA for the past 3 days
* one issue that I found strange, only when the phone was booted into the bootloader Windows device manager showed Android as an unknown device. Which I could only solve by using Zadig and installing Winusb driver... but still running "fastboot devices" while phone is in bootloader / Fastboot mode still shows no devices....
I've been trying to solve this about 4 days now scouring the internet for any information I could find and nothing seems to work. But everything worked just fine before I unlocked the bootloader / flashed OxygenOs 11 via OTA and now windows to see the phone while in the bootloader....
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
jwoegerbauer said:
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
Click to expand...
Click to collapse
@jwoegerbauer not entirely sure what you are trying to imply with your message...
If you are trying to point out that ADB doesn't work in bootloader / fastboot mode, I am completely aware of this. And never mentioned otherwise in my original message.
With my phone booted up into Android
And I run "adb fastboot bootloader" the phone will reboot into bootloader mode but my PC still shows waiting for devices... Or if I boot into bootloader / fastboot mode manually and run “fastboot devices" it shows no connected devices. And no fastboot Commands work either... I am not trying to run ADB Commands in fastboot mode.
AFAIK starting with Android 10 the command sequence should be as this
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
...
fastboot reboot
because fastbootd got moved to Android's userspace.

Categories

Resources