I dont know if this is the right place to ask this. If it isnt, mods can move or remove the post.
I was using an app for months on an emulator with http toolkit. But suddenly it stopped working after its most recent update few days ago. Every time I launch it now, it throws an error "check API configuration"
{
"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"
}
I was using Android studio with AVD Pixel 6 API 33 Android 13 x86_64
Out of curiosity, I created a separate avd using Pixel 5 API 28 Android 9 x86, and it works on this somehow, but again shuts down if I connect http toolkit to the emulator. If I disconnect HT, it runs. So Im convinced it somehow is rejecting the toolkit connection. I patched it using the ca-certificate from toolkit but it doesn't work.
Edit: Further investigation reveals the app is actually rejecting the adb proxy. So before I pushed 10.0.2.2:8001 the app worked fine. However as soon as I pushed it through, it started giving the error. So its apparent that its detecting the proxy and rejecting it even though its patched to accept the proxy.
How can I get it to accept it? I patched it with the toolkit certificate earlier, however it doesnt seem to be working anymore.
I appreciate any help I get with this.
Never heard of "adb proxy".
jwoegerbauer said:
Never heard of "adb proxy".
Click to expand...
Click to collapse
global proxy via shell. Can you help?
Related
Suddenly, mine stopped working. Launching it would give error messages boxes.
Tried to uninstall it, removed all registry references to "Samsung" and "Kies", re-installed it. Same problem.
This is what appears now (Windows7 64):
{
"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"
}
Any ideas?
Thanks.
GK
Was there any PC updates since lat confirmed working? ie Windows, software, resister changes etc...
You could try a system restore to an earlier time
Sent from my GT-I9500 using xda premium
UpInTheAir said:
Was there any PC updates since lat confirmed working? ie Windows, software, resister changes etc...
You could try a system restore to an earlier time
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Yes, there were...Windows updates ones.
It seems that, some now and then, a Windows update messes up some things. For instance, the calculator went beserk in the last update. Reverted the system to a pre-update restore point. Calculator OK. Couple of days later, the update kicked in again, calculator to the dogs.
In the past, there were instances where Windows updates would mess some things up and then just a short time later another update would kick-in and things went back to normal. Clearly MS is, sometimes, putting out some buggy updates just to patch them a week later.
What a wonderful IT world...I feel like I am allways catering for the latest blunder...Sheessh....
GK
No matter what VNC server and viewer I try on a desktop PC, none work, and they all show a black screen with weird lines.
I enable debugging mode, have correct adb connection and drivers, and I remember being able to connect through VNC fine before, but not since 4.4.3 onwards...
This is what I see... it looks like a color setting or something, but tweaking settings in the viewer leads me no results:
I also have a weird glitch where the keyboard becomes invisible after closing any VNC server, and I have to reboot to get it back visible.
{
"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"
}
bump fer justice
I've encountered a similar situation with at least 2 VNC servers. Didn't dig too much into the problem, but I'd be interested in a fix too.
I've seen TeamViewer being recommended as an alternative, but I'd rather use VNC.
Oh, and I'm using CM11, 4.4.3 nightlies.
PS: Don't bump your own threads in such a short period. You might have problems with the moderators.
Thanks... to this day, I'm still unable to use any VNC server... I even went back to stock with root, and using different PC's, but no go.
When I tried to capture screenshots from twrp recovery and I used the wrong pixel format (rgb888 instead of rgb565) or reaolution for ffmpeg to decode the raw images I got similar images like you get with vnc. I dont know is that helps or not.
Hi,
So a few weeks ago "VSCO cam" the well-Known picture editing apps for android devices stopped working on my CM11 Nexus4
I contacted support Thinking It was A problem with their Latest update.. But, After a few emails they asked If my device was rooted
I told them that I run CM11 which By default is Rooted and that was his reply:
{
"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"
}
So my questions is:
How is that even possible ? do the app scan the OS for root ?
and if that was the case, Is there a way to "fake-un root" the device or something ?
Are there any Apps you know that will not work on rooted device other than VSCO ?
PS : If this was the wrong forum I'm truly sorry I thought this thread fits here.
And i might want to add: is there a workaround or fix? I tried to unroot and reinstall and it still doesnt work. I also tried to reinstall backup via Titatium which was mentioned somewhere - didn't help... Neither did setting restrictions in privacy app management.I really like the editing tools and variety of filters (especially since they did cost money)
Customer service insists that it is their policy now... Can you maybe cloak the rooting status?
Ps: root cloak via xposed framework does not work...
Somehow it did work in the end... I dont even have root cloak any more and everything works fine. U just dont know why... ?
I got a Moto G phone running Oreo. I have a firewall installed, and its logs show an app with the name "System" trying to connect to various AWS hosted addresses. The phone is not rooted. I am trying to find out which process this System actually is, and what is its purpose. I am trying to somehow capture some traffic and find something.
If anyone knows what exactly this is and whether I should be worried or not, please let me know.
Here are some of them:
server-52-222-149-174.fra53.r.cloudfront.net:443
server-52-222-149-128.fra53.r.cloudfront.net:443
server-52-222-149-139.fra53.r.cloudfront.net:443
server-52-222-149-89.fra53.r.cloudfront.net:443
server-52-222-149-54u.fra53.r.cloudfront.net:443
server-52-222-149-143.fra53.r.cloudfront.net:443
server-52-222-149-206.fra53.r.cloudfront.net:443
server-52-222-149-99.fra53.r.cloudfront.net:443
server-54-230-93-53.fra2.r.cloudfront.net:443
server-54-230-93-231.fra2.r.cloudfront.net:443
server-54-230-93-238.fra2.r.cloudfront.net:443
server-54-230-93-128.fra2.r.cloudfront.net:443
server-54-230-93-148.fra2.r.cloudfront.net:443
server-54-230-93-236.fra2.r.cloudfront.net:443
server-54-230-93-37.fra2.r.cloudfront.net:443
server-54-230-93-198.fra2.r.cloudfront.net:443
server-54-230-93-211.fra2.r.cloudfront.net:443
server-54-230-93-54.fra2.r.cloudfront.net:443
server-54-230-93-207.fra2.r.cloudfront.net:443
server-54-230-8-80.lhr3.r.cloudfront.net:443
server-54-230-8-118.lhr3.r.cloudfront.net:443
server-54-230-8-51.lhr3.r.cloudfront.net:443
server-54-230-8-31.lhr3.r.cloudfront.net:443
server-54-230-8-199.lhr3.r.cloudfront.net:443
server-54-230-8-29.lhr3.r.cloudfront.net:443
server-54-230-8-87.lhr3.r.cloudfront.net:443
server-54-230-8-156.lhr3.r.cloudfront.net:443
server-54-230-8-122.lhr3.r.cloudfront.net:443
server-54-230-8-12.lhr3.r.cloudfront.net:443
server-54-230-8-6.lhr3.r.cloudfront.net:443
server-54-230-8-98.lhr3.r.cloudfront.net:443
server-54-230-8-53.lhr3.r.cloudfront.net:443
server-13-32-158-252.fra56.r.cloudfront.net:443
server-13-32-158-222.fra56.r.cloudfront.net:443
server-13-32-158-26.fra56.r.cloudfront.net:443
server-13-32-158-38.fra56.r.cloudfront.net:443
server-13-32-158-107.fra56.r.cloudfront.net:443
server-13-32-158-254.fra56.r.cloudfront.net:443
server-13-32-123-5.lhr4.r.cloudfront.net
server-13-32-123-73.lhr4.r.cloudfront.net
server-13-32-123-75.lhr4.r.cloudfront.net
server-143-204-181-81.lhr50.r.cloudfront.net:443
server-143-204-181-49.lhr50.r.cloudfront.net:443
server-143-204-181-63.lhr50.r.cloudfront.net:443
server-143-204-229-32.cdg3.r.cloudfront.net
server-143-204-229-114.cdg3.r.cloudfront.net
server-143-204-229-17.cdg3.r.cloudfront.net
server-143-204-229-102.cdg3.r.cloudfront.net
server-143-204-229-85.cdg3.r.cloudfront.net
server-143-204-229-71.cdg3.r.cloudfront.net
server-143-204-229-20.cdg3.r.cloudfront.net
server-143-204-15-118.mxp64.r.cloudfront.net
server-143-204-15-20.mxp64.r.cloudfront.net
server-143-204-15-40.mxp64.r.cloudfront.net
server-143-204-15-4.mxp64.r.cloudfront.net
server-143-204-15-18.mxp64.r.cloudfront.net
server-143-204-15-72.mxp64.r.cloudfront.net
server-143-204-15-68.mxp64.r.cloudfront.net
server-143-204-15-112.mxp64.r.cloudfront.net
{
"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"
}
-----------------------------------------------------------
I found some more information using logcat:
[ 10-19 17:12:33.467 1229: 1309 E/LocSvc_xtra2 ]
connect:204] connect to 54.230.93.211 failed
This is one of the IPs that System process is trying to connect. Some googling tells that this is Location Service being used probably. I have GPS turned off completely when I don't need it. I have also given access to GPS only to OpenMaps application which isn't running at the moment. All google apps are in disabled state.
I also noticed that these connection attempts happen every 5-6 minutes.
I cannot use strace as don't have root. I am trying to route the traffic from the phone through my PC to be able to capture network traffic.
I have successfully unbricked my phone back to hydrogen twice before but unfortunately I don’t have a windows computer or friends. It seems to load the same in wine but it dosen't recognize the device (oneplus 6) and often freezes. Anybody have an idea how i can make this work. thanks
{
"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"
}
Linux_fart_18.3 said:
I have successfully unbricked my phone back to hydrogen twice before but unfortunately I don’t have a windows computer or friends. It seems to load the same in wine but it dosen't recognize the device (oneplus 6) and often freezes. Anybody have an idea how i can make this work. thanks
Click to expand...
Click to collapse
With Virtual system install windows 7 and get your job done.
reza6d said:
With Virtual system install windows 7 and get your job done.
Click to expand...
Click to collapse
I got my windows 7 key yesterday and strangely what ive found out through researched is that my laptop is so old that it only supports 32 bit virtualization and not 64 even though the host system is a 64 bit. Anyhow, I get the same results as when I try to run it through wine.
https://drive.google.com/file/d/1E27aYpN82vv0GZQcK9iQuCSlwZX37q0J/view?usp=sharing
Finally got some one to let me fix it on their windows 10, easy peasy.
Hey i know this thread is old but:
There's a cross-platfrom implementation for EDL: https://github.com/bkerler/edl
QFIL emulation should do what you need if you already have the required files.