I would like to root my s7 edge but i am not able to find a comprehensive guide
Showing posts with label Guide. Show all posts
Showing posts with label Guide. Show all posts
Friday, 5 August 2016
(Guide) me to move my apps to SD card
I have a mi pad internal memory is only 16gb. Wt to do ..
[GUIDE] Installing recoveries on 5X, no PC need
Hello guys and girls,
Did you know that 5X has two recovery partitions? Did you know that you do not need PC, cable, buggy ADB drivers, PC utilities and other stuff to install your favorite recovery to any assigned partition and keep the stock at the same time?
Did you know that you are free to start any installed recovery tool?
This guide brings you a deeper understsnding what is inside your device.
Prerequisites: your bootloader must be unlocked, device must be rooted (CM13 is rooted out the box - just enable it in the developer settings).
Go on:
1. Install Termux terminal emulator from Playmarket.
2. Type 'su' command in Termux, then confirm root access.
3. Type this command as a root:
ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name
- if it reports error try step by step discover right path by typing ls /dev/block/platform etc until you see 'by-name' folder.
This command reports you all partitions installed on your device. Check it out carefully and find strings which end with these values:
recovery -> /dev/block/mmcblk0p20
erecovery -> /dev/block/mmcblk0p21
So now in my example you can see that I have two recovery tool partitions labeled 'recovery' and 'erecovery' and their system names. The first is regular recovery called by VolUp+Pwr button, the second is an alternative recovery, called with the same buttons, but when plugged to PC.
You can flash any recoveries there in any combination on your taste.
4. Download desired recovery (twrp for example), unpack and put .IMG file to the root of your memory card, internal or external it does not matter. Just open any file manager and note the full file path. In my example it is:
/storage/emulated/0/recovery.img
5. Flash recovery typing this command:
dd if=/storage/emulated/0/recovery.img of=/dev/block/mmcblk0p21
- in this example you can see that I am flashing an alternative recovery. Just change the 'of' parameter to your desired partition, using its system name.
Done!
6. Instead of cables, PCs, magic buttons I advise you to launch your desired recovery tool with the following simple commands in terminal emulator as a root:
# reboot recovery
or
# reboot erecovery
That's all.
Did you know that 5X has two recovery partitions? Did you know that you do not need PC, cable, buggy ADB drivers, PC utilities and other stuff to install your favorite recovery to any assigned partition and keep the stock at the same time?
Did you know that you are free to start any installed recovery tool?
This guide brings you a deeper understsnding what is inside your device.
Prerequisites: your bootloader must be unlocked, device must be rooted (CM13 is rooted out the box - just enable it in the developer settings).
Go on:
1. Install Termux terminal emulator from Playmarket.
2. Type 'su' command in Termux, then confirm root access.
3. Type this command as a root:
ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name
- if it reports error try step by step discover right path by typing ls /dev/block/platform etc until you see 'by-name' folder.
This command reports you all partitions installed on your device. Check it out carefully and find strings which end with these values:
recovery -> /dev/block/mmcblk0p20
erecovery -> /dev/block/mmcblk0p21
So now in my example you can see that I have two recovery tool partitions labeled 'recovery' and 'erecovery' and their system names. The first is regular recovery called by VolUp+Pwr button, the second is an alternative recovery, called with the same buttons, but when plugged to PC.
You can flash any recoveries there in any combination on your taste.
4. Download desired recovery (twrp for example), unpack and put .IMG file to the root of your memory card, internal or external it does not matter. Just open any file manager and note the full file path. In my example it is:
/storage/emulated/0/recovery.img
5. Flash recovery typing this command:
dd if=/storage/emulated/0/recovery.img of=/dev/block/mmcblk0p21
- in this example you can see that I am flashing an alternative recovery. Just change the 'of' parameter to your desired partition, using its system name.
Done!
6. Instead of cables, PCs, magic buttons I advise you to launch your desired recovery tool with the following simple commands in terminal emulator as a root:
# reboot recovery
or
# reboot erecovery
That's all.
Tuesday, 2 August 2016
[GUIDE] Unlocking BOOTLOADER and Rooting Easy Method
Just download the files attached here and do as per the video tutorial here, and you are done. Your bootloader may still remains if black, which doesn't mean that it is locked. You can check the status of bootloader with the given tool. Good luck! If you have any doubts comment here, or below the video tutorial.
Saturday, 30 July 2016
[GUIDE] How to build a Samsung Kernel July 30, 2016

How to compile a Samsung Kernel from source
Ok folks, I am going to show you how to build a Sammy kernel from source. This will be a very long guide, so I might miss one or two things. But we will solve that if it happens.
Below is a list of requirements that you must have in order to be successful.
REQUIREMENTS
1. For the best outcome, you need to be on Linux. I dont support VM Box
2. All the android dependencies. (Which I will provide)
3. A github account or the like. Its free.
4. Be familiar with terminal commands
5. And have alot of patients
SETTING UP YOUR BUILD ENVIRONMENT
First thing we need to do is set up your build environment. So in order to do this we need to install some packages to make sure your kernel
compiles correctly.... So open a terminal on your desktop, and copy and paste the code into your terminal from below:
Code:
sudo apt-get install git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng
Friday, 29 July 2016
[Guide] Full Screen Dialer - MM
[Guide] Full Screen Dialer - MM
This guide assumes you are already proficient at de/recompiling stock apk's.
We are modifying SecContacts_M.apk.
*** Add new files attached to the bottom of this post.
res\values\ids.xml
Add new ID
smali\com\android\dialer\dialpad\DialpadFragment.s mali
Add new fields.
Increase .locals by 3 and add new code in BLUE
Increase .locals by 3 and add new code in BLUE
Increase .locals by 3 and add new code in BLUE
Add new code in BLUE
Increase .locals by 5 and add new code in BLUE
Add new methods to bottom of smali.
Next smali...
smali\com\android\dialer\dialpad\DialpadKeyButton. smali
Increase .locals by 3 and add new code in BLUE
Next smali...
smali\com\samsung\dialer\dialpad\ap.smali
Add new fields.
Increase .locals by 3 and add new code in BLUE
Add new code in BLUE
Add new code in BLUE
Add new code in BLUE
Add new methods to the bottom of this smali.
Rom Control V2 Entries
[SOURCE CODE][DEV TOOL][SDK 21+]6thGear RomControl v2.+ for Devs by daxgirl
Add arrays
Add to your pref
This guide assumes you are already proficient at de/recompiling stock apk's.
We are modifying SecContacts_M.apk.
*** Add new files attached to the bottom of this post.
res\values\ids.xml
Add new ID
Code:
<item type="id" name="gear_panel_bg_view">false</item>
Add new fields.
Code:
# instance fields
.field private final mFullscreenBG:Z
.field private final mThemeoverride:Z
Code:
.method private K()V
.locals 7
.
.
.
const v2, 0x7f0201cc ## type="drawable" name="dialpad_fragment_background"
iget-boolean v4, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mFullscreenBG:Z
if-eqz v4, :cond_td
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getContext()Landroid/content/Context;
move-result-object v4
const-string v5, "dialpad_fragment_background_fullscreen" # This is your resource name
const-string v6, "drawable" # This is the resource type
invoke-static {v4, v5, v6}, Lcom/android/wubydax/IdUtils;->getIdentifier(Landroid/content/Context;Ljava/lang/String;Ljava/lang/String;)I
move-result v2
:cond_td
invoke-virtual {v1, v2}, Landroid/content/res/Resources;->getDrawable(I)Landroid/graphics/drawable/Drawable;
move-result-object v1
invoke-virtual {v0, v1}, Landroid/view/View;->setBackground(Landroid/graphics/drawable/Drawable;)V
goto :goto_1
.end method
Code:
.method private N()V
.locals 5
.
.
.
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getResources()Landroid/content/res/Resources;
move-result-object v0
const v1, 0x7f0201cd ## type="drawable" name="dialpad_fragment_bg"
iget-boolean v2, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mFullscreenBG:Z
if-eqz v2, :cond_td
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getContext()Landroid/content/Context;
move-result-object v2
const-string v3, "dialpad_fragment_bg_fullscreen" # This is your resource name
const-string v4, "drawable" # This is the resource type
invoke-static {v2, v3, v4}, Lcom/android/wubydax/IdUtils;->getIdentifier(Landroid/content/Context;Ljava/lang/String;Ljava/lang/String;)I
move-result v1
:cond_td
invoke-virtual {v0, v1}, Landroid/content/res/Resources;->getDrawable(I)Landroid/graphics/drawable/Drawable;
Code:
.method private g(Landroid/view/View;)V
.locals 5
.
.
.
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getResources()Landroid/content/res/Resources;
move-result-object v0
const v1, 0x7f0201cc ## type="drawable" name="dialpad_fragment_background"
iget-boolean v2, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mFullscreenBG:Z
if-eqz v2, :cond_td
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getContext()Landroid/content/Context;
move-result-object v2
const-string v3, "dialpad_fragment_background_fullscreen" # This is your resource name
const-string v4, "drawable" # This is the resource type
invoke-static {v2, v3, v4}, Lcom/android/wubydax/IdUtils;->getIdentifier(Landroid/content/Context;Ljava/lang/String;Ljava/lang/String;)I
move-result v1
:cond_td
invoke-virtual {v0, v1}, Landroid/content/res/Resources;->getDrawable(I)Landroid/graphics/drawable/Drawable;
move-result-object v0
invoke-virtual {p1, v0}, Landroid/view/View;->setBackground(Landroid/graphics/drawable/Drawable;)V
goto :goto_1
.end method
Code:
.method public b(Landroid/view/View;)V
.
.
.
const v0, 0x7f0e021a ## type="id" name="digits"
invoke-virtual {p1, v0}, Landroid/view/View;->findViewById(I)Landroid/view/View;
move-result-object v0
check-cast v0, Lcom/android/dialer/dialpad/EllipsisTextView;
iput-object v0, p0, Lcom/android/dialer/dialpad/DialpadFragment;->c:Lcom/android/dialer/dialpad/EllipsisTextView;
move-object/from16 v2, p0
invoke-virtual {v2, v0}, Lcom/android/dialer/dialpad/DialpadFragment;->setDialerDigitPressed(Landroid/widget/TextView;)V
iget-object v0, p0, Lcom/android/dialer/dialpad/DialpadFragment;->c:Lcom/android/dialer/dialpad/EllipsisTextView;
iget-object v2, p0, Lcom/android/dialer/dialpad/DialpadFragment;->v:Landroid/content/Context;
invoke-static {v2}, Lcom/android/dialer/dialpad/w;->a(Landroid/content/Context;)Lcom/android/dialer/dialpad/w;
move-result-object v2
invoke-virtual {v0, v2}, Lcom/android/dialer/dialpad/EllipsisTextView;->setKeyListener(Landroid/text/method/KeyListener;)V
Code:
.method public onCreateView(Landroid/view/LayoutInflater;Landroid/view/ViewGroup;Landroid/os/Bundle;)Landroid/view/View;
.locals 10
const/4 v4, 0x0
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->setSDBackground()V
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->setThemeOverride()V
sget-object v0, Lcom/android/dialer/dialpad/DialpadFragment;->O:Ljava/lang/String;
const-string/jumbo v1, "onCreateView >>>>>"
invoke-static {v0, v1}, Landroid/util/secutil/Log;->secI(Ljava/lang/String;Ljava/lang/String;)I
const v0, 0x7f030098 ## type="layout" name="dialpad_fragment"
iget-boolean v6, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mFullscreenBG:Z
if-eqz v6, :cond_td
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getContext()Landroid/content/Context;
move-result-object v6
invoke-virtual {v6}, Landroid/content/Context;->getResources()Landroid/content/res/Resources;
move-result-object v6
const-string v7, "dialpad_fragment_fullscreen" # This is the resource name
const-string v8, "layout" # this is resource type
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getContext()Landroid/content/Context;
move-result-object v9
invoke-virtual {v9}, Landroid/content/Context;->getPackageName()Ljava/lang/String;
move-result-object v9
invoke-virtual {v6, v7, v8, v9}, Landroid/content/res/Resources;->getIdentifier(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)I
move-result v0 #This now holds your id number
:cond_td
invoke-virtual {p1, v0, p2, v4}, Landroid/view/LayoutInflater;->inflate(ILandroid/view/ViewGroup;Z)Landroid/view/View;
Code:
.method setDialerDigit(Landroid/widget/TextView;)V
.locals 3
iget-boolean v1, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mThemeoverride:Z
if-eqz v1, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v1, "main_digit_color"
const v2, -0x1000000
invoke-static {v0, v1, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
:cond_td
return-void
.end method
.method setDialerDigitPressed(Landroid/widget/TextView;)V
.locals 3
iget-boolean v1, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mThemeoverride:Z
if-eqz v1, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v1, "main_digit_color_pressed"
const v2, -0x1000000
invoke-static {v0, v1, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
:cond_td
return-void
.end method
.method setDialerLetter(Landroid/widget/TextView;)V
.locals 3
iget-boolean v1, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mThemeoverride:Z
if-eqz v1, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v1, "main_letter_color"
const v2, -0x1000000
invoke-static {v0, v1, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
:cond_td
return-void
.end method
.method public setSDBackground()V
.locals 5
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadFragment;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v1, "enable_dialer_custom_bg"
const/4 v2, 0x0
invoke-static {v0, v1, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
if-eqz v0, :cond_td
const/4 v0, 0x1
iput-boolean v0, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mFullscreenBG:Z
:cond_td
return-void
.end method
.method public setThemeOverride()V
.locals 3
const/4 v2, 0x0
iput-boolean v2, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mThemeoverride:Z
new-instance v0, Ljava/io/File;
const-string v1, "/data/data/com.wubydax.romcontrol.v2/files/modcfg_theme_override"
invoke-direct {v0, v1}, Ljava/io/File;-><init>(Ljava/lang/String;)V
invoke-virtual {v0}, Ljava/io/File;->exists()Z
move-result v0
if-eqz v0, :cond_td
const/4 v0, 0x1
iput-boolean v0, p0, Lcom/android/dialer/dialpad/DialpadFragment;->mThemeoverride:Z
:cond_td
return-void
.end method
smali\com\android\dialer\dialpad\DialpadKeyButton. smali
Increase .locals by 3 and add new code in BLUE
Code:
.method public a()V
.locals 6
.
.
.
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadKeyButton;->getResources()Landroid/content/res/Resources;
move-result-object v0
## entire dialpad background setup for transparency
const v1, 0x7f020072 ## type="drawable" name="call_dial_btn_bg_easy_dialpad_button_white" id="0x7f020072" />
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadKeyButton;->getContext()Landroid/content/Context;
move-result-object v3
invoke-virtual {v3}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v3
const-string v4, "enable_dialer_custom_bg"
const/4 v5, 0x0
invoke-static {v3, v4, v5}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v3
if-eqz v3, :cond_td
invoke-virtual {p0}, Lcom/android/dialer/dialpad/DialpadKeyButton;->getContext()Landroid/content/Context;
move-result-object v3
const-string v4, "call_dial_btn_bg_easy_dialpad_button_transparent" # This is your resource name
const-string v5, "drawable" # This is the resource type
invoke-static {v3, v4, v5}, Lcom/android/wubydax/IdUtils;->getIdentifier(Landroid/content/Context;Ljava/lang/String;Ljava/lang/String;)I
move-result v1
:cond_td
invoke-virtual {v0, v1, v2}, Landroid/content/res/Resources;->getDrawable(ILandroid/content/res/Resources$Theme;)Landroid/graphics/drawable/Drawable;
move-result-object v0
invoke-virtual {p0, v0}, Lcom/android/dialer/dialpad/DialpadKeyButton;->setBackground(Landroid/graphics/drawable/Drawable;)V
goto :goto_0
.end method
smali\com\samsung\dialer\dialpad\ap.smali
Add new fields.
Code:
# instance fields
.field private final mFullscreenBG:Z
.field private final mThemeoverride:Z
Code:
.method private a(Landroid/widget/ImageView;Z)V
.locals 4
.
.
.
if-nez p1, :cond_0
:goto_0
return-void
:cond_0
if-eqz p2, :cond_1
const/4 v0, 0x0
invoke-virtual {p1, v0}, Landroid/widget/ImageView;->setVisibility(I)V
invoke-direct {p0}, Lcom/samsung/dialer/dialpad/ap;->c()I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/ImageView;->setImageResource(I)V
invoke-direct {p0}, Lcom/samsung/dialer/dialpad/ap;->f()I
move-result v0
invoke-virtual {p0}, Lcom/samsung/dialer/dialpad/ap;->setThemeOverride()V
iget-boolean v1, p0, Lcom/samsung/dialer/dialpad/ap;->mThemeoverride:Z
if-eqz v1, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v1
invoke-virtual {v1}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v1
const-string v2, "main_letter_color"
const v3, -0x1000000
invoke-static {v1, v2, v3}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
:cond_td
invoke-static {v0}, Landroid/content/res/ColorStateList;->valueOf(I)Landroid/content/res/ColorStateList;
move-result-object v0
invoke-virtual {p1, v0}, Landroid/widget/ImageView;->setImageTintList(Landroid/content/res/ColorStateList;)V
Code:
.method private a(Landroid/widget/TextView;I)V
.locals 1
if-nez p1, :cond_0
:goto_0
return-void
:cond_0
iget-object v0, p0, Lcom/samsung/dialer/dialpad/ap;->s:[I
aget v0, v0, p2
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setText(I)V
iget-object v0, p0, Lcom/samsung/dialer/dialpad/ap;->e:Landroid/graphics/Typeface;
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTypeface(Landroid/graphics/Typeface;)V
invoke-direct {p0}, Lcom/samsung/dialer/dialpad/ap;->e()I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
move-object/from16 v1, p0
invoke-virtual {v1, p1}, Lcom/samsung/dialer/dialpad/ap;->setDialerDigit(Landroid/widget/TextView;)V
Code:
.method private b(Landroid/widget/TextView;I)V
.
.
.
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setText(I)V
iget-object v0, p0, Lcom/samsung/dialer/dialpad/ap;->f:Landroid/graphics/Typeface;
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTypeface(Landroid/graphics/Typeface;)V
invoke-direct {p0}, Lcom/samsung/dialer/dialpad/ap;->f()I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
move-object/from16 v1, p0
invoke-virtual {v1, p1}, Lcom/samsung/dialer/dialpad/ap;->setDialerLetter(Landroid/widget/TextView;)V
invoke-direct {p0, p1}, Lcom/samsung/dialer/dialpad/ap;->g(Landroid/widget/TextView;)V
iget-boolean v0, p0, Lcom/samsung/dialer/dialpad/ap;->d:Z
invoke-direct {p0, p1, v0}, Lcom/samsung/dialer/dialpad/ap;->a(Landroid/widget/TextView;Z)V
invoke-direct {p0, p1}, Lcom/samsung/dialer/dialpad/ap;->i(Landroid/widget/TextView;)V
goto :goto_0
.end method
Code:
.method private c(Landroid/view/View;)V
.locals 5
invoke-virtual {p0}, Lcom/samsung/dialer/dialpad/ap;->a()I
move-result v1
invoke-virtual {p0}, Lcom/samsung/dialer/dialpad/ap;->b()I
move-result v2
invoke-virtual {p0}, Lcom/samsung/dialer/dialpad/ap;->setThemeOverride()V
iget-boolean v3, p0, Lcom/samsung/dialer/dialpad/ap;->mThemeoverride:Z
if-eqz v3, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v3, "main_divider_color"
const v2, -0x1000000
invoke-static {v0, v3, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v2
:cond_td
const/4 v0, 0x0
:goto_0
Code:
.method setDialerDigit(Landroid/widget/TextView;)V
.locals 3
invoke-virtual {p0}, Lcom/samsung/dialer/dialpad/ap;->setThemeOverride()V
iget-boolean v1, p0, Lcom/samsung/dialer/dialpad/ap;->mThemeoverride:Z
if-eqz v1, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v1, "main_digit_color"
const v2, -0x1000000
invoke-static {v0, v1, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
:cond_td
return-void
.end method
.method setDialerLetter(Landroid/widget/TextView;)V
.locals 3
invoke-virtual {p0}, Lcom/samsung/dialer/dialpad/ap;->setThemeOverride()V
iget-boolean v1, p0, Lcom/samsung/dialer/dialpad/ap;->mThemeoverride:Z
if-eqz v1, :cond_td
invoke-virtual {p1}, Landroid/view/View;->getContext()Landroid/content/Context;
move-result-object v0
invoke-virtual {v0}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;
move-result-object v0
const-string v1, "main_letter_color"
const v2, -0x1000000
invoke-static {v0, v1, v2}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I
move-result v0
invoke-virtual {p1, v0}, Landroid/widget/TextView;->setTextColor(I)V
:cond_td
return-void
.end method
.method public setThemeOverride()V
.locals 5
const/4 v2, 0x0
iput-boolean v2, p0, Lcom/samsung/dialer/dialpad/ap;->mThemeoverride:Z
new-instance v0, Ljava/io/File;
const-string v1, "/data/data/com.wubydax.romcontrol.v2/files/modcfg_theme_override"
invoke-direct {v0, v1}, Ljava/io/File;-><init>(Ljava/lang/String;)V
invoke-virtual {v0}, Ljava/io/File;->exists()Z
move-result v0
if-eqz v0, :cond_td
const/4 v0, 0x1
iput-boolean v0, p0, Lcom/samsung/dialer/dialpad/ap;->mThemeoverride:Z
:cond_td
return-void
.end method
Rom Control V2 Entries
[SOURCE CODE][DEV TOOL][SDK 21+]6thGear RomControl v2.+ for Devs by daxgirl
Add arrays
Code:
<string-array name="crop_entries">
<item>Center Crop (default)</item>
<item>Center Inside</item>
<item>Fit XY</item>
</string-array>
<string-array name="crop_values">
<item>0</item>
<item>1</item>
<item>2</item>
</string-array>
<string-array name="custom_bg_type_entries">
<item>Image</item>
<item>Solid color</item>
<item>Gradient</item>
</string-array>
<string-array name="custom_bg_type_values">
<item>0</item>
<item>1</item>
<item>2</item>
</string-array>
<string-array name="gradient_entries">
<item>Top to bottom</item>
<item>Bottom to top</item>
<item>Left to right</item>
<item>Right to left</item>
</string-array>
<string-array name="gradient_values">
<item>0</item>
<item>1</item>
<item>2</item>
<item>3</item>
</string-array>
Code:
<PreferenceScreen
android:title="Main Dialer Options"
android:summary="Set backgrounds or color">
<com.wubydax.romcontrol.v2.prefs.MySwitchPreference
android:defaultValue="false"
android:key="enable_dialer_custom_bg"
android:summaryOff="Disabled"
android:summaryOn="Enabled \n> You must also enable custom colors and modify them or the dialpad will not be very visible."
android:title="Enable custom background"/>
<com.wubydax.romcontrol.v2.prefs.MyListPreference
android:defaultValue="0"
android:dependency="enable_dialer_custom_bg"
android:entries="@array/custom_bg_type_entries"
android:entryValues="@array/custom_bg_type_values"
android:key="dialer_custom_bg_type"
android:title="Background type"/>
<com.wubydax.romcontrol.v2.prefs.UriSelectionPreference
android:dependency="enable_dialer_custom_bg"
android:key="dialer_bg"
android:title="Select image for Background"/>
<com.wubydax.romcontrol.v2.prefs.MyListPreference
android:defaultValue="0"
android:dependency="enable_dialer_custom_bg"
android:entries="@array/crop_entries"
android:entryValues="@array/crop_values"
android:key="dialer_crop_type"
android:title="Set Image Scaling Type"/>
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference
android:defaultValue="#00000000"
android:dependency="enable_dialer_custom_bg"
android:key="dialer_bg_primary_color"
android:title="Select primary color"/>
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference
android:defaultValue="#00000000"
android:dependency="enable_dialer_custom_bg"
android:key="dialer_second_gradient_color"
android:title="Secondary Color (for gradient)"/>
<com.wubydax.romcontrol.v2.prefs.MyListPreference
android:defaultValue="0"
android:dependency="enable_dialer_custom_bg"
android:entries="@array/gradient_entries"
android:entryValues="@array/gradient_values"
android:key="dialer_bg_gradient_orientation"
android:title="Gradient orientation"/>
<com.wubydax.romcontrol.v2.prefs.MySeekBarPreference
android:defaultValue="255"
android:dependency="enable_dialer_custom_bg"
android:key="dialer_opacity"
app:maxValue="255"
android:title="Background Opacity"/>
<PreferenceCategory
android:title="Dialer Colors - disable if Theme conflicts" />
<com.wubydax.romcontrol.v2.prefs.FilePreference
android:title="Digit and Letter Colors On/Off Toggle"
android:key="modcfg_theme_override"
android:defaultValue="false"
android:summaryOn="Colors enabled"
android:summaryOff="Colors disabled" />
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference
android:title="Dialer Digits"
android:key="main_digit_color"
android:summary="Set digit color"
android:dependency="modcfg_theme_override"
app:packageNameToKill="com.android.contacts"
android:defaultValue="#ff000000" />
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference
android:title="Dialer Letters"
android:key="main_letter_color"
android:summary="Choose letter color"
android:dependency="modcfg_theme_override"
app:packageNameToKill="com.android.contacts"
android:defaultValue="#ff000000" />
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference
android:title="Dialer Divider"
android:key="main_divider_color"
android:summary="Choose divider color"
android:dependency="modcfg_theme_override"
android:defaultValue="#ff000000" />
<com.wubydax.romcontrol.v2.prefs.ColorPickerPreference
android:title="Dialer Digits Pressed"
android:key="main_digit_color_pressed"
android:summary="Set digit color"
android:dependency="modcfg_theme_override"
android:defaultValue="#ff000000" />
</PreferenceScreen>
Thursday, 28 July 2016
[GUIDE] Fix On Stuck TWRP Reboot Bug w/o Odin
How To Fix Stuck On TWRP Reboot Bug
For TWRP 2.8.4.0 and up only
For TWRP 2.8.4.0 and up only
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
If you ever encountered a TWRP bug like when you reboot, instead of rebooting into the system. You're rebooting in TWRP recovery again and again and again. So i have a simple fix that i've found out..
This will revert your phone's recovery to stock recovery. And make sure that your TWRP version is 2.8.4.0 Above
This is just another way of resolving the bug. Specially if you do not have a PC. And just a copy of file needed for this fix.
So let's get started.
1. First. Download CF-Auto-Root for your specific device.
Download CF-Auto-Root Here
2. Extract it and get the .tar file.
3. Extract the .tar file and take the recovery.img and put it on your External Sdcard or Internal Storage.
4. Now, open TWRP Recovery and select install.
5. On your Corner of the screen. Find and tap Images..
6. Now locate your recovery.img and select it.
7. It will prompt a selection. Select Recovery and Install.
8. After flashing, go back to your home screen of your TWRP Recovery and Select Power then Power off. Do not flash SuperSU if it prompts. Just ignore it.
9. After turning off. Open up your device again and SuperSU Installing screen will pop up. Just wait a few seconds and it will flash stock recovery..
If it turns off after flashing stock recovery, power it on again and it should work.
Let me know if it also works on you.
Good Luck ! :good: :fingers-crossed: ]
Wednesday, 27 July 2016
Lg k7 Viper4 android guide
Requirements:*
-Root
-Busybox
-Custom recovery
Installation:
1.- Deactivate NuPlayer in developer options.
2.- Deactivate any other equalizer.
3.- Set selinux to permissive with an app
Download link for viper
http://forum.xda-developers.com/atta...3&d=1428464518
4. Reboot to twrp flash viper.
5.reboot. Open viper. You have to install driver i used middle one.
6.click enable viper inside app. And force viper.
Also set user ui to expert in settings for extra options.
Make sure to give thanks to the viper team
-Root
-Busybox
-Custom recovery
Installation:
1.- Deactivate NuPlayer in developer options.
2.- Deactivate any other equalizer.
3.- Set selinux to permissive with an app
Download link for viper
http://forum.xda-developers.com/atta...3&d=1428464518
4. Reboot to twrp flash viper.
5.reboot. Open viper. You have to install driver i used middle one.
6.click enable viper inside app. And force viper.
Also set user ui to expert in settings for extra options.
Make sure to give thanks to the viper team
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Wileyfox Swift
Creating custom splash.img for Wileyfox Swift:
Note:
This is not bootanimation, this is the splash screen (the 'Wileyfox' logo which is displayed when device is switched ON)
This is for Wileyfox Swift only..
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
STEPS:
1. Make sure you have a picture for your custom splash with:
i. Resolution: 720x1280
ii. PNG or JPG format
iii. picture size less than 200kB
iv. less colorful
(Tip: Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 16 or below & download it)
2. Download this tool to your computer: CM_Splash_Maker.zip
And extract it.
3. Drag & drop your splash picture on the file "CREATE_Logo.bat" & select your device.
4. After the custom splash image (filename.img) is created, the output directory will be opened..
5. Transfer the filename.img to the device's internal storage & flash it using Terminal Emulator like:
(Or you can flash it from fastboot as given below)
Note:
Incase you flashed & your device doesn't bootup, don't worry ;)
Just flash the original splash.img from fastboot like:
Credits:
1. Based on my original tool for Yu devices here..
2. @GokulNC (myself ;)) who created this tool..
3. @beroid (who provided the stock splash.img & tested this).
Hit the Thanks :good: button if it worked for you ;)
You're welcome to post the custom splash screens that you made :)
Note:
This is not bootanimation, this is the splash screen (the 'Wileyfox' logo which is displayed when device is switched ON)
This is for Wileyfox Swift only..
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
STEPS:
1. Make sure you have a picture for your custom splash with:
i. Resolution: 720x1280
ii. PNG or JPG format
iii. picture size less than 200kB
iv. less colorful
(Tip: Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 16 or below & download it)
2. Download this tool to your computer: CM_Splash_Maker.zip
And extract it.
3. Drag & drop your splash picture on the file "CREATE_Logo.bat" & select your device.
4. After the custom splash image (filename.img) is created, the output directory will be opened..
5. Transfer the filename.img to the device's internal storage & flash it using Terminal Emulator like:
Code:
dd if=/sdcard/filename.img of=/dev/block/bootdevice/by-name/splash
Note:
Incase you flashed & your device doesn't bootup, don't worry ;)
Just flash the original splash.img from fastboot like:
Code:
fastboot flash splash splash.img
1. Based on my original tool for Yu devices here..
2. @GokulNC (myself ;)) who created this tool..
3. @beroid (who provided the stock splash.img & tested this).
Hit the Thanks :good: button if it worked for you ;)
You're welcome to post the custom splash screens that you made :)
Monday, 25 July 2016
Guide to upgrade KII-L21 to MM & active FP of Custom Roms.
Dear XDA & Fellow Community Members,
This Guide is for KII-L21 variant ONLY!
& hereby declare that not I nor XDA is responsible for any damage & or WW3 trigger of your device.
Try at your own risk.
Assuming you have variant KII-L21 ( cust version : C636D00x/C185D00x )
& also on stock LP firmware, rooted, bootloader unlocked, TWRP installed.
if not, search forum for BL unlock,rooting & TWRP installation guide.
Step 1 : Take a clean Nandroid of existing installation of your device.
Step 2: Flash stock recovery via ADB & Fastboot of your last known stock rom installed
this one worked for me : https://www.androidfilehost.com/?fid=24545070682210594
Command : adb reboot bootloader
fastboot devices
fastboot flash recovery *recovery img name*.img
Step 3 : Download your exact firmware.According to cust version stated in "About Phone" of your last stock rom.
( cust version : C636D00x/C185D00x )
Cust : C636D00x >>> http://consumer.huawei.com/vn/mobile...n.htm?id=82266
Cust : C185D00x >>> http://forum.xda-developers.com/hono...tered-t3388491
Step 4 : Extract the zip & copy dload folder to your SD card. It'd be safer if a high speed fresh SD is used I suppose.
Step 5: Turn off your Device, the press the Volume up+Volume Down+power button at same time for 10 seconds,
then release the power button only. you'll see firmware upgrading. wait for upgrade to finish.
Step 6 : If you wish , you can set up EMUI, but not mandatory. now, flash TWRP again.
Step 7 : Download any build newer than 20th july of CM , download gapps Nano, flash together via TWRP
if any error is found, just factory reset from TWRP & flash again.
CM Thread : http://forum.xda-developers.com/hono...ghtly-t3344499
Step 8 : First boot might take few minutes, after booting, set up CM. Voila !!! FP works like charm ^_^
Extra steps >>>>>
if you want FP on Ressurection Remix, just dirty flash RR latest build just after setting up CM. it worked for me, not sure if it will work for you or not. :confused: if found boot loop, i'll suggest waiting for @maxprzemo to update RR.
& Again, Thanks to @crpalmer & @BadDaemon for everything they have done for our device. :good:
& also thanks to al the moderators & whole XDA community ^_^ :good:
:highfive: :highfive: :highfive:
This Guide is for KII-L21 variant ONLY!
& hereby declare that not I nor XDA is responsible for any damage & or WW3 trigger of your device.
Try at your own risk.
Assuming you have variant KII-L21 ( cust version : C636D00x/C185D00x )
& also on stock LP firmware, rooted, bootloader unlocked, TWRP installed.
if not, search forum for BL unlock,rooting & TWRP installation guide.
Step 1 : Take a clean Nandroid of existing installation of your device.
Step 2: Flash stock recovery via ADB & Fastboot of your last known stock rom installed
this one worked for me : https://www.androidfilehost.com/?fid=24545070682210594
Command : adb reboot bootloader
fastboot devices
fastboot flash recovery *recovery img name*.img
Step 3 : Download your exact firmware.According to cust version stated in "About Phone" of your last stock rom.
( cust version : C636D00x/C185D00x )
Cust : C636D00x >>> http://consumer.huawei.com/vn/mobile...n.htm?id=82266
Cust : C185D00x >>> http://forum.xda-developers.com/hono...tered-t3388491
Step 4 : Extract the zip & copy dload folder to your SD card. It'd be safer if a high speed fresh SD is used I suppose.
Step 5: Turn off your Device, the press the Volume up+Volume Down+power button at same time for 10 seconds,
then release the power button only. you'll see firmware upgrading. wait for upgrade to finish.
Step 6 : If you wish , you can set up EMUI, but not mandatory. now, flash TWRP again.
Step 7 : Download any build newer than 20th july of CM , download gapps Nano, flash together via TWRP
if any error is found, just factory reset from TWRP & flash again.
CM Thread : http://forum.xda-developers.com/hono...ghtly-t3344499
Step 8 : First boot might take few minutes, after booting, set up CM. Voila !!! FP works like charm ^_^
Extra steps >>>>>
if you want FP on Ressurection Remix, just dirty flash RR latest build just after setting up CM. it worked for me, not sure if it will work for you or not. :confused: if found boot loop, i'll suggest waiting for @maxprzemo to update RR.
& Again, Thanks to @crpalmer & @BadDaemon for everything they have done for our device. :good:
& also thanks to al the moderators & whole XDA community ^_^ :good:
:highfive: :highfive: :highfive:
[Guide] Backup ,restore imei and fix invalid imei number
Requirements :
Imei number
Mobile unkle tools
Es file explorer
Fixing invalid imei
This method dosent require root
Install and open mobile unkle tools
Go to engeeniring mode (MTK)
Under connectivity open cds information
Click radio indormation
Open phone 1
Type in the box
AT+ EGMR=1,7,"Enter your imei number here"
Press sent command
Reboot
In phone 2
Type
AT+ EGMR=1,10,"Enter your imei number here"
Reboot
Do not forget to add space between AT+and EGMR
And your imei has been added
Backing up imei
Requires root
Open es file manager grant root permissions
Go to /data/nvram/md/nvram/
Copy the whole nvd_imei Filder to your sdcard
And this filder is your imei backup
Another way of backing up imei
Use mobile unkle tools and click in backup imei to sdcard
This creates a imei backup in another format but restoring imei is not allways sucess full using this method
Restoring imei
Requires root
just paste the nvd imei folder in
/data/nvram/md/nvram/
And reboot
Imei restored
Using mobile unkle tools
Click restore imei from sdcard
And then reboot
This method not restore imei allways in higher androod versions like marshmallow
Thanks
Hope you like this guide:good::laugh:
Imei number
Mobile unkle tools
Es file explorer
Fixing invalid imei
This method dosent require root
Install and open mobile unkle tools
Go to engeeniring mode (MTK)
Under connectivity open cds information
Click radio indormation
Open phone 1
Type in the box
AT+ EGMR=1,7,"Enter your imei number here"
Press sent command
Reboot
In phone 2
Type
AT+ EGMR=1,10,"Enter your imei number here"
Reboot
Do not forget to add space between AT+and EGMR
And your imei has been added
Backing up imei
Requires root
Open es file manager grant root permissions
Go to /data/nvram/md/nvram/
Copy the whole nvd_imei Filder to your sdcard
And this filder is your imei backup
Another way of backing up imei
Use mobile unkle tools and click in backup imei to sdcard
This creates a imei backup in another format but restoring imei is not allways sucess full using this method
Restoring imei
Requires root
just paste the nvd imei folder in
/data/nvram/md/nvram/
And reboot
Imei restored
Using mobile unkle tools
Click restore imei from sdcard
And then reboot
This method not restore imei allways in higher androod versions like marshmallow
Thanks
Hope you like this guide:good::laugh:
[GUIDE] Installing Xposed on Stock ROM
Getting Xposed up and running on this thing is pretty simple once your rooted, but I got a request to make this, and I don't want anyone breaking their phone while they're trying to get it installed, so I made a guide.
Before you begin, you'll need your phone rooted with SuperSU (systemless root). My phone is the Amazon Prime version running stock ROM version 6.1, but I'm sure this will work fine on the later version, or the non-Prime version of the phone. You also must have TWRP installed. Not really sure how you got root without having TWRP, but you do need it.
As always, you're doing this at your own risk. It's not my fault if your phone gets bricked, damaged, or becomes sentient and plots with other Android devices to kill you and your cat.
With all that out of the way, let's get started here.
1. First, you need DVDandroid's Material Design Xposed installer. It's a really great alternative to the official Xposed installer and I prefer it on all my devices. You can download it from this thread.
2. After installing that, open it up. You'll be greeted with a screen telling you to be careful and that this could damage your device. Dismiss it.
3. Slide over to the systemless tab in the Xposed installer. The official version of Xposed framework will probably work fine, but I prefer using the systemless version wherever I'm using systemless root. I've had a higher success rate with it.
4. From the top dropdown, choose xposed-(version)-sdk23-topjohnwu, where (version) is replaced with the latest version of the file. This should be selected by default, but double check.
5. Click Install/Update. Xposed installer will give you a few warnings and ask for root access, but at the end of it all, your phone will reboot.
6. The rest is automatic. Your phone will boot into TWRP, where it will run a couple scripts, and then reboot back into the system. The first boot process will take a long time, and might even loop once or twice. It will also rebuild the caches for every app on your phone, so it will take a while. Once it finally finishes, you should be booted to Android with Xposed framework enabled!
That's it! Install your favourite modules and play with your phone to your heart's content!
Also note that after performing these steps, your device will take a long time to boot up. The Xposed framework simply being initialized will make your phone take much longer to start up than normal. Every additional module you enable will also make your phone take a little longer to boot. You can disable the Xposed framework in the Xposed Status tab of the Xposed Installer using the switch at the top. This will disable Xposed and your phone will boot quickly again (without even removing Xposed!), so you can use this as a hotswitch for enabling/disabling Xposed (if that makes sense in your use-case). Removal of Xposed is also pretty straightforward. Just head over to the systemless tab in Xposed Installer and click the Uninstall button. I've never personally tried this because I see no reason for it, but I can't imagine why it would break anything.
Before you begin, you'll need your phone rooted with SuperSU (systemless root). My phone is the Amazon Prime version running stock ROM version 6.1, but I'm sure this will work fine on the later version, or the non-Prime version of the phone. You also must have TWRP installed. Not really sure how you got root without having TWRP, but you do need it.
As always, you're doing this at your own risk. It's not my fault if your phone gets bricked, damaged, or becomes sentient and plots with other Android devices to kill you and your cat.
With all that out of the way, let's get started here.
1. First, you need DVDandroid's Material Design Xposed installer. It's a really great alternative to the official Xposed installer and I prefer it on all my devices. You can download it from this thread.
2. After installing that, open it up. You'll be greeted with a screen telling you to be careful and that this could damage your device. Dismiss it.
3. Slide over to the systemless tab in the Xposed installer. The official version of Xposed framework will probably work fine, but I prefer using the systemless version wherever I'm using systemless root. I've had a higher success rate with it.
4. From the top dropdown, choose xposed-(version)-sdk23-topjohnwu, where (version) is replaced with the latest version of the file. This should be selected by default, but double check.
5. Click Install/Update. Xposed installer will give you a few warnings and ask for root access, but at the end of it all, your phone will reboot.
6. The rest is automatic. Your phone will boot into TWRP, where it will run a couple scripts, and then reboot back into the system. The first boot process will take a long time, and might even loop once or twice. It will also rebuild the caches for every app on your phone, so it will take a while. Once it finally finishes, you should be booted to Android with Xposed framework enabled!
That's it! Install your favourite modules and play with your phone to your heart's content!
Also note that after performing these steps, your device will take a long time to boot up. The Xposed framework simply being initialized will make your phone take much longer to start up than normal. Every additional module you enable will also make your phone take a little longer to boot. You can disable the Xposed framework in the Xposed Status tab of the Xposed Installer using the switch at the top. This will disable Xposed and your phone will boot quickly again (without even removing Xposed!), so you can use this as a hotswitch for enabling/disabling Xposed (if that makes sense in your use-case). Removal of Xposed is also pretty straightforward. Just head over to the systemless tab in Xposed Installer and click the Uninstall button. I've never personally tried this because I see no reason for it, but I can't imagine why it would break anything.
Root Guide eUI 5.6 / 5.8
Root your phone at your OWN RISK
Instructions:
- Install MTK_X20Drivers
- Enable Developer mode
- Enable USB debugging in developer mode.
- Enable OEM unlocking
1. Download the FlashTool for yours version of eUI - 5.6 or 5.8
2. Enter Fastboot mode, reboot the phone whilst pressing Power On + Volume Down
3. Open adb_cmd.exe
4. Write fastboot oem unlock - (expects to complete the command)
5. Write fastboot flash recovery Letv-X620-Twrp-3.0.2-0.img - (expects to complete the command)
Now you should have TWRP installed !
Hold Power Button and Volume Up button to reboot into TWRP. Change in English language with right button.
- Flash no-verity-opt-encrypt.zip. If you do not do this you will not be able to boot your phone!
- Flash SuperSu .
That's all !!!
Instructions:
- Install MTK_X20Drivers
- Enable Developer mode
- Enable USB debugging in developer mode.
- Enable OEM unlocking
1. Download the FlashTool for yours version of eUI - 5.6 or 5.8
2. Enter Fastboot mode, reboot the phone whilst pressing Power On + Volume Down
3. Open adb_cmd.exe
4. Write fastboot oem unlock - (expects to complete the command)
5. Write fastboot flash recovery Letv-X620-Twrp-3.0.2-0.img - (expects to complete the command)
Now you should have TWRP installed !
Hold Power Button and Volume Up button to reboot into TWRP. Change in English language with right button.
- Flash no-verity-opt-encrypt.zip. If you do not do this you will not be able to boot your phone!
- Flash SuperSu .
That's all !!!
Sunday, 24 July 2016
[Guide] [TOOL] One-Click Flash your Redmi 3 with many rom
Hey, everyone! Now we introduce you our product: King Flasher.
It's an one-click flash tool for android users.
You can easily flash both CM, MIUI, Flyme, ResurrectionRemix, XOSP, Bliss and many other rom with this tool.
For those who don't have a PC, we are going to make a mobile version.
Go to download: King Flasher
[Guide]:
1. Install King Flasher on your computer and make sure it can access to the internet.
2. Connect your phone to computer with USB cable and open USB debbuging.
How to open USB debbuging: Settings > About device > Tap BUILD NUMBER 7 times > Back to Settings > Developer options > Select USB Debbuging.
3. Please open King Flasher and choose a ROM you like, then click Flash.

4. Wait for downloading ROM.

5. After the download finished, King Flasher will flash your phone automaticlly. It will take about 5-10 minutes to finish.

6. Your phone will reboot to the new system when it finish.

It's an one-click flash tool for android users.
You can easily flash both CM, MIUI, Flyme, ResurrectionRemix, XOSP, Bliss and many other rom with this tool.
For those who don't have a PC, we are going to make a mobile version.
Go to download: King Flasher
[Guide]:
1. Install King Flasher on your computer and make sure it can access to the internet.
2. Connect your phone to computer with USB cable and open USB debbuging.
How to open USB debbuging: Settings > About device > Tap BUILD NUMBER 7 times > Back to Settings > Developer options > Select USB Debbuging.
3. Please open King Flasher and choose a ROM you like, then click Flash.

4. Wait for downloading ROM.

5. After the download finished, King Flasher will flash your phone automaticlly. It will take about 5-10 minutes to finish.

6. Your phone will reboot to the new system when it finish.

[guide] ( need root) how to use fingerprint button as home, back and recents button.
If you want to use the fingerprint sensor as capacitive button and remove the on screen buttons, here are how to do it. TESTED ON XT 1640 (BRAZIL VERSION)
First you need to root and install TWRP recovery. take a look on the other threads for it.
Install the EX Kernel from here (http://forum.xda-developers.com/moto...-0-01-t3424836) [ READ THIS THREAD FOR MORE INFORMATION ABOUT COMPATIBILITY]
If everything works fine, this kernel makes you fingerprint work as home button, but to have others functions, intall this app ( http://forum.xda-developers.com/andr...dware-t3361340)
Now you can remapp as your wish.
TO REMOVE THE ON SCREEN BUTTONS:
Use any build.prop editor and just add this line ( qemu.hw.mainkeys=1 )
post your screenshots if you enjoy it.
thanks to flar2 for the kernel and app.
First you need to root and install TWRP recovery. take a look on the other threads for it.
Install the EX Kernel from here (http://forum.xda-developers.com/moto...-0-01-t3424836) [ READ THIS THREAD FOR MORE INFORMATION ABOUT COMPATIBILITY]
If everything works fine, this kernel makes you fingerprint work as home button, but to have others functions, intall this app ( http://forum.xda-developers.com/andr...dware-t3361340)
Now you can remapp as your wish.
TO REMOVE THE ON SCREEN BUTTONS:
Use any build.prop editor and just add this line ( qemu.hw.mainkeys=1 )
post your screenshots if you enjoy it.
thanks to flar2 for the kernel and app.
[GUIDE] Xposed on P9 Lite
Hey everyone!
Since there is no dedicated thread for how to install Xposed for the P9 Lite yet, I thought I quickly provide the method how I made it work for future users.
What you need?
- Unlocked BL
- TWRP Installer
- Root
So you want to get the version of Xposed provided by Wanam. Version 86 for arm64 is what you are looking for! You can get it here:
http://forum.xda-developers.com/xpos...t3180960/page1
Don't worry that it says Samsung devices in the thread.
Download the zip package that you need and place it somewhere. Then download the Xposed installer apk.
For example here in the first post attached:
http://forum.xda-developers.com/show...3034811&page=1
Install the apk.
Now it's time to fire up TWRP and make a backup!
Then flash the zip you have downloaded before. If you downloaded the right version, it should flash without errors.
Now reboot. BE PATIENT. It can take several minutes for the first boot.
That's it. You should now be able to use Xposed modules :victory:
Sidenote: some people mentioned that you may need to switch your SELinux mode to permissive. Since I had it on permissive in the first place I don't know if it's really the case.
PS: leave a like for the guys providing these awesome Xposed frameworks if you download them :good:
Since there is no dedicated thread for how to install Xposed for the P9 Lite yet, I thought I quickly provide the method how I made it work for future users.
What you need?
- Unlocked BL
- TWRP Installer
- Root
So you want to get the version of Xposed provided by Wanam. Version 86 for arm64 is what you are looking for! You can get it here:
http://forum.xda-developers.com/xpos...t3180960/page1
Don't worry that it says Samsung devices in the thread.
Download the zip package that you need and place it somewhere. Then download the Xposed installer apk.
For example here in the first post attached:
http://forum.xda-developers.com/show...3034811&page=1
Install the apk.
Now it's time to fire up TWRP and make a backup!
Then flash the zip you have downloaded before. If you downloaded the right version, it should flash without errors.
Now reboot. BE PATIENT. It can take several minutes for the first boot.
That's it. You should now be able to use Xposed modules :victory:
Sidenote: some people mentioned that you may need to switch your SELinux mode to permissive. Since I had it on permissive in the first place I don't know if it's really the case.
PS: leave a like for the guys providing these awesome Xposed frameworks if you download them :good:
Root Guide for Noob
Installing a custom recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
Make sure your computer has working fastboot and adb.
Download recovery -- visit twrp.me to obtain the latest version of Recovery for your device.
Connect the {{{device_name}}} to the computer via USB.
Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
Once the flash completes successfully, reboot the device into recovery to verify the installation.
See All About Recovery Images for more information about custom recoveries and their capabilities.
Make sure your computer has working fastboot and adb.
Download recovery -- visit twrp.me to obtain the latest version of Recovery for your device.
Connect the {{{device_name}}} to the computer via USB.
Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
Once the flash completes successfully, reboot the device into recovery to verify the installation.
Friday, 22 July 2016
[Guide] Stock Miui (7/8): Official unlock, recovery, root, xposed, DPI & debloat
Please read this thread thoroughly and carefully. Do this at your own risk. The following had worked for two of the same devices. I've made this guide partly for my own notes and because other guides out there seemed incomplete.
Aim of this guide is to have an unlocked bootloader so that you can use Alka recovery to enable root, busybox and Xposed on stock Miui. Alka is a good recovery to use since it's already patched (boot.img) so that it can flash Miui recovery ROMs (OTA?) as well as CM based ROMs. It also has the ability to backup the entire phone (EFS partition). I would strongly suggest backing up all partitions and moving it to your computer or SD card after. You may choose Cofface TWRP if you're never going to try CM based ROMs. Helpful links from other guides will be posted at the end.
Debloating is a big thing that I do to stock ROMs. This essentially prevents the ROM from running the apps, slimming the ROM and hopefully extending daily usage. There are few things that broke though. The only thing I could care about is that I'm not able to change the wallpaper via the Settings (lockscreen + homescreen) anymore. The rest that broke are the features that I don't use such as Cleaner (sponsored by Cheetah), dual apps and etc. Debloat accordingly, be cautious as I won't be necessarily explaining what each item does.
Prep work
Sign up and login to all the neccessary accounts
Using MiFlash tool to flash another Miui ROM (China to Global, skip if you already like your Miui version)
Flashing TWRP (Alka) & Root
Download the following files:
Follow these, don't reboot in between unless stated:
Flashing Xposed
Download the latest SolarWarez Xposed: http://forum.xda-developers.com/xpos...-miui-t3367634
Download Material Xposed Installer: http://forum.xda-developers.com/xpos...aller-t3137758
Download Xposed uninstaller, just in case: http://forum.xda-developers.com/show....php?t=3034811
A few posts suggests that the latest official Xposed v86 works with Miui, but doesn't seem to be the case for me.
Xposed modules that I use:
Changing DPI
Using FX Explorer (Root access enabled) or any explorer you feel fit.
ROM Debloating
Using FX Explorer (Root access enabled) or any explorer you feel fit.
Create the backup location:
Debloat app folder as you wish but here's my list:
Aim of this guide is to have an unlocked bootloader so that you can use Alka recovery to enable root, busybox and Xposed on stock Miui. Alka is a good recovery to use since it's already patched (boot.img) so that it can flash Miui recovery ROMs (OTA?) as well as CM based ROMs. It also has the ability to backup the entire phone (EFS partition). I would strongly suggest backing up all partitions and moving it to your computer or SD card after. You may choose Cofface TWRP if you're never going to try CM based ROMs. Helpful links from other guides will be posted at the end.
Debloating is a big thing that I do to stock ROMs. This essentially prevents the ROM from running the apps, slimming the ROM and hopefully extending daily usage. There are few things that broke though. The only thing I could care about is that I'm not able to change the wallpaper via the Settings (lockscreen + homescreen) anymore. The rest that broke are the features that I don't use such as Cleaner (sponsored by Cheetah), dual apps and etc. Debloat accordingly, be cautious as I won't be necessarily explaining what each item does.
Prep work
Sign up and login to all the neccessary accounts
- Sign up for unlock: http://en.miui.com/unlock/, this will take 3-4 days.
- Make sure you're also signed into your Mi account on your phone and that you can find your phone at http://i.mi.com/.
Enable Windows TESTSIGNING first: https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspxRestart your computer and then install the following:
The TESTSIGNING boot configuration option is enabled or disabled through the BCDEdit command. To enable test-signing, use the following BCDEdit command:
Bcdedit.exe -set TESTSIGNING ON
To disable test-signing, use the following BCDEdit command:
Bcdedit.exe -set TESTSIGNING OFF
- Mi PC Suite (http://pcsuite.mi.com/)
- Mi ROM Flashing Tool and drivers for fastboot & ADB (http://en.miui.com/a-234.html)
- Mi FlashUnlock tool (http://en.miui.com/thread-202290-1-1.html)
- Fastboot EDL, just in case (http://forum.xda-developers.com/redm...-test-t3398718)
- Enable developer mode by going to Settings > About phone > Tap on MIUI Version repeatedly until you get a toast that Developer Mode is enabled
- Go back to Settings and then tap on Additional Settings > Developer options
- Enable Developer options
- Enable OEM unlock
- Enable USB debugging
- Plugin your phone into your computer, it should now install all the drivers
- Turn TESTSIGNING OFF and restart your computer
- In Device Manager, you should see under Android Phone: Android Composite ADB Interface and Xiaomi Composite MDB Interface
- You phone should have also asked you to allow debugging from your computer (check always allow)
Using MiFlash tool to flash another Miui ROM (China to Global, skip if you already like your Miui version)
- Boot into fastboot by holding volume-down + power, you will get the fastboot bunny
- Download your desired fastboot version: http://en.miui.com/a-234.html, you can check the changelog and description from here: http://en.miui.com/download-301.html
- Or you can use Miui 8 Global Beta: http://forum.xda-developers.com/redm...ote-3-t3417423
- Extract the fastboot ROM (.tgz) twice, the first extract you'll be left with .tar file, the second should leave you with a directory of files
- Place that directory in the root of your drive (or somewhere with a short location)
- Launch the MiFlash tool, browse to your extracted fastboot ROM and click on refresh. You should now also see your device listed
- Click on Flash All and click on refresh once more
- Now flash your device, it should take upwards of 170s
Flashing TWRP (Alka) & Root
Download the following files:
- TWRP https://dl.twrp.me/kenzo/
- Alka http://www.mediafire.com/download/fe...lka+Update.zip
- Universal Boot Img Patcher http://forum.xda-developers.com/redm...sboot-t3371667
- SuperSU https://download.chainfire.eu/969/SuperSU/
Follow these, don't reboot in between unless stated:
- Enter fastboot (volume-down + power)
- Type fastboot flash recovery twrp.img
- Swipe to allow modifications
- Flash universal boot img patcher zip
- Flash twrp.img by selecting "Select Image" option.
- Select recovery partition & flash it
- Now reboot to recovery
- Flash alkarecoveryupdate.img by selecting "Select Image" option.
- Reboot to recovery
- Flash SuperSU
- Reboot system and let it boot Miui, it may take longer than usual
Flashing Xposed
Download the latest SolarWarez Xposed: http://forum.xda-developers.com/xpos...-miui-t3367634
Download Material Xposed Installer: http://forum.xda-developers.com/xpos...aller-t3137758
Download Xposed uninstaller, just in case: http://forum.xda-developers.com/show....php?t=3034811
A few posts suggests that the latest official Xposed v86 works with Miui, but doesn't seem to be the case for me.
- Install the Xposed Installer of your choice (apk install)
- Enter recovery (volume-up + power)
- Flash v86-sdk22-arm64 (LP, sdk23 is for MM)
- Clear cache and dalvik
- Reboot the phone, this should take 5m or longer since we wiped the cache
Xposed modules that I use:
- App Settings
- MIUI Brightness Fix
- Mobile Radio Active Fix
- Power Nap
- Play Store Fixes
- Spotify Skip
- TextLinkify
- WhatsApp Tuner
- xMIUI
- xInsta unfortunately does not work well.
Changing DPI
Using FX Explorer (Root access enabled) or any explorer you feel fit.
- Go to system/ and edit build.prop
- Add this line in between persist.hwc.downscale_threshold=1.15 & #ro.hdmi.enable=true
ro.sf.ldc_density=370
- Reboot your phone
ROM Debloating
Using FX Explorer (Root access enabled) or any explorer you feel fit.
Create the backup location:
- Create a folder in system named _backup
- Create subfolders named app, data-app, priv, vendor
Debloat app folder as you wish but here's my list:
- Go to system/app
- Cut the following into system/_backup/app
AGPSTestMode
AmapITS
AnalyticsCore
AntHalService
BasicDreams
BrowserProviderProxy
BugReport
CalendarLocalAccount
CalendarWidget
Drive
Email
FM
Galaxy4
GuardProvider
HTMLViewer
HiddTestApp
HoloSpiralWallpaper
KSICibaEngine
KingSoftCleaner
LatinImeGoogle
LiveWallpapers
LiveWallpapersPicker
LunarInfoProvider
MiDiscover
MiLivetalk
MiWallpaper
NoiseField
Notes
OmaDownload
OmaDrmEngineApp
PartnerBookmarksProvider
PhaseBeam
PhotoTable
QtiBackupAgent
QtiFeedback
SampleAuthenticatorService
SapClientApp
SecureSampleAuthService
StaProxyService
StepsProvider
Stk
SystemAdSolution
TouchAssistant
Videos
WAPPushManager
WfdClient
fastdormancy
imstests
jjcontainer
jjhome
jjknowledge
jjstore
- Go to system/data-app
- Cut the following into system/_backup/data-app
Facebook
klobugreport
- Go to system/priv
- Cut the following into system/_backup/priv
AndroidForWork
AutoTest
BackupRestoreConfirmation
Browser
Calendar
CleanMaster
FM2
GoogleBackupTransport
GoogleFeedback
SpacesManagerService
SpacesTrustAgent
Velvet
cit
- Go to system/vendor
- Cut the following into system/_backup/vendor
CTA
ChinaMobile
ChinaTelecom
ChinaUnicom
CmccPower
MPCS
app
[GUIDE] [XPOSED] Move Around In POKEMON GO w/o actually MOVING AROUND!
Prerequisites ROOTED PHONE with Xposed Installer v85
i am using this method my account is still active ;)
Caution : use it At your own Risk i am Not Responsible for your Account Banned
THANKS TO THE APP DEVELOPER FOR HIS HARDWORK :D
1. Download and activate in Xposed installer.
2. Reboot the device to complete activation.
3. Go to Settings go to Developer Options and check Allow Mock Location.
4. If you are on Android 6 or above, please grant Location and Draw over other apps permissions.
5. Press and hold on the Map to set your initial location.
6. Press the play button to display the controls, you can drag it around screen by holding on the right or left of the N button.
7. Long press the N button to stop the service.
VIDEO GUIDE
Link : youtube.com/watch?v=JlNqkLRdbdE
HAVE FUN LAZY BUMS:D;)
i am using this method my account is still active ;)
Caution : use it At your own Risk i am Not Responsible for your Account Banned
THANKS TO THE APP DEVELOPER FOR HIS HARDWORK :D
1. Download and activate in Xposed installer.
2. Reboot the device to complete activation.
3. Go to Settings go to Developer Options and check Allow Mock Location.
4. If you are on Android 6 or above, please grant Location and Draw over other apps permissions.
5. Press and hold on the Map to set your initial location.
6. Press the play button to display the controls, you can drag it around screen by holding on the right or left of the N button.
7. Long press the N button to stop the service.
VIDEO GUIDE
Link : youtube.com/watch?v=JlNqkLRdbdE
HAVE FUN LAZY BUMS:D;)
Thursday, 21 July 2016
[Guide] How to fix Android OS battery drain (stay awake) without root!
Hello guys! It has been a long time since I have been trying to sort out my drain issues on my S6 Edge+ , a couple of days ago I finally figured out to use Wakelock Detector without root then it comes out that it was actually the maps keeping the phone awake via "NLPWakelock" through Android OS. I will cover out the process step by step to found out which app is causing the drain and why! We will need ABD, so we must have a computer.
1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too.
Play store link: https://play.google.com/store/apps/d...r.noroot&hl=tr,
2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.

3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write
If the output is similar to the image below, it means you have ADB installed and if you have device entry you have your ADB device drivers installed too.
If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )
4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions:
At this point we may see a popup dialog on our phone like this:

You need to allow it and preferably you can check always allow option.
5) That's it guys. Now we have Wakelock detector working!

Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.
Notes:
Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.
Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!
1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too.
Play store link: https://play.google.com/store/apps/d...r.noroot&hl=tr,
2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.

3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write
Code:
adb devices
If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )
4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions:
Code:
adb -d shell pm grant com.uzumapps.wakelockdetector android.permission.BATTERY_STATS

You need to allow it and preferably you can check always allow option.
5) That's it guys. Now we have Wakelock detector working!

Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.
Notes:
Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.
Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!
Subscribe to:
Posts (Atom)