I have H's hero and want to flash the new daroy kernel
Im using ubuntu and i connect usb, get to fastboot with the red highlight, then in terminal i type:
/home/name/Desktop/androidSDK/tools/fastboot erase boot (it erases boot)
then i type:
/home/name/Desktop/androidSDK/tools/fastboot flash boot boot.img and i get "cannot load boot.img"
I wasnt sure about the commands so i tried redownloading, putting them in the tools folder and then skipping the first line where it erase the current boot but i still get "cannot load boot.img"
Maybe the problem is that im not plugging things in in the right order, maybe its the commands, i dont know...please help. thanls
got it, forgot to put cd in front
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!
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!
Hey Guys,
So I was trying to downgrade to 4.3 on my Nexus 7, and I was dumb enough to disconnect it before it was complete. I believe it was in the process of deleting user data. Now I have a screen that says "booting failed" on the left, the google logo in the middle, an unlock symbol on the bottom, and a start banner on the top left, but every time I try to hit start, it just stays on the same screen saying booting failed. Same results when I try to boot into recovery. Is there any hope?
You should investigate whether or not you can communicate with it using fastboot. You might need to get it to the bootloader screen (rather than the "failed boot" screen). [REF] Nexus 7 Button Combinations
If you can, then there is all sorts of hope (from what you describe, it sounds like the bootloader is unlocked). All you need to do is do a little reading about fastboot - for instance in the "return to stock" thread here on XDA.
fastboot is the gateway to all things root with the N7.
There might be hope
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
I've done exactly the same thing. Any update please?
Thank you
bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
Stuck as in no messages, no output, prompt never returns?
Have you tried soft-booting a recovery to see what happens? e.g.
e.g. TWRP
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
e.g. CWM
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
-OR- (non-touch version)
fastboot boot recovery-clockwork-6.0.2.3-grouper.img
(The above are just examples, I'm not recommending a particular version of either custom recovery)
That might be a start. By communicating with a soft-booted recovery (adb shell blah-blah-blah), you can look at the kernel log (e.g. "adb shell dmesg") and see if it is complaining about partitions, filesystems, etc. The only rub with this is that because of the N7's use of an "internal" pseudo-SD card, the custom recoveries try and mount the userdata partition as soon as they start up, so if there is something wrong with that filesystem, the recovery itself might get wedged. I think I saw this with TWRP for instance - the touch interface wouldn't come up when I had a effed-up userdata partition. So, either an older recovery or a non-touch interface recovery might be adviseable here if you have troubles.
good luck
Solved!
Alright, two things helped me out here.
1. I used a different computer and reinstalled everything.
2. When you unzip the stock rom, it still leaves one zipped file in there that also needs to be unzipped into the platform-tools folder.
And now I'm in business!
Hi all im new to this forum. I am having a problem with my N7 im trying to unbrick it with nexus tool kit but at the flashing stage its says FAILED write failed unknown error for all partitions and when I try to flash a rom in twrp it hangs on patching system unconditionally. Has any one come across this problem before.
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
gavster26 said:
Update I have no software on my device without a way to flash it all tools including fastboot via comand prompt can't see it in bootloader mode please I really need help
Click to expand...
Click to collapse
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
yaro666 said:
so you can boot to recovery or bootloader?
try nexus root toolkit - there is an option to unbrick. Wipe everything and try to unbrick.
how windows detects your N7? maybe try different usb cable - if not genuine, then cut a lil bit of plastic, so it goes all the way to the usb port
give some photos of what errors do you have in recovery
Click to expand...
Click to collapse
I can boot to bootloader and thats it that tool can't write to any partitions thats what I tried in the first place it erased the partitions but then could not write to them so im left with no system no kernel or recovery
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
yaro666 said:
Download drivers from here
Open cmd as admin and type fastboot devices, it should detect your n7 with some numbers and letters.
If you have grouper (wifi) n7 then download recovery here
Go to bootloader, connect n7 with pc and type:
fastboot flash recovery twrp.img
Where twrp.img is the name of recovery file you downloaded.
Then type: fastboot reboot
In cmd you probably have to go to proper folder just use cd.. to go up a folder and cd name of the folder to go to proper folder. I use C:\adb as drivers install right there
Click to expand...
Click to collapse
Ok thanks I've got twrp to boot and I fastbooted aosp mm system and kernel but it won't boot up and twrp cant mount storage data or cache where to go from here it wont fastboot any stock img
Yotaphone2 from china
YD206-> YD201
android 4.4.3-> Firmware 5.0.0-EU1.187a.zip
Hello, first post!
I bought my first android phone and ofcource tried to upgrade it to Android 5.0 Lollipop using yotaphone flasher program. I ended up to a jammed android logo ->softbricked phone..
The problem was finally solved by using fastboot program. You can find it in yotaphone_flasher folder, which you probably already have if you're in this situation.
So I do not recommend trying to update OS using yotaphone flasher, I would use fastboot, it is easier than you think and above all it seems to be the safest way to update as fas as i know.
If you want to know more about the fastboot: https://forum.xda-developers.com/showthread.php?t=2277112
This is a walkthrough made by androidnoob. Use at your own risk:
Download yotaphone flasher if you don´t allready have it: ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Install yotaphone_flasher.exe and use it to download the firmware.
The default folder is C: Program Files (x86) / yotaphone_flasher, in that folder you will find fastboot.exe and firmware folder.
Copy the following files from the firmware folder to yotaphone_flasher folder (same folder you have fastboot.exe), you will need them later in the updating phase:
userdata.img
system.img
boot.img
Make sure that Yotaphone 2 is in downloading mode:
Simultaneously press the power + vol down until the display reads downloading. It may take more than one reboot so keep pressing until it appears.
Connect your phone to a computer via USB Cable.
Open the fastboot.exe. You can only do it in the command prompt, so press shift + right mouse at yotaphone_flasher folder-> Choose to open a command prompt. (Now you have to press enter after every command line)
In the command prompt, type the following:
fastboot
fastboot devices
If you see your phone's serial number, the connection works.
Start wiping memory, type:
fastboot erase system -w (this will erase everything, including your user data)
fastboot erase boot
And it´s time to install the update, type:
fastboot flash userdata userdata.img
fastboot flash -S 512M system system.img (For me installing in parts was a game changer. It´ll take some time so don´t panic)
fastboot flash boot boot.img
fastboot reboot
Yotaphone 2 will reboot. Wait 5-30 minutes, and the update is complete! Later my phone automatically updated 5.0.0-EU1.124b, so you can probably download this firmware using yotaphone flasher at the beginning of this process. I haven´t yet installed a sim so no idea if there are more issues.
This walkthrough has been compiled from various sources, so thanks to all for sharing! Hope this helps someone in trouble.
Yes, you can update your phone using manual fastboot commands. For convenience, a 4pda user rewrited YotaFlasher to a more polished version, making it flash system fastboot flash -S 512M system system.img command. I uploaded the new YotaFlasher in this guide.
You saved my day, the other methods did not work, I must add that it must be exclusively with the original cable, the others still with the error of "powered by android"
sotka said:
And it´s time to install the update, type:
fastboot flash userdata userdata.img
fastboot flash -S 512M system system.img (For me installing in parts was a game changer. It´ll take some time so don´t panic)
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Hi, Could you tell me how to install the system.img in parts? I have a 1.4gb system.img file that I am trying to install on a bootlooping Yotaphone 2.
I keep getting a "Invalid sparse file format at header magi" when I do the second step, which I think is linked to the .img being too large. But I have no idea how to make it smaller. Thanks for any help!