Related
Hi My nexus 7 was working fine I had a custom rom (paranoidandroid ) tried to upgrade to the latest release and now stays stuck at jelly bean splash screen
ive tried
installing frivers through wugz 1.5
nexus root kit uninstalled reinstalled tried to connect in fastboot mode nothing
I used a windows 7 box and an xp box updated usb drivers on both pcs nothing its like the port on the nexcus 7 was broken or something please help!
The only way I see out is if maybe I can connect through linux but not sure how to I do have a laptop running backtrack I could use
Wrong forum for this but:
Sounds like you tried to install on top of the existing ROM without wiping.
Can you get into fastboot? if so open a command prompt from the folder you have fastboot.exe installed and type "fastboot devices". do you see your serial number? If so you're fine! Flash a custom recovery you can easily wipe/reset and wipe dalvik cache and install a new ROM.
asawoszc said:
Wrong forum for this but:
Sounds like you tried to install on top of the existing ROM without wiping.
Can you get into fastboot? if so open a command prompt from the folder you have fastboot.exe installed and type "fastboot devices". do you see your serial number? If so you're fine! Flash a custom recovery you can easily wipe/reset and wipe dalvik cache and install a new ROM.
Click to expand...
Click to collapse
I can get into fastboot and it doesnt recognize it ive tried everything different cables etc
also i was upgrading from 1.9.2 to 1.9.5 so a full wipe was not required
My main problem is i cant connect cant list devices
so if you're in fastboot mode and you type "fastboot reboot-bootloader" nothing happens?
I don't see how installing a ROM would cause these problems.
asawoszc said:
so if you're in fastboot mode and you type "fastboot reboot-bootloader" nothing happens?
I don't see how installing a ROM would cause these problems.
Click to expand...
Click to collapse
Nothing at all it doesnt recognize it at all
I dont see either I dont get it and I cant get into recovery if i try that it gets stuck at google screen
if i try to boot then I just get stuck at splash
tried different systems no dice
Put your device in fastboot mode. Do not connect it yet.
Run wugz 1.5.2 (that's the latest I think) and press the "Full Driver Installation guide".
Check the instructions to remove your current drivers. Remove them.
connect your device
Reinstall the drivers manually (not via the toolkit). Use the naked drivers from here.
Download the factory image from here and flash it via the toolkit.
root it, flash cwm do whatever you want to do :silly:
profit
Wont respond or recognize it
snipestech said:
Wont respond or recognize it
Click to expand...
Click to collapse
You need to install the drivers. Do you know how to get into your device manager in windows and install drivers for devices connected? You need to dl th wugz that regunus told you about above. After installing you can tell your computer to search in that folder to install drivers. When you open your device manager do you see anything yellow with a question mark. Once you have the drivers installed correctly then follow this http://forum.xda-developers.com/showthread.php?t=1781250 and you will be golden. Been through this a couple times already
Also when you try to manually install drivers for the devices that are not recognized in the device manager make sure to guide the driver install wizzard in the folder Universal_Naked_Driver_0.7 (or wherever you unzipped your drivers) and NOT in a specific directory like "amd64" or "i386".
If all drivers are succesfully installed, your computer will see the device in fastboot mode and your problems are gone ^_^
snipestech said:
Wont respond or recognize it
Click to expand...
Click to collapse
You can install the toolkit from here http://forum.xda-developers.com/showthread.php?t=1809195 then use it to install the drivers, then install temp cwm, then reboot into recovery, do a full wipe and try to install 1.95 again. You can use the toolkit to install a rom as well if you download it to your computer. Hope it helps.You always have to wipe cache and dalvic cache when flashing any rom. No wipe means you don't need to do a data/factory reset.
Vocalshock said:
You need to install the drivers. Do you know how to get into your device manager in windows and install drivers for devices connected? You need to dl th wugz that regunus told you about above. After installing you can tell your computer to search in that folder to install drivers. When you open your device manager do you see anything yellow with a question mark. Once you have the drivers installed correctly then follow this http://forum.xda-developers.com/showthread.php?t=1781250 and you will be golden. Been through this a couple times already
Click to expand...
Click to collapse
Its not connecting at all Ive done this before ive had many Android phones when i connect nothing happens. I tried different cables computers etc nothing no connection at all
Would like to try to connect on linux if not Its going on ebay as is
snipestech said:
Its not connecting at all Ive done this before ive had many Android phones when i connect nothing happens. I tried different cables computers etc nothing no connection at all
Would like to try to connect on linux if not Its going on ebay as is
Click to expand...
Click to collapse
dude, forget the ebay! Your device is ok!
Check the Device Manager in the control panel to make sure all the drivers have been installed correctly. After that we'll see
I did dalvic and that's it also I already tried that tool kit regunus is connect via teamviewer see if he can help
Sent from my Galaxy Nexus using xda premium
snipestech said:
I did dalvic and that's it also I already tried that tool kit regunus is connect via teamviewer see if he can help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I think he should be able to help. If not let me have a go at it..I have Team Viewer.
He would need dubugging mode on wouldnt he
Sent from my SGH-I777 using Tapatalk 2
Regunus tried no avail.
I reformatted my laptop dual boot windows 7 32 bit.
Tried all previous suggestions its not recognized, me and Regunus came to the conclusion that the port can't be bad Cuz it charges yet it does not recognize it.
I just finished installing adb fastboot on ubuntu if I go to terminal and list devices nothing if I connect my Galaxy sIII it shows up so again not being recognized while other devices do.
Current state :
Fastboot start goes to paranoid android jelly bean splash
And hangs
Fastboot recovery stays stuck at Google screen
I have reciept and all to bad I can't return may just post on ebay
Same Issue
I'm having the same problem, was this ever resolved?
Edit: I was having the same problem. Downloaded 'Nexus 7 Toolkit' and ran the 'install driver' option again (option 1). Device was recognized again.
No such thing as no way out. Keep find a way to connect and you're all set. Have you tried force reboot to fastboot and then enter recovery? I have similar problem once with my nexus s and i finally find a way after 10 hours of constant googling
I've tried nexus 7 toolkit
I reboot into fastboot mode and select recovery and it goes to Google and hangs I've tried on different post nothing at all
Sent from my SPH-L710 using Tapatalk 2
When it was recognized what state was it in?
fastboot mode?
Sent from my SPH-L710 using Tapatalk 2
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.
Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
BraydenJW said:
Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
Click to expand...
Click to collapse
try these as drivers
Trying now
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
Thank you. Trying this now. I'll let you know how it goes.
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
BraydenJW said:
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
Click to expand...
Click to collapse
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
datechnerd said:
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
Click to expand...
Click to collapse
I'm afraid that did not work. I get an error message saying there wasn't any drivers found in that folder.
i.imgur.com/mkLZzBe.png
The two files are directly within the extract folder on my desktop. I'm running Windows 8. I right-clicked g2 in device manager, and selected update driver software and navigated to the extract folder on my desktop.
Thank you for your help so far, do you know where I could go from here?
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
BraydenJW said:
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
Click to expand...
Click to collapse
go to sideload and install drivers
datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
I'm sorry. I'm not entirely sure what you mean. When I go to sideload on TWRP, it gets stuck on the loading feature part indefinitely.
cityneversleepz said:
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
Click to expand...
Click to collapse
Thank you. I've tried it from my own laptop and my work computer and both have similar results. I'll try it from one of my older computers. I'll post back with my findings.
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
BraydenJW said:
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
datechnerd said:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
Click to expand...
Click to collapse
Thank you! Trying this now. I'll report back soon.
It's looking good! It showed up in my adb devices now. Just have to re-download the rom
I pushed the ROM and am installing it now. If this goes through successfully, I'll send you some money over paypal if you wish. Nothing huge, but at least a little as a token of my appreciation.
The ROM installed successfully. I'm just waiting for the first boot now. It's taking a while (about 5 minutes now) and I'm VERY nervous.
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
BraydenJW said:
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
Click to expand...
Click to collapse
that rom says let the first boot take as much time as needed.
datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Alright! I'll leave it for a few hours. PM me your paypal email if you'd like me to make a donation to you! You've been an extreme help!
datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Left it for over an hour. No luck. Something is wrong.
SOLVED!
Hello All.. I have searching for hours not making much progress. Last night my LG G2 ran out of battery and I plugged it into the car charger and it soft bricked. I've been pretty busy lately so I'm on an old ROM Optimus DE 2.2. I don't have the ROM saved and I've been trying to ADB sideload the ROM back onto my phone but in the command prompt it says device not found. I tried installing some generic drivers and that didn't work. I tried the LGUnitedMobileDriver and that isn't working either.
I'm not sure what to do next. I have ADB on my computer and ADB sideload on my TWRP recovery, so I would like to push the ROM on my phone so I can flash it without having to wipe my phone. What drivers do I need; right now my phone shows up under other devices in device manager. Or am I sideloading wrong? Any help please lol..
I was caught off guard because of the random soft brick. If I would have been working on my phone I would have had the proper backups made. Thanks for any help, it is much needed I need my phone back ASAP!! Thanks again.
SOLVED
Finally figured it out. I had to updated my device (LG G2) with the ADB drivers not the LG drivers.
I went into Device Manager, right clicked my phone, clicked update driver software, clicked browse my computer, clicked let me pick from a list of drivers, then selected ADB drivers, then selected HTC Dream Composite ADB Interface. I believe the drivers I last installed were Snoop05's adb-setup-1.4.2.
Then I did a backup in TWRP, then I sideloaded the ROM. Next I had to wipe everything but internal memory and the use Nandroid Manager to restore my data from the backup... Took my whole day but at least I have a phone again.
The car charger soft bricked it ?
So you have TWRP, the drivers you can get from the LG site too. Just search for your model and go to software update section. This is for D802, i dont know if the drivers are the same: http://www.lg.com/uk/support-mobile/lg-D802
Hmm..i dont know how to use the sideload..
Another way can be with USB flash drive and OTG cable, i used my usb flash drive with OTG cable to flash ROMs from TWRP
Last option is lg flash tool and then reroot
Thanks for your help guys.. I appreciate it! Looks like I just needed to update my phone with the ADB drivers in Windows 8 Device Manager. I'm back up and running.
But yea so weird.. I haven't flashed anything on this phone in months so I guess something was corrupted when it died. I think it was trying to boot with too low of a charge and the battery died mid boot which corrupted something.
Although you've solved it let me recommend you another way.
Use : "adb push romname.zip /sdcard/romname.zip"
instead of "adb sideload romname.zip"
Hi
Last night my phone accidentally drop then its not boot up as it show only boot logo of onepus so I decided to reflash the phone I successfully install driver of ORT co 9008 then detect then unbrick or flash using this all steps completes successfully then I remove phone from PC and start or switch on phone but its won't on even as before it was showing the oeplus logo as saw before and new its comport detecting and gone in device manager.
Thnx pls help
lokeshbhati1987 said:
Hi
Last night my phone accidentally drop then its not boot up as it show only boot logo of onepus so I decided to reflash the phone I successfully install driver of ORT co 9008 then detect then unbrick or flash using this all steps completes successfully then I remove phone from PC and start or switch on phone but its won't on even as before it was showing the oeplus logo as saw before and new its comport detecting and gone in device manager.
Thnx pls help
Click to expand...
Click to collapse
Obviously people are reading this. We don't know what to say, probably because most of us suspect the phone's fall broke something. If the fall did *not* break something in the phone, maybe using TWRP to attempt flashing a rom will work. Do you have TWRP installed? If not, use your computer (and Odin) to do so. Make sure to REBOOT IMMEDIATELY to recovery (TWRP, that is). Unplug phone from computer, replug phone into computer again. It should be recognized. Copy a rom of your choosing to the "download" directory on the phone. Then "factory wipe" the phone. (Do NOT wipe "internal storage"). Flash the rom (and gapps if this is a custom rom). Reboot. And here's hoping it works!
How can i install or go custom recovery After successful flash its not show adb or oneplus device not boot on,no bootloader,not show anything.dear
lokeshbhati1987 said:
How can i install or go custom recovery After successful flash its not show adb or oneplus device not boot on,no bootloader,not show anything.dear
Click to expand...
Click to collapse
But flash was not successful. Is the phone showing any sign of life? Charging icon on screen when cable is plugged in? Anything? I fear you have broken it.
No sign of life only heating when connected to charger or USB in computer only show Qualcomm port 9008 in pc when I press both volumes+power button
shonkin said:
Obviously people are reading this. We don't know what to say, probably because most of us suspect the phone's fall broke something. If the fall did *not* break something in the phone, maybe using TWRP to attempt flashing a rom will work. Do you have TWRP installed? If not, use your computer (and Odin) to do so. Make sure to REBOOT IMMEDIATELY to recovery (TWRP, that is). Unplug phone from computer, replug phone into computer again. It should be recognized. Copy a rom of your choosing to the "download" directory on the phone. Then "factory wipe" the phone. (Do NOT wipe "internal storage"). Flash the rom (and gapps if this is a custom rom). Reboot. And here's hoping it works!
Click to expand...
Click to collapse
shonkin said:
But flash was not successful. Is the phone showing any sign of life? Charging icon on screen when cable is plugged in? Anything? I fear you have broken it.
Click to expand...
Click to collapse
No sign of life only heating when connected to charger or USB in computer only show Qualcomm port 9008 in pc when I press both volumes+power button