Hello, my nook works fine if connected to charger, but it starts freezing and hanging if the USB is removed. The power button also doesn't respond so I can't switch off my nook, but the solution i found is when the freezing happens I connect the charger again then the light beside the USB glows green then turns orange and when the light turns orange the nook restarts itself.
Can any one help me with this odd behavior i'e it works fine if connected to a charger or PC but when removed it some times works for like 5 minutes then freezes. This behavior happens only when I root my nook when running stock firmware with out any root it seems to work fine, so I can't think about a battery problem.
What do you folks think about this, if any one faced this issue and found a problem please help me. Nook is such a wonderful reader and I like it rooted. I thought of a problem with the rooting method and tried all rooting methods (touchnooter, nookmanager, torimu, some custom roms) but the problem persists.
Thank you.
If it works on the stock ROM and freezes on a custom ROM, the usual suspects are close at hand:
Faulty rooting/custom ROM installation procedure --> try one of the newer ones, such as "Twisted Modded" or 1337-ROM, do a full wipe/reset before that
Faulty CWM --> Check your CWM version and see if another one is available
Thanks for the reply
critialmass said:
If it works on the stock ROM and freezes on a custom ROM, the usual suspects are close at hand:
Faulty rooting/custom ROM installation procedure --> try one of the newer ones, such as "Twisted Modded" or 1337-ROM, do a full wipe/reset before that
Faulty CWM --> Check your CWM version and see if another one is available
Click to expand...
Click to collapse
However I sold nook and bought Kindle 7th gen and It works fine.
I experience very similar problem. It just freezes and doesn't respond anything. It's hard to tell when the reader freeze or just switched off by itself. Sometimes it's enough to hold the power button for about 3 seconds and it turns on as usually. Sometimes it requires to hold the button for like 20 seconds to switch it hard off and then it turns on as usually. When it loads it shows the battery as more or less charged (not less than 10%).
I can't link the problem with firmware - it first started on 1.1 rooted version, which worked great for years before. I switched to that 1337 ROM firmware yesterday and the same problem appears. It even appears in CWM bootloader...
Is it possible that it's just faulty battery problem? My NST is pretty old - I bought it in 2011. Can it be a problem with memory or something else? Any way to test it?
Sorry to hear that
Bobby55 said:
I experience very similar problem. It just freezes and doesn't respond anything. It's hard to tell when the reader freeze or just switched off by itself. Sometimes it's enough to hold the power button for about 3 seconds and it turns on as usually. Sometimes it requires to hold the button for like 20 seconds to switch it hard off and then it turns on as usually. When it loads it shows the battery as more or less charged (not less than 10%).
I can't link the problem with firmware - it first started on 1.1 rooted version, which worked great for years before. I switched to that 1337 ROM firmware yesterday and the same problem appears. It even appears in CWM bootloader...
Is it possible that it's just faulty battery problem? My NST is pretty old - I bought it in 2011. Can it be a problem with memory or something else? Any way to test it?
Click to expand...
Click to collapse
Well I was done with it, so I sold it and bought kindle 7th gen and its been great but nook simple touch rocks with android and moon reader. I wish it worked for me but anyway kindle is doing a nice job paired with Calibre and Acrobat DC.
Related
Hello
My HD2 Worked well for a long time, but now everytime I press the "sleep" key it turns off for half a second then turns back on and proudly displays the lockscreen without me pressing anything. There is no way to turn the screen off and go in standby mode anymore.
Obviously the battery drains so much faster from not being able to have the screen off and this silly problem actually makes the phone unusable
I flashed a few roms using HardSPL and now HSPL2. I'm currently running Artemis 11.0, the problem appeared may days after flashing while using Artemis ROM 9.0. A hard reset seemed to fix it but the problem reappeared. Today flashing 11.0 only solved the problem at first boot.
Anyone had that before? Not sure if it's software/rom related or not anymore. HELP
As far as Ive seen, its only you an me who have had this problem so far.
Honestly, Im relieved to see someone else with this problem.
I had exactly as you described, but using Axlor roms.
It worked fine for 1/2months, then all of a suddon the screen backlight wouldnt go off, but a reset fixed it.
But it got worse and worse.
Now nothing will work...
Ive taken everything back to stock, and i mean EVERYTHING! Not a single app installed.
And I still have this problem. I've tried it all.
I think its a warrenty job....
EDIT:
I also noticed the backlight will go off fine when the phone is charging, is that the same for you?
I just sent the phone off to Tmob today, to see if they can fix/replace it.
I'll keep you informed.
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
I experienced this issue when I minimised a game called virtual pool. Closing it in task manager would then allow me to permanently make the phone sleep.
samsamuel said:
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
Click to expand...
Click to collapse
How come Ive still got the problem after reflashing several times and taking everything back to exactly as it came from the box?
flannco said:
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
Click to expand...
Click to collapse
I too have had the navi panel problem.
Im praying they fix mine under warrenty
Yes the problem is exactly what you describe, hard reset and flashing to a stock rom doesn t fix it with no programm running in the background
Navipanel seems to be on randomly sometimes so can I guess it could be related.
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Considering sending it for warranty now.
Thanks for replies! If anybody knows more let us know
Update re standby problem
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
flannco said:
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
Click to expand...
Click to collapse
I have a feeling mines going to come back from tmob in the same state i sent it in...
What other options do with have if they sent it back without fixing it?
any info? I still have not had mine back.
bump... any more infos on this?
CrocMonsieur said:
bump... any more infos on this?
Click to expand...
Click to collapse
Ive noticed allot more people getting this problem. So its not only us.
Tmob are replacing mine, so Im guessing its out of our control now.
did any of you guys try performing a task 29 in between flashing roms? it may help
Audio Oblivion said:
did any of you guys try performing a task 29 in between flashing roms? it may help
Click to expand...
Click to collapse
Actually no, I overlooked it.
Probably would have been a good idea
Prehaps thats worth a try Mr Opr
CrocMonsieur said:
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Click to expand...
Click to collapse
Thanks for this workaround. Now with the urgency gone hopefully somebody finds a lasting solution without the need of sending it in..
I have same problem guys after 4 months using. ...and my HD2 is unusable with no standby. I mean battery gets weak during 2-3 hours. Whats your guess guys is it software problem. Cause Im afraid of this is hardware prob because after reset goes my device in wrong state.
Help!
Sadly I'm running into this same error with my t-mobile hd2....getting serious power drain...can anyone confirm if the task 29 helped at all? Mine won't stay off for more than 30 seconds.
** Found out the google easy sms beta app I was running had a service which was causing the app to come out of standby...uninstalling this app cured the problem.
For me, it was a sd slot problem. When i removed the sd card, phone always waked up after 0.5 seconds, and card was detected as bad.
Now the SD slot was changed (under guarranty) and it work fine, no wake up if sd slot is empty.
Any update on this? My HD2 starting doing this today as well
And I have no usb cable at work to 'trick' it. The only option is to pull the battery which I don't want to do. This is ridiculous. Am I going to have to hard-reset the damn thing to fix it?
FYI I didn't do *ANYTHING* to my phone in a couple of weeks (no new apps, etc.) and it started doing this out of the blue.
You hit the red 'end call' button and it goes black..then comes right back on.
The odd thing is it *thinks* its plugged in because the only screen setting I can get it to acknoweldge is the 'backlight level when charging'. So somehow my phone thinks its plugged in even though my only usb cable is back home.
Grrr. No registry tweaks or temp files I can delete to reset this behavior?
my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..
Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje
Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?
everything was stock on mine, no root.......maybe thats why i could recover it??!!
Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.
I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.
Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions
That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!
I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1
I got my A7 and flashed the 4/17 rom right away, used it stock for a couple of days then installed dexters mod1.42 and for a day or two it worked fine. Then the menu key stopped working. sometimes it would work for an hour and then stop working again. I deleted the dexter mod, wiped cache and did factory reset when the key worked and everything was fine.
Then I did the bestialbub a7-gapps zipmod and everything worked great for 4-5 days then the same problem, no menu key. are there any known apps that may cause this problem? I am waiting for the menu key to work again so I can try again, are there any settings or other mods that will get me the market but leave me close to stock.
steamtv support just had me do a reset and flash latest firmware and that doesnt help much.
Please, I love the A7 when it's working and need some help.
Thanks,
Billy
Does this happen when the back of the device is hotter than warmer? I've had this happen often when the days are warmer and hotter. That's the reason why because the heat affects parts of the wiring. The other solution is to use Button Savior (an app on the market).
Ytain
The menu smart key comes and goes no matter the temp. It's not working now, sometimes it will work for a little while and then stop again. I can't wipe/reset without the memu key. I want to get it back to stock to see if it's a hardware problem then take it from there. Any suggestions anyone?
billy
same here (I thought, I'm the only one encounter this kind of problem). My Aunt gave me A7 as present. after 2 days, all the smart keys malfunctioned. it works fine for 10 min after that it wont work anymore. I've installed button savior for remedy. I think ytain is right, A7 has problem when the back of the device becomes hot.
Hello,
I had the same issues with some of the keys of the keyboard. but at first it started only happening when the battery was low but recently it was happening all the time.
This was making my life difficult as i write some sms to my friends and it's quite annoying.
I left my phone untouched and went to repair center of my provider to show what was happening. Put my phone there for repair and in the same day went there to pick up the phone good as new.
The issue is that the stripes connecting from the keyboard to the cellphone were a bit fragile and probably broke or it wasn't making any contact whatsoever. Now i have the phone working 100%. no problem.
Hope this helps
Hi,
Wi-Fi on my Nexus 10 always worked good. Then some days ago I turned it on and... Wi-Fi seems dead. I mean it stucks on "Wi-Fi activation..." and doesn't go on. Wi-Fi function seems not to be activable, switch button remains grey and disabled. It happens with 5.1.1 stock rom, then I made a complete factory reset and problem still remained, then i've tried with a 12.1 cyanogenmod and... problem still remained. Wi-Fi seems completely dead. Could it be an hardware issue? Is there an app with whom I can make hardware diagnostics? Or any other advice? Bluetooth also doesn't work and with cyanogenmod every 10-15 secs it shows "unfortunately bluetooth sharing stopped" message...
Thanks in advance.
Hello and thank you for using Q/A,
I don't know if there is a App to check hardware, but I think your WLAN and Bluetooth Chip is broken.
The last thing you can try is flashing Stock via Fastboot. Don't forget to erase all partitions before. There are several instructions in Nexus 10 General section.
Kind regards
Trafalgar Square
I have the same problem, but I am sure the chip is not broken because when I flash and reflash, sometimes the Wifi just comes on. but when I attempt a reboot its gone again. Tried FXR wifi fix but it doesnt always work.
I read somewhere that it could be a problem with the Persist partition but still havent managed to fix it
New problem!
Hi!
I've solved my old problem by replacing motherboard with a new one (with 32 GB HD instead of 16 from my old one). WiFi was perfect. I also had to buy a new 3-button set (power & volumes) because old one was deteriorated. All was right.
But from yesterday a new problem comes out. I was trying to flash last CM snapshot release for Nexus 10, but tablet simply powered off.
If I plug it to PC via USB and press power button I can see battery icon fully charged, but tablet don't turn on. If I keep it plugged, sometimes tablet auto turns on in bootloader mode for a few minutes, then screen flickers and tablet turns off. I've tried to flash CM in these minutes but, at first reboot, tablet turns off.
I think it could be a battery problem. Maybe it's gone and cannot be recharged, contrary to what battery icon seems to say.
Now, I've spent 80 euros for a new motherboard and 15 for 3-button change. A new battery will cost about 50 euros. 50 euros is less than buying a new tablet but, considering a new problem can come out in any moment, is it worth? Also, like when I had motherboard problem, I'm not sure battery is the problem. Any advice to solve or about buying or not a new battery? Thanks!
Took my risks and bought a new battery, arrived on yesterday morning. Battery changed and CM13 correctly flashed, now it seems to be ok. Luckily i hit the right problem.
Hi everyone!
So I just had this problem after I woke up yesterday. I googled a lot but only found similiar problems.
Let me tell you what happened chronologically:
After turning the phone on in the morning it started updating apps as if I was doing a firmware update: "updating apps 1 of 135" etc. Note that my nexus was already running on 5.1.1 and had the latest updates installed.
Now it randomly freezes the screen on whatever screen it was before it happens and it won't respond to any touch input. This can also happen when not using the phone, then it will freeze at the lockscreen (the time freezes with it so sometimes i can see at what time it froze). Also, it loses connection with Wi-Fi as i'm using Whatsapp Desktop when i'm on my laptop and it mentions me that my phone is not connected.
The only thing that "fixes" (temporarily) it is a reboot. Now sometimes, on the lockscreen, i can just hold the power button and the pop-up comes in to turn the phone of, which i can somehow just tap on an it responds by turning the phone off. But sometimes (less frequent than the latter mentioned) the pop-up doesn't come in and holding the power button for a few secs will do the trick.
I hope I informed you all enough and my end question is: does any of you know what this is? How i can fix it or what i can do to prevent it or anything as I am hopeless. (my G3 is up for reparation so this is my sisters old phone, i had a nexus 4 myself for 2 years before the G3).
Thanks in advance!!
The best way to test it is by reformat the OS.
I positively think that it will solve the problem.
Since the phone is no longer under warranty, I guess there is no harm to install custom rom on it. They are fast and stable too.
Hope this help. Good luck.
Sent from my Nexus 4
EXACT thing happened to me too. Backup your data and hard reset from recovery. This fixed it for me
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
multimedias said:
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
Click to expand...
Click to collapse
Then it's time to change the screen or phone. Looks like it is a hardware issue.
Nitin
nitin.chobhe said:
Then it's time to change the screen ...
Nitin
Click to expand...
Click to collapse
I agree, your screen needs to be replaced.