Database Develop

SOLUTIONS that worked for me - Unbrick, from Rom to Factory, to Cyanogenmod

I just wanted to relay my experience for anyone who might run across the same problem. There are so many solutions (some good, some bad) that I thought I'd try and help someone else out that was in one of these situations. Keep in mind, the solutions are all here at XDA, I just had to dig and try a few things.
This Captivate was on a Ginger Clone rom (2.2) from about a year ago and I wanted to go to Cyanogenmod. I personally run Cyanogenmod7 (181), and was trying to replicate that.
[Boot-Loop]
I Attempted to clear caches and go straight to Cyanogenmod. This may have been an inexperienced guess that I might be able to do this, but I know a few other folks that manage to do this. I ended up in a boot loop
[Getting to Download mode]
Can be frustrating, but seems to be if you have the usb unplugged, battery out, sim out, put the sim in, battery in, usb in (phone will turn on, so you have to move fairly quickly) and then hit the up and down volume buttons it will go into download mode.
[Go back to Factory]
I tried using the Odin 1 click solution. I believe there are more than 1 versions of this, but it would just get stuck at "Do not turn off target". I decided to try something else. The Java based Hemidal 1.3 aka "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" seems like it is very well written and very easy. It has you update a driver in the mix and it works fantastically.
[Now I'm at Stock 2.2, rooted]
Need to turn on USB debugging, and I was expecting to be able to put
on the rom manager by copying over a file, naming it update.zip but it won't run due to some signing restriction.
[Unable to run any scripts or update.zip]
http://forum.xda-developers.com/showthread.php?t=833423
Basically, you need to turn off signing
[Went off the tracks, bricked the phone]
I decided I would try and apply the Cyanogenmod rom a different way. I went to their wiki and tried to use their Hemidal 1.1.1 update suite and script. I ended up with a brick. I didn't panic, I used the below url and it worked to get me back into download mode. I then used the previously successful Hemidal one click to fix it.
http://www.traemcneely.com/2011/05/...e-possibly-vibrant-kernel-error-black-screen/
I went back to the 3e recovery installer, ran that script, it worked and let me run unsigned code, I installed rom manager via update.zip, and from rom manager I was able to apply Cyanodenmod 7-v181 and then the Google apps and I was happy. Took about 2 1/2 hours to go through all that. Kind-of a pain... happy now.
Rich

Wish I had your kind of luck
I have a Captivate that isn't "bricked" per say but when I plug it into my computer when it's in download mode I only ever get "unknown device". Forcing a driver install causes a code 10 which makes it unusable as well. I have tried 4 different cables and 3 different computers now and tried all of the USB ports on each of the computers I tried at and always get unknown device even with the correct drivers installed. The 3 button trick doesn't work to put it in download mode but using a jig does. I have tried every operating system combo as well heimdall in OSX and Linux says no device connected, and in Windows 7 32 bit and 64 bit I get the unknown device error, also tried Windows XP and get the same error. I have tried 4 different usb cables now as well in each situation with the same unkown device/no device connected error (2 motorola cables, 1 samsung oem cable, and one no-name cable). I was going to gift this to my Dad because he's been missing Android since he gave his HD2 away and went back to a Blackberry.

[Q] O2X bricked after restoring from nandroid backup? [Linux-related]

Hi there, honored experts!
Today I got my precious Optimus Speed bricked, after I successfully restored a recent nandroid backup.
I've been happily running paranoid android for the last months, and often updated the phone with the help of goo.im manager. Today I did a full factory-reset after the CWM upgrade-process, to get rid of the old "disappearing keyboard"-bug. I backed up all my apps and data with superbackup and titanium-backup, and even created an online nandroid-backup (freshly updated nandroid-scripts and patch for my device).
After the reset I had issues to restore everything, since ti-backup often got stuck in batch-restore-processes. Because I couldn't stop the stuck process, it required me to soft-reboot the device a few times. And in the end, it failed to boot.
So I went into CWM, and restored my nandroid-backup. This went fine, and no errors were reported. But after soft-rebooting it, it only showed the LG-Logo-Screen, and nothing else happened. So I tried to get back into CWM - with no luck .
I've tried every possible key-combination I could find, and the only mode I can bring my device into is "S/W Upgrade". In this mode it is recognized by my laptop (running Linux), but rustys recovery fails, because nvflash reports:
Code:
sh ./flash-recovery-ext.sh
Nvflash started
USB device not found
even though lsusb shows:
Code:
# lsusb
Bus 001 Device 017: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
I'm fresh out of ideas - maybe one of you can help me out? Otherwise the only thing I could try now is to turn it back in where I bought it.

I'm no expert at these matters,but I can tell you from my experience because I bricked mine P990 two times and was able to bring it back to life.
In both instances I used Smartflash, found V30a ICS ROM for it and flashed it over it, and it came back to life.
But when you do this,you will have ICS bootloader and you won't be able to install PA or CM since they work on the old bootloader.
Or you can flash it to the stock Gingerbread ROM https://hotfile.com/dl/168874678/8ea13eb/NVFlash_LGP990_V20Q_EuroOpen.7z.html
And I would recommend reinstalling nv flash drivers before,just in case the error is on your computer. http://www.mediafire.com/?cdgwwgkdozht8pw

Also, try All in one kit, http://forum.xda-developers.com/showthread.php?t=2020737 maybe it will help you. I repaired my bricked phone with it a lot of times. Its very easy to use as everything is explained there.

Jasper_bin
this device is 99% unbrickable
just go ahead with the AIOT by SPYROSK (this guy is a silent killer with amazing skills)....link in my signature
it works like a magic....real magic if you read the opening post and do it properly
Thanks

Hi Obersoldat,
I'm currently on the new BL - PA has a spin for the old, and one for the new BL. Is smartflash a windows-binary? Since I currently have no access to a windows-machine :-/.
Hi Make1 and Sreeprajay,
thanks for your recommendation. I'll also hit that thanks button if it helps me solve this, but first I've got two questions:
1st: As said above, I currently have no access to a windows-machine. Therefore I wanted to try working this out with nvflash on Linux. AFAIK this should be possible, even though there would be no nice menu-system. The question is if there's a difference due to the special drivers on windows which are mentioned everywhere? I ask that, because I've successfully rooted my buddies TP-Tablet on Linux with adb, and without any special drivers (which were said to be mandatory on windows).
2nd: What am I aiming for in Spyrosks AIOT? Instantly I'd think option 2B (Change Recovery with NVFlash) might help me. As in ProgMaqs Full-Brick-Repair. Then I'd look into the batch-Scripts, and simply manually execute the needed Steps.

Ok, so I dug up my old windows-tower from the attic, soldered a power-cord that I was missing, and fired it up. Took me more than 2 hours - thats what I meant with "no access to a windows-machine".
I ran Spyrosks AIOT, but no luck . The only possible ways to save this phone, are IMHO the nvflash based methods. But nvflash on windows reports the same error: "USB device not found".
Yes - I installed the driver out of the AOIT - but it seems that it cannot be activated for my phone. I think it's not in the right state to be recognized as a device that would need that driver, so windows won't activate it.
Attached is a screenshot of how the phone appears in my Device-Manager when connected in "S/W Upgrade"-mode.
Do you still think this phone can be saved somehow? I had high hopes as I read that this phone is nearly unbrickable

Come on, please someone help me. I'm not trying to be lazy here, or have someone else do the searching/thinking for me. I just can't figure out how to solve this - propably due to a lack of experience.
I don't think this is a simple problem - but there must be a reason why that phone is said to be 99% unbrickable. I hope I'm not the other 1% in this case.
Anyone?

I would have known what to do if the pc recognized your phone when you've installed drivers because almost exact problem happened to me few days ago.
Okay, now I will suggest random things well, I'm just trying to help :/
I suppose cwm isn't working?
Then about S/W Upgrade mode, have you installed APX drivers? Because when you connect phone in S/W upgrade mode with APX drivers installed then Device manager shows no errors.
You also mentioned that you restored a backup so it means you have latest backup of your system which you wanted to use. Tell me if I'm not correct. Then full wipe of your phone will fix everything, you will just flash a new rom, do the rooting stuff again and then you can restore your backup again.

maybe its because you are on linus, try restoring a STOCK GB KDZ if you are on the old layout, if you are in the new layout use a official LG smartflash, try that on windows and use AIO Toolkit !

Hey, thanks a lot! Actually the last Tip did the Trick!
After I downloaded and installed the full LG phone suite, I was able to restore the phone with the official LG support-tool. During the installation of the PC-Suite one or two new drivers were installed, which then lead to the phone beeing correctly recognized by the Windows 7 on the PC.
So to sum that up, and clarify the questions I brought up earlier:
Can the windows Drivers do more than what the native ones on Linux?
Absolutely yes! Only the drivers which came with the PC-Suite made my PC recognize the P990, which it didn't do before. Propably even the special drivers which come with Spyrosks AIOT depend on them (correct me if thats not true).
Can I restore my bricked phone with only Spyrosks AIOT?
In my case that did not work. Even after installing the PC-Suite and its drivers (including the support-tool drivers) the nvflash based methods in spyrosks AIOT did not find my device, which was connected over USB. But LGs support-tool did, and revived the device .
Hope that helps other people in my situation. The legendary unbrickability of this thing is proven once again
Thanks to all of you (Yesyesyes - I'll hit that button right away!)

[Q] AT&T HTC One COMPLETELY wiped...

a friend of mine went out and got the HTC One, we rooted it and put on a nightly of CM 10.2 - and the phone worked relatively well, very well in fact, except the MMS/Group messaging was causing the phone to lockup and reboot. we've had a group message going on for an eternity involving a few of our friends, so many times a day this would happen.
not knowing what to do, i suggested he download a new rom, the stable or the latest nightly, and erase everything, and reinstall. somewhere in the process he erased everything - including the new rom, the phone is completely blank and in a boot loop. we can boot into fastboot or into the recovery.
and, we are Mac guys, except for an older Vista laptop i have. (to give you an idea on it's age, it has a 25gb hdd).
when we had first rooted it, i used MTP to copy the new rom over to the phone. the stock rom was still in place, the xfer went fine. but now there's no rom on the device, MTP doesn't work, the computer sees it as a 'One' but has no driver, and i'm at a bit of a loss.
i have tried to install the HTC SyncManager to get the phone to connect to my Vista machine with no luck, every time i connect Windows tries to look for a driver and it fails. somewhere in the forums i found a 'universal driver kit' which said it covered the HTC One (called it a Google Nexus Device, but recognized it at least).
however, my admittedly weak knowledge of fastboot and adb has proven not enough to get a new rom on the phone. i don't know if it's drivers or my lacking skillset, and i'd love any suggestions on taking a completely wiped HTC One with Koush's CWM on it, and getting a rom on it.
thanks.

dorf71 said:
a friend of mine went out and got the HTC One, we rooted it and put on a nightly of CM 10.2 - and the phone worked relatively well, very well in fact, except the MMS/Group messaging was causing the phone to lockup and reboot. we've had a group message going on for an eternity involving a few of our friends, so many times a day this would happen.
not knowing what to do, i suggested he download a new rom, the stable or the latest nightly, and erase everything, and reinstall. somewhere in the process he erased everything - including the new rom, the phone is completely blank and in a boot loop. we can boot into fastboot or into the recovery.
and, we are Mac guys, except for an older Vista laptop i have. (to give you an idea on it's age, it has a 25gb hdd).
when we had first rooted it, i used MTP to copy the new rom over to the phone. the stock rom was still in place, the xfer went fine. but now there's no rom on the device, MTP doesn't work, the computer sees it as a 'One' but has no driver, and i'm at a bit of a loss.
i have tried to install the HTC SyncManager to get the phone to connect to my Vista machine with no luck, every time i connect Windows tries to look for a driver and it fails. somewhere in the forums i found a 'universal driver kit' which said it covered the HTC One (called it a Google Nexus Device, but recognized it at least).
however, my admittedly weak knowledge of fastboot and adb has proven not enough to get a new rom on the phone. i don't know if it's drivers or my lacking skillset, and i'd love any suggestions on taking a completely wiped HTC One with Koush's CWM on it, and getting a rom on it.
thanks.
Click to expand...
Click to collapse
1. Download Parallels Desktop for Mac & a copy of Windows 7 x86 (torrents available)
2. Install Android SDK to Windows C drive (exactly to C:/)
3. Download the AT&T RUU here to C:/. (The RUU is an .exe you run with the phone connected to pc in recovery to flash it.) Note: you may run into errors once or twice flashing it, but keep trying and it should eventually work.
4. Connect phone to pc and boot into recovery
5. Run the RUU you downloaded
6. After you finish the flash, reboot your phone if it doesn't automatically.
7. Your phone should now have stock AT&T running.
I hope this helps. -Mike

A Hot Mess, Need Help - M7, S-On, Trouble with ADB

The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.

Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!

eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?

[Q] HTC One thinks its a galaxy note 3 on multiple ROMS

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.