Got an unlocked dual-SIM XCover Pro and it's completely unlocked and factory-reset (no passwords, etc. anywhere) and it has no "business" name applied to the work profile and both profiles, personal and work, appear to be fully accessible.
Does the dormant work profile imply any risks? Is there any way to know if the (maybe?) original corporate owner could automatically reset the phone, or otherwise mess with it?
Maybe it's never been part of a Samsung/Knox corporate environment and has never been registered (can you tell?)
Thoughts?
Related
G'day all XDA'ers. I got my phone from eXpansys unlocked just a week or so ago. This is not my first Windows phone but my first WP7 device for sure. I have been using the forums and the wiki to get my Focus up and rocking.
All is going well except full data service. No i know it sounds odd but data service is "kinda" working. By that i mean that i can get my corporate Exchange email ok and for some reason m.cnn.com will come in ok. For a local newspaper site it will render about 1/4 of the main page and thats it and Fark i will get a logo. All other sites fail in either stock IE or Browser+. Its trying.......just not succeeding. Looks like GMail and Hotmail can't sync over this borked celldata connection either - company Exchange only.
Last phone was a Blackberry and verified with the carrier that no flags or anything needed to be changed on their end. I verified with the *#7465625# that all locks are disabled. Most annoying is that i popped my SIM into my gf's iPhone and everything works fine.....and it was unlocked and she is with a different carrier.
I put on Samsung's Network Profile tool but i don't have any other network profiles to select. Auto config is on.
Not sure where else to look. Calls work, SMS works, MMS isn't supported on my carrier so didn't test. I really thought i had it figured out until the iPhone test worked.
For reference carrier is M3 Wireless Bermuda but to keep it interesting my liveID is registered to Canada.
Thoughts?
Also i got the Device Info app from Marketplace and see i am getting an IP and it is from my carrier's range. And though i should add that APN settings have been triple checked.
The Network Selection type is manual with carrier network selected and roaming is enabled.
And as an update the Hotmail did eventually update.......no word on the GMail
Little more detail
This might be a carrier limitation......maybe. I noticed that when i popped my gf's SIM into my phone i see a Digicel network profile now in Samsung's tool. Even after swapping out my M3 SIM the Digicel profile is still there - no M3 profile loaded/created. I need to get the data service on my gf's phone reactivated for a test but there might be something here.
Again....a small handful of sites work and Exchange and Hotmail works. I can't see the rhyme or reason of it. Google.com mostly loads (no logo) but detects my gmail account....but m.google.com won't work. Mobile version of bermudasun works but not other paper. m.cnn.com is groovy but not m.youtube.com.
will post back with more detail. Wish i could see what the carrier proxy or dns information was......
I am an Exchange 2003 admin at a company with over 500 devices using ActiveSync across multiple platforms and revisions.
We enabled ActiveSync policies this week, forcing a 4 character password down to the device, with the setting "wipe after x failed password attempts" disabled.
Within 48 hours, 3 users have reported their Samsung Fascinates (and one US Cellular Samsung Mesmerize - which appears to be the same CDMA Galaxy S variant) have randomly reverted to stock. The user was not doing anything in particular at the time, nor did they enter their PIN incorrectly.
Does anyone know if Verizon has acknowledged this issue, or plans to provide a fix? It feels wrong having to ask these users to go buy Touchdown, when every other Android phone works out of the box.
My guess would be that it's an issue with 2.1 not really the fact that it's a galaxy s.
2.2 has better support for exchange AS. Depending on the trust you can place on the user I'd suggest creating a new policy for them that doesn't require the pin but request that they use the pin, until the Galaxy S gets froyo.
I'll do a nandroid backup on my phone and enable the policy for my phone and see if it happens to me, I'm not running the stock kernel though so it could be different for me.
Unfortunately we can't do per-device polices with exchange 2003 without some trickery on a users extended AD attributes. And, since there's no way to identify Fascinate users, they report their AS user agent as 'android', so it's difficult to be proactive until they call in with the problem.
I don't think it's related to all galaxy s variants, plenty of Epic and TMobile Galaxy users are fine, but the US Cellular variant appears to be a direct copy of the Fascinate, also on 2.1update1, and exhibits the same symptoms.
Users are lying. They fat fingered the password or the screen came on in their pocket. I work IT in a company that has about 5k android devices and about 20k of iphone bb and windows phones. The exchange admin is a android enthusiast and we talk often, when they started enforcing wipe policy they were swamped by calls about devices wiping themselves but after users got used to entering the passcode the calls pretty much stopped.
Sent from my SCH-I500 using XDA App
Except we don't set that as part of the policy, as stated in the OP. I can mess up my PIN an unlimited amount of times with no ill effect.
There are threads about this on androidforums as well as the vzw forum, but I can't link with my low post count. I just wanted to come to the place where I knew there was the most knowledge with this issue.
Hmm, I have not specifically tested this, so I don't know if Samsung added this functionality or not, but the stock mail client for Android 2.1, to the best of my knowledge, does not support PIN code passwords. That functionality was added into Froyo by Google. I suppose it's entirely possible that the mail client on the Fascinate is buggy and causing this issue.
I know what you mean about having to tell them to pay for a mail app, but I think they'll be happy about it after the fact, after seeing how much better Touchdown really is. The stock mail client is so bare-bones, it's honestly quite ridiculous. Google really needs to get their act in gear and code a decent, full-featured mail client, because right now the iPhone beats Android at Exchange syncing, even though it also can't hold a candle to Touchdown.
Trying to understand where the security/lock sit:
1) If the digcert was in the device then bootloader, kernel, or both, can be tied to a device, and then protected from change. Is that the case?
2) If the digcert was in either the bootloader or the kernel , they can be tied to one another, but then , if both were changed at the same time, security couldn't be enforced.
3) Any digcert has to be validated vs. a matching digcert. Those can exist at Samsung, at ATT, or both. In fact, from descriptions in other threads, they seem to be present at certain Best Buy stores, at least temporarily.
4) If '3' is correct (ANDIF '1' is not correct), then all that is need to circumvent the lock is again, a dual change to bootloader and kernel, or am I missing something?
5) If '3' is correct, it seems that part of the public-private key may sit at ATT and at VZW. While those two parts couldI] be different, the infrastructure to manage this would be more cumbersome then I give them credit to manage. Therefore, it would be a logical (yet WAG) assumption that VZW and ATT either
(a) rely on the Samsung master certificate and/or(b) have the same certificate as each other. Is there a way to test this 'b' theory?
Bump
flyboy43 said:
Trying to understand where the security/lock sit:
1) If the digcert was in the device then bootloader, kernel, or both, can be tied to a device, and then protected from change. Is that the case?
2) If the digcert was in either the bootloader or the kernel , they can be tied to one another, but then , if both were changed at the same time, security couldn't be enforced.
3) Any digcert has to be validated vs. a matching digcert. Those can exist at Samsung, at ATT, or both. In fact, from descriptions in other threads, they seem to be present at certain Best Buy stores, at least temporarily.
4) If '3' is correct (ANDIF '1' is not correct), then all that is need to circumvent the lock is again, a dual change to bootloader and kernel, or am I missing something?
5) If '3' is correct, it seems that part of the public-private key may sit at ATT and at VZW. While those two parts couldI] be different, the infrastructure to manage this would be more cumbersome then I give them credit to manage. Therefore, it would be a logical (yet WAG) assumption that VZW and ATT either
(a) rely on the Samsung master certificate and/or(b) have the same certificate as each other. Is there a way to test this 'b' theory?
Click to expand...
Click to collapse
Bump
flyboy43 said:
Trying to understand where the security/lock sit:
1) If the digcert was in the device then bootloader, kernel, or both, can be tied to a device, and then protected from change. Is that the case?
2) If the digcert was in either the bootloader or the kernel , they can be tied to one another, but then , if both were changed at the same time, security couldn't be enforced.
3) Any digcert has to be validated vs. a matching digcert. Those can exist at Samsung, at ATT, or both. In fact, from descriptions in other threads, they seem to be present at certain Best Buy stores, at least temporarily.
4) If '3' is correct (ANDIF '1' is not correct), then all that is need to circumvent the lock is again, a dual change to bootloader and kernel, or am I missing something?
5) If '3' is correct, it seems that part of the public-private key may sit at ATT and at VZW. While those two parts couldI] be different, the infrastructure to manage this would be more cumbersome then I give them credit to manage. Therefore, it would be a logical (yet WAG) assumption that VZW and ATT either
(a) rely on the Samsung master certificate and/or(b) have the same certificate as each other. Is there a way to test this 'b' theory?
Click to expand...
Click to collapse
I recommend you take this to one of the bootloader discussion threads, the one in the Verizon S4 General section titled "If we are serious about unlocking this bootloader" or something like that seems to be more active. However, I can tell you that number 4 is incorrect on your list. ODIN packages flash bootloaders and kernels, but there is a counter on the phone that prevents older bootloaders and kernels from being flashed.
Hi All,
Please help. I'm a rookie at rooting and have an unlocked Japanese Note 3 through AU (my Japanese service provider). I was in a rush and paid someone to unlock it before heading back to the States last year. The phone works with my AT&T sim card but when I am back in Japan (with Japanese sim) I am constantly being dropped from the network. 4G service usually works for internet, etc, but I cannot make/receive phone calls and only occasionally can send/receive text messages. I need to know if I should re-root the phone (and leave it rooted) or just do a factory reset (or perhaps change some other setting to get things working again)? The problem with a factory reset is that it will probably re-lock the phone and I don't have a code.
Strange Detail:
Whenever I try to dial a number, the name of a Chinese Province shows up under the Contact's Name. This suggested to me some network issue where the phone somehow thinks it's in China (though texts still kinda work...) and doesn't connect correctly to the Japanese network.
Details:
Model: sm-N900J (per the download screen) i believe this means it has a SnapDragon Processor
Knox warranty has been tripped (apparently by the guy I paid to unlock it originally - is that bad?)
Android 4.3 (looks like I'm still in the original version of Jellybean. Should I upgrade to Kitkat or Lollipop?)
Other Issues:
As of two days ago, the phone now restarts after about 5 minutes of use. Like many Note 3 phones, it's always done the occasional random restart (another reason to root?) but now it's making the phone almost unusable. Also, since having the phone rooted/unlocked/re-rooted I always get a series of warnings upon start-up. Typically, standard Samsung apps like S Planner, Calendar Storage, Keyguard and Index Service have stopped. I have never been able to use the Calendar (or other basic apps) since it always crashes. Is this an issue with Knox clashing with something from the original root (I still see SuperSU loaded -but "turned off"- in the apps menu)?
Idealy...
...someone can help me decide the best course of action (Root, Reset, Other), and how to make sure I can connect back up to my Japanese network properly. I think I'd prefer to root since what I want is an unlocked phone that works smoothly, with good battery life, little to no bloatware, a custom theme and a working S pen. If I root, what's the best method (already have SuperSU apparently) and which ROM and version of Android would be the most stable?
Main Issues Recap:
No connection to phone network (or limited 4G internet).
Phone restarts every few minutes.
Many Apps crash upon Start-up.
Thanks in advance!
So, here's an update that someone with a similar problem might find useful...
Japan uses CDMA for voice and GSM for LTE Data. Somehow (probably through using my phone in the states on a GSM network) the phone was no longer connecting to the CDMA network. Since I'd gotten no responses and felt like there was a good chance that a factory reset would not reverse the sim-unlock I'd stupidly paid to have done, I did a factory reset. Despite appearing to have solved my Index Service, Calendar Storage, S Planner crashing issues, I was still having the exact same problem of LTE working but no CDMA network.
Somehow I stumbled on to this website...(well, I'm unable to post as a new user but searching for "How To Fix Samsung Galaxy error while searching for network" should bring it up).
There, I found some really odd directions that solve network error issues. The only part of the instructions I was really able to carry out was take out the battery and simultaneously press the home and power buttons 10 times. I restarted my phone and miraculously was able to place a call for the first time in a year in Japan!
But then I no longer had any data. I figured it had to do with the APN settings being wiped in the strange reset I just tried. But when I went into Settings>More Networks>Mobile Networks there was no longer an Access Point Names option in the menu. There is no longer a "Network Mode" option either. I used to have that set to LTE/WCDMA/GSM but now I only see a System Select option that simply lets me change my CDMA roaming mode from Automatic to Home Only.
I tried searching everywhere for the missing Access Point Names menu to no avail (and almost attempted to try flashing CyanogenMod for the time hoping this would bring back the APN settings menu) but then I realized that I could do a search in the settings app. I searched APN and the option came right up (though it's frustrating that this now appears to be hidden). Using the following settings (copied below) from the AU by KDDI website I created a new APN profile. Now mobile date appears to be working just fine too!
So, now I just need to decide if I want to keep running Touchwiz in Jellybean or use my new found confidence to try rooting and custom roms...
I'm also kind of curious to see that the next phone bill comes in as expected and I'm not being charged for a bunch of crazy usage! Also, any suggestions to help explain how I got into this problem in the first place, or how to clean up any loose ends would be appreciated.
APN Setting for LTE NET for DATA
APN name au.au-net.ne.jp
User name [email protected]
Password au
Authentication type CHAP
It started when some scumbag stole my bag which contained my old phone (s5) and wallet etc
My phone had a dodgy battery, smashed screen and inactive sim.
I only had it with me as it still connected to wifi so was a back up if I needed internet.
I'm particularly worried that I had screenshot of bank statements and various other sensitive documents as well as passwords for email etc stored in my notes.
I had a fingerprint lock screen set up as well as a password on private mode (I'm pretty sure I stored some passwords etc in private but not all)
As soon as i realised I called my network and had it blacklisted I then tried to do a remote wipe via device manager but although it showed the handset on the account there wasn't a remote wipe function.
I then changed my passwords for everything I remember having including my Google device manager account.
Unfortunately there was videos/photos of my kids that weren't back up which breaks my heart:crying:
So my main questions are.......
What is the most likely thing a criminal would do with the phone?
Factory reset then sell abroad? Change imei number?
How difficult would it be to hack into the phone to get my data?
Would all of that be too much effort considering the value of the model?
Finally is there any way samsung can wipe the phone for me?
Thanks so much for any help
much love