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?
Adb is saying that it doesn't recognize "fastboot" as a command. I haven't really use ADB since I got the phone in February, has there been changes to the commands needed?
I did a simple search and found this: http://www.nexusoneforum.net/forum/...-fastboot-devices-command-not-recognized.html
GL Hope it helps.
Problem is not it recognizing cause Adb reboot-bootloader works.
This used to work
Cd\
Cd androidsdk/tools/
Fastboot oem lock
Has something been moved? And if so what is the new path?
sarge363 said:
This used to work
Cd\
Cd androidsdk/tools/
Fastboot oem lock
Has something been moved? And if so what is the new path?
Click to expand...
Click to collapse
Make sure fastboot is still in your tools folder. With some of the updated sdk fastboot gets removed. If it's not there you can get it from the cm wiki and just put it in the tools folder.
Sent from my PG06100 using Tapatalk
The problem is that you think you need to run adb to get fastboot to work.
adb and fastboot are 2 separate programs. ADB is the Android Device Bridge where fastboot is another standalone command line program s used to directly flash the filesystem etc.
If you download the Android SDK now, it won't have fastboot included, so you need to get it from somewhere else, like the old CM wiki as crump suggested.
Once you have the compiled fastboot file, you can navigate to it from a command prompt and execute the fastboot commands
Greetz
Thanks for the clarification. I really only used it once or twice when I first got the phone. And I just looked and I am missing the fastboot. I'll give it a shot.
In cm wiki there is only fastboot 32bit. I have 64bit, will it still work?
sarge363 said:
In cm wiki there is only fastboot 32bit. I have 64bit, will it still work?
Click to expand...
Click to collapse
Yes, 64 bit computers are backwards compatible for the most part
Sent from my illuminated black thing
Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"
Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89
Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.
Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.
you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op
IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill
One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.
I want to download the latest possible ADB/Fastboot binaries because a little bird whispered in my ear that the Asus USB ID's have been added so -i 0x0b05 isn't needed when using fastboot on the TF201.
Anyways, I do NOT use the "android-sdk" nor have I ever downloaded it. I simply used a tool called knives and forks which put the binaries in system32/syswow64 and then somehow symlinked them to always respond when typing "adb" in CMD regardless of where i start the CMD. I don't need to cd to an android-sdk folder (I don't even have one, derp)
So how can I update to the latest binaries WITHOUT downloading the sdk?
removed
shabbypenguin said:
while not the most ideal answer, i work on a lot of low end devices and in an effort to keep it simple for em i bundle up the binaries needed for most devices. normally i have adb for all 3 platforms and fastboot for all three. ive yet to update the mac and linux binaries but my zip does have the latest windows adb/fastboot
www.Shabbypenguin.com/OUDstuff/Tools/ADB-Tools.zip
Click to expand...
Click to collapse
Much obliged!
Thank you! You just saved me from a 2-3hr download tethered to my phone!
shabbypenguin said:
while not the most ideal answer, i work on a lot of low end devices and in an effort to keep it simple for em i bundle up the binaries needed for most devices. normally i have adb for all 3 platforms and fastboot for all three. ive yet to update the mac and linux binaries but my zip does have the latest windows adb/fastboot
www.Shabbypenguin.com/OUDstuff/Tools/ADB-Tools.zip
Click to expand...
Click to collapse
I've been frustrated with error: device offline.
My SDK manager is still downloading stuff & I found this thread.
Latest adb helps!!!
Thank you so much.
dsymbol said:
I've been frustrated with error: device offline.
My SDK manager is still downloading stuff & I found this thread.
Latest adb helps!!!
Thank you so much.
Click to expand...
Click to collapse
that zip is old, instead http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081
use teh attached file there. chances are the device offline is due to outdated adb and a 4.2 device.
shabbypenguin said:
that zip is old, instead http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081
use teh attached file there. chances are the device offline is due to outdated adb and a 4.2 device.
Click to expand...
Click to collapse
you're absolutely correct.
i've updated to 4.3 & run into device offline problem.
Your adb 1.0.31 helps. in less than 5 mins, while i've been sitting here for 3 hours waiting for the SDK manager to update files.
Thanks for this!
Hi all.
I have searched the forum for solution to my problem but can't seem to find it.
When trying to flash 5.1 I get an error
After,I try to flash all .img files manually. All flash normal except system.img
I searched forums, used Wugs tool, tried on different PC's (Windows 8.1 & Windows 7) tried with different fastboot versions but no result.
Older versions flash normal(5.0.1, 4.4.4, etc..)
Any suggestions?
How much ram the PCs have?
One has 8gb ram installed,another one has 16gb
arsen4oo said:
One has 8gb ram installed,another one has 16gb
Click to expand...
Click to collapse
Strange...
Can you pack the adbs and fastboots to a zip or rar and upload it to somewhere or give me a link which adb and fastboot you use. I am going to try flash 5.1 in 30 minutes.
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
arsen4oo said:
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
Click to expand...
Click to collapse
Using your binaries it flashed fine, I got no errors.
My specs: Windows 8.1 Pro 8GB ram.
What is different with my setup about ram management is that since I have an SSD as drive C I moved the pagefile.sys to my HDD.
I also have Microsoft Visual C++ 2008, 2010, 2012 redistributables installed. I have no idea if that counts
I don't think problem is caused by pagefile.
But seems many people have this issue when flashing 5.1
Flashing from ubuntu is an alternative solution..
I have no idea what the issue is but here is how I got round exactly the same error message on my Windows 7 machine.
Create a new local user (with admin rights) and then reboot your machine. Log in with that user and close any applications that try to auto-start. Then try the batch file and it should now work.
I think it must be related to memory/open applications. I have loads of stuff open in the background, i.e. in the systray, with my standard login. This new user had nothing. Using this user after a reboot seems to do the trick!
Try to download the nexus image again. It might be corrupted or extract it again using 7zip. Just flashed mine a while ago using "minimal adb and fastboot" on windows 7 x64 with 2gb of RAM. Machines doesn't have anything to do with adb flashing. It's the file itself or the adb drivers.
Edit: I see you've already sorted this out via ubunta machine. Good for you.
I had the same issue last night too. I downloaded the latest nexus USB drivers and the flash completed successfully.
Had the same issue. Spent all night unbricking my phone. One of the partitions didn't flash right and i left my phone over night and it still didn't boot up. got 2 hours of sleep.
Kitkat flashed fine though.
So what i did. im using minimal adb fastboot
1) flash 4.4.4 images
2) extract ALL 5.1 image files (boot, system, etc) into the minimal adb fastboot folder C:\\program files etc etc
3) flash each item manuall
-fastboot flash bootloader bootloadername.img
-fastboot flash radio radioname.img
-then do the same with boot, radio, system, userdata, cache. (fastboot flash "partition" "name".img) so if youre flashing boot, then boot boot.img
this should boot up just fine. 2-5 minutes tops.
Manual flashing fixes it
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
BorgKing said:
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
yep you got it right :good:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Sanjay Varma said:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Click to expand...
Click to collapse
lol i got the idea from the same vid. Just ive flashed partitions manually before.
russian392 said:
lol i got the idea from the same vid. Just ive flashed partitions manually before.
Click to expand...
Click to collapse
lolz - though he is explaining well, I did mistakes as the commands and file names identically followed by each other