yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] charlie71:
No idea for remove bottom icon tray?

Anyone with a Hermes have success at this?
[Nexus 6 Q&A, Help & Troubleshooting] Flying Scotsman:
Around February, my phone was working fine and connecting to my PC and being recognised (in both the phone AND PC/Device Manager). Because I was rooted, I used Wug's toolkit to flash the latest factory image at the time (which included the February security update) and kept data as I've done in the past. It was fine for ~2 weeks after that factory image flash and then my phone just stopped recognising the PC, and my PC stopped recognising the phone as a device. It was completely out of the blue, and seems unfixable.

When I plug my phone into my Desktop - it just charges. It doesn't appear in the device manager at all (image below - Device manager WITH phone plugged in and not appearing):

[IMG="Device Manager AFTER phone plugged in"]https://i.gyazo.com/f1c36ffe678cef27a2e297a8912c55b7.png[/IMG]

I've had to do the old 'update drivers' thing in the past with other phones, but they would normally appear under "Phone" or "Other devices" - but both are missing from the list ("Show hidden devices" used in that image). There's also no yellow triangle to say an unknown device has been connected. It just flat out doesn't know it's there. I've also updated/re-downloaded the SDK (and Google drivers) but the phone still isn't recognised.

It got so bad, I had to use USBDeview to uninstall the drivers in the first place because they never appeared. It still didn't help.

On the phone side of things - I'm not given an option to mount the phone as any form of storage. It just behaves like I've plugged it into a charger.

In the USB and Storage settings (image below) - I'm not given an option for ANY form of USB connection.

[IMG="USB and storage settings while plugged into PC"]https://i.gyazo.com/62753727d92543310b03be62fb0e61c6.png[/IMG]

And in the notification shade (again, while plugged into my PC) no option is given. It just charges:

[IMG="Notifcation shade after being plugged into PC"]https://i.gyazo.com/73dd00254d841a9ec13441cfe9d9ead1.png[/IMG]

I've also tried factory resetting the phone, since it charges fine so I don't think it's the charging port but now I've lost root AND the problem is still there. I still can't install OTA updates because in order to get Root, I had to use a kernel which disabled those "this device has been modified" alerts when you boot it, which means the OTA just fails (Error 7 (or 6) - and something about recovery).

In Fastboot, it just says it's 'charging' and makes no attempt to connect via USB. Recovery is the same so it doesn't sound like an Android problem per-se since it affects Fastboot but hardware wise - would could it be?

As a last resort, I've also tried multiple cables (working one for the Nexus 7, DS4 one and a Motorola one) and none of them seem to have helped.

I've also tried different USB ports and on different machines - both running windows 10 and both with the drivers installed but still no luck.

Any help would be greatly appreciated because I'm just sick of this problem at this point.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
You've tried a lot.

My idea is to try to connect to another PC, when possible not Windows 10.

This to check that the problem isn't caused by the phone.
[Nexus 6 Q&A, Help & Troubleshooting] Flying Scotsman:
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.

I'll try it when I get home. Thanks for the reply!
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Wish you luck.

W10-updates are causing issues on my PC
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
[Nexus 6 Q&A, Help & Troubleshooting] Flying Scotsman:
Tried 3 different USB cables and no luck.

I've got a spare microUSB I bought from eBay which I'll need to solder but the only thing I could find on faulty ports were that it doesn't charge right but mine does.

Going to try connecting it to a windows 7 laptop and see where that goes. If it still doesn't work - the only thing left would be the port itself which will be a pain to replace (and still doesn't guarantee it'll be fixed).
[Nexus 6 Q&A, Help & Troubleshooting] Dopamin3:
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
[Nexus 6 Q&A, Help & Troubleshooting] Dvoraak:
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
[Nexus 6 Q&A, Help & Troubleshooting] electricpete1:
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
[Nexus 6 Q&A, Help & Troubleshooting] Flying Scotsman:
Tried it on my Windows 10 laptop as well and it's the same problem. Just tried it on my older Windows 7 laptop as well, and same story.

My older Nexus 7 2012 connects fine to all 3 so I don't think it's the drivers.

Sadly already tried this but what's worse is - I've looked through all the possible 'dropdown' options and the drivers/device doesn't appear but it appears in USB Deview (where I uninstalled them).

Tried both the universal ADB driver and Google's own one from the SDK - sadly didn't work in the end.

I'm beginning to think the same to be honest. It doesn't connect in Fastboot, which leads me to believe it's more hardware than software because if it were Android itself screwing up - it would at least work in Fastboot as that doesn't touch Android.

It doesn't mount as anything, so I can't access my files on any of the systems I've tried. I've even tried my younger brother's laptop and it doesn't 'see' it (but his Nexus 4 connects and works just fine).

I bought my Nexus 6 ~6 months after release so it's out of warranty (what a time for it to run out of warranty). I bought a new USB port from eBay ages back so I might have to fit it myself since all the repair shops I've contacted would take ~3 days to do it and I need to have a phone.

I really hope replacing the port will fix it. It charges fine, which makes me slightly worried it won't work (as it's not an obvious port issue) but I can't think of anything else which could be the problem.

Thanks to everyone who's replied though! I'll see how the USB replacement works out.
[Nexus 6 Q&A, Help & Troubleshooting] qprjim:
Hello all, long time lurker 1st time poster....

I've never really felt the need to post because i normally just do a search and work things out for myself, but i'm now having the same problem and noticed this around 2-3 weeks ago after trying to copy some pictures i'd taken onto my Laptop from my Nexus 6 and it not being recognised, only charging.

I've tried EVERYTHING (apart from reverting back to Windows 7) mentioned in this thread and in a couple of the other threads i've found where a few Nexus 6 users have had the same problem. I'm now stumped for ideas.

My Nexus 6 runs as flawlessly as usual, no battery drainage, stutters etc.

I'm currently running Temasek's 18.2 (5.1.1) rom, and have been using it now for a long time (probably for 8 months or so with absolutely no problems whatsoever). I've updated to MM a few times and tried a few different Roms, but to be honest i just found that LP worked better for me so have always just reverted back to the last official LP 5.1.1 LVY48I Rom using Wugfresh's Tool Kit (i know i know :o , but having rooted/played about with other Samsung/HTC Phones in the past, i just preferred to use it) and then restoring my backed up reliable Temasek's 18.2 Rom.

So, what else can i say....well, i called Motorola around a week ago for some advice, just incase there is a potential warranty claim (because my Nexus 6 is only around 9 months old), but as i have a Custom Rom on it, they said that there is nothing that they can do.

I do have an official clean 5.1.1 Rom LMY48M that i fortunately backed up to my TWRP Folder on my laptop just after installing TWRP+rooting. I did 1st of all also try connecting my Sandisk Ultra Dual USB DRIVE 3.0 to my Nexus with the Rom on there, but the Nexus just doesn't even know that the USB Drive is connected, so I have had to send it via bluetooth to my Nexus from my laptop, as that was the only way to get it on there. I found that Zipping the file 1st, sending it to my Nexus via Bluetooth and then extracting it once i'd received it saved hours in time because the file was too large in its original form (something like 4+gb down to 1.9gb). I've also tried a few other LP Rom's in the last couple of weeks, hoping that maybe i'd accidentally switched a setting off or something and that the phone would correct itself and my connection problem would correct itself but i've had no joy.

NOW...........................probably a silly question :o :o but it's the only other way i can think of returning to Stock for a potential warranty claim. I know that i can install the official 5.1.1 Rom i backed up via TWRP because i've tried, but is there a way to remove Root+TWRP and return to Stock Recovery+remove root without using a PC ? I'm pretty sure that there isn't but feel the time is right for me to ask the Question as i'm really not 100% sure.

Many Thanks in advance for helpful advice given, like i've said at the start of this post, i've held off asking Questions before because i had no real need and just searched :angel: , but this has really stumped me :confused: .

CHEERS
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
Some quick thoughts.

1. The Motorola rep you spoke to I think read from a script and didn't realize you were talking about the Nexus 6. As this is a developer device, having custom software on it should make no difference for warranty purposes. If I am mistaken however, read on.

2. If you're going to install a stock ROM on the Nexus 6, a PC will be required, especially if needing to replace TWRP with the stock recovery. So why not download the latest Android 6.0.1 image from Google's Nexus firmware page and flash that? There's no point in reverting to an Android 5.x image simply for a warranty claim.
[Nexus 6 Q&A, Help & Troubleshooting] qprjim:
Many thanks Strephon Alkhalikoi for your quick reply and sorry for my slow 1 (work was getting in the way....)

1 - at some point today, i hope to chase my potential problem up with Motorola or possibly Expansys because i purchased the Nexus 6 from them via Play.com/Rakuten.co.uk

2 - The 5.1.1 Stock image that was going to be put on the Nexus was only a normal TWRP back up i'd saved by chance straight after flashing+rooting that i had saved to my Laptop. There is no way for me to flash any new Stock software because my Nexus is just not recognised by my Laptop. I've tried installing+uninstalling drivers/Minimal ADB Fastboot file/Wugfresh's Toolkit, plus Developer options usb debugging on/off etc and Settings/Storage/USB Connection (3 little dots top right) which gives me 2 options Media Device (MTP) + Camera (PTP) but after changing either, still no sign of connection, just charging.

As it stands it works fine on 5.1.1, but with me not being able to Flash any Stock Roms because of my Laptop connection issue, it will be forever more on LP. I could put up with that but obviously i need to try and sort this out also because i can't transfer normally any media files backwards/forwards (only via the much slower Bluetooth) and it will affect any future sell on value when it's time to move on.

Many Thanks once again
[Nexus 6 Q&A, Help & Troubleshooting] JonesL:
SBE repaired my nexus 5, when it was rooted/unlocked.

Is there any damage to the usb port? Never tell the customer service rep that your device.
[Nexus 6 Q&A, Help & Troubleshooting] qprjim:
Cheers for the reply JonesL

As far as I'm aware, there isn't any damage to the USB Port. I did say I thought that that might be the problem but she said if it was the reason, then the phone wouldn't charge at all.

I could still send it in and hope that on the off chance they don't check for Root, but i will be liable for the postal returns plus the hassle of being without a mobile whilst it is away. Also, I've now given my IMEI number and a couple of other details so I'm sure I'll now flag up on their system when its checked.

Oh well....
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] sanathxda:
Respected sir,

SGSA has only 650 mb of ram so.. we wont be able to play some heavy games and it lags a looooooooot . So i had read about swapping but our device is mounted as sdcard 0 and sdcard 1 so can anybody plz help me how to achieve this guyz?

Tnx in adv
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] amit020:
root ur phone and download roehsoft ram expander from play store and which version of android u r using
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] sanathxda:
I know that root is a must and even tried that app it didn't work :( .... I am on 5.1.1
[Sprint Samsung Galaxy S6] keishbby:
I am looking to root my Sprint Galaxy s6 the build number is G920PVPU3CPD3. I had the settings for the APN set to get free hotspot. When I did the upgrade they made took the option away. I don't have access to it anymore so rooting my phone is my next option but I don't want to trip Knox on the phone. It's only a few months old. Can anyone help with this?

Thanks

Keishbby
[Sprint Samsung Galaxy S6] anderd:
Currently the only rooting methods available WILL trip knox.
[Nexus 5 Q&A, Help & Troubleshooting] mike99:
Hi,

I have TMO Nexus 5, 2.5 yrs old. Suddenly, my phone shuts down with more than have battery charge remaining. I cannot do anything by pressing any buttons. it is dead. If I connect to the charger, phone goes on the loop. The google sign appears on the screen, then it goes dark in a second or 2, then sign appears again, and so on. I can access the bootloader menu but only for a second. Then the phone goes off again. I cannot even properly turn it off, even when press power/volume up/down keys together. It just will not shut off.

Happened a few times before, but I was able to revive it by charging 3-4 hours and eventually it stopped looping. This time, no luck. Between the episodes like this, it worked just fine. Stock, never rooted, latest android 6.01.

Bad battery or something else? I did order the battery and will try to swap it, but would like to know if this could be anything else.

Normally, I would try to simply remove the battery and then put it back, but this battery is a little trickier to remove. I do not want to do this until I decide the battery needs to be changed.

Thanks very much.
[Fire TV Themes and Apps] d3adpool:
I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?
[Fire TV Themes and Apps] deanr1977:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
[Fire TV Themes and Apps] d3adpool:
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.
[Fire TV Themes and Apps] deanr1977:
Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
[Fire TV Themes and Apps] LittleBill21:
i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x

both give the identical error, yet other apps are getting su control just fine?

any idea's? [MENTION=3991724]rbox[/MENTION]
[Fire TV Themes and Apps] Y314K:
I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.

I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.
[Fire TV Themes and Apps] Y314K:
[MENTION=728928]d3adpool[/MENTION] , [MENTION=3971688]deanr1977[/MENTION] , [MENTION=7571060]LittleBill21[/MENTION]

Where you guys ever able to come up with an answer or fix for this issue ??
[Fire TV Themes and Apps] d3adpool:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
[Fire TV Themes and Apps] phresch:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)

I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.

The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.

It seems like this just affects 1st-gen firetv boxes.

The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.

I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
[Fire TV Themes and Apps] phresch:
I had the su & /sdcard/ problem too.

I'm going to guess that things went something like this (they did for me):

1] installed twrp & pre-rooted bueller ROM

2] discovered that the included superSU had no GUI

3] replaced superSU with another version to access a GUI

4] discovered su/sdcard bug

5] found & flashed the zip fix

6] tried to su /sdcard/ & still doesn't work

I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..

However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.

I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.

You have a couple of options, both will give pretty close to the same end result:

First option:

1. re-flash your firmware ROM

2. flash the zip to fix the mount namespace problem

3. install a different SuperSU with a GUI

Second option:

Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.

Hopefully that helps
[Fire TV Themes and Apps] king200:
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?
[Fire TV Themes and Apps] Y314K:
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?

I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.

I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from [MENTION=3991724]rbox[/MENTION] since I really do not want to accidentally loose my Fully unlocked bootloader.

Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?

Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.

Either way ES File Explorer / Root Setting will not work for your right. Not matter what?

Hope I can get past this bug before updating my other 3 FTV1's.