My Honor 5x has been hacked and has somehow gotten a RAT (Remote Administration Tool) or something related installed on it. The user of the tool has tried taking my information but hasn't gotten any (as far as I know). I have tried everything I could think of to fix this, yet nothing has worked.
Things I have tried:
1.) Resetting - I have reset my phone 8 times now, it has not helped at all.
2.) Flashing new ROM - I have flashed my phone twice, I thought this would have worked, it didn't. I flashed the stock rom from huawei itself, and locally installed the update to get it to Android 6.0.1
3.) Hard resetting - Basically the same as a reset, has done nothing.
Info:
* Huawei Honor 5x - KIW-L24
* Running Android 6.0.1 / EMUI 4.0 (was 4.1, but after resets and flash, was 4.0)
How can I get rid of this? It seems to be installed somewhere where it can't be uninstalled, I've looked through system processes and everything, nothing looks out of the normal.
You gotta be more specific than that..... Like why you think you have rat and how did the hacker tried to take your info
Related
Google has issued a brand new Android 5.1.1 Factory Image file that should patch the StageFright Security bug forever. If you want to install a clean Lollipop OS on your tablet, then you should check all the info listed in this post.
The StageFright Security bug should’ve been fixed with the previous LMY48I Android 5.1.1 release, but that didn’t happen as tons of Nexus 10 users have reported that the security vulnerability was still there. If you want to be sure that this bug is fixed, then you should flash the latest LMY48M firmware version of Android 5.1.1 Lollipop OS on your tablet.
Installing a factory image on your will always remove all the data from your tablet and you should create backups before starting the flashing process. Read the following guidelines first:
use this post only with the Google Nexus 10 tablets.
– don’t try to update any other different tablets with the files that you will find in this post.
by installing this Android 5.1.1 LMY48M factory image you should know that the flashing process will remove all data from it.
– however, if your tablet is running a stock Android 5.1.1 LMY48I build that hasn’t been modified in any way, then you can use a small workaround in order to avoid the ‘factory reset’.
– more info on the update workaround can be found when you reach the tutorial instructions.
backup all the important files before starting the installation process.
enable USB Debugging for your tablet from its Developer Options menu.
– if you can’t find Developer Options under Settings menu, then you should enable it first: go to Settings> About Phone and tap 7 times on the Build Number section.
– return to Settings, scroll down, open Developer Options and find the USB Debugging option in order to enable it.
use this post only if you are an advanced user.
we cannot be blamed in case you end up losing any data in the process nor in case you brick your device.
check your Nexus 10 battery charge level and make sure that it is over 40%, it will prevent your device from powering down during installation.
read the whole tutorial and make sure that you won’t be skipping any steps, so that you will be able to complete the factory image installation at your first attempt.
I've used three different browsers to read this page in case I have some sort of content blocker active, and I see no tutorial in any of them...?
It's always nice to see people trying to help, and notifications of new ROMs are always welcome (though I installed LMY48M weeks ago), but there are already hundreds of tutorials showing how to upgrade a ROM - maybe you decided not to go ahead with the rest of your post?
With latest update 5.1.1 LMY48T my tablet powering OFF randomly. I had naver this issue before on 5.0.2 (( This update is piece of crap in my opinion
Amiga4ever123 said:
With latest update 5.1.1 LMY48T my tablet powering OFF randomly. I had naver this issue before on 5.0.2 (( This update is piece of crap in my opinion
Click to expand...
Click to collapse
I've had the same problem, plus now I have battery issues. The tablet won't fully charge and will randomly turn off after some unknown time of use.
This update has killed my battery.
Beware of this update!!!!!!!!!!!!!!!!!!!!!!!!!!!! IT TOTALLY SCREWS YOUR NEXUS 10!!!!!!!!!!!!!! I´m reverting back to LMY47V because the newer updates are bricking my Nexus 10! I have flashed and reinstalled it 10 times by now, it just can´t handle this update! I think they did it for you to buy a new Nexus device by killing the Nexus 10!
maw said:
Beware of this update!!!!!!!!!!!!!!!!!!!!!!!!!!!! IT TOTALLY SCREWS YOUR NEXUS 10!!!!!!!!!!!!!! I´m reverting back to LMY47V because the newer updates are bricking my Nexus 10! I have flashed and reinstalled it 10 times by now, it just can´t handle this update! I think they did it for you to buy a new Nexus device by killing the Nexus 10!
Click to expand...
Click to collapse
Are you referring to build lmy48m or lmy48t?
I can't get to flash anything. Even after flashing another version, the old version just stays. I've tried everything. Formatting, erasing, downgrading, nothing works. I think my Nexus 10 is officially dead. It will boot up and like 1 minute after it just crashes and reboots again. I have read that others have this problem, could be that the motherboard is shot. Since there are no motherboards available, I can't even repair it. It lasted exactly 2 years, what a waste!
Well I just spent hours going through all the ota update from original jelly bean that it came with up to the latest lollipop build lmy48t and everything is working fine thus far.
The 5.0.1 Android unrooted tablet was sent to a service lab, where it came back from having its motherboard replaced, when for some reason its OS was downgraded to Android 4.4.4. Since then some apps do not work, such as TV apps (that worked fine before) - the tab cannot play movies and shows on those apps, although those apps are supposed to work on Android 4.3 and so on. Moreover, since then I cannot update my OS, tab saying that I have the latest version (which is obviously not true) and when going to the Tool Kit saying that "An error has encountered when installing the recommended incremental update pack". Factory Data Reset did not do anything. According to the Root Checker, the device was not rooted, although it seems to me that the lab has messed with my OS. What do you think? The lab says though that my OS is "beyond their control" and that they could not have touched it, just replaced the motherboard with an original one, suggesting me "just to wait" for the update to come out, which I am sure will never happen. Any suggestions how to solve this? Do you think that the lab has messed with my OS or what do you think happened here? Thanks a lot, guys!
Can anyone answer that?
Can anyone answer that please?
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
Hi people, I don't know where to ask anymore. Sorry in advance for my english.
I have a serious problem with my P9 Lite VNS L21. It is no brand, as far as I know.
Everything started when I updated to EMUI 5.0 Android 7.0. (I know nothing about this stuff)
I started to have some bugs like: I couldn't turn on bluetooth, I couldn't open settings cause they always crash, and stuff like this.
So what I decided to do, hope I can turn back, was to install a custom ROM.
What I found was the Lineage 14, but the EliteKernel was required. And so on, I flashed it.
After that, bugs were becoming more and more annoying: I didn't even have the keyboard anymore.
So I did a factory reset.
Than, I was in an infinite loop in the first Wizard Setup. It was always restarting after I logged in into my google account and whatever I would press between Inizitialize a new phone or Restore from backup, it always went back.
After, I downloaded a new firmware to restore everything back and now.. nothing works. Always in black screen, I can't go into recovery, I can't fastboot, I can't even use dload.
I tried to remove battery and put it back, but it didn't work.
Sorry for the wall of text but I thought it was better to explain everything.
Thanks in advance.