Related
hello, my htc evo was working fine, but after flashing some roms i got it missed up
to start off, my phone turns on stays on for exactly 2 mins and 15 secs, then screen turns off, phone vibrates 5 times the green led light start flashing then nothing, the only way to to turn the phone back again is to pull the battery out
now when i connect my phone to the computer, sd card isnt detected however i manged to fix it by fowling this guide
http://forum.xda-developers.com/showthread.php?t=695243
now whenver i connect my phone to the computer it asks for qualcomm drivers thats what i see under device manager 3 yellow arrows with qualcomm something something, the guide above mentions how to fix it, but i need root and i cant root the phone atm because i cant get ADB working, phone displays qualcomm drivers
i was rooted with CWM recovery, but atm i have updated my phone to the latest ruu using fastboot mode drivers (holding the volume key and power), and im back to stuck with no root or custom recovery hoping that will fix the problem but its still there.
so is there any way that i can fix my phone, like when the phone turns on it works great but after 2 mins screen turns black and vibrates 5 times.
please let me know if anyone knows a solution to fix this.
thanks
surda said:
hello, my htc evo was working fine, but after flashing some roms i got it missed up
to start off, my phone turns on stays on for exactly 2 mins and 15 secs, then screen turns off, phone vibrates 5 times the green led light start flashing then nothing, the only way to to turn the phone back again is to pull the battery out
now when i connect my phone to the computer, sd card isnt detected however i manged to fix it by fowling this guide
http://forum.xda-developers.com/showthread.php?t=695243
now whenver i connect my phone to the computer it asks for qualcomm drivers thats what i see under device manager 3 yellow arrows with qualcomm something something, the guide above mentions how to fix it, but i need root and i cant root the phone atm because i cant get ADB working, phone displays qualcomm drivers
i was rooted with CWM recovery, but atm i have updated my phone to the latest ruu using fastboot mode drivers (holding the volume key and power), and im back to stuck with no root or custom recovery hoping that will fix the problem but its still there.
so is there any way that i can fix my phone, like when the phone turns on it works great but after 2 mins screen turns black and vibrates 5 times.
please let me know if anyone knows a solution to fix this.
thanks
Click to expand...
Click to collapse
Damn...I had this problem and couldn't fix it...
here's my one attempt:
http://forum.xda-developers.com/showthread.php?t=1304584
This guy doug piston fixed his 5 vibrate error:
www.incredibleforum.com/forum/htc-i...off-vibrates-5-times-green-light-flashes.html
thanks for your help, but i have already tried all these steps before couldn't get it fixed, however they mention updating the radio might fix the issue, but i have S-on so how can i flash radio with S-ON?
anyone knows how to please?
What rom were you last running when this happened?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Sacrifusion said:
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Click to expand...
Click to collapse
IMHO, it looks like faulty slider flex cable (exact same situation i had, but i was able to enter recovery after 2 minutes of logo on screen)
Try to power on phone with slider open.
If you can enter in recovery mode with "volume -" (if it light blue led or vibrate) and see is d-pad is working.
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Sacrifusion said:
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Click to expand...
Click to collapse
To be able to enter recovery, it is not "holding volume-" while powering on phone or keeping it pressed.
Press power button (and it should vibrate), and release it.
When blue led is on press and release vol- button many times untill you enter recovery (don't keep it pressed all time)
Ah, you are absolutely right. I've never entered recovery like that on another Android before. I loaded up the "near perfect" rom and my game pad seems to be working for now, so it appears I am back in business.
How problematic is it if my slider flex cable is going bad? Will it permanently fail eventually?
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
As of now it's been doing this for over two hours. What are my options? Thanks for any help in advance.
Click to expand...
Click to collapse
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
ZVNexus said:
As I am someone with the highest levels of skill, I believe I will be able to assist you with the powers of Google.
This exact same scenario happened to me a couple weeks ago, but for different reasons. (I flashed magisk on a non magisk compatible ROM) This guide over on the OnePlus 3 forums helped out a lot. Just keep in mind the mini version probably won't fix it for you, only the full one fixed it for me. Probably should do the same. Reason I say is because when I did the mini, it did boot up ish, but the logo was all faded and wouldn't let me get to recovery or fastboot. Also it showed up as 900E in device managed instead of QS 9008. This made it so I couldn't use the tool to flash it anymore, for some reason. I forgot what I did to fix it from there, but don't do what I did .
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
Yeah might just have to wait until it dies.
nunchez said:
Yeah I saw this exact thread on the OnePlus forums, thing is I can't get it to power off at all. The power button is completely unresponsive even after holding it down for more than 40 seconds. I'm just going to give it another shot once it dies on its own, hopefully one of those methods will work. Thanks anyway though.
Click to expand...
Click to collapse
This has never failed!!! .. Unless its hardware
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
Turnoff.. hold the power button and both v+ and v-
For about 10secs.. hope it works for you
nunchez said:
Flashed back to stock and wiped everything few days ago. Today all of a sudden I can't get past the bootloader unlocked warning and the OnePlus logo flashes for a split second then it keeps doing this repeatedly. I also can't switch off the phone because the power button doesn't seem to do anything and I also can't boot into recovery. Fastboot works but that doesn't last long either, it exits fastboot mode on it's own and goes back to the bootloop again, also during fastboot all the buttons are unresponsive. The phone is not detected when connected to a PC during this bootloop, but if I do try to boot into fastboot mode and then plug it in the phone shows up as QHUSB_BULK for a split second and disappears.
Click to expand...
Click to collapse
Sorry for replying old post. I have been facing this critical scenario for last two days. The phone never turned off, always looped through unlock warning. No, button working. Can you please share , what about your findings at the end ??
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.
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
wincaffeine said:
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
Click to expand...
Click to collapse
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
boe323 said:
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
Click to expand...
Click to collapse
I have tried what you suggested. Still nothing.
If I can I'd try to resolve this without returning the thing but yeah, it may really be a hardware fault. Guess I have to wait for a miracle to happen (like the phone turning on by itself after several hours, like with some posts that I have found around).
If all else fail, maybe I'd just ask Google to replace it.
Thanks anyway :good:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
kentek said:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
Click to expand...
Click to collapse
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
wincaffeine said:
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
Click to expand...
Click to collapse
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
boe323 said:
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
Click to expand...
Click to collapse
Because of warranty?