Hot answers tagged

18

JTAG and Android are two separate things. You may find JTAG pins visible either under your device's battery or near its SIM / MicroSD card holder. The pins are hidden. You may have to dismantle your phone's back cover. The JTAG pins are usually six gold pins clustered close to each other, as shown in this photo: Click to enlarge You use a special ...


17

The term "brick" usually refers to the stone, which means: "device can only be used as paper-weight". Taken literally, there's no way to "unbrick". However, you also find terms like "hard-brick" and "soft-brick" used, which makes the term "brick" less absolute: A soft-brick is something you easily can recover from (count it as a "temporary paper-weight"), ...


10

You most probably have an unpartitioned sdcard, clockworkmod however assumes that is partitioned and wants to mount the first partition (/dev/block/mmcblk0p1). You can fix this by repartitioning your sdcard so that it has a mountable fat-formatted first volume and then retry. If you don't mind using the commandline, boot to recovery and connect via adb ...


10

I figured this out only after months of being without most of my phone's functionality and taking it to a 3rd-party repair place that declared it "unrepairable". It is stupidly easy: Download an apk of your home launcher (I got one from here: http://forum.xda-developers.com/archive/index.php/t-1125331.html ) E-mail it to yourself Use voice commands to ...


9

Brick is a much-hyped word that gets bandied about without understanding what it is. There's two types of brick, hard and soft. Let's go through this to make the distinction clearer. Hard - this is where the handset will absolutely refuse to boot at the press of the power button. Diagnostics: Dead screen, no power. That is the symptom of a hard brick. ...


8

Your phone is almost certainly not permanently bricked. Chances are you can boot into recovery to flash a new ROM. Worst case, you'll have to flash the phone back to stock with RSD Lite. That said, there's really no way to unroot the phone or flash a stock ROM without having to re-install your apps. You can try flashing a stock ROM without wiping data ...


6

Solved. ASUS released the new firmware in its website. Flashing it unbricked my device: Download the stock firmware from ASUS’s official website. On the website, select Android in the OS drop down menu, then select Firmware, and download the latest firmware. Extract the downloaded firmware file. You will get another archive file. Extract this one as well ...


6

This may not be as easy as you think. The eMMC is connected to the board with a Ball Grid Array (BGA) connection, which is pretty difficult to reconnect once removed. You can see photos of the chip and more discussion on the topic on this XDA post. As for where the chip is, you might be able to find it on some teardowns, but my eyes didn't catch it in ...


6

From @AndrewT 's comment, I gathered this: Referring this answer on StackOverflow What does stop do? stop entered in a root terminal basically stops the Android process called zygote. This in turn stops all processes registered in the context of zygote, that is, all services (including system services) registered to zygote. This includes the ...


5

Is it unplugged when trying to do this? I could hold X while booting, then I would see the Android and exclamation. Then hold Up/Down Volume and get the recovery. You have to press both Up & Down at the same time. It is not a rocker key and you can press them both. Use Enter key on keypad with the arrow above OK to make a selection.


5

To add, after a little thought I think the lack of a cache directory may have been my problem all along. I formatted this ext2 and this may have solved the problem. Therefore a damaged cache directory might have been the root cause of this problem. after formatting the cache and running /sbin/recovery it went straight into Clockwork (it was a big surprise) ...


5

The risk of really "bricking" a phone is not that high as it may seem, at least with more recent models, as there are multiple levels of safety-guards in place: If you break your regular system, there's a fallback possible to the recovery mode. If that's broken as well, there are things like Fastboot in place. Only if you break the lowest level, and e.g. ...


4

Final Answer (to wrap up the question) [short version]: Battery was utterly dead, when popped open and measured at the tabs, voltage was under the safe minimum. New battery ordered from eBay plugged in, tablet worked! Just had to to escape from a boot cycle of doom, root and install Cyanogenmod 9 alpha (of which there are numerous available tutorials for ...


4

Since you do have working fastboot access, you have a few options from there: You can... Get a custom recovery like TWRP. Then run fastboot flash recovery /path/to/twrp.img. With TWRP, you can to try to reinstall ROMS, do factory resets, and make backups of your current system (Which may be a good idea, even if it's bricked). Do a factory reset with ...


4

It's a chip soldered to the main board in the phone. You can only remove it by desoldering it from the board in a soldering oven. (This is a precisely temperature-controlled device: a kitchen oven won't do.) Even if you did manage to desolder it safely, the chip itself isn't a lot of use to you. Because it's an internal component, it doesn't fit into a ...


4

Samsung devices can usually be forced into download mode using a JIG. They are pretty simple and cheap to make. If your device has been soft-bricked this will almost always work. http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/


4

Episode 3: Return of the Shell. If I ever had any chance of solving this, I first had to figure out why the shell wasn't working. adbd itself was responding, so it was started on the tablet side - but it could not execute the shell, even when I hack-patched it to invoke a file (/sbin/sh) that I myself placed in the boot image - being 100% sure that it had ...


3

If you have a custom recovery already, where Clockwork Mod Recovery is the most popular one, there's an option there to do a complete backup, sometimes called a "nandroid". As long as you have this backup folder lying around (it won't disappear when doing wipes from CWM) and you can enter CWM, you can restore that backup as well. Since the backup includes ...


3

There are the two things of note that I see in your data: The instructions indicate that you should use fastboot -i 0x1949 boot u-boot.bin. This is actually not correct, because the fastboot boot command is intended for hotbooting a boot.img, not a bootloader (they are different). The original XDA instructions give the proper command, which is fastboot -i ...


3

As you haven't mentioned your phone related information, I can share my view. When your phone is not responding or bricked then you can use your phone PC Compassion or PC suite or whatever depends on what your phone model gave you. I own Sony Ericsson Xperia Mini Pro. Sometime back while installing another ROM the phone bricked. I googled and read lots of ...


3

I wanted to copy the zip directly to the internal storage You can't just want to, you have to. ClockworkMod does not mount the external SD card, you have to put it on the internal SD storage (often called the internal SD card and separate from the main system storage). If you can't access the internal SD then you'll need to flash an Odin-packed ROM ...


3

Thank god I figured out how to fix it. The problem was that I was using software that was meant to root a first gen Nexus 7, and I had the second gen (2013) version. Whoops. In order to fix it, I downloaded the Unroot/Stock Toolkit from http://www.androidrootz.com/2013/08/nexus-7-one-click-toolkit-for-mac-2013.html and then downloaded the factory images ...


3

Ok Solved! We have Operation! Here is what happened. Fastboot format data failed "cannot format partition type ' ' Please Enter Password: Error Popped up in TWRP when I had never set one and when I tried to do anything it could never mount /system or /cache or anything I did fastboot flash recovery Clockwork recovery zip and from there I got the error ...


3

This is mostly speculation, but mediaserver is probably what is used to play all and any sound on android. Some app was probably using mediaserver inappropriately, causing it to show as using excessive battery. logcat2 is probably the process used for logging output, and is where many debug and error messages are sent to. Outright deleting them probably ...


3

I thought I could use my nandroid backup to flash system.img, etc. to overwrite what's there but it's one big .win file. So I looked up the fastboot commands anyways and stumbled on an xda thread about un-bricking TF300s where they used fastboot erase on every mount point then fastboot flashed the stock firmware blob file from Asus' support website. Ran ...


3

Note: Keep in mind, Samsung Galaxy S2 has infamous Superbrick bug. Every flash can result in permanent brick (only board changing or maybe JTAG unit can recover device). You can learn more about it here. Note2 : Last resort to enter Download mode is to get USB JIG. There is plenty of this on Internet and it's very cheap. Also there is tutorials on Internet ...


3

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

The device was not bricked. After a few hours I held down the power button again, and the frozen screen was replaced by the "no battery" screen. After charging, the device is back to normal. I caution users of this particular device not to use apps that try to force the systemwide screen orientation. It was lucky that the battery was nearly empty when this ...


3

Provided your device is rooted, you can do that with simple dd commands. Trouble is just to find out what partitions you might need to backup: some devices have more than 20 partitions, and you will most likely not need more than 5 backed up. This is where e.g. my little tool Adebar comes in which, amongst others, creates you a script for exactly this ...


2

You may have to run an ruu if you don't have a custom recovery You could try rebooting into bootloader and doing a factory reset there (typically, turn device off, hold volume down and power till you're in the bootloader, volume moves, power selects in that screen)



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