Database Info

Bricked? Please help, phone barely boots... Wifes phone and she is ticked

Some background... The whole reason I was rooting this phone was the volume button was malfunctioning... constantly pressing up. I used the hack-ace tool linked somewhere else and followed the directions. At one point during the install the phone went black and the red light began to blink... in command prompt window it just said waiting for device for a long time. Now all it will do it go into the clockworkmod recovery screen. If I try to restart hack ace it says the sd card is either not mounted or corrupted. Any help?!? this is my wifes phone so I need to fix it fast!

soniktoothe said:
Some background... The whole reason I was rooting this phone was the volume button was malfunctioning... constantly pressing up. I used the hack-ace tool linked somewhere else and followed the directions. At one point during the install the phone went black and the red light began to blink... in command prompt window it just said waiting for device for a long time. Now all it will do it go into the clockworkmod recovery screen. If I try to restart hack ace it says the sd card is either not mounted or corrupted. Any help?!? this is my wifes phone so I need to fix it fast!
Click to expand...
Click to collapse
When did you use AAHK? It has recently been retired and the files it needs are gone, so using it now can get you stuck. If you have CWM the phone was either S-Off or bootloader-unlocked at some point. Which is it?

bananagranola said:
When did you use AAHK? It has recently been retired and the files it needs are gone, so using it now can get you stuck. If you have CWM the phone was either S-Off or bootloader-unlocked at some point. Which is it?
Click to expand...
Click to collapse
Thanks so much for the quick reply! IT had no rooting done before today, it had gotten a little ways into the rooting before it quit... That must be how CWM is on there. It had gotten to the point of HBoot being installed when it quit.

soniktoothe said:
Thanks so much for the quick reply! IT had no rooting done before today, it had gotten a little ways into the rooting before it quit... That must be how CWM is on there. It had gotten to the point of HBoot being installed when it quit.
Click to expand...
Click to collapse
What does hboot say? In case you don't know how to get there, reboot holding power and volume-down.

bananagranola said:
What does hboot say? In case you don't know how to get there, reboot holding power and volume-down.
Click to expand...
Click to collapse
The only thing I can get into is CWM, and it is tricky getting it to run... I think it quit before loading HBoot... TO do that I have to pull the battery and have it hooked up by USB, then turn it on.

Hold volume down as you do your power up procedure
Sent from my ADR6425LVW using Tapatalk 2

soniktoothe said:
The only thing I can get into is CWM, and it is tricky getting it to run... I think it quit before loading HBoot... TO do that I have to pull the battery and have it hooked up by USB, then turn it on.
Click to expand...
Click to collapse
Turn off your phone (you can pull the battery), then hold power and volume-down.

dlamber7 said:
Hold volume down as you do your power up procedure
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
It doesnt seen to respond to that...

Do you have adb? You could try adb reboot bootloader.

bananagranola said:
Do you have adb? You could try adb reboot bootloader.
Click to expand...
Click to collapse
Is that accessed from cwm?

soniktoothe said:
Is that accessed from cwm?
Click to expand...
Click to collapse
From your computer. You will need to install adb.

bananagranola said:
From your computer. You will need to install adb.
Click to expand...
Click to collapse
Okay, I have the adb installed and went through the process of connecting my inspire with the adb. A serial number came up so assume all is not lost because it installed the drivers for this device.
Where shall I go from here? Once again I can't say thanks enough...

Connect your phone and type adb devices. If it finds a device, type adb reboot bootloader. What does it say?

Send him over to #aceroot, it will be faster.
Sent from a dream.

Yeah, do what Tei says. Head to the freenode channel #AceRoot.

Webchat.freenode.net
In channel put "#aceroot" without the quotation.
Sent from a dream.

Thanks for your time last week on this, today the phone booted up with one press of the power button. No idea what happened but whatever glitch there was... it appears to have worked itself out.

Go there and get it set up properly anyway. That should have never happened.
Sent via LG E970 SlickROM v6

[Q] Sent my Nexus 5 to LG for repair, returned with this on boot

My Nexus 5 display shattered and sent it for display replacement to LG. They replaced the display and sent it back to me. After that when turning on the phone, I see this appear on the screen.
Not able to embed imgur link here. Attached the image.
It works perfectly well otherwise. I just want to know what does this mean.
Also, I'm planning to root my Nexus 5. I'm ignorant about how to root it. I'm little hesitant after seeing the above Would be helpful if someone can help me unlock the bootloader and root my phone.

blnwp said:
My Nexus 5 display shattered and sent it for display replacement to LG. They replaced the display and sent it back to me. After that when turning on the phone, I see this appear on the screen.
Not able to embed imgur link here. Attached the image.
It works perfectly well otherwise. I just want to know what does this mean.
Also, I'm planning to root my Nexus 5. I'm ignorant about how to root it. I'm little hesitant after seeing the above Would be helpful if someone can help me unlock the bootloader and root my phone.
Click to expand...
Click to collapse
its the bootloader. normally youd see it when you turn on the phone pressing the power butyon okus the volume down key.

simms22 said:
its the bootloader. normally youd see it when you turn on the phone pressing the power butyon okus the volume down key.
Click to expand...
Click to collapse
Okay. Thanks. As it appears without pressing the volume key, assuming it's not normal.
Besides, can you help me on how to proceed with rooting my phone? Should the normal steps work? I wanted to try the CF-Auto-Root but little hesitant because of this. Also guides say to use Volume up + down + power to enter bootloader mode. When I do that, it just appears in that same screen I mentioned. As you said if this is the bootloader, I'm already in bootloader and should proceed to next step?

blnwp said:
Okay. Thanks. As it appears without pressing the volume key, assuming it's not normal.
Besides, can you help me on how to proceed with rooting my phone? Should the normal steps work? I wanted to try the CF-Auto-Root but little hesitant because of this. Also guides say to use Volume up + down + power to enter bootloader mode. When I do that, it just appears in that same screen I mentioned. As you said if this is the bootloader, I'm already in bootloader and should proceed to next step?
Click to expand...
Click to collapse
yea, thats the bootloader.
any nexus is easy to root, and all follow the same steps. the basics..
1. fastboot oem unlock. this unlocks the bootloader
2. fastboot flash a custom recovery.
3. flash either the su binaries or a custom rom via your new recovery.
4. reboot and profit.

simms22 said:
yea, thats the bootloader.
any nexus is easy to root, and all follow the same steps. the basics..
1. fastboot oem unlock. this unlocks the bootloader
2. fastboot flash a custom recovery.
3. flash either the su binaries or a custom rom via your new recovery.
4. reboot and profit.
Click to expand...
Click to collapse
Thanks!! Appreciate the help. Will update if anything goes wrong with the root process.

Rooted using your steps and it went well. Thanks.
Sent from my Nexus 5 using Tapatalk

You should reboot completely after bootloader unlock or u will end up bootloopin
Sent from my Nexus 5

Yes, I read about in AC before rooting and I did reboot after unlock. Thanks!
Sent from my Nexus 5 using Tapatalk

[Q] XT925 Bricked after FDR

Hi all,
Did a factory data reset with a rooted, bootloader unlocked XT925 on stock jb and now its bricked. I can't access recovery, and when I do the simulated battery pull by pressing both volume keys and power button, it shows the moto dual core screen, before going to the android with the blue bar underneath usually seen while updating for about 30 seconds before briefly flashing the android on its side with the red triangular warning sign above it, then it powers off.
Is there anything I can do to save it? I had modified the start up animation which I think may be causing it. It won't even show up when plugged into my computer.
Thanks

Hi there :
At this point, can you get your xt925 on fastboot mode by pressing volume up and power while it is off? if so, you can just go ahead and flash a 4.1.2 rom. Since your BL is unlocked you can download one from any region that suits you.

hbenz2008 said:
Hi there :
At this point, can you get your xt925 on fastboot mode by pressing volume up and power while it is off? if so, you can just go ahead and flash a 4.1.2 rom. Since your BL is unlocked you can download one from any region that suits you.
Click to expand...
Click to collapse
Can't get into fastboot

aamd11 said:
Can't get into fastboot
Click to expand...
Click to collapse
With power + volume up you can't get to fastboot?

aamd11 said:
Can't get into fastboot
Click to expand...
Click to collapse
i have seen an unusual trend of hard bricks coming from fdr's recently. i cant begin to explain it, or offer a fix for it.
unfortunately from what you have described, your phone seems to be gone.
i can only suggest that anyone having issues with there phone, that they think a fdr would fix, dont do it!! re-flash with rsd instead until we determine what is causing this.
i know its not wide spread, but i wouldnt risk it just the same.

Sad Panda said:
With power + volume up you can't get to fastboot?
Click to expand...
Click to collapse
i got same problem. but when i get on fastboot and i start flashing my backup stock rom, it fails...
what can it be?

bweN diorD said:
i have seen an unusual trend of hard bricks coming from fdr's recently. i cant begin to explain it, or offer a fix for it.
unfortunately from what you have described, your phone seems to be gone.
i can only suggest that anyone having issues with there phone, that they think a fdr would fix, dont do it!! re-flash with rsd instead until we determine what is causing this.
i know its not wide spread, but i wouldnt risk it just the same.
Click to expand...
Click to collapse
Sad Panda said:
With power + volume up you can't get to fastboot?
Click to expand...
Click to collapse
Nope fastboot is inaccessible. Oh well! Sad this happened just before I updated to the loooong awaited KK build as well. Luckily I found a Sony Xperia Z1 for a great price so off to new things (and new subsection of XDA).
Thanks for the replies everyone!

on the other hand Xperia is a good unit

[Q] Dead after flashing stock rom - really dead

Hi there,
Today I tried to get back from cm12 to stock rom. I flashed, then tried to reboot ... nothing.
The phone is absolutely dead. No light when connected to power, no vibration when pressing the power button, no fast boot, no recovery mode. I tried to press power button over one minute, I tried to press for 20 seconds five times... nothing.
The device is absolutely dead. "adb devices" / "fastboot devices" show nothing, my Mac does not even see anything on the usb-port.
I cannot imagine how this is even possible. Is it really possible to destroy a device with flashing?
Has anybody have a hint for me?
S.

It's entirely possible to brick a device with flashing, in fact it's the most likely way to brick a device. Exactly what did you flash? And using what method?
Transmitted via Bacon

I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip
all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...
What a pitty

McSvenster said:
I used the method described here (xda-dev forum) with the stock rom from cygn.com : cm-11.0-XNPH44S-bacon-signed-fastboot.zip
all the flashes went fine, then I gave : "fastboot reboot" and got back " rebooting... finished. total time 0.005s". (And a black screen)...
What a pitty
Click to expand...
Click to collapse
Did you use a toolkit or did you do it manually?

//edit
Wow somehow I got threads mixed up while switching back and forth from Tapatalk and chrome. Sorry ignore what I wrote lol.
From what I've read, the colorOS stuff is the way to recover from a bricked phone. I don't have any experience in it though so I can't help much there. I would seek advice from that colorOS thread and hopefully you're able to recover
Sent From Lollipopified Bacon Goodness!

ek69 said:
If going back from cm12 to cm11s then the cm11s firmware files need to be flashed also.
Are you able to get back into fast boot mode still?
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
The stock images contain the firmware so that isn't the issue.

The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?

McSvenster said:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
Click to expand...
Click to collapse
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.
You didn't answer my question earlier though, diff you flash manually or via a toolkit?
I'd suggest you try this out:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon

McSvenster said:
The phone is practically dead, so colorOS seems to be no solution as I don't know how to flash it without usb connection. But thanks for the hint.
What I do not understand: What could have gone so wrong that the whole power circuit is damaged? I thought, that flashing only affects the internal "hard disk".
Does anyone know what exactly happens on powering on a working phone?
Click to expand...
Click to collapse
Well, I'm not entirely sure but I think that when you press the power button, you connect two ends, one end has a signal and the other end doesnt, when those two connect, the one without the signal gets a signal which will result in a battery going on maybe? Of this last battery part I'm not sure but that's how I guess it works...

I did the same as you - This fixed it for me.
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Basically you have to use a Windows computer and the original ColorOS firmware to fix your partitions. Follow this guide and it will flash your One with ColorOS, then you can flash TWRP and go on to flash CM11S.
It worked for me but it was a bit of a pain.

timmaaa said:
Nobody said anything about the power circuit being damaged, and it almost definitely isn't. That isn't the cause of a brick, what's most likely wrong is the partitions are corrupted, so it has no information telling it how to boot, what to boot into, or even to boot at all.
You didn't answer my question earlier though, diff you flash manually or via a toolkit?
I'd suggest you try this out:
http://forum.xda-developers.com/showthread.php?t=2991851
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, I mixed up two answers... I did it all with the fastboot commands (e.g. fastboot flash userdata cm11s\userdata_64G.img)
Thank you all a lot for your hints - I will try to fix it with a windows computer and keep you informed.

I'd suggest you try this out:
http://forum.xda-developers.com/show....php?t=2991851
Click to expand...
Click to collapse
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.
Again, thanks a lot!
All the best,
Sven

McSvenster said:
Well, that did the trick, thank you very much! Using Windows the phone was detected as a Qualcom mass storage. I could then use the tool that directly flashed the stock cm11.
Again, thanks a lot!
All the best,
Sven
Click to expand...
Click to collapse
Awesome news.
Transmitted via Bacon

Recovery only..

I have a Oneplus One here and tried to install a rom onto it after wiping everything.
When I plug it in the charger it goes to recovery, when I reboot to bootloader it does the same, after flashing too.
How can I recover it?

Did you install TWRP or CWM ? If so try another rom , if not read up on adb and install custom recovery first and find out if your bl is unlocked , if not start there , theres alot of reading you need to do
Sent from my A0001 using XDA-Developers mobile app

Vintage144 said:
Did you install TWRP or CWM ? If so try another rom , if not read up on adb and install custom recovery first and find out if your bl is unlocked , if not start there , theres alot of reading you need to do
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have TWRP. I had a rom installed so the bootloader is unlocked. All the guides suggest fixing it via fastboot but I cannot access that.. I think the partitions are messed up...

mrgnex said:
I have TWRP. I had a rom installed so the bootloader is unlocked. All the guides suggest fixing it via fastboot but I cannot access that.. I think the partitions are messed up...
Click to expand...
Click to collapse
Hey I think you have same problem as me. It's the volume button. It's stuck at Volume - (down). So every time you start your phone, it think you want to go to Recovery. What I did was, I tap the phone little hard on my hand sideways when I boot it up. That unstucks the volume button.
It works for me but not sure if it is the correct way. Just a suggestion. Don't hold me responsible if it breaks anything else.

viny2cool said:
Hey I think you have same problem as me. It's the volume button. It's stuck at Volume - (down). So every time you start your phone, it think you want to go to Recovery. What I did was, I tap the phone little hard on my hand sideways when I boot it up. That unstucks the volume button.
It works for me but not sure if it is the correct way. Just a suggestion. Don't hold me responsible if it breaks anything else.
Click to expand...
Click to collapse
I wish it was that easy. I didn't have the back cover on it when I tried this.

Did you have a backup of the previous rom (if one) that would save you the trouble, if not , adb
Sent from my A0001 using XDA-Developers mobile app

Hi, were you able to find a solution for this? I'm getting same issue now. PFA dmesg output http://pastebin.com/dKqm9e0c