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

[g1rafucker]

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

[Te-k]

Hi,

Is your phone rooted?

[electromage]

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]

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]

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]

So the modules run and it gets stuck?

[Joedmin]

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

[oefielixir]

Any news on that?