Database Users

HELP."error: cannot load boot.img" Trying to flash US 3.0 onto my UK 3.0 Xoom.

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

[Q] "error: cannot load boot.img" UK Wifi only xoom

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!

Replacing Rom manager with CWM

I'm trying to replace ROM manager with Tenfars via fastboot and it keeps saying error: cannot load d:recovery-en-goapk.img
Any idea what I might be doing wrong? I deleted the system/recovery-sh and am in fastboot now. Thanks for any help.

Phoneguy589 said:
I'm trying to replace ROM manager with Tenfars via fastboot and it keeps saying error: cannot load d:recovery-en-goapk.img
Any idea what I might be doing wrong? I deleted the system/recovery-sh and am in fastboot now. Thanks for any help.
Click to expand...
Click to collapse
where did you save the recovery img?

Phoneguy589 said:
I'm trying to replace ROM manager with Tenfars via fastboot and it keeps saying error: cannot load d:recovery-en-goapk.img
Any idea what I might be doing wrong? I deleted the system/recovery-sh and am in fastboot now. Thanks for any help.
Click to expand...
Click to collapse
Looks like you need to use full path to .img file.

i was getting this error this morning when i went to do this as well
what i did was:
put the 3 files required to utilize fastboot through command prompt (the 2 adb files, and fastboot itself) and the recovery image WITHOUT RENAMING IT into a folder simply called fastboot in C:\
in command prompt i did:
Code:
> cd C:\fastboot
> fastboot devices (to verify my phone was being seen)
> fastboot flash recovery C:\fastboot\recovery-en-goapk-1029.img (or whatever the hell it's called)
and it worked. for some odd reason, it wouldn't go when i renamed the file, or didn't type the EXACT file path to the recovery image..
maybe this will help you?

I have the img file in c:\ Just for the heck of it I also renamed one recovery and placed in c:\atrix. No matter what directory I choose it still says can't load.
c:\fastboot> fastboot flash recovery c:\recovery-en-goapg.img
That looks right to me but not sure what's up.

jakew02 said:
i was getting this error this morning when i went to do this as well
what i did was:
put the 3 files required to utilize fastboot through command prompt (the 2 adb files, and fastboot itself) and the recovery image WITHOUT RENAMING IT into a folder simply called fastboot in C:\
in command prompt i did:
Code:
> cd C:\fastboot
> fastboot devices (to verify my phone was being seen)
> fastboot flash recovery C:\fastboot\recovery-en-goapk-1029.img (or whatever the hell it's called)
and it worked. for some odd reason, it wouldn't go when i renamed the file, or didn't type the EXACT file path to the recovery image..
maybe this will help you?
Click to expand...
Click to collapse
That's what I needed... Thank You! Still learning my way around.

did it work?

Yes it worked. I needed to type in the full line, not just what was told to type in at the beggining of the thread. It's definately a learning thing. I'm trying to decide what ROM I'd like to run now.... I have the 4-5 beta, tried Cherryblur.5 and didn't like it so I went back. Now I have the blur theme but it still seems a little glitchy and the battery issue is annoying. I read that the ROM manager didn't wipe and install properly plus the issue with it not seeing the ext sd card is a problem.

trouble flashing recovery

Hi guys so here's the deal, i've just unlocked the bootloader on my Nexus 4 and tried to falsh recovery.
I connected my nexus to the computer and transferred the twrp.img file to the main directory and typed:
fastboot flash recovery twrp.img
one I hit enter an "error: cannot load 'openrecovery-twrp-2.3.2.3-mako.img' " error appeared.
any ideas?

prhing said:
Hi guys so here's the deal, i've just unlocked the bootloader on my Nexus 4 and tried to falsh recovery.
I connected my nexus to the computer and transferred the twrp.img file to the main directory and typed:
fastboot flash recovery twrp.img
one I hit enter an "error: cannot load 'openrecovery-twrp-2.3.2.3-mako.img' " error appeared.
any ideas?
Click to expand...
Click to collapse
you need to put the recovery on your desktop not your device, in the same folder as fastboot.

prhing said:
Hi guys so here's the deal, i've just unlocked the bootloader on my Nexus 4 and tried to falsh recovery.
I connected my nexus to the computer and transferred the twrp.img file to the main directory and typed:
fastboot flash recovery twrp.img
one I hit enter an "error: cannot load 'openrecovery-twrp-2.3.2.3-mako.img' " error appeared.
any ideas?
Click to expand...
Click to collapse
You have to put the file you want to flash in android-sdk\platform-tools folder where the fastboot (.exe) file also is located.
Oeps didn`t see Simms post

simms22 said:
you need to put the recovery on your desktop not your device, in the same folder as fastboot.
Click to expand...
Click to collapse
I'm doing it on a Mac and I put both the fast boot file and the recovery file in the same directory.
I still get the same error.

prhing said:
I'm doing it on a Mac and I put both the fast boot file and the recovery file in the same directory.
I still get the same error.
Click to expand...
Click to collapse
Here is a tutorial to setup adb and use fastboot on a mac to verify its is working correctly http://www.google.nl/url?sa=t&rct=j...bojYmmm1t6sMySi1e4a5bXw&bvm=bv.47244034,d.d2k. Do you see a serialnumber if you type fastboot oem devices? And does the name of the recovery end with .img, if so delete .img.

prhing said:
I'm doing it on a Mac and I put both the fast boot file and the recovery file in the same directory.
I still get the same error.
Click to expand...
Click to collapse
On a Mac its ./fastboot flash recovery nameofrecovery.img

Use goomanager app from play store to flash it if you have trouble with pc.
Pc is always better and safer though
Sent from my Nexus 4 using xda premium

help me to root yureka

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.