adb bootloader prblems - ONE Q&A, Help & Troubleshooting

I'm running Ubuntu CLI only and am running into a little problem.
When I have my phone booted into cm11/cm12 and I run adb devices I can see my oneplus one, however when I reboot to the bootloader andd see the fastboot icon displayed on the phone i no longer see my phone when I run adb devices.
This isn't a huge problem as long as I have a rom saved to the emulated sdcard, however if I run into problems and loose a backup rom how would I go about pushing a rom to my onplus one since I cannot see the onplus in fastboot?
Thanks for any and all help, and I hope I have provided enough info!

nevermind
Im and idiot... I booted into recovery and adb worked there, I'm used to always pushing from the bootloader so didn't even think to try this.

Adb doesn't work in fastboot mode, only fastboot works in fastboot mode.
Transmitted via Bacon

Related

[Q] Unable to Flash Custom Recovery, ADB not detecting device, etc.

First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
cm recovery
WunderWuffle said:
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
Click to expand...
Click to collapse
uncheck update cm recovery under settings..developer option..
WunderWuffle said:
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
Click to expand...
Click to collapse
My first piece of advice: stop using a toolkit, it's clearly creating more confusion than it's actually helping.
When you're issuing the 'adb devices' command are you booted into Android? What happens when you issue 'fastboot devices' when you're in fastboot mode?
Transmitted via Bacon
paztine said:
uncheck update cm recovery under settings..developer option..
Click to expand...
Click to collapse
Its always been unchecked.
timmaaa said:
My first piece of advice: stop using a toolkit, it's clearly creating more confusion than it's actually helping.
When you're issuing the 'adb devices' command are you booted into Android? What happens when you issue 'fastboot devices' when you're in fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
When I did adb devices, I was in Android iirc. I can't remember since the last time I did it was a day or two ago. Sorry. I am not very knowledgeable in this area. I have not done the fastboot device command.
WunderWuffle said:
Its always been unchecked.
When I did adb devices, I was in Android iirc. I can't remember since the last time I did it was a day or two ago. Sorry. I am not very knowledgeable in this area. I have not done the fastboot device command.
Click to expand...
Click to collapse
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
timmaaa said:
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
Click to expand...
Click to collapse
I just did that. Here are my results. It says that my device has been tampered with, and my boot loader is unlocked. And now, for some odd reason (I guess I was in fastboot while I was doing adb commands), it not detects my One. Thank you!
demkantor said:
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
Click to expand...
Click to collapse
Since I am not on my computer anymore, I will check these out and I will get back to both of you in a bit. Thanks!
timmaaa said:
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
Click to expand...
Click to collapse
demkantor said:
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
Click to expand...
Click to collapse
I rooted the phone manually using command prompt and everything worked! I got TWRP recovery, and Root Checker says I'm rooted! Thank you very much! Doing it this way took my less than 7 minutes while using the toolkit took me more than three hours, and that didn't even work!

adb commands not working in fastboot mode. Is it normal?

I was trying to flash a custom ROM on my moto g xt1033. I used choosing the zip from USB otg after wiping and formatting everyrhing but. It flashed but a black screen came instead of cm logo and I was stuck at welcome to cm screen without touchscreen working. http://forum.xda-developers.com/mot...4-4-4-help-t3019082/post58587594#post58587594
Then I tried side loading or pushing method. But problem is adb commands are not working in fastboot mode. They are working when phone is switched on. (Adb devices show serial number and device in normal mode) Fastboot commands are working fine in fastboot mode but not adb. When I type adb devices in fastboot mode there is nothing after list of device attached. So adb push or adb side load give me waiting for device or device not found result. Is it normal. Earlier I have latest Motorola device manager and latest android SDK. Tried uninstalling and installing them, tried changing USB ports, tried rebooting the phone and restarting windows pc several times but still no luck.!!
Yes, it's normal that ADB commands do not work in Fastboot mode. But you can access custom recovery from the fastboot screen.
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Guru.Eclairs said:
@lost101 if adb commands do not work in fastboot mode then how "adb sideload" works when we clean install a ROM? Many threads at XDA say it should work
Click to expand...
Click to collapse
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
lost101 said:
You have to be in a custom recovery (TWRP, CWM, Philz Touch) and enable the 'adb sideload' option.
Click to expand...
Click to collapse
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Guru.Eclairs said:
I have latest philz touch. Also tried twrp..but adb still not working in fastboot mode or recovery mode. The device disappears from My Computer area when in fastboot
Click to expand...
Click to collapse
It doesn't work on all versions of Windows; I think I've had it working in Windows 7. But I mainly use it in Linux - where no driver is required.
I also have windows 7.. Thanks Anyway
Guru.Eclairs said:
I also have windows 7.. Thanks Anyway
Click to expand...
Click to collapse
It's a driver issue. Your phone is not being recognised. If you boot a Linux LiveCD from DVD / USB, you can access recovery mode ADB that way.
sudo apt-get install android-tools-fastboot​
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
audit13 said:
Not sure if this will help but, after completely wiping my phone, I installed TWRP using fastboot commands, booted to TWRP, mount, copy ROM to moto g, and install using TWRP.
If you are in fastboot mode, type fastboot devices and see what happens.
Click to expand...
Click to collapse
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
audit13 said:
I'm not 100% sure how adb works on the moto g but I don't think adb commands work in fastboot mode. When I connect my moto G to my computer after the ROM has booted and I am at the phone's desktop, I type "adb devices" and I see my device listed. Then I type "adb reboot-bootloader" to get into fastboot mode and adb commands no longer work.
I have Philz Touch on my Moto G and sideloading is an option. I don't think you can side load from fastboot.
Click to expand...
Click to collapse
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Guru.Eclairs said:
If adb doesn't work in fastboot mode then whats the propose of word "sideload"
Click to expand...
Click to collapse
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
audit13 said:
I have no idea as I have never used adb to install anything except apk files when the phone has been booted to the desktop.
I always use fastboot commands to install recovery and install stock ROMs.
Using adb to side load may refer to the aibility to install files while the phone is running.
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
Click to expand...
Click to collapse
​
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Guru.Eclairs said:
​
OK leave it. Do you have any idea how to increase 2g/3g speed. Any trick/mod/script?? I flashed cm11 quarx build and internet is painfully slow
Edit- no sideload means pushing a flashable zip to the root of internal storage when phone is in recovery mode. We do it for clean installing ROMs.(Format and wipe everything). After format there is no operating system left in phone so we do sideload rom
Click to expand...
Click to collapse
Sorry, I don't know how to increase speed except try a different radio/modem on your phone. I rarely use data on my phone because I have an iPad with LTE.
Guru.Eclairs said:
Fastboot Devices command works flawlessly in fastboot mode. I can flash .IMG files. But none of adb commands working. When I type adb devices there is no result after List of Devices attached. So I can't sideload anything
Click to expand...
Click to collapse
Sounds like your fastboot driver is working fine but your adb driver is not...go into your custom recovery and then check Device Manager in Windows to see if you have all your drivers working properly.
If you are having adb driver issues you could try the Universal adb driver setup file attached.
adb commands don't work in fastboot mode. Install a recovery (Preferably TWRP because I forget how CWM's adb sideload works). For TWRP, go to advanced, then adb sideload. Make sure to install the adb drivers tho, or else the sideload won't work. If you're sticking with stock, press the Vol+ button for about 15 secs, then tap the power button. Use the Vol- and + keys too scroll. There should be an option like "Install firmware through adb" or something. Scroll to that, then hit the power button to go to that option. Then, just sideload the firmware.
Check device manager 1st phone is conected properly
adb has no relation to fastboot.adb will not work while in fastboot, it never worked that way either.
There is no sideload while in fastboot, you're confusing it with the adb sideload, that has nothing to do with fastboot.
Reading and comprehension are desirable here.

Wiped OS, ADB not working, verge of tears

I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Acrylicus said:
I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Click to expand...
Click to collapse
If you are able to get into TWRP then this link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 will surely help you
- Install your device drivers first (If they are installed properly, then only skip this)
- Once adb and fastboot files are loaded on your computer, open command prompt and type command "fastboot devices". If you see your device serial number on the prompt, you are good to proceed ahead with flashing procedure.
- I recommend you to flash fastboot images of CMOS12 using that link.

Bricked Device Help

Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Kogecha said:
Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Click to expand...
Click to collapse
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Renosh said:
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Click to expand...
Click to collapse
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Kogecha said:
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Click to expand...
Click to collapse
Twrp also has USB-OTG function .. Even if you don't have any ROM on phone .. You can download a rom to a usb pendrive and connect it to phone twrp will recognize the USB pendrice and then can install rom from that ..
sent from Bacon (OnePlus One)

No OS... TWRP won't display files on otg/sd

I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file
emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb
I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...
emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.
I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going

Categories

Resources