Database Users

I think i bricked it!! Help me please!

So I installed Paranoid rom and wiped just like normal but now its stuck at the JB splash screen. My pc wont recognize it in fastboot and I cant get into recovery. Did I brick this thing or what?

poliati said:
So I installed Paranoid rom and wiped just like normal but now its stuck at the JB splash screen. My pc wont recognize it in fastboot and I cant get into recovery. Did I brick this thing or what?
Click to expand...
Click to collapse
how do you know for sure its not recognizing it in bootloader?

When I plug in my nexus I can't do anything. The hardware buttons don't work. I don't see anything in the drivers when I plug it in either.
Sent from my HTC One X using xda premium

Well, just to let you know, you haven't bricked it. Bricking something means you can't access the device what so ever i.e. it won't boot, won't go into recovery/bootloader mode etc. As to fixing it, I'm not sure. Can the device turn off and on? Have you got drivers installed properly (was fastboot and adb working before this happened)?

deleted

I am sure you tried every option , have you tried adb reboot recovery command, when u turn on phone, or adb reboot bootloader. If the manual way does not work, for example when device is powered off (volume down then holding power for 10 seconds). Let me know. Need more details.
Sent from my HTC Glacier using xda premium

Ok I'm trying that now.
Sent from my HTC One X using xda premium

Hi I think I'm facing the same issue as poliati. I tried to flash it back to stock image but the process freezes at "sending 'system' <438656kb>. Can someone please help?

r1tesh said:
I am sure you tried every option , have you tried adb reboot recovery command, when u turn on phone, or adb reboot bootloader. If the manual way does not work, for example when device is powered off (volume down then holding power for 10 seconds). Let me know. Need more details.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
So rebooting isnt the problem but getting into recovery or even getting my computer to recognize my device is what i need help with. The entire thing freezes when im in bootloader and try to plug into my computer. So i have to reset by holding down the power button. Ive installed and uninstalled drivers through wugfresh toolkit and nexus 7 toolkit.

poliati said:
So rebooting isnt the problem but getting into recovery or even getting my computer to recognize my device is what i need help with. The entire thing freezes when im in bootloader and try to plug into my computer. So i have to reset by holding down the power button. Ive installed and uninstalled drivers through wugfresh toolkit and nexus 7 toolkit.
Click to expand...
Click to collapse
Try plugging in and then going to boot loader.
Sent from my Nexus 7 using xda premium

When I plug it in, I can't do anything at all.
Sent from my HTC One X using xda premium

CharliesTheMan said:
Try plugging in and then going to boot loader.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That doesnt work either. The thing is, I can use the volume buttons BEFORE I plug it in, but as soon as I plug it into a computer the tablet freezes and i have to reset it.

So ive uninstalled all drivers including the SDK and reinstalled everything and im still stuck at the bootloader. Im starting to believe that its pretty much a lost cause. Can anyone help with trying to figure out what i may have to do now.

If you can get into the bootloader, you're not bricked, nor is it a lost cause.
Since you uninstalled them reinstall the drivers. Download the factory image (nakasi) from here, and then follow these instructions to use cmd and fastboot to reflash the stock ROM.

Ok I will try this.

Freakin love this site!!!
OK, so i now have everything up and running after about 2 hours of uninstalling and installing everything. Turns out that my cpu (or me) was duplicating the drivers. I feel dumb for that

[Q] Nexus 7 stuck at locked fastboot

After a failed attempt to install the 4.3 update with the NRT, my N7 is stuck in a locked fastboot mode. Every time press start it says booting failed.
is there a way to fix this? or am i doomed?
The guide for returning it to a stock image requires an unlocked fastboot mode...

Sounds like you'll have to unlock and flash again.
Sent from my Nexus 7 using Tapatalk 4

korockinout13 said:
Sounds like you'll have to unlock and flash again.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
well the device has usb debuging turned off...
is there a way to turn it back on from the fastboot mode?

Fastboot doesn't need USB debugging. USB debugging has nothing to do with custom recovery or fast boot.
Sent from my Galaxy Nexus

Pirateghost said:
Fastboot doesn't need USB debugging. USB debugging has nothing to do with custom recovery or fast boot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
so what do you recommend me doing? i am kind of lost right now....

mp44christos said:
so what do you recommend me doing? i am kind of lost right now....
Click to expand...
Click to collapse
Read the sticky that tells you how to fix it with fastboot?
Sent from my Galaxy Nexus

mp44christos said:
so what do you recommend me doing? i am kind of lost right now....
Click to expand...
Click to collapse
If you made a backup before, then start your device into boot loader Volume Up+Volume Down+Power button. Then go to recovery and recover your boot status. In case if you forgot to make a backup, then you should do at least one for your systems apps and then do a fresh install over again and restore system configuration afterwards.

[Q] Help i Have tried everything!!! Need a genius!

im hoping someone can help i really want to get my tablet working again! so its stuck on google logo screen i can get it into fastboot but nothings working to bring it back to life i have tried the kits i have tried it manually both get stuck at sending system. i have tried to push the factory zip by using adb sideload but it says waiting for usb debugging to be enabled which i cant do obviously since it doesnt turn on. any help would be awesome!!!

You can't use adb in the bootloader(fastboot mode). Use fastboot commands to flash a custom recovery and then use adb while in custom recovery (TWRP, CWM)
Sent from my Nexus 7 using xda app-developers app

veeman said:
You can't use adb in the bootloader(fastboot mode). Use fastboot commands to flash a custom recovery and then use adb while in custom recovery (TWRP, CWM)
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
tried it didnt work

Erica24 said:
tried it didnt work
Click to expand...
Click to collapse
That's a little lacking on info. What didn't work? Flashing the custom recovery? The adb transfer? The .zip flash? You need to provide the pertinent info if you want the correct help.
As far as the part of being stuck at sending system, this is something I have noticed when using older fast boot binaries or having a driver issue on your PC. Try downloading the sdk and updating to the newest fast boot and adb binaries. Fastboot refuses to work on my wife's laptop, and gets stuck in the exact same place. But, it works fine from mine.
Sent from my Nexus 7 using xda premium

rebel1699 said:
That's a little lacking on info. What didn't work? Flashing the custom recovery? The adb transfer? The .zip flash? You need to provide the pertinent info if you want the correct help.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i can flash custom recovery no problem but the adb transfer does not work theres no zip. on the sd card so i have to try and get it on the card to flash it because sending system through fastboot hasnt worked i tried to push it to the sd card but it says waiting for usb debugging.

Erica24 said:
i can flash custom recovery no problem but the adb transfer does not work theres no zip. on the sd card so i have to try and get it on the card to flash it because sending system through fastboot hasnt worked i tried to push it to the sd card but it says waiting for usb debugging.
Click to expand...
Click to collapse
Which custom recovery are you using? I would suggest TWRP 2.6.0.0. I always have great luck getting adb to initialize with it. Just go into the advanced menu and hit adb sideload. As a secondary measure, if you have an otg cable, you can put the zip on a flash drive and load that way too. Advanced-mount-click otg
Sent from my Nexus 7 using xda premium

Erica24 said:
im hoping someone can help i really want to get my tablet working again! so its stuck on google logo screen i can get it into fastboot but nothings working to bring it back to life i have tried the kits i have tried it manually both get stuck at sending system. i have tried to push the factory zip by using adb sideload but it says waiting for usb debugging to be enabled which i cant do obviously since it doesnt turn on. any help would be awesome!!!
Click to expand...
Click to collapse
Hi, Erica24....
I've also had issues with 'sending system' myself... many times. Indeed, when fastboot flashing 4.3 a couple of weeks ago, I had endless problems with it. I'm not sure why, but it could be because of its size.
'sending system' should take no more than a minute or so; two minutes tops.
Anyway, if you think it's taking too long, open up another command prompt window (in whatever folder you have the fastboot.exe stored in) and type...
Code:
fastboot devices
If you DON'T see a SERIAL NUMBER, it means the FASTBOOT connection has died... and you'll be sitting there for evermore waiting for system to go across.
If that is the case, disconnect from the PC, reboot the bootloader, and reconnect to a different USB port on your PC. Also, ensure you're using the original USB cable that shipped with your Nexus 7.
As I've said, for me, 'sending system', is often problematic...but changing USB ports, and trying again, has fixed it for me in the past. It's often just a case of perserverance, unfortunately.
Rgrds,
Ged.

rebel1699 said:
Which custom recovery are you using? I would suggest TWRP 2.6.0.0. I always have great luck getting adb to initialize with it. Just go into the advanced menu and hit adb sideload. As a secondary measure, if you have an otg cable, you can put the zip on a flash drive and load that way too. Advanced-mount-click otg
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have tried doing it through adb sideload but in red letters it states failed and I am to using twrp 2.6.0.0

Erica24 said:
I have tried doing it through adb sideload but in red letters it states failed and I am to using twrp 2.6.0.0
Click to expand...
Click to collapse
That's because the factory images are NOT flashable zips. You have to use fastboot on bootloader screen for factory images.
Sent from my Galaxy Nexus

I'm a geenyous!
But I'm stumped anyway.
Sent from my cell phone telephone using some sort of app...

GedBlake said:
'sending system' should take no more than a minute or so; two minutes tops.
Click to expand...
Click to collapse
Just flashed my grouper and flo back to factory last night. Both on the same computer running Ubuntu12.04. Grouper took about 15 minutes to send system, flo took less than 2 min.
Sent from my Nexus 7 using XDA Premium HD app

mr1ncred1ble said:
Just flashed my grouper and flo back to factory last night. Both on the same computer running Ubuntu12.04. Grouper took about 15 minutes to send system, flo took less than 2 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
15 minutes sounds a bit long... when it works on my grouper, it usually goes across in about 90 seconds. But the trick is getting it to work at all. Which usually involves lot's of plugging and unplugging into different USB ports, and repeatedly rebooting the bootloader. Eventually, it acquiesces... and bends to my will... 'cos I'm stubborn like that.
It's an either-or situation for me... it either goes across quickly, or it doesn't goes across at all. But eventually, it does goes across.
Rgrds,
Ged.

GedBlake said:
15 minutes sounds a bit long... when it works on my grouper, it usually goes across in about 90 seconds. But the trick is getting it to work at all. Which usually involves lot's of plugging and unplugging into different USB ports, and repeatedly rebooting the bootloader. Eventually, it acquiesces... and bends to my will... 'cos I'm stubborn like that.
It's an either-or situation for me... it either goes across quickly, or it doesn't goes across at all. But eventually, it does goes across.
Click to expand...
Click to collapse
Fastboot always works perfectly on the first try and system takes 1 minute. You might have a short in your USB cord, or faulty USB ports.

cmason37 said:
Fastboot always works perfectly on the first try and system takes 1 minute. You might have a short in your USB cord, or faulty USB ports.
Click to expand...
Click to collapse
Hi, cmason37...
Well, anythings possible, I suppose... but your explanation doesn't really hold much weight, as I never have other USB connectivity problems. And I've flashed ROMs on other devices before, without problems. Besides, the whole 'sending system' issue isn't unique to me... it's been referred to before, by others.
I have no idea why it happens, but for some reason the fastboot connection is lost when sending system (and it doesn't happen every time)... it never happens with sending boot, or recovery. I'm used to it; I know that it's not really a problem; just a temporary irritation that is eventually resolved by some USB plugging and unplugging, rebooting the bootboader a couple of times... and some very colourful expletives.
It eventually all gets resolved. And I have JellyBean 4.3, rooted, running on my N7.
But, hey... great you don't have similar inconveniences - glad that it all works for you.
Rgrds,
Ged.

Deleted Bootloader

Hello Guys!!
I have Problem.... yesterday I restarted My nexus 7 and it stopped working.... when i tried to turn it on, there appeared only google logo...
but today I tried to fix this problem and flash stock with fastboot, but there was problem with flashing boot and flashing bootloader.... and I by accident deleted bootloader with this command: fasboot erase bootloader....
so now my nexus 7 bricked verrrrry hard and it does nothing when i connect to charger, but when i connect to PC, computer says that usb device not recognised.... what to do??? is there any way to do it manually??

giokaxo said:
Hello Guys!!
I have Problem.... yesterday I restarted My nexus 7 and it stopped working.... when i tried to turn it on, there appeared only google logo...
but today I tried to fix this problem and flash stock with fastboot, but there was problem with flashing boot and flashing bootloader.... and I by accident deleted bootloader with this command: fasboot erase bootloader....
so now my nexus 7 bricked verrrrry hard and it does nothing when i connect to charger, but when i connect to PC, computer says that usb device not recognised.... what to do??? is there any way to do it manually??
Click to expand...
Click to collapse
If you had made nvflash blobs before your unfortunate fastbootery, then you should be able to restore the bootloader and partitioning. Otherwise you might be able to get a few $$$ on eBay if the screen is in good condition.

pokey9000 said:
If you had made nvflash blobs before your unfortunate fastbootery, then you should be able to restore the bootloader and partitioning. Otherwise you might be able to get a few $$$ on eBay if the screen is in good condition.
Click to expand...
Click to collapse
unfortunatelly not.... is there any way to fix this ptoblem except selling it??

You accidentally typed all that and hit enter? ???
Sorry to hear that.
Sent from my SGH-T989 using Tapatalk

kj2112 said:
You accidentally typed all that and hit enter? ???
Sorry to hear that.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Not only, ... erasing the bootloader is no problem as long as you do not reboot. Flashing a new bootloader before rebooting would have solved the situation.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Not only, ... erasing the bootloader is no problem as long as you do not reboot. Flashing a new bootloader before rebooting would have solved the situation.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
is there any solution to repair my nexus 7 :crying::crying:

If you've rebooted, it doesn't sound like there's any fix.
But I'm going off other comments. I'm no expert.
Sent from my SGH-T989 using xda app-developers app

bricked phone, tried everything

Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?

sfl007 said:
Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?
Click to expand...
Click to collapse
Phone model?
You can try to flash through LG Flash Tools

Swakiny said:
Phone model?
You can try to flash through LG Flash Tools
Click to expand...
Click to collapse
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,

sfl007 said:
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,
Click to expand...
Click to collapse
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.

markrulesallnow said:
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.
Click to expand...
Click to collapse
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?

sfl007 said:
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?
Click to expand...
Click to collapse
Try IOroot ... flash it true ADB !!

Denfic said:
Try IOroot ... flash it true ADB !!
Click to expand...
Click to collapse
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.

sfl007 said:
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.
Click to expand...
Click to collapse
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !

​
Denfic said:
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !
Click to expand...
Click to collapse
Sorry, what do you mean by "opening window in map"?

I was also in the same boat for 36 h, stuck on trwp recovery, no rom, no gaps in memory... I'm freely sailing now! I did this:
- press together power and lower button to get usb connecting screen, unplugged usb cable.
- LG tools installed and D-802 pilots {for me] installed, plug cable and check pilots again.
- launch in LG tools option for wrong install repair
- wait until the complete rom repair is installed, quite long, and then you win automatic reboot! You just loose root. Ioroot 25 again, that's all.
Hope it works for you chaps.

I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Yeh try this ... what i meant was when opening windows in adb-map ... windows -explorer !
But try the llink provided ...it will wake up your phone ..! :good:

Believe me before doing any thing using your pc just try to change the usb port first, then let it install the driver automatically(if you're using w7/8)
if windows xp just dont plug your phone remove the old LG driver and then plug your phone to another usb port that the one you have used it before with your phone and install the driver, and then proceed....
Why i am telling you this?
because i had almost the same problem with my galaxy note 2..... it wasn't recognizing my phone until i changed my usb port in download
mode and let it istall the driver......
hope it'll help.......... :good:

Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, when I try this the computer recognizes my phone as a "USB Modem Phone ADB port" in device manager. But when I follow the directions in the link above if fails at Step 24. It says the phone is not connected. It is asking for my phone to be in "Download mode" in step 17, but I can only get into Fastboot mode. Is that the issue?

Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?

sfl007 said:
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?
Click to expand...
Click to collapse
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)

Swakiny said:
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)
Click to expand...
Click to collapse
ok, it seems like it goes off. the backlight appears to be off, but when I hold the volume up button and then plug it in, it immediately goes to fastboot. ugh.
can i use fastboot to send the phone to download mode? I'll start searching for that now.....

Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Holy cow. This might be the last piece of the puzzle. I will report back after trying this.