Database Develop

no usb in fastboot

plz help, I tried to flash my phone today and now the usb does not work under fastboot anymore, when i try to put the phone in fastboot and type the command in cmd it just says *waiting for device* and i have to use cmd for flash the boot.img so in theory i think my phone is brickt, but i can access my sd card and all that stuff but my phone wont boot, can sombody plz help?
HBOOT 2.02.0002
RADIO-3831.10.00.11_M
ROM: sabsa_prime_V10.0
S: on

GBmaster said:
plz help, I tried to flash my phone today and now the usb does not work under fastboot anymore, when i try to put the phone in fastboot and type the command in cmd it just says *waiting for device* and i have to use cmd for flash the boot.img so in theory i think my phone is brickt, but i can access my sd card and all that stuff but my phone wont boot, can sombody plz help?
HBOOT 2.02.0002
RADIO-3831.10.00.11_M
ROM: sabsa_prime_V10.0
S: on
Click to expand...
Click to collapse
Are you trying fastboot commands or adb?
Try this, when in android
"adb reboot bootloader"
then when its in bootloader,
"fastboot devices" and see if your serial number comes up

markj338 said:
Are you trying fastboot commands or adb?
Try this, when in android
"adb reboot bootloader"
then when its in bootloader,
"fastboot devices" and see if your serial number comes up
Click to expand...
Click to collapse
trying fastboot commands yes, but the phone does not go into usb mode
C:\android>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
that did not work either

is there anyway to flash the boot.img file from cwm? thats what i need to get the phone working again!

Do you Use Win8?

Silversniper said:
Do you Use Win8?
Click to expand...
Click to collapse
no i use windows 7! tryd on every computer i have and still the same, no usb in fastboot

Nobody knows how to fix it?
Sent from my GT-P5110 using xda app-developers app

I am having a similar issue, the phone boots and the USB port works fine in recovery and when booted but nothing happens when it is plugged into the PC in fastboot mode. It is not the PC as other phones work fine in fastboot etc. It seems like the fatboot part of the hboot does not recognise USB, there is not even any device appearing in the device manager (unknown or known) when the phone is in fastboot and connected to the PC, it should change on the phone to say "FASTBOOT USB" when connected to the computer, It makes unlocking the boot loader a bit difficult as I cannot execute the fastboot oem command to get the unlock code from htcdev.com

Stuck in bootloop. No custom recovery or unlocked bootloader.

So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?

As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.

ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info

or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.

AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.

AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair

Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.

Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?

CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes

CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.

CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.

Remote command not allowed for unlocked bootloader

I want to flash custom recovery in my phone but it shows
remote: command not allowed
In bootloader, it shows that it is unlocked.
i get the same error when I type
fastboot oem devices-info
remote: command not allowed
I tried
fastboot oem unlock XXXXXXX(huawei code)
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock
it shows
remote command not allowed
The recovery is still Huawei e-recovery, it asked me to download the update but it always failed when it comes to download package.
What should I do now?

hjaxuan said:
I want to flash custom recovery in my phone but it shows
remote: command not allowed
In bootloader, it shows that it is unlocked.
i get the same error when I type
fastboot oem devices-info
remote: command not allowed
I tried
fastboot oem unlock XXXXXXX(huawei code)
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock
it shows
remote command not allowed
The recovery is still Huawei e-recovery, it asked me to download the update but it always failed when it comes to download package.
What should I do now?
Click to expand...
Click to collapse
Connect to pc, issue unlock command, then
Fastboot flash recovery xxxxx.img
Where xxxxx is the name of custom recovery file. Take a picture of the error, if any and share here

muradulislam said:
Connect to pc, issue unlock command, then
Fastboot flash recovery xxxxx.img
Where xxxxx is the name of custom recovery file. Take a picture of the error, if any and share here
Click to expand...
Click to collapse
as i said, it shows that the phone already unlocked.
I able to flash the recovery successfully but when i tried to boot my recovery
it will show
remote command not allowed

hjaxuan said:
as i said, it shows that the phone already unlocked.
I able to flash the recovery successfully but when i tried to boot my recovery
it will show
remote command not allowed
Click to expand...
Click to collapse
To boot your recovery, disconnect from pc, press and hold power, vol up until a reboot, let go of power but keep the other pressed for about 5,6 sec more.

muradulislam said:
To boot your recovery, disconnect from pc, press and hold power, vol up until a reboot, let go of power but keep the other pressed for about 5,6 sec more.
Click to expand...
Click to collapse
Even though I had flash the recovery, when i enter recovery mode using this method, it is still showing huawei e recovery

hjaxuan said:
Even though I had flash the recovery, when i enter recovery mode using this method, it is still showing huawei e recovery
Click to expand...
Click to collapse
Did you disconnect it from PC before pressing and holding power, Vol up?
Just making sure...

muradulislam said:
Did you disconnect it from PC before pressing and holding power, Vol up?
Just making sure...
Click to expand...
Click to collapse
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked

hjaxuan said:
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
Click to expand...
Click to collapse
And power + vol down also boots to fastboot mode?
If this is the case then I am of no help to you at all. Another user is facing the same problem and no solution there till now.

hjaxuan said:
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
Click to expand...
Click to collapse
Phone off, disconnect cable to PC, vol+ and power - enter to recovery

DRUGER said:
Phone off, disconnect cable to PC, vol+ and power - enter to recovery
Click to expand...
Click to collapse
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed

hjaxuan said:
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
Click to expand...
Click to collapse
Try to unlock bootloader again using
Fastboot OEM unlock xxxxxxxxxxxxxxxx
And then try flashing twrp again using
Fastboot flash recovery2 xxxxxx.img

muradulislam said:
Try to unlock bootloader again using
Fastboot OEM unlock xxxxxxxxxxxxxxxx
And then try flashing twrp again using
Fastboot flash recovery2 xxxxxx.img
Click to expand...
Click to collapse
I tried
fastboot oem unlock XXXXXXX
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock XXXXXX
it shows
remote command not allowed

hjaxuan said:
I tried
fastboot oem unlock XXXXXXX
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock XXXXXX
it shows
remote command not allowed
Click to expand...
Click to collapse
Just try
Fastboot OEM unlock xxxxxx
Followed by
Fastboot flash recovery xxxxxx.img
Many users reported that this worked. Don't do anything in between.

hjaxuan said:
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
Click to expand...
Click to collapse
build number your firmware???

druger said:
build number your firmware???
Click to expand...
Click to collapse
nem-l22c636b140

hjaxuan said:
nem-l22c636b140
Click to expand...
Click to collapse
You may put screenshot comand line whith comand flashboot
Also try this TWRP https://drive.google.com/file/d/0B1Ez6wAY1mj6c0xxaTBUWmZVN1k/view?usp=sharing (Chinese)

Huawei E-Recovery is a secondary recovery. Try adb reboot recovery.
Sent from my honor 5X using XDA Labs

DRUGER said:
build number your firmware???
Click to expand...
Click to collapse
U don't have proper drivers installed.

Hi all ! I had exactly the same issue... The problem was solved by using the TWRP-CN image pointed by Druger ! (thank you mate) Any other attempt resulted into a fail. Twrp is of course in chinese language but follow this, and your life will be a bed of roses : youtube.com/watch?v=KOhR92EKD7A
Hope this will help
Note : Chinese NEM-AL10 2gigs ram model.

Huawei honor 5c
Can somebody help me my huawei (5c) i tried to install twrp on phone and it say command is not allowed. Im unlocked bootloader, i writed adb reboot bootloader, adb fastboot flash recovery xxxx.img and then it says command not allowed. Ps my file name is twrp and i try twrp.img on flashing

"waiting for devices" in ADB While trying to install TWRP?

Updated today to OB14. Now trying to re-flash twrp. Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?

arachniac1 said:
Updated today to OB14. Now trying to re-flash twrp. Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
Click to expand...
Click to collapse
Just kill adb.exe with Taskmanager... And try again..

arachniac1 said:
Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
Click to expand...
Click to collapse
Something is not quite right. adb and fastboot have different requirements, and will never work at the same time.
adb = works in OS or TWRP, will not work in fastboot mode. Debugging must also be enabled
fastboot = only works in fastboot mode. Debugging enabled not needed.
So adb working, and fastboot not working is expected, but to me, means you are not in fastboot mode. Or your are changing modes/states between commands (which is really confusing).
Go into fastboot mode and type: fastboot devices
And see if it returns the phone ID.

Unlock OEM via ADB

Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks

_08_ said:
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
Click to expand...
Click to collapse
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.

shihabrumel said:
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
Click to expand...
Click to collapse
It won't let me. It says:
my command: fastboot oem unlock System: FAILED (remote "flashing unlock is not allowed")
Fastboot: error: command failed.
Same with the critical. I also had an error trying another command, it said, not allowed in lock mode.
Actually, I'm trying other commands and it's the same error with all comands.

My Mi A2 was not booting
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: