Related
Basically I tried to install acid audio mod 8 on my phone but did not realize that it was xperia only, so now it is stuck on "android is upgrading"/"starting apps" everytime i reboot. I tried flashing back to acid audiomod 7 and that didnt help. I am running Slimrom with franco kernel btw. I also tried wiping dalvik cache, just cache, and formating the phone from recovery, none of that helped. I dont have any roms saved on my phone or any backups so I am stuck like this and I cant connect my phone to my pc, my pc would recognize it but it wont show up in my computer so I cant access it to to save another rom to it. I tried connecting via recovery (where it goes "download mode do not unplug the device until the process is complete") But that doesnt work, the it would try and install drivers for two "Full JellyBean on Mako" (so it seems like slimrom is based off of a older cm 10 build), but it would come back with no drivers found. When I am in recovery via clockwork my pc recognizes my phone as "Android" but again I still cant do anything with it. Someone please help! I need to fix it by tonight because I am going camping tommorow with family for a few days so having my phone working is a must .
Thanks for those that try to help!
PS I tried using nexus 4 toolkit to reinstall drivers that didnt help.
Deleted
Sent from my Nexus 4 using xda app-developers app
help!
please help! Im searching for what I can do but i cant find anything at all.
What exactly do you mean it recognizes as android? Do you mean from device manager? Does it recognize it via adb? If so you can use adv to push or side load a rom
Sent from my Nexus 4 using xda app-developers app
marsdta said:
What exactly do you mean it recognizes as android? Do you mean from device manager? Does it recognize it via adb? If so you can use adv to push or side load a rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Im not sure how to do that, lol, im still pretty noob, but yeah I mean from devicemanager.
I would install the SDK . you could also use the adb files of the toolkit if you want
When you locate the adb files. Open a command prompt (shift right click ) and type adb devices. To check if its being recognized. If it is we can push a ROM.
Download ROM of choice and place it in the same folder as adb
Then type the command
Adb push nameofrom.zip /sdcard/nameofrom.zip
Or if you near a PC I can help out via teamviewer
Sent from my Nexus 4 using xda app-developers app
marsdta said:
I would install the SDK . you could also use the adb files of the toolkit if you want
When you locate the adb files. Open a command prompt (shift right click ) and type adb devices. To check if its being recognized. If it is we can push a ROM.
Download ROM of choice and place it in the same folder as adb
Then type the command
Adb push nameofrom.zip /sdcard/nameofrom.zip
Or if you near a PC I can help out via teamviewer
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Could you please help out through team viewer lol? I know I have adb sdk installed, just dont know how to use it.
lemon07r said:
Could you please help out through team viewer lol? I know I have adb sdk installed, just dont know how to use it.
Click to expand...
Click to collapse
LEARN.
exbo, no comment, not even worth say anything lol maybe try learning manners.
Anyways thank you marsdta for helping me through team viewer .
Download the factory image, learn to use adb or try the toolkit to flash it back to stock, and never touch your phone again. As far as drivers, try this. http://junefabrics.com/android/downloadold.php
marsdta said:
What exactly do you mean it recognizes as android? Do you mean from device manager? Does it recognize it via adb? If so you can use adv to push or side load a rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hello sir I to have the same problem I tried to install beats audio on my gionee elife e3 mobile it was also having same problem but I am using windows 8.1 it was detecting as android phone but not android device so please help me over team viewer I have all drivers installed for it though when I select update driver of unknown device as android device it dosent show android adb interface but when I select as android phone it shows android adb interface and in sdk when I use adb devices it dosent show any name so where can I side load to so help me please....
lemon07r said:
Basically I tried to install acid audio mod 8 on my phone but did not realize that it was xperia only, so now it is stuck on "android is upgrading"/"starting apps" everytime i reboot. I tried flashing back to acid audiomod 7 and that didnt help. I am running Slimrom with franco kernel btw. I also tried wiping dalvik cache, just cache, and formating the phone from recovery, none of that helped. I dont have any roms saved on my phone or any backups so I am stuck like this and I cant connect my phone to my pc, my pc would recognize it but it wont show up in my computer so I cant access it to to save another rom to it. I tried connecting via recovery (where it goes "download mode do not unplug the device until the process is complete") But that doesnt work, the it would try and install drivers for two "Full JellyBean on Mako" (so it seems like slimrom is based off of a older cm 10 build), but it would come back with no drivers found. When I am in recovery via clockwork my pc recognizes my phone as "Android" but again I still cant do anything with it. Someone please help! I need to fix it by tonight because I am going camping tommorow with family for a few days so having my phone working is a must .
Thanks for those that try to help!
PS I tried using nexus 4 toolkit to reinstall drivers that didnt help.
Click to expand...
Click to collapse
i had the exact same problem, it was stuck at starting apps, then suddenly i heard my phones msg toe go up, so i thought id randomly give a call to the hone, and it rang and showed up the diler, i rejected, jumped in settings, and as it turns our, i had an old version of nova launcher which wasnt compatable with art. and since it was my default launcher ,even though it fc'd android kept trying to launch it i set lg home as default and now its fine phone is lg g2
you can do what is stated above or you can wipe data using stock recovery, not needing any pc, but you will loose all your data
shriom_manerker said:
i had the exact same problem, it was stuck at starting apps, then suddenly i heard my phones msg toe go up, so i thought id randomly give a call to the hone, and it rang and showed up the diler, i rejected, jumped in settings, and as it turns our, i had an old version of nova launcher which wasnt compatable with art. and since it was my default launcher ,even though it fc'd android kept trying to launch it i set lg home as default and now its fine phone is lg g2
Click to expand...
Click to collapse
Download stock images etc
Go into fastboot, use the fastboot toolkit to flash them. That's what I did cause recovery was being weird. This was a while ago though. I dont have a nexus 4 anymore so I can explain how to do it in detail, i broke it and now im stuck with my dumb iphone 4s.
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!
can anyone tell my y my adb does not see my device?? i downloaded the drivers that i believe were the ones for the vs980, if those are the wrong ones please tell me.
i still managed to get root but now i need to push recovery but it doesnt see my device....
Lg stock drivers don't seem to help pc to see phone in recovery I installed pdanet and downloaded lg drivers through it and now adb works.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
Lg stock drivers don't seem to help pc to see phone in recovery I installed pdanet and downloaded lg drivers through it and now adb works.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I owe you more than that thanks. This is incredibly useful info!
Backstory:
Flashed 800 radio on 802 (curiousity...)
Didn't have 802 radio on device to flash back
802 in bootloops
google usb drivers wouldn't install
@lingarajug saved my sanity and taught me something
I love how much I can learn on xda-dev...
Hahahahahhahahaha they say curiosity killed the cat, I was in the worst situation like you were but I tried copying new Rom and gapps to sdcard and flash and went into recovery and curiously cleaned everything in advanced wipe and left with phone with no Rom to boot and no file to flash I did sleep all night and finally my old ideas came through and found pdanet and since then have been spreading this message around, glad that it helped u.
Sent from my LG-D800 using xda app-developers app
Hello everyone,
Last night I was wiping my phone in TWRP to reinstall a ROM and without paying attention, I accidentally hit clear internal storage when I was checking things to wipe. Now I have nothing to flash to it in ADB and no ROM loaded to the phone. I have ADB on my laptop. How can I use that to push a ROM file from my laptop to my phone so I can use it from TWRP to flash some firmware back onto my phone and boot it up again? I have very little experience in ADB, so any help that can be give with ADB commands would be helpful and appreciated. Thanks in advance.
Here you go, buddy!
http://forum.xda-developers.com/showthread.php?t=1667929
Awesome! Thanks! I wish I had seen that last night. It sounds like it's actually very simple. Now if only I wasn't at work without my phone...haha. I'll give it a shot when i get home.
I've been trying what that post says to do, but I can't get my PC to recognize the phone. I installed the drivers from LG's site for the VS980 (yes, that is my correct model). My computer runs windows 7. When I plug the phone in, my computer says it's an unspecified device and fails to find any drivers to install. Does anyone know of where I can download drivers for my model? Thanks again.
vPro97 said:
Here you go, buddy!
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
No, "adb sideload name.zip" is the correct way. There are very few devices that have recovery with no sideload functionality. You need to go into TWRP - Advanced - ADB Sideload.
Sent from my LG-D800 using XDA Free mobile app
penser said:
No, "adb sideload name.zip" is the correct way. There are very few devices that have recovery with no sideload functionality. You need to go into TWRP - Advanced - ADB Sideload.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Actually, I ended up using the push command. I just had to install the ADB universal driver here. Thanks for the help!
ATT 4.2.2 MDL. I flashed CyanogenMod 10.2 earlier today and it was working fine. Then I installed gapps, cuz, well I need gmail and calendar and the play store. Then my keyboard disappeared and I couldn't set CM up. Googling leads me to believe that it's an issue with the specific gapps package, get the proper package. Get the zip uninstaller for the old gapps. Uninstalled old. Reinstalled new. Then Cyanogenmod has constant popups about gapps failing and cyanogenmod setup wizard failing, to where they are non stop, can't do anything with it. Okay. So I started from scratch, same issue. So then I tried again, thought I did proper procedure (wiped, etc.), but now there's no TWRP folder to pull my CM from to install? How did that disappear? Yes I realize I sound like a moron. Point duly noted. Anyone reading this, where do I go from here? I'm in TWRP now and just... lost.
Do you still have cm on your sdcard? Just install it. Never heard of a gapps uninstaller. Maybe that did something
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Do you still have cm on your sdcard? Just install it. Never heard of a gapps uninstaller. Maybe that did something
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
every directory is empty hunting around the 'Install' area. There used to be a TWRP folder that held my CM zip, gapps zip, etc. It's gone.
Wittyusernametaken said:
every directory is empty hunting around the 'Install' area. There used to be a TWRP folder that held my CM zip, gapps zip, etc. It's gone.
Click to expand...
Click to collapse
Can you boot into the os? Or boot into recovery? If you can you can get cm or another rom on to your device and flash it.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Can you boot into the os? Or boot into recovery? If you can you can get cm or another rom on to your device and flash it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm in TWRP right now, otherwise it hangs on the Samsung Custom screen. How do I get another ROM from TWRP?
jd1639 said:
Can you boot into the os? Or boot into recovery? If you can you can get cm or another rom on to your device and flash it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload doesn't seem to work. It's selected from the TWRP and says Starting ADB sideload feature. Then in my terminal I get
"error: device not found"
"error: device not found"
do not understand. by the TWRP page it should work? My command is "adb sideload C:/Users/tho/cm-10.2-20130811-noobdev-jflteatt.zip"
Wittyusernametaken said:
ADB sideload doesn't seem to work. It's selected from the TWRP and says Starting ADB sideload feature. Then in my terminal I get
"error: device not found"
"error: device not found"
do not understand. by the TWRP page it should work? My command is "adb sideload C:/Users/tho/cm-10.2-20130811-noobdev-jflteatt.zip"
Click to expand...
Click to collapse
While the phone is in recovery, you should be able to use "adb push <source_file> /sdcard/filename" to push the ROM to your sdcard. You can then flash it from the recovery.
jmjoyas said:
While the phone is in recovery, you should be able to use "adb push <source_file> /sdcard/filename" to push the ROM to your sdcard. You can then flash it from the recovery.
Click to expand...
Click to collapse
Just tried that, I'm getting "The system cannot find the path specified" and then when I tried it again, "Error: device not found"
I changed the filename to cm10.2.zip for brevity and it's in the same directory as adb. Any other ideas?
Wittyusernametaken said:
Just tried that, I'm getting "The system cannot find the path specified" and then when I tried it again, "Error: device not found"
I changed the filename to cm10.2.zip for brevity and it's in the same directory as adb. Any other ideas?
Click to expand...
Click to collapse
When in recovery type adb devices. Is your device recognized? If not you have a driver issue
Sent from my Nexus 5 using XDA Free mobile app
If jd's suggestion works and your device is recognized. Try it with no .zip on end. If you are using windows.
jd1639 said:
When in recovery type adb devices. Is your device recognized? If not you have a driver issue
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I get "List of devices attached" but then it shows nothing. Interesting since earlier it was the only way to for me to get my phone to reboot into TWRP so it had to have been seeing it at one point. CRAP.
Wittyusernametaken said:
I get "List of devices attached" but then it shows nothing. Interesting since earlier it was the only way to for me to get my phone to reboot into TWRP so it had to have been seeing it at one point. CRAP.
Click to expand...
Click to collapse
Go to your device manager with your phone plugged in. There's probably an asterisk on one of the usb ports. Update that driver manually. Go to let me pick from a list on the computer. Pick andriod adb interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go to your device manager with your phone plugged in. There's probably an asterisk on one of the usb ports. Update that driver manually. Go to let me pick from a list on the computer. Pick andriod adb interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I've got Other Devices and then underneath it SAMSUNG_Android. Having Windows update the driver does nothing, it cannot find the driver. Manually pointing it to the folder C:\Users\tho\Downloads\SAMSUNG_USB_Driver_for_Mobile_Phones which contains the driver does nothing as well I get another message about "Windows was unable to install your SAMSUNG_Android Windows could not find driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Except that driver I got was from the Samsung website? So that makes no sense. I feel like I'm going in circles. What do I do now that Windows won't install any drivers?
I thought installing Keis installs the drivers??.
You could install then uninstall Keis.
Wittyusernametaken said:
I've got Other Devices and then underneath it SAMSUNG_Android. Having Windows update the driver does nothing, it cannot find the driver. Manually pointing it to the folder C:\Users\tho\Downloads\SAMSUNG_USB_Driver_for_Mobile_Phones which contains the driver does nothing as well I get another message about "Windows was unable to install your SAMSUNG_Android Windows could not find driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Except that driver I got was from the Samsung website? So that makes no sense. I feel like I'm going in circles. What do I do now that Windows won't install any drivers?
Click to expand...
Click to collapse
Go to below where you search for a driver and to where it says let me pick from a list on the computer. Kies should install the property driver but sometimes doesn't. If you use kies, do what rug said and uninstall it except for the drivers. Kies is a pos
Edit, oh by the way, you're definitely not bricked. You'll be able to get your device working again.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go to below where you search for a driver and to where it says let me pick from a list on the computer. Kies should install the property driver but sometimes doesn't. If you use kies, do what rug said and uninstall it except for the drivers. Kies is a pos
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No. I don't have Kies. Previously I was frozen on 4.2.2 MDL and paranoid Kies would update me so no need for it. When I search for it and pick Samsung Android I get to another window that gives me the option of
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.510.0 [5/23/2013]
There's no option for Kies or such.
Wittyusernametaken said:
No. I don't have Kies. Previously I was frozen on 4.2.2 MDL and paranoid Kies would update me so no need for it. When I search for it and pick Samsung Android I get to another window that gives me the option of
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.5.916 [9/16/2010]
Samsung Android ADB Interface Version: 2.9.510.0 [5/23/2013]
There's no option for Kies or such.
Click to expand...
Click to collapse
Pick the newer one and let it do it's thing
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Pick the newer one and let it do it's thing
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm getting somewhere now. Recognized now on adb devices. Pushed the CM file. Flashing now. Is it advisable to Wipe cache/dalvik or just reboot straight in after flashing CM? Thank you so much for your help
Wittyusernametaken said:
I'm getting somewhere now. Recognized now on adb devices. Pushed the CM file. Flashing now. Is it advisable to Wipe cache/dalvik or just reboot straight in after flashing CM? Thank you so much for your help
Click to expand...
Click to collapse
I'd try first just dirty flashing it, no wipes that way it'll save your current settings
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'd try first just dirty flashing it, no wipes that way it'll save your current settings
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sweet. I'm in CM. It's not starting the setup wizard, that's odd, but w/e. Do you have any suggestions for google apps (gmail/calendar/play store) since gapps led me on the rabbit trail to destruction. All I want is slimmed down, fast, no bloat and the three previous gapps, but it seems like this is gonna be much trickier than I thought.