Tag Info

Hot answers tagged

12

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


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


8

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


8

Brick is a much-hyped word that gets bandied about with-out understanding what it is. There's two types of brick, hard and soft. Lets 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. ...


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

JTAG has zero involvement with Android! You may find a JTAG being visible either under the battery or near the SIM/SDCard holder, its a circuitary pin-layout hidden, one may have to dismantle the back cover, usually 6 gold pins in a cluster close together. It is that, using a special hardware box that has a vast-array of cables with designated pins ...


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


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


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

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.


4

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

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


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

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


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)


2

If you didn't already have your bootloader unlocked and tools in place to reload the Android operating system (ie, ROMs or disk images), I strongly suspected you are completely screwed.


2

Are you able to get into the recovery boot menu? (On my phone, it is accessed by holding down the vol down button when turning on the phone). If so, there may be something that can help you. I have had this happen to me, and what I had to do was to try re-installing the ROM from the zip file, using the process described here (scroll down to Flashing ...


2

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


2

Before you un-root I'd recommend upgrading to the Stable release of CM 6.1 which may fix your problems. If you do unroot you can use Appbrain to reload all your apps but you'll still have to re-enter in all your settings and what not. If you stay rooted and use Titanium Backup you can reload all your apps from your SD card with all their settings intact. ...


2

Go to Download Mode and flash Galaxy S2 firmware/recovery using heimdall or Odin (over USB). There's no other way.


2

That's a soft brick, for the reasons below: Handset is still powering on adb is responding handset recognizes usb cable plugged in (how else were you able to adb?) handset recognizes the sdcard Look at this question to see Izzy's answer on what is classified as a "brick". Something went awry there and it clobbered the recovery environment... mind ...


2

First of all, do a nandroid backup to save the current state of the phone. Get a ROM that can be flashed via recovery (usually .zip, not .img or .tar.img), then just execute: adb shell mount /sdcard adb push <romname.zip> /sdcard If the first option to mount the sdcard fails, you can manually mount if from recovery. Also sdcard path might vary from ...


2

Summing up the solution from above comments: Fixing up the possibly broken build.prop file You don't need to mount your SDCard to revert your changes. If you can boot into recovery, and access the device via adb shell, you can do so and replace your edited build.prop file with the backup copy you've created (using the cp command), thus restoring the state ...


2

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


2

A "factory reset" only wipes the user data from the device: it doesn't touch the system apps or operating system at all. You need to either find the APK file you're missing (perhaps from a friend with the same phone) and install it as a system app via adb (since you can't use the phone normally), or find the stock ROM and reflash it onto your phone using the ...


1

Solved! Found the solution in Lenovo's forum, A1 and A1107 Unbrick fix/full factory restore: There have been several instances of people having problems with A1 and A1107 devices. This guide explains how to fix any software issue, including those that "brick" the device, or stop it booting up at all, by restoring the tablet to a completely stock factory ...



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