Database Develop

[Q] rooted Nook Color sound issue

I am having the sound issue where sometimes I lose sound due to some unknown issue. In Linux I can usually restart the sound process by running
alsa-utils restart
A find on that does find an alsa folder as /system/usr/shared/alsa with shows the pcm file but whats the command in Android to try and restart it manually if there is no alsa-utils. I shouldn't have to reboot to get it restarted and it would be nice to create a shortcut to a script that would run when I lose sound.
I know some people have said it was a fault with some Nooks that needed returning, but I'm under the suspicion its something else causing it. Any suggestions?

Xerxes910 said:
I am having the sound issue where sometimes I lose sound due to some unknown issue. In Linux I can usually restart the sound process by running
alsa-utils restart
A find on that does find an alsa folder as /system/usr/shared/alsa with shows the pcm file but whats the command in Android to try and restart it manually if there is no alsa-utils. I shouldn't have to reboot to get it restarted and it would be nice to create a shortcut to a script that would run when I lose sound.
I know some people have said it was a fault with some Nooks that needed returning, but I'm under the suspicion its something else causing it. Any suggestions?
Click to expand...
Click to collapse
It has been reported that 1.1.0 fixes the No sound after sleep issue.

Is there an autonooter for 1.1.0? I didn't think there was? Any update now would mess up my rooting of it. I'm also having intermittent reboots. Anyone seen that?

Xerxes910 said:
Is there an autonooter for 1.1.0? I didn't think there was? Any update now would mess up my rooting of it. I'm also having intermittent reboots. Anyone seen that?
Click to expand...
Click to collapse
Are you on 1.01? If so, you might want to get ROM Manager from the market and install Clockwork recovery using Rom Manager. That way you have recovery if something goes south.
There is no current AutoNooter for 1.1. There are some ROM updates to rooted 1.1 but read the full thread so you know the problems if any before you try a 1.1 ROM.
If you don't want to update beyond 1.01 now use the SCRIPT solution to block the OTA altho reports say the OTA won't run on a rooted NC. Hope this helps.

So I took my Nook in to possible exchange it because some people said it was possibly a bad batch. I wiped it and went back to the stock image and when I took it in I was informed there were none ANYWHERE in the Phoenix valley. So something is definitely up. The person there said they are going to announce their own market! LAME! Give me a Froyo or Gingerbread update! Anyway the dude said I had to update to 1.1.0 to fix the problem and now I have to go down that rooting experience. <SIGH>

1.10 does indeed fix the audio problem.
However I have yet to find a rooted 1.10 image that has worked. Last time I tried (yesterday) gmail wouldn't work, market refused to download and my nook reported corruption and forced a erase & deregister / clear data upon itself...

"There was a problem with authorization. Please wait while we reset your device"

"There was a problem with authorization. Please wait while we reset your device"
OK - I have a Nook that was purchased at 1.00. I registered with BN.
Then I used NookColor_v1.1.0_r2.zip to root it.
I installed Market and got ADB to work. Life was great.
I think life started turning south when I went to the BN marketplace and purchased a book. In the middle of reading it, I got the dreaded "There was a problem with authorization. Please wait while we reset your device".
Fortunately, I had backed up my ROM using ROM Manager. So, I re-installed my ROM and it wasn't long before I got the message again. I feel like I'm now in an endless loop of resetting my device. I'm not sure how to get out of it. I've read several threads on this subject that simply leave me confused at this point. I'm looking for guidance. I LOVED my rooted Nook Color while it lasted. I don't like it stock. I'm looking for help.

I've been rooted on 1.0.1 since Christmas, and shortly after I first rooted, I had this happen to me too. There were others affected as well. Back then, we didn't have the recovery image, so I just set everything back up by hand. Since then it hasn't happened to me.
I haven't dug further, but I would guess that there is something that B&N doesn't like in the rooted image, but after a reset, it was happy again. Again, this was with my 1.0.1 root and an earlier rev of Autonooter, but this may be a way out of the loop you're in.

I had the same problem and assumed that it was because BN authorization puts a file on your NC that is date sensitive and if you do a restore (I was using titanium backup) and put an older file in place it will trip this reset scenario. I did a reroot with autonooter 3.0 and restored everything but any BN apps or data and the problem is gone.

Same thing just happened to me too. Going to restore and re-root later today.

I just went through the same problem as well. Tried out Nookie Froyo on emmc. Liked the Nook stock interface better. Tried restoring via CWM and get the "There was a problem with authorization. Please wait while we reset your device" error. Tried it twice and got the same error twice as soon as it connects to wifi.
Ended up having to flash back to stock and start the rooting process all over again. And now it seems to be fine.

Happened to me two weeks ago and I kept restoring. That's the problem, when I restored back to an older rom. Just root it again, restore the apps manually by dling off the market or through Astro. Don't restore the whole thing through CW. It worked for me because I haven't had the problem since then.

khmerwunder said:
Happened to me two weeks ago and I kept restoring. That's the problem, when I restored back to an older rom. Just root it again, restore the apps manually by dling off the market or through Astro. Don't restore the whole thing through CW. It worked for me because I haven't had the problem since then.
Click to expand...
Click to collapse
It happened to me as well funny thing was that I had a 1.1.0 never rooted Nook Color and I rooted with AutoNooter 3.0.0 and it happened within 24 hours. There was no restoring backups or anything. Any ideas?

bobo12 said:
It happened to me as well funny thing was that I had a 1.1.0 never rooted Nook Color and I rooted with AutoNooter 3.0.0 and it happened within 24 hours. There was no restoring backups or anything. Any ideas?
Click to expand...
Click to collapse
Again, my guess is that there is something in the rooting process that trips the reset. If you allow the reset to proceed without restoring the whole rom (Titanium restores should be fine) then you likely won't see it again. It's a little tedious, but should be ok... I've been running rooted for over a month with 1.0.1, and aside from the first reset, it's been smooth sailing.

scottanious said:
Again, my guess is that there is something in the rooting process that trips the reset. If you allow the reset to proceed without restoring the whole rom (Titanium restores should be fine) then you likely won't see it again. It's a little tedious, but should be ok... I've been running rooted for over a month with 1.0.1, and aside from the first reset, it's been smooth sailing.
Click to expand...
Click to collapse
I allowed it to reset but when it came back I was missing several crucial applications such as gmail, the android market and youtube. The rest (that are included in the root) were there. But I was lost without those applications and believed that a full rom reset was needed. Would there have been another way?

Using Titanium Backup, backup only User apps and data. Do not backup System apps and/or data. When you get back up from the reset and re-root, only restore User apps and data.
Maybe you can restore the ROM and backup just the User apps and data. Remove the SDcard. and then let it reset, or reset it to stock yourself. Get it back to how you want the base, root, install TiBu then restore your User apps and data.
Shameless plug: if you haven't already, buy Titanium Backup. It can be a life saver, or at least a sanity saver. I have no affiliation with the author, just a fan of the program.
Homer

Nc unrooted by itself.

Can anyone help? Here's what happened. I rooted my nc then I was playing with for a while. Then I clicked on one off my files that I installed myself, clicked on it and my nc restarted. When it turned back on it had the nc boot screen instead of the customized boot up screen. When I tried setting it up again and signing on to my gmail account it was working. So I had to unroot the whole thing. Now everything works. But can someone explain why it restarted and kind of unrooted by itself? Thank ill really appreciate it.
Sent from my ADR6300 using XDA App

Perhaps a Software Update reset your NC.

What file did you run? Also, what firmware version is your Nook currently running vs what version was it running before?

My firmware version is 1.0.1 right now. It hasn't changed. I used autorooter 2.12.25.

I actually just had the same thing happen to me with mine. It's a 1.1 from the box. All I was doing was changing some wall papers, then re-booted to try and install a different keyboard but didn't get there before seeing there was an "authentication problem" and needed to reset. I noticed some quirks after I was playing in rom manager and tried to reboot into recovery from there...whoops. I flashed nookie froyo and didn't like it, and I think reverting back gave me some issues. I've unrooted and re-rooted as of last night. I think I may just exchange it while I have the option. I used the 1.1 image posted somewhere here to un-root and used auto nooter 3.0 to root.

This just happened to me. I think it had to do with verifying my books, making sure they are legal copy's or something. or maybe updating one of my subscriptions. (Don't know)
My Nook is updated with 1.1.0
I rooted with autonooter 3.0
My thinking is that I should de-register and re-root
Than access my nookbooks thru a market app.

[Q] Rooted NC Spontaneously reboots to stock "half-root"!!

First of all - I apologize if this has been covered already. In the last couple of months, I have read countless thousands of threads and postings, and have been able to solve all of my issues until now.
I was attempting to flash an OC kernel to my auto-nootered stock ROM NC. I ended up in endless bootloops, and ended up using CWM recovery to restore my last image. The problem now is that once restored, the NC work flawlessly for about 15 minutes, then spontaneously reboots to the factory stock screen. Not a huge problem, except that it won't log in to my B&N account or Google account, and it appears to be partially rooted (superuser and market are in the extras drawer, but market won't connect. There is no youtube app).
This is happening over and over, and everytime I think I'm out of the woods, it flashes back to this stock ROM that won't do anything. What do I do next?
As an aside, I have had no luck with ADB... on my PC, I can't type any text into the command window, and on my Mac, the Manager File never shows up, regardless of where I download from. I'm hoping this can be handled with installing .zip files if possible...
Thanks for the help... I appreciate the assistance of those who know what they're doing!!!
Chris

[Q] Rooted Nook HD+ boot problem

A question for any intellectual Android/Nook-addicts out there...
Basically, I've rooted my Nook HD+ (Numberous times now) and have experience rooting android devices in the past and have had no problems. I used the CWM method - installed universal root on factory stock (And afterwards, 2.1.0 stock just to see if it fixed the problem... it didn't) and extras (Tried not installing extras twice also, didn't make a difference)
Basically, I've learnt the hard way that eight resets on boot and the device hard-resets to factory stock. The first Root Bootup is fine (The bootup after removing the CWM sdc) and, after turning it off and on again, so is the second bootup... But the third one is where the problem occurs. I power on as normal, and the standard 'Nook' screen appears as it begins to boot...
It then proceeds to resetting itself eight times - never getting past the 'Nook' screen that appears at the start of every bootup, therefore causing a hard factory reset.
I've tried using the CWM recover method to the OS I used before rooting the nook originally, and there doesn't seem to be any problems if the device isn't rooted. I've also just let it update itself from factory version to current version - and it works fine with that also.
Perhaps this is common and I'm just a plain idiot. I honestly can't find any answers - so if it is common, sorry for wasting your time!
Thanks for your time!
- P

Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:

P Complex said:
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
Click to expand...
Click to collapse
Why are you installing superuser? It is already installed with the universal root. That may be it too.
Edit: And some of the apps I put on there are old on purpose. Like Root Browser. I have it set so that the free version is ad free. If you update it, the ad free goes away.
Sent from my Nook HD+ running CM10.1 on emmc.

I am VERY sorry it's taken me so long to reply! Even though I've only just joined, I should have done it long before now.
I found the problem - it was 'Pimp my Android' app. I was experiencing something called 'boot loop' - so much for my research skills for such a common problem. I fiddled about with my usual settings - and found some that cause it to get stuck like that, even when they're set not to activate on startup!
Tis' all working now. Everything else seems to be just peachy! You were right, thanks for your help