Related
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.
So these are the steps I've taken:
- Download SDK Manager and install platform-tools and Google USB Driver
- Boot my phone up and connect to the PC
- I can run the command 'adb devices' and my device shows with a unique ID.
- Boot my phone into recovery/download mode (purple screen).
- Connect my phone, the PC detects it.
- However, when I run the command 'fastboot devices', nothing shows up.
Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.
I've run out of ideas and have been googling for answers for a very long time, but to no avail.
Any help would be greatly appreciated, thanks!
illquo said:
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.
So these are the steps I've taken:
- Download SDK Manager and install platform-tools and Google USB Driver
- Boot my phone up and connect to the PC
- I can run the command 'adb devices' and my device shows with a unique ID.
- Boot my phone into recovery/download mode (purple screen).
- Connect my phone, the PC detects it.
- However, when I run the command 'fastboot devices', nothing shows up.
Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.
I've run out of ideas and have been googling for answers for a very long time, but to no avail.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>
And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
LaserOP said:
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>
And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
Click to expand...
Click to collapse
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.
The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.
So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
illquo said:
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.
The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.
So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
Click to expand...
Click to collapse
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.
By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
LaserOP said:
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.
By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
Click to expand...
Click to collapse
I'll give it a go again, thanks.
By purple screen, I mean holding down the power button and both volume control buttons and the screen boots into a purple screen. Just a purple screen, that's it. I can boot into two other modes by holding down the power button and the volume up button and another by holding the power button and volume down button. I don't have a boot mode that displays any options as you've listed above.
EDIT: I'm in fastboot mode now! It was the mode where you hold down the power button and volume down button. Hahaha. I'll let you know how I get on with unlocking the bootloader. Thanks for your help
No problem, if you found my replies helpful please press the thanks button! It is much appreciated!
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
Hello guys!
My device is not booting in boot loader i have run the command of adb devices and my device is recognize by system but adb reboot boot loader command not rebooting device in boot loader and when i run command fastboot oem unlock it stuck at <waiting for device>.
Kindly help me to solve this problem.
Regards,
Taimoor Javaid
I am having the same problem except i cannot boot into bootloader by using the physical buttons either
timimalik said:
Hello guys!
My device is not booting in boot loader i have run the command of adb devices and my device is recognize by system but adb reboot boot loader command not rebooting device in boot loader and when i run command fastboot oem unlock it stuck at <waiting for device>.
Click to expand...
Click to collapse
Hi...
You apparently have enabled developer options and usb debugging. Did you also enable OEM unlocking from the same menu?
---------- Post added at 00:15 ---------- Previous post was at 00:02 ----------
ronin2011 said:
I am having the same problem except i cannot boot into bootloader by using the physical buttons either
Click to expand...
Click to collapse
On your device, go to Settings -----> About phone. Tap 7 times on the “build number“. You should now have enabled developer mode. Go back to the Settings menu and enter "Developer options" and enable USB debugging. Also check “OEM unlocking“. (It might be that you firstly have to connect the phone to a PC and tick “always allow this computer”and then get back to developer options menu and check “OEM unlocking“.
You may then start working with adb and fastboot.
(ps. Be aware that unlocking the bootloader triggers automatic factory reset - you will lose what you have not backed up)
r&xp said:
Hi...
You apparently have enabled developer options and usb debugging. Did you also enable OEM unlocking from the same menu?
---------- Post added at 00:15 ---------- Previous post was at 00:02 ----------
On your device, go to Settings -----> About phone. Tap 7 times on the “build number“. You should now have enabled developer mode. Go back to the Settings menu and enter "Developer options" and enable USB debugging. Also check “OEM unlocking“. (It might be that you firstly have to connect the phone to a PC and tick “always allow this computer”and then get back to developer options menu and check “OEM unlocking“.
You may then start working with adb and fastboot.
(ps. Be aware that unlocking the bootloader triggers automatic factory reset - you will lose what you have not backed up)
Click to expand...
Click to collapse
Hi,
Yes i have enable OEM unlocking option but no success.
timimalik said:
Hi,
Yes i have enable OEM unlocking option but no success.
Click to expand...
Click to collapse
Ok... Step by step... Please make sure you type exactly the commands as shown here:
1. type adb devices if it works, and shows your device then:
2. type adb reboot bootloader. If it works, and you should boot to bootloader. Next:
3. type: fastboot devices. Is you device stiil listed??? If not then there is some kind of trouble here. Your device is listed by adb, but not fastboot. If that is the case I personally do not have experience to help out. The only thing I can think of is that you may have missing drivers that do not allow correct communication between you device and PC.
If that is not the case and your device is listed by fastboot, then:
4. type: fastboot oem unlock. It will show that it is waiting. You will have to look at your device's screen and by using the devices buttons CONFIRM oem ulocking (on your device, not the windows command prompt)
5. If all goes well, your device should ask ask to reboot. Either reboot from menu, or just hold down the power button for a while.
6. After reboot, if all went well, your device will restart and perform an automatic factory reset. You cannot do anything about it. It just happens with OEM unlocking. At this point let it boot normally, and re-enable developer options and usb debugging to continue with root process, or anything that you want to do.
Can't thing of anything else for the moment... Let us know how it goes, perhaps a more experienced member, could share some insights???
I have already enabled usb debugging and oem unlocking yet neither adb reboot bootloader nor using the volume down + power button boot into bootloader mode, both of them lead to the tablet restarting normally to system
r&xp said:
Ok... Step by step... Please make sure you type exactly the commands as shown here:
1. type adb devices if it works, and shows your device then:
2. type adb reboot bootloader. If it works, and you should boot to bootloader. Next:
3. type: fastboot devices. Is you device stiil listed??? If not then there is some kind of trouble here. Your device is listed by adb, but not fastboot. If that is the case I personally do not have experience to help out. The only thing I can think of is that you may have missing drivers that do not allow correct communication between you device and PC.
If that is not the case and your device is listed by fastboot, then:
4. type: fastboot oem unlock. It will show that it is waiting. You will have to look at your device's screen and by using the devices buttons CONFIRM oem ulocking (on your device, not the windows command prompt)
5. If all goes well, your device should ask ask to reboot. Either reboot from menu, or just hold down the power button for a while.
6. After reboot, if all went well, your device will restart and perform an automatic factory reset. You cannot do anything about it. It just happens with OEM unlocking. At this point let it boot normally, and re-enable developer options and usb debugging to continue with root process, or anything that you want to do.
Can't thing of anything else for the moment... Let us know how it goes, perhaps a more experienced member, could share some insights???
Click to expand...
Click to collapse
The problem is at Step 2 adb reboot bootloader only reboot device not booting it into bootloader.
anyone else getting this problem?
Let's wake this thread in a bang! ?
Come on guys! Did anyone manage to deal with the problem? I have absolutely the same issue. Step 2 is the problem for me too. No fastboot mode neither through adb reboot bootloader nor the tablet physical buttons. I get either a normal reboot or the stock recovery which has not many options.
Any help would be appreciated!
Thanks in advance!
cmd with adb...
And I followed the steps meticulously - unlocked bootloader etc, but I get to the "writing recovery part" -
And it says FAILED (remote not allowed in locked state)
I don't get it! =(
I have unlocked bootloader, I have installed drivers, I did EVERYTHING...
Any advice?
In dev options it says my bootloader is unlocked however when I type:
fastboot oem unlock -
It comes up with options to unlock press vol up
but volume up button does not acknowledge me pressing it!!!
Please delete this thread no longer valid
thanks
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck