so i had my xperia z on and plugged it in to my pc and it went off and did not turn back on tried all the tips on the forum but none of them worked.
i only got the phone 8 days ago.
mtwiscool said:
so i had my xperia z on and plugged it in to my pc and it went off and did not turn back on tried all the tips on the forum but none of them worked.
i only got the phone 8 days ago.
Click to expand...
Click to collapse
Did u perform rooting? unlocking BL? flashing roms ?
either ways....getting your phone is one worst thing....
It is very hard to brick an Xperia device nowadays.
You sure is not just out of juice? Sometimes it can be that the battery suddenly dies and you have to leave it charging a lot of time to turn it back to life.
Locked or unlocked bootloader?
Flashtool should do the job in case of soft brick. Or even EMMA in case you are unlocked.
Does it get detected by the PC?
DrKrFfXx said:
It is very hard to brick an Xperia device nowadays.
You sure is not just out of juice? Sometimes it can be that the battery suddenly dies and you have to leave it charging a lot of time to turn it back to life.
Locked or unlocked bootloader?
Flashtool should do the job in case of soft brick. Or even EMMA in case you are unlocked.
Click to expand...
Click to collapse
unlocked bootlocker(unlocked when i got it)
battery was at 100%
rooted but no custom firmware or karnel and i did the root the day i got the phone and the phone died when pluging it into a pc to get some files from the phone the only application(on phone) open was boot up ones and Google chrome.
Not a Issue with the pc as i used an xpreia u and the xperia z worked on the same port.
the phone stopped even getting picked up by the pc only red led.
this is a know issue with the xperia z(from android) ics when i loocked at it, it seamed to be the sleep of death and power reset did not work.
firmware: default .434 uk
phone model: xperia c3603
Have you tried connenting it in fastboot mode?
DrKrFfXx said:
Have you tried connenting it in fastboot mode?
Click to expand...
Click to collapse
i did try that but it just flashed the red led
mtwiscool said:
i did try that but it just flashed the red led
Click to expand...
Click to collapse
Discarded driver corruption?
Reparations probably are gonna cost you as much as a new device if they need to replace the motherboard.
Youare not under warranty.
DrKrFfXx said:
Discarded driver corruption?
Click to expand...
Click to collapse
it still finds my old xperia u
and i did reinstall that with no success yestaday.
can you flash only the stock kernel from fast boot mode? i once had the same issue when the device failed to start with red led blink, and flashing the kernel fixed this issue.
You bought the phone with unlocked bootloader? Was it used? Else I think you're confusing unlockable and unlocked.
the phone has at last got to sony my issue should get fixed soon
mtwiscool said:
the phone has at last got to sony my issue should get fixed soon
Click to expand...
Click to collapse
Any news? My Z died most likely because I messed with terminal emulator (tried to get rid off CWM bootloop the easy way ) and it didn't boot up ever again... Only thing I get out of it is red led when pressing power and vol+ when usb is connected. Computer sees it as a usb device but cannot connect to it. No fastboot or flash mode. I'm going to send it for repairs but it will probably be too expensive to get it done.
I already got htc one to replace Z. One sounds awesome! Incredible speakers for a phone. It is fast and sweet. BUT it looks STUPID when you put Z and One side by side... And no waterproofness of course
webbimato said:
Any news? My Z died most likely because I messed with terminal emulator (tried to get rid off CWM bootloop the easy way ) and it didn't boot up ever again... Only thing I get out of it is red led when pressing power and vol+ when usb is connected. Computer sees it as a usb device but cannot connect to it. No fastboot or flash mode. I'm going to send it for repairs but it will probably be too expensive to get it done.
I already got htc one to replace Z. One sounds awesome! Incredible speakers for a phone. It is fast and sweet. BUT it looks STUPID when you put Z and One side by side... And no waterproofness of course
Click to expand...
Click to collapse
sbe = slow
nearly 2 weeks and not even looked at the device
mtwiscool said:
sbe = slow
nearly 2 weeks and not even looked at the device
Click to expand...
Click to collapse
So sony sucks globally when it comes to customer care?! Have to try it my self. I've heard that finnish service company is very very good at what they do... Even if your phone has a 50 cal bullet hole smack in the middle they'll blame water/moisture damage. If you manage to convince them to actually look at your device they'll send it to some Euro main service central where it will be sucked in to a wormhole and time around that phone seems to stop
update:
SBE fault : charging - does not charge
Status : With High Level Engineer - Component Repair
update:
sbe have said the phone is unrepairable and are going to exchange it for another one.
Wow this took some time...
Almost two months it took:
1. Sending device to finnish service center
2. It was sent to sony service right away
3. after waiting and waiting I asked finnish service whats going on: Atleast their version was that sony had fixed (or replaced with a new device) and sent it back to finland. And during shipping device was lost.
4. According to finnish service sony was figuring out what to do, propably giving new devices....
5. So after almost two months I got a replacement XZ. And it was done under warranty. Yay!
Hello XDA-Forum,
i am new here, so you dont know me. Therefore i have to mention at least one thing about me: I never ask for help. Especially not regarding electronic Devices and Computer Systems. I always found my answers without asking.
Now i do ask for help. Do the math, its a serious problem . As i am used to solve my problems before asking for help, i have much to tell before anyone could add to what i already know about this problem (although i have to admit that i am pretty new to the Smartphone World). And as sure as i know that no one here wants to read another "Phone broken, HELP!" Thread, so sure i know that not everyone has the time or patience to read my ramblings (i actually wrote a rant too, but decided not to include it here ). So i prepared a summary, and you can see at a glance (almost) if you could help me at all.
Short Story:
My HTC One is Hard Bricked, and beyond my ability to repair - stuck in QHSUSB_DLOAD mode, no access to partitions, no booting under dead screen. It seems i have to send it in for repairs, but i dont like that(well who does?). I researched the problem, tried every solution i could find - no result! if you happen to know a solution, please read the long story to learn what i have tried so far, and if your solution is something completely new (something i didnt try) - PLEASE tell me ASAP before i send it in for repairs.
So, i tried everything i know of and came to the conclusion: it is beyond repair, at least for me. But as this is against everything i believe in (well not everything but i hope you get the point ) i want to find some other Solution if not for me ( as i need my Phone to be working again soon) then at least for the next one facing the same problem. Again: read the long story, or at least the last part, to know what i am asking for... Basically i want to collect all information regarding this problem and find a solution if possible.
Oh and i would prefer technical answers (even if i might have to learn more to understand them) over answers that suggest "Dont bother, you are a noob, you wouldnt understand, just send it in". If you are about to give such an answer, rethink and do something else .
Long Story (Part 1 - What happened):
31/12/2013: My HTC One suddenly stopped working. Until then it worked just fine since i bought it in July 2013. It happened without any apparent cause or any hint of what went wrong, during everyday use, no water involved, no falling, nothing that i could identify as cause. I pressed the power button to wake the phone as always - but the screen stayed black. At first i thought the battery could be empty, but i checked it only 5 minutes before, and it said 32%... still i thought the power indicator could be buggy. Since then it never showed any lifesign again though. It wont start, it wont charge.
I researched about this, and it seems that others had the same problem, and on several different devices. I think i found almost every Qualcomm based device, but mostly the problem was caused by flashing, so this can not be the same problem. If i remember correct, i found HTC One, HTC One S, HTC Desire C, HTC Sensation, Nexus 4/7, Samsung Galaxy S3/S4 and maybe some more, with the same issue i have - Device suddenly went black and got stuck in QHSUSB_DLOAD mode without apparent cause. Many people get at least a lifesign from the LED tough ( be it blinking occasionally, or staying on all the time, or blinking after pressing certain buttons) - i dont.
Long Story (Part 2 - What i tried):
I found several tips on how to revive a device in this state, most recommending something like "press power and one(or both) volume button(s) for XX seconds/minutes" sometimes with the addition to do this under a bright light bulb.
I tried holding the power button, power + vol. down, power + vol. up, power + vol. up + vol. down, for {10,20,30 seconds, or 1,1.5,2,3,5,10 minutes} (countless times), and the same under a light bulb (i doubt this makes any difference as i already did some resets previously, outside in pitch black darkness long before the phone died).
Some recommended to plug it in to charge and dont touch it for 3,8,12 hours - i did that. i tried charging with wall plug and via USB at laptop (for short periods and for 1,3,4,6,8,12,18 hours without touching it).
At the moment i try to leave it off the charger for some days (the weekend and probably some days after) hoping that it will eventually loose all charge and does some sort of reset after that. I doubt it will work, or even be enough time for discharging (as i doubt that it actually USES power in this state) but dont know what else to try before sending it in.
The charging-led stays off when plugged in and there is no response at all from the device. Except when i plug it in at the laptop, Windows recognizes it as QHSUSB_DLOAD. And under Linux i get the Qualcomm device too - no partitions though. If i press power for 10 seconds while connected, it reconnects - so the power button is working. QPST recognizes it as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode? I tried to get some information through QPST but it tells me the phone needs to be in DIAG mode - which i obviously cant activate on the phone itself. Other than that no life sign at all( also no recognition by adb and fastboot - so its not booting under a dead screen as someone suggested somewhere - dont remember where).
Everyone who had gone as far as i did in trying to revive the phone just gets this last answer "JTAG, or send it in for repair".
Long Story (Part 3 - What i learned):
As i understand it, the Qualcomm Processor switches to this state (QHSUSB_DLOAD) in case there is a severe problem. But i want to know exactly WHAT problem can cause this? And if there is ANY way of convincing the processor to switch to some other state without opening the device?
I dont know JTAG, i never heard of it before this research, so please correct me if i am wrong, i did just a brief research on JTAG and found it too complex to grasp in one or two days i will delve into it at a later time. Here is my first few-minutes-glance at JTAG: it is some sort of standardized hardware-debugging protocol built into many chips, and also the Mainboard or Processor or both in modern Smartphones and Tablets. One would need to open the device and solder the connection cables of a "JTAG-Box" to specific contacts on the Phones Mainboard, is that right? or is there a plug? (I think i found some people using a plug and some using solder iron... i dont remember properly.) When a JTAG-Box is connected to a JTAG-enabled chip, it can issue debugging-commands and/or queries to check (and/or modify?) the functionality of the chip. I found some mentions of JTAG via USB without explanation, is this a way to issue JTAG commands without JTAG-Box over USB Cable? (would be very convenient) Or is it just a way to connect the JTAG-Box via USB to the Computer?
You might ask, if i researched it, i should have every answer, so why am i posting this? Right, i got SOME answers. Now, i know...:
1) ... that am not the first one, nor the only one with this particular Problem. And not even my phone model is the only device with this problem. It might be, all Qualcomm powered devices are possible candidates for a sudden-brick-syndrome.
2) ... some ways to revive a Phone in this state (none working for mine).
3) ... if all reviving tricks fail - JTAG or Repair-service.
4) ... that JTAG needs an opened device (or does it? JTAG via USB maybe?)
5) ... that my phone is not entirely dead: at least the processor can still (sort of) communicate with the PC in Qualcomm High Speed USB - DownLOAD mode.
6) ... no one knows (or tells) what the cause is (or could be) for this problem. The only answers i got are: "There are many possible causes." and "It could be a Software problem" (HTC Support) and finaly "No one can tell without analyzing the device" (HTC and Carrier Support) - Sure no one can definitely tell what EXACTLY is wrong with THIS device... but someone could know what COULD be wrong (What the KNOWN causes are), and just tell me.
Long Story (Part 4 - What i want to know):
Well... I could(/should?) just give in and send my phone in for repairs and hope for warranty. But i did unlock the bootloader through HTCDev (had no other option for unlocking due to HBOOT 1.44) and suspect, they might use this fact to refuse warranty and charge me for repairs, which i might not be able to afford right now. Further, i am feeling absolutely helpless in doing so, and i am NOT used to feel helpless facing ANY sort of problem with ANY electronic device! It is NOT a nice feeling! And i want to change that! Even if it will be too late for me, as i have to get my phone back soon and will probably send it in this week for that reason, i want to find a Solution, that anyone could use to solve this Problem without even contacting the Service, if it is possible to find such a Solution. That is the reason i am posting this, and here is what i want to know:
1) EVERY Story about devices stuck in QHSUSB_DLOAD mode.
1a) IF they where revived and HOW.
1b) What was the cause?
1c) If they could not be revived...
- ... and had to be replaced by a new device: what did the repair team tell what exactly was broken? if they told you anything at all.
- ... and needed replacing parts: WHAT parts where replaced?
- ... ANY hint of what caused the defect?
1d) WHEN did it happen? (while flashing seems to be the most common scenario, but i and some others had it happen during everyday use)
2) What exactly is possible to do in QHSUSB_DLOAD mode (probably using QPST)? and what isnt? f.e.:
2a) Pulling any data from the phone without switching to DIAG mode?
2b) Getting ANY information about the phone? (IMEI,CID, etc... Hardware components - i guess it would need a switch to DIAG mode?)
2c) Switching to DIAG(or any other) mode ONLY using the PC and USB connection? (if possible, how?)
2d) Pushing any Data to the device
As i understand it, that is the purpose of this mode(is that correct?), but:
2e) What data can be pushed? Bootloader? System Image? .... i think some CPU firmware is delivered with QPST, correct?
2f) Is it possible to convert an existing System Backup so that it can be flashed with QPST? (i understand QPST needs files in IntelHEX format to push them? Or is that just the CPU Firmware?)
2g) QPST recognizes my phone as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode?
3a) If i get no Partitions in Linux while the QHSUSB_DLOAD device is recognized, could this be an indicator for an Hardware failure?
3b) Does it mean, at least the flash memory is fried? (my guess)
3c) Could i tell if the Mainboard was fried by NOT even getting a QHSUSB_DLOAD device? Or can it still be the Mainboard?
3d) Can i tell anything from these facts (Getting QHSUSB_DLOAD device recognized but no partitions)? other than "its a hard burned brick" obviously...
4a) Which kind of HARDWARE failure could create this state?
4b) and how could that happen during normal use in a device that is only 6 months old, and in good condition? 5a) What kind of SOFTWARE failure could cause it?
5b) while it is running? (every day use / not flashing) 6) IF i send it in:
6a) Will they be able to access my data?
6b) Can they tell (by JTAG maybe) if it was rooted,flashed, had an unlocked bootloader?
6c) And the hardware is dead, will they just replace the fried parts? or replace the Phone with a new one? (not really important but nice to know )
7a) Is it possible to use ANY type of JTAG commands/queries/(whateveritiscalled) WITHOUT opening the device? (via USB)
7b) Without a JTAG-Box? (already existing software simulating a JTAG-Box) 8) What kind of Information can be gathered by JTAG? f.e.:
8a) Working state of hardware components?
8b) Access to files on flash memory? 9) What kind of modifications/commands can be made/issued by JTAG? (depends on the device/chip attached i assume?)
I know i could just buy a JTAG-Box and learn everything about JTAG to answer some of these questions myself. But i did not find time for learning about something completely new (new for me) yet, and i dont have the money at the moment to just buy a JTAG-Box without knowing how to, and if i will use it (dont even know how much it is...). I will certainly NOT open my 660€ phone, probably breaking the screen and whatever in the process, because of its DONT-OPEN-ME-Design(nice looking, but in some cases inconvenient), and make it a test-dummy for my first JTAGing steps. So it would be nice if someone with some experience in that matter, could give me a brief overview of the possibilities and uses of a JTAG-Box - AND if there is some way to simulate one.
And finally i would like to get into contact with people who might have a clue of the possible causes for this problem, and the ability and willingness to work on a solution. I did find some WIP Unbricking Projects also working on a solution for QHSUSB_DLOAD related issues, but all of them where Model-specific (and mostly for cases where a specific flashed software was the cause) and none for the HTC One (M7)... Although i would like to have a general solution for every device and cause, i doubt there would be any Model-specific Project if it was POSSIBLE at the moment to provide a general one. It would be nice though, if we could at least TRY to make one(some people probably are already trying). But i assume (from what i read) that the existing unbricking projects still need access to the internal storage. So, no access to storage = hardwarefailure & not unbrickable by software?? Even if thats the case and my phone is realy beyond (sofware)repair, i would still like to get answers to my other questions!
If you did read all of this - Congratulations! Have a coffee and a break
I am sorry for:
- noob questions (if there are any left besides the JTAG related - i cant tell anymore)
- annotations and supplements in braces (it can be annoying, i always squeeze in some thoughts somewhere)
- forcing you to read this wall of text, probably full of spelling and grammar errors (i am tired and somewhat tense)
- bad English (not my native language, and... i am tired)
OMG this post is incredibly long. I'll give you a short answer.
Yout phone is hard bricked and MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things.
If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty. You SHOULD sebd your device for repair definitely, I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Sent from my HTCONE using Tapatalk
Very interested in the actual answer, and the reason, subscribed.
Sent from my iPod touch using Tapatalk
elvisypi said:
... MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things...
Click to expand...
Click to collapse
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
elvisypi said:
...If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead...
Click to expand...
Click to collapse
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
elvisypi said:
...probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty...
Click to expand...
Click to collapse
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
elvisypi said:
...I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Click to expand...
Click to collapse
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
MarvThor said:
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
Click to expand...
Click to collapse
Hi, just wondering if you had any updates to your story?
I have a HTC One in basically the same situation - it totally died on my wife in the middle of her using it. The battery was at over 50% and we have never even dev unlocked it or flashed ROMs or recovery etc. No lights come on when charging, tried all manner of the power, power+vol key combos etc, tried the bright light as well, nothing gets it to come alive. Plugging into the computer does recognise the HSUSB_DLOAD low level qualcomm device but as yet I havent been able to get drivers to allow it to be recognised. I am taking it to a place on the weekend that says they have JTAG box and may be able to help. I would send it away for warranty replacement but it's my wife's phone and she hadnt backed up the photos on it for a few months and we have a 20 month old son, so we are trying everything possible to retrieve the data off it. Lesson learned, will be putting in place backup regime on our phones from now on!
Will let you know if any joy comes from the JTAG process
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Sorry, i totally forgot about this Thread over all the other things in the last weeks (Starting a Business, moving to a new Place.. etc).
scarecrow420 said:
Hi, just wondering if you had any updates to your story?
Click to expand...
Click to collapse
Yes, i sent it in for repairs, and got it back two weeks later. They had to replace the Mainboard and some other Parts(plus some they broke during Repairs), i could not get any information about the possible causes other than "there are many"... It was covered by the warranty though.
I dont think they could get any data from the Phone.
scarecrow420 said:
Will let you know if any joy comes from the JTAG process
Click to expand...
Click to collapse
I would appreciate that
scarecrow420 said:
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Click to expand...
Click to collapse
If the cause is indeed the power brick, i will have to check mine again (measure its output). It is supposed to have 5.0V 1.0A output only, which is the same that the HTC Charger is labeled with.
Well, good luck with your Phone! But if your Phone is as dead as mine, i am afraid you probably wont get those Photos back...
-
Ok, i got my phone back without trouble - but i am still researching (when i have got the time ) the causes and a possible solution for this problem. So, if anyone has any information that could be helpful: please post it here!
Hi guys! Sorry for my bad english but i'm italian. My HTC One gone in QHSUSB_DLOAD mode 3 times (it's not a joke) and i've still it in my hands
This is my configuration now: (today my phone entered in QHSUSB_DLOAD mode)
Firmware = 4.19.401.8 (Darkbootoader)
ROM = SkyDragon v12.0
Kernel = ElementalX 13.0
PVS = 5
Today when tried to turn on the screen with doble tap it do nothing, screen was completly black and same thing when i hold the power button with vol down. After i plug in USB (it was a normal nokia cable) cable and hold power + vol. down for about 20 seconds (there wasn't LED or blinking button, anything) it's boot into bootloader:highfive:
I suppose (because every time my phone bricks when i do too Undervolting) it has "hangry" of energy and it boots up anymore if i don't give him an "help". The same thing when i had the MIUI with the same undervolting
Maybe is too much Undervolting the reason of hard brick, did you undervolt your CPU like me?
Did you find out any answer?
Where you able to bring it back to life?
Did you send it back to HTC for repairs? How did it go?
Would this work?
http://unlimited.io/qhsusbdload.htm
Dredead said:
Would this work?
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
third time.
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Hi, I Have Same Problem Since A Month With My HTC One M7 32GB
I Got this phone as a Gift From USA HTC one M7. My Phone Just got hanged on lockscreen when i try to restart it, it turns off but did not turn on,no single light is turning on, no screen light or notification, no recovery or download mode. its like a brick piece. i tried all charging tricks such as USB PC ,Wall Charger for Hours, Orignal Charger and rest things, i cannot send phone to USA , i am in qatar, what should i do, any guys who experienced such problem and how did they solved it and, what will be the cost if no warranty. any help ? thanks in advance. :crying:
till22 said:
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Click to expand...
Click to collapse
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
mkclarke said:
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
Click to expand...
Click to collapse
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
clsA said:
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Cool, thanks! I wonder if a vm running linux would work. All my machines are windows. Not sure how the vm would handle the usb connection. I'll have to see what I can figure out.
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
clsA said:
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Yes! I just thought of that after I posted. I think I still have an ubuntu live CD around here somewhere...
Thanks!
I'll be damned! This worked! I just popped in the latest Ubuntu liveCD and went to town. My phone is now up and charging. Once it's at 100%, I'll try pushing TWRP recovery to it and restoring my last backup.
Thanks again for sending me to that link!
---------- Post added at 10:42 AM ---------- Previous post was at 09:59 AM ----------
Done and done... pushed TWRP and restored my last backup. It's as if it were never bricked! And it also updated my kernel, which is what I was trying to do in the first place.
Just for future reference for anyone coming across this thread, there are two distinct types of bricks being discussed here.
The first results from a borked firmware update. In this case, everything works on the hardware side, it's just that the phone can't boot because the firmware is messed up. This is usually fixable using Dexter's method.
The second, and the problem experienced by the OP, is more serious and is hardware related. I have seen this occur with multiple HTC models. Something related to power management on the motherboard dies so that the phone no longer can no longer get power to start up. When this happens, the phone will typically have shut down without warning despite having a good battery charge. I have never seen or heard of a fix for it beyond returning it for warranty repair.
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Being new to Sony Xperia phones in particular and Android in general, are there any "standard fixes" for when a phone seems to be dead?
After routinely putting the phone to sleep with about 35% battery capacity left, I now can not rouse the phone, nor charge it.
Long press (20 seconds) of power button was my first try. Pressing the yellow reset button in the compartment with the SIM was next. Neither had any effect. Tried a recommendation I read to press the power button and volume down button. Nothing. Charging via the wall wart on mains power and via computer USB port seems to be not working as well -- at least no notification light is on. I will leave it plugged in for a few hours to see what happens, JIC.
Any other things I should try before taking it back to the Sony store? Not sure the stores here in Thailand even take back defective phones as they are not bona-fide Sony stores. They are licensed resellers.
I bought the phone on 18-October-2014, and have not done any rooting or "modding," just normal (?) user actions like adding a few apps and making a few calls.
I think you've done everything to get the phone up and running, take it back to the shop and ask for a replacement or your money back. That would work in uk not sure about where you are?
Thanks. I was hoping there was some esoteric ritual I could perform.
I'm going to wait a day or so to see if it resurrects, like a few people have reported. If it remains unresponsive, I'll try the store. I also seem to recall seeing a Sony repair center someplace.
Same problem
Great, you're not alone out there.
I got my Sony Z3 Compact on the 25th of October. Also didn't do any unsupported things with it. No unlocking, no rooting or tweaking. Only original apps from App Store.
After long-pressing the on/off button, I selected the restart option on the screen. Then everything just stopped. A brick.
Tried power+volDown (nothing happens), tried USB connecting to Sony flash tool "Emma" (nothing happens when connecting to a PC, basically the same as not connecting a cable to anything, device manager doesn't find any device connected), tried yellow hard-power button. Nothing happens - a complete brick. Even after connecting a charger, the light does not come up. The battery was almost full (about 90%) at the moment of disaster.
Gotta carry it to the service.
Did you fix your brick?
Phoneless in Thailand
No, I couldn't revive my phone. I took the phone to the Sony-licensed store where I bought it and they wouldn't replace/refund it. They only replace within seven days of purchase, and I went to the store on day #11. (The phone bricked on day #9, but I waited a full 24-hour period to see if letting the battery drain further might help.)
Took the phone to the "Sony Service Center" which is only a collection center to send damaged goods to Bangkok, a two-hour drive up the road. I should expect to hear from them in "three to four weeks." Having lived in Thailand for as long as I have, that translates to "You'll be lucky to have your phone back by New Years Day." Considering they should get the phone within a day, they must have a LOT of damaged products in queue if I can't even get a status report for at least three weeks.
Hope you have better luck.
Luckily I got my brick replaced on 12th of November. So far so good - the new Sony Xperia Z3 Compact is working and I love it. Hope you will also meet your beloved soon...
I've already searched on the forum and googled it and came to the conclusion that my Xperia Z1 is now a paper weight.
Still my curiosity got the better of me
In short, I have a Xperia Z1 (C6902) which was working perfectly till today (2 years old),
Rooted, Unlocked bootloader, TWRP recovery, CM 12.1 Nightly ROM (July).
I remember the battery level was around 40% and after a phone call, I put it on charge and that was the last time I saw my phone powered on :|
I came back, only to see that my xperia z1 is bricked. I've already tried -
1. Power + Vol -
2. Power + Vol +
3. Holding Vol - while connecting to laptop/computer
4. Holding Vol + while connecting to laptop/computer
Neither the phone vibrates nor the LED shows any color, not even recognized in laptop/computer and Sony PC Companion app in windows.
So is there any way to recover my phone now?
As told earlier, my phone is 2 years old so of course out of the "warranty" period but it's really not fair to me as a consumer, cause it's an already known bug and a very serious one, not ought to be on any phone let alone on a once flagship.
So is there any way I can fight my way with the Sony to get my phone repaired without shelling out double the cost of current market price of this 'flagship'
I am planning on taking my phone to Sony service center tomorrow.
GravityDead said:
I've already searched on the forum and googled it and came to the conclusion that my Xperia Z1 is now a paper weight.
Still my curiosity got the better of me
In short, I have a Xperia Z1 (C6902) which was working perfectly till today (2 years old),
Rooted, Unlocked bootloader, TWRP recovery, CM 12.1 Nightly ROM (July).
I remember the battery level was around 40% and after a phone call, I put it on charge and that was the last time I saw my phone powered on :|
I came back, only to see that my xperia z1 is bricked. I've already tried -
1. Power + Vol -
2. Power + Vol +
3. Holding Vol - while connecting to laptop/computer
4. Holding Vol + while connecting to laptop/computer
Neither the phone vibrates nor the LED shows any color, not even recognized in laptop/computer and Sony PC Companion app in windows.
So is there any way to recover my phone now?
Click to expand...
Click to collapse
may be your battery dead.
In my opinion you can save the path to Sony repair center. Even if they get the phone running I think they will deny any support because your phone isn't in original state.
It is rooted, bootloader unlocked, etc.
If you have luck only the battery died and replacing the old with a new is enough. The problem is that you need some skills changing it yourself because our z1 hasn't got a removable back cover.
@GravityDead u may follow this link and try the steps mentioned here: http://forum.xda-developers.com/showthread.php?t=1849170
If that didnt work then u may try this link: http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Good luck Bro!
iedafarha said:
may be your battery dead.
Click to expand...
Click to collapse
I don't think so, the battery was working just fine
motorazrv3 said:
In my opinion you can save the path to Sony repair center. Even if they get the phone running I think they will deny any support because your phone isn't in original state.
It is rooted, bootloader unlocked, etc.
If you have luck only the battery died and replacing the old with a new is enough. The problem is that you need some skills changing it yourself because our z1 hasn't got a removable back cover.
Click to expand...
Click to collapse
Well, I thought about it too but how will SONY know I unlocked the bootloader as most probably motherboard is the issue here and it will have to replaced.
Though I don't feel good lying to people but IMO, voiding warranty because of root is not a good policy and especially if the phone the company sold is bricked due to THEIR common bug, it is just pure evil.
For months I was telling everyone to wait for xperia Z5 for their next upgrade but I've changed my mind now, AFTER facing many problems with Z1 like low speakers sound, VERY poor wifi range, how could I forget the lollipop update, man it was very slow/laggy, lollipop update was the reason I rooted my xperia z1 and now THIS bug (so many guys has lost their phones to this bug, just read sony forums)
markakash said:
@GravityDead u may follow this link and try the steps mentioned here: http://forum.xda-developers.com/showthread.php?t=1849170
If that didnt work then u may try this link: http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Good luck Bro!
Click to expand...
Click to collapse
thanks man, I've bookmarked them for future reference.
UPDATE: my phone booted up today but I don't know how and that's what scares me 'cause I read it somewhere on the sony forums that this bug comes back eventually.
I woke up, switched on and connected the charger disappointingly but to my amazement phones' LED lit up (Red LED for showing low battery), I left it to get charged up for a reasonable time. and now it's working just like yesterday now
Though I've learned a very good lesson that
never to buy phones on launch but to wait to read reviews on forums.
thanks again guys, I will post back if something goes wrong again and if you need to ask something then please go ahead
Hi!
This is the first time I post a thread on xda since I had my Xperia Arc .. good times. Then I switched to Windows Phone and a couple months ago I returned to android with a Moto X 2nd gen.
I never installed a mod, rom or even unlocked the bootloader or root my phone, I really wanted only use my phone for my regular tasks.
The problem is today I was going to check my messages and the screen won't turn on, I supposed it was the battery so I pluged my phone to the power source and.. nothing.. It's just dead :/
I connected my phone to my PC to see if I can see any signal of life and I've noticed when I plug my phone to my PC and press and hold the power button a green led turns on for 2 -3 seconds and then dies again .. My PC can't detect the phone , I just get "unknown device"...
The phone was new or used before you?
If it was used perhaps you need a new battery. If it was new you must go at motorola service center to fix it by your warranty.
Jim_C30 said:
The phone was new or used before you?
If it was used perhaps you need a new battery. If it was new you must go at motorola service center to fix it by your warranty.
Click to expand...
Click to collapse
It was new, I ordered from the page .. that's sad
Have you already tried volume down + power?
Flipz77 said:
Have you already tried volume down + power?
Click to expand...
Click to collapse
yep, I've tried many combinations like press and hold volume down then press and hold both volume - and power for 2 minutes .. and nothing..
Is just strange, no idea why this happened !!! ..
Tomorrow I will call support and see what happens
Plug it into the charger overnight. Check it in the morning. Try holding out Vol +, Vol - and power for 30 sends.
So is support willing to help you? When my Moto X suddenly died they didn't want to help me...
Support..?? Really.. I will tell u something... I wanted to contact them through email and checked web site, so I could see contact us options - but when I checked that the link was broken... So I decided to get to service support chat.. But u know what they said..?. They can't five me their e mail....what..?. Seriously?? They can't give something that I can't access but it's publicly posted... They are waste.. Don't waste ur time on them..
Sent from my XT1092 using XDA-Developers mobile app
Sorry to hear about your phone.
I'd be interested to hear the outcome of this..
The same thing happened to my MotoX. After months of discussions with Moto Support I ended up getting the phone repaired "outside of warranty". They refused to cover the repair because I had moved to Australia. (ridiculous for a 'global' company.)
After paying a huge amount to repair the phone, I booted it up and realized they had replaced the 'main board' with the wrong part. My 32gb phone was now a 16gb model.. The repair cost me more than a brand new 16gb model off the shelf!
I've tried to contact moto to resolve the issue but have had radio silence from motorola and the repair center ever since.
I hope you have better luck, and more free time to keep hounding them than I did...