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.
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, I've got issues. I accidentally wiped internal storage as I was trying to flash a new ROM. I'm trying to ADB push a new ROM to the phone so I can actually get it functional. I'm running a command prompt from my SDK folder, but it keeps telling me that I don't have a device connected. Now, I know I had working drivers on this PC because it is the one I used to root. Any ideas why it would keep telling me that? Or some drivers that might work. I'm booted into TWRP 2.6.3.3 I have System, Data, and Cache mounted, and when I plug the phone in the PC makes the new device sound. I'm kind of at the end of my options here.
Have you tried flashing back to stock?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Install universal drivers, not carrier ones. They are indeed "limited". You could alternatively try Koush's drivers That are floating around.
doktor buknasty said:
Have you tried flashing back to stock?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Steamer86 said:
Install universal drivers, not carrier ones. They are indeed "limited". You could alternatively try Koush's drivers That are floating around.
Click to expand...
Click to collapse
So that's what I had to do. Back on bone stock. At least it works again.
i have a stock nexus 4 bought last year from a relative, when they tried to do an OTA update to (i think 4.4) it restarted and gave an error with the android being open in the middle. After restarting the phone it's been stuck in the "X" bootup screen
i tried to clear cache partition and that didn't work.
i got the android sdk and tried to connect it to the computer. it was recognized as an android bootable device in the device manager, but nothing shows up in the file manager, and when i tried to run the "adb device" command no devices show up.
i guess my question is, is there a way for me to pull the data from the phone first before i do the flashing? i heard that if i get rid of the "-w" in the flash-all.sh/flash-all.bat then it'll prevent the data wipe, is that also true?
thanks for the help!
looks like u didnt install the drivers properly... update them first... or reinstall all the drivers... thankyou..
Sent from my LG-E975 using XDA Premium 4 mobile app
krishnanmailbox1 said:
looks like u didnt install the drivers properly... update them first... or reinstall all the drivers... thankyou..
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
which driver? i also downloaded the google usb driver from android sdk and restarted computer a couple times
thanks
After downloading sdk tools you need to install couple of drivers from sdk... Open sdk and check onece if you have drivers installed properly
Sent from my LG-E975 using XDA Premium 4 mobile app
krishnanmailbox1 said:
After downloading sdk tools you need to install couple of drivers from sdk... Open sdk and check onece if you have drivers installed properly
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah, i did that and installed the usb driver, but it only shows up in device manager as "other device" and i can't access it. I guess i'll just factory reset and lose all my data haha... next time i'll know to always back up
i ended up unlocking the phone with
>>fastboot oem unlock
then ran the flash-all.bat file(on windows) and flashed it to 4.3 and it works now (no problems for now..)
I rooted my nexus 4 with towel root and delete some Google system apps being Google drive and chrome. I was using a few closed modules as well as xposed installer. I was having issues connecting to WiFi so I uninstalled everything but didn't unroot and factory reset my phone the issue now is when I boot up my phone I have no file manager to install apps (Google drive) and no web browser (Google chrome) to connect to the internet. And when I try to log into my Gmail or play store I get an error message saying this service is unavailable at the moment or my device is not provisioned for internet if problem persist contact customer service. I tried to install to unlock the boot loader ad install CWM with the nexus 4 root toolkit some thing went wrong and now there's no stock recovery period. It will still go into bootloader mode but now the phone doesn't even show up as being detectable to the computer. Phone still boots fine I can call and receive incoming calls text work fine as well. If there was some way I can install towel root again and the nexus 4 boot loader unlock app I think I could use flashify to flash clockworkmod so I could put the stock factory Rom on my internal storage wipe the device of the cheap I did and then flash stock 4.4.4 with a Gapps package I'd be okay but since I can't get the computer to recognize my nexus 4 I'm stuck. Please any help is greatly appreciated.
When you boot into the boot loader does the device show up in device manager at all? It'll probably show up but with an exclamation mark on a USB. If it does, right click on it and update driver software, then browes your computer and choose let me pick from a list...... Then choose android adb interface. It'll ask you if you're sure. Just say yes.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you boot into the boot loader does the device show up in device manager at all? It'll probably show up but with an exclamation mark on a USB. If it does, right click on it and update driver software, then browes your computer and choose let me pick from a list...... Then choose android adb interface. It'll ask you if you're sure. Just say yes.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes it does but when I tried to update the drivers it will not update them. I tried this on Windows xp 32 bit and on a windows 7 64 bit based computer. I tried to manually install the drivers but the computer can't find the drivers on my computer even if I put then into an accessible folder.
x.0ni.x said:
Yes it does but when I tried to update the drivers it will not update them. I tried this on Windows xp 32 bit and on a windows 7 64 bit based computer. I tried to manually install the drivers but the computer can't find the drivers on my computer even if I put then into an accessible folder.
Click to expand...
Click to collapse
Use the "let me pick from a list of devices..." it's right below the option where you would search for software on your computer.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Use the "let me pick from a list of devices..." it's right below the option where you would search for software on your computer.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried that too. Still wouldn't locate them.
phone got wiped, os and all. can only get into team win recovery (no android with !). in recovery file manager there is NOTHING on the phone. can not get phone to be recognized by computer. used sdk to install drivers still nothing. can not activate usb debugging as there is no os. reboot in recovery gives warning no os on phone. there is nothing to restore, all folders in install tab are completely empty. is there anyway to save my phone? there is nothing on it...just enough for safe mode and recovery.
You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.
Paltirian said:
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.
Click to expand...
Click to collapse
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?
Paltirian said:
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?
Click to expand...
Click to collapse
Simplest way is to download the factory image. Google nexus factory image. It's a .tgz file. Extract it using 7-zip. There's a flash-all.bat file in there. Boot into the bootloader and with your device connected to the pc just double click the flash-all.bat. It will wipe your device so if you can, backup first.
Sent from my Nexus 5 using XDA Free mobile app
You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much
Paltirian said:
You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much
Click to expand...
Click to collapse
No problem, glad you got it working. I like lollipop. It looks different but once you get over the difference you like it. I'm running 5.0.1
Sent from my Nexus 9 using XDA Free mobile app