I've seen a number of reports of rooted 1.1s being reset to factory after receiving a notification to the effect of "There was a problem with authorization. Please wait while we reset your device", after which the NC is wiped.
I heard this from a couple of friends whose NCs I nootered and initially thought it was due to my nootering via a nandroid from a possibly bad uSD, but I've come across two other cases in the wild.
So far it appears to be a wipe of /data since apps installed into /system are apparently still there.
Since the forums aren't filled with threads about this from panicked users, I'm wondering how wide-spread the issue is. I'm sure I'm not the only one who has nootered NCs via nandroid, but would that cause this issue? Maybe dalvik cache not being cleared after a restore? Would there be anything device-specific that would break?
Anyone else experienced this or heard about it?
It's been discussed previously, you may be able to find the threads with search. I've had this happen two or three times, and it was only after tinkering with hidden system settings. I don't think B&N is intentionally remotely resetting any Nook Colors.
I believe it has to do with Titanium Backup. Someone can point you in the right direction. Apparently restoring /system with Ti will get you in trouble because it uses 'old' keys so the stamps don't match, and going to the Nook Market will hose the device.
I have only had this happen to me if I restored any of the BN stock applications. If I only restore user apps/data, no wipes. There are plenty of threads around with this. Some report it is more random, but I'm not convinced. It appears that BN apps look for something related to authentication that includes some kind of date stamp: mismatch = reset.
Homer
tokyomonster said:
It's been discussed previously, you may be able to find the threads with search. I've had this happen two or three times, and it was only after tinkering with hidden system settings. I don't think B&N is intentionally remotely resetting any Nook Colors.
Click to expand...
Click to collapse
I'm inclined to agree, although hearing of two cases all of a sudden after months of no issues with previously nootered NCs makes me wonder.
What hidden system settings were you tinkering with?
Homer_S_xda said:
I have only had this happen to me if I restored any of the BN stock applications. If I only restore user apps/data, no wipes. There are plenty of threads around with this. Some report it is more random, but I'm not convinced. It appears that BN apps look for something related to authentication that includes some kind of date stamp: mismatch = reset.
Click to expand...
Click to collapse
So you're suggesting restoring a nandroid of /system is what's triggering this?
Get off 1.1 and hop on 2.2
edison said:
So you're suggesting restoring a nandroid of /system is what's triggering this?
Click to expand...
Click to collapse
I'd like to chime in and confirm your issue. I did a nandroid backup of my stock 1.1.0 rooted. Then I flashed nookie froyo to my emmc to test it out. Didn't like the interface much. So I tried restoring through my nandroid backup.
"There was a problem with authorization. Please wait while we reset your device"
Tried it three times and same issue. I had to restore to stock and reroot. And all is fine since. Sucks cause I thought that's what nandroid backups were for.
edison said:
So you're suggesting restoring a nandroid of /system is what's triggering this?
Click to expand...
Click to collapse
Yes. That is what happened to me. I think the key is to backup your user apps/data and then unregister/wipe before doing the upgrades. Then reregister and finally restore your user apps/data.
xboxexpert said:
Get off 1.1 and hop on 2.2
Click to expand...
Click to collapse
Problem with 2.2 or 3.0, no B&N stock reader or other stock features. Unless you know something different.
Homer
racks11479 said:
I'd like to chime in and confirm your issue. I did a nandroid backup of my stock 1.1.0 rooted. Then I flashed nookie froyo to my emmc to test it out. Didn't like the interface much. So I tried restoring through my nandroid backup.
"There was a problem with authorization. Please wait while we reset your device"
Tried it three times and same issue. I had to restore to stock and reroot. And all is fine since. Sucks cause I thought that's what nandroid backups were for.
Click to expand...
Click to collapse
This really makes me wonder if the issue is caused by corrupt nandroids. I can't get any of these new generic 8GB uSDs to make a working NF but other "brand" uSDs work fine. Before I found this out, I made the CWR boot + backups on one of these cards. If the uSD is flaky, then it stands to reason that the restored files might be flaky which in turn could cause a reset.
Alternatively, if there's device-specific info in the nandroids, like SNs or device IDs (the stuff that's saved in the rombackup.zip on p3), that was restored to a different NC, I could see how it could get confused and puke. But to restore to the same NC and have issues? Sounds fishy.
When you restored to stock, was it 1.1.0 stock? How'd you do the restore? 8x failed boots? dd a restore image? One of the CWR factory zips?
Yeah, I just flashed the stock 1.1.0 CWM image from here http://forum.xda-developers.com/showthread.php?t=945838
This just happened to me this morning. I'm not as technical as you guys, and I have no idea what a nandroid is. But I used AutoNooter 3.0 after updating to 1.1, and everything was fine for a week or so. Installed Launcher Pro, Dolphin HD, and a few other apps. This morning, I tried logging into Google Talk (which I hadn't tried before) with a different ID than the one I used to set up Google and YouTube. (I have two Google IDs, and the one I've used for Google Talk was not the same one I'd used to set things up on the Nook. I've since deleted the extra ID and am now using one for everything.) Soon after this, like ten minutes, I was merely reading a book and got the authentication error and reset. Since then, it's just weird.
It looks very much like it did when I got it. But NookColor Tools and Market is there. Softkeys is not. The stock book reader is acting funky, sometimes not displaying the menu that lets you change your page display. Sometimes not letting you make it go away. Getting rid of a bookmark brings me back to the home screen. It's just messed up.
At one point, for no apparent reason, it popped up with the the Market setup, but failed when trying to set up my Google account.
Anyone have any suggestions. I'm guessing I have to bring it back to the beginning, but I'm unclear of the right way to do that, because there's so much information here with various links, and I don't understand all the terms.
Any help would be appreicated.
loribuono said:
This just happened to me this morning. I'm not as technical as you guys, and I have no idea what a nandroid is. But I used AutoNooter 3.0 after updating to 1.1, and everything was fine for a week or so. Installed Launcher Pro, Dolphin HD, and a few other apps. This morning, I tried logging into Google Talk (which I hadn't tried before) with a different ID than the one I used to set up Google and YouTube. (I have two Google IDs, and the one I've used for Google Talk was not the same one I'd used to set things up on the Nook. I've since deleted the extra ID and am now using one for everything.) Soon after this, like ten minutes, I was merely reading a book and got the authentication error and reset. Since then, it's just weird.
Click to expand...
Click to collapse
This is the kind of stuff that keeps me worried. I'm on rooted eclair via autonooter 3.0 and I have everything working perfect!! I'm seriously done configuring and it runs like a champ, but I feel like one day it's just going to blow up somehow or my wife will grab it and try to sign in to something and then...boom!
Related
I was using my phone a few hours ago (adding an icon from the application drawer to the home screen if that will help with solving the problem) when suddenly, the phone reset itself as though I had done a wipe from the recovery console. I had to sign back into Google and re-sync my contacts and calendar. All my settings were back to defaults. My home screen icons disappeared and changed to the default icons (browser, contacts, dialer, market, messaging, maps) as did the wallpaper. All my SMS messages were gone. Basically, it as was as though I had wiped and flashed the ROM for the first time.
However, and this is the weird part. Not only were all my apps still there but they were still installed. All the settings were lost but they were still there. I am not concerned with the restoration of my settings or anything like that. I've got that all covered with backups. My big question is why did it happen? Has anyone experienced or heard of this phantom reset? My ROM details are in my sig but just in case that changes and someone visits this post later, it will make more sense to them if I list it in the post itself.
Cyanogen 3.6.8.1 w/Recovery Menu v1.4. Radio v2.22.19.26i. A2SD on 550MB ext2 partition. Compcache enabled/24MB.
Has the only happened once with you? It could have been just a glitch.
supremeteam256 said:
Has the only happened once with you? It could have been just a glitch.
Click to expand...
Click to collapse
Well, I can tell you why your apps survived, because you have them on sd card so that's not weird, you can wipe all you want and they will survive.
I would say this is a glitch, don't worry about it unless it happens again.
borodin1 said:
Well, I can tell you why your apps survived, because you have them on sd card so that's not weird, you can wipe all you want and they will survive.
I would say this is a glitch, don't worry about it unless it happens again.
Click to expand...
Click to collapse
Yes, the apps on sd being the reason I didn't lose them makes sense. I had a different problem losing apps on the sd when I wiped but that was a mistakes in the way I was slinking and it was also on JF1.51 (a2sd is very unstable on that ROM). Anyway, I'm seriously hoping it was just a one time glitch because my setup is voodoo smooth otherwise. I finally got my G1 running perfectly and I'd hate to think something was wrong. Either way, Nandroid is always an option.
Phantom Reset Not a Glitch. Happened Again!
OK. So it happened again. The phantom reset that I described in the first post happened to me again. It's pretty annoying to have to perform Nadroid restores all the time. Anyone have any real thoughts other than telling me it was a fluke?
Possible Answer
I am pretty certain that this happened right after I used Backup for Root Users. I have my identical setup on my father's G1 and this has never happened. He has told me in the past that he does not use that app. I don't want to instantly blame the app but I want to provide as much info as possible. Cyan's ROMs are too good for this to be an issue.
aaronratner said:
OK. So it happened again. The phantom reset that I described in the first post happened to me again. It's pretty annoying to have to perform Nadroid restores all the time. Anyone have any real thoughts other than telling me it was a fluke?
Click to expand...
Click to collapse
The dev has reported that it has issues (if you can replicate the errors, send him a logcat)
hes on the forums on this site
SOLVED
Thanks a lot. I will try and write-up (on dev's site) of what I was doing when it happened. It happened to me twice so I don't think I will use it again (at least until it's fixed). I am a backup freak so I like to use multiple apps but nandroid seems to cover it all. I will stick with what seems to work (and work well) for now.
On a side note, Cyan's latest looks too juicy not to try out. Going to upgrade now.
Picked up my NC 1.0.1 today. Rooted without issue. After having a Google Talk conversation, I lost access to Marketplace, and all Google Apps? Can't log back in?
Anyone else having similar issues?
P.S. My wallpaper was changed as well ?!?!?!?!?!
p.p.s. My browsing history and favorites are gone too? Please tell me an update or something was just pushed out. I feel like I just wasted a few hours of my life here.
My rooted 1.0.1 nook has problems as well. Gets authorization error and resets data. After restoring through the clockwork recovery, had it up just for 5 minutes before it automatically reset again. Lost all my apps, market access, youtube, etc. Don't know if this issue has been discussed before. May just have to go back to stock.
It appears that something is amiss. I cannot sign back into any Google Services.
Can't establish a reliable data connection to the server
This could be a temporary problem or your phone may not be provisioned for data services. If it continues call Customer Care.
Click to expand...
Click to collapse
Would a simple re-rooting solve the issue?
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
abexman said:
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
Click to expand...
Click to collapse
I might add that I got my device it was at 1.0.0 and I rooted then reflashed to stock to upgrade to 1.0.1 and rerooted. Then I noticed after today's unexpected reboot/data wipe (the status screen during the reboot says it was wiping data) it again gave a message that it had just upgraded to 1.0.1 so I initially thought this was an issue with the device thinking the firmware upgrade was not quite done...
Mine quit working as well. Mine is a 1.0.0 that was auto-nootered. Everything was fine and I used it daily. Now it is a brick, nothing I do seems to make it boot. Every once in a while I can get the backlight to come on but nothing else and it just goes off again in a few seconds.
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
If your NC dosen't boot at all. Try doing a dd of snowfox's boot.img in dev section. See thread for more info. You'll need to boot into NF from SD.
Sent from my HTC Desire using XDA App
scottfish said:
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
Click to expand...
Click to collapse
I have tried rerooting, and restoring through clockwork...it seems to always revert and bootloop. Although the reroot lasted a week and clockwork restore hasn't lasted 24hrs twice now.
Not sure what to do but My wife is ready to kill me! I'll have to go stock till someone finds a way to bust up this authorization or just wait I read some ROMs are being developed.
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
I hadn't realized I should be doing this. I will try it. I am actually thinking that my first store purchase came w/ an update (my issue seemed to start right after a magazine trial purchase was made).
Thanks.
>DARKMAN< said:
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
Click to expand...
Click to collapse
Thank you, I will try that. All the searching I did was for disable OTA NC and such but actually searching for OTACerts brought out many many threads that were archived on this subject... I can't wait to get home to try it!
I did not rename the ota file.... will give it a go.
I have done some research here and on Google on a really odd problem...
My wife has a NC I updated to 1.0.1 then rooted. About a week later on her way to work it restarted and unupdated (?) back to 1.0.0... So I thought it was a fluke, root was gone but most things still worked, not Youtube or market but other apps I installed while / did.
Now twice, 2 days in a row I have checked out the device, I installed Clockwork, did a backup and the next morning on the way to work (She works in manhattan, takes the train in) it is bootlooped "touch the future of reading" so last nite I ran the clockwork restore and it was fine then again this morning... same thing stuck in a boot loop.
As happy as I am about her being able to restore it on her own...it takes a while and shes at work by the time its done! and the maddening part is that I booted it multiple times the nite before in both cases...
What could be causing this? Things I haven't tried yet?
I checked the SD to make sure there weren't any update.zips or similar,
I have not formatted the SD, that I will do tonight.
I read the whole thread regarding Clockwork I didn't see anything I might have messed up...Does this have to do with uSD boot priority and maybe I have a hidden file on the SD?
And I have really searched for something similar, people have bootloops but not like mine that I can see.
Sorry for being long here but this is frustrating, I'm not all that new at this I've been voiding my warranties for a long time and this one has me stumped...
Thanks in advance for any reasons, suggestions.
EDIT: Looks like I am not alone, I am seeing more of these problems pop up now.
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
eyecrispy said:
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
Click to expand...
Click to collapse
I have disabled OTA but if this is a registration/ auth problem I guess it wouldn't help.
I have NOT gone the 1.0.0 then root path and that sounds like a good next step, thank you.
Long time reader, first time poster (hello everyone!). I was wondering what the opinion of the folks here might be and if they've any suggestions. Today my rooted Nook Color suddenly started acting up. Applications are very often not responding as they should, bringing up the 'Wait' and 'Force Close' box (happens when pressing the soft back and menu buttons as well). It's really quite weird, earlier today I was using it just fine, and suddenly it started acting like this. I tried the usual things like fixing permissions and clearing the dalvik cache, nothing helps. Also, annoyingly restoring a backup from a previous 'known working' state didn't help either. (I suppose I should note that I'm not running CM7 or anything like that)
Any suggestions or ideas on what could have happened? Should I perhaps return it to stock and try to exchange it for a new one (I've only had it for about a month)? The fact that it seemed to still be happening when I restored a back up makes me wonder if it's some kind of hardware issue.
The thing driving me crazy is how it's so suddenly acting strangely. I've been using it rooted (and overclocked, on dalingrin's excellent kernel) just fine for about a month and it's never seemed unstable or anything.
I forgot to mention (not that it probably matters) but the volume buttons caused the wait/force close thing too. Guess I'll be calling them tomorrow.
Having same problems. And VERY SLOW. Wait or Force Close
Very weird, but I noticed today that it started acting flaky in my Nookie Froyo 0.6.8.
I installed Amazon's app store on there today and angry birds rio. The apps seem to be okay, but general opening and navigating are herky jerky.
Something else that is weird, I was just using it and it completely locked up on me to the point of needing to do a hard shutdown by holding down the power. At the exact same time, I happened to look at my phone and it also had rendomly rebooted itself at the exact same time. My phone is running CM7 (Droid1).
Coincidence?
HI,
I had a variety of problems with similar symptoms as you describe, but I had
been playing with several uSD installs of HC/Froyo/CM7 internal/Froyo internal etc.
I believe that the main cause of my problem was due to an interaction between
the EXT3 and EXT4 formatting of the cache partition. The solution for me was to
reformat the cache partition for my current installation.
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Not sure if any of these are relevant to you though.
Good luck.
Peter
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
pmilford said:
HI,
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Click to expand...
Click to collapse
Thanks, but I tried those already (I forgot to mention it in the first post, but I did try reformatting the cache partition).
JLCollier2005 said:
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
Click to expand...
Click to collapse
Yeah, I guess that's a good idea. Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
9thSage said:
Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
Click to expand...
Click to collapse
All I'd need to do to install Froyo from here is format/factory reset everything with clockwork and then install the zip from within CWM, correct?
Couldn't get it to work for some reason. Since I wasn't sure, I decided to format data, cache, and system, then use one of the excellent "Nook Color Restore to Stock" zips. It seemed like it was ok (couldn't test it more since I forget my B&N password and evidently made a typo when tying my mother's maiden name ), decided to try that back up again since I knew the back up worked at one time with no problem (and the md5 was fine, so that shouldn't have changed) and it worked fine for maybe 20 minutes, but now it's weird again.
I'll have to try Froyo again tommorow when I'm hopefully less out of it. I suppose that's probably a more meaningful test.
I know I said I was going to install Froyo, but I decided to try bringing it back to stock and re-rooting it from scratch. I've been using it for a while (reinstalling apps, changing settings back...etc) and it's worked absolutely fine. Been using it on and off for a few hours.
I'll be sure to really bang on it today to make sure it's stable, but so far so good.
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
9thSage said:
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
Click to expand...
Click to collapse
Glad to hear! I actually just had a similar problem (again on my Droid) that it ended up being the ROM, but yet everyone else I know had no problem on that rom....just goes to show you Android is different for every unit.
Hi there, i have faced some problem here when i wanted to restore back my settings through KIES after i updated my firmware to LA1 using KIES too. i have not rooted my Gnote.
The problem is that it will take a LONG LONG time when restoring the 'miscellaneous content files'?
Anyone faced this before...Really appreciate your help...Thanks...
Yes! Very similar problem, if you replace 'a very long time' with 'a ridiculous amount of time'. It gets stuck around 76% and then just stops. As I've found with samsung software - it never actually tells you what it's doing, it just fails to do it.
My only solution thus far is to do the restore and deselect miscellaneous content files. Then the restore works fine. Unfortunately that means I've lost all my apps, and probably a lot of other stuff I'd really quite like. Going to call Samsung in the morning and see if they have an answer. Will post back if they say anything useful.
Restoring through Kies doesn't work
I'm having the same problem. I mean, how the heck are we supposed to back up our devices??
I had done a factory reset on my Note (for unrelated reasons) and backed everything up through Kies. But when I went to restore everything, NOTHING got restored at all, even though Kies said that the restoration was successful.
I've never had a problem backing up any of my phones in the past, and I don't know why it's so difficult with the Note. I'm looking forward to ICS coming out, but it's going to be a pain in the rear if I have to manually restore everything on my phone again.
Suggestions anyone? (My phone isn't rooted either)
samtetley said:
Yes! Very similar problem, if you replace 'a very long time' with 'a ridiculous amount of time'. It gets stuck around 76% and then just stops. As I've found with samsung software - it never actually tells you what it's doing, it just fails to do it.
My only solution thus far is to do the restore and deselect miscellaneous content files. Then the restore works fine. Unfortunately that means I've lost all my apps, and probably a lot of other stuff I'd really quite like. Going to call Samsung in the morning and see if they have an answer. Will post back if they say anything useful.
Click to expand...
Click to collapse
Probably what we can do is to deselect the misc content files. To avoid losing the apps, we can use some software inside market such as apps backup & restore. That will settle both the problems of backup and restore.
Beethoven9th said:
I'm having the same problem. I mean, how the heck are we supposed to back up our devices??
I had done a factory reset on my Note (for unrelated reasons) and backed everything up through Kies. But when I went to restore everything, NOTHING got restored at all, even though Kies said that the restoration was successful.
I've never had a problem backing up any of my phones in the past, and I don't know why it's so difficult with the Note. I'm looking forward to ICS coming out, but it's going to be a pain in the rear if I have to manually restore everything on my phone again.
Suggestions anyone? (My phone isn't rooted either)
Click to expand...
Click to collapse
You can refer to above.
It is more recommended to root your SGN and use titanium backup as the backup tools. Everything can be backup from using titanium backup.