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!

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

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.

Yotaphone 2 soft bricked, step-by-step help

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!

I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck

I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.

George425 said:
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
Click to expand...
Click to collapse
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled..

Hello sir,
Copy the twrp file to the folder where ADB is installed. The folder is located in C drive.
Next you can Shift+right click, open powershell/cmd, whichever is there.
Now type in command
" fastboot flash recovery tw" and click tab button. After tab button, click enter.
This should be done when phone is in bootloader mode and connected to laptop/PC.
after the command execution is over, you can reboot to recovery.
First flash Ex kernel and then flash magisk, in THIS ORDER ONLY, OR YOUR PHONE WILL BRICK!
And voila, you have root! Flash anything!

____Mdd said:
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled.
Click to expand...
Click to collapse
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?

George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You flashed it. Reboot into recovery now.

George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You've done it! Reboot to recovery!

Lyuu said:
You flashed it. Reboot into recovery now.
Click to expand...
Click to collapse
DhirajKale789 said:
You've done it! Reboot to recovery!
Click to expand...
Click to collapse
Yes you are both absolutely correct thank you for your help! I didn't think it was working!