Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
olik79 said:
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
Click to expand...
Click to collapse
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
levone1 said:
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
Click to expand...
Click to collapse
Thank you SO much! I wasn't really able to boot using power and volume up, BUT after your encouraging words and the idea that I might just be using wrong keys, I researched some more and found out about this little red button within the sim card slot! It allowed me to reboot, get into fastboot, install recovery and cyanogenmod afterwards! I'm happy again
Related
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
So, been rooting, fiddling, installing ROMs, etc for a couple years. By no means am I an expert, I can just do research and read. I've had bootloops, and crashes, and all the same issues everyone else on this forum has had over the course of learning this stuff. So, when my phone wouldn't boot up even into recovery, I didn't sweat it at first. But, well, I've tried everything and nothing works. I can't boot, I can't charge it. Nothing works.
So, here's the breakdown.
Lt28i
Was running stock
Phone was rooted
CWM recovery
Bootloader is unlockable via regular means.
Hated it since a recent update. Phone was slow and i wanted JB. So i started the process.
I installed a new kernel, was in the process of installing a new ROM, but the instructions said to delete /system. I did.
From that point on, phone would not boot. Would not charge and would not get into recovery.
I can't connect via adb/fastboot.
It's a brick sitting on my desk. I've since gotten an HTC one, which IS AWESOME guys, but I hate having a perfectly fine piece of hardware just sitting on my desk collecting dust, (not to mention hate admitting defeat) so I'd like to get it working and either give it to a friend or sell it. Can anyone help.
Symptoms. As soon as i plug it in, the red light goes on. After about 15 minutes, the sony logo comes on with the red light off for just under 10 mins or so, then black screen and red light on. So, it's in a kernel boot-loop of sorts, but never gets past it and therefore doesn't charge. I've left it unattanded for over a week to drain the battery, hoping it'll reset, but no change. Immediately the red light goes on when plugged in. No way to boot into recovery. No way to connect to fastboot.
Any ideas?
Have tried the following:
http://forum.xda-developers.com/showthread.php?t=1849170
and a bunch of others. None has worked.
So your bootloader is locked?
You can't flash any custom kernel on locked bl.
First, connect your phone to a wall charger for whole night.
Then use Update Service or PCC to repair it.
Remember: do not connect your phone to PC until it ask you to do so.
Press vol down when connecting to PC.
cities516 said:
So your bootloader is locked?
You can't flash any custom kernel on locked bl.
First, connect your phone to a wall charger for whole night.
Then use Update Service or PCC to repair it.
Remember: do not connect your phone to PC until it ask you to do so.
Press vol down when connecting to PC.
Click to expand...
Click to collapse
sorry, my mistake. The plan was to flash a kernel, but i never got around to it. I had looked into unlocking the bootloader, but wanted to see if I could get any good JB roms first. Sorry about that false info.
I have both let the phone die completely, or so I think, unless it keeps its charge for over a week and charged it for about 40 hours. Like I said, it does the bootloader boot loop which seems to keep it from charging. I never get to the screen where it shows the charging icon, so I can't tell, but I've definitely left it on a charger (not PC) for at least a day and a half. No go.No amount of pressing vol down works.
Does flashtool work on bricked phones?
lewis021 said:
Does flashtool work on bricked phones?
Click to expand...
Click to collapse
Yes, Unless your device is hard bricked meaning it wont show any led or wont do anything basically
AndroidHoneyComb said:
Yes, Unless your device is hard bricked meaning it wont show any led or wont do anything basically
Click to expand...
Click to collapse
Well, that's why I'm hopeful, cause the led does light up immediately on plugin. And the Sony logo screen shows up for a few minutes, then disappears. I have tried flashtool, but it won't connect. No go.
vijn said:
Well, that's why I'm hopeful, cause the led does light up immediately on plugin. And the Sony logo screen shows up for a few minutes, then disappears. I have tried flashtool, but it won't connect. No go.
Click to expand...
Click to collapse
Your either using flash tool wrong (Hold the down button while plugging in the usb to go in flashmode and then flash the ftf quick before flashmode restarts of being idle) The Sony logo is still there so there should be no reason to send it in until all possible repair techniques have been used
AndroidHoneyComb said:
Your either using flash tool wrong (Hold the down button while plugging in the usb to go in flashmode and then flash the ftf quick before flashmode restarts of being idle) The Sony logo is still there so there should be no reason to send it in until all possible repair techniques have been used
Click to expand...
Click to collapse
Well, I've used flashtool a whole bunch of times. Sure from time to time there's an issue with it, but I've tried different versions and none has been successful. And I'm very familiar with the "getting into flashmode" process. And yes, I would agree with you that if the sony logo shows up, then there's gotta be a way, but I'm telling you, it's just not happening. I've tried 100 times.
vijn said:
Well, I've used flashtool a whole bunch of times. Sure from time to time there's an issue with it, but I've tried different versions and none has been successful. And I'm very familiar with the "getting into flashmode" process. And yes, I would agree with you that if the sony logo shows up, then there's gotta be a way, but I'm telling you, it's just not happening. I've tried 100 times.
Click to expand...
Click to collapse
Does Flashtool show anything after you connect your phone to PC with flashmode?
"Drivers have to be installed" or somethimg?
vijn said:
Well, I've used flashtool a whole bunch of times. Sure from time to time there's an issue with it, but I've tried different versions and none has been successful. And I'm very familiar with the "getting into flashmode" process. And yes, I would agree with you that if the sony logo shows up, then there's gotta be a way, but I'm telling you, it's just not happening. I've tried 100 times.
Click to expand...
Click to collapse
If you can see the Sony Logo then it has to work, Hold the down key, while plugging it in and it will show a green led... I had the same problem as you (cause I do things that sony may not like, on my phone)
1. Make sure you have the correct drivers installed.
2. Turn your phone off and unplug USB cord.
3. Hold the VOLUME DOWN button while inserting the USB cord.
4. You should see your small notification light in the top right of the phone turn green.
AndroidHoneyComb said:
If you can see the Sony Logo then it has to work, Hold the down key, while plugging it in and it will show a green led... I had the same problem as you (cause I do things that sony may not like, on my phone)
1. Make sure you have the correct drivers installed.
2. Turn your phone off and unplug USB cord.
3. Hold the VOLUME DOWN button while inserting the USB cord.
4. You should see your small notification light in the top right of the phone turn green.
Click to expand...
Click to collapse
Ya, first of all. I can neither turn the phone on or off. I have no control of it. It "turns on" when it wants and off when it wants. But when i say turns on, it only turn onto the sony logo screen after about 20 mins of being plugged in, when I guess the charge is just enough to allow it to start the boot process. Then the sony logo screen turns on, until that tiny charge dies and the phone turns off and the red LED comes on. Process repeats over and over again. I even put a rubber band on the phone to keep the volume down button pressed so that when the charge does reach the right level for the boot process that the vol down button will trigger recovery, but no deal. If this is the only way to get this thing working, is what you've recommended above, then phone is completely bricked, cause the phone has been like this for 2 weeks and nothing has worked. I know i have the drivers, cause up until this issue, flashtool worked fine. But the PC doesn't even recognize that there's a device plugged in at all now, cause the phone never boots. So, it's like plugging in a usb HDD that is off. I didn't really expect anyone to have a solution, cause i've done extensive research and tried almost everything I've read that seemed relevant, but I still had hope. I suspect the only way to fix it is to open it and connect directly to the mobo in some other way, but i don't have the tools or resources for that. Not even sure I can send it in to be repaired cause it's rooted. Unless someone has a eureka solution, my only option is to send it in to a 3rd party repair guy. Any other thoughts?
The most important thing is: what have you done to your phone before?
Flash something or edit something?
To turn off your phone, long press power + vol up until 3 vibrations.
Then connect your phone to a wallcharger for whole night.
(Do not use PC cable... It won't charge much...)
Then flash stock ftf via Flashtool.
Sent from my LT26i using xda app-developers app
Just read my first 2 posts in the recovery thread sticky'd in the general section.
Then reinstall ALL drivers available in flashtool.
Then use the rubber band trick from my thread. Make sure that the rubber band pushes the button in.
Sit back and wait ,believe me this is the hardest step.
From my Xperia LT28at ION
ToledoJab said:
Then use the rubber band trick from my thread. Make sure that the rubber band pushes the button in.
Sit back and wait ,believe me this is the hardest step.
Click to expand...
Click to collapse
I laughed at the method simplicity, and got amazed on how effective is it.
So when you connect the phone to your PC while holding the volume down key...no green light, and its not recognized by your PC at all, right? Assuming you're using windows; does windows try to install any drivers or anything? Are you prompted in any way that a device has been connected?
and did you try the above mentioned? Hold UP and power button for like 10 seconds...you'll feel it vibrate once...then a few seconds later it should vibrate 3 times...I bricked my phone to some degree Sunday...only I had no response whatsoever...no led while charging, or otherwise...and literally no response from anything...until i tried that vibrate 3 times thing...and it booted right up after...
NO GO!
Well, I've tried it all. @ToledoJab I've read and reread that original post a bunch of times. followed all instructions, in fact, I had read that post many times before even posting in this forum with no luck, but I thought I'd be patient and try again, Used the rubber band technique. Nothing. Seems, when the rubber band is used, the phone doesn't even start the boot process, meaning never shows the sony logo screen.
@jtr what no one seems to understand is, there is absolutely no response to using the power button to turn this on or off. No vibrate, nothing. There are only 2 states. 1. When plugged into wall or PC, LED is red and after 20 mins Sony logo shows up if the vol down button isn't pressed. 2. When not plugged in no led.
Flashtool has been open for 2 days, phone has been plugged in, with rubber band. Drivers installed. Phone is never recognized because it never turns on. it's in perpetual red light on mode.
I don't know guys. I'd say this is an official brick. Not sure there's any way to fix this without opening it up. Still open to any ideas, but please read what I've posted because all the recommendations so far have been things I've already said I've tried, and numerous times. I can't imagine there's anything else to try, but thought I'd update you guys nonetheless.
cool, i understand.
If the volume down key is preventing it from going into that boot loop, though...it seems to be responding to physical input to some degree...
Have you tried any of this without a sim card? I know that sounds trivial, but after a full week of messing with mine a fresh sim-less start knocked out several bugs...and i hadn't read much of that on xda, but the AT&T return directions suggested a without sim boot up as the first thing to do? and at the time, i too, was dealing with some sort of varying degree of brick.
There are also varying ways to drain a permanent phone battery...i wouldn't say thats the best way to go about this, but a friend of mine has a screwed up car charger that does exactly this...which he's kept to bring his samsung nexus out of hard bricks multiple times...i'd say that's definitely a last resort though...the stuff you'd need would only be a couple bucks at radio shack i'd imagine haha.
If you get the Sony screen you should get in to flash mode, and I say should.
With the phone plugged in to PC with flashtool ready to flash, try to do a one vibration reset at Sony screen then immediately press and hold volume down.
Sent from my LT28i using xda app-developers app
Hi folks,
first post but an important one. Important enough to join and hopefully get some answers.
My LTE Nexus 7 (running 5.0.2) bricked last night. It got stuck on the Google screen and I had no way to unlock the bootloader to flash a different version of the OS. SO this morning thinking I had nothing to lose I removed the back panel with the intention of tearing the thing down. Then it hit me. The common theory seems to be that it's the way the bootloader is not mounting the storage. So as the device never completely powers off what would happen if I cut the power manually. Hopefully a hard reset. So I detached the battery cable from the board and left it alone for a few moments. After popping the kettle on I returned, replaced the cable and tried turning on my Nexus. Lo and behold it works!
I have an unbricked device.
Which is great an all, but I have the proper tools and knowhow to delve into the hardware. More importantly though I'm trying to find out why that might have worked.
Any thoughts?
Has anyone else tried this as a solution to unbrick their device? Did it work?
There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button
Gorgtech said:
There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button
Click to expand...
Click to collapse
But surely that's not the same as disconnecting the battery?
Trev
It´s not the same but once you´re in a "boot loop", you have no chance of eg. entering the recovery. This is why you need a way to shut down the device first.
But in case even this "forced shut down" doesn´t help and you´re out of warranty, maybe it´s not the worst idea to open the device anyway since you´ve got nothing else to lose
Hey guys
I was super happy with my Australian Telstra M9 until an hour ago. I plugged it with 3% of battery in for charging and turned it off to speed the process up. When it was off the charging icon showed up just as usual. After a few hours I came back, unplugged the phone and it flashed 100% for a second. After that - nothing! It just won't turn on! I pressed every button and every possible combination of those. I plugged it back in for a bit and connected it to my laptop. But it's not even recognized. I googled for a bit but found no solution. I rooted the phone a couple of weeks ago but didn't do anything like that today. No updates, no new apps only some WhatsApp and 9gag.
What do you reckon? Is it bricked? Will I get a replacement and how long will that take? I have to leave Australia in 9 days so I'm quite on a schedule. -.-
Does anyone have any advice?!
Cheers Max
Edit: is there a chance to recover the data? I'm traveling and forgot to back anything up. Some of the data is quite important. And do you think I'll get into trouble because of the root?
No clue, try a different charger maybe.
I tried three different charges plus my laptop. Neither of them worked. Is there gonna be any way to rescue the data from the internal storage or will the just wipe it after they repaired it?
I would try holding the power and volume up button for at least 2-3 minutes. If it does come on, as soon as you feel it vibrate, move your finger down to the volume down button and hold it until you get into download mode. Then boot to the bootloader and then recovery and restore a nandroid.
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
MrDuvet said:
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
Click to expand...
Click to collapse
Hold power + volume up button will work in most cases.
TBH, don't really know what happened to you. Did you flash custom rom, recovery? or only root?
I didn't know that. I only new power + vol down. And I didn't hold it for a minute. I did nothing but flashing TWRP and root the stock rom. I didn't even change much with the root and only use it for titanium backup and adaway. That's why I was so baffled, when the phone suddenly "broke" because I didn't do anything unusual to it.
MrDuvet said:
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
Click to expand...
Click to collapse
I'm glad you got your phone up and running. I know exactly how you feel, I had the same thing happen to me. I thought mine died when the screen went black after I flashed a kernel. Its always scary when the phone won't respond.
The phone was likely frozen. Power + Volume Up forces the phone to reboot after being held for a while. It could be some weird software issue due to the rooting and TWRP, but no one can say for sure. It might happen again but now you know how to reboot it If you really want to avoid the possibility of problems, you probably want to run stock and not root the phone or change bootloader... but what's the fun in that?
You're right no risk no fun. I'm actually waiting for cm so running stock is no option anyway
Thanks for saving me lots of headaches
FYI - I thought I had bricked mine as well - no flashing activity in a couple of weeks, all good chargers. Even made an appointment for repair.
Read the "hold power and vol up for a minute or two," and was like... nooooo... 10 seconds is the max you'd do that for... but tried it... bam, worked like a charm at ~45 seconds for me. Got into HTC FTM mode in which no option worked (reboot to bootloader, simlock, couple of others seemed to just pop immediately back to this weird non-download menu). Holding power for a while after that reset the device. Working now.
Thanks for the thread... been doing this for five years and this is the first no-charge no-response event I've had
lyall29 said:
I would try holding the power and volume up button for at least 2-3 minutes. If it does come on, as soon as you feel it vibrate, move your finger down to the volume down button and hold it until you get into download mode. Then boot to the bootloader and then recovery and restore a nandroid.
Click to expand...
Click to collapse
Worked like a champ, thanks a ton! :good:
Hi All,
About a week ago my M9 powered down while on charge and then wouldn't power on again. No response at all from the standard power button but only holding it for a few seconds at a time.
I knew the buttons to hold to enter bootloader and after several tries it powered on again.... It then ran for a couple of days with no issues.
Then a couple of days later had to power off the phone on a flight - same issue - wouldn't power on - dead.
It took several attempts to bring it back to life. I'm now in a position when every time I power off the phone it just doesn't want to come back on? Thought that it may have been a custom rom issue or a kernel issue - have tried changing both (painful experience by the way - having to wait for the phone to decide when its ready to wake up "when it feels like it after each new installation) but the problem is still there.
I have also found that entering bootloader using the power button and volume button isn't the only solution to "waking up" the phone. Just holding the power button for 10-60 seconds has the same effect - but it sometimes takes several attempts over several minutes - its very random.
Does anyone else have this recurring problem every time they power off? Does anyone on "stock" have the problem?
I'm starting to think that maybe its hardware rather than a software issue?
Try turning off the phone, plugging in the charger, and holding all three buttons for two minutes.
HTC has recommended this as a fix for battery issues like the slow charging bug. Apparently it clears all the battery settings and recalibrates it. The phone will reboot repeatedly while you're doing this, but that's normal. Keep holding the buttons.
I have seen HTC phones do this in the past when the battery system gets confused.
Bricked M9
iElvis said:
Try turning off the phone, plugging in the charger, and holding all three buttons for two minutes.
HTC has recommended this as a fix for battery issues like the slow charging bug. Apparently it clears all the battery settings and recalibrates it. The phone will reboot repeatedly while you're doing this, but that's normal. Keep holding the buttons.
I have seen HTC phones do this in the past when the battery system gets confused.
Click to expand...
Click to collapse
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
aairlinepilot said:
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
Click to expand...
Click to collapse
Best to run a logger like BetterBatteryStatsor GSam Battery Monitor to find out what is draining it
sausje85 said:
Best to run a logger like BetterBatteryStatsor GSam Battery Monitor to find out what is draining it
Click to expand...
Click to collapse
I am unaware of any way to do this if the phone wont turn on - it's dead.
aairlinepilot said:
I am unaware of any way to do this if the phone wont turn on - it's dead.
Click to expand...
Click to collapse
Ah you cannot even get it charged anymore?
I know HTC phones had an issue that when they are completely drained, they seem to be dead, even not charging or anything. Yet if you keep them in the charger, eventually they would show as charging and being able to turn on again.
aairlinepilot said:
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
Click to expand...
Click to collapse
Leave it in connected to the stock charger overnight and see if that helps. If not, you might have a hardware fault and need to return it for warranty service.
I too thank you most profusely!!
I have a Nokia 6.1 TA-1043. I have not unlocked the bootloader, and it runs the default operating system (Android One, probably Nokia flavoured). It has gotten slower over the years, and it had a period where it crashed every now and then (sudden reboot). Anyway , some days ago I decided to reboot the phone because it was slow, and it instantly shut off. After waiting probably 20 seconds without response, I decided to hold the power button down to force it. I don't remember exactly what I did, but after trying to again hold the button down to turn it on again, it vibrated as usual but the screen remained black. I then most likely tried holding volume + and power to force another reboot, unsuccessfully. I then tried holding volume - and power to enter download mode. It might have vibrated, or I might have touched the cable making me think it vibrated, but nothing happened. I pressed some random buttons after I think.
Now, the phone does seem to charge. It gets warm when I plug in the charger. I've searched for hours on different forums, and some people say that their phone was magically resurrected after the battery went completely flat after few days. I have tried plugging the phone a bit and testing every button combination (including volume +, volume - and power at the same time) for a few days now. It's dead.
The phone is also seemingly not recognised at all on my windows 10 PC. Haven't tried on Linux.
I have a few theories:
1. The phone simply hard bricked itself due to some hardware failure.
2. I bricked the phone by (blindly due to screen being blank) entering recovery mode and unknowingly factory resetting the phone and shutting it off mid process.
3. The battery is messed up? Some suggest deconnecting the battery. It would require the use of a heat gun to even open the phone though.
I've seen some people suggest entering EDL-mode either by shorting some pins or using a modified USB-cable. However, that would either require opening a phone that isn't supposed to be opened easily, or plugging a modified USB-cable into my computer, nether of which seem safe. I've also seen people mention that whatever needs to be flashed in EDL-mode must be signed by Nokia, which I can't do obviously haha.
It's probably time to move on right? Has someone managed to get a phone in that state to work again?
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
alprtewwqfr said:
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
Click to expand...
Click to collapse
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situation?
speedrocket2110 said:
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situations
Click to expand...
Click to collapse
I don't know because I'm not in that situation, but I had a similar one but only boot to download mode.