Related
As I was running the P.A.C. Man ROM with nightlies, I installed the most recent update at the time, the "pac_mako-nightly-20130722.zip". I have been dirty flashing all the nightlies without any problems, until this morning. I installed the new nightly from TWRP, then wiped the dalvik and cache, and then rebooted the system, but when the phone started up again, I got an SD card error - I cannot view any of the contents of my SD card from ES File Explorer or anything and I cannot open or find any of them (picture, music, etc.) from anywhere.
From the file manager in TWRP, I can see that all the files are still there, but the SD card that is been seen everywhere else is a completely different one. If I plug my phone into my computer, the SD card shows up as a "generic hierarchical" with no contents.
Another thing, I cannot access the internet in anyway anymore. The wifi is stuck on "Turning wifi on..." and my SIM card is getting no response ("No Service") - if I remove my SIM card, my phone doesn't do anything either.
I already tried a factory reset to no avail. Nothing I do is working and right now my phone is pretty much stuck in a state of uselessness. I can start it up and it will load normally, but once loaded, there are errors - wifi stuck on "Turning on," no service, SD card is unreadable, and I can't transfer any files from my computer to my phone because it shows up as a "generic hierarchical" SD card.
What do I do?
Wipe system, data, cache and dalvik. Start fresh, reflash ROM. Might help.
Sent from my Nexus 4 using Tapatalk 4 Beta
ridikolous said:
Wipe system, data, cache and dalvik. Start fresh, reflash ROM. Might help.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've done all of that twice now, but still it doesn't work.
Try a different ROM. Or return your phone back to stock. There is a guide somewhere.
Sent from my Nexus 4 using Tapatalk 4 Beta
roll back to earlier nightly. 721 cm side issues
ziddey said:
roll back to earlier nightly. 721 cm side issues
Click to expand...
Click to collapse
How can I do that?
NexusAndroid4 said:
How can I do that?
Click to expand...
Click to collapse
adb push or sideload an earlier ROM zip to your phone, or restore your backup.
NexusAndroid4 said:
How can I do that?
Click to expand...
Click to collapse
by flashing an older nightly...?
ziddey said:
by flashing an older nightly...?
Click to expand...
Click to collapse
I deleted my old nightlies to clear up space on my SD card... Does that ruin everything?
NexusAndroid4 said:
I deleted my old nightlies to clear up space on my SD card... Does that ruin everything?
Click to expand...
Click to collapse
No, adb push or adb sideload a different ROM zip, done.
NexusAndroid4 said:
I deleted my old nightlies to clear up space on my SD card... Does that ruin everything?
Click to expand...
Click to collapse
time to buy a new phone
CMNein said:
No, adb push or adb sideload a different ROM zip, done.
Click to expand...
Click to collapse
I downloaded the 07/21 file and the sdk. I'm trying to adb sideload in TWRP but I get the error:device not found - adb devices lists no serial number in TWRP. My device's serial number shows up in the Android OS but not in TWRP. What do I do?
Install the adb drivers again with your phone in recovery and connected and try again.
Sent from my Nexus 4 using Tapatalk 4 Beta
CMNein said:
Install the adb drivers again with your phone in recovery and connected and try again.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I believe I've done this reinstalling and it still failed, but could you tell me how?
NexusAndroid4 said:
I believe I've done this reinstalling and it still failed, but could you tell me how?
Click to expand...
Click to collapse
How to install the drivers?
Check if anything is showing up under your cpu's device manager when your phone is connected in recovery. Right click on that device, go to driver tab, select update driver, and then select the path to where you put the drivers you DL'd.
CMNein said:
How to install the drivers?
Check if anything is showing up under your cpu's device manager when your phone is connected in recovery. Right click on that device, go to driver tab, select update driver, and then select the path to where you put the drivers you DL'd.
Click to expand...
Click to collapse
In Device Manager, my phone shows up as "mako." When I try to update from the path of the AndroidSDK in recovery mode, I get an error.
You're pointing it all the way to the sub folder the drivers are in? It's extras/Google/USB drivers or something similar.
Sent from my Nexus 4 using Tapatalk 4 Beta
CMNein said:
You're pointing it all the way to the sub folder the drivers are in? It's extras/Google/USB drivers or something similar.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes:
C:\...\sdk\extras\google\usb_driver
NexusAndroid4 said:
Yes:
C:\...\sdk\extras\google\usb_driver
Click to expand...
Click to collapse
When your phone is booted is it showing up as "online" or "offline" when you do adb devices?
How old are the drivers you have? Might have to update them. The SE Linux code that broke wireless, etc... didn't affect adb. You're just going to have to mess around until you can get your cpu to recognize your phone while you're in recovery. That's all I got.
CMNein said:
When your phone is booted is it showing up as "online" or "offline" when you do adb devices?
How old are the drivers you have? Might have to update them. The SE Linux code that broke wireless, etc... didn't affect adb. You're just going to have to mess around until you can get your cpu to recognize your phone while you're in recovery. That's all I got.
Click to expand...
Click to collapse
Nothing shows up at all with adb devices. When I do adb devices in the normal Android OS, it works, but not in recovery. I installed the SDK today so that shouldn't be the problem.
Hi guys, I made a mess today. I decided to restore my stock LG software backup and everything went well. Then there were some LG updates and when they downloaded, I chose to install them. That took me to TWRP. I figured it needs the stock recovery to install the updates so I gave up on the updates and tried to reboot my device. It booted back to TWRP. I found it a bit weird, but I didn't care since I had a backup on the phone. I wiped data, cache, system and dalvik and restored the backup. Guess what, the phone would still only boot into recovery. I started freaking out so I wiped everything except internal again and flashed an AOSP based rom along with the gapps. Still wouldn't boot except recovery. Then I started to freak out even more and decided to wipe EVERYTHING, along with Internal storage. And here I am now, wiped every single thing on the device, stuck in recovery and can't connect my phone to the PC with usb. just a few minutes before I have to leave home. Any ideas on how to fix this? It was just some pointless LG update and it caused such a mess... ADB sideload won't work for me, I'm gonna attempt to find some drivers or something.
Anybody?
Sent from my HTC One X using xda app-developers app
Evetything you need its allready posted. Just search
Sent from my LG-D802 using Tapatalk
darkobas said:
Evetything you need its allready posted. Just search
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Dude, I've done my research and tried to fix it myself. The phone won't go into download mode and it won't connect to my PC. Drivers installed, LG tool installed. I just don't know what to do and I need help from someone who does know.
ViktorN said:
Dude, I've done my research and tried to fix it myself. The phone won't go into download mode and it won't connect to my PC. Drivers installed, LG tool installed. I just don't know what to do and I need help from someone who does know.
Click to expand...
Click to collapse
If you have twrp 2.6.3.4 you sideload rom but this may not help you.
You are going to have to go back to 100%stock.
Sent from my LG-LS980 using xda premium
mchlbenner said:
If you have twrp 2.6.3.4 you sideload rom but this may not help you.
You are going to have to go back to 100%stock.
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
Sideloading won't work for me either.
Sent from my HTC One X using xda app-developers app
In TWRP you have USB-OTG. If you have this cable you can install ROM from USB-flash)
I had the same issue. Only way to fix it was with the LG flashing tool. Make sure the usb port you are using on your computer is working and the cable isn't broken. I just followed the steps from this thread and it worked 100% for me.
http://forum.xda-developers.com/showthread.php?t=2432476
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.
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
Bonehead move I know. Now I need some help to fix. I flashed a stock 5.0 ROM and everything was working fine. Got the 5.0.1 prompt so I flashed a stock recovery (4.4.4 hence my problem). Of course the update wouldn't flash. Now to complicate things all of a sudden my PC won't detect my Nexus 4. It detects my wife's Nexus 4 fine so I'm thinking not a cable or driver problem. Ive tried multiple cables and reinstalled drivers with no luck. So now I need to root and or install custom recovery without a PC. Any ideas?
icekold1694 said:
Bonehead move I know. Now I need some help to fix. I flashed a stock 5.0 ROM and everything was working fine. Got the 5.0.1 prompt so I flashed a stock recovery (4.4.4 hence my problem). Of course the update wouldn't flash. Now to complicate things all of a sudden my PC won't detect my Nexus 4. It detects my wife's Nexus 4 fine so I'm thinking not a cable or driver problem. Ive tried multiple cables and reinstalled drivers with no luck. So now I need to root and or install custom recovery without a PC. Any ideas?
Click to expand...
Click to collapse
You're going to need to get your pc to recognize your device. When booted into the bootloader and your device connected to the pc look in device manager. What does it show?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're going to need to get your pc to recognize your device. When booted into the bootloader and your device connected to the pc look in device manager. What does it show?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't show anything. Its as if it isn't connected at all. I've tried from the bootloader and recovery screens and also rebooted both phone and pc. Still shows nothing in device manager. Phone shows charging but no mtp notification or anything that it is connected. As soon as I plug our other nexus 4 in the pc recognizes it immediately.
icekold1694 said:
It doesn't show anything. Its as if it isn't connected at all. I've tried from the bootloader and recovery screens and also rebooted both phone and pc. Still shows nothing in device manager. Phone shows charging but no mtp notification or anything that it is connected. As soon as I plug our other nexus 4 in the pc recognizes it immediately.
Click to expand...
Click to collapse
Is your device still rooted? If so you can flash the stock recovery image file from 5.0 in flashify
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your device still rooted? If so you can flash the stock recovery image file from 5.0 in flashify
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
No I lost root when I flashed the 5.0 stock rom.
icekold1694 said:
No I lost root when I flashed the 5.0 stock rom.
Click to expand...
Click to collapse
I would try deleting your usb drivers on the pc, rebooting and then trying your device again. Flashing the 4.4.4 recovery should not have done anything to mess up your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would try deleting your usb drivers on the pc, rebooting and then trying your device again. Flashing the 4.4.4 recovery should not have done anything to mess up your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
OK I will try that again and post results. Another possible problem I noticed is in root explorer I have a directory of emulated/0 I don't remember having before.
icekold1694 said:
OK I will try that again and post results. Another possible problem I noticed is in root explorer I have a directory of emulated/0 I don't remember having before.
Click to expand...
Click to collapse
I'm sure that directory was always there. It's a normal directory
Sent from my Nexus 9 using XDA Free mobile app
I uninstalled/reinstalled drivers and still no go. Detects the wifes nexus 4 but not mine. Guess I'm screwed.
icekold1694 said:
I uninstalled/reinstalled drivers and still no go. Detects the wifes nexus 4 but not mine. Guess I'm screwed.
Click to expand...
Click to collapse
To root your device use towelroot from your device. Although I don't know what you're going to do with root. Also, can you get the device detected by your pc when you're booted into recovery or the device?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
To root your device use towelroot from your device. Although I don't know what you're going to do with root. Also, can you get the device detected by your pc when you're booted into recovery or the device?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot wouldn't work. Says device isn't supported. Maybe it will get updated to work on lollipop. If I could obtain root I can flash custom recovery and start with a fresh install. Just have to find a way to do it with an app