Database Users

How do you get into download mode?

I'm holding volume down and power. I hear the jingle but it just stays on the "Vibrant" screen... Ugh. My phone is brokedy broke.

Are you rooted?

I rooted with RyanZa's OCLF but unrooted right before doing the recent OTA update. After doing that, my phone wouldn't boot past the Vibrant screen. So now, I'm trying to get in download mode so I can use Odin to get back to stock. Nothing is working for me right now though.

Ok, I was going to tell you the easiest way to get into download mode, but your phone has to be on. It is still possible if you know how to use ADB and your phone was in debug mode.
Also, how long did you wait on the Vibrant screen before restarting it? It can take awhile. Did you have any lag fixes installed?

trunkstar1 said:
I'm holding volume down and power. I hear the jingle but it just stays on the "Vibrant" screen... Ugh. My phone is brokedy broke.
Click to expand...
Click to collapse
the best and easiest way i have found to get in to download mode is this.
1. remove batt.
2.plug usb into computer
3.put batt. in
4.hold volume down+up
5. plug usb into phone.
if you need more help with getting your phone up and running, feel free to PM me cuz i just went through this my self, i know how confusing it can get.

I had done RyanZa's lag fix but I also undid that before doing the OTA update. My phone was in debug mode, but unfortunately I don't know how to use ADB. I waited a while on the Vibrant screen but I'll try it again in case I really didn't wait long enough.
Btw, thanks for the continued assistance.

Yea.
Try this also:
Plug in your phone til you see the big battery charging icon
hold down both volume keys and power.
As soon as the battery goes away, release the power key but continue to hold volumes.. Try that..

You are essentially holding down the wrong buttons...
There after two "modes" your phone can be put into...
1. Download mode:
Done by having your phone off and then quickly turning it on and holding down JUST the up and down volume controls while having the usb already plugged in (easist I've found is stated above regarding taking the battery out, plug in usb, hold both volume buttons, then while holding them put battery back in)
2. Recovery mode:
Done by holding both up and down volume buttons AND the power button. (note: after the vibrant screen comes up, release only the power button while still holding volume buttons or else the vibrant screen will just reboot over and over)
Sent from my SGH-T959 using XDA App

Thanks all, I realized that I didn't have the right drivers installed. (duh). Thanks goes out to those who pointed me in the right direction.
The new problem I have came after accidentally pulling the USB cord out of my laptop while running ODIN. Now, all I get when trying to get in download mode is a graphic of a phone, a yellow triangle with exclamation mark, and a computer.
Anyone know what do do?

Possible brick?

So I've encountered the soft brick many times and been fine. Well now, after messing with Odin, the phone is off and won't come back on.
I've attempted turning it on with the power, power + vol up/down, plugged in, pulled the battery for a few mins and tried again, etc...
Is this a possible full on brick?

try doing it without pressing the power button

To expand a little on what chikin said
1. remove battery, sim and sd cards
2. plug in usb from phone to pc
3. holding only the volume buttons (up and down), pop the battery back in
This should launch you into dl mode. I remember last week someone was having the same issue, phone would not respong to anything and would not power on, and this method brought him to dl mode where he could use odin to flash to stock. If it doesn't work at first, keep trying, patience and persistence is the key.

Br1cK'd said:
To expand a little on what chikin said
1. remove battery, sim and sd cards
2. plug in usb from phone to pc
3. holding only the volume buttons (up and down), pop the battery back in
This should launch you into dl mode. I remember last week someone was having the same issue, phone would not respong to anything and would not power on, and this method brought him to dl mode where he could use odin to flash to stock. If it doesn't work at first, keep trying, patience and persistence is the key.
Click to expand...
Click to collapse
Oh wow, thank you so much! I was ready to drop this thing in the toilet and go make an insurance claim today.

Did you get 'er to boot?
Sent from my Br1cK'd_KA6 Vibrant via the XDA App

Damn, think I am on the same boat and it's slowing sinking. Just got my phone last night too and followed the video on how to flash the AXURA Vibrant edition rom and everything appeared to go smoothly and then after it was done I rebooted my phone and now I can't turn it on and even tried the pulled battery method mentioned here too.
How long does it take after you pop in the battery? A few seconds or a minute before something comes up on screen? Thanks.

Bricked?

Editing this as I'm desperate for help and things have moved on since I first posted, below is where I am up to post 11 of this thread.
I flashed Vegacomb b (exe), it restarted but stayed on the warning about paying for vegacomb for 10-15 minutes which didn't seem right so I held power for 6 seconds and it turned off. After that it would never turn on or go into recovery (I know all the methods, none worked).
Today I unhooked the battery, when I plug the battery back in the screen comes on for a second but then it's as it was, unresponsive. HOWEVER, if I plug the mains in with the battery disconnected then it immediately tries booting but still sticks at the warning (left for over 20 minutes). If I plug the battery in while on this screen then remove the mains it stays on. The power button is unresponsive through this so I still cannot get into recovery.
Any more ideas that haven't been mentioned?
I've tried well over 100 times to get into recovery but it's not happening
anyone willing to have a go at fixing (cheaply!) if I send them it?
Original Post:
Hi guys, just managed to (re?) install Vegacomb (b, from exe), it restarted but stayed on the white screen with the warning text about paying for Vegacomb for over 10 minutes so I held down the power button to turn it off, now I cannot do anything to boot it up (tried holding power button down from 0.5 seconds to 60 seconds!), it also won't boot into recovery. Is there anything at all that can be done to get this going?
cheers

OK, I've tried holding down back while plugging in (fully charged btw), tried all variations of button presses with back and power, with and without USB, with and without power cable.
Only got until 10PM (UK time) to get this sorted (it's now 6PM) so any help/advise would be appreciated

Flash back to modded stock then try again.
From modded stock go app drawer and run recovery
From recovery wipe data, cache then go advance then wipe dalvik
Then press back
Then install zip from SD
Choose vegacomb from whatever directory on your SD you copied it to then confirm
If you ain't Got Vegacombe zip then download it.
Or you could run the .exe again but the above is my preferred method.
Also you might need to download modded stock v2 if you ain't already got it.
Good luck.

intel007 said:
Flash back to modded stock then try again.
From modded stock go app drawer and run recovery
From recovery wipe data, cache then go advance then wipe dalvik
Then press back
Then install zip from SD
Choose vegacomb then confirm
If you ain't Got Vegacombe zip then download it.
Or you could run the .exe again but the above is my preferred method.
Good luck.
Click to expand...
Click to collapse
??
the Vega won't turn on and won't go into recovery, cannot flash anything, nothing comes up on PC, tried all variations of the back and power buttons (inc back, plug in power & usb, press power, leave 2 seconds and release back) over 100 times. it's like it's dead.
the only thing it does is show a blue LED when I plug the power cable in

I've read that if you got less than 50 or 60% battery it wont go into flash mode (back button 2 seconds - power & back 2 seconds)
Have you got enough battery cause mine takes half a day to charge.

intel007 said:
I've read that if you got less than 50 or 60% battery it wont go into flash mode (back button 2 seconds - power & back 2 seconds)
Have you got enough battery cause mine takes half a day to charge.
Click to expand...
Click to collapse
100% (solid blue LED), been on charge for over 24 hours

I'm baffled mate, I've had same issue couple of times but after 10mins or so I've always got it to power back on.

Bricked
I've had the same problem and although quite drastic, remove the rear cover and unplug the battery connection (the multipin one with red and brown/black wires).
With the mains plug out,i found that if you press volume up and power with the wires unplugged and leav eit for a few mins then use back + power it will start as you need it to.
It may take a few tries but i have managed to do it following this procedure about 7-8 times.
Hope this helps.
DAve

I had trouble getting into recovery when the Vega was 100% charged (i.e. charge led was solid blue). When I let it discharge a little so it was flashing with the charger plugged in, I managed to get into recovery then.

dmarchant said:
I had trouble getting into recovery when the Vega was 100% charged (i.e. charge led was solid blue). When I let it discharge a little so it was flashing with the charger plugged in, I managed to get into recovery then.
Click to expand...
Click to collapse
I can't discharge it though as it doesn't turn on, left it 14 hours from last night, back at work again now and it still says fully charged
got the battery disconnected now to give it a try

Disconnected battery for around 10 minutes, put it all back together, still can't boot or get to recovery
EDIT: it works when the battery is disconnected (goes to the Vegacomb warning screen but no further, cannot power off or get to recovery still)
any ideas?

Anyone got any ideas?
it's meant to be unbrickable from what I've read so there must be a way around it but I'm out of ideas!

its user error. remeber to put it into recovery mode you need the power cable plugged into it too as well as usb.

slybunda said:
its user error. remeber to put it into recovery mode you need the power cable plugged into it too as well as usb.
Click to expand...
Click to collapse
Cheers, but its not user error. I'm not that stupid

Hi, this may not help but i had trouble flashing the stock rom because of the battery being fully charged, could only get the screen to light up so left it over night and then went through the normal routine and got into recovery.
Bill

Hi there
Just one question, how do you know for sure it hasn't gone into nvflash mode?
I know what you are going through trying to get the ruddy thing into nvflash, it's a mare if you don't quite get that timing right but seeing as the screen doesn't light up when it's in nvflash what is telling you whether you are actually in it, other than the screen coming on to say you are not or relying on a windows message?
As I said I had the same problems many a time but I use Audi tool now to tell me if nvflash has started, I got it off the Modaco forum, but when you are in nvflash it actually tells you so rather than relying on perhaps windows to tell you it has happened
If you haven't come across the audi tool before then just do a search for it on Modaco, I don't know if they have got it here on XDA.

mmace said:
Anyone got any ideas?
it's meant to be unbrickable from what I've read so there must be a way around it but I'm out of ideas!
Click to expand...
Click to collapse
wow, i'm quite surprised by the number of people who are taking their batteries out when they think there is a problem. You should never need to do this unless it is actually faulty.
Ok yes the Vega is nearly indestructible I have had my in a complete mess many times and have never had to do anything that hard to recover. Some times it will be a pain to get into nvflash mode but this can always be done just have to be patient and know a couple of tricks.
If you have tried the back button and then the power a few times and nothing there is another method.
Instead unplug the power then hold the back button down, whilst holding down the back button plug in the power release the back button after a couple of seconds (I like to count to 5)
I am hoping that you already have the USB cable connected and the right drivers installed on your PC.
Billy..
If you need more help head over to TabletRoms and look in the Vega forum (sorry XDA guys just there is a lot of other useful information there)

wks said:
Hi, this may not help but i had trouble flashing the stock rom because of the battery being fully charged, could only get the screen to light up so left it over night and then went through the normal routine and got into recovery.
Bill
Click to expand...
Click to collapse
I've tired fully charged and letting the battery drain for 40+ mins after it's been on the "warning" screen
mitt69 said:
Hi there
Just one question, how do you know for sure it hasn't gone into nvflash mode?
I know what you are going through trying to get the ruddy thing into nvflash, it's a mare if you don't quite get that timing right but seeing as the screen doesn't light up when it's in nvflash what is telling you whether you are actually in it, other than the screen coming on to say you are not or relying on a windows message?
As I said I had the same problems many a time but I use Audi tool now to tell me if nvflash has started, I got it off the Modaco forum, but when you are in nvflash it actually tells you so rather than relying on perhaps windows to tell you it has happened
If you haven't come across the audi tool before then just do a search for it on Modaco, I don't know if they have got it here on XDA.
Click to expand...
Click to collapse
I have Audi, I also have Device manager open, I know 100% it's never gone into recovery mode sine I started with this problem.
BillyFish said:
wow, i'm quite surprised by the number of people who are taking their batteries out when they think there is a problem. You should never need to do this unless it is actually faulty.
Ok yes the Vega is nearly indestructible I have had my in a complete mess many times and have never had to do anything that hard to recover. Some times it will be a pain to get into nvflash mode but this can always be done just have to be patient and know a couple of tricks.
If you have tried the back button and then the power a few times and nothing there is another method.
Instead unplug the power then hold the back button down, whilst holding down the back button plug in the power release the back button after a couple of seconds (I like to count to 5)
I am hoping that you already have the USB cable connected and the right drivers installed on your PC.
Billy..
If you need more help head over to TabletRoms and look in the Vega forum (sorry XDA guys just there is a lot of other useful information there)
Click to expand...
Click to collapse
TabletRoms has been no help for me, there's been no reply at all for my problem but there has here and at MoDaCo. I pulled the battery as a last resort as NOTHING is working, I've tried all the tricks at least 2 dozen times, some a hundred +, including the one you mention

Well I don't want to teach you to suck eggs, but I take it you did use Audi to delete and replace your drivers.
And then when powering on the Vega you held the back button for 2 secs and then the back and power buttons for 6 secs to get the Vega detected?
For me I can only see that there can only be 3 other possible causes
1./ the back button is broken on the vega
2./ The USB port on your PC or on the Vega has gone up the swanee
3./ The USB lead is no good
The Vega may be unbrickable but if the back button or the USB port has had it then .....

Yeah, tried it, cheers.

I think I'm bricked?

I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.

You fool.

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium

Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312

overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.

I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2

ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7

Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up

KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.

So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7

abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.

Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before

First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.

So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?

Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it

Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.

abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way

dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?

[Q] Nexus 10 wont turn on.

I placed my nexus 10 on charging yesterday, and after a while (2-4 hours later) when i came back, i found the device to be turned off, I tried the power button in all the combination with volume buttons, but still no luck (even held the power button for 3mins) I searched online, and couldnt find any help on other forums. Some said to keep it on charging overnight and then try powering it up. But still no luck.
I dont get any notification when i connect it to charger, although when i press the power button while connected the screen lights up, and battery charging sign shows up.
Any help would be greatly appreciated.

epicbearman said:
I placed my nexus 10 on charging yesterday, and after a while (2-4 hours later) when i came back, i found the device to be turned off, I tried the power button in all the combination with volume buttons, but still no luck (even held the power button for 3mins) I searched online, and couldnt find any help on other forums. Some said to keep it on charging overnight and then try powering it up. But still no luck.
I dont get any notification when i connect it to charger, although when i press the power button while connected the screen lights up, and battery charging sign shows up.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
So you cannot even get to the recovery?
You ether over charged it (very unlikely to happen) or you have a faulty N10.
Sent from my Nexus 4

andyabc said:
So you cannot even get to the recovery?
You ether over charged it (very unlikely to happen) or you have a faulty N10.
Sent from my Nexus 4
Click to expand...
Click to collapse
No, can't even get to recovery. But i have been using the device for over two months now, nothing like this ever happened. What about the charging sign when i press the power button. It might be some kind of a sleep mode or something, no?

epicbearman said:
No, can't even get to recovery. But i have been using the device for over two months now, nothing like this ever happened. What about the charging sign when i press the power button. It might be some kind of a sleep mode or something, no?
Click to expand...
Click to collapse
Could be a bootloader corruption, software issue, hardware issue or some part of the hardware "thinks" that it is still on when it is not causing it to not switch on.
Have you noticed any issues before it just came off like extreme overheating?
Sent from my Nexus 4

andyabc said:
Could be a bootloader corruption, software issue, hardware issue or some part of the hardware "thinks" that it is still on when it is not causing it to not switch on.
Have you noticed any issues before it just came off like extreme overheating?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well, yes the tablet was getting overheated after a long session of hd videos, or games, but that use to happen all the times.

I believe this is normally called a "Sleep of Death" or sometimes "screen off death". Hold power + vol up + vol down at the same time for 5 seconds and you should boot into fastboot. From there hit the power button to turn the tablet on. Then go about finding a better ROM/kernel combo that doesnt give you this problem.

EniGmA1987 said:
I believe this is normally called a "Sleep of Death" or sometimes "screen off death". Hold power + vol up + vol down at the same time for 5 seconds and you should boot into the bootloader. From there hit the power button to turn the tablet on. Then go about finding a better ROM/kernel combo that doesnt give you this problem.
Click to expand...
Click to collapse
Like i said, its not working i tried using that combination, it wouldnt budge. Screen wont even turn on.

EniGmA1987 said:
I believe this is normally called a "Sleep of Death" or sometimes "screen off death". Hold power + vol up + vol down at the same time for 5 seconds and you should boot into the bootloader. From there hit the power button to turn the tablet on. Then go about finding a better ROM/kernel combo that doesnt give you this problem.
Click to expand...
Click to collapse
You just need to press power and volume down to enter the bootloader.
Sent from my Nexus 4
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
epicbearman said:
Like i said, its not working i tried using that combination, it wouldnt budge. Screen wont even turn on.
Click to expand...
Click to collapse
Try press and holding the power button for around 10 seconds and then try powering it up again.
Sent from my Nexus 4

Are you using the charger/cable that came with your device?

Its working.
Weird how it was taking any input from the power button though. I kept the tablet on charging over night and i tried turning it on in the morning and it worked.
Thank you all.

epicbearman said:
Its working.
Weird how it was taking any input from the power button though. I kept the tablet on charging over night and i tried turning it on in the morning and it worked.
Click to expand...
Click to collapse
I've had my Nexus 10 for less than a week, and this morning I encountered this problem. I was working on setting up syncing through an app called FolderSync and SugarSync. Syncing of one of the folders seemed to go into a loop. The device locked up completely a couple times. I got the process running again and left it running while I went for a workout. When I came back no way could I get it turned on.
I had tried all the things suggested here before checking here for help. I'll try your "solution" of leaving the device on charge overnight. If I can't get it going tomorrow morning I'll return it to Staples, where I bought it.
I have an iPad and have never encountered anything even close to these problems. Bought the Nexus 10 specifically to run the Vim Touch app for Android. The only Vim app for the iPad is horribly crippled.
Sounds like this thread pretty much exhausted the possibilities by the time epicbearman discovered his "solution," but if by chance anyone has any further suggestions I would be grateful.
Thanks,
Eric Weir

I had the exact problem as the OP and none of my chargers worked. I then googled and found someone that said to try to charge via their PC USB instead of the wall charger. I left it plugged into the USB for a couple of hours and the charge went to 4% ( so it must have been very dead ) and all is well.

I charged it via the usb charger, and connected it to my pc overnight. Try doing that.

Take off the back and disconnect the battery and reconnect it
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2

IRX120 said:
Take off the back and disconnect the battery and reconnect it
Click to expand...
Click to collapse
Thanks. If I'd gotten this in time, I suspect it would've worked. But when I couldn't get it started after trying everything else and leaving it on charge overnight, I returned it to Staples.
Will order a Nexus 7 from Google. If I can get Vim Touch running successfully---my reason for wanting an Android tablet---and I find the screen to small for heavy writing---I want to get by with a soft keyboard---I'll order another 10 and give the 7 to my daughter.
Thanks again,
Eric Weir