Hard bricked my M8 (help appreciated) - One (M8) Q&A, Help & Troubleshooting

Hello,
Ill tell you a short story how I got this phone bricked.
So i got a OTA update to 6.0.1 (as I remember) and the phone started acting crazy. "system UI stopped working" message showed up once an hour and after that phone reboots. I got tired of my phone rebooting all the time so Ive decided to root it and install a custom ROM. Ive successfully rooted it, instelled TWRP and flashed a HTC M8 google play eddition rom on my phone. Everything was smooth except that it didnt recognize the SIM card and (again) it kept rebooting once an hour out of nowhere (this time the restart was immediate. No "system UI has stopped" message appeared). So i flashed another rom.. (silly me). I flashed a M8 HD Revolution rom because it was the most popular one and I thought it will fix all my problems. I flashed it successfully, the phone booted, it started optimizing apps and then shut down. I tried to turn it on again, it started optimizing apps again and after it finished optimizing ir shut down again. And that was the last time I saw my phone atleast trying to boot.
After all that I tried all the button combinations (vol up + power, vol down + power, vol up + vol down + power), Ive red alot and tried the same combinations with different timing. IT WONT BOOT INTO BOOTLOADER. adb and fastboot commands does not work also. When I connect my phone to a pc i was able to hear a windows connection sound, after 5-10 secs i hear a disconnect sound, after 5 secs it connects again, and disconects again ang again and again.... I managed to screen shot my device manager screen and saw Qualcomm HS-USB QDLoader 9008 in the device list appearing and disappearing every 10 secs. I googled it and found some info that I might have hard bricked my htc. I didnt have much time at that moment to dive into the ocean of information and decided to leave my phone connected to a charger overnight. NOW my phone is dead (100%). No flashing lights, no *connected/disconnected to a pc* sound, the screen is black, it wont turn on - no signs of life..
Is there anything that I can do? (the warranty is voided)
Could it be that the battery was damaged and it was the issue of my phone restarting all the time?
Any help will be much appreciated
*dont mind my english*

Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!

Paulius Sirv said:
Hello,
Ill tell you a short story how I got this phone bricked.
So i got a OTA update to 6.0.1 (as I remember) and the phone started acting crazy. "system UI stopped working" message showed up once an hour and after that phone reboots. I got tired of my phone rebooting all the time so Ive decided to root it and install a custom ROM. Ive successfully rooted it, instelled TWRP and flashed a HTC M8 google play eddition rom on my phone. Everything was smooth except that it didnt recognize the SIM card and (again) it kept rebooting once an hour out of nowhere (this time the restart was immediate. No "system UI has stopped" message appeared). So i flashed another rom.. (silly me). I flashed a M8 HD Revolution rom because it was the most popular one and I thought it will fix all my problems. I flashed it successfully, the phone booted, it started optimizing apps and then shut down. I tried to turn it on again, it started optimizing apps again and after it finished optimizing ir shut down again. And that was the last time I saw my phone atleast trying to boot.
After all that I tried all the button combinations (vol up + power, vol down + power, vol up + vol down + power), Ive red alot and tried the same combinations with different timing. IT WONT BOOT INTO BOOTLOADER. adb and fastboot commands does not work also. When I connect my phone to a pc i was able to hear a windows connection sound, after 5-10 secs i hear a disconnect sound, after 5 secs it connects again, and disconects again ang again and again.... I managed to screen shot my device manager screen and saw Qualcomm HS-USB QDLoader 9008 in the device list appearing and disappearing every 10 secs. I googled it and found some info that I might have hard bricked my htc. I didnt have much time at that moment to dive into the ocean of information and decided to leave my phone connected to a charger overnight. NOW my phone is dead (100%). No flashing lights, no *connected/disconnected to a pc* sound, the screen is black, it wont turn on - no signs of life..
Is there anything that I can do? (the warranty is voided)
Could it be that the battery was damaged and it was the issue of my phone restarting all the time?
Any help will be much appreciated
*dont mind my english*
Click to expand...
Click to collapse
Did u wipe the system file and data before flashing new ROM?

redpoint73 said:
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Click to expand...
Click to collapse
Ive tried your technique, few times actully. Phone does not want to show any indication of life. I might have flashed the rom on low battery I just found out that the cable I was using to flash roms ir damaged and does not function properly. Now Im using a new power cable to charge the device but still, no signs of life.
Thank you very much for helping

justinchao740 said:
Did u wipe the system file and data before flashing new ROM?
Click to expand...
Click to collapse
Revolution HD has a aroma installer, I wiped it during instalation process

Same problem I had my phone not booting to bootloader ,also when I connect charger nothing happen after that i do keep pressing valume up+ power buttom untill my screen blink after blink u have to keep pressing both button power+volume up for 12 seconds and released both Button's and Press valum dawn and successfully entered to bootloader hope this will help you also
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Paulius Sirv said:
Revolution HD has a aroma installer, I wiped it during instalation process
Click to expand...
Click to collapse
Keep pressing volume up and power dont lose hope volume up+power only way to restart your device sorry for bad English hope u understand

sayad1 said:
Same problem I had my phone not booting to bootloader ,also when I connect charger nothing happen after that i do keep pressing valume up+ power buttom untill my screen blink after blink u have to keep pressing both button power+volume up for 12 seconds and released both Button's and Press valum dawn and successfully entered to bootloader hope this will help you also
---------- Post added at 05:54 PM ---------- Previous post was at 05:50 PM ----------
Keep pressing volume up and power dont lose hope volume up+power only way to restart your device sorry for bad English hope u understand
Click to expand...
Click to collapse
Thank you very much, Ive heard about this method and Ill definitely try it . I just borrowed a data cable from my friend and LED light showed up (orange blinking).

Paulius Sirv said:
Thank you very much, Ive heard about this method and Ill definitely try it . I just borrowed a data cable from my friend and LED light showed up (orange blinking).
Click to expand...
Click to collapse
Wc reply if this method work for you

redpoint73 said:
Are you s-on or off? Its very hard to brick this device flashing ROMs with s-on.
Try leaving the phone on charger for a few hours, then hold power+vol up for a minute or so. Most folks don't realize you have to hold the buttons for so long in this "no boot" condition, and start to freak out. I've done it myself!
Click to expand...
Click to collapse
I left my phone to charge overnight and the LED light came on (Its a really good sign). At first it was flashing orange, later it was only orange and now its green, so that means that my battery was fully drained. However, I tried holdin power + vol up for atleast 3-4 minutes but nothing happened except that the LED light is not greeen nor orange anymore. If I connect my phone to a pc, in the device manager "Qualcomm HS-usb qdloader 9008" shows up for 20-30 seconds and dissapears, after few secs it reappears again and so on. I was looking for a solution for a few hours and I think I found a decent tutorial how to unbrick it but Im not able to find neccesary firmware for my phone because I dont know my CID (link: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/). Any other ideas?
BTW, thank you very much for trying to help

I've never seen these "unbricking" guides work on this device. If you can't get to at least bootloader, you are probably looking at JTAG, new motherboard, or new phone.
Really, your best bet is to keep playing with the button combos with the charger attached and unattached.

Related

[Q] Help please! 3x vibrate and amber flashing light after removing battery! (brick?)

Hey guys, I'm normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .

Dead phone in APX mode, now what ?

Hi,
I've got a HTC One x, which worked fine untill i flashed it with Cyanogenmod.
To start from the beginning.
I never liked the HTC Sense stuff to much, so i did with my HOX what ive done with all my other android phones. I unlocked it and installed Cyanogenmod. When i did that i started having stability problems, suddenly acore stoped, then gmail stoped and so on.
So i decided i wanted to try another rom, without much luck. After fidling around with it for a couple of days, it started behaving strangely.
Suddenly it could wouldnt turn on after beeing powered down, i had to leave it for days, then suddenly it would pop back on when left connected to a computer for a while.
I RUU'ed the phone, going back to HTC Sense, still giving me acore and other application errors. Then i installed a another ROM ( Jellybean ), and when i woke up one morning the phone was dead. It would not boot, not in normal mode, not into recovery, nothing. Ive tried all the tricks in the book, volum down + power, volume up&down + power, just power, just volum down and so on.
Ive been googling alot trying to figure out if the phone is beyond repair, or if there is any hope left. I noticed one day when fidling with it that when i connected to my windows 7 machine, the computer made a "USB CONNECTED sound". i looked in the device manager section, and there i see a unknown device called APX. I unplug the phone and it goes away, so i google and find that this is some low lever mode on the phone. My hopes are that this is a way of flashing some sanity back into the phone.
I found some APX drivers lying around on the net, and now it identitfies itself as "NVIDIA USB Boot-recovery driver for Mobile devices", not that this helps my in any way.
I read somewhere that you can use nvflash, but its not giving me much info.
Soooo....i have a phone which is pretty much dead, except for entering into APX mode ( the screen is black as if the phone is dead, no leds, no nothing ). Anyone have any smart ideas to how i can get the phone back to life ?
Nope. If you search this forum, the only APX advice I've seen is to drop the phone. Actually serious. (Don't do that)
Anyway, looks like you'll be returning it and hoping it gets fixed without them figuring out that you broke it.
hey do you already solve this problem ?? i solved mine by pressing volume + then plug the charger .. wait for sec. a red light will apear in your phone and it will charge.. charge it for atleast one night or for an hour. then try to boot in fastboot.. when you boot in fastboot flash RUU file or if you have a custom recovery try to flash a custom rom. ) press thanks if you helped you . )
---------- Post added at 05:11 AM ---------- Previous post was at 05:01 AM ----------
hey do you already solve this problem ?? i solved mine by pressing volume + then plug the charger .. wait for sec. a red light will apear in your phone and it will charge.. charge it for atleast one night or for an hour. then try to boot in fastboot.. when you boot in fastboot flash RUU file or if you have a custom recovery try to flash a custom rom. ) press thanks if you helped you . )
contact xmoo he might be able to help, so far all i can tell you is that your phone is dead. htc should fix it if you act stupid and say it stopped working overnight.

[Q] Zenfone 2 got into reboot loop after upgrade

Hi,
I have received new zenfone 2 and it asked for software upgrade. After that it said it is optimizing applications and eventually got into reset loop with only showing ASUS logo. I have tried to get into recovery mode pressing the power and volume up and release on vibrate... nothing happend!!!
Now it vibrates every minute or so... but it even does not turn the screen on... just vibrating every now and then...
Please, help!
Zvika
Zvika Perry said:
Hi,
I have received new zenfone 2 and it asked for software upgrade. After that it said it is optimizing applications and eventually got into reset loop with only showing ASUS logo. I have tried to get into recovery mode pressing the power and volume up and release on vibrate... nothing happend!!!
Now it vibrates every minute or so... but it even does not turn the screen on... just vibrating every now and then...
Please, help!
Zvika
Click to expand...
Click to collapse
Power off completely, then hold volume up and power to get to bootloader. Press volume down until you get to recovery and hit power button. It should reset and then a android appears. If it then says error hold power and press up volume. You should get to recovery menu that way.
Wipe cache...
Reboot and see what happens...
ultramag69 said:
Power off completely, then hold volume up and power to get to bootloader. Press volume down until you get to recovery and hit power button. It should reset and then a android appears. If it then says error hold power and press up volume. You should get to recovery menu that way.
Wipe cache...
Reboot and see what happens...
Click to expand...
Click to collapse
I'm having the same issue, but no matter what I do the error stays on and if I hold the power and press up for too long the phone turns off.
chillpillv1 said:
I'm having the same issue, but no matter what I do the error stays on and if I hold the power and press up for too long the phone turns off.
Click to expand...
Click to collapse
Try tapping up volume 3 times but remember to let go of power at roughly the same time or 10 seconds later the phone will power off...
It just do not enter this recovery mode... no matter what
ultramag69 said:
Try tapping up volume 3 times but remember to let go of power at roughly the same time or 10 seconds later the phone will power off...
Click to expand...
Click to collapse
It just do not enter this recovery mode... no matter what.
After charging it all night, and having the battery icon, I have tried it once more. Now the screen remains black and the phone just vibrate here and there every minute - unless I turn it off...
i am facing the same problem. but my phone is not opening. its behaving like dead. when i press the power button sometimes its vibrate but noting on the screen. no charging logo while charging what to do?? please help !!!!!!!!!
Yes. this is the same with my device...
Anaxious Asheque said:
i am facing the same problem. but my phone is not opening. its behaving like dead. when i press the power button sometimes its vibrate but noting on the screen. no charging logo while charging what to do?? please help !!!!!!!!!
Click to expand...
Click to collapse
No solution so far.
Im having the same problem too
For wipe cache partition and hardware reset procedure, please see the following: http://www.asus.com/us/support/FAQ/1011956/
If possible, please send a private message to email below with case # N150638445 in the subject line. Please provide your serial number & if possible your build number (once you are able to boot) under Apps/Settings/About/Software information/Build number.
We would like to gather as much info as possible to help resolve any issues with ASUS Zenfone 2.
Sincerely,
Frank
ASUS_USA
[email protected]
Did anyone ever resolve this issue?
Mine is the same and won't boot up, just vibrates once and does nothing....
i resolved simply reflashing the old pre rooted firmware 2.19.40.18 and installing ota 2.19.40.20 with adb sideload after complete unroot with supersu.i forgot to uninstall xposed and this was the reason of my botloop after update to 2.19.40.20.luckily i had twrp so before reflashing i backupped all my stuff.that's it.you need to reflash droidboot,recovery,boot and system imgs from bootloader with the usually way.no other way out.hope you installed a custom recovery before loop,so you can backup
CenereZar said:
i resolved simply reflashing the old pre rooted firmware 2.19.40.18 and installing ota 2.19.40.20 with adb sideload after complete unroot with supersu.i forgot to uninstall xposed and this was the reason of my botloop after update to 2.19.40.20.luckily i had twrp so before reflashing i backupped all my stuff.that's it.you need to reflash droidboot,recovery,boot and system imgs from bootloader with the usually way.no other way out.hope you installed a custom recovery before loop,so you can backup
Click to expand...
Click to collapse
how did you do it ?
I have the same problem
---------- Post added at 12:33 AM ---------- Previous post was at 12:07 AM ----------
my device is in error screen, and with the dead robot.
Hi guys, please help, maybe some of you could do that for me... Problem is strange and I just did not find solution jet... So, I just can not power down my ZE551ML completly. Device is trying somehow to boot up, getting some kind of loop. First of all, phone came to me totaly dead - I have to plug it in to charger for 3-4 hours to ligh up notification led... After that it turned on normally. After first boot and setting things up, updates showed up. So I did update - for 4 times, OTA. It looks ok (now I have 2.20.40.90 clean, I mean no root or unlocked BL). But strange comes when I want to turn it off (power down) - device is shutting down, screean is going black and... bum! - the battery icon is showing up: emty for the very first few seconds, then it changeing to green (showing actually power state, I mean accu capacity), then device reboot itself and whole process starts over and over again... I can not stop it. Well, I think if the battery would be full, that could completly discharge it - couse is unstopable... I found, that when I press vol- when the battery is green, phone shuts off its screen, but after 20 seconds the process begins over again... i can boot it normally by pressing vol+ and power - it leads me to the bootloader manu, then boot normally - done. but it is very annoing... beside that phone is ok. Can someone help? BTW - I did factory reset from stock recovery, but it did not help...
hillvieira said:
how did you do it ?
I have the same problem
---------- Post added at 12:33 AM ---------- Previous post was at 12:07 AM ----------
my device is in error screen, and with the dead robot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I had the same problem. My solution was to unplug the usb charger. After that, the update was successfully.
on me Z007 I did a factory reset because my phone would not start and when it did it kept giving me messages about unfortunately this stopped and that stopped BBM, Zenui, google play store etc. Once i did the factory reset the phone worked again but I had no data so I thought I would just restart. Now all I get is ASUS and the spinning wheel. any suggestions??
Hello, I own model Asus Zenfone 2 laser 5.5 ( ZE550KL ) I have also same problem, phone keeps on rebooting....... Showing Asus logo and then vibrates and again start rebooting
I have installed asus firmware from SD card from recovery mode which was successfully installed .... did every thing after pressing volume and power button and even performed necessary actions by doing fastbood mode.
but phone is on same condition.... showed every where.. even service center people raised there hands
Kindly help me to recover my phone back.

Probably hard bricked - not sure

Hi,
after running a rooted Kitkat for a year or so I thought I wanted to install CM12.1. So I wiped and flashed via CWM Recovery and also flashed some GApps (probably the wrong one). After flashing (with confirmation that everything was successful), I wanted to reboot but after clicking on reboot, the screen just went black. Waiting for 5 mins, nothing changed.
Pushing the Power-On button lets the phone vibrate once, that's it. Pushing Vol+ or Vol- together with Power-On does not change anything. Connecting a charger to the phone, let the red LED flash once.
What can I do to revive my phone....?
Suggestions or hints are greatly appreciated
aalemann said:
Hi,
after running a rooted Kitkat for a year or so I thought I wanted to install CM12.1. So I wiped and flashed via CWM Recovery and also flashed some GApps (probably the wrong one). After flashing (with confirmation that everything was successful), I wanted to reboot but after clicking on reboot, the screen just went black. Waiting for 5 mins, nothing changed.
Pushing the Power-On button lets the phone vibrate once, that's it. Pushing Vol+ or Vol- together with Power-On does not change anything. Connecting a charger to the phone, let the red LED flash once.
What can I do to revive my phone....?
Suggestions or hints are greatly appreciated
Click to expand...
Click to collapse
Try holding power and volume up together for 8-10 seconds, just to make Sir it's totally powered off, then connect the charger and see if it starts charging. Older batteries don't do well in this phone. It wseems to me you might have had the sudden-battety-drain phenomenon when you flashed.
levone1 said:
Try holding power and volume up together for 8-10 seconds, just to make Sir it's totally powered off, then connect the charger and see if it starts charging. Older batteries don't do well in this phone. It wseems to me you might have had the sudden-battety-drain phenomenon when you flashed.
Click to expand...
Click to collapse
Thanks, that seemed to have work. I am now a happy user of CM12.1 on my Xperia Z1 Compact

NOOB: hard bricked op3, volume up button hasn't been working

First off, I did do a search, but as far as I can tell no one has had this problem so far.
This is all after modding using a tool kit: (i can't include the url but it is the toolkit by neisor on the oneplus forums)
tldr: phone stuck in bootloop, computer wont recognize the phone, maybe because it keeps shutting off and then booting to the 1+ logo, then shutting off again, would drivers help? what can I do about the volume up button?
So for a while my volume up button hasn't been working, and the mega unbrick post shows that I need to hold the volume up button for at least 25 seconds and while holding, plug my phone in. I have also seen some posts that say the volume up button could be a software issue, and the button itself could be working, and it is just not registering, as well as someone saying that you could take the back off and manually press the button, instead of using the bar on the outside of the phone (would this work?). I have gotten the button to work in the past by pressing the volume up button to the side instead of straight in, but I haven't been able to get it to work since my phone got bricked.
Another issue: my phone is stuck in a boot loop, I can't access fastboot, and I'm unsure of recovery because my volume up button is not working. would it be worth it to deal with the constant vibrating to try to get it to recovery?
I have been able to shut the phone off by holding the power button for something like a minute and a half, though.
This is my first post, and if I have broken any rules I am very sorry, but I need help and am tired of not having a phone.
Thank you everyone,
Mark
Edit: this is what I did to root the phone:
1. download the toolkit
2. unlock bootloader (when fastbooting the phone said unlocked at the bottom, and a message about not being secure showed every time I rebooted the phone)
3. flashed twrp (no issues, still booted, recovery went to twrp. for some reason I had to flash multiple times as every now and then recovery would revert to stock op, although I did make a backup through twrp)
4. send supersu zip file to phone, install using twrp (phone would not boot, op logo stayed on phone for 2 hrs + until I rebooted to fastboot and tried to reinstall the backup I made, still nothing)
5. Try magisk (still stuck on op logo)
6. try to go back to stock, accidentally lock bootloader (now the phone is stuck in bootloop, don't know what to do from here as I cant get to fastboot and am unsure of recovery's accessibility.)
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Thanks
150208 said:
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
Click to expand...
Click to collapse
thanks for the correction, I will keep trying the volume buttons, if it doesn't work by the end of today I will search for a new volume button.
Thanks again,
mark
Ouch
badabdba said:
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Click to expand...
Click to collapse
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
MarkTheFur said:
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
Click to expand...
Click to collapse
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
MarkTheFur said:
... what can I do about the volume up button?
Click to expand...
Click to collapse
Can you boot into recovery by pressing power+volume down buttons?
Update: Got phone to show on computer as qualcomm under coms and ports
So last night I went ahead and held volume up for about 20 seconds, then plugged the phone in, keeping the volume up button pressed the entire time. my phone stopped bootlooping and showed up as a qualcom device! So I have downloaded the new driver the stock os, and am going to proceed to try to unbrick my phone.
Wish me luck,
Mark
Yes, I did, and its working so far
tnsmani said:
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
Click to expand...
Click to collapse
I still need to turn off the signed drivers features ( a huge bi*ch, I have to use another computer to contact microsoft or something to get my computer to load when I turn off safe boot or whatever its called), but once I do that I can install the driver and attempt to reinstall the stock os. Hopefully everything will go well.
Thank you,
Mark
Not as far as I know
rk2612 said:
Can you boot into recovery by pressing power+volume down buttons?
Click to expand...
Click to collapse
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
MarkTheFur said:
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
Click to expand...
Click to collapse
Glad to hear that there is some progress. Best of luck and keep us informed.

Categories

Resources