Hot answers tagged unbricking
8
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
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"), ...
6
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 ...
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
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 ...
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. ...
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 ...
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
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
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
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 ...
1
It could very well be due to your mobile sitting on top of it.
There may have been an electrostatic discharge from your phone, that was sent through the Nexus 7, breaking/harming some components.
If you can, I would suggest you take it to the repair center - it would be the only way if this is what has happened.
1
I had the same problem with my y200.
Go to huaweidevice.com and download the firmware.
Extract the folder downloaded and copy it to the SD card.
Insert the sd card into the phone.
Press vol up & down key at the same time + power button, then a message installing package comes up.
Then wait until the phone reboots.
That's how its done
1
If you can get into the bootloader, you can issue a fastboot -w command which will erase all data - this normally solved boot loops.
If not, you should be able to install a new ROM using the same bootloader (fastboot), you just need the system.img file (make sure you issue a fastboot -w command before you flash, however).
I believe that this pink screen ...
1
It doesn't look good I'm afraid. You would need to be able to see 'something' relating to the phone from a 'lsusb' command to be able to use odin to recover your device without cracking it open.
You've probably already seen this, but it looks like the JTagBox is your best bet.
Good luck!
1
If you can't get the device to even turn on, then this will not really help...
From XDA post about unbricking this device:
Prepare ODIN with the firmware you want to flash (in my case was Gingerbread 2.3.4) and get it ready to go.
Remove battery, wait for a bit. Insert battery again.
Flash a recovery with your specific filesystem (EXT4 or RFS)-(If you ...
1
Well it hasnt worked for me but you can try turning off the phone and do not turn it on but press and hold the home button the volume up button and then hold the power button along with it and itll take you to a special bootup and you need to format and do all the stuff listed and then click reboot phone
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 ...
1
The best you can do is power off the device completely, but do nothing for now, head over to samfirmware and download the appropriate ROM for your region.
Once you do that, refer to the instruction on using Odin.
You should have the PIT, and the MD5 file, and also the CSC file set up within Odin.
Then press and hold the VOLUME DOWN button, and then ...
1
I managed to do it using help from XDA-Developers. Here is the procedure :
Download the best SBF file from here. Among those corresponding to your geographical region and carrier, choose the most recent one.
Flash it to the phone by using either "sbf_flash" if you are on Ubuntu, OSX or another Linux, or by using "RSD Lite" if you are on Microsoft Windows.
...
1
Happened to me one on my DHD
my phone had same symptoms
what i did was take the batttery out then Hold the power button and then insert the battery into the phone again (while holding the power button down/ pushing) and my phone rebooted into bootloader and from there i switched to recovery
hope this trick will work for you.
good luck
1
I Hard Bricked my phone yesterday when I went to flash a custom ROM. I think I was trying to flash a ROM for the wrong model or something, not sure. Whatever, totally bricked. I had two options as I saw it:
Option 1
Go to AT&T, play dumb, and see if they would give me a new phone. (it worked) Since it was hard bricked, they could not even turn it on, ...
1
The firmwares files you are trying to flash using ODin have bootloaders removed and they are for s5570 while you have s5570i.
You should download the firmwares that are specific to your phone from here http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-S5570I&r=1#modelsa1
Hope your problem gets resolved if it isnt till now...
1
It could be that the phone is stuck in a boot loop at or before the OS has a chance to load. According to XDA, to get into the recovery partition, start with this: Home button + Volume button - + On button.
If you can get into fastboot mode, you can issue a command from the PC with a usb cable. After seeing if the device is there with "fastboot devices", ...
Only top voted, non community-wiki answers of a minimum length are eligible
