I know this is cheesey but I have a feeling it will help someone out there. Attached to this post is the streakmod custom recovery image and a simple .bat file for recovery and rebooting. Instead of typing in the fastboot commands manually, all you need to do is type 'recovery' or 'reboot' and the commands will execute. Just make sure these .bat files and the recovery img are all in the same folder as your fastboot.exe files for this to work. Its not much but it does make things easier. Thanks
Related
im a noob to this and i've searched and cant find the answer anywhere
im trying to test the 10mb patch before i apply it
so trying to use fastboot, i can confirm that my fone is connected when i use fastboot using fastboot devices
however, where do i place the mem-boot.img to test it
do i leave it in /sdcard/ directory or leave it on my computer in the same folder as the fastboot command?
because i understand i need to run fastboot boot <bootimage>.img
thanks!
http://forum.xda-developers.com/showthread.php?t=566410
Read the lower half of the first post, what don't you understand?
i dont understand where i save the bootimage before i flash it
i want to test it
i understand how to flash the boot images, but it recommends testing before i do so
i can connect the phone and confirm its connected via flashboot on my pc
so do i leave the boot image in the same directory as the flashboot directory on my pc and test it that way?
or do i put the boot image on my fone somewhere?
newcastlepunto said:
i dont understand where i save the bootimage before i flash it
i want to test it
i understand how to flash the boot images, but it recommends testing before i do so
i can connect the phone and confirm its connected via flashboot on my pc
so do i leave the boot image in the same directory as the flashboot directory on my pc and test it that way?
or do i put the boot image on my fone somewhere?
Click to expand...
Click to collapse
Boot.img in the same folder as the fastboot.exe
Terminal Emulator Install
Copy the boot.img to the root of your sdcard. Then issue these commands from the terminal emulator.
Code:
su
flash_image boot /sdcard/boot.img
reboot
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
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.
Good morning,
I followed the tutorial here on XDA on how to basically factory reset my Nexus 7. Unfortunately, while going through all the steps I also deleted my recovery. Now I am unable to flash any recovery back on my device. I have tried flashing Clockwork, TWRP and even Google Stock recovery, but it won't work. Neither flashing via Nexus 7 toolkit nor by hand was successful, instead it always returns the following error message:
Booting into Android using an Insecure Boot Image..
cannot load "root\boot-insecure-.img' : No error
Now my Nexus 7 is in some random state, since Android 4.2.2 is installed, but rooting via the Toolkit returns the same message when it comes to the point of flashing a recovery. Then it simply skips the remaining steps and does not install the superuser app. I also downloaded and tried using the ROM Manager, but since root-access is missing, it can't do anything either.
Do you guys have any solution to this?
Help is very much appreciated!
Thanks!
marcfeld said:
Good morning,
I followed the tutorial here on XDA on how to basically factory reset my Nexus 7. Unfortunately, while going through all the steps I also deleted my recovery. Now I am unable to flash any recovery back on my device. I have tried flashing Clockwork, TWRP and even Google Stock recovery, but it won't work. Neither flashing via Nexus 7 toolkit nor by hand was successful, instead it always returns the following error message:
Booting into Android using an Insecure Boot Image..
cannot load "root\boot-insecure-.img' : No error
Now my Nexus 7 is in some random state, since Android 4.2.2 is installed, but rooting via the Toolkit returns the same message when it comes to the point of flashing a recovery. Then it simply skips the remaining steps and does not install the superuser app. I also downloaded and tried using the ROM Manager, but since root-access is missing, it can't do anything either.
Do you guys have any solution to this?
Help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Though toolkits save a lot of time, I always prefer to do stuff the manual way and I suggest you do the same. To flash the recovery do the following steps
1) a) if you are running Windows open cmd as administrator and CD into a folder containing adb and fastboot .exes
b) copy paste a downloaded recovery image in the same folder and rename it to recovery.img for simplicity.
2) boot into boot loader by pressing power volume down and volume up all together after the device is turned off
3) in bootloader enter the fastboot mode and in cmd on PC type
Code:
fastboot devices
At this moment your device should turn up in the command prompt.if it doesn't then try installing the Asus drivers and repeat the steps above carefully.
4) once all that is over type
Code:
fastboot flash recovery recovery.img
And then the recovery must be flashed . you will get an output on cmd with the time taken to flash it too .
Then reboot into recovery and enjoy.
A succinct summary, Red Devil.
I always maintain, on a my Windows laptop, a folder called FastBootAdb, that contains the following files...
fastboot.exe
adb.exe
AdbWinApi.dll (needed by Windows)
AdbWinUsbApi.dll (needed by Windows)
If I wish to flash a new recovery.img (or a new boot.img - useful for certain kernels, that consists of nothing but a boot.img, like franco for example. Most custom kernels though, consist of more than just a boot.img, and need to flashed via TWRP or CWM, and can't just be fastboot flashed).
Anyway... I just copy the new recovery into this folder, rename it to recovery.img and run the fastboot command accordingly...
Code:
fastboot flash recovery recovery.img
...similarly with the boot partition...
Code:
fastboot flash boot boot.img
To be honest, I'm puzzled why people feel the need to overcomplicate this very simple procedure with toolkits.
Rgrds,
Ged.
Thanks a million guys!
I will try this as soon as I get home tonight and let you know.
nourtsW escape
This did the trick!
Thanks again guys!
marcfeld said:
This did the trick!
Thanks again guys!
Click to expand...
Click to collapse
Glad you got it sorted.
With Android, there's always 'more than one way to skin a cat!'.
Rgrds,
Ged.
GedBlake said:
Glad you got it sorted.
With Android, there's always 'more than one way to skin a cat!'.
Rgrds,
Ged.
Click to expand...
Click to collapse
I am so relieved, because I thought I had bricked it...
GedBlake said:
A succinct summary, Red Devil.
I always maintain, on a my Windows laptop, a folder called FastBootAdb, that contains the following files...
fastboot.exe
adb.exe
AdbWinApi.dll (needed by Windows)
AdbWinUsbApi.dll (needed by Windows)
If I wish to flash a new recovery.img (or a new boot.img - useful for certain kernels, that consists of nothing but a boot.img, like franco for example. Most custom kernels though, consist of more than just a boot.img, and need to flashed via TWRP or CWM, and can't just be fastboot flashed).
Anyway... I just copy the new recovery into this folder, rename it to recovery.img and run the fastboot command accordingly...
Code:
fastboot flash recovery recovery.img
...similarly with the boot partition...
Code:
fastboot flash boot boot.img
To be honest, I'm puzzled why people feel the need to overcomplicate this very simple procedure with toolkits.
Rgrds,
Ged.
Click to expand...
Click to collapse
ive done this exactly step by step and i getthe system cannot find the specified path i made a folder inside the windows folder i named it recovery in the command prompt i did cd windows then cd recovery then i typed fastboot devicesthen it said that
Help! Nexus 7 won't accept recovery flash image
I've tried all the above. I can get to the command prompt, and fastboot devices sees my device. I input the above commands to reflash, it starts with message "sending 'recovery' <xxx.xkb>' then nothing. It just sits there until I reset or reboot my nexus 7. Can anyone help?