Database Users

[Q]Brick ?

Hey , i havent touched my N7 forquit a while .. today i tryed to turn it on and found out it is out off power soi plugged it into my charger but when i tried to turn it up i passed the google logo and was stuck at the blackbean logo (when its connected to the charger it show the charging ani but turns off after 5 sec then i need to click the power bottom to see the charging ani again) and when i try to get into fastboot i cant . it just shows me the place where i can select between "start" , "recovery" and "fastboot" but it get stuc on that screen . i cant move anything or just hit "start" cuz it doesnt work either .
So am i bricked ? what can i do ?
i dont understand how that happened since i didnt touch it all week long .. (oh yea and the battery never charges it stays forever on the lowest point of the ani)

Leave it charge for a while without messing with it.
secondly it is not bricked, if it turns on any bit and if it shows anything on the screen it is not bricked.
I don't know why people keep using that word incorrectly, brick means that your device is basically a brick, a paperweight.
And that screen that says recovery etc IS where you fastboot from, that's the bootloader screen.
Sent from my Nexus 7 using xda premium

nodstuff said:
Leave it charge for a while without messing with it.
secondly it is not bricked, if it turns on any bit and if it shows anything on the screen it is not bricked.
I don't know why people keep using that word incorrectly, brick means that your device is basically a brick, a paperweight.
And that screen that says recovery etc IS where you fastboot from, that's the bootloader screen.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
OK , thank you .
still , l cant get to the fastoot and into the rom itself or recovery meaning i cant do nothing . how screwed am I ?

rkiller51 said:
OK , thank you .
still , l cant get to the fastoot and into the rom itself or recovery meaning i cant do nothing . how screwed am I ?
Click to expand...
Click to collapse
If you get to the menu that says "recovery" "start" "reboot bootloader" then you are in fastboot mode/bootloader.
Leave it charge a while and see if it works and if not you can flash a factory image or better yet, reflash your recovery and flash a ROM zip
Sent from my Nexus 7 using xda premium

nodstuff said:
If you get to the menu that says "recovery" "start" "reboot bootloader" then you are in fastboot mode/bootloader.
Leave it charge a while and see if it works and if not you can flash a factory image or better yet, reflash your recovery and flash a ROM zip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I cant . its in that mode but still stuck , flashing doesnt work and so is any kind of flashing .
what can i do ?

What error do you get when you try flash something by fastboot?
Sent from my Nexus 7 using xda premium

When you are 'stuck' in fastboot, you have a couple ways to go about it... one option and that is to run the N7 toolkit to get the N7 into recovery. From there you can restore your stuff, drop stuff onto your N7 to flash a new rom, etc...
http://forum.xda-developers.com/showthread.php?t=1809195
Basically you run the toolkit like you are going to root it. Then when you get past installing the USB drivers and such, IIRC there was an option to get into recovery.

Ughh, toolkits.
Sent from my Nexus 7 using xda premium

nodstuff said:
What error do you get when you try flash something by fastboot?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
kpjimmy said:
When you are 'stuck' in fastboot, you have a couple ways to go about it... one option and that is to run the N7 toolkit to get the N7 into recovery. From there you can restore your stuff, drop stuff onto your N7 to flash a new rom, etc...
http://forum.xda-developers.com/showthread.php?t=1809195
Basically you run the toolkit like you are going to root it. Then when you get past installing the USB drivers and such, IIRC there was an option to get into recovery.
Click to expand...
Click to collapse
nodstuff said:
Ughh, toolkits.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
DOESNT wrok . i am stuck at "waiting forr device" .. annoying .
now that i charged all night i can move in bootloader screen ! but when i get into recovery it is stucked in google logo and hen i plug it to the PC / charger it just get stucked and i cant move it anymore or use any tool kit . its like the device is dead !
any ideas ?

Sounds like you need to fastboot the factory image to the device. Try multiple versions of fastboot. People have been reporting problems and switching to a new version of fastboot has helped.
Sent from my Nexus 7 using XDA Premium HD app

kkl0wn said:
Sounds like you need to fastboot the factory image to the device. Try multiple versions of fastboot. People have been reporting problems and switching to a new version of fastboot has helped.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
How can i do that ?
- no recovery
- no fastboot (freez on plug)
- no boot
=nothing ?
or am i missing somthing ? i can think of a way to solve this . plz help !!

Try a new version of fastboot... possibly from one of the rootkits then follow these instructions....
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Sounds like you're in fastboot mode and the above should work. Possibly make a YouTube video to show us the problems.
http://forum.xda-developers.com/showthread.php?t=1929617 ( Here's a thread that shows what I mean. Some people have problems with certain fastboot versions.)
Sent from my Nexus 7 using XDA Premium HD app

[Q] NO OS Installed on Nexus 7

i try rooting my N7 but wiped all data on in so i have no os and im stuck in the google screen and cant do anything. i tried anything that i understood on forums, my pc wont recognize it. nexus root kit doesnt seem to work cause it say adb device not found and fastboot cant find it either. so am stuck with a n7 with no os, have tried reinstalling the stock os image from google but i cant boot the tablet at all it just stays in that google screen.
so if anyone can help me atleast try to reinstall the stock os ......because i am a noob

You have to be in boot loader mode.
Sent from my Nexus 7 using Tapatalk 2

Adb has to find the device before the adb and fastboot commands will work
Sent from my Nexus 7 using xda app-developers app

I did the same thing to my 7 the second day after I bought it. What you described is exactly what I had experienced. This is what I did to restore my 7. I kept holding the power button until it turned off. Afterwards, I charged it for a while cause the battery was low.Then I got the tablet to go into fastboot mode by holding volume down 1st and then the power button. After that, I flashed using the Nexus 7 toolkit. Upon flashing, download 4.1.2 firmware using the toolkit and flash that to your tablet. 4.2.1wouldn't work for me. That brought my 7 back to life in new stock form.
In conclusion, I re-rooted using the toolkit and flashed a custom 4.2.1 rom using TWRP recovery.
If you can get your 7 into fastboot and your computer still will not recognize your 7, reinstall the drivers to your computer. I used PDA drivers. That worked for me.
I hope this works for you.

Is OK guys just use this http://forum.xda-developers.com/showthread.php?t=:D
Sent from my Nexus 7 using xda premium

try this
SiLeNtZoR said:
i try rooting my N7 but wiped all data on in so i have no os and im stuck in the google screen and cant do anything. i tried anything that i understood on forums, my pc wont recognize it. nexus root kit doesnt seem to work cause it say adb device not found and fastboot cant find it either. so am stuck with a n7 with no os, have tried reinstalling the stock os image from google but i cant boot the tablet at all it just stays in that google screen.
so if anyone can help me atleast try to reinstall the stock os ......because i am a noob
Click to expand...
Click to collapse
try this
try the site priyanairmumbai.blogspot.in/2014/01/to-upgrade-nexus-7-and-2013-models-to.html

SiLeNtZoR said:
i try rooting my N7 but wiped all data on in so i have no os and im stuck in the google screen and cant do anything. i tried anything that i understood on forums, my pc wont recognize it. nexus root kit doesnt seem to work cause it say adb device not found and fastboot cant find it either. so am stuck with a n7 with no os, have tried reinstalling the stock os image from google but i cant boot the tablet at all it just stays in that google screen.
so if anyone can help me atleast try to reinstall the stock os ......because i am a noob
Click to expand...
Click to collapse
I DID THE SAME THING
our devices are not "bricked", just screwed really bad...
did you manage to fix it?

.
..

Flashed over nexus 7 bootloader

I accidentally flashed over my bootloader with a stupid toolkit, i usually don't use them but i wanted to experiment with one. I flashed a boot.img over my bootloader and now my cpu wont recognize my nexus 7. For some reason im having the hardest time at getting any drivers to install, maybe because im frustrated at this point. Can someone help please, would be greatly appreciated. I can give you any info you need.

If you flash the bootloader with garbage, the only hope of a rescue is if you immediately flash it again with not garbage (a valid bootloader image) before you exit fastboot mode.
If you pressed the power button to reset the device, you now have a hard brick.
Until such a time as someone cracks APX mode on the device, or Asus releases a version of "nvflash" for the N7 - there is nothing further you can do except replace the motherboard.
Sorry.

So I got it to charge while its turned off and im able to get into recovery now, but my computer still doesn't recognize my nexus. Do I need to reinstall the drivers and is there a way to install drivers without having to connect the nexus?

i fixed it, it was just me being frustrated with this thing. Sorry to take up a post

poliati said:
i fixed it, it was just me being frustrated with this thing. Sorry to take up a post
Click to expand...
Click to collapse
Eh? The part about overflashing the bootloader (with junk) was completely spurious?

How did you flash over the bootloader without the drivers?
Sent from my Infected HTC Incredible

The drivers were installed but for some reason my samsungs drivers are needing it up
Sent from my HTC One X using xda premium

[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.

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.