Develop Bugs

fastboot and "waiting for device"???

I'm trying to change the kernel (with DooMKernel) on my Arc.
I installed the ADB drivers (at least I hope ), in fact, when I plug in my arc in my device manager I can read:
-Android phone
->Android ADB Interface
So, when i tryed with fastboot.exe -i 0x0fce getvar version command, it's ok, I get a response back.
With fastboot flash boot boot.img, I get the "waiting for device"
What's the problem??

try type fastboot flash boot boot.img

But that won't flash the kernel...
Sent from my LT15i using XDA Premium App

beranchoi said:
try type fastboot flash boot boot.img
Click to expand...
Click to collapse
I get the same result!!
Flo95 said:
But that won't flash the kernel...
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
Sorry... I'm confused

Fastboot boot boot boot.img just boots the kernel but doesn't flash it.
Sent from my iPad 2 using Tapatalk

Is your boot loader unlocked ??

Flo95 said:
Fastboot boot boot boot.img just boots the kernel but doesn't flash it.
Click to expand...
Click to collapse
So, what's right command??
KingWickedd said:
Is your boot loader unlocked ??
Click to expand...
Click to collapse
yes, it's!! In my phone, open the dialler and enter *#*#7378423#*#* to access the service menu, and he says bootloader unlocked!!

fastboot flash boot boot.img is right
Sent from my iPad 2 using Tapatalk

Flo95 said:
fastboot flash boot boot.img is right
Click to expand...
Click to collapse
Even with this command, the result is the same!!

ssl3vin said:
Even with this command, the result is the same!!
Click to expand...
Click to collapse
did you try
Code:
fastboot -i 0xfce flash boot boot.img
?

drcyber said:
did you try
Code:
fastboot -i 0xfce flash boot boot.img
?
Click to expand...
Click to collapse
THANKSSSSS
yes, it works!!

use this https://rs639l3.rapidshare.com/#!do...r|6525|R~3AB292D7A53EFF1EE7A8A05879380BA4|0|0.
All drivers is on this file .
extract file and open the file" fastboot_with_Android_USB_file" ,so press shift and clic right bouton from mouse on the file fastboot, in the menu shoose "open the window command here".
The sreen CMD automaticly is opening .so you can write fastboot flash boot boot.img.

Amivieu said:
use this https://rs639l3.rapidshare.com/#!do...r|6525|R~3AB292D7A53EFF1EE7A8A05879380BA4|0|0.
All drivers is on this file .
extract file and open the file" fastboot_with_Android_USB_file" ,so press shift and clic right bouton from mouse on the file fastboot, in the menu shoose "open the window command here".
The sreen CMD automaticly is opening .so you can write fastboot flash boot boot.img.
Click to expand...
Click to collapse
Sorry, but the DRIVERS ARE OK, my phone is recognized as ADB interface!!!
but when I enter with fastboot flash boot boot.img, he show the message "waiting for device".
Instead with the command fastboot -i 0xfce flash boot boot.img it's works perfectly

drcyber said:
did you try
Code:
fastboot -i 0xfce flash boot boot.img
?
Click to expand...
Click to collapse
What does the -i 0xfce do? Because it works!

Daanmannetje said:
What does the -i 0xfce do? Because it works!
Click to expand...
Click to collapse
how does it work,this is what i get when i copy-past that line:
"""C:\Documents and Settings\Dedaj\Desktop\Xperia Arc\Xperia Tools\fastboot\fastboo
t>fastboot -i 0xfce flash boot boot.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
C:\Documents and Settings\Dedaj\Desktop\Xperia Arc\Xperia Tools\fastboot\fastboo
t>""""
so what i'm doing wrong!
EDIT:
Fixed

I got the same problem. I'm using Windows 8 and I got "waiting for device" error. I tried to write "-i 0xfce" but it didn't work. How can I fix this ?
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
And I also ran "cmd" as administrator but it did not work too.

im having the exact same problem
welocan said:
I got the same problem. I'm using Windows 8 and I got "waiting for device" error. I tried to write "-i 0xfce" but it didn't work. How can I fix this ?
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
And I also ran "cmd" as administrator but it did not work too.
Click to expand...
Click to collapse
im having the exact same problem we should make this more big so everyone can see it

APPLEMYASS said:
we should make this more big so everyone can see it
Click to expand...
Click to collapse
Or just Google fastboot Windows 8 and do some reading.

Check this
When the command window opens type 'fastboot devices'
What happens? what do you get?

Make sure u hv enabled USB debugging from Settings-> Development.
Hit thanks if I helped u...
Sent from my Xperia Arc using xda app-developers app

[Q] Complete noob needs help relocking bootloader

Okay so I have the One X, decided I wanted to root it even though I have NO IDEA what its all about (yes I know Im an idiot). I basically got as far as unlocking the bootloader then something went wrong and I couldnt get any further. I basically just want to relock the bootloader but I have no idea how. Like I said, Im a complete noob and need someone to really walk me through this the simplest way there is. Ps Im on a mac, which Im sure makes it even more difficult.
Any help is greatly appreciated :/

well, i don't know anything about mac, but i do know how to re-lock the bootloader under microsoft windows.
All you have to do is download FASTBOOT in any windows pc, download it from here
press and hold volume down + power button on your phone (to enter bootloader)
when in bootloader, enter fastboot mode by just hitting power key once,
now connect USB to pc and the phone
u'll see FASTBOOT PC written in your phone screen,
now go to the downloaded fastboot folder in ur pc,
hold SHIFT and Right click, Select OPEN COMMAND WINDOW HERE,
in the command window, just write : fastboot oem lock
That's it!

thanks so much for your reply. I'm gonna hold out and see if anyone can give me a mac reply but I'm gonna see if anyone I know can lend me their laptops and try what you said. thanks again
Sent from my HTC One X using xda app-developers app

becatron said:
thanks so much for your reply. I'm gonna hold out and see if anyone can give me a mac reply but I'm gonna see if anyone I know can lend me their laptops and try what you said. thanks again
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
here is a thread explaining how to unlock on mac, quite simple steps
to lock the bootloader, all u need is to write ./fastboot-mac oem lock instead of ./fastboot-mac oem unlock :good:

I tried that link before and its never worked. I dont have a great understanding of Terminal and it usual gives me something along the lines of 'no such file or directory'.
Edit: I just got '-bash: ./fasboot-mac: No such file or directory'

becatron said:
I tried that link before and its never worked. I dont have a great understanding of Terminal and it usual gives me something along the lines of 'no such file or directory'.
Edit: I just got '-bash: ./fasboot-mac: No such file or directory'
Click to expand...
Click to collapse
That means that you haven't downloaded fastboot!
You need to download fastboot.exe to perform this operation.
or simply visit some friend with a windows pc and do the task

still can't get my hands on a Windows laptop :/ just moved house too so don't even have any wifi agh.

One question, do you have the Android SDK installed? I can help you with the mac since it is the same as linux
arun6106 said:
That means that you haven't downloaded fastboot!
You need to download fastboot.exe to perform this operation.
or simply visit some friend with a windows pc and do the task
Click to expand...
Click to collapse
.exe extentions doesn't work on Macs :silly:

matt95 said:
One question, do you have the Android SDK installed? I can help you with the mac since it is the same as linux
Click to expand...
Click to collapse
I'm sorry but Wtf does sdk mean?

becatron said:
I'm sorry but Wtf does sdk mean?
Click to expand...
Click to collapse
Lol, download this file then unzip it, using the terminal go to that folder and type
Code:
./fastboot oem lock

matt95 said:
Lol, download this file then unzip it, using the terminal go to that folder and type
Code:
./fastboot oem lock
Click to expand...
Click to collapse
I'll try this tomorrow after work. thank you for taking pity on me and helping and not laughing me off the forum

becatron said:
I'll try this tomorrow after work. thank you for taking pity on me and helping and not laughing me off the forum
Click to expand...
Click to collapse
Don't worry :good: no one is a genius in here

matt95 said:
Lol, download this file then unzip it, using the terminal go to that folder and type
Code:
./fastboot oem lock
Click to expand...
Click to collapse
Okay so just tried this and its not working. How and what exactly do I type? When I type ./fastboot oem lock it just brings up a big page of abbreviations and commands. Its also saying ERROR: Could not get pipe properties
This is so stressful

becatron said:
Okay so just tried this and its not working. How and what exactly do I type? When I type ./fastboot oem lock it just brings up a big page of abbreviations and commands. Its also saying ERROR: Could not get pipe properties
This is so stressful
Click to expand...
Click to collapse
Is your phone in fastboot mode? if yes it should work, you should see a red highlighted "fastboot usb"

matt95 said:
Is your phone in fastboot mode? if yes it should work, you should see a red highlighted "fastboot usb"
Click to expand...
Click to collapse
Yep it is.. This is what I got
Rebeccas-MacBook:~ administrator$ /Users/administrator/Downloads/android\ 3/fastboot oem lock
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
...
ERROR: bulkOut endpoint not assigned
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
I know im probably not writing it properly

You need to download the file I posted, unzip it, navigate to that folder and then try to type exactly what I write
Code:
./fastboot
paste here what you get
Sent from my HTC One using XDA Premium 4 mobile app

matt95 said:
You need to download the file I posted, unzip it, navigate to that folder and then try to type exactly what I write
Code:
./fastboot
paste here what you get
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is what I get when I type ./fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Rebeccas-MacBook:~ administrator$

OK! fastboot is working, now do it again but type
Code:
./fastboot oem lock

matt95 said:
OK! fastboot is working, now do it again but type
Code:
./fastboot oem lock
Click to expand...
Click to collapse
Nope its still not working
Rebeccas-MacBook:~ administrator$ ./fastboot oem lock
-bash: ./fastboot: No such file or directory
Rebeccas-MacBook:~ administrator$ /Users/administrator/Downloads/android\ 3/fastboot ./fastboot oem lock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Rebeccas-MacBook:~ administrator$

You have to type
Code:
./fastboot oem lock
not
Code:
3/fastboot ./fastboot oem lock

Nokia X ADB Driver autoinstall for Windows

Guys, here's the ADB driver for the Nokia X, just run the exe and you're done
https://www.dropbox.com/s/xz7hu90lvvhm47f/NokiaX_ADB_Driver.exe
Note: For fastboot you need to use this :
HTML:
fastboot -i 0x0421 <command>
example
HTML:
fastboot -i 0x0421 flash boot boot.img

AngSanley said:
Guys, here's the ADB driver for the Nokia X, just run the exe and you're done
https://www.dropbox.com/s/xz7hu90lvvhm47f/NokiaX_ADB_Driver.exe
Note: For fastboot you need to use this :
HTML:
fastboot -i 0x0421 <command>
example
HTML:
fastboot -i 0x0421 flash boot boot.img
Click to expand...
Click to collapse
Sir one help my Nokia x device only connected emergency contivity on pc and not turn on plz hel me sir

arulkumareee said:
Sir one help my Nokia x device only connected emergency contivity on pc and not turn on plz hel me sir
Click to expand...
Click to collapse
Try this fix http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617

please i want it for 32 bit
it run only in 64 bit

abdelbdee said:
please i want it for 32 bit
it run only in 64 bit
Click to expand...
Click to collapse
Here http://ultradevs.blogspot.com.eg/2016/02/Nokia-X-XL-Drivers.html

[Flashing STOCK ROM from Custom Rom] [No Recovery Mode, Fastboot accessible]

I followed these steps and now my Asus zf2 (ze551ml) is back alive! For the issue mentioned below, I didn't find much anywhere so I thought I'd put here what helped me.
Issue: Only fastboot mode accessible, can't enter recovery. (Also my bootloader was locked, MM bootloader, No OS). After selecting recovery mode from bootloader, again it enters fastboot, i.e the process in video above couldn't install the recovery (This must be because my bootloader was locked). I tried unlocking the bootloader by the .bat files available on XDA but since I'd not enabled OEM unlocking, unlocking failed everytime. My OS got wiped out, so only fastboot mode was accessible.
Solution:
I believe you have installed Minimal ADB and fastboot on your PC.
Download the raw file from the XDA thread.
Now first of all, change extention of the .raw firmware file to .zip.
Then just extract all files from it into adb and fastboot folder.
Now in folder (where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
Perform the following commands one after another:
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again, if USB debugging was on then this will definitely work)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. Don't worry, first boot gonna take a little longer time.

Download raw file
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance

bb04 said:
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
Click to expand...
Click to collapse
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
FYI, I didn't add the links because one can't add external links in their first posts.

mukunds11 said:
FYI, I didn't add the links because one can't add external links in their first posts.
Click to expand...
Click to collapse
it could be better if you would have removed or edited last line while copying commands

help. my phone condition is just like this. at first when i connected my phone to computer, powershell detected it, but then after a while, my phone disappeared from powershell. can someone help me ?
edit, i just did the thing and its doing fine even though my phone look like it is not detected

Question Does anyone have FULL Fastboot Flashing steps?

Does anyone have the full fastboot flashing steps from the Bootloader to everyfile in the image file.zip?

I'm not sure exactly what you're asking. To be rooted? To merely flash full stock firmware? If the latter, just extract the full firmware zip and the latest Platform Tools into the same folder. If you don't want to wipe your phone, edit the Flash-All.bat with Notepad (assuming you're running Windows) and remove the "-w ", and save the file. Then open a command prompt in that folder, type Flash-All.bat and press enter. That's it.
If you're asking what are the steps the Flash-All.bat takes to flash everything that's in the inner zip file that's unextracted, just open the Flash-All.bat with Notepad and take a look.
If you're wanting to be rooted, [GUIDE] Root Pixel 6 Pro with Magisk.
If none of my guesses are correct, please be more specific of what exactly you're asking.

Wouldn't it be just fastboot flash filename "file location" for each file?

spart0n said:
Wouldn't it be just fastboot flash filename "file location" for each file?
Click to expand...
Click to collapse
Every device is different, with Motorola we started with :
fastboot gat-var
and flashed each image seperately.

The "flash-all.bat" only does a "fastboot update <update.zip>" - so no individual flashing of image files.....

s3axel said:
The "flash-all.bat" only does a "fastboot update <update.zip>" - so no individual flashing of image files.....
Click to expand...
Click to collapse
Yea, but i cannot tell where the image.zip is getting hung up at if i run that.

AndroidAddict420 said:
Yea, but i cannot tell where the image.zip is getting hung up at if i run that.
Click to expand...
Click to collapse
You could open a command shell and run the flash-all.bat from there - then you at least see the output of the command.
Or you can enter the commands from the flash-all.bat manually in a commandline window (everything starting with "fastboot..." )....

s3axel said:
You could open a command shell and run the flash-all.bat from there - then you at least see the output of the command.
Or you can enter the commands from the flash-all.bat manually in a commandline window (everything starting with "fastboot..." )....
Click to expand...
Click to collapse
I am using LIX

AndroidAddict420 said:
I am using LIX
Click to expand...
Click to collapse
OK, I don't know LIX - is that some kind of Linux ?
I would still assume you can execute the dividual fastboot commands from the flash-all.bat (flash-all.sh) manually ?!

s3axel said:
OK, I don't know LIX - is that some kind of Linux ?
I would still assume you can execute the dividual fastboot commands from the flash-all.bat (flash-all.sh) manually ?!
Click to expand...
Click to collapse
LIX is short for Linux

I'm not sure if fastboot would work in a Linux terminal window as I've always used Windows... Best of luck finding a solution!
Oh, and by the way, you can use fastboot in CMD and flash individual partitions with it. An example command of flashing the bootloader file would be:
"fastboot flash bootloader bootloaderfilename.img"
You essentially just have to change the last word before the filename to flash different partitions (aside from when you're flashing the update image, as it's a little bit different then).
Also note that the bootloader.img file would have to be in the exact same location as your adb and fastboot files. But again, I'm not at all sure how it would work on Linux...

NippleSauce said:
I'm not sure if fastboot would work in a Linux terminal window as I've always used Windows... Best of luck finding a solution!
Oh, and by the way, you can use fastboot in CMD and flash individual partitions with it. An example command of flashing the bootloader file would be:
"fastboot flash bootloader bootloaderfilename.img"
You essentially just have to change the last word before the filename to flash different partitions (aside from when you're flashing the update image, as it's a little bit different then).
Also note that the bootloader.img file would have to be in the exact same location as your adb and fastboot files. But again, I'm not at all sure how it would work on Linux...
Click to expand...
Click to collapse
Why would anyone ever change their bootloader?

spart0n said:
Why would anyone ever change their bootloader?
Click to expand...
Click to collapse
To update it.

If you want to flash each image separately, you can follow these steps (for some images, sequence is important, so I suggest following the sequence below to avoid issues)
Code:
################################################
### Files from the root of the factory image zip
################################################
# bootloader (replace <version> with the bootloader file version)
fastboot flash bootloader bootloader-raven-slider-<version>.img
# reboot to bootloader
fastboot reboot bootloader
# radio (replace <version> with the radio file version)
fastboot flash radio radio-raven-<version>.img
# reboot to bootloader
fastboot reboot bootloader
#####################################################
### Files from the image zip in the factory image zip
#####################################################
# boot
fastboot flash boot boot.img
# dtbo
fastboot flash dtbo dtbo.img
# vbmeta
fastboot flash vbmeta vbmeta.img
# vbmeta_system
fastboot flash vbmeta_system vbmeta_system.img
# vbmeta_vendor
fastboot flash vbmeta_vendor vbmeta_vendor.img
# vendor_boot
fastboot flash vendor_boot vendor_boot.img
# reboot to fastboot
fastboot reboot fastboot
# super
fastboot flash super super_empty.img
# product
fastboot flash product product.img
# system
fastboot flash system system.img
# system_ext
fastboot flash system_ext system_ext.img
# system_other (replace <other> with the inactive slot)
fastboot flash system_<other> system_other.img
# vendor
fastboot flash vendor vendor.img
# vendor_dlkm
fastboot flash vendor_dlkm vendor_dlkm.img
# reboot
fastboot reboot