This is my first time posting here so hi everyone.
I have a problem with my moto g5+.
I purcased my moto g5+ around a year a go completely new and ended up not using it.
Now my primary device broke down and i thought its time to switch only one problem.
It won't turn on.
When I connect charger white led will consistantly blink but nothing else happens no battery charging screen , nothing.
It wasn't compleatly discharged since I charged it up till 100% and turned it off when I puted it away , i still did charge it a couple times during the year of not using it and last time was a month ago and it charged just fine.
No water or Physical Damage has been done to the phone no rooting also , it just wont turn on.
I tried hard reseting it , tried to hold power button for 5 min tried to enter boot loader to access recovery mode with no luck.
I used original charger and cable that came with phone to charge it.
Since warranty is out of the way by this point because i bought it in july im seeking a fix or recommendation here.
All help will be appreciated
ridestos said:
This is my first time posting here so hi everyone.
I have a problem with my moto g5+.
I purcased my moto g5+ around a year a go completely new and ended up not using it.
Now my primary device broke down and i thought its time to switch only one problem.
It won't turn on.
When I connect charger white led will consistantly blink but nothing else happens no battery charging screen , nothing.
It wasn't compleatly discharged since I charged it up till 100% and turned it off when I puted it away , i still did charge it a couple times during the year of not using it and last time was a month ago and it charged just fine.
No water or Physical Damage has been done to the phone no rooting also , it just wont turn on.
I tried hard reseting it , tried to hold power button for 5 min tried to enter boot loader to access recovery mode with no luck.
I used original charger and cable that came with phone to charge it.
Since warranty is out of the way by this point because i bought it in july im seeking a fix or recommendation here.
All help will be appreciated
Click to expand...
Click to collapse
It seems your device had hard bricked, you can recover it by using the blank flash file.
Here is the procedure:-
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
But, I don't understand how you are device got hard bricked as you need to downgrade or root it to get your device bricked. But you can recover it by above link.
riyan65 said:
It seems your device had hard bricked, you can recover it by using the blank flash file.
Here is the procedure:-
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
But, I don't understand how you are device got hard bricked as you need to downgrade or root it to get your device bricked. But you can recover it by above link.
Click to expand...
Click to collapse
thanks for the reply gonna try it today, I don't really understand my self how did i hard brick it but gonna try you're solution.
riyan65 said:
It seems your device had hard bricked, you can recover it by using the blank flash file.
Here is the procedure:-
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
But, I don't understand how you are device got hard bricked as you need to downgrade or root it to get your device bricked. But you can recover it by above link.
Click to expand...
Click to collapse
Tried doing this methode but my pc wont reconize the device as connected , when i connected it to the pc it showed lightning symbol like charging , i left it to charge for 2h but still nothing.
In order to use blankflash successfully your PC needs to be in test mode. To do this
Code:
Click Start, and then type cmd in the Search box.
Under Programs, right-click cmd.exe, and then click Run as administrator.
At the command prompt, type the following text, and then press Enter: bcdedit /set TESTSIGNING OFF.
Close the Command Prompt window, and then restart your computer
When you plug in phone, look at device manager, ports, and see that it is connected. It should say something like "Qualcomm HS- USB Diagnostics " with a port "Comm 7" or whatever #.
1.Be sure Qualcomm drivers are installed.
2.Make sure your Hard Bricked Moto is connected in device manager under ports .
3.Hold volume down and power until you see it connect under ports. It should say "qhsusb-bulk" You should hear a slight sound from PC when it connects. This can be very tricky as another member [ Rakesh1b] explained his method.
trick is to press and hold the power button then it disconnects and connects to pc u could hear sound from pc then press voldown and power and launch blankflash.bat at the same time i mean same time then it detects and leave the buttons once you see the script running if not it will reboot the device and after running the script it will be booted to fastboot mode . if u failed 1st time repeat same power off then remaing things same as mentioned.
Click to expand...
Click to collapse
[email protected] said:
In order to use blankflash successfully your PC needs to be in test mode. To do this
Code:
Click Start, and then type cmd in the Search box.
Under Programs, right-click cmd.exe, and then click Run as administrator.
At the command prompt, type the following text, and then press Enter: bcdedit /set TESTSIGNING OFF.
Close the Command Prompt window, and then restart your computer
When you plug in phone, look at device manager, ports, and see that it is connected. It should say something like "Qualcomm HS- USB Diagnostics " with a port "Comm 7" or whatever #.
1.Be sure Qualcomm drivers are installed.
2.Make sure your Hard Bricked Moto is connected in device manager under ports .
3.Hold volume down and power until you see it connect under ports. It should say "qhsusb-bulk" You should hear a slight sound from PC when it connects. This can be very tricky as another member [ Rakesh1b] explained his method.
Click to expand...
Click to collapse
Thanks for heads up gonna try to do it again tomorrow I hope this will work and I will be able to get my new phone runing tomorrow since I really need that phone .
ridestos said:
Thanks for heads up gonna try to do it again tomorrow I hope this will work and I will be able to get my new phone runing tomorrow since I really need that phone .
Click to expand...
Click to collapse
Good luck, as it is not an easy process. One time it took me nearly half an hour to time it right, to get blankflash to run successfully. Also I played with a phone that would never flash Vaches blankflash for the G5 + but had to use the one for addison, Moto Z play. When that happens you have to do the extra step of flashing the addison to potter files. Hopefully you won't have to do all that, but just warning that sometimes it is necessary. Like I posted before, in device manager on PC, make sure under ports it shows as qhsusb-bulk under the port it lists as. Also be sure you have adb/fastboot and all its drivers correctly installed. I am really curious as to how it got hard bricked, because even doing my test phone, it is difficult to hard brick it. I have this "test phone" that has a bad microphone, so I have run it through all kinds of crap, rather than jeopardise my every day phone.
ridestos said:
This is my first time posting here so hi everyone.
I have a problem with my moto g5+.
I purcased my moto g5+ around a year a go completely new and ended up not using it.
Now my primary device broke down and i thought its time to switch only one problem.
It won't turn on.
When I connect charger white led will consistantly blink but nothing else happens no battery charging screen , nothing.
It wasn't compleatly discharged since I charged it up till 100% and turned it off when I puted it away , i still did charge it a couple times during the year of not using it and last time was a month ago and it charged just fine.
No water or Physical Damage has been done to the phone no rooting also , it just wont turn on.
I tried hard reseting it , tried to hold power button for 5 min tried to enter boot loader to access recovery mode with no luck.
I used original charger and cable that came with phone to charge it.
Since warranty is out of the way by this point because i bought it in july im seeking a fix or recommendation here.
All help will be appreciated
Click to expand...
Click to collapse
If your phone was in oreo, you maybe want to try the addison (moto z play) blankflash, i once bricked mine and the potter blankflash always failed.
Also try the USB 2.0 ports, as the 3.0 ones doesn't recognizes it.
Put it on the charger and let it charge. IT could just be deader than disco.
Also check your cable make sure it's a data cable buddy.
pwag said:
Put it on the charger and let it charge. IT could just be deader than disco.
Also check your cable make sure it's a data cable buddy.
Click to expand...
Click to collapse
Already tried that didn't work. And I'm using included cable that came with g5+
red002 said:
If your phone was in oreo, you maybe want to try the addison (moto z play) blankflash, i once bricked mine and the potter blankflash always failed.
Also try the USB 2.0 ports, as the 3.0 ones doesn't recognizes it.
Click to expand...
Click to collapse
Well good news is , that i manged to get it to show up as the device with which i should be able to do blank flash.
The problem now is it won't stay in bootloader to be recognized as that device longer than 30 sec.
It just turns off after some time and pc automaticly wont recognize it anymore.
[email protected] said:
Good luck, as it is not an easy process. One time it took me nearly half an hour to time it right, to get blankflash to run successfully. Also I played with a phone that would never flash Vaches blankflash for the G5 + but had to use the one for addison, Moto Z play. When that happens you have to do the extra step of flashing the addison to potter files. Hopefully you won't have to do all that, but just warning that sometimes it is necessary. Like I posted before, in device manager on PC, make sure under ports it shows as qhsusb-bulk under the port it lists as. Also be sure you have adb/fastboot and all its drivers correctly installed. I am really curious as to how it got hard bricked, because even doing my test phone, it is difficult to hard brick it. I have this "test phone" that has a bad microphone, so I have run it through all kinds of crap, rather than jeopardise my every day phone.
Click to expand...
Click to collapse
Well managed to get it to point where my pc recognized phone as device buuut another thing came up. It only is recognized for max 30sec after witch phone gets disconected from pc. Any way to fix that? Or mby im doing something wrong here? I'm starting to consider battery replacment which i dont want to do because it awful to replace battery on this thing.
What is it recognised as? Battery replacement may save you from having to go through the blankflash process if the device will not stay on while plugged in. Only use blankflash if it shows as qhsusb-bulk.
[email protected] said:
What is it recognised as? Battery replacement may save you from having to go through the blankflash process if the device will not stay on while plugged in. Only use blankflash if it shows as qhsusb-bulk.
Click to expand...
Click to collapse
yes it showed up like that but like I said it wont stay on. I remembered one time when I got it to work this month. I was able to boot in to android , factory reset it but the problem was as soon i pluged in the charger phone went from 44% up to 89% in 2 sec then droped to 14% and then to 0 and turned off. I was able to turn it on again after that , it showed 44% like before the charger was connected then I tried to charge it while it was off and since then I haven't been able to go past booting screen since it just turns off after like 30sec on boot screen.
Mby i should just buy a new battery and see if that will fix it.
ridestos said:
yes it showed up like that but like I said it wont stay on. I remembered one time when I got it to work this month. I was able to boot in to android , factory reset it but the problem was as soon i pluged in the charger phone went from 44% up to 89% in 2 sec then droped to 14% and then to 0 and turned off. I was able to turn it on again after that , it showed 44% like before the charger was connected then I tried to charge it while it was off and since then I haven't been able to go past booting screen since it just turns off after like 30sec on boot screen.
Mby i should just buy a new battery and see if that will fix it.
Click to expand...
Click to collapse
I would recommend that or to take it to a service center. Using the blankflash method could brick the device forever (if it's just a battery/display problem), also you will have to live with another devices bootloader and resulting problems from that.
Wolfcity said:
I would recommend that or to take it to a service center. Using the blankflash method could brick the device forever (if it's just a battery/display problem), also you will have to live with another devices bootloader and resulting problems from that.
Click to expand...
Click to collapse
Well service center is out of the way since closest one to me is like 200km away . I should be able to replace it my self so no problems there. I just hope that maybe replacing the battery will fix everything since the phone is practicly brand new and it would be painful and expensive if it's not a battery problem but like motherboards or smth like that.
ridestos said:
Well good news is , that i manged to get it to show up as the device with which i should be able to do blank flash.
The problem now is it won't stay in bootloader to be recognized as that device longer than 30 sec.
It just turns off after some time and pc automaticly wont recognize it anymore.
Click to expand...
Click to collapse
Reboot your pc, and connect the phone to the wall charger for about 10 minutes, then try again the blankflash, and when it's done just play around with the volume up/down buttons just to keep the bootloader on, and use the g5+ toolkit to flash the oreo stock firmware
in any case, this is the blankflash i used it
https://www.mediafire.com/file/hw7hs4vve51c1qh/blankflash.zip/file
Led Light Blinking
ridestos said:
Well good news is , that i manged to get it to show up as the device with which i should be able to do blank flash.
The problem now is it won't stay in bootloader to be recognized as that device longer than 30 sec.
It just turns off after some time and pc automaticly wont recognize it anymore.
Click to expand...
Click to collapse
How did you managed to show it up as a device , i couldn't. I tried everything that i understood from written on these forums, installed qualcomm drivers , moto g5 plus drivers. The device doesn't show up in device manager, its just blinking and doesn't show anything else , i tried charging it overnight. The Led light does go away after a while when i put it o charging, but when i hold down the power button and volume down key it starts blinking again and nothing beyond that
Rather Suhail said:
How did you managed to show it up as a device , i couldn't. I tried everything that i understood from written on these forums, installed qualcomm drivers , moto g5 plus drivers. The device doesn't show up in device manager, its just blinking and doesn't show anything else , i tried charging it overnight. The Led light does go away after a while when i put it o charging, but when i hold down the power button and volume down key it starts blinking again and nothing beyond that
Click to expand...
Click to collapse
Well for me it works like this , i leave it for about 12h (over night) untouched , then after that I can put it on charger and get in bootloader with holding down power button and vol down button at the same time. I have seen some other people that have revived their phones like this usualy they say to just leave it for 24h but for me it works after 12h. if u can get in to the bootloader
after those hours and the phone doesn't turn off (like mine) I would suggest that u leave it for charging in bootloader for atleast 2h and then try to power it on in factory mode thats how I got it to work one time. I hope this will help you.
ridestos said:
Well for me it works like this , i leave it for about 12h (over night) untouched , then after that I can put it on charger and get in bootloader with holding down power button and vol down button at the same time. I have seen some other people that have revived their phones like this usualy they say to just leave it for 24h but for me it works after 12h. if u can get in to the bootloader
after those hours and the phone doesn't turn off (like mine) I would suggest that u leave it for charging in bootloader for atleast 2h and then try to power it on in factory mode thats how I got it to work one time. I hope this will help you.
Click to expand...
Click to collapse
Thanks for replying.
A few points to clear with 12 hours untouched ,do you mean i have to left phone as it is without even charging and if so after 12 hours for how much time do you charge it before getting it to bootloader and did you charge it with the moto turbo charge or just a regular charger or with computer.
Related
This just happened three days ago, when I want to turn on my N7, I have to keep the button pressed for a long time, and when I tried charging it, the battery icon didn't appeared. Also, battery has been heating up by only watching YouTube videos. This has never happened before, and battery is also calibrated... Help!
Please provide more info. Is it unlocked/rooted, which rom/kernel are you using?
Yes, unlocked/rooted, running 4.4.2 stock. I don´t know if Xposed modules can be causing that...
Please I need a reply, I can´t turn on my N7! I tried pressing the power button for more than 1 minute and still nothing happens. I also tried powering it via recovery and via PC but still nothing happens. Also, when I try to turn it on, the tablet starts heating, and it continues to be hot while trying to charge it. I really need a reply!
closercloud said:
Please I need a reply, I can´t turn on my N7! I tried pressing the power button for more than 1 minute and still nothing happens. I also tried powering it via recovery and via PC but still nothing happens. Also, when I try to turn it on, the tablet starts heating, and it continues to be hot while trying to charge it. I really need a reply!
Click to expand...
Click to collapse
Try full charge (~6 hrs) then unplugging the battery and replugging it back after opening the back cover.
I also tried that, but still nothing happened. I think it could also be the screen because when I connected my tablet to the PC, it recognized it as a USB device, but still nothing was shown in screen...
If you can access it via ADB, it means it booted into Android. So, it sounds likely to be the screen's failure.
Well, actually when I connect it something like this appears, so I guess it´s ADB or something...
That's not ADB. It's sooo not ADB. It's bad news. It basically means your device is hardbricked. Only a previously created nvflash backup or Asus can revive it.
Erovia said:
That's not ADB. It's sooo not ADB. It's bad news. It basically means your device is hardbricked. Only a previously created nvflash backup or Asus can revive it.
Click to expand...
Click to collapse
Well, I knew about nvflash, but never made one... I guess I´ll have it serviced. Thank you.
Like the topic says, RSD Lite isn't detecting my Mini. It is detected and drivers installed in Windows 8.1. Difficult to get phone in fastboot mode, but eventually gets there. Any ideas?
Tried a script a found instead, received a bunch of low battery fails. Can't seem to get the phone to charge, not sure how to proceed.
zefyx said:
Tried a script a found instead, received a bunch of low battery fails. Can't seem to get the phone to charge, not sure how to proceed.
Click to expand...
Click to collapse
The best answer for low battery flashing is using a Moto Factory cable...
What difference would that make, the battery would still be drained? It's making it almost impossible to even get into fastboot mode.
zefyx said:
Tried a script a found instead, received a bunch of low battery fails. Can't seem to get the phone to charge, not sure how to proceed.
Click to expand...
Click to collapse
Will it boot to recovery? Also do you have moto device manager installed? If not, install it.
Also try a different usb port
When you plug it into power what does it do?
Topsnake said:
Will it boot to recovery? Also do you have moto device manager installed? If not, install it.
Also try a different usb port
When you plug it into power what does it do?
Click to expand...
Click to collapse
If I don't attempt to boot to recovery but maybe once a day, it will; one time. Device Manager is installed and I've tried all three available USB ports. When I plug it in, nothing happens. The screen stays dark. The only guaranteed way to get the phone up is to hold power and volume up. When these issues first appeared, it would charge while powered off.. sometimes. I baby the phone, definite A-stock. No idea what could have caused it. Rebooted one day and it never progressed further than the Motorola vibration.
Do you have xposed installed? Do you have a custom recovery?
IF so, try flashing something called xposeddisabler.zip from your SD card, then try to boot normally and see if that gets you past the M logo.
Xposed is installed, but I have no custom recovery. I uninstalled Safestrap awhile back to prepare for SunShine and such. That's the most bummer thing about all of this, $25 burning a hole in my pocket to unlock my phone -- something I've waited for since buying my Mini at launch.
I guess the biggest problem I'm facing now is that the device refuses to charge. I can no longer get into recovery. It will however bootup with the power button and using the power+volup. I'm out of ideas. I've found others with this issue, but no one seems to have an answer. I'd really appreciate any helpful feedback.
zefyx said:
Xposed is installed, but I have no custom recovery. I uninstalled Safestrap awhile back to prepare for SunShine and such. That's the most bummer thing about all of this, $25 burning a hole in my pocket to unlock my phone -- something I've waited for since buying my Mini at launch.
I guess the biggest problem I'm facing now is that the device refuses to charge. I can no longer get into recovery. It will however bootup with the power button and using the power+volup. I'm out of ideas. I've found others with this issue, but no one seems to have an answer. I'd really appreciate any helpful feedback.
Click to expand...
Click to collapse
RSD light has known issues on 8.1. You will have to get it into bootloader mode and manually flash it via adb.
zefyx said:
What difference would that make, the battery would still be drained? It's making it almost impossible to even get into fastboot mode.
Click to expand...
Click to collapse
"factory" cable is not the cable that comes with the phone it is a special cable that allows the phone to charge in situations such as yours where the phone will not boot to any stage of the OS.
BladeRunner said:
"factory" cable is not the cable that comes with the phone it is a special cable that allows the phone to charge in situations such as yours where the phone will not boot to any stage of the OS.
Click to expand...
Click to collapse
I dont think the factory cable charges the phone, I believe it bypasses the battery allowing for the phone to powerup straight from the wall/usb power, or flashing when the battery is too low.
there are a couple tutorials on youtube on how to make one using a spare micro usb you have laying around
asuhoops8628 said:
I dont think the factory cable charges the phone, I believe it bypasses the battery allowing for the phone to powerup straight from the wall/usb power, or flashing when the battery is too low.
there are a couple tutorials on youtube on how to make one using a spare micro usb you have laying around
Click to expand...
Click to collapse
you're probably right, but either way it gets you by the "low battery" warnings
Finally got my factory cable. How can I get the phone into fastboot mode with it? It instantly turns on and hangs at the same Moto logo trying to boot into Android whenever connected to the PC.
Got it into fastboot mode once, with the factory cable and went into BP Tools. Was able to charge the phone to 19%, but now I can't get back into fastboot.
Nothing happens when plugging USB into wall or PC with factory cable or normal now either >:|
EDIT: let the phone die, and all is well. Booted into fast boot after letting charge 100% and now I'm just looking for restoration files as sbf is down.
zefyx said:
Nothing happens when plugging USB into wall or PC with factory cable or normal now either >:|
EDIT: let the phone die, and all is well. Booted into fast boot after letting charge 100% and now I'm just looking for restoration files as sbf is down.
Click to expand...
Click to collapse
What FXZ you need, I have a couple of them stored locally... could throw in dropbox if its the correct one.
Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)
I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.
I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.
Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"
charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.
I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.
As title states, have a sm-g935f running stock firmware that won't boot.
Had issues with it freezing and rebooting so re-flashed stock firmware, has run fine for approximately 3 weeks now when suddenly, whilst installing swiftkey it froze, then turned off. Had roughly 50% charge at this point. Have googled for hours now, tried different button combinations for varying lengths of time to try to boot. Have left it to charge for 2 hours and have just had another crack at it. Charge indicator does not appear on screen when plugged in, led at top of display does nothing at any point.
I'm out of ideas at this point, really could use the expertise of the greater xda community now, this is my only phone and its unusable right now leaving me connectivity-ly stranded.
Thanks in advanced for the help guys :cyclops:
Can u boot into Recovery mode?
No, it does nothing at all. It won't even attempt to turn on
So brick it is.
Boot it into Download mode by pressing Vol Down + Home key and Power Key. Then open Smartswitch app click preferences and click emergency recovery follow the steps then
I also had this problem. Basically you need to follow SjDU. If you cannot get into download mode. Try and leave the phone uncharged for 24 hours. Then charge for about 30 min and try to get into download mode.
AndrOmega said:
So brick it is.
Click to expand...
Click to collapse
Why thank you, so helpful
Thanks guys, ill leave for 24 hours, i just have no way of knowing whether its uncharged or not, it really gives nothing at all regardless of what i do. Not even a slight vibrate when i plug it into a charger or pc.
regardless, ill leave it and report back
Thanks
Hi,
It seems to me that it's really dead, give a try at leaving it uncharged for a few hours and then trying again.
However I wouldn't hold my expectations up, I had a similar problem with the Galaxy S4, phone was constant freezing after a Stock flash (I was using custom ROM before), then tried to restart the phone, phone got stuck and removed battery. Turned out bootloader died and I had to flash it again using JTAG (S4 was pretty easy to open up).
I hope that you won't need to use a JTAG Flash, since it needs to open the device and obviously S7 is pretty hard to get to the circuit. An easy option is trying an USB JIG to get to download mode (that is, if your phone has charge - hence you will need to try first the option others suggested - and a working bootloader), you can easily find this device for less than 5 dollars on eBay.
Hope you get your beloved device working again.
All the best,
~Lord
Sent from my Galaxy S7 Edge using Tapatalk
Hi everybody,
I have a 6P for 1 year and a half now, I never had big issues with it, only some random reboots.
But it has just turned off this morning and can't turn on no matter what. I have tried a lots if things, hold on the power button or power + volume but it didn't work.
The fact is when i plugg it on my PC, it is detected as something like Qualcomm Dloader H-USB, i don't remember the exact name of it. And when i hold the power button while plugged on my PC, every 15 seconds i have the exact same sound on my PC that if i removed something (like usb key for example).
I deduce that my phone is maybe still alive, so is there any solution ?
Thanks you.
@deltanight24 Any random shutdowns as well? I think you just need a new battery. Nexus 6p is plagued with couple issues one being the battery and the other the big core. Usaully the big core causes bootloops so I'm leaning more towards battery for you. You probably could use a fresh one anyways after couple years giver or take.
I have this exact same issue. Is the device bricked?
chuckywang said:
I have this exact same issue. Is the device bricked?
Click to expand...
Click to collapse
Yes. :crying: I have the same. I've spent many many hours with qfil and assorted qpst programs. I only ever got command line tools to work, and we en after that, still no boot. ..
The phone is probably in the so called EDL Mode ( 9008 ). My phone is also stucked in this mode suddenly. It was working fully fine, battry was charged and used for 2-3 hours (still enough charge inside), then it turned off when i was dialing a phone number. Since then its dead and i cant turn it on. Its detected by computer.
Have someone be able to get it working again? I dont care about the phone itself. I need my data.