Database Users

soft bricked vibrant

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.

Recovery only works when USB is plugged in

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

Need Help Unbricking Nexus 7

The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !

Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.

I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|

What were you doing before you go into this situation?

I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.

Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.

Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here

Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?

I tried everything and windows still doesn't recognize my device in fastboot

Have you tried Nexus Root Toolkit v .1.5.4?

kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer

Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.

Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!

Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.

Help required - Bootloader only

Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks

herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers

jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue

herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?

I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.

Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD

I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck

erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung

LG G2 Bootlooping - Can't get into recovery

I had CM 10.2 on my LG G2 but I wanted to give it to a friend so I thought I'd better remove the root for warranty reasons. I removed it with this method(D802): http://forum.xda-developers.com/showthread.php?t=2432476
After flashing it stucks on the LG logo. I tried to get into recovery by holding Vol down + Power but it turns off and the LED begins to blink red. After that I used "Upgrade Recovery" with the LG mobile support tool. Now my branding(hutchinson 3) is back but it still stucks and I still can't get into recovery.
I've now been looking for 6 hours for any solutions but nothing seems to be working so far. I hope you can help me.

try vol dwn+pwr until the LG logo shows up, let go and press and hold them again

It boots up to the 3 Branding then and the bootloop keeps on going.

The uota
Connect it to your PC and use ADB to reset it

ADB can't find my device
edit: It must be a driver problem, "lge android net mtp device" cannot be installed for some reason. I re-downloaded and installed the drivers, restarted my comp and "lge android net mtp device" is still not working.

Volume up to enter download mode while inserting USB. Will install drivers. If not, extract drivers, point module from device manager to folder. If still no, try koush's universals. Flash stock. You may not have a recovery left after looping with kdz.

Steamer86 said:
Volume up to enter download mode while inserting USB. Will install drivers. If not, extract drivers, point module from device manager to folder. If still no, try koush's universals. Flash stock. You may not have a recovery left after looping with kdz.
Click to expand...
Click to collapse
None of them worked for me.
Steamer86 said:
extract drivers, point module from device manager to folder.
Click to expand...
Click to collapse
It says driver is already installed, but it isn't.

So uninstall, reconnect, force them.

Still not working.
Device manager - property of MTP device
Device satus: Device can't be started(Code 10). (Sorry I had to translate it from German.)

Phone needs to be in download mode. It should trigger other drivers, not just mtp. Try another computer...

Um.
Try do this
http://forum.xda-developers.com/showthread.php?t=2582142

You can also try to install pdanet and check with that. Select the device and proceed. Once the drivers are installed .. Try flashing the stock... Lemme know of this works
Sent from my LG-D802 using XDA Premium 4 mobile app