It seems that B&N use your credit card as your unique identifier rather than your email or something else. Maybe I'm wrong, but they needed it verified just to ship me a charger that will fit into the damn thing.
I refused to put in my CC # to register the nook as I don't see why you need to have that kind of info in an ereader all the time. I mean what a hassle if the thing gets stolen.
Anyway I used one of those alias CC#'s to register, but it will expire in a month.
What happens when it does? I'll need to add something else to buy any books of course, but will I lose content I've already got?
danbutter said:
It seems that B&N use your credit card as your unique identifier rather than your email or something else. Maybe I'm wrong, but they needed it verified just to ship me a charger that will fit into the damn thing.
I refused to put in my CC # to register the nook as I don't see why you need to have that kind of info in an ereader all the time. I mean what a hassle if the thing gets stolen.
Anyway I used one of those alias CC#'s to register, but it will expire in a month.
What happens when it does? I'll need to add something else to buy any books of course, but will I lose content I've already got?
Click to expand...
Click to collapse
Pretty sure the CC is not stored or used in any way on the Nook Color, it's on the B&N Website.
In fact I did not register on my NC at all, I skipped it and did it at home. Then I logged in as that user on the NC, no credit card input etc.
danbutter said:
It seems that B&N use your credit card as your unique identifier rather than your email or something else. Maybe I'm wrong, but they needed it verified just to ship me a charger that will fit into the damn thing.
<snip>
Click to expand...
Click to collapse
B&N will register the device without a credit card (I did that )so if you have a CC# there that will 'expire' (assume it's a one time #) it will should not create a problem. Of course when you go to buy something you will need to supply a valid CC# at that time, just use another 'one time' #.
Also altho 'I feel your pain' about the microUSB, you are not alone.. it's a major problem for B&N and possibly the reason for the two week 'time out'. Cheers
Just an FYI, and kinda related, for recurring CC puchases, neither the vendor nor the purchaser has a credit card number stored on either system. The CC merchant (Sage, Trust Commerce, etc.) is the only one who does, and there is a GUID issued for that specific transaction and is tied to to the user account and vendor account combination, and cannot be used for anything other than transactions between those two parties.
A GUID does nothing for anybody who might hijack it. Thought it would be worth mentioning.
You will not lose access to any of your purchased content if the CC info on your account is modified. However, because each downloaded book is encrypted with a hash key generated using your name + CC#, you will need to delete the local copies of the files from your device and re-download a new copy of the book. The newly downloaded book will contain info associated with your new CC.
Thanks for all the replies. Every little bit of info helps!
Related
Hi there,
Ive just grabbed a Nook HD for my Mom for christmas, We got it running to discover all her prior purchased .mobi books will not work.. So I took it to factory, rooted etc did the OOBE bypass and discovered its called "TESTs Nook" now.. To cut a long story short.. How do I either change the user name or add another account as its just got a circle that spins for litterally hours (unless it restarts!)
Thanks
JackJack762 said:
Hi there,
Ive just grabbed a Nook HD for my Mom for christmas, We got it running to discover all her prior purchased .mobi books will not work.. So I took it to factory, rooted etc did the OOBE bypass and discovered its called "TESTs Nook" now.. To cut a long story short.. How do I either change the user name or add another account as its just got a circle that spins for litterally hours (unless it restarts!)
Thanks
Click to expand...
Click to collapse
You can't change the test name. And you can't add an account that has B&N access because the device is not registered. But I think you can just add a profile by tapping the test name at the top.
Sent from my HD+ rooted stock using Tapatalk
If you skip OOBE, you cannot change the Test's name. You also cannot create another profile, as you have explained, the waiting icon will just spin for hours, until the end of time, or when the battery dies out (whichever comes first).
If you'd like to change the Test's name, or create another profile, you need to register your Nook device. You cannot skip OOBE. I'm not too familiar with the Nook HD (I'm only accustomed to the HD+), but do you need to skip OOBE to root? If not, then go ahead register (remember the credentials, they are extremely important, you will not be able to register the device again without the same credentials) and then root. After that you can probably get a reader off Google Play which reads .mobi (of course, I'm sure that was your plan all along).
Best of luck, and unfortunately with skipping OOBE, you cannot create profiles or change TEST's name.
All the best.
Hi,
I was thinking about something.
1. know were chromecast gets the update file (url checking for updates)
2. redirect your modem so it goes to another server to get an updatefile
3. updatefile is a eureka file
4. let chromecast think its original and updates the CC with this file
Maybe you can just fool the CC to update from another url with a modified image.
This would be the easiest way to hack it.
Let me know if its possible
I think it won't be possible, because of firmware keys, and security. It will check if the firmware has a digital signature. But I'm not 100% sure about that.
At the least you'd need to match the Google signature before it would install... which is much harder than it sounds.
1024 bit key, so you've got to guess a password that's 128^256 or a hella bunch of potential passwords on the apk signature.
That also assumes that only the update file is signature checked - there might be some negotiation between the Chromecast and the mothership which involves other layers.
Basically with current computing capabilities and only a signature check you're probably looking at a minimum of a few years to crack the current signature unless I did the maths wrong.
mildlydisturbed said:
At the least you'd need to match the Google signature before it would install... which is much harder than it sounds.
1024 bit key, so you've got to guess a password that's 128^256 or a hella bunch of potential passwords on the apk signature.
That also assumes that only the update file is signature checked - there might be some negotiation between the Chromecast and the mothership which involves other layers.
Basically with current computing capabilities and only a signature check you're probably looking at a minimum of a few years to crack the current signature unless I did the maths wrong.
Click to expand...
Click to collapse
It's even worse than that!
It will only take updates over HTTPS which means you need to have a server running that has Google Security certificate or nothing happens!
..
Asphyx said:
It's even worse than that!
It will only take updates over HTTPS which means you need to have a server running that has Google Security certificate or nothing happens!
Click to expand...
Click to collapse
Ok, so to update with other fw is not possible.
Did somebody even checked this possebility?
phantmbox said:
Ok, so to update with other fw is not possible.
Did somebody even checked this possebility?
Click to expand...
Click to collapse
Yep!
The last exploit took advantage of a vulnerability in the USB startup that would allow you to create multiple USB Hubs and overflow the unit to put it back into a Factory Flash mode. Once there you could load up your own rom. This is why the Teensy was required to send commands to the CCast and break it's boot cycle.
Google Patched that rather quickly!
And once the device boots there are several more layers of protection including using the aforementioned HTTPS to ensure all updates are coming from google and only google.
If you folks really want root the best way to go is to buy a NIB unit and make sure you disconnect Internet access until you have successfully rooted and flashed Eureka.
Considering the low price $35 you can recoup some of that money by selling the one that updated to a friend or relative. Even Ebay I suppose but you probably won't get full price there.
And I would do it sooner rather than Later because at some point Google will start shipping Units with the unrootable ROM in it out of the box.
Then you will have to wait until (and hope) another Exploit is found.
Seriously s*cks how we (non US folk) are being treated like second rank citizens... but we won't let that stop us from getting our entertainment, will we
DISCLAIMER : I'm not responsible if your account gets banned, your gear vr goes up in smoke or your paid content is taken away at some point.
how to ...
1:
go to the play store and get the app HOLA
it's a VPN which will allow you to launch oculus home app as if you were in the USA
if you do it correctly, you will see all the paid apps
2: ***** APPARENTLY THIS STEP NOT REQUIRED .. ALL CC ACCEPTED *****
now you need a US based credit card ...
go to neteller.com, create an account
put some money in the account (many different payment methods)
choose to receive a 'Net+' card, basically a mastercard from Neteller
I have one, and even though I live in the Netherlands, it's accepted as a US card. (sometimes thats a problem, today its a blessing)
your card will come via snail mail in about 4-5 days
3:
in Oculus home, go to settings, add payment method
enter your CC details
they also want a state/city/zip ... just choose a US city and Google their zip codes.
This works 100% for me, however when you are not connected to the VPN your paid games and apps will not showup. And who knows, we are probably breaking TOS so they could potentially take the content away from you.
axewater said:
Seriously s*cks how we (non US folk) are being treated like second rank citizens... but we won't let that stop us from getting our entertainment, will we
DISCLAIMER : I'm not responsible if your account gets banned, your gear vr goes up in smoke or your paid content is taken away at some point.
how to ...
1:
go to the play store and get the app HOLA
it's a VPN which will allow you to launch oculus home app as if you were in the USA
if you do it correctly, you will see all the paid apps
2:
now you need a US based credit card ...
go to neteller.com, create an account
put some money in the account (many different payment methods)
choose to receive a 'Net+' card, basically a mastercard from Neteller
I have one, and even though I live in the Netherlands, it's accepted as a US card. (sometimes thats a problem, today its a blessing)
your card will come via snail mail in about 4-5 days
3:
in Oculus home, go to settings, add payment method
enter your CC details
they also want a state/city/zip ... just choose a US city and Google their zip codes.
This works 100% for me, however when you are not connected to the VPN your paid games and apps will not showup. And who knows, we are probably breaking TOS so they could potentially take the content away from you.
Click to expand...
Click to collapse
You dont seem to need to do step #2, just use a US IP and put your credit card in normally.
Link to Hola on Google Play:
https://play.google.com/store/apps/details?id=org.hola
Thanks for the guide mate!
Do you guys have checked app permissions of HOLA VPN? And do you feel confortable to use your credit card through a free VPN that ask you access to your identity, position, device ID, etc?
dalamario said:
Do you guys have checked app permissions of HOLA VPN? And do you feel confortable to use your credit card through a free VPN that ask you access to your identity, position, device ID, etc?
Click to expand...
Click to collapse
The folks at HOLA are not able to intercept the transaction, there is another layer of encryption. We are basically putting an SSL encrypted 'letter' into another encrypted VPN envelope... They can decrypt the VPN packets (and they must in order to forward them to the final destination) but not the SSL layer.
Although SSL is pretty broken, based on a broken trust model and broken code ... but in theory .. we should be ok.
HOLA can have all my identity info, device id, position ... have fun with it. They are providing me a valuable service for 'free'. I'm ok with that as long as they stay out of my bank account and dont steal my private pictures
Domen Lo said:
You dont seem to need to do step #2, just use a US IP and put your credit card in normally.
Click to expand...
Click to collapse
Can you let us know what kind of CC you used ? Is it a Canadian one ? .EU ? Asia ?
axewater said:
Can you let us know what kind of CC you used ? Is it a Canadian one ? .EU ? Asia ?
Click to expand...
Click to collapse
Eu card, works fine. Other continents work fine as well, judging from the posts on other forums.
Credit card companies are usually pretty good with customer protection against fraud so hopefully we should be ok
Sent from my SM-N910G using XDA Premium 4 mobile app
axewater said:
Seriously s*cks how we (non US folk) are being treated like second rank citizens... but we won't let that stop us from getting our entertainment, will we
DISCLAIMER : I'm not responsible if your account gets banned, your gear vr goes up in smoke or your paid content is taken away at some point.
how to ...
1:
go to the play store and get the app HOLA
it's a VPN which will allow you to launch oculus home app as if you were in the USA
if you do it correctly, you will see all the paid apps
2:
now you need a US based credit card ...
go to neteller.com, create an account
put some money in the account (many different payment methods)
choose to receive a 'Net+' card, basically a mastercard from Neteller
I have one, and even though I live in the Netherlands, it's accepted as a US card. (sometimes thats a problem, today its a blessing)
your card will come via snail mail in about 4-5 days
3:
in Oculus home, go to settings, add payment method
enter your CC details
they also want a state/city/zip ... just choose a US city and Google their zip codes.
This works 100% for me, however when you are not connected to the VPN your paid games and apps will not showup. And who knows, we are probably breaking TOS so they could potentially take the content away from you.
Click to expand...
Click to collapse
Can you teach me on how I can install BBC i-Player on my Android phone from the USA?
So UK owners can't use their credit cards for payments on the UK release devises?
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.
Hello,
With my former employer I had a phone that I used my Samsung account with, problem is that Samsung account is registered with the work phone number I had at the time, so I can no longer login to my account because of 2 factor authentification being enforced onto my account (without my consent).
To regain access to my Samsung account I need to have the phone's Serial Number, how can I get it? I don't have anything left from the phone, but I used it regularly with Google Account, Windows, "Your Phone" app, etc....
Can I get it through Windows registry, logs or some online webservice?
Regards,
Where it was bought... especially if it's was a carrier phone.
It was bought by the company which I no longer have contact with.
That's not data normally shared. I'm not a fan of most multitiered security as it always causes me problems.
Doesn't it show you a serial number in the phone information?
Otherwise try this app once. The serial number is also displayed under the Personal tab...
Phone INFO ★SAM★ - Apps on Google Play
All-in-one INFO and TOOLS for Samsung devices.
play.google.com
Roger.T said:
Doesn't it show you a serial number in the phone information?
Otherwise try this app once. The serial number is also displayed under the Personal tab...
Phone INFO ★SAM★ - Apps on Google Play
All-in-one INFO and TOOLS for Samsung devices.
play.google.com
Click to expand...
Click to collapse
she doesn't have the phone that she used to open the Samsung account anymore, that's how I'm reading it.
3mel said:
she doesn't have the phone that she used to open the Samsung account anymore, that's how I'm reading it.
Click to expand...
Click to collapse
Ah ok. I have probably misunderstood that...
Then I don't see any possibility...
Roger.T said:
Ah ok. I have probably misunderstood that...
Then I don't see any possibility...
Click to expand...
Click to collapse
I was gonna suggest yesterday that she bites the bullet and just rings her old employers and explains she's spent lots of money thru the account.
they'd probably say the phone has been scrapped by now, in that case back to Samsung and look for a contact us link.
she can't be the first person to face this scenario since they brought in 2FA. if she still has an email account attached that's something.
3mel said:
I was gonna suggest yesterday that she bites the bullet and just rings her old employers and explains she's spent lots of money thru the account.
they'd probably say the phone has been scrapped by now, in that case back to Samsung and look for a contact us link.
she can't be the first person to face this scenario since they brought in 2FA. if she still has an email account attached that's something.
Click to expand...
Click to collapse
Mmmmm, humble pie... or minced meat pie?