I have installed a nightly update for Cyanogen 7 and since then the phone is stuck on the Cyanogen logo.
I can get into recovery but since I don't have any firmware files on my SD I can't reinstall the ROM. I just need a way to put the files on my internal SD.
I have tries ADB which didn't detect my phone. I have installed the driver (The phone is found as the Nexus S for some reason) .
I also couldn't get into download mode although I don't have the hardware lock as I can get into recovery.
What can I do in this situation? I am already thinking of opening the phone, swapping out the internal SD and transferring the files through the computer. I would like to know if there's any other way.
Thank you!
romitkin said:
I have installed a nightly update for Cyanogen 7 and since then the phone is stuck on the Cyanogen logo.
I can get into recovery but since I don't have any firmware files on my SD I can't reinstall the ROM. I just need a way to put the files on my internal SD.
I have tries ADB which didn't detect my phone. I have installed the driver (The phone is found as the Nexus S for some reason) .
I also couldn't get into download mode although I don't have the hardware lock as I can get into recovery.
What can I do in this situation? I am already thinking of opening the phone, swapping out the internal SD and transferring the files through the computer. I would like to know if there's any other way.
Thank you!
Click to expand...
Click to collapse
Plug phone into computer and boot in recovery. If still not recognized by adb go to advanced and select reboot recovery. This should get you adb. ADB push "namehere".zip sdcard.
If still having problems Odin back to stock and start over. To get to download mode make sure phone is off, battery pull if necessary. Plug USB to phone press volume up and down and hold and plug USB into computer.
Sent from my GT-I9000 using XDA Premium App
Awesome! Thanks to you I have managed to get into download mode now.
All the guides that I found says I should use the power button. You said only up and down while connecting. That worked.
I am very grateful.
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
kaywoo said:
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
Click to expand...
Click to collapse
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
Yeah it's weird. Even after coming back to stock, unrooted, the hard-reset via stock recovery doesn't work unless USB is plugged in. Maybe some files are missing
Wow, I'm glad I stumbled on this thread, I was going nuts trying to figure out why I couldn't boot back into CWM after going back to the stock image and applying the OTA .zips.
Confirmed, I can get it to boot into CWM from fastboot only if I have the USB cable plugged in. Otherwise it just hangs on the Google splash screen.
Weird.
I've been able to boot into recovery using the app "quickboot" which had an option to reboot into recovery. My usb cable isn't plugged in.
Sent from my Galaxy Nexus using Tapatalk 2
This sounds a bit like my Nexus S i9020. It will only go into bootloader without the usb, and only go into download mode with USB attached (although it doesn't have to be powering it). This is the same on both handsets I've used. Maybe not a 'flaw' and more a nod to using fast boot/adb?
Sent from my Nexus S using xda app-developers app
I am currently having the same problem. Did anybody come up with a fix for this?
I'm having the same issue with the nexus 7. I've found out that you can boot into recovery if you have ROM Manager installed and select reboot into recovery.
Does anyone know if this is an OS issue or recovery issue?
Interesting. Was wondering why I couldn't get into Recovery from the Bootloader.
Another bug for me is that if I boot into Bootloader with the USB connected, I cannot make any selection using the volume keys. Only works if I boot in first without USB connected, then connect once I'm booted.
Its a bug, guys learn to search in the Development threads, I'm sure its being worked on,personally I've been able to get into recovery without have to connect via USB, if all else fails you can enter recovery via USB and ADB, by issuing the command adb reboot recovery in terminal/cmd
I had the same issue last week. Not sure what changed but now I'm able to get into recovery using the reboot menu or good mngr/rom mgr. No need for usb. I'm on modaco rom and used both clockwork and twrp.
Sent from my PG86100 using xda app-developers app
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
I have the same problem.
LTE Galaxy Nexus
Nexus 7 (16gb)
Miracle.vl63 said:
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
Click to expand...
Click to collapse
There are two different versions of CWM- one uses the power and vol-up/down buttons for keys- the other used the tablets touchscreen for button press functions.
You may have installed the touch(screen) version of CWM- try using the touchscreen for controls.
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
omegajester said:
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
Click to expand...
Click to collapse
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Trikkenut said:
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Click to expand...
Click to collapse
Nope, disconnecting the battery didn't change anything. Wug Fresh (Nexus Root Toolkit developer) informed me on Google + that it's a Google issue and it should be fixed in a future update. For now i'll be either plugging in USB to computer or ROM Manager.
I can't even get into the boot loader with my usb plugged into a charger not a computer
askho said:
I can't even get into the boot loader with my usb plugged into a charger not a computer
Click to expand...
Click to collapse
Try Quick Boot
Free, easy to use, will boot to bootloader, recovery, reboot etc... requires root of course, you already have that.
i dont't have root because it was screwed up right fromt he get go
Hi guys.
My frind is a newbbie and formated the system and the sdcard of his nexus 4.Since i have one, rooted, he asked for my help...
The problem is i can't get the windows to recognize the device. I've tried it in a different computer (one who never had an android device connected), and still nothing. Tried using adb and fastboot, and even tried the WUG toolkit, and nothing. When i connected it to the pc, it doesn't even make the usual sound of a new device being connected.
If the pc can see the device i can do the rest, but right know i need your help on this issue...
many thanks.
Anyone please...! Is it Bricked?
Since it doesn't boot into android adb won't work so fastboot is the only option. Just flash the stock 4.3 image and flash custom recovery after if he wants it
Sent from my Nexus 4 using xda app-developers app
otariq said:
Since it doesn't boot into android adb won't work so fastboot is the only option. Just flash the stock 4.3 image and flash custom recovery after if he wants it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The pc didn't recognice any device, so fastboot wasn't a solution either... The fuc&%$$%/ usb cable was broken!!!!!
New cable = problem solve!
thanks anywat
Rom stopped working one day. Now wont boot past Google screen with lock unlocked on bottom. Does boot into recovery or bootloader.
Computers wont read device. Device does charge when plugged into anything else.
Tried drivers and PDAnet installed still no read. Wont do anything when plugged into 3 different computers. Anything I can do or might as well throw it out?
Did you do anything to it before it stopped working? Is it charged? I find that once the battery dies sometimes you have to leave it charging for hours before it will boot.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
gc84245 said:
Did you do anything to it before it stopped working? Is it charged? I find that once the battery dies sometimes you have to leave it charging for hours before it will boot.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
It boots fine. Battery is fine. Fully Charged. Boots up to google screen and stays there.
Having a similar problem.
Is it possible to use an OTG cable even if USB debugging is not enabled, that way you could flash a working ROM, right? Or am I missing something obvious?
Same problem here. After updating to a CM Nightly, my Nexus 7 wont boot past Google logo. Can access recovery, but I have no idea what to do from there. I have no idea how to get it working again...
same here. I can only access adb fastload nothing else.
How to recover from here?
LG flash tool just stays at ready. Ive unplugged and replugged. Unplugged, powered off, plugged back in as download mode still stays at ready. So back to flash is out. Phone stuck at lg logo, but can boot to download mode, and twrp. Computer doesn't recognize twrp in adb sideload mode. I'm on windows 8, using the oem cable, and turned off the signature enforcement and restarted computer as well. So that's out. Otg is out as well I've tried exfat and fat32 on an 8gb san disk cruzer. I've used just the otg and ive used it in combination with a y--cable, both of which i've used before successfully. Also I checked the external sd folders for the otg and used the cat/proc/mounts in terminal. This post definitely sounds condescending and i'm sorry. This is one time when i would be so grateful to be proved a moron. The one solution i haven't tried yet is using the flash tool with the ota .tot file, instead of the shipping rom. What do I do?
If u can't get into recovery then revert to stock is the only option. Try holding power and vol down and press on screen where home button should be and it should take u to recovery and then u can use sideload with koush drivers and if it does not work then going back to stock is only option.
Sent from my LG-D800 using xda app-developers app
What are koush drivers? Any idea what im doing wrong with lg flash tool, because that isn't working, otherwise i would've went back to stock already.
Stock lg mobile drivers don't seem to help pc see ur phone in recovery mode so koush drivers or pdanet installed in ur pc can help solve ur problem.
Sent from my LG-D800 using xda app-developers app
Thank you so much. It was dumb to ask what the drivers were, i googled it, installed, and it worked. thank you so much.