Database Info

[Q] Is my device bricked?

when i was on runny v1.1 rom,i tried to flash unity v4 kernel,and it's very unstable,i had no other choice but to reflash the rom to get the kernel back.
the rom has wipe code in it's updater script...
the device hanged at "formatting nand with ext4 alignment" for like half an hour,...
having read the danger of pulling battery...i decided to gold the volume buttons and power button...the phone then rebooted and vibrate for 7 times...what can i do?i tried adb,but the computer cannot detect the device/...

If you don't want to pull the battery leave it run flat and then pull it. Charge it while the phone is off and then see if you can boot into hboot. If you can get to hboot then no you almost certainly haven't bricked your phone.

have you tried holding down the volume down button then holding down power at the same time? this should take you to the bootloader. from there you can go to recovery and format system, data and cache then install a previous backup or a new rom

i used the button method to reboot...and after that it rebooted and vibrates for 7 times...when i pulled my battery,and i tried to open it with volume down and power button held,all it does is just vibrates for 7 times again..

tcchuin said:
i used the button method to reboot...and after that it rebooted and vibrates for 7 times...when i pulled my battery,and i tried to open it with volume down and power button held,all it does is just vibrates for 7 times again..[/QUOTE
can you get your pc to connect to it? does charging light light up?
if not try connecting wall charger and see if it will charge?
Click to expand...
Click to collapse

no to both questions...

how much charge was in the battery before this happened?
the only thing i can think to try now is a new battery. im getting out of my depth a little now...

After powering it on have you tried to see if adb recognises the phone and if it does does it respond to commands?
You'll find adb&fastboot within my sig, alongwith some HTC drivers download and install both onto your PC (assumong that you don't already have them). then plug the phone into PC by USB. Run a CMD, go to the directory where you extracted adb files and try
Code:
[B]adb devices [/B] [COLOR="Green"]-- [I]just to see if it recognises [/I]device?
[/COLOR]If it does then try :
Code:
[B]adb reboot recovery[/B]
[I]if no response then try[/I]
[B]adb reboot-bootloader[/B]
report back and good luck

it was like around 90%...
it cannot detect the phone...

O dear!
tcchuin said:
it was like around 90%...it cannot detect the phone...
Click to expand...
Click to collapse
It's look like a visit to the local HTC service centre is next step, based on the complete lack of reponse from your phone. Although I'd obviously never advise any one to tell lies , it's probably not a good idea to meantion S-OFF etc when returning the phone and you'll most probably get a replacement unit or at least a new motherboard!

[Q] Sensation won't boot :( Please help..Anyone???

Hi all,
I recently bought a used sensation from ebay and now it won't boot. I allready read a couple posts in this forum. Did the adb reboot and adb reboot bootloader and didn't work. So I think it's not rooted. What exactley happens is, the will not boot. It stays blank and the led lights too, but when plug it into my laptop\pc, it gets reconized and able to install the adb drivers to it. The led lights are then lit and pressing the power button kills it for a second and then restarts. Getting the same connection to my pc but no boot. I then installed adb tools trying to reboot the bootloader, but when i type in adb devices, I get nothing listed. So when i tried adb reboot i get error: no device found
Just moments ago i installed a new jdk and currently installing android sdk to make a proper connection with the device.
Any advice?? Pff

I think it phone has been completely wiped so there is no any OA Rom installed. Try booting in to recovery then see if its rooted then install any custom Rom. The most safest way is install RUU from ur PC which restore it to original.
Sent from my HTC Sensation Z710e using xda premium

still no luck
I've read the post noob guide (adb,sdk..), done every step, still it won't see my phone

Run RUU from PC because it phone is recognized by pc that's best way.
Sent from my HTC Sensation Z710e using xda premium

Just check which recovery have u got if clockwork then flash any custom Rom again. U need 2 use card reader to transfer rom
Sent from my HTC Sensation Z710e using xda premium

can I use one of these stock ruu's?

http://forum.xda-developers.com/showthread.php?t=1228648

Ok so from what I understand is that even without being in bootloader or recovery. Just by being connected, I can install stock ruu to my phone and then everything else? I'm downloading one of the ruu now

Ok from what i read, I cannot get into the bootloader or recovery cause it's maybe hard bricked. Is there a fix for this?

jasminthoria said:
Run RUU from PC because it phone is recognized by pc that's best way.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Ok sorry for the late reply. Due to my "lovely" bandwidth, I finally found the stock rom for my device, version tmous 1.45.531.1. I ran the setup and everything went fine, until i got an error error 1105 or something that it's not compatible with my device. How can that be if it'.s not from another vendor. It says t mobile on top lol. Does this mean that i'm screwed?

Still haven't got it to boot. Only led is lit when plugged in charger or pc. The screen stays blank and unplugged it does nothing. Only if there was a way to get it in fastboot or just to see life in my device

Hold volume down plus power button. You will be in fastbboot .

first press and hold the vol - button then just press the power button without holding it, but keep holding the vol -
wait 10 seconds
release the vol - button
press power button again
now you should be in fastboot
on your computer in command prompt type fastboot devices and see if your computer recognizes the phone

[S3] Bricked phone - only ADB is working

Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.

Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.

Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!

Need help with xoom, possible brick

First,
I really want to thank everyone for their support in this forum. Everyone has been amazing.
I was trying to bring my MZ601 back to stock yesterday. Something bad happened during fastboot and asked me if I wanted to unlock my device. Then the screen locked up and didnt do anything. I rebooted the device and now it gets stuck in a boot loop with the EOS symbol (last rom I installed). When I enter recovery there is nothing there, all of my data is gone.
Worse the device is not recognized on my computer nor can it be found in adb fastboot. I have updated motorola drivers, but I think the device never gets past a certain point in order to be found.
Can somebody please help me.
Thanks,

Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).

demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
Hi,
Thanks for the tips. Unfortunately, it seems that I have caused the entire sd card partition to be erased. That mean when I trry to fastboot my device is not recognized. Also, i cannot add anything to my xoom through usb. I have tried to flash through the external sd card, but to no avail. What do I have to do?

What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.

dfib1 said:
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply to my message.
Unfortunately I cannot find my device when it is plugged into my computer (PC). It does not show up on my computer nor in the device manager. I can start the fastboot protocol on my device by rebooting, but I also cannot find my device in ADB.
Thanks for the reply, but I am still very stuck.

are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app

ndanl said:
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
I did everything I have done before. I have setup android sdk, java, and motorola drivers on two different PCs. Both fail to find my device when i type ADB devices nor does ADB reboot bootloader work. I tried the different cable, but that also did not work.

Hi,
I see that your problem is quite hard, try doing this:
1 - Force your tablet to shut down (vol+ + Power)
2 - Turn on while holding the vol- button
3 - Keep pressing vol-
4 - Plug on your PC and try fastboot devices, adb won't work!
5 - If 4 didn't work, keep trying until it does
6 - Install a Stock ROM (so you will solve your problems)
If the above don't work, contact me via PM, so we can talk easily (maybe GTalk or something like this). Good Luck
~XxLordxX
"This Story Ends Where It Began" - Octavarium (Dream Theater)

XxLordxX thank you!!!
I took your advice and just used fastboot. Then I flashed the stock rom I wanted to use. My xoom is back up and running. I really appreciate the tip.
Also thank you to everyone that responded in the post, again, that is why I love coming here.

demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
I have this problem now but I don't know what to do. Please help me out

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.