Related
Hi Everyone,
Ive been on a bit of a mission with T-mobile and have been in touch with the directors office, they are under the impression that nothing has been locked down on the phone in rc7/rc30 that would limit the use of the phone from a development standpoint.
Ive given them a few examples of things that cant be done but they refuse to do anything (other than cancel my contact if i want) as im only one person who is complaining.
I know everyone runnning rc30v1.2 and rc8v.12 is ok atm, but could EVERONE please send a little email of complaint. Just explaining that you are unhappy that they have locked down the phone and denied us root.
cl&[email protected]
They say that if they get more complaints then something will be done
ITS WORTH A SHOT ISNT IT?
PS... If anyone wants to cancel their contract in the uk because of the lack of access, call 01707 315000 and ask to talk to Leah within the Directors team about your G1 problem. I explained that i couldnt get my apps working because i couldnt edit/add files to system directories.
They should offer to cancel it, it worked for me
Yeah, it's worth a shot, although from past experience with T-Mobile this may be akin to trying to extract blood from a stone
I tried doing the same thing after I got my G1 (before anyone figured out the hole in RC29). I found the people over at T-Mobile USA are just as clueless. As soon as you mention the words Android or G1, they instantly transfer you to a different support queue. I tried to explain what root access was and they didn't have a clue what I was talking about.
I found that here in the UK also, these people work in the directors team and so far have not fobbed me off.
They dont claim to be technical but are at least talking to the T-mobile developers about this. They have raised my concerns with the UK G1 manager, i think my case just needs a little more oomph from others complaining.
I've already called HTC, G1 support, and the PDA/Smartphone support ppl. None of them were willing to even try to understand the issue.
T-mobile have just called me and have advised that we should expect a statement about the issue by the end of the week. The issue is now with board members apparently
Maybee they are actuclly starting to understand??
You should have them email. At least that way it leaves a paper trail.
SGTDavePwnage said:
T-mobile have just called me and have advised that we should expect a statement about the issue by the end of the week. The issue is now with board members apparently
Maybee they are actuclly starting to understand??
Click to expand...
Click to collapse
That's very interesting that T-Mobile is even considering the idea of allowing root access, to the point where it would be an executive decision by the board members. Do you have any other information on this aside from your first post? Can anyone else confirm this?
i phoned tmobile uk today and asked why i couldnt get root on my tc5-rc8.
and i had a long talk with the guy and he said he had a email about this issue
and went throught a few things with me on my phone. and then he said he would phone me back tomorrow with someone that new more about the g1 then the tec support staff. and he would be able to give me more answers about it.
qtronix
Cool
Sounds like my insessant *****ing at T-mobile support might have gotten us somewhere?
At least techies are not fobbing people off at the moment.
Could you please concider sending an email to the address i posted, just so they are aware that others are miffed.
******This is a copy of the email i sent to the directors team******
Leah
Many thanks for your call....
As t-mobile dont seem to see/understand the problem I have given the contact details of the director team to a group of developers so that you can hopefully get a few more calls about this. Please believe me that I am not the only person who has these concerns, but when people call tech support about this they are simply fobbed off by people who are not trained/do not understand the issue.
I would like to point out an error with t-mobiles response that they have in no way locked down the phone so that it is detremental for putting developed software onto the phone.
Please see a few examples of how the new RC8 Software limits Developers :-
1. Say I wanted my screen to automatically rotate without wanting to open the keyboard, this is simply a matter of editing offset: 1104724 within /system/framework/framework.odex to 0x0F001246.
I could do this on the old software but not on the new RC8
2. Say i wanted to update the web browser to do the same, this would mean editing the origional browser source code released by Google and putting it on my phone. Again, this was possible with root access on RC7 but has now been made impossible on the new RC8.
3. Say i wanted to make a tethering application that allows me to use my G1 as a modem to my PC (i know this would cost me money on my contract for data transfer) but I might want to do it so that i can connect to my workplace vpn to fix something. This was Doable on RC7, but now is not.
4. The G1 currently has no way of clearing cache for the marketplace, this again was doable on RC7 but not on RC8
5. The G1 has a limited ammount of space to install applications. It would be a good idea if we could install applications to our SD memory Cards, but again we cant do this because of the new software.
The above examples are just some simple things developers are working on that would benefit the phone, but we cant develop them and put them on the phone.
Basically anything that means editing a system file / writing a file to a system directory is now impossible.
Please understand that developers are not trying to take over the world or ruin the phone. We are simply trying to make the phone do what we want / improve the features.
This is how OpenSource works. Everyone has access to the Source code so that it can if neccecary be customised/edited to improve things for everyone.
The new software has made it impossible for programs that interact with the main system files or require extra files to be put in a system folder, to work.
Developers understand why the phone RC7 software was unsafe in the way it ran commands, we understand why you fixed the command running problem, but instead of fixing the issue properly you have just locked down root access?? Why??
If the new software in no way limits what developers can do, then why when you search on the net are so many people “Jailbreaking” their phones to get the access they require.
http://arstechnica.com/news.ars/post/20081105-android-liberation-t-mobile-g1-jailbroken.html
Can i draw your attention to
"In contrast, the G1 has been developed by the Open Handset Alliance project. It's extremely unlikely that this alliance, which is committed to an open platform, will engage in the same kinds of protective shenanigans that Apple has resorted to. The Android philosophy states that "anyone can contribute to Android and influence its direction. That means that anyone can download, build, and run the code needed to create a complete mobile device."
So why jailbreak an already-open device? One big jailbreak advantage is that it allows you to bypass the G1's internal storage. Until now, you were limited by the G1's built-in memory for installing and running programs. With the jailbreak, you can install applications onto a local SD card and run them from the card. Running low on memory? Just swap cards in and out.
Jailbreaking also allows you to use low-level tools that run in the background. Want your G1 to call home and report your location every 20 minutes? A simple Unix process, called a daemon, can handle that for you. You can set daemons up to remind you of appointments, to scan for nearby wireless devices and more. The world of handheld computing doesn't begin or end with graphic interfaces. There's an enormously rich world of possibilities available through command line processes.
Most importantly, jailbreaking gives you complete control of your system from the bottom up. It lets you stop thinking of your phone as a handheld gadget and start using it as a fully-capable Unix platform. "
Please could you explain how T-mobile are of the opinion that they have not limited developers with the above examples in mind.
The G1 is being sold as a Developer friendly OpenSource Phone. How can you claim this is developer friendly when the software severely limits what developers can do?
Are T-mobile saying that the phone was never supposed to allow users this access and that the RC7 root access was a mistake?
Eagerly Awaiting your response..
******
Well written, although I would have DEFINITELY left out the part about tethering the phone.
vr24 said:
Well written, although I would have DEFINITELY left out the part about tethering the phone.
Click to expand...
Click to collapse
I did think about that, but then i reconcidered as we already have tetherbot which works without root.
Suppose we will just have to see if anything comes of it
SGTDavePwnage said:
I did think about that, but then i reconcidered as we already have tetherbot which works without root.
Suppose we will just have to see if anything comes of it
Click to expand...
Click to collapse
you can always call t-mobile and say that after you updated the phone it is now:
constantly feezing, apps are running slow, and at times you can not connect to internet.
also tell them that you tried a factory reset and it did not help (make up a story that you have friend that has a lot of app and his phone runs faster than you phone with no apps installed)
if you have insurance they will send you one for free, you just have to return your old phone,
i believe they are still sending out rc29 for replacements as of now.
friend and cousin tried it and it worked.
might be worth a shot
Just got this in my inbox:
"Thank you for letting us know of your concerns with the 'open source' and 'root access' on your G1 mobile phone. We really do appreciate your comments about this.
We're aware that there are concerns in relation to this and our leadership teams in the UK and the USA are currently reviewing your comments and our position. We plan to provide you and other customers with similar concerns, with a response early next week, which should answer your concerns. I'll be in touch with you then.
Your comments are extremely valuable to us Mr * and I'm grateful for your patience while we look into this. I'd like to thank you personally for your co-operation.
In the mean time I hope you enjoy your weekend.
Kind regards
Leah Young
Directors' Office Co-ordinator
T-Mobile (UK)"
Of course, their answer could be anything from "f*ck off" to "yes, we'd love to embrace the openness of android with both arms, here everyone, have root!" so we'll all have to keep our fingers crossed 'til monday.
Well I just hope they release an update with options that allow us to turn off all background services (myfaves) and unwanted datatraffic (or actuall prevent overriding options when roaming).
How did that dead horse like the beating?
Perhaps a dead horse. Could it be that Tmo has now figured out that with root access, it won't take long for people like the coders at XDA to fully jailbreak the device to the point that voIP will be easy for any user to obtain? Are they just trying to protect their ability to profit off of voice traffic?
rynosaur said:
Perhaps a dead horse. Could it be that Tmo has now figured out that with root access, it won't take long for people like the coders at XDA to fully jailbreak the device to the point that voIP will be easy for any user to obtain? Are they just trying to protect their ability to profit off of voice traffic?
Click to expand...
Click to collapse
Hummm... I think ALL wireless providers are threatened by VOIP but the main reason root access was blocked was due to bad press mainly by tons of articles stating that there is a huge security risk and a flaw was found with Android which could let remote users attack someone's device...blah blah blah and so forth. That pretty much scared T-Mobile and Google which hated to have bad press so close to the G1 just being released and were forced to correct this issue. The only problem with that protection came with closing alot of freedom for the G1 and may happen to alot of more Android-based devices in the future, I'm afraid... Maybe Google will realize that there are other ways to protect mobile hijacking (which is extremely rare anyways) by creating some type of built-in firewall software instead?
rynosaur said:
Perhaps a dead horse. Could it be that Tmo has now figured out that with root access, it won't take long for people like the coders at XDA to fully jailbreak the device to the point that voIP will be easy for any user to obtain? Are they just trying to protect their ability to profit off of voice traffic?
Click to expand...
Click to collapse
Root is not necessary to build a voip app. Fact is, G1 launched with a skype-compatible voip app called iSkoot. Look it up.
SGTDavePwnage said:
Cool
Sounds like my insessant *****ing at T-mobile support might have gotten us somewhere?
At least techies are not fobbing people off at the moment.
Could you please concider sending an email to the address i posted, just so they are aware that others are miffed.
******This is a copy of the email i sent to the directors team******
Click to expand...
Click to collapse
i wont quote the entire email because its big. but you sir are very well spoken, great email!
http://review.cyanogenmod.com/#change,5677
This is an interesting patch to the CM7 repository frameworks base. If you scroll down and expand the comments you can follow the guys arguments on justifying such feature. Basically from what I understand this would allow you to spoof personal data to apps which may or may not request it. From contacts to SD card contents as well as phone IMEI (International Mobile Equipment Identity) number.
It's not a committed change but I wanted to see what the community thinks of having such feature. Personally I see all the reasons why this would open up a can of warms. What do you think?
I think in some other implementation this could be really helpful to the paranoid (like myself). However, I also think that those that are against it have VERY valid points. The community needs MORE widespread acceptance, not less, and something like this could cause major problems with Google, Carriers, Developers....
Sent from a bird cage, with a swing!
Correct me if I am wrong, but the intention is to spoof necessary data that an app might request that it doesn't actually need and to help prevent app force closes that straight up permission blocking causes. Like pandora requiring to read contact data.
Setting aside the other ramifications for a second... This is actually a good idea. It gives us power to not have to accept (for example) Pandora being greedy bastards.
Now the other ramifications are indeed severe. But for example, Swype. Why the hell can't I just buy it on the market?
I think arguing over it is a moot point. This cat is already out of the bag. We can't stuff it back in. This functionality is coming. Maybe not on Cyanogen, but it will be here for the masses soon. The greedy bastards that are trying to milk the system had just better deal with it.
Wow this thread could not have popped up at a worse time , what with all the NexusSense 0.3 users having trouble with their IMEI's.
But having read through all the comments on the change, i see why the CM team do not want to implement it, obviously this kind of change would piss off devs and carriers and of course google.
Yes it is a good idea for us users, but for CM's image and survivability , id say not having it is a sacrifice we need to make
First of all:
Wrong section.
Second: They won't add it anyway.
Some developers cried about it and everything.
dario3040 said:
First of all:
Wrong section.
Second: They won't add it anyway.
Some developers cried about it and everything.
Click to expand...
Click to collapse
I figured this is about a development of Android ROM and posted in "Android Development" section. Forgive me if there was a better place to post it in.
This is also not marked as abandoned (as of this post) and still up for debate in the open section of Cyanogenmod Gerrit section.
For devices without an IMEI because they don't have a cellular radio, such as the Nook Color, some amount of this is valid and regarded as highly valuable. While I don't condone being able to haphazardly change or spoof your IMEI, I do believe that for devices that don't have an IMEI that some measure should be taken to create a device specific IMEI that will persist between different ROMs and ROM installations. Unfortunately with no IMEI support for devices like the Nook Color, there is no persistent ID that can be used. As developers continue to use the IMEI as a "device stable" ID, we need to come up with a way to support devices that don't have such an ID, and perhaps generate a non-colliding IMEI from a has of their login information, or some other identifying metric that will persist between different installations. The TAC could be created to identify the device type, and then the serial number could be generated based upon some information provided by the user.
In short, outright spoofing is probably a bad idea, but something needs to be done for devices that don't supply these sorts of IDs.
hi all!
please note: i am nothing near a professional user or even coder! i rooted my phone and i install custom roms on it, and thats about it. in addition to that i am concerned about my privacy. for me it started with the LBE Privacy Guard from the play store, it was quite nice until it stopped working, and made my phone stuck in a boot loop...
i have read and searched a lot of stuff before i decided to write this. but i havent found an easy and understandable how to. maybe that is because there no easy way to this. please go easy on me if there is already a thread for this...
i just installed openpdroid on my samsung galaxy s+ (i9001) and that is just because user bululu has made a patch for the rom i am using (cm10.1 from user davidteri) - thanks to both of them! i installed the patch with cwm (clockworkmod) and afterwards i was wondering there is no privacy setting in my menu or anything that would let me set up permissions. but from all the stuff i was reading before i figured i will need some kind of gui (not sure this is the right word - that goes for most of the stuff, but please correct me where u can, i will try and learn) so i installed 'pdroid manager' from the play store. that would finally let me set permissions for the apps! so far, so good. i am now using openpdroid...
should be all good at this point u might think, but this is where my questions begin ^^ f.ex:
is this the best solution atm? are there more solutions? what are the differences? what can u recommend?
furthermore i try to figure out how to encrypt email on android. most things i read point to k9 mail and using agp (or apg? is this the same?). i did some research on that topic an it seems to be the 'android privacy guard'. more questions here too...
it seems to be out of development, since the last changes are from 25.12.2010. is there a newer alternative for that or something i missed? or maybe it is still the thing to use or it is quite finished in its current state?!? but i dont wanna clog my device with old or unsupported software until i am 99% sure on what to do...
so basically i am asking if there is a nice and user friendly (with images) 'how to' for this kind of stuff i was just missing or is it just impossible (at the current state) to do such thing? if both answers are 'no' i'd like to start something like that, of course with your help that is...
because it seems the info i found is not coherent, its all bits and pieces one needs to bring together (in the right order and with compatible software). at least thats what it feels like for me as non-professional user and linux noob. i have no problem with puzzling stuff together but i also would like to help others who would like to do increase their security and get different opinions on whats the best way to do some things...
so if any of u got an opinion to any of the above please let me know! and help or links would be greatly appreciated! lets see if we can bring some things together and make our devices, our communication and our data more secure! and please note: this should not be device specific, my device and rom was just for information and for better understanding my starting point. this should be as broadly defined and open minded as possible. so everybody could partake and make use of it...
thanks for reading!
kind regards
bad1080
Hi,
I want to know if i encrypt my Galaxy S7, if it's possible to remove lock screen with dr.fone toolkit ?
If it's possible it's bad because password it's for restrict any person to access to phone !
Thank for any help !
Hi,
Up !
Do you know the answer ? Please ?
Thank !
azer7 said:
Hi,
Up !
Do you know the answer ? Please ?
Thank !
Click to expand...
Click to collapse
Hello,
The Galaxy S7 has multiple variants and builds. Normally when asking this kind of question, you should include the model of your device. That way anyone wanting to help you actually has the knowledge to be able to do so. Phones have different internal parts, memory space, and so on. You can find your model number by doing the following:
- slide down the notification bar, sometimes you may have to slide down twice depending on the device. Click the gear in the upper right hand corner. "Settings"
OR
- Access your app drawer or all apps section and find your "settings" section/app. Most of the time it will have a icon of a gear, or three lines that resemble on off switches. Older androids sometimes use just have three lines (as the settings icon)
- Find the section labeled "About Device / Device Info" its usually labeled something similar if not exactly. Open this section
(Galaxy phones usually have this section at the bottom of your "settings" section)
- Somewhere within this section, there will be a label that reads "Model" and that is your specific variant which is needed in device specific situations.
* Take Note of this for future reference. You might think okay ill remember that. But when you come to realize your devices model number may be XDA-2017T1 and you look for something pertaining your device. You will also find something like this:
XDA-2017
XDA-2017YP
XDA-2017YP2
XDA-2017T0
XDA-2017T2
XDA-2017T10
Assuming that you will continually update and/or customize your phone. You will probably just memorize this, along with other important information. Some important things you should include while researching is as follows (the top two are very important)
1. [Model Number] ex) XDA-2017T1
2. [Android Version] ex) 6.0.1 Marshmallow
3. [Baseband]
4. [Kernel]
5. [Chipset]
6. Is device "rooted?"
7. Is the bootloader unlocked?
8. GSM or CDMA. Older devices even use IDEN
Those are only some.
* I also want you to know that im not trying to lecture you, or give you a hard time. I am honestly trying to help you and in order to successfully help you I have to ensure that you know things, or mention things, that is important to do. So your device isnt broken, or you get information that is correct but incorrect for your specific device.
But back to the topic originally referenced.
Q) "Is the program Dr. Fone able to bypass the screen lock security measures on the Samsung Galaxy S7?"
A) Based on limited information that is device specific, and the current Supported Devices section from Dr Fones documentation
"No"
• Dr. Fone doesnt have the capabilty to bypass your screen lock. They will probably include the S7 within a period of time due to it being a main stream phone though.
• Remember this; locks can and will be broken. Just because a vulnerabilty hasnt been exposed or discovered doesnt mean that its 100% secure.
• Keep current with OTA updates, keep in tune with tech type news.
• Encryption is vast subject, but I can refer to it like the "invisible magical ink" That was popular in the 90's. The light that reveals the ink to the naked eye, is your password. The inabilty to see the ink normally without a specific tool, would be encryption. So if someone cracked your password, your encryption would also be disabled. I linked more information below, for you to read. I still dont fully understand encryption myself, nor do I believe or trust it.
I based this information assuming your device is the SM-G930. It is accurate as possible but not guaranteed. Do realize with the information I mentioned and with the question you asked. I was able to do a simple Google search and almost immediately found the answers. Try to figure things out before you ask in the future. You can repeat the process of not researching prior to posting but typically your post will die. If you get stuck and have put forth honest effort, the great people here at XDA will probably help out greatly. I hope I have helped you, and you now feel better about your concerns. please pay it foward.
If you feel ive helped or gave a honest attempt to help. Hit the thumbs up, that is the thanks button.
-juzten
▪Information on Android Encryption▪
https://source.android.com/security/encryption/full-disk
▪Samsung S7 Model Numbers ▪
https://www.google.com/amp/techbeasts.com/list-of-samsung-galaxy-s7-s7-edge-model-numbers/amp/
▪Dr. Fone's Supported Devices, Screen Lock ▪
https://drfone.wondershare.com/reference/android-lock-screen-removal.html
.
.
.
.
.
[☆☆☆] I TAKE NO CREDIT, AND GIVE THANKS TO THE PEOPLE WHO WROTE AND/OR RESEARCHED THE ABOVE REFERENCES. THESE REFERENCES ARE THE RESOURCES I USED TO CONCLUDE AN ACCURATE RESPONSE TO THE QUESTION ASKED IN THE OP. NO CLAIM IS MEANT TO BE IMPLIED, OR IS GIVEN WITH THE INFORMATION PRESENTED AS FACTUAL. AS WITH ALL DOCUMENTATION, ERRORS ARE MADE OCCASSIONALLY AND YOU SHOULD FURTHER RESEARCH ANY DOUBT. I TAKE NO RESPONSIBILTY FOR ANY DAMAGE OR LOSS THAT OCCURED IN DIRECT RELATION TO MY STATEMENTS MADE. [☆☆☆]
Hi,
juzten said:
Hello,
The Galaxy S7 has multiple variants and builds. Normally when asking this kind of question, you should include the model of your device. That way anyone wanting to help you actually has the knowledge to be able to do so. Phones have different internal parts, memory space, and so on. You can find your model number by doing the following:
Click to expand...
Click to collapse
I'm sorry, I completely forgot to mention the model of my S7, it is the SM-G930F on Android 6.0.1 Marshmallow, thanks for answering me.
On the other hand, I'm disappointed that a commercial program can unlock a phone.
I hope that this way of circumventing the locking of smartphones will be solved, because malicious people could use it to unlock phones that do not belong to them ...
The only way to protect yourself from this program is to install an application that protects personal data.
Thank you again for answering!
Wondershare Dr. Fonefor unlooking thr screen.
Wondershare Dr. Fone is a powerful instrument to regain iPhone lost information, it can help scan and recover them from iTunes or iCloud copies in case you've got backup your iPhone into iTunes or iCloud, or it helps you regain contacts directly from the device. Besides it's harmonious with iPhone 5s/5c/4S/ / 4/3GS and it might recover 18 kinds of content such as pictures, videos, contacts, messages, notes, and phone log, voicemail, voice memos, calendars, reminders, etc.. :good:
I agree with you. A commercial program available for a few dollars can unlock a password protected phone. What is Android/ios waiting to solve this threat?
Does anyone know how to know how to circumvent a device ban on android? Clearing cache, deleting app, deleting app history does not work. They are placing a device ban for this particular app on the phone.
Any recommendations or advice appreciated.
Thank you.
They who. What app
Tinder
Maybe "They" think it is not appropriate. Any other app being blocked? When blocked does it give you some info/message
Am just trying to figure out how to circumvent a device ban. Have been researching xprivacy and things like this but have not quite figure out how they are linking the device. Even a factory reset doesn’t work.
If a factory reset didn't fix it I'd wonder if your phone is even legal? That pretty much has to be the IMEI is banned AFAIK.
Did you buy it from a legit source?
Laser422 said:
Am just trying to figure out how to circumvent a device ban. Have been researching xprivacy and things like this but have not quite figure out how they are linking the device. Even a factory reset doesn’t work.
Click to expand...
Click to collapse
Probably IMEI based. That's what other apps like Snapchat have used for handing out device bans. You can't circumvent it if its IMEI based unless you know how to mask it or spoof it. The app may also look for additional things like the MAC address and IP address in combination.
enigmaamit said:
Probably IMEI based. That's what other apps like Snapchat have used for handing out device bans. You can't circumvent it if its IMEI based unless you know how to mask it or spoof it. The app may also look for additional things like the MAC address and IP address in combination.
Click to expand...
Click to collapse
Yeah, I would imagine it is IMEI based.
Any recommendations on how to spoof it?
Thanks
Laser422 said:
Yeah, I would imagine it is IMEI based.
Any recommendations on how to spoof it?
Thanks
Click to expand...
Click to collapse
I doubt XDA would take kindly to people advising how to conceal IMEI.
Journyman16 said:
I doubt XDA would take kindly to people advising how to conceal IMEI.
Click to expand...
Click to collapse
Hello and good afternoon, @Journyman16
Just for your information: We do not allow discussions of or support for the change or edit of IMEI's. But we accept if the discussion is about the restoration or repair of the original IMEI. And we also allow spoofing or masking of IMEI as long as it's done on sofware level and the actual, original IMEI isn't tampered with. Spoofing of IMEI's is mainly used out of privacy concerns; however, if such talks deviate to illegal purposes we'd highly appreciate a report.
Regards
Oswald Boelcke
Senior Moderator
Oswald Boelcke said:
Hello and good afternoon, @Journyman16
Just for your information: We do not allow discussions of or support for the change or edit of IMEI's. But we accept if the discussion is about the restoration or repair of the original IMEI. And we also allow spoofing or masking of IMEI as long as it's done on sofware level and the actual, original IMEI isn't tampered with. Spoofing of IMEI's is mainly used out of privacy concerns; however, if such talks deviate to illegal purposes we'd highly appreciate a report.
Regards
Oswald Boelcke
Senior Moderator
CC: @Badger50
Click to expand...
Click to collapse
Thanks for clarifying Oswald. I didn't know how it might be seen by XDA. TBH I didn't really know what a 'device ban' is having only heard of IMEI's being banned after the phone being stolen.
Laser422 said:
Yeah, I would imagine it is IMEI based.
Any recommendations on how to spoof it?
Thanks
Click to expand...
Click to collapse
There used to be some ways to do that (with root) on older android versions, but i've never needed to try anything like this personally.
I believe there are xposed modules purpose built for obfuscating IMEI, MAC address and IP address, to disallow apps from identifying devices, like xprivacy, but again, I don't think these work on newer versions of Android.
You can try, but going by my current knowledge (on newer android versions), the only recourse you have is to get a new device (and preferably use a different account) to log into the app in question if it really matters to you.
Journyman16 said:
TBH I didn't really know what a 'device ban' is having only heard of IMEI's being banned after the phone being stolen.
Click to expand...
Click to collapse
There are many apps that use "device ban" in addition to "account ban". They usually create a device ID in their database which is based on IMEI, MAC address and IP addresses, and can deny access to their services based on one or more of these identifiers.
Game companies do this all the time, and social media companies like SnapChat and TikTok also employ similar banning techniques. And over the years, it's getting damn near impossible to circumvent these bans. Upto Android 6, you could just provide fake device identifiers to the app with xposed modules and mess around with them but with all the exploits being patched, it is no longer that easy on a software level now.
Thanks for the response
We have tried xprivacy and haven’t had much luck. I’m trying to figure out what the next step is
In these forums the people aren’t experienced enough because this is really getting hard/technical, you’re looking in the wrong place sorry to tell you
Kekleroni said:
In these forums the people aren’t experienced enough because this is really getting hard/technical, you’re looking in the wrong place sorry to tell you
Click to expand...
Click to collapse
There are many knowledgeable people on this forum, but with how large this site is, we can't all see everything. Comments like yours don't help, and I'd like to point you to Rule 10:
10. Help others if you can.
If you see posts from others where you can help out, please do so. This place exists because people are helping each other, and even if you are relatively new to the matter, there's probably quite a few people with less experience than you, who could benefit from what you've learned. Don't be shy.
Click to expand...
Click to collapse
If you have nothing constructive and helpful to say, it is probably better to say nothing.
@Laser422 What do you mean by "device ban"? Are you saying that the Play Store won't let you install the app? Can you provide screenshots? What make and model is your phone, and what OS version are you running? Is your bootloader unlocked and are you rooted?
Do this:
Go to Play Store. Tap profile icon upper right. Tap Settings.
Expand About section. Do you see "Play Protect certification - Device is certified"?
V0latyle said:
@Laser422 What do you mean by "device ban"? Are you saying that the Play Store won't let you install the app? Can you provide screenshots? What make and model is your phone, and what OS version are you running? Is your bootloader unlocked and are you rooted?
Do this:
Go to Play Store. Tap profile icon upper right. Tap Settings.
Expand About section. Do you see "Play Protect certification - Device is certified"?
Click to expand...
Click to collapse
It's most likely an account ban. Tinder probably thought he was catfishing. Or somebody reported him.
Terms of Use
With 43 billion matches to date, Tinder® is the world’s most popular dating app, making it the place to meet new people.
policies.tinder.com
gernerttl said:
It's most likely an account ban. Tinder probably thought he was catfishing. Or somebody reported him.
Terms of Use
With 43 billion matches to date, Tinder® is the world’s most popular dating app, making it the place to meet new people.
policies.tinder.com
Click to expand...
Click to collapse
That wouldn't prevent him from installing the app. He just wouldn't be able to log in.
Or using a company phone with policy in place only allowing some apps