Kaspersky detects trojans, but is unable to neutralize them. Would you have a solution to propose me? In attachment you have a screenshot.
The full references are:
Model: Energizer Energy400
Android version: 4.4.2
Kernel version: 3.4.67
Build number: APLS.KK1.MP7.V1
Custom build version: Energy400_FR_4.4_B047_HW1_8GB_V03_201604130900
Hardware version: V1.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To get rid off of Trojans/Virusses do a Factory Reset.
jwoegerbauer said:
To get rid off of Trojans/Virusses do a Factory Reset.
Click to expand...
Click to collapse
The factory reset didn't work, there are still trojans in the filesystem (I did Vol Up + Power On, then selected factory reset)
Any other idea than the factory reset? The infected files seem to be deep in the filesystem.
Also, I tried to towelroot the device but it didn't work
thomasbb said:
Any other idea than the factory reset? The infected files seem to be deep in the filesystem.
Also, I tried to towelroot the device but it didn't work
Click to expand...
Click to collapse
Re-flash Stock ROM.
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Here is what I found:
Flashtool: https://www.getdroidtips.com/flash-stock-firmware-using-sp-flash-tool/
Energy500 firmware: http://www.mediafire.com/file/14igk2ma27qa385/Energizer_Energy_S500_MT6735M_V005_20161219.zip/file
My phone is an Energy400, would it be ok (no way to find an Energy400 firmware...)? My computer runs under Linux but I guess it works the same: run Flashtool, burn the "scatter" file, and this is it?
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Also, I tried this: https://www.droidthunder.com/unlock-bootloader/
but the terminal is frost saying: < waiting for any device >
All the commands worked until fastboot oem unlock and fastboot flashing unlock though
Re-flashing phone's Stock ROM is done by means of ADB:
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
jwoegerbauer said:
Re-flashing phone's Stock ROM is done by means of ADB:
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
In my case, it gives:
Code:
adb devices
adb reboot sideload
adb sideload Energizer_Energy_S500_MT6735M_V005_20161219.zip
then? Tomorrow I'll try, if it's not the right file to be used, please stop me before that time.
thomasbb said:
In my case, it gives:
Code:
adb devices
adb reboot sideload
adb sideload Energizer_Energy_S500_MT6735M_V005_20161219.zip
then? Tomorrow I'll try, if it's not the right file to be used, please stop me before that time.
Click to expand...
Click to collapse
It's not an update.zip and not for your device.
Try disabling them... maybe it's possible.
CXZa said:
Try disabling them... maybe it's possible.
Click to expand...
Click to collapse
How could I root my device to try to remove the trojans with adb? Thank you for your time though
Regarding the firmware, I asked one to Energizer and they answered they're dealing with my request
thomasbb said:
How could I root my device to try to remove the trojans with adb? Thank you for your time though
Regarding the firmware, I asked one to Energizer and they answered they're dealing with my request
Click to expand...
Click to collapse
For disabling you don't need root.
adb shell pm disable-user --user 0 <package_name>
@thomasbb
try this
App Freezer for Android - APK Download
Download App Freezer apk 1.0.6 for Android. Freeze unwanted app or package on Android (Samsung, Sony, Xiaomi, Huawei, etc)
apkpure.com
what is more convenient than individually disabling packages via ADB, IMO
CXZa said:
For disabling you don't need root.
adb shell pm disable-user --user 0 <package_name>
Click to expand...
Click to collapse
ADB says:
Code:
~/Android/Sdk/platform-tools > ./adb shell pm disable-user --user 0 /system/app/DeskClock.apk
java.lang.IllegalArgumentException: Unknown component: /system/app/DeskClock.apk
at android.os.Parcel.readException(Parcel.java:1476)
at android.os.Parcel.readException(Parcel.java:1426)
at android.content.pm.IPackageManager$Stub$Proxy.setComponentEnabledSetting(IPackageManager.java:2963)
at com.android.commands.pm.Pm.runSetEnabledSetting(Pm.java:1271)
at com.android.commands.pm.Pm.run(Pm.java:141)
at com.android.commands.pm.Pm.main(Pm.java:79)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:243)
at dalvik.system.NativeStart.main(Native Method)
jwoegerbauer said:
@thomasbb
try this
App Freezer for Android - APK Download
Download App Freezer apk 1.0.6 for Android. Freeze unwanted app or package on Android (Samsung, Sony, Xiaomi, Huawei, etc)
apkpure.com
what is more convenient than individually disabling packages via ADB, IMO
Click to expand...
Click to collapse
The application is installed. As soon the ads start to pour, I'll track down the apps that just reinstalled and freeze them. Thank you for you help
Related
how to enable adb shell in recovery mode?
when i try "adb shell" in recovery mode,it says sh not find somthing
does this means can't use adb in recovery mode?
i want trace recovery bin by ida pro,sames i have 2 chose:
1,enable adb shell and gdb server in recovery mode
2,or run recovery bin in normal mode.
the 1st,cant open adb shell
the 2nd got segment error in sh
please help!
<robin> said:
how to enable adb shell in recovery mode?
when i try "adb shell" in recovery mode,it says sh not find somthing
does this means can't use adb in recovery mode?
i want trace recovery bin by ida pro,sames i have 2 chose:
1,enable adb shell and gdb server in recovery mode
2,or run recovery bin in normal mode.
the 1st,cant open adb shell
the 2nd got segment error in sh
please help!
Click to expand...
Click to collapse
Release 5a recovery?? I get error: closed
Drivers are good aye?
Stifilz
no,i'm at 3.2.1
how to open adb shell?
<robin> said:
no,i'm at 3.2.1
how to open adb shell?
Click to expand...
Click to collapse
Wtf. Normally just adb shell. Does adb pull or adb push work etc?
<robin> said:
how to enable adb shell in recovery mode?
when i try "adb shell" in recovery mode,it says sh not find somthing
does this means can't use adb in recovery mode?
i want trace recovery bin by ida pro,sames i have 2 chose:
1,enable adb shell and gdb server in recovery mode
2,or run recovery bin in normal mode.
the 1st,cant open adb shell
the 2nd got segment error in sh
please help!
Click to expand...
Click to collapse
hi robin,
1. change region to US,
2. download this hacked_recov,
3. run recovery, update with this file, should finish with error 7,
4. wait one minute, and adb should be available - make sure that you have installed adb drivers for recovery device.
5. when in adb shell type this:
Code:
/system/bin/tempsu
PATH=$PATH:/system/bin:/system/xbin
and you will get root, and normally working with all the commands shell.
br
condi
wow,thanks candi!
your tool is real cooooool
i can trace recovery now!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
getting prohibit update as a result of checking version or base
condi said:
hi robin,
1. change region to US,
2. download this hacked_recov,
3. run recovery, update with this file, should finish with error 7,
4. wait one minute, and adb should be available - make sure that you have installed adb drivers for recovery device.
5. when in adb shell type this:
Code:
/system/bin/tempsu
PATH=$PATH:/system/bin:/system/xbin
and you will get root, and normally working with all the commands shell.
br
condi
Click to expand...
Click to collapse
So I've been at this for days now. From what I can read here and on the web it looks like my region file is screwed up. Tried a million different region zips.
I can get device to show in adb as recovery.
Any thoughts?
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
khaytsus said:
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
Click to expand...
Click to collapse
Ok cool i just made this guide for all the people who are affected by this bug myself included
Xmaster24 said:
Ok cool i just made this guide for all the people who are affected by this bug myself included
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well add 5 more guys I got 3 thanks here and another two on another help request
Fantastic!! Thank you. I have been pulling my hair out trying to figure out why my watch was all of a sudden "unauthorized" after updating. to 6.0.1
Guys just realised the whole cause of this when I flashed everything stock for the new update. It turns out that the actual cause of the problem was invisiblek's kernel and not the new system itself. sorry for any inconvenience this may have caused you.
(deleted)
New script
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Xmaster24 said:
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Click to expand...
Click to collapse
Thanks a bunch! Will be sure to give you credit on the thread.
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
GohanBurner said:
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
Click to expand...
Click to collapse
Make sure you have the adb driver installed, fastboot uses a separate driver and it does not require authentication either
KevinX8 said:
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Click to expand...
Click to collapse
i knew it has something to do with adbkey
In order to get the oreo mulitasking, i have uninstalled the EMUI launcher by ADB command :
Code:
adb shell pm uninstall -k --user 0 com.huawei.android.launcher
Is there any way to reinstall the launcher to system?
Ways to solve:
1. Change the Huawei app gallery to China and search "華為桌面”, it will be installed as system app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first way is to perform a full reset of the phone. Not ideal.
I saw mention in another thread a while back that it can be downloaded from the Chinese version of the Huawei app store if you change your location and search for it in Chinese.
If you're rooted you could use ADB to push the APK.
I think they're your only options. It would have been better to disable it rather than uninstall as you could enable it again.
can someone who has uninstalled the launcher do a quick check for me?
please install the newest pixe launcher or 1 of the newest pie launchers and set the navbar to the keys (no gestures), give the new launcher all permissens that it wants and reboot.
i would like to know if the new nav gestures and recents overview will kick in and work
If you have kept a copy (apk) before uninstalling it, you could just install it back.
Here is how you can extract it:
Code:
adb shell pm path com.huawei.android.launcher -- show the path to the APK
adb shell cp /path/to/apk/from/above /storage/emulated/0/Download/base.apk -- copy it to Download folder on device
adb pull /storage/emulated/0/Download/base.apk -- copy it to PC
Is it possible to copy base.apk from any custom ROM and install it?
henexekrar said:
If you have kept a copy (apk) before uninstalling it, you could just install it back.
Here is how you can extract it:
Click to expand...
Click to collapse
hoe where you planning on pushing it back?
demon2112 said:
hoe where you planning on pushing it back?
Click to expand...
Click to collapse
Not sure what you mean. You could install it the same way as any other APKs.
henexekrar said:
Not sure what you mean. You could install it the same way as any other APKs.
Click to expand...
Click to collapse
you are right hahah
henexekrar said:
Not sure what you mean. You could install it the same way as any other APKs.
Click to expand...
Click to collapse
Unsuccessful. Can't install .apk [emoji849]
Отправлено с моего LYA-L29 через Tapatalk
Li-Pol said:
Unsuccessful. Can't install .apk [emoji849]
Отправлено с моего LYA-L29 через Tapatalk
Click to expand...
Click to collapse
Then I have no clue, works on chinese rom. But that's also meaningless on chinese rom since app store has it..
henexekrar said:
If you have kept a copy (apk) before uninstalling it, you could just install it back.
Here is how you can extract it:
Code:
adb shell pm path com.huawei.android.launcher -- show the path to the APK
adb shell cp /path/to/apk/from/above /storage/emulated/0/Download/base.apk -- copy it to Download folder on device
adb pull /storage/emulated/0/Download/base.apk -- copy it to PC
Click to expand...
Click to collapse
I did extract the APK before I uninstalled it, but I can install the APK afterwards..
I can only conclude that launcher app is installed differently on international rom vs chinese rom, unfortunatrly I dont have a chance to get my hands on an international rom to see how that's like.
Guys, you can always try to change the country to china on Hisuite and search for the launcher is Chinese - it is mentioned in another post and see if you can get it installed.
Sent from my LYA-L29 using Tapatalk
kinli1234 said:
In order to get the oreo mulitasking, i have uninstalled the EMUI launcher by ADB command :
Code:
adb shell pm uninstall -k --user 0 com.huawei.android.launcher
Is there any way to reinstall the launcher to system?
Click to expand...
Click to collapse
Found this on another thread - in an adb shell type the following:
cmd package install-existing <package-name>
Just tried it with powergenie and it works. Give it a go if you still need to.
Grondah said:
Found this on another thread - in an adb shell type the following:
cmd package install-existing <package-name>
Just tried it with powergenie and it works. Give it a go if you still need to.
Click to expand...
Click to collapse
Confirmed, works! :good:
Grondah said:
Found this on another thread - in an adb shell type the following:
cmd package install-existing <package-name>
Just tried it with powergenie and it works. Give it a go if you still need to.
Click to expand...
Click to collapse
I need to reinstall the emui launcher on my Al00 where i removed it with adb. Can you tell me the exact package name for my version and if I have any chance to restore it? I am not rooted btw
afico said:
I need to reinstall the emui launcher on my Al00 where i removed it with adb. Can you tell me the exact package name for my version and if I have any chance to restore it? I am not rooted btw
Click to expand...
Click to collapse
The EMUI launcher is called com.huawei.android.launcher and you should be able to fine.
it works!!! great!
now it owuld be nice to rmoeve yellow pages and chianese huawei video
Install Application Inspector then you can get the package names for everything.
install: adb shell pm install-existing com.huawei.android.launcher
Hello friends
I uninstalled the com.android.documentsui package with adb a few days ago
And I really got into trouble
How can I reinstall it?
I have to say that I found the apk file on the Internet, but when I use
Code:
pm install --user 0 android.documentsui-7.0.apk
, I get this error:
Code:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.android.documentsui signatures do not match the previously installed version; ignoring!]
Can anyone help me? Or say goodbye to document?
ciger7 said:
Can anyone help me? Or say goodbye to document?
Click to expand...
Click to collapse
I'm not an expert so I don't know if this will help, but Occam's Razor says that you can switch OUT of adb to install & uninstall, and then, after you get out of this locked-up situation, you can try adb again later.
You didn't mention so I need to ask a basic debugging question:
QUESTION:
Did you try to uninstall directly from the phone (without using adb) and then try to install directly on the phone (again, without adb)?
If so, do you get any errors and if so, are they the same or different than what you get using adb?
GalaxyA325G said:
I'm not an expert so I don't know if this will help, but Occam's Razor says that you can switch OUT of adb to install & uninstall, and then, after you get out of this locked-up situation, you can try adb again later.
You didn't mention so I need to ask a basic debugging question:
QUESTION:
Did you try to uninstall directly from the phone (without using adb) and then try to install directly on the phone (again, without adb)?
If so, do you get any errors and if so, are they the same or different than what you get using adb?
Click to expand...
Click to collapse
In answer to your question:
Document software is a system software and can not be deleted or disabled by the user. I deleted it with adb.
In response to your second question:
I could not install it normally and with the phone and encountered this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since I completely deleted this program from the device, I do not understand the reason for this error!
ciger7 said:
Hello friends
I uninstalled the com.android.documentsui package with adb a few days ago
And I really got into trouble
How can I reinstall it?
I have to say that I found the apk file on the Internet, but when I use
Code:
pm install --user 0 android.documentsui-7.0.apk
, I get this error:
Code:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.android.documentsui signatures do not match the previously installed version; ignoring!]
Can anyone help me? Or say goodbye to document?
Click to expand...
Click to collapse
When you uninstall any sys app from adb, still apk will be there.
I guess you may have use adb command like
Code:
pm uninstall --user 0 package.name
In that case simply do this
Code:
pm install --user 0 package.name
replace package name with one you want.
In case you have used command hide instead of uninstall, use
Code:
pm unhide --user 0 package.name
Thanks, I will try this
Make your solution look right
But I think in order for the apk file to remain, I have to use -k (keep data), which I did not use. It is true?
dr.ketan said:
When you uninstall any sys app from adb, still apk will be there.
I guess you may have use adb command like
Code:
pm uninstall --user 0 package.name
In that case simply do this
Code:
pm install --user 0 package.name
replace package name with one you want.
In case you have used command hide instead of uninstall, use
Code:
pm unhide --user 0 package.name
Click to expand...
Click to collapse
I tested your code and wrote:
Code:
pm install --user 0 com.android.documentsui
And I got this error:
Code:
Error: failed to write; com.android.documentsui (No such file or directory)
I can not understand what is the problem!
Do you know how to solve it?
Exists one way to unbrick a phone without Pc/Notebook? Like using a Other phone with otg or something else
rael7979 said:
rael7979 said:
Exists one way to unbrick a phone without Pc/Notebook? Like using a Other phone with otg or something else
Click to expand...
Click to collapse
Phone? Which phone? What is the problem?
Click to expand...
Click to collapse
Infinix Hot 11 X689F, the problem its because I flashed a wrong twrp in my phone, so because that my phone dont start anymore and dont open reovery mode
Take phone to authorized service center and let them try to fix it.
if the other phone is rooted you can use it for fastboot commands:
adb + fastboot Installer
The link provided let you download and flash an ADB / Fastboot from 2008 what is heavily outdated,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what? type 'adb version' and tell me your version
This got released in 2023
Installing Termux would solve the problem.
pkg install android-tools
jwoegerbauer said:
The link provided let you download and flash an ADB / Fastboot from 2008 what is heavily outdated,
View attachment 5866147
Click to expand...
Click to collapse
[ ] You know how zip signing works.
(the binaries are from Feb 2020)
alecxs said:
if the other phone is rooted you can use it for fastboot commands:
adb + fastboot Installer
Click to expand...
Click to collapse
But i can't enter in fastboot mode to send the commands, i need a tool like mtk bypass to android, do you know one?
WoKoschekk said:
Installing Termux would solve the problem.
pkg install android-tools
View attachment 5866221
Click to expand...
Click to collapse
But termux doesn't recognize my device, I put usb but connect and disconnect all the time, and isnt my usb cable
rael7979 said:
But termux doesn't recognize my device, I put usb but connect and disconnect all the time, and isnt my usb cable
Click to expand...
Click to collapse
pkg upgrade
pkg install tsu
With tsu you are root in termux and able to detect your device. Do not use su because then you will leave the termux shell and the ability to run commands from Termux.
WoKoschekk said:
pkg upgrade
pkg install tsu
With tsu you are root in termux and able to detect your device. Do not use su because then you will leave the termux shell and the ability to run commands from Termux.
Click to expand...
Click to collapse
Ok, after that I run the android tools command yeah? Tomorrow I will try
rael7979 said:
Ok, after that I run the android tools command yeah? Tomorrow I will try
Click to expand...
Click to collapse
Yes, after them run pkg install android-tools and you can use fastboot.
alecxs said:
...
(the binaries are from Feb 2020)
Click to expand...
Click to collapse
Only confirms the binaries you linked to are not really useful because massively outdated.
Yes, binaries are v29.0.6 (2020).
adb-ndk/bin at master · Magisk-Modules-Repo/adb-ndk
adb-ndk. Contribute to Magisk-Modules-Repo/adb-ndk development by creating an account on GitHub.
github.com