Showing posts with label Being. Show all posts
Showing posts with label Being. Show all posts

Friday, 16 October 2015

com not being recognized



Guys I'm trying to root with the cubed root but when I go into download mode and open command prompt to identify the com ports I get an error not recognizing the ports should I download another version of the tool used to do it or is something wrong with the device??? Any assistance appreciated



Monday, 12 October 2015

Phone not being detected on PC



Hi All,

Not posted in here for a while but always the first place i come when I have any issues.

Received my Z5 today. Everything is sweet but I cant seem to get the phone to connect to my PC so Sony Companion doesn't pick it up. There's nothing in Device manager and nothing comes up in the notification bar like it did on my Z. The phone does charge and vibrate when the USB cable is initially plugged in. Am i missing something obvious or is there something i need to do.
I have tried it on both Win 7 and Win 10. Installed the companion first on win 10 but not on Win 7. I haven't tried sony's supplied cable as i cant see this helping.... (trying it now)

Any help would be appreciated

Cheers



Problem with the phone being off and charging



So, i have a issue when the phone is completely off. And it's when i plug in the charger the screen turns on with the charging animation and then





This pops up (Not my screenshot, found it on a reddit thread with the similar problem)

Now the question i have. Is there a permanent fix for it? I know if you hold the power button with volume up at the same time it'll start up after a while. But i'd just like my phone to start when i hold the power button.

Thanks in advance!

Edit: I propably should've posted my ROM and such. I'm using the stock ROM from a german forum named handy-faq. The reason for that is because i accidently wiped my original rom when i flashed a custom one.



Sunday, 11 October 2015

LG G3 not being recognised, USB not transferring files



I'm hoping someone can help. I have an LG G3 phone and is factory unlocked and running Lollipop 5.0. When I first got the phone (second hand), I was able to connect the phone via USB to my PC and was able to transfer files back and fore no problem. Until about 3 weeks ago, I am now unable to do this. The PC won't recognise the phone at all, all the USB connection does is charge the phone and I can see no option to get the phone to change to file transfer mode.

I had a look at Storage in the settings menu and I don't have the three dots that some people have spoke about. I have factory reset the phone and this hasn't fixed it.

I have tried using a different USB cable, this was the same. The drivers are installed (phone was recognized before). I have also tried the LG Suite, again same result. I also had a look in Device Manager for ACER something or other and this wasn't there.

I am currently having to use Bluetooth to transfer files back and fore to my PC and this is a bit slow. I'm assuming that an update LG have done has somehow broke the USB settings. I am also unable to root the phone (tried this before the USB stopped working and nothing worked) and possibly go back to KitKat 4.4.2 to even try that.

My phone has software version V20u-EUR-XX, Kernel Version 3.4.0 and build number LRX21R.A1439960697. There is no update available for my phone in the Software Update center.

After quite a bit of searching, it seems that this is a common issue but I have not found a solution to this. Can anyone help? Is there any firmware or software that I can try?

Thanks.



Thursday, 8 October 2015

Tuesday, 6 October 2015

Messenger is not being kept under hibernation for some reason



Basically after one of the latest FB Messenger updates, it's being woke up for some reason. Unrooted, Moto X 2014 retail running 5.1 and running current 2.7.1 release - I can't pinpoint the reason of the wakeup since the device isn't rooted but apparently it said "Wifi was scanned" other then GCM probably.

For further info, FB Messenger version is 42.0.0.17.137. Had a couple updates since it started but still happening.