search

mvt-project / mvt

MVT (Mobile Verification Toolkit) helps with conducting forensics of mobile devices in order to find signs of a potential compromise.
https://mvt.re
Other
10.31k stars 960 forks source link

[mvt.android.modules.adb.chrome_history] Running module ChromeHistory... #396

Open g1rafucker opened 12 months ago

g1rafucker commented 12 months ago

stuck on [mvt.android.modules.adb.chrome_history] Running module ChromeHistory... any clues? its been 30mins

Te-k commented 12 months ago

Hi,

Is your phone rooted?

electromage commented 12 months ago

I've hit this also. My phone is not rooted - is that a requirement? Is there a way around this? My understanding is that rooting the phone can present new security issues.

Te-k commented 11 months ago

Yes, MVT can only access Chrome history if your phone is rooted, which definitely creates some security issues. That said, it should tell you it couldn't access and not block on it. I am not sure what is the issue there. What is your android version? Can you check if you can access /data/data/com.android.chrome/app_chrome/Default/History in adb?

lost-in-bits commented 10 months ago

Yes, MVT can only access Chrome history if your phone is rooted, which definitely creates some security issues. That said, it should tell you it couldn't access and not block on it. I am not sure what is the issue there. What is your android version? Can you check if you can access /data/data/com.android.chrome/app_chrome/Default/History in adb?

I'm having the same issue. when I run adb shell getprop ro.build.version.release, adb returns "13".

Additionally, I get "adb: inaccessible or not found" when I try to access /data/data/com.android.chrome/app_chrome/Default/History.

Let me know if you need any more information.

Te-k commented 10 months ago

So the modules run and it gets stuck?

Joedmin commented 8 months ago

Is it possible to skip this check on a non-rooted device?

oefielixir commented 7 months ago

Any news on that?

dsh0 commented 1 month ago

Until the issue is fixed, when ADB ask to authorise the connected computer, you need to check the box to remember the device. ChromeHistory hangs if you give one time permission, but if the box is checked it detects immediately that the device is not rooted and moves on. You can always revoke authorisation later.

Nader-B10 commented 1 month ago

Screenshot 2024-08-17 173912 how to fix this?

Benjipeper commented 3 weeks ago

hey guys a got a really weird problem, i got my android listed as adb devices through "adb connect [IP-adress]:5555" and try to run the "mvt-android check-adb" its start running but then still gives the "No devices found" after running "chrome_history" any ideas what might causes this?