Related
Hi there, have a specific problem, tried to google and search through the forum but no success.
I have stock ROM with 4.2.1 android, no root etc., I was browsing web via Firefox, opened 3 pages, battery cca 48% when suddenly everthing freezed, even home button and whole screen become unresponsive. I pressed the Power button for several seconds to turn it off and to restart it, however the screen is off all the time. I have tried to do hard reset, hold the power button for 30-180 seconds, hold all 3 hardware buttons for 30-180 seconds, hold just power and one volume button, connect to PC (always connects as Unknown device, not able to load any driver), tried all of this with and without power supply connected. After all this I am still not able to boot the device. Any idea?
Try unbricking Nexus 7 guide
Hi, you should always be able to get your Nexus 7 back to factory defaults by following one of the many "unbrick nexus 7" guides, like:
http://forum.xda-developers.com/showthread.php?t=1781250
Good luck !
unfortunately I am not able to flash it as my screen is still black, I do not see whether it is on or not, I am also not able to connect it to computer as it still pops up message that the device is unknow and I am not able to install any driver for it, nor automatically, nor google usb drivers... still getting unknown device message...
I'd just return it to Google and get a new one
Sent from my Nexus 7 using Tapatalk HD
harweyko said:
unfortunately I am not able to flash it as my screen is still black, I do not see whether it is on or not, I am also not able to connect it to computer as it still pops up message that the device is unknow and I am not able to install any driver for it, nor automatically, nor google usb drivers... still getting unknown device message...
Click to expand...
Click to collapse
Ouch ! That sounds like a broken device to me. I'd also RMA it.
Have you try plugging your tablet into your charger and check if your device is charging or not? (you'll see a battery status in the center of the screen) if so try to charge it for an hour or so and then after that try to press the ff.
while your tablet is off press and hold both vol. up and vol. down button then press and hold the power button. keep it press for at least 10 secs. and see if you can go/access your fastboot mode..
charged for more than 4 hours, tried that, did not helped, already sent for repair... hopefully will be changed for new one...
Just pry off the back and unplug the battery, ubereasy and will work fine again. Unless you got a lemon
Sent from my Nexus 7 using xda app-developers app
so at the end it was faulty motherboard, so I receveid new device...
I'm stupid. Like really really stupid. Here's the story.
I'm a very basic ubuntu on PC user, so when I found out they'd released Ubuntu Touch, I googled it immediately. The download site said in no uncertain terms that "THIS IS A DEVELOPER PREVIEW IMAGE, NOT FOR GENERAL USERS", but I said what the hey, I'll just reflash the stock image if something goes wrong.
The installation went successfully, but Ubuntu wasn't taking any keyboard input to get past the initial setup phase. I was already looking at 3 hours of sleep before work so I just flipped my nexus case shut and went to sleep.
Now that I'm at work and trying to power up the thing, nothing happens. The screen flickers for a fraction of a second when I keep power + vol down pressed, but it keeps looping in that flickering mode. When I plug it into a charger, it doesn't show a charging symbol (it would only show that if it were off, so maybe ubuntu is still running?)
I restarted it at least a couple of times without issue when Ubuntu wasn't recording my keyboard touches, and I'm positive now that Ubuntu didn't put my tablet into sleep mode when I flipped the lid shut (like I was used to with the factory rom) so the battery is dead, but it should at least still give a battery charging indication?!
I also read somewhere that it might help to keep the power button pressed for 30 seconds, but that didn't do anything. I feel like taking the darn thing apart and yanking the battery, the caveman approach. RIP IT APART!
If I can put it into fastboot mode, all my problems will be over, I can take over from there. But what do I do to get it there, other than the normal, obvious power + vol down?
Helpful suggestions are most welcomed, as well as rants telling me how I shouldn't have done what I did
Forgot to mention that the computer gives no indication that a device has been plugged in. Also hey! My screen is on constant flicker now, something like one of those old television sets.
Give a shot at a force restart. Hold the power button for like 20 seconds. And start it up while holding power and volume down.
Sent from my MB612 using xda app-developers app
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
Didn't notice you said you tried already lol. Hmmmm a battery pull would definitely help but I know you don't want to open your case. Only things I can think of would be the force reset, letting the battery die completely, or a restart through adb which won't work since its not picking up a device on your computer.
Sent from my MB612 using xda app-developers app
I managed to get it to work, apparently the battery was down, and since I couldn't even get it to turn off all the way it wasn't even showing the battery indicator it shows while off.
I'm now able to get into CWM recovery and fastboot but fastboot isn't recognizing that a device is plugged in. I used USBDeview to remove all drivers and reinstalled them but still no go. And all the guides I'm reading are asking me to put the device into USB debugging but I can't do that since there is no OS on the device at all, not Ubuntu, not JB.
I tried to sideload "image-nakasi-jdq39.zip" using CWM but that didn't work...
* daemon started successfully *
error: device not found
And fastboot just keeps saying "waiting for device".
Update your adb and fast boot binaries. Adb debugging doesn't matter at all in fastboot
Sent from my Nexus 7 using Tapatalk HD
Thanks a lot, both of you. It's working now, just going through the initial setup. Thanks a lot!
Hello all,
Recently I have had a major issue with my nexus 7. About a week ago, it died (ran out of battery) while I was using it. When I attempted to turn it on after charging it, I would get the screen that says google, with unlocked lock icon. The tablet would be frozen at this screen. I left it running until it died again. I was running the latest stable release of cyanogenmod 10 with no problems before when this happened.
By now I had realized that the nexus may have been bricked. I did some googling and found that this is an issue other users have been having when their battery died on android 4.2.2. I attempted to restore the nexus. At this time I was able to access bootloader on the device by holding down all of the buttons at the same time. However, I decided not to restore the nexus, and wait until a time where I would be able to turn all of my attention to the problem. But when I tried to restore the device yesterday, I was not able to access bootloader! I connected the device to my PC (running win8) and it is not recognized. Similarly, trying fastboot restart-bootloader gives me "waiting for device". I am afraid that the bootloader may have been corrupted somehow.
My question is, how can I fix this? Is there a way to reflash the bootloader, or is there something that I am missing? Is there a hardware operation that needs to be performed on the device (battery pull, etc)?
Thanks.
AW: [Q] Help! Nexus 7 not working, may be bricked
I doubt your nexus is bricked. Most likely you entered the APX mode. Hold down the power button for about 6-10 seconds, then it should exit from there.
http://forum.xda-developers.com/wiki/APX_mode
Sent from my Nexus 7 using xda app-developers app
Not working
AndDiSa said:
I doubt your nexus is bricked. Most likely you entered the APX mode. Hold down the power button for about 6-10 seconds, then it should exit from there.
http://forum.xda-developers.com/wiki/APX_mode
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I hold down the power button, the device just turns off and comes back on again. The google boot logo shows for a few seconds, then I get a black screen.
patil215 said:
When I hold down the power button, the device just turns off and comes back on again. The google boot logo shows for a few seconds, then I get a black screen.
Click to expand...
Click to collapse
If you get a Google logo, that is a good sign - it means the bootloader is at least partially intact, possibly even in perfect shape.
I would proceed assuming that your battery is completely discharged.
Put the device on the charger overnight and then try starting it up while it is still plugged in to the charger. Hold the vol-down button and the power button continuously until at least one second after the Google logo flashes - this should put the device into fastboot mode if the bootloader is intact.
Something to remember is that Li-Ion batteries have a safety feature that prevents them from charging if the battery voltage gets too low. This is part of the reason why they are shipped with a 50% charge - they can sit that way for months and months only self-discharging at a very very slow rate.
OTOH, if you discharge the battery deeply and then let it sit for a long time afterward - especially if there is something like APX mode draining current - the battery voltage can fall below this "safety threshold voltage" and (even though it is still a "good battery" it can no longer be charged).
I'm not sure it the N7 can be started up while plugged in to only the charger; if it can, disconnecting the battery and trying to power up the device might be a way to discriminate "dead device" from "unchargeable battery".
good luck
I've tried this before
bftb0 said:
If you get a Google logo, that is a good sign - it means the bootloader is at least partially intact, possibly even in perfect shape.
I would proceed assuming that your battery is completely discharged.
Put the device on the charger overnight and then try starting it up while it is still plugged in to the charger. Hold the vol-down button and the power button continuously until at least one second after the Google logo flashes - this should put the device into fastboot mode if the bootloader is intact.
Something to remember is that Li-Ion batteries have a safety feature that prevents them from charging if the battery voltage gets too low. This is part of the reason why they are shipped with a 50% charge - they can sit that way for months and months only self-discharging at a very very slow rate.
OTOH, if you discharge the battery deeply and then let it sit for a long time afterward - especially if there is something like APX mode draining current - the battery voltage can fall below this "safety threshold voltage" and (even though it is still a "good battery" it can no longer be charged).
I'm not sure it the N7 can be started up while plugged in to only the charger; if it can, disconnecting the battery and trying to power up the device might be a way to discriminate "dead device" from "unchargeable battery".
good luck
Click to expand...
Click to collapse
I've tried this before. I still get a google screen, even after fully charging it. Does this mean that the battery has become unusable? How can I fix this?
Then try it again. It takes less time than typing a post into XDA.
There are two ways to try it.
1) Hold both Power & Vol-Down simultaneously, and keep holding them down until at least 4 seconds after the B&W "Google" text appears on the screen
2) Hold only the Power button down continuously, but be ready! Press the Vol-Down button as soon as the Google logo appears! - you only get less than a second to do this. (If you are late, the bootloader tries to boot the boot partition). Also, you need to keep holding the Power button down (3 or 4 seconds) after this - wait long enough that you are convinced that the fastboot screen is not going to occur.
As for the battery, you can pop off the back case and use a voltmeter to CAREFULLY measure the open-circuit voltage. The normal 0%-to-100% voltage range is about 3.6v - 4.15v. Obviously if it won't take a charge then there is a battery issue. BE CAREFUL - avoid doing anything which could short the terminals even momentarily.
bftb0 said:
Then try it again. It takes less time than typing a post into XDA.
There are two ways to try it.
1) Hold both Power & Vol-Down simultaneously, and keep holding them down until at least 4 seconds after the B&W "Google" text appears on the screen
2) Hold only the Power button down continuously, but be ready! Press the Vol-Down button as soon as the Google logo appears! - you only get less than a second to do this. (If you are late, the bootloader tries to boot the boot partition). Also, you need to keep holding the Power button down (3 or 4 seconds) after this - wait long enough that you are convinced that the fastboot screen is not going to occur.
As for the battery, you can pop off the back case and use a voltmeter to CAREFULLY measure the open-circuit voltage. The normal 0%-to-100% voltage range is about 3.6v - 4.15v. Obviously if it won't take a charge then there is a battery issue. BE CAREFUL - avoid doing anything which could short the terminals even momentarily.
Click to expand...
Click to collapse
I've tried holding down the buttons in various configurations at least 50 times already. As for the battery, there is current flowing, so I don't think this is a battery issue. Also worth noting is that if the device completely dies and I plug it in again, the charging battery sign appears (an empty battery slowly filling with white bars). Sometimes the device will give a black screen with little white sparks flickering randomly on it.
Well there have been several posts on here with identical symptoms, where the affected owner later reported that their tablet mysteriously started operating normally.
Unfortunately nothing consistent seems to have emerged from those reports.
You could try disconnecting the battery for a few minutes and reconnecting it to see if that makes any difference.
But whatever you do, you're gonna eventually have to press some buttons & the procedure I suggested is diagnostic for the bootloader, even if the boot or /system partition are borked.
BTW In my experience that battery charging graphic shows the charge state of the battery - does yours show closer to empty or full?
bftb0 said:
Well there have been several posts on here with identical symptoms, where the affected owner later reported that their tablet mysteriously started operating normally.
Unfortunately nothing consistent seems to have emerged from those reports.
You could try disconnecting the battery for a few minutes and reconnecting it to see if that makes any difference.
But whatever you do, you're gonna eventually have to press some buttons & the procedure I suggested is diagnostic for the bootloader, even if the boot or /system partition are borked.
BTW In my experience that battery charging graphic shows the charge state of the battery - does yours show closer to empty or full?
Click to expand...
Click to collapse
Mine shows the battery going from empty to full, like an animation. Also, I'm considering sending in the device for repair but I know that since the bootloader is unlocked it probably wouldn't be free.
Also can you link me to any posts related to this? They might be useful in solving my problem.
Thanks
Were you able to get your computer to recognized your Nexus when you connected it? I had to jump through a bunch of hoops with my Win8 machine to get the driver installed, because it didn't pass Microsoft's signature check. Maybe you can use Wug's toolkit to try to fix it, or at least re-lock the bootloader before sending it in for repair?
codehunter2000 said:
Were you able to get your computer to recognized your Nexus when you connected it? I had to jump through a bunch of hoops with my Win8 machine to get the driver installed, because it didn't pass Microsoft's signature check. Maybe you can use Wug's toolkit to try to fix it, or at least re-lock the bootloader before sending it in for repair?
Click to expand...
Click to collapse
After spending a few hours, I was able to get an adb driver installed onto my computer, I also had to jump through a lot of hoops (I run win8 too). Running adb devices shows the nexus in recovery mode. However, I can't access the bootloader whatsoever. Typing fastboot reboot-bootloader just hangs, and I've tried several toolkits but they just hang. I'm not sure if I can do anything unless I can access bootloader. If you know anything I can do please tell.
patil215 said:
Mine shows the battery going from empty to full, like an animation. Also, I'm considering sending in the device for repair but I know that since the bootloader is unlocked it probably wouldn't be free.
Click to expand...
Click to collapse
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27541 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
patil215 said:
After spending a few hours, I was able to get an adb driver installed onto my computer, I also had to jump through a lot of hoops (I run win8 too). Running adb devices shows the nexus in recovery mode. However, I can't access the bootloader whatsoever. Typing fastboot reboot-bootloader just hangs, and I've tried several toolkits but they just hang. I'm not sure if I can do anything unless I can access bootloader. If you know anything I can do please tell.
Click to expand...
Click to collapse
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
bftb0 said:
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27451 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
Click to expand...
Click to collapse
Can I have the links that you mentioned about users having identical symptoms that "fixed themselves"?
I really don't want to send it in for repairs if it's going to cost me. I'm a student with not much money to spare . One of the reasons I bought the nexus 7 in the first place.
bftb0 said:
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27451 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
Click to expand...
Click to collapse
I also fully charged the nexus 7 overnight. The battery icon now showed no animation because the battery was full (it first showed a picture of the lighting bolt battery, then a picture of a full battery) so I believe that the battery is working correctly.
patil215 said:
Can I have the links that you mentioned about users having identical symptoms that "fixed themselves"?
I really don't want to send it in for repairs if it's going to cost me. I'm a student with not much money to spare . One of the reasons I bought the nexus 7 in the first place.
Click to expand...
Click to collapse
I didn't make a record of them - you will need to search. What sounded very familiar was when you had said
patil215 said:
...black screen with little white sparks flickering...
Click to expand...
Click to collapse
What I recall - probably imperfectly - was that most of those cases seemed to spontaneously resolve when the owner charged their battery. And since your story started out with "black screen and little white sparks flickering", and "low battery" it sounded quite similar.
The various folks who mentioned this said things like "white lines flashing", "like sparks", or "like snow on an old-fashioned TV screen". Don't know if that will help you search, but they are in this forum (Q&A).
I also don't know if their tablets were in one particular mode or another (judging from a PC connected to the tablet - a black screen on the tab doesn't tell you anything) - I don't think any of them reported this.
As I said previously, that Black and White Google logo is produced by the bootloader. I just started my tablet in APX mode right now, and while the "charging battery" icon shows up when using the APX cold-start sequence (Vol-Up+Power), that B&W Google (text) Logo does not show up on the screen - the tablet goes directly from battery charging to APX mode (detected by looking at the PC - device shows up under "Other devices -> APX" in the device manager; VID/PID pair USB\VID_0955&PID_7330&REV_0103
)
So, my point is that it sure seems like your bootloader is there and capable of at least starting up at least part way.
What if your Vol-Down button was not working and you had a borked "boot" partition? If you had that combination, the bootloader wouldn't go into fastboot mode, as it would never see the Vol-Down keypress... and if your boot partition was borked, then you would never get any boot accompanied by a black screen.
At this point I think you should try observing the behavior of the USB port from the PC while trying to start it up... and even though you've tried it before, see if you can get the fastboot screen to appear. Perhaps there is something funky going on with your Vol-down button.
good luck
bftb0 said:
I didn't make a record of them - you will need to search. What sounded very familiar was when you had said
What I recall - probably imperfectly - was that most of those cases seemed to spontaneously resolve when the owner charged their battery. And since your story started out with "black screen and little white sparks flickering", and "low battery" it sounded quite similar.
The various folks who mentioned this said things like "white lines flashing", "like sparks", or "like snow on an old-fashioned TV screen". Don't know if that will help you search, but they are in this forum (Q&A).
I also don't know if their tablets were in one particular mode or another (judging from a PC connected to the tablet - a black screen on the tab doesn't tell you anything) - I don't think any of them reported this.
As I said previously, that Black and White Google logo is produced by the bootloader. I just started my tablet in APX mode right now, and while the "charging battery" icon shows up when using the APX cold-start sequence (Vol-Up+Power), that B&W Google (text) Logo does not show up on the screen - the tablet goes directly from battery charging to APX mode (detected by looking at the PC - device shows up under "Other devices -> APX" in the device manager; VID/PID pair USB\VID_0955&PID_7330&REV_0103
)
So, my point is that it sure seems like your bootloader is there and capable of at least starting up at least part way.
What if your Vol-Down button was not working and you had a borked "boot" partition? If you had that combination, the bootloader wouldn't go into fastboot mode, as it would never see the Vol-Down keypress... and if your boot partition was borked, then you would never get any boot accompanied by a black screen.
At this point I think you should try observing the behavior of the USB port from the PC while trying to start it up... and even though you've tried it before, see if you can get the fastboot screen to appear. Perhaps there is something funky going on with your Vol-down button.
good luck
Click to expand...
Click to collapse
UPDATE!:
Not sure if this will help at all. But I ran adb -d reboot bootloader, and the device just turned off. Completely. I turned it on again by holding power for 15 seconds but I got the exact same thing as before (google with black screen following). Once the device was on and I connected it to Windows, windows said "Windows detected malfunctioning device". But I couldn't duplicate the results again. Running adb -d reboot bootloader just hangs.
patil215 said:
UPDATE!:
Not sure if this will help at all. But I ran adb -d reboot bootloader, and the device just turned off. Completely. I turned it on again by holding power for 15 seconds but I got the exact same thing as before (google with black screen following). Once the device was on and I connected it to Windows, windows said "Windows detected malfunctioning device". But I couldn't duplicate the results again. Running adb -d reboot bootloader just hangs.
Click to expand...
Click to collapse
Incredibly, extra-ordinarily bizzare. ADB on the tablet side is a daemon process that runs in userspace. You would need a completely functional kernel to be running on the tablet, and a functioning ramdisk too in order to communicate with the tablet. ADB does not talk to fastboot mode, nor any other mode of the bootloader.
IF YOU ARE REALLY SHUTTING YOUR DEVICE OFF AND THEN SOMETIME LATER YOU ARE ABLE TO TALK TO THE TABLET BY USING THE adb COMMAND (not fastboot), THAT MEANS THAT THE BOOTLOADER IS SUCCESSFULLY BOOTING SOME (unknown) LINUX KERNEL.
That truly beggars the question of why you are seeing anything on the screen after the google logo. Did the previous ROM not have a splash-screen?
Well, if you can communicate with ADB it might be appropriate to try:
adb reboot recovery
and see what this does.
If you can find the device in the Windows device manager, what would be really, really helpful would be the device VID/PID pair.
The way you do this is like this:
1) Identify the device in device manager; right-click on it and select "Properties"
2) Select the "Details" tab
3) In the "Property" Combo-box pulldown, select the Property Name"
Hardware Ids
If you can get those values we can identify exactly which mode the device is in. There is a decoder ring at the end of the first post in this thread
OK, I'm starting to get fatigued, as I offer up both things to attempt as well as avenues of exploration, and you seem to simply ignore all of it.
I know you have tried it several times, maybe even a million times. Please try both methods of starting the tablet to try and intercept the initial phase of the bootloader startup and see if you can get the tablet to go into fastboot mode.
It's OK to try it and fail. But in all this back-and-forth, not once have you said, "yes I tried it again and it still failed". Try it and report the result, even if it fails.
Please try it again - both methods. In the second method where you click the Vol-Down button only after you see the B&W "Google" text, you need to do it really quickly - and not let your finger off the Power button either for several seconds.
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
PS
The "-d" option to the adb command should only be needed if you were running an emulator via the Google SDK on the same PC.
If that were the case, when you ran the command
Code:
adb devices[/url]
you would see multiple lines of output indicating multiple devices on the machine - one for each running emulator, and one for the actual hardware device (so long as it is actually booted into a recovery or OS and you have the right drivers installed).
bftb0 said:
Incredibly, extra-ordinarily bizzare. ADB on the tablet side is a daemon process that runs in userspace. You would need a completely functional kernel to be running on the tablet, and a functioning ramdisk too in order to communicate with the tablet. ADB does not talk to fastboot mode, nor any other mode of the bootloader.
IF YOU ARE REALLY SHUTTING YOUR DEVICE OFF AND THEN SOMETIME LATER YOU ARE ABLE TO TALK TO THE TABLET BY USING THE adb COMMAND (not fastboot), THAT MEANS THAT THE BOOTLOADER IS SUCCESSFULLY BOOTING SOME (unknown) LINUX KERNEL.
That truly beggars the question of why you are seeing anything on the screen after the google logo. Did the previous ROM not have a splash-screen?
Well, if you can communicate with ADB it might be appropriate to try:
adb reboot recovery
and see what this does.
If you can find the device in the Windows device manager, what would be really, really helpful would be the device VID/PID pair.
The way you do this is like this:
1) Identify the device in device manager; right-click on it and select "Properties"
2) Select the "Details" tab
3) In the "Property" Combo-box pulldown, select the Property Name"
Hardware Ids
If you can get those values we can identify exactly which mode the device is in. There is a decoder ring at the end of the first post in this thread
OK, I'm starting to get fatigued, as I offer up both things to attempt as well as avenues of exploration, and you seem to simply ignore all of it.
I know you have tried it several times, maybe even a million times. Please try both methods of starting the tablet to try and intercept the initial phase of the bootloader startup and see if you can get the tablet to go into fastboot mode.
It's OK to try it and fail. But in all this back-and-forth, not once have you said, "yes I tried it again and it still failed". Try it and report the result, even if it fails.
Please try it again - both methods. In the second method where you click the Vol-Down button only after you see the B&W "Google" text, you need to do it really quickly - and not let your finger off the Power button either for several seconds.
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
PS
The "-d" option to the adb command should only be needed if you were running an emulator via the Google SDK on the same PC.
If that were the case, when you ran the command
Code:
adb devices[/url]
you would see multiple lines of output indicating multiple devices on the machine - one for each running emulator, and one for the actual hardware device (so long as it is actually booted into a recovery or OS and you have the right drivers installed).[/QUOTE]
Sorry for not indicating the results of all of your suggestions.
Believe me, I have probably tried both of your button combinations at least two dozen times already. And I have gone down every avenue of exploration that you've suggested.
I've even tried every single one of the button combinations in the thread of nexus 7 button combinations. When I do anything from when the device is on, after 5 seconds or so the device turns off. Then the tablet shows the Google screen for about 5 seconds, no matter what I do. After the google screen comes a blank black screen (I can tell the device is still on because it's illuminated black, different from if the device was dead or powered off). There's not even a way I can get the tablet to power off - it just automatically restarts even if it's not connected to power, so I have to let it die or do a battery pull if I want to fix it. The black screen remains there indefinitely (until the battery runs out of course).
I've tried disconnecting the battery, leaving it disconnected for 30 minutes, connecting the device to power with the battery disconnected, having the buttons held down and connecting the tablet to wall power and USB pc, and different chargers. Nothing gives me a different result. The battery is alive and working, and the voltimeter did give me a current, sorry for not posting that earlier. About the random sparks/snow, there is really no pattern to when these appear, although they might be more frequent (but it might just be me) after a battery pull or full battery discharge.
Remember, I used to be able to access the bootloader but that stopped working for some reason. I'm kicking myself right now for not restoring the tablet when I was able to access bootloader, but I was busy at the time.
I've had some experience with rooting, locking, and unlocking other android devices, but this is something extremely weird.
Also, I should have posted the hardware ID's of the device before. I had done the exact same thing as you suggested when I was trying to install an adb driver for the nexus 7 (had to jump through a lot of hoops to get it working on win8, goddamn win8). The hardware ID's are USB\VID_18D1&PID_D001&REV_9999 and USB\Vid_18D1&PID_D001. According to the guide this means the device is in custom recovery, which makes sense because I was running Cyanogenmod 10 with clockworkmod recovery. If normally booting into the OS, the tablet should be giving me the default animated Cyanogenmod splash screen. Perhaps this issue is a bug with clockworkmod recovery?
I know that -d is to target a specific device, however I pulled up adb and went through each command methodically (really tedious) to see which ones would work. For some reason adb -d reboot-bootloader was the only thing that gave me a response, and even that won't do anything anymore (it just hangs, same with any other adb command). adb reboot recovery hangs also, and any fastboot command gives me waiting for device. Since I've installed a driver for it, in device manager the device shows up as Android phone and Android Composite ADB Interface. Windows tells me it's working properly (really? I'm not so sure windows).
I'd like to apologize for not indicating the results of trying your suggestions. Believe me, I have been trying them! I've spent probably a total of 12 hours trying to get this damn tablet fixed.
I'd also like to thank you. Without people like you this forum would not be any good. I am really grateful for any advice even if it does not work.
I know this is a hell of a problem. No goddamn clue how this happened. I love android but I sincerely hope that this is a clockworkmod recovery problem because otherwise that would make it a mistake on Google's (and therefore android's part). I know that the battery issues are quite frequent on android 4.2.2, but I have yet to find another user with my symptoms.
Lastly, do you know of some way to lock the device or destroy evidence of having the bootloader unlocked without being able to access the bootloader, in case this can't be fixed and I have to send it in for repair?
Click to expand...
Click to collapse
patil215,
Whew. That took you some time to write - thanks for all the details.
The USB\VID_18D1&PID_D001 USB Device Id sure does look like the custom recovery. I will assume - unless you say differently - that you would see this VID/PID pair any time you had the "black screen but with the backlight on".
Android uses this thing called the "BCB" (Boot Communications Block) to write instructions for the bootloader about what it should do when it starts up the next time. In the absence of seeing this, no doubt the bootloader has a default behavior. But basically, the way this works is that a "reboot" command eventually causes the kernel to write into this non-volatile memory area, and then a soft hardware reset occurs. The bootloader is aware of the BCB, and under normal circumstances, it will read it and attempt to follow the indicated boot mode - and then either erase the BCB or fill it with the "default booting instructions" just prior to booting a kernel or special-purpose mode previously indicated. In this way it will return to it's default behavior the next time it is booted.
The reason I mention it is that I have seen on other devices that got borked (HTC Droid Eris) in a way that sometimes those phones would always jump into a particular booting mode - and ignore any hard-button presses that would normally cause the bootloader to follow a different path. The Eris had/has "bootloader", "fastboot", and "OEM" modes and sometimes borked devices would not boot into anything other than the OEM mode.
So, since you apparently are seeing some evidence that a partially-functioning recovery is running, that sounds like a very similar scenario - the Asus bootloader is always booting to your (damaged?) recovery.
So, that's materially different (I think) than what other folks might have experienced it. The first time I've seen it here, although TBH I've only been looking in here for a little less than 3 months.
I don't know what else to suggest - it sounds like maybe you've tried things like "adb shell" commands?
If the bootloader can't be forced into fastboot mode, that (possibly damaged) recovery mode is the only privileged thing you have left. It seems to me that if you can't get into that somehow - adb being the most obvious route - then there is little left to do.
No, I don't know how to relock the bootloader without using the bootloader. That's probably something that can only be done with factory methods (possibly in APX mode).
Sorry.
Hello everyone!
I was using the Shield (pro model, 500gb) and suddenly it won't respond to the remote control. I turned the Shild off and then tried to turn it on, but it won't. When I try to turn it on the shield button turns green but only for 1 second and then turns off. Nothing is displayed on the TV. I have tried many times turning on the Shield and it only turns green the button for one second and then turns off.
I have tried the instructions provided here, but to no avail: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=Reset_SHIELD.htm
Has anyone encontered this issue and resolved it? Don't know how to recover my device now
Thanks a lot for your help!
Best regards,
David.
austmathr said:
Hello everyone!
I was using the Shield and suddenly it won't respond to the remote control. I turned the Shild off and then tried to turn it on, but it won't. When I try to turn it on the shield button turns green but only for 1 second and then turns off. Nothing is displayed on the TV. I have tried many times turning on the Shield and it only turns green the button for one second and then turns off.
I have tried the instructions provided here, but to no avail: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=Reset_SHIELD.htm
Has anyone encontered this issue and resolved it? Don't know how to recover my device now
Thanks a lot for your help!
Best regards,
David.
Click to expand...
Click to collapse
Im not a expert in this sphere, but according your written the power button on Shield not lights and this happened without your interfering, my guessing and opinion sounds like you have hardware problem, this symptoms not sounds like software. Try this one and or not I would go sending back by warranty!
https://youtu.be/2AzHF-uNiY8
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
austmathr said:
Hello everyone!
I was using the Shield and suddenly it won't respond to the remote control. I turned the Shild off and then tried to turn it on, but it won't. When I try to turn it on the shield button turns green but only for 1 second and then turns off. Nothing is displayed on the TV. I have tried many times turning on the Shield and it only turns green the button for one second and then turns off.
I have tried the instructions provided here, but to no avail: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=Reset_SHIELD.htm
Has anyone encontered this issue and resolved it? Don't know how to recover my device now
Thanks a lot for your help!
Best regards,
David.
Click to expand...
Click to collapse
...and BTW you have 16gb or 500gb console?
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
I have a pro (500gb) model. Thanks, I'm going to try this and report back my findings.
Thanks!
Hello again!
I tried what is mentioned on the video but it does not enter into bootloader. The video mentions to press the nvidia button two times and in the first time the green light keeps on. In my case, when I press the first time, even if I keep pressing, the green light just turns on for 1 second and goes off. The second time it is the same, and actually nothing happens
Anyone has encountered this issue?
thanks!
Did you manage to eventually get this sorted?
I have an almost identical problem; the remote for my SATV Pro stopped responding, mid-session, one day.
I had to pull the plug and it would no longer boot, thereafter.
The light will stay on indefinitely, it seems - I left it on overnight to test.
It won't enter the bootloader menu, either; if I hold the power button for 6 seconds, the light switches off and I can still hear the harddrive.
when trying the push button method do not forget,the USB and HDMI should be plugged to each device before start. me I just press for start then I instantly press again and hold,works well .
Did you figure out what happened and if there is a fix for this? My Nvidia Shield Pro is having the exact issue and unfortunately my unit is a month over the warranty period =(.
Same light flash for a second after power, but nothing after. I'm thinking it must be a hardware issue, but how to troubleshoot it? Wish an nVidia engineer would help out.
My 2015 Shield 16GB went dark today and I have the LED on for 6-10 seconds after replugging, and then it shuts itself off. I only see the green Shield logo for few seconds. Tried going into bootloader, but there it too shuts down after few seconds...
same her mine just gave up.
Was Shield Experience 8.2.1 recently released or am I just seeing it now for some reason? Maybe that's what caused your problems?
edit: seems like there are issues with the TV trying to go from 7 directly to 8.2.1. See the sticky:
https://www.nvidia.com/en-us/geforc...ield-experience-upgrade-821released-11162020/
after one night unplugged i got it booting again and it run for about 10 minutes or so.
efter that i have now tried toapply new cooling paste and even tried with another power adapter, but noting seems to help so far.
and as some one else up there said, i can still hear the hdd spin
A very similar thing has happened to me but maybe my difference can shed light on this issue?
I was cleaning (sweeping specifically) and accidentally turned the shield on. I pressed the touch button on the front of the shield to put it back to sleep and I then heard a *pop* sound. After that the shield will only turn on for a second, the green light will come on for a second and then it will switch off.
I opened it up (pretty easy with just my finger nails even) and I can hear sounds coming from the mainboard when I plug it in, like it's still receiving power even though it wont turn on.
I have little to no experience repairing electronics but my assumtion is I discharged enough static to blow the power button board on the front of shield unit.
Also to add, the shield unit will not respond to the inputs of a controller or a keyboard that has been paired with it.
I identified the infinitesimally thin wires that connect the touch power button to the main board but they dont seem to be damaged themselves - I plugged the power supply in while each side was disconnected and the shield unit turned on when I reconnected the wires.
I'm going to assume that if I can replace the power button board on the front of the unit it will work again but I'm not sure and cant be sure unless I can get a spare part.
Or maybe I should just take it to a repair shop?
Has anyone managed to get their unit working properly after this specific issue.
Side note: it's strange how many others have this exact same issue in this exact month isnt it?
Just following up a little bit.
I got a new power supply from Ebay to see if that would make a difference.
It did not - the power supply is not the issue.
Oh just to add - I tried cloning the original drive but I was still able to read it on my computer and the drive-clone didn't change the outcome so that wasnt the issue either.
overdrivepower said:
Just following up a little bit.
I got a new power supply from Ebay to see if that would make a difference.
It did not - the power supply is not the issue.
Oh just to add - I tried cloning the original drive but I was still able to read it on my computer and the drive-clone didn't change the outcome so that wasnt the issue either.
Click to expand...
Click to collapse
I turned mine off at the device last night and, pop, a huge static discharge from my finger. My Shield now exhibits the same behavior as everyone else in this thread.
Just wondering if you or anyone else every figured out a fix? Possibly blow fuse or capacitor in the power circuitry?
No change in status.
I'd like to still fix mine but I ended up buying a mini PC, which is a million times better than a proprietary-hardware device.
It's not locked down like an android only device (even though it runs on win10) and I can do much more with it than just watch movies and play android games/apps.
Anyway if anyone else can find a solution to this that'd be great.
D
DreadfulDrummer said:
Did you manage to eventually get this sorted?
I have an almost identical problem; the remote for my SATV Pro stopped responding, mid-session, one day.
I had to pull the plug and it would no longer boot, thereafter.
The light will stay on indefinitely, it seems - I left it on overnight to test.
It won't enter the bootloader menu, either; if I hold the power button for 6 seconds, the light switches off and I can still hear the harddrive.
Click to expand...
Click to collapse
Did you remember to connect it to a PC via USB first?
Cause if not... Well theres your first problem.
Same here, stuck at circles........
Nvidia Shield TV Pro 16GB 4K HDR
All right guys, I'm back with the following steps
If you own a SHIELD Controller
• Unplug SHIELD TV.
• Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
• While holding the A and B buttons at the same time, connect power to SHIELD TV.
If you do not own a SHIELD controller
• Unplug SHIELD TV.
• Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
• While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV.
• Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Use the X and Y buttons on the controller to move to "Boot recovery kernel".
3. Press the A button to select "Boot Recovery Kernel".
4. You may see the dead Android robot on screen. This is expected behavior. If so, press B button on the controller.
5. You will see Android Recovery Menu.
6. Use the X and Y buttons on the controller to move to "wipe data/factory reset".
7. Press the A button to select "wipe data/factory reset".
8. After process select "reboot system now".
8. SHIELD will boot to home screen.
Do the factory reset
It will bring you back to recovery
Select "Continue"
device will process and reboot like new
Hope this works....ENJOY
It did for me
I received the above info while chatting with Nvidias tech support
Ok, here's as much info as I can give as my phone is locked up:
Stock Mi A1 with 1st Oreo update: December patch level
I have not tried to load anything custom on it, nor have I even loaded the apps to do so.
I took my phone out of my pocket and it is locked on on a screen that says Fastboot.
Power button does not work. Long press power button does not work. Power+UP volume button does not work. Power+UP+DOWN volume buttons do not work.
Plugging the phone into the computer via USB port does nothing.
The battery is non-removable, so I can't pull it to reset.
I am at a complete loss as to what happened, why it happened, and how to resolve it. The phone was working fine this morning. I took it out of my pocket to use it and then discovered the issue. I live in Thailand, and there are no local service centers for Xiaomi, so hopefully someone will have an idea of how to fix the issue.
Any help, ideas or suggestions would be MOST appreciated!
Regards,
KB
UPDATE: I tried to restart the phone via the power button while it was plugged into the computer via USB. Holding the power button down for 10 seconds (guesstimate) did force a restart. This was NOT the case when not plugged in. In any event, if anyone has an idea of what happened and why, I would really like to know! I am wondering if there was some sort of long press key combo or something that happened while it was in my pocket.
Sorry for replying to my own post, but I am totally confused by this issue. I did a lot of searching and reading on Fastboot, and they ALL said that to get there, you had to enable Developer Tools on your phone, download a program for your computer, and then connect the phone via USB.
Here's the thing: I have a photo of the screen, so this is not some hallucination!
1) I DID NOT have Developer Tools enabled on the device. (I do now as I enabled it to see if it was already enabled...it wasn't)
2) I DID NOT download and install an ADB program for the computer.
3) I DID NOT (before the issue) connect the phone to the computer via USB.
So my question is how the h*ll did I get into Fastboot?????
This is really concerning as maybe Xiaomi has an issue similar to the root issue One Plus had and I happened to pocket dial the right combo???? In any event, it does not give me a warm fuzzy about what is going on behind the scenes here!
Any thoughts or info appreciated.
--KB
To get phone into fastboot mode you have to hold power off + volume down button. Might have happened in tight pocket.
_mysiak_ said:
To get phone into fastboot mode you have to hold power off + volume down button. Might have happened in tight pocket.
Click to expand...
Click to collapse
Thanks mysiak...in all my reading, nowhere was that mentioned! And yeah, it was in a pocket pressed up against a seat, so could easily have pocket dialed that combo.
Also, it is not easy to find the solution when it is locked there. I THOUGHT I had held the power off button long enough when trying to get out of Fastboot, but maybe missed it by a second or two. My solution was just to hold down the power button until the phone turned off. Whether that is the correct solution, I don't know as I still have not found anything about getting into and out of Fastboot without a computer.
Regards,
--KB
KB_Thailand said:
Thanks mysiak...in all my reading, nowhere was that mentioned! And yeah, it was in a pocket pressed up against a seat, so could easily have pocket dialed that combo.
Also, it is not easy to find the solution when it is locked there. I THOUGHT I had held the power off button long enough when trying to get out of Fastboot, but maybe missed it by a second or two. My solution was just to hold down the power button until the phone turned off. Whether that is the correct solution, I don't know as I still have not found anything about getting into and out of Fastboot without a computer.
Regards,
--KB
Click to expand...
Click to collapse
Power+volume down button is the usual way how to get into fastboot mode. From a PC you can type "adb reboot bootloader", but many prefer just using phone buttons combo (myself including). If you want to get out of fastboot, you either hold power off button until phone vibrates shortly - this works in whatever mode, even if powered on, basically it's "emergency shutdown" as we don't have removable battery. Or if you are connected to a PC, type "fastboot reboot".
Long story short, you did it right
Btw. if you will hold power+volume up combo long enough, you'll end in stock recovery mode with "no command" on the screen. Don't panic, just hold power off button and then start phone normally
I had the same problem and plugged into the computer via USB and holding the power button down for 10 seconds did force a restart. and the phone is OK since then!!! Thank you you saved my time!!!
Thank you.
Picked up my Mi A1 this morning and it had the beautiful FASTBOOT icon on the screen. The phone has been lying on my desk for several weeks without a SIM. When I could not clear the FASTBOOT message I Googled for a solution and this thread was the result. I just wanted to record my grateful thanks. I plugged the phone into a computer USB socket and held the power button until the error message disappeared, as recommended by KB_Thailand..
XDA doing what it aims to do.:good:
It is always nice to find solutions instead of even more questions. Glad that it helped!
After the initial glitches, the A1 has been pretty dang dependable.
I still am using my A1. The A2 and A3 (someone needs to be fired over that monstrosity) left me flat. I am hoping against hope that the A4 will be 'the one', otherwise I am going to have to look for something other than Xiaomi.