Hey guys. I am running ubuntu 10.10 and i have successfully installed android sdk and the eclipse in their proper places and added the neccessary coding to make everything work. One problem though. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL. i know others have achieved to being able to flash it without a problem.. I have tried to troubleshoot this myself with the help of the internet and xda... but still the same problem keeps re occuring. and to tell you the truth, it is really pissing me off. I have downloaded fastboot drivers and placed them in the sdk/tools folder and moved adb to that folder as well for easier access. I dont know what else to do. If any one has any solutions or would be a help please. Thank you for reading.
bosna110 said:
. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL
Click to expand...
Click to collapse
The question is: can linux see the phone (plug in the phone while in fastboot mode and check dmesg)
If linux sees it and fastboot can't.. make sure its not permission issues [read is fastboot running as root? if not can your user read the USB device?] The phone identifies its self differently in fastboot mode vs. adb/mass storage mode. So don't assume the fact adb works from your normal login means fastboot will also.
linux sees it no problem.. but when im in fastboot mode, its not wanting to list the device.
Try executing fastboot as root.
Sent from my Gingerbread on Dream using XDA App
ok give me 1 sec.. ill go try it our right now. i am trying to flash terry's spl and radio so i can have the extra 14 or 15 megs of ram extra because my g1 is so sluggish right now i can barely use it for anything.
Strange thing with me is that it loads a different driver in fastboot. If I have it turned on normally, in my Device Manager it shows as "ADB interface -> HTC Dream Composite ADB Interface". (I think it used to show as just "HTC Dream"). I had to switch to HTC Bootloader. :/
Edit: only skimmed. Missed anything about Linux.
He's on linux ... the drivers should load automatically.
Sent from my Gingerbread on Dream using XDA App
ok i must be doing something wrong its either me or the laptop.. im doing "su" on the terminal and then when i enter in my password, it says auth failed.... this is friggen bee ess
Try
sudo fastboot devices
And when asking for the password you enter your user's password.
Sent from my Gingerbread on Dream using XDA App
still doing the same thing.
ok, what i did was
1. open terminal
2. cd sdk/tools
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
4. then when i look at the listed devices, my phone isnt listed..
5. then i try doing sudo fastboot devices and entering my password and its still not working.
let me try restarting my laptop.. perhaps that is going to fix it..
ok, just to make my self look dumber lol.. when my phone is shut off
i pressed back and the power buttons at the same time until the white screen with the android skateboards come up.. am i supposed to then press the trackball button to get into fastboot mode?
cause maybe i am not pressing something correctly to get it to work right. ill keep refreshing this page every minute for a reply..
bosna110 said:
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
Click to expand...
Click to collapse
adb will never work if you are in fastboot mode... and fastboot will only work when in fastboot mode.
so Dont run './adb devices' run './fastboot devices' or as we mentioned to run it as root 'sudo ./fastboot devices'
ok, gotcha. when i did the ./fastboot devices, it told me the Permission denied.
im sorry, i must be really brain dead right now.. i totally forgot to checkmark fastboot as an exectuable on its properties.. now its recognizing my G1 no problem. now its the flashing that is giving me some trouble
Related
So it seems to me that trying to read other threads about using fastboot is that it's pretty specific to the phone you're using. None of the other fastboot threads work for me when trying to get fastboot to load up on the comp here. I have it installed, have the path right, and can't get it to stay up. It pops up, runs a ton of script and closes. I never get a chance to type anything in to any line anywhere, muchless actually send a command. I need help and am totally lost
So so lost
I am totally lost and have absolutely no idea which direction to be going to learn this stuff. Any links to useful info for our phone, or anything you can find or tell me or whatever is apprechiated. I believe the problem is in the SDK, since I can never get the command screen open for more then a second. Or I may just be a total idiot. Should I be booting into fast boot on the phone and then plugging in, or plugging in then booting up? Do i have to open fastboot on the computer first or second? Or do I even open fastboot on the computer. Simply put I cannot get the phone and computer to link up, or keep a dialog box open on the computer end to send commands thru.
Ok so Ive gotten as far as knowing that I have fastboot on the computer and ADB. Now I cant figure out how to get the device to register. I uninstalled and reinstalled drivers as all the reading has told me to do. When I boot into fastboot on the phone, and plug in, the google fastboot driver recognizes the phone is there but ADB isn't coming up. In all of the reading I've done in this case it says to uninstall all drivers associated with the phone and plug it in while in fastboot. I did this, twice, to no avail. I then reinstalled all the drivers and am still stuck at not being able to get my device recognized by adb
You have to access those through a command prompt.
Sent from my Zio using XDA App
basically if it was working I may not know. I have no idea what happens or how to use fastboot or adb. but I think it should do something when I plug the phone into the usb in fastboot. it should bring up a command window for telling the phone what to do right? or do I have to do something to get the command window open. as far as i can tell everything is working like it should.
Ok this is where I must be lost. shouldnt there be a window to type the prompt in to?
YEAH NEVERMIND
Black background, no skaterboarders?
Hello.
Slowly learning noob. I have a Zio from Cricket (as yet unmodified), running Android 2.2.1. I'm a Mac user (OS X 10.6, if it makes a difference).
I've downloaded adb, and confirmed it's working by using "adb devices" to identify my phone.
I've downloaded fastboot-for-mac. I've been able to reboot my phone using "fastboot reboot". BUT, the command "fastboot devices" returns "??????????????? fastboot".
I'm wondering if my phone's actually in fastboot mode. I power-off the phone, then simultaneously press-and-hold the Send (green) and End (red) buttons. After a few seconds, I see a black screen with white writing. I do not see the white screen with 3 skateboarders that my reading here, and Google Image search, leads me to expect. I assume I'm doing something wrong. I haven't discovered what, though. Advice would be appreciated.
When you boot up with end/send the Zio boots in to fastboot yes.....
Sent from my M865 using XDA Premium App
Thanks!
That tells me I am in fastboot. Any suggestions about why "fastboot devices" returns only a string of question marks?
I don't want to proceed with rooting, etc., if I can't even get fastboot to identify my device.
You should beable to root without fastboot just dl universal androot from market and run. I personaly would wait til u have a chance to use a windows based pc to run fastboot and install spz0 2.1 rom.
Sent from my Zio using XDA App
Sounds like a environment variables path issue. Running Windows 7?
Sent from my M865 using XDA Premium App
Alright so last night i was able to unlock my phone and root it no problem on my mac computer (which I regret and wish i did it on windows) but the phone worked great after. But after debating if I should unroot I went ahead and tried unrooting the phone but the phone would not activate, it became stuck in bootloader. Ive tried everything that I could look up online and even called google for help but they said to search online and ask the developers. Ive tried flashing the stock image back on but it wouldnt work, it kept saying ivalid boot image header fastboot reason fall-through from normal boot mode. I dont even think my computer is recognizing the phone anymore so I dont know how I would get back into terminal to flash anything. If anyone can help me I would appreciate it. I have no idea what to do now after trying for a whole day. Thanks all, hope someone can be a savior.
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
zephiK said:
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
Click to expand...
Click to collapse
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Is the device recognized by the fastboot command when connected to either the mac or pc?
zylstrajs said:
Is the device recognized by the fastboot command when connected to either the mac or pc?
Click to expand...
Click to collapse
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
Adb is for android. You want to use the command: fastboot devices
dnasr87 said:
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Click to expand...
Click to collapse
If you want to start over you'd want to be flashing the stock images https://developers.google.com/android/nexus/images
Have your phone in bootloader mode (vol down + power)
Go into the directory with fastboot and type fastboot devices.
If your environment is set up properly then it should display your device as the output. From there you can flash back to stock.
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
what does it say why you type
>fastboot devices
zylstrajs said:
what does it say why you type
>fastboot devices
Click to expand...
Click to collapse
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
dnasr87 said:
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
Click to expand...
Click to collapse
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
zephiK said:
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Click to expand...
Click to collapse
I did when I rooted it then once it crashed I tried to start over but wiped my computer.. I'll re download and try again
zylstrajs said:
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
Click to expand...
Click to collapse
I did it on my mac, if i try to connect my phone to a pc it wont recognize it because its stuck in bootloader. I have already tried connecting it
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
PaisanNYC said:
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
Click to expand...
Click to collapse
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
dnasr87 said:
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
Click to expand...
Click to collapse
Are you in the NYC area? I'd just come over with my laptop and do it for you.
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
not necessary some one can just use hangouts remote desktop to help you i thinks that's what they use on xda assist
Acer ADB
Your PC might not be recognizing because you got the Acer ADB of doom...
Just roll back your driver.
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
Don't send it to a stranger on the internet. You never know who is who behind a screen lol
Honestly bro, if i were close to you, I'd just do it for you. I have the stock image, drivers, and adb/fastboot all set up. i'm good at fixing things, horrible at explaining things.
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
I have a problem with trying to see the phone in cmd. Fastboot goes fine it connects I have all drivers on still nothing works at all. I can't figure it out cause I need to get rid of this bloatware.
jdwilder23 said:
I have a problem with trying to see the phone in cmd. Fastboot goes fine it connects I have all drivers on still nothing works at all. I can't figure it out cause I need to get rid of this bloatware.
Click to expand...
Click to collapse
I'm sorry but you'll have to elaborate on your problem. Are you having trouble using adb in cmd? As in no devices list when you type adb devices but they do when you type fastboot devices ? You may need to check what you downloaded/installed and make sure that the folder that it downloaded to--that you've cd'ed into to use adb/fastboot--does contain adb.exe. I suggest this installer straight from Google. Also, adb will only display/connect devices when it's not in fastboot mode.
idk
I'm having problems with getting my token code to unlock my boot loader thru HTC but I downloaded the right software and it does recognise the device as adb but when I go into cmd prompt and type fastboot oem get_token_identifier it's not recognized and doesn't do anything. So I'm stuck on getting my token for htc
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!