Forgive my ignorance, but ive never used android before and expecting my phone delivered tomorrow (htc hero! )
As i understand it, the android app store signs the apps similar to iphones itunes store to prevent piracy and malware.
Is this correct?
Ive read about how one can "root" the device by loading a image file thru the bootloader over usb, but i wonder, is there a sudo command or similar to temporarily enable root access and later return to default state?
I suppose i could flash it with the root image, install the app and then flash back the default os image, but that feels pretty awkward procedure and would probably raise a bunch of new problems as how the default os would launch the app installed under another os.
I was hoping to start tinkering with programming, but im unsure if i can "throw in the app" and expect it to work..?
After using mac´s for over 20 years ive become too used to stuff just working right out of the box, so i dont feel like experimenting on my own...
There is an option in the settings that lets you install unsigned apps, so no rooting required.
xarvox said:
As i understand it, the android app store signs the apps similar to iphones itunes store to prevent piracy and malware.
Is this correct?
Click to expand...
Click to collapse
Not exactly! Many paid apps are copy protected, but most of the free ones are not. Unlike the iPhone, where you can only install "unauthorized" apps if you jail break the device, Android allows you to install and run applications from a variety of sources on a stock device.
In essence, you do not need to root the device to develop for it, but there are certain things that applications can only be done on a rooted device (for example, receiving a file via Bluetooth, WiFi tethering etc).
I was hoping to start tinkering with programming, but im unsure if i can "throw in the app" and expect it to work..?
Click to expand...
Click to collapse
Well, programming errors aside ( ), and as long as you don't need to do anything that requires root privileges, yes you can. You should bear in mind that the *vast* majority of Android devices will not have been rooted, and therefore the vast majority of available applications do not require rooted phones.
Personally, I expect that later Android builds will remove many of the restrictions that require applications to have root access, so that they can function without requiring a device to be rooted.
Regards,
Dave
Ive found a app that would tether my laptop (mac) over wifi, but requires me to root the device.
Is there a way to temporarily do this, install the app and make the neccisary changes and then switch back to default state?
I don't believe so.
As far as I'm aware, the application requires the elevated privileges when it runs as opposed to just configuration changes. I don't think that even a setuid would help, since I believe the app expects to find and use su/sudo.
Regards,
Dave
Hi,
So I was always under the impression that rooting is more dangerous because it lets applications more access to the system and let it perform more actions. However, now that I think about it can't this be handeled by a program that limits permissions?
Or do apps in a rooted phone behave differently than in an unrooted one (ie.can do actions not included in the permission system)?
What about an unrooted phone?
If I install a spyware what information can't it gather that it can on a rooted?
Thank you very much!
oy-ster said:
Hi,
So I was always under the impression that rooting is more dangerous because it lets applications more access to the system and let it perform more actions. However, now that I think about it can't this be handeled by a program that limits permissions?
Or do apps in a rooted phone behave differently than in an unrooted one (ie.can do actions not included in the permission system)?
What about an unrooted phone?
If I install a spyware what information can't it gather that it can on a rooted?
Thank you very much!
Click to expand...
Click to collapse
http://www.lockergnome.com/android/2013/01/25/how-safe-is-rooting-android-devices/
http://google.about.com/od/socialtoolsfromgoogle/a/root-android-decision.htm
http://www.bullguard.com/bullguard-...ity/mobile-threats/android-rooting-risks.aspx
Thank you for the links, I have alredy enconutered some of them previously (I usually Google before posting ) and they are part of my confusion.
On one hand: http://www.bullguard.com/bullguard-...ity/mobile-threats/android-rooting-risks.aspx says about apps with root access circumvent the security system, on the other: http://google.about.com/od/socialtoolsfromgoogle/a/root-android-decision.htm notes that you can control this access, so why does first warning exists?
Also, do superuser apps can detect every element and limit it accessability? For example, what about malicious code that I recieve from clicking on some pernicious link?
PS. When one of the pages said: "A common practice that people do with "rooted" phones is to flash their ROM's with custom programs." - it meant custom OS/ROM or did it mean the program you are using in order to perform flashing?
Thank you.
upity up.
MOD EDIT @gregbradley WARNING. King root sends your IMEI number to an IP address in China. Only use this method if you are OK with this. You have been warned
Pls remove this thread.
I removed Kingroot and flash supersu instead because that is the most important trick in this tutorial but ppl seems to believe what they choose to believe…
Reserved
Enough said.
Remove remove
There are reports that king root sends IMEI /your personal information to some chinese servers..
It is not safe i think...Please check xda before trying this . Now that you have tried use the app for few days and monitor it ..and please report back if there is any suspicious activity by the app.
Video ?!!!
Video Guidance incomplete
Were you asked to remove your much easier way to root, or did you take it down just out of spite?
Am I to expect nothing more from you in the way of efforts to help people like me root, who simply don't understand WTF anybody else here is even talking about?
I simply need to know, that's all. I'm frustrated because obtaining root seems so close and yet completely out of reach.
AddictedToGlass said:
Were you asked to remove your much easier way to root, or did you take it down just out of spite?
Am I to expect nothing more from you in the way of efforts to help people like me root, who simply don't understand WTF anybody else here is even talking about?
I simply need to know, that's all. I'm frustrated because obtaining root seems so close and yet completely out of reach.
Click to expand...
Click to collapse
He was not asked to remove it. XDA allows the mention of this root method as long as the warning about information being sent to an IP address in china is mentioned as well.
XDA Rule 17
17. Apps that collect identifying details
We don't routinely remove Apps that collect identifying numbers or other personal and device identifiers.
However, should an App, developed by you, be identified as one that maliciously performs this activity (e.g. by not disclosing it to the user), it will be removed from the site and possible sanctions applied;
Click to expand...
Click to collapse
Just google king root and use it. The info here was just about which buttons to press.
1) use king root
2) install recovery
3) Flash SuperSU.zip and remove kingroot.
Done
WARNING. King root sends your IMEI number to an IP address in China. Only use this method if you are OK with this. You have been warned
Thread closed at OP request
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.
Redmi 4x satoni(not rooted or flashed)
Is there any way to detect root by exploit, apps like Kingo root and king root and many other one click root apps do this kind of thing where they use and exploit in the Android system and root the phone using it and similarly a malware can do the same?
(I'm assuming this is what it is)(spear phishing)
Can an apk file really gain root access and rewrite your device's rom with a malware in it, is that a thing?
I have installed a third party app where it just disappeared into the background(most likely social engineering) and I tried all avs but it came clean even went into safe mode and settings and tried app managers and settings but all failed
Next I tried the factory reset and the symptoms still persists
Note that I have created new accounts and changed passwords and have MFA on but is there any way for it to reinfect because I'm using the same device to create the new account?
Like is it because it infected my google access or something to come again after factory reset
Thanks
If you think a girlfriend virus is bad, just wait until you get married.
To answer your question....
Android is designed to be very rootkit-resistant. Features such as Verified Boot prevent unsigned/modified images from loading if the bootloader is locked; while it is possible for a malicious app to use an unpatched exploit to root the device every time it runs, any modificaiton made to any critical partiion such as /boot and /system would be detected, and the device would warn the user that the system is corrupted.
Since you've removed the app from your device and performed a factory reset, you should be safe. Good job on using MFA, by the way.
V0latyle said:
If you think a girlfriend virus is bad, just wait until you get married.
To answer your question....
Android is designed to be very rootkit-resistant. Features such as Verified Boot prevent unsigned/modified images from loading if the bootloader is locked; while it is possible for a malicious app to use an unpatched exploit to root the device every time it runs, any modificaiton made to any critical partiion such as /boot and /system would be detected, and the device would warn the user that the system is corrupted.
Since you've removed the app from your device and performed a factory reset, you should be safe. Good job on using MFA, by the way.
V0latyle said:
If you think a girlfriend virus is bad, just wait until you get married.
To answer your question....
Android is designed to be very rootkit-resistant. Features such as Verified Boot prevent unsigned/modified images from loading if the bootloader is locked; while it is possible for a malicious app to use an unpatched exploit to root the device every time it runs, any modificaiton made to any critical partiion such as /boot and /system would be detected, and the device would warn the user that the system is corrupted.
Since you've removed the app from your device and performed a factory reset, you should be safe. Good job on using MFA, by the way.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
No I think I misunderstood there were two apps that I downloaded one disappeared into the back ground (which is causing more havoc) and is undetectable by android avs and i m having trouble removing(got from a sketchy link from my gf)
The second app was just an Instagram app follower which ran in the background and I could uninstall directly(got from playstore)
I want to know how to detect and remove the first one
alokmfmf said:
got from a sketchy link from my gf
Click to expand...
Click to collapse
That's why one should always use protection.
alokmfmf said:
The second app was just an Instagram app follower which ran in the background and I could uninstall directly(got from playstore)
I want to know how to detect and remove the first one
Click to expand...
Click to collapse
What makes you think the first app is still there? If you've performed a factory reset, it's gone - unless it downloaded again when you restored your Google account to your device.
Are you sure you're not mistaking a built-in app?
alokmfmf said:
Is there any way to detect root
Click to expand...
Click to collapse
Yes, almost every banking / payment app does it.
V0latyle said:
That's why one should always use protection.
What makes you think the first app is still there? If you've performed a factory reset, it's gone - unless it downloaded again when you restored your Google account to your device.
Are you sure you're not mistaking a built-in app?
Click to expand...
Click to collapse
Yes I'm sure as my accounts getting hacked my personal media getting leaked permissions asked repeatedly and sim getting disabled
Also I'm trying not to log in to my google account and see how that works
Although I have tried to make new accounts from scatch and start from a clean new slate from factory reset it it may be the device itself I'm afraid
Social engineering-spear phishing(I think)
Redmi4x satoni
I was asked to click on a link and download an apk by my girlfriend and as soon as I downloaded it, it disappeared and I was asked to delete the apk
(I do not have access to the link also)
Later I realized that it tracks permissions, media and keyboard(except of exactly who I'm texting to because of android sandbox)
I tried FACTORY RESET but the symptoms still persisted (like getting hacked again and my private info getting leaked,sim deduction and detection of sim card and permissions being asked again and again even though I allowed it)
I checked all the settings of my phone and nothing is abnormal(I'm not rooted)
Is it possible that a used account could somehow transmit virus because I had a nasty malware on my phone so I factory reset my phone but the symptoms still remain so I used a new google account and others also but it still comes back so I'm guessing its the kernel or the ROM that got infected
I tried all avs but they all came clean and I'm certain that my android is infected with something
First and foremost I need to know how to DETECT the malware (to know which app is causing this)
And second how to REMOVE the malware
Thanks.
Which OS version? If not running on Pie or higher it's suspectable to the Xhelper family of partition worming malware
Yeah sounds like you got a worm... nasty critters.
A reflash may be the best option although if it is Xhelper it can now be removed without a reflash.
You are what you load
blackhawk said:
Which OS version? If not running on Pie or higher it's suspectable to the Xhelper family of partition worming malware
Yeah sounds like you got a worm... nasty critters.
A reflash may be the best option although if it is Xhelper it can now be removed without a reflash.
You are what you load
Click to expand...
Click to collapse
Yes I know I made a stupid decision its completely my fault I tried using the xhelper method but it comes clean I assume there is only one method that involves disabling the play store
I run on miui 11 nougat 7
Any methods to detect and remove the malware are welcome
And about reflashing its very complicated for mi phones most
alokmfmf said:
I run on miui 11 nougat 7
Any methods to detect and remove the malware are welcome
And about reflashing its very complicated for mi phones most
Click to expand...
Click to collapse
Reflash it to stock firmware. If you can upgrade to Android 9 consider doing so for security purposes. It may have performance/functionality drawbacks though for your application though, not sure as I never used 6,7 or 8.
Make sure you reset all passwords, keep social media, sales and trash apps off the phone. Always keep email in the cloud ie Gmail or such.
Run Karma Firewall. Be careful what you download and especially install... don't sample apps unless you have a real need for that particular app. Once installed don't allow apps to update as they may try to download their malware payload, a way to bypass Playstore security.
blackhawk said:
Reflash it to stock firmware. If you can upgrade to Android 9 consider doing so for security purposes. It may have performance/functionality drawbacks though for your application though, not sure as I never used 6,7 or 8.
Make sure you reset all passwords, keep social media, sales and trash apps off the phone. Always keep email in the cloud ie Gmail or such.
Run Karma Firewall. Be careful what you download and especially install... don't sample apps unless you have a real need for that particular app. Once installed don't allow apps to update as they may try to download their malware payload, a way to bypass Playstore security.
Click to expand...
Click to collapse
Will not logging in my google account help
alokmfmf said:
Will not logging in my google account help
Click to expand...
Click to collapse
No. The malware is in the phone apparently in the firmware.
blackhawk said:
No. The malware is in the phone apparently in the firmware.
Click to expand...
Click to collapse
I disagree, unless Xiaomi/Redmi's AVB/dm-verity implementation is useless, it should prevent a persistent rootkit.
I suspect this has little to do with the phone and more to do with reused passwords and other "organic" security failure.
V0latyle said:
I disagree, unless Xiaomi/Redmi's AVB/dm-verity implementation is useless, it should prevent a persistent rootkit.
I suspect this has little to do with the phone and more to do with reused passwords and other "organic" security failure.
Click to expand...
Click to collapse
You're probably right. Forgot it was running 11... lol, organic security failure, I like that
blackhawk said:
You're probably right. Forgot it was running 11... lol, organic security failure, I like that
Click to expand...
Click to collapse
The security measures that prevent persistent rootkits have been in place long before Android 11.
The most common root cause of a breach of security is the failure to ensure sufficient security in the first place. Simple passwords, reused passwords, no MFA, connected accounts, etc. Yes, there are plenty of Android viruses out there, but all of them "live" in the user data space. Of course, there may be unpatched exploits that allow root access, but these must be exploited every time the app is run. An app cannot modify the boot or system partitions without tripping AVB (if the bootloader is locked) whereupon the device would warn that the OS is corrupted.
At the end of the day, it's much much easier to simply use social engineering or other methods to gain someone's credentials, rather than trying to hack their device.
V0latyle said:
The security measures that prevent persistent rootkits have been in place long before Android 11.
Click to expand...
Click to collapse
Yeah Android 9 was where the hole for the Xhelper class of rootkits was plugged for good. It runs securely unless you do stupid things. This phone is running on that and its current load will be 3 yo in June. No malware in all that time in spite of the fact it's heavily used. It can be very resistant to attacks if set up and used correctly.
V0latyle said:
The most common root cause of a breach of security is the failure to ensure sufficient security in the first place. Simple passwords, reused passwords, no MFA, connected accounts, etc. Yes, there are plenty of Android viruses out there, but all of them "live" in the user data space. Of course, there may be unpatched exploits that allow root access, but these must be exploited every time the app is run. An app cannot modify the boot or system partitions without tripping AVB (if the bootloader is locked) whereupon the device would warn that the OS is corrupted.
Click to expand...
Click to collapse
I was initially thinking his was running on Android 8 or lower. Forgot On Android 9 and higher (except for a big hole in Android 11 and 12 that was patched if memory serves me correctly) about the only way malware is getting into the user data partition is if the user installs it, doesn't use appropriate builtin settings safeguards or by an infected USB device. Any phone can be hacked if the attacker is sophisticated and determined enough to do so... in my opinion. Even if this happens a factory reset will purge it on a stock phone unless the hacker has access to the firmware by remote or physical access. Never allow remote access to anyone...
V0latyle said:
At the end of the day, it's much much easier to simply use social engineering or other methods to gain someone's credentials, rather than trying to hack their device.
Click to expand...
Click to collapse
Lol, that's what social media is for
blackhawk said:
No. The malware is in the phone apparently in the firmware.
Click to expand...
Click to collapse
OK thanks for helping its been good
alokmfmf said:
OK thanks for helping its been good
Click to expand...
Click to collapse
You're welcome.
I retract that (post #12) as I forgot it is running on Android 11. Like V0latyl said it's probably the password(s) that were compromised if a factory reset didn't resolve the issue other than the exceptions I stated in post #16.
Also i found this on the net if that helps with the situation
Be especially wary of spear phishing. Do not click on any weird link sent by your closest friends, or if you feel compelled to do so, open it from a tightly secured operating system (a fresh VM) where you have never logged in to your social networks.
And
Factory resets are not enough to santitize the device.
Also I'm a bit scared as some people on the net have told that in some cases that even a flash might not wipe it as it resides in the boot logo or some places where flashes do not reach or in flash ROMs chips(but of course this is all very rare)
I am very fascinated and would like to learn more about it any suggestions would be helpful