8-31-21: My report on the death of this app for the NST is a little premature. See post #5, etc., for a "fix". It worked for the poster and it worked for me. It might work for you.
Don't shoot the messenger...
Sometime in late 2020 or early 2021 it became impossible to negotiate an initial login with the Kindle app (yes, even with the OTP they email you). I've checked the security certificates and they are fine. I've tried installing the app on newer devices, going all the way to Oreo. Same behavior. A logcat on the NST shows a failed SSL negotiation so it looks like the server just won't talk to the old app any longer--at least for an initial authorization. That's the very bad news.
There is a tiny bit of good news for those who already have the Kindle app installed and authorized. At least on my three devices it continues to function completely. You can still check out Overdrive Kindle books and send them to your device and the same book on different devices appears to sync. You can also sideload .mobi books and read those. The clock is, however, probably ticking.
I mention this as a warning for anyone who has a legacy Kindle installation and is thinking of doing major work on their device. If you uninstall or wipe out the Kindle app, it's gone for good. It may be possible to use something like Titanium Backup to restore the app. I was able to find all this out after a reset and then restore my NookManager backup and the app worked fine.
Edit: I have done a little experimenting and the app authorization token appears to include a lot about the device and system. So it's not possible to use Titanium Backup. I tried this on a FW 1.2.1 installation with a working copy of Kindle. Then I updated and rooted FW 1.2.2, installed the Kindle app and then restored a Titanium backup from the same device (but with FW 1.2.1). It failed to initialize, asking to register again. I've had success only in restoring a NookManager backup from the same device with the same FW, etc., and in cloning a device from a NookManager backup. This is not something I would necessarily recommend, but you might have your reasons. However, when I tried to correct the MAC address, this threw off the Kindle app token and it reverted to asking for registration again. So there's very little wiggle room for preserving a working installation if you have to do any significant changing.
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
If the SSL layer is somewhere in Android oh boy that might be harder cookie to bake from my point of view.
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
I
Click to expand...
Click to collapse
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
Click to expand...
Click to collapse
My understanding of the issues is very limited. I once happened into a discussion where it was stated that apps which need to communicate with external servers contain their own SSL certificate which has an expiration date. If so, apps like that just die a "natural" death.
It's actually amazing that there are some apps requiring logins that still work on the NST. Two that come to mind are ancient versions of Pandora and TuneIn Radio. I use both and they still perform flawlessly. For now.
Until today I didn't know what Pandora is but I am familiar with TuneIn radio app. Good to know that some of those apps is still working. Well it just had to be complicated with SSL/TLS hidden somewhere in Android layer. I totally understand why people like Android user friendly UI and apps availability. Still gamble with Java seems that didn't paid of regarding promised platform crossing ability.
So either porting to a new Android version which probably will not be very new (low RAM) or making custom Linux which is anything but user friendly?
Edit: Scratch that question about Linux and the app OP mentioned! I just realize that there is no Linux Kindle app. It could be used through Wine and such witchcraft but that is stupid way of doing things on this device. Better option is to use it on PC and then pass it on to NST using Calibre IMHO. SSL/TLS although remains as weak spot for the time being. Oh well... If that issue with certificates get somehow fixed maybe Kindle cloud reader from browser could reclaim at least part of functions of dedicated Kindle app.
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
wrexroad said:
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
Click to expand...
Click to collapse
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
nmyshkin said:
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
Click to expand...
Click to collapse
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
wrexroad said:
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
Click to expand...
Click to collapse
Excellent. As I expected based on legacy installs continuing to work, once the credentials are on the device, you're good to go whether you use single or two factor login after.
I had a password issue with Amazon awhile back and I'll bet that's where the problem originated. When I changed my password, authentication must have gone to two-factor. I need to check that, but I'm pretty sure that's it. What great news! Back to seamless library book checkout and download, all on the device!
BTW, the version of the app you mention is the only one that works (again!) on the NST.
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
wrexroad said:
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
Click to expand...
Click to collapse
Mmm... I'm glad you posted this before I started testing. I have two NSTs with working Kindle apps right now and I don't want to trash those while tracking down the "solution". I need to think about how I'm going to approach this.
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
wrexroad said:
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
OK, that's what I had hoped for and expected since my two working installs were made before my auth. got changed to two-factor. With really old apps you never quite know how server negotiation is going to evolve.
I hope to give it a try later today.
wrexroad said:
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
When I went to my Amazon account it seemed like 2SV was not enabled, by which I mean that clicking on "edit" for the settings generated an email which contained a link that took me to a page with a button that said "Get Started".
I didn't pursue this. I didn't see anything about turning it off--or should I have gone farther along?
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
wrexroad said:
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
Click to expand...
Click to collapse
Yeah, this is not working for me. I looked at the 2SV stuff again this morning and thought, "well, I'll just set it up and then disable it". Except I don't own a mobile phone (no, truly, just an emergency ancient (non-text message) device I keep in my glove compartment), and the QR thingy woud do me no good with the NST. So I'm cooked.
Despite apparently not having 2SV set up, now I can't even generate an OTP email when I try to login with the Kindle app. But my two working installations continue to function. Puzzlement.
Edit: I had a friend with a mobile phone help me out. So I finally got to where I could "disable" 2SV. But it made no difference. Still can't log in or even generate an OTP email by trying to log in. I'm glad this worked for you and I'd like to think it might work for others, but alas my account appears to be "special".
Edit-Edit: Yeehaw! It took a lot of fumbling for me with the unwieldy password I had to recreate in the near past, but by clearing the dalvik cache and making sure that 2SV was actually listed as "disabled" at Amazon, I was finally able to log in a new installation!!! Now I don't have to run a "clone" of another device on this particular NST. Thank you, @wrexroad, for taking the time to look into this and communicate your findings. One big step back from the brink for the Kindle app
That's awesome, I'm glad you got it running! In the future, if you need to get a password via text, you can use a temporary number here: https://sms24.me/en/countries/us/
Hey folks,
I just stumbled into this NST world and want to share my experience with the Kindle app. I'm on FW 1.2.2, and used NookManager to root. I replaced the certs file as recommended in another thread. Once I was ready to login, I enabled 2fa on my Amazon account in a browser. The instructions there clarified that I would need to use PASSWORD+OTP when registering my device. Previously I had tried only the OTP, or only my normal passwrord, but those failed. Appending the OTP to my password, I was able to login.
Hope that helps anyone else who has reached this point.
Related
I'm guessing there's a utility, or utilities, running on the Nook that does things like auto updating the firmware, seeing what books are in your library, what page you're reading, other usage stats, etc.. Has there been any work to disable these spies?
Although I mainly wanted the Nook as a tablet, I'd like to buy a few books, and use it to view a few (Legally owned) PDF files. But if B&N is going to mess with my rooting, or decide something isn't legal, or otherwise decide to remove things off my Nook (Remember the Kindle and 1984?), or spam me based on what I'm reading, I'd rather wipe all B&N software from the device, and just have an Android tablet.
BTW, if the above sounds like a complaint, it's aimed at B&N, not the developers here, for which I am most thankful for all their awesome work!
Since there hasn't been an update yet, nobody is sure if the methods used by other devices will work or not. I believe there are a few threads in the development forum that talk about possible ways of preventing it from auto updating, but they haven't been tested yet to see if they work.
Do some looking in the dev forum or do a search and I"m sure you'll find what I'm talking about. It's a standard method of preventing Android from updating, but no telling if it will work.
Edit:
Here is the thread I was referring to:
http://forum.xda-developers.com/showthread.php?t=860480&highlight=update
Thanks for the response. I checked the link, and was surprised Android has the auto-update functionality built in. Do you know anything about possible spy applications? Has anyone checked it's internet activity? Any strange processes?
What do you mean it hasn't updated. The day you first powered it on and connected to the internet you got an update, at least mine did.
I imagine you could use wireshark and then turn on your radio and see where the nook goes first. It could have a schedule so maybe completely restore the device and then see the first addresses or urls it goes too on it's own. Once you get that then it's just a matter of entering those urls in the host file with an unresolvable address.
I probably will use Wireshark, when I get my nook (Christmas present). I just didn't want to reinvent the wheel, and be all prepared when I finally get it. I'm surprised there isn't more interest in privacy with the nook.
Mine didn't update when I got it. It's version 1.0.0, and until you set up wifi there is no way for it to get an update. Also, there isn't a way to check for updates. The original Nook had an option to check for updates, not with the NC.
Hi All-
Trying to get the Audible app working from the android market. It downloads and installs seemingly correctly. I can even browse the audible catalog using it.
What isn't working correctly for me is entering my account information to authorize the device & start playing items from my audible library. I seem to end up in an endless loop of asking for my credentials, saying they're good, followed by asking for them again. (I have another thread open where I am experiencing the exact same problem with the android market -- I can't seem to buy paid apps but free apps download and install fine & dandy)
Hopefully this issue with audible & my android market issue are caused by the same problem & both will start working once solved. In the mean time, can anyone confirm they have audible working on their device??
Thanks,
Mark
Have Exactly Same Issue
I called Audible and spoke with tech service - they even reset my password but to no avail. Audible is basically clueless (owned by Amazon so maybe it's a conspiracy
docfreed said:
I called Audible and spoke with tech service - they even reset my password but to no avail. Audible is basically clueless (owned by Amazon so maybe it's a conspiracy
Click to expand...
Click to collapse
I really dont think audible tech support can be faulted for not being able to help you get their app working on a rooted ereader.
Audible and Rooted Nook Color
I have this same issue with the Audible app. I had an email thread with someone from the app team and here is what I got from them.
"The problem is that we are not getting a consistant device id for use in authentication. I'm guessing from the device that you're using that you're making your own framework builds; if so, if you can force the DeviceID field to always give the same value, then your activation problems should stop.
I've deactivated all the activations on your account. Just to be explicit, we check TelephonyManager.getDeviceId(), and if your phone type is TelephonyManager.PHONE_TYPE_NONE we'll check android.provider.Settings.Secure.ANDROID_ID. If for whatever reason you can't get these working correctly, then you can use the .audiblePrefs file from a device where this does work; we cache the device id there in case TelephonyManager.getDeviceId() returns null but your phone type isn't PHONE_TYPE_NONE."
So it looks like someone will need to figure out how to ensure that the Device id remains the same during all the transactions with Audible.
Sean
Thanks for finding that, Sean.
I have an android phone I can look at rooting to get to the mentioned prefs file. Perhaps that would be a way to generate a stop-gap while one of the devs looks into the device id issue.
Mark
Doesn't Market Use the Device ID
It seems that I remember that the Android Market also uses the phone device ID - in fact that is why certain cheap Android tablets cannot have the Market installed. Since we can get Market on a rooted Nook Color with no issue, I don't understand how the device ID would keep changing in case of Audible.
Keeping an eye on this thread. I would love to have my Audible app working
Sent from my nook color using XDA App
Same problem here; also following it like K8108; thanks for any help you guys can come up with!
I havent tried to install audible yet but wanted to listen to my huge library of books on my old mytouch before they had an app and found a solution. You can buy SoundTaxi and rip the downloaded Audible books from your PC to whatever format you want and put on memory card on the Nook and listen. its not as bad as you think.
The odd thing of it is that under 0.2 and side-loading the app seemed to work for me. Moving to the latest autonooter however is causing the authentication problem that everyone is having.
Audible support was very kind, but basically said we do not support tablets only phones. My NC was trying to connect to audible.co.uk thus causing the conflict. As a Californian this isn't going to work for me obviously. The app seems to be able to download but not play the .aa files. Is there anyway to check the server without sending an in-app email, as that is the only way I know how to check?
Subscribed to the thread with hope that someone smarter than me can figure this out.
Update: Forgot to state that using adb of Audible does not work. Does this have anything to do with the new .jar file from Barnes and Noble, or something in the Autonooter itself. 0.2 was working very nice, but that was also under 1.0.0.
So doesn't anyone have any android device with working Audible on it... that can examine .audiblePrefs
RpDn said:
So doesn't anyone have any android device with working Audible on it... that can examine .audiblePrefs
Click to expand...
Click to collapse
I have audible working on my android rooted HD2 - and have put several builds on there, but don't know a lot of techie stuff. If you will explain to me where to look, I could have a try.
It's been suggested to copy a working .audiblePrefs file over, but I don't have another android device to set up. I might borrow one, though, for a temporary setup, to get a working .audiblePrefs file (or an Id anyway), if I knew it was the way to get around this glitch. Was hoping someone with a NC and another android device would have tried it by now.
I have a Samsung Fascinate with Audible. I copied .audiblePrefs from my SF to my NC, rebooted my NC, and I am still in the loop of entering my username and password.
I am don't know much about the technical side of this, but I am very good at following directions. If there is anything you want me to try, just let me know. I am very anxious to try this.
I don't mind posting my .audiblePrefs file, but I don't know if there is personal information in there that I should be careful about posting.
I think you should keep your prefs file to yourself... it may be specific enough to include subscriber Id. Also, you may have exceeded your activation limit if you've tried too many times before copying your prefs... an email to Audible can reset the limit.
I find it interesting that the activation loop includes a quick flash of "Activation successful" on the screen. Audible sent me a reply in response to question... that they reset my activations... didn't solve prob, of course. Also interesting that I -can- play recent 'free' excerpts dnld'd from them via Audible app on the NC.
Just need a modder to look into this Id storage/reading. I'm a comptech but just a newbie on Android/NC.
I call all the time to have Audible reset my activations. That is no big deal for me. I am rooting phones all the time or switching computers and I never deactivate devices the way you are supposed to. I do wish Audible would wise up and give their users a way to reset activations online. But at least they never hassle me about resetting them when I call them.
Any new updates on getting Audible to work? Just did the autonooter and have hit the same problem.
Thanks,
Tim
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
k8108 said:
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
Click to expand...
Click to collapse
I went from a stock 1.1.0 and then applied autonooter for the first time. Audible does not allow the authentication to occur just as the original poster noted.
k8108 said:
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
Click to expand...
Click to collapse
I did same thing (except I requested only my Android activations be reset, so as not to affect my PC or WinMo phone)...and have been using Audible on my NC successfully for a week.
I had 2 Nook Colors I bought Friday. Today I have successfully set up one with 1.1.0 and autonooter'd using 3.0. Followed instructions and everything works as assumed.
On the second nook (wife's), I can load Autonooter, but when I get to the YouTube part, it has a network issue. I then try and go to GMail and it says the account is not set up to sync, but where it wants me to set this up is not a settings option in Nook Color Tools or anywhere I know.
I've had to reset this device twice back to factory settings. Can someone give me an idea on what I can try to do this differently?
I tried a third time by setting up the Google Account at the account setup screen during setup, but still have the problem. Seems that there is some GSM settings popping up on this device.
Wife is not happy that my NC can be rooted and her's cannot. I'm to the point of returning hers and getting a new one.
So, her device works fine as-is before trying to root it? Wireless is fine, connections are okay, browser works, etc?
I'd say double-check that you're actually on 1.1.0 if you're using the noot for 1.1.0, or maybe wait for the real Auto Nooter to see if that works better.. Should be out in a day or two hopefully.
Yeah, her device works fine stock. I have flashed it back to stock 1.0, stock 1.0.1, etc. each time doing a sideload update to 1.1.0. I then used the Autonooter for 1.1.0 and I keep getting some issue with setting up her gmail account on the phone.
If I try and set it up during the Android Setup, it loops and simply makes me set it up again. Otherwise, if I skip...I get asked to set up gmail account when trying the YouTube My Channel portion of the setup. I get the network error there.
What I have noticed is that when setting up the account on the Android Start-up section, it gives me a notification of sync/connections, but the account does not setup to sync. This is the problem - I can't find where to make the account sync or complete setup with the Autonooter I guess.
Like I said, my Nook works fine and was the first one I did. I followed the same procedures on her's and it is the same issue each time.
Disclaimer: She doesn't use the Gmail account much, but I logged into on PC. Not sure if that is a factor.
Thanks for your feedback!
lxadoz104 said:
Wife is not happy that my NC can be rooted and her's cannot. I'm to the point of returning hers and getting a new one.
Click to expand...
Click to collapse
Best advice I can give (though it seems one device may have something goin on for sure) is that you earn some brownie points and give her yours and get yourself a new one! Amazing the future favors returned by an action like this, hehe.
Great idea. Where can I adjust the account settings for her account in place of mine? (Google account)...Thanks.
lxadoz104 said:
Great idea. Where can I adjust the account settings for her account in place of mine? (Google account)...Thanks.
Click to expand...
Click to collapse
Both my wife and I use same account for the Market (really don't like paying twice for apps...we do the same for purchased books from kindle / B&N)...you can add / remove google mail accounts from inside google mail settings. Just click ADD ACCOUNT, and disable yours (or at least disable sync).
**Disclaimer** Sharing apps across multiple devices in the same household is smart, and not a slight to developers at all. We purchase apps and books, and both use them...that's called economical
Oh also.be sure to check out these cases for your new toys! We both have them, and they're perfect!!
http://forum.xda-developers.com/showthread.php?t=934081
Have you tried just doing it from 1.0.1? Is there a specific reason you want to be on 1.1.0?
lxadoz104 said:
.I get asked to set up gmail account when trying the YouTube My Channel portion of the setup. I get the network error there.
Disclaimer: She doesn't use the Gmail account much, but I logged into on PC. Not sure if that is a factor.
Click to expand...
Click to collapse
Is her G-Mail account linked to YouTube? This is a pre-requisite. Good Luck!
The easy (but time consuming) fix for this is to downgrade to 1.0.0 or 1.0.1 (make sure the downgrade was successful via settings-device info-about or whatever it is.) Then use one of the older auto-nooters to noot that version. From here, if you still would like to have a rooted 1.1 ROM, install rom manager from the Market and use it to flash the 1.1 pre-rooted ROM from the dev section. This would be the best way in my opinion.
I know nothing about any of this so bare with me guys/gals please. Just need help once and ill remove my account. If any of you feel like im wasting your time then please tell me and ill remove my post. Thankyou and i hope someone will give me an idea of whats going on.
Friends ex girlfriend is remotely accessing his phone from her computer, she can lock him out and write text out of format on the lock screen. She has deleted everything on his phone 8 times in the past hour. The Verizon recovery app has been disabled, we went into the Verizon store and changed EVERYTHING, number, passwords, made sure if she ever called in wanting info she couldn't get it. There is no way she figured out any of the passwords, she doesn't have access to any of his accounts, gmails facebook etc... i thought for sure she was using the recovery app but that's impossible cause no account has been created to access to his phone. Idk guys like i said im not an expert one thing that has me most skeptical she can write whatever she wants, whatever color, on his phone on any spot on the screen. Its completely out of set text formations on the lock screen looks like doodles i guess. Just curious if you guys have have ever heard of anything like this happening before. Thanks and i apologize if this shouldn't be here just on a desperate attempt to figure this out. Verizon is completely stumped they have no idea how she does it, even the main tech guy at the store (idk his credentials) cant figure it out.
From what I've seen so far, Android Device Manager (part of Google's setup) can do remote wipes. as can Motorola ID. I imagine both of these may "automatically setup" when you re-activate the phone. Beyond that, you'd need an app to perform such changes, I'd think.
Also, if he's on a joint-account with his exGF, and if she has access to the account, VZ may be doing this without the store-people knowing it?
schwinn8 said:
From what I've seen so far, Android Device Manager (part of Google's setup) can do remote wipes. as can Motorola ID. I imagine both of these may "automatically setup" when you re-activate the phone. Beyond that, you'd need an app to perform such changes, I'd think.
Also, if he's on a joint-account with his exGF, and if she has access to the account, VZ may be doing this without the store-people knowing it?
Click to expand...
Click to collapse
If it's Android Device Manager, maybe it would be sufficient to just change the Google login password?
Yeah, he changed his Google password right?
schwinn8 said:
From what I've seen so far, Android Device Manager (part of Google's setup) can do remote wipes. as can Motorola ID. I imagine both of these may "automatically setup" when you re-activate the phone. Beyond that, you'd need an app to perform such changes, I'd think.
Also, if he's on a joint-account with his exGF, and if she has access to the account, VZ may be doing this without the store-people knowing it?
Click to expand...
Click to collapse
He was on a joint account but upon breakin up with her he took her phone, cancelled it, removed her from the account changed his passwords to facebook and google and everything else. Just for the guy to call in and request info he has to answer 5+ extra security questions before hes allowed any info. But ill check out the ADV maybe thats it. Thankyou
Hi all,
I've just rooted my Nook Simple Touch and am running the 1337 ROM. Everything's run smoothly so far, with the exception of one thing: my reader app (Mantano) won't sync with my cloud account.
I've been using Mantano Cloud for a few years now, and it's indispensable to my reading habits because it syncs across all of my devices. As such, switching to another service is not an option; I need to find a way to get this to work with my account.
When I first tried it, the sync made as far as "Processing book metadatas (75%)," but would go no further. I tried deleting the account and resyncing, but then it wouldn't even get that far (instead hanging at the first step, "Downloading changes from cloud"). As an experiment, I tried making a trial account and syncing one book, which worked. Thinking that perhaps I was trying to sync too much at once, I cleaned out my Cloud library (cutting from ~150 books down to ~20 books, and from ~1800 annotations to none). Still the Nook was unable to sync with my account (I gave it a few hours just to be sure that it wasn't simply an impatience issue).
I am wondering if maybe the issue is caused by trying to sync books from the newer version of Mantano I use on my phone (2.5) to the earlier version (2.2.12) that's compatible with Android 2.1, but I'm not sure.
As this is clearly app-specific, I have emailed the developers to ask their advice, but I know that these boards are often a much more valuable resource. Do you guys have any suggestions on what the issue might be, or possible solutions I could try that would allow me to sync my library between these devices?
Thanks in advance for any help you can provide!
chelce said:
[...]
Click to expand...
Click to collapse
Hello there, chelce,
First off, thank you for using my/our (it's @yattaro's and mine) 1337 ROM - we hope you're enjoying it!
Now, onto your issue. This is all pure speculation, as I don't and have never used Mantano myself, but I do have an idea of what your problem might be.
What I'm guessing is that the older version of Mantano installed on your Nook for some reason is incompatible with your specific Mantano account because of how it's already hooked up to a mobile device with the latest version of the Mantano app installed. The reason I think this is because of how you guaranteed that the old version of the Mantano app will work properly, albeit with a different account, and because of how I'll bet you didn't connect your phone to the new, temporary account.
To test this theory, first, please cut the Mantana system .apk from /data/app and paste it onto your external sdcard (/sdcard) using either ADB, an FTP server or a root-enabled file explorer. Then, re-install Mantano by tapping on the .apk you just moved from /data/app to /sdcard.
Now, please temporarily disconnect your phone from your Mantano account.
Finally, go through the setup/sign in process of Mantano on your Nook and see if it connects.
ИΘΘK¡€ -
Thanks for your quick reply! I am definitely enjoying the ROM, and will be happy when I can get Mantano working so I can actually start reading on my Nook.
I tried your suggestion, and unfortunately it didn't work. It was a good thought though. I also tried syncing my phone to the trial account that my NST was able to sync to, and then syncing my NST to it again. It worked. It seems to be my specific account, but I'm not sure how to rectify this short of cancelling my account and starting over again (which I would rather not do because it's a paid account).
Any thoughts? Conversely, an update to Android 2.3 would also solve the issue, but I'm not sure what the timeline is on developing for that (and unfortunately I don't know enough to be able to help).
Thanks again - always nice to be able to come to a community for support!
Updated Issue
In the hopes of finding a solution to a problem that is still happening, here is an update to the problem I mentioned in my previous posts:
I decided to bite the bullet and just sync to a different account. It was a minor hassle/expense to set it up, and my Nook was working fine for a week (syncing posed no problems). Then, tonight, I synchronized a file from my phone to the cloud, and when I tried to synchronize my NST to download the file to it, it got stuck on "Processing book metadatas (88%)." Basically, I somehow got stuck in the same dead end as before.
I unsynchronized the file on my phone, but my NST is still getting stuck at 88% during the sync.
I am at a loss for how to proceed. I cleared the cache (both of the app and the device), and had already tried (un/re)installing the last time this happened, to no avail (first the app, then everything after a factory reset, and finally the whole ROM).
Any thoughts or suggestions? Mantano still hasn't gotten back to me, so as of right now I'm stalled.
Thanks!
chelce said:
In the hopes of finding a solution to a problem that is still happening, here is an update to the problem I mentioned in my previous posts:
I decided to bite the bullet and just sync to a different account. It was a minor hassle/expense to set it up, and my Nook was working fine for a week (syncing posed no problems). Then, tonight, I synchronized a file from my phone to the cloud, and when I tried to synchronize my NST to download the file to it, it got stuck on "Processing book metadatas (88%)." Basically, I somehow got stuck in the same dead end as before.
I unsynchronized the file on my phone, but my NST is still getting stuck at 88% during the sync.
I am at a loss for how to proceed. I cleared the cache (both of the app and the device), and had already tried (un/re)installing the last time this happened, to no avail (first the app, then everything after a factory reset, and finally the whole ROM).
Any thoughts or suggestions? Mantano still hasn't gotten back to me, so as of right now I'm stalled.
Thanks!
Click to expand...
Click to collapse
Sad to say, I honestly can't imagine exactly what your problem is, nor how to fix it. I bet it's a nug (a nook bug), which is what I call those small (or not so small), inexplicable issues Nook Touches often have that don't seem to have a fix.
I'm very sorry I couldn't be of more assistance.
chelce said:
In the hopes of finding a solution to a problem that is still
Any thoughts or suggestions? Mantano still hasn't gotten back to me, so as of right now I'm stalled.
Thanks!
Click to expand...
Click to collapse
Hello Chelce. Did you solve the problem? Did the guys at Mantano answer?
I have found the same problems as you.
I use Mantano PRO 2.2 in a rooted NST and PRO 2.5 on a number of other devices. I sync them all through Mantano Cloud (paid) service.
As long as I do not sync PDFs, there are no problems. But once a PDF creates a "faulty/unsyncable" entry into the highlights/notes DB, the NST will fail at syncing.
A pitty, since Mantano is hands down the best ebook service for academic work, where we"indulge" in extensive annotations, and where we need those notes to be easily stored, catalogued, and shared.
nicvel said:
Hello Chelce. Did you solve the problem? Did the guys at Mantano answer?
I have found the same problems as you.
I use Mantano PRO 2.2 in a rooted NST and PRO 2.5 on a number of other devices. I sync them all through Mantano Cloud (paid) service.
As long as I do not sync PDFs, there are no problems. But once a PDF creates a "faulty/unsyncable" entry into the highlights/notes DB, the NST will fail at syncing.
A pitty, since Mantano is hands down the best ebook service for academic work, where we"indulge" in extensive annotations, and where we need those notes to be easily stored, catalogued, and shared.
Click to expand...
Click to collapse
I'm going out on a limb here but I have one more thing for you to try. Similar problems have occurred recently with the Kindle app and have long been a problem with Google Books. User @tshoulihane tried updating the security certificates on the NST (some of which have expired) and that allowed both the Kindle and Google Books apps to connect properly and sync content. The thread is here. All I did was download his file and replace the original cacerts.bks (saved old one just in case). Then reboot.
I will add 'USERtrust' to my updated cacerts.bks - it occurs to me that it isn't just having root certificates expire on the nook that cause problems, some websites will potentially migrate their certification path over time. Not sure I can fit it in before Friday though...