Database Users

Why won't adb see my device?

Trying to go from paranoid android to stock 4.2, and adb won't see my device, what is the deal?

ok, nevermind

alright heres the deal, in fastboot, it won't see my device, what is the deal?
I type in "Fastboot" devcices, and it just goes to the next line. Argh i'm getting pissed

Anybody? HELP!

Cor-master said:
Anybody? HELP!
Click to expand...
Click to collapse
Have you installed the Google USB drivers from the SDK, this guide will help you out.
http://developer.android.com/tools/extras/oem-usb.html

Cor-master said:
Anybody? HELP!
Click to expand...
Click to collapse
Have you got the right drivers on your PC?
Edit: Somebody beat me to it.

I've had a folder on my desktop I've been using since I rooted my flyer back in March, and my windows sees it in the bootloader, but cmd prompt doesn't.

here's a screenshot. God I've done this crap a million times, adb works inside android, but in the bootloader it does nothing, I hate getting stumped on simple crap.

Cor-master said:
here's a screenshot. God I've done this crap a million times, adb works inside android, but in the bootloader it does nothing, I hate getting stumped on simple crap.
Click to expand...
Click to collapse
I think Windows "sees" the device as a different device when it's in Fastboot mode versus being in Recovery mode, vs. fully booted.
Try force installing the driver per these directions:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/

Cor-master said:
here's a screenshot. God I've done this crap a million times, adb works inside android, but in the bootloader it does nothing, I hate getting stumped on simple crap.
Click to expand...
Click to collapse
In device manager, is there a device with an unknown driver (warning sign)? when your N7 is connected to your PC?

I just downloaded wugs root tool kit, reinstalled drivers throught it, it worked completly...yet if I manually type commands I get nothing...ugh..
screw it I wanted to do it manually so I could try and keep my data, but so be it.

I am having the same issue. Google drivers installed while device was turned on. Adb works flawlessly as long as the device is fully booted. When the device reboots into recovery, windows sees it as a different device. Reinstalling the drivers while in recovery fails.
Sent from my Nexus 7 using xda premium

I dunno what the deal is. On my vivid kernels have to be flashed through fastboot because of htcs s on crap and it always works. Even stranger toolkits work fine but manually typing commands doesn't
Sent from my HTC PH39100 using Tapatalk 2

[Q] PLEASE HELP!!! Cannot connect to computer!!!

Hey everyone, thanks in advance for the help. I just got a nexus 4 yesterday, that was already updated to 4.3 when I got it. My problem is when I go to unlock the boot loader, it won't recognize the phone. It says "list of devices attached" but doesn't give a serial number. Also, before this, it was giving a serial number, but was saying it was offline. So I uninstalled and reinstalled the drivers. Any help is most appreciated.
Sent from my Nexus 4 using xda premium

You might need updated adb/fastboot exe/dll's. Grab them from a toolkit, that's what I did.

meangreenie said:
You might need updated adb/fastboot exe/dll's. Grab them from a toolkit, that's what I did.
Click to expand...
Click to collapse
I completely upgraded the whole SDK. Still no good.
Sent from my Nexus 4 using xda premium

Try this... When you're connected to the PC , toggle USB debugging off and on.. It might ask for authorisation of ur PC in your phone.. Give yes.. Then do adb devices .. You might fight the offline thing gone
Sent from my Nexus 4 using Tapatalk 4

badhri said:
Try this... When you're connected to the PC , toggle USB debugging off and on.. It might ask for authorisation of ur PC in your phone.. Give yes.. Then do adb devices .. You might fight the offline thing gone
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I did that, got it to boot into boot loader through adb, then my fastboot drivers wouldn't install. So I uninstalled everything and started from scratch and now I can't even get the serial number to come up.
Sent from my Nexus 4 using xda premium

Enzopreme said:
I did that, got it to boot into boot loader through adb, then my fastboot drivers wouldn't install. So I uninstalled everything and started from scratch and now I can't even get the serial number to come up.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hmm.. doesn't it get shown as Android devices under device manager?
I too had a similar kind of problem with adb. I uninstalled the drivers manually and installed it again using Koush's Universal ADB (Android Debug Bridge) Driver for Windows. It has fastboot thing also. It worked for me.
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
You can also try someone else's PC or something. Install the drivers using the above link and just fastboot. Sorry, if that is of not much help. I'm new, both to this place and to this Nexus 4 device as well. All the best.

[Q] Fastboot Doesn't Work

I'm not able to use fastboot at all on my nexus 4
I always get:
< waiting for device >
adb works fine, I can shell and view all the files etc. and "adb devices" lists my phone there and doesn't say offline. I've done all the normal stuff like changing USB ports (2.0 and 3.0) and I've tried different versions of ADB and the driver, clearing the RSA keys on the device. The phone is totally stock, no root and running 4.3 / JWR66Y and this has been happening before the latest OTA (JWR66Y) update (first OTA of 4.3)
Here's my bootloader info
Command line: console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677 uart
_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=mode_reset gpt=ena
ble lge.kcal=0|0|0|x lge.rev=rev_10 androidboot.emmc=true androidboot.serialno=0
0475fbe14129674 androidboot.bootloader=MAKOZ20i androidboot.baseband=mdm bootrea
son=reboot
and I'm currently using the "Android Composite ADB Interface" Rev8 driver from the SDK on Windows 7 x64 along with the 18.0.1 version of the platform tools.

Did you download the fastboot.zip and place it in platform-tools of the android SDK?
Sent from my Nexus 4

Try the SDK package ..
Sent from my MB886 using xda app-developers app

I'm using the fastboot binary from the SDK as stated in the OP

I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
Sent from my Nexus 4 using xda app-developers app

marsdta said:
I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you mean the ADB driver or something else, I've tried the naked ADB driver and the SDK ADB driver, both give the same result, ADB.exe connects, I can open a shell and see the files etc., but fastboot.exe just hangs on waiting for device

When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
Sent from my Nexus 4 using xda app-developers app

marsdta said:
When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No problem there. I don't think ADB would work if the driver weren't working would it?

It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app

Delete.. Dndnt read OP properly.

marsdta said:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes I've reinstalled the driver a few times and tried different drivers. I've tried the universal naked 0.72.the rev8 from the SDK and Koushes, all 3 work with adb and none worked with fastboot

marsdta said:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Which driver did you use in the end? I've tried just about everything, I even grabbed another nexus 4 and I'm having the same issue with that one (which is on the earlier 4.3 OTA update btw)

Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside
Sent from my Nexus 4

Cream$ickleHJ said:
Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside
Sent from my Nexus 4
Click to expand...
Click to collapse
Download from where? Which files do you suspect are missing?

I used the one from the SDK. When booted up device manager shows adb composite and when in boot loader device manager shows android boot loader interface.
When you are reinstalling the drivers did you uninstall them first. That's what I usually do. Once helped someone who had the driver installed several times, so they were conflicting . I would uninstall drivers and delete any mention of them. Reboot PC. When plug in phone I ignore it trying to search and install boot loader driver. And install it manually
Sent from my Nexus 4 using xda app-developers app

Soft brick but with no adb connection on bootloader

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!

[Q]Oh I've done it now... think I'm bricked?

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.