Database Info

Am i bricked...

While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?

goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?

Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)

It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.

If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!

With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app

The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.

goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE

If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?

enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk

I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)

Bricked Sensation 4g (tmobile)

Hi guys, I was letting my phone charge, and when I checked it a few hours later, it wouldn't turn on, the orange light is NOT blinking/on, and I haven't rooted the phone or installed any custom firmwares. I got the phone "New" on ebay, and I've been using it for like 2 months now. I searched around the web for a solution, and some people recommended removing the battery, putting the battery in and holding VOL DOWN and POWER at the same time, and for some reason, I got it into the white screen with colored words on it. I did a Factory reset, and it got me back to the HTC home screen but it went back to a bootloop and now wont turn on anymore (strange)
Anyways, now i can't even go back into the recovery mode. I haven't rooted/modded this phone since I got it, so it's kind of weird to see this happen. I'm assuming the previous owner might have messed around with it and screwed it up? What should I do at this point?

is it the phone still can turn on and go to bootloader..?
if so..maybe you can try flashing and replace it with a new RUU stock..
firstly you must know what cid and software version of your phone..to do that..you can follow this guide
if your phone still don't want turn on...you can try replace it with different battery..
hope this help..

JJeamy said:
is it the phone still can turn on and go to bootloader..?
if so..maybe you can try flashing and replace it with a new RUU stock..
firstly you must know what cid and software version of your phone..to do that..you can follow this guide
if your phone still don't want turn on...you can try replace it with different battery..
hope this help..
Click to expand...
Click to collapse
Not anymore, it can't go into bootloader anymore. It could yesterday but no matter how many times I try it, it won't go into bootloader anymore :\

hyudryu said:
Not anymore, it can't go into bootloader anymore. It could yesterday but no matter how many times I try it, it won't go into bootloader anymore :\
Click to expand...
Click to collapse
try this, eject you battery sim and sd card and charge your phone without them for few hours or overnight , after that reinsert them and try to power on the phone

Mile_zdr said:
try this, eject you battery sim and sd card and charge your phone without them for few hours or overnight , after that reinsert them and try to power on the phone
Click to expand...
Click to collapse
Still nothing The orange LED doesn't come on/flash anything. The phone can't turn on and it's just dead now.

hyudryu said:
Still nothing The orange LED doesn't come on/flash anything. The phone can't turn on and it's just dead now.
Click to expand...
Click to collapse
did you already try using different battery..?

hyudryu said:
Still nothing The orange LED doesn't come on/flash anything. The phone can't turn on and it's just dead now.
Click to expand...
Click to collapse
check this http://forum.xda-developers.com/showthread.php?t=1522351

Nexus 5 Stuck at Google Loading Screen (Picture attached)

Hi.
This phone was working perfectly and I left it to go away to another country so it must have discharged it's battery.
When I got back it would not turn on. Even after charging for a day, it will not turn on.
When I have the charging cable connected, it goes to Google Logo Screen and it loops (restarts over and over again)
There is no error message.
Picture is attached so please let me know what to do. It was a gift so no receipt to claim warranty.
Thanks for any help in advance.

joongpark said:
Hi.
This phone was working perfectly and I left it to go away to another country so it must have discharged it's battery.
When I got back it would not turn on. Even after charging for a day, it will not turn on.
When I have the charging cable connected, it goes to Google Logo Screen and it loops (restarts over and over again)
There is no error message.
Picture is attached so please let me know what to do. It was a gift so no receipt to claim warranty.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.

Lethargy said:
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Click to expand...
Click to collapse
Thanks for the help...I am not sure If I am able to get into recovery more. Last time I tried, I was not able to.
Let you know once I try it.
Thanks.

Lethargy said:
Try booting into stock recovery and clearing cache, reboot.
If that doesn't work then you'll have to unlock the bootloader (which wipes data) and try flashing the factory images. A guide for that can be found in the first link of my signature.
Click to expand...
Click to collapse
I just tested and I am not able to get into recovery more...I am not sure what that mean. Should I connect Nexus to computer and see if it's recognized by computer and try to reload stock ROM?
Phone was never unlocked or flashed...it was in the same state as it was bought.
Can this be hardware problem? I saw some reports of similar thing happening with power button problem or other hardware problems.

joongpark said:
I just tested and I am not able to get into recovery more...I am not sure what that mean. Should I connect Nexus to computer and see if it's recognized by computer and try to reload stock ROM?
Phone was never unlocked or flashed...it was in the same state as it was bought.
Can this be hardware problem? I saw some reports of similar thing happening with power button problem or other hardware problems.
Click to expand...
Click to collapse
did you go into the bootloader, choose recovery, and it went to an android laying on its back?

This is the weirdest things...Spent days and days trying to bring it back to life and it would just reboot after GOOGLE logo. There was no way to get into recovery more.
I was looking around and someone said that tapping hard behind the power button with finger might bring it back and it did...so crazy. No matter what, I am a happy camper.
If you have tried everything, just try it...it behind power button and it might wake up the android that's been sleeping.

joongpark said:
This is the weirdest things...Spent days and days trying to bring it back to life and it would just reboot after GOOGLE logo. There was no way to get into recovery more.
I was looking around and someone said that tapping hard behind the power button with finger might bring it back and it did...so crazy. No matter what, I am a happy camper.
If you have tried everything, just try it...it behind power button and it might wake up the android that's been sleeping.
Click to expand...
Click to collapse
Can u explain how did u do that .what do u mean by behind the power button

I have the option to buy this device from a guy who has this problem and i have said to him to try the tips but not working. Computer does not see the device yet and thats logic since it just goes for 2-3 sec in bootloader he told me. Is this the power buttion failure or can it be fixed with nexus toolkit?
Price is €50 because of that and little damaged glass but i doubt if i can let it boot normal again.

Is my phone dead now?

Hi,
I recently got my phone from service provider they changed the motherboard. I was trying to unlock the bootloader since I have new motherboard it was unsuccessful so I couldn't unlock it. I was in bootloader menu I choose fastboot to unlock it, after a unsuccessful try I decided to reboot. So I choose reboot option but phone stuck at that menu. Nothing happened for 2 minutes. I removed the battery and now I can't open my phone. What should I do now?
edit: after 10 minutes it suddenly decided to boot itself but it's constantly rebooting itself idk what I'm gonna do now.
edit 2: now it's stuck on beats audio logo...
edit 3: I removed the battery, did a factory reset. Now I can reach lockscreen but when I unlock it phone is not responding and it restarts itself.
edit 4: somehow I managed to boot my phone successfully. For test the phone I installed subway surfers I played like maybe 2 minutes and then it was frozen and it made a weird noise from speaker for 5-10 secs and phone restarted itself again. And the bottom of the phone is kind of overheated. Now I figured out that if I wait for 10 minutes and if phone was completely cold it can boot itself but if it's overheated it can't bootself. I really hate this phone.

koolthing said:
Hi,
I recently got my phone from service provider they changed the motherboard. I was trying to unlock the bootloader since I have new motherboard it was unsuccessful so I couldn't unlock it. I was in bootloader menu I choose fastboot to unlock it, after a unsuccessful try I decided to reboot. So I choose reboot option but phone stuck at that menu. Nothing happened for 2 minutes. I removed the battery and now I can't open my phone. What should I do now?
edit: after 10 minutes it suddenly decided to boot itself but it's constantly rebooting itself idk what I'm gonna do now.
edit 2: now it's stuck on beats audio logo...
edit 3: I removed the battery, did a factory reset. Now I can reach lockscreen but when I unlock it phone is not responding and it restarts itself.
edit 4: somehow I managed to boot my phone successfully. For test the phone I installed subway surfers I played like maybe 2 minutes and then it was frozen and it made a weird noise from speaker for 5-10 secs and phone restarted itself again. And the bottom of the phone is kind of overheated. Now I figured out that if I wait for 10 minutes and if phone was completely cold it can boot itself but if it's overheated it can't bootself. I really hate this phone.
Click to expand...
Click to collapse
did you try to use a RUU.exe?

rzr86 said:
did you try to use a RUU.exe?
Click to expand...
Click to collapse
phone is completely stock atm. Can I use a ruu.exe without s-off and unlocked bootloader? And that game / freeze / constant 5 seconds noise problem happened one more time but before all of these problems.

koolthing said:
phone is completely stock atm. Can I use a ruu.exe without s-off and unlocked bootloader? And that game / freeze / constant 5 seconds noise problem happened one more time but before all of these problems.
Click to expand...
Click to collapse
of course you can use it without S-OFF
only your bootloader must be locked or relocked
i assume is still locked since you tried htcdev method

rzr86 said:
of course you can use it without S-OFF
only your bootloader must be locked or relocked
i assume is still locked since you tried htcdev method
Click to expand...
Click to collapse
I bought this phone from Turkey so I downloaded Turkish Ruu file which is: RUU_PYRAMID_LE_ICS_35_S_HTC_TUR_3.32.468.112_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253106_signed.exe but I got 132 signature error which also means that I downloaded wrong RUU file. I'll try to s-off somehow to learn my phone's cid.

koolthing said:
I bought this phone from Turkey so I downloaded Turkish Ruu file which is: RUU_PYRAMID_LE_ICS_35_S_HTC_TUR_3.32.468.112_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253106_signed.exe but I got 132 signature error which also means that I downloaded wrong RUU file. I'll try to s-off somehow to learn my phone's cid.
Click to expand...
Click to collapse
you can use the cid getter app

rzr86 said:
you can use the cid getter app
Click to expand...
Click to collapse
I don't know why but I can't charge and turn on my phone. I think is hard bricked now.

koolthing said:
I don't know why but I can't charge and turn on my phone. I think is hard bricked now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1522351

rzr86 said:
http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
I'm on ubuntu 12.04 now and keep getting device can't be detected error. I think it's completely dead.

koolthing said:
I'm on ubuntu 12.04 now and keep getting device can't be detected error. I think it's completely dead.
Click to expand...
Click to collapse
if you know about jtag method then see this thread
http://forum.xda-developers.com/showthread.php?t=2775115
it is your last option
by the way try this
remove battery,sim and sdcard and charge the device as it is for 4-5 hours
put them back and switch it on
see if it boots

rzr86 said:
if you know about jtag method then see this thread
http://forum.xda-developers.com/showthread.php?t=2775115
it is your last option
by the way try this
remove battery,sim and sdcard and charge the device as it is for 4-5 hours
put them back and switch it on
see if it boots
Click to expand...
Click to collapse
jtag is too complicated for me. I left my sensation to charge overnight like you said but still no luck. Anyways, thank you so much for your help.

koolthing said:
jtag is too complicated for me. I left my sensation to charge overnight like you said but still no luck. Anyways, thank you so much for your help.
Click to expand...
Click to collapse
you take it to a local shop to do it
but know this, it may be expensive

I managed to get to QHSUSB_DLOAD mode. I had this output I dont have any sdx.
Searching for bricked device...
The bricked device is on
Use the above node to perform operations using the emmc_recover tool
Click to expand...
Click to collapse

koolthing said:
I managed to get to QHSUSB_DLOAD mode. I had this output I dont have any sdx.
Click to expand...
Click to collapse
did you try unbricking method again?

rzr86 said:
did you try unbricking method again?
Click to expand...
Click to collapse
ye i tried wire trick in this video https://www.youtube.com/watch?v=_Pcxt6nKI10 and i tried unbricking method.
problem is; in the output there should be a node about sdX
You should get something like sdX. We are interested on that "X"
Click to expand...
Click to collapse
but i didnt get anything about sdx in output... it can detect my device but i can't continue because of this.

[Q] Softbricked Photon

My Photon Q won't boot up for some reason. I didn't do anything especially strange to it. It ran out of power, I plugged it in as it was turning off and then it wouldn't boot up. It's not a problem with the screen because when I turn it on it still comes up with "Bootloader unlocked etc" but then I just get a blank screen, with the LCD on, but just black. So the phone is rooted and I managed to get it into TWRP. Any ideas on what I can do to get it working?

Charge it enough to see if you can get it to boot... This is always a dangerous scenario with this device it seems, running the battery completely dead.
I had similar issues where I could not boot because the battery would die before it would finish booting. If you can get it to offline charge, that's the best thing to do. If not, try to charge it in TWRP.
Once you get enough of a charge, it should boot. If it still doesn't, restore a backup in recovery.

arrrghhh said:
Charge it enough to see if you can get it to boot... This is always a dangerous scenario with this device it seems, running the battery completely dead.
I had similar issues where I could not boot because the battery would die before it would finish booting. If you can get it to offline charge, that's the best thing to do. If not, try to charge it in TWRP.
Once you get enough of a charge, it should boot. If it still doesn't, restore a backup in recovery.
Click to expand...
Click to collapse
Hi arrrghhh, thanks for the reply. I tried doing that and it didn't work, but thankfully I managed to backup my photos, phone numbers and text messages using TWRP, followed this guide (http://forum.xda-developers.com/showthread.php?t=2295643) and did a stock reset. So now I can relax in the knowledge that my phone isn't dead afterall.

liquidmetalrob said:
Hi arrrghhh, thanks for the reply. I tried doing that and it didn't work, but thankfully I managed to backup my photos, phone numbers and text messages using TWRP, followed this guide (http://forum.xda-developers.com/showthread.php?t=2295643) and did a stock reset. So now I can relax in the knowledge that my phone isn't dead afterall.
Click to expand...
Click to collapse
Evidently you didn't have a full backup?
You should definitely make one - can't always depend on links to stay alive with this old device.
Honestly that should be step #1 after flashing a custom recovery like TWRP... immediately take a full backup in case you ever need to restore.

arrrghhh said:
Evidently you didn't have a full backup?
You should definitely make one - can't always depend on links to stay alive with this old device.
Honestly that should be step #1 after flashing a custom recovery like TWRP... immediately take a full backup in case you ever need to restore.
Click to expand...
Click to collapse
Do you know how to get APNs working? You probably know that changing the MNC number causes the APN to disappear. I managed to get it working before, but that was ages ago and I can't remember how I did it.

liquidmetalrob said:
Do you know how to get APNs working? You probably know that changing the MNC number causes the APN to disappear. I managed to get it working before, but that was ages ago and I can't remember how I did it.
Click to expand...
Click to collapse
OK, it turns out I didn't have to change the MNC, and it's working with the default value of 20. Thanks anyway!