Bleeding-edge builds of ApkTool.
cm_golden-userdebug 7.1.2 NJH47F db0312e049 release-keys/
rr7.1_golden.nova.20170822.zip– Nougat 7.1.2 (Resurrection Remix) 20170822, for
Samsung Galaxy S3-Mini NFC(I8190N).
The base of the partition-structure is from
It will disable the
Security-Enhanced Linux (SELinux)🔗︎ and newly Android 7.0 added
dalvik's ART Just-In-Time (JIT)🔗︎, the SELinux will be set to permissive settings, just in-case it will be enabled in the future. The modification will allow mtp and adb access from boot and recovery, so you could access your phone at that stage too, it will resolve some WiFi and cast problems and will allow ADB access without annoying popups (default allowed), knox is disabled too but it won’t do much on the custom ROM (unless you’ll be manually download KNOX to access Samsung-pay, which in this case it could be useful to keep it anyway).
Clicking the WiFi or Bluetooth buttons on your newly flushed/reset phone,
and the button keeps turning-back to disabled-state?
-before you’ll snap your tablet in half
in a pure-rage against the machines, try the following solution…
This version is pretty much the latest one you’ll see online: https://www.busybox.net/downloads/binaries/1.21.1/
But the real latest one (to date) binary (ready to use!) is this one:
Unofficial builds for
were moved to here:
if [[ ! -z $2 ]]; then let "RC=($((16$2)) & 16711680) >> 16"; let "GC=($((16$2)) & 65280) >> 8"; let "BC=$((16$2)) & 255"; fi case $1 in scr_red) ;& scr_green) ;& scr_blue) ;& scr_yellow) ;& scr_cyan) ;& scr_magenta) ;& scr_white) ;& scr_black) P=/sys/class/misc/mdnie/hook_control/ if [[ ! -z $2 ]]; then echo $RC > $P/$1_red echo $GC > $P/$1_green echo $BC > $P/$1_blue fi echo $(printf "#%02X%02X%02X\n" $(cat $P/$1_red) $(cat $P/$1_green) $(cat $P/$1_blue)) ;; esac
Some time ago I’ve published an article(post?) about blocking ads using the router,
while it works just fine for non-html files, such as scripts, images and such,
it isn’t so great solution for blocking iframes that shows HTML content,
when the (original firmware) D-Link router software identify a forbidden domain,
it sends out a series of responses, ending with a html page (HTML 1.0 302 redirect -> 200 response page),
while for <script> elements it works perfectly, since it renders an invalid script,
– blocked domain, which shows ads, for example in an iframe in the page (such as eBay),
will still block the original content, but will show an iframe, well… filled with the D-Link’s blocked page msg:
git clone --recursive git://github.com/iBotPeaches/Apktool.git
git -c http.sslVerify=false clone --recursive https://github.com/iBotPeaches/Apktool.git
./gradlew applyPatches– Applies
./gradlew build fatJar– Builds Apktool, including final binary.
./gradlew - Optional - build fatJar Proguard jar too
After 1-2 minutes you should have a jar file at
there is no , it’s “android:Theme.Holo”.
A collection of MTK-devices (mostly Chinese) and older compatible w/ Samsung, HTC, HTM vendors (x86 and x64).
Does not required root access, pulling is a great way of using some “vendor only” applications, for me it was a very well-designed Hebrew-Date calendar, only available in native Samsung-Galaxy ROMS for some vendors.
Other than that it is a slow (one by one), but sure way of file backup, from “root location” that is available on readonly basis.
alternative options maybe using a file-manager such as “X-Plore”, and compressing the entire folder tree of the desire “root location”, placing the zip in a readable location on the SdCard, the entire process might take a while but the download process will be much faster due to one-big-file-handling instead of one-by-one fetching which requires a lot of “connection” overhead..
appspot is a sandbox/playground (whatevvvvveeeerrrr….) for apps…served by Google Frontend servers
breaking the logic without any whitepapers was quite easy…
I was proxy’ing my phone’s addresses, through my PC’s FIDDLER, this is a monthly routine,
since I need to keep up with all the junk push through publishers, through their new updated applications,
after I’m maintaining a list of all new PING, TRACKING, STATISTICS, ADVERTISEMENTS and plain old UNNEEDED JUNK,
I’m adding it to my sub-website hosts.eladkarako.com.
this time I’ve noticed something cool: using the host-name:
gaednsproxy.appspot.com with a simple mimetype of
text/html and short GET request:
request was made by some open source application named DroidFu:
GET http://gaednsproxy.appspot.com/?d=WTJ4cFpXNTBjek11WjI5dloyeGxMbU52YlE9PQ%3D%3D HTTP/1.1 Host: gaednsproxy.appspot.com User-Agent: Android/DroidFu Connection: close Connection: close
response was just an ip..
HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Date: Thu, 11 Dec 2014 07:56:31 GMT Server: Google Frontend Cache-Control: private Alternate-Protocol: 80:quic,p=0.02 Connection: close 220.127.116.11
looks like an escaped-base64 argument, I’ve thought..
using my good old base64 enc/dec here
it was double enc/ in base64
WTJ4cFpXNTBjek11WjI5dloyeGxMbU52YlE9PQ%3D%3D (unescaped)-> WTJ4cFpXNTBjek11WjI5dloyeGxMbU52YlE9PQ== (first base64 decode)-> Y2xpZW50czMuZ29vZ2xlLmNvbQ== (second base64 decode)-> clients3.google.com
so this one was just a simple reverse hostname (clients3.google.com) to IP (18.104.22.168)…
double base64 looks kind’a overkill, fishy?? don’know..
from my experience it just may be a plain Anti-Fraud (Anti Man-In-The-Middle, Proxy/DNS Poisoning, etc…),
this way the IP is resolved through an external-server (a.k.a “safe place”), other then a risked machine (self Android device),
simple but effective….
הדרכה בתמונות מסך
- Install a custom-recovery
- turn off the phone, wait for full shutdown (no screen/LED indicator)
- hold [volume down]+[home button]+[power button]
- press [volume up] on this screen
- on your pc: uninstall KIES package (if exist..), and install plain drivers from http://developer.samsung.com/technical-doc/view.do?v=T000000117
- on your pc: download odin: Odin3_v3_07.rar, extract it anywhere.
- on your pc: download this version of TWRP custom recovery (better then clockwork’s): openrecovery-twrp-22.214.171.124-ha3g.img.rar, extract it anywhere (but just once, you need to end up with tar file, don’t extract the tar file itself).
- plug in your phone to USB2.0 port (don’t use USB3.0), wait for drivers installation to finish.
- right click Odin3-v3.07.exe and select “Run as administrator”
- on odin, click the PDA button, load the tar file, press start wait till finish.
- the phone will restart (done).
- install supersu binary “package”
1st Thing You Got To Know Is That This Project Is A Part Of A 1-Man 1-Day Hackaton I’m Putting MySelf Through Every Month, This Month I’ve Started At Nov. 14 – Nov 15. (Saturday Fun), Listening An Endless Loop Of This Track:
You need to follow the system-requirements, and install the minimal Java-SDK (JDK) version in-order to support Android SDK development tookit (for example, did you know you can’t compile anything if you are using JDK v9 ? :) )…