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
Related
I am trying to unlock my device and keep having the problem of it not being recognized in fastboot.
I have the latest drivers from the android SDK (4.0), and have trying reinstalling them. It appears to mount fine, and all of the adb commands work. However, when I try fastboot devices, it returns nothing. fastboot oem unlock only gives a "waiting for device".
Any ideas?
Thanks
Device needs to be in the fastboot screen of the bootloader...
Sent from my Nexus One using XDA App
While I feel really stupid for somehow missing that fact in dozens of threads, it doesn't seem to fix the problem. I now have it in fastboot and at the top is says "FASTBOOT USB". Windows recognizes the device when its plugged in, but still no luck with devices.
Nevermind, I figured it out. It downloaded fastboot from another source. I am guessing that I was somehow missing a file. Thanks though.
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
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 installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??
What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.
Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)
Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.
It finally worked, thanks a lot brother :laugh:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.