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!

Permarooted s-off still get no CWM recovery mode!?

I am rooted with s-off running on a ATT simcard but still can't boot in CWM recovery. In rom manager it says: current recovery Clockworkmode 3.0.2.4
Whenever I attempt to boot into recovery the MT4G comes up it reboots and it comes up agains and boots regularly. Any thoughts?
I followed all the instructions in this thread and am at the 85.xxx bootloader
http://forum.xda-developers.com/showthread.php?t=858996

I am bone stock other since I've not be able to get into recovery mode. Would a factory reset help?

Do it manually. Go to the bootloader and load recovery from there, or use adb and type adb reboot recovery.

adb does the same thing it attempts to get into recovery then goes blank and reboots regular and same thing with hboot.

Do you have fastboot on?

Nope. Fastboot is off. I can't even factory reset the phone. It just reboots like with everything else

be1ieve1111 said:
Nope. Fastboot is off. I can't even factory reset the phone. It just reboots like with everything else
Click to expand...
Click to collapse
most likely it feels as if the recovery image didn't take.
Code:
adb reboot bootloader
from there select "recovery" and see what boot loader you are using. If you have the engineering screen manually flash it.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
1. Download CWR3. - link supplied above
2. Save to your Android SDK tools (c:\android-sdk-windows\tools) or platform-tools (c:\android-sdk-windows\platform-tools) folder and rename to recovery.img
3. Turn off your phone.
4. Hold the volume down button + power until you boot to a white screen.
5. Use the volume rocker to select FASTBOOT then press the power button to select it.
6. Connect your phone.
7. Open up a windows command prompt and navigate to your sdk tools or platform tools folder. tools (c:\android-sdk-windows\tools) or platform-tools (c:\android-sdk-windows\platform-tools)
8. Type
Code:
FASTBOOT DEVICES
to make sure your computer "sees" your phone and is ready to flash the recovery. You should get a serial number and then the word fastboot as the output.
9. Type
Code:
fastboot flash recovery recovery.img
and press enter. Give it a minute to do it's thing. You should get a message that says writing recovery and success.
10. Unplug your phone and use the volume rocker to select BOOTLOADER and then again to select RECOVERY and you should be booted into the orange menu of Clockwork Recovery 3
Click to expand...
Click to collapse
taken and modified from http://forum.xda-developers.com/showthread.php?t=919834

It says fastboot isn't a recognized command when I type FASTBOOT DEVICES
also for the bootloader part. It loads real quick and it says something about no image or wrong image in the lines of code that loads on the screen then disappears

Are you using Linux? If so, cd to platform-tools and use ./fastboot instead of fastboot. Otherwise try updating adb and see if it works. Also, the random text is the phone searching for PD15IMG or another restore image. Disregard that, unless you want to flash the stock unrooted image.

Need Help Recovering my Stuck Xoom

Hi Guys,
I've been trying to unlock, root and flash my Xoom but have become stuck - and I Just need some clear guidance on what to do next before I completely mess it up.
I have a UK 3g Xoom, and I was following this guide here
I managed to unlock the Xoom fine, it was reset back to how it was. made sure i checked debugging in the settings...These were the last steps I did (in bold):-
1.) Reboot into fastboot mode
adb reboot bootloader
(You should see “Starting Fastboot protocol Support.” at the top of your Xoom)
2.) Time to get your hands dirty
a.) fastboot flash boot boot.img
b.) fastboot reboot
The xoom will reboot and display the Dual Core M logo then do:
c.)
adb remount
adb push bcm4329.ko /system/lib/modules
adb reboot
Once Again The xoom will reboot and display the Dual Core M logo then do:
d.)
the device did reset - but when the M logo appears I tried adb remount command, but it's telling me device not found. I have installed all the usb drivers etc...not sure what's going on.
The device can be reset, but doesn't get any where, i can get Starting fastboot protocol support up on there screen, and a couple of time i was able to get in to recovery (android logo with !)
Edit*
and im sure the recovery is the standard one - i only get options for:- rebot system now, apply update from usb drive, wipe data/factory reset, wipe cache partion.
Can I sort this out?
Thanks in advance

Ok, I've managed to flash back a stock image...device is locked again.

HSKalay said:
Ok, I've managed to flash back a stock image...device is locked again.
Click to expand...
Click to collapse
There are guides here on the xda Xoom forum that you can use very successfully--try this:
http://forum.xda-developers.com/showthread.php?t=1249798
It's much easier to flash solarnz's Universal Xoom Root zip linked in the thread above than using the method you linked to. You will need a micro sdcard and solarnz's cwm recovery R4c v 3.2.0.0.

Restore to original ROM with factory cable. How?

I have bricked Kindle fire while trying to install Android Market. To the point that shell doesn't work.
I made myself a factory cable. So I can easily go into fastboot mode. I tried various ways that people post in different threads. None seem to work as expected.
Is there a way to completely flash the original amazon ROM in fastboot?

Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?

There seems to be very little help on how to use a factory cable. I am in a similar boat as you. Shell works for me but adb commands do not. I can't push or pull or install. I can navigate, change file names, and move files to some directories. My problem is that I don't know how to put the stock rom on and flash it. I actually have 6.2 on the sdcard but don't know what to do with it.
As for your problem, I experienced the same thing. adb devices didn't list my KF but I could see it in lsusb. I typed the usb description at $ "1949:0006 Lab126" and it called me an idiot or something but then I typed ./adb shell and vioala. I'm sure that didn't do anything and won't ever work again but there you have it.
I have a couple of open questions out there to see if we can get help and if I learn anything I will make sure you hear it next.
ToonaKan

Dmitry_G said:
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
Click to expand...
Click to collapse
You must insert cable, when switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
After kindle will be in fastboot, with Kindle Fire Utility v.6 install TWRP recovery and with recovey install stock or CM7 firmaware.

Admittedly, I am a little green when it comes to this but I never got it to list in fastboot devices either with a cable (and I am not sure I am supposed to), you can check if its connected in fastboot mode by:
fastboot -i 0x1949 getvar product
it should return "kindle"
from there I did:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot oem idme bootmode 4000
fastboot reboot
To get twrp up and running then I flashed the prerooted 6.2.1. Going back to the orginal rom should be similar

Ok. Passing "-i 0x1949" to fastboot helped and now I can communicate with KF in fastboot.
But a new problem has surfaced. I'm trying to install TWRP:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
It writes "downloading 'boot.img'" and gets stuck there. I waited for 15 minutes.
Ideas?

You need to now check to make sure your drivers are now up to date.

So it seems that I can't really do any operations with fastboot. Every command just freezes at the first thing it does. Weird.
I'm on a mac. I never installed any drivers for KF - it just worked. Do I even need a driver for KF on a mac?

There must have been something with the factory cable. I finally managed to load TWRP.
Now I'm trying to install stock ROM renamed to update.zip. I push it into /sdcard. Then in TWRP I tap on Install and select update.zip.
I get:
E:failed to mount /sdcard (Invalid argument)
E:Can't mount /sdcard/update.zip
What does that mean?

Ok guys. I found the solution. "E:failed to mount /sdcard (Invalid argument)" tells you that your sdcard is not formatted correctly. Here is the fix I did.

I already have TWRP installed and also have a factory cable. But I still have a few questions.
1. With a factory cable, is there any way to directly flash the stock firmware or do you always have to install and use TWRP?
2. From reading about TWRP, it seems that after installing it, you can then load the stock firmware onto the sdcard directory and then complete the restore operation. As a safeguard, and to make things easier, I have already put a copy of 'update.zip' on there just in case I need it. My question is - on an unrooted Fire, would it not be a good idea to stick 'update.zip' on the sdcard before rooting? That way if something goes wrong, all you need to do is get TWRP on there and the restore file is already in place. Or am I being overly cautious?

Trouble flashing 5.0.0! Help needed!!!

Need help here!
My Nexus 10 was with stock 4.4.4, rooted with TWRP. I decided to flash the factory image files by removing the -w in flash-all.sh. However it ended up with being stuck with the rotating balls. After about 45 minutes, I decided to go to the fastboot mode (pwr+both volumes), then select recovery (I planned to do factory reset and clear cache). After trying to reboot into recovery mode (pwr + one volume button), it now shows an open bootloader with following message below the bootloader (the bootloader seems still unlocked):
Dowloading...
Do not turn off target!!
What does it mean? What is it exactly downloading? And what should I do? Should I lock the bootloader? Also it does not respond now if I push the volume buttons. It's not recognized on my Mac with the with the following command:
fastboot devices
I also notice the following line:
Reboot Mode Flag: NONE
Now I just booted into recovery, but it shows the bootloader with the exclamation mark! After a few minutes, it automatically switched to the never-ending rotating balls. What can I do?

When you get the Downloading...message you're in the Recovery screen. Don't worry about the message. Press vol up and power to get into the recovery menu - there you can wipe cache and system. As you're in recovery, Fastboot devices will not recognise your tablet, only adb commands.
If I was you and this didn't work, I'd just reboot into fastboot and flash the image files manually. You'll lose root, data and twrp but these can easily be gotten back through fastboot.

Hi,
In case you want help to flash Stock Firmware files. Check the Manta Help Thread .
http://forum.xda-developers.com/showthread.php?t=2670400
~Lord