Tag Info

Hot answers tagged

8

The Replicant Project builds tools with every release; you can find their tools here (go down the directory tree in a path like replicant-2.3/preview/0002/tools/), along with notes about which git version was used for the source. Go one directory up and read COPYING for details. Note: They only offer Linux builds. Source code is here.


8

Simply put, fastboot oem lock puts your bootloader into a mode that prevents you from overwriting your recovery image, without a subsequent fastboot oem unlock. This serves as a security precaution, primarily where the default recovery and firmware is installed. Because: The default recovery will only allow manufacturer/Google signed firmware to be ...


6

Fastboot is a binary and protocol used to communicate with Android devices in the early boot stage. It allows to change of the boot target and therefore is often used to install custom boot-loader (TWRP, clockworkmod, etc.) and ROMs. The binary often comes with the Android SDK, for example on my linux system it is installed at ...


5

Personally I had to run fastboot as root/sudo for fastboot to detect the device. I tried this on Linux as I don't own a Mac, but it's *NIX anyway ;)


4

You want the Android SDK. From the CyanogenMod wiki: After installing the Android SDK or ADB Standalone you can use 'fastboot' in addition to the more common ADB. After installing the SDK you will need to add the Android SDK platform-tools package.


4

You should try a factory reset before trying to reflash the phone. AFAIK you need to unlock the bootloader (voiding your warranty) to flash a ROM, even on the Nexus S. Instructions: Turn the power off. If your Nexus S is frozen, pull the battery out and reinsert it Hold the Volume Down button Press and release the Power button You are now ...


4

I believe you need the stock recovery, based on http://2chnull.info/r/smartphone/1292830738/801-900. You can get back to stock recovery easily, for example follow this thread: http://forum.xda-developers.com/showthread.php?t=884093


4

Make sure your phone is powering off completely before you try to boot into the bootloader. For a DHD you might need to go into Settings > Applications and uncheck the "FastBoot" option in order for it to power down completely (source). If #1 doesn't help, try turning your phone off, then pulling the battery. After you've pulled the battery and waited a ...


4

Because your phone is branded by Orange Austria, the SIM card is likely locked. SonyEricsson states: ... you can’t unlock the boot loader if you have a SIM lock protected phone http://unlockbootloader.sonyericsson.com/which-phones#13182586887331&if_height=1139


4

Well, when HTC leaves it up to us, it's up to us, so I kept playing with it. It turns out that the response I got is a generic response from fastboot: It does a piss-poor job of checking its arguments. That particular response, in effect, means, "invalid command arguments." Yes, I made a typographical error and this was the result. It didn't occur to me ...


4

The clue lies with the comment above But I just tried 'adb reboot bootloader', and it worked. which shows that adb is indeed recognizing the USB connection, but not in fast-boot mode which is where this answer comes in... Sounds like the udev rule for the fast-boot is absent! Do this: lsusb with the cable plugged in while the handset is in fast-boot mode. ...


4

Had similar problems. My Nexus 4 was discovered just fine, but Nexus 10 failed to be seen as an Android adb device. So I uninstalled the Nexus 4 drivers, rebooted, and then installed some unsigned drivers from internet called Naked Drivers. After that both Nexus 4 and Nexus 10 were properly recognized. Then, attempted to unlock the Nexus 10 using WugFresh ...


4

Yes. Locking the bootloader is possible after you have installed a custom firmware. A locked bootloader will not allow you to ad-hoc boot custom binaries (using fastboot boot boot.img and will not allow you to directly write to the flash chips. An unlocked bootloader however does offer you this and newly available commands are: fastboot flash partition ...


3

From this xda thread by albundy2010 I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only ...


3

fastboot is when you enter fastboot mode, by powering up with volume up key pressed. Then fastboot devices would work. Why are you invoking the recovery on its own via adb shell? The recovery binary is reliant on the startup scripts used within the recovery partition unless the partition is messed up. Recovery only works by powering up with volume down ...


3

After flashing a new firmware it is advised to perform a factory reset (all your data will be lost, so take a backup.) While the phone is off: Press the VOLUME UP, HOME and POWER buttons together till it vibrates. Now it has entered RECOVERY MODE. Navigating using the volume buttons highlight the option wipe data/factory reset and press the HOME button to ...


3

Rooting the Atrix 4G does only that - gives you elevated privileges on stock OS. In order to be able to install a different recovery image and custom ROMs, the phone's bootloader must be unlocked first. This is a fairly complicated process that carries the usual warnings and disclaimers of modifying phone software. It will most definitely void your ...


3

I don't know anything about this phone, but this thread on xda has dump of the stock ROM. I am not sure if it includes the boot.img or not. The dump seems to be android 1.6, the original thread is here and is HUGE. There is also a 2.2 thread here and it does look like the Zio has its own section on XDA as well. In the Development section, i found this ...


3

This solution worked: $ cd 1.0-GRI40-nexusone-superboot $ ./fastboot-linux flash:raw boot boot.superboot.img I've found the necessary info on http://www.gotontheinter.net/content/fastboot-cheat-sheet


3

This approach will work (provided there are no proprietary funny locks in place anywhere), but the recovery partition is no party to it from the very beginning. The default.prop is overwritten on bootup, copied from the boot partition, which is not a directly accessible file system. You need an image of the boot partition, which you will then unpack, make ...


3

fastboot oem unlock always deletes userdata for security reasons, so it must be used only once (until you lock again manually). CWM is needed if you want to flash a root package (you can't push it via fastboot), but that is not usually the only way to root a device. The CWM install needs only the fastboot flash recovery recovery_name command, which does ...


3

For future reference, this was my related case (involving a Nexus 4): I tried to bring my phone back to the original state (bootloader locked + stock rom). Now fastboot devices did not show the device where adb device did, until I put the phone in fastboot mode (this makes sense, but took me a while to figure out...) To put the Nexus 4 in fastboot mode: ...


3

You don't use adb to connect to a device when it's in the bootloader menu: you need to use the fastboot command instead. That's why it's called "fastboot mode"! Not all phones support fastboot: in particular, older HTC phones use a proprietary protocol called HBOOT instead, but I think the newer ones support fastboot.


3

The partition you want to write to is called boot, not bootloader, so the correct command is fastboot flash boot boot.img


2

HTC used to have a copy of the Linux binary, but they changed their developers portal and now I can't find that one anymore, either. The only other pre-compiled version I've been able to find is here (link originated from this thread on droidforums.net, which also has a link to a pre-compiled OSX binary). I checked with readelf on my Linux VM and it looks ...


2

Unlocking the bootloader will wipe your device. You can however get root access without unlocking the boot loader. If you then still want to unlock the bootloader, as you already have root access you can follow Sparx's advice and use a back up app before doing so.


2

The Odin-able kernels for my Galaxy S are simply the zImage in a .tar file. But the zImage has a peculiar format, and I believe it's specific to Samsung devices. I would assume that either the kernel you've compiled is the wrong format, or simply doesn't work and the system is restoring the stock kernel from the recovery image.


2

Nexus Ones do not ship with 'S-OFF', they ship with a "locked" bootloader which then must be unlocked. You can actually use fastboot to unlock the bootloader, just run fastboot oem unlock on your PC using ADB (Android Device Bridge). MoDaCo has a post here with complete instructions and a multi-platform download of the needed tools.


2

Steps I've used in the past for this kind of issue : Check your USB cable - some are no good for data. (this is frequently the issue when my computer can't see my phone) reboot everything you say the drivers aren't installing - what's the issue there? try manually installing the drivers.


2

No. If you have a custom recovery that supports adb / root, you can boot into it and use adb to remount /system as read-write and push the missing file over. But otherwise you don't have access to most of the phone.



Only top voted, non community-wiki answers of a minimum length are eligible