Related
OK, so here's the issue. I have an HTC Desire C. It's my girlfriends so I don't know the OS version. I replaced the Touch Digitizer because it was shattered (it did respond to touches though). Now that its replaced it seems to respond to touches but not correctly. I can't get it to swipe the lock screen out of the way. It's as if it is not calibrated correctly. So I'm stuck on the lock screen.
I want to run ADB so I can figure out if its registering touch events correctly, and also try and send them over ADB. But, being my girlfriends phone, she never enabled "USB Debugging". When I hook the phone to the computer, I don't see it showing up as a unknown device in windows Device manager (VISTA). I know it works, cause I tried it with my Nexus S and that shows up. I know the steps are first find it in device manager then manually select the driver as the ADB interface, I've had this working on my Nexus S. But the issue is that it doesn't show up at all in Device manager, and I assume its because USB debugging is off. I tried turning off USB debugging on my Nexus S, hooked it to my computer, and it doesn't show up either. So it seems like that is the issue.
I tried to boot into recovery (power button + volume down), then went into fastboot, connected the phone to the comp again, but it still does not show up.
Below are some of the other things I have tried, but they still brought me no luck:
I have tried installing HTC sync so I get the HTC drivers on my computer, but it doesn't even show up in HTC's software (In fact, it does not show up as a storage device either, I assume cause you have to accept the notification on the phone, but I can't use the phones UI at all). I tried moving the HTC drivers into c:\windows\system32 and it still does not show up. I then tried rebooting the phone and my computer. Still does not show up. It seems like windows isn't even reading the phone as a USB device. Tried swapping USB cables (both work with my nexus s), and still nothing. Is there something I am missing?
Any help would be much appreciated, this is driving me crazy.
Also, after replacing the digitizer, if I first boot into the phone and then hit the power button, I don't get the content window that allows you to choose "reboot", "shutdown", etc. The only thing I can do is hold it for 15 seconds and the thing turns off. I'm hoping this is because I never passed the lock screen for the first time. I'm hoping this is not an indicator that I screwed something up when I opened the phone. I've had my Nexus S open plenty of times.
Another guy had same issue. here
Try that.
life!
Yea let us know if it works
Lifehacker7 said:
Another guy had same issue. here
Try that.
life!
Click to expand...
Click to collapse
I can't get the phone to show up when I type "fastboot devices" or "adb devices". I have tried this from the lock screen, from the bootloader, from the bootloader and in fastboot mode. That is my critical problem now. Cable is actual data cable, and I'm using USB port on back of a desktop computer. Is there anything else that could be causing the phone to not be recognized?
I was watching a video on my phone when all my apps made a pop-up saying "Unfortunately *app* has stopped working". This happened for every app, I tried to factory reset from recovery mode because I couldn't access Settings, but when I did the factory reset nothing changed and the problem persisted. I decided to just leave the phone and the next day it wouldn't turn on at all no matter what and when I tried to charge it and left it for two hours it seemed as if it wasn't charging because the temperature of the phone or the charger didn't change so I came to the conclusion that my phone is bricked. When I plug the phone in by USB to a computer, the computer makes the connected sound.
-Huawei Y320-U151 [Rooted]
-No Custom Recovery
beanz_v7 said:
I was watching a video on my phone when all my apps made a pop-up saying "Unfortunately *app* has stopped working". This happened for every app, I tried to factory reset from recovery mode because I couldn't access Settings, but when I did the factory reset nothing changed and the problem persisted. I decided to just leave the phone and the next day it wouldn't turn on at all no matter what and when I tried to charge it and left it for two hours it seemed as if it wasn't charging because the temperature of the phone or the charger didn't change so I came to the conclusion that my phone is bricked. When I plug the phone in by USB to a computer, the computer makes the connected sound.
-Huawei Y320-U151 [Rooted]
-No Custom Recovery
Click to expand...
Click to collapse
Any Updates on what happened with your phone?
Hello. Your phone uses MTK Cpu? (You can see in gsmarena and if ur cpu for example is MTxxxx)
If yes then install VCOM drivers for your phone on pc (works well on windows xp) after that see if pc finds your device or not (in device manager u can see that) if the pc finds it and there are no problems u can flash it with SP-Flashtool .
and if no, it means there is an hardwere problem (it happens when phone falls on ground and etc...)
You can find a guid on internet for flashing your phone
Sorry i didnt explaind everything and sorry for my bad english
Sent from my SM-G360H using XDA Forums
Hello, there.
I bought my nexus 5 the day it was launched. Worked great for 2 yeas+.
Now is dead. It's a long story.
One day simply died. I pluged it to charge it and turn on and off constantly (boot loop). I watched some videos on youtube where people constrantly press the power button and after a moment, it worked. But eventualy stop working again and it never boot again.
I can't access fastboot, nothing. I researched again and found that the power button could be damaged. So I removed it and install a new one and SURPRISE. The loop was gone, it charges, but the power button doesn't seem to be working...or could be another thing!!!
When I plug it to the USB, the PC recognize it, but as "other device". However, it call it "Android". Can't understand.
If I search for adb devices on the command line, it founds nothing.
If adb devices could find it, maybe i'll be able to boot it from the command line, right?
Any help would be appreciated.
Thanks
Adb commands won't work unless the phone is booted into the rom. If you can get into the bootloader, fastboot commands should work if the drivers are loaded.
First, I will say that I have done an extensive amount of searching and reading about boot loops and issues with the Note 4 before posting this. After days of dead ends, I have to ask for help...
About a week ago (end of January 2017), I installed the Verizon security patch update for Android 6.0.1 for my Note 4 (SM-N910V): MMB29M.N910VVRS2CQA1. Everything was normal until this past Friday night, when I used a flashlight app (had been installed since I had the phone and used often) and it spun into a bootloop. Battery was at 20% at the time, and since I've had the phone, the battery quickly discharges below ~15%.
Situational Details:
Anyways, the bootloop goes all the way to the home screen, and often the touchscreen is active for a few seconds (varies) before it freezes for 5 seconds and continues the bootloop. It's worth noting that during the bootloop, the screen gets incrediby hot at a specific point: horizontally across from the power button and vertically below the light sensor.
Also, I'm able to access the recovery menu, download menu, and boot menu. Also, when a power cable is connected to the phone (with battery inside), the phone screen shows the empty charging battery symbol and then immediately turns on, without me having to press the power button. After that, the only way to actually power off the phone is to remove the battery or let it bootloop until it dies.
So far, I've tried the following without success:
-Wiping partition cache
-Factory data reset
-Flashing stock ROM with Odin. Though Odin recognized the device in the USB port and it accepted the ROM which I loaded it with, there was no activity from Odin to the phone once I clicked "Start". I'm using the original USB cable that came with the phone (the one that I charge it with), and the USB port is working fine.
-Using Kies3/Kies2.6/Smartswitch to revert back to factory stock ROM. Though Kies3 is allegedly the correct software, they all display an error message that my device is not supported, when I attach a USB cable to my laptop from my phone (regardless of USB port).
-When using Kies3 to try Tools > Firmware upgrade and Initialisation, Kies accepts "SM-N910V" as the model number, but it displays an error message that my S/N is incorrect, though I am copying and verifiying the IMEI from under the battery compartment (I also registered my phone with Samsung using this IMEI, so I know it's valid).
-Wiping partition cache 5x + Factory data reset 5x before rebooting
When in the recovery mode, the current android version MMB29M.N910VVRS2CQA1 is listed, which I find incredibly bizarre, since I thought it would have flashed to the stock ROM after a factory data reset. *shrug*
It's crossed my mind that the exceedingly hot temps may be causing the boot loop, but genuinely do not know if that's true or why it would become so hot in the first place. Either way, I just want to toss the idea out that maybe I have a hardware issue that's causing such overheating.
Anyways, at this point, I'm totally confused about what to do, especially since it's not totally bricked. Any/all help is greatly appreciated.
Anybody have any thoughts at all? I'm more and more open to the theory that it's overheating and causing a boot loop. When it's been sitting for a long time at room temperature, the screen remains at full brightness on the Verizon splash screen, and does so until it gets stupidly hot near the microSD / SIM slots... then it boots up for ~5-15 seconds, freezes for 5 seconds, and boot loops again.
I may try to thoroughly wrap my phone in plastic wrap and apply an ice pack before attempting to use it again. I find it hard to believe that the culprit is batteries since the issue happens with both batteries that I have (purchased separately at different times).
Ok, I had my Note 4 totally cold yesterday and booted it up normally. I discovered a few things while playing with it:
When the first reboot happened,the usual hot spot was hardly to room temperature. I tried this exact same test again this morning, with the same results... the hot spot was not even to room temperature when it froze and rebooting.
It's worth noting that I figured out the screen does not freeze if the display is constantly moving, regardless of phone temperature. For example, I normally try to do something/anything prior to the phone freezing and rebooting, like establish a file transfer type usb connection to my laptop, instead of the default 'charge' type connection. Well, to go through the settings menu and pick out the connection type, the screen will always hang for a split second as it loads the next set of menus. Normally, it would freeze at this point and reset. But today, I decided to click on the Apps button and oscillate my finger on the screen to flip between pages of apps... and it worked for several minutes straight.
I know my problem seems incredibly strange, but do any of these symptoms have any plausible explanation? I'd hate to think there is literally nothing that I do and that my $$$ Note 4 phone is now a brick.
1weirdtrick said:
First, I will say that I have done an extensive amount of searching and reading about boot loops and issues with the Note 4 before posting this. After days of dead ends, I have to ask for help...
About a week ago (end of January 2017), I installed the Verizon security patch update for Android 6.0.1 for my Note 4 (SM-N910V): MMB29M.N910VVRS2CQA1. Everything was normal until this past Friday night, when I used a flashlight app (had been installed since I had the phone and used often) and it spun into a bootloop. Battery was at 20% at the time, and since I've had the phone, the battery quickly discharges below ~15%.
Situational Details:
Anyways, the bootloop goes all the way to the home screen, and often the touchscreen is active for a few seconds (varies) before it freezes for 5 seconds and continues the bootloop. It's worth noting that during the bootloop, the screen gets incrediby hot at a specific point: horizontally across from the power button and vertically below the light sensor.
Also, I'm able to access the recovery menu, download menu, and boot menu. Also, when a power cable is connected to the phone (with battery inside), the phone screen shows the empty charging battery symbol and then immediately turns on, without me having to press the power button. After that, the only way to actually power off the phone is to remove the battery or let it bootloop until it dies.
So far, I've tried the following without success:
-Wiping partition cache
-Factory data reset
-Flashing stock ROM with Odin. Though Odin recognized the device in the USB port and it accepted the ROM which I loaded it with, there was no activity from Odin to the phone once I clicked "Start". I'm using the original USB cable that came with the phone (the one that I charge it with), and the USB port is working fine.
-Using Kies3/Kies2.6/Smartswitch to revert back to factory stock ROM. Though Kies3 is allegedly the correct software, they all display an error message that my device is not supported, when I attach a USB cable to my laptop from my phone (regardless of USB port).
-When using Kies3 to try Tools > Firmware upgrade and Initialisation, Kies accepts "SM-N910V" as the model number, but it displays an error message that my S/N is incorrect, though I am copying and verifiying the IMEI from under the battery compartment (I also registered my phone with Samsung using this IMEI, so I know it's valid).
-Wiping partition cache 5x + Factory data reset 5x before rebooting
When in the recovery mode, the current android version MMB29M.N910VVRS2CQA1 is listed, which I find incredibly bizarre, since I thought it would have flashed to the stock ROM after a factory data reset. *shrug*
It's crossed my mind that the exceedingly hot temps may be causing the boot loop, but genuinely do not know if that's true or why it would become so hot in the first place. Either way, I just want to toss the idea out that maybe I have a hardware issue that's causing such overheating.
Anyways, at this point, I'm totally confused about what to do, especially since it's not totally bricked. Any/all help is greatly appreciated.
Click to expand...
Click to collapse
Do you have USB debugging turned on? Do you have all of the USB drivers for Samsung phones installed? Are you using the stock USB cable when you use Odin?
If you can't get Odin to flash your firmware(it has to be the same version you have or newer, it can't be older), then you may have a hardware issue that is a result of the excess heat you mentioned.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Do you have USB debugging turned on? Do you have all of the USB drivers for Samsung phones installed? Are you using the stock USB cable when you use Odin?
If you can't get Odin to flash your firmware(it has to be the same version you have or newer, it can't be older), then you may have a hardware issue that is a result of the excess heat you mentioned.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I didn't have USB debugging turned on before. I turned it on (under developer options... which I barely have time to access before it restarts), but now both my laptop and desktop won't recognize the device via any USB port. I do have the USB drivers for Samsung phones installed and have re-installed them a few times, to be safe. Also, I am only using the stock USB cable when doing any of these things.
1weirdtrick said:
I didn't have USB debugging turned on before. I turned it on (under developer options... which I barely have time to access before it restarts), but now both my laptop and desktop won't recognize the device via any USB port. I do have the USB drivers for Samsung phones installed and have re-installed them a few times, to be safe. Also, I am only using the stock USB cable when doing any of these things.
Click to expand...
Click to collapse
Does the device show in device manager? What is it labelled as in device manager?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Does the device show in device manager? What is it labelled as in device manager?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Assuming you mean the device manager in Windows, it's only showing as "Unknown USB Device (Device Descriptor Request Failed)".
Two new interesting notes:
When I enter Maintenance Boot Mode (Down Volume + Power to boot) and select USB Debug Mode, it now just performs a normal reboot. I can't recall for certain if this was any different in the past.
When I have the ability to access Developer options, I can definitely see that USB debugging is checked. Also, when I select 'USB configuration', 'charging' is pre-selected by default. When "MTP" (media transfer protocol) is selected, the developer mode menu still displays the value as 'charging', even though subsequently accessing the 'USB configuration' sub-menu shows that MTP is selected. Weird.
1weirdtrick said:
Assuming you mean the device manager in Windows, it's only showing as "Unknown USB Device (Device Descriptor Request Failed)".
Two new interesting notes:
When I enter Maintenance Boot Mode (Down Volume + Power to boot) and select USB Debug Mode, it now just performs a normal reboot. I can't recall for certain if this was any different in the past.
When I have the ability to access Developer options, I can definitely see that USB debugging is checked. Also, when I select 'USB configuration', 'charging' is pre-selected by default. When "MTP" (media transfer protocol) is selected, the developer mode menu still displays the value as 'charging', even though subsequently accessing the 'USB configuration' sub-menu shows that MTP is selected. Weird.
Click to expand...
Click to collapse
Have you tried booting to safe mode, if it boots to safe mode then it's a user app or a user app update that is causing your bootloop. In safe mode you can uninstall whatever app or app update caused it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Have you tried booting to safe mode, if it boots to safe mode then it's a user app or a user app update that is causing your bootloop. In safe mode you can uninstall whatever app or app update caused it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yeah, I thought about that, too. I've tried safe mode even after factory resets + cache wipes and it still boot loops. ("Safe mode" does indeed display in the bottom left of the display/GUI) Good thoughts, though.
1weirdtrick said:
Yeah, I thought about that, too. I've tried safe mode even after factory resets + cache wipes and it still boot loops. ("Safe mode" does indeed display in the bottom left of the display/GUI) Good thoughts, though.
Click to expand...
Click to collapse
Starting to sound like a hardware issue.
Sent from my SM-S903VL using Tapatalk
Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.
Riverseo said:
Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.
Click to expand...
Click to collapse
I actually start the MSM tool ,wait until it boots up, position my cursor close to the start button on the tool, then I connect my phone to cable make sure it's attached to both PC and phone , put phone in edl ( hold power button and both vol up and vol down at same time) phone should go blank and you should see a connect on the MSM tool, hit start,,,, hth
My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc
Riverseo said:
My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc
Click to expand...
Click to collapse
When I go into edl it's a completely blank ,,,screen is black
Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.
Riverseo said:
Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.
Click to expand...
Click to collapse
I would just make sure you have all the correct drivers, especially l2, other than that iam out of ideas maybe someone with more experience will reply,, good luck
No worries cheers for the help though!