Related
After spending my entire Saturday trying in vain to get my win 7 laptop to recognize my captivate I've decided I need to reach out for some help.
Right when I gore my phone, without too much hassle I did the superoneclick root via my pc with great success. Did the lagfix after that and all was well. Go me right?
I used my phone for a little bit and decided that it was time to but sonera music and pictures on it. This is where it all went wrong.
For background, I have done up to this Point: tried both driver sets that are floating around (and exe and the version most often linked to in help threads with a simple setup file), Ive tried kies, I've tried going into device manager to manually locate the divers. Nada.
At this point the drivers with the setup file will no longer install because the install of the exe screwed up at some point. Windows is only showing the device as us composite hub or as a unknown device. I can sometimes get it to say Samsung android usbb device but it shows that it is in error and it still wot see the phone. Someone else asked me if I had used the mount option when I comes up in my notifications bar which I haven't because it never gives me the option. I've tried disabling launcherpro, undoing the root, undoing the lagfix, formatting and wiping user data on the phone, still nada. I've tried all usb modes. Nada.
First things first, can someone explain to me exactly what I should do in device manager to get the drivers in order? I'm pretty sure this is the root of my problem. Any idea on how to get rid of the erroneous drivers that are causing the driver setup to fail?
Any help would be great :S
Need to try and manually remove three old drivers, then try and re install. Id suggest using the ones design gears posted on his one click back to stock post
Sent from my SAMSUNG-SGH-I897 using XDA App
I snipped this from one of my old posts in the Vibrant section...
For those of you having a problem with Windows 7 recognizing your Vibrant ... here is how I fixed it on my system.
*Note: You do not need to load any special USB drivers for your phone to be recognized in Mass Storage mode in Windows 7.
*Warning: You follow these instructions at your own risk ... no screaming at me if you try it and something gets screwed up!
1) Navigate your way into the Device Manager / Universal Serial Bus Controller
2) Uninstall the device(s) "USB Root Hub" (My system had 2 listed)
3) You will lose mouse and keyboard control (because you just removed the USB Hubs)
4) Reset your PC and allow Windows to boot normally.
5) Go back to the device manager and wait for all of the "!" marks to go away as windows re-installs the USB Hubs and reinitializes all of your devices.
6) Make sure your Vibrant is in mass storage mode and has USB debugging OFF
7) Plug in your Vibrant via the USB cable and be amazed as windows recognizes your device and assigns the drive letters. After you select the mount option on your phone you will have normal access via windows explorer.
Hope this helps some of you out there !!!
~Stresa
Sent from Samsung Vibrant
thanks for the good responses guys but both of those have failed. Odin cant even see my phone, same issue with superoneclick root. I even just tried on an enitrely different PC and got the same "device could not start" message.
tried deleting all the drivers for the USB devices. nada. still no connection
Subrock said:
After spending my entire Saturday trying in vain to get my win 7 laptop to recognize my captivate I've decided I need to reach out for some help.
Right when I gore my phone, without too much hassle I did the superoneclick root via my pc with great success. Did the lagfix after that and all was well. Go me right?
I used my phone for a little bit and decided that it was time to but sonera music and pictures on it. This is where it all went wrong.
For background, I have done up to this Point: tried both driver sets that are floating around (and exe and the version most often linked to in help threads with a simple setup file), Ive tried kies, I've tried going into device manager to manually locate the divers. Nada.
At this point the drivers with the setup file will no longer install because the install of the exe screwed up at some point. Windows is only showing the device as us composite hub or as a unknown device. I can sometimes get it to say Samsung android usbb device but it shows that it is in error and it still wot see the phone. Someone else asked me if I had used the mount option when I comes up in my notifications bar which I haven't because it never gives me the option. I've tried disabling launcherpro, undoing the root, undoing the lagfix, formatting and wiping user data on the phone, still nada. I've tried all usb modes. Nada.
First things first, can someone explain to me exactly what I should do in device manager to get the drivers in order? I'm pretty sure this is the root of my problem. Any idea on how to get rid of the erroneous drivers that are causing the driver setup to fail?
Any help would be great :S
Click to expand...
Click to collapse
kies or mass storage?
for kies debugging in settings>aplications must be disabled. i dont remember what works better ask on connection or to have connection type preset in settings>applications>usbsettings. im on froyo which works a million times better, kies on jf6 was like a 90% fail rate. it just didn't work for me.
for mass storage you need to mount the phone from a message in the notification bar, even if it asks the connection type and you tick mass storage it will not be mounted, you still need to mount from the notification bar.
you can also mount the sdcards from the notification bar in debugging mode which bypasses the connection type setting in settings>applications>usbsettings.
i tend to leave debugging on in case i need adb to fix my phone, i only turn it off to use kies which is useful to fix my contacts when i have multiples (it's alot easier to fix 200+ contacts on a computer screen using a mouse and keyboard), or install an update if i choose to run the phone stock.
tried in every combination of modes, cant get it connect any possible way. I also dont get the option to mount it from the notification bar so perhaps I have a hardware issue.
Are you using the stock usb cable? I've had problems with some but not all generic cables.
Sent from my SAMSUNG-SGH-I897 using XDA App
may not be what you want to hear
I actually had a similar problem, though not the same. My phone charges and I can use mass storage without issue, but I could not get Odin One Click updaters to ever "see" my phone. I tried every USB port on my box, tried several different driver sets (including the ones DG recommends). Eventually, I tried on a different computer. Odin saw it fine, updated no problems, first time out of the gate.
I know, I know, not everyone has access to two computers, and furthermore there "should" be no reason it can't work on a particular one, but for me, short of formatting my PC and reinstalling OS, I tried everything else I could think of.
Good luck, either way!
post moved to new thread
I don't think there should be a logical reason as to why this would ever work, but Windows (and computers in general sometimes) has a tendency to surprise me like that... but what if you try removing the drivers by whatever automatic means you are provided with, and then check and remove them manually (if necessary), and finally run CCleaner or some other program with registry cleaning capabilities to give your PC that last little enema.
Then use DG's drivers and install them in whatever way he recommends (been a while since I installed the drivers). That's really all I can think of on the PC side... maybe putting a cheap little USB hub between your phone and your PC if you have one laying around as another mostly futile attempt.
Fair warning, it is possible for CCleaner to mess up your PC... any program that messes with the registry can potentially do so. I've never seen the program cause harm, but it is possible.
I've had the same problem with my Crappy from day one. I still somehow got SuperOneClick to Root my phone through multiple attempts. But if all you need to do is transfer files from your phone to PC, and vice versa. I would recommend Android Sync Manager. It can read most of the file systems in the phone, and transfers at a decent speed.
same here
One of my PCs recognizes Cappy with the same cable, OS, drivers. Other one doesn't.
So I ended up using "ADB Wireless" from Market. It works pretty good, slower than USB, but works.
Also - if you are willing to make your PC work - try fresh reinstall of Windows 7SP1 and disable driver update from Internet.
Since your just trying to put music and pictures on the phone, try Kies Air from the market. Install it on your phone then you can transfer files wirelessly with the browser from your computer.
USB Cable
gbrown2036 said:
Are you using the stock usb cable? I've had problems with some but not all generic cables.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Definitely check the USB cable. I had this exact issue before. I checked drivers, did a bunch of un-installing and manual installing of drivers. Finally I tried my stock USB cable and all worked perfectly!
Hello everyone,
First and foremost, please forgive me if an answer to this has already been posted somewhere; I have searched several different forums extensively, and while I have found several similar problems, I have tried their solutions and come up empty-handed. Here's my dilemma:
1. My phone simply refuses to be detected/recognized by my PC via USB connection, through Kies/Odin/Windows Explorer, though I can be detected and connect through AirDroid.
2. I have updated my Samsung USB Drivers for Mobile Phones, and reinstalled those drivers multiple times.
3. I have tried multiple different USB cords, as well as multiple different USB ports.
4. I have been successful in connecting my wife's Note 1 to my PC.
5. I have tried dialing the "*#0808#" code into the dialer, and it always tells me that the signal is weak.
6. I have done a factory reset, both through the settings menu and through the recovery mode.
7. After having done the factory reset, I have been able to get the phone to download updates, but when the phone tries to install them, it only gets to 25% every time and then shows "Error", after which it tells me that the firmware was unable to update.
8. I have downloaded, installed, and tried every app I can find that claims to be able to root a phone without a PC, and they have all failed.
9. I am simply unable to find the "USB Connections" menu, the one where the MTP or PTP modes are, and have only been able to access it through Samsung's "Smart Care" app.
10. I have also tried to get Odin to recognize my phone by resetting my SIM card, and by using the battery removal trick: neither worked for me.
I think that pretty much covers everything right now.... I am COMPLETELY dumbfounded, and have NO idea what to do, NOR do I have any idea if this is a hardware or software problem. ANY help would be MOST appreciated.
Hi,
You have already made a post here on same topic. Please do not make multiple posts of same topic. kindly wait for the experts to answer your question.
Thread Closed.
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
So, something very weird started happening to my phone. Out of nowhere, about 7 hours ago, it would stop charging whenever it was on, charging only when it was off and connected to my laptop. However, I thought it was just something wrong in the dev options, and I went to change whatever was the USB option to "charge phone". With this, I did accidentally forgot to activate the OEM option, and had to reboot not long after. You can probably see where this is going now.
Now I have a phone that bootloops on the FAP Lock message, and whenever I go to download mode to fix it, my PC just doesn't recognize the Phone. I've tried different USB cables, all of them are only recognized when the phone is shut down. So it isn't a hardware problem, because the Phone actually charges when it's shut down, and it isn't a problem with my USB ports or cables, as anything else I use with it works fine. And the worst part is, I need this phone today for a serious bank matter, and I can't afford to lose any data on it either, there's some very personal important stuff from yesterday that wasn't backed up yet. And keep in mind that paying for it to be fixed is the last option for me, as I can't afford it (besides, I fear they might end up getting the phone in factory reset mode, and I can't lose that data as I said).
Any kind of suggestions on how to get either the PC to recognize the phone, or flashing in a different way that doesn't need the PC to recognize the device? Thanks in advance.
Edit: Whenever I try to connect the phone via USB, it doesn't even make the Windows "USB connected" sound, it's just like it isn't there at all. One time, I got it to show, but it was as a "unrecognized usb device", and I haven't been able to replicate it yet.
Hello, I have a Samsung A51 through T-Mobile. Recently my phone has only been charging and won't do any data transfer or bring up the menu to select what to do with the connection. After trying many different things I found out it will connect with data transfer only when I restart the phone while it's plugged in. Once I unplug the phone and plug it back in nothing. But if I leave it plugged in and restart it again it shows up.
Any ideas? All help would be greatly appreciated. I've looked around and cannot find anything regarding my issue.
Thank you
Try a known good cable.
Make sure the phone pop up enabling the data connection is enabled. Without permission each time access will be denied... at least on my Samsung.
Access the drive directly in Device Management; hit scan for new devices.
Check Event Viewer for errors logged.
Reload the drivers on the PC.
blackhawk said:
Try a known good cable.
Make sure the phone pop up enabling the data connection is enabled. Without permission each time access will be denied... at least on my Samsung.
Access the drive directly in Device Management; hit scan for new devices.
Check Event Viewer for errors logged.
Reload the drivers on the PC.
Click to expand...
Click to collapse
I can do all that. But only after restarting my phone while it's plugged in. It's not a cable issue or a USB port issue. Ive tried multiple cables and ports. And also tried same cable with different phone. The port on my phone is fine. If I plug it in, restart my phone it shows up as it should. Once I disconnect the phone and plug it back in, nothing. It's very odd. I think it may be an update issue from t mobile. But figured I'd check here.
Thank you for your response
Also, the pop up to allow access only shows up when phone is plugged in and I restart it. I unplug it and plug it back in. And it will only show thats charging and there isn't a prompt or selection of what to do with usb (transfer files, images, MTP, tethering etc.
Shadow42 said:
Hello, I have a Samsung A51 through T-Mobile. Recently my phone has only been charging and won't do any data transfer or bring up the menu to select what to do with the connection. After trying many different things I found out it will connect with data transfer only when I restart the phone while it's plugged in. Once I unplug the phone and plug it back in nothing. But if I leave it plugged in and restart it again it shows up.
Any ideas? All help would be greatly appreciated. I've looked around and cannot find anything regarding my issue.
Thank you
Click to expand...
Click to collapse
Try this troubleshooting steps https://www.wikihow.com/Clear-the-Record-of-USB-Plug-in-Equipment and that https://www.partitionwizard.com/disk-recovery/the-last-usb-device-malfunctioned-windows-10.html from time to time my Samsung devices have some kind of issues with Windows 10.
Also you should try with adb commands pairing both and allow the access always when the prompt appears, it could be some kind of permission denied or malfunctioning that either Samsung is not asking correctly to PC or the permission from PC is not coming properly to device, this should happen due to some old logs or a filled directory in the USB hub in Windows that needs some cleaning.
Shadow42 said:
Also, the pop up to allow access only shows up when phone is plugged in and I restart it. I unplug it and plug it back in. And it will only show thats charging and there isn't a prompt or selection of what to do with usb (transfer files, images, MTP, tethering etc.
Click to expand...
Click to collapse
Check Developer options>USB default configuration
Try clearing system cache on the phone.
Try a hard reboot on the phone.
If you unplug the phone from the PC you need to reauthorize it via the phone pop up after you reconnect it... each time.
If you always leave the PC on, reboot it.
blackhawk said:
Check Developer options>USB default configuration
Try clearing system cache on the phone.
Try a hard reboot on the phone.
If you unplug the phone from the PC you need to reauthorize it via the phone pop up after you reconnect it... each time.
If you always leave the PC on, reboot it.
Click to expand...
Click to collapse
Like I've said. There is no prompt unless I restart my phone while plugged in. This isn't my first phone. I understand how it "should" be working. And it only acts as it should when I plug it in and restart the phone. Once I unplug it and plug it back in its as if I'm using a charg only cable.
Thanks for the response
Shadow42 said:
Like I've said. There is no prompt unless I restart my phone while plugged in. This isn't my first phone. I understand how it "should" be working. And it only acts as it should when I plug it in and restart the phone. Once I unplug it and plug it back in its as if I'm using a charg only cable.
Thanks for the response
Click to expand...
Click to collapse
Meh then play with it... you know the drill.
Goggle it and look at other models/OS's that had the same issue as well. A lot of the same issues keep reoccurring so this tactic is helpful with newer models too.
Either it's settings, the load got screwed up or it's hardware maybe the port. Worse case... a mobo failure.
Try it in safe mode.
I probably do a factory reset* especially if it's an old load. If that fixes it but the issue returns latter, it's a setting or 3rd party app causing it.
*if it persists after a factory reset it's possible the firmware version is the problem or the firmware got corrupted during the flash. Reflash firmware.
blackhawk said:
Meh then play with it... you know the drill.
Goggle it and look at other models/OS's that had the same issue as well. A lot of the same issues keep reoccurring so this tactic is helpful with newer models too.
Either it's settings, the load got screwed up or it's hardware maybe the port. Worse case... a mobo failure.
Try it in safe mode.
I probably do a factory reset* especially if it's an old load. If that fixes it but the issue returns latter, it's a setting or 3rd party app causing it.
*if it persists after a factory reset it's possible the firmware version is the problem or the firmware got corrupted during the flash. Reflash firmware.
Click to expand...
Click to collapse
Thank you. I'll start with safe mode and go from there. I appreciate your response.
It's frustrating. Find a usable work around for the time being if you can.
Most times the solution is staring you in the face, step back and rethink it. When did it start? What was done before it started?
Try clearing the data in the Android Setup apk (Android Setup com.google.android.setupwizard Android).
Use a 3rd party app like Package Disabler PD MDM to clear it as doing it in Settings leaves a Null* (presumably) and can't fix it sometimes. I know this particular app (PD MDM) works because I had it happen to me with a USB popup issue a while back.
Clearing Android Setup apk data completely resolved it. If you see Android Setup as a cache app it is the culprit; normally it never runs except during initial setup.
*when data is reported as zero, Nulls are apperantly not reported but still there screwing things up.