Database Users

Need help with ADB on a mac

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!

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.

[Q] Nexus 7 2012 -- Recovery won't flash - Please help!

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?

[Q] Wipe device and install factory image via adb?

N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!

Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4

ddb540 said:
N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!
Click to expand...
Click to collapse
Hey you might want to look at the Google Nexus Toolkit. You can sideload a file if you already have a custom recovery installed.
http://forum.xda-developers.com/showthread.php?t=1995688
Good luck!

Lord Yurij said:
Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!

ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.

abaaaabbbb63 said:
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.
Click to expand...
Click to collapse
Sorry, I typed incorrectly. Yes, I did fastboot flash system system.img, etc.

ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.

Convert a tar.md5 file to .img
gee2012 said:
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.
Click to expand...
Click to collapse
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,

AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
Odin? That's for samsung mate. Won't work here. You need to download the factory images and extract it to get stock recovery. Or just head over to general section and there are thread for flashable stock recovery/modem/kernel. There is also a guide on how to use adb, a very detailed one at that. I'm sure you won't have trouble following it. Just read carefully and do it. All the things you need are given in that thread.
Edit: Guide - http://forum.xda-developers.com/showthread.php?t=2010312

AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
1. Make sure you have Android SDK installed. if not download here.
2. Download Nexus 4 factory rom from here.
3. Unzip the factory rom [occam-kot49h-factory]. If you dont know how to unzip. Download and install Winrar. Open the file with Winrar and Extract it somewhere in your computer.
4. Turn off your phone
3. Hold Volume up + Power; once it loads up to bootloader; connect it to your computer
5. The file [occam-kot49h-factory] you extract it early; in there you should see a file flash-all-bat. Open it [run it as admin if you are running Vista/7/8] and let it do its magic. Your phone will factory reset.

http://www.wugfresh.com/nrt/
go to this website, download the toolkit, and connect your nexus to computer on fastboot mode, do some few clicks, and boom, done

''Could not do normal boot'' error and odin doesnt recognise my phone! Please help :(

(SOLVED) Hello, today i decided to root my phone( Galaxy Grand Prime SM-G530F)using odin but i guess i used the wrong file. Odin said ''Restart'' and nothing happened, then i unplugged my phone. I wish I hadnt done this
When i try to turn my phone on, I only can see download mode and i guess it is called ''bootloop''. It says ''could not do normal boot''. I couldnt solve this problem using Odin because Odin doesnt see/recognise/find my phone. I checked the USB port drivers and my wire but i still cant fix the problem. Please help me, I am so desperate and cant afford a new phone :crying:

Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app

TimSchumi said:
Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.

Oh, crap, i forgot
Sent from my SM-G350 using XDA-Developers mobile app

fabiossilva21 said:
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.
Click to expand...
Click to collapse
I tried to remove the battery but it didnt work

tunasdf said:
I tried to remove the battery but it didnt work
Click to expand...
Click to collapse
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much

tunasdf said:
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much
Click to expand...
Click to collapse
No problem! Glad you managed to fix it! Now remember to flash the right file