I used the nexus toolkit to unlock my nexus 10. I allowed it to reboot from the software interface and it failed to boot into fastboot. Now it is stuck in boot loop. I've tried 100 times to press power and volume buttons to access stock recovery and all it does is vibrate. What am I doing wrong?
Sent from my Samsung Galaxy S4
First dont use toolkits second boot into fastboot and then into recovery.
Sent from my Galaxy Nexus using xda app-developers app
How do I get into fastboot? I've tried holding down power and both volume buttons but it doesn't seem to work.
Sent from my Samsung Galaxy S4
Is your device charged enough? Or doesnt it show anything at all when plugging in?
Sent from my Galaxy Nexus using xda app-developers app
When this first started yesterday it was fully charged. I believe it is low now but I have it plugged in. It shows the battery charging icon at the moment.
Sent from my Samsung Galaxy S4
Maybe it was too discharged? Have you tried after about half an hour?
Sent from my Galaxy Nexus using xda app-developers app
Just tried again. It's been charging for 4 hours and still does the same thing. I hold all the buttons down and it vibrates about every 5 seconds or so. It's strange, I've installed custom roms on several tablets and phones but never had this problem.
Sent from my Samsung Galaxy S4
Hi,
I hope you figure out how to solve the issue with your nexus by now. If you have not then I would like to tell you that I experienced the same issue. I used nexus toolkit to get back to stock room after rooted with the toolkit and then flashed Cyanogen nightly. But when I tried to boot up, the screen stuck in a bootloop. And I tried the button combination many times, all I heard was the vibration after 5 seconds. I spent days reading on the xda and Android forum but could not found out why. But then I read about Flaws in Nexus 10. One of the user mentioned that he could not get into the fastboot mode with the button combination and he returned his device as a defective unit and Google accepted it and replaced him with a new one. His conclusion was that the device actually was in fastboot mode even the screen wasn't on.
So I thought my device was suffering the same defect, so I plugged it in my laptop after hearing the vibration, my laptop recognized it and I was able to flash the stock rom. After all this, I still not manage to get into fastboot mode on my Nexus 10. A friend of mine tried to fix my tablet, he kept it for a month and only twice he managed to get the fastboot screen shown up and that occurred after when he had been playing with buttons for more that 3 hours.
I do hope that you have fixed your tablet by now, if not I hope this info will give you some clues, and sorry if you don't understand my English. It is my fourth language and I'm really not fluent at all.
I have Nexus 5, and nexus 7 2013. The button combination to fastboot works fine no problem at all.
Related
Hello Friends,
My nexus 7 is not booting up now. I was browsing internet an hour back (N7 showed battery as 7% then). Suddenly, it shutdown automatically saying low battery.
I left it in charge for 30 mins (used the cable that came along with N7). After 30 mins, I noticed the charging icon was not appearing and the screen was blinking occasionally. I tried connecting the cable to laptop and other power points but same result.
I tried pressing the power and volume down button while it is charging, the google logo, JB icon appeared but in seconds, they disappeared and the some lies appeared in a blank screen. N7 is not booting up.
Please guide me in fixing this issue. I searched in the internet and I found at least one person had the same issue but no solution was given. My N7 is also 4 months old and was imported from US.
Additional information:
1. N7 is very much in stock. Not rooted. Never attempted to root.
2. Last I checked, it had around 4 gb free (it is 8GB N7).
3. The laptop is not recognizing the device now.
Please help, guys!
"
I've had my Nexus 7 for about 4 months and it's been working good until about a couple days ago. It ran out of battery so I plugged in the charger. It began charging but something weird happened when it turned on. It started having static lines across the screen and it would work for about 3 min and then the static lines would appear. After that it would turn off. I left it charging for about 6 hrs and now it won't boot up at all. Could this be due to a cell phone sitting on top of the nexus 7 cover for a couple days? Could it be that the radio frequency from the cell phone messed up the nexus 7? I'd appreciate some help...Thanks
I had also a similar problem a week ago...
Suddently it shutdowns and I've tried many times to boot it but nothing appeared...
I charged it for 15 minutes ( no charging icon) but nothing changed...
I left it all the night in charge and tried to boot it in the morning...pressing the boot key 5 seconds nothing appeared but pressing it 25 i managed to boot up it...(yeah, 25 seconds! That was my last hope)
Since that time i don't let it turn off because of low battery...I'm always afraid it dosn't turn on...
lebrac said:
I had also a similar problem a week ago...
Suddently it shutdowns and I've tried many times to boot it but nothing appeared...
I charged it for 15 minutes ( no charging icon) but nothing changed...
I left it all the night in charge and tried to boot it in the morning...pressing the boot key 5 seconds nothing appeared but pressing it 25 i managed to boot up it...(yeah, 25 seconds! That was my last hope)
Since that time i don't let it turn off because of low battery...I'm always afraid it dosn't turn on...
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it.
I have kept it charge now. Keeping my fingers crossed.
just keep try pressing the power botton ,it's works for me
Sent from my Nexus 7 using xda premium
lebrac said:
I had also a similar problem a week ago...
Suddently it shutdowns and I've tried many times to boot it but nothing appeared...
I charged it for 15 minutes ( no charging icon) but nothing changed...
I left it all the night in charge and tried to boot it in the morning...pressing the boot key 5 seconds nothing appeared but pressing it 25 i managed to boot up it...(yeah, 25 seconds! That was my last hope)
Since that time i don't let it turn off because of low battery...I'm always afraid it dosn't turn on...
Click to expand...
Click to collapse
isotonik said:
just keep try pressing the power botton ,it's works for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. It is struck at logo now.
try to booting to the bootloader and connect to the pc . if u're PC can detect nexus 7 , no need to worri
sorry for my bad english
Sent from my Nexus 7 using xda premium
isotonik said:
try to booting to the bootloader and connect to the pc . if u're PC can detect nexus 7 , no need to worri
sorry for my bad english
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks again.
While trying to boot, I have got some options now. Start, Restart Bootloader, Recovery Mode, Power off. Which one I should try now. I have connected the N7 to PC through the cable but I dont think, the PC detects it now.
Anyway, sometimes I have to use this "brute-force" way to boot on my N7 even if I turn it off manually...
In the manual it says that pressing the boot key for 20 seconds is like a reset of the device when it doesn't boot up normally...
choose START, it will boot up normally.
just stay in the bootloader and install the driver first or you can go to the device manager in your PC, make sure driver is installed on your PC
Sent from my Nexus 7 using xda premium
isotonik said:
just stay in the bootloader and install the driver first or you can go to the device manager in your PC, make sure driver is installed on your PC
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, he has to install the drivers , but why now? If he got to the bootloader the device works...
Inviato dal mio Nexus 7
lebrac said:
Anyway, sometimes I have to use this "brute-force" way to boot on my N7 even if I turn it off manually...
In the manual it says that pressing the boot key for 20 seconds is like a reset of the device when it doesn't boot up normally...
choose START, it will boot up normally.
Click to expand...
Click to collapse
I chose Power Off. Now, the charging icon appears. And it is charging.
Good...probably it will boot up now
Inviato dal mio Nexus 7
he has said that n7 can't detect with pc.
i just wanna know the truth
if fastboot is working , meaby is time to unlock the bootloader and try costom rom
once ogain sorry for my bad english
Sent from my Nexus 7 using xda premium
lebrac said:
Good...probably it will boot up now
Inviato dal mio Nexus 7
Click to expand...
Click to collapse
I leave it at charging now. I will try to boot after an hour. I cant thank you enough for those timely replies.
isotonik said:
he has said that n7 can't detect with pc.
i just wanna know the truth
if fastboot is working , meaby is time to unlock the bootloader and try costom rom
once ogain sorry for my bad english
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If he wants to use it with the stock rom, he won't unlock the bootloader...he looses many features but it's his decision...
Inviato dal mio Nexus 7
It is still in charge. If i power on, the google and the jb logo appear but it is just struck there.
Planning to charge fully and then try to power on. I am really worried.
Sent from my GT-N7000 using xda app-developers app
try reboot in recovery and get wipe cache first.
if still get stuck .
sorry i just can give you option to unlocked your bootloader and try costom rom.
or wait until somebody who read this thread can help you
Sent from my Nexus 7 using xda premium
My wife ran into this same problem today.
Think it might be something with the latest update?
She is completely stock as well.
Maybe it didn't shut down neatly and has corrupted a file? If you can boot into recovery then if all else fails you could re-flash the os surely.
Nexus 7 Tapatalk 2
shadowclock said:
My wife ran into this same problem today.
Think it might be something with the latest update?
She is completely stock as well.
Click to expand...
Click to collapse
I read about a lot of people with this problem....and someone says that it started with 4.2 update...maybe in 4.1.2 it was ok
Inviato dal mio Nexus 7
I have a Nexus 7 tablet running 4.2 official, stock, OTA 4.2. The device isn't even rooted and somehow i turn it on today and it's stuck at the Nexus splash animation and has been for hours. I JUST fully charged the battery, i've held vol up/down and power until it resets, i've done everything and i can not make it turn on. Is it still possible to use like a Toolkit or something on an unrooted device? I don't know what happened to it. Any suggestions would be appreciated.
Thanks in advance!
Well if you haven't done anything to it just call Asus and see what's up and try and get a new device
Sent from my Nexus 7 using Tapatalk HD
Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert
Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app
I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app
The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.
It's 4 days old. Send it back as defective.
turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.
I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium
Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.
did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.
I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.
I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok
Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...
djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.
I have had a nexus 4 for a while, and I rooted it about 2-3 months ago, but today for absolutely no reason, it won't turn on (please note it was fully charged when I left it). I have tried to leave it plugged in for a while, and after I tried turning it on nothing happened. When I connected it to my computer it showed up as QHSUB_DLOAD. I don't have any custom rom or kernel, all I have is an unlocked bootloade on my rooted nexus 4. I tried holding the power button for over 30 seconds (it was suggested on another post here at XDA) and it still wouldn't do anything. Please help me, I have no idea what happened or how to fix this.
PROBLEM FIXED!
jonapunk sent me a message with a simple procedure to solve this:
"Try volume up and power for 20 sec. Then press power button one more time"
I have put his message up for everyone to see in case they encounter the same issue.
Android 9000 said:
I have had a nexus 4 for a while, and I rooted it about 2-3 months ago, but today for absolutely no reason, it won't turn on (please note it was fully charged when I left it). I have tried to leave it plugged in for a while, and after I tried turning it on nothing happened. When I connected it to my computer it showed up as QHSUB_DLOAD. I don't have any custom rom or kernel, all I have is an unlocked bootloade on my rooted nexus 4. I tried holding the power button for over 30 seconds (it was suggested on another post here at XDA) and it still wouldn't do anything. Please help me, I have no idea what happened or how to fix this.
Click to expand...
Click to collapse
There are several threads already dealing with this.
Got a new replacement Nexus 4 from google today and turned on phone and the colours were all fuzzy. After turning screen off, it doesnt turn on. Doesnt go into bootloader mode. Tried all the button combinations also.
I was using my Nexus 7 (2013) this morning surfing some sites, when all of a sudden my touchscreen just up and died. No laggy response, no jittery response, just nothing. I can't even unlock it when I wake it up. I can't power it off (as far as I know), since after I hold the power button down, I can't select Power Off.
I'm rooted running a stock 4.3 as fas as I know. Any ideas of where to begin? Thanks in advance.
Sent from my iPad using Tapatalk
I had the same issue when I didnt use it for 4 days. Touch would respond and when the power off dialog came up I couldnt touch it but just hold the power button longer and it will reboot. I held it for about 15 seconds maybe 20 and it will restart
Well, if that previous posters suggestion does not work, or any software-related solution, my first suggestion would be to send it back for a replacement, barring that, it sounds like something could have come loose, if you're the type to try it, you can see how that is addressed with the 2012 version:
Google for "How to Fix Nexus 7 Touch Screen Problems", the video is by Tampatec.
Happened to me too once but i was on a custom rom and kernel. I freaked out when the touch wasn't responding!
I held down to power button to power-off/reboot. It seemed to result in a bootloop and i wasn't exactly patient because i was freaking out a bit!
So, i powered down the device again, booted into recovery (TWRP) and to my relief the touch worked!! I just rebooted back to the system and everything was fine.
This happened to me on stock android 4.3 twice. I believe it is a software issue with the last one or two factory builds of 4.3 for this device. As previously stated, my problem was fixed by holding down the power button for about twenty seconds until it rebooted.
Sent from my Nexus 7 using Tapatalk 4
I got it to reboot and that seemed to do the trick *crosses fingers*
Sent from my XT901 using Tapatalk
Had this issue too a few days ago. I connected it to my PC and rebooted it via adb reboot command.
Occasionally I get this issue after switching the screen on running completely stock 4.3, but I can solve it by holding the power button - not to reboot, but just so the menu comes up. That alone wakes the touchscreen up for me.