Related
***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own
The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P
Does fastboot detect the device?
janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.
VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)
Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.
After a successful day of unlokcing and rooting my new tablet, I decided to try and experiment with the dpi to try and get some phone based apps working using an app called "LCD Density Modder" I changed to Mdpi - 160, and the tablet turned off. It restarts to the Goolge logo, with an unlocked lock then dies again. What went wrong and how do I fix it? Help me out guys :crying:
Try holding down the power button for 10-20 seconds.
If that doesn't work, leave it plugged in for a couple hours and try again.
Sent from my Nexus 7
It turns on, and fastboot will show up, but Android will not boot. Or if it is booting, it's only a black screen. Is there any way to erase the pixel settings I've applied through recovery or the Nexus 7 toolkit? Or am I totally missing the point?
Edit: The screen does actually appear to be lit. Just black
theshafe said:
After a successful day of unlokcing and rooting my new tablet, I decided to try and experiment with the dpi to try and get some phone based apps working using an app called "LCD Density Modder" I changed to Mdpi - 160, and the tablet turned off. It restarts to the Goolge logo, with an unlocked lock then dies again. What went wrong and how do I fix it? Help me out guys :crying:
Click to expand...
Click to collapse
do you have a custom rom recovery installed? go into your recovery and wipe data/factory reset. or if you flashed a custom rom, go into the recovery wipe data/factory reset and reflash your rom.
I've tried this, to no avail. After the Google logo, a portion of the screen flashes pink and the tablet goes dark again
You can use wugs toolkit to reinstall a factory image, or you can sideload one using fastboot command, wugs method is easier. The file you edited is the build.prop if you still have adb access you could use adb shell to edit the file and change the settings back. Sadly I don't have a clue as to the default settings for dpi in the n7 build.prop.
Cheers Danny
After attempting to factory reset, and trying all these methods I realized that USB debugging is now disabled :crying:
Have you tried booting into recovery (power and volume down) whilst the tablet is connected to the PC via USB? I found that helps you get into recovery sometimes from bootloops etc.
Cheers Danny
Yes, I can get into recovery and fastboot but any attempt at booting Android results in a black screen
Kk come down.. Boot into Fastboot download wugfresh toolkit, and click the flash back to stock and unroot option and check the box that says device will not boot.. Problem solved
Sent from my Nexus 7 using Tapatalk HD
I tried to, but the drivers wont install because it won't boot
Forgive me, I can do all this but I'm a little slow :silly:
Shafe when you rooted your tablet how did you go about it?
Did you use a toolkit? If so which one?
What type of computer did you use, windows, Mac or Linux?
If it was windows which windows was it, XP, vista, 7, 8?
There are known problems in getting drivers to work with certain windows etc. But if you used a toolkit to root then you must have had working drivers at some point during the process.
Any more info you can provide will help get to the bottom of this
Cheers Danny
I used the not so creatively named Nexus 7 ToolKit v 4.0.0 on windows 7. I've had the drivers and just reinstalled them from the toolkit, so they are now on there again. The problem is that I factory reset and since Android won't boot, I have no way of enabling USB debugging
Grab wugs from here
http://forum.xda-developers.com/showthread.php?t=1766475
[Toolkit] Wug's Nexus Root Toolkit v1.6.1 [Updated 11/30/12]
And follow Francis instructions posted above, should sort your problem. You won't need more drivers as you already have them installed.
Cheers Danny
I tried this a couple times, but after trying to flash stock + unroot it says my ADB device was not found because USB debugging isn't on
Found a guide that will allow you to restore stock through fastboot
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
I am not experienced enough with fastboot to really be of more help. Hope this does the trick.
Cheers Danny
Yep, I found this a few minutes ago and am giving it a shot. I'm inexperienced also, but I guess I'll have to learn! Thanks brother
Forget all toolkits and use fastboot, you'll gain twice that way; working N7 and also you'll have gained some knowledge.
It's a lot easier than it seems.
Sent from my Nexus 7 using xda premium
I went from a rooted and unlocked Nexus7, tried to flash a new Rom from recovery, but didn't have GAPPs installed.
I tried to transfer them over when it last booted up, but they wouldn't copy.
I tried to reset with the Nexus tool kit, and its killed my Nexus7 Wifi
All I have is the boot logo with the unlocked symbol.
I can try to restart but it hangs..
I try to start recovery, and all I see is the android lying down with a red triangle over his heart
Is there anyway to recover from this state...
I have No ABD access either...
I've been reading and searching/trying for hours with no luck...
Marty
SH00T said:
I went from a rooted and unlocked Nexus7, tried to flash a new Rom from recovery, but didn't have GAPPs installed.
I tried to transfer them over when it last booted up, but they wouldn't copy.
I tried to reset with the Nexus tool kit, and its killed my Nexus7 Wifi
All I have is the boot logo with the unlocked symbol.
I can try to restart but it hangs..
I try to start recovery, and all I see is the android lying down with a red triangle over his heart
Is there anyway to recover from this state...
I have No ABD access either...
I've been reading and searching/trying for hours with no luck...
Marty
Click to expand...
Click to collapse
ok firstly you should have made a backup from clockworkmod/team win recovery before you flashed anything! as then you could have just reflashed it and been right back to square 1.
secondly stay calm your not bricked. adb does not work while your in fastboot mode. only fastboot mode does. i suspect that you had a bad download and its had an issue while flashing your stock rom.
so, download your prefered android version from here making sure to download the correct type for your n7 IE wifi for wifi and mobile or the 3g version. if you use the wrong type you can brick your tablet.
then simply follow this guide, changing the names of the files to match the one you download. if you follow this guide you will get your device back to stock and boot-able.
just make sure you have a working adb/fastboot folder and make sure you place the extracted files in that folder before you try to flash anything.
good luck pal
http://forum.xda-developers.com/showthread.php?t=2199373 also see here, same issue seemingly...
**Quoted from myself as the issue is the same**
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man
Thanks a heap... Took a while, watched the vid a couple of times, had a hard time extracting the files I needed... WinRAR for the win....
My nexus7 is back up and running....
I will paypal you a beer for you great post..
Cheers Marty
No probkem man, glad I could help
Hello all.
I dropped my N4 the other day, breaking the digitizer. Screen is fine, receives calls and texts etc, but I have no touch functionality at all.
I am not sure I want to fix the phone as it looks a little beyond what I can do. So, I want to sell it as it is for someone else to fix. I am rooted etc on stock rom. Phone is recognised as an android device when connected to my laptop (win 8.1) but I can't access my data at all. I have tried to flash the stock rom again using Nexus 4 Toolkit, but it doesn't find my nexus. I have uninstalled and reinstalled drivers etc. Still no luck.
I booted into recovery, but for some reason I chose a the touch recovery twrp, so that is unusable for me. All I want to do is format the thing to sell it on and be done with it.
Any ideas?
mgolder said:
Hello all.
I dropped my N4 the other day, breaking the digitizer. Screen is fine, receives calls and texts etc, but I have no touch functionality at all.
I am not sure I want to fix the phone as it looks a little beyond what I can do. So, I want to sell it as it is for someone else to fix. I am rooted etc on stock rom. Phone is recognised as an android device when connected to my laptop (win 8.1) but I can't access my data at all. I have tried to flash the stock rom again using Nexus 4 Toolkit, but it doesn't find my nexus. I have uninstalled and reinstalled drivers etc. Still no luck.
I booted into recovery, but for some reason I chose a the touch recovery twrp, so that is unusable for me. All I want to do is format the thing to sell it on and be done with it.
Any ideas?
Click to expand...
Click to collapse
Download the 4.3 factory images, boot your phone in fastboot, connect it to your PC, and use the "Flash-all" script in the factory images zip. It should restore and wipe your phone, and you don't need any touching.
abaaaabbbb63 said:
Download the 4.3 factory images, boot your phone in fastboot, connect it to your PC, and use the "Flash-all" script in the factory images zip. It should restore and wipe your phone, and you don't need any touching.
Click to expand...
Click to collapse
Phone is in fastboot, windows beeps when connection phone up, clicking on 'flash all' brings up the command prompt telling me fastboot isn't recognised as an internal or external command . . . .
Things like debugging are on, as I have the jellybean logo also.
mgolder said:
Phone is in fastboot, windows beeps when connection phone up, clicking on 'flash all' brings up the command prompt telling me fastboot isn't recognised as an internal or external command . . . .
Things like debugging are on, as I have the jellybean logo also.
Click to expand...
Click to collapse
Ok. Install these drivers, then try again:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
abaaaabbbb63 said:
Ok. Install these drivers, then try again:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Click to expand...
Click to collapse
That description really helped on that link. Using that, and then the Nexus 4 Toolkit, it all came together and I have put it back to the stock ROM now. Thank you :good:
Download mode, but cant dl anything from pc to phone now even using odin.
Phone just stuck in boot loop.
Got as far as loading twrp onto it via odin and then when tried search for file just blank folders, nothing in them.
So worried totally bricked it. everyone says get into safe mode, but when try to all it goes to is twrp.
HELPPP!!!!
If you can get into TWRP and aree able to do a complete wipe. It will return your OS to factory settings and fix the boot loop. Other wise try the emergency recovery on Smart switch.
You will need your model information as well as the phone serial number.
Oh,
even phone storage showing "0" in twrp and try wipe just fails.
Cosmic Blue said:
If you can get into TWRP and aree able to do a complete wipe. It will return your OS to factory settings and fix the boot loop. Other wise try the emergency recovery on Smart switch.
You will need your model information as well as the phone serial number.
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
TWRP, tried wipe and few other options on twrp and all says failed.(as does odin now)
The weird thing is was all going fine till went to look for the zip files put onto phone before loading twrp which video said too, but when went to folder that SHOULD show all phones system/pic/video forlders and the 2 zip files I put on phone, it is all gone, folder and all folders showing empty. even internal memory showing as empty.
Magisk-v13 rooting instructions video was what I used.
Have just dl smart switch.
All this because fast charge wasn't working and battery drain fast. Guess thats why seller never sent me the quick charger kit and usb and just a wireless charger with old 0.7mah old samsung charger. 6-7H to charge.
Got another fastcharger but didnt work with the phone.
Just reading about smartswitch and seems can only use if can run from my s7 edge phone. but cant get back into phone.??
Dl it to pc and just tried to run it and yep, saying
app failed to start because its side by side config is incorrect???? Please see app event log to use the command line sxstrace.exe tool for more detail.
Sorry,
Now just more confused
Right,
Out of desperation I found a file, which to a useless tech head like me seemed to ring a bell being a md5 file and can with my odin download, so loaded it up and after 4 tries of
to catch the bootloop with pressing start and holding down and releasing the buttons on phone while starting odin with the file it worked and dl file onto phone, phone restarted after few minutes and then worried for a minute when just flashed the samsung logo, but RESULT. Loaded up, only to ask for pass code, put mine in and said wrong so tried the trick to get into bottloader system reset screen and reset to factory setting AND ALL Good again, just fresh start again.
So for anyone and future info/help the file that saved my AR*E was
cf-auto-root-hero2lte-hero2lte-smg935f.tar
So if need do a search guys or if ok can post a link to one on here if OK ?
imbloodyskintagain said:
Dl it to pc and just tried to run it and yep, saying
app failed to start because its side by side config is incorrect???? Please see app event log to use the command line sxstrace.exe tool for more detail.
Click to expand...
Click to collapse
Updating for future reference/help anyone gets same issue with smartswitch(windows 10)
Google came up with answer,
needed to dl and run.
2008 Microsoft Visual C++ Redistributable package(x86)
This fixed the smartswitch exe file not starting issue.