I am trying to install recovery in fastboot mode, but i get always this message "fastboot is not recognizeble as an internal or external command". Does anyone know how can i solve this?
Thanks
You have to download fastboot driver and run CMD from the folder where fastboot files are located (shift+right click).
You can find countless tutorial and links on Google for fastboot drivers
Related
I'm trying to install baconbits on my G2 and I have a mac. I cannot seem to get the recovery image to work through fastboot. Help?
I can access the phone through the terminal but once I command it to reboot to the bootloader I can't get it to find the img file
There's a fastboot binary available for download from this page: http://developer.htc.com/adp.html
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
pak256 said:
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
Click to expand...
Click to collapse
You can flash files from recovery if they are on the SD card. You can either adb push while in recovery, or mount USB storage and tranfer the file. Or just transfer it via USB while the phone is on (big, green android screen)
I'm not sure how to install baconbits, but I think you need fastboot to flash the .img file. Recovery flashes .zip files and fastboot flashes .img files. You can put fastboot-mac in the same folder as adb... then fastboot flash recovery your_recovery.img. You really don't need adb (for this) since you can boot into fastboot on the phone by restarting while holding down the trackpad button.
These might be the droids you are looking for...
Code:
adb (read the instructions)
adb devices (you'll see your phone if it's plugged in, turned on, and in the proper mode)
adb reboot bootloader (white screen with androids on skateboards)
fastboot-mac (more reading...)
fastboot-mac devices (your phone again)
fastboot flash recovery your_recovery.img
fastboot reboot-bootloader
For some reason, I had a little trouble flashing my recovery- sometimes it would hang and wouldn't flash, sometimes it would only fastboot boot. So if you run into trouble, there might be other problems.
While you are at it, you might as well save yourself the trouble and either add the adb and flashboot folders into your path, or put the binaries somewhere in your path. I also renamed fastboot-mac to fastboot for simplicity.
Going to try that when I get out of class but I think you helped me realize what I was doing wrong. Thanks and will let you know if it works
Sent from my T-Mobile G2 using XDA App
Okay I could get the fastboot prompts to work but when I try to flash the recovery it tells me "g2recovery.img" could not be loaded
okay, used clockwork and got it to work. yay!
HELP."error: cannot load boot.img" Trying to flash US 3.0 onto my UK 3.0 Xoom.
Hi all, Im a newbie.
Im having trouble flashing my UK Xoom with the US ROM so that i can update to 3.1.
I'm trying to do the following:
1. Install the Android-SDK,
2. Make a path to the fastboot command via right clicking Computer selecting properties select advanced system, environment variables, click on PATH and in the variable value input paste:
C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools
3. Make sure you de-zip the stock us Wifi firmware into the C:\Program Files (x86)\Android\android-sdk\platform-tools directory. Download these from the MotoDev web-site.
4. Place your xoom in fastboot by turning off then repowering holding the volume down button to enter fastboot mode.
Open the command prompt if not already open...
Unlock your Xoom by typing:
fastboot oem unlock
at the command prompt.
then enter the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Ive got up to "fastboot flash boot boot.img but in command prompt it says "error: cannot load boot.img"
On my xoom it says "starting fastboot protocol support"
Ive unzip the boot.img file is in the platorm-tools folder
Please help.
Thanks
hilfiger2k said:
Hi all, Im a newbie.
Im having trouble flashing my UK Xoom with the US ROM so that i can update to 3.1.
I'm trying to do the following:
1. Install the Android-SDK,
2. Make a path to the fastboot command via right clicking Computer selecting properties select advanced system, environment variables, click on PATH and in the variable value input paste:
C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools
3. Make sure you de-zip the stock us Wifi firmware into the C:\Program Files (x86)\Android\android-sdk\platform-tools directory. Download these from the MotoDev web-site.
4. Place your xoom in fastboot by turning off then repowering holding the volume down button to enter fastboot mode.
Open the command prompt if not already open...
Unlock your Xoom by typing:
fastboot oem unlock
at the command prompt.
then enter the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Ive got up to "fastboot flash boot boot.img but in command prompt it says "error: cannot load boot.img"
On my xoom it says "starting fastboot protocol support"
Ive unzip the boot.img file is in the platorm-tools folder
Please help.
Thanks
Click to expand...
Click to collapse
Did you open the command prompt from the platform-tools folder?
Also when you unlocked did you get the warning on screen you had to accept twice?
Another possibility is before typing the command to flash the boot image, type adb remount and the enter.
Sent from my GT-I9000 using XDA Premium App
Hi, Thanks for answering. I just tried "adb remount" but it says error device not found"
When you say, Did you open the command prompt from the platform-tools folder?
How do you do that? I just opened it normally from the program files.
And also yes on the xoom it gave to warnings and i accepted both so the xoom is unlocked.
Is it best to start again? If so should the MZ604_HWI69 folder be unzipped into the platfoem tools folder yes?
And also in the PATH what should i edit it to.
At the moment it says: C:\Android\android-sdk\platform-tools;C:\Android\android-sdk\tools;C:\Program Files\Java\jdk1.6.0_25\bin\java.exe
rschenck said:
Did you open the command prompt from the platform-tools folder?
Also when you unlocked did you get the warning on screen you had to accept twice?
Another possibility is before typing the command to flash the boot image, type adb remount and the enter.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Hi, Thanks dude. Ive solved it. You were correct. I just had to open the command prompt from within the platfom-tools folder. Then everything was straight forward.
Cheers mate )))))
Now thats sorted one more thing....how to i click a thanks to your thanks meter???
Done the "thanks"
Cheers
Sent from my LG-P990 using XDA App
No worries...glad it worked out for you.
Sent from my GT-I9000 using XDA Premium App
Hi all,
I'm new to this, so please be gentle (ie I'm a bit slow)
After getting completely frustrated at the lenght of time to get the UK Honeycomb update from Motorola I've decided to take the plunge and flash the US version.
I've floowed all the instructions on downloading SDK, the USB drivers, the US images and I've successfully unlocked my Xoom.
However, when I type the instruction 'fastboot flash boot boot.img' I get the following error message - "error: cannot load boot.img"
The i got the US HWI69 files from Moto and saved them in the SDK\..Platform-Tools folder. That's also the same folder the file path in System Properties' points to - so I can't understand why its not recognising the file?
Can anyone out there help? As I say I'm pretty new to this, so may need a bit of coaching...
The steps I'm following are:
adb reboot bootloader
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
As I say, I've performed the unlock, just unable to go any further. If I connect to my pc and type adb devices, it finds the xoom ok..
I have read someithng about opening command prompt in the platforms-tools folder, but I'm unclear how to do this or if this is the problem?
dhawkes said:
The steps I'm following are:
adb reboot bootloader
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
As I say, I've performed the unlock, just unable to go any further. If I connect to my pc and type adb devices, it finds the xoom ok..
I have read someithng about opening command prompt in the platforms-tools folder, but I'm unclear how to do this or if this is the problem?
Click to expand...
Click to collapse
to open the command window in a folder, shift and right click in the folder and click on open command window here... (windows 7)
ed.dark said:
to open the command window in a folder, shift and right click in the folder and click on open command window here... (windows 7)
Click to expand...
Click to collapse
could be
or try redownloading the US images as they might be a bit corrupt?
ed.dark said:
to open the command window in a folder, shift and right click in the folder and click on open command window here... (windows 7)
Click to expand...
Click to collapse
Sorry if I'm being a tool, but holding down shift and right clicking in the folder does not give me an option to open a command window? In fact holding shift down doesn't seem to have an effect - just the usual right click menu?
I'm using XP Media Center version, service pack 3 if that helps?
Am i missing something really obvious? (Probably )
I'll try downloading the images again..
Its only for windows 7. download xp power toys for the addon for xp
http://go.microsoft.com/fwlink/?LinkId=211471
Hey, ed.dark (and Lothaen) Thanks for taking the time to read and answer my query. I'm delighted to say once the power toys were installed it was all plain sailing.
3.1 has just been picked up and is installing and I'm over the moon.
Thanks guys!
Driver is not installing properly ....I have tried to install driver using pdanet. It shows driver installed but when I try to do root in fastboot n search fastboot command in c drive...I get driver error........
hackersamraj said:
Driver is not installing properly ....I have tried to install driver using pdanet. It shows driver installed but when I try to do root in fastboot n search fastboot command in c drive...I get driver error........
Click to expand...
Click to collapse
forget pdanet it won't do good anyway. First you would need this files on your pc/laptop.
download the drives first for your device link :- https://androidmtk.com/download-yu-usb-driver
download adb platform tools:- https://dl.google.com/android/reposi...st-windows.zip
download recovery:- https://dl.twrp.me/tomato/
after downloading is done.install drivers and then extract adb paltform tools and place the downloaded twrp img into the same folder.
Now keep in mind your directory should not have spaces eg D:\New folder\adb tools\.... but D:\New_folder\adb_tools or simply place to desktop.
go to the folder where adb and your twrp img is copied press shift+right click and select open command window here and put your yureka in fastboot mode. then type fastboot -i 0x1ebf devices now your device shold be listed.
type fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery recovery_name.img replace recovery_name.img with your twrp recovery name. download any super user app and then flash that using twrp recovery.
hello everyone..new on the forum..its my first post...
so, MODs pls delete or guide where to post this question although i didnt find any relevant thread...
i just bought a new asus m1 pro and have been trying to root it with majisk from 2 days but no luck..
here is what i did...
first i unlocked bootloader from asus website's apk..link is https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
on this link 740KB bootloader unlocker
then instead of installing any drivers i installed asus pclink available on pclink.asus.com as i assumed it would contain drivers..although haven't started pclink program just completed installation..
then from this link https://www.xda-developers.com/install-adb-windows-macos-linux/ under microsot windows adb setup heading 1st step gives u zip containing adb and fastboot drivers so extracted it and ran cmd from extracted folder and got twrp image file from https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development/recovery-twrp-3-2-1-x-t3787134 got the twrp-3.2.2-1 20180727 57MB image file....
then ran cmd from extracted folder after connecting phone typed adb devices and device was there (gonna attach screenshots of cmd) and then adb reboot bootloader then fastboot flash recovery twrp.img (i copied twrp file to this folder and renamed it as twrp.img) and then fastboot reboot all this went fine in cmd according to me but i haven't used cmd before so i know nothing about it...
and yes after adb reobot bootloader the phone did switch off and restarted and phone screen displayed fastboot mode and after fastboot reboot phone did restart...
cmd screenshot..
https://imgur.com/anxoFAB
so even after all this i booted to recovery (vol down+lock) but i find that twrp is not there...its still the phone's recovery software...
what i can't seem to understand is after cmd showing everything it should there should be rare possibility of this happening..right?or does it happen more often?
if i would have got stuck in some other manner i would have searched web but this after a bit of searching seems rare...
experts please help....much needed...