Related
Question...
Just upgraded my primary comp and i wanted to mount my Nexus one to try a new kernel.
I plugin the cable but all that happends is that it charges the found, i have no option to mount?
So i look under usb devices at my computer and finds out that it has a "Windows error code 43".
I try and connect it to another computer, its the same.
I just bought 2 new cables, same problem.
OS: Windows 7 64 bit
My Nexus is listed as "Unknown Device" with no option to install the x64 driver.
So my question is... did i brick my N1 so i'm not able to mount it anymore?
__________________________________________
Update:
I sent the device into HTC' repair center, my phone had a Unlocked Bootloader.
Received the phone back today, it had the bootloader locked again and when i turned it on "Update detected" then i got Android 2.2 FRF91 YAY!
Right click on unknown device and select update driver. Then select the appropriate driver either from the SDK or the Android website. It's been discussed multiple times. Search the stickies.
Also if you bricked your phone, you'd be freaking out alot more.
I did -.- I have installed this driver alot of times, and as i wrote, i already tried the x64 driver.
Windows tells me the best suitable driver is installed, which is Unknown device.
I even tried removing all usb drivers to let it search again, i tried adding the driver manually, also failed.
I tried the driver from the SDK and using search/google i was able to find a x64 usb driver, which also fails. Windows error code 43.
Jack Everyman said:
Also if you bricked your phone, you'd be freaking out alot more.
Click to expand...
Click to collapse
Believe me, i am freaked out :/
I have been developing a android app on my laptop for about 2-3 weeks now, and i wanted to mount my phone at my stationary pc.. Now i cannot mount it on either my laptop (with all the drivers installed) or on my stationary pc :/
Here you can see what it looks like
Note: It does not accept any of the drivers posted in the USB Driver topic
This driver set didn't work? http://forum.xda-developers.com/showthread.php?t=613217
chesh420 said:
This driver set didn't work? http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
Nope... I just installed Windows 7 32-bit, the same issue.
All i get when i try the drivers are:
"Windows has determined the driver software for your device is up to date.
Unknown device."
You may want to try a live thumbdrive with ubuntu 10. That worked for my 64bit system. Also you can boot your phone right?
Bricked generally means that you can not turn on your phone, thus turning it into a useless brick. From what I understand this only happens when you update the radio and remove the battery.
If you have changed your rom previously are you running the Desire rom?
I've been running the Cyanogenmod ROM while ive been developing my android apps.
I have been unable to mount it after i installed my new hardware. I should also say that my comp managed to destroy a USB-stick aswell.
Worked before upgrading comp, now it doesn't.
And yes, i am able to boot up the Nexus
If you can boot into your phone its not 'bricked'. Do you have SD card reader on your laptop or desktop, or another smart phone or device with an Micro SD card slot. If so I'd pop up the SD card and try to read it by itself. If that doesn't work I think its just the card not the phone. If it does then something screwy my have happened to your phone.
Jack Everyman said:
If you can boot into your phone its not 'bricked'. Do you have SD card reader on your laptop or desktop, or another smart phone or device with an Micro SD card slot. If so I'd pop up the SD card and try to read it by itself. If that doesn't work I think its just the card not the phone. If it does then something screwy my have happened to your phone.
Click to expand...
Click to collapse
My computer also burned out my Cardreader, so that is not a option either.
However i was able to use the MicroSD reader in my laptop.
My SD card works just fine there.
Search for usbdeview, download it , run it and uninstall your htc usb drivers and then reinstall your X64 driver from the sdk. That should solve your problem.
I know this sounds stupid, but are you using a cable to extend the length of your usb? If so, unplug it.. i had the same problems, it was a stupid cable and i was freaking out.
Re: N1 Brick
No, not that either. Also tried formating the SD card, no luck.
-------------------------------------
Sent via the XDA Tapatalk App
Try following this Guide..
http://wiki.cyanogenmod.com/index.php/Install_the_Latest_Android_sdk
It took me a few goes to get Windows to LOAD the correct Driver
Tried, didn't work aswell... However i do have another question for you guys:
My teacher got a HTC Desire, i asked him to try my MicroUSB (original) cable and see if he could mount with it, he couldn't either, only charging like it does on my Nexus.
So i decided to buy another original HTC MicroUSB cable but i had to wait for the shop to receive the cable from HTC.
Meanwhile i bought this cable and tried it with no luck aswell: http://www.av-cables.dk/computer_ka...a_microb/usba_han_microb_han_1_m_1888_da.html - This one didn't work either.
New question:
Does it require a original Nexus One (HTC) MicroSD cable to mount?
I mean, the cable must be broken somehow too since the Desire cant mount using it aswell.
The shop received the cable today and i should pick it up today.
WebghostDK said:
Nope... I just installed Windows 7 32-bit, the same issue.
All i get when i try the drivers are:
"Windows has determined the driver software for your device is up to date.
Unknown device."
Click to expand...
Click to collapse
This tells to me you did it wrong. Do not search for drivers, do not let let windows determine anything. Tell it you have disk, navigate to your drivers and install them. Give windows a choice and you'll never get anything done.
Cant connect to RSDlite with my droid x
Here is the story.
I could really use some help here. I had originally rooted my droid x and then tried moving the bin to xbin to keep root. But being that i am really new to this i did not know you couldn't update to 2.2 if you had anything custom installed. so i SBF flashed my phone to stock.. left root off, then updated. Being dumb i tried using the root program for 2.1 on my 2.2. says its rooted fine.. it didn't.. no big deal i hope. i don't know if this has any affect as to why this issue is happening but i figured its worth mentioning. Anyways... so now i want to downgrade from 2.2 to 2.1 so i can root and move the bin file properly but i cant. Every time i try to connect to my computer in PC mode, it fails to load/install the driver for my X. my computer recognizes that its the MB810 but fails... so i cannot connect properly to RSDlite in order to perform the flash.. i have tried connecting in all modes media sync... charge only.. PC mode.. etc.. and yes USB debugging is enabled.. i have been trying to figure this out for a couple days now and I'm going crazy. Any help would be greatly appreciated.
BTW i am using windows 7 64bit
UPDATE:
I now have the drivers installed and the phone connects properly to my computer, not sure if i am connecting properly to RSDlite but it still will not allow me to flash the sbf. the sbf i am using is the phoxus -the gift- for the life of me i cannot figure out why it will not let me flash. i open RSD..select my sbf.. connect my phone.. and the start button will not light up.
o0gamerbear0o said:
Cant connect to RSDlite with my droid x
Here is the story.
I could really use some help here. I had originally rooted my droid x and then tried moving the bin to xbin to keep root. But being that i am really new to this i did not know you couldn't update to 2.2 if you had anything custom installed. so i SBF flashed my phone to stock.. left root off, then updated. Being dumb i tried using the root program for 2.1 on my 2.2. says its rooted fine.. it didn't.. no big deal i hope. i don't know if this has any affect as to why this issue is happening but i figured its worth mentioning. Anyways... so now i want to downgrade from 2.2 to 2.1 so i can root and move the bin file properly but i cant. Every time i try to connect to my computer in PC mode, it fails to load/install the driver for my X. my computer recognizes that its the MB810 but fails... so i cannot connect properly to RSDlite in order to perform the flash.. i have tried connecting in all modes media sync... charge only.. PC mode.. etc.. and yes USB debugging is enabled.. i have been trying to figure this out for a couple days now and I'm going crazy. Any help would be greatly appreciated.
BTW i am using windows 7 64bit
Click to expand...
Click to collapse
I would delete the drivers and install the Motorola driver that you can get at Motorola. I have 2.2 which is running great but I still had to reinstall the drivers see that my PC could See my DX.
Before you can do anything your PC has to See your DX with no issues.
Hope this helps
I'm on 7/32
o0gamerbear0o said:
Cant connect to RSDlite with my droid x
Here is the story.
I could really use some help here. I had originally rooted my droid x and then tried moving the bin to xbin to keep root. But being that i am really new to this i did not know you couldn't update to 2.2 if you had anything custom installed. so i SBF flashed my phone to stock.. left root off, then updated. Being dumb i tried using the root program for 2.1 on my 2.2. says its rooted fine.. it didn't.. no big deal i hope. i don't know if this has any affect as to why this issue is happening but i figured its worth mentioning. Anyways... so now i want to downgrade from 2.2 to 2.1 so i can root and move the bin file properly but i cant. Every time i try to connect to my computer in PC mode, it fails to load/install the driver for my X. my computer recognizes that its the MB810 but fails... so i cannot connect properly to RSDlite in order to perform the flash.. i have tried connecting in all modes media sync... charge only.. PC mode.. etc.. and yes USB debugging is enabled.. i have been trying to figure this out for a couple days now and I'm going crazy. Any help would be greatly appreciated.
BTW i am using windows 7 64bit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=760955
Switch the mode of the device when pluggied in and the drviers should load fine. That said change it from PC mode to Windows Sync Mode and you should be good to go.
Follow this to get your computer to recognize your DX running Froyo, you need new drivers.
1. USB Mass Storage without Development Mode on.
2. MotoConnect will prompt; Install.
3. PC Mode with Development Mode on.
4. ADB activate again on leaked Froyo.
Thanks for all the quick replies. I really appreciate it. I will try all of this when I get home. Thanks again. I'll keep you posted.
Sent from my DROIDX using XDA App
I could do everything except "mass storage" on win 7 x64. I finally had to reinstall windows to get it working again. Hope you have better luck.
Sent from my DROIDX using XDA App
ok i have ADB access which i have never used before.. but all the drivers are installed now and i still cant flash the SBF file still using RSDlite.. im so confused.
o0gamerbear0o said:
ok i have ADB access which i have never used before.. but all the drivers are installed now and i still cant flash the SBF file still using RSDlite.. im so confused.
Click to expand...
Click to collapse
which file did u dl, its the full SBF zip file which was almost 300MB.
yea i do have the full sbf. its 235 some megs or something.. i have used it before.. now i reintalled windows and the RSDlite is working and the phone is connecting and i have the option to click the start button but now i am getting this error.
Failed flashing process. Failed flashing process. Phone (0000): Phone is not compatible with multi-interface super-file. (0x703B); phone connected.
any ideas?
o0gamerbear0o said:
yea i do have the full sbf. its 235 some megs or something.. i have used it before.. now i reintalled windows and the RSDlite is working and the phone is connecting and i have the option to click the start button but now i am getting this error.
Failed flashing process. Failed flashing process. Phone (0000): Phone is not compatible with multi-interface super-file. (0x703B); phone connected.
any ideas?
Click to expand...
Click to collapse
no sorry, i just did the downgrade and had no problems.
well as it turns out.. somehow i got it working, but i dont know how.. but i did. so yea. i guess installing a new copy of windows seemed to do the trick. I hope this thead can help others also. GOOD LUCK and thank you all for helping me out.
You can also go to ubuntu and get a copy of linux for free, burn it to disc, then boot into linux from the disc. No install needed. Once in, use SFB_Flash (google it) to flash the SFB file...P3Droid and Birdman both recommed this vs the RSDlite.
Hello,
I read about the froyo rollout and I fired up Kies. It prompted me with an update and I've done it. After that my SGS can't connect to Kies: the app on the mobile keeps restarting and it doesn't stops. The only way I found that lets me connect is to restart the phone, be very quick and connect it very early. That way it will work, otherwise there is no way. I can't browse my files or anything. Is there a way to solve this?
I have the same problem... Most of the time I get the flashing back and forth to the MTP app. Sometimes (very rarely) it connects.
Try clearing your caches. Download Cachemate for root. You need to have root enabled for it to work.
Also search for FileSearcherforKiesFix and look at the guides for that.
At the moment I can't get anything to run but you may get lucky.
Try to remove your sd card and restart
Sent from my GT-I9000M using XDA App
Same issue here on a bell i9000m. I thought i messed up the drivers some how, but im glad to see im not the only one. If you look in device manager, you will notice the mtp driver is not installed properly. Several attempts to manually reinstall driver failed for me.
Win 7 64bit.
Sent from my GT-I9000M using XDA App
Hi.
I am also with Bell on an i9000m and my kies does connect to my device but some things arent working properly.
Example... I check for new firmware (which there isint any yet) and now i get an option to back up my contacts before i flash. I tried this and after about 5 mins it comes bqck saying that there was no response from my device.
This is a bit worrysome for me as i have read some people in europe who were flashing to froyo had the upgrade stop and hang about half way through the process which essentially semi bricked their phone and they had to flash back throuh odin. They said it was like the phone had become "non-responsive".
Anyone else here with a similiar issue as mine? Any advice?
Thanks...
Sent from my GT-I9000M using XDA App
Kies is the worst POS pice of software I have ever tried. I spent 3-4 hours getting Kies to connect to my phone in order to update to Froyo. Installed drivers, unistalled drivers, installed again. Unmounted cards and connected. Unmounted and remounted.
What finally worked for I problem I had with a flashing MTP Application was to delete the contents of the internal SC card.
This only became an issue for me when i used kies to update to jh7. Now everytime I try to connect to kies, my phone not only unmounts both cards, but will not let me remount. i have to reboot the phone just to get the sd's working again. I tried yanking the external and all that did was throw my phone into a borkfest, and that simply makes zero sense. . .
its been a very long while since i updated my phone and used to work fine very slow even when over clocked but fine. the only other thing that happend was very rarely it would restart.
but now the screen wont work all time. it does work some times but not alot. works from reseting the phone. also it may be a loose wire tho because bumping the phone seems to fix it but i think it is just luck that it does.
now the phone is geting calls but nothuing is showing only ringing. i cant even place a call.
what i need to know is what is the latest stable build? and how do i get into the recovery again i cant seem into it again?
im tinking of going back to the original 2.1 but i love the 2.2 only programs ah well i also love haveing a working phone more.
if its a hardware issue simply flashing a new rom wouldnt help i suggest reverting back to stock and take it into a sprint tech store and who knows it could be under warranty still and yes if u flash an ruu theres know way they would ever know it was rooted to begin with.
how do i do this. i can not use adb to push anything to the phone adb wont list the phone in the devices
tutorial i am useing is the stickied one.
how do i revert back to stock
dont see a tutorial but im going to search a bit more
this is old 2.27 official ruu exe when you download it plug your phone into a computer via usb and dont put it in disk mode needs to be charge only im pretty sure then on your computer run the ruu exe and itll update everyhting on your phone and please make sure u have a stable usb cord that wont get disconected easily because all the updates should take around 10-15 min after that youll be on the stock sprint software then u can just update everyhting on your phone by pressing menu settings about phone and software updates but [B]please note that once u runn the ruu you will not be rooted anymore but you can still root easily via z4root after u update everything should u feel the need to[/B] thats all.
http://www.4shared.com/file/2uQunBaV/RUU_Hero_C_Sprint_2276515_R_si.html
thats the download link to the ruu.
thank you the one i was trying wouldnt load in hboot once my phone boots ill try this
yea with this all u need to do is plug your phone into a computer and run the ruu exe and it does everything for you i just couldnt find the right 2.3 ruu but u can still update everything the normal way after this
is there a certain way i connect it because it keeps giving me error 170 usb connection error
edit could it be that i am running 64 bit 7
When it gives you the 170 error with Win7, disconnect and reconnect the usb and re-run the program
Sent from my HERO200 using XDA Premium App
still no go. i did have an error installing sync because i have a 64 bit 7 OS is there a 64 sync install?
one that works because the one that was suppost to work messed up also
I've got 32-bit, sorry I'm not sure if there is a different procedure for 64-bit
Sent from my HERO200 using XDA Premium App
Have you tried a different USB cable? Beyond that, way back when I used HTC sync it was on 64 bit windows 7 fine with no issues. I don't even have it installed now and it ruus fine. If a cable doesn't resolve it, then maybe you just need to delete your USB root hub and force it to redetect USB devices
~maybe I set it too high...
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
This link help me and right now im on the way to updating the phone. thanks everyone who helped ... now hopefully this is going to fix all my problems
have you installed htc hero drivers yet try these out
place them on your desktop then go to devices/printers then click android phone/properties and update drivers dont do an automatic search make sure you choose desktop for the path.
http://handheld.softpedia.com/get/Drivers/HTC-Hero-Drivers-81097.shtml
yea phone so far is now working as it should touch screen and calls thanks again
well, as the title says. Its been like this for a few months now, so I decided reinstall the ROM. I've tried different ROMs and every time it shows up as SM-N900s (Galaxy Note 3) in windows. However, on the phone under settings, it says HTC One. On the newest insertcoin ROM it came up in windows as HTC ONE on first boot, but after that, it went back to being the SM-N900s. As well, I always make sure to do a full wipe before I install a new ROM. I checked the build.prop and it list the model ID as HTC ONE so I have no clue what could be going on here. maybe someone here has a suggestion? I'm thinking maybe this is a possible cause of my mediaserver problem that I just couldn't fix, since it happened in every rom I've tried. phone is rooted, unlocked, and S-OFF.
bbmaster123 said:
well, as the title says. Its been like this for a few months now, so I decided reinstall the ROM. I've tried different ROMs and every time it shows up as SM-N900s (Galaxy Note 3) in windows. However, on the phone under settings, it says HTC One. On the newest insertcoin ROM it came up in windows as HTC ONE on first boot, but after that, it went back to being the SM-N900s. As well, I always make sure to do a full wipe before I install a new ROM. I checked the build.prop and it list the model ID as HTC ONE so I have no clue what could be going on here. maybe someone here has a suggestion? I'm thinking maybe this is a possible cause of my mediaserver problem that I just couldn't fix, since it happened in every rom I've tried. phone is rooted, unlocked, and S-OFF.
Click to expand...
Click to collapse
Its most likely a driver issue on your computer, nothing to do with the phone imo. Uninstall these Samsung drivers and install HTC drivers.
didn't work. removed all traces of samsung drivers and software from the drive and the registry, but still comes up as SM-N900s. I Don't get it. There must be some root cause that's creating all the strange (though minor) issues on my phone.
@bbmaster123 install the latest HTC sync manager after uninstalling every older driver version.. do a full reset if that's possible. Do you end up having this problem with every custom Rom that you flash?
It's not a widely reported issue which leads me to thinking that it's more about your computer than your phone.
Still says sm-n900s after installing sync manager. While I haven't tried many custom roms, it still said smn900s in all the rims I've tried, regardless of kitkat or lollipop. I'll try using my brothers laptop tomorrow when he comes to visit and let you know how it goes
bbmaster123 said:
Still says sm-n900s after installing sync manager. While I haven't tried many custom roms, it still said smn900s in all the rims I've tried, regardless of kitkat or lollipop. I'll try using my brothers laptop tomorrow when he comes to visit and let you know how it goes
Click to expand...
Click to collapse
See question 2 here about how to force the HTC driver, this is a driver problem, the 2nd link below is another guy who recently had the same problem.
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
http://forum.xda-developers.com/htc-one/help/hard-brick-how-fix-t3135013/page2 post 15 onwards.
Seanie280672 said:
See question 2 here about how to force the HTC driver, this is a driver problem, the 2nd link below is another guy who recently had the same problem.
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
http://forum.xda-developers.com/htc-one/help/hard-brick-how-fix-t3135013/page2 post 15 onwards.
Click to expand...
Click to collapse
Thanks, I never would have found that!
My phone already comes up as My HTC in device manager when running normally. in any other mode it comes up as android composite usb. It does try and fail to install some driver during boot though, however it only lasts for about 3 seconds, so I have no time to install anything. as well, fastboot boot recovery.img never worked for me anyway, so instead I always just flashed my recoveries. So I can't get my computer to trigger that driver installer besides rebooting the phone, unless you know a way. But yeah, you may be right about it being my pc and not my phone (for this problem anyway).
bbmaster123 said:
Thanks, I never would have found that!
My phone already comes up as My HTC in device manager when running normally. in any other mode it comes up as android composite usb. It does try and fail to install some driver during boot though, however it only lasts for about 3 seconds, so I have no time to install anything. as well, fastboot boot recovery.img never worked for me anyway, so instead I always just flashed my recoveries. So I can't get my computer to trigger that driver installer besides rebooting the phone, unless you know a way. But yeah, you may be right about it being my pc and not my phone (for this problem anyway).
Click to expand...
Click to collapse
Ignore that HTC MTP driver thing that pops up on you computer whilst your phone is booting, we all get that.
fastboot boot recovery command no longer works unless you are on HBOOT 1.44 I think was the last time it worked, only way to do it now is to flash recovery files.
Seanie280672 said:
Ignore that HTC MTP driver thing that pops up on you computer whilst your phone is booting, we all get that.
fastboot boot recovery command no longer works unless you are on HBOOT 1.44 I think was the last time it worked, only way to do it now is to flash recovery files.
Click to expand...
Click to collapse
I don't think my phone even shipped with hboot 1.44. Or maybe it did. what the hell do I know. I guess then I'll have to wait until I can access my brother's pc later today to test it out
Well, turns out you were right all along. its my computer's fault. I guess I'll just have to mess around with the drivers. Thanks for the help! Too bad though, I was hoping that was the root cause of all the other annoying issues on my phone... oh well I guess I can live with unlocking my phone to change songs!
bbmaster123 said:
Well, turns out you were right all along. its my computer's fault. I guess I'll just have to mess around with the drivers. Thanks for the help! Too bad though, I was hoping that was the root cause of all the other annoying issues on my phone... oh well I guess I can live with unlocking my phone to change songs!
Click to expand...
Click to collapse
Get yourself into device manager and add/remove programs, and remove everything to do with your HTC, the trouble is, windows is a pain for still remembering and self installing the driver again upon reboot, so before you restart your computer, unplug your phone, restart your computer, and look up or get a driver cache cleaner for you PC, run that then restart again, now try reinstall the drivers, drivers firtst ie HTC Sync Manager and then plug your phone in.
I finally fixed it just by uninstalling HTC driver installer and plugging my phone back in. windows right away installed:
USB Composite device
HTC One
My HTC
usb mass storage device
HTC Sync manager serial interface
HTC Android Phone USB Device
I probably am going to fresh install windows anyway, been meaning to for a while, but at least I got this one solved. thanks for the help seanie!
I guess I should make new individual threads for my other phone problems, eh? I got the mediaserver battery drain issue, ACR doesn't record anymore for some reason, and the music controls on my lock screen stopped functioning.
bbmaster123 said:
I finally fixed it just by uninstalling HTC driver installer and plugging my phone back in. windows right away installed:
USB Composite device
HTC One
My HTC
usb mass storage device
HTC Sync manager serial interface
HTC Android Phone USB Device
I probably am going to fresh install windows anyway, been meaning to for a while, but at least I got this one solved. thanks for the help seanie!
I guess I should make new individual threads for my other phone problems, eh? I got the mediaserver battery drain issue, ACR doesn't record anymore for some reason, and the music controls on my lock screen stopped functioning.
Click to expand...
Click to collapse
I guess your on Lollipop, The media server issue can be sorted by going into settings - developer options - use NuPlayer (experimental), uncheck it and restart, not sure about the other issues, but it may be worth reflashing your rom and starting fresh.
As for re-installing Windows, prepare for Windows 10 or download the beta of it, when it goes RTM you can use your windows 7 or 8 key to activate it, and it totally rocks, ive been using it as my main driver now for 3 months.
I'm running kitkat (I like it better) and that option isn't under developer options. The only options I've changed under there are enabling usb debugging(but of course) and force gpu rendering. also using dalvik instead of ART, since in kitkat it was buggy, from what I've heard. I do want to also start a fresh install of the same rom, but I just haven't found the time. I did try reinstalling the rom and restoring my data with Titanium Backup, but it just ended up restoring the problem too. For now, I've just been using system tuner to kill mediaserver right after boot, and the problem goes away until next boot.
I have windows 10 build 10130 on another drive and have been testing it since the first TP, and I agree, its pretty sweet, but I'm not 100% sure yet that I'm gonna switch over to it as my main OS on my main PC. I will be definitely updating my windows 8.1 recording computer to Windows 10 as soon as it goes RTM.
bbmaster123 said:
I'm running kitkat (I like it better) and that option isn't under developer options. The only options I've changed under there are enabling usb debugging(but of course) and force gpu rendering. also using dalvik instead of ART, since in kitkat it was buggy, from what I've heard. I do want to also start a fresh install of the same rom, but I just haven't found the time.
I have windows 10 build 10130 on another drive and have been testing it since the first TP, and I agree, its pretty sweet, but I'm not 100% sure yet that I'm gonna switch over to it as my main OS on my main PC. I will be definitely updating my windows 8.1 recording computer to Windows 10 as soon as it goes RTM.
Click to expand...
Click to collapse
Not heard of the media server bug on KitKat soz.
Still don't like the Windows 10 start menu live tiles, but Start10 fixes that.
I've been using classic start, but I always have to keep switching back to the stock start to launch modern apps, which I only barely use, just stuff like calculator and settings
bbmaster123 said:
I've been using classic start, but I always have to keep switching back to the stock start to launch modern apps, which I only barely use, just stuff like calculator and settings
Click to expand...
Click to collapse
bit off topic really, but see the picts below:
cool, then I'll have to give it a try. Much more like the win7 start menu than win10's stock menu.