Related
The usual DISCLAIMER: Use at your own risk!
Fastboot mode usually comes up if something went wrong when trying to flash a recovery image, for example when flashing AmonRa recovery or ClockWorkMod. It happened to me several times so I tried to learn to revive it without reflashing the original firmware. Note: This tutorial works only if recovery is the only one broken. (If the ROM itself is broken, then that's a subject for another tut.) In this case, the most logical thing to do is just reflash the recovery image. So how do you do it in fastboot mode? Here's how:
Symptom
You tried flashing a custom recovery like ClockWorkMod or Thunderg, or you flashed an incorrect ROM, and when you rebooted, it showed this screen:
Code:
fastboot mode started
udc_start()
and the phone stays there. When you plugin the phone to your computer's USB, it is detected and the screen has this display:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
You will need
1) Your PC and your USB cable for the phone
2) USB drivers for your phone (use B2C from LG).
3) Android SDK (download from here)
4) Java, required to run the SDK (but right now I am not sure if this is required to run fastboot!)
5) ClockWorkMod or AmonRa Recovery.
Here's what to do
1) Assuming phone is turned on in fastboot mode, plug it in to the USB of your PC. You will know that it is detected if you see the the lines "suspend", "reset" and whatnot on the phone's screen.
2) Extract the recovery image from the zipfile downloaded from step#5 above (e.g. LGp500-recovery-v12.img). Place the image file in the same folder where fastboot.exe is (usually in the tools\ folder in the SDK). For your convenience, rename the img file as recovery.img
3) Fire up your command prompt and cd to the directory where fastboot.exe is located. Then type the following command:
Code:
fastboot erase recovery
Once you get the confirmation that it was successful, type this:
Code:
fastboot flash recovery recovery.img
Once you get the success confirmation, reboot the phone, or you can also type (optional):
Code:
fastboot reboot
The phone will reboot itself, and with any luck you should be able to go back to your same old Android bootscreen. Note that no settings were modified here, so this is extremely useful for those who do not want a clean slate after a fastboot nightmare.
Also, note that if this is successful, you can now boot to recovery with the usual button-combos, thus enabling you to flash ROMs and other recovery zips.
Note: On some SDK versions, fastboot may not be included. For your convenience, I have attached the fastboot binary I got from my downloaded SDK. I have also attached AdbWinApi.dll which some user reported is missing in the SDK. Place the DLL in the same folder where fastboot.exe is located.
Questions, just drop me a line here
thanks dude, its very usefull
Nice tutorial for newbies like me, thanks...
Sent from my LG-P500 using XDA Premium App
We already have a tut like this.
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
d3s3rt_eagle said:
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
Click to expand...
Click to collapse
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Usefull, thank you
Sent from my LG-P500 using XDA Premium App
Kudos to arvinoids.
This will be of great help in times of need.
Sent from my LG-P500 using Tapatalk
arvinoids said:
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Click to expand...
Click to collapse
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
d3s3rt_eagle said:
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
Click to expand...
Click to collapse
Wow, that's strange. I have r11 and it is included there. For your convenience, I have attached the fastboot.exe from r11 on the first post. Thanks for trying this out.
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
hey
I run the CMD
executed cd command but the next command
"fastboot erase recovery"
gives the following error ( see the image)
Please help
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
lekhwani said:
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Yes. For the first time.
DJoptimus-One said:
Yes. For the first time.
Click to expand...
Click to collapse
How is your phone now?
Sent from my LG-P500 using Tapatalk
lekhwani said:
How is your phone now?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Revived now
DJoptimus-One said:
Revived now
Click to expand...
Click to collapse
Good to hear that. I think this is your 2nd or 3rd day and you came across worst o1 modding scenario and overcame it. Kudos to you.
Sent from my LG-P500 using Tapatalk
AdbWinApi.dll is included in platform-tools
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Hi. Sorry I was away for the weekend and just got back. Thanks for reporting this. I just did a search on my desktop and found out that AdbWinApi.dll is included in the platform-tools package. I will add the instructions to download the package from the SDK. I'm glad you were able to revive your phone. Thanks again!
pymebrahimi said:
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
Click to expand...
Click to collapse
I'm afraid your issue may not be a subject for this tutorial. Fastboot mode is activated when the phone's recovery image is broken. May I know how you are sure that the recovery is actually broken?
Well I am trying to Flash the latest fagyi NAND for Blackstone - http://forum.xda-developers.com/showthread.php?t=1914723
So I did everything, but when I reached the fastboot thingy, I did this:
After ROM flashed, took batter out and restarted device.
Blue screen showed up, forced fastboot, ready USB state, so I connected to PC
Then I opened a command prompt, so now what should I enter in the command prompt! I am using fagyi's fastboot!
Thanks, in advance!
Sorry for double posting, but please someone answer me, or atleast give me a tip/advice!
Do you mean this part?
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
Click to expand...
Click to collapse
post-mortem said:
Do you mean this part?
Click to expand...
Click to collapse
Yeah that exactly!
Step 2 says
2. Extract the 'adb files & fastboot.exe' files to a folder
Click to expand...
Click to collapse
so the 1st question is, do you know what folder you put those files in? Note that we're talking about your computer, not your phone. On your computer, open a command prompt by doing Start -> Run... -> cmd (This is Step 13). Navigate to the folder from Step 2 This is Step 14). Then, type the appropriate commands from Steps 15 & 16.
Still don't get it? Ask away!
Um the files are placed in C:
And when I enter the commands, it says 'File too big to fit in memory"? What do I do now?
So your step 14 should be to type cd c:\, then 15 fastboot flash recovery recovery.img
Is that when you get the error?
Yes, exactly then!
Ok, try redownloading the fastboot program, or install the Android SDK to get the newest version directly from Google.
I've redowloaded it alot of times! And I already have the Android SDK and am using the latest one!
Are you sure that you're using the correct version of all relevant programs? By that, I mean 32 vs 64-bit.
I am not sure about that, how should I know?
Do you get the same error if you type fastboot devices ?
I havent typed that yet!
EDIT: No I get this - "RH104393397 fastboot"
Please Admin/Moderator, lock this thread, my problem is now fixed!
Angat said:
Please Admin/Moderator, lock this thread, my problem is now fixed!
Click to expand...
Click to collapse
Can you tell me how do you fix the problem ? I have the same problem
Hey guys I'm in the process of using the new rooting method and I'm at the part where I put the unlock_code.bin into my phone but I go into my computer and my phone doesn't show up. I am currently in bootloader and stopped for fear of hurting my phone. How do I proceed? So sorry for being such a noob but I'd really really appreciate it if someone could help me!
KungPow90 said:
Hey guys I'm in the process of using the new rooting method and I'm at the part where I put the unlock_code.bin into my phone but I go into my computer and my phone doesn't show up. I am currently in bootloader and stopped for fear of hurting my phone. How do I proceed? So sorry for being such a noob but I'd really really appreciate it if someone could help me!
Click to expand...
Click to collapse
Guessing that your using windows system, did you install htc sync?
yup I got all the drivers. And yes im using windows.
Can anyone help me? I'm at the part where I use the unlockcode.bin but I don't know what I'm doing and need help.
Thanks
KungPow90 said:
Can anyone help me? I'm at the part where I use the unlockcode.bin but I don't know what I'm doing and need help.
Thanks
Click to expand...
Click to collapse
So your CID was successfully set?
Yes my CID was set. I need help with the unlock_code.bin
So I tried to run the command fastboot flash unlocktoken Unlock_code.bin as you are supposed to in the HTCdev site but this is the response:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
KungPow90 said:
So I tried to run the command fastboot flash unlocktoken Unlock_code.bin as you are supposed to in the HTCdev site but this is the response:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
you need to have fastboot executable installed in that directory also is your phone in debugging mode ?
take a peak at gunny's adb/fastboot primer here http://forum.xda-developers.com/showthread.php?t=1754018
hopefully that'll do it. good luck
ostoristn accomplish
Ok I put fastboot in there and it still didn't work. The phone is currently in bootloader. Yes I had debugging on when I switched it to bootloader.
What do you mean by didn't work? What is happening now when you run fastboot flash unlocktoken Unlock_code.bin
area51avenger said:
What do you mean by didn't work? What is happening now when you run fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
It is the same thing as before,
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
KungPow90 said:
It is the same thing as before,
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
go into the directory where your adb is and run "adb devices" from command prompt and let's see if your device is recognized, if it isn't it might be your drivers or try a different usb port.
Crappyvate said:
go into the directory where your adb is and run "adb devices" from command prompt and let's see if your device is recognized, if it isn't it might be your drivers or try a different usb port.
Click to expand...
Click to collapse
ok maybe im not running the commands right. i know for a fact that i have all the adb and fastboot stuff but it says the same thing as it did for the fast boot but with adb instead.
KungPow90 said:
ok maybe im not running the commands right. i know for a fact that i have all the adb and fastboot stuff but it says the same thing as it did for the fast boot but with adb instead.
Click to expand...
Click to collapse
are you on a pc ? how are you running your fastboot command at the prompt ?
KungPow90 said:
It is the same thing as before,
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Are you executing the commands from the folder where fastboot exists ? For example
You have adb, fastboot in C:\android-sdk\platform-tools" then you need to goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the command
"
abhipati said:
Are you executing the commands from the folder where fastboot exists ? For example
You have adb, fastboot in C:\android-sdk\platform-tools" then you need to goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the command
"
Click to expand...
Click to collapse
Ok ok now we are getting progress. It accepted fastboot and took the command but couldn't find the file "Unlock_code.bin"
KungPow90 said:
Ok ok now we are getting progress. It accepted fastboot and took the command but couldn't find the file "Unlock_code.bin"
Click to expand...
Click to collapse
did you get the unlock_code.bin from the htcdev website ?? It also needs to be in the same directory as your fastboot executable.
Crappyvate said:
did you get the unlock_code.bin from the htcdev website ?? It also needs to be in the same directory as your fastboot executable.
Click to expand...
Click to collapse
Yes the code came from htcdev and i put it in the same location as i am running my executions. I don't understand how it cant find it...
KungPow90 said:
Yes the code came from htcdev and i put it in the same location as i am running my executions. I don't understand how it cant find it...
Click to expand...
Click to collapse
what error do you get exactly and what command are you running ?
ensure you are giving correct names ( including case ) and correct paths
hi all
trying to flash manually. have read guides with no success.
have tried renaming the extracted file, saving to sd card, tried flashing the zip in twrp and still no luck.
question - does anyone know the commands to flash the BLOB file?
i found this article BUT want to know if i should be using the same commands.
http://www.androidauthority.com/eee-pad-transformer-prime-ics-9-4-2-13-us-firmware-56714/
Copy the “blob” file into the root of your tablet’s removable microSD card.
Open the Android Terminal Emulator app on your tablet.
In the Terminal Emulator screen, type “su” (without the quotation marks) and press Enter. This will allow root access to Terminal Emulator.
Type the command “dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4” (again, without the quotation marks) and press Enter. The command will take about 5 to 20 minutes to finish.
Reboot your device when the following is displayed in the app:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
As soon as the tablet is rebooted, the update process will automatically kick in.
thanks
azreal8 said:
hi all
trying to flash manually. have read guides with no success.
have tried renaming the extracted file, saving to sd card, tried flashing the zip in twrp and still no luck.
question - does anyone know the commands to flash the BLOB file?
i found this article BUT want to know if i should be using the same commands.
http://www.androidauthority.com/eee-pad-transformer-prime-ics-9-4-2-13-us-firmware-56714/
thanks
Click to expand...
Click to collapse
What kind of tablet are u talking about in your post ?
Thx Josh
hi josh..
its a tf700t.
also my micro SD slot is dead so obviously the command would be different as i'd be using my SD card slot on my dock.
azreal8 said:
hi josh..
its a tf700t.
also my micro SD slot is dead so obviously the command would be different as i'd be using my SD card slot on my dock.
Click to expand...
Click to collapse
Is your bootloader unlocked, with the asus unlock tool ?
And the tablet does boot into android ?
lj50036 said:
Is your bootloader unlocked, with the asus unlock tool ?
And the tablet does boot into android ?
Click to expand...
Click to collapse
yes it's unlocked and i'm running cromi-x 5.4 with hunds extreme tweaks kernel.
i want to flash to the stock firmware (.10) as i'll
1) be bringing it back to asus for a repair job - defective micro sd slot
2) want to flash roms which say i need .10 version bootloader.
i've looked at the manually flashing guides my tf doesnt detect nor does twrp flash it when i try to install.
azreal8 said:
yes it's unlocked and i'm running cromi-x 5.4 with hunds extreme tweaks kernel.
i want to flash to the stock firmware (.10) as i'll
1) be bringing it back to asus for a repair job - defective micro sd slot
2) want to flash roms which say i need .10 version bootloader.
i've looked at the manually flashing guides my tf doesnt detect nor does twrp flash it when i try to install.
Click to expand...
Click to collapse
Ok no worries let see if we can find a solution ..
What we will need
PC with working fastboot & adb
Stock blob from Asus website
That is about it, let me know if you have these things..
Thx Josh
lj50036 said:
Ok no worries let see if we can find a solution ..
What we will need
PC with working fastbot & adb
Stock blob from Asus website
That is about it, let me know if you have these things..
Thx Josh
Click to expand...
Click to collapse
thx..i have fastboot on my tf and the stock asus blob from their site
azreal8 said:
thx..i have fastboot on my tf and the stock asus blob from their site
Click to expand...
Click to collapse
We need fastboot on your PC also ..
I assume that you are running a windows PC
Head over here and set it up
http://forum.xda-developers.com/showthread.php?t=2588979
Thx Josh
lj50036 said:
We need fastboot on your PC also ..
I assume that you are running a windows PC
Head over here and set it up
http://forum.xda-developers.com/showthread.php?t=2588979
Thx Josh
Click to expand...
Click to collapse
yes win 8.1.
i installed fastboot on my pc to push thru twrp so i think i'm good to go.
azreal8 said:
yes win 8.1.
i installed fastboot on my pc to push thru twrp so i think i'm good to go.
Click to expand...
Click to collapse
Ok well make sure the blob file is with the fastboot.exe
plug the tab into the PC open CMD window as admin and run these command
Code:
fastboot devices
What is the output of this command ?
Thx Josh
lj50036 said:
Ok well make sure the blob file is with the fastboot.exe
plug the tab into the PC open CMD window as admin and run these command
Code:
fastboot devices
What is the output of this command ?
Thx Josh
Click to expand...
Click to collapse
sorry im back.
when i type "fastboot devices" i get:
015d3fb64d381a0d fastboot
azreal8 said:
sorry im back.
when i type "fastboot devices" i get:
015d3fb64d381a0d fastboot
Click to expand...
Click to collapse
Is the blob in that same folder with the fastbot.exe ?
Thx Josh
lj50036 said:
Is the blob in that same folder with the fastbot.exe ?
Thx Josh
Click to expand...
Click to collapse
yes but it's just named "blob" and was directly extracted from the asus file. i haven't extracted the meta folder from the asus file. do i need to?
azreal8 said:
yes but it's just named "blob" and was directly extracted from the asus file. i haven't extracted the meta folder from the asus file. do i need to?
Click to expand...
Click to collapse
No you will not need that just the blob ...
So from CMD window opened as admin run this command...
Code:
fastboot -i 0x0b05 flash system blob
Let it do its thing ....
Once it comes back to command prompt type
Code:
fastboot reboot
Let it boot into new rom with new bootloader and such ..
Thx Josh
lj50036 said:
No you will not need that just the blob ...
So from CMD window opened as admin run this command...
Code:
fastboot -i 0x0b05 flash system blob
Let it do its thing ....
Once it comes back to command prompt type
Code:
fastboot reboot
Let it boot into new rom with new bootloader and such ..
Thx Josh
Click to expand...
Click to collapse
thx josh! i followed your instructions and the TF went thru an updating process before booting to the home screen.
i checked the settings and the build says:
"J0P40D.WW_epad-10.6.1.14.10-20130801" so i assume thats all correct now?
QN - do you know where i can get the stock kernel? as i'll be returning it for a repair under warranty i assume i need to restore this too?
azreal8 said:
thx josh! i followed your instructions and the TF went thru an updating process before booting to the home screen.
i checked the settings and the build says:
"J0P40D.WW_epad-10.6.1.14.11-20130801" so i assume thats all correct now?
QN - do you know where i can get the stock kernel? as i'll be returning it for a repair under warranty i assume i need to restore this too?
Click to expand...
Click to collapse
That is the stock everything on there after the blob flash ...
it should end in 14.10 ....
Thx Josh
lj50036 said:
That is the stock everything on there after the blob flash ...
it should end in 14.10 ....
Thx Josh
Click to expand...
Click to collapse
awesome. was a typo. thanks so much for your help and quick response.
you're a champion!!!!
azreal8 said:
awesome. was a typo. thanks so much for your help and quick response.
you're a champion!!!!
Click to expand...
Click to collapse
Its why we are here .....
No problem can you add "SOLVED" to the thread title .... :good:
Thx Josh
lj50036 said:
Its why we are here .....
No problem can you add "SOLVED" to the thread title .... :good:
Thx Josh
Click to expand...
Click to collapse
For future reference, placing blob in the same folder as fastboot is not required. However you do need the blob folder to be the current folder for your terminal session.
FL00DY said:
For future reference, placing blob in the same folder as fastboot is not required. However you do need the blob folder to be the current folder for your terminal session.
Click to expand...
Click to collapse
Are you @_that in disguise!?
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
It means you've not copied the files into your ADB folder as it can't find the fastboot files
ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
gamer.11 said:
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
Click to expand...
Click to collapse
This won't work if fastboot binary isn't in env PATH.
EddyOS said:
It means you've not copied the files into your ADB folder as it can't find the fastboot files
Click to expand...
Click to collapse
"Into your FASTBOOT folder". adb's got nothing to do with this.
http://forum.xda-developers.com/showthread.php?t=2513701
Follow method two in this guide.
beekay201 said:
This won't work if fastboot binary isn't in env PATH.
Click to expand...
Click to collapse
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Easiest way is to extract the sh1t out of the Google file until you eventually see all the img files. Then extract the fastboot zip into the same folder they're in and open a command prompt there.
Fastboot zip -
https://www.dropbox.com/s/b8wxmwfi2ekdw3a/Adb And Fastboot.zip?dl=0
Sent from my Android 5.0 Nexus 5
gamer.11 said:
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Click to expand...
Click to collapse
Because it's in your PATH.
beekay201 said:
This won't work if fastboot binary isn't in env PATH.
"Into your FASTBOOT folder". adb's got nothing to do with this.
Click to expand...
Click to collapse
People refer to the folder with ADB and fastboot in it as the ADB folder (If you had adb/fastboot in the system path this wouldn't even be required)
Do you really think I meant them to use ADB? Come on, now
beekay201 said:
Because it's in your PATH.
Click to expand...
Click to collapse
oh "env" meant environment, sorry did not understand your shot hand.
by the way OP? solved your issue?
EddyOS said:
People refer to the folder with ADB and fastboot in it as the ADB folder
Click to expand...
Click to collapse
I refer to this folder as the platform tools folder
nikon120 said:
I refer to this folder as the platform tools folder
Click to expand...
Click to collapse
Makes more sense I guess, just more to type! This is where being in PATH makes life better