Related
Hello all, I'm curious to hear your thoughts and advice.
My nook is completely unresponsive. It is not stuck at rooted forever.
In fact this has nothing with a root attempt/reset/restore/power on.
I had done a a fresh reset/root with touchnooter about four months ago and was happily and smoothly reading for about two months. I then got busy and put the nook down, did not touch or use for about another two months. I tried to use it about a week ago but found that it had run out of battery in sleep after the two months of disuse (not surprising). I put it on charge overnight and everything booted right and functioned well once it turned on, except that the battery indicator in the statusbar showed a "?" and the battery info in system info showed 100% "unknown". After alot of fruitless research I put it down with the intention of reset/restore/root when I had the time.
I just picked it up this morning and was faced with the expected "Press then button below to wake up your NOOK" screen. But when I pressed the "n" button nothing happened. Obviously holding the "n" did nothing as well.
I tried to power it off and on- nothing
holding power for 20- nothing
power for 30- nothing
8 failed boots- nothing
left right- nothing
left right power-nothing
random pushing and holding of power- nothing
all these with mem card in and out- nothing
all these plugged usb- nothing
all these pugged ac- nothing
I let it charge some more- nothing
None of the buttons do anything, the screen stays inevitably at the " press the n button to wake" screen. no activity whatsoever except that when It is plugged in, the green light shows. NO ORANGE LIGHT... it is fully charged by both usb and ac.
It is not detected at all by windows anywhere.
In Linux- lsusb, bklid, and df -h yield nothing. My nook might as well be the invisible stupid ereader.
I did not drop it, sumbmerge it, perform magic around it... It has been sitting on a shelf doing nothing.
To repeat, the only thing my nook does is light up green when plugged.
It is unchangeably stuck on poe's face...
If this isn't true brick, I don't know what is.
I'm exhausted. Any ideas? I appreciate the help.
Best,
Thomas
i don't know. i just know my dog ate mine and i'm now in the market for a new screen, so if you don't get it working sell me the unit and get some money for yourself to purchase a new one =D
or you could google the disassembly instructions and try unplugging the battery, not very hard to do. could be of .. some help perhaps?
I would definitely take you up on your offer, but i'm still under warranty.
However, I would still like to have my original, and figure out what is going on and why it happened.
Ideas?
Thank you.
similar problem were solved
Hi! I might have read about similar problem solved on USB host mode here http://forum.xda-developers.com/showpost.php?p=23475998&postcount=131
That's it, thanks so much.
if it help
if it helps let them know in the tread that you had same problem. they are wondering whether it is due to host mode
[N2E]: After automatic update to 1.1, Nook Touch Screen absolutely DEAD--Nothing Work
THIS WAS A POST FROM ANOTHER SITE AS TO MY PROBLEM:
I was reading on my N2E last night. I put it down for about 30 minutes and when I came back it was displaying the default "Authors" screensaver (I had switched to the Nature photos) and asking to slide to unlock. I thought, "Oh, the new software update must have downloaded and installed. I'll check it out." To my shock, the touch screen was completely unresponsive--no amount of swiping would unlock from the screen saver. I let it set for a while longer thinking perhaps the softare update was not yet finished. No such luck.
As a result of the new update, my NOOK is now completly DEAD! I tried powering off, but couldn't do that because you are asked to confirm power off on the touchscreen, which no longer works. So, I looked online and tried the soft reset/reboot by holding down the "Home" or "n" button and then pressing the power button for several seconds. Great--it started rebooting...and came right back to the "authors" screen saver and asking to swipe to unlock. I tried this rebooting process several times, always with the same result: back to screeensaver mode with completely unresponsive touchscreen.
So, looked at the online technical troubleshooting discussion and helps and decided to try a downloaded manual install of the software update. Plugged my NOOK into my computer and it recognized it. So, I downloaded the manualo software update and dragged and dropped it onto the NOOK as directed and sure enough, it started to reboot itself. I thought, "whew, maybe this will fix it". NOPE--came right back to the locked screensaver, with no mention of attempting to update software, and the touchscreen is still dead. (By the way, all of this was done initially with the NOOK showing about 94% charged, so it was not a battery issue.)
Reconnected the NOOK to my computer and the software update file was gone from its home directory, which implies it did something with it. So, I tried repeatedly to install the software update manually, always with the same result: NOOK comes back to locked default "authors" screensaver wtih a dead touchscreen.
Looked online for B&N technical support again saw that others had this problem (though only found a couple references). Found the instructions to do a factory reset and reluctantly tried that, desparate to make my NOOK work again, but frustrated that if it did I would have to rebuild everyting on it and download my 400+ B&N book library all over again. But, guess what, factory reset just comes up to the "Welcome to your all-new NOOK" screen (sounds like progress), BUT the touchscreen is STILL dead, so I can't hit the "Next" button onscreen to proceed with setting up my factory-reset NOOK. Tried rebooting again (as this seems to be the only solution offered in the online tech support) and now it just keeps coming back to the "Welcome to your all-new NOOK" screen with a dead touchscreen keeping me from doing anything.
So, now I am taking it back to my local B&N store in hopes they will exchange it for a new NOOK.
I really want to see a feature to disable automatic updates in the future. I specifically didn't download and manually install when the update came out, figuring I'd wait for the automatic download to give time to B&N to work out the bugs and perhaps issue a patch (as they have done in the past for the N1E). Instead I get no warning about the automatic download (happens while I am reading and set the NOOK aside for 30 minutes), and then the update KILLS my NOOK.
I am not a satisfied NOOK customer at this point.
MY POST: (from the that site)
Not Sure how to do this post or whatever, but I was happy until the update and everything that happened to you is the same with me. This is the first post that describes what happened to me. I'm out of warranty and refuse (and can't) to buy another one of these. If their updates can do this, I'm not sure I want to sink another $100 into the shareholders pockets. I'd really like to know if anyone knows what may be wrong with it.
In addition to what was already mentioned, I took the battery out several times(which seems intimidating but very easy but voids the warranty) and took it completely apart cleaning the screen very well with water and another time a glass cleaner. I tried rooting also. Not sure of what to do now. It seems software related due to working fine until the update. Still at the "Welcome to your all-new NOOK" screen with unresponsive screen. I wasn't sure if the last sentence from B&N was a personal message to me welcoming me to the "new" state of the my nook.
Thanks for any help from anyone.
Thanks.
Identical problem.... and no fix..
It is a shame you got no solution for this. and the worst, you are not the only one... it happened exactly the same with my Nook ST....
Hopeless...
Machiavelli_The_Man said:
THIS WAS A POST FROM ANOTHER SITE AS TO MY PROBLEM:
I was reading on my N2E last night. I put it down for about 30 minutes and when I came back it was displaying the default "Authors" screensaver (I had switched to the Nature photos) and asking to slide to unlock. I thought, "Oh, the new software update must have downloaded and installed. I'll check it out." To my shock, the touch screen was completely unresponsive--no amount of swiping would unlock from the screen saver. I let it set for a while longer thinking perhaps the softare update was not yet finished. No such luck.
As a result of the new update, my NOOK is now completly DEAD! I tried powering off, but couldn't do that because you are asked to confirm power off on the touchscreen, which no longer works. So, I looked online and tried the soft reset/reboot by holding down the "Home" or "n" button and then pressing the power button for several seconds. Great--it started rebooting...and came right back to the "authors" screen saver and asking to swipe to unlock. I tried this rebooting process several times, always with the same result: back to screeensaver mode with completely unresponsive touchscreen.
So, looked at the online technical troubleshooting discussion and helps and decided to try a downloaded manual install of the software update. Plugged my NOOK into my computer and it recognized it. So, I downloaded the manualo software update and dragged and dropped it onto the NOOK as directed and sure enough, it started to reboot itself. I thought, "whew, maybe this will fix it". NOPE--came right back to the locked screensaver, with no mention of attempting to update software, and the touchscreen is still dead. (By the way, all of this was done initially with the NOOK showing about 94% charged, so it was not a battery issue.)
Reconnected the NOOK to my computer and the software update file was gone from its home directory, which implies it did something with it. So, I tried repeatedly to install the software update manually, always with the same result: NOOK comes back to locked default "authors" screensaver wtih a dead touchscreen.
Looked online for B&N technical support again saw that others had this problem (though only found a couple references). Found the instructions to do a factory reset and reluctantly tried that, desparate to make my NOOK work again, but frustrated that if it did I would have to rebuild everyting on it and download my 400+ B&N book library all over again. But, guess what, factory reset just comes up to the "Welcome to your all-new NOOK" screen (sounds like progress), BUT the touchscreen is STILL dead, so I can't hit the "Next" button onscreen to proceed with setting up my factory-reset NOOK. Tried rebooting again (as this seems to be the only solution offered in the online tech support) and now it just keeps coming back to the "Welcome to your all-new NOOK" screen with a dead touchscreen keeping me from doing anything.
So, now I am taking it back to my local B&N store in hopes they will exchange it for a new NOOK.
I really want to see a feature to disable automatic updates in the future. I specifically didn't download and manually install when the update came out, figuring I'd wait for the automatic download to give time to B&N to work out the bugs and perhaps issue a patch (as they have done in the past for the N1E). Instead I get no warning about the automatic download (happens while I am reading and set the NOOK aside for 30 minutes), and then the update KILLS my NOOK.
I am not a satisfied NOOK customer at this point.
MY POST: (from the that site)
Not Sure how to do this post or whatever, but I was happy until the update and everything that happened to you is the same with me. This is the first post that describes what happened to me. I'm out of warranty and refuse (and can't) to buy another one of these. If their updates can do this, I'm not sure I want to sink another $100 into the shareholders pockets. I'd really like to know if anyone knows what may be wrong with it.
In addition to what was already mentioned, I took the battery out several times(which seems intimidating but very easy but voids the warranty) and took it completely apart cleaning the screen very well with water and another time a glass cleaner. I tried rooting also. Not sure of what to do now. It seems software related due to working fine until the update. Still at the "Welcome to your all-new NOOK" screen with unresponsive screen. I wasn't sure if the last sentence from B&N was a personal message to me welcoming me to the "new" state of the my nook.
Thanks for any help from anyone.
Thanks.
Click to expand...
Click to collapse
The factory restore does not actually fix every possible problem with your Nook.
If your Nook responds at all, try to boot it up on an SD card like ClockworkMod or noogie.
At least that way you can see what is happening.
The partitioning might have become corrupted which the "factory restore" does not touch.
If no response with anything, try disconnecting the battery.
You might also try booting over USB using the techniques in rooting the new white glow.
Hello I was wondering if I'm just screwed I bought 2 nook simple touch, one for me and one for a present to my mother for her birthday on march 16. I bought them at best buy for $40 a piece on January 30. I used mine and was perfect but when I tried to set up my mom it wouldn't load the license agreement, always got stuck or reboot or something, so I loaded cwm on an sd card just to play around, tested on my nook and was fine, then put it on my moms nook booted once then I didn't press anything and turn it off then I load the image but when I tried to boot again it got stuck on the load screen and wont do anything, no reset sequence will work with the sd card on or off the other nook boots with this sd card. at the end I exchanged with my mom she is happy with her nook an I have a useless unit do you think they will exchange it I didn't rooted it or did anything to it but has the n cwm splash on screen forever. I'm in Costa Rica right now and wont return home until May do you think I'll might be able to exchange it or should I just try to repair it.
I'm glad that your mother got the working one!
You say that that one will boot on your CWM SD card, but yours won't?
It may be hard to get your unit exchanged with a conspicuous screen on it, even if it's not your fault.
When you plug it into your desktop is there any indication of a new USB device found?
If it's charged and no amount of the power button gets a reaction, I'd open it up.
any news???
Hi endor43, same problem here, have been able to find any solution?
endor43 said:
Hello all, I'm curious to hear your thoughts and advice.
My nook is completely unresponsive. It is not stuck at rooted forever.
In fact this has nothing with a root attempt/reset/restore/power on.
I had done a a fresh reset/root with touchnooter about four months ago and was happily and smoothly reading for about two months. I then got busy and put the nook down, did not touch or use for about another two months. I tried to use it about a week ago but found that it had run out of battery in sleep after the two months of disuse (not surprising). I put it on charge overnight and everything booted right and functioned well once it turned on, except that the battery indicator in the statusbar showed a "?" and the battery info in system info showed 100% "unknown". After alot of fruitless research I put it down with the intention of reset/restore/root when I had the time.
I just picked it up this morning and was faced with the expected "Press then button below to wake up your NOOK" screen. But when I pressed the "n" button nothing happened. Obviously holding the "n" did nothing as well.
I tried to power it off and on- nothing
holding power for 20- nothing
power for 30- nothing
8 failed boots- nothing
left right- nothing
left right power-nothing
random pushing and holding of power- nothing
all these with mem card in and out- nothing
all these plugged usb- nothing
all these pugged ac- nothing
I let it charge some more- nothing
None of the buttons do anything, the screen stays inevitably at the " press the n button to wake" screen. no activity whatsoever except that when It is plugged in, the green light shows. NO ORANGE LIGHT... it is fully charged by both usb and ac.
It is not detected at all by windows anywhere.
In Linux- lsusb, bklid, and df -h yield nothing. My nook might as well be the invisible stupid ereader.
I did not drop it, sumbmerge it, perform magic around it... It has been sitting on a shelf doing nothing.
To repeat, the only thing my nook does is light up green when plugged.
It is unchangeably stuck on poe's face...
If this isn't true brick, I don't know what is.
I'm exhausted. Any ideas? I appreciate the help.
Best,
Thomas
Click to expand...
Click to collapse
There are times when a Nook gets in a mode where it won't accept a charge.
Opening it up and disconnecting the battery for a minute might fix this.
endor43 said:
That's it, thanks so much.
Click to expand...
Click to collapse
When this worked for you did the light turn orange right when you plugged the battery back in? I just took the battery out, plugged the nook into a charger, and with it plugged in plugged the battery back in and the light stays green the whole time yet I'm not able to use the nook at all.
My nook second generation is not responding to my touch I tried everything to get it to work and I eventually got it to completely power of what if it does not work when I turn it on what should I do
It could be power/battery problems.
Check to see if it makes itself known when the USB is plugged in.
If it reacts at all, that's an indication of life.
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then it goes to a black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. Playing around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried downgrading to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. laying around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried going down to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
Sorry, this post isn't going to help, but I literally laughed out loud when I saw
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Click to expand...
Click to collapse
in the preview of the post. Lol
Maybe I should delete my original Karma-Killing post as a start.
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
a.mcdear said:
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
Click to expand...
Click to collapse
It might not be software but I can see the recovery screen so I have some reasons to believe it could still be software. Unfortunately, if I try to RMA, they're going to say that I voided the warranty....because I probably did by opening the case AND running a cooked ROM. So, they'll fix it but as a service. I'm not sure it would be worth the cost.
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
yanbo2012 said:
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
Click to expand...
Click to collapse
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Skyeclad said:
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Click to expand...
Click to collapse
Yea, you screwed up by opening it. You might as well upgrade if all else fails. I'd hold off on another transformer for as long as I can though if I were you...already hearing about minor defects in tf300s such as light bleeding.
Then there's always the...iPad...but make sure you update if you get one! Jailbreak that MF first and then you'd be good to go. My dad wants me to jailbreak his iPad 2, but it doesn't help that he's "update happy"
Skyeclad said:
I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
farsight73 said:
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
Click to expand...
Click to collapse
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Skyeclad said:
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Click to expand...
Click to collapse
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
1) NVflash works on B60 and below.. check yours
2) Put it in a freezer for a night
3) Dissemble again and see if anything disconnected or loose since the last time you open it.
4) Smell it and see if anything like burn smell around the motherboard(this could be over voltage from a weak components).
.
.
.
.
.
If all above still yielled the same result..
5) Check and see if your TF101 could survive 2 storey height drop..
Good Luck..
farsight73 said:
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
...
2) Put it in a freezer for a night
...
Good Luck..
Click to expand...
Click to collapse
A lot of LCD screens can be damaged by freezing, unless you know that the TF is safe I would not freeze it.
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Skyeclad said:
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Click to expand...
Click to collapse
Lol, didn't you already take it apart before?
I2IEAILiiTY said:
Lol, didn't you already take it apart before?
Click to expand...
Click to collapse
Yes, but at the time I was looking for a cable that I could loosen, now I'm looking for a cable to tighten. Fml, yes it sounds stupid but I'm at the point where I need to decide if a repair or replacement is the next step. I'm not thrilled with anything out there.
Almost exactly the same problem here...
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
I had the same problem of the backlight being on but no video. It worked over the hdmi but that was it. I had to send in my unit via a RMA to get it fixed.
Thankfully it was under warranty so they fixed it. Did you drop your unit?
MeLikes said:
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
Click to expand...
Click to collapse
Just out of curiosity, why not nvflash your way back to stock? I did because I couldn't find my HDMI mini cable. I haven't opened my tablet again. I'm going to try to RMA it.
try to nvflash stock rom and start over? that would your best chance....
Sent from my Transformer TF101 using xda premium
Well first of all i don't know how to use NVflash, and secondly i have a B70 transformer so i don't know if it will work. Also i need to flash the stock Taiwan firmware because that's the original firmware that came with it and i can't find instructions for that. Just wondering though does flashing the stock rom using NVflash also install the stock recovery?
Hello all,
(First of all, if you watch the video you will understand what I'm trying to explain here, but I wasn't able to make myself very clear, secondly I don't have support from asus/google in my country)
I've been using my nexus 7 for almost 4 months and haven't had any problems with it until now. When I upgraded to 4.2 I noticed that the speakers sound was strange sometimes, but most of the time it worked just fine. But today something very sad happened
When I unlocked the tablet I realized it was in my sister's user (I was already at launcher's "home"), so I locked it in order to switch to my user, but when I pressed the unlock button, the screen wasn't normal, it went crazy. I couldn't see anything, just shades of black and white (see video above for details). After that I tried anything but the the screen was the same. Something important to mention is that the screen responds normal to touch input, so I can unlock, open menu, recent apps, etc only by knowing where to touch. I'm even able to turn it off by holding power button and then choosing "yes, reboot tablet" without being able to see anything on the screen.
It worth mention that after several reboots, screen locks/unlocks I manege to get the screen to work perfectly for a couple of minutes, but when I locked the tabled the screen stopped working again.
My question is: DO you guys think that this is a screen problem, some wires that aren't well connected or even maybe Android OS problem? And would it worth it to buy a new screen and try to find someone to change it for me or I should just throw it in the trash?
PS: The tablet is completely stock now, just rooted and with busybox, no OC, no GPU OC, etc...
http://www.youtube.com/watch?v=Sna69-GKIYE&feature=g-crec
Try flashing a factory image. If that doesn't work, it's most likely a hardware issue. You should be able to get warranty service if that's the case.
Factory image: https://developers.google.com/android/nexus/images#nakasigjop40d
Edit: Missed the part about no support from Google/Asus. Disregard the warranty statement.
Sent from my Nexus 7 w/ PA and m-kernel
Problem kind of solved
EvanA said:
Try flashing a factory image. If that doesn't work, it's most likely a hardware issue. You should be able to get warranty service if that's the case.
Factory image: https://developers.google.com/android/nexus/images#nakasigjop40d
Edit: Missed the part about no support from Google/Asus. Disregard the warranty statement.
Sent from my Nexus 7 w/ PA and m-kernel
Click to expand...
Click to collapse
Thanks for the answer. I decided to do that (even though I didn't think it would solve the issue).
I turned off the tablet and booted into recovery by holding vol up and down + power and guess what??? when it booted into recovery the screen was perfect again, I could see all information about the tablet, lock state, etc. I decide to reboot it and it has been working normally for a couple of hours from now, I have even made some benchmarks and everything was ok.
Now I'm more confused than before: Hardware or OS problem? The tablet is working now, so I'll just backup all my titanium backup data to my pc and leave USB debugging on, so if the problem returns I'll just flash stock again.
EDIT: After some hours the screen problem returned. I flashed 4.2.1 and the problem was still there. I guess I'll just have to find someone who will open my tablet and see if the wires are properly connected.
So, a few days ago, I started having some problems with my stock Nexus 7 (not unlocked, no ROMs or anything like that). Some apps just wouldn't open, they would force close within a second of opening. Anyway, I think it might have stemmed from the game "Let's Golf 3", as problems started after playing that, and when going back in to it after a day of issues, a message appeared saying "Unfortunately, launcher has stopped" - it gave me the option to report or cancel, but whatever I pressed, the message popped back up. I pressed the sleep button, which seemed to turn my Nexus off somehow.
Then, when trying to to turn my Nexus back on, it just stays on the 'X' screen. I have done a factory wipe through the fastboot menu a few times, but it still stays stuck on the 'X' screen. To turn it off, I hold down the power button, but it just starts the process again automatically. The only way to actually turn the device off is through the fastboot menu.
I have seen talk of 'factory image' and drivers etc... but I am not too comfortable with that sort of thing. I know the basics of troubleshooting devices, but not much more. I am very wary of doing anything more than what the device provides me with.
Any idea how I can get my Nexus started, or am I going to have to look for a replacement?
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Leonhan said:
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Click to expand...
Click to collapse
Is that not for rooted devices?
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
AW: [Q] Nexus stuck on 'X' screen, even after full wipe
Gawge said:
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
Click to expand...
Click to collapse
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
mihahn said:
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I too had the same problem. Tried everything. Finally gave it to ASUS service centre in Nehru Place. They will replace the mother board. May take 15 more days. So sad!
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
FYI,
The tablet can "play possum" when it is in APX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown APX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
bftb0 said:
FYI,
The tablet can "play possum" when it is in AVX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown AVX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
Click to expand...
Click to collapse
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
Service centre seems to be the only solution. My sympathies!
Gawge said:
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Click to expand...
Click to collapse
Call Asus first. Make sure to let them know it is less than 2 months old. If they want you to perform the return through the original retailer, they will tell you. But it's best to eliminate any other middlemen if that is possible, as I suppose that the tablet ultimately goes back to Asus anyway.
(Might be different through other channels, e.g. PlayStore - I dont know).
I assume bricked is the right term. And I'm pleading for some help here on what I can try before I call Google Support again.
Here is the quick run down: Bought 2 Nexus 6P, (Gray - Me), (White - Wife). Wife bricks her phone in 15 days, screen seems to work when held at different angles, can't seem to get it to stay on permanently, acts almost like an old VCR where it will partially draw the screen horizontally. Almost like a loose connector. It only stays on for milliseconds at a time, not long enough to factory reset or do anything remotely useful. Holding power for 8 seconds doesn't help. Holding power and both volumes does not help. Just to clarify, device is running, screen is black. Not a boot issue per say as a screen issue. Could previously hear her get alerts, can't right now (only see a battery icon). Since the screen is the main issue, I'm flailing in the dark as to where I am at any given point in time.
I assume how she uses the device because mine has been perfect and I can't seem to find a vocal crowd with this issue. However, after she bricks hers, she uses mine for an entire week and doesn't have any problems. Google support is extremely helpful and sends out an entire new device. I set it up and restore the apps, within 3 days (Friday -> Sunday) she has the exact same issue again - bricked. Now I'm completely flabbergasted. This device is still spotless, she has barely used it, it hasn't hit a surface hard, hasn't even been sneezed on. I can't even begin to stress how short a time period this is for a device to brick in. I can't help but feel this is a software app and the restore brought over the delinquent app. However, how come I can't reset the device and get back to a clean slate? Can anyone give me a trick?
Please, please help. She wants me to switch back to Verizon because of these device issues. However, even with 2 people, we are saving a ton on Project Fi and I really need this to work. Everything else has been a joy.
So I got it working. But I have a few questions...
Process:
1. Connected it to charger
2. Held power and both volume connectors
3. Held power again
4. Did both of these actions for upwards of 30 seconds at a time hoping for some response from the device.
5. Put it down on the table to write my forum post (still charging).
6. Battery image came on and off the screen randomly
7. Picked it up and held power one last time and it started booting normally.
I'm not sure which sequence of events led to what and I'd really love to know how to reliably reset it in the future. If this is the case then it means it was a software issue all along that persisted over several reboots.
Additionally, I'm frantically pulling software off of her phone - Elmo Calls, Sesame Go, Snapfish, Pinterest, etc. Fearing that one of these apps that I don't run on my device could be causing this. Is there any way to troubleshoot the software itself and see what device could have had access to the screen power and perhaps been powering the screen off as soon as I attempted to power it on (causing a flicker)?
Thanks.
your experience is really unusual you bought 2 phones but the one you are using does not have problems but your wife has, you switched phone then the problem occurs there is a chance a program is causing it as you already received a new one and it still occurring try to let her use the phone with the same software you are using and avoid which you dont use see if there is any progress.
Did you try factory resetting either phone?
Sounds like a software issue if they both had the exact same issue.
does she have some kind of serious strong magnet in her body or purse? haha
Soulfly3 said:
does she have some kind of serious strong magnet in her body or purse? haha
Click to expand...
Click to collapse
That's what I was going to say. Seems consistent to what a strong magnet would do to a screen. My next guess was a rogue app.
No magnets, nothing crazy. It started happening again yesterday a few hours after fixing it, I've hard wiped the device and bypassed the restore. Only updated the base applications and it is sitting on a charger - waiting to see if it will happen again.
Get a new wife?
VerucaSalt said:
Get a new wife?
Click to expand...
Click to collapse
Or, as OP seems to like to get things in 2, get 2 new wives so that if you brick one, you still have one left without having to wait for RMA.
All jokes aside, is there any specific oddities in how your wife uses phones (Does she work at a metal scrapyard with a big ass magnet? Okay, I promise, last one.) Or you could be extremely unlucky to have bought a defective unit, which was replaced by another defective unit.
To reliably reset the 6P you just hold the power button until the phone vibrates as it starts to boot again. Did the screen flake out as it booted up too?
ttminh1997 said:
Or, as OP seems to like to get things in 2, get 2 new wives so that if you brick one, you still have one left without having to wait for RMA.
All jokes aside, is there any specific oddities in how your wife uses phones (Does she work at a metal scrapyard with a big ass magnet? Okay, I promise, last one.) Or you could be extremely unlucky to have bought a defective unit, which was replaced by another defective unit.
Click to expand...
Click to collapse
Although these posts are funny as hell, honestly you would be surprised how many common every day things you come into contact with that can wipe data right off any storage medium. Although its definitely a possibility that you received a crap refurb phone, when you get the next RMA I would take some time to monitor your wife's daily routine with her cell (not her tinder activities), she might just be placing it near/on something that is wiping the phone or corrupting the data. Could also be a really junk app, but google is pretty good about keeping them out of the play store the best they can.
dl200010 said:
To reliably reset the 6P you just hold the power button until the phone vibrates as it starts to boot again. Did the screen flake out as it booted up too?
Click to expand...
Click to collapse
Yea, it was flaking out on the 8 second hold reboot - I performed it dozens of times without getting my screen back. What works reliably for me is to hold power and both volumes and then hit power again once the diagnostic screen shows up (whether I can actually see it or not). The reboot off of the diagnostic screen seems to bring the phone back to life consistently.
She is using the phone w/ just the base apps from yesterday - I told her to try breaking it without loading new apps - will see how this plays out today.
jaaaaaaaaf said:
Yea, it was flaking out on the 8 second hold reboot - I performed it dozens of times without getting my screen back. What works reliably for me is to hold power and both volumes and then hit power again once the diagnostic screen shows up (whether I can actually see it or not). The reboot off of the diagnostic screen seems to bring the phone back to life consistently.
She is using the phone w/ just the base apps from yesterday - I told her to try breaking it without loading new apps - will see how this plays out today.
Click to expand...
Click to collapse
Was that diagnostic screen flaking out too? I suggest to get more aggressive and factory reset through recovery and than ONLY connect her google account to get her contacts. Run like that for about a week. Otherwise your other choice would be to unlock the bootloader and try a custom ROM. I would suggest Cyanogenmod, DLROM (mine), Pure Nexus Project, or even Noob Builds.
ttminh1997 said:
Or, as OP seems to like to get things in 2, get 2 new wives so that if you brick one, you still have one left without having to wait for RMA.
Click to expand...
Click to collapse
haaaaaaaa, very good
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
Soulfly3 said:
does she have some kind of serious strong magnet in her body or purse? haha
Click to expand...
Click to collapse
Was actually going to say this too, is there somewhere she goes or sits which has some kind of strong magnetic field? It's odd that it happened to one and then to the next one, unless they're just both from a faulty batch.
Suppose I will add a follow-up. Since I ripped all her software off the device it hasn't crashed once in the same fashion. So I mean, that is the conclusion. I'd love to say I knew how to dive deep enough into Android to pinpoint exactly which app had such incredibly disruptive and adverse affects (far worse than complete OS crashes). But I don't know Android well enough. Google has the original phone. It definitely seems like an app should not have been able to take over the display so completely.
I'm going to move forward and have my wife install more of her apps. Just wanted to shoot an update out in case I don't revisit this. Thanks everyone who posted.
Maybe a combo of rogue (rouge?) apps? I mean some apps do have the ability to draw over screen, so that might have caused whatever problem you had.
And OP, don't leave us