Tag Info

Hot answers tagged

14

To make the system recognize the Android device, in their several modes, one needs to set permissions for his user in udev. You need to repeat this process of loading Android udev IDs, for every mode the phone has (operating system, bootloader or recovery) because they have different USB IDs # reboot into fastboot mode adb reboot bootloader # grab you ...


12

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 ...


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.


7

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 ;)


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 ...


6

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 ...


6

What needs to be done is to bundle the boot.img and construct a new zip file suitable for flashing via ClockworkMod or TWRP. Pre-requisites: a Linux environment that has the usual development packages, such as Java installed. (It can also apply to other platforms, just be careful that the instructions here indicating the path used below, uses a forward ...


5

Linux/OSX Run fastboot as root or with sudo. Other OS: credits


5

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 ...


5

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: ...


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

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 ...


4

If you can find a ROM on a forum or website, you can easily flash it using fastboot - as long as it supports fastboot flashing. Most ROM makers provide both types of ROM flashing mode. To flash, you should have a .img file (most likely called system.img). You can flash this by connecting your device in fastboot mode to your pc and using this command: ...


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

Are you rebooting the device into the bootloader and entering fastboot USB on the bootloader menu? Try: adb reboot bootloader Then, look for on-screen instructions to enter fastboot mode.


4

Had the same issue right now. fastboot oem lock didn't find the device. Disconnected the device from USB and held the power button for 10s to reset. Booted like a charm afterwards


4

According to this XDA thread it's an issue with the bootloader file. You could try downloading a different factory image for your device and try the bootloader from there instead (the recent images have all had the same 4.23 version, although different files). Does anyone else get a "invalidState" and "signature mismatch" message when trying to flash ...


4

Fastboot allows you to send commands to your phone while in the bootloader. The bootloader is the one place that ADB is not running. Disclaimer, not all of these may work with your device. fastboot oem unlock Unlock your bootloader. If your device supports this, you can unlock your bootloader here. Most phones require an exploit in order to gain root ...


4

As far as I know, your device is not that hard bricked, that you can't boot into the bootloader (fastboot mode). so at every time you should be able to install a custom recovery via fastboot flash recovery recovery.img. if you are in recovery mode with a working recovery, you can do a factory reset (reflash the system, root,... partitions from a protected ...


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



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